Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🤖 Github automation to publish gem in Rubygems #116

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pedrofurtado
Copy link
Contributor

@pedrofurtado pedrofurtado commented Jul 28, 2021

@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:

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 👍

🤝

@pedrofurtado pedrofurtado changed the title 🤖 Github automation to publish gem in Rubygems (Dispatching workflow in actions tab, by repo admins) 🤖 Github automation to publish gem in Rubygems Jul 28, 2021
@pedrofurtado
Copy link
Contributor Author

@unixmonkey Let me know what you think about 🍻 🤝

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant