ci: Trigger the release workflow whenever a release was created #59
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
This uses the [release](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#release) workflow event rather than check for specific tags pushed.
|
I'm a bit nervous that this will break the release process and I don't know how to test/verify that |
|
Can wait before doing the release, merge this, release, if doesn't work revert and release another patch version afterwards |
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 uses the
release workflow event rather than check for specific tags pushed. Unless I misunderstand how you handle your tags, this should be slightly more robust (and also you don't need to care about the tag name).