blob: 58919d5bee961fe5724ffabf011c8c9a5ede26c8 [file] [log] [blame]
Edwin Kempin4c58c302011-01-11 10:33:33 +01001not a Gerrit project
2====================
3
4With this error message Gerrit rejects to push a commit if the git
5repository to which the push is done does not exist as a project in
6the Gerrit server or if the pushing user has no read access for this
7project.
8
9The name of the project in Gerrit has the same name as the path of
10its git repository (excluding the '.git' extension).
11
12If you are facing this problem, do the following:
Edwin Kempinddfc41a2011-05-06 10:32:05 +020013
14. Verify that the project name specified as git repository in the
15 push command is typed correctly (case sensitive).
16. Verify that you are pushing to the correct Gerrit server.
Edwin Kempin5819c952012-12-12 13:07:05 +010017. Go in the Gerrit WebUI to 'Projects' > 'List' and check that the
Edwin Kempinddfc41a2011-05-06 10:32:05 +020018 project is listed. If the project is not listed the project either
Fredrik Luthander5d976a02012-01-20 13:06:06 +010019 does not exist or you don't have
20 link:access-control.html#category_read['Read'] access for it. This
David Pursehouse221d4f62012-06-08 17:38:08 +090021 means if you are certain that the project name is right you should
Fredrik Luthander5d976a02012-01-20 13:06:06 +010022 contact the Gerrit Administrator or project owner to request access
23 to the project.
Edwin Kempin4c58c302011-01-11 10:33:33 +010024
25This error message might be misleading if the project actually exists
26but the push is failing because the pushing user has no read access
27for the project. The reason that Gerrit in this case denies the
28existence of the project is to prevent users from probing the Gerrit
29server to see if a particular project exists.
30
31
32GERRIT
33------
34Part of link:error-messages.html[Gerrit Error Messages]