Give crater permissions to the triage team#2449
Give crater permissions to the triage team#2449cuviper wants to merge 1 commit intorust-lang:mainfrom
Conversation
|
Error: The feature Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip. |
|
#2002 was a previous proposal for this (but only for |
|
Well at least for beta crater runs, they don't need the ability to create new builds, |
|
I have a general negative sentiment on this, echoing @jieyouxu's concern. The bar for triage membership is low. I like the idea of it, but expanding permissions more than what is already allowed (which, tbh, I have thought a ton about) makes me weary. I think it's better to do one or more of the following:
|
|
I would personally continue to be hesitant about try permissions, but crater should be fairly safe. In principle you can still cause damage but we grant triage members permissions to do that anyway in other ways (and, honestly, I don't know how worried I am - the worst case is pretty benign here, I think). |
|
Another possible approach (without having to explicitly recharter triage team into two teams just yet, which I last understand was something that's in the works) could also be something like a |
We in the release team have appreciated the triage team's help with beta crater reports, especially @theemathas, and they may do more with the ability to queue crater jobs themselves.
r? @Mark-Simulacrum