More forms of tampered or redirected git state are detected, each with a specific reason.
What's wrong with this entry?
Checking a repository now reports a specific reason when its git directory looks tampered with, rather than only catching one narrow case, so more forms of redirected or borrowed git state are caught.
- Reasons reported include an old-format git directory, a redirected common directory, reftable storage, borrowed objects, a suspicious git directory and too many include directives.
- Object-store stamps are recorded as part of the check.
misplaced: "borrowed_objects"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.247
Worktree cleanliness checks and removal use the same pinned config, and removal aborts when unsure
Both mention safety
-
v2.1.247
Git metadata files are read with a size cap instead of being slurped whole
Both mention safety
-
v2.1.239
Wider Unicode normalisation of untrusted text
Both mention safety