Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use --no-verify instead of config modification. #49

Open
adborden opened this issue Aug 6, 2021 · 0 comments
Open

Use --no-verify instead of config modification. #49

adborden opened this issue Aug 6, 2021 · 0 comments

Comments

@adborden
Copy link

adborden commented Aug 6, 2021

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:

  git config --local hooks.gitleaks false
  git commit -m "message" 
  git config --local hooks.gitleaks true
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@adborden