Test: Continue Working On improvements

[joyceerhl]

Refs: #165409, #165408, #165406, #167106

• Windows @sbatten
• macOS @chrmarti
• Linux @andreamah

Authors: @joyceerhl

Complexity: 5

Create Issue

---

Background:
Following the recent UX study we ran on Continue Working On, we have made some improvements to the usability and discoverability of the Continue Working On feature.

Prerequisites:

• on desktop: GitHub Codespaces v1.13.2
• on web: use insiders.vscode.dev

Please verify:

1. (web) The welcome views in the debug and terminal views clarify that you can transfer your working changes when you use Continue Working On to a different environment
2. (desktop with Codespaces installed) When using the Continue Working On... picker, the Codespaces quickpick item has a quickpick item button for learning more about the Codespaces option
3. (desktop in a GitHub Repositories workspace) Continue Working On is surfaced in the SCM view as a secondary action in the SCM action button dropdown
4. When using the Continue Working On flow, you should be prompted to pick a development environment before you see an auth prompt
5. There should be no mention of 'edit sessions' in the UI exposed through the Continue Working On flow; it should only reference 'working changes' or 'cloud changes' which should be a more intuitive name
6. There are now commands in the palette to bypass the two-step Continue On picker and invoke Continue On for a specific development environment, i.e. instead of selecting Continue Working On... and then Create New Codespace, you can select Codespaces: Continue Working in a New Codespace
7. Create 30 codespaces (to hit the codespaces creation limit for the microsoft org), use Continue On and choose Codespaces. You should be prompted to delete a codespace first and then allowed to continue creating a codespace

[chirag127]

what is "cloud changes"?

[joyceerhl]

@chirag127 You can read more about it in our documentation: https://code.visualstudio.com/docs/sourcecontrol/github#_continue-working-on