{"version":"2.1.283","anchor":"git-tls-ca-config-now-also-set-per-url-and-per-origin","canonical_anchor":"git-tls-ca-config-now-also-set-per-url-and-per-origin","heading":"Git certificate settings can now be written for a specific site and address","tier":"internal","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/git-tls-ca-config-now-also-set-per-url-and-per-origin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Git certificate settings can now be written for a specific site and address\n\nWhen passing certificate settings to git, Claude Code can now set the trusted certificate file per site and per full address, not only globally\n\n**Unclear.** It is not clear where this is used, and it may be a renamed internal rather than a change you would notice.\n\n**What**\n\nClaude Code can pass certificate settings to git, so that git trusts a certificate authority (the organisation that vouches for a site's security certificate) chosen by whoever runs your setup. Given an address, it can now produce three versions of git's `http.sslCAInfo` setting: a general one, one for that site, and one for that exact address.\n\n**Why**\n\nIn git, a setting for a specific address overrides a broader one, so this may fix custom certificates being ignored for some git remotes.\n\n- Area: Git\n- Names: `http.sslCAInfo`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}