Improve .gitignore with additional patterns - #234
Open
MiWeiss wants to merge 1 commit into
Open
Conversation
Enhanced .gitignore with commonly needed patterns: Added entries for: - General log files (*.log) - Environment files (.env, .env.*) - Editor swap files (*.swp, *.swo, *~) - Python cache files (*.pyc, *.pyo, .python-version) - OS files (.DS_Store, Thumbs.db) Organized entries with comments by category: - Node - Build output - Environment files - IDE and editor files - Python - Browser extension - OS files - Jekyll This prevents accidental commits of sensitive data, OS-specific files, and temporary editor files. Co-Authored-By: Claude Sonnet 4.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.
Summary
Changes Made
Added Patterns
General logs:
*.log- All log files (supplements existing npm-debug.log)Environment files:
.envand.env.*- Environment configuration files (may contain secrets)!.env.example- Explicitly allow example env filesEditor files:
*.swp,*.swo- Vim swap files*~- Backup files from various editorsPython:
*.pyc,*.pyo- Python bytecode files.python-version- pyenv version fileOS files:
.DS_Store- macOS folder metadataThumbs.db- Windows thumbnail cacheOrganization
Added comments to group related patterns:
Why This Matters
Security:
.envfiles often contain API keys and secretsCollaboration:
Cleanliness:
Common Scenarios Prevented
.DS_Storefiles.swpfiles that cause conflicts.envfile with production secrets gets committedTest Plan
.env.exampleis still tracked (if it exists)🤖 Generated with Claude Code