|
|
@@ -127,7 +127,7 @@ When running `detect` on a git repository, gitleaks will parse the output of a `
|
|
|
[here](https://github.com/zricethezav/gitleaks/blob/7240e16769b92d2a1b137c17d6bf9d55a8562899/git/git.go#L17-L25)).
|
|
|
[`git log -p` generates patches](https://git-scm.com/docs/git-log#_generating_patch_text_with_p) which gitleaks will use to detect secrets.
|
|
|
You can configure what commits `git log` will range over by using the `--log-opts` flag. `--log-opts` accepts any option for `git log -p`.
|
|
|
-For example, if you wanted to run gitleaks on a range of commits you could use the following command: `gitleaks --source . --log-opts="--all commitA..commitB"`.
|
|
|
+For example, if you wanted to run gitleaks on a range of commits you could use the following command: `gitleaks detect --source . --log-opts="--all commitA..commitB"`.
|
|
|
See the `git log` [documentation](https://git-scm.com/docs/git-log) for more information.
|
|
|
|
|
|
You can scan files and directories by using the `--no-git` option.
|
Zachary Rice