Google Git
Sign in
gerrit / gerrit / 4f12dcc3748e195a8bd788bc382fb3deb70c4e71
commit4f12dcc3748e195a8bd788bc382fb3deb70c4e71[log] [tgz]
authorThomas Draebing <thomas.draebing@sap.com>Tue Mar 28 20:59:04 2023 +0200
committerThomas Draebing <thomas.draebing@sap.com>Mon Apr 03 15:42:28 2023 +0200
treed87d4b62a67fa81d788036ace6811346a98530c4
parent6e069195734a8fb8e7c8899a7cd87b367d8175dc [diff]
Set uninteresting branches based on project configuration

The set of uninteresting branches varies depending on whether the
"Create a new change for every commit not in target" is set or not.
If it is not set all branches are uninteresting since you aren't
allowed to push the same commit for review on two different branches.
If it is set there are a lot more edge-cases to consider which
potentially requires a lot of rev-walking which in turn potentially
comes with a significant performance impact.

Not having to take the penalty for uninteresting edge-cases is the
preferred behavior.

Bug: Issue 16814
Release-Notes: Improve Rebase-SubmitStrategy performance in some cases
Change-Id: I2338c0a94304b7f899d446afa23fde920dc4639c
2 files changed
tree: d87d4b62a67fa81d788036ace6811346a98530c4
  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.