Repository navigation
fix(pulls): re-read a lazily unknown mergeability once - #149
Merged
Merged
Conversation
GitHub computes mergeability lazily, so the first pulls/N read often returns mergeable null or state unknown for a mergeable pull request. After the main pass, re-read such green non-draft rows once (pulls/N only, no sleep, no loop, outside the --limit budget, never after a rate limit) and judge the verdict on the re-read. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
… trigger Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
GitHub computes pull request mergeability lazily: the first
pulls/Nread often returnsmergeable: null/unknown, so a green, mergeable PR was reportedblocked (unknown)and a single run under-reportedreadyPRs (observed on wstein/regrip#25-29: first run 3 blocked, second run 5 ready).pulls/Nonly), at the end so the other reads gave GitHub time; no sleep, no loop, no second re-read--limit; none after a rate-limit stop; a failed re-read keeps the rowblocked/unknownand is reported as an error (exit 1)docs/pulls.mdand CLI help amended; no schema changeBlocker
Draft until the independent Opus review of the exact head is CLEAR and CI is green.
🤖 Generated with Claude Code