policy-bot
policy-bot copied to clipboard
palantir
A GitHub App that enforces approval policies on pull requests
It would be helpful to specify different approval rules for additive-only changes to certain files. This should be easy to add in code (the `File` abstraction already contains the information),...
```yml policy: approval: - and: - approvalrule1 disapproval: if: targets_branch: pattern: "^(develop|production)$" changed_files: paths: - "^ScriptFolder/" - ".github/" requires: teams: ["adminteam"] # the list of rules approval_rules: - name: approvalrule1...
I was looking through your readme and there doesn't seem to be a way to only run given check if it wasn't authored by someone. For example for my smaller...
Today we allow conditional policies on aspects of file modification like number of lines added/deleted/modified. Certain workflows would benefit from extending this to also allow conditional policies on the addition...
Hi there! I've been trying out `policy-bot` for my team and it's been working really well. One thing I think would be cool would be to customize the messages in...
One feature natively support by github pull-request reviews is dismissing stale approvals:  I believe the `invalidate_on_push` option should similarly dismiss stale approvals to help clear the UI and also...
It would be great to have the case where “approvals have been made but invalidated as the HEAD has since been pushed to” be surfaced in the policy-bot UI? (The...
Predicates can sometimes fail for multiple reasons. For example, a disapproval predicate for title formatting could fail due to matching multiple regex patterns. Currently, only the first pattern to fail...
It would be great if we could somehow specify that the team required for approval for a rule would be dynamically determined based on the file path. As an example,...
It would be really sweet if I could leave a comment on a PR to ask policy bot to do the validation and post back whether it is valid _Originally...
