Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: add devcontainer configuration (#419)
Adding a .devcontainer configuration If you never worked with Devcontainers before, here is a good article about it: [What the heck are devcontainers][1]. Another good one can be found here: [your open source project needs a devcontainer - here's why][2] Tl;Dr: Devcontainers are awesome and they help to define an isolated development environment which is standardised across all contributors setups and leverages the beauty of [GitHub Codespaces][3]. **Special notes for your reviewer**: Just try it out once, before dismissing it. Setting up your VScode to use the Devcontainer is easy: 1. Make sure you have the following plugin installed: [`ms-vscode-remote.remote-containers`][4] 2. Open VScode in the root-directory of the Repository 3. Click "Reopen in Container" once VScode shows you the popup, telling you that it detected a devcontainer configuration. alternative is to use [GitHub Codespaces][3] from your browser. **Documentation**: https://www.aaron-powell.com/posts/2021-03-08-your-open-source-project-needs-a-dev-container-heres-why/ https://code.visualstudio.com/docs/remote/containers https://github.com/qdm12/godevcontainer https://github.com/features/codespaces **Does this PR introduce a user-facing change?**: ```release-note NONE ``` [1]: https://cedi.dev/post/devcontainer-pt1/ [2]: https://www.aaron-powell.com/posts/2021-03-08-your-open-source-project-needs-a-dev-container-heres-why/ [3]: https://github.com/features/codespaces [4]: https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers
- Loading branch information