-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
doc: adding labels doesn't require commit rights #92941
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
Conversation
As of [RFC 39][1], package maintainers are members of the NixOS github organization who don't have commit rights. However, they *do* have what GitHub calls [Triage rights][2], which means that package maintainers are able to add labels to PRs. The documentation should make this clear. I don't know the right way to phrase this in the docs, but the current text of "Requires commit rights" is definitely incorrect. [1]: https://discourse.nixos.org/t/join-the-package-maintainer-team/3751 [2]: https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level
@@ -49,7 +49,7 @@ | |||
<itemizedlist> | |||
<listitem> | |||
<para> | |||
Add labels to the pull request. (Requires commit rights) | |||
Add labels to the pull request. (Requires maintainer rights) |
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.
s/maintainer/triage/
The maintainer privilege set is different from the triage privilege set on GitHub (see: https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level).
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.
That might be the case, but I think the language of github permissions is too low-level for this doc. Users shouldn’t need to understand the low level github permissions system, and how that maps on to teams in the NixOS org. The important question is, “what governs whether a user can add labels to PRs in the NixOS org?”, in language the user understands and can take action on.
I think it might be as simple as “all package maintainers” or “all NixOS org members” (“but who gets to be an org member?” is the natural question arising here)
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.
Why not both? That way, we can keep a high level user facing explanation ("NixOS org terminology"), and make it clear to people who know about GitHub rights exactly what's going on. 😃
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 nixpkgs manual is already way too long and unfocused. I don’t want to add to that.
We should maybe document the GitHub permissions thing somewhere, but this isn’t the doc section to do it.
Thought: now that OfBorg automatically adds labels, do we even need documentation encouraging reviewers to do it? Could we just get rid of those lines? |
I marked this as stale due to inactivity. → More info |
I marked this as stale due to inactivity. → More info |
Motivation for this change
As of RFC 39, package maintainers are members of the NixOS github
organization who don't have commit rights. However, they do have what
GitHub calls Triage rights, which means that package maintainers
are able to add labels to PRs. The documentation should make this
clear.
I don't know the right way to phrase this in the docs, but the current
text of "Requires commit rights" is definitely incorrect.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)