feat: proper docker publish flow #219
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
tchataigner
force-pushed
the
feature/docker-publish-flow
branch
from
33a28cc to
c91a475
Compare
huitseeker
reviewed
Sep 12, 2024
tchataigner
force-pushed
the
feature/docker-publish-flow
branch
from
595659f to
d6e62cd
Compare
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 PR updates our docker publish flow so that we can upload our images as package of the repository.
For now the image has to be run on top of the desired branch to use for the image publication and the tag for the image is a manual input.
The workflow could be upgraded later on to trigger on commit merge on
releasebranches, and have manual trigger for:latestimages ondev.Successful run Aptos:
Successful run Ethereum: