Github API rate optimization #28
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
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.
Resolves #24
Modified the workflow file to use the user provided Github token instead of the automatically generated token. This drastically increases the API limit from 1000 to 5000.
Also modified the
github_handlinglogic:Like seen in this workflow https://github.com/oindrillac/time-to-merge-tool/actions/runs/3499848007/jobs/5861864319, we increased the API limit we started with to 5000 and as a result, we collected all PRs (250) in one go. Moving forward we should be able to collect ~600 PRs without getting rate limited.
Note: The model training step fails currently. Will investigate that here #23