docs: sync dbc command output - #434
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
added
the
documentation
Member
|
Cool automation! I notice that this doesn't catch the verbose install output: https://docs.columnar.tech/dbc/guides/finding_drivers/#verbose |
Member
|
thanks for catching that. I'll fix that. |
Member
|
Closing in favor of #437 |
amoeba
added a commit
that referenced
this pull request
Jul 23, 2026
Adds some missing fences to commands that needed them and syncs the docs. This was pointed out in #434 (comment).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated update of
dbccommand output in docs.This PR was opened by the Sync Docs workflow after detecting that one or more annotated output blocks no longer match the output of the currently released
dbc.Review the diff before merging to confirm the changes look correct and there are no unexpected formatting regressions.