Repository navigation
ci(review): report the Claude review as a commit status on the PR - #701
Conversation
A comment-triggered run is a run for the default branch, so its own check lands on main's tip and never appears on the PR. Post a 'Claude Review' status on the reviewed commit: pending while the review runs, then success, failure or error from the job's outcome. Advisory, not required.
|
@claude /review |
|
Claude finished @theCodeDrift's task in 2m 58s —— View job Review completeReview mode: incremental — read 0 prior review thread(s) before reviewing. The only prior record on this PR is the trigger comment (
[New] One concrete correctness issue, posted inline on the new "Mark the review pending on the PR" step (lines 208–220): it has no Everything else checked out:
|
@claude /reviewruns are triggered byissue_comment, so GitHub runs them for the default branch: the run's own check is recorded onmain's tip, never on the PR. A "wait for all checks" loop on the PR therefore finishes while the review is still running, and the tracking comment is no substitute, since it is edited many times and no edit marks the last one.This posts a
Claude Reviewcommit status on the PR head commit the review checked out:always()step, so a failed run never stays yellow. A runner that dies outright clears with a re-run.The SHA is read from the checkout, not re-queried, so a push mid-review cannot move the status onto an unreviewed commit. The status is advisory, not required: most PRs are never reviewed, and a required status that is never posted stays pending forever.
statuses: writeis added to the job. It is safe only whilegh apistays off the model's--allowedTools(the model's environment holds the job token, andgh prcannot set a status); the workflow header now says so./focusis deliberately unchanged: it is a human asking where to look, not something an agent waits on.Not exercised yet: comment-triggered workflows run from
main, so the first real run is the first@claude /reviewafter this merges.