[wp-trac] [WordPress Trac] #27207: Extend core's .gitignore file

WordPress Trac noreply at wordpress.org
Wed Feb 26 18:50:12 UTC 2014


#27207: Extend core's .gitignore file
------------------------------+--------------------------
 Reporter:  TobiasBg          |       Owner:  markjaquith
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:  3.9
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by bpetty):

 Definitely agree with scoping `build` properly. Personally, I always
 anchor my excludes. I'd rather keep adding new ones when I actually run
 into them rather than specifying loosely defined excludes - it really
 doesn't happen that often. I have a bunch in my own `.git/info/exclude`
 file, but ignoring the more personal ones (like my IDE project files), I
 still have these core-specific ones:

 {{{
 /src/.htaccess
 /src/wp-content/uploads/

 /src/wp-content/plugins/*
 !/src/wp-content/plugins/index.php
 !/src/wp-content/plugins/hello.php
 }}}

 Well, `.htaccess` isn't actually WP intentionally placing it in `src`, but
 I just find myself placing it there every time since running `grunt build`
 clears the entire `build` folder, and I don't want to keep fixing my
 permalinks while running from the `build` directory every time I make a
 change. So I just copy it into `src` so it's brought over automatically.
 Of course, the same applies to the plugin excludes, and really anything
 else that would have normally been specified for
 `https://core.svn.wordpress.org/trunk`.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27207#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list