v0.0.15
Description
This release brings git-xargs functionality in line with GitHub's API recommendations for integrators regarding rate limits.. This means that git-xargs now respects GitHub API rate limits and reacts to related header values that GitHub may send when rate limiting a client, in order to intelligently slow down and stagger open pull request API calls.
To further assist in running rate-limit-compliant jobs, git-xargs now features two separate processing channels for two types of work:
- Work that can be performed in parallel as quickly as possible
- Work that needs to be treated sensitively in observance of rate limits (such as making open pull request API calls to GitHub)
Work that can be performed in parallel is still done as quickly as possible. Pull requests API calls that are generated by a git-xargs run are now staggered and opened serially at the end of a run. In addition, open pull request API calls that fail due to rate limiting are now automatically retried, with configurable back-off behavior.
In addition, new flags have been added to assist with configuring your git-xargs jobs so that they do not trip GitHub rate limits.
Please see the new section of the git-xargs README titled "Rate Limiting" for more information.