{"version":"2.1.251","anchor":"clearer-error-when-a-cloud-session-cannot-clone-from-gitlab-","canonical_anchor":"clearer-error-when-a-cloud-session-cannot-clone-from-gitlab-","heading":"Clearer error when a cloud session cannot clone from GitLab or Bitbucket","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/clearer-error-when-a-cloud-session-cannot-clone-from-gitlab-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Clearer error when a cloud session cannot clone from GitLab or Bitbucket\n\nCloud sessions now say plainly that GitLab and Bitbucket repos can't be cloned yet.\n\n**What**\n\nTrying to move a GitLab or Bitbucket repo into a cloud session now says plainly that cloud sessions cannot clone from that host yet, instead of only pointing you at GitHub setup steps.\n\n**Details**\n\n- The message names the detected host rather than assuming GitHub.\n- It appears on the non-GitHub path when no usable git source is available for the repo.\n\n**Evidence**\n\n`Cloud sessions can't clone from ${vn} yet`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}