docs: add security warning for .env files#5
Closed
shrwnsan wants to merge 1 commit into
Closed
Conversation
Add warning to README about not committing .env files to version control. The .gitignore already covers .env, but users should be explicitly reminded before adding secrets. Resolves #3 Co-Authored-By: GLM <zai-org@users.noreply.github.com>
Owner
Author
|
Closing as out of scope - see issue #3 for rationale. |
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.
Summary
Add warning to README about not committing .env files to version
control. The .gitignore already covers .env, but users should
be explicitly reminded before adding secrets.
Security Impact
Prevents accidental credential leakage to repository history.
Related
Resolves #3
🤖 Generated by Claude Code - GLM 4.7