← Changelog
FixedAuditor

Merge checks judge each change once, fixed findings close on every review, and answers to replies respect the spend caps

When Auditor wrote a pull request's description after a review, that edit started merge checks again, so the same push was judged and billed twice. Now Auditor's own edits don't start them, and a run whose head, title, description, labels and checks match the last one's is skipped and costs nothing; edits by people and other bots are still judged, and @auditor checks always judges again. A finding whose code was fixed now closes on the next review even when that review skips the layer that found it, so a fixed deep finding no longer keeps the check failing. And answers to replies under a finding count toward the monthly and per-pull-request spend caps, as the docs said: once a cap is reached, Auditor says so in the thread instead of answering.

Answers to replies show in Logs as session = athr_<repository id>_<pull request>, and in a repository's cost with its reviews.

More in Replying to a finding.