this post was submitted on 04 Nov 2025
46 points (96.0% liked)

Git

3934 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 2 years ago
MODERATORS
top 9 comments
sorted by: hot top controversial new old
[–] hoppolito@mander.xyz 5 points 2 weeks ago (1 children)

This is really cool but I’m unsure why exactly the kitty/iterm image protocols are a requirement.

Is it to display the actual ‘graph’ on the left of the screen? If the terminal does not support image display does it degrade gracefully (e.g. unicode symbols) or does it just not work?

If it only works in terminal emulators with specific image support that seems a tad unfortunate for what otherwise seems a very nice fire-and-forget solution for trawling through commit logs.

[–] xav@programming.dev 2 points 2 weeks ago

Apparently there's an automatic detection of what's supported and a nice degradation. But yes, I don't see a clear advantage wrt tig's UTF-8 graph display.

[–] fraksken 3 points 2 weeks ago (1 children)
[–] FizzyOrange@programming.dev 1 points 2 weeks ago (1 children)
[–] fraksken 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I mean ... tig does a lot more, but it also has the revision graph

-edit: typo-

[–] FizzyOrange@programming.dev 1 points 2 weeks ago

Yeah but one is using Tk and the other doesn't look any better than git log --graph. I think the point of this is that it looks okish and is in the terminal.

[–] FishFace@piefed.social 2 points 2 weeks ago (1 children)

Falls into a weird niche for me - if I'm in a situation where text-only history is not good enough, I'll just use something graphical, rather than some crazy image-in-terminal solution.

Mostly in git I use an alias I wrote/stole ages ago which displays linear history compactly.

[–] ozr@programming.dev 1 points 2 weeks ago* (last edited 2 weeks ago)

It is a handful, but git log --graph --decorate --all --full-index --color=always | less -R is what I use and I think it's great. Especially after I found the vim mode in my terminal emulator alacritty, and copying the commit hashes got really easy

[–] ulterno@programming.dev 0 points 2 weeks ago

Nice.
I tend to use the graph made by git, but always feel like it would make my comprehension faster, if I had a properly rendered tree. But then I have been too lazy to use something like gitk.

Looking at the repo, the code being Rust, I feel like I will give it a try the next time I need to view a graph and hopefully the interface matches my requirements.