Kael

刚开始用 ava 就发现，握草好鸟，这是什么鬼，发现原来是 `power-assert`

Confirmed. Really weird behavior of `git check-ignore`. IMO, `c/*` means ignoring everything **inside** of directory `c` but not `c` itself. I need to check the spec However, this issue might...

But I think this issue will not cause the situation that we copy wrong files (we always copy files instead of directories), so it is of low priority.

I'm really not quite sure about the compatibility cross different file systems. I'm struggling in my head whether I should make the validation as a convention(warning) or not(error)

https://git-scm.com/docs/gitignore does always miss rules. I'm not sure if `**folder` is a rule of gitignore or only a side effect of git.

@mgol Your case is not an issue of `node-ignore`, and might not be discussed here. `*` makes `src` ignored as well as everything inside `src` and the things inside `src`...

This topic had already been discussed in the eslint repo. To support both .gitignore-style pattern and fnmatch(3), or mutually translate these 2 kinds of patterns is not even possible.

It is easy for us to implement this by extending `node-ignore` .gcloudignore ``` .gcloudignore # If you would like to upload your .git directory, .gitignore file or # files from...

IMO, `node-ignore` is a pure parser to parse some ignore patterns which follow the .gitignore rules, and we'd better add any other features to it. Even if I add a...

I am closing this. Be free to reopen this issue if necessary