1.3.2

Prevent users from approving a change multiple times (#35)

Prior to this, a single user could satisfy a policy that required more than one approval. Now, only the most recent event from each user is considered when computing approval.

Other Changes

• Make Datadog configuration optional (#26)
• Improve README

1.3.1

Use only branch name in status check context (#23)

The new status check contexts added in 1.3.0 used the full branch label (which included the organization, similar to what it looks like when merging in a fork). Now, only use the branch name as originally intended.

1.3.0

Improved Status Check Context

This release is mainly focused on modifying the context value used for the status check. Originally it was the same value for all PRs. To improve policy-bot's ability to protect branches, we've changed the default behavior to produce a context using the following template: <configured-context>: <target-branch-of-pr>. For example, if the PR is targeting the master branch, the context would be: policy-bot: master.

You can still use the legacy context by turning on the config flag post_insecure_status_checks. For more information, see the godoc.

Other Changes

• Publish snapshot Docker images (#6)
• Improve README

1.2.0

Initial open source release! 🎉