Kjell Tore Guttormsen
10ad1254ab
A repo's `status` is now the worst JUDGED finding, and `SKIP` only when nothing was judged. `SKIP` used to rank between `OK` and `WARN`, so one un-runnable check spoke for every check that ran: 0 ERROR, 0 WARN and a dozen OK headlined as "skipped". Five repos in org-ops census 05, `okr` among them with the most OK in the org, reading as unread. "`SKIP` is never a pass" survives in the half of the rule that carries it — an unregistered repo, or an empty finding set, still says SKIP, because there is nothing else to be worst of. Fixing the status alone would have traded "clean repos look skipped" for "skipped checks look clean". So `notChecked` rides beside it: in --json, and as a `· N not checked` qualifier on the summary line. Absent means an older engine, not zero. Measured across all 21 local clones from ONE saved sweep, so before and after come from the same findings rather than two sweeps of a moving org: 343 findings before, 343 after. 8 repos moved, every one SKIP -> OK. 1 ERROR and 3 WARN before, 1 ERROR and 3 WARN after — the counts that decide whether a repo needs work did not move. BREAKING: consumers reading `.status` see a changed value domain. 147 -> 154 tests.
12 lines
195 B
JSON
12 lines
195 B
JSON
{
|
|
"name": "repo-standard",
|
|
"version": "0.7.0",
|
|
"private": true,
|
|
"type": "module",
|
|
"engines": {
|
|
"node": ">=18"
|
|
},
|
|
"scripts": {
|
|
"test": "node --test scripts/*.test.mjs"
|
|
}
|
|
}
|