Google Git
Sign in
gerrit / gerrit / 0a707c9f5f2fb67e936893309f032ddae64ec7a2
commit0a707c9f5f2fb67e936893309f032ddae64ec7a2[log] [tgz]
authorBen Rohlfs <brohlfs@google.com>Fri Sep 22 13:36:37 2023 +0200
committerBen Rohlfs <brohlfs@google.com>Thu Sep 28 17:21:07 2023 +0200
treea2ae2b10e2a1caacf15719c25f62fb6ff7d420d0
parentd96344cc34a5c632eb0bd0da23d99c11f1ea0aa7 [diff]
Further refine the revision parents UI

<gr-revision-parents> is a new (flag protected) component that shows
additional information about the parents (aka bases) when comparing
two patchsets. The component is shown above the file list and below
the patchset picker on the change page. A small amount of information
is also added to the patchset picker (<gr-patch-range-select>).

This is the outcome of discussions with Arnab and Youssef in
go/revision-parents.

This change is still flag protected, so no users are directly
affected.

I would prefer to have detailed UX discussions once this is live in
canary.

It is expected that this still needs some testing and polish.

Example screenshot: https://imgur.com/a/vhR40hj

Release-Notes: skip
Google-Bug-Id: b/289177174
Change-Id: I2dd65f8bde157235875c938fb13bb2b3555f5a41
7 files changed
tree: a2ae2b10e2a1caacf15719c25f62fb6ff7d420d0
  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. .pydevproject
  30. .zuul.yaml
  31. BUILD
  32. COPYING
  33. INSTALL
  34. Jenkinsfile
  35. package.json
  36. README.md
  37. SUBMITTING_PATCHES
  38. version.bzl
  39. web-dev-server.config.mjs
  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.