🤖 Github automation to publish gem in Rubygems #116
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.
@unixmonkey Hi again! 👋
I think this automation can help us a lot, in order to publish versions in rubygems without need to clone/build/publish manually in our PC or something else.
Once released is done and the version is defined in
version.rb
, we just need to dispatch the workflow in Github Actions tab. Only repo admins can make this action, and that is great 🍻What do you think about?
PS: We have the option to publish by workflow dispatching, or define to be triggered after a release is created in repo, so we would keep in sync rubygems releases and github releases. Do you have a preference by one or another approach?
The second approach I just need to change:
PS 2: Before merge, we just need to define a new repo secret, with name
RUBYGEMS_AUTH_TOKEN
containing the auth token generated by rubygems dashboard 👍🤝