Google Git
Sign in
gerrit / gerrit / 27d6201a4f6b6d4f61a0c9f632efd16060fcd955
commit27d6201a4f6b6d4f61a0c9f632efd16060fcd955[log] [tgz]
authorYoussef Elghareeb <ghareeb@google.com>Tue Feb 23 18:21:46 2021 +0100
committerYoussef Elghareeb <ghareeb@google.com>Fri Feb 26 17:56:33 2021 +0100
tree24c1c8bb8bbdef67131d811aaa01ef0219cbadbb
parentb334bae2355b61e1c745914692868d14877a9aa7 [diff]
Add the source content type to the comment context

This change adds a new field "source_content_type" to the CommentInfo
entity. This field contains the content type (mime type) of the source
file where the comment is written.

This is needed by the front-end to do syntax highlighting. We return the
file content type in the Get Diff endpoint (check DiffFileMetaInfo). In
this change we are reusing this small part of the diff logic to compute
the mime type of the source file while loading the comment context.

Also added some tests to make sure the content type is returned
correctly, and another test to make sure the comment context is
de/serialized correctly.

Change-Id: Ib1f7281866ca6a11e88e44024a424f253efcb758
11 files changed
tree: 24c1c8bb8bbdef67131d811aaa01ef0219cbadbb
  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.