Add pre-commit hooks for code quality and security checks
#2
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.
Summary
This PR adds comprehensive pre-commit hooks to the Python container template to ensure code quality, security, and consistent formatting across all contributions.
Changes Made
New Files Added
.pre-commit-config.yaml- Pre-commit configuration with multiple hooks:.secrets.baseline- Baseline file for detect-secrets to track known secrets and avoid false positivesFiles Modified
development-requirements.txt- Addedpre-commitandbanditdependenciesMakefile- Added new targets:pre-commit-install- Install pre-commit hookspre-commit-update- Update pre-commit hooks and run checkspre-commit-run- Run pre-commit on all filespre-commit-clean- Remove pre-commit hooksREADME.md- Added comprehensive documentation for:.gitignore- Added exclusions forbandit-report.jsonand.secrets.baselineBenefits
Usage
After merging, developers can set up pre-commit hooks with:
The hooks will automatically run on every commit, ensuring code quality and security standards are maintained.
Testing