This release includes changes originally released in the 1.7.x and 1.8.x versions. These older releases are not recommended due to regressions in important functionality.
Fix invalidate_on_push for pull requests from forks (#61, #68, #76)
Originally released in 1.7.0, fully fixed in 1.9.0.
Due to API limitations in GitHub, the information required to implement invalidate_on_push was not being returned for pull requests from forks, meaning new commits pushed to these PRs did not invalidate approval. We've switched to an alternate method of retrieving push times for commits from forks.
Note: policy-bot now errors on pull requests from private forks. We believe that these PRs are uncommon and that fixing the invalidate_on_push behavior is more important, but please let us know if you relied on this functionality.
Add modified_lines predicate (#71)
Originally released in 1.8.0
Users can now use the modified_lines predicate to apply rules based on the number of lines added or removed by a pull request. See the README for details on how to configure this predicate.
Fix error when posting audit statuses (#73)
Originally released in 1.8.1
policy-bot monitors status checks to verify that other users with write access do not overwrite the statuses generated by policy-bot. If an overwrite is detected, policy-bot posts a failed status, but previously used a description value that was too long, causing GitHub to return an error response instead.
Adjust how update merge commits are detected (#76)
A commit is now considered an update merge (for the purpose of the ignore_update_merges option) if it is created via the UI or API and has exactly two parents, one that is part of the pull request and one that is not. Previously, the second parent had to appear in the last 100 commits on the target branch. The new method is simpler and takes advantage of the fact that GitHub already excludes commits that exist on the target branch from the pull request commits.