Prompted by a dev.to comment:
today a full re-run has a clear path (rescan issue), but a row-level
dispute — "rule D004 is wrong for this specific tool" — quickly loses its
anchor: which row, which scanned version, which rule.
Three small fixes:
- Stable anchor links per row in leaderboard.html (
#server-name), so a
dispute can point at the exact row.
- Scanned-version column — every row shows the exact package version that
produced the score. Scores are point-in-time; the table should say so
per-row, not just in a footnote.
dispute issue template (.github/ISSUE_TEMPLATE/dispute.yml) with
pre-filled fields: server name, scanned version, rule ID, row link, and
"why this rule doesn't apply here". Small disputes shouldn't require a
full rescan thread.
Related but separate: rescan template could be added in the same pass
(fields: server, version to scan, what changed).
Prompted by a dev.to comment:
today a full re-run has a clear path (
rescanissue), but a row-leveldispute — "rule D004 is wrong for this specific tool" — quickly loses its
anchor: which row, which scanned version, which rule.
Three small fixes:
#server-name), so adispute can point at the exact row.
produced the score. Scores are point-in-time; the table should say so
per-row, not just in a footnote.
disputeissue template (.github/ISSUE_TEMPLATE/dispute.yml) withpre-filled fields: server name, scanned version, rule ID, row link, and
"why this rule doesn't apply here". Small disputes shouldn't require a
full rescan thread.
Related but separate:
rescantemplate could be added in the same pass(fields: server, version to scan, what changed).