Allowing Release from Specific Branches #3597
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
wu-sheng
approved these changes
Nov 16, 2023
There was a problem hiding this comment.
LGTM. As @basvanbeek suggested, we could release RC(x) from other branch, such as zipkin-ve. The release script should be changed.
wu-sheng
reviewed
Nov 16, 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.
Currently, the release process is initiated from the master branch. However, when attempting to create a new release for the
zipkin-v3branch, the process still defaults to using the master branch for publication.In this pull request, I've modified the workflow to checkout the branch intended for release, ensuring releases are initiated from the correct branch.