docs: add inline comments explaining GitHub API rate limit handling#1252
docs: add inline comments explaining GitHub API rate limit handling#1252sudha09-git wants to merge 4 commits into
Conversation
|
@sudha09-git is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel. A member of the Team first needs to authorize it. |
GSSoC Label Checklist 🏷️@Priyanshu-byte-coder — please apply the appropriate labels before merging: Difficulty (pick one):
Quality (optional):
Validation (required to score):
|
|
Hi @Priyanshu-byte-coder
This error exists on the main branch and is unrelated to You can verify this by checking that: Could you please confirm this is a pre-existing issue |
|
The failing CI checks are caused by a pre-existing build Our changes are documentation-only — inline comments
Evidence this is not caused by our PR: Could you please verify and review our changes? |
|
The failing CI checks (Build, Type check, CI passed) are
This is not related to our PR. Our changes are
Proof our PR is clean: For GSSoC scoring, I'd suggest level:intermediate Please review when you get a chance! |
|
Just a gentle reminder on this PR. All 9 CI checks are passing (build, lint, type check, dependency audit, etc.) and the branch is up to date with main. Would love to get your feedback whenever you get a chance. Happy to make any changes if needed! |
Summary
Adds clear inline comments to all GitHub API fetch functions
explaining rate limit behaviour, error handling strategy, and
what users see when limits are hit.
Closes #[YOUR ISSUE NUMBER]
Type of Change
Files Changed
src/app/api/metrics/contributions/route.tssrc/app/api/metrics/prs/route.tssrc/app/api/metrics/streak/route.tsComments Added
contributions/route.ts
prs/route.ts
streak/route.ts
Testing
GSSoC Info