-
Notifications
You must be signed in to change notification settings - Fork 229
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
Did you forget to push tags to GH repository? #213
Comments
Damn :/ Yeah I forgot about tags On Fri, Oct 11, 2013 at 3:49 PM, Zeke Fast notifications@github.com
|
You can just use |
Do you know what's the easiest way to find sha1 for releases? |
Do you mean having code find sha1 for it? I think it's impossible exactly determine the commit by code, because even same code committed on different time has different hashes. If you have no tags for previous releases and I'm the only who notice that. I'd suggest don't bothering with tagging and just pay attention to this in future or use |
I always tag releases. I forgot this time because it was a pre-release and I was in rush :( On Sun, Oct 13, 2013 at 4:43 PM, Zeke Fast notifications@github.com
|
I try to use |
@dkubb |
Lets move this to devtools ;) |
I don't use |
@solnic It's this thing: https://github.com/svenfuchs/gem-release I ditched jeweler for this and I really like it. |
Yeah, it's a nice single purpose library. It adds the "release" command to gem. With the |
I just recalled I used to use it and then I stopped, not sure why. |
Seems like just tagging the shas where the version was bumped would do it. https://github.com/solnic/virtus/commits/master/lib/virtus/version.rb |
@zekefast, I'm closing this issue now. If you need access to these tags for any reason, please let me know, otherwise, I'm going to leave it be since 1.0 has been released. |
@elskwid, Since 1.0 was released this is Okay. Thanks! |
Please, push tags for versions on rubygems.org to GitHub, at least for latest 1.0.0.rc2.
Thank you in advance!
The text was updated successfully, but these errors were encountered: