GitHub Community
Nested CODEOWNERS #21809
-
|
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. 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
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
Hello @chrislloyd, |
Beta Was this translation helpful? Give feedback.
-
|
Future viewers may want to check out https://github.com/marketplace/actions/codeowners-bot |
Beta Was this translation helpful? Give feedback.
-
|
you can also take a look at https://github.com/gagoar/codeowners-generator |
Beta Was this translation helpful? Give feedback.
-
|
Hi @MChevy422, any news regarding support for nested CODEOWNERS files in the repo? It's two years since it was added into the feature requests list, it would be great to know if this won't ever be implemented or if is planned to be done at some point :). This would be really helpful in big repos to improve readability and maintainability of the code owners file. |
Beta Was this translation helpful? Give feedback.
-
|
re: https://github.com/marketplace/actions/codeowners-bot This is interesting but does not address a very common use case: merge conflicts with codeowners files with different contents on different CI/CD related branches (ie release, develop). At the moment we are limited to 3 non-conflicting CODEOWNERS files, one in .github, one in root, and one in docs/ Ideally we should be able to have an arbitrary amount of CODEOWNERS files ( ie .github/release/CODEOWNERS, .github/develop/CODEOWNERS). |
Beta Was this translation helpful? Give feedback.
-
|
+1 on this. For mono-repos this is a critical feature |
Beta Was this translation helpful? Give feedback.
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
MChevy422