Ignore local secret environment files - #2
Merged
Merged
Conversation
Mrbaeksang
marked this pull request as ready for review
July 28, 2026 01:47
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
1 participant
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.
What changed
.envand.env.*files by default.env.exampleWhy
A local npm bootstrap token was supplied through
.env. The file was untracked but not ignored, which made accidental publication possible.Impact
Local secret files no longer appear as untracked Git candidates. The actual
.envfile and its value are not included in this pull request.Verification
.envresolves throughgit check-ignore.envlocal permissions were restricted to owner-only (0600).gitignore