utils/github/api: print more info on rate limits #20879
Merged
+6
−3
Conversation
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
There was a problem hiding this comment.
Pull Request Overview
This PR enhances GitHub API rate limit error messages by including additional information about the specific rate limit that was exceeded. The change improves debugging by showing the resource type and limit value when rate limits are hit.
- Updated
RateLimitExceededErrorto accept and display resource type and limit information - Modified the error message format to include resource-specific rate limit details
- Changed the constructor signature to use keyword arguments for better clarity
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Bo98
force-pushed
the
api-ratelimit-message
branch
from
c0128fb to
c04010e
Compare
Bo98
force-pushed
the
api-ratelimit-message
branch
from
c04010e to
0566b57
Compare
p-linnane
approved these changes
Oct 15, 2025
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.
GitHub rate limits aren't quite as simple as there being one limit for everyone. The limit varies depending on what type of token it is, whether you are even authenticated and what type of resource you are hitting. It's probably worthwhile outputting all of that.
I've not really tested this since I'd need to spam requests to get my IP rate limited.