Multiple branches in monorepo

[mahdialibi]

If i have a monorepo with multiple branches. We work actively in these branches in parallel. Does the code-review-graph handle this?

[tirth8205]

Thanks for raising this! Currently the graph is built per-worktree — if you're using git worktree for parallel branches, each worktree gets its own .code-review-graph/ directory with an independent graph DB.

For branch switching within a single checkout, the graph is rebuilt on code-review-graph build. The incremental builder only re-parses changed files, so switching branches and rebuilding is fast.

If you're looking for branch-aware caching (keeping separate graph snapshots per branch), that's an interesting enhancement we could consider. Could you describe your workflow in more detail?

[tirth8205]

v2.0 adds multi-repo support (code-review-graph register, serve --multi). For multiple branches in a monorepo: the graph is built from the current working tree state. If you switch branches and run code-review-graph update, the graph updates incrementally to reflect the new branch state (~2 seconds). Each branch doesn't get its own graph — the graph reflects whatever is currently checked out.

[tirth8205]

Improvement pushed: builds now store the git branch name and HEAD SHA in the graph metadata. The status command warns if the graph was built on a different branch than the current one. For parallel branch work, git worktrees remain the recommended approach (each worktree gets its own .code-review-graph/).

[tirth8205]

The graph reflects the current worktree state by design. When you switch branches, run code-review-graph update for an incremental diff. For parallel branch work, use git worktrees — each worktree gets its own .code-review-graph/ database. Branch metadata is stored since v2.0.

[tirth8205]

Multi-branch monorepo: each branch maintains its own checkout, and code-review-graph build runs against the files currently checked out. For multi-branch parallel work, you'd need to either use separate worktrees with separate --repo paths, or rebuild the graph when switching branches. The multi-repo registry (code-review-graph register) can help manage multiple repos. Issue correctly closed as a design explanation.