Preserve session diff availability across refreshes and forks#237
Conversation
Greptile SummaryThis PR introduces a three-state
Confidence Score: 5/5Safe to merge — the three-state diff model is correctly implemented end-to-end with no blocking issues. No P0 or P1 findings. The Unknown/Empty/Present model is consistently applied across the SQLite schema, fork SQL, DB read/write helpers, in-memory state, and UI visibility logic. Migration 061 conservatively handles binary/metadata-only diffs by leaving zero-line legacy rows as NULL rather than 0. The optimistic WHERE clause in No files require special attention. Reviews (12): Last reviewed commit: "Preserve session diff availability acros..." | Re-trigger Greptile |
210aa87 to
016adde
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
9219acb to
cd2fa4d
Compare
fc16796 to
99f4f55
Compare
- Track explicit empty, present, and unknown states while retaining known line totals when refreshes fail. - Reset source-derived diff metadata on forks and refresh the new worktree state. - Keep binary-only, metadata-only, and diagnostic diffs available through chat shortcuts and documentation.
|



Uh oh!
There was an error while loading. Please reload this page.