Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" is a real answer.
1claude.yml (the workflow that answers '@claude review') was manually turned off on 09-30. Since 10-01 a PR that only changes workflow files is held until someone comments '@claude review', so those PRs can't merge. Turn claude.yml back on?
In plain terms. Should I turn the comment-triggered code reviewer back on? It was switched off last week, and since then any PR that only edits our CI files is stuck with no way to merge.
Why, and what was tried
The session raising this recommends: Turn the comment-triggered reviewer back on It's the only cure the hold names today. A manual re-run of claude-code-review.yml does NOT clear it: the review job is skipped for workflow-only PRs on every trigger, dispatch included (claude-code-review.yml ~L589). Option 2 is a PR to the review workflow itself, which hits the same self-modify block and needs an attended merge. Only risk: if it was turned off for the 09-28 Actions bill, comment-triggered runs come back — one run per comment, not per push. Tried first, unsuccessfully: Checked the Actions API: claude.yml and claude-review-recheck.yml both disabled_manually on 09-30; claude-code-review.yml active. Read the classify/decide steps on origin/main to confirm a dispatch can't cure the hold. First stuck PR: #17472 (only touches post-merge-heavy.yml). Couldn't find who turned it off or why.