Dive into a file's history to find root cause
Dual-licensed under MIT or Apache 2.0
git-dive is for better understanding why a change was made. Frequently, we
work on code bases we didn't start which have too little documentation. Even
worse if the original authors are not around. git-blame is an invaluable
tool for this but it requires a lot of ceremony to get the information you
need.
Features
- Git-native experience
- Syntax highlighting
- Focuses on relative references (e.g. HEAD~10)
- More room for code by merging the SHA and Time columns into a rev column
- Easier to compare timestamps via the rev column (e.g. HEAD~10)
- Easier to remember, avoiding the need for copy/pasting SHAs
- Focuses on "blaming" merge-commits (PRs) to more quickly see the whole context for a change
- Easy to find relevant config with git dive --dump-config -
Planned Features - Interactive pager that let's you browse through time - Reverse blame
git-dive was inspired by perforce time lapse
view.
Download a pre-built binary (installable via gh-install).
Or use rust to install:
console
$ cargo install git-dive
See the uninstall method for your installer.