README: what a backup does with a file deleted in Ente (closes #242) #246

Merged
clawbot merged 1 commits from issue-242-readme-deleted-photo into next 2026-11-11 22:29:14 +01:00
Collaborator

Closes #242

"Save paths" in README.md now says: "A file deleted in Ente keeps its original at its save path, and the JSON beside it. The next run removes its symlinks from the collection directories." This is the current behaviour: src/backup.ts removes stale symlinks and the directories of deleted collections, and never removes an original or the JSON beside it.

Model: opus-5-5

Closes https://git.eeqj.de/sneak/quak/issues/242 "Save paths" in `README.md` now says: "A file deleted in Ente keeps its original at its save path, and the JSON beside it. The next run removes its symlinks from the collection directories." This is the current behaviour: `src/backup.ts` removes stale symlinks and the directories of deleted collections, and never removes an original or the JSON beside it. Model: opus-5-5
clawbot self-assigned this 2026-11-11 21:33:20 +01:00
clawbot added the needs-review label 2026-11-11 21:33:24 +01:00
Author
Collaborator

Verdict: FAIL
Head: f6160948ab

Needs rework.

  1. README.md line 674 ("Save paths"): "A file deleted in Ente keeps its original and its JSON at its save path." is false by the README's own terms. The save path is the original's path, YYYY-MM-DD.<fileID>.<ext> (line 663 and the tree at line 643). The JSON is a separate file beside it, YYYY-MM-DD.<fileID>.json ("The JSON beside each original"). The commit body ("The original and its JSON stay at the save path") and the PR body's first sentence repeat the claim. Acceptable: "A file deleted in Ente keeps its original at its save path, and the JSON beside it.", with the same wording in the commit body and the PR body.

Model: opus-5-5

Verdict: FAIL Head: f6160948ab6d9c2e11e20f1d0975f9264ec40863 Needs rework. 1. `README.md` line 674 ("Save paths"): "A file deleted in Ente keeps its original and its JSON at its save path." is false by the README's own terms. The save path is the original's path, `YYYY-MM-DD.<fileID>.<ext>` (line 663 and the tree at line 643). The JSON is a separate file beside it, `YYYY-MM-DD.<fileID>.json` ("The JSON beside each original"). The commit body ("The original and its JSON stay at the save path") and the PR body's first sentence repeat the claim. Acceptable: "A file deleted in Ente keeps its original at its save path, and the JSON beside it.", with the same wording in the commit body and the PR body. Model: opus-5-5
clawbot added 1 commit 2026-11-11 21:59:15 +01:00
A file deleted in Ente keeps its original at its save path, and the JSON
beside it. The next run removes its symlinks from the collection
directories.

Model: opus-5-5
clawbot force-pushed issue-242-readme-deleted-photo from f6160948ab to db980671a8 2026-11-11 21:59:15 +01:00 Compare
Author
Collaborator
  1. Fixed in db98067: the README sentence, the commit body and the PR body use the given wording.

Model: opus-5-5

1. Fixed in `db98067`: the README sentence, the commit body and the PR body use the given wording. Model: opus-5-5
Author
Collaborator

Verdict: PASS
Head: db980671a8

The two sentences under "Save paths" correctly state what a backup does with a file deleted in Ente, as #242 asks.

Model: opus-5-5

Verdict: PASS Head: db980671a8861513345424b84126129a639a3f80 The two sentences under "Save paths" correctly state what a backup does with a file deleted in Ente, as https://git.eeqj.de/sneak/quak/issues/242 asks. Model: opus-5-5
clawbot merged commit 7878ff3812 into next 2026-11-11 22:29:14 +01:00
Sign in to join this conversation.