Repository navigation
ci: add Needs review status to the board sweep - #651
Merged
Merged
Conversation
A ready PR waiting on a reviewer now gets Needs review instead of In Progress, so the review queue is visible on its own. This covers a non-draft PR with no review yet, and one whose changes-requested reviewers have all been asked to review again. Drafts and PRs with an outstanding changes-requested verdict stay In Progress. Issues follow their furthest linked PR, as before.
navareamol
requested review from
LeeroyHannigan,
amrith,
c33howard,
jcshepherd,
pdf-amzn,
robinnsc and
yesyayen
as code owners
October 29, 2026 07:55
LeeroyHannigan
approved these changes
Oct 29, 2026
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
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.
Summary
Adds a Needs review status to the Roadmap board sweep, between In Progress and Review. Today a ready PR that nobody has reviewed sits in In Progress, mixed in with drafts. This makes the review queue its own column.
How a PR moves
Todo -> In Progress -> Needs review -> Review -> Done
Issues are unchanged in logic: an issue takes the furthest status of its trusted open linked PRs, so an issue whose PR waits on a reviewer is now in Needs review.
Use cases
Failure and edge cases
Testing