git-worktree-manager

Git worktrees for parallel branches are managed by automating worktree creation, assigning non-conflicting ports using a deterministic base/stride scheme, and persisting assignments to isolate concurrent local development environments safely.

Dev servers break across git worktrees when multiple branches attempt to bind the same port or share environment files. Automating port allocation and syncing .env files isolates each worktree so concurrent branches run independently.

To automatically copy .env files when creating a git worktree, use tooling that detects local environment files in the main repository and replicates them into the new worktree directory during the setup process.

Yes, stale and merged branches can be detected before cleaning up git worktrees by running a script that checks for uncommitted changes and identifies merged branches, ensuring outdated worktrees are safely removed without data loss.

Git worktree automation works for multiple agents that must not share a branch by creating isolated worktrees with deterministic naming and separate environments, allowing agents to operate concurrently on independent branches without interference.

The best way to remove outdated git worktrees after a merge is to automate cleanup by identifying merged branches, detecting stale worktrees, and safely deleting the isolated directories instead of relying on ad-hoc rm -rf commands.