Review settings in the repository, from .auditor.yaml
A repository can keep its review settings in an .auditor.yaml file at its root: when reviews run, what re-reviews post, the deep review and its depth, skip rules, the walkthrough, fixes and the rest, by the settings' own names. What the file sets wins over the team's settings and the repository's on the Auditor page, and anything it leaves out keeps those. Auditor reads it from the default branch whenever a push there changes it, so a pull request can't loosen its own review.
Models, spend caps, ticket trackers, documentation crawls and everything Shopify stay on the Auditor page, since they cost money or reach outside the repository. A line Auditor can't use (one of those, a key that names no setting, or a value out of range) is skipped and the rest applies.
A pull request that changes the file gets a finding on each line Auditor won't be able to use once it merges, and the repository's settings on the Auditor page show what the file sets and link to any such line.
More in Settings in the repository.