Skip to content

CI - BUGFIX - Count a reviewer as named once they have reviewed - #409

Open
logan-nc wants to merge 2 commits into
developfrom
bugfix/pr-conventions-reviewer-check
Open

CI - BUGFIX - Count a reviewer as named once they have reviewed#409
logan-nc wants to merge 2 commits into
developfrom
bugfix/pr-conventions-reviewer-check

Conversation

@logan-nc

Copy link
Copy Markdown
Collaborator

Release note

  • Audience: developers
  • Numerical impact: none
  • Migration: none

The PR Conventions bot claimed a pull request was "missing a reviewer" on pull requests that had one. It checked only requested_reviewers, which holds pending review requests — GitHub drops a reviewer from that list the moment they submit a review. The check therefore stayed quiet while nobody had reviewed and fired once someone did.

Regression report

Not applicable: this changes .github/ only, no files under src/.

Notes for reviewers

A reviewer counts as named whether or not they have acted — assignment alone is sufficient, exactly as before. The added listReviews call is not a requirement that someone review; it only remembers an assignment GitHub has already cleared.

Timeline on #391, which is the reported case:

When Event requested_reviewers
08-15 18:33:56 krystophny review_requested [krystophny] — quiet
08-17 21:43:14 krystophny approved [] — GitHub auto-clears
08-18 19:07:11 workflow re-ran on a push [] — posts the nag

No review_request_removed event appears in the timeline, so nobody unassigned them; the clearing was GitHub's own on review submission.

Replaying old vs new against all 25 open pull requests:

Self-reviews are excluded (r.user.login !== pr.user.login) so an author commenting on their own pull request does not satisfy the check. Any review state counts — APPROVED, CHANGES_REQUESTED, or COMMENTED — since the check is about a human being named, not about approval.

The metadata job read only requested_reviewers, which holds pending review
requests. GitHub removes a reviewer from that list as soon as they submit a
review, so the check went quiet while nobody had reviewed and fired once
somebody did -- nagging precisely the pull requests furthest along.

Treat a submitted review from anyone other than the author as evidence that a
reviewer was named. Assignment alone still suffices; the reviewer never has to
act. Verified against all open pull requests: silences #390, #391, #392, #407,
leaves every pending-request PR untouched, and still nags the nine with nobody
named.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dh1NCejnd3fYMmcRKoQRcG
@github-actions github-actions Bot added the bugfix Something was wrong and now is not label Aug 19, 2026
@logan-nc
logan-nc marked this pull request as draft August 19, 2026 12:04
Focus values were all src/ modules, so a workflow or conventions change had
nobody obvious to review it and landed unassigned -- which is how the reviewer
nag this branch fixes went unowned. Add the CI and Repo Areas from naming.md
to the two maintainers who work on repository plumbing, and say in the prose
that Focus names Areas outside src/ too.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dh1NCejnd3fYMmcRKoQRcG
@logan-nc
logan-nc requested a review from matt-pharr August 19, 2026 12:24
@logan-nc
logan-nc marked this pull request as ready for review August 19, 2026 12:24
@logan-nc

Copy link
Copy Markdown
Collaborator Author

@matt-pharr this one is a very small diff - quick review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Something was wrong and now is not

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants