fix: use correct Docker build Actions workflow #59
Conversation
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
Fix the name of the file of the build Action, which should use https://github.com/OpenCHAMI/github-actions/blob/v3.3/.github/workflows/docker-build-release.yml and wasn't because I can't read no good. Signed-off-by: Travis Raines <[email protected]>
rainest
had a problem deploying
to
Docker Push
GitHub Actions
Failure
cjh1
approved these changes
Nov 19, 2025
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.
Fix the name of the file of the build Action, which should use https://github.com/OpenCHAMI/github-actions/blob/v3.3/.github/workflows/docker-build-release.yml and wasn't because I can't read no good.
See https://github.com/OpenCHAMI/power-control/actions/runs/19506800374
https://github.com/OpenCHAMI/github-actions/blob/v3.3/.github/workflows/docker-build-release.yml#L41-L44 does exist, but not if your repo config has "Sorry Github, our action is in Another Castle" PEBKAC errors.