|# This is a template .gitignore file for git-managed WordPress projects.|
|# Fact: you don't want WordPress core files, or your server-specific|
|# configuration files etc., in your project's repository. You just don't.|
|# Solution: stick this file up your repository root (which it assumes is|
|# also the WordPress root directory) and add exceptions for any plugins,|
|# themes, and other directories that should be under version control.|
|# See the comments below for more info on how to add exceptions for your|
|# content. Or see git's documentation for more info on .gitignore files:|
|# Ignore everything in the root except the "wp-content" directory.|
|# Ignore everything in the "wp-content" directory, except the "plugins"|
|# and "themes" directories.|
|# Ignore everything in the "plugins" directory, except the plugins you|
|# specify (see the commented-out examples for hints on how to do this.)|
|# Ignore everything in the "themes" directory, except the themes you|
|# specify (see the commented-out example for a hint on how to do this.)|
By using ! to invert the exclusion includes all stuff from the path
Now if I have a .DS_Store file in
@avioli you may want to check that you have
Either way, the negation that re-includes your specific theme directory shouldn't override .DS_Store's exclusion.
Now that the file's been added, you'll need to manually remove it from the repository for the .gitignore to take effect again.
@avioli re-reading your question, it sounds as though you may be posing a hypothetical problem rather than describing one you've encountered, so I'd like to follow up with a little more explanation.
The negation that matches the .../my-theme/ path should not match .DS_Store files; even if
The reason for this is that the negation is applied to the path:
This line tells git to remove the .../my-theme/ path from its list of exclusions, but the pattern doesn't use any wildcards that might apply to individual files within that path, so it won't override the earlier .DS_Store exclusion. To override file exclusions such as .DS_Store, we'd need to follow it up with:
...which would apply to all files within the .../my-theme/ path, and would therefore override the .DS_Store exclusion pattern. (So don't do it!)
Hope that helps. .gitignore patterns can be a little confusing.
(An aside: ending patterns with a slash to specify paths is relatively recent; as @benklocek pointed out, earlier versions of git don't support this.)
I am trying to implement this on a Wordpress to limit version control on plugin and theme subdirectories. How to clone the full site though to get started since most of the site is ignored? What order and steps are to be taken? I first added all files except the custom plugin and theme subdirectories but when i clone, I get an error that the directory is not empty.
I have experienced an issue where untracked files do not show in my working tree. This was caused by the trailing slashes after directories. Example:
Update: I suppose this .gitignore excludes everything in the root so it means also wp-config:-)
Why you don't want WordPress core files in your project's repository?
If you have a local development environment don't you want to track the code of Wordpress? How can you then clone the code on your live server if you ignore core files?
Hi, don't understand why not to keep images in version control.
Read here that
But, what is the alternative for website developed by multiple developers in parallel?
Is ignoring uploads folder can be viewed as best practice and version controlling it - always a bad practice? Or each website is unique, etc...
P.S. Read somewhere that images is data, not code. So it should be treated like that and not version controlled. But then, additional procedure is needed for managing images repository somewhere else and checking if it's updated on each git pull by a developer. Moreover deploy to staging/production should be hooked on this procedure as well.