Merge request flow feature proposal

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

I'm looking to have a branch protected against direct commits, but still allow developers to commit through a peer-review process.

Basically, I'd like to have the branch protected (to prevent accidental non-reviewed pushes), but still allow users with developer privilege to use their existing credentials to review and accept merge requests.

I suppose that merges that could not be automated through the GitLab UI would still require higher access.

I'm thinking this could be feasible by having a different kind of branch protection which would behave differently through the GitLab merge UI.