More granular permission for protected branches

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

• Close this issue

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.