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
Sparse: a stop's materialize can delete the user's copy of an out-of-view file the old tree already tracks #256
Found reviewing #251 (fix for #248); predates it, reproduced by the reviewer. On a sparse checkout, a merge/pick/rebase stop's materialize can remove or overwrite the user's local copy of an out-of-view path the old tree already tracks (the untracked-file guard deliberately skips paths the old tree tracks). Needs: refuse (or preserve) when the on-disk copy differs from the tracked content, instead of deleting it; tests for merge, pick, rebase and abort. Related to the abort-delete issue filed from #252.
Activity
fix(repo): refuse an abort whose kept file blocks a directory, cover …
fix(repo): abort overwrites only the stopped tree's own bytes; stream…
fix(repo): keep a symlink at a recorded protected path; index skipped…
fix(repo): private abort keeps symlinks, stop deletes before conflict…
fix(repo): a restore never writes through a symlink (ref #255 #256)
fix(repo): abort discards an edited conflict, reports retained plaint…
fix(repo): never delete through a symlinked parent; treat ENOTDIR as …
test(repo): pin lstat and under_symlink semantics (ref #255 #256)
fix(repo): delete or overwrite only the stop's own files on materiali…