Repository navigation
gh-prs-merge: wait out a spent GitHub rate limit, and fail loudly past it (0.68.3) - #191
Merged
Merged
Conversation
…t it (0.68.3) A rate-limited `gh search prs` was reported as "skipped inaccessible or invalid scope", every scope warned, nothing was found, and the run printed an all-zero summary with exit 0: a sweep that did nothing, reported as a sweep with nothing to do. Gh now recognises GitHub's primary and secondary rate-limit refusals, reads the reset from `gh api rate_limit` (free, answers while everything else is refused), and waits it out when it is within --rate-wait (default 900s), then retries. A reset further off throws RateLimitError, which the sweep counts as FAILED for that scope, so the run exits 1 and says when to retry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan33 finding(s) HIGH/CRITICAL: 7 | MEDIUM: 12 | LOW: 14
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
A rate-limited
gh search prswas reported as "skipped inaccessible orinvalid scope", every scope warned, nothing was found, and the run printed an
all-zero summary with exit 0: a sweep that did nothing, reported as a sweep
with nothing to do.
Gh now recognises GitHub's primary and secondary rate-limit refusals, reads
the reset from
gh api rate_limit(free, answers while everything else isrefused), and waits it out when it is within --rate-wait (default 900s),
then retries. A reset further off throws RateLimitError, which the sweep
counts as FAILED for that scope, so the run exits 1 and says when to retry.
🤖 Generated with Claude Code