Access Control doc: Move 'Add Patch Set' to correct place

The "Add Patch Set" section was added directly after the "Push"
section, before the existing subsections of "Push", so now those
subsections are shown underneath "Add Patch Set" instead.

Move "Add Patch Set" down below those subsections.

Change-Id: Idfa2979843922eafb820b59eef37c92c888a66c2
This commit is contained in:
David Pursehouse 2016-08-31 10:25:19 +09:00
parent f4aa8b2a52
commit 596f3643a4

View File

@ -564,20 +564,6 @@ that would otherwise be used. Or it may give permission to upload
new changes for code review, this depends on which namespace the
permission is granted to.
[[category_add_patch_set]]
=== Add Patch Set
This category controls which users are allowed to upload new patch sets to
existing changes. Irrespective of this permission, change owners are always
allowed to upload new patch sets for their changes. This permission needs to be
set on `refs/for/*`.
The absence of this permission will prevent users from uploading a
patch set to a change they do not own. By default, this permission is granted to
`Registered Users` on `refs/for/*` allowing all registered users to upload a new
patch set to any change on that ref.
[[category_push_direct]]
==== Direct Push
@ -625,6 +611,20 @@ The force option has no function when granted to a branch in the
`+refs/for/refs/heads/*+` namespace.
[[category_add_patch_set]]
=== Add Patch Set
This category controls which users are allowed to upload new patch sets to
existing changes. Irrespective of this permission, change owners are always
allowed to upload new patch sets for their changes. This permission needs to be
set on `refs/for/*`.
The absence of this permission will prevent users from uploading a
patch set to a change they do not own. By default, this permission is granted to
`Registered Users` on `refs/for/*` allowing all registered users to upload a new
patch set to any change on that ref.
[[category_push_merge]]
=== Push Merge Commits