[#6870]Fix: Use RELEASE_BRANCH instead of hardcoded main in release script#6901
Closed
Pranaykarvi wants to merge 24 commits intoapache:mainfrom
Closed
[#6870]Fix: Use RELEASE_BRANCH instead of hardcoded main in release script#6901Pranaykarvi wants to merge 24 commits intoapache:mainfrom
Pranaykarvi wants to merge 24 commits intoapache:mainfrom
Conversation
Co-authored-by: Qian Xia <lauraxiaqian@gmail.com>
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.
Description
The release script previously had the
git clonecommand hardcoded to themainbranch. This caused issues when attempting to release from a different branch, such asrelease, resulting in cloning the wrong codebase.This PR introduces the
RELEASE_BRANCHvariable, allowing the user to specify a branch dynamically. If not provided, it defaults torelease. This enhances flexibility and prevents accidental use of the wrong branch during the release process.Changes Made
RELEASE_BRANCH=${RELEASE_BRANCH:-release}early in the script.git clonecommand to use$RELEASE_BRANCHinstead ofmain.This change allows safe and accurate automation for multi-branch release workflows.