Describe the bug
Gitleaks exits with exit code 0 when ambiguous argument to log-opts are provided
To Reproduce
Run Gitleaks with log-opts that triggers an error from git log
Expected behavior
When error occurs I would expect exit code 1
** Logging**
8:47AM ERR fatal: ambiguous argument '18ee779d989c28192f5d439a91bcbbd3bf11dac2^..ffc5f83a4f995ed146c27fa32227ddfff251f282': unknown revision or path not in the working tree.
8:47AM ERR Use '--' to separate paths from revisions, like this:
8:47AM ERR 'git [...] -- [...]'
8:47AM INF no leaks found
8:47AM INF scan completed in 30.9416ms
Basic Info (please complete the following information):
- OS:Osx Monterey
- Gitleaks Version: 8.0.4