Skip to content

feat: prevent github api rate limit exhaustion#4854

Open
basantnema31 wants to merge 1 commit into
JhaSourav07:mainfrom
basantnema31:fix-rate-limit-exhaustion
Open

feat: prevent github api rate limit exhaustion#4854
basantnema31 wants to merge 1 commit into
JhaSourav07:mainfrom
basantnema31:fix-rate-limit-exhaustion

Conversation

@basantnema31
Copy link
Copy Markdown

Resolves #4851. This PR implements a generic sync task queue to stagger GitHub API requests, and refactors existing components to use the centralized exponential backoff wrapper (fetchWithRetry) to prevent API quota exhaustion.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Jun 7, 2026

Someone is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added the status:blocked This PR is blocked due to a failing CI check. label Jun 7, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 7, 2026

🚨 Hey @basantnema31, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status:blocked This PR is blocked due to a failing CI check.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CRITICAL: Prevent GitHub API Rate Limit Exhaustion and Implement Exponential Backoff

1 participant