.gitignore-忽略文件目录

Question

Is there any way to create a .gitignore folder rather than a file? Such that Git would parse .gitignore/ignorerulesA and .gitignore/ignorerulesB both as ignore files?

I could see this being useful in a scenario where I have two repositories with a non-overlapping structure that I want to merge.

repoa
  filea
  foldera
  .gitignore/ignorea

repob
  fileb
  folderb
  .gitignore/ignoreb

With this structure I can merge repoa and repob without any conflicts.

If this isn't possible already, would it make sense to request this feature?

I'm not sure if the search results for my question are so poor because:

1. maybe this is just a bad idea
2. I don't have the right search term ".gitignore folder" is just a bunch of instructions on how to ignore a folder. "multiple .gitignore files" just talks about placing .gitignores in different folders.
3. I'm a genus and nobody has thought of this before.

---

Update: Clarification

If we take the two repositories in my example above and apply different .gitignore rules for each repository.

For instance in repoa I want to ignore foldera and in repob I want to ignore fileb. I end up in this situation

repoa
  filea
  foldera
  .gitignore
    foldera

repob
  fileb
  folderb
  .gitignore
    fileb

Now I want to create repoab.

mkdir repoab
cd repoab
git init
git remote add repoa /path/to/repoa
git remote add repob /path/to/repob
git pull repoa master
git pull repob master
rom ../repob
 * branch            master     -> FETCH_HEAD
Auto-merging .gitignore
CONFLICT (add/add): Merge conflict in .gitignore
Automatic merge failed; fix conflicts and then commit the result.

Essentially every single time I deal with an update to repoa or repob I'm going to have to deal with this conflict, which is certainly not ideal.

Answer 1

You can ignore directories with <directoryname>/ .

In your example adding file*/ will ignore both folders, and there won't be a merge conflict if you try to merge the 2 repo/branch.

Answer 2

As you found searching for "multiple .gitignore files", you can put different files in different directories, but Git doesn't handle multiple .gitignore files in one directory. In general, Git looks for a configuration file like this in your pwd and then crawls up to parent directories until it finds one or reaches the root directory. That strategy doesn't mesh with having a special directory full of multiple configuration files.

Though this won't solve your merging problem (I think you need submodules for that), you can set up a global .gitignore for things like editor swapfiles that other collaborators don't need to ignore. I have one at ~/.gitignore and tell Git to read it in ~/.gitconfig :

[core]
  excludesfile = /Users/kristjan/.gitignore

Answer 3

With this structure I can merge repoa and repob without any conflicts.

But you can't. .gitignore files can have exclusions, and even without those it's possible for one repo to expect some kinds of files to be included where the other expects them to be generated (and so ignores them). Order matters.

You can put your .gitignore s in the trees they apply to, foldera/.gitignore and so forth. That won't help for toplevel files, but if you've got conflicting specs there you also have conflicting files there, so the ignore mess isn't really the problem there.