ci: auto-assign a round-robin reviewer to new PRs#1760
Open
notgitika wants to merge 2 commits into
Open
Conversation
New PRs currently land in a shared queue with no named reviewer, so many sit unreviewed. This adds a workflow that requests one reviewer per new non-draft PR, round-robin over the existing AUTHORIZED_USERS roster (pr.number % pool), skipping PRs that already have a reviewer and never assigning the author. Follows the metadata-only pull_request_target pattern from pr-size.yml (needed so fork PRs can be assigned; safe because no PR code is checked out). Also adds a dry-run-by-default sweep script to assign reviewers to the existing backlog of unreviewed PRs.
github-actions
Bot
added
size/m
agentcore-devx-automation
Bot
added
the
claude-security-reviewing
Contributor
Package TarballHow to installgh release download pr-1760-tarball --repo aws/agentcore-cli --pattern "*.tgz" --dir /tmp/pr-tarball
npm install -g /tmp/pr-tarball/aws-agentcore-0.24.1.tgz |
Contributor
|
Claude Security Review: no high-confidence findings. (run) |
agentcore-devx-automation
Bot
removed
the
claude-security-reviewing
Contributor
Coverage Report
|
agentcore-devx-automation
Bot
added
the
claude-security-reviewing
Contributor
|
Claude Security Review: no high-confidence findings. (run) |
agentcore-devx-automation
Bot
removed
the
claude-security-reviewing
Hweinstock
reviewed
Jul 15, 2026
| @@ -0,0 +1,67 @@ | |||
| name: Assign PR Reviewer (round-robin) | |||
|
|
|||
| # Auto-assigns one reviewer to each new external PR, so community contributions | |||
Contributor
There was a problem hiding this comment.
Are there ideas in the comment here that we don't feel like are expressed clearly below in the implementation, if so why?
|
|
||
| // Stateless round-robin: PR number modulo pool size. Deterministic, no state | ||
| // file to keep in sync, and spreads load evenly as PR numbers increase. | ||
| const reviewer = pool[pr.number % pool.length]; |
| @@ -0,0 +1,67 @@ | |||
| name: Assign PR Reviewer (round-robin) | |||
Contributor
There was a problem hiding this comment.
broader q: is there any prior art you were able to find in your research? Does the strands team have anything?
I'm wondering about what happens if the assigned reviewer isn't available (PTO), or busy with another project. Also is there a clear path to overriding the assigned reviewer here if I want someone else to review?
Also wondering if a no-code solution might be simpler. For example, on-call responsible for external PR review for their week, or we delegate these are part of sprint work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
External PRs currently land in a shared queue with no named reviewer, so many sit unreviewed.
This PR adds a workflow that requests one reviewer per new non-draft PR when the PR author is not in the existing
AUTHORIZED_USERSroster. Reviewers are selected round-robin from that roster. PRs authored by someone inAUTHORIZED_USERSare left unassigned, and PRs that already have a reviewer are skipped.Safety: follows the metadata-only
pull_request_targetpattern frompr-size.yml(needed so fork PRs can be assigned; safe because no PR code is checked out or executed, only PR metadata is read and a reviewer requested).Future work: We can look into adding a CODEOWNERS file and then editing this workflow to make sure the right folks with context are tagged in PRs. I will also be looking into a simple starter system to assignees to get pinged on our slack