Create a release script to automated the release process #1520
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
|
So do we just need to store the version in a different file so that GitHub actions can run it? |
Yeah if it was outside of the workflow folder everything could be done within a GitHub action |
|
When I ran this the tag was missing everything after the first line of the changelog. |
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 automates the first 5 steps of the release process. Unfortunately I cant make this a manual github action due to writing to the workflows/ci.yml file. Its pretty simple to run even from windows just open a git bash terminal and type
scripts/release.shThe next step of the automation is to make the ci.yml upload the files and perform the release when tagged.