git-worktree

Manage Git worktrees through a unified interface that handles creation, listing, switching, and cleanup to ensure isolated parallel development. Per-worktree configuration and environment file copying guarantee each worktree remains valid and isolated from the main checkout.

Environment file handling for Git worktrees works by copying per-worktree configuration files into each new isolated checkout. This ensures every parallel development branch maintains its own valid environment setup, preventing cross-branch contamination during feature work.

Yes, you need both Bun and Git installed to automate worktree lifecycle management. Bun executes the automation scripts while Git provides the underlying worktree functionality required to create, list, switch, and clean up isolated parallel development branches.

Git worktree automation supports bare-repo-safe operations, allowing you to manage isolated parallel development branches within bare repositories. Registration verification validates each worktree against the bare repository to ensure safe and consistent execution.

The best way to clean up stale Git worktrees is using a unified lifecycle manager that safely removes isolated checkouts after parallel feature development. It validates worktree registration before deletion, ensuring the main repository remains consistent and free of orphaned branches.

Git worktree registration validation matters because it verifies each isolated checkout is properly linked to the main repository before you begin parallel code reviews. This prevents cross-branch contamination and ensures each worktree remains a valid, isolated environment.