opendev/gerrit
Code Issues Proposed changes

Improve push tag examples in the access control documentation

Browse Source 
The examples of pushing a tag in the access control documentation
imply that pushing a tag is only possible over SSH, when in fact
it is also possible over HTTPS.

Reword the examples to also include HTTPS.

Change-Id: I561e116c8c1a4ce0912fccdbd77a0848bb2bc060
This commit is contained in:
David Pursehouse
2012-12-12 19:22:45 +09:00
parent be7f458826
commit 690cebedcd
1 changed files with 18 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
Documentation/access-control.txt
View File

@@ -651,14 +651,20 @@ of merge commits.
Push Annotated Tag
~~~~~~~~~~~~~~~~~~
This category permits users to push an annotated tag object over
SSH into the project's repository. Typically this would be done
with a command line such as:
This category permits users to push an annotated tag object into the
project's repository. Typically this would be done with a command line
such as:
====
git push ssh://USER@HOST:PORT/PROJECT tag v1.0
====
Or:
====
git push https://HOST/PROJECT tag v1.0
====
Tags must be annotated (created with `git tag -a`), should exist in
the `refs/tags/` namespace, and should be new.
@@ -686,14 +692,20 @@ requires the same permission as deleting a branch.
Push Signed Tag
~~~~~~~~~~~~~~~
This category permits users to push a PGP signed tag object over
SSH into the project's repository. Typically this would be done
with a command line such as:
This category permits users to push a PGP signed tag object into the
project's repository. Typically this would be done with a command
line such as:
====
git push ssh://USER@HOST:PORT/PROJECT tag v1.0
====
Or:
====
git push https://HOST/PROJECT tag v1.0
====
Tags must be signed (created with `git tag -s`), should exist in the
`refs/tags/` namespace, and should be new.