Skip to content

merge blockers

Why GitHub dismissed your approval after a push, and how to re-review only what changed

Othman Shareef · November 22, 2026 · 5 min read


Your approval disappeared because the branch has “Dismiss stale pull request approvals when new commits are pushed” turned on. When a push changes the pull request’s diff, GitHub dismisses every approving review given before that push, and the pull request needs a fresh approval before it can merge. Read what changed since you approved, then approve again.

What does “Dismiss stale pull request approvals” do?

It ties each approval to the diff the reviewer actually saw. Per GitHub’s docs on protected branches, you can dismiss stale approvals “when commits are pushed that affect the diff”. Without it, an approval keeps counting no matter what lands afterwards, so a reviewer can approve version one and the branch can merge version four.

Why was my GitHub approval dismissed?

GitHub’s docs list four ways the diff can move under an approval:

  • The author or anyone else pushed new commits to the pull request branch.
  • Someone clicked Update branch, which brings the base into the branch. Our guide to why GitHub says the branch is out of date explains when that button shows up.
  • A related pull request was merged into the target branch.
  • The merge base introduced new changes after the review was submitted.

The last two catch people out, since nobody touched the pull request itself. The diff is measured against the base, so a change on the base is enough.

Where is the setting in GitHub?

In a classic branch protection rule, open the repository’s Settings, then Branches, and edit the rule. Under Require a pull request before merging, select Require approvals, then Dismiss stale pull request approvals when new commits are pushed, as the branch protection rule docs describe. Rulesets have the same option under the same heading. If you cleared it in branch protection and approvals still vanish, check the repository’s rulesets and the organization’s.

There’s a side effect in the same docs: with this on, building the merge commit yourself and pushing it straight to the protected branch fails unless its contents exactly match the merge GitHub generates for the pull request.

How does it interact with “Require approval of the most recent reviewable push”?

They sit next to each other in the settings. Dismissing stale approvals checks that the approval covers the current diff. Requiring approval of the most recent reviewable push checks who approved: it has to be someone other than the person who made the latest push. Reviewers who approved earlier can approve again after that push.

With only the first one on, the person who pushed last can still approve their own push. GitHub says that if you worry about a pull request being hijacked, dismissing stale reviews is the safer of the two. On a protected main branch I’d turn on both. When the second one blocks you, the message asks for “approval from someone other than the last pusher”, which is covered in our guide to the last pusher rule.

How should a reviewer re-review after an approval is dismissed?

Read the change between your approval and now, nothing else. That slice is an interdiff, and it’s usually small:

  1. Lean on viewed files. GitHub unmarks a viewed file when it changes, so anything still checked doesn’t need reopening.
  2. Read the commits pushed since your review. If the author rebased or force-pushed, compare the old and new branch tips with git range-diff instead.
  3. If the dismissal came from Update branch or the base moving, the new lines are mostly other people’s merged work. Check that the merge didn’t change what this pull request does, then approve.

More on that in re-reviewing pull requests with an interdiff. I do this in Pyor, where viewed state syncs with GitHub and you can shift-click a range of commits to review only that span.

For the rest of the required review settings, see our guide to required reviews.

Frequently asked questions

Does clicking Update branch dismiss an approval?

Yes, when the setting is on. GitHub lists Update branch next to a new push and a related pull request merging into the target branch as changes that make the diff differ from what was approved, and the approving review is dismissed as stale.

Can the same reviewer approve again after their approval is dismissed?

Yes. A dismissed approval does not lock the reviewer out. They read the new version and approve again. If Require approval of the most recent reviewable push is also on, the new approval has to come from someone other than the person who made the latest push.

Should I use dismiss stale approvals or require approval of the most recent push?

They answer different questions. Dismissing stale approvals makes every approval cover the current diff. Requiring approval of the most recent reviewable push makes sure someone other than the last pusher approved. GitHub calls dismissing stale reviews the safer choice against a hijacked pull request. You can turn on both.

Review your next PR in Pyor.

Pyor’s merge box updates the branch, merges with any method the repo allows, turns on auto-merge, or joins the merge queue, in the same window you review in. Free for individuals, and it talks to GitHub straight from your machine.