Help improve reviews with the findings your team decided
Auditor → Knowledge has a switch, off by default, that lets the findings your team fixed or dismissed as wrong become test cases for the reviewer: the changed lines around the finding, the finding and how it ended, with nothing that names your repository, the rest of the file, who wrote it or which commit.
Every finding a team decides says something about the reviewer: a fix means it was right, a thread resolved with the code left alone or a 👎 means it was wrong. With the switch on, each such deep finding may be copied into the tests Auditor's review quality is tuned against, in an anonymised form: the hunk the finding sits in with some lines of context on both sides, the file's name and folder, the finding's text with links, commit ids, mentions and your repository's and account's names removed, and for a fixed finding the lines of the fixing commit that touch it. Never your repository's name, the pull request number, authors or other files, and never an excerpt that looks like it holds a credential.
The switch cannot be turned on while your Directives require zero data retention. Nothing is copied at review time: the lines are read through the GitHub App only when we build the test set, and they stay with us, never in a public set.
More in Help improve reviews.