{"version":"2.1.283","anchor":"git-tlsssl-settings-passed-through-git-config-key-n-env-var","canonical_anchor":"git-tlsssl-settings-passed-through-git-config-key-n-env-var","heading":"Git TLS settings set through environment variables now apply to Claude Code's own git commands","tier":"use","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/git-tlsssl-settings-passed-through-git-config-key-n-env-var","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Git TLS settings set through environment variables now apply to Claude Code's own git commands\n\nCertificate and TLS settings passed through GIT_CONFIG_KEY_n and GIT_CONFIG_VALUE_n now reach git commands Claude Code runs itself\n\n**Unclear.** Which of Claude Code's internal git commands besides the reset receive these settings is not fully known.\n\n**What**\n\nGit can take config settings from environment variables: `GIT_CONFIG_COUNT`, `GIT_CONFIG_KEY_n` and `GIT_CONFIG_VALUE_n`. When you set TLS settings this way, Claude Code now passes them on to the git commands it runs itself, such as a `reset --hard`. TLS is the encryption used for secure connections. Only `http` settings like these are passed on:\n\n- `sslcainfo` and `sslcapath`, the certificate authority bundle\n\n- `sslverify`\n\n- `sslversion`, `sslcipherlist` and `sslbackend`\n\n- `schannelcheckrevoke` and `schannelusesslcainfo`\n\n- `pinnedpubkey`, certificate pinning\n\n- `proxysslcainfo`\n\nBefore, those internal git commands ran without these settings.\n\n**Why**\n\nIf you are behind a corporate proxy with a custom certificate bundle set through environment variables, Claude Code's own git operations could fail certificate checks. They now use the same settings as your own git commands.\n\n- Area: Git\n- Names: `GIT_CONFIG_COUNT`, `GIT_CONFIG_KEY_n`, `GIT_CONFIG_VALUE_n`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}