docs: fix how to update next minor upgrade branch#6154
Merged
Conversation
MGatner
reviewed
Jun 18, 2022
Member
MGatner
left a comment
There was a problem hiding this comment.
This is my fault for not looking closely. But I actually recommend working off the repo branches directly for release, as it makes the process faster and reduces mistakes:
Work off direct clones of the repos so the release branches persist for a time
So the upstream remote is irrelevant.
MGatner
requested changes
Jun 18, 2022
Member
MGatner
left a comment
There was a problem hiding this comment.
It won't let me suggest a change for untouched lines, but please rework for direct branch access.
Member
Author
|
Fixed the git commands. |
MGatner
approved these changes
Jun 23, 2022
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.
Description
Checklist: