-
Notifications
You must be signed in to change notification settings - Fork 1
Chore: [AEA-0000] - use gitleaks for secret scanning #97
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -75,15 +75,14 @@ repos: | |||||||||
| types_or: [sh, shell] | ||||||||||
| pass_filenames: false | ||||||||||
|
|
||||||||||
| - repo: local | ||||||||||
| hooks: | ||||||||||
| - id: git-secrets | ||||||||||
| name: Git Secrets | ||||||||||
| description: git-secrets scans commits, commit messages, and --no-ff merges to prevent adding secrets into your git repositories. | ||||||||||
| - id: gitleaks | ||||||||||
| name: Git Leaks | ||||||||||
| description: gitleaks scans commits, commit messages, and --no-ff merges to | ||||||||||
| prevent adding secrets into your git repositories. | ||||||||||
| entry: bash | ||||||||||
| args: | ||||||||||
| - -c | ||||||||||
| - 'git-secrets --pre_commit_hook' | ||||||||||
| - "gitleaks git --pre-commit --redact --staged --verbose" | ||||||||||
| language: system | ||||||||||
|
||||||||||
| language: system | |
| language: system | |
| pass_filenames: false | |
| always_run: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description claims this hook scans commit messages and
--no-ffmerges, butdefault_stagesispre-commitand this command is run in the pre-commit stage. Either adjust the description to match what’s actually being scanned (e.g., staged changes), or add an explicitcommit-msgstage hook if commit message scanning is required.