Git Notes
HubBenefits of Git and GitHub - Why They MatterGit vs GitHubVersion Control SystemWhat Is GitWhat Is GitHubConfigure Git - User Identity and SettingsCreate GitHub Account - Sign Up GuideFirst Git Repository - Getting StartedInstall Git on Linux - Complete Setup GuideInstall Git on macOS - Installation GuideInstall Git on Windows - Step-by-Step GuideGit Add - Stage ChangesGit Clone - Copy Remote Repositories LocallyGit Commit - Save ChangesGit Diff - Compare Changes in Your RepositoryGit Ignore - Exclude Files from Version ControlGit Init - Initialize RepositoryGit Log - View Commit HistoryGit Status - Check Repository StateGit Fetch - Download Remote Changes Without MergingGit Pull - Fetch and Merge Remote ChangesGit Push - Upload Local Commits to Remote RepositoryGit Remote - Manage Remote Repository ConnectionsLocal Repository - Understanding Your Git Working EnvironmentRemote Repository - Collaborate Through Shared RepositoriesSync Local and Remote - Keep Repositories in HarmonyAmend Commit - Fix Last CommitDelete Branch - Clean Up BranchesGit Reset - Move HEAD and Undo CommitsGit Restore - Discard ChangesGit Revert - Safely Undo ChangesRecover Lost Commits - Reflog GuideFork RepositoryGitHub PagesGitHub Profile SetupGitHub RepositoriesGitHub Stars and WatchersRepository SettingsCode ReviewsGit CloneGit FetchGit PullGit PushGitHub IssuesLabels and MilestonesOpen Source ContributionsGitHub Project BoardsPull Requests - Propose and Review Code ChangesTeam Collaboration with Git and GitHubAutomated Testing with GitHub ActionsCI/CD with GitHub ActionsDeployment Automation with GitHub ActionsIntroduction to GitHub ActionsGitHub Actions RunnersGitHub Actions WorkflowsEnterprise Git Workflows - Scale Git for Large OrganizationsFeature Branch Workflow - Isolate Development WorkGitFlow Workflow - Structured Release ManagementMonorepo Workflow - Manage Multiple Projects in One RepositoryTrunk-Based Development - Ship Code Fast and SafelyDeployment WorkflowsGitHub Pages DeploymentNetlify Deployment from GitHubRender Deployment from GitHubVercel Deployment from GitHubBranch Protection Rules - Secure Your Git BranchesPersonal Access Tokens - Authenticate with GitHubRepository Security Best PracticesSecret Scanning - Detect Leaked Credentials in CodeSigned Commits - Verify Commit Authenticity with GPGSSH Keys - Secure Git Authentication Without PasswordsGit Bisect - Find Bugs with Binary SearchGit Cherry-Pick - Apply Specific Commits to Any BranchGit Hooks - Automate Workflows with Git EventsGit Internals - Understanding How Git Works Under the HoodGit Stash - Temporarily Save Uncommitted ChangesGit Submodules - Manage External Dependencies as Git ReposGit Tag - Mark Important Points in HistoryGit Worktrees - Work on Multiple Branches SimultaneouslyCollaborative Web App ProjectComplete Team Workflow ProjectGitHub Actions Project - Build a CI/CD PipelineOpen Source Project Contribution - Guided ExercisePortfolio Project with Git - Showcase Your SkillsGit Command CheatsheetGit Interview Questions - Comprehensive Preparation GuideGitHub Interview QuestionsScenario-Based Git Interview QuestionsGit Troubleshooting GuideGit Best Practices - Professional Development HabitsCommon Git Errors and Fixes - Quick SolutionsGit Command Reference - Complete Command GuideLearning Resources - Continue Your Git & GitHub EducationBranch Strategies - Choosing the Right Git Branching ModelCreate Branch in Git - Start New Development LinesFast-Forward Merge in Git - Clean Linear HistoryGit BranchGit CheckoutGit MergeGit RebaseMerge Branches in Git - Combine Development WorkMerge Conflicts - Resolve Git Conflicts Like a ProSwitch Branch in Git - Navigate Between Branches
Learn how to use .gitignore files to exclude files and directories from Git tracking. Master patterns, global ignores, and best practices for different project types.
The .gitignore file tells Git which files and directories to exclude from tracking. This is essential for keeping your repository clean by ignoring build artifacts, dependency folders, environment files, and other generated content.
Why Use .gitignore?
Not every file in your project should be tracked by Git:
- Dependencies (
node_modules/,vendor/) — can be reinstalled - Build outputs (
dist/,build/) — can be regenerated - Environment files (
.env) — contain secrets - OS files (
.DS_Store,Thumbs.db) — system-specific - IDE files (
.idea/,.vscode/) — editor-specific settings - Log files (
*.log) — temporary runtime data
Creating a .gitignore File
Create a .gitignore file in your project root:
bash example
touch .gitignoreAdd patterns to ignore:
bash example
# Dependencies
node_modules/
vendor/
# Build output
dist/
build/
*.min.js
*.min.css
# Environment files
.env
.env.local
.env.production
# OS files
.DS_Store
Thumbs.db
# IDE files
.idea/
.vscode/
*.swp
*.swo
# Log files
*.log
npm-debug.log*Gitignore Pattern Syntax
Basic Patterns
| Pattern | What It Matches |
|---|---|
file.txt | File named file.txt in any directory |
/file.txt | File named file.txt only in root |
dir/ | Directory named dir and all its contents |
*.log | All files ending in .log |
*.py[cod] | Files ending in .pyc, .pyo, or .pyd |
doc/*.txt | .txt files in doc/ (not subdirectories) |
doc/**/*.txt | .txt files in doc/ and all subdirectories |
Wildcards and Special Characters
Example
# * matches anything except /
*.txt # All .txt files
temp* # Files starting with "temp"
# ** matches directories recursively
**/logs # logs directory anywhere
logs/** # Everything inside logs/
a/**/b # a/b, a/x/b, a/x/y/b, etc.
# ? matches a single character
file?.txt # file1.txt, fileA.txt, etc.
# [] matches character ranges
*.[oa] # .o and .a files
*.[0-9] # Files ending in a digit
# ! negates a pattern (un-ignore)
*.log # Ignore all log files
!important.log # But keep important.log
Directory vs File Patterns
bash example
# Trailing slash means directory only
build/ # Ignore the build directory
logs/ # Ignore the logs directory
# No trailing slash matches both files and directories
build # Ignores file or directory named "build"Step-by-Step Example
bash example
# Create a new project
mkdir my-project && cd my-project
git init
# Create some files
touch index.js app.css .env secret.key
mkdir node_modules logs
touch node_modules/package.js logs/error.log
# Check status - everything is untracked
git statusOutput
On branch main
No commits yet
Untracked files:
(use "git add <file>..." to include in what will be committed)
.env
app.css
index.js
logs/
node_modules/
secret.keybash example
# Create .gitignore
cat > .gitignore << EOF
node_modules/
logs/
.env
*.key
EOF
# Check status again
git statusOutput
On branch main
No commits yet
Untracked files:
(use "git add <file>..." to include in what will be committed)
.gitignore
app.css
index.js
nothing added to commit but untracked files presentThe ignored files no longer appear in git status.
Global Gitignore
Set up a global gitignore for patterns that apply to all your projects:
bash example
# Create a global gitignore file
touch ~/.gitignore_global
# Configure Git to use it
git config --global core.excludesFile ~/.gitignore_globalAdd common patterns to ~/.gitignore_global:
bash example
# OS generated files
.DS_Store
.DS_Store?
._*
.Spotlight-V100
.Trashes
Thumbs.db
ehthumbs.db
Desktop.ini
# Editor files
*.swp
*.swo
*~
.idea/
.vscode/settings.json
*.sublime-workspaceCommon .gitignore Templates
Node.js Project
bash example
node_modules/
dist/
build/
.env
.env.local
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.npm
.yarn-integrity
coverage/Python Project
Example
__pycache__/
*.py[cod]
*$py.class
*.so
.Python
env/
venv/
.venv/
*.egg-info/
dist/
build/
.pytest_cache/
.coverage
htmlcov/
Java Project
bash example
*.class
*.jar
*.war
*.ear
target/
.gradle/
build/
.settings/
.classpath
.projectReact/Next.js Project
bash example
node_modules/
.next/
out/
build/
.env.local
.env.development.local
.env.test.local
.env.production.local
npm-debug.log*
yarn-debug.log*
coverage/Ignoring Already Tracked Files
If a file is already tracked by Git, adding it to .gitignore will not remove it. You need to untrack it first:
bash example
# Remove file from tracking but keep it locally
git rm --cached filename.txt
# Remove entire directory from tracking
git rm -r --cached node_modules/
# Commit the removal
git commit -m "Remove tracked files that should be ignored"Remove All Ignored Files from Tracking
bash example
# Remove all cached files
git rm -r --cached .
# Re-add everything (gitignore will now take effect)
git add .
# Commit the changes
git commit -m "Apply .gitignore rules to tracked files"Checking Ignore Rules
Test If a File Is Ignored
bash example
git check-ignore -v filename.txtOutput
.gitignore:3:*.txt filename.txt
This shows which rule in which file is causing the ignore.
List All Ignored Files
bash example
git status --ignoredOutput
On branch main
Ignored files:
(use "git add -f <file>..." to include in what will be committed)
.env
logs/
node_modules/Force Adding Ignored Files
Sometimes you need to track a file that matches an ignore pattern:
bash example
# Force add an ignored file
git add -f config/.env.example
# Or use negation in .gitignore
# .gitignore:
# .env*
# !.env.exampleNested .gitignore Files
You can have .gitignore files in subdirectories. Rules apply relative to the directory containing the .gitignore:
project/
├── .gitignore # Root rules
├── src/
│ └── .gitignore # Rules for src/ directory
├── tests/
│ └── .gitignore # Rules for tests/ directory
└── docs/
└── .gitignore # Rules for docs/ directory
Interview Questions
- How do you ignore a file that is already being tracked by Git?
First remove it from the index with git rm --cached filename, then add the pattern to .gitignore, and commit the changes. The file remains on disk but is no longer tracked.
- What is the difference between
.gitignoreand.git/info/exclude?
.gitignore is committed to the repository and shared with all collaborators. .git/info/exclude is local-only and not shared — use it for personal ignore rules that should not affect others.
- How do you ignore all files in a directory but keep the directory itself?
Git does not track empty directories. Add a .gitkeep file inside the directory, then in .gitignore use dir/* followed by !dir/.gitkeep.
- What does the
pattern mean in.gitignore?**
Double asterisk matches directories recursively. For example, /logs matches a logs directory anywhere in the repository, and logs/ matches everything inside the logs directory.
- How can you create a global gitignore that applies to all repositories?
Create a file (e.g., ~/.gitignore_global) and configure Git with git config --global core.excludesFile ~/.gitignore_global. Add OS and editor-specific patterns there.
Exam Focus
Revise definitions, diagrams, examples, and short-answer points for Git Ignore - Exclude Files from Version Control.
Interview Use
Prepare one clear explanation, one practical example, and one common mistake for this Git & GitHub topic.
Search Terms
git-github, git & github, git, github, basics, ignore, git ignore - exclude files from version control
Related Git & GitHub Topics
Continue learning this concept
Git BasicsGit Add - Stage ChangesMaster the git add command for staging changes, understanding the staging area, staging specific files, patterns, and preparing commits for version control.Git BasicsGit Clone - Copy Remote Repositories LocallyLearn how to use git clone to copy remote repositories to your local machine. Understand clone options, shallow clones, and best practices for cloning repositories.Git BasicsGit Commit - Save ChangesComplete guide to git commit command including commit messages, best practices, amending commits, commit history, and working with atomic commits for clean Git history.Git BasicsGit Diff - Compare Changes in Your RepositoryMaster the git diff command to compare changes between commits, branches, and staging areas. Learn diff output format, comparison options, and practical examples.Git BasicsGit Init - Initialize RepositoryLearn git init command to create new repositories, understand .git directory structure, initialize existing projects, and set up repository configuration for version control.Git BasicsGit Log - View Commit HistoryMaster git log command for viewing commit history, formatting output, filtering commits, searching repository history, and understanding repository timeline and evolution.