Installation

• From the IDE (recommended, you get notified of updates): Settings > Plugins > Marketplace, search for "Gerrit" and Install.
• Manually: download the release matching your IDE and install it with Settings > Plugins > ⚙ > Install Plugin from Disk....

Then restart the IDE.

Getting started

1. Open Settings > Version Control > Gerrit and add an account with the web URL of your Gerrit, your login and your HTTP password (in the Gerrit web UI under Settings > HTTP Credentials, or HTTP Password in older versions). Test checks the connection.
2. Open the Gerrit tool window. It lists the changes of the Gerrit projects whose Git repositories are part of your IDE project.
3. Push as usual: the push dialog has a "Push to Gerrit" section for the Gerrit options. "Push commits to Gerrit by default" in the settings ticks it in new push dialogs; after that, each project keeps your last choice.

With accounts on several Gerrit instances, add all of them and pick the one a project talks to with Use for This Project. A project whose remotes point at only one of them picks it by itself.

To clone a project from Gerrit, use Get from VCS and pick Gerrit as version control.

Troubleshooting

List of changes is empty

By default, the list only shows changes of the Git repositories in your IDE project.

• Check that the repositories are registered under Settings > Version Control.
• Check that at least one remote of each repository points at the host of your Gerrit account.
• If Gerrit is cloned from another host than its web UI, set the "Clone base URL" of the account.
• Or add a remote named like the Gerrit project, with the Gerrit web URL as its URL.

Error-message on checkout or cherry-pick: "No repository found for Gerrit project"

With "List all Gerrit changes (instead of changes from the currently open project only)", the list also shows changes of projects that are not part of your IDE project. You can vote on and submit these, and review them: the files of such a change, their diff and its comments come from Gerrit. Checking a change out, cherry-picking it and fetching it need the local clone of its project; clone the project and add it to your IDE project for these.

Error-message when clicking a change: "Cannot fetch changes"

Gerrit 2.9 and 2.10 tell the plugin where to fetch a change from only with the download-commands plugin installed; newer versions do without it. The Gerrit update procedure offers to install it, but it isn't selected by default, so run the update again if you skipped it. For an existing or new instance, this installs it:

java -jar gerrit.war init -d {gerrit-instance} --install-plugin=download-commands

Error-message when loading changes: "Bad Request. Status-Code: 400. Content: too many terms in query."

Enable "List all Gerrit changes (instead of changes from the currently open project only)" in the plugin settings.

Error-message when loading changes: "SSLException: Received fatal alert: bad_record_mac"

Your Gerrit (or the reverse proxy in front of it) only accepts SSLv3. Enable TLS there; SSLv3 is insecure anyway.

Checking out from VCS with Gerrit plugin does not work

Cloning from the plugin does not work with every authentication method. If it fails to authenticate or does not finish:

• use the SSH clone URL in the clone dialog (the Gerrit web UI shows it in the project settings), or
• clone with the Git plugin and add the Gerrit account afterwards.

Background is in this Gerrit mailing list topic.

Loading file-diff-list is slow

The file list and diffs come from Git: the plugin fetches the change from Gerrit. Running git gc locally and gerrit gc on the server (ask your Gerrit administrator) usually helps.

Authenticate against *-review.googlesource.com

In the Gerrit web UI, open Settings > HTTP Credentials > Obtain password. In the text shown, find the line starting with your host (e.g. gerrit-review.googlesource.com) and take login and password from it:

gerrit-review.googlesource.com,FALSE,/,TRUE,12345678,o,git-username.gmail.com=password-until-end-of-line

Here the login is git-username.gmail.com and the password is everything after the =.

How it works

• IDE integration: a tool window lists the changes, see com.urswolfer.intellij.plugin.gerrit.ui. The push dialog has no extension point, so the plugin adds its options to Git's push dialog at startup, see com.urswolfer.intellij.plugin.gerrit.push.
• REST API: most of the communication with Gerrit uses the Gerrit REST API, through the standalone gerrit-rest-java-client, see com.urswolfer.intellij.plugin.gerrit.rest.
• Git: listing the files of a change, diffs, checkout and cherry-pick run on the local clone with the IDE's Git plugin, see com.urswolfer.intellij.plugin.gerrit.git.

Development

Open the project in IntelliJ IDEA with the Gradle, Plugin DevKit and UI Designer plugins enabled. CONTRIBUTING.md explains how to build, test and run it in a sandbox IDE. Pull requests go to the default branch intellij2020.3, which targets the oldest supported IDE, so a change reaches every newer one.

Support the project

If you like this plugin, you can support it:

• Spread it: tell your friends who use IntelliJ and Gerrit about it.
• Rate it on the JetBrains Marketplace.
• Star it on GitHub.
• Improve it: report bugs and request features, or fix and build them yourself, everything is open source.
• Donate, see below.

Donations

You can support this work with this donation link. If you would rather not use PayPal (it takes 2.9% plus $0.30 of each donation), please contact me. Only trust the link on github.com/uwolfer/gerrit-intellij-plugin.

Credits

• Parts of this plugin are based on the code of the IntelliJ GitHub plugin.

Thanks to JetBrains for providing a free license for developing this project.

Copyright and license

Copyright 2013 - 2026 Urs Wolfer

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this work except in compliance with the License. You may obtain a copy of the License in the LICENSE file, or at:

https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.