fix api rate limit errors#18
Merged
Mattraks merged 5 commits intoMattraks:mainfrom Dec 18, 2023
Merged
Conversation
Contributor
Author
|
@Mattraks I noticed that this action skips over logs where the action was deleted or renamed. Is that by design, a limitation of the API, or an issue that can be fixed? |
Contributor
Author
|
thanks @Mattraks! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
With a GitHub account that has an active paid subscription, I recently got
in this run.
With node16, this run failed with:
https://github.com/octokit/octokit.js/#fetch-missing said to bump to at least node18.
So, after bumping to node20, this run finished successfully, though it doesn't appear that an API rate limit was hit.