{"version":"2.1.236","anchor":"uploading-a-repo-to-the-cloud-can-refuse-to-carry-uncommitte","canonical_anchor":"uploading-a-repo-to-the-cloud-can-refuse-to-carry-uncommitte","heading":"Uploading a repo to the cloud can refuse to carry uncommitted credential files","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/uploading-a-repo-to-the-cloud-can-refuse-to-carry-uncommitte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Uploading a repo to the cloud can refuse to carry uncommitted credential files\n\nUploading your repo to a cloud session aborts if uncommitted credential-looking files are present.\n\n**What**\n\nBefore packaging your checkout for a cloud session, uncommitted files with credential-looking names abort the upload. Bundling also gained a cheaper tier that packages only the branch you have checked out plus the current commit, instead of every branch.\n\n**Details**\n\n- The refusal is reported as an upload outcome of `uncommitted_credentials`, or `credential_check_failed` when git cannot report the working tree state.\n- The narrower bundle is reported as `current_branch_only`.\n- The credential refusal only applies when the caller asks for it.\n\n**Evidence**\n\n`uncommitted_credentials`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}