Repository navigation
Ignore env and all .env variants - #174
Merged
Merged
Conversation
A file named env containing production API keys and the database password was committed to this public repo on 2026-10-19, because only specific .env names were ignored. Ignore env and every .env* file so neither can be committed again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
On Oct 19, a file named
envcontaining production secrets was committed to this public repo. Google flagged the leaked API key the same day..gitignoreonly listed specific.envnames, so nothing stopped it.Change
Adds two rules to
.gitignore:env.env*, which covers.env,.env.local,.env.productionand similarNo tracked files match either pattern, so nothing currently in the repo is affected.
.dockerignorealready excludes both.Not covered here
Ignoring the file doesn't undo the leak. The leaked keys still need to be rotated or revoked.
🤖 Generated with Claude Code