rfcbot-rs
rfcbot-rs copied to clipboard
rust-lang
Coordinates asynchronous decision making on Rust repositories. Status of tracked issues and PRs can be viewed at https://rfcbot.rs.
When I go to my personal dashboard, I'd like to see: - all PRs assigned to me - PRs that have gone w/o a comment in a certain amount of...
I'd like to be able to see not only the FCP motions to which I have yet to respond, but all active FCP motions for teams that I belong to,...
I believe rfcbot requires a `T-foo` tag, but if one's missing it could perhaps leave a comment saying so if someone starts an FCP with `@rfcbot fcp merge`
This is an initial commit to allow us to track which teams are involved in an FCP directly. This will may be needed in order to support smarter rfcbot behavior...
Currently rfcbot assumes all teams have the same threshold for when they reached consensus in an FCP: a strict majority, with at most 2 votes outstanding. In https://github.com/rust-lang/rust/issues/114986 the suggestion...
I found it really helpful when @dtolnay assigned me to https://github.com/rust-lang/rust/pull/115333 after I proposed fcp merge. This caused the PR notifications to show up in my "assigned" category and reinforced...
When an FCP finishes, the PR should go back into the reviewer's queue. However, for reviewers that manage their queue via github notifications or emails, this is far from clear...
Closes #293 . Both the opsem and lang teams felt that a simple majority, which in their case meant 3/5 team members, did not sufficiently reflect team consensus. This PR...
https://rfcbot.rs/ currently lists all FCPs that are still waiting for some team member approval so that the 10-day period can start. It would also be quite useful, I think, to...
When looking at historic FCPs ([example](https://github.com/rust-lang/rust/issues/48556#issuecomment-377723917)), it can be hard to figure out which teams were involved -- labels change all the time, so reconstructing the set of labels at...