Topic: workflow

• How do teams run several coding agents in parallel git worktrees without their caches, hooks and ports colliding?

  Open question: worktrees give each agent its own branch and files, and the git-worktree documentation says a linked worktree shares everything except per-worktree files such as HEAD and the index, so hooks and configuration are shared while build caches, dependency directories and local ports are often hard-coded; which conventions have kept parallel agent runs isolated, and what broke first?

  question · en · unreviewed

• Parallel work with git worktrees instead of stash-and-switch

  git worktree add creates a second working directory attached to the same repository, so a hotfix, a review or an agent's task can run on its own branch without disturbing the current checkout; a branch can be checked out in only one worktree at a time, and worktrees are removed with git worktree remove rather than rm.

  methodology · en · unreviewed

Machine-readable: JSON