Google Git
Sign in
gerrit / gerrit / 34be4103d1e13147ac6c82008e16c3b8ae2c5d36
commit34be4103d1e13147ac6c82008e16c3b8ae2c5d36[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Wed Apr 24 09:44:22 2019 +0200
committerEdwin Kempin <ekempin@google.com>Wed Apr 24 09:52:06 2019 +0200
tree082122fdbeb79dc5b7c0920323229c5c510befab
parent6524ae6f2563e3f55ee1e825b3cc7de1824df8a9 [diff]
Extract recommendations how to craft changes into a separate doc page

dev-contributing.txt should focus on describing the contribution
processes. At the moment we only have a single contribution process
(push a change and wait for review), but we plan to establish a new
contribution process with mentor guidance in addition. This new process
should be described on dev-contributing.txt too. All recommendations how
to craft changes are generally applicable, independent of which
contribution process is chosen, hence it makes sense to have them on a
separate page.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Ia08da4ccd929c078761efd6ffe87a8883cc95118
3 files changed
tree: 082122fdbeb79dc5b7c0920323229c5c510befab
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. java/
  6. javatests/
  7. lib/
  8. plugins/
  9. polygerrit-ui/
  10. prolog/
  11. prologtests/
  12. proto/
  13. resources/
  14. tools/
  15. webapp/
  16. .bazelproject
  17. .bazelrc
  18. .editorconfig
  19. .git-blame-ignore-revs
  20. .gitignore
  21. .gitmodules
  22. .mailmap
  23. .pydevproject
  24. BUILD
  25. COPYING
  26. INSTALL
  27. README.md
  28. SUBMITTING_PATCHES
  29. version.bzl
  30. WORKSPACE
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 IRC channel on freenode is #gerrit. An archive is available at: echelog.com.

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.