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. What does this mean for users in the public preview?įor current users, we encourage you to migrate to GitHub Codespaces with us. 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. However, after the GitHub-native experience was released, we started hearing that the two distinct experiences were causing confusion amongst our users.
Since GitHub is the home of 50M developers, it made sense to partner with them to address this feedback.
Why is the service moving?ĭuring the preview we’ve 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. If you’re 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. Today, we’d like to share some news regarding this partnership: Visual Studio Codespaces will be consolidating into GitHub Codespaces. 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. We’ve also shipped dozens of enhancements, adjusted to better align with your expectations, and amassed feedback to help inform our roadmap. Since then, we’ve seen incredible validation and excitement about codespaces and the scenarios they enable. At the last Ignite, we announced the public preview of Visual Studio Codespaces and shared our vision for cloud-powered development environments that would enable developers to work from anywhere and on any platform.