GoKawiilYour Setup Script Should Support Git Worktrees A worktree-aware setup script can diagnose missing tools, share one Docker stack, and isolate ports, databases, and state for safe parallel development. Ally Piechowski · Jul 28, 2026 · 5 min read development
git
engineering-management
On one production app I work on, a fresh Git worktree becomes runnable with one setup script:
bin/setup
Setup prepares the environment and exits, then the normal development command runs. I’ll use bin/dev here as shorthand for whatever command the repository already uses. Setup doesn’t hide the server inside a clever process manager.
bin/setup is a repo-owned executable that turns a checkout into a working development environment. Call it make setup or script/bootstrap if that fits your project. The interface matters more than the name: one command returns either a ready repository or exact repair instructions.
The same command should work from every Git worktree. Parallel coding agents made this important enough to treat as ordinary development infrastructure.
A Second Checkout Is Not a Second Environment
A Git worktree is another checkout with its own working tree, HEAD , and index while sharing the repository’s common Git data. That separation is great for code. Git does not know that both copies of the app want the same port, database, cache keys, callback URL, Terraform state, or container name.
... continue reading