worktree-pr-merge

To merge multiple PRs sequentially using Git worktrees, update the main worktree first, then merge subsequent PRs one by one and rebase each worktree after the preceding PR lands to maintain consistent state and avoid build failures.

Your PR merge may appear to fail because the local branch-delete step returns a non-zero exit code, but the actual GitHub merge succeeded. When merging PRs across worktrees, you should not treat this specific local deletion exit code as a failure.

To fix NETSDK1004 errors on a cold Git worktree, run `dotnet restore` before executing `dotnet test --no-restore` to ensure dependencies are downloaded for branches that have never been built locally.

To force-push a branch in a Git worktree that has no upstream set, use the explicit remote reference command: `git push --force-with-lease origin <branch>` to ensure correct branch push behavior and avoid merge errors.

You should rebase worktrees after each preceding PR merges to main. This sequential merge discipline ensures subsequent worktrees remain consistent with main and prevents file conflicts when multiple PRs touch the same files.

The best way to coordinate parallel PR development is to use sequential merge discipline across worktrees, ensuring deterministic execution, correct handling of merge exit codes, and explicit upstream pushes to avoid false build failures and merge errors.