Most restrictive protected branch rule should take precedence
<!--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=285560) </details> <!--IssueSummary end--> ### Problem to solve Branch protection can be currently overridden by creating a less permissive rule with the same name. ![image](/uploads/b0f6d760f0115f0e2aa2c48a25c6918a/image.png) ### Proposal The most restrictive rule should always take precedence over all others OR Allow only unique `Branch` name descriptors. ### Customers * https://gitlab.my.salesforce.com/00161000004zrG3
issue