GitHub: why the review request is not shown
Reviewers are requested with POST /repos/OWNER/REPO/pulls/NUMBER/requested_reviewers (reviewers for people, team_reviewers for teams), and GET on the same address lists both. GitHub's documentation says that once a requested reviewer submits a review, they are no longer a requested reviewer; their review is listed with the pull request's reviews instead. In search, requested reviewers are likewise no longer listed after they review (checked October 25, 2026).
is:pr is:open review-requested:@me you, and teams you are on is:pr is:open user-review-requested:@me only you, by name
Why a request is missing
- You already reviewed: an approval, a request for changes or a comment review ends your request. It comes back only when the request is made again.
- It was asked of a team: the documentation says
review-requested:USERNAMEalso finds requests to teams the person is on,user-review-requested:@meonly requests to you directly,team-review-requested:TEAMNAMEone team's requests, andteam-review-requested-user:USERNAMEonly the requests to that person's teams. A public report from 2023 asked for the direct filter because some teams were asked to review a lot. - A token that cannot see the teams: a public report from 2026 found
requested_teamsempty in the pull request for a token that could not see the organization's teams (an outside collaborator's), whileGET …/requested_reviewerslisted the team either way. - Code owners and drafts: the documentation says code owners are requested automatically when a pull request changes code they own, but not on a draft; they are notified when the draft is marked ready for review.
What to do
- Choose the search:
user-review-requested:@mefor what asks you by name,review-requested:@meto include your teams,team-review-requested:ORG/TEAMfor one team. - Read team requests from the right place:
GET /repos/OWNER/REPO/pulls/NUMBER/requested_reviewerslists the teams even when the pull request's ownrequested_teamsis empty. - Asked again after a review: the author requests your review again; until then your earlier review stands. If GitHub refuses the request, see a review request refused.
- A draft: mark it ready for review so that code owners hear of it.
In IntelliJ IDEA: Review requests is review-requested:@me in one repository
How the GitHub support built into IntelliJ IDEA shows review requests, in its source (checked October 31, 2026; IntelliJ IDEA: GHPRSearchPanelViewModel.kt, GHPRListSearchValue.kt, GHPRDataContext.kt, pullRequestInfoShort.graphql, pullRequestReviewer.graphql, GHReviewersUtils.kt):
- The Review requests filter of the pull request list searches GitHub for
is:open review-requested:@mein the one repository the list belongs to, so requests to your teams are in it too. The Review filter's Awaiting review from you adds the samereview-requested:@me. There is no choice foruser-review-requested:@me, but text typed in the search box is added to the search as it is (see why the pull request list is incomplete). - A pull request's reviewers come from GitHub's
reviewRequests(the first 100, people and teams) and its last 100 reviews. A reviewer still asked shows as waiting for review, one asked again after reviewing as re-requested, and one who reviewed and was not asked again by the state of their review (see changes requested).
GitHub pull requests in IntelliJ IDEA
Pull Request Inbox for GitHub, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, fills "Waiting for my review" with GitHub's search review-requested:@me, so your teams' requests are in it, and "I am a reviewer" with that search and reviewed-by:@me; up to 200 pull requests each, most recently updated first. A pull request's reviewers are the people asked and the people who reviewed, with the teams asked listed under them. After an automatic refresh it shows a notification for each pull request that newly waits for your review: asked of you by name, or found by the review-requested:@me search (Waiting for my review, I am a reviewer, and All open with Everywhere), so a request to one of your teams counts there. In the other lists, a request only to your team brings no notification, as the plugin does not read who is in a team. As on GitHub, any review you submit, comments alone included, ends a request to you: commenting on a pull request nobody asked you about brings no notification. The review inbox, diffs and conversations are free; approving, commenting and merging are Pro (US$1.50 a month, with a 30-day trial).
GitHub is a trademark of GitHub, Inc.; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with or endorsed by GitHub, Inc. or JetBrains.
More: GitHub merge refused (405, 409) · GitHub review refused (422) · GitHub search 422 "Validation Failed" · "Resource not accessible by personal access token" · 401 "Bad credentials" · "Resource protected by organization SAML enforcement" · "API rate limit exceeded" · GitHub diff 406 "too_large", 3,000 files · GitHub line comment 422 "must be part of the diff" · GitHub branch update refused (422) · GitHub pull request not created (422, 403) · GitHub auto-merge refused · GitHub draft, ready for review or close refused · GitHub conversation not resolved · GitHub checks not shown (check runs 403) · GitHub file contents not read · GitHub compare refused (404, 422) · GitHub comment or reply refused (403 locked, archived) · GitHub merge method not allowed (405) · GitHub branch not found (404, 301) · GitHub Enterprise Server not reached · GitHub pull request list incomplete · GitHub 404 Not Found, renamed repositories (301, 307) · GitHub line comment outdated or not on the diff · GitHub pull requests not updating, notifications late · GitHub suggested change cannot be applied · GitHub required check stuck at "Expected" · GitHub code owner review required · GitHub merge blocked by unresolved conversations · GitHub merge blocked by unsigned commits · GitHub branch that merges through a merge queue · GitHub merge waiting for an approval of the most recent push · GitHub merge waiting for code scanning results · GitHub merge waiting for code quality results · GitHub merge blocked by a code coverage threshold · GitHub merge blocked by license compliance results · GitHub branch locked or its updates restricted · GitHub branch not deleted after merging · GitHub merge waiting for a team's approval (Required reviewers) · GitHub merge blocked by secret scanning alerts · GitHub stacked pull request not merging · GitHub push blocked by push rules · GitHub merge blocked by commit metadata rules · GitHub force push blocked · GitHub issue not closed by a merged pull request · GitHub pull request not checked out locally · GitHub pull request has merge conflicts · GitHub changes requested and dismissing a review · GitHub co-author not credited for a commit · GitHub dependency review check failed · GitHub Dependabot not rebasing its pull request · GitHub fork not syncing with upstream · GitHub pull request base branch not changing · GitHub pull request not reverting · GitHub pull request template not showing · GitHub pull request labels or assignees not added · GitHub pull request not closing or reopening · GitHub push blocked by push protection · GitHub pull request comment hidden · GitHub pull request blocked until deployments succeed · GitHub team review request replaced by members · GitHub pull request file no longer marked Viewed · GitHub pull request marked merged without being merged · GitHub Copilot review does not count as an approval · GitHub checks not running on a pull request a workflow created · GitHub Update branch button not shown on a pull request · GitHub checks failing on a Dependabot pull request · GitHub checks failing on a pull request from a fork · GitHub checks skipped by [skip ci] in a commit message · GitHub checks gone after the retention period · GitHub code review limits in a public repository · GitHub pull requests turned off or limited in a repository · GitHub checks run on every pull request in a stack · GitHub pull request showing commits already squash merged · GitHub pull request not showing a file diff · GitHub push to a pull request branch from a fork refused · GitHub check cancelled on a pull request · GitHub Rebase and merge not available · GitHub merge commit message not what you expected · GitHub pull request shows every line changed · GitHub API request timed out · GitHub pull request image or document diff not shown · GitHub review request refused (422) · GitHub pull request from Copilot: checks not running, approval not counted · GitHub push refused: GH006 and GH013 on a protected branch · GitHub "At least 1 approving review is required", approvals that do not count · GitHub pull request plugins for IntelliJ IDEA, compared · 日本語