265

I have a git repository hosted on Github. After committing many files, I am realizing that I need to create .gitignore and exclude .exe, .obj files.

However, will it automatically remove these committed files from the repository? Is there any way to force that?

Pavan Nagadiya
  • 519
  • 3
  • 8
Madhur Ahuja
  • 21,604
  • 14
  • 69
  • 116
  • 12
    Future googlers may find this extremely useful. Succinct and to the point: https://www.git-tower.com/learn/git/faq/ignore-tracked-files-in-git – Austin Dean Feb 20 '18 at 22:51
  • 4
    Does this answer your question? [How to make Git "forget" about a file that was tracked but is now in .gitignore?](https://stackoverflow.com/questions/1274057/how-to-make-git-forget-about-a-file-that-was-tracked-but-is-now-in-gitignore) – LightCC Jul 27 '20 at 21:33
  • The correct answer [is here](https://stackoverflow.com/a/20241145/6501141https://stackoverflow.com/a/20241145/6501141). If you `git rm --cached` (or just delete the offending files and commit), it can delete those files on checkout. Using `git update-index --skip-worktree ` will remove them from being tracked directly. – LightCC Jul 27 '20 at 21:35

6 Answers6

376

No you cannot force a file that is already committed in the repo to be removed just because it is added to the .gitignore

You have to git rm --cached to remove the files that you don't want in the repo. ( --cached since you probably want to keep the local copy but remove from the repo. ) So if you want to remove all the exe's from your repo do

git rm --cached /\*.exe

(Note that the asterisk * is quoted from the shell - this lets git, and not the shell, expand the pathnames of files and subdirectories)

manojlds
  • 275,671
  • 58
  • 453
  • 409
69

If you have not pushed the changes already:

git rm -r --cached .
git add .
git commit -m 'clear git cache'
git push
slal
  • 2,361
  • 17
  • 26
55

However, will it automatically remove these committed files from the repository?

No. Even with an existing .gitignore you are able to stage "ignored" files with the -f (force) flag. If they files are already commited, they don't get removed automatically.

git rm --cached path/to/ignored.exe
liamvictor
  • 3,161
  • 1
  • 21
  • 25
KingCrunch
  • 124,572
  • 19
  • 146
  • 171
19

I had to remove .idea and target folders and after reading all comments this worked for me:

git rm -r .idea
git rm -r target
git commit -m 'removed .idea folder'

and then push to master

Emanuele
  • 561
  • 1
  • 5
  • 10
5

However, will it automatically remove these committed files from the repository?

No.

The 'best' recipe to do this is using git filter-branch as written about here:

The man page for git-filter-branch contains comprehensive examples.

Note You'll be re-writing history. If you had published any revisions containing the accidentally added files, this could create trouble for users of those public branches. Inform them, or perhaps think about how badly you need to remove the files.

Note In the presence of tags, always use the --tag-name-filter cat option to git filter-branch. It never hurts and will save you the head-ache when you realize later taht you needed it

liamvictor
  • 3,161
  • 1
  • 21
  • 25
sehe
  • 350,152
  • 45
  • 431
  • 590
  • I ran this command it showed Rewrite 57c1f1f04a3ed01f50c3260714cfc82c973ac816 (3/3) WARNING: Ref 'refs/heads/master' is unchanged and nothing happened – Madhur Ahuja Jun 30 '11 at 13:36
  • It is a warning, and most likely means that the master branch did not (yet) contain any revisions with the files to be removed. You can easily check that. If there is a problem, please update the question. **PS:** use -- `--all` to rewrite all (local) branches at once – sehe Jun 30 '11 at 13:46
2

Even after you delete the file(s) and then commit, you will still have those files in history. To delete those, consider using BFG Repo-Cleaner. It is an alternative to git-filter-branch.

Ash
  • 131
  • 1
  • 3