Reputation: 271
I want to set up configuration described below:
Registered user can not push his changes directly to master. He has to push these changes for review:
git push origin master
- it should be rejected by Gerrit (origin = Gerrit)
git push origin HEAD:refs/for/master
- it should be allowed by Gerrit
Registered user can create a new branch. This branch will be treated as a backup and a way of cooperation between two or more developers so it shouldn't be reviewed.
git push origin xyz_abc
- it should be allowed by Gerrit
How should I configure Gerrit
to achieve such functionality ?
Upvotes: 20
Views: 15484
Reputation: 19356
You need to change the Access settings of your project and there you need to make use of the Exclusive
flag to override the Deny settings for refs/heads/master
. With a configuration like this you should be able to achieve this "allow to push everywhere except to the master
branch".
Upvotes: 3
Reputation: 11
With guidance from mmelnik answer to this thread.
When the references overlap, only one of them works at a time (more generic one).
So, you should not set deny permission for master and allow all other branches, instead you can use a prefix for your development branches and use the below reference to allow the push to them:
^refs/heads/YourPrefix.*
Note: Preserve the ^
& *
at the start and end for the regex.
Upvotes: 0
Reputation: 2896
There are no good instructions anywhere, so thought I'd document the steps here.
1. Navigate to your project's Access page
Projects > List > your_project > Access
2. Edit Access
Click the Edit button
3. Add Reference to refs/heads/*
This is the reference for all direct pushes. We're going to configure who can do what to this path.
Click "Add Reference" and type in 'refs/heads/*' (no quotes)
4. Deny the "Push" permission
The Push permission is the one which controls who can make direct pushes. Merge pushes and pushes to Gerrit will still be allowed (see notes below).
5. Save Changes
And you're done. The finished config should look something like this:
Note
If this doesn't work, make sure you have the Push permission set to ALLOW on refs/for/refs/* - this is the permission which allows pushes to Gerrit.
Upvotes: 10
Reputation: 4456
If there are many branches you can use namespaces (e.g. dev/*) for branches and set access control for these namespaces.
Upvotes: 0
Reputation: 8310
AFAIK you can set up permissions for every repo/project in gerrit. For example who can push / who can force push / who can approve your changes and all that. Check below link if it is usefull :
https://git.eclipse.org/r/Documentation/access-control.html
Upvotes: 0