You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the CODEOWNERS file is static, maybe with each commit to the main branch, we could have a job that makes sure that the people present in MAINTAINERS.md are also present in CODEOWNERS and if needed appends them?
Current situation
When an external contributor or a maintainer opens a PR, one needs to manually set
flatcar-maintainers
as reviewer.Impact
nebraska-maintainers
,flatcar-maintainers
, etc.)Ideal future situations
There is
CODEOWNERS
file to automatically set a GitHub team as a reviewer of the PR for a given repo.Implementation options
CODEOWNERS
file here: https://github.com/flatcar/.githubMAINTAINERS
file here: https://github.com/flatcar/Flatcar/blob/main/MAINTAINERS.md - we can decide to maintain both file separately (one is CNCF thing, the other one is a GitHub feature) or find a way to merge themflatcar-maintainers
should be set as reviewers of all PRs inside theFlatcar
organizationnebraska-maintainers
should be set as reviewers of all Nebraska PRsAdditional information
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#about-code-owners
The text was updated successfully, but these errors were encountered: