blob: df465660347664f1fa6ff3c0fff7843927e6a982 [file] [log] [blame]
Edwin Kempin40f31e52011-01-12 14:11:06 +01001prohibited by Gerrit
2====================
3
4This is a general error message that is returned by Gerrit if a push
5is not allowed, e.g. because the pushing user has no sufficient
6privileges.
7
8In particular this error occurs:
Edwin Kempinddfc41a2011-05-06 10:32:05 +02009
Edwin Kempin40f31e52011-01-12 14:11:06 +0100101. if you push a commit for code review to a branch for which you
Fredrik Luthander0bb123d2011-12-29 11:36:48 +010011 don't have upload permissions (access right
12 link:access-control.html#category_push_review['Push'] on
13 `refs/for/refs/heads/*`)
142. if you bypass code review without
Edwin Kempin8dd505c2012-01-23 10:42:41 +010015 link:access-control.html#category_push_direct['Push'] access right
Fredrik Luthander0bb123d2011-12-29 11:36:48 +010016 on `refs/heads/*`
Edwin Kempin8dd505c2012-01-23 10:42:41 +0100173. if you push an annotated tag without
18 link:access-control.html#category_push_annotated['Push Annotated Tag']
19 access right on 'refs/tags/*'
Fredrik Luthander0bb123d2011-12-29 11:36:48 +0100204. if you push a lightweight tag without the access right link:access-control.html#category_create['Create
21 Reference'] for the reference name 'refs/tags/*'
Edwin Kempin40f31e52011-01-12 14:11:06 +010022
David Pursehouse221d4f62012-06-08 17:38:08 +090023For new users it often happens that they accidentally try to bypass
Edwin Kempind1a83692011-02-09 07:51:09 +010024code review. The push then fails with the error message 'prohibited
25by Gerrit' because the project didn't allow to bypass code review.
26Bypassing the code review is done by pushing directly to refs/heads/*
27(e.g. refs/heads/master) instead of pushing to refs/for/* (e.g.
28refs/for/master). Details about how to push commits for code review
29are explained link:user-upload.html#push_create[here].
30
Edwin Kempin40f31e52011-01-12 14:11:06 +010031
32GERRIT
33------
34Part of link:error-messages.html[Gerrit Error Messages]