Fix devcontainer config to use new vscode user #32
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
Codecov Report
@@ Coverage Diff @@
## main #32 +/- ##
=======================================
Coverage 76.19% 76.19%
=======================================
Files 5 5
Lines 210 210
=======================================
Hits 160 160
Misses 50 50 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
ehsteve
approved these changes
Dec 7, 2022
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.
This PR (will be very similar to the other 4), it helps address this issue: HERMES-SOC/hermes_eea#6
It sets the default user of the devcontainer to be the new
vscodeuser that is introduced in this PR (Should be merged after this one is merged): HERMES-SOC/sdc_aws_base_docker_image#23It also fixes a few path issues that were pointed out in the issue.