git-worktree-merge

To merge a git worktree branch back to main, review diffs, detect overlaps with other open PRs, validate with a dry-run merge, and perform post-merge worktree cleanup. This ensures safe integration via GitHub PR or local merge.

Git worktree overlap detection identifies conflicting changes between your current worktree branch and other open PRs before merging. You need it to prevent merge conflicts and ensure your feature work integrates safely into main without overwriting parallel changes.

Yes, you can perform dry-run merge validation before merging a worktree to main. This checks for potential conflicts and verifies health gates pass, ensuring the merge will succeed before you commit to the actual integration via PR or local merge.

The best way to review diffs between a worktree and main is to generate a diff summary that highlights all changes. This allows you to verify the feature work before proceeding with overlap detection, PR creation, and the final merge into main.

Yes, you need to clean up the worktree after merging to main. Post-merge cleanup involves removing the worktree directory and associated branch references, keeping your repository organized after the feature work has been successfully integrated.

Yes, this worktree merge workflow supports both GitHub PR guidance and local merge options. It guides you through creating or updating a PR if needed, or performing a direct local merge, with overlap checks and automated guidance for either path.