If GitHub says “Merging is blocked: New changes require approval from someone other than the last pusher”, the branch has “Require approval of the most recent reviewable push” turned on. Someone with write access who did not make the latest push has to approve the pull request after that push. An approval from before the push no longer counts, and neither does an approval from the person who pushed last. If the message instead says it is “waiting on 1 more approval from a reviewer with write access because the last pusher could not be determined”, the fix is the same: one more approval, given after the latest push.
What does “approval from someone other than the last pusher” mean?
Per GitHub’s docs on protected branches, you can require that the most recent reviewable push be approved by someone other than the person who pushed it. Without it, a reviewer can push a last commit to a shared branch, approve the pull request, and that commit merges without anyone else reading it. With it on, the latest push always needs a second person.
So the block shows up right after a push, even when the earlier approver was someone else. Their approval covered the code before the push, and it doesn’t carry over.
How do I unblock a PR blocked by the last pusher rule?
- Check who made the latest push. That person’s approval cannot count, even if they are a reviewer and not the author.
- Ask someone else with write or admin access to approve. Approvals from people without write access do not count toward required reviews.
- If a reviewer approved before the push, they can approve again. GitHub’s docs say reviewers who already approved can reapprove after the most recent push to meet the requirement.
- If a review requesting changes is also blocking, that reviewer has to approve, or someone with write access can dismiss the review when its author is away.
Push nothing else between the approval and the merge. Every new push starts the wait again. If you rely on GitHub auto-merge, it holds until that fresh approval lands.
What does “the last pusher could not be determined” mean?
The same rule needs to know who made the latest push, so it can discount that person’s approval. When GitHub cannot tie the push to an account, it cannot tell whose approval to discount. The message says what it does instead: it waits for one more approval from a reviewer with write access. Give that approval after the latest push and the pull request can merge.
Where is “Require approval of the most recent reviewable push”?
In a classic branch protection rule, go to the repository’s Settings, then Branches, and edit the rule. The option sits under Require a pull request before merging, next to Require approvals, Dismiss stale pull request approvals when new commits are pushed, and Require review from Code Owners, as the branch protection docs list them. Rulesets have the same option under the same heading. If the setting is off in branch protection and the banner still shows, check the repository’s rulesets and the organization’s.
Should you keep the last pusher rule or dismiss stale approvals?
They do different jobs. Dismiss stale pull request approvals when new commits are pushed removes an approval once a push changes the diff, and GitHub’s docs say it is safer to dismiss stale reviews. The last pusher rule only decides who is allowed to approve. I’d turn both on for a protected main branch. The extra approval costs little on a small pull request, and less when the reviewer reads only what changed since their last review.
For the other required review settings and the “at least 1 approving review is required” message, see our guide to required reviews. In Pyor, a file you marked viewed stays viewed until its content changes, so re-approving after a one-line fix means opening the files that push touched and nothing else.
Frequently asked questions
Why does an approval from before the latest push stop counting?
With "Require approval of the most recent reviewable push" on, the approval has to cover the latest push. GitHub says reviewers who already approved can reapprove after that push to meet the requirement. So the earlier reviewer is not blocked, they just have to approve again.
Can the person who pushed last approve the pull request?
No. The setting requires approval from someone other than the person who made the most recent reviewable push. That includes a reviewer who pushed a small fix to the branch: after that push, their own approval does not count, and someone else with write access has to approve.
Where do I turn off Require approval of the most recent reviewable push?
In a classic branch protection rule it sits under Require a pull request before merging, in Settings, then Branches. Rulesets have the same option under the same heading. Turning it off lets whoever pushed last approve their own change. Dismiss stale pull request approvals when new commits are pushed, in the same section, is the other half and worth keeping on either way.