Automate creating a GitHub release #545
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
The current release process of a new BlueChi version to GitHub involves quite a few manual steps. Due to introducing submodules, the default artifacts of a GitHub release does not contain the respective source files - emphasizing the need for automation. Based on the manual flow, its easy to automatically create a release when a new tag is pushed. Signed-off-by: Michael Engel <mengel@redhat.com>
engelmi
requested review from
alexlarsson,
mkemel,
rhatdan and
sdunnagan
as code owners
|
I like this change. Mainly tying the release to a tag instead of manual triggers |
Signed-off-by: Michael Engel <mengel@redhat.com>
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.
The current release process of a new BlueChi version to GitHub involves quite a few manual steps. Due to introducing submodules, the default artifacts of a GitHub release do not contain the respective source files - emphasizing the need for automation. Based on the manual flow, its easy to automatically create a release, including the required artifacts, when a new tag is pushed.
It also links this release process to publishing the python bindings to PyPi.
This is a proposal. If accepted, I'd also update the README.maintainer.md accordingly.