Google Git
Sign in
gerrit / gerrit / ae7b747dfadbec911bf655fc73b445644bad732e
commitae7b747dfadbec911bf655fc73b445644bad732e[log] [tgz]
authorYoussef Elghareeb <ghareeb@google.com>Thu Jan 07 11:30:57 2021 +0100
committerYoussef Elghareeb <ghareeb@google.com>Thu Jan 07 13:18:58 2021 +0100
treea8d0e6e9bb311b407808c55246c0785f04c6ff51
parent9418a1effe9fe8c78582b00c1dded279d6878aff [diff]
Disallow creating changes on internal Gerrit refs

This is a follow up to change If5fb50e1f7b which allowed creating
changes using the REST API to particular refs, namely: refs/heads,
refs/meta/dashboards, HEAD or refs/meta/config.

We found some cases with changes created on other ref patterns, e.g.
refs/experimental. Although these cases were not frequent, but the
previous change could break existing workflows.

With this change, we modify the behaviour to disallow creating changes
on refs/tags/* and Gerrit internal refs instead, such as refs/users/*,
refs/groups/*, refs/meta/external-ids/*, etc...

Change-Id: I35ca35be9e8294acf2f4f906c380331a45e0234a
4 files changed
tree: a8d0e6e9bb311b407808c55246c0785f04c6ff51
  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.