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:
on: [workflow_dispatch]
# to
on:
release:
types: [created]
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 👍
@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 👍🤝