Merge checks written in plain English
Write rules about the pull request itself, such as "a change to migrations/ says in the description how to roll it back", under Merge checks on the Auditor page's Reviews tab or in .auditor.yaml. Auditor judges them on every push and every edit of the title or description and reports them as a check of their own, Auditor merge checks, with a one-line reason for each. A required check that fails fails it, so branch protection can block the merge; warnings never do.
A check can apply to every pull request, or only to those that change files matching its paths. Comment @auditor checks to judge them again. Skipped and paused pull requests get a skipped check, which branch protection accepts.
Each run is one model call over the title, description, labels and diff, billed like a review and counted toward the spend caps.
More in Merge checks.