{"version":"2.1.290","anchor":"git-command-line-config-warning-messages-reworded","canonical_anchor":"git-command-line-config-warning-messages-reworded","heading":"Shorter warning when git is run with hooks or include paths on the command line","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/git-command-line-config-warning-messages-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Shorter warning when git is run with hooks or include paths on the command line\n\nThe permission warning for git commands that set core.hooksPath or an include path on the command line is now shorter\n\n**What**\n\nWhen Claude wants to run git with `core.hooksPath` or an include path set on the command line, Claude Code asks you first. The reason it shows is now shorter, for example \"it runs git with core.hooksPath set on the command line\". The old wording also explained that this turns the repository's own hooks back on, and that these run files the session writes.\n\n**Why**\n\nThe permission prompt now gives less explanation. The underlying risk is unchanged: hooks set this way can run files created during the session.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}