Conversation
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow intended to automatically assign reviewers to PRs based on labels and a simple load-balancing heuristic.
Changes:
- Introduces
.github/workflows/auto-assign-reviewers.ymlto select and request reviewers when PRs are opened/updated/labeled. - Implements label-based eligibility (
assign-for-review) and weighting (size-*,priority-high) to prioritize larger/higher priority PRs. - Tracks current reviewer “load” across open PRs to pick the least-loaded candidates.
… Usr/sogh/prreviewbot
…api-builder into Usr/sogh/prreviewbot
|
|
||
| --- | ||
|
|
||
| ## Team Communication |
There was a problem hiding this comment.
Team Communication need not be checked in
|
|
||
| | # | Item | Owner | Status | | ||
| |---|---|---|---| | ||
| | 1 | **Decide on Aniruddh's inclusion** — remove to reduce his load, or keep as equal | Team | Pending | |
There was a problem hiding this comment.
Keep me included in the reviewers section, this way I can help distribute the load of reviewing as per the bot.
|
|
||
| --- | ||
|
|
||
| ## Open Items |
There was a problem hiding this comment.
This Open Items should not be checked in
|
|
||
| --- | ||
|
|
||
| ## Changelog |
There was a problem hiding this comment.
ChangeLog neednot be checked in
| pull_request_target: | ||
| types: [opened, reopened, labeled] | ||
|
|
||
| # TODO: Remove before merging — temporary trigger for testing from PR branch. |
There was a problem hiding this comment.
This TO DO comment needs to be removed. Even if I approve now, and this merges, it will not trigger the workflow even if folks add the label to their PRs.
Aniruddh25
left a comment
There was a problem hiding this comment.
This workflow is getting triggered only on pushing to the Usr/sogh/prreviewbot branch, so none of us could test it while you were away,
Better would have been to merge it in without that condition so it could become LIVE.
Why make this change?
Automate PR reviewer assignment to distribute review workload evenly across the team instead of relying on manual assignment or CODEOWNERS (which adds all owners).
What is this change?
Adds auto-assign-reviewers.yml, a label-driven GitHub Actions workflow that assigns exactly 2 reviewers per PR using load-balanced selection.
High-level workflow steps-
How is this tested?