ci: setup release-please to automate new releases #223
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 output generated by gorelease is not used in any way and we can skip calling it.
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.
Setup release-please using the release-please-action to automate creating new releases. The workflow is:
maincommit the action will scan all commits made since the last release/tagfixorfeat, see Conventional Commits), create/update release PRCHANGELOG.mdVersioninhcloud/hcloud.gomaincommit, the action will scan for merged release PRs that have no associated Git Tag/GitHub Release and then create tags and GitHub releases for themIf you want to see how this works in practice, checkout these links from my fork (until I delete the fork):