Repository navigation
Fix GraphQL RESOURCE_LIMITS_EXCEEDED errors due to GitHub API limits #1086 - #1089
Merged
bluekeyes merged 2 commits intoOct 28, 2025
Merged
Conversation
Generate changelog in
|
✅ Successfully generated changelog entry!Need to regenerate?Simply interact with the changelog bot comment again to regenerate these entries. 📋Changelog Preview🐛 Fixes
|
bluekeyes
approved these changes
Oct 28, 2025
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.
Before this PR
Over the past few days, we’ve encountered an issue with the policy-bot where reviewers are not being automatically assigned to pull requests (PRs) when they are created or opened for review.
Because of the following error:
failed to select reviewers: failed to list repository collaborators: failed to load repository collaborators: Resource limits for this query exceededAfter this PR
That people are automatically assigned by policy-bot when PRs are created
More context
See for more information #1086
Possible downsides?
Possibility that GraphQL request limit is reached because the amount of calls can possibly double based on the amount of collaborators in an environment. Brought up by @bluekeyes in context of #1030