pr-merge

To safely merge a reviewed pull request and clean up the branch, you can use a workflow that checks review status, handles merge method selection, polls merge state, and deletes local and remote branches with guardrails. This prevents accidental merges and ensures safe cleanup.

Yes, you can automate branch and worktree cleanup after a GitHub pull request merge by using a process that detects worktree setups and removes local and remote branch state appropriately. This ensures safe cleanup with fallbacks if conflicts or protections require human intervention.

Merge strategy selection for squash and rebase operations works by choosing the behavior based on branch type, repository settings, and explicit flags. The process checks merge readiness and handles auto-merge when available, stopping when conflicts or protections require human intervention.

Yes, this pull request merge workflow supports standard repositories and worktree-based setups, including integration branches, phase branches, and direct merges after review. It applies guardrails and fallbacks to ensure safe operations across these different branch configurations.

If a pull request has merge conflicts or branch protection rules, the merge process stops and requires human intervention. It checks merge readiness, handles auto-merge enablement when available, and uses failure-safe operations to avoid unsafe merges.

You need to check review status before merging a pull request to prevent accidental merges of unreviewed code. Review-aware merging ensures the workflow only proceeds after a pull request has been reviewed, removing final friction while maintaining safety guardrails.