Rework GHCR publish actions #64
Merged
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
sokovninn
requested review from
kozlov721,
klemen1999,
conorsim and
HonzaCuhel
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 pull request includes changes to the GitHub Actions workflows to improve deployment processes for images to GitHub Container Registry (GHCR).
Changes to deployment workflows:
.github/workflows/gar-publish.yaml: Removed the release trigger from the GAR deployment workflow to streamline the deployment process..github/workflows/ghcr-publish-manual.yaml: Added a new workflow to manually deploy images to GHCR, including steps for checking out the branch, extracting the commit hash, logging into GHCR, and building and pushing the image..github/workflows/ghcr-publish.yaml: Renamed the existing GHCR deployment workflow to clarify that it deploys the latest image on release.