Added explanation for "not a Gerrit project" error

Added a documentation page that explains the
"not a Gerrit project" error in details and what
can be done to solve the problem.

Signed-off-by: Edwin Kempin <edwin.kempin@gmail.com>
Change-Id: Ib50dbddd4357c39b0ed2f44158d23596d5770bce
This commit is contained in:
Edwin Kempin 2011-01-11 10:33:33 +01:00
parent 40f31e52d2
commit 4c58c30bd5
2 changed files with 33 additions and 0 deletions

View File

@ -15,6 +15,7 @@ Error Messages
* link:error-missing-changeid.html[missing Change-Id in commit message]
* link:error-multiple-changeid-lines.html[multiple Change-Id lines in commit message]
* link:error-no-new-changes.html[no new changes]
* link:error-not-a-gerrit-project.html[not a Gerrit project]
* link:error-not-valid-ref.html[not valid ref]
* link:error-permission-denied.html[Permission denied (publickey)]
* link:error-prohibited-by-gerrit.html[prohibited by Gerrit]

View File

@ -0,0 +1,32 @@
not a Gerrit project
====================
With this error message Gerrit rejects to push a commit if the git
repository to which the push is done does not exist as a project in
the Gerrit server or if the pushing user has no read access for this
project.
The name of the project in Gerrit has the same name as the path of
its git repository (excluding the '.git' extension).
If you are facing this problem, do the following:
1. Verify that the project name specified as git repository in the
push command is typed correctly (case sensitive).
2. Verify that you are pushing to the correct Gerrit server.
3. Go in the Gerrit WebUI to 'Admin' -> 'Projects' and check that the
project is listed. If the project is not listed the project either
does not exist or you don't have read access ('+1 Read Access' in
the link:access-control.html#category_READ['Read Access'] category) for it. This means if you certain that
the project name is right you should contact the Gerrit
Administrator or project owner to request access to the project.
This error message might be misleading if the project actually exists
but the push is failing because the pushing user has no read access
for the project. The reason that Gerrit in this case denies the
existence of the project is to prevent users from probing the Gerrit
server to see if a particular project exists.
GERRIT
------
Part of link:error-messages.html[Gerrit Error Messages]