| commit | d736da341fe1041e879165b0c78177eab9ceed24 | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Wed Jul 27 12:41:05 2022 +0200 |
| committer | Edwin Kempin <ekempin@google.com> | Wed Jul 27 17:33:06 2022 +0200 |
| tree | d6a46757b6a2ebdff01626fa9ac9fdcf24835200 | |
| parent | 5eae617f633d8b6d7f09a4e0364fc4a7d578da59 [diff] |
Revamp the documentation of the submit strategies * Merge the 'Submit Type' section into the section that describes the 'submit.action' configuration parameter. * Make it clear that 'submit action', 'submit type' and also 'submit strategy' are all synonymous terms. * Add a hint explaining that the values to be set for submit.action in project.config indeed contain spaces (e.g. it's 'merge if necessary' and not 'merge_if_necessary'). * Keep existing anchors so that they continue working. * Fix name of the 'Merge Always' submit action, which was wrongly documented as 'Always Merge'. * Explicitly mention that 'cherry pick' is the only action that ignores dependencies. * Order the submit actions by importance, starting with the most used submit action 'merge if necessary' and ending with the least recommended submit actions 'fast-forward-only' and 'cherry-pick'. * Fix various formatting issues. * Consistently wrap lines after 80 characters. This revamp is just a first step to rework this documentation and further improvements by follow-up changes are necessary. E.g. the descriptions of the different submit actions have not been updated yet and are still suboptimal and inconsistent. Signed-off-by: Edwin Kempin <ekempin@google.com> Release-Notes: skip Change-Id: I0dd66d71f3989308cba32330412e4f90052f7a86
Gerrit is a code review and project management tool for Git based projects.
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.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
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.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
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>]
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.