ci: trigger job deploy also on releases/ branches #640
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
jpastoor
force-pushed
the
support_multiple_releases
branch
from
be3c986 to
91d308f
Compare
msvolenski
approved these changes
Jun 13, 2023
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.
If we want to support both 4.x and 5.x releases simultanuously, we need some way to trigger the releases github action on multiple branches.
releases/v4.xoff a49f32fdeployis updated to work for both branchesmasterandreleases/**buildstep:get-current-versionnow lists the latest tag that is merged in that branch with --merged. So it won't find the 5.x tag in the 4.x tree.