Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign uprevert .gitignore? #117
Comments
This comment has been minimized.
This comment has been minimized.
|
I think it won't be too hard to just fix up the We can always apply the |
feross
added a commit
that referenced
this issue
Apr 21, 2015
This comment has been minimized.
This comment has been minimized.
|
standard@3.7.0 removed support for .gitignore until we can make it work more reliably. |
feross
closed this
Apr 21, 2015
Flet
added a commit
to Flet/standard
that referenced
this issue
Oct 23, 2015
lock
bot
locked as resolved and limited conversation to collaborators
May 11, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
jprichardson commentedApr 17, 2015
Can we consider reverting the .gitignore patch? It doesn't work like people expect, see: #116 & #115.
I'm working on migrating a large project over and my .gitignore is huge. Standard (with .gitignore patch) reports no issues, which is incorrect, because versions before report thousands of lines. What I liked about standard before was that it was super simple to ignore files, just place the patterns in
package.json. Now I don't know if it's looking inpackage.jsonfirst and then.gitignoreor vice versa. Regardless, it's complicated the whole thing.I can understand why one would choose
.gitignorepatterns, but I think we need to either get it near perfect or not at all IMHO.@feross what are your thoughts?