feat(code-review): pass confirmed=true when posting inline comments
The inline-comment MCP tool now requires confirmed=true to post (otherwise calls are buffered). This structurally prevents subagent test/probe comments from reaching customer PRs — subagents that inherit the tool and probe it without confirmed=true see their calls harmlessly buffered. Backward compatible: against older versions of claude-code-action that don't know the param, the extra field is ignored and the comment posts as before.
This commit is contained in:
parent
6f049b620f
commit
db8834ba1d
1 changed files with 1 additions and 1 deletions
|
|
@ -68,7 +68,7 @@ Note: Still review Claude generated PR's.
|
|||
|
||||
8. Create a list of all comments that you plan on leaving. This is only for you to make sure you are comfortable with the comments. Do not post this list anywhere.
|
||||
|
||||
9. Post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`. For each comment:
|
||||
9. Post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment` with `confirmed: true`. For each comment:
|
||||
- Provide a brief description of the issue
|
||||
- For small, self-contained fixes, include a committable suggestion block
|
||||
- For larger fixes (6+ lines, structural changes, or changes spanning multiple locations), describe the issue and suggested fix without a suggestion block
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue