From b7c7a106f88caa9b5652893d9a6102159139a94c Mon Sep 17 00:00:00 2001 From: openhands Date: Fri, 5 Jun 2026 15:26:11 +0000 Subject: [PATCH] docs(code-review): trigger /github-pr-review alongside /codereview in Option B automation prompt --- openhands/usage/use-cases/code-review.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openhands/usage/use-cases/code-review.mdx b/openhands/usage/use-cases/code-review.mdx index 0260fab4..6619cc10 100644 --- a/openhands/usage/use-cases/code-review.mdx +++ b/openhands/usage/use-cases/code-review.mdx @@ -468,7 +468,7 @@ Step 3 — Post a progress comment and save the comment ID: -d "{\"body\": \"🔍 **Review in progress…**\\n\\nWe are performing the review through OpenHands Cloud Automation. You can log in and [view the conversation here](${SESSION_URL}).\"}" \ | python3 -c "import sys,json; print(json.load(sys.stdin)['id'])") -Step 4 — /codereview +Step 4 — /codereview and /github-pr-review Review the pull request using the pr-review plugin. Post a comprehensive code review on GitHub with inline comments on specific changed lines where appropriate, and a concise overall summary. Avoid duplicating existing unresolved review comments. When submitting the review, choose the appropriate event type: