-
Notifications
You must be signed in to change notification settings - Fork 8
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
Automatically accept/reject beta/stable nominations #12
Comments
@spastorino I'm on this issue. Can you detail a bit what you mean by "what needs to be done to accept/reject a backport"? I was thinking to apply either the label Perhaps would you like something more like in this comment? |
👍, we should just fire that comment that also does the labelling adjustments. |
Btw there is no |
Also does triagebot have a proper code structure to create Zulip commands more easily now? |
ah good point, didn't know that. Are you referring to this documentation? In my opinion, not as clear as you wrote it here. Worth a small PR to clarify the wording?
mmm are you referring perhaps to issue #1 ? I can't tell, don't know what the plan was. I'm still wrapping my head and figuring out the actual workflow and API to/from Zulip, so I may be off, but by reading the code I think that commands have their own handler and adding a new handler is some copy&paste. |
I think @LeSeulArtichaut refers to our wg procedure document, I think there it's clear or at least should :). |
I believe this should be moved to rust-lang/triagebot – cc @Mark-Simulacrum |
I'd argue that it's still useful to at list keep an issue here. It's a todo list of the things we want to have. We could link this to an issue in rust-lang/triagebot maybe |
It would be cool if from the meeting we could say
@triagebot beta-accept #1111
or@triagebot beta-reject #1111
and have triagebot adding a comment on github doing what needs to be done to accept/reject a backport.The text was updated successfully, but these errors were encountered: