policy-bot
policy-bot copied to clipboard
palantir
A GitHub App that enforces approval policies on pull requests
When the `.policy.yml` file is updated, existing PRs need some kind of action (comment, reopen, etc.) to trigger reevaluation with the new policy. We should either: 1. Listen to push...
In repo we often have different sets of files that can be approved by different groups of people. Often a PR will include changes to multiple files that are owned...
One of our internal projects has a high rate of PR creation, which means that PRs that are open for more than a day or two are likely to have...
It would be helpful if policy-bot support a way to set default options for all rules in a policy without copying code or using YAML references. I'm imagining something like...
When enabling the bot for the first time, it should evaluate all open PRs and post status checks.
P3: Policybot should accept webhooks for org changes and update Approvals accordingly. For example, on https://github.com/palantir/policy-bot/pull/23, I approved before being a member of the devtools team and was correctly identified...
Closes https://github.com/palantir/policy-bot/issues/239 After we migrated over to policy bot, I had a couple people ask why the dismiss feature didn't work the same. If you check the dismiss reviews option...
closes #470 As mentioned in #470 there are certain situations where we could run into API limitations on the number of status checks posted to a SHA / context pair....
Add var ENV PORT + POLICYBOT_PORT export PORT=8080 or POLICYBOT_PORT=8080 Run on Cloud requer default var $PORT in env serverless Or add flags --port in command line
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the go/manage-go-mod-dependencies-oss check. To enable or disable this check, please contact the maintainers of Excavator.
