website/docs/cli-reference/repo.md
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
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
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
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
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