{"version":"2.1.282","anchor":"git-config-written-for-git-bundles-values-are-now-quoted-an","canonical_anchor":"git-config-written-for-git-bundles-values-are-now-quoted-an","heading":"Generated git config now quotes values and allows keys without values","tier":"internal","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/git-config-written-for-git-bundles-values-are-now-quoted-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Generated git config now quotes values and allows keys without values\n\nWhen Claude Code writes a git config file for a copied repository, it now quotes values and writes valueless keys on their own\n\n**Unclear.** Which Claude Code feature writes this config, and where the second group of entries comes from, is not known.\n\n**What**\n\nClaude Code sometimes writes a git configuration file for a copy of a repository. Values in the `[core]` section used to be written as-is. Now:\n\n- values are quoted where needed\n\n- keys with no value are written on their own\n\n- a second group of entries is written in double quotes, with backslashes and double quotes escaped\n\n**Why**\n\nConfig values that contain special characters should no longer break the copied repository's configuration.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}