-
Notifications
You must be signed in to change notification settings - Fork 2
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
Support releasing without rake #3
Comments
I am open to us pointing to a script file in the repo that can run build & push, but since this is such a small action, I do want to keep it focused on the most common way of releasing (which is running |
is that actually the most common way? I package many ruby gems for Arch Linux and the majority of them uses |
+1 for not requiring |
https://github.com/rubygems/rubygems/blob/072176243027a60e20ffe6976ec59b45bc65f351/bundler/lib/bundler/gem_helper.rb#L76 by default bundler's rake task checks if the tag already exists |
Ahh, good to know. Although that requires the tag to be formatted like |
I appreciate an action is published to make releasing easier. Standardizing the ecosystem is a good thing and I wasn't aware of rubygem-await (but have certainly it the problem it wasn't published before).
With the aim of replacing my release-gem.yml I started to play with this. In a test project I noticed this uses
rake release
, and then saw it was also documented in the README:My test project doesn't use
rake
at all and I'd like it if I didn't need to runbundle install
just to publish the gem. My current workflow usesgem build
andgem push
. Are you open to supporting this way or should I enhance my current workflow to reuserubygems/configure-rubygems-credentials
? (I really appreciate those steps are separated for easier composability).The text was updated successfully, but these errors were encountered: