How to find every GitLab merge request waiting for your review

Someone asked for your review, and now you can’t find it. GitLab collects every merge request that needs you on one page, your merge request homepage, and a few other routes lead to the same list. Here is where to look in 2026.

Your merge request homepage

To open it, use any of these:

• Press Shift+M.
• In the left sidebar, select Merge requests.
• From outside a project or group, in the top bar, select Search or go to, then Merge requests I’m working on.

It lists every merge request where you’re the author, an assignee or a reviewer, on three tabs: Active, which needs attention from you or your team; Merged, for the last 14 days; and Search, to filter all merge requests.

In the default Workflow view, the Active tab groups them by where they are in the review:

Section	What’s in it	Counts as active
Your merge requests	You’re the author or assignee and haven’t added reviewers (drafts too, unless you turn off Show your drafts)	Yes
Review requested	You’re a reviewer, and your review is still due	Yes
Returned to you	Reviewers commented on yours or requested changes	Yes
Waiting for author or assignee	You reviewed them and requested changes or left comments	No
Waiting for approvals	Yours, with reviewers who haven’t reviewed or approved yet	No
Approved by you	You reviewed and approved them	No
Approved by others	Yours, approved by all their reviewers, possibly ready to merge	No

Each row shows the author, the reviewers (a green check mark means that reviewer approved), and a compact set of checks: conflicts, unresolved threads such as 0 of 3, approval status and the latest pipeline.

If you’d rather see your reviews apart from your own work, select Display preferences in the upper right and switch to the Role view. Review requested lists everything awaiting your review, and Reviewed lists what you’ve already reviewed.

The homepage arrived in GitLab 17.9 behind a feature flag, on GitLab.com first, and has been on by default since GitLab 18.2. On an older self-managed instance, use the Reviewer filter below.

Filter a project’s merge requests by reviewer

1. In the project, select Code › Merge requests.
2. Select Search or filter results, then Reviewer.
3. Choose = and a username, yours included.

Add more filters and they’re combined with AND. Reviewer = None finds merge requests nobody has been asked to review. On Premium and Ultimate, Approver finds merge requests a user is eligible to approve, even if nobody requested their review.

Your To-Do List

Every review request adds an item to your To-Do List, whatever your email settings. When your review is re-requested, GitLab emails you, unless your notifications are disabled, and adds a new to-do item if your earlier one is done. Once the merge request merges or closes, the to-do items of its reviewers are marked as done. More in the GitLab To-Do List explained.

Email

GitLab can also email you when you’re added as a reviewer, depending on your notification level for the project. If you’ve cut GitLab’s email down, keep the to-do items: they arrive either way. See how to stop GitLab email notifications without missing a review.

From the command line or the API

In a project’s directory, the GitLab CLI lists its open merge requests that have you as a reviewer:

glab mr list --reviewer=@me

Add --group my-group to cover a group, or -R group/project for another project.

To cover every project at once, call the merge requests API with scope=reviews_for_me, which returns merge requests where you’re assigned as a reviewer. This endpoint returns merge requests in every state by default, so add state=opened:

curl --header "PRIVATE-TOKEN: <your_access_token>" \
  "https://gitlab.example.com/api/v4/merge_requests?scope=reviews_for_me&state=opened"

A token with the read_api scope is enough. More in GitLab token scopes explained.

Review requests on your phone

GitLab doesn’t push anything to your phone, so a review request waits on the homepage until you next open it. MergeBell’s inbox is built on your To-Do List, grouped by project, so a review request shows up there as a to-do, and a push alert tells you about it: free, checked every five minutes, or every minute on Pro. From there you can read the changes and approve or merge, with anything still blocking the merge listed before you tap. See how to review a GitLab merge request on your phone.