Show negated passing atoms as blocking submit requirements A submit requirement that is unsatisfied because of a veto vote (-label:Code-Review=MIN) is shown with a red "cancel" icon, while one that is merely missing votes is shown with the neutral "block" icon. Other requirements can be blocked in the same way, by something that is present but must be absent. For example, a requirement like "-subject:WIP" or "-prefixsubject:Edit" cannot be satisfied by adding votes; the author must change the commit. These were shown with the neutral icon, as if waiting for reviewers. Treat an unsatisfied requirement as blocking when one of its passing atoms is negated in the submittability expression, either with a unary minus or with NOT. The veto vote case is a special case of this rule, and the existing check for it is kept. Note that this also applies to the default No-Unresolved-Comments requirement (-has:unresolved), which is now shown as blocking while there are unresolved comments. These also require action from the author or the commenter rather than from additional voters. Release-Notes: Unsatisfied submit requirements with a negated passing atom are shown as blocking Change-Id: Ie5b938b3d376d736a010e58baf5c25ab09d56c85
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on GitHub.
Please report bugs on the issue tracker.
Due to spam abuse, membership in the repo-discuss Google Group is required in order to create issues. See the announcement for more info.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Due to spam abuse, membership in the repo-discuss Google Group is required in order to create Gerrit changes on the gerrit-review Gerrit server.
Note that we do not accept Pull Requests via the GitHub mirror.
Find a full list of contact options on the website.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update && apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 8 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8
To run a Ubuntu 20.04 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.