{"version":"2.1.283","anchor":"governed-git-mount-push-url-check-no-longer-rejects-every-ur","canonical_anchor":"governed-git-mount-push-url-check-no-longer-rejects-every-ur","heading":"Cloud sessions can now honour a valid git mount push URL","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/governed-git-mount-push-url-check-no-longer-rejects-every-ur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud sessions can now honour a valid git mount push URL\n\nA check that wrongly rejected every git mount push URL in cloud sessions is fixed, so valid URLs can now redirect pushes\n\n**Unclear.** The added check was not identified, so it is unclear which other URLs are now refused.\n\n**What**\n\nIn cloud and runner sessions, a work item's git setup can give a separate push URL, called the git mount, where pushes should go. Claude Code checks that URL before using it. The check used to look at the plain text rather than the parsed URL, so every URL counted as unusable. It now checks the parsed URL properly, and also runs one extra check. When a URL is rejected, pushes still go to the upstream remote and a warning is printed.\n\n**Why**\n\nIn practice, pushing through the git mount probably never worked before, and valid push URLs should now be used.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}