Found reviewing PR #316.
write_report emits TYPE: message lines with no severity column, and the workflow picks its heading from the aggregate result.
So a PR with one DANGLING_EDGE and 19 DISCONNECTED gets a comment headed "Network integrity: broken references / These fail the build" above 20 visually identical lines, 19 of which do not fail the build. The curator has no way to find the one blocker short of knowing the SEVERITY table by heart.
This matters now in a way it did not before: #316 is the first release where the error/warning distinction is load-bearing.
Fix: prefix each report line with its severity, and have the report or the comment state the error/warning counts.
Found reviewing PR #316.
write_reportemitsTYPE: messagelines with no severity column, and the workflow picks its heading from the aggregate result.So a PR with one
DANGLING_EDGEand 19DISCONNECTEDgets a comment headed "Network integrity: broken references / These fail the build" above 20 visually identical lines, 19 of which do not fail the build. The curator has no way to find the one blocker short of knowing theSEVERITYtable by heart.This matters now in a way it did not before: #316 is the first release where the error/warning distinction is load-bearing.
Fix: prefix each report line with its severity, and have the report or the comment state the error/warning counts.