user-search: Remove approval requirement from basic search Basic search (i.e. not using the explicit predicate) can never work as expected for approval requirements because when a label is applied to a change a comment containing the label name is added as a message on the change. This means that any change with that label will match with the comment predicate, regardless of the label score. For example if we have two changes with the following labels: Change 1: Code-Review+2 Change 2: Code-Review+1 Then both changes have messages like: Patch Set 1: Code-Review+2 Patch Set 1: Code-Review+1 And when we issue the query: Code-Review+2 the query builder resolves it into both a label predicate (which will only match change 1) and a message predicate (which will match both changes). Undo the formatting change that was done in Ia1a138d3e, since it is no longer relevant. Instead, remove the approval requirement section from the basic search documentation. Add a clarification that if the user wants predictable search results they should use explicit predicates rather than the basic search. This reverts commit 025b2633aefaa04eba8134dee90da559efd94bcd. Bug: Issue 8589 Change-Id: I58a27530c3f2b530d078e030b2eebd3e47c82f0f
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.