You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original version of the Continue Working On feature shipped over a year ago and allows you to continue a "virtual"/"serverless" GitHub or Azure Repos repository in a different context such as a codespace, desktop clone, or container. With #141293 we have been working to 1. expand Continue Working On to make it easy to work on the same repo across desktop and web VS Code instances and 2. integrate Edit Sessions into Continue Working On transitions so that your uncommitted changes come with you whenever you switch contexts.
Last milestone, we added support for resuming edit sessions when you Continue Working On a repository in VS Code for the Web (vscode.dev and GitHub Codespaces). This milestone, we also added support for resuming edit sessions when you Continue Working On a repository in desktop VS Code.
Ensure you have the latest VS Code Insiders build installed.
Ensure you have "workbench.experimental.editSessions.enabled": true in your settings on both insiders.vscode.dev and desktop VS Code. This is enabled by default in Insiders at the moment.
Also ensure you have "workbench.experimental.editSessions.autoResume": "onReload" in your settings on both insiders.vscode.dev and desktop VS Code
Run Edit Sessions: Sign In and Codespaces: Sign In from the command palette in your settings on both insiders.vscode.dev and desktop VS Code
Test plan:
From the remote indicator or command palette, choose the Continue Working On item.
When you are in a GitHub repository in https://insiders.vscode.dev, ensure that you see the following options for Continue Working On:
Create some uncommitted changes in the source workspace, and test that your uncommitted changes come with you when using Continue Working On in the following scenarios:
When in desktop VS Code, use the Open Remote Repository action from the remote indicator or command palette to browse a GitHub or Azure Repos repository without cloning:
When you are in a virtual GitHub repository on desktop, ensure that you see the following options for Continue Working On:
Create some uncommitted changes in the source workspace, and test that your uncommitted changes come with you when using Continue Working On in the following scenarios:
Refs #156833
Authors: @joyceerhl
Complexity: 5
Create Issue
The original version of the Continue Working On feature shipped over a year ago and allows you to continue a "virtual"/"serverless" GitHub or Azure Repos repository in a different context such as a codespace, desktop clone, or container. With #141293 we have been working to 1. expand Continue Working On to make it easy to work on the same repo across desktop and web VS Code instances and 2. integrate Edit Sessions into Continue Working On transitions so that your uncommitted changes come with you whenever you switch contexts.
Last milestone, we added support for resuming edit sessions when you Continue Working On a repository in VS Code for the Web (vscode.dev and GitHub Codespaces). This milestone, we also added support for resuming edit sessions when you Continue Working On a repository in desktop VS Code.
Pre-requisites:
"workbench.experimental.editSessions.enabled": true
in your settings on both insiders.vscode.dev and desktop VS Code. This is enabled by default in Insiders at the moment."workbench.experimental.editSessions.autoResume": "onReload"
in your settings on both insiders.vscode.dev and desktop VS CodeEdit Sessions: Sign In
andCodespaces: Sign In
from the command palette in your settings on both insiders.vscode.dev and desktop VS CodeTest plan:
From the remote indicator or command palette, choose the Continue Working On item.
When you are in a GitHub repository in https://insiders.vscode.dev, ensure that you see the following options for Continue Working On:
Create some uncommitted changes in the source workspace, and test that your uncommitted changes come with you when using Continue Working On in the following scenarios:
When in desktop VS Code, use the Open Remote Repository action from the remote indicator or command palette to browse a GitHub or Azure Repos repository without cloning:
When you are in a virtual GitHub repository on desktop, ensure that you see the following options for Continue Working On:
Create some uncommitted changes in the source workspace, and test that your uncommitted changes come with you when using Continue Working On in the following scenarios:
Known issues:
The text was updated successfully, but these errors were encountered: