policy-bot
policy-bot copied to clipboard
palantir
A GitHub App that enforces approval policies on pull requests
Hello, I would like to know why the remote policy configuration has to be full public. We would like to use it with a github entreprise on premise version where...
We have `invalidate_on_push=true` and one of the most common reported issues is someone updating a PR without getting a new review. It would be *great* if the bot could add...
## What happened We've been using the request_reviews functionality to try to ensure incoming PRs (across >100 repos) get attention from a team member by pushing them into team members'...
policy-bot should handle PRs which change 300+ files (300 is a Github limitation for certain APIs).
When I deployed my policy-bot, I kept getting this error ```yaml could not get access_tokens from GitHub API for installation ID 123456: unsupported protocol scheme ``` Turns out it's because...
## What happened? We've been using the new `request_review` functionality pretty heavily both internally and externally, and it's been very effective in more equally load balancing PRs to members of...
We structure our projects so that all code is in a `src/` folder, and currently have a policy that looks like the following: ```yaml - name: no code changed if:...
Hi, Policy bot is working fine since more than 6 months and we face an issue when we create pull requests (~200/250 files) from a release branch to master branch:...
Because allow_contributor includes the PR author and overrides the allow_author option, you are unable to achieve the following workflow: Scenario: you want to enable an approver who sees a small...
Currently the following sequence ends up in an approve: 1. Reviewer approves 2. Reviewer requests changes (e.g. because an issue was spotted later on) 3. PR author dismisses request changes...
