Verification · Feedback and evaluation · Developer feedback capture
Outcome tracking
Was the finding fixed in a later commit, dismissed or ignored.
How to build it
- Store each finding with its ID, file, line and the commit it was raised on.
- On each later push, check whether the flagged lines changed and record fixed, dismissed or ignored.
- Keep the outcome record for each finding so calibration can use it.
Signals in a repository
- A findings table or log file that records each finding's status.
- A scheduled job that reads resolved review threads and writes their status back.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.