I work in a monolithic Git repo - there are thousands of engineers making commits every day. Singular files that every engineer can update and that need frequent updating are a problem. Files like this end up having lots of merge conflicts and end up being very long. CODEOWNERS is currently that kind of file, which makes the whole feature almost useless to us. I’m hesitant to introduce it.

In the documentation it says that they “A CODEOWNERS file uses a pattern that follows the same rules used in gitignore files”. I think taking the .gitignore inspiration one step further - and allowing CODEOWNERS to be nested, would solve this problem. There are of course difficulties in  doing so (“which CODEOWNERS takes precedence?”), but I would solve these by following the same conventions as git.

CODEOWNERS is generally more useful to large teams, and by allowing them to be nested it would be even more useful to the largest of teams. Thanks!

Hello @chrislloyd

Thank you for your feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.

Once again, thank you for your input!

Greatly appreciated