Bulldozer Versions Save

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.

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

• Fix regression (from 1.9.0) with the body: empty_body option for squash commits (#193)
• Upgrade palantir/go-githubapp to the latest version, introducing new error metrics and log fields (#201)

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.

Other Changes

• Include a default configuration file in the Docker image (#189). Note that this file does not set certain required properties that must be set using environment variables or by mounting your own configuration file.

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

• Update google/go-github, palantir/go-githubapp, and palantir/go-baseapp to the latest versions (#179)
• Convert to Go modules. Version tags will have a leading v going forward but published versions will be the same as before. (#179)
• Improve the example server configuration file (#182)

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)

Other Changes

• Add additional debug logging around evaluation and signals (#168)
• Update google/go-github to the latest version, skipping webhook payload validation when the secret is empty (#167)

Other Changes

• Upgrade palantir/go-githubapp, fixing a rare panic in GitHub client middleware (#152, #162)
• Build with Go 1.13.4 (#159)

Add basic support for loading configuration from the environment (#139)

All GitHub configuration and certain sensitive values in the Bulldozer configuration can now be read from environment variables. Values in the environment override values set in the configuration file. The variables are described next to the matching configuration property in the example configuration.

Fix handling of check_run events (#142)

GitHub does not always include a full pull request object in webhook payloads for the check_run event. Always use a full object loaded from the API for processing instead.

Other Changes

• Build with Go 1.12.7 (#140)
• Upgrade Godel to 2.16.0 (#140)
• Documentation improvements (#137, #138)

Update palantir/go-github app (#134)

Fixes tagging for rate limit metrics.