You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -451,7 +451,14 @@ Yes — if private contributions visibility is enabled in your GitHub settings.
451
451
452
452
### Are there GitHub API rate limits?
453
453
454
-
Yes, but CommitPulse minimizes API usage using caching and optimized GraphQL queries.
454
+
Yes. CommitPulse minimizes API usage via caching and optimized GraphQL queries, but if you hit the GitHub API rate limit (typically 5,000 requests per hour for authenticated users), you might see errors or missing data.
455
+
456
+
#### Troubleshooting Rate Limit Errors
457
+
458
+
1.**Wait it out:** Rate limits automatically reset every hour.
459
+
2.**Provide your own PAT:** If self-hosting, ensure you've provided a valid `GITHUB_TOKEN` in `.env.local` to get the authenticated rate limit.
460
+
3.**Avoid aggressive bypassing:** Avoid repeatedly using the `&refresh=true` parameter, which bypasses the cache and consumes API quota on every load.
461
+
4.**Check GitHub API Status:** Occasionally, GitHub's GraphQL API itself experiences degradation. Check [githubstatus.com](https://www.githubstatus.com/).
0 commit comments