microsoft / microsoft/vscode-remote-release
Automatically open in container
Open
Nobody has claimed this yet.
containers
feature-request
plan-review
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Please add a setting for always attempting to open in a container if a project contains the .devcontainer folder.
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
No files, tests, or entry points are named in the issue. Start by locating the existing behavior for opening projects in a container and its settings, then define the new setting's behavior when a project contains a .devcontainer folder; done means the setting reliably attempts to open such projects in a container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, vscode
- Domain
- developer-experience, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100