docs(contributing): Add devcontainer/cli as alternative method for local development setup
#6343
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cal development setup
👷 Deploy request for qwik-insights pending review.Visit the deploys page to approve it
|
PatrickJS
approved these changes
May 20, 2024
|
thanks! |
|
Thanks @octet-stream for you amazing help 👏 |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Recently found an alternative way to use devcontainers other than VSCode extension devcontainer/cli. It turned out to be useful for my case, because VSCodium does not have this extension. So, I decided to add this piece to the documentation :)
What is it?
Description
This PR updates contributing.md with instruction for local development using devcontainer/cli.
Use cases and why
Checklist: