Skip to content

Permission level missing between Developer and Master to enforce pushes to protected branches only through MRs

Currently GitLab permissions does not support a group of "Master Developers" working in peer-reviewing team which wants to protect commits to master by error without peer-review from another "Master Developer": Current permissions have following effects:

  • Developer can't push directly to protected branches on gitlab

  • Developer can't accept and merge MRs to protected branches

  • Master can push directly to protected branches on gitlab

  • Master can accept and merge MRs to protected branches

We are working as a team and wish to avoid pushing to a protected branch, but be able to review each other's MRs and merge them need following permissions level: Let's call it Peer-Developer (do not care of name) which is between Developer and Master:

  • Peer-Developer can't push directly to protected branches on gitlab
  • Peer-Developer can accept and merge MRs to protected branches if he is not the MR requester

Looking at the current permissions table and at lines that are different between Developer and Master those would be the proposed added permission of Peer-Developer compared to Developer:

✓ Accept MRs to protected branches if he is not the merge-requester

That level for a project should also be enforced for group owners of the corresponding project.