Test: Continue On between SSH and HTTP remotes

[joyceerhl]

Refs: #172341

• anyOS @aiday-mar
• anyOS @amunger

Complexity: 4
Roles: Developer, Engineering Manager

Create Issue

---

You can now transfer working changes for the same repository across different VS Code workspaces regardless of whether you like to use HTTP or SSH remotes.

If you have SSH cloning set up locally:

1. Start in a GitHub repo in insiders.vscode.dev
2. In VS Code desktop, configure "github.gitProtocol": "ssh" (and make sure you have set up your local machine for SSH cloning)
3. Make some uncommitted changes in insiders.vscode.dev
4. From the remote indicator, select Continue Working in New Local Clone
5. If you're doing this for the first time you should be prompted to sign in to transfer your changes in insiders.vscode.dev and again locally
6. Your working changes should restore in the local clone

If you do not have SSH cloning set up locally, you can equivalently do:

1. Open a GitHub repo in insiders.vscode.dev
2. Clone that same repo to VS Code desktop
3. Locally run git remote set-url origin <ssh equivalent of http origin>
   • e.g. https://github.com/microsoft/vscode.git -> git@github.com:microsoft/vscode.git
4. Make some uncommitted changes in insiders.vscode.dev
5. Run Store Current Working Changes in Cloud in insiders.vscode.dev
6. Run Resume Latest Working Changes from Cloud in VS Code desktop
7. Ensure your working changes restore in the local clone

[amunger]

I'm not sure what SSH cloning is, but didn't see the Continue Working in New Local Clone, so I probably don't have it set up.
Second part worked fine tho.