Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upReview GitHub organization teams & permission #10290
Comments
|
@larsbergstrom Good idea! If you provide me with a list of the only people who need Admin perms, I'll do the permissions changes. Current members of the "Developers" team with legacy admin perms:
Current members of the Core team, with legacy admin perms:
|
|
Move me to the Write group, please. |
|
I'd like to edit |
|
Admin perms should be: Everybody else should just have Write (which I believe gives the ability to change assignee & labels). |
|
Related to this is the list of owners at https://github.com/orgs/servo/people, which I think should be just: For convenience, https://help.github.com/articles/repository-permission-levels-for-an-organization/ is the repo permission levels, which does indicate that Write is sufficient for changing assignee & labels. |
|
Added a "check the repo's permissions" section to https://github.com/servo/servo/wiki/Adding-a-repo-to-Homu documenting a guess at the correct perms to hand out when setting up new stuff, based on how Servo/Servo is. |
|
The last remaining thing is "set up branch protection". Branch protecting every repo in the org is not feasible right now because Homu is not working on all repos. Additionally, it's unclear whether we want to add Homu to every repo that's ever been forked to the org. Superseding this with #17626 for next steps. Please re-open if there's additional tasks here not captured by #17626. |
Right now, as a holdover from the VERY old days of GitHub, nearly all Servo reviewers plus some random others have
Adminpermissions. There are also two security groups. I'd like to:Writecc @edunham