Skip to content

Commit c0af83f

Browse files
committed
Docs
1 parent e3f6bd7 commit c0af83f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ $ npm install -g git-stats
1212
```
1313

1414
### 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.
1616

1717
#### Using `git` hooks
1818
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
3131
#### Overriding the `git` command
3232
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`.
3333

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:
3535

3636
```sh
3737
# Override the Git command

0 commit comments

Comments
 (0)