What
Hooks are commands you set up to run automatically at certain points, for example before a tool runs. Some hooks are tied to a particular project folder. Such a hook now does not run when both of these are true:
- that folder is no longer a working copy (a checked-out copy of a repository) this session can use
- the session's own folder is not in one either
It fails with a warning instead.
Why
This most likely affects sessions that use several working copies or several project folders at once. A hook from a folder that has gone away now stops with a warning.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
How a hook becomes tied to a particular project folder is not known.