You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Shape one revision-aware workflow across Changes, Compare and impact review #444
Keep the complete change footprint, the relevant code structure, and before/after source in one investigation. For f2544ff^..f2544ff, Git and Compare show 15 changed paths; Changes shows 11, excluding three JSON and one snapshot path (397 added lines). Some excluded paths carry model behavior. Changes already has windows, Touched/Net, commit rail and chunk diffs; Compare already has historical code and full-file inventory.
First slice
Keep every changed path discoverable without making up structural metrics for unparsed paths. Mark why a row has no metric. Preserve repo, revisions/side, selection and range across Changes → Compare → historical source → Back.
Then shape an unchanged-neighbor view and responsibility movement with source evidence. For this refactor, individual functions got simpler while much of the aggregate complexity moved; never turn a delta into a blanket quality or equivalence verdict.
Evaluate interactive batch and flow-signature work later (progress, cancellation and coverage), reusing the existing Product Grid task for batch startup and existing Compare/backend hooks. No arbitrary historical whole-program tracing in the first slice.
Prove parity with Git on the 15-file fixture plus a metadata-only change. Preserve Touched/Net semantics and the working In repo/diff behavior.
Activity