{"id":230507,"date":"2020-09-04T09:00:49","date_gmt":"2020-09-04T16:00:49","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=230507"},"modified":"2020-11-02T09:37:55","modified_gmt":"2020-11-02T17:37:55","slug":"visual-studio-codespaces-is-consolidating-into-github-codespaces","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/visual-studio-codespaces-is-consolidating-into-github-codespaces\/","title":{"rendered":"Visual Studio Codespaces is consolidating into GitHub Codespaces"},"content":{"rendered":"

At the last Ignite, we announced the public preview of Visual Studio Codespaces<\/a> and shared our vision for cloud-powered development environments that would enable developers to work from anywhere and on any platform. Since then, we\u2019ve seen incredible validation and excitement about codespaces and the scenarios they enable. We’ve also shipped dozens of enhancements<\/a>, adjusted to better align with your expectations, and amassed feedback to help inform our roadmap. A key piece of this roadmap was partnering with our friends at GitHub to provide a native experience using the same service that powers Visual Studio Codespaces. Today, we\u2019d like to share some news regarding this partnership: Visual Studio Codespaces will be consolidating into GitHub Codespaces<\/a>.<\/p>\n

If you\u2019re an existing Visual Studio Codespaces user, you can start your transition to GitHub Codespaces now and the current Azure offering will be retired in February 2021.<\/p>\n

Why is the service moving?<\/h2>\n

During the preview we\u2019ve learned that transitioning from a repository to a codespace is the most critical piece of your workflow and the vast majority of you preferred a richly integrated, native, one-click experience. Since GitHub is the home of 50M developers, it made sense to partner with them to address this feedback. However, after the GitHub-native experience was released, we started hearing that the two distinct experiences were causing confusion amongst our users.<\/p>\n

We believe that by consolidating the current Codespaces experiences into one, we can eliminate confusion, simplify the experience for everyone, and make more rapid progress to address customer feedback.<\/p>\n

What does this mean for users in the public preview?<\/h2>\n

For current users, we encourage you to migrate to GitHub Codespaces with us. Since GitHub Codespaces is still in a limited public beta, we will be working to get you added to the beta as quickly as possible. The next time you connect to a codespace through the portal<\/a> or Visual Studio Code, we\u2019ll prompt you to submit the preferred GitHub account you\u2019d like to be added to the beta. Every Azure subscription owner with a Visual Studio Codespaces plan will also receive an email requesting their preferred GitHub account.<\/p>\n

While GitHub Codespaces provides an optimized creation experience for GitHub repositories, you can still utilize Git repositories hosted elsewhere (e.g Azure Repos, Bitbucket) with a few extra configuration steps. Check out our FAQs<\/a> for more details.<\/p>\n

What does this mean for users in the private preview?<\/h2>\n

The private preview of Visual Studio 2019 support for Windows-based Codespaces will also move to GitHub. Users currently in the private preview will be invited to continue the private preview on GitHub as soon as it\u2019s available in the next few weeks. All new users accepted to try Windows Codespaces and Visual Studio will onboard directly to the private preview on GitHub. Stay tuned for more details.<\/p>\n

What happens next?<\/h2>\n

We want to ensure you have ample time to migrate so existing users can continue accessing your codespaces via the current portal<\/a> beyond the start of GitHub general availability.<\/p>\n

Here\u2019s a short summary of our timeline:<\/p>\n