Open coleshaw opened 4 years ago
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?
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
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?