Tool / A database-backed lease per repository lets one integration write to the target at a time; merges use each task's original branch point as the base, so an advanced main is not a reason to rebase; agents declare intended files, symbols and dependencies as soft reservations, checked before the merge is written.
Integration Guard
Integrates parallel agents' worktree branches into main through one lease-guarded, three-way merge per repo, with soft file and symbol reservations that warn about overlap early.
The summary describes what the project says it does; inclusion is not an endorsement.
Part of a self-hosted Vibe Kanban fork. Interesting because it refuses the reflex rebase: a moved main only matters if the declared surfaces overlap. Write-up: https://dev.to/evertonkozloski/integration-guard-safely-merging-parallel-concurrent-ai-agents-from-git-worktrees-into-main-4l7m
- Coordinate
- Integrate
AI-drafted