From 61294d8d12a33f71e7d152bffe90a95837c3b33c Mon Sep 17 00:00:00 2001 From: zhaochangle Date: Tue, 26 May 2026 15:52:35 +0800 Subject: [PATCH] 1 --- .github/workflows/opencode-review-runner.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/opencode-review-runner.yml b/.github/workflows/opencode-review-runner.yml index 54b121f714718d..3d80e110fa9007 100644 --- a/.github/workflows/opencode-review-runner.yml +++ b/.github/workflows/opencode-review-runner.yml @@ -177,6 +177,7 @@ jobs: ## Final response format - After completing the review, you MUST provide a final summary opinion based on the rules defined in AGENTS.md and the code-review skill. The summary must include conclusions for each applicable critical checkpoint. - If the overall quality of PR is good and there are no critical blocking issues (even if there are some tolerable minor issues), submit an opinion on approval using: gh pr review PLACEHOLDER_PR_NUMBER --comment --body "" + - Note that when submitting review comments in this way, the content will not be escaped, so you need to input multi-line text with line breaks directly, rather than using `\n`. - If issues found, submit a review with inline comments plus a comprehensive summary body. Use GitHub Reviews API to ensure comments are inline: - Inline comment bodies may include GitHub suggested changes blocks when you can propose a precise patch. - Prefer suggested changes for small, self-contained fixes (for example typos, trivial refactors, or narrowly scoped code corrections).