fix: raise checkSuites/checkRuns page size to 100#33
Merged
Conversation
The hardcoded checkRuns(first: 25) silently dropped required status checks once a repo's CI suite grew past 25 runs, causing every commit to evaluate as StatusSuccess=false and blocking promotion. Bump both checkSuites and checkRuns to the GraphQL maximum of 100.
v2.0.3 relies on the deprecated GitHub Actions cache v1/v2 API, which now returns HTML error pages and breaks the Static Checks job. v3.0.1 uses actions/cache@v4. Pinned by commit SHA for supply-chain safety. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mrowek
approved these changes
May 19, 2026
2 tasks
gdud
added a commit
that referenced
this pull request
May 19, 2026
revert: roll checkSuites/checkRuns page sizes back to PR-#33 originals
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
GFM's GraphQL query hardcodes
checkRuns(first: 25)andcheckSuites(first: 20)(github/types.go). Once a repo's CI check suite grows past 25 check runs, GFM silently stops seeing the later runs — including requiredstatus_check_names— and every commit evaluates asStatusSuccess=false, blocking promotion.Real-world example
DocPlanner/noa-whisper-app run 26088940665 — promotion blocked with
THERE IS NO COMMITS PASSING EVALUATIONdespite all 6 requiredbuild_push_*checks being successful on the develop head.Of the 6 required
build_push-*checks, 3 sat at positions 26, 30 and 32 inside the suite — invisible to GFM.Change
Bump both page sizes to the GraphQL maximum of 100. Minimal, no behavior change for repos already under the old limits. Proper pagination would be the long-term fix; this unblocks current users immediately.
Test plan
go build ./...passes (verified locally)IS STATUS SUCCESS: ✔🤖 Generated with Claude Code