-
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
Workflow for tracking PRs assignment #1773
Workflow for tracking PRs assignment #1773
Conversation
578fa73
to
905ffee
Compare
905ffee
to
c1f5839
Compare
The job starts but GH returns an error, so I'll check what's happening 🙂 |
bd97ce8
to
d34bc21
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.
Okay, seems very close. There are still a couple open comments from me and a couple new ones.
I don't think anything here is blocking. If you can get to it now, good. Otherwise, a TODO will be okay.
just a bit more time, I'm working on resolving the open comments because they do make sense :) |
d34bc21
to
24b9b6a
Compare
7e8b4fa
to
c23d51d
Compare
I think all the comments are now resolved 👍 @rustbot ready |
General overview at: rust-lang#1753 - Added a new DB table with the fields to track how many PRs are assigned to a contributor - Initial DB table population with a one-off job, manually run.
41e29c8
to
a75633d
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.
A couple comments that I'd like for you to followup on in another PR, but let's land this.
for (idx, job) in jobs.into_iter().enumerate() { | ||
let ctx = ctx.clone(); | ||
task::spawn(async move { | ||
// Allow some spacing between starting jobs |
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.
Also not going to block on this, but seems like we could also just spawn one task that runs through all the jobs. Or just not worry about the delay (we can always add it later if it's a problem).
Implement a command to query from Zulip the number of assigned PRs. The command returns own Github username and assigned PRs to review. This command cannot be be used to check other peoples' work. Allows testing that the DB queries created in rust-lang#1773 are working correctly.
Implement a command to query from Zulip the number of assigned PRs. The command returns own Github username and assigned PRs to review. This command cannot be be used to check other peoples' work. Allows testing that the DB queries created in rust-lang#1773 are working correctly.
Implement a command to query from Zulip the number of assigned PRs. The command returns own Github username and assigned PRs to review. This command cannot be be used to check other peoples' work. Allows testing that the DB queries created in rust-lang#1773 are working correctly.
Implement a command to query from Zulip the number of assigned PRs. The command returns own Github username and assigned PRs to review. This command cannot be be used to check other peoples' work. Allows testing that the DB queries created in rust-lang#1773 are working correctly.
Implement a command to query from Zulip the number of assigned PRs. The command returns own Github username and assigned PRs to review. This command cannot be be used to check other peoples' work. Allows testing that the DB queries created in rust-lang#1773 are working correctly.
This is the third try 😅 to land part of the work on #1753 (pull requests tracking and balanced assignment for the Rust project contributors).
This patch implements:
r? @jackh726