-
Notifications
You must be signed in to change notification settings - Fork 77
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
@rustbot ready
alias to switch to waiting on review?
#1339
Comments
I really want |
I at least only regularly look at waiting-on-review; any other state is likely to get entirely lost. I think it's reasonable to ask the reviewer to take point at either reassigning or identifying and pursuing that help. |
Duplicate of #553. |
I think this is a great idea. I find maintaining these labels pretty tedious. I'd be happy to help mentor someone here. I'm going to leave some notes. |
@rustbot claim |
I would also like the bot to pay attention to GH reviews. Here is what I would suggest:
The question is how easy/hard this will be to do =) |
I'm thinking about the first part first -- the GH review with "changes requested". My guess is that this trigger a notification? If so, I guess we want to edit this function: triagebot/src/handlers/notification.rs Line 16 in 67f108c
|
After a first analysis, if we would want to support simpler single word abbreviations, from the example above I also wonder if it would be better for the GH review section to be its own issue since the two are different in scope 🤔 |
@Llandy3d that makes sense to me, yes |
Just filed #1373 |
No, the handlers are per-function, that is, for this feature it likely makes sense to either:
It's likely that the github review is not too well integrated into our processing right now, so that may need some modifications to the github.rs file to parse the webhook events (at least adding some fields). |
I think it has been fixed by #1381... |
I would love to see simpler invocations that we can recommend to PR authors, that handle switching the various "waiting on" labels.
Also, could we define sets of mutually exclusive labels, such as the various "waiting on" labels, so that you only have to add one and the bot will automatically remove others?
The text was updated successfully, but these errors were encountered: