Repository navigation
[Feature] Add an All changes tab showing a worktree's diff as one view - #43
Merged
Merged
Conversation
KieranP
force-pushed
the
unnified-diff
branch
from
November 14, 2026 10:56
f35a323 to
17dedf0
Compare
KieranP
force-pushed
the
unnified-diff
branch
16 times, most recently
from
November 18, 2026 22:50
e9cf884 to
5ff7cb1
Compare
KieranP
enabled auto-merge (squash)
November 18, 2026 22:51
KieranP
disabled auto-merge
November 18, 2026 23:04
Reviewing what an agent changed across twenty files meant opening twenty file tabs and stepping through them one at a time. The All changes tab shows every file in the Changes list, in its order and scope, as one scrolling list of diffs with review comments on their lines. Each file is its own view, a header over its Unified or Split diff, and only the files near the screen are read and built. - Open it beside the Changes filter or with tabs open-all-changes - Step, find, fold, collapse and comment across files as in a file tab - Draw Unified and Split, in file tabs too, on one scroller over a canvas - Batch each read's git runs: 300 modified files read in 0.08 s, not 3.3 s Closes #42 Co-Authored-By: Claude Opus 5.5 <[email protected]>
KieranP
force-pushed
the
unnified-diff
branch
from
November 18, 2026 23:11
5ff7cb1 to
e77b8f4
Compare
KieranP
enabled auto-merge (squash)
November 18, 2026 23:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #42
Reviewing what an agent changed across twenty files meant opening twenty file tabs and stepping through them one by one. The All changes tab shows every file in the Changes list, in its order and Modified/Branch scope, as one scrolling diff with review comments on its lines. It follows the owner's picks from the mockups on the issue.
tabs open-all-changes; a Changes row click shows the tab at that file, and the file at the top lights its rowtabs step/findand the rotor work on it; headers, folds and notices sit in row gaps, hosted only near the screenreview addreaches the tabDocs/design/files/all-changes-tab.md; status and owner feedback:PROGRESS.mdMemory, measured over 1,802 changed files plus 191 added: 191 MB against 78 MB with the tab shut (1.43 GB before hosting only what is near the screen).
Known limits, queued in
PROGRESS.md: in Split, find, the arrows and the rotor skip the rows of added and removed files, and Split is two locked scroll views, to be reworked as one; every file's rows are still read and held, capped at 200,000.Tests:
make test, 2,999 passing;swift format lint --strictandswiftlintclean.🤖 Generated with Claude Code