-
Notifications
You must be signed in to change notification settings - Fork 31k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test: Continue On end-to-end scenarios #161875
Comments
@bpasero do you have the GitHub Codespaces extension installed? That should be sufficient for the Create New Codespace option to appear. |
Ah I see, yeah now when I install it it seems better. |
is it expected that edit: I was not on insiders.dev |
@amunger are you using Continue On > Clone Locally, or Continue On > Reopen on Desktop? The quality of VS Code (stable/insiders) should always be preserved. |
Refs #160047
Authors: @joyceerhl
Complexity: 5
Create Issue
With this release, we now support the following Continue On transitions in core, accessible via the
Continue Working On
command in the palette. When you use Continue On, any uncommitted changes you have created in your current workspace should travel with you to the destination workspace:Please play with these transitions across insiders.vscode.dev and VS Code desktop. In particular, besides filing issues for bugs and UX issues, please also file issues for missing features/transitions.
Known missing transitions:
The text was updated successfully, but these errors were encountered: