security: add .gitignore to prevent secret leaks#1
Open
nradawg wants to merge 1 commit into
Open
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
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.
Risk
This is a public repository with no
.gitignore. Without one, any.env, key file, or credential in the working directory can be committed accidentally. Once pushed to a public repo, secrets are considered permanently compromised — they remain in git history forever.Fix
Adds a standard
.gitignorecovering.envvariants, key/cert files, Node build artifacts, logs, and editor folders.Important follow-up
This PR prevents future leaks only. If any secrets have already been committed, they must be rotated at the source — deleting them in a new commit does not purge them from git history.