403 - API rate limit exceeded
- Dominant language
- Ruby
- Stars
- 48
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Every command, we call GitHub api to fetch files and so on. However this can cause issues like API rate limit.
Ways to solve this:
- Require some credentials so have a bigger limit ( not even sure if this would work )
- Cache the files locally somehow, and create a update method which would run once a day or when forced.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the GitHub API calls made by each command and identify where rate-limit failures occur. Review the proposed credentials and local-cache approaches before choosing a direction; the work is done when repeated commands no longer exceed the API limit and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, ruby
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100