-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GitHub CODEOWNERS file #5054
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
PR Check ResultsEcosystem✅ ecosystem check detected no changes. BenchmarkLinux
Windows
|
.github/CODEOWNERS
Outdated
/crates/ruff/src/rules/pylint/ | ||
/crates/ruff/src/rules/pyupgrade/ | ||
/crates/ruff/src/rules/ruff/ | ||
/crates/ruff/src/rules/tryceratops/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the process by which this is kept up-to-date? (E.g., if we add new directories, or rename, or remove?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm seeing a message on top of the file saying "This CODEOWNERS file is valid". I believe GitHub checks it against the repository. Let me do a quick commit and verify.
If not, we could use https://github.com/mszostok/codeowners-validator although it seems to be not maintained anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I think GitHub seems to be only checking for syntax. Also, the codeowners-validator
is giving me segmentation fault :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The path could contain patterns as well but if we don't use patterns then we could do a manual check on just the existence of path in CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case, I might vote to only include the folders for which we're enforcing rules, and add them as we go. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, makes sense. Do you have any other folders in mind? (I'll comment out the rest before merging)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Na, that's fine, I may add some later :)
Also: it may be easier just to remove rather than comment-out, since they'll probably get stale if we don't maintain them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Summary
Add GitHub CODEOWNERS file.
Initiating this, we can discuss and iterate further.
https://help.github.com/articles/about-codeowners/
Test Plan
Look out for review requests :)