-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
Tags not showing in log #206
Comments
@albertogg thanks for reporting this. I cannot reproduce the problem for tags pointing to commits in the current branch. Is the repo you experience the issue open source to reproduce? |
Thanks for the quick response... yes, it is. It's this one https://github.com/qmk/qmk_firmware. |
So turns out to be an issue in the library I am using to interact with the git repo: https://libgit2.org - I am working on a small repro for them to look into. |
ha, Interesting. I see that you already put the work rust-lang/git2-rs#594. Thanks! let's see how this goes. |
Nice, I can imagine. very fast turn around. thanks! |
@albertogg btw. this is what confused me in the base c++ lib: libgit2/libgit2#5586 |
I see, If you don't annotate the tag they will be "lightweight", that behavior seems odd, I would have never thought of that. But I don't completely understand... is the rust library using the c++ library underneath? |
@albertogg exactly, libgit2 is the base library powering gitlab and gitkraken and git2-rs is the rust safety wrapper that I am using |
Hi, this is a very cool TUI, thank you. I was testing it out and found myself needing to look at which commits are tagged within the Log. It seems that this is not happening despite seeing that the feature was implemented in #47. I haven't look at the code.
Expected behavior
Seeing the tag next to the commit message.
Screenshots
Here are a couple of screenshots. One is with GitUp showing the tag in the commit, and the second one is the Log on GitUI.
Context (please complete the following information):
macOS 10.14.6
0.8.1
1.42
The text was updated successfully, but these errors were encountered: