{"version":"2.1.321","anchor":"stop-hooks-skipped-when-no-git-repo","canonical_anchor":"stop-hooks-skipped-when-no-git-repo","heading":"Some Stop hooks no longer run outside a git repository","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/stop-hooks-skipped-when-no-git-repo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Some Stop hooks no longer run outside a git repository\n\nCertain Stop hooks are now skipped when there is no git repository in the current folder or any folder above it\n\n**Unclear.** Which Stop hooks are affected is not stated; it may be only some built-in ones rather than hooks you write.\n\n**What**\n\nA Stop hook is a script you can configure to run when Claude finishes responding. Certain Stop hooks are now skipped when Claude Code finds no `.git` folder or `HEAD` file in the current folder or any folder above it, which means you are not inside a git repository.\n\nWhen this happens, the debug log records \"no .git or HEAD at or above\".\n\n**Why**\n\nOutside a git repository, some Stop hooks can now quietly not run. If a hook seems to be ignored, check the debug log for that line.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}