https://github.com/pivaldi/git-diffview
A bash script to view git changes between two paths.
https://github.com/pivaldi/git-diffview
Last synced: 9 months ago
JSON representation
A bash script to view git changes between two paths.
- Host: GitHub
- URL: https://github.com/pivaldi/git-diffview
- Owner: pivaldi
- Created: 2015-10-30T17:39:10.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2023-07-03T08:18:16.000Z (over 2 years ago)
- Last Synced: 2025-02-15T18:52:18.828Z (11 months ago)
- Language: Shell
- Size: 1.95 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# git-diffview
A bash script to show the changes between two git paths as a treeview.
## Installation
```code
sudo curl https://raw.githubusercontent.com/pivaldi/git-diffview/master/git-diffview -o /usr/local/bin/git-diffview
```
## Usage
```code
git diffview [ []]
```
## Suggestion
Add the following line into the [alias] section of your ~/.gitconfig file.
```code
dv = diffview
```
Doing so, you can also use the command like this:
```code
git dv [ []]
```
## Rationale
Let's suppose that you just pulled the changes from a git repository,
and would like to know what happened between the two last commits.
Using the git dialect, this will correspond to what changed between HEAD, and HEAD~.
| HEAD~ | | HEAD | | HEAD~ | | HEAD |
| :--: | ---- | :--: | ---- | :--: | ---- | :--: |
| ⭣ | .... | ⭣ | _ or _ | ⭣ | .... | ⭣ |
| previous | | last | | commit | | commit |
| commit | | commit | | n-1 | | n |
This is what **git diffview** will show you by default.
```code
user@dev:~/project [master]$ git diffview↲
root
├── node-A
│ ├── node-B
│ │ ├── leaf-1
│ │ └── leaf-2
│ └── node-C
│ └── leaf-3
└── node-D
└── leaf-4
```
In the above resulting treeview, you'll easily see that some work has
been done on leaf-1, leaf-2, leaf-3, and leaf-4, under the root
directory in the master branch of the project.
It's now straigthforward to visualize what part of the project tree get
touched.
If you're looking for changes elsewhere in the git history, you can add
one or two additional parameters.
Each of these parameters can be a commit reference (HEAD, or SHA-1
based), or a branch name, as in the **git diff** command.
For example, use **git diffview HEAD~2** for the changes between
commits n and n-2, or **git diffview HEAD~2 HEAD~4** for those between
commits n-2, and n-4.