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).
2.4 KiB
| title | description |
|---|---|
| bd repo | Manage multiple repository configuration |
{/* AUTO-GENERATED: do not edit manually */}
Generated from bd help --doc repo.
Configure and manage multiple repository support for multi-repo hydration.
Multi-repo support allows hydrating issues from multiple beads repositories into a single database for unified cross-repo issue tracking.
Configuration is stored in .beads/config.yaml under the 'repos' section:
repos: primary: "." additional: - ~/beads-planning - ~/work-repo
Examples: bd repo add ~/beads-planning # Add planning repo bd repo add ../other-repo # Add relative path repo bd repo list # Show all configured repos bd repo remove ~/beads-planning # Remove by path bd repo sync # Sync from all configured repos
bd repo [flags]
bd repo add
Add a repository path to the repos.additional list in config.yaml.
The path should point to a directory containing a .beads folder. Paths can be absolute or relative (they are stored as-is).
This modifies .beads/config.yaml, which is version-controlled and shared across all clones of this repository.
bd repo add <path> [flags]
Flags:
--json Output JSON
bd repo list
List all repositories configured in .beads/config.yaml.
Shows the primary repository (always ".") and any additional repositories configured for hydration.
bd repo list [flags]
Flags:
--json Output JSON
bd repo remove
Remove a repository path from the repos.additional list in config.yaml.
The path must exactly match what was added (e.g., if you added "/foo",
you must remove "/foo", not "/home/user/foo").
This command also removes any previously-hydrated issues from the database that came from the removed repository.
bd repo remove <path> [flags]
Flags:
--json Output JSON
bd repo sync
Synchronize issues from all configured additional repositories.
Reads issues.jsonl from each additional repository and imports them into the primary database with their original prefixes and source_repo set. Uses mtime caching to skip repos whose JSONL hasn't changed.
Also triggers Dolt push/pull if a remote is configured.
bd repo sync [flags]
Flags:
--json Output JSON
--verbose Show detailed sync progress