Skip to content

merge blockers

Why GitHub says requested changes must be addressed to merge, and how to clear it

Othman Shareef · November 22, 2026 · 5 min read


If GitHub shows “Changes requested” with “requested changes must be addressed to merge this pull request”, a reviewer submitted a Request changes review and the branch requires reviews. Either that reviewer submits a new review that approves, or someone with write access dismisses their review. Pushing fixes alone doesn’t clear it.

Why does GitHub say requested changes must be addressed?

On its own, a Request changes review blocks nothing. GitHub’s docs on required reviews call it purely informational unless a ruleset or classic branch protection rule requires pull request reviews. Once a rule requires them, a review that requests changes holds the merge: the pull request cannot merge until the same collaborator submits another review that approves.

The block belongs to that one reviewer. Resolved threads, green checks and other people’s approvals don’t touch it.

How do I get the reviewer to clear changes requested?

  1. Push the fixes the review asked for, and reply on each thread so the reviewer sees what changed.
  2. Open the Reviewers section in the sidebar and click the sync icon next to their name. That re-requests their review. You need write access to the repository to request reviews.
  3. The reviewer submits a review with Approve, and the block lifts.

The second review goes faster when the reviewer reads only what changed since their last pass instead of the whole diff again.

How do I dismiss a review that requested changes?

When the reviewer is on leave, has left the team, or the pull request has moved on, GitHub lets you dismiss the review:

  1. On the Conversation tab, open the reviews summary.
  2. Next to the review, open the options menu and click Dismiss review.
  3. Type the reason and click Dismiss review again.

The comment is required and shows in the pull request conversation. The review turns into a review comment, so it no longer blocks, and everyone on the pull request can read the reason. I’d save it for a reviewer who is really away. A ping usually takes less time than explaining the dismissal later.

Who can dismiss a pull request review?

By default, repository administrators and anyone with write access can. In an organization repository, a branch protection rule can turn on Restrict who can dismiss pull request reviews, and then only the people, teams, or apps you pick may dismiss. Rulesets offer the same restriction. If you have write access and the Dismiss review option is missing, that restriction is the likely cause.

Can an admin merge with changes requested?

Often, yes. GitHub’s docs say repository owners and administrators can merge a pull request when a reviewer who requested changes has left the organization or is unavailable. That depends on the rule. By default, branch protection restrictions do not apply to admins, and Do not allow bypassing the above settings applies them to admins too. Rulesets work through a bypass list instead, and rules from several rulesets and branch protection stack, with the most restrictive version winning. If the banner survives a change to one rule, check the others, as in repository rule violations.

Why does changes requested persist after I fixed everything?

  • The reviewer has not reviewed again. A comment saying “looks good” is not an approval. It has to be a review submitted with Approve.
  • A different person approved. Other approvals count toward Require approvals, but they do not lift the block one reviewer placed.
  • Another rule also blocks. Required approvals, code owner review, or the last pusher rule can each hold the merge after the changes requested review is gone.

For the full set of review settings, see our guide to required reviews, and for when a reviewer should block at all, see when to request changes. In Pyor, the reviewer can approve from the review dock or the command palette without opening github.com.

Frequently asked questions

Does pushing new commits clear a changes requested review?

No. Pushing fixes does not change the review. On a branch that requires reviews, the pull request stays blocked until the same reviewer submits an approving review, or someone with permission dismisses their review. Re-request their review from the Reviewers sidebar so they know the fixes are in.

Who can dismiss a review that requested changes?

GitHub says repository administrators and people with write access can dismiss a review. In an organization repository, the branch rule or ruleset can narrow that to chosen people, teams, or apps. Dismissing needs a comment, and the review becomes a plain review comment.

Does Request changes block merging on every repository?

No. GitHub calls a Request changes review purely informational unless a ruleset or classic branch protection rule requires pull request reviews. Without one, the pull request can merge while the review still asks for changes.

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.