git-worktree-workflow

Managing git worktrees across forks involves coordinating base clones and related worktrees to handle syncing, PR preparation, and cleanup. This workflow enforces safe preconditions and consistent merge or rebase strategies to reconcile related sibling clones.

Setting up a git worktree workflow for issues means creating isolated working directories linked to your main repository. You can start by instructing your assistant to work on a specific issue number to automatically create and manage the corresponding worktree.

Git worktrees can prepare pull requests and facilitate cross-branch merges by providing separate directories for each task. The workflow enforces explicit user confirmations and safe preconditions before applying any merge or rebase strategies.

Coordinating git worktrees across teams automates branch syncing by deriving default branches and resolving worktree paths. It manages base clones and related repos to ensure consistent state without manual reconciliation for every update.

Cleaning up git worktrees after merging involves pruning obsolete directories and syncing the base clone. The workflow manages this cleanup phase by enforcing safe preconditions and explicit confirmations before removing any worktree.

You should avoid using a git worktree workflow if your version control process cannot accommodate explicit user confirmations or strict preconditions. Complex reconciliations across sibling clones require consistent merge strategies that may not suit rapid, unattended automated pipelines.