opendevstack / opendevstack/ods-quickstarters
.devcontainer integration
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 39
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when I start with a new quickstarter environment but have to focus an requirements and deps beforehand.
Different projects might require different prerequisite or tooling.
Describe the solution you'd like
Include a .devcontainer setup for each quickstarter or even different flavours simple/advanced.
Meanwhile this is a common approach for reproducible configs. A developer does not have to use it, it's an option.
Describe alternatives you've considered
N/A
Additional context
https://code.visualstudio.com/docs/devcontainers/containers
https://code.visualstudio.com/remote/advancedcontainers/overview
Contributor guide
No contributing guide indexed for this repository
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 or tests are identified in the issue. Start by listing the quickstarter directories and reading the linked VS Code devcontainer documentation; determine the required setup for each quickstarter or flavor, then verify that each proposed configuration supports reproducible development without being mandatory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100