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
We kinda want it that way because we want to record who is responsible for specific parts of the repo, even/especially where they are not maintainers and dont have write access to the repo.
This both allows us to remember who is responsible and pings them in the event a PR is raised to change relevant code.
Not sure if its always been this way - but certainly now we are getting errors about the CODEOWNERS file not being valid
Surely there is a pretty valid use case for readonly CODEOWNERS - would this be possible ?
The text was updated successfully, but these errors were encountered:
We have a repo (https://github.com/envoyproxy/envoy) where there are quite a few CODEOWNERS and most do not have write permissions
We kinda want it that way because we want to record who is responsible for specific parts of the repo, even/especially where they are not maintainers and dont have write access to the repo.
This both allows us to remember who is responsible and pings them in the event a PR is raised to change relevant code.
Not sure if its always been this way - but certainly now we are getting errors about the
CODEOWNERS
file not being validSurely there is a pretty valid use case for readonly CODEOWNERS - would this be possible ?
The text was updated successfully, but these errors were encountered: