Adapt documentation to having 'Projects' as top level menu

Change-Id: I6d4ea6ffa680d0a6ff19f961165ed81a1c95634f
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
This commit is contained in:
Edwin Kempin 2012-12-12 13:07:05 +01:00
parent 690cebedcd
commit 5819c95874
3 changed files with 7 additions and 7 deletions

View File

@ -15,14 +15,14 @@ To fix this problem verify
* that the branch name in the push specification is typed correctly
(case sensitive) and
* that the branch really exists for this project (in the Gerrit WebUI
go to 'Admin' -> 'Projects' and browse your project, then click on
go to 'Projects' > 'List' and browse your project, then click on
'Branches' to see all existing branches).
If it was your intention to create a new branch you can either
* bypass code review on push as explained link:user-upload.html#bypass_review[here] or
* create the new branch in the Gerrit WebUI before pushing (go to
'Admin' -> 'Projects' and browse your project, in the 'Branches'
'Projects' > 'List' and browse your project, in the 'Branches'
tab you can then create a new branch).
Please note that you need to be granted the

View File

@ -14,7 +14,7 @@ If you are facing this problem, do the following:
. Verify that the project name specified as git repository in the
push command is typed correctly (case sensitive).
. Verify that you are pushing to the correct Gerrit server.
. Go in the Gerrit WebUI to 'Admin' -> 'Projects' and check that the
. Go in the Gerrit WebUI to 'Projects' > 'List' and check that the
project is listed. If the project is not listed the project either
does not exist or you don't have
link:access-control.html#category_read['Read'] access for it. This

View File

@ -54,8 +54,8 @@ Change Submit Action
--------------------
The method Gerrit uses to submit a change to a project can be
modified by any project owner through the project console, `Admin` >
`Projects`. The following methods are supported:
modified by any project owner through the project console, `Projects` >
`List` > my/project. The following methods are supported:
* Fast Forward Only
+
@ -120,8 +120,8 @@ if the user has been granted the `Create Reference` access right.
Additional branches can also be created through the web UI, assuming
at least one commit already exists in the project repository.
A project owner can create additional branches under `Admin` >
`Projects` > `Branches`. Enter the new branch name, and the
A project owner can create additional branches under `Projects` >
`List` > my/project > `Branches`. Enter the new branch name, and the
starting Git revision. Branch names that don't start with `refs/`
will automatically have `refs/heads/` prefixed to ensure they are
a standard Git branch name. Almost any valid SHA-1 expression can