CODEOWNER approval groups required
Proposal
we would like to see support more flexible codeowner approval rules.
example structure
- shared_sub_project
- sub_project 1 (devs 1,2,3)
- sub_project2 (devs 4,5,6)
- sub_project 3 (devs 7,8,9)
We have for example a monorepo with 3 subprojects, each subproject has 3 devs. The subprojects share another subproject. We want to enforce code quality by having at least two different projects approve changes on the shared project. right now we have a rule like
[shared maintainers][2] dev1 dev4 dev7
shared_sub_project
But with this rule we are often blocked by the need of two of three specific devs to approve the mr. If we could have groups instead this would be much more efficient. so we suggest something like
[shared maintainers][2] (dev1,dev2,dev3), (dev4,dev5,dev6), (dev7,dev8,dev9)
shared_sub_project