You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ $ npm install -g git-stats
12
12
```
13
13
14
14
### Catching the `git commit` command
15
-
Would you like to catch and automatically store the commits when you do `git commit`?
15
+
Would you like to catch and automatically store the commits when you do `git commit`? If so, try one of the following solutions.
16
16
17
17
#### Using `git` hooks
18
18
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
31
31
#### Overriding the `git` command
32
32
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`.
33
33
34
-
If so, put the following lines in your `~/.bashrc` (or `~/.bash_profile` on OS X) file:
34
+
Add the following lines in your `~/.bashrc` (or `~/.bash_profile` on OS X) file:
0 commit comments