microsoft / microsoft/aspire-devcontainer-feature
How does this relate to documentation and template repo?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 10
- Forks
- 10
- Avg merge
- 6h 47m
- Merged PRs (30d)
- 1
Description
I see this feature is in the official dotnet org, but it is not referenced in the Aspire devcontainer documentation nor in the Aspire devcontainer template.
How do these approaches relate to each other? Should one be used over the other?
What is the future for this feature? The responsiveness to issues posted on this repo seems not that high?
@joperezr @eerhardt @aaronpowell @maddymontaquila @mitchdenny?
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
Start by comparing the Aspire devcontainer documentation with the .devcontainer/devcontainer.json file in the linked Aspire devcontainer template. Determine whether the issue can be resolved by documenting the relationship and recommended use cases; done means the feature's role, future direction, and relationship to the template are clearly answered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100