Adding support to handle more than 100 repos per user or organization #7
+39
−9
Conversation
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
1 participant
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.
While using the NPM repo at work to automat pulls and checkouts of our source trees, we ran into an issue where the Github API is limiting the requests to 100 repos per page. As a result the query for 1000 results per page only results in the first 100 repos.
The following code adds a recursive function that walks the pages until an empty result [] or an error occurs. In practice I've tested this with an account with 118 repos. I don't have an account with >200 repos, so I have not yet tested page 3.
Integration tests require adding >100 repos to github and have obvious cleanup problems, so I have not supplied any.