gruntwork-io / gruntwork-io/git-xargs

New Parameter: wait time between pushes

Open
#110 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
1.1k
Forks
75
PR merge metrics
No merged PRs in 30d

Description

As I understand, git-xargs works for following way:
1. clones all passed repos
2. runs the command on all repos
3. pushes all changed repos to remote
4. opens all PRs

Our main branches require successful workflow-runs for merging. So I should use the --no-skip-ci option. But this would mean, that I start over hundred workflow-runs in a few seconds. This would block our runners for hours.

Instead I don't use the --no-skip-ci option and run a script afterwards which does an empty commit to each repository to trigger the workflow and wait some time.

**Describe the solution you'd like**
My prefered solution would be, if git-xargs runs the steps 1-4 per repo and then waits some configurable time before repeating steps 1-4 with the next repository.
This way I the wait time will be used to wait for runners to complete and for the rate limit to go down.
In my case most of the execution time is wasted for waiting. This way, it could be decreased.

**Describe alternatives you've considered**
Additional parameter to configure wait time between pushes.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.