v1.16.1

Other Changes

• Evaluate pull requests for reviewer assignment on reopened events (#192)
• Fix documentation link on the app landing page after adding v prefix to tags (#190)

v1.16.0

Add teams mode for reviewer requests (#183)

When using this mode, Policy Bot requests reviews from teams rather than individual users. The teams must be collaborators with at least read permissions on the repository.

Enable asynchronous processing for webhooks (#187)

Policy Bot now processes all webhooks in separate goroutines, avoiding issues with GitHub webhook delivery time outs. By default, there are 10 workers processing events with a queue size of 100. These values are adjustable 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 (#186)
• Convert to Go modules. Tags now have a leading v, but published versions are the same as before. (#186)

1.15.1

Support check runs for has_successful_status predicate (#176, #178)

Policy Bot now looks at statuses from check runs when evaluating the has_successful_status predicate. This requires updating the app configuration in GitHub to grant read-only access to checks and enable check run webhooks.

Other Changes

• Update NPM development dependencies (#177)

1.15.0

Add ignore_commits_by option (#156)

This option allows rules to ignore all commits that are authored and committed by users matching specific criteria. This can be useful to prevent automated commits from invalidating approval or to ignore changes by trusted contributors.

Add comment_patterns approval method (#158)

This option takes a list of regular expressions that identify approval (and disapproval) comments. Use this method instead of the existing comments method to match comments by exact text or by more complicated patterns.

Validate regular expressions when loading policies (#157)

Policies with invalid regular expressions now fail to load instead of failing only when a rule with an invalid expression is evaluated. Regular expressions are now also validated as part of the validation API.

Other Changes

• Improve commit loading when push times are missing from the initial API response (#154)
• Increase the pull request file limit to 3000 (#161)
• Document known security limitations in the README (#159)

1.14.0

Add has_labels predicate (#151)

The has_labels predicate makes approval rules conditional on the existence of labels on a pull request. All of the labels in the list must be present to activate the rule. This predicate is not recommended for security control given the relatively limited permissions required to add and remove labels.

1.13.0

Add ignore list to changed_files predicate (#146)

The changed_files predicate now has an optional ignore list, allowing the predicate to disregard changes to specific patterns. Please see the README for more details.

1.12.6

Other Changes

• Do not run reviewer assignment when processing PRs for status events (#145)

1.12.5

Add policy validation endpoint (#142)

The new /api/validate endpoint allows users to upload policy files for validation prior to committing them to a repository. Please see the README for more details.

Add has_successful_status predicate (#141)

The has_successful_status predicate makes approval rules conditional on specific status checks passing. This can be useful to change approval based on CI checks or other dynamic information that may change between pull requests.

Other Changes

• Fix team lookups for reviewer assignment (#143)

1.12.4

Other Changes

• Upgrade palantir/go-githubapp, potentially fixing a rare panic in GitHub client middleware (#137)
• Build with Go 1.13.4 (#138)

1.12.3

Add option for requesting all possible reviewers (#130)

Users can now modify how to request users by setting the option "mode". By default policy-bot will request random users. However, when set to "all-users", policy-bot will request everyone who may approval.

Other Changes

• Add better debug logging for reviewer selection (#131)
• Clarify interaction of allow_author and allow_contributors in README (#132)