{"version":"2.1.321","anchor":"git-config-keys-formatoutputdirectory-and-formatsuffix-tre","canonical_anchor":"git-config-keys-formatoutputdirectory-and-formatsuffix-tre","heading":"Two more git settings are treated as dangerous","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/git-config-keys-formatoutputdirectory-and-formatsuffix-tre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Two more git settings are treated as dangerous\n\nClaude Code now treats the git settings format.outputdirectory and format.suffix as dangerous, like core.worktree and core.bare\n\n**What**\n\nGit is the version-control tool many projects use. Claude Code keeps a list of git settings it treats as dangerous. That list now also includes:\n\n- `format.outputdirectory`\n\n- `format.suffix`\n\nThey sit alongside `core.worktree` and `core.bare`.\n\n**Why**\n\nThese settings can make git write files outside the project, so a project's own settings are less able to do that unnoticed.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}