Google Git
Sign in
gerrit / gerrit / bf9df393af6d64fa0bb2feffb62ac7c415b5389b
commitbf9df393af6d64fa0bb2feffb62ac7c415b5389b[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Fri Jan 12 15:20:48 2018 +0100
committerEdwin Kempin <ekempin@google.com>Wed Aug 01 08:58:18 2018 +0200
tree4982978c92bde356987a63e0ec9a491b110074c5
parentb9287e0a0ffc77f165e6711487f684820ad78d6b [diff]
Add REST endpoint to check for auto-closeable changes in a project

The consistency check searches for open changes that can be auto-closed
because a commit of the change is already contained in the destination
branch or because the destination branch contains a commit with the same
Change-Id. Normally Gerrit auto-closes such changes when the
corresponding commits are pushed directly to the repository. However if
auto-closing on direct push fails and the push is still successful
change states get inconsistent (changes that are already part of the
destination branch are still open). This consistency check is intended
to detect and repair this situation.

Change-Id: I79e46f70d59258ef972ba5d72e40d952fccc0c0f
Signed-off-by: Edwin Kempin <ekempin@google.com>
11 files changed
tree: 4982978c92bde356987a63e0ec9a491b110074c5
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. gerrit-acceptance-tests/
  6. gerrit-gwtdebug/
  7. gerrit-gwtui/
  8. gerrit-gwtui-common/
  9. gerrit-plugin-gwtui/
  10. java/
  11. javatests/
  12. lib/
  13. plugins/
  14. polygerrit-ui/
  15. prolog/
  16. prologtests/
  17. proto/
  18. resources/
  19. tools/
  20. webapp/
  21. .bazelproject
  22. .editorconfig
  23. .git-blame-ignore-revs
  24. .gitignore
  25. .gitmodules
  26. .mailmap
  27. .pydevproject
  28. BUILD
  29. COPYING
  30. INSTALL
  31. README.md
  32. SUBMITTING_PATCHES
  33. version.bzl
  34. 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 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.