On a GitHub pull request, a reviewer is someone asked to read the change and leave a review. An assignee is someone who owns the pull request and is responsible for moving it along. A review request notifies the reviewer and puts the pull request in their review-requested:@me search until they review. An assignment subscribes the person to the thread and shows up in assignee:@me. It asks nobody to review, and required approvals never look at it.
What each field means
Reviewers sit under Reviewers in the right sidebar of a pull request. Requesting a review sends a notification, and after new commits the author can click Re-request review next to a reviewer’s name. A review is what counts toward merging: per GitHub’s protected branch docs, required approvals come from reviewers with write permissions or from a designated code owner.
Assignees sit under Assignees in the same sidebar. The field works the same way on issues and pull requests and records whose job the pull request is, with no effect on reviews.
Who can fill each one
To request a review you need write access, and you can request it from any person or team with read access. Assignees are people only. Per GitHub’s assignment docs, you can assign yourself, anyone who has commented on the pull request, anyone with write permissions, and organization members with read permissions, up to 10 per pull request.
How each one gets notified
Both get notified, with a different reason attached. In the notifications API, review_requested means you or a team you belong to were asked to review, and assign means you were assigned. Being assigned also subscribes you to the conversation, so later comments reach you too.
The notifications inbox has a filter for each. reason:review-requested shows review requests for you or your teams, and reason:assign shows updates on pull requests and issues you are assigned to, as listed in GitHub’s inbox filters reference. Requesting a review from a large team can notify every member. Teams avoid that with auto assignment, or with Only notify requested team members plus a request to one member.
Splitting the two on a team
GitHub leaves the convention to you. I make whoever will merge, usually the author, the assignee, and the people who need to read the change reviewers. The assignee chases the review, answers comments and merges. Reviewers owe a review and nothing more. Assigning a reviewer as well blurs that, because they then show up in both searches below.
You can automate most of the reviewer side. Code owners are requested for review automatically when a pull request touches files they own (not on drafts). A team’s code review settings can replace the team with a few members, picked by round robin or load balance. Despite its name, auto assignment fills the Reviewers field and leaves Assignees alone. For choosing who those reviewers should be, see how to assign code reviewers without a bottleneck and our CODEOWNERS guide.
review-requested:@me vs assignee:@me
Both work in GitHub search, because any qualifier that takes a username accepts @me.
is:open is:pr review-requested:@meis your review queue. It includes requests sent to your teams, and a pull request leaves it once you review.is:open is:pr user-review-requested:@menarrows that to requests made to you by name.is:open is:pr assignee:@meis the work you own. Reviewing leaves the assignment in place, so a pull request stays here until it closes or someone reassigns it.is:open is:pr no:assigneefinds pull requests nobody has claimed.
I keep the first and third bookmarked, one for what I owe a review and one for what I need to land. The review requested filter guide covers the rest of that qualifier family, and stop losing review requests covers why a search alone still lets some slip. Pyor’s pull request lists filter by Reviewer and Assignee as GitHub searches, so the counts match what GitHub returns.
Frequently asked questions
Does assigning someone to a pull request ask them to review it?
No. Assigning puts the person in the Assignees field and subscribes them to the pull request, but it does not create a review request. To ask for a review, add them under Reviewers. Required approvals in branch protection count reviews from people with write access, and the docs never mention assignees there.
Why did a pull request drop out of my review-requested:@me search?
GitHub removes requested reviewers from review-requested results once they review the pull request. If the author wants another look after new commits, they can click Re-request review next to your name in the Reviewers sidebar, and the pull request shows up in your search again.
Can a team be an assignee on GitHub?
The docs only list people as assignees: yourself, anyone who commented, anyone with write access, and organization members with read access, up to 10 per pull request. Teams can be requested as reviewers, and team review settings can swap the team for a few of its members.