Three generated-content defects from the adversarial review, all structurally invisible to the drift gate (generated-vs-generated): - Usage lines now mirror Cobra's help template: a runnable command shows its UseLine, a command with subcommands shows '<path> [command]', both when both apply. Previously bare UseLine() stamped 'bd mol [flags]' on 30 parent pages — a line the binary never prints. - The generated CLI index publishes the Global Flags block; the binary prints it on every --help but no page carried it. - docsmint neutralizes prose lines that Mintlify's prebuild would dedent into MDX ESM blocks (a line beginning 'export'/'import' outside a fence gets wrapped in a code span). This is why /cli-reference/mail returned HTTP 200 while rendering only a parse-error placeholder — reproduced, fixed, and covered by a planted-hazard test; fenced content stays verbatim. Also rewords check-cli-docs-drift.sh's early-PASS message, which asserted 'the supplied binary differs' as the cause when uncommitted local edits produce the same result. All 113 pages + docs/CLI_REFERENCE.md regenerated through the pipeline; TDD'd in cmd/bd/help_all_test.go and tools/docsmint/docsmint_test.go. Verified live: /cli-reference/mail renders real content, zero parse errors; generate-cli-docs.sh --check, docsync, freshness, and mint broken-links all pass on this tree.
1.6 KiB
| title | description |
|---|---|
| bd vc | Version control operations |
{/* AUTO-GENERATED: do not edit manually */}
Generated from bd help --doc vc.
Version control operations for the beads database.
These commands provide git-like version control for your issue data, including branching, merging, and viewing history.
Note: 'bd history', 'bd diff', and 'bd branch' also work for quick access. This subcommand provides additional operations like merge and commit.
bd vc [command]
bd vc commit
Create a new Dolt commit with all current changes.
Examples: bd vc commit -m "Added new feature issues" bd vc commit --message "Fixed priority on several issues" echo "Multi-line message" | bd vc commit --stdin
bd vc commit [flags]
Flags:
-m, --message string Commit message
--stdin Read commit message from stdin
bd vc merge
Merge the specified branch into the current branch.
If there are merge conflicts, they will be reported. You can resolve conflicts with --strategy.
Examples: bd vc merge feature-xyz # Merge feature-xyz into current branch bd vc merge feature-xyz --strategy ours # Merge, preferring our changes on conflict bd vc merge feature-xyz --strategy theirs # Merge, preferring their changes on conflict
bd vc merge <branch> [flags]
Flags:
--strategy string Conflict resolution strategy: 'ours' or 'theirs'
bd vc status
Show the current branch, commit hash, and any uncommitted changes.
Examples: bd vc status
bd vc status [flags]