Fixed in 704fd0b: the no-change check now ignores line endings and trailing blanks (report.same_line_comment_text), so a body that Gitea normalized is no change; the test `test_a_reused_line_comm…
Answer to the werkrevisor result for 3729f3e:
- YELLOW finding
cli.py:539-548(Jev doubts it): answered in its line comment; the failed gate check blocks a merge that a failed cancel left…
Not changed: a network error outside GiteaError ends the run as ERROR (exit code 30), which fails the required status check. Gitea's scheduled merge ("merge when checks succeed") waits until all…
Fixed in 602663a: hints_hold_merge is validated as boolean like the other gate switches; the string "false" is a config error. Test test_the_switch_must_be_a_boolean.
Not changed: like all…
Not changed, on purpose: a restart is a manual request for the state of the gate, so each restart with open hints answers with a short comment. Werkator restarts a review build only on demand, so…
Fixed in a66d56e: a failed cancel ends the review with exit code 10, so the failed gate check stops the merge scheduled earlier. Test test_a_failed_cancel_is_named, red without the fix.
🤖…
Fixed in f11a884: findings of this review that are no line comment, e.g. refused by Gitea, count as open hints too; a restart releases them, since it reuses the verdict without findings. Test…
Fixed in 23983b0: the PR doc says that the gate note, also a failed cancel, goes into the commit status and the result comment, and that a restart posts a short comment.
🤖 Generated with [Claude…
Not changed in its first form: Gitea 1.27 answers 404 when no merge is scheduled, which counts as success; any other error fails the gate check since a66d56e, on purpose, since an uncancelled…
Fixed in a66d56e: a restart comments only when the merge still waits or is newly scheduled; "merge already scheduled" stays silent. Test test_a_restart_comments_only_a_change_of_the_merge.
The…
Fixed in 23983b0: a restarted review posts its gate note as a short PR comment, since the result comment names the first review; a failed cancel is part of that note and, since a66d56e, also fails…
Answer to the werkrevisor result for 37142cd:
- YELLOW "no AI review: the PR needs 105191 input tokens": the CI still runs werkrevisor 0.19.3, which gives up a prompt above the input limit;…
Not changed: this is the PR#30 follow-up. The RED case moved from test_review_kind_follows_the_verdict into test_red_gives_a_comment_review_and_a_failed_gate, which asserts the review list…
Not a defect in the current flow, but guarded explicitly now: rules.py always sets skip_llm for a secret, so cli.py collects no full files and calls no selection. Since the last commit…
Fixed in 64e0b7b: a malformed usage field (no integer, a boolean, a list instead of an object) now makes the selection cost an estimate instead of ending the review. Test `test_malformed_usage_valu…
Assessment of the werkrevisor findings (as of the last commit):
The CI reviews of the last two commits ran with the installed 0.19.3, which gives up a prompt above the input limit: "no AI review:…