fix: cap GitLab contribution pagination (#1247)#1326
Conversation
|
@mittalsonal 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):
|
|
Kind request for GSSoC labels when reviewed: gssoc:approved, one level:* label, and ype:bug if it fits the repo’s scoring rubric. Thanks! |
|
Verification completed locally:
This PR intentionally keeps the change small and limited to the GitLab contributions pagination guard in |
228adf1
into
Priyanshu-byte-coder:main
|
🎉 Merged! Thanks for contributing to DevTrack. If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers. Keep an eye on open issues for your next contribution! |
Description\n- add a GitLab pagination safety cap in etchGitLabContributions()\n- stop malformed or repeated x-next-page values from keeping the request alive indefinitely\n- align the GitLab fetch guard with the existing bounded GitHub pagination pattern in the same route\n\n## Related Issue\n- Closes #1247\n\n## Checklist\n- [x] one-file fix\n- [x] git diff --check passes\n- [x] change is scoped to the GitLab contributions pagination loop only\n\n## Pillar\n- Open Source\n