{"version":"2.1.242","anchor":"third-way-of-transferring-a-repository-to-a-cloud-session","canonical_anchor":"third-way-of-transferring-a-repository-to-a-cloud-session","heading":"Third way of transferring a repository to a cloud session","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/third-way-of-transferring-a-repository-to-a-cloud-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Third way of transferring a repository to a cloud session\n\nThere is a third way to get your repo into a cloud session, an overlay pinned to your head commit.\n\n**What**\n\nThe code that decides how to get your repository into a cloud session now has a third option alongside sending a bundle and pointing at a remote reference: an overlay pinned to your local head commit. Whether it is offered is fed in as an input from elsewhere.\n\n**Details**\n\n- The decision now also takes a maximum file count for folder-based transfer.\n\n**Evidence**\n\n`case \"overlay\":`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}