You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
New FeaturesKind: in v2.1.251,
New FeaturesSection of the release
What
Trying 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.
Details
The message names the detected host rather than assuming GitHub.
It appears on the non-GitHub path when no usable git source is available for the repo.
Evidence
Cloud sessions can't clone from ${vn} yet
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
