<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=14168) </details> <!--IssueSummary end--> 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.