1
0
mirror of https://github.com/github/gitignore synced 2025-02-18 16:39:08 +01:00
Tom Willmot 3cdfcae597 Don't ignore core WordPress files as they are required for the site to run.
Only files which can change per install should be excluded.
2012-04-19 18:02:09 +02:00
2012-04-15 17:16:03 +02:00
2010-11-13 05:54:52 +08:00
2011-02-21 18:02:55 -08:00
2010-11-22 17:42:32 -08:00
2012-03-08 20:45:16 +09:00
2011-06-13 09:40:25 -07:00
2011-08-17 00:55:26 -05:00
2011-02-01 06:03:02 +08:00
2010-11-10 03:43:58 +08:00
2012-01-12 16:37:34 -02:00
2011-02-21 17:56:28 -08:00
2011-08-02 21:36:51 +01:00
2011-05-01 18:11:31 +01:00
2010-11-09 04:49:58 +08:00
2010-11-09 04:49:25 +08:00
2010-11-09 15:51:51 +08:00
2012-03-16 18:49:26 -03:00
2010-11-09 16:08:50 +08:00
2011-05-29 21:24:34 -04:00
2010-11-23 09:36:53 +08:00
2012-03-03 02:08:17 +01:00
2011-05-12 20:27:24 +05:30
2011-10-08 09:23:47 +02:00
2010-11-10 03:43:28 +08:00
2011-02-21 18:03:04 -08:00
2012-03-24 23:22:27 +11:00
2010-11-22 17:54:05 -08:00
2011-02-21 18:08:03 -08:00

A Collection of Useful .gitignore Templates

That's what we're trying to build. Please contribute by forking and sending a pull request.

Also please only modify one file per commit. This'll make merging easier for everyone.

Global gitignores (OS-specific, editor-specific) should go into the Global/ directory.

For more information on gitignore: gitignore(5)

Global Ignores

git has a global configuration that applies rules to all of your projects. For example:

git config --global core.excludesfile ~/.global_ignore

... will apply the rules in ~/.global_ignore for all of your repos.

This is useful if you use an editor (like Emacs) that drops backup files, or if you work in an environment that generates binary or intermediate files that are always ignored.

Description
No description provided
Readme 12 MiB
Languages
Markdown 100%