-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
[automatically] deploy to rubygems #4
Comments
should we even bother deploying to rubygems? we can probably just get away with pulling it from github |
yeah, i think deploying to rubygems might be a good idea. As someone extraordinarily smart writes:
|
I want to use it in my Gemfile and think others might as well. We'll need an account first, then I think we can grant other people with existing accounts with the ability to create new versions. |
You can use it in a Gemfile from a git source. I would normally agree about shipping it to RubyGems, but I don't see much added benefit since this is really just an internal tool. But I'll defer to the majority. |
Oh, but I want to use it externally! It's a pretty cool tool and could help other module authors, too. |
When we have an account and so can get an API token, https://docs.travis-ci.com/user/deployment/rubygems/ |
we should setup a pipeline to automagickally deploy to rubygems
related: voxpupuli/plumbing#20
The text was updated successfully, but these errors were encountered: