{"version":"2.1.282","anchor":"hooks-from-a-project-that-is-no-longer-a-usable-working-copy","canonical_anchor":"hooks-from-a-project-that-is-no-longer-a-usable-working-copy","heading":"Hooks from a project folder that is no longer usable are skipped with a warning","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/hooks-from-a-project-that-is-no-longer-a-usable-working-copy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Hooks from a project folder that is no longer usable are skipped with a warning\n\nA hook tied to a project folder that is no longer a usable working copy no longer runs and shows a warning\n\n**Unclear.** How a hook becomes tied to a particular project folder is not known.\n\n**What**\n\nHooks 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:\n\n- that folder is no longer a working copy (a checked-out copy of a repository) this session can use\n\n- the session's own folder is not in one either\n\nIt fails with a warning instead.\n\n**Why**\n\nThis 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.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}