-
Notifications
You must be signed in to change notification settings - Fork 94
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
log does not work with annotated tags #71
Comments
I think I've seen that before, but I didn't look too much into it. The workaround I was using was: grgit.log {
range 'v1.0.0^{commit}', 'HEAD'
}.each { println it.id } Does that work for you? Either way I'll probably add it to the wishlist, just to see if there's a better way to handle this. |
Yes, that does the trick. I was not aware of that syntax. As Lothar Matthäus would say: Again what learned. (https://www.youtube.com/watch?v=fH55rwgx1nY) But I had to write |
Yes, the GString stuff should be enhanced (#72). I'm guessing there's some trick to resolving the right type of object (in the grgit code) to use in the log that would avoid needing to add the |
given: 'a git repository with a tag'
when: 'I have the following groovy script'
an Exception is thrown
Caught: org.eclipse.jgit.errors.IncorrectObjectTypeException: Object 6b291bb71a1b2372323fdfbb24a408b62248303e is not a commit.
I tried
without success.
It does only work, if I change it to
There is no problem with simple (non-annotated) tags.
The text was updated successfully, but these errors were encountered: