-
Notifications
You must be signed in to change notification settings - Fork 165
Add InfoSec's pre-commit hook for secrets detection #8010
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
base: main
Are you sure you want to change the base?
Conversation
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
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.
LGTM
|
💚 Build Succeeded
cc @ycombinator |
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.
Let's first see the pre-commit not failing and then merge this, right? 🙂
Just a heads up: @christophercutajar is looking into a fix to the failure we're seeing in CI:
|
What does this PR do?
This PR adds the pre-commit hook for detecting if secrets are being committed, as recommended by Elastic's InfoSec team.
Why is it important?
To prevent secrets from committed to the Elastic Agent repository.