refactor: Improve branch/release scripts#762
Merged
Conversation
✅ Deploy Preview for stackable-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
NickLarsenNZ
approved these changes
Jul 24, 2025
Member
Author
No, the new release branch is inserted as others were before. It only uses a hyphen instead of a slash.
No, the old branches can be kept as is. All releases up to 25.3 can continue to use branches with slashes. The new 25.7 release will instead point to a branch with a hyphen.
Yes, that's true. But there shouldn't be many mentions afair. |
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.
This PR improves a bunch of things:
release-YY.M.Xinstead ofrelease/YY.M.Xto be inline with all other release branches.HEADandorigin/mainif they are not in sync