Add catch-dotenv hook and corresponding tests to manage .env files #1
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.
This pull request introduces a new pre-commit hook to block
.envfiles from being committed to the repository and optionally generate a sanitized.env.examplefile. It also ensures.envis added to.gitignoreautomatically, helping prevent accidental exposure of secrets. The hook is registered in the project configuration and includes a comprehensive test.envfile for validation.New pre-commit hook for dotenv protection:
catch-dotenvhook to.pre-commit-hooks.yamlthat blocks commits containing.envfiles and can generate a value-sanitized.env.examplefile.pre_commit_hooks/catch_dotenv.pyscript, which blocks.envfile commits, updates.gitignorewith a canonical banner and.enventry, and generates.env.examplewith only variable names.setup.cfgfor CLI use.Testing resources:
testing/resources/test.envfile with dummy secrets and various environment variables for testing the hook’s behavior.