| commit | ea3e3b704a0f1f1aa110902a3011f343591d1140 | [log] [tgz] |
|---|---|---|
| author | Logan Hanks <logan@google.com> | Mon Jun 12 14:21:47 2017 -0700 |
| committer | Logan Hanks <logan@google.com> | Wed Jun 14 14:17:25 2017 -0700 |
| tree | bb43da21122972501269cb86346e1d0149f28243 | |
| parent | fc05596270ff189a45e9d8a34a1f6c8ff1133171 [diff] |
Downgrade default notify for WIP reviews Sometimes reviews are posted to a change while it's in the WIP state. The owner may be preparing guidance for their upcoming reviewers, or a CI bot may be reporting about tests. In general, for the purpose of filtering messages, we distinguish between bot and human actions on the basis of whether a tag is provided. A non-null tag is assumed to indicate automation. For reviews posted by humans, the default notify level depends on whether hasReviewStarted is true for the change. If a new WIP change is created and pending reviewers are added, those reviewers should never receive an email about the change until the owner starts review. Therefore, when WIP is true, hasReviewStarted is false, and tag is null, the default notify level is downgraded from ALL to OWNER. If the change has started review, the default notify level continues to be ALL (only if tag is null). For reviews posted by bots, the default notify level is downgraded for all WIP changes, even after they've entered review. For example, a CI bot may post failing test results for a series of intermediate patch sets. This is just noise to reviewers, but useful to the owner, so when WIP is true and tag is non-null, the default notify level is downgraded to OWNER. Change-Id: I93395e36470090377d2120bb8136e7c11670d224
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.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recursive 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 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.