Working with .gitignore

Not every file in your project should be tracked by Git. Dependencies, build artifacts, system files, and especially sensitive data like API keys should never be committed to version control. The .gitignore file is your guardian against these mistakes. In this lesson, you'll learn how .gitignore works, master ignore patterns and wildcards, protect sensitive information, use templates for different project types, and handle files that were accidentally committed. Proper use of .gitignore keeps repositories clean, secure, and professional!

What Is .gitignore?

.gitignore is a special file that tells Git which files and directories to exclude from version control.

Why Use .gitignore?

Security: Prevent committing passwords, API keys, secrets
Cleanliness: Exclude dependencies, build artifacts, logs
Performance: Smaller repositories, faster operations
Relevance: Only track source code, not generated files
Cross-platform: Ignore OS-specific files (.DS_Store, Thumbs.db)
Editor files: Exclude IDE configurations (.vscode/, .idea/)

What NOT to commit:

Dependencies (node_modules/, vendor/)
Build output (dist/, build/, *.exe)
Environment files (.env, .env.local)
Secrets (API keys, certificates, passwords)
Log files (*.log, logs/)
System files (.DS_Store, Thumbs.db)
Editor configs (.vscode/, .idea/)
Temporary files (*.tmp, *.cache)

How .gitignore Works

Files matching patterns in .gitignore are:

Not shown in git status as untracked
Not staged when you run git add .
Not included in commits
Still present in your working directory (not deleted)

📝 .gitignore Is Just a Text File

.gitignore is a simple text file with one pattern per line. You can edit it with any text editor. The dot (.) at the beginning makes it a hidden file on Unix systems.

Creating a .gitignore File

Method 1: Create Manually

BASH

# In your repository root
touch .gitignore

# Edit it
nano .gitignore
# or
code .gitignore

Method 2: Create with Initial Content

BASH

# Create with basic Node.js ignores
cat > .gitignore << EOF
node_modules/
.env
*.log
dist/
EOF

Method 3: Use GitHub Templates

When creating a repository on GitHub:

During repository creation
Click "Add .gitignore" dropdown
Choose your language/framework (Node, Python, Java, etc.)
GitHub adds a pre-configured .gitignore

Method 4: Use gitignore.io

Generate custom .gitignore files at gitignore.io:

Enter your stack (e.g., "Node, macOS, VSCode")
Get a comprehensive .gitignore
Copy to your project

Pro Tip: Commit .gitignore to your repository so everyone on the team uses the same ignore rules!

Pattern Syntax and Rules

Basic Patterns

1. Exact Match

GITIGNORE

# Ignore specific file
secret.txt

# Ignore specific directory (trailing slash)
logs/

# This ignores:
# - logs/ in root
# - any/path/logs/ anywhere in project

2. Wildcards (*)

GITIGNORE

# Ignore all .log files
*.log

# Ignore all .txt files in any directory
*.txt

# Ignore files starting with 'temp'
temp*

# Ignore files ending with '.backup'
*.backup

3. Question Mark (?)

GITIGNORE

# Matches single character
# Ignores file1.txt, fileA.txt, but not file10.txt
file?.txt

4. Character Ranges ([...])

GITIGNORE

# Ignore file0.txt through file9.txt
file[0-9].txt

# Ignore fileA.txt, fileB.txt, fileC.txt
file[ABC].txt

5. Double Asterisk (**)

GITIGNORE

# Ignore .log files in any subdirectory
**/*.log

# Ignore node_modules anywhere in the tree
**/node_modules/

# Ignore all files in any 'temp' directory
**/temp/*

6. Negation (!)

GITIGNORE

# Ignore all .txt files
*.txt

# But track important.txt
!important.txt

# Ignore all files in logs/
logs/*

# But track logs/keep.log
!logs/keep.log

7. Comments (#)

GITIGNORE

# This is a comment
# Comments help explain why things are ignored

# Dependencies
node_modules/

# Environment variables
.env*

# Build output
dist/
build/

Pattern Rules Summary

TEXT

Pattern          | Matches
-----------------|----------------------------------
file.txt         | Specific file in root or anywhere
*.log            | All .log files
logs/            | Directory named 'logs' anywhere
/logs/           | Only 'logs' in root directory
**/logs/         | 'logs' in any subdirectory
*.log            | Any .log file anywhere
**/*.log         | .log files in any subdirectory
!important.log   | Exception: don't ignore this
file[0-9].txt    | file0.txt through file9.txt
temp?            | temp1, tempA, etc. (1 character)
#comment         | Comment line (ignored by Git)

Common .gitignore Patterns

Node.js / JavaScript Projects

.gitignore

# Dependencies
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*

# Environment variables
.env
.env.local
.env.development.local
.env.test.local
.env.production.local

# Build output
dist/
build/
.next/
out/

# Misc
.DS_Store
*.pem
.vscode/
.idea/

# Testing
coverage/
.nyc_output/

# Cache
.cache/
.parcel-cache/
.npm/

Python Projects

.gitignore

# Byte-compiled / optimized
__pycache__/
*.py[cod]
*$py.class

# Virtual environments
venv/
env/
ENV/
.venv

# Distribution / packaging
dist/
build/
*.egg-info/
.eggs/

# Unit test / coverage
.pytest_cache/
.coverage
htmlcov/

# Environment variables
.env
*.env

# IDEs
.vscode/
.idea/
*.swp
*.swo

# OS
.DS_Store
Thumbs.db

Java Projects

.gitignore

# Compiled class files
*.class

# Package files
*.jar
*.war
*.ear

# Build directories
target/
build/
out/

# IDE
.idea/
*.iml
.eclipse/
.settings/

# Gradle
.gradle/
gradle-app.setting

# Maven
pom.xml.tag
pom.xml.releaseBackup

# Log files
*.log

# OS
.DS_Store
Thumbs.db

React / Next.js Specific

.gitignore

# Dependencies
node_modules/
/.pnp
.pnp.js

# Next.js
.next/
out/
next-env.d.ts

# Production
build/
dist/

# Debug
npm-debug.log*
yarn-debug.log*

# Environment
.env*.local
.env

# Vercel
.vercel

# Testing
coverage/

# Misc
.DS_Store
*.pem
.vscode/
.idea/

WordPress Projects

.gitignore

# WordPress core files
/wp-admin/
/wp-includes/
/wp-content/uploads/
wp-config.php

# Plugins (track only custom)
/wp-content/plugins/*
!/wp-content/plugins/my-custom-plugin/

# Themes (track only custom)
/wp-content/themes/*
!/wp-content/themes/my-custom-theme/

# Cache
/wp-content/cache/

# Backups
*.sql
*.sql.gz

# Log files
*.log

Protecting Sensitive Data

Environment Variables

Never commit files containing secrets:

.gitignore

# Environment files
.env
.env.local
.env.development
.env.production
.env.*.local

# Configuration with secrets
config/secrets.yml
config/database.yml
credentials.json

# API keys
*api-key*
*apikey*
*.key
*.pem

Create Example Files Instead

Provide templates without actual secrets:

.env.example

# Copy this file to .env and fill in your values
DATABASE_URL=postgresql://user:password@localhost:5432/dbname
API_KEY=your_api_key_here
SECRET_KEY=your_secret_key_here
STRIPE_KEY=sk_test_your_stripe_key

In .gitignore:

GITIGNORE

# Ignore actual env file
.env

# But track the example
!.env.example

🔒 Security First

Critical Security Rules:

Never commit passwords, API keys, or tokens
Never commit database credentials
Never commit SSL certificates or private keys
Use environment variables for secrets
Always add .env to .gitignore BEFORE committing anything

If You Already Committed Secrets

IMPORTANT: If you've already committed secrets:

Immediately rotate/change the secret (the old one is compromised!)
Remove it from Git history (see next section)
Add it to .gitignore so it doesn't happen again

Handling Already-Tracked Files

.gitignore only affects untracked files. If a file is already tracked, adding it to .gitignore won't remove it from Git.

Stop Tracking a File (Keep Locally)

BASH

# Remove from Git but keep in working directory
git rm --cached filename

# For directories
git rm --cached -r directory/

# Example: Stop tracking .env
git rm --cached .env

# Commit the removal
git commit -m "Stop tracking .env file"

# Now .env is ignored (make sure it's in .gitignore)

Complete Example

BASH

# Scenario: You committed .env by mistake

# 1. Add to .gitignore
echo ".env" >> .gitignore

# 2. Remove from Git (keep local copy)
git rm --cached .env

# 3. Commit the change
git commit -m "Remove .env from version control"

# 4. Push
git push

# Now .env exists locally but isn't tracked by Git

Remove Sensitive File from History

If you committed sensitive data, you need to remove it from Git history:

BASH

# Method 1: Using git filter-repo (recommended)
# Install: pip install git-filter-repo

git filter-repo --path secrets.txt --invert-paths

# Method 2: Using BFG Repo-Cleaner
# Download from: https://rtyley.github.io/bfg-repo-cleaner/

java -jar bfg.jar --delete-files secrets.txt

# After either method:
git push --force

Warning: Rewriting history is destructive!

Coordinate with team before doing this
Everyone will need to re-clone the repository
The secret is still in old clones—rotate it immediately!

Where to Put .gitignore

Repository Root (Most Common)

TEXT

my-project/
├── .gitignore          ← Main ignore file
├── src/
├── tests/
└── package.json

Subdirectories (For Specific Ignores)

TEXT

my-project/
├── .gitignore          ← General ignores
├── frontend/
│   └── .gitignore      ← Frontend-specific ignores
├── backend/
│   └── .gitignore      ← Backend-specific ignores
└── docs/

Global .gitignore (Personal Preferences)

For files you never want to track in any repository:

BASH

# Create global gitignore
touch ~/.gitignore_global

# Add your personal ignores
cat > ~/.gitignore_global << EOF
# OS files
.DS_Store
Thumbs.db

# Editor files
.vscode/
.idea/
*.swp
*.swo

# Personal notes
TODO.md
NOTES.md
EOF

# Configure Git to use it
git config --global core.excludesfile ~/.gitignore_global

💡 Global vs Repository .gitignore

Global: Personal preferences (editor, OS files)

Repository: Project-specific files (dependencies, build artifacts)

Use both! Global for your personal setup, repository for team-wide rules.

Debugging .gitignore Issues

Check If File Is Ignored

BASH

# Check specific file
git check-ignore -v debug.log

# Output shows which rule is matching:
# .gitignore:3:*.log    debug.log
#           ↑ line number ↑ pattern

# Check multiple files
git check-ignore -v *.log

See All Ignored Files

BASH

# Show ignored files in status
git status --ignored

# List all ignored files
git ls-files --others --ignored --exclude-standard

Common Issues

Issue 1: File Not Being Ignored

Problem: Added file to .gitignore but it still shows in git status

Cause: File was already tracked before being added to .gitignore

Solution:

BASH

git rm --cached filename
git commit -m "Stop tracking filename"

Issue 2: Wrong Pattern

BASH

# ❌ This only ignores 'logs' in root
/logs/

# ✅ This ignores 'logs' anywhere
logs/
# or
**/logs/

# Test your pattern
git check-ignore -v path/to/file

Issue 3: Whitespace Issues

Trailing whitespace in .gitignore can cause issues!

GITIGNORE

# ❌ Has trailing space (won't work)
*.log 

# ✅ No trailing space (works)
*.log

Practice .gitignore Commands

Try these commands to work with .gitignore:

Practice .gitignore Commands

Explore ignored files and debug patterns

Try these examples:

.gitignore Best Practices

1. Add .gitignore Early

Create .gitignore before your first commit to avoid accidentally tracking unwanted files.

2. Start with a Template

Use gitignore.io or GitHub templates for your language/framework.

3. Comment Your Ignores

GITIGNORE

# Dependencies - regenerated from package.json
node_modules/

# Environment variables - contains secrets
.env

# Build output - generated by webpack
dist/
build/

# Editor config - personal preferences
.vscode/
.idea/

4. Organize by Category

GITIGNORE

# ===========================
# Dependencies
# ===========================
node_modules/
vendor/

# ===========================
# Environment & Secrets
# ===========================
.env
.env.local
*.key
*.pem

# ===========================
# Build Output
# ===========================
dist/
build/
*.exe

# ===========================
# Development
# ===========================
*.log
.DS_Store
.vscode/

5. Be Specific When Possible

GITIGNORE

# ❌ Too broad - might ignore important files
*.json

# ✅ Specific - only ignore what you mean to
package-lock.json
tsconfig.json

6. Use Exceptions Carefully

GITIGNORE

# Ignore all .env files
.env*

# Except the example file
!.env.example

7. Don't Ignore .gitignore Itself

The .gitignore file should be committed so everyone uses the same rules!

8. Review Regularly

As your project evolves, update .gitignore to match new patterns.

Starter .gitignore Templates

Minimal Universal Template

.gitignore

# Environment variables
.env
.env.local

# Dependencies (add your language's dependency folder)
node_modules/

# Build output
dist/
build/

# Logs
*.log

# OS files
.DS_Store
Thumbs.db

# Editor directories
.vscode/
.idea/

Full Stack Web Project

.gitignore

# Dependencies
node_modules/
vendor/

# Environment
.env
.env.local
.env.*.local

# Build
dist/
build/
.next/
out/

# Database
*.sqlite
*.db
*.sql

# Logs
*.log
logs/

# Testing
coverage/
.nyc_output/

# Cache
.cache/
.npm/
.eslintcache

# Editor
.vscode/
.idea/
*.swp
*.swo

# OS
.DS_Store
Thumbs.db
desktop.ini

# Misc
*.pem
.vercel

Key Takeaways

.gitignore tells Git which files to exclude from version control
Create .gitignore before your first commit to avoid mistakes
Never commit secrets, API keys, or sensitive data—use .env and .gitignore
Use templates from gitignore.io or GitHub for your stack
Common ignores: node_modules/, .env, dist/, *.log, .DS_Store
Already-tracked files need git rm --cached to be ignored
Use git check-ignore -v to debug why files are ignored
Commit .gitignore itself so the team shares ignore rules
Use global .gitignore for personal preferences (editor, OS files)
Patterns: * (wildcard), / (directory), ! (exception), # (comment)

What's Next?

Excellent work! You now understand how to use .gitignore to keep your repositories clean, secure, and professional. Proper .gitignore usage is essential for every project!

In the final lesson, we'll cover Common Git Problems & Solutions. You'll learn to troubleshoot typical Git issues, recover from mistakes, fix detached HEAD state, undo unwanted changes, and handle emergency situations. This troubleshooting guide will help you confidently solve problems when things go wrong!

🎯 Practice Assignment

Before the final lesson:

Review your current projects—do they have proper .gitignore files?
Create or update .gitignore using a template from gitignore.io
Check if any sensitive files were accidentally committed
Set up a global .gitignore for your personal editor/OS preferences
Use git check-ignore -v to verify your patterns work
Create .env.example files for projects with environment variables

Good .gitignore habits prevent security issues and keep repositories clean!

Test Your Understanding of .gitignore

Question 1 of 4

What is the purpose of .gitignore?

Current Score0 / 0

What Is .gitignore?

.gitignore is a special file that tells Git which files and directories to exclude from version control.

Why Use .gitignore?

Security: Prevent committing passwords, API keys, secrets
Cleanliness: Exclude dependencies, build artifacts, logs
Performance: Smaller repositories, faster operations
Relevance: Only track source code, not generated files
Cross-platform: Ignore OS-specific files (.DS_Store, Thumbs.db)
Editor files: Exclude IDE configurations (.vscode/, .idea/)

What NOT to commit:

Dependencies (node_modules/, vendor/)
Build output (dist/, build/, *.exe)
Environment files (.env, .env.local)
Secrets (API keys, certificates, passwords)
Log files (*.log, logs/)
System files (.DS_Store, Thumbs.db)
Editor configs (.vscode/, .idea/)
Temporary files (*.tmp, *.cache)

How .gitignore Works

Files matching patterns in .gitignore are:

Not shown in git status as untracked
Not staged when you run git add .
Not included in commits
Still present in your working directory (not deleted)

📝 .gitignore Is Just a Text File

.gitignore is a simple text file with one pattern per line. You can edit it with any text editor. The dot (.) at the beginning makes it a hidden file on Unix systems.

Creating a .gitignore File

Method 1: Create Manually

BASH

# In your repository root
touch .gitignore

# Edit it
nano .gitignore
# or
code .gitignore

Method 2: Create with Initial Content

BASH

# Create with basic Node.js ignores
cat > .gitignore << EOF
node_modules/
.env
*.log
dist/
EOF

Method 3: Use GitHub Templates

When creating a repository on GitHub:

During repository creation
Click "Add .gitignore" dropdown
Choose your language/framework (Node, Python, Java, etc.)
GitHub adds a pre-configured .gitignore

Method 4: Use gitignore.io

Generate custom .gitignore files at gitignore.io:

Enter your stack (e.g., "Node, macOS, VSCode")
Get a comprehensive .gitignore
Copy to your project

Pro Tip: Commit .gitignore to your repository so everyone on the team uses the same ignore rules!

Pattern Syntax and Rules

Basic Patterns

1. Exact Match

GITIGNORE

# Ignore specific file
secret.txt

# Ignore specific directory (trailing slash)
logs/

# This ignores:
# - logs/ in root
# - any/path/logs/ anywhere in project

2. Wildcards (*)

GITIGNORE

# Ignore all .log files
*.log

# Ignore all .txt files in any directory
*.txt

# Ignore files starting with 'temp'
temp*

# Ignore files ending with '.backup'
*.backup

3. Question Mark (?)

GITIGNORE

# Matches single character
# Ignores file1.txt, fileA.txt, but not file10.txt
file?.txt

4. Character Ranges ([...])

GITIGNORE

# Ignore file0.txt through file9.txt
file[0-9].txt

# Ignore fileA.txt, fileB.txt, fileC.txt
file[ABC].txt

5. Double Asterisk (**)

GITIGNORE

# Ignore .log files in any subdirectory
**/*.log

# Ignore node_modules anywhere in the tree
**/node_modules/

# Ignore all files in any 'temp' directory
**/temp/*

6. Negation (!)

GITIGNORE

# Ignore all .txt files
*.txt

# But track important.txt
!important.txt

# Ignore all files in logs/
logs/*

# But track logs/keep.log
!logs/keep.log

7. Comments (#)

GITIGNORE

# This is a comment
# Comments help explain why things are ignored

# Dependencies
node_modules/

# Environment variables
.env*

# Build output
dist/
build/

Pattern Rules Summary

TEXT

Pattern          | Matches
-----------------|----------------------------------
file.txt         | Specific file in root or anywhere
*.log            | All .log files
logs/            | Directory named 'logs' anywhere
/logs/           | Only 'logs' in root directory
**/logs/         | 'logs' in any subdirectory
*.log            | Any .log file anywhere
**/*.log         | .log files in any subdirectory
!important.log   | Exception: don't ignore this
file[0-9].txt    | file0.txt through file9.txt
temp?            | temp1, tempA, etc. (1 character)
#comment         | Comment line (ignored by Git)

Common .gitignore Patterns

Node.js / JavaScript Projects

.gitignore

# Dependencies
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*

# Environment variables
.env
.env.local
.env.development.local
.env.test.local
.env.production.local

# Build output
dist/
build/
.next/
out/

# Misc
.DS_Store
*.pem
.vscode/
.idea/

# Testing
coverage/
.nyc_output/

# Cache
.cache/
.parcel-cache/
.npm/

Python Projects

.gitignore

# Byte-compiled / optimized
__pycache__/
*.py[cod]
*$py.class

# Virtual environments
venv/
env/
ENV/
.venv

# Distribution / packaging
dist/
build/
*.egg-info/
.eggs/

# Unit test / coverage
.pytest_cache/
.coverage
htmlcov/

# Environment variables
.env
*.env

# IDEs
.vscode/
.idea/
*.swp
*.swo

# OS
.DS_Store
Thumbs.db

Java Projects

.gitignore

# Compiled class files
*.class

# Package files
*.jar
*.war
*.ear

# Build directories
target/
build/
out/

# IDE
.idea/
*.iml
.eclipse/
.settings/

# Gradle
.gradle/
gradle-app.setting

# Maven
pom.xml.tag
pom.xml.releaseBackup

# Log files
*.log

# OS
.DS_Store
Thumbs.db

React / Next.js Specific

.gitignore

# Dependencies
node_modules/
/.pnp
.pnp.js

# Next.js
.next/
out/
next-env.d.ts

# Production
build/
dist/

# Debug
npm-debug.log*
yarn-debug.log*

# Environment
.env*.local
.env

# Vercel
.vercel

# Testing
coverage/

# Misc
.DS_Store
*.pem
.vscode/
.idea/

WordPress Projects

.gitignore

# WordPress core files
/wp-admin/
/wp-includes/
/wp-content/uploads/
wp-config.php

# Plugins (track only custom)
/wp-content/plugins/*
!/wp-content/plugins/my-custom-plugin/

# Themes (track only custom)
/wp-content/themes/*
!/wp-content/themes/my-custom-theme/

# Cache
/wp-content/cache/

# Backups
*.sql
*.sql.gz

# Log files
*.log

Protecting Sensitive Data

Environment Variables

Never commit files containing secrets:

.gitignore

# Environment files
.env
.env.local
.env.development
.env.production
.env.*.local

# Configuration with secrets
config/secrets.yml
config/database.yml
credentials.json

# API keys
*api-key*
*apikey*
*.key
*.pem

Create Example Files Instead

Provide templates without actual secrets:

.env.example

# Copy this file to .env and fill in your values
DATABASE_URL=postgresql://user:password@localhost:5432/dbname
API_KEY=your_api_key_here
SECRET_KEY=your_secret_key_here
STRIPE_KEY=sk_test_your_stripe_key

In .gitignore:

GITIGNORE

# Ignore actual env file
.env

# But track the example
!.env.example

🔒 Security First

Critical Security Rules:

Never commit passwords, API keys, or tokens
Never commit database credentials
Never commit SSL certificates or private keys
Use environment variables for secrets
Always add .env to .gitignore BEFORE committing anything

If You Already Committed Secrets

IMPORTANT: If you've already committed secrets:

Immediately rotate/change the secret (the old one is compromised!)
Remove it from Git history (see next section)
Add it to .gitignore so it doesn't happen again

Handling Already-Tracked Files

.gitignore only affects untracked files. If a file is already tracked, adding it to .gitignore won't remove it from Git.

Stop Tracking a File (Keep Locally)

BASH

# Remove from Git but keep in working directory
git rm --cached filename

# For directories
git rm --cached -r directory/

# Example: Stop tracking .env
git rm --cached .env

# Commit the removal
git commit -m "Stop tracking .env file"

# Now .env is ignored (make sure it's in .gitignore)

Complete Example

BASH

# Scenario: You committed .env by mistake

# 1. Add to .gitignore
echo ".env" >> .gitignore

# 2. Remove from Git (keep local copy)
git rm --cached .env

# 3. Commit the change
git commit -m "Remove .env from version control"

# 4. Push
git push

# Now .env exists locally but isn't tracked by Git

Remove Sensitive File from History

If you committed sensitive data, you need to remove it from Git history:

BASH

# Method 1: Using git filter-repo (recommended)
# Install: pip install git-filter-repo

git filter-repo --path secrets.txt --invert-paths

# Method 2: Using BFG Repo-Cleaner
# Download from: https://rtyley.github.io/bfg-repo-cleaner/

java -jar bfg.jar --delete-files secrets.txt

# After either method:
git push --force

Warning: Rewriting history is destructive!

Coordinate with team before doing this
Everyone will need to re-clone the repository
The secret is still in old clones—rotate it immediately!

Where to Put .gitignore

Repository Root (Most Common)

TEXT

my-project/
├── .gitignore          ← Main ignore file
├── src/
├── tests/
└── package.json

Subdirectories (For Specific Ignores)

TEXT

my-project/
├── .gitignore          ← General ignores
├── frontend/
│   └── .gitignore      ← Frontend-specific ignores
├── backend/
│   └── .gitignore      ← Backend-specific ignores
└── docs/

Global .gitignore (Personal Preferences)

For files you never want to track in any repository:

BASH

# Create global gitignore
touch ~/.gitignore_global

# Add your personal ignores
cat > ~/.gitignore_global << EOF
# OS files
.DS_Store
Thumbs.db

# Editor files
.vscode/
.idea/
*.swp
*.swo

# Personal notes
TODO.md
NOTES.md
EOF

# Configure Git to use it
git config --global core.excludesfile ~/.gitignore_global

💡 Global vs Repository .gitignore

Global: Personal preferences (editor, OS files)

Repository: Project-specific files (dependencies, build artifacts)

Use both! Global for your personal setup, repository for team-wide rules.

Debugging .gitignore Issues

Check If File Is Ignored

BASH

# Check specific file
git check-ignore -v debug.log

# Output shows which rule is matching:
# .gitignore:3:*.log    debug.log
#           ↑ line number ↑ pattern

# Check multiple files
git check-ignore -v *.log

See All Ignored Files

BASH

# Show ignored files in status
git status --ignored

# List all ignored files
git ls-files --others --ignored --exclude-standard

Common Issues

Issue 1: File Not Being Ignored

Problem: Added file to .gitignore but it still shows in git status

Cause: File was already tracked before being added to .gitignore

Solution:

BASH

git rm --cached filename
git commit -m "Stop tracking filename"

Issue 2: Wrong Pattern

BASH

# ❌ This only ignores 'logs' in root
/logs/

# ✅ This ignores 'logs' anywhere
logs/
# or
**/logs/

# Test your pattern
git check-ignore -v path/to/file

Issue 3: Whitespace Issues

Trailing whitespace in .gitignore can cause issues!

GITIGNORE

# ❌ Has trailing space (won't work)
*.log 

# ✅ No trailing space (works)
*.log

Practice .gitignore Commands

Try these commands to work with .gitignore:

Practice .gitignore Commands

Explore ignored files and debug patterns

Try these examples:

.gitignore Best Practices

1. Add .gitignore Early

Create .gitignore before your first commit to avoid accidentally tracking unwanted files.

2. Start with a Template

Use gitignore.io or GitHub templates for your language/framework.

3. Comment Your Ignores

GITIGNORE

# Dependencies - regenerated from package.json
node_modules/

# Environment variables - contains secrets
.env

# Build output - generated by webpack
dist/
build/

# Editor config - personal preferences
.vscode/
.idea/

4. Organize by Category

GITIGNORE

# ===========================
# Dependencies
# ===========================
node_modules/
vendor/

# ===========================
# Environment & Secrets
# ===========================
.env
.env.local
*.key
*.pem

# ===========================
# Build Output
# ===========================
dist/
build/
*.exe

# ===========================
# Development
# ===========================
*.log
.DS_Store
.vscode/

5. Be Specific When Possible

GITIGNORE

# ❌ Too broad - might ignore important files
*.json

# ✅ Specific - only ignore what you mean to
package-lock.json
tsconfig.json

6. Use Exceptions Carefully

GITIGNORE

# Ignore all .env files
.env*

# Except the example file
!.env.example

7. Don't Ignore .gitignore Itself

The .gitignore file should be committed so everyone uses the same rules!

8. Review Regularly

As your project evolves, update .gitignore to match new patterns.

Starter .gitignore Templates

Minimal Universal Template

.gitignore

# Environment variables
.env
.env.local

# Dependencies (add your language's dependency folder)
node_modules/

# Build output
dist/
build/

# Logs
*.log

# OS files
.DS_Store
Thumbs.db

# Editor directories
.vscode/
.idea/

Full Stack Web Project

.gitignore

# Dependencies
node_modules/
vendor/

# Environment
.env
.env.local
.env.*.local

# Build
dist/
build/
.next/
out/

# Database
*.sqlite
*.db
*.sql

# Logs
*.log
logs/

# Testing
coverage/
.nyc_output/

# Cache
.cache/
.npm/
.eslintcache

# Editor
.vscode/
.idea/
*.swp
*.swo

# OS
.DS_Store
Thumbs.db
desktop.ini

# Misc
*.pem
.vercel

Key Takeaways

.gitignore tells Git which files to exclude from version control
Create .gitignore before your first commit to avoid mistakes
Never commit secrets, API keys, or sensitive data—use .env and .gitignore
Use templates from gitignore.io or GitHub for your stack
Common ignores: node_modules/, .env, dist/, *.log, .DS_Store
Already-tracked files need git rm --cached to be ignored
Use git check-ignore -v to debug why files are ignored
Commit .gitignore itself so the team shares ignore rules
Use global .gitignore for personal preferences (editor, OS files)
Patterns: * (wildcard), / (directory), ! (exception), # (comment)

What's Next?

Excellent work! You now understand how to use .gitignore to keep your repositories clean, secure, and professional. Proper .gitignore usage is essential for every project!

🎯 Practice Assignment

Before the final lesson:

Review your current projects—do they have proper .gitignore files?
Create or update .gitignore using a template from gitignore.io
Check if any sensitive files were accidentally committed
Set up a global .gitignore for your personal editor/OS preferences
Use git check-ignore -v to verify your patterns work
Create .env.example files for projects with environment variables

Good .gitignore habits prevent security issues and keep repositories clean!

Test Your Understanding of .gitignore

Question 1 of 4

What is the purpose of .gitignore?

Current Score0 / 0

What Is .gitignore?

Why Use .gitignore?

How .gitignore Works

Creating a .gitignore File

Method 1: Create Manually

Method 2: Create with Initial Content

Method 3: Use GitHub Templates

Method 4: Use gitignore.io

Pattern Syntax and Rules

Basic Patterns

1. Exact Match

2. Wildcards (*)

3. Question Mark (?)

4. Character Ranges ([...])

5. Double Asterisk (**)

6. Negation (!)

7. Comments (#)

Pattern Rules Summary

Common .gitignore Patterns

Node.js / JavaScript Projects

Python Projects

Java Projects

React / Next.js Specific

WordPress Projects

Protecting Sensitive Data

Environment Variables

Create Example Files Instead

If You Already Committed Secrets

Handling Already-Tracked Files

Stop Tracking a File (Keep Locally)

Complete Example

Remove Sensitive File from History

Where to Put .gitignore

Repository Root (Most Common)

Subdirectories (For Specific Ignores)

Global .gitignore (Personal Preferences)

Debugging .gitignore Issues

Check If File Is Ignored

See All Ignored Files

Common Issues

Issue 1: File Not Being Ignored

Issue 2: Wrong Pattern

Issue 3: Whitespace Issues

Practice .gitignore Commands

Practice .gitignore Commands

.gitignore Best Practices

1. Add .gitignore Early

2. Start with a Template

3. Comment Your Ignores

4. Organize by Category

5. Be Specific When Possible

6. Use Exceptions Carefully

7. Don't Ignore .gitignore Itself

8. Review Regularly

Starter .gitignore Templates

Minimal Universal Template

Full Stack Web Project

Key Takeaways

What's Next?

Test Your Understanding of .gitignore

What is the purpose of .gitignore?

Know someone who'd find this guide helpful? Please share!

Never Miss a New Git & GitHub Tutorial

You might also like

UI Components

Developer Tools

HTML Game

Join Our Web Development Training Program

Join Our Social Communities

Git & Github Tutorials

Working with .gitignore

What Is .gitignore?

Why Use .gitignore?

How .gitignore Works

Creating a .gitignore File

Method 1: Create Manually

Method 2: Create with Initial Content

Method 3: Use GitHub Templates

Method 4: Use gitignore.io