1
0
mirror of https://github.com/github/gitignore synced 2024-11-25 21:24:23 +01:00
Commit Graph

20 Commits

Author SHA1 Message Date
Josh Whaley
5521a828aa Update Node.gitignore
Updated link for the dependency directory from [this](https://npmjs.org/doc/faq.html#Should-I-check-my-node_modules-folder-into-git) to [this](https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git-).
2014-08-13 10:52:00 -04:00
Scott J. Roberts
446dae3d53 Adding .lock-wscript 2014-05-07 17:47:05 -04:00
cheddar
9390b1072d Reintroduce link to npmjs
And remove my own opinions...
2014-04-04 17:33:30 -05:00
cheddar
4d30a45c9e Remove opinion from Node.js .gitignore file
This is a PR to remove the opinionated lines from the Node.js .gitignore file.

I do not believe that Github's pre-baked .gitignore files should be promulgating opinions, especially in a community that is as fresh as the Node.js community.  Questions of what should be checked in should be a decision made on an organization-by-organization basis, or left up to the individual.  Github's inclusion of opinion in these files puts unnecessary authority behind that opinion, which can have the negative side-effect of people following without thinking.
2014-04-04 10:05:58 -05:00
Stuart P. Bentley
6b8815dc43 Remove Results classes from Node gitignore
These aren't really common patterns in the Node world, and if a Node project includes one of these types as files, they're as likely to want to include them in the project as not (`*.csv` is as likely to be a data source as `*.json`).
2014-02-28 12:46:45 -08:00
Adam Roben
937523ae50 Reduce comments 2014-02-28 11:37:14 -05:00
Stuart P. Bentley
f3f11fb2f1 Node.gitignore: correct term for instrumentation 2014-01-07 02:52:27 -08:00
Stuart P. Bentley
bdf8aec8f9 Add .grunt directory 2014-01-07 02:33:15 -08:00
Stuart P. Bentley
8845a345c0 Add coverage directory, rename coverage heading 2014-01-07 02:27:32 -08:00
Stuart P. Bentley
b0440f97cc Add build/Release to Node gitignore
This re-covers the http://nodejs.org/api/addons.html case for which the "build" directory was added in 00686415c4, but doesn't break cross-environment projects that use the build directory for including concatenated/minified source. Mazel tov!
2014-01-07 01:49:40 -08:00
Stuart P. Bentley
935e9b4560 Clarify node_modules comment
Now linking to the official npm FAQ entry (with tl;dr) rather than straight to mikeal's blog post
2014-01-07 01:37:13 -08:00
Stuart P. Bentley
d79a88b29f Refactor Node.gitignore with comments
The "build" directory is lost in this refactor, as many JS projects
do wish to include a minified/concatenated version of their source
in the "build" folder in source control.
2014-01-02 20:02:57 -05:00
Ray Solomon
00686415c4 add 'build' to Node.gitignore
This is to exclude compiled code from nodejs addons.
Reference: http://nodejs.org/api/addons.html
2013-11-13 01:27:28 -08:00
Dan Kerimdzhanov
fa1ea3d7f2 remove npm-debug.log entry 2013-11-08 18:34:37 +06:00
Ivan Zuzak
f0dde55c6b ensure single trailing newline 2013-10-06 14:40:01 +02:00
Andrej Mihajlov
3df67a9651 Update Node.gitignore 2012-11-08 14:07:25 +01:00
Ankur Oberoi
541e85287f checking in the node_modules dir is best practice for app developers
according to the community since recent changes.

see: http://www.mikealrogers.com/posts/nodemodules-in-git.html
by @mikeal
(cherry picked from commit 44b47ec5bd0222ccf55efe5bcdb8bd3c55271803)
2012-01-06 00:59:41 -05:00
indexzero
aa8f00968f [minor] Update Node.gitignore for npm 1.0 2011-05-29 21:47:07 -04:00
Peat Bakke
330290971a Removing .DS_Store; specific to OS X, and redundant with Global/OSX 2010-11-10 03:40:33 +08:00
amrnt
4dc09001b5 adding Node.js ignores 2010-11-09 15:51:04 +08:00