revert: roll checkSuites/checkRuns page sizes back to PR-#33 originals#35
Merged
Conversation
The 100-run bump in PR #33 raised the GraphQL query cost ~20× (worst case ~2,526 points/call against the 5,000/hour bucket). Revert just the inner connection; checkSuites stays at 100. Repos whose CI emits more than 25 runs in a single suite will need a different fix. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
gdud
changed the title
mrowek
approved these changes
May 19, 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
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.
Summary
Fully reverts the GraphQL query expansion from PR #33. Restores:
checkSuites(first: 100)→20checkRuns(first: 100)→25Why
PR #33's bump inflates GraphQL cost ~20×: the nested
checkSuites × checkRunsmultiplier went from20 × 25 = 500to100 × 100 = 10,000per commit, pushing one GFM call from ~131 to ~2,526 points against the 5,000/hour bucket.Known consequence
Repos whose CI emits more than 25 check runs in a single suite — including DocPlanner/noa-whisper-app — will go back to evaluating as
IS STATUS SUCCESS: ✖once:latestrolls forward. A follow-up that paginatescheckRunswould fix both repos cleanly without the cost penalty.Test plan
go build ./...passesv1.1.10, confirm release workflow publishes the new image🤖 Generated with Claude Code