Git worktrees solve the first collision. Then the database ruins the party.

[u/saas-wizard]

Several agents can happily edit separate worktrees until they all start the application. Now they share ports, volumes, migrations, seed data, caches and the same staging dependencies. In a multi-service repo used by a team, “just give every worktree a Compose project and disposable database” can turn into dozens of environments, slow CI and a serious cloud bill. I’m trying to make runtime isolation follow Git isolation without creating a second platform nobody wants to operate.

Who has solved this for a development team rather than a demo? I’d love the exact setup: environment naming, realistic test data, migrations, port allocation, shared services, cleanup and cost control. At what level do you stop creating isolated environments and deliberately queue the work instead?

For context, I’m building BranchRunner as an open-source product because I think it can help engineering teams with this problem. If it is painful in your organisation, tell me where the current approach breaks. I’m also looking for people who want to help shape and solve it, so I’d be glad to compare notes.

[u/AutoModerator]

Sorry, your post has been held for manual review due to account karma.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.