gitignore - hide ignored files during checkout

Question

Here is my problem (via example steps):

• I have a Git repo with two different branches (branchA and branchB), which are currently identical.
• Checkout to branchB and create a new file "foo.txt".
• Add that file to ".gitignore" of that branch, so that it is successfully ignored in branchB.
• Create another file "hello.txt", stage it and commit it.
• Checkout to branchA.
• foo.txt appears in branchA, but hello.txt does not.

Why does foo.txt appear in branchA and not get "hidden" like hello.txt does?

From my perspective this is a great annoyance and seems like a bug/feature request, but has Git been designed to act this way? I was surprised to find no other people complaining about this.

Answer 1

foo.txt is not appearing in branchA, it's just no longer being ignored because your changes to .gitignore (I assume you committed these to branchB) are lost when you checked out branchA. foo.txt is just an untracked file. Having foo.txt "disappear" when you switch to branchA is saying you want the file deleted from your working directory. This very different than ignoring a file.

You can specify ignore patterns that affect the whole repository regardless of what branch you have checked out using the $GIT_DIR/info/exclude file. This is local to your repository though, so ignore patterns specified in this file will not be propagated to other repositories. See gitignore(5).

Answer 2

It is not a bug. To understand how it works, you need to know a few things.

• .gitignore is not "automatically" applied globally. You need to commit it.
• Any uncommitted files will be visible in every branch. When switching branches, you should either commit the file, or you could stash it.

Also, this question has been asked before, though I don't blame you for not finding it in the search. Working on two unrelated files in separate git branches

Answer 3

The quick answer:

• hello.txt is not "hidden", it has been committed to branchB and therefore you will not see in branchA untill you merge or rebase branchB into branchA
• the same happens to .gitignore. If you committed .gitignore to branchB (which I guess you did) and then checkout branchA, well, branchA has no .gitignore file and that´s why you see foo.txt. Again, you need to merge or rebase branchB into branchA