use custom github token #578
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #578 +/- ##
=======================================
Coverage 75.08% 75.08%
=======================================
Files 55 55
Lines 3363 3363
=======================================
Hits 2525 2525
Misses 838 838
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
wakamex
force-pushed
the
wakamex/custom_github_token
branch
from
9064e20
to
35472ad
Compare
wakamex
force-pushed
the
wakamex/custom_github_token
branch
from
35472ad
to
1a69534
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
followed this recommendation: https://github.com/actions/setup-python/blob/v4/docs/advanced-usage.md#avoiding-rate-limit-issues
checked that the rate limit is actually being used using the linked example: actions/setup-python#443 (comment)