<!--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=285522) </details> <!--IssueSummary end--> ### Problem to solve Large repositories and monorepos contain both mission critical code as well as non-mission critical code (documentation, etc). Teams managing these large repositories cannot selectively state which paths/directories have more stringent policies. Today branch protection is all or nothing. This prevents administrators from encouraging contributions to non-mission critical parts of the code. ### Proposal Provide a mechanism which allows repo administrators detail which paths/directories inside the repository should abide by the branch protection settings and which ones do not.