* docs: generate CLI reference from live help * docs(cli): move bd version stamp from per-command pages to index only Drops the `(bd version X.Y.Z)` suffix from the auto-generated header on every per-command CLI reference page (writeSingleCommandDoc) and the docs/CLI_REFERENCE.md preamble (writeAllHelp). The version label now lives only on the index page emitted by scripts/generate-cli-docs.sh: - Dev tree (website/docs/cli-reference/index.md, docs/CLI_REFERENCE.md): labelled "Latest" - Versioned snapshots (website/versioned_docs/version-X.Y.Z/...): labelled with the explicit semver tag parsed from the directory name This eliminates the 100+-file no-signal diff a release version bump otherwise produces, restoring the "regen as a separate small commit" workflow PR #3704 enables. After this change a version bump alone yields zero diff on the dev tree; only the new versioned snapshot created at release-cut time carries the new tag. No datestamps are introduced anywhere — scripts/generate-cli-docs.sh --check remains deterministic across CI runs. Refs: mybd-afb, PR #3704 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: CI Bot <ci@beads.test> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.6 KiB
| id | title | slug | sidebar_position |
|---|---|---|---|
| vc | bd vc | /cli-reference/vc | 999 |
Generated from bd help --doc vc
bd 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
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