Create a staging branch #272
Merged
Conversation
This file contains 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
samelamin
approved these changes
Nov 22, 2023
|
potentially its simpler to merge this after the next runtime upgrade? |
agreed |
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.
Since im struggling to keep track of everything, all changes go to the branch
stagingand when we do a runtime upgrade we do a PR tomain.So during development
new_changes_1 -> stagingnew_changes_2 -> stagingReady for runtime upgrade
staging -> mainThis allows us to do things like check the spec_version, benchmarks and migrations etc systematically before an upgrade.