Google Git
Sign in
gerrit / gerrit / 33c13a444eb58321a5a96184fe3ae5427fa8142d
commit33c13a444eb58321a5a96184fe3ae5427fa8142d[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Fri Jan 10 11:38:06 2020 +0100
committerEdwin Kempin <ekempin@google.com>Fri Jan 10 11:41:35 2020 +0100
tree63825f95a1042fbaeecc4ebc4d39af13f428ac7c
parenta767f08db318d9cb619bd73d441fb363436eb029 [diff]
Label config: Allow to configure individual votes as sticky

At the moment one can only configure min/max (-2/+2) or all (-2 .. +2)
votes as sticky, but sometimes it's e.g. wanted that all negative
(-2, -1) / all positive (+1, +2) votes are sticky. Instead of adding
sepcific copy rules for this (e.g. copyNegativeScore and
copyPositiveScore) allow to configure indiviual votes as sticky. This is
more flexible and can cover all possible scenarios.

E.g. we could use the new copy rule to make positive votes in the
homepage repo sticky which e.g. helps with visualising consent on design
docs (see issue 12025).

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

Gerrit Code Review

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

Build Status

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.