[Docs] Updated Subtree Docs for Upgrading Versions #2594
Merged
Conversation
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
Added documentation on how to upgrade the version of a subtree. This is non-trivial since many repos store their versions on different branches. Change the branch of a subtree is basically creating a new subtree, so the old subtree needs to be completely remove from VTR first.
|
@vaughnbetz Please review whenever you have a moment. This is a non functional change which just adds documentation on how to upgrade from one version of a subtree to another when the subtree is on a different branch. I do not know if this is the most efficient way of doing it; however, I do think that this is the easiest to write down. |
|
Looks good; thanks. |
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.
Added documentation on how to upgrade the version of a subtree. This is non-trivial since many repos store their versions on different branches. Change the branch of a subtree is basically creating a new subtree, so the old subtree needs to be completely remove from VTR first.