Google Git
Sign in
gerrit / gerrit / e6d6e1de272dfc37edf417509370d668b07bff0e
commite6d6e1de272dfc37edf417509370d668b07bff0e[log] [tgz]
authorGal Paikin <paiking@google.com>Thu May 07 18:31:22 2020 +0200
committerGal Paikin <paiking@google.com>Mon May 25 13:45:41 2020 +0000
tree7529ce18e2cdb5a4fc1ed1ee8b236c2c73ebf023
parentc538a5f6af61b025629a710c01674228e8879412 [diff]
Fix links and file name in emails for patchset-level comments

Currently, emails that include patchset-level comments will have
links to the file /PATCHSET_LEVEL. This is changed in such way
that all of those links will now link to the comments tab.

Also, the name of the file in the email was /PATCHSET_LEVEL, but now
it is "Patchset".

There are currently no tests about links being valid, simply because
it requires a brute-force string comparison. In my opinion, such a
test won't add much value anyway.

There is now a test about patchset level email notifications, that
confirms that the name /PATCHSET_LEVEL was changed to Patchset Level,
and also confirms that any links involving "/PATCHSET_LEVEL" were
omitted.

Change-Id: I08b6bcaff618ce4a645b1de936339f31d0fe0b15
4 files changed
tree: 7529ce18e2cdb5a4fc1ed1ee8b236c2c73ebf023
  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. polymer-bridges
  19. .bazelignore
  20. .bazelproject
  21. .bazelrc
  22. .bazelversion
  23. .editorconfig
  24. .git-blame-ignore-revs
  25. .gitignore
  26. .gitmodules
  27. .gitreview
  28. .mailmap
  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. WORKSPACE
  40. yarn.lock
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.