-
Notifications
You must be signed in to change notification settings - Fork 78
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 work queue tracking in triagebot DB #1879
Add work queue tracking in triagebot DB #1879
Conversation
Signed-off-by: apiraino <[email protected]>
Add checks in multiple points when identifying or finding an assignee. Filter out team members currently not having capacity, return messages instructing what to do in case the assignment is rejected. Signed-off-by: apiraino <[email protected]>
d917ccf
to
886116c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just double checking, we don't have to do anything fancy with the db before merging, right
Correct, the DB schema should be already ready to process the review assignments. The case of |
This check is specifically used when assigning from the Github web UI Signed-off-by: apiraino <[email protected]>
886116c
to
5afc243
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We talked a bit in DMs - there are certainly things we could do to minimize the risk (bubble up potential db failures instead of expect
ing, land the db changes separately, fallbacking to existing non-filtering if db failture), but these aren't needed.
Let's land this.
Rebase of #1786
This implements the new way of assigning pull requests reviews (designed in #1753). When this PR is merged, PRs in
rust-lang/rust
will be assigned based on user preferences. These can be queried from Zulip (see docs).If no preferences are set, PRs will be just assigned (like always).
There are multiple points where PRs are assigned (via comment or using the GH UI), I've tried to cover all cases, took some time to test them all. The amount of changes reflect that it is not so easy to catch all spots where this happens. I wish I could make a smaller patch but I think this is an all-or-nothing situation where all cases should be handled at once.
Also modified the zulip triagebot command
work show
to return the # work queue capacity set by the user. This is helpful in case a PR assignment is rejected. A PR to update the documentation will follow-up after merge of this.If a PR assignment is rejected we will return a message with some context. Examples:
Failed PR assignment to a user:
Failed self-assignment:
r? @jackh726