Open adborden opened 3 years ago
Any reason why the work-around when you encounter a false positive is to disable hooks, instead of just use the git commit --no-verify option?
git commit --no-verify
Hook output currently recommends:
git config --local hooks.gitleaks false git commit -m "message" git config --local hooks.gitleaks true
Any reason why the work-around when you encounter a false positive is to disable hooks, instead of just use the
git commit --no-verify
option?Hook output currently recommends: