Repository navigation
ci(container): publish the advanced demo image to GHCR - #63
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds the container-release workflow so the repo ships its containerized example app to GHCR as
ghcr.io/guard-core/guard-core-php-example, matching the family convention: every python repo publishes its example app this way (fastapi-guard-example, flaskapi-guard-example, djapi-guard-example, tornadoapi-guard-example, plus the agent), and the Go and PHP adapter fleets do the same.Mirrors the python template (release -> version tag + latest, master push on
examples/**, manual dispatch) against the existingexamples/advanced_appcompose stack, with this repo's action-pinning style.