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 www.rust-lang.org repository under automation #1271
base: master
Are you sure you want to change the base?
Conversation
I should probably have admin. I think the pontoon accounts are still used but it's been a while since I've poked at that integration |
I know that it is currently only you, but perhaps we should then make it |
1de4298
to
4b08419
Compare
Ok, changed. Just out of curiosity, why is |
Perhaps we should note why @Manishearth needs admin rights so we can review this in the future. This also makes me think that it would be nice to have a tool that collects all individuals with individual access to repos and generates a report that automatically gets posted somewhere every 3ish months for review. |
(Marking as draft now, since |
I think the way we prefer to handle this is by creating a new team as a subteam which reflects these permissions. |
@rylev it's for things like Pontoon and Heroku setup. Third party integrations, especially experimenting with them, often needs admin to go smoothly. |
Co-authored-by: Eric Huss <eric@huss.org>
Repo: https://github.com/rust-lang/www.rust-lang.org
So, there are a few things going on here. I'm not sure about the
rust-pontoon-trial
andrust-lang-owner
accounts.Also, I'm not sure how are the individual
deploy
andtry
branches used and what should be their branch protections.CC @dtolnay @Manishearth
Extracted from GH: