Skip to content

Commit

Permalink
Fix gitleaks by scanning only files (#562)
Browse files Browse the repository at this point in the history
When gitleaks attempts to scan the git history
in a shallow clone, it can trigger the bug
gitleaks/gitleaks#1168.
By disabling git scanning, we should be able to
avoid it.

Signed-off-by: Daniel Grimm <[email protected]>
  • Loading branch information
dgn authored Jan 20, 2025
1 parent e27e1be commit f982921
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Makefile.core.mk
Original file line number Diff line number Diff line change
Expand Up @@ -665,7 +665,7 @@ lint-watches: ## Checks if the operator watches all resource kinds present in He
@hack/lint-watches.sh

lint-secrets: gitleaks ## Checks whether any secrets are present in the repository.
@${GITLEAKS} detect --redact -v
@${GITLEAKS} detect --no-git --redact -v

.PHONY: lint
lint: lint-scripts lint-copyright-banner lint-go lint-yaml lint-helm lint-bundle lint-watches lint-secrets ## Run all linters.
Expand Down

0 comments on commit f982921

Please sign in to comment.