microsoft / microsoft/vscode-remote-release
easy way to open remote development workspace
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Type: Feature Request
I have quite a many remote connections. On many of those, I multiple workspace folders each corresponding to an application. I need an easy way to launch the workspace folder directly into a new window.
Currently Remote Explorer lists Remote connections and its workspace folders in tree format. The issue is that my list is long and Remote Explorer doesn't have a search funtion. An alternative was to use the command palatte Remote-SSH: Connect to host... which does filter the servers by name as we type. But that list shows only the server not the workspace folder.
So either the remote explorer can provide search funtionality and list the workspace folders related to the matching servers
OR
Remote-SSH: Connect to host... can list the workspace folders related to the list of matching servers returned in autocomplete.
Extension version: 0.110.1
VS Code version: Code 1.90.1 (611f9bfce64f25108829dd295f54a6894e87339d, 2024-06-11T21:01:24.262Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 4.4.0-1128-aws
System Info
| Item | Value |
|---|---|
| CPUs | 11th Gen Intel(R) Core(TM) i5-11500 @ 2.70GHz (12 x 2712) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.73GB (7.51GB free) |
| Process Argv | --crash-reporter-id 6b0e180e-4558-4feb-98a6-b5502275d6ca |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | SSH: AWS-EC2 |
| OS | Linux x64 4.4.0-1128-aws |
| CPUs | AMD EPYC 7571 (2 x 0) |
| Memory (System) | 15.43GB (6.93GB free) |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyonecf:30548226
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelt:31048053
dsvsc021:30996838
bdiig495:31013172
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
pythonprt:31056678
dwnewjupytercf:31046870
2f103344:31071589
legacy_priority:31077528
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Remote Explorer workspace-folder tree and the Remote-SSH: Connect to host... command described in the issue. Determine which entry point can expose searchable workspace folders, then verify that matching servers and their folders can be opened in a new window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100