Google Git
Sign in
gerrit / gerrit / 329416c67371e1bae09496843e94b7d09b3c94c7
commit329416c67371e1bae09496843e94b7d09b3c94c7[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Mon Jul 25 15:52:35 2022 +0200
committerEdwin Kempin <ekempin@google.com>Tue Jul 26 06:25:11 2022 +0000
tree113bffff960ec3a08af7e0f736af43222207597f
parentb7e9bb1d9f35f29abb13777adf43043ec81e0957 [diff]
Document that refs/meta/config is often excluded from submit requirements

We had cases where project owners misconfigured a submit requirement so
that they couldn't change the refs/meta/config branch through review
anymore:

1. The project owner adds a submit requirement without applicableIf
   expression although the submit requirement is intended to apply to
   code branches only.

2. After the submit requirement has been added, changes to the
   refs/meta/config branch can no longer be submitted, because the new
   submit requirement cannot be satisfied there (e.g. it requires a vote
   from a bot that doesn't run for the refs/meta/config branch).

3. The project owner cannot add the missing applicableIf expression
   because submission to the refs/meta/config branch is blocked by the
   unsatisfiable submit requirement.

In this case fixing the submit requirement requires bypassing code
review and projects owners may not know how to do this or it may even
not be allowed to them.

Update the documentation for the applicableIf expression to mention
explicitly that this parameter is often used to exclude the
refs/meta/config branch from a submit requirement. Maybe this can help
preventing project owners from running into the issue described above.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I9ab8d7a37f8602aa72a11b016e8165fd997f3ffe
Release-Notes: skip
2 files changed
tree: 113bffff960ec3a08af7e0f736af43222207597f
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. polymer-bridges
  20. .bazelignore
  21. .bazelproject
  22. .bazelrc
  23. .bazelversion
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitignore
  27. .gitmodules
  28. .gitreview
  29. .mailmap
  30. .pydevproject
  31. .zuul.yaml
  32. BUILD
  33. COPYING
  34. INSTALL
  35. Jenkinsfile
  36. package.json
  37. README.md
  38. SUBMITTING_PATCHES
  39. version.bzl
  40. WORKSPACE
  41. yarn.lock
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status Maven Central

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 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.