Merge Request Inbox for GitLab™
A free inbox for GitLab merge requests (MRs), on GitLab.com and GitLab Self-Managed, in IntelliJ IDEA, PyCharm, WebStorm, Rider and the other JetBrains IDEs: what is waiting for your review, and what changed since you last looked. No AI features, no telemetry.
Get it on JetBrains Marketplace · reading is free, Pro has a 30-day trial
GitLab CI pipelines, jobs and job logs in the same IDE: our GitLab pipeline plugin.
Comparing GitLab merge request plugins for IntelliJ IDEA, PyCharm or Rider? See the options side by side.
This plugin is not affiliated, endorsed, sponsored, or approved with or by GitLab Inc. GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions.
Review inbox
- MRs waiting for your review, from the projects you have open, from their group (subgroups included) or from everywhere on the instance
- Each row shows what is new to you (new, new commits, new activity), approvals and change requests, comments and when it last changed
- A notification when a new review request arrives (the list refreshes every 5 minutes while it is open)
- Multi-repository projects: every GitLab clone in the project is listed, not only the first one
Reviewing
- All changed files in one diff viewer, fetched from GitLab (nothing to fetch locally); step through them file by file
- Mark files as viewed; a later push that changes a file clears its mark (files it did not touch keep theirs), and files changed since your last visit are flagged
- Discussion threads (inline comments) appear in the diff gutter; comment on the selected lines straight from the diff
- Open threads first, resolved ones folded away; reply, resolve and reopen
- Merge checks in plain words: approvals still needed, changes requested, unresolved threads, the pipeline, conflicts, a needed rebase; and the head pipeline, with a link
Finishing
- Approve or request changes, and take either back
- Merge as the project is set up (merge commit, semi-linear or fast-forward), squash when the project allows it, your own commit message, deleting the source branch, or merge when the pipeline succeeds
- Rebase, mark as ready or as draft, close, check out the source branch (also from a fork), or create a merge request (or a draft) from your current branch
Free and paid
Free: the review inbox, diffs, viewed marks, discussions, merge checks, pipelines and checking out the source branch. Paid, with a 30-day free trial: approve, request changes, comment, reply, resolve, merge, rebase, mark as ready, close and create merge requests. Licenses are sold through JetBrains Marketplace: US$1.50 a month or US$15 a year for individuals, US$3 a month or US$30 a year per user for organizations (Marketplace shows the price in your currency).
Buying for a team: an organization license is managed in JetBrains Account, where an administrator assigns it to developers; the on-premises JetBrains License Server can serve it too. Pay by card or PayPal; for a purchase order or a bank transfer, ask for a quote with Get Quote on the plugin's Marketplace pricing page.
Install
Install it from JetBrains Marketplace, or in your IDE open Settings | Plugins | Marketplace and search for Merge Request Inbox for GitLab. Then open a project whose Git remote is on gitlab.com or on your GitLab Self-Managed server (set its address in the plugin settings) and find GitLab MRs in the right tool window bar.
Works with
- GitLab.com: HTTPS and SSH remotes, including SSH over port 443
- GitLab Self-Managed (Free tier and up, Community or Enterprise Edition): set the server's address in Settings | Tools | Merge Request Inbox for GitLab; a relative URL root works too. A server whose host name contains gitlab is recognised from the remote and read without a token
- The IDE's proxy settings (including proxy authentication) and trusted certificates, for self-signed or company certificates
- Tested against GitLab CE 18.11 and 19.5 on October 22, 2026: creating, commenting on lines, suggesting and applying changes, approving, requesting changes, rebasing, merging, and merging when the pipeline succeeds. GitLab CE has no API to withdraw a change request; the plugin says so
- IntelliJ IDEA, PyCharm, WebStorm, Rider and the other JetBrains IDEs 2024.1 or later with Git, and Android Studio Koala (2024.1.1) or later
Access token
Public projects can be read without a token: merge requests, checks and diffs. GitLab shows comments only to signed-in users. For comments, private projects and your review inbox, create a personal access token with the scope api to approve, comment and merge as well (choose it from the start if you want to try Pro), or read_api to read only (how to create one; the plugin settings have a link that opens the form with the name and scope filled in). Project and group access tokens work too. Enter it in Settings | Tools | Merge Request Inbox for GitLab: one token for GitLab.com and one for your Self-Managed server, each kept in the IDE's password safe and sent only to its own server. If GitLab answers "insufficient_scope" (The request requires higher privileges than provided by the access token), see which scope to add; if it answers 401 "invalid_token" (Token is expired, Token was revoked), see what happened to the token; if it answers 429 "Retry later" or "This endpoint has been requested too many times", see rate limits and how long to wait; if it answers 404 "Project Not Found", see address or access; if a list answers 400 ("scope does not have a valid value") or 404 "Group Not Found", see why GitLab refused the list; if changes_count says "1000+" or files seem to be missing from the changes, see GitLab's diff limits; if the files changed since your last visit are not marked after a large push, see compare_timeout and the diff limits; if a merge is refused (405, 409, 422), see why GitLab refused it; if it fails with "This project requires squashing commits when merge requests are accepted." or "Squashing failed", see the squash setting that applies; if an approval is refused (401, 409) or taking it back answers 404, see why GitLab refused the approval; if a comment, a reply, resolving a thread or applying a suggestion is refused (400 "Note …", 403), see why GitLab refused it; if creating a merge request answers 409 "Another open merge request already exists for this source branch", see why GitLab did not create it; if a rebase answers 403 "Cannot push to source branch" or fails afterwards with "Rebase failed", see why the rebase did not happen; if setting auto-merge answers 405, or it merges at once, see what GitLab does with auto-merge.
No AI features, no cloud of ours
The plugin talks only to GitLab: gitlab.com, the Self-Managed server you set and, without a token, a server your Git remote points at whose host name contains gitlab. Your code and comments are not sent to any AI service or to any server of ours, and there is no telemetry.
日本語
IDE の言語が日本語のとき、画面はすべて日本語で表示されます。お問い合わせは日本語でも受け付けます。日本語の説明