e981d81315
- The 'Submit Type' and 'Allow content merges' sections were wrongly listed under the 'The file rules.pl' section. - The described path to update the submit in the UI was outdated. - In the 'Submit section' section 'mergeContent' was described as "Defines whether to automatically merge changes." which sounds like changes would be merged automatically, which is not the case. - The 'Submit Type' and the 'Allow content merges' sections didn't mention how the corresponding parameter in 'project.config' is named. - The 'Submit section' section contained an incomplete entry for "Merge strategy". - The phrasing in the 'Submit Type' section sounded like a change that is being submitted but cannot be merged stays in the state 'Submitted' which is no longer the case. Change-Id: I07a69381d2d5d2fffdf7deeb5129339aa7f1bc01 Signed-off-by: Edwin Kempin <ekempin@google.com> |
||
|---|---|---|
| .settings | ||
| antlr3 | ||
| contrib | ||
| Documentation | ||
| e2e-tests/load-tests | ||
| java | ||
| javatests/com/google/gerrit | ||
| lib | ||
| modules | ||
| plugins | ||
| polygerrit-ui | ||
| prolog | ||
| prologtests | ||
| proto | ||
| resources | ||
| tools | ||
| webapp | ||
| .bazelignore | ||
| .bazelproject | ||
| .bazelrc | ||
| .bazelversion | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .gitmodules | ||
| .gitreview | ||
| .mailmap | ||
| .pydevproject | ||
| BUILD | ||
| COPYING | ||
| INSTALL | ||
| Jenkinsfile | ||
| package.json | ||
| 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 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 --recurse-submodules 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.