feat: enable release branch option for tag action#9
Merged
Conversation
WalkthroughThe project has introduced a new optional input parameter Changes
TipsChat with CodeRabbit Bot (
|
Manav-Aggarwal
approved these changes
Nov 30, 2023
gupadhyaya
approved these changes
Nov 30, 2023
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
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.
Overview
related to evstack/ev-node#1362
this change has already been implemented and verified in celestia-app and celestia-node.
This flag is required when making releases not on
mainormasterbranches.Checklist
Summary by CodeRabbit
New Features
release-branchparameter to specify the branch for tag generation in the release workflow.Documentation
Chores