commit | 94db6b6e845fc3647cbf08a291b64f8f29b2b7fd | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Fri Sep 02 14:37:17 2016 +0200 |
committer | Edwin Kempin <ekempin@google.com> | Tue Sep 06 11:42:46 2016 +0200 |
tree | 4b7256d9939c76f7d7910f71423ef9403f607021 | |
parent | 86cdf1b494f44095408567a6b98941e7a0ee8e43 [diff] |
Make permissions for tag creation consistent For each tag type you need a special permission for the tag creation: - Lightweight tags require 'Create Reference' - Annontated tags require 'Push Annotated Tags' - Signed tags require 'Push Signed Tags' When creating a tag by push there are 2 cases: 1. The commit to which the tag points already exists in Gerrit (it is reachable from any branch/tag that is readable by the calling user) 2. The commit to which the tag points is new (it is not reachable from any branch/tag that is readable by the calling user) So far the permissions that were required to push a tag on a new commit were inconsistent: - For lightweight tags we required 'Push' in addition to 'Create Reference' - For annotated/signed tags 'Push Annotated Tags'/'Push Signed Tags' were sufficient. Due to this it was not possible to allow pushing of annotated/signed tags for existing commits, but not for new commits. Change the behaviour for annotated/signed tags so that it's consistent with the behaviour for lightweight tags and require 'Push' in addition to 'Push Annotated Tags'/'Push Signed Tags', if the tag points to a new commit. We may consider renaming 'Push Annotated Tags'/'Push Signed Tags' to 'Create Annotated Tags'/'Create Signed Tags' later. Add tests for the tag creation by push that cover lightweight and annotated tags on existing and new commits. Tests for signed tags may be added later. Change-Id: I1094a2be4871e16239b6a6daefc537ffc77af3bf Signed-off-by: Edwin Kempin <ekempin@google.com>
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 IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Buck and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit cd gerrit && buck 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>]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.