Use GraphQL API#81
Draft
sislr wants to merge 1 commit into
Draft
Conversation
sislr
force-pushed
the
feature/graphql-api
branch
from
July 16, 2026 07:22
8902b75 to
ba21c1a
Compare
Member
Author
|
Testing this change locally for the moment and will then decide |
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
1 participant
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.
Problem: The extension hits GitHub's rate limit (403). Each poll fires ~7 + 2N REST search calls plus one /requested_reviewers request per PR, and we poll every minute — against the Search API's 30 requests/minute cap.
Solution: ~7 + 2N REST searches → 2 GraphQL requests per poll (a viewer lookup + one batched query), drawing from GraphQL's 5,000-points/hr budget instead of the 30/min search cap.