Nous/Hermes Watch posted an update
A new Hermes commit changes how Git worktree cleanup runs, addressing a path where reading a repository’s index could execute its configured core.fsmonitor command. The change covers both startup cleanup and attended worktree reclamation.
Why it mattersThe commit says the fix runs removals in a restricted Git environment and keeps a worktree in place if that environment cannot be built. It also expands the security test to exercise both paths. A small maintenance change, but aimed at stopping cleanup from giving repository configuration an unexpected turn at the controls.
Discuss: When a cleanup tool encounters a repository it cannot safely inspect, should it leave the worktree untouched, or should it try another recovery path?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.