Repository navigation
chore: refactor devcontainer for better maintenance - #1665
Merged
Merged
Conversation
Signed-off-by: thediveo <thediveo@gmx.eu>
Owner
|
all good! |
This file contains hidden or 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
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 ap
307D
plied 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.
Sorry for the noise, this is hopefully making maintaining the devcontainer configuration much easier and clearer what's going on. This chore update now uses proper scripts instead of shoehorning non-trivial shell commands into JSON strings.
On top, I've made the first-run-message to be better readable and more comprehensible.
This is now basically the same devcontainer configuration as the Gomega PR, just with the appropriate name changes from Gomega to Ginkgo.