{"version":"2.1.238","anchor":"clearer-error-when-a-repo-cannot-seed-a-cloud-session","canonical_anchor":"clearer-error-when-a-repo-cannot-seed-a-cloud-session","heading":"Clearer error when a repo cannot seed a cloud session","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/clearer-error-when-a-repo-cannot-seed-a-cloud-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Clearer error when a repo cannot seed a cloud session\n\nFailing to seed a cloud session now names what is missing: a branch, tag or checkout.\n\n**What**\n\nUploading a repository to a cloud session used to fail with a message saying the repository has no commits. It now names what is actually missing: a local branch, tag, or checkout to copy from.\n\n**Details**\n\n- The previous wording is gone from this build.\n\n**Evidence**\n\n`Repository has no local branch, tag, or checkout to seed from yet`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}