You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[fix](ci) Change code-review workflow from approval-based to status-based tracking (#62469)
Replace GitHub PR review approval/request-changes mechanism with commit
status tracking for code-review workflow. The workflow now:
- Posts "pending" status on PR open/sync/reopen events
- Updates to "success" status when /review comment triggers automated
review
- Removes decision-based approval logic and RESULT_START/RESULT_END
parsing
- Changes gh pr review --approve to --comment for final summary
Copy file name to clipboardExpand all lines: .github/workflows/opencode-review-runner.yml
+2-38Lines changed: 2 additions & 38 deletions
Original file line number
Diff line number
Diff line change
@@ -82,20 +82,14 @@ jobs:
82
82
83
83
## Final response format
84
84
- 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.
85
-
- 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 --approve --body "<summary>"
85
+
- 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 "<summary>"
86
86
- If issues found, submit a review with inline comments plus a comprehensive summary body. Use GitHub Reviews API to ensure comments are inline:
87
87
- Inline comment bodies may include GitHub suggested changes blocks when you can propose a precise patch.
88
88
- Prefer suggested changes for small, self-contained fixes (for example typos, trivial refactors, or narrowly scoped code corrections).
89
89
- Do not force suggested changes for broad, architectural, or multi-file issues; explain those normally.
90
90
- Build a JSON array of comments like: [{ "path": "<file>", "position": <diff_position>, "body": "..." }]
91
91
- Submit via: gh api repos/PLACEHOLDER_REPO/pulls/PLACEHOLDER_PR_NUMBER/reviews --input <json_file>
92
92
- The JSON file should contain: {"event":"REQUEST_CHANGES","body":"<summary>","comments":[...]}
93
-
- After publish your opinion, your final response MUST end with exactly one machine-readable result block in this format:
94
-
RESULT_START
95
-
{
96
-
"decision": "APPROVE" | "REQUEST_CHANGES"
97
-
}
98
-
RESULT_END
99
93
PROMPT
100
94
sed -i "s|PLACEHOLDER_REPO|${REPO}|g" /tmp/review_prompt.txt
101
95
sed -i "s|PLACEHOLDER_PR_NUMBER|${PR_NUMBER}|g" /tmp/review_prompt.txt
@@ -130,29 +124,6 @@ jobs:
130
124
failure_reason="OpenCode exited with status $status"
0 commit comments