-
Notifications
You must be signed in to change notification settings - Fork 1
[FEAT repo-guard] - Integrate GitHub API Rate Limit Awareness #97
Copy link
Copy link
Open
Labels
backlogReady for sprint planning; triggers project additionReady for sprint planning; triggers project additionfeatureNew functionality or enhancementNew functionality or enhancementgithub-apiGitHub API integrations and rate-limitingGitHub API integrations and rate-limitingneeds-refinementNeeds scoping before implementationNeeds scoping before implementationreliabilitySystem stability, HA, and error handlingSystem stability, HA, and error handling
Metadata
Metadata
Assignees
Labels
backlogReady for sprint planning; triggers project additionReady for sprint planning; triggers project additionfeatureNew functionality or enhancementNew functionality or enhancementgithub-apiGitHub API integrations and rate-limitingGitHub API integrations and rate-limitingneeds-refinementNeeds scoping before implementationNeeds scoping before implementationreliabilitySystem stability, HA, and error handlingSystem stability, HA, and error handling
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Sprint Backlog
[FEAT repo-guard] - Integrate GitHub API Rate Limit Awareness
Description
The current implementation in
internal/githubuses a standard client without explicit rate limit handling. Implement a customhttp.RoundTripperor use a library that respects GitHub'sX-RateLimit-Resetheaders and implements exponential backoff.Labels
User Story
As a Developer I can ensure the operator doesn't fail due to GitHub rate limiting, so that sync operations remain robust during high-load.
Benefit
Prevents the operator from being throttled by GitHub during large sync operations or when managing many organizations.
Acceptance Criteria
http.RoundTripperor library is integrated.X-RateLimit-Resetheaders are respected.