feat(vscode): post inline comments to GitHub pull requests - #14025
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Incremental review of commit Files Reviewed (42 files)
Previous Review Summaries (6 snapshots, latest commit 5c98157)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 5c98157)Status: No Issues Found | Recommendation: Merge Incremental review of commit Files Reviewed (1 file)
Previous review (commit f6d18b2)Status: No Issues Found | Recommendation: Merge Incremental review of commit Files Reviewed (2 files)
Previous review (commit d718369)Status: No Issues Found | Recommendation: Merge Incremental review of commit Files Reviewed (2 files)
Previous review (commit f5f75ea)Status: 1 Issue Found | Recommendation: Address before merge Overview
Incremental review of commit Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Previous review (commit cdffd39)Status: 1 Issue Found | Recommendation: Address before merge Overview
Note: the PR description embeds screenshots as HTML The previous findings (retry loop, draft identity, silent batch failure, annotation retention, dead Issue Details (click to expand)WARNING
Files Reviewed (82 files)
Previous reviewStatus: 6 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
WARNING
SUGGESTION
Files Reviewed (82 files)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
…ote-diff-comments
…ote-diff-comments
What Problem This Solves
The diff viewers in Changes and Agent Manager could only create local agent comments. Reviewing a checked-out pull request meant leaving Kilo to write inline PR comments on GitHub, and there was no clear way to tell local feedback apart from a published GitHub comment.
Why This Change Was Made
PRReviewActionswrite path so a comment is validated against the current PR revision before it is published.Entersends to Kilo,Cmd/Ctrl+Entersaves locally, and a secondCmd/Ctrl+Enterin the review sends all comments to Kilo. Publishing to GitHub always needs an explicit click.User Impact
Send all to chat (N)andSend N to GitHub #PR. Only the chat action shows theCmd+Entershortcut.Evidence
Screenshots from an isolated VS Code self-test against a private disposable PR:
Automated checks:
bun run typecheck,bun run lint,bun run compilebun run knip,bun run check-kilocode-change, source-link and table-padding guardsSelf-test flows verified:
Cmd+Entersaves, plainEntersends to Kilo, a secondCmd+Entersends all comments to Kilo without touching GitHub, and the explicit GitHub button posts to the PR inline comment endpoint.