aboutsummaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-22 15:13:05 -0500
committerCraig Jennings <c@cjennings.net>2026-05-22 15:13:05 -0500
commit0afe48df3d4fa49da889fbeaeaa38e8f971e030a (patch)
treea92f1d88727942cad5f9568a28d3c38d7d1e746c /scripts
parent2b3e5a5a7327a6ffdb6fbca92c9691a05c7221c1 (diff)
downloadrulesets-0afe48df3d4fa49da889fbeaeaa38e8f971e030a.tar.gz
rulesets-0afe48df3d4fa49da889fbeaeaa38e8f971e030a.zip
docs(rules): add an unable-to-verify reporting standard
verification.md required running tests/lint/typecheck/build before claiming done, but said nothing about what to do when a command can't run. A new "When You Cannot Verify" section requires a four-part report (command attempted, why it couldn't run, risk left unverified, and the smallest next command for the user) and states the principle that a check that didn't run is never reported as a pass.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions