.gitignore is ignored by Git
Asked Answered
H

38

1746

My .gitignore file seems to be being ignored by Git - could the .gitignore file be corrupt? Which file format, locale or culture does Git expect?

My .gitignore:

# This is a comment
debug.log
nbproject/

Output from git status:

# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#       debug.log
#       nbproject/
nothing added to commit but untracked files present (use "git add" to track)

I would like debug.log and nbproject/ not to appear in the untracked files list.

Where should I start looking to fix this?

Haler answered 12/7, 2012 at 12:9 Comment(12)
Make sure your .gitignore file uses ANSI or UTF-8 encoding. If it uses something else like Unicode BOM, it's possible that Git can't read the file.Chit
Possible duplicate of How to make Git "forget" about a file that was tracked but is now in .gitignore?Bluegreen
@Chit this was exactly the problem on my machine (Windows). I has used echo "file" > .gitignore in PowerShell, the file had a UCS-2 encoding!Kaylee
git rm --cached debug.log nbproject/Uranalysis
Why the first comment here is not an answer is beyond meSawhorse
@Sawhorse Amusingly, that was the answer to my question (I'm the op), although it is an answer much further down.Haler
@MattParkins Ah I see it now, it still surprises me that such a simple and to the point answer is buried as a comment or that the actual accepted one is down there. Thanks!Sawhorse
If the files are indeed in the Untracked files list, make sure to chek out for trailing spaces (@Shermy answer)Mcmahan
don't start ur folder names with /folder. That messed me up. Should have been folder/.Joses
@GayanWeerakutti put simply, does that code let go of all historical baggage of code changes tracked by git for debug.log, nbproject/ as well as sets the resp. files to be untracked by git ? 🤔Ariella
@Ariella It only remove the file from the working directory and add that removal into the index. The history is preserved.Uranalysis
@Kaylee That's what I did too. Git For Windows comes with a "touch" program which will create it properly. touch .gitignoreVicereine
H
236

Fixed. OK, I created the .gitignore file in Notepad on Windows and it wasn't working. When I viewed the .gitignore file on Linux it looked like organised gibberish - perhaps Notepad had written out Unicode rather than ASCII or whatever 8-bit is.

So I rewrote the file on my Linux box, and when I pulled it back into Windows it works fine! Hurrah!

Haler answered 12/7, 2012 at 12:30 Comment(18)
In Notepad simply choose the encoding "ANSI" in the "Save As" dialog. Or better yet, get a proper text editor - after all you're a programmer :) ... I can recommend "Programmer's Notepad", others prefer Notepad++ and there are literally hundreds more out there.Portable
hehe, yep, I should have created it in netbeans (which I was using at the time), eclipse or visual studio. I just called it from the commandline thinking it wouldn't make a difference.Haler
We need to use linux/unix like relative path and not the windows path( i.e to use "/" instead of "\") even if you are using windows OS and save it in ANSI as mentioned in previous comment.Englert
My problem was similar - my .gitignore was using UTF8 with a BOM. Just saved it as UTF8 without a BOM and it magically started working.Scrunch
This was my problem. But even if the file looks ok on Linux, if you changed it on Windows and it is being ignore, try do delete it and type it again on Linux. Worked for me.Dowland
Best way for me is to just copy paste working .gitignore and edit that. Thank you.Scauper
This was my problem as well. I had created the .gitignore file with "echo dirName > .gitignore" because Windows makes it such a pain to create files that start with ".". The encoding of the file created this way was unreadable by git, and it interpreted it as a binary file instead. Clicked "Encoding --> UTF-8" in Notepad++, save, done.Cermet
Had the same problem as @Cermet in powershell - the file is by default saved as UTF16.Resourceful
Trailing spaces can get you there, too :)Heigl
I ran into this issue as well, copy/pasting the contents of the VS .gitignore file from Chrome was my problem. I should have directly saved the file somehow else.Hose
I had the same problem as Laura as well. Arghhhh Windows. -_-Bor
Going from a bash to occasionally using powershell - this command "echo someline >somefile" writes out UTF16. What the?Pilatus
For those of you using Notepad++, the option to select is Encoding > Encode in ANSI.Argentina
Leave a comment if you're going to downvote the answer, (this one worked for me)Haler
The common source of problem - line separators. They are two bytes on windows (0d 0a) and one byte in unix (0a). When you move windows file to unix 0d bytes will treat as significant on end of lines. Example: write bash script on windows with shebang [#!/usr/bin/env python3] and try to move to unix, [chmod +x] and run - there will be binary name [python3\x0d] and shell will fail.Fidge
@Argentina Better encode as UTF8 NO BOM.Tuttle
@Portable I do not approve on hating the Notepad++. In my opinion it is the best text editor for Windows. Period. Mostly because if you don't like something about it, you can fix it yourself.Tuttle
@Tuttle good for you. And now perhaps look up the difference (😜) between Notepad, a program that ships with Windows and -- while it has improved over the recent years -- can hardly be called a programmer's editor, and Notepad++ an excellent (small, fast, feature-rich) editor sharing the first few letters. At no point did I hate Notepad++ or discourage its use or even "spread" hate about it. While at the time of my comment I used PN2, I now prefer Notepad++ on systems where I can't have VSCodium or SublimeText. You're a bit late to the party, too ...Portable
I
3524

Even if you haven't tracked the files so far, Git seems to be able to "know" about them even after you add them to .gitignore.

WARNING: First commit or stash your current changes, or you will lose them.

Then run the following commands from the top folder of your Git repository:

git rm -r --cached .
git add .
git commit -m "fixed untracked files"
Incisure answered 12/7, 2012 at 12:20 Comment(29)
i got a "Unknown option: -rm" when trying to run "git -rm -r --cached"Prase
I got "usage: git rm [options] [--] <file>..." printed when I tried "git rm -r --cached". If it matters, I'm using Git from within PowerShell after clicking "Tools->Open a shell here" in GitHub for Windows.Jeanninejeans
on Windows: git rm . -r --cached and git add .Psychometrics
It should be: git rm -r --cached . and git add . The dot is important! It specifies to apply this to all files under the current directory, (so do this when in the top level git directory). I would edit this, but don't have enough reputation.... :)Piddle
Be aware to commit all your changes before, otherwise you will lose control on all the changed files!!Caoutchouc
The first 3 commenters seem to have missed the dot in the end. This means every file. "git -rm -r --cached ." <-- notice the dot.Rhizopod
If rm this file, what happen with this file in server when I push it to server ?Suitor
If anyone is wondering, you can do this for certain files by replacing the . in this answer with the path name in both the rm and add commands.Albacore
Works and is safe to push to server. It just fixes gitignore.Swiss
I'm not sure about the last step, just keep doing git rm and git add, eventually somehow it'll just work, but don't do commit, kinda of scary.Degas
Can't this inadvertently change the Unix file permissions?Morten
If you don't want to commit, a workaround is to put your changes onto the shelf: "git stash". Run the above commands. and run "git stash pop"Scarce
At least on windows this commands lead to all files beeing committed (including files listet in .gitignore). So in my case it's not working/wrong.Shawnshawna
This just solved my issue without wasting a bunch of hours! This answer should be accepted as the solution too.Motoring
TIL that copy pasting multiple lines into GIT bash, immediately executes all lines except the last one.Saidee
The suggested solution added the files I intended to ignore - the exact opposite of what I wanted...Kp
git commit -m "fixed untracked files" . There should be a dot at last.Discussant
I would recommend use list of filenames instead .Oakman
By George it actually worked. Now why does this issue even come up in the first place? seems like the default behavior should be to not let this happen...Whitacre
If this affects such an enormous number of git users, this could be considered a bug or a feature request for intuitiveness. By the way, is this issue reproduced on machines other than Windows? Git installer for Windows has a checkbox to disable caching and it is enabled by default.Hypocaust
faced this issue in ubuntu 16.04. now working perfectKeifer
This removed the .gitignore file from my project leaving me unable to add it back in, no idea why - please be careful with these commands.Nichy
This solution does not work! It's ridiculous how often this issue comes up and how difficult it is to address, even if one is an experienced git user.Scathe
really nice , but i dont understand what is the meaning of first line git commit -m "fixed untracked files"Albaugh
It's 2019, and this is still an issue, reproduced on ma mac. Fixed the issue and made me feel all warm inside. Tickled me just right.Universality
@Scathe you're right as it's imperative to be specific as to what files you're untracking eg. git rm -r --cached debug.log nbproject , while git rm -r --cached . would simple untrack all files in the project ⚠️Ariella
@hosamhemaily the line is a commit command which explains the file/sub-folders that were unindexed from history by git rm -r --chached <file-name>. 👉️ to understand git add . && git commitAriella
Before doin that just type !.gitignore in your gitignore file.Waldemar
The answer is correct in that if a folder or file exists in the repo then the changes will not be ignored by .gitignore. If you want to fix it without using git commands (like if you use Github Desktop) then cut and paste the file/folder out of your local directory. push it, then add them back in. That worked for me.Spilt
P
365

If it seems like Git isn't noticing the changes you made to your .gitignore file, you might want to check the following points:

  • There might be a global .gitignore file that might interfere with your local one

  • When you add something into a .gitignore file, try this:

      git add [uncommitted changes you want to keep] && git commit
      git rm -r --cached .
      git add .
      git commit -m "fixed untracked files"
    
  • If you remove something from a .gitignore file, and the above steps maybe don't work, if you found the above steps are not working, try this:

      git add -f [files you want to track again]
      git commit -m "Refresh removing files from .gitignore file."
    
      // For example, if you want the .java type file to be tracked again,
      // The command should be:
      //     git add -f *.java
    
Podite answered 3/9, 2015 at 13:54 Comment(6)
Perhaps could you edit @AlinHuruba 's answer to add your step 3 ?Moulmein
@Moulmein Thank you for your advice,I didn't find AlinHuruba's answer,I don't known what's the difference,so please tell me directly.Podite
The step 3 is what I needed. Most of the answer just tell how to remove the file which we want to untrack. Thanks for the opposite point of view.Inextricable
Thanks @Podite for the reply. Usually it works for me too but I am having issues within a latex proj, with the main .pdf, which I don't need to commit, as I am working remotely on overleaf. I also checked for empty spaces in the .gitignore ... do you have an idea what's going on? -- maybe you have any idea? (not sure if I should post it as another question) -- ThanksExcruciating
@Excruciating .pdf file is one kind of large file for git,and you must pay attention to the file path and directory path.Podite
the file is 334 kb and the path seems correct ...plus, I am basically using the same .gitignore for other proj., where git is able to ignore the mail .pdf ...very weirdExcruciating
H
236

Fixed. OK, I created the .gitignore file in Notepad on Windows and it wasn't working. When I viewed the .gitignore file on Linux it looked like organised gibberish - perhaps Notepad had written out Unicode rather than ASCII or whatever 8-bit is.

So I rewrote the file on my Linux box, and when I pulled it back into Windows it works fine! Hurrah!

Haler answered 12/7, 2012 at 12:30 Comment(18)
In Notepad simply choose the encoding "ANSI" in the "Save As" dialog. Or better yet, get a proper text editor - after all you're a programmer :) ... I can recommend "Programmer's Notepad", others prefer Notepad++ and there are literally hundreds more out there.Portable
hehe, yep, I should have created it in netbeans (which I was using at the time), eclipse or visual studio. I just called it from the commandline thinking it wouldn't make a difference.Haler
We need to use linux/unix like relative path and not the windows path( i.e to use "/" instead of "\") even if you are using windows OS and save it in ANSI as mentioned in previous comment.Englert
My problem was similar - my .gitignore was using UTF8 with a BOM. Just saved it as UTF8 without a BOM and it magically started working.Scrunch
This was my problem. But even if the file looks ok on Linux, if you changed it on Windows and it is being ignore, try do delete it and type it again on Linux. Worked for me.Dowland
Best way for me is to just copy paste working .gitignore and edit that. Thank you.Scauper
This was my problem as well. I had created the .gitignore file with "echo dirName > .gitignore" because Windows makes it such a pain to create files that start with ".". The encoding of the file created this way was unreadable by git, and it interpreted it as a binary file instead. Clicked "Encoding --> UTF-8" in Notepad++, save, done.Cermet
Had the same problem as @Cermet in powershell - the file is by default saved as UTF16.Resourceful
Trailing spaces can get you there, too :)Heigl
I ran into this issue as well, copy/pasting the contents of the VS .gitignore file from Chrome was my problem. I should have directly saved the file somehow else.Hose
I had the same problem as Laura as well. Arghhhh Windows. -_-Bor
Going from a bash to occasionally using powershell - this command "echo someline >somefile" writes out UTF16. What the?Pilatus
For those of you using Notepad++, the option to select is Encoding > Encode in ANSI.Argentina
Leave a comment if you're going to downvote the answer, (this one worked for me)Haler
The common source of problem - line separators. They are two bytes on windows (0d 0a) and one byte in unix (0a). When you move windows file to unix 0d bytes will treat as significant on end of lines. Example: write bash script on windows with shebang [#!/usr/bin/env python3] and try to move to unix, [chmod +x] and run - there will be binary name [python3\x0d] and shell will fail.Fidge
@Argentina Better encode as UTF8 NO BOM.Tuttle
@Portable I do not approve on hating the Notepad++. In my opinion it is the best text editor for Windows. Period. Mostly because if you don't like something about it, you can fix it yourself.Tuttle
@Tuttle good for you. And now perhaps look up the difference (😜) between Notepad, a program that ships with Windows and -- while it has improved over the recent years -- can hardly be called a programmer's editor, and Notepad++ an excellent (small, fast, feature-rich) editor sharing the first few letters. At no point did I hate Notepad++ or discourage its use or even "spread" hate about it. While at the time of my comment I used PN2, I now prefer Notepad++ on systems where I can't have VSCodium or SublimeText. You're a bit late to the party, too ...Portable
T
125

Without adding another commit to your project, one line will be enough to make .gitignore work as it is supposed to:

git rm -r --cached debug.log nbproject

This will remove them from the repository, but still keep them physically. In plain English, it deletes any history of changes related to them, and also will not track their change in any future commit. You may find a better explanation here.

Trochanter answered 19/3, 2014 at 23:40 Comment(3)
Worked exactly as I wanted - I had only 1 file which was not tracked properly. I saved its contents in notepad, and did: git rm -r --cached someFile.php and it worked like a charm :)Bounty
@FMFF This will remove it from the repository but still keep them physically, in plain English, it deletes any history of changes related to them, and also will not track their change in any future commit. A better explication you may found here: #37280154Billybillycock
I got a "fatal: pathspec 'debug.log' did not match any files"Nonflammable
S
52

Another cause of this issue is blank spaces or tabs before the statement:

Example:

# Be aware of the following:
 notWorkingIgnore.*
workingIgnore.*

And as pointed out by the comment below a trailing space can be an issue as well:

# Be aware of the following:
notWorkingIgnore.* #<-Space
workingIgnore.*#<-Nospace
Shermy answered 23/12, 2013 at 1:48 Comment(2)
A trailing space was my problem, which is even even trickier to find.Daciadacie
Yes, the same here. I thought I could write comments after the file pattern: *.txt # Tex files. But git understands: "Ignore the files with the extension txt "Morten
D
46

I noticed that the encoding of the .gitignore was having an effect--if the file was Unicode, it was ignored, if it was ASCII, it wasn't.

Process:

  1. Verify status: PS> git status
  2. Create a function to Get-FileEncoding
  3. Test .gitignore's encoding: PS> Get-FileEncoding .gitignore
  4. Change the encoding to ASCII: PS> Set-Content .gitignore -Encoding Ascii -Value (Get-Content .gitignore)
  5. Confirm: PS> git status
Dekow answered 13/8, 2015 at 21:14 Comment(2)
1000 thanks for this. I was creating the .gitignore file on my system using the touch .gitignore and echo ".db" >> .gitignore route via powershell. I found that the echo ".db" >> .gitignore" was setting the file encoding to UCS-2 LE-BOM, a quick conversion to ASCII and the gitignore started working.Shores
You can try by skipping Step 2 & 3.Bummalo
P
37

As with the other solutions, commit first and be aware that you will lose any un-committed changes.

I had better results with this:

git rm -r --cached .
git reset HEAD --hard
git status

Note that the status shouldn't have any modified files now.

Pine answered 14/11, 2016 at 23:13 Comment(2)
this one is not working for me but ifeegoo's answer doesDanielledaniels
Lovely jubbley Rodders.Bismuthous
D
25

In my case, it's because the files already exist in the repository and I'm trying to ignore it.

These are the things I did to fix the issue:

  • Copy the files to a temporary folder
  • Remove them from my project folder.
  • Commit the changes which remove those files from the repository
  • Re-added those files to my project folder

By then, any changes I made on those files were ignored.

I think you can't ignore files that already exist on the repository.

Dawdle answered 21/8, 2017 at 8:27 Comment(1)
In my case, they were already staged. Only after doing what you suggest, then attempting to commit and seeing the warning that they had been staged and were removed did I realize that was the problem.Conroy
B
20

All the answers here are actually workarounds. You need to create the .gitignore file before you run git init. Otherwise git will never know you need to ignore those files, because they have been tracked already.

echo .idea/ >> .gitignore
git init

If you develop on a daily basis, I advise you to add your habitual ignored files to your ~/.gitignore_global file. That way, git will already know which files you (meaning "your user", since it's a file in your home directory) usually ignore.

Bodleian answered 25/11, 2015 at 21:21 Comment(2)
~/.gitignore_global is a configurable name. Run git config --global core.excludesfile first to see if you already have a file defined. If not, run git config --global core.excludesfile ~/.gitignore_global.Retrogressive
A workaround if you didn't create .gitignore first: rename the tracked file. .gitignore will be applied as if it were new.Retrogressive
Q
17

Also check out the directory where you put .gitignore.

It should be in the root of your project:

./myproject/.gitignore

Not in

./myproject/.git/.gitignore
Quach answered 14/10, 2014 at 6:32 Comment(0)
P
12

Whenever I encounter the situation that git is tracking a file that is listed in .gitignore, I use the following:

git update-index --skip-worktree <file_name>
Permatron answered 16/4, 2021 at 19:35 Comment(2)
Thanks, this is much cleaner than the other answersBareback
Thanks, this magically fixed my problem!Stacy
D
10

There's another issue with .gitignore that might happen, especially for a Windows user. Git does not like it when you name .gitignore (such as unity.gitignore).

You'll want to always name it .gitignore, or on Windows, .gitignore. as Windows thinks you are trying to rename it without a filename.

Disaffirm answered 16/8, 2015 at 15:49 Comment(0)
W
9

Specifically for Windows users: If you have untracked files and clearing/removing the cached files is not working. Try opening PowerShell and converting the .gitignore file to UTF-8 encoding:

$Myfile = Get-Content .\.gitignore`
$Myfile | Out-File -Encoding "UTF8" .gitignore

You need to only do this once to encode the .gitignore file for that directory, and since the file is then encoded correctly, whenever you edit the file in the future it should work. I believe this is due to a glitch with GitHub not being about to read non UTF-8 encoding for a .gitignore file. As far as I'm aware this issue has not yet been resolved for Windows. It's not too big of a deal, just a pain to debug when it's not working.

Willing answered 11/11, 2017 at 1:20 Comment(0)
R
8

I just ran into this issue. The content within my .gitignore file continued to appear in the list of untracked files.

I was using this to create the ignore file:

echo "node_modules" > .gitignore

It turns out that the double quotations were causing the issue for me. I deleted the ignore file and then used the command again without quotes, and it worked as expected. I did not need to mess with the file encoding. I'm on a Windows 10 machine using Cmder.

Example:

echo node_modules > .gitignore
Rigging answered 25/8, 2017 at 6:36 Comment(2)
Weird, this echo statement fixed a problem I had locally where an ignored file that I deleted on accident and then recreated was showing up as a committable, untracked file. For some reason, even though this did not change my ignore file, it fixed my problem.Fleetwood
this is the only thing that worked for me. mac user. i had to specify the files i wanted ignored manually back in .gitignore but that only took a few seconds. Thank you!Warison
S
7

There are some great answers already, but my situation was tedious. I'd edited the source of an installed PLM (product lifecycle management) software on Win10 and afterward decided, "I probably should have made this a git repo."

So, the cache option won't work for me, directly. Posting for others who may have added source control AFTER doing a bunch of initial work AND .gitignore isn't working BUT, you might be scared to lose a bunch of work so git rm --cached isn't for you.

!IMPORTANT: This is really because I added git too late to a "project" that is too big and seems to ignore my .gitignore. I've NO commits, ever. I can git away with this :)

First, I just did:

rm -rf .git
rm -rf .gitignore

Then, I had to have a picture of my changes. Again, this is an install product that I've done changes on. Too late for the first commit of the pure master branch. So, I needed a list of what I changed since I'd installed the program by adding > changed.log to either of the following:

PowerShell

# Get files modified since date.
Get-ChildItem -Path path\to\installed\software\ -Recurse -File | Where-Object -FilterScript {($_.LastWriteTime -gt '2020-02-25')} | Select-Object FullName

Bash

# Get files modified in the last 10 days...
find ./ -type f -mtime -10

Now, I have my list of what I changed in the last ten days (let's not get into best practices here other than to say, yes, I did this to myself).

For a fresh start, now:

git init .
# Create and edit .gitignore

I had to compare my changed list to my growing .gitignore, running git status as I improved it, but my edits in .gitignore are read-in as I go.

Finally, I've the list of desired changes! In my case it's boilerplate - some theme work along with sever xml configs specific to running a dev system against this software that I want to put in a repo for other devs to grab and contribute on... This will be our master branch, so committing, pushing, and, finally BRANCHING for new work!

Shondrashone answered 10/3, 2020 at 14:27 Comment(0)
E
6

OK, so in my case the accepted solution did not work, and what worked is described here:

Is Visual Studio 2013 ignoring your .gitignore file?

In short:

  • Close Visual Studio.
  • Navigate to your .git folder
  • Delete ms-persist.xml
  • Restart Visual Studio
Elery answered 29/3, 2016 at 10:41 Comment(0)
P
6

For me none of the previous answers worked. I had to copy .gitignore text into the exclude.txt file found at

<Your-project-folder>\.git\info

Once done, refresh your changes and all the untracked files are gone. Commit as usual.

Plantain answered 20/2, 2017 at 0:47 Comment(0)
B
6

I had this problem, with a .gitignore file containing this line:

lib/ext/

I just realized that in fact, this directory is a symbolic link to a folder somewhere else:

ls -la lib/ext/
lrwxr-xr-x 1 roipoussiere users 47 Feb  6 14:16 lib/ext -> /home/roipoussiere/real/path/to/the/lib

On the line lib/ext/, Git actually looks for a folder, but a symbolic link is a file, so my lib folder is not ignored.

I fixed this by replacing lib/ext/ by lib/ext in my .gitignore file.

Blalock answered 3/5, 2017 at 14:21 Comment(0)
S
6

My issue was (as OP suggested) a corrupt .gitignore file. I didn't believe that it was and ignored the possibility until everything else failed. The corruption didn't show up in vi, but there were two bytes on the start of the file that caused the .gitignore file to be ignored. For me, these only showed up when I typed cat .gitignore, which showed:

��# Built application files
*.apk
*.ap_

# ...

I have no idea how these ended up there, but recreating the file fixed the issue. A hex analysis of the corrupt file showed the following:

user@dev ~/project/myproject $ xxd -b .gitignore
00000000: 11111111 11111110 00100011 00000000 00100000 00000000  ..#. .
00000006: 01000010 00000000 01110101 00000000 01101001 00000000  B.u.i.
Selfconsistent answered 8/1, 2018 at 2:15 Comment(1)
That looks like a UTF-16 byte order mark in a UTF-8-encoded file. en.wikipedia.org/wiki/Byte_order_markTransient
B
5

I had this same problem. I believe the issue was a CR vs. CR+LF discrepancy. I stashed things in my .gitignore using CMD (on Windows 7) and the following command:

Bad:

echo "file_to_be_ignored.py" >> .gitignore<br>
echo "*~" >> .gitignore

Etc.

The issue was that this command does not place the correct end-of-line marker for Git to recognize the newlines (either CR or CR+LF when Git expects the other). I solved the problem by manually replacing each newline in Vim (Vim to the rescue!) and it worked perfectly.

Try editing your .gitignore in Notepad++ or Vim (ideally). Even if the file looks like it's formatted correctly, try replacing the newlines. It sounds weird, I know, but it worked for me. :D

Bedelia answered 21/2, 2015 at 6:32 Comment(0)
K
4

I've created .gitignore using echo "..." > .gitignore in PowerShell in Windows, because it does not let me to create it in Windows Explorer.

The problem in my case was the encoding of the created file, and the problem was solved after I changed it to ANSI.

Kursk answered 30/4, 2019 at 18:18 Comment(0)
A
4

Another possible reasona few instances of Git clients running at the same time. For example, "git shell" + "GitHub Desktop", etc.


This happened to me. I was using "GitHub Desktop" as the main client, and it was ignoring some new .gitignore settings: commit after commit:

  1. You commit something.
  2. Next, commit: it ignores .gitignore settings. Commit includes lots of temporary files mentioned in the .gitignore.
  3. Clear Git cache; check whether .gitignore is UTF-8; remove files → commit → move files back; skip one commit – nothing helped.

Reason: the Visual Studio Code editor was running in the background with the same opened repository. Visual Studio Code has built-in Git control, and this makes for some conflicts.

Solution: double-check multiple, hidden Git clients and use only one Git client at a time, especially while clearing the Git cache.

Allometry answered 23/5, 2019 at 9:57 Comment(0)
P
3

One thing to also look at: Are you saving your .gitignore file with the correct line endings?

Windows:

If you're using it on Windows, are you saving it with Windows line endings? Not all programs will do this by default; Notepad++ and many PHP editors default to Linux line endings so the files will be server compatible. One easy way to check this, is open the file in Windows Notepad. If everything appears on one line, then the file was saved with Linux line endings.

Linux:

If you are having trouble with the file working in a Linux environment, open the file in an editor such as Emacs or nano. If you see any non-printable characters, then the file was saved with Windows line endings.

Psychometrics answered 13/11, 2012 at 2:21 Comment(0)
E
3

One tricky thing not covered by the other answers here is that the .gitignore file won't work if you have inline comments, like this:

foo/bar # The bar file contains sensitive data so we don't want to make this public

So, if you do have comments like that, change them like this:

# The bar file contains sensitive data so we don't want to make this public
foo/bar
Exam answered 28/9, 2017 at 20:18 Comment(0)
S
3

For me it was yet another problem. My .gitignore file is set up to ignore everything except stuff that I tell it to not ignore. Like such:

/*
!/content/

Now this obviously means that I'm also telling Git to ignore the .gitignore file itself. Which was not a problem as long as I was not tracking the .gitignore file. But at some point I committed the .gitignore file itself. This then led to the .gitignore file being properly ignored.

So adding one more line fixed it:

/*
!/content/
!.gitignore
Skyscraper answered 4/9, 2018 at 19:41 Comment(1)
this deserves more vote. adding !.gitignore solves my problem.Denson
P
2

It is also a possibility that you edited the .gitignore file with a sudo command. I encountered the same issue and while executing the commands: git status, I could still see the "should be ignored" files.

Upon editing with nano .gitignore instead of sudo nano .gitignore, I could see the correct reflection.

Pulchi answered 22/10, 2018 at 6:15 Comment(0)
T
2

I too have the same issue on Ubuntu, I created the .gitignore from the terminal and it works for me

touch .gitignore

Tommi answered 20/7, 2019 at 0:1 Comment(0)
H
2

Mine wasn't working because I've literaly created a text document called .gitignore

Instead, create a text document, open it in Notepad++ then save as .gitignore

Make sure to pick All types (*.*) from the dropdown when you save it.


Or in gitbash, simply use touch .gitignore

Hideaway answered 15/8, 2019 at 20:8 Comment(0)
T
2

My problem was that I wrote down files to ignore with quotes " " separation not with slash /.

This did not work and was ignored by git :

"db.sqlite3"
"tdd_venv/"

This worked just fine :

/db.sqlite3
/tdd_venv/

I also checked my file encoding in windows with Notepad++. Encoding was set to UTF-8.

Thibaud answered 6/12, 2019 at 17:28 Comment(0)
L
2

I saw that a few of you already answered that but I don't know whether it was stated clearly.

In my case the problem appeared due to creating the .gitignore file with echo commmand which resulted in file encoding being changed.

In order to fix that I had to open the text file, click save as and change the encoding in the bottom tab to UTF-8.

When I used the touch command to create the file and edit its contents via text editor the problem did not occur.

Lubber answered 3/5, 2021 at 10:53 Comment(0)
C
1

Just remove the folder or file, which was committed previously in Git, by the following command. Then gitignore file will reflect the correct files.

    git rm -r -f "folder or files insides"
Characterization answered 10/4, 2017 at 8:13 Comment(0)
J
1

If you are a Notepad++ user, try doing the following:

Open your .gitignore file using Notepad++ and do:

Menu EditEOL ConversionWindows FormatSave.

Try using git status again and see if it works for you.

I have posted the answer to a similar question here.

Joplin answered 28/3, 2018 at 11:42 Comment(0)
U
1

Lot of answers here but what worked for me is not altogether in any particular one , I am jotting all the steps one by one that needs to be done here in a simple manner :

Pre --- Take a backup of repo just in case. (I did not but may make you feel safer)

  1. Make sure whether this is your first commit or earlier these files were add and thus have become cached.
  2. If yes , then git rm -r --cached . and git add . (do not miss the dot)
  3. If it still isn't working , open file in notepad
  4. Go to File -> Save as
  5. Change the encoding to ANSI. (Some answers mistakenly say UTF-8 , but it doesn't work and wastes time needlessly)
  6. Again git rm -r --cached . and git add . (do not miss the dot)
  7. Now do Git status and verify what we wanted has happened
Upbraid answered 25/6, 2021 at 13:23 Comment(0)
L
1

Despite having tried the various suggestions in this post and others (e.g. Gitignore not working and gitignore not working - being ignored?) I couldn't get git to ignore the files/folders contained within my .gitignore.txt file.

I should stress that unlike many of the previous answers that address the problem whereby a file/directory that has already been previously committed is to be untracked, in my case, I encountered this problem prior to making my first commit (i.e. having only run git init followed by git status).

There were a number of other promising suggestions including:

  • text file encoding must be ANSI instead of UTF, e.g. Encoding -> ANSI in Notepad++
  • EOL conversion for Windows, e.g. Edit -> EOL Conversion -> Windows in Notepad++
  • no leading or trailing whitespaces for the items in .gitignore.txt
  • no leading "/" when defining a folder

but none were applicable or resolved my issue.

After playing around with different ways of creating a .gitignore.txt file I managed to figure out how to get it to work, although I can't say that I understand why. It would be interesting to know if anyone can offer an explanation.

For the benefit of those who may also find that the previous answers don't address their issue I'll describe what I tried, what didn't work and what did. Hopefully by doing so it may also shed light on the why. Note that I'm using Windows 10.

Attempt #1 (failed)

Creating the new txt file in Windows Explorer:

  1. (In the project folder) Right-click -> New -> Text document
  2. Changed file name to ".gitignore"
  3. Opened file in Notepad++, entered file/directory names to be ignored
  4. Encoding -> ANSI [Note 1], save changes

I ran git status but the files/folders I wanted ignored were shown as untracked. I checked the file properties in Windows Explorer. As expected the filename was ".gitignore" and the file type was "Text Document (.txt)".

Note 1:

Several contributors have stated that the encoding must be ANSI (rather than UTF). In Notepad++ I've found that regardless whether I do Encoding -> ANSI, or Encoding -> Convert to ANSI + save, close the file, and re-open it (in Notepad++), when I check the encoding it always reports UTF-8. This was also the case for the .gitignore.txt file that eventually worked.

Attempt #2 (failed)

Creating the new txt file in Notepad++:

  1. In Notepad++ created new file, entered items to ignore
  2. Saved as ".gitignore.txt", changed "Save as type" from "Normal text file" (default) to "All types", and un-ticked the box "Append extension" (ticked by default).

I ran git status and as before all files/directories were listed under untracked files. As before the filename was ".gitignore" and the file type was "Text Document (.txt)".

Attempt #3 (succeeded)

With the same file (.gitignore.txt) still open in Notepad++:

  1. Saved as ".gitignore" selected "Normal text file" for "Save as type", which automatically ticked the box "Append extension"

I noticed that the file created appeared to be name-less in Windows Explorer. I checked the file's properties: the file name field was blank and the file type was "Text Document (.gitignore)". After ticking "File name extensions" in Windows Explorer (View -> File name extensions) the "name-less" file shows the ".gitignore" extension.

I ran git status and this time the files/folders I wanted ignored were not listed as untracked files - success!

Opening the file in Notepad++ I noticed that the encoding was UTF-8, and the file name was identified as ".gitignore" (unlike in Windows Explorer).

So it appears there is subtlety in the way the txt file is created. Perhaps this is a peculiarity unique to Windows?

Lajoie answered 6/1, 2022 at 21:10 Comment(1)
Save As .gitignore.txt worked a treat.Prince
D
0

This might sound silly, but what solved my problem was realizing that .gitignore is working correctly, even if it says deleted: yourfile on git status.

I was going to ignore an error log file, to ignore any errors I caused, but save the ones caused by other developers in case they came in handy one day while debugging an odd problem. However, git does not let you "ignore" and also keep a file at the same time.

I wanted it to be "frozen in time", but git says it either gets tracked, or it is not allowed to be there at all.

Dictator answered 9/3, 2020 at 9:13 Comment(0)
G
0

PhpStorm (and probably some other IDE users), in my case problem was that I created and added file outside the project, through the finder.

I deleted that one, and recreated the same one but in PhpStorm project, with right-click -> New -> File, and it worked right away.

Glycogen answered 9/4, 2020 at 17:3 Comment(0)
B
0

My 30 cent trick:

  1. Pl clean your directory. git clean -f (I tried git rm -r --cached . but it did not work for me.)

Warning: git clean -f will remove untracked files, meaning they're gone for good since they aren't stored in the repository. Make sure you really want to remove all untracked files before doing this.

May be you can try git clean -xdf which removes ignored dirs and untracked files

  1. Now bring HEAD to the current position git reset HEAD --hard.
  2. check git status.

  3. Now create .gitignore which in my cases wanted to ignore a folder called data. So I wrote /data/ (initial / is for file/folder, later / is for folder only).

  4. Now do git add, commit, and push.
Buckish answered 15/4, 2020 at 9:50 Comment(0)
A
-1

I experienced that .gitignore is ignored working with Flutter project in VS Code on Windows 10.

I tried many of the above suggestions. Nothing helped.

Final solution: just delete .git folder and start with a new repository. .git folder is located in the root of Flutter project and hidden by default.

Be sure to add folders and files to .gitignore before the first commit.

Aragonite answered 1/8, 2023 at 12:13 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.