Github actions for publish to rubygems #92
Closed
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
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.
@robertomiranda I created a Github Actions in order to release versions to rubygems automatically when we create a new release/tag in Github.
It is not working yet, because it is required to create a new secret in repo settings with name
RUBYGEMS_AUTH_TOKENand token generated in RubyGems dashboard. Can you create it for us, please, when you have time?Once the secret is created, we can test creating a "official" release here in repo to execute the flow.
Recently, I also merged for us the #93 to prepare repo for the version release, setting the version number in code 馃憤
Thanks a lot! 馃嵒