gitleaks hooks #9
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔒 Add Git-leaks Pre-commit Hook
This PR adds a pre-commit configuration with git-leaks to automatically detect and prevent commits containing secrets, API keys, passwords, and other sensitive information.
What's Changed
Added .pre-commit-config.yaml with git-leaks hook
Configured git-leaks v8.28.0 with verbose and redacted output
Pre-commit hooks are now installed and active
Why This Matters
Security: Prevents accidental commits of sensitive data
Compliance: Ensures repository follows security best practices
Automation: Runs automatically on every commit
Team Safety: Protects all contributors from security mistakes
How It Works
Git-leaks scans all staged files before each commit
If secrets are detected, the commit is blocked
Verbose output shows what was found (redacted for security)
Contributors can fix issues before committing
Testing
✅ The setup has been tested and verified to work correctly
✅ Test commits containing secrets are properly blocked
✅ Normal commits without secrets proceed as expected
Next Steps
After merging this PR:
All team members should run pre-commit install in their local repos
Existing secrets in the repository should be rotated if any are found
Consider running gitleaks detect on the entire repository history
This change enhances our security posture and helps maintain clean, secure code.