cannot request a review from yourself: GitHub error workaround
Works around GitHub's block on requesting a review from the PR author. Use when a review request fails with the pull-request-author error, so you can route the request to a teammate, a team, or CODEOWNERS instead. Key trigger: the self-review request error on your own PR.
TL;DR
GitHub forbids requesting a review from the pull request author, including yourself. You cannot work around the block itself; instead request the review from someone else: a teammate, a team with write access, or let CODEOWNERS assign reviewers automatically.
Review cannot be requested from pull request author.- Request a teammate instead: use Reviewers in the PR sidebar, or
gh pr edit 123 --add-reviewer teammate-login. Expected: the teammate appears under Reviewers. - Or request a whole team:
gh pr edit 123 --add-reviewer org/team-slug. Expected: the team is listed as a requested reviewer. The team needs write access to the repo or the request is silently dropped. - Or assign the PR to a shepherd:
gh pr edit 123 --add-assignee teammate-login. Expected: the assignee shows in the sidebar and gets notified. - For the long term, add a CODEOWNERS file so the right reviewers are requested automatically on every PR.
Use this when
- You tried to request a review from yourself and got the error
- A bot or agent tried to self-request a review on an agent-authored PR
- You need review coverage on your own PR
Not for this skill when
- You want to approve your own PR (also blocked; get a teammate's approval)
- Branch protection requires reviews you cannot satisfy alone; same answer, find a reviewer
- You are trying to review someone else's PR (no block applies)
Variant phrasings
- "github review cannot be requested from pull request author"
- "how to request review on my own pull request"
- "self review request blocked github workaround"
Why it happens
Review requests exist to get independent eyes on a change. Letting the author request a review from themselves would satisfy branch protection's review requirement without any real review, so GitHub blocks it at the API level.
Edge cases
- Team review requests fail silently when the team lacks write access; check the team's repo permission first.
- CODEOWNERS requests can also fail silently if the listed owners lack access; keep the file in sync with the team roster.
- Draft PRs accept review requests but many reviewers ignore them; mark ready for review when you actually want eyes.
Provenance
Resolved from the public thread: https://vectle.com/posts/pstVzuaf6N-LcCFfJXUKTbVQ