pr-captain-merge

Merging a GitHub pull request while respecting branch protection rules requires a tool that performs true merge commits and enforces principal authorization. This ensures only conflict-free, auditable integrations occur without bypassing branch rules.

Yes, you can simulate a pull request merge on GitHub before executing it by using a dry-run flag. This allows you to verify that the merge will be conflict-free and compliant with branch protection rules without actually modifying the repository history.

The safest way to merge a PR on a protected main branch is to use a process that creates true merge commits without squash or rebase, requires explicit principal approval for bypasses, and maintains a clean, auditable history to prevent accidental history rewrites.

To bypass GitHub branch protection rules for an authorized merge, you must use a specific principal authorization flag. This enforces explicit approval, ensuring the merge is auditable and only performed by an authorized captain when strictly necessary.

No, this merge process does not use squash or rebase when integrating pull requests. It performs true merge commits to maintain a clean, auditable history and prevent accidental history rewrites in collaborative development workflows.