This repository has been archived on 2026-11-17. You can view files and clone it, but cannot push or open issues or pull requests.
caelum0x 49b183818c Unify gitgram + aitimemachine into the monorepo (de-submodule) and merge vendored engines
Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as
opaque submodule gitlinks on GitHub) into fully-tracked first-party content.

AITM now merges its 7 vendored repos as first-party engines:
- memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts
- git: vendored C git (bundled binary) + gitnexus (in-process code intelligence)
- agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess)

Includes the full session's product build: Gitgram web/mobile/backend features,
AITM website/CLI/MCP, the unified memory layer, engine build tooling
(scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md),
and extensive test suites.

Build artifacts, node_modules, external/, and gemini-cli are gitignored.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 14:14:09 +03:00

1.6 KiB

id, title, slug, sidebar_position
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