4 ms·
Keifu – A TUI for navigating commit graphs with color and clarity
- M4R5H4LL 9mo agoThanks for sharing. That would be a nice additional example in .NET with Andy TUI. The library is not Rust but there are a few examples you might be interested in, including a HN client [2] [3]. References: [1] https://github.com/rivoli-ai/andy-tui2 https://github.com/rivoli-ai/andy-tui2 [2] https://github.com/rivoli-ai/andy-tui2/blob/main/examples/Andy.Tui.Examples/Demos/HackerNewsDemo.cs https://github.com/rivoli-ai/andy-tui2/blob/main/examples/An... [3] https://imgur.com/a/CgECRa2 https://imgur.com/a/CgECRa2
- RVRX 9mo agoServes a bit of a different purpose - but for working with git in the terminal I'm a big LazyGit fan - https://github.com/jesseduffield/lazygit https://github.com/jesseduffield/lazygit I use it in neovim with https://github.com/kdheepak/lazygit.nvim https://github.com/kdheepak/lazygit.nvim
- animal_spirits 9mo agoSeconded, lazygit helps so much with understanding my index
- NSPG911 9mo agoI use LazyGit as well, but the graph icons always piss me off so much. I've gotten used to it, but I'd love to change the icons.
- mixmastamyk 9mo agoJeez ads on a gitlab readme, and no screenshots to see the annoying icons.
- mr_vile 9mo agoNot trying to be pessimistic here, but I feel like the author is being a bit loaded with the marketing text. There's many pieces of TUI software that do this exact same thing with "color and clarity" and the same fuzzy search, etc. This repository here has a pretty exhaustive list of these softwares: https://github.com/indigane/git-graph-drawing https://github.com/indigane/git-graph-drawing Anyway, congratulations to the author for actually releasing their work.
- goodpoint 9mo agoslopware?
- lloydatkinson 9mo ago> Unicode commit graph with per-branch colors I think every popular Git client can do this, no? I'm waiting for a Git client which can colour commits by category/areas/files. It would be helpful to see which areas of the codebase have the most commits. Especially useful if using conventional commits (eg. fix: correct usage of foo) alongside it. Areas or files with a lot of commits tend to be sources of bugs or indicate other things. You can write a script to find this sort of thing, but that requires you to remember to do it. If it was built in passively to a Git client, I think a lot more would be revealed.
- eMPee584 9mo agoDon't wait.. vibe-code, it's 2026!!1
- hbogert 9mo agoIf your history looks like in that screenshot, then yeah, you definitely need like software like that