{"version":"2.1.236","anchor":"git-commands-run-for-cloud-seeding-can-no-longer-reach-the-n","canonical_anchor":"git-commands-run-for-cloud-seeding-can-no-longer-reach-the-n","heading":"Git commands run for cloud seeding can no longer reach the network or prompt","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/git-commands-run-for-cloud-seeding-can-no-longer-reach-the-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Git commands run for cloud seeding can no longer reach the network or prompt\n\nGit calls made while packaging your repo for the cloud cannot fetch or ask for passwords.\n\n**What**\n\nGit invocations on the path that packages your repository for a cloud session now run with no network protocols allowed (`GIT_ALLOW_PROTOCOL` set to \"none\"), lazy fetching off, terminal credential prompts off, and bare repositories only when explicitly named. A hang waiting for a password or a surprise fetch is no longer possible there.\n\n**Details**\n\n- The base argument list adds `safe.bareRepository=explicit`.\n- `git status --porcelain` now always states an untracked-file mode, passing `--untracked-files=normal` when it is not asking for all of them, rather than relying on whatever the repository configures.\n- A new failure message covers the case where untracked files exceed the size budget for seeding.\n\n**Evidence**\n\n`GIT_ALLOW_PROTOCOL: \"none\",`\n\n- Area: Cloud Sessions\n- Names: `GIT_ALLOW_PROTOCOL`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}