<!--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=388339) </details> <!--IssueSummary end--> Our environment has naming standards for our "official repo". Folks are expected to fork the official source, do whatever they want in their copy, and submit an MR. From time to time, folks with elevated rights end up cloning the wrong repo and pushing their playground branches into the "official copy". This is a bit frustrating. Protect Branches cannot solve this very well as, when set to `*` with Merge=`None` and Push=`None` the `rebase` button doesn't work on any branches - even when explicitly listed under `Protect Branches`.