If no rule matches can policy-bot not set a failed status on the PR? about policy-bot HOT 1 OPEN

The way we usually solve this problem (automatically merging PRs from bots or scripts) is a bit different:

1. Policy Bot is always a required status check in GitHub
   1. PRs from bots that modify the right files are automatically approved
   2. PRs from humans require review (you could also auto-approve these if you wanted)
2. Bulldozer will always wait for required status checks (as configured in GitHub) to pass
3. When bots open PRs, they add the merge when ready label to the PR. This label is the trigger that enables Bulldozer to merge the PR when all the checks are passing. You could also have another app or a GitHub Action add labels like this.

In other words, while Policy Bot is a precondition to merge, it is not the trigger that activates Bulldozer. This has worked pretty well for us and I think it's useful to be able to say that a check is always required and should always be present on a PR.

That said, you are not the first person to ask for Policy Bot to skip PRs where the policy does not match any rules. We added the explicit failure as a safety measure to help prevent policies that accidentally approved or ignore changes that they shouldn't have. We developed Policy Bot primarily as a compliance tool, so these safety measures are important.

I think we could add a server-level flag to control this behavior so people who are using Policy Bot for convenience rather than compliance could disable this and skip posting a status when no rules match. Unlike the initial implementation in #711, I think we want to only skip posting a status when there are no matching rules. The pending status is useful to indicate that you probably have a condition wrong in the policy (something should have been approved, but it was not) and the failure/error status is useful if something goes wrong during evaluation.

Making this a server-level flag is important to us because for our workflows, we don't want individual projects to be able to opt-in to this feature. We'd leave it disabled (which should also be the default), but you and other users could enable it when you deploy Policy Bot.

from policy-bot.