v0.1.7

What's Changed

• Bump go-git to v5.6.1 by @zackproser in #123

Full Changelog: v0.1.6...v0.1.7

v0.1.6

What's Changed

• Bump CircleCI Go to version 1.18 by @zackproser in #122

Full Changelog: v0.1.5...v0.1.6

v0.1.5

What's Changed

• Added FUNDING.yml by @eak12913 in #111
• Clean up temporary clone paths by default by @zackproser in #113
• Refactor contexts in CircleCI config by @eak12913 in #117

New Contributors

• @eak12913 made their first contribution in #111

Full Changelog: v0.1.3...v0.1.5

v0.1.3

Modules affected

Description

• Correct readme referencing incorrect flag name: --max-pull-request-retries -> --max-pr-retries

Special thanks

Special thanks to the following users for their contribution!

• @jdimatteo

Related links

• #107

v0.1.2

Modules affected

Description

• Use go install in instructions instead of go get
• Update Installation instructions header text
• Update codeowners
• Implement support for requesting reviewers

Special thanks

Special thanks to the following users for their contribution!

• @briandfoy

Related links

• #91
• #92
• #99
• #104

v0.1.1

Modules affected

Description

• Fix --skip-pull-requests behavior

Related links

• #86

v0.1.0

Modules affected

Description

• Prepend [skip ci] to commit messages by default
• Fix concurrency bug(s)
• Prettify run report with pterm.sh tables / styles

Migration guide

• The --max-concurrent-repos flag has been removed. Please update any earlier git-xargs invocations / scripts that use that flag to remove it.
• By default, git-xargs will now prepend [skip ci] to all commit messages, unless you pass the new --no-skip-ci flag. This feature is intended to prevent large git-xargs jobs from causing excessively costly continuous integration (CI) jobs.

Related links

• #89
• #85
• #84

v0.0.16

Description

• Updated the PR template so you get a nice little form.
• Updated codeowners so that more people are notified.
• Updated the table outputs to be markdown friendly. This replaces the pipe | and dash - symbols in the printed output.

Related links

• #73
• #76
• #78

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:

1. Work that can be performed in parallel as quickly as possible
2. 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.

Related links

• #67

v0.0.14

Description

• Support for overriding base branch names. Adds a new optional --base-branch-name flag. Pass this flag to override the base branch to target pull requests against for all repositories in a given run of git-xargs.

Special thanks

Special thanks to the following users for their contribution!

• @nirnanaaa

Related links

• #64