bd help --docs-root now additionally writes docs/cli-reference/ in Mintlify form (frontmatter title as H1, extensionless root-relative links, JSX auto-generated markers since Mintlify parses .md through MDX) and rewrites the CLI Reference pages array inside docs/docs.json via a textual splice that leaves the rest of the file byte-identical — the ~113 nav entries are never hand-maintained. The Docusaurus outputs (docs/CLI_REFERENCE.md, website/docs/cli-reference/, versioned snapshots) are unchanged. generate-cli-docs.sh --check seeds docs/docs.json and docs/cli-reference/ into its scratch root and diffs both; check-cli-docs-drift.sh adds them to GEN_PATHSPECS and the regeneration fingerprint; docs-autofix-push.sh allowlists the new generated paths; check-doc-flags.sh scans the new docs/ subdirectories and requires command coverage in docs/cli-reference/. Includes the initial docs/docs.json scaffold (nav mirrors the Docusaurus sidebar IA) and the generated docs/cli-reference/ pages. TDD: new emitter behavior covered in cmd/bd/help_all_test.go (Mintlify page format, nav splice correctness + idempotence, bare-root generation without docs.json).
73 lines
1.6 KiB
Markdown
73 lines
1.6 KiB
Markdown
---
|
|
title: "bd vc"
|
|
description: "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 [flags]
|
|
```
|
|
|
|
## 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]
|
|
```
|