Test: Continue Working On to desktop VS Code

[joyceerhl]

Refs #156833

• Windows @karrtikr
• macOS @jrieken
• Linux @karthiknadig

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:

1. Install the following extensions:
   • GitHub Repositories (latest pre-release)
   • Azure Repos (latest pre-release)
   • Remote Repositories (latest pre-release v0.19.2022082301)
   • Remote-Containers (0.248.0-rc)
   • GitHub Codespaces (1.10.2)
2. Ensure you have the latest VS Code Insiders build installed.
3. 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.
4. Also ensure you have "workbench.experimental.editSessions.autoResume": "onReload" in your settings on both insiders.vscode.dev and desktop VS Code
5. 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:

1. From the remote indicator or command palette, choose the Continue Working On item.

2. When you are in a GitHub repository in https://insiders.vscode.dev, ensure that you see the following options for Continue Working On:
   

3. 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:

Source	Destination
https://insiders.vscode.dev/github/microsoft/vscode-wasm	Clone repository locally and open on desktop
https://insiders.vscode.dev/azurerepos/Monacotools/Monaco/Sandbox	Clone repository locally and open on desktop
https://insiders.vscode.dev/github/microsoft/vscode-wasm	Reopen on the desktop in RemoteHub
https://insiders.vscode.dev/azurerepos/Monacotools/Monaco/Sandbox	Reopen on the desktop in RemoteHub

6. 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:
   

7. When you are in a virtual GitHub repository on desktop, ensure that you see the following options for Continue Working On:
   

8. 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:

Source	Destination
Open Remote Repository > https://github.com/microsoft/vscode-wasm	Clone repository locally and open on desktop
Open Remote Repository > https://dev.azure.com/monacotools/Monaco/_git/Sandbox	Clone repository locally and open on desktop
Open Remote Repository > https://github.com/microsoft/vscode-wasm	Clone repository in a container volume
Open Remote Repository > https://dev.azure.com/monacotools/Monaco/_git/Sandbox	Clone repository in a container volume

Known issues:

1. Reopen on the Desktop results in error about Git Base extension not being loaded when the last active window is a remote window vscode-remote-repositories-github#223
2. Do not prompt to sign into edit sessions if already signed into settings sync #158384
3. Git uri handler clone should preserve branch #158386
4. RemoteHub: Continue On from web does not check if git is existing #123492

[karrtikr]

Remote-Containers (0.248.0-rc)
GitHub Codespaces (1.10.2)

I assume these need to be updated to:

Remote-Containers (0.248.0)
GitHub Codespaces (1.10.3)

Not sure how to get the -rc version if that's intended.

• Renamed "workbench.ezperimental.editSessions.autoResume": "onReload' to "workbench.experimental.editSessions.autoResume": "onReload"
• Renamed GitHub Codespaces: Sign In to Codespaces: Sign In