1531f6101a
This change alters the semantics of adding reviewers/CCs during push to match the semantics of the Post Reviewers endpoint. The fact that they differed is mostly an accident of history: support for adding reviewers over push long predates reviewers-by-email or any of the other fanciness added to Post Reviewers in the past few years. The most significant semantic change is increasing the space of allowed reviewers via push option: * By email, if the project allows it. * Group names. For now at least, attempting to add a non-existing reviewer still fails, whether due to a non-existing email when reviewers by email are not supported, or a non-email input. The error message in this case has changed to align with the error message from the REST API. Due to an issue in the implementation of GroupResolver, adding groups via push currently only works for internal groups if the group is visible to anonymous users. This is still strictly more functionality than before, when groups weren't supported at all, so keep the behavior even with this known bug. Change-Id: I24c0c27664d04f431e5b0f0c854df4a6de2ac014 |
||
|---|---|---|
| .settings | ||
| antlr3 | ||
| contrib | ||
| Documentation | ||
| gerrit-acceptance-tests/src/test/java/com/google/gerrit/acceptance/git | ||
| gerrit-gwtdebug | ||
| gerrit-gwtui | ||
| gerrit-gwtui-common | ||
| gerrit-plugin-gwtui | ||
| java | ||
| javatests | ||
| lib | ||
| plugins | ||
| polygerrit-ui | ||
| prolog | ||
| prologtests | ||
| proto | ||
| resources | ||
| tools | ||
| webapp | ||
| .bazelproject | ||
| .bazelrc | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .pydevproject | ||
| BUILD | ||
| COPYING | ||
| INSTALL | ||
| README.md | ||
| SUBMITTING_PATCHES | ||
| version.bzl | ||
| WORKSPACE | ||
Gerrit Code Review
Gerrit is a code review and project management tool for Git based projects.
Objective
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.
Documentation
For information about how to install and use Gerrit, refer to the documentation.
Source
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Reporting bugs
Please report bugs on the issue tracker.
Contribute
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.
Getting in contact
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
License
Gerrit is provided under the Apache License 2.0.
Build
Install Bazel and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
Install binary packages (Deb/Rpm)
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>]
Use pre-built Gerrit images on Docker
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.