Skip to:

Opened 9 years ago

Closed 9 years ago

Last modified 5 years ago

#2802 closed defect (bug) (fixed)

Refresh SVN and Git repo properties

Reported by: netweb's profile netweb Owned by:
Milestone: 2.6 Priority: normal
Severity: normal Version: trunk
Component: General Keywords:


Switch to svn:autoprops and remove svn:eol-style properties

See #BuddyPress6409

Update svn:ignore, svn:global-ignore and .gitignore properties see:

Proposed to also add IDE/Editor specific ignores, e.g. .idea for PhpStorm, any others? Netbeans maybe?
(By adding a .gitignore rule to .gitignore file to allow for personal customizations (see core's implementation of this) we can proably avoid having to do this for each editor.

See discussions at:

Change History (6)

#1 @johnjamesjacoby
9 years ago

In 5770:

Tidy up SVN properties.

  • This first steps removes svn:eol-style, svn:executable, svn:mime-type on all files.
  • The svn:ignore and svn:global-ignores properties have been tidied up to match WordPress core.
  • A subsequent commit will re-instate svn:mime-type via svn:auto-props.

Hat-tip DJPaul. See #2802.

#2 @johnjamesjacoby
9 years ago

In 5772:

Add .htaccess, .DS_Store, and .gitignore to .gitignore, taking influence from WordPress core.

Hat-tip netweb. See #2802.

#3 @johnjamesjacoby
9 years ago

I think adding a .idea file is fine.

If Netbeans has a directory specific configuration file, I've never needed to use that functionality myself. Most of what I do involves projects with several plugins and themes in them, all of which utilize a similar configuration.

#4 @netweb
9 years ago

  • Milestone changed from Awaiting Review to 2.6
  • Resolution set to fixed
  • Status changed from new to closed
  • Version set to trunk

Marking this as fixed for now, happy to revisit this later but there are a few workarounds for IDE/Editor ignore rules.

See these GitHub references:

#5 @netweb
9 years ago

Adding some extra info in regard to PhpStorm .idea:

Per @JohnBillion in #WP34345

IDE-specific .gitignore rules should not be present in a project. They should be managed in the user's ~/.gitignore_global.

#6 @johnjamesjacoby
5 years ago

Assigning all closed & unassigned tickets in the 2.6 milestone to myself.

Note: See TracTickets for help on using tickets.