ci: ensure docker-build is triggered after release #125
+8
−0
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
A workflow can't trigger an other workflow, this is a gh action rule to avoid infinite loop. In order to trigger docker-build after release action, we have to do to manually. Hopefully, it's possible to refer local actions.
Pitasi
previously approved these changes
May 20, 2022
tbruyelle
force-pushed
the
ci/ensure-docker-build
branch
from
8779737 to
f113e23
Compare
Pitasi
approved these changes
Jun 1, 2022
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.
A workflow can't trigger an other workflow, this is a gh action rule to
avoid infinite loop.
In order to trigger docker-build after release action, we have to do it
manually. Hopefully, it's possible to refer local actions.