| commit | a112144f6f484923d06d38b48e5998cd5c428527 | [log] [tgz] |
|---|---|---|
| author | Youssef Elghareeb <ghareeb@google.com> | Wed Jun 14 14:53:59 2023 +0200 |
| committer | Youssef Elghareeb <ghareeb@google.com> | Thu Jun 29 10:42:38 2023 +0200 |
| tree | b9316674354e34dccc88a2b54be1ea7444ecec98 | |
| parent | 4c11544ba8c7170c21c8ad9124ecf9c82e57e096 [diff] |
Add a new parents_data field in RevisionInfo The new field is a list of ParentInfo entities and provides more information about the parent commit of the patch-set. There are two cases for parent commits: 1) It can be a merged commit in the target branch. We detect this case by checking if the parent commit SHA-1 is reachable from the tip of the target branch. 2) Otherwise, we assume that the parent commit is a patch-set of another gerrit change. We lookup the parent commit SHA-1 in the change index to get the change data of the parent. The new `parents_data` field is not returned in response by default, but is gated with a List Change Option. Returning this data on the API is beneficial to provide better highlights of the parents in the web UI when showing diffs (especially patchset diffs). The web UI can request CommitInfo for each LHS/RHS patchsets in the diff. Note on compatibility: we added a new entity called ParentCommitData in the entities package, but this entity is not serialized anywhere. It's only used as an intermediary entity before surfacing the new data on the API, hence it does not harm. Change-Id: I9d572e61eed9c8a3937f7e4064f0357323481654 Release-Notes: Add a new parents_data field in RevisionInfo Forward-Compatible: checked
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.