Skip to content

Releases: palantir/bulldozer

1.1.0

13 Nov 17:07
0809cf2
Compare
Choose a tag to compare
  • track pull_request events, so bulldozer can trigger from labels that are added

1.0.0

25 Oct 22:57
87ae18e
Compare
Choose a tag to compare

Bulldozer is now a GitHub App! 🎉

As part of the rewrite, we've:

  • Improved the configuration format
  • Added more expressive blacklist and whitelist configuration
  • Added support for Bulldozer-only required status checks
  • Improved squash message generation
  • Fixed other bugs and made minor behavior tweaks
  • Updated to use palantir/go-githubapp and palantir/go-baseapp

Bulldozer 1.0 still understands configuration from the 0.4.x series, so while you will have to enable the new application on repositories, you do not need to update configuration all at once.

0.4.12

29 Aug 23:12
75f60bc
Compare
Choose a tag to compare

Allow whitespace when finding commit messages (#47)

Allow whitespace after the opening tag and before the closing tag that
delimit commit messages in a PR body. Also place the regexp in
multi-line mode and use ^ and $ to match the start and end of lines
instead of the literal \r\n string.

0.4.11

03 Aug 20:27
a0468b7
Compare
Choose a tag to compare

Use pagination when listing reviews and reviewers (#46)

Fixes review detection on PRs that have many reviews.

0.4.10

17 Jul 22:39
Compare
Choose a tag to compare

Add option to ignore squashed commit messages (#45)

Exposes a new configuration option which causes squash and merges to specify an empty body.

0.4.9

12 Jul 00:09
c80162a
Compare
Choose a tag to compare

Add support for multiple config file paths (#44)

Based on server configuration, the application will now look for the
repository configuration file in multiple paths until it finds one. If
no paths are specified, the existing .bulldozer.yml is used.

This commit makes the minimal amount of change necessary to get this
working. Ideally, there would be more refactoring to standardize config
passing and client construction, but I'm not ready to do that yet.

Fix leaks when polling for PR mergeability (#43)

The GitHub API requires polling PR status if the mergeable property is
null, because a background job is running to compute this value. But the
mergeable property is also null for merged PRs. In cases where there was
a race between multiple requests to merge the PR (e.g. if there were
many status updates at once), one or more of these requests would end up
polling a merged PR forever, waiting for it to be mergeable.

Add a limit on the total number of poll attempts and also check for PRs
that are merged or closed after we start polling. In addition, only try
to merge PRs in response to successful status checks.

Add update strategy config option (#30)

Values are "deferToPR" and "always"

0.4.8

12 Feb 21:32
24fbe22
Compare
Choose a tag to compare

Modify github approval verification logic (#29)

  • Modify github approval verification logic

If reviews are not required for a repo, then only consider review status
as failed if someone has explicitly disapproved the repo

Fixes #27

Upgrade github.com/google/go-github to 79fc6c1 (#24)

Moving to use golang/dep (#16)

Cap body limit to 6M (#17)

Use a custom user-agent string (#14)

0.4.7

26 Sep 17:43
Compare
Choose a tag to compare

Fix type casting for webhooks (#13)

0.4.6

26 Sep 16:58
Compare
Choose a tag to compare

Fix release publish (#12)

0.4.5

26 Sep 16:46
Compare
Choose a tag to compare

Fix publish script

Cannot use reference in command block (#11)

Fix circleci config (#10)

Publish snapshot docker containers (#9)

Publish snapshot docker containers