Seen on issue #83: @qa's approval pasted technical review detail (whitespace nits) into the issue thread. Review internals belong on the PR; the issue gets exactly ✅ Reviewed PR #N — looks good.
Seen on issue #83: @qa's approval pasted technical review detail (whitespace nits) into the issue thread. Review internals belong on the PR; the issue gets exactly `✅ Reviewed PR #N — looks good.`
Seen on issue #83: qa's approval pasted whitespace-nit detail into the issue
thread. The issue is for the creator/orchestration; review internals belong on
the PR. On APPROVE the full reply (+run report) now posts to the PR and the
issue gets exactly '✅ Reviewed PR #N — looks good.' (falls back to the issue
only if no PR could be resolved).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Seen on issue #83: @qa's approval pasted technical review detail (whitespace nits) into the issue thread. Review internals belong on the PR; the issue gets exactly
✅ Reviewed PR #N — looks good.