July 28, 2026
Clone wars hit the comments
Setup Script Should Support Git Worktrees
One app, many copies, and the internet is already arguing about who broke the vibe
TLDR: The article says every extra copy of a project should have one setup command that makes it run without clashing with the others. Commenters mostly agreed the problem is real, but the thread got spicy when one person said the author’s own comment sounded AI-written.
A seemingly nerdy idea about making one-click setup work for every Git worktree — basically, every extra copy of a project you open to work on different tasks at once — turned into a mini-comment-section soap opera. The post’s big point is simple: copying a project is easy, but keeping those copies from fighting over the same local stuff like ports, databases, and background services is where the chaos begins. The proposed fix? A single bin/setup command that gives each copy its own identity so developers can run several versions side by side without surprise collisions or mystery breakage.
But the real popcorn moment came from the comments. The author jumped in to ask which shared resource has been the hardest to separate, only for one reader to immediately deliver a brutal plot twist: the comment was supposedly flagged because it “reads as AI generated.” Ouch. That turned a practical workflow post into a very 2026 internet scene: half useful engineering chat, half vibe policing. Elsewhere, another commenter chimed in with a been-there-done-that flex about using a run/ folder and scripts everywhere, while someone else dropped the cheeky bigger-picture take that Git looks almost mysteriously ahead of its time for today’s AI-heavy coding habits.
So yes, the article is about smoother setup. But the community made it about something much juicier: when does “helpful automation” become “this sounds like a bot wrote it,” and why does every dev tool discussion eventually become a personality test?
Key Points
- •The article argues that a repository-owned setup command such as `bin/setup` should make any Git worktree ready to run or provide exact repair instructions.
- •Git worktrees separate source files but do not isolate runtime resources such as ports, databases, cache keys, callback URLs, Terraform state, and container or Compose names.
- •The proposed approach is to share compatible local services while assigning each worktree its own identity, ports, database names, cache namespace, and other local resource names.
- •The setup script should maintain a local registry for worktree identity and port allocation, use locking for concurrent setup runs, and handle stale reservations and later bind collisions.
- •`bin/setup` is described as owning toolchain bootstrap, diagnostics, Docker service readiness, configuration generation, isolated database creation and migration, dependency checks, and then exiting before normal development commands run.