beads/website/versioned_docs/version-1.0.5/cli-reference/vc.md
matt wilkie b55472412b
docs: snapshot versioned docs for 1.0.5 release (#4246)
The v1.0.5 tag shipped with cmd/bd/version.go bumped to 1.0.5 but without
the Docusaurus version snapshot, so check-version-consistency (via
scripts/check-docs-version.sh) went red on main: versions.json and
docusaurus.config.ts lastVersion were still 1.0.4 and
website/versioned_docs/version-1.0.5 was missing.

Create the 1.0.5 docs snapshot to restore consistency:
- docusaurus docs:version 1.0.5 (versions.json + versioned_docs + sidebar)
- set docusaurus.config.ts lastVersion to 1.0.5
- regenerate versioned CLI reference (stamps "Reference for bd v1.0.5")
- regenerate website/static/llms-full.txt

Verified: scripts/check-versions.sh and scripts/check-doc-flags.sh pass.

Refs: mybd-4qku

Agent-Signature: claude-opus-4-8-medium on behalf of matt wilkie
2026-05-28 21:51:26 -07:00

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