Releases: palantir/bulldozer
v1.13.0
Update pull requests on more events (#235)
Pull requests that match trigger conditions for updates are now updated when they are opened or when labels are added. Previously, pull requests only updated if the target branch changed after the pull request was opened.
Other Changes
v1.12.0
Fix handling of skipped and neutral check results (#223)
Bulldozer now accepts skipped
and neutral
checks as valid conclusions for required statuses, matching GitHub's behavior. This applies both for required statuses set by branch protection and required statuses set in the Bulldozer configuration file.
Other Changes
v1.11.0
Add option to prevent merges without required checks (#217)
By default, Bulldozer will now avoid merging pull requests that target branches with no required status checks.
To continue using the previous behavior, set the merge.allow_merge_with_no_checks
option to true
like so:
version: 1
merge:
allow_merge_with_no_checks: true
The v0 configuration format is not updated to support this feature. Repositories using the v0 configuration will be treated as if allow_merge_with_no_checks
is set to the default value false
.
v1.10.1
Add branch_patterns
trigger condition (#200)
Users can now set the branch_patterns
option to a list of regular expressions to trigger merges to branches with names that match any of the patterns.
Other Changes
v1.10.0
Replace use of whitelist/blacklist with trigger/ignore (#196)
Users can now specify trigger
and ignore
instead of whitelist
and blacklist
in their configuration options, respectively.
The blacklist
and whitelist
options are deprecated and will
be removed in a future release.
Account for special GitHub behavior with Travis CI (#194)
Travis CI status checks are apparently special-cased in GitHub code for
protected branches such that they behave differently from all other
checks. To allow Bulldozer to work for users of Travis CI Enterprise,
implement a matching special case in Bulldozer.
v1.9.1
v1.9.0
Improve asynchronous processing for webhooks (#180)
While Bulldozer previously performed merges and updates in separate goroutines, this release moves all webhook processing out of the request handler goroutine. By default, there are 10 workers processing events with a queue size of 100. These values can be adjusted using the workers.workers
and workers.queue_size
configuration properties.
Other Changes
1.8.0
Add support for fast-forward merging (#176)
Using the new merge mode ff-only
will fast-forward the target branch of the pull request to match the source branch. This merge method only works if a fast-forward merge is possible, i.e. the source branch contains all commits on the target branch.
Other Changes
- Clarify when
push_restriction_user_token
is required in response to GitHub updates (#171)