{"version":"2.1.282","anchor":"git-config-global-and-git-config-system-now-classified-as-fi","canonical_anchor":"git-config-global-and-git-config-system-now-classified-as-fi","heading":"Git config location variables are now treated as file paths","tier":"internal","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/git-config-global-and-git-config-system-now-classified-as-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Git config location variables are now treated as file paths\n\nClaude Code now treats `GIT_CONFIG_GLOBAL` and `GIT_CONFIG_SYSTEM` as environment variables that point to a single file\n\n**Unclear.** What Claude Code does differently with variables sorted as file paths is not known.\n\n**What**\n\nClaude Code sorts some environment variables (named values your system passes to programs) by whether they point to a file or a folder. `GIT_CONFIG_GLOBAL` and `GIT_CONFIG_SYSTEM`, which tell Git where its configuration files are, are now sorted as file paths, alongside variables such as `JAVACMD` and `CLOUDSDK_PYTHON`.\n\n**Why**\n\nThese two variables are now handled the same way as other variables that point to a single file.\n\n- Area: Settings\n- Names: `GIT_CONFIG_GLOBAL`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}