claude-code-review.yml: add missing --comment flag - #57
Merged
Conversation
Same issue as pgxntool-test#61/pgxntool#84: the /code-review plugin only prints its findings to the job log by default; it needs --comment to post a PR comment. Every automated review here has run correctly but never posted anything visible on the PR.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
jnasbyupgrade
added a commit
to jnasbyupgrade/cat_tools
that referenced
this pull request
Aug 2, 2026
Debugging why the paid review isn't behaving as expected (e.g. the missing --comment flag that silently swallowed every review before Postgres-Extensions#57) previously meant either waiting 5-20+ min per iteration for the cost gate to clear, or hand-editing the workflow just to see the raw transcript. Adding the "claude-debug" label to a PR now (a) skips the cost gate entirely, and (b) sets show_full_output: true so the full raw Claude Code JSON transcript, including tool results, lands in the job log. The label is checked live via `gh pr view` rather than the static event payload, so adding it and clicking "Re-run jobs" picks it up without a new push. `labeled` is added as a trigger type so applying the label alone kicks off a fresh run; the job's `if:` scopes that to only the claude-debug label itself, so tagging a PR with anything else doesn't trigger another paid review.
jnasbyupgrade
added a commit
to jnasbyupgrade/cat_tools
that referenced
this pull request
Aug 2, 2026
Debugging why the paid review isn't behaving as expected (e.g. the missing --comment flag that silently swallowed every review before Postgres-Extensions#57) previously meant either waiting 5-20+ min per iteration for the cost gate to clear, or hand-editing the workflow just to see the raw transcript. Adding the "claude-debug" label to a PR now (a) skips the cost gate entirely, and (b) sets show_full_output: true so the full raw Claude Code JSON transcript, including tool results, lands in the job log. The label is checked live via `gh pr view` rather than the static event payload, so adding it and clicking "Re-run jobs" picks it up without a new push. `labeled` is added as a trigger type so applying the label alone kicks off a fresh run; the job's `if:` scopes that to only the claude-debug label itself, so tagging a PR with anything else doesn't trigger another paid review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/code-reviewplugin only prints its findings to the job log by default; it needs--commentto post a PR comment. This workflow's prompt was missing that flag, so every automated review has run (real API cost, correct analysis) but never posted anything visible to the PR.show_full_outputon a canary PR with a deliberately injected bug: the review agent found the bug correctly, but its own final line read "No--commentargument was provided, so no GitHub comments were posted." Adding--commentfixed it there; this is the same one-line fix ported here unchanged.Test plan