-
Notifications
You must be signed in to change notification settings - Fork 40
fix: wrap github rest api access in an apiclient #530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAttention: Patch coverage is
@@ Coverage Diff @@
## main #530 +/- ##
==========================================
+ Coverage 78.89% 79.05% +0.16%
==========================================
Files 100 101 +1
Lines 23452 23689 +237
Branches 23452 23689 +237
==========================================
+ Hits 18503 18728 +225
- Misses 2741 2743 +2
- Partials 2208 2218 +10
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
d9e6160 to
b351e0e
Compare
AlexD10S
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super helpful fix, really appreciate you taking this on!
Applies some of the best practices from https://docs.github.com/en/rest/using-the-rest-api/best-practices-for-using-the-rest-api in an attempt to minimize errors caused by rate limiting of the Github API. When rate limiting occurs, errors will be returned with more detail information.
One can also now create a personal token on GitHub and specify locally via
GITHUB_TOKENif rate limiting occurs. The default limit is 60 per hour, so probably fine for most standard CLI usage.todos:
[sc-3686]