How to Ignore Already Tracked Files in Git

1. Why .gitignore Ignores Untracked Files Only

By design, .gitignore specifies patterns for untracked files. Once a file has been staged and committed, Git tracks it in the index. Git will not stop tracking a file merely because its name matches a new rule in .gitignore.

To make Git obey the .gitignore rule, you must remove the file from Git's index (cache) while leaving the physical file untouched on your local disk.

2. Method 1: Untrack a Single File

Use the --cached flag with git rm:

# 1. Ensure the file is listed in your .gitignore
echo ".env" >> .gitignore

# 2. Remove the file from Git index only (keeps file on disk)
git rm --cached .env

# 3. Commit the change
git commit -m "chore: untrack .env file"

3. Method 2: Untrack an Entire Directory

If you accidentally committed an entire directory (such as node_modules/ or dist/), add the -r recursive flag:

# Remove directory recursively from Git cache without deleting local files
git rm -r --cached node_modules/

# Commit the removal
git commit -m "chore: untrack node_modules directory"

4. Method 3: Refresh the Entire Repository Index

If you added a comprehensive new .gitignore and need Git to apply it across all files in your project:

# 1. Commit or stash any outstanding edits first
git add .
git commit -m "Save work before refreshing index"

# 2. Clear Git cache for the entire repository
git rm -r --cached .

# 3. Re-add all files (respecting newly added .gitignore patterns)
git add .

# 4. Commit the cleaned index
git commit -m "chore: refresh git index with updated .gitignore"