adding gh workflow for v1 -> v2 migration #2127
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
zone117x
reviewed
Dec 7, 2020
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Adds a new Github workflow to automate the change, commit, and PR creation of updating the chainstate and chainstate consensus files for the V1 -> V2 migration.
Upon an authorized
repo_dispatchPOST to this repo, the workflow will kick off. It'll download the chainstate files from GCS, commit that to a new branch created frommaster, and create a new PR displaying those changes and some metadata of the files, while assigning multiple people as reviewers and assignees.An example of the PR can be found here.
Type of Change
Does this introduce a breaking change?
No
Are documentation updates required?
No
Checklist