Add support for devcontainers. #6
Conversation
|
Testing this out, noticed the qmk firmware folder. We might want to handle the qmk_firmware directory better. Eg, init it as a submodule or add it to gitignore, or something. |
|
@drashna how about now? Not sold on the new code workspace file being created, but it allows for both qmk_userspace and qmk_firmware in the sidebar. |
|
It looks like the code workspace doesn't get loaded unless you manually load it. Which, you could just add a folder to the workspace, anyways. And a short look shows that there isn't a good solution for this :/ I'd say just opt to not add the workspace creation. |
…qmk/qmk_firmware.
|
Yeah I came to the same conclusion. I've removed the automatic workspace generation, and sync'ed up the VSCode extensions with qmk/qmk_firmware. |
.devcontainer/devcontainer.json
Outdated
| "xaver.clang-format", | ||
| "llvm-vs-code-extensions.vscode-clangd", | ||
| "bierner.github-markdown-preview", | ||
| "donjayamanne.git-extension-pack" |
There was a problem hiding this comment.
VS Code recommended the dev/remote containers extension on first setup, for me. Not sure if we want/need it here.
"ms-vscode-remote.remote-containers"
Description
Creation command is a bit long, but it does the job.
Allows for the use of GitHub Codespaces to do compilation online, rather than setting up a local environment.