The flow is: 1. :G blame to blame the current file in a locked split 2. navigate to a line, then hit o to open the commit in another split 3. search for a change of interest, then navigate to either the --- or +++ line and hit o to open the before or after version of the file in another split 4. repeat steps 1-3 as needed to drill to whatever history you need 5. ctrl-w o to kill all the splits and leave you with just the buffer of interest
whereas I'm pretty happy with git CLI for the majority of git interaction, and a graphical client like gitk for visualizing branch history, I haven't found any other history inspection technique or tool that comes close to this.
wonger_•8h ago
cjhveal•7h ago
To that end, I'd probably pick up a good Terminal User Interface like `lazygit` before spending much time investing into fully driving git through vim. Grains of salt suggested, but if you're interested in exploring other git TUI options, I've also heard good things about `gitui`[0].
[0]: https://github.com/gitui-org/gitui
eulgro•4h ago