[wp-trac] [WordPress Trac] #41078: Detect if someone’s site is under version control, and suggest better ways to edit their sites

[WordPress Trac]

#41078: Detect if someone’s site is under version control, and suggest better ways
to edit their sites
----------------------------+------------------
 Reporter:  karmatosed      |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  high            |   Milestone:  4.9
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  close           |     Focuses:
----------------------------+------------------

Comment (by danieltj):

 Whilst it's not the most elegant solution, it does provide some fallback
 in detecting if there is a `.svn` or `.git` folder in the root and then
 setting a flag which states the site is (at least partially) under a VCS
 and having an interface for a user to yay or nay say which files/folders
 are being VCS'd.

 It's not the most ideal but in some instances people may want to update a
 production site that is under VCS and push to the repo from prod down to
 dev etc. Everyone uses SVN and Git differently and this seems like the
 most inclusive approach. You could also argue that those that know it's
 under a VCS won't try and edit it using the Code Editor, so doing
 expensive background tasks doesn't seem like a great idea.

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