Initial Devcontainer Setup #48
Closed
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
|
Should be good to go. |
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.
Due to the nature of devcontainers vsocde will handle the cloning of the repository whilst the dockerfile will provide the surrounding environment.
Whilst this configuration works it isn't setup in the recomended way for devcontainers.
The Dockerfile clones the git repo for
LLVMandTeaching-Software-Analysis. Additionally, devcontainers clone theTeaching-Software-Analysisto a custom path that's mapped to the file system/workspaces/Teaching-Software-Analysis. As a result the build is run again as apostCreateCommand.I've added additional build artefacts to the
.gitignorefile.fixes #47