Workflow for auto releasing on GH #292
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
|
Checks failed due to codecov, same problem as in #290 |
FabianHofmann
approved these changes
May 21, 2024
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.
Continuing on #283 I suggest to add a workflow for auto releasing on GitHub. This can be done by using the action
gh-release. One can configure it, so that it auto generates the release notes as well (Same outcome as using the button from the web GUI).I marked this as draft for two reasons:
.github/workflows/deploy.ymlv*.*.*as the tag for releases and you don't want to make a release for every tag. Need to discuss if adding this filter to the.github/workflows/deploy.ymlas well.