Testing some release processes #47
Closed
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
jason-famedly
force-pushed
the
jason/new-release-script
branch
from
a02a3f3 to
2778d6c
Compare
jason-famedly
force-pushed
the
jason/new-release-script
branch
from
2778d6c to
4d8a56d
Compare
jason-famedly
force-pushed
the
jason/new-release-script
branch
from
4d8a56d to
55f1271
Compare
jason-famedly
force-pushed
the
jason/new-release-script
branch
from
55f1271 to
ee34a6f
Compare
Contributor
Author
|
Replaced by #60 |
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.
For famedly/product-management#2985
I would like a release script that is user friendly, will handle a lot of the details of merging in upstream changes, and will even add to the existing changelog for me
Still using the version format of
vX.Y.Z_Afor this work. Adjust that to something else will be a followup.Will create the release directory if it does exist, or switch to it if it already does
Will pull and merge any changes from upstream on their similar branch
If there were local changes they will be added to the bottom of the entry for the most recent version(need to test hotfix behavior still)
Will push this release branch to Github
WIP - will probably not open a PR automagically, that could be unsecure
Once PR is open for release, CI should run
Release will be tagged locally and pushed to Github where the docker image should be built