Google Git
Sign in
gerrit / gerrit / 777ff4715d92eaaef5e149334d901188359f3294
commit777ff4715d92eaaef5e149334d901188359f3294[log] [tgz]
authorGal Paikin <paiking@google.com>Wed Oct 16 20:30:12 2019 +0200
committerGal Paikin <paiking@google.com>Wed Dec 11 16:29:27 2019 +0100
treeea83c570ac6cae10714eb32d47693c41bd2d6157
parentfde8bb17436d3dfdbbf365d49161a1ed8cef8331 [diff]
Add idForNewChange parameter for cherry-picking a change

Add capability when performing the cherry-pick change method to
specify the numeric change-id of the new change that is to be created.
Cherry-pick is also possible to an existing change, and it will just
create a new patchset; in this case, we check to see that the inputs
given to the function agree with the Change-Id and the Id of that
change, otherwise we throw an error.

This change is useful when performing a batchUpdate. When performing a
batchUpdate it is necessary to know the numeric change id in advance, so
without passing the numeric change id as a parameter it will not be
possible to perform a batchUpdate with both the cherry-pick and any
other update that involves the newly created change (e.g sending
notifications).

Change-Id: I156d30ff719106041f499f0e73b456478f1e1e97
1 file changed
tree: ea83c570ac6cae10714eb32d47693c41bd2d6157
  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.