Problem
The current implementation fetches repository statistics directly from the GitHub API on every request. This may lead to GitHub API rate limit issues when the application receives higher traffic.
Proposed Solution
- Add caching layer for repository statistics.
- Refresh cached data periodically.
- Display cached values when API requests fail.
Benefits
- Better performance
- Reduced API requests
- Improved reliability during rate limiting
Related PR
#852
Problem
The current implementation fetches repository statistics directly from the GitHub API on every request. This may lead to GitHub API rate limit issues when the application receives higher traffic.
Proposed Solution
Benefits
Related PR
#852