microsoft / microsoft/vscode-remote-release
Open workspace in container when workspace file is not at the root
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
We have a repo where shared IDE files are stored in an "ide" folder, including the .code-workspace file. The folders section looks like this:
"folders": [
{
"path": ".."
}
],
When attempting to add remote development container support, we found that having the config file not at the root when trying to use the "Remote-Containers: Open Workspace in Container" method. Opening a workspace on a physical machine works fine with the file in this location. We would like to see this same feature supported for container development as well.
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 tracing the "Remote-Containers: Open Workspace in Container" flow and how it locates the .code-workspace file. Reproduce the case with the workspace file under an "ide" folder and a folders path of ".."; done means that workspace opens in the container as it does on a physical machine.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100