vscode-remote-release
https://github.com/microsoft/vscode-remote-release
Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
not yet supported2 Subscribers
Add a CodeTriage badge to vscode-remote-release
Help out
- Issues
- Ability to add an extension as a default extension to devcontainer while installing the extension
- Files replaced with symlinks under WSL are not being detected as changed by VScode run from WSL
- High CPU usage by vscode-server/typescript
- remote.containers.repositoryConfigurationPaths doesn't work with WSL / SSH / Clone in Volume
- Auto-connect to remote on startup
- Allow picking folder names under volumes
- Use existing Node to connect
- Clone repository with specific branch
- If a devcontainer has a directory mapping VsCode uses the container's internal mapped directory as the identifier for the dev container instead of the project directory.
- Extensions specified in devcontainer.json doesn't get installed to "offline" host, even if remote.downloadExtensionsLocally=true
- Docs
- not yet supported