{"version":"2.1.319","anchor":"git-commit-filetemplate-flags-added-to-a-pattern-list","canonical_anchor":"git-commit-filetemplate-flags-added-to-a-pattern-list","heading":"Command patterns now match git commit -F and -t right after commit","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/git-commit-filetemplate-flags-added-to-a-pattern-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Command patterns now match `git commit -F` and `-t` right after `commit`\n\nA list of command patterns now matches `git commit -F` and `git commit -t` when the flag comes straight after `commit`\n\n**Unclear.** What this pattern list controls, such as permission checks, is not stated.\n\n**What**\n\nClaude Code has a list of command patterns that now includes `git commit -F*` and `git commit -t*`. A flag is an option added to a command. `-F` reads the commit message from a file and `-t` uses a template file. Before, the list only matched these flags when another argument came before them.\n\n**Why**\n\nA command with `-F` straight after `commit` no longer slips past the patterns.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}