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
After #263, #264 and #265, "Use" restores an object's own folder as of a past result (doc/protocol.md section 5). Each Codex review found another case where a file and a folder change places. Per master on 2026-11-15, the remaining ones are tracked here, not fixed before 0.3.0: they are not normal use, which is the merge standard.
Covered and tested (entryActions.test.ts, the Use test with "a file added since")
a file the folder did not hold then, committed or not, is removed;
an object folded inside since (a folder with its own object.json) is left as it is;
a historical file where a folder stands now, when the change's deletions empty that folder;
A historical file where a non-empty folder holding files no commit tracks stands. rmdir refuses, so the Use fails with an error and nothing is half written, since the write queue fails the change.
A path in the folder that is a link now or was then: the link check refuses it as no path of the project.
A case-only rename between the result and now (Notes.md / notes.md) on a case-insensitive disk.
A receipt and its output across such a swap: ordering is deletions, then receipts, then outputs, but this is untested.
To do
Write each as a failing test first, and fix it with git's own semantics as the model (a checkout of the object's tree, dir.c remove_path, unpack-trees' "would be overwritten" check).
Activity