-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
docs: remove outdated references to CODEOWNERS #369505
Conversation
As of b01ca00 (CODEOWNERS: Switch to alternate mechanism, 2024-10-10) and NixOS#336261, this repository doesn't use the GitHub CODEOWNERS file, but instead has its own similar mechanism. Remove and update references to the CODEOWNERS file in various documentation files.
For critical packages, this convention needs to be negotiated with the | ||
maintainer. A critical package is one that causes mass-rebuild, or where an | ||
author is listed in the [`CODEOWNERS`](../.github/CODEOWNERS) file. | ||
author is listed in the [`OWNERS`](../ci/OWNERS) file. |
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 feel like this whole paragraph has been wrong for a while. OWNERS
is for things that don't have a meta.maintainers
as well, that may or may not be critical.
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.
But I don't want this to be a blocking comment. We can rewrite it in another PR.
Co-authored-by: Fernando Rodrigues <[email protected]>
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!
As of b01ca00 (CODEOWNERS: Switch to alternate mechanism, 2024-10-10) and #336261, this repository doesn't use the GitHub CODEOWNERS file, but instead has its own similar mechanism. Remove and update references to the CODEOWNERS file in various documentation files.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.