Fix a bug committing changes to dockers_*.json after an image is updated #559
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 fixes two bugs:
Publish
action in the GitHub workflow commits changes todockers_*.json
and pushes them to themain
if a variable that determines whether the file is updated or not is set toTrue
. With recent changes to Github actions, the method we previously used to set this variable is deprecated; hence the variable is not correctly set, resulting in not committing the changeddockers_*.json
files tomain
. This issue is fixed in this PR.dockers_*.json
was not updated with the latest image builds. The only impact image in the recently merged PRs issv-pipeline
; hence this PR adds the build and pushed the image to thedockers_*.json
.