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

Etna-gem should auto-publish when version changed #54

Open
coleshaw opened this issue Jun 3, 2020 · 1 comment
Open

Etna-gem should auto-publish when version changed #54

coleshaw opened this issue Jun 3, 2020 · 1 comment

Comments

@coleshaw
Copy link
Collaborator

coleshaw commented Jun 3, 2020

We should publish this gem to RubyGems.org whenever the version is changed (or a tagged release pushed, or equivalent).

Alternatively, as a stop-gap, should @graft set it up so that Cole and Zach can publish, too?

@graft
Copy link
Contributor

graft commented Jun 3, 2020

The main issue is it requires a secret (rubygems api key), dealing with this is described here: https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets

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

No branches or pull requests

2 participants