CODEOWNERS as the team name in approval_rules

[huydinhle]

We would like to utilize the CODEOWNERS file for the teams array in approval_rules. Is there a way to do this ?

[bluekeyes]

At the moment, policy-bot has no integrations with the CODEOWNERS file. Can you provide some more detail about the use you have in mind?

[NargiT]

how will this work with bots?

[aw185176]

For large repositories, we might have one GitHub team, but the CODEOWNERs is more granular, giving ownership of specific packages/directories to individual team members, not the whole team. It would be nice to be able to enforce that specifically someone listed as a CODEOWNER (based on which files changed) is required to approve it

[leslie-qiwa]

I like to utilize code owners too for code reviewer, but current GitHub requires code owner to have write permission, which is showstopper for us. If this project can support this feature, it will be very useful.

[Andrei-Predoiu]

We already make use of CODEOWNERS, especially to enable fine grained ownership in large repos. We want to use policy bot Being able to reference CODEOWNERS would also make the transition much easier.

[aw185176]

Internally we have implemented a simple tool that allows writing OWNERS files in individual directories which are valid subsets of the policy-bot config file and merging them into a single policy-bot file. It seems to work pretty well and allows monorepo teams to self-serve access for their directories. If there is interest, we could look into open-sourcing.

[Andrei-Predoiu]

I think that would be very useful.

[papaslon]

@aw185176 We are lacking exactly that feature from policy-bot. Could you share your implementation here please?