{"version":"2.1.281","anchor":"git-invocations-can-now-be-pinned-with-extra-c-config","canonical_anchor":"git-invocations-can-now-be-pinned-with-extra-c-config","heading":"Git invocations can now be 'pinned' with extra -c config","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/git-invocations-can-now-be-pinned-with-extra-c-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Git invocations can now be 'pinned' with extra -c config\n\nGit commands Claude Code runs now add extra -c config settings by default, in a new \"pinned\" mode\n\n**Unclear.** The finding does not list which settings are added or which git calls use a mode other than pinned.\n\n**What**\n\nWhen Claude Code builds a git command, it can now pass extra one-off settings using git's `-c key=value` option. This option changes a git setting for that single command only and leaves your saved configuration alone. The mode that adds these settings is called `\"pinned\"`, and it is the default.\n\n**Why**\n\nGit commands run by Claude Code can now behave the same way regardless of some of your local git settings."}