werkator build succeeded after 00:08
werkrevisor 0.6.0: four verdict colours, and only deterministic rules block hard. - 🟠 ORANGE: findings of the LLM and of the classifier Jev. No bot review; a developer approval after checking the findings unlocks the merge (assessment status `warning`, exit 15 where codes are distinguished, 0 in approval mode). - 🔴 RED: only deterministic rules. First rule: open questions in a changed PR document (`[ ]`, bullet or paragraph without checkbox under "Open Questions"/"Offene Fragen"). - Fixes from the comparison on hsadmin-ng: no `FIXME.review` markers in findings, secret scan ignores `src/test/**` except real key formats, documentation files trigger no hard-YELLOW path rules. Reason: the repository admin on dev.hostsharing.net is an operator, so an admin merge override is no way out of a false RED; model and classifier findings are often wrong (3 of 8 Sonnet findings in the comparison). 222 unit tests green in the pinned PR-Agent image. Open: whether Gitea ignores a stale bot REQUEST_CHANGES after a later ORANGE/YELLOW head; tested on werkprobe after the rollout. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: mhoennig <michael@hoennig.de> Reviewed-on: #2
306 B
306 B
Geplante Regeln
Festgelegte Anforderungen an werkrevisor, die noch nicht umgesetzt sind.
Zurzeit ist keine geplante Regel offen.
Die Regel „Offene Fragen im PR-Dokument verhindern ein Approval“ ist seit werkrevisor 0.6.0 umgesetzt;
sie steht in der README unter [pr_doc].