gh:pr-merge-emergency

To merge a GitHub PR by bypassing branch protection, the admin override validates the PR is open, not a draft, and has passing CI checks. It then posts an audit comment, performs a squash merge, deletes the branch, and creates an incident issue for accountability.

No, you cannot emergency-merge a draft PR or one with merge conflicts. The override requires the PR to be fully open, not a draft, and free of conflicts before executing the admin merge to ensure production stability.

Forcing a GitHub PR merge without approval creates an audit trail by posting an audit comment on the PR and generating a follow-up incident issue. It also syncs project status to maintain accountability for the emergency action.

Yes, an emergency GitHub PR merge still requires CI checks to pass. The admin override bypasses the approval requirement but explicitly validates that required CI checks are green before proceeding with the merge.

Use an emergency admin merge for a GitHub hotfix when an urgent incident requires immediate action and a reviewer is unavailable. It enforces a substantive reason requirement to ensure the override is justified for critical situations like security patches.

After an emergency merge on GitHub, the branch is automatically deleted. The process uses a squash merge strategy and removes the source branch while creating post-merge audit artifacts like an incident issue.