Re:Parallel development without the headaches using Git work...
by tlarkworthy on Monday August 24, 2026 @01:04AM
(#49415352)
I use a top level meta-repository to create a virtual monorepo of all my repositories and vendor their upstreams, then use worktrees off off the submodules to prepare patches. I never need to change directory from the root meta-repository even with multiple agents. Gives you a full monorepo experience without actually having to own any of the parts, every agent has its own isolated worktree so does not conflict.
[ Parent
| on HN ]
Re:Parallel development without the headaches using Git work...
by Klaster_1 on Monday August 24, 2026 @02:14AM
(#49415782)
Doesn't that mean that if you need to work on several repos for a feature at the same time, you'd have to WT each submodule compared to a single WT for a monorepo? Do you use a custom orchestration layer to fire all commands or lets agents manage the WTs?
Re:Parallel development without the headaches using Git work...
by tlarkworthy on Tuesday August 25, 2026 @04:00AM
(#49430457)
Yeah, but actually the agent recreates the folder structure, so work trees/task1 subfolder contains a sparse subset of work trees for task1 if it crosses repos. Yeah I have a skill for creating the isolated worktrees. The agents manage all this complexity and the complexity is isolated to the meta repository, it does not spill into the real code repos