Skip to content
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

Rate limiting for repository cloning? #139

Closed
jpage-godaddy opened this issue Aug 31, 2023 · 1 comment · Fixed by #142
Closed

Rate limiting for repository cloning? #139

jpage-godaddy opened this issue Aug 31, 2023 · 1 comment · Fixed by #142
Labels
enhancement New feature or request

Comments

@jpage-godaddy
Copy link

Describe the solution you'd like
The ability to rate limit repository cloning operations

Describe alternatives you've considered
None

Additional context
I'm attempting to do a bulk operation on an org containing 176 repositories, but github is resetting the connection on all these clone operation attempts. It appears that the cloning is all being done in parallel, and my guess is that it's rate limiting operations. I see there's rate limiting on creating pull requests; perhaps applying a similar solution for the cloning operations would allow things to complete. Currently the operations are just failing without retries.

@jpage-godaddy jpage-godaddy added the enhancement New feature or request label Aug 31, 2023
cbrand added a commit to cbrand/git-xargs that referenced this issue Jan 8, 2024
Add rate limiting to github clone calls, avoiding issues
with github "permission denied" and EOF errors when cloning too many repositories in parallel.

Fixes gruntwork-io#139
@flinn
Copy link

flinn commented Mar 19, 2024

Bumping this, is there anything we can do towards helping to get this PR merged? I'm happy to alter the README files with the documentation if that'd help move this along.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants