mirror of
https://github.com/IonicaBizau/git-stats.git
synced 2025-01-03 10:22:11 +01:00
Docs
This commit is contained in:
parent
e3f6bd79c9
commit
c0af83f6a3
1 changed files with 2 additions and 2 deletions
|
@ -12,7 +12,7 @@ $ npm install -g git-stats
|
||||||
```
|
```
|
||||||
|
|
||||||
### Catching the `git commit` command
|
### Catching the `git commit` command
|
||||||
Would you like to catch and automatically store the commits when you do `git commit`?
|
Would you like to catch and automatically store the commits when you do `git commit`? If so, try one of the following solutions.
|
||||||
|
|
||||||
#### Using `git` hooks
|
#### Using `git` hooks
|
||||||
The way I recommend to track your git commits is to use git hooks. Run the following command to initialize the `post-commit` git hook.
|
The way I recommend to track your git commits is to use git hooks. Run the following command to initialize the `post-commit` git hook.
|
||||||
|
@ -31,7 +31,7 @@ step will not be needed after clonning a repository (the git hooks will be added
|
||||||
#### Overriding the `git` command
|
#### Overriding the `git` command
|
||||||
One of the solutions is becoming a mad scientist, overriding the `git` command with a function. However, this may not work for you if you're using `zsh`.
|
One of the solutions is becoming a mad scientist, overriding the `git` command with a function. However, this may not work for you if you're using `zsh`.
|
||||||
|
|
||||||
If so, put the following lines in your `~/.bashrc` (or `~/.bash_profile` on OS X) file:
|
Add the following lines in your `~/.bashrc` (or `~/.bash_profile` on OS X) file:
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
# Override the Git command
|
# Override the Git command
|
||||||
|
|
Loading…
Reference in a new issue