From 0153f8787d548d3b2a122d0c374332b11411d398 Mon Sep 17 00:00:00 2001 From: Bohdan Triapitsyn Date: Wed, 10 Jun 2026 11:56:53 +0300 Subject: [PATCH] ci: prevent review bot probe comments --- .github/workflows/pr-review.yml | 4 ++-- .opencode/agent/pr-review.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/pr-review.yml b/.github/workflows/pr-review.yml index 09be1586..f5b14e15 100644 --- a/.github/workflows/pr-review.yml +++ b/.github/workflows/pr-review.yml @@ -19,8 +19,8 @@ jobs: review: if: | (github.event_name == 'pull_request_target' && github.event.pull_request.draft == false) || - (github.event_name == 'issue_comment' && github.event.issue.pull_request && (startsWith(github.event.comment.body, '/oc-review') || contains(github.event.comment.body, ' /oc-review'))) || - (github.event_name == 'pull_request_review_comment' && (startsWith(github.event.comment.body, '/oc-review') || contains(github.event.comment.body, ' /oc-review'))) + (github.event_name == 'issue_comment' && github.event.issue.pull_request && github.event.comment.user.login != 'openchamber-bot[bot]' && (startsWith(github.event.comment.body, '/oc-review') || contains(github.event.comment.body, ' /oc-review'))) || + (github.event_name == 'pull_request_review_comment' && github.event.comment.user.login != 'openchamber-bot[bot]' && (startsWith(github.event.comment.body, '/oc-review') || contains(github.event.comment.body, ' /oc-review'))) runs-on: ubuntu-latest permissions: contents: read diff --git a/.opencode/agent/pr-review.md b/.opencode/agent/pr-review.md index 35374372..c4060744 100644 --- a/.opencode/agent/pr-review.md +++ b/.opencode/agent/pr-review.md @@ -104,7 +104,7 @@ Pay extra attention to: Match the repository's existing PR-review style: concise summary first, then a confidence/merge signal, then concrete findings. Do not use a header like `## OpenCode PR review`. -Leave exactly one top-level PR comment with `gh pr comment "$PR_NUMBER" --body "..."` or an equivalent `gh api` call. Do not create separate inline review comments unless the workflow explicitly asks for inline comments later. Printing the review to stdout is not enough: after posting, verify that the new comment exists on the PR (for example with `gh pr view "$PR_NUMBER" --json comments`) before finishing. +Leave exactly one top-level PR comment with `gh pr comment "$PR_NUMBER" --body "..."` or an equivalent `gh api` call. Do not create separate inline review comments unless the workflow explicitly asks for inline comments later. Never post test, probe, placeholder, or debugging comments. Printing the review to stdout is not enough: after posting, verify that the new comment exists on the PR by reading comments only (for example with `gh pr view "$PR_NUMBER" --json comments`); do not verify by posting any additional comment. Use this structure: