{"version":"2.1.296","anchor":"governed-git-warning-now-says-sources-keep-upstream-url-as-o","canonical_anchor":"custom-headers-check-function-replaced-and-git-subprocess-e","heading":"Cloud git setup keeps the plain upstream URL as origin and no longer passes GIT_CONFIG","tier":"notice","area":"Cloud Sessions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/governed-git-warning-now-says-sources-keep-upstream-url-as-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Cloud git setup keeps the plain upstream URL as origin and no longer passes GIT_CONFIG\n\nRepository setup now adds origin with the plain upstream URL instead of the credentialed one, and git subprocesses no longer inherit GIT_CONFIG\n\n**Unclear.** It is not confirmed that git remotes now actually behave the way the new warning says.\n\n**What**\n\nThese changes affect how Claude Code sets up git, the version-control tool, in a repository it prepares for a session.\n\n- Setup now adds the `origin` remote using `originURL` instead of `authURL`, so the URL that contains credentials is no longer written into the repository's git config. A new `originURL` field sits next to `authURL`.\n\n- For a governed git setup with a direct-upstreams list, the warning now says every source keeps its upstream URL as origin and no in-session fetches are routed through the git mount. Before, it said every source was reset to its upstream URL after preparation.\n\n- Git commands that Claude Code runs no longer inherit `GIT_CONFIG` from your environment. Any variable matching `GIT_CONFIG`, in any letter case, is removed. This joins the existing `GIT_CONFIG_GLOBAL=\/dev\/null` and the removal of `CLAUDE_CODE_SESSION_ACCESS_TOKEN`.\n\n- Separately, a new check looks at whether `ANTHROPIC_CUSTOM_HEADERS` holds a non-empty header and whether it matches a value from another source. What that check controls was not shown.\n\n**Why**\n\nThe credentialed URL is no longer stored in the repository's git config, and an inherited `GIT_CONFIG` can no longer change how Claude Code's git commands behave. Admins of governed git setups should expect sources to keep their upstream URL as origin rather than being reset after preparation.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}