{"version":"2.1.299","anchor":"git-commit-parsing-excludes-m-from-value-taking-flags","canonical_anchor":"git-commit-parsing-excludes-m-from-value-taking-flags","heading":"Git command parsing no longer treats -m as taking a value","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/git-commit-parsing-excludes-m-from-value-taking-flags","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Git command parsing no longer treats `-m` as taking a value\n\nWhen reading git commands, Claude Code no longer counts `-m` among the options that take a value\n\n**Unclear.** It is not clear which git commands, if any, now get a different permission decision because of this.\n\n**What**\n\nClaude Code reads git commands to work out their parts. It no longer treats `-m` as an option that is followed by a value. The internal lists of git options that take values were also reorganised.\n\n**Why**\n\nThis may change how some shell commands that use git are sorted when Claude Code decides whether they need your permission to run.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}