Revert per-repo changes - #6286
intentionally-left-nil wants to merge 3 commits into
Conversation
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (24 files)
Fix these issues in Kilo Cloud Previous Review Summaries (2 snapshots, latest commit 582517d)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 582517d)Status: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe only change since the previous review is an import reformatting in Overview
Issue Details (click to expand)WARNING
Incremental Changes (1 file)
Files Reviewed (29 files)
Fix these issues in Kilo Cloud Previous review (commit a483752)Status: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe revert itself is complete and self-consistent (no dangling references to the removed feature), but the new Overview
Issue Details (click to expand)WARNING
Files Reviewed (29 files)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
pandemicsyn
left a comment
There was a problem hiding this comment.
pre-approving but might be worth breaking up this change like the bot says. Since we do canary rollouts the migration will land first and we'll have a window of time where both versions are live.
Instead of having a single UI for all per-repo changes, we are going to leave the existing code alone for now. There already is the ability to turn code reviewers off per-repo and a bigger feature ended up having too much scope creep
582517d to
1f9c61f
Compare
Instead of having a single UI for all per-repo changes, we are going to leave the existing code alone for now. There already is the ability to turn code reviewers off per-repo
and a bigger feature ended up having too much scope creep