beads/docs/cli-reference/repo.md
Chris Sells de0200ff77 docs(emitter): Cobra-accurate usage lines, published global flags, MDX ESM guard
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.
2026-07-12 10:37:17 -07:00

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 [command]

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