opendev/gerrit
Code Issues Proposed changes

Documentation: Bypass review updated with 2.2.x permissions

Browse Source 
Updates the Bypass review section in user-upload.txt with information
about how to configure permissions in Gerrit 2.2.x instead of the old
2.1.x permissions.

Change-Id: I74222b9932e14bd88d04d5a20c91476b9aaea29c
Signed-off-by: Fredrik Luthander <fredrik.luthander@sonyericsson.com>
This commit is contained in:
Fredrik Luthander
2012-01-23 17:00:45 +01:00
committed by Gustaf Lundh
parent 2b3cd55297
commit c10f9e7617
1 changed files with 14 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
Documentation/user-upload.txt
View File

@@ -280,19 +280,26 @@ or rewritten by the pusher.
* `refs/tags/*`: annotated tag objects pointing to any other type * `refs/tags/*`: annotated tag objects pointing to any other type
of Git object can be created. of Git object can be created.
To push branches, the link:access-control.html#category_push_direct['Push'] To push branches, the proper access rights must be configured first.
right must be granted to one (or more) of the user's groups. The Here follows a few examples of how to configure this in Gerrit:
allowed levels within this category are:
* Update: Any existing branch can be fast-forwarded to a new commit. * Update: Any existing branch can be fast-forwarded to a new commit.
This is the safest mode as commits cannot be discarded. Creation This is the safest mode as commits cannot be discarded. Creation
of new branches is rejected. of new branches is rejected. Can be configured with
* Create: Implies Update, but also allows creation of a new branch link:access-control.html#category_push_direct['Push'] access.
if the name does not not already designate an existing branch name. * Create: Allows creation of a new branch if the name does not
* Delete: Implies Create and Update, but also allows an existing already designate an existing branch name. Needs
link:access-control.html#category_create['Create Reference']
configured. Please note that once created, this permission doesn't
grant the right to update the branch with further commits (see above
for update details).
* Delete: Implies Update, but also allows an existing
branch to be deleted. Since a force push is effectively a delete branch to be deleted. Since a force push is effectively a delete
followed by a create, but performed atomically on the server and followed by a create, but performed atomically on the server and
logged, this also permits forced push updates to branches. logged, this also permits forced push updates to branches.
To grant this access, configure
link:access-control.html#category_push_direct['Push'] with the
'Force' option ticked.
To push annotated tags, the `Push Annotated Tag` project right must To push annotated tags, the `Push Annotated Tag` project right must
be granted to one (or more) of the user's groups. There is only be granted to one (or more) of the user's groups. There is only