feat: automatic release using release-please #14
+73
−0
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
|
@drnic @obie Please review this PR and see if it's a good idea. I have implemented this in this gem: https://github.com/SELISEdigitalplatforms/gotenberg |
bugloper
force-pushed
the
feat/automatic-realease
branch
from
70b13f1 to
d553dbf
Compare
|
I’ll have a look at this when I next look at cutting a release |
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.
Automatic release using Google's
release-pleaseaction and https://www.conventionalcommits.org/en/v1.0.0/Provides automatic versioning and changelogs
Note: Will need to add
RUBYGEMS_AUTH_TOKEN&GEM_HOST_API_KEY