Verification · Finding validation · Noise budget
Carried findings
Findings that did not fit are kept and offered on the next run instead of dropped.
How to build it
- Save the findings that did not fit under the cap, keyed by the change identifier.
- On the next run, offer saved findings that still apply to the current code.
- Drop a saved finding once its code is removed or the issue is fixed.
Signals in a repository
- A store of deferred findings, such as a file or database table, keyed by pull request.
- Bot comments on later runs that cite earlier carried findings.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.