-
Notifications
You must be signed in to change notification settings - Fork 581
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
Support virtual workspaces #2722
Comments
Not everything is supported yet, so there's no need to test exhaustively since I already know some things are not yet working, but you should be able to:
|
Unable to verify due to https://github.com/microsoft/vscode-remotehub/issues/40, someone else may have better luck |
My understanding is that you need the virtual workspace of the repo opened. So have Then it's like:
|
@alexr00 the comments don't appear in the file when I check out a PR: On the left is the editor from the GHPR extension. On the right is the normal Remote Repositories editor The other scenarios seem to work well. |
@TylerLeonhardt thanks for testing this! I'm not able to repro what you're seeing. Are you using the nightly/insiders version of GHPRI? |
👋 Hi there, Martin here, from the VS Code team.
Recently we've announced the Remote Repository feature that lets you browse and edit files and folders directly on GitHub.
Open Remote Repository...
opens VSCode on a folder or workspace located on a virtual file system. We call this a virtual workspace. We observed that not all extension support this well, either because they can not, or they haven't thought about it.It would be fantastic if you could test whether your extension can handle virtual workspaces:
Check out the Virtual Workspaces Extension Author Guide on how to do that.
When done, set the new
virtualWorkspaces
capability in your 'package.json'."virtualWorkspaces": true
if your extension is prepared for virtual workspaces"virtualWorkspaces": false
if your extension should be disabled when a virtual workspace is openedFor questions and comments please use the Virtual Workspaces Tracking Issue.
Thanks for the support and the great work! ❤️
The text was updated successfully, but these errors were encountered: