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)

1.12.2

Improved handling for requesting reviewers (#127)

Reduce the number of events that trigger the request reviewer flow.

Check for assigned reviewers just before requesting (#126)

Previously we only checked once, performed lookups, and possibly requested reviewers after a human had already done so. Instead, we can check a second time just before making the last API call.

1.12.1

Fix regression in pull_request_review_event handling (#125)

Usage of the in-preview isDraft field in the GraphQL API caused failures when the field was missing.

1.12.0

Add ability to request reviewers automatically (#121, #122 #123, #124)

policy-bot can now automatically request reviewers when a pull request is opened by using the request_review option on an approval rule. See the README for more usage details.

Other Changes

• Bump mixin-deep from 1.3.1 to 1.3.2 (#118)
• Allow policy-bot to be hosted at a subpath behind a proxy (#117)

1.11.0

Add only_has_contributors_in predicate (#114)

The new only_has_contributors_in predicate is similar to has_contributor_in, but applies to all contributors on a pull request, including the pull request author. This is useful to enable special approval conditions when a mix of trusted users and/or automated bots have contributed to a pull request.

Add ability to read some configuration values from the environment (#113)

All GitHub options and certain sensitive Policy Bot options can be defined or overridden by environment variables. The exact properties and environment variable names are described in the sample configuration file.

Fix caching when a pull request contains no changed files (#105)

Previously, if a pull request had no files, the file cache for a request was never initialized. When a policy has many file-based rules, this can lead to a huge number of unnecessary API requests and delay evaluation.

Other Changes

• Document URLs for GitHub App configuration (#104)
• Bump lodash from 4.17.11 to 4.17.14 (#101)
• Update palantir/go-githubapp to the latest version (#115)

1.10.1

Order rules by status on the details page (#96)

When viewing the details of a pull requests, rules are now ordered by status, with approved rules at the top, then pending rules, and finally skipped rules. This makes it easier to see which rules are still required when the policy contains many different rules.

Other Changes

• Correctly identify rate limit metrics by installation ID (#95)
• Add additional debug logging for rare GitHub API failures (#97)
• Improve documentation (#94, #98)

1.10.0

Add client caching for GitHub REST requests (#91)

GitHub responses to v3 REST API requests are now cached and requests are made conditionally when possible. This reduces the request load Policy Bot places on GitHub and avoids rate limiting. Cached requests are always re-validated with GitHub to avoid working with stale data. The maximum size of the cache is also configurable by administrators.

Other Changes

• Increase the number of retries when the pushedDate of a commit is not loaded (#92)

1.9.3

Fix author_is_only_contributor predicate for web commits (#89)

Commits created via the GitHub UI are now properly detected as having a single author. Previously, GitHub was incorrectly identified as a non-author contributor.

Other Changes

• Update front end build dependencies