feat(vscode): add PR merge readiness controls - #13953
Conversation
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (10 files)
Fix these issues in Kilo Cloud Previous Review Summaries (8 snapshots, latest commit 05684c1)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 05684c1)Status: No Issues Found | Recommendation: Merge Files Reviewed (5 files)
Previous review (commit 4f430d2)Status: No Issues Found | Recommendation: Merge Files Reviewed (20 files)
Previous review (commit 1b7a2ac)Status: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Previous review (commit b057881)Status: No Issues Found | Recommendation: Merge Files Reviewed (22 files)
Previous review (commit fb55540)Status: No Issues Found | Recommendation: Merge Files Reviewed (1 files)
Previous review (commit 5c2df10)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (3 files)
Fix these issues in Kilo Cloud Previous review (commit 24c3155)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (8 files)
Fix these issues in Kilo Cloud Previous review (commit 3c04a86)Status: 6 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (52 files)
Reviewed by grok-4.6 · Input: 220.3K · Output: 23.3K · Cached: 2.4M Review guidance: REVIEW.md from base branch |
|
a non-blocking nit (just consistency with similar yet different function before that) and files conflicts to solve. I would approve otherwise. |
Verify workflow behavior against #13951, #13953, and #13780; preserve sandbox-specific Git approval requirements. Check saved-file omissions against Kilo-Org/cloud#5813 and folder controls against cloud#5948.
What Problem This Solves
The Agent Manager PR panel did not provide a compact view of approval status, merge readiness, conflicts, branch updates, or merge actions. Users had to leave the panel to understand whether a PR could merge or what action was needed next.
Why This Change Was Made
This adds a GitHub-backed merge readiness surface while keeping GitHub responsible for remote mergeability, branch updates, merge methods, and auto-merge. Conflict file paths are loaded on demand with
git merge-treewithout changing the worktree, index, or stash.User Impact
Fix with Kilofor conflicts.Evidence
Merge-ready state
Merge method menu
Merging blocked with auto-merge
Behind branch and Update branch
Conflict state
Validation
bun run typecheckbun run bundlebun run test:unit, 5378 passed, 2 skippedgit merge-treeconflict detection test with divergent commits