How to make Git forget a tracked file now in .gitignore

Johnny Simpson - May 11 '22 - - Dev Community

When we track a file in git, it can sometimes get cached and remain tracked, even if we add it to our .gitignore file. This is simply because .gitignore prevents files from being added to Git's tracking system, but it will not actively remove those that are already tracked. This can lead to issues when you have something you no longer want to be tracked, but can't seem to remove it from your git repository.

Fortunately, there is an easy way to fix this. git has a built in rm function which lets us remove cached or tracked changes. To run it, you can use the following command to remove a specific file, where [filename] can be removed with the file you wish to stop tracking:

git rm --cached [filename]
Enter fullscreen mode Exit fullscreen mode

Similarly, if an entire directory needs to be removed, use the -r flag which means recursive, to remove an entire directory and everything within it from tracking:

git rm -r --cached [directory]
Enter fullscreen mode Exit fullscreen mode

After running this command, you can then add ammend your commit and push it to your remote:

git add .
git commit -m "Removed tracked files which shouldn't be tracked"
git push
Enter fullscreen mode Exit fullscreen mode

NOTE this will not remove files from your local computer, but it will remove tracking of files from your git repository. It will also remove the files from other developers computers or servers upon your next git pull. Be careful with this command, as I accidentally deleted all images on FJOLT using it a couple of weeks ago. :)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .