GitHub won’t let you approve a pull request you opened. Its docs say it flatly: “Pull request authors cannot approve their own pull requests.” That holds for admins and repository owners too. If you work alone and the branch wants an approval, either drop the required approvals to zero, merge past the rule as an admin, or put yourself (or an app) on a bypass list.
Why can’t I approve my own pull request on GitHub?
A required review exists to put a second person between the code and the branch. If the author could approve, a rule asking for one approval would ask for nothing. GitHub states the rule on its page about approving with required reviews. The same note covers Copilot: you can’t approve a pull request Copilot raised if you assigned Copilot to its issue. Approvals that count come from people with write or admin permission, and Copilot’s own reviews don’t count at all.
How do solo developers merge with required approvals on?
If you’re the only person with write access, a required approval can never be met. I keep the pull request and drop the approval count to zero.
- Classic branch protection. In Settings, then Branches, edit the rule and keep Require a pull request before merging selected, with Require approvals unchecked. Every change still goes through a pull request, and nothing waits on a reviewer you don’t have.
- Rulesets. Set the required approvals to 0. The rulesets docs say that in this case the pull request “doesn’t necessarily have to be approved, but it must be opened.”
- Admin merge. By default, classic branch protection rules don’t apply to people with admin permissions, per GitHub’s protected branches docs. The owner of a personal repository can merge past a missing approval unless Do not allow bypassing the above settings is turned on.
You still have to read the code anyways, ideally the next morning once you’ve forgotten what you meant. Our guide to solo developer code review covers the routine, and author self-review covers the read itself.
How do bypass lists work for teams and bots?
On a team, the usual case is one trusted person or one automation that has to merge without the normal approval. There are two places to set that up.
- In a classic branch protection rule, Allow specified actors to bypass required pull requests lets chosen actors push to the branch without a pull request. Bypass lists there only work when the repository belongs to an organization.
- In a ruleset, the Bypass list section takes repository admins, organization owners, the maintain or write role, teams, GitHub Apps and Dependabot, as the ruleset setup docs list them. Click Add bypass, pick the actor, and switch Always allow to For pull requests only if they should still open a pull request and merge it past the rules.
For a bot, put the GitHub App on the bypass list rather than having the bot approve its own pull requests. GitHub Actions can approve pull requests if you turn on Allow GitHub Actions to create and approve pull requests, but a workflow approving the pull request it opened is the same self-approval with extra steps.
Can I use a second account to approve my own PR?
Not within the rules. The GitHub Terms of Service allow one free account per person, plus at most one free machine account “used exclusively for performing automated tasks.” Logging into it by hand to approve your own work isn’t an automated task, and the approval records a review that never happened.
How is this different from the last pusher rule?
The author rule is always on and looks at who opened the pull request. Require approval of the most recent reviewable push is opt-in and looks at who pushed last. A reviewer who pushes a small fix to someone else’s branch can approve it under the author rule, but their approval stops counting under the last pusher rule. We covered that message, “New changes require approval from someone other than the last pusher”, in its own post, and the other required review settings in our guide to required reviews.
I review my own branches before they become pull requests at all. Pyor’s desktop app (I build it) runs a local review of a branch against its base, which is where a solo self-review fits best.
Frequently asked questions
Can an admin approve their own pull request on GitHub?
No. GitHub's docs say pull request authors cannot approve their own pull requests, and admin permission does not change that. What an admin can do is merge without the approval: by default, classic branch protection rules don't apply to people with admin permissions, unless the rule has Do not allow bypassing the above settings turned on.
Can I require a pull request but zero approvals?
Yes. In a classic branch protection rule, select Require a pull request before merging and leave Require approvals unchecked. In a ruleset, set the required approvals to 0. GitHub's rulesets docs say the pull request doesn't have to be approved in that case, but it must be opened.
Is a second GitHub account to approve my own PRs allowed?
GitHub's Terms of Service allow one free personal account per person, plus at most one free machine account that is used only for automated tasks. A second account you sign into by hand to click Approve is not an automated task, so it doesn't fit that allowance.