Feature/369 adjust vscode container build and deploy #370
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
added 2 commits
February 12, 2020 16:38
ghost
approved these changes
Feb 14, 2020
ghost
deleted the
feature/369_adjust_vscode_container_build_and_deploy
branch
This pull request was closed.
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.
Closes #369
Changes the update procedure for the
stelligent/vscode-remote-cfn_nagDockerHub repo. It will now only build and push an image if something inside the.devcontainer/directory is updated in the master branch. This is made available by implementing a new GitHub Actions Workflow, replacing the old build and push items from within thescripts/publish.shfile.