Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
Template .gitignore file for WordPress projects
# 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.)
# !wp-content/plugins/my-single-file-plugin.php
# !wp-content/plugins/my-directory-plugin/
# Ignore everything in the "themes" directory, except the themes you
# specify (see the commented-out example for a hint on how to do this.)
# !wp-content/themes/my-theme/

The "!" exclusion feature doesn't work with git Does with git 1.7.1.

This is awesome, thank you!

avioli commented Jul 6, 2011

By using ! to invert the exclusion includes all stuff from the path
Since I have a .DS_Store file in my theme directory, it get's included in the repo, because of the inversion.
Is there a solution?
Example (last two lines from the gist above):


Now if I have a .DS_Store file in wp-content/themes/my-theme/ it will be included in the repo.

@avioli perhaps put your .DS_Store line after everything else?


redoPop commented Jul 6, 2011

@avioli you may want to check that you have .DS_Store specified in your project's .gitignore file or your global .gitignore list. If you're depending on global gitignore's, it could also be that someone else who's working on your project doesn't have .DS_Store in their global .gitignore and subsequently added the .DS_Store file to the project.

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.


redoPop commented Jul 6, 2011

@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 .DS_Store is a pattern in a global .gitignore file or a pattern that appears earlier in the same file, it will remain excluded after the .../my-theme/ negation.

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.)

avioli commented Jul 13, 2011

@JBartlett Thank you for the clarification. I didn't have .DS_Store inside .gitignore. I thought all dot-named files/folders are excluded from the git repo by default.

Great gist !

I use git submodule (for plugins) and in that case you must add:


I find whenever I'm changing branches using this gitignore, my plugins disappear when I merge back into the master, has anyone else encountered this problem?

Posted a question on stackoverflow to no avail

Hmmm... I can't seem to make the /* work -- it insists on grabbing everything. (I'm a git newbie so it's likely that I'm missing something...)

OK. I think I got it now. I needed to create my .gitignore file PRIOR to adding all the files using git add . . Hopefully this'll help some other newbie out there someday...

This is still really useful 2 years later!

ecommy commented Jan 11, 2013

Just wanted to say a simple thank you!

Great!, Now I can use the same directory for the clone and the rest of the code without using symlinks

togume commented Feb 14, 2013

Like Thanks!

Thank you for this setup man, I forked it to a version that I am using for my latest project. Cheers.

Fantastic, thanks so much :)

realph commented Feb 26, 2013

Very nice!

tubiz commented Aug 28, 2013

How I exclude the file.
Everything is fine whis this gists except that the file isn't displaying

Thank you for this contribution, saved me a lot of time :)

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.

jabes commented Nov 9, 2013

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:


Should be..



Fantastic, thanks!

Great example.
I have added also wp-config.php.
I am using git versioing for wp for getting updates from dev, to tst and then from tst to production, on each of these wp-config.php is different. What is your opinion?

Update: I suppose this .gitignore excludes everything in the root so it means also wp-config:-)


dytra commented Mar 5, 2014



Thank you! :D

after I deployed git init with git ignore set for wordpress I found nothing is there. Now I pissed off and want to get back those files but don't know hoe to do it. Can any one suggest how to solve this problem.

Thank you, this is great help!

i am new to wordpress and use linux...where should i add this code...

iparr commented Oct 20, 2014

@Vinoth945 Add it to the root of your WordPress directory, so the folder where wp-content and friends are.

I'm using git 2.3.0 and had to do this to get the wp-content directory unignored.


awesome, great gist !

Thanks man

nnmous commented Apr 20, 2017

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?

You can see A collection of useful .gitignore templates and here is a WordPress.gitignore file.

@jabes you are right !
I also removed the trailing slashes to get it up and running

This is what I was looking for, thanks a bunch

blachawk commented Nov 9, 2017

Thank you, this was a good starting point for me to understand how to keep WP files properly controlled in a git repository.

w7089 commented Jan 8, 2018

Hi, don't understand why not to keep images in version control.

Read here that

The problem is that when you’re working with other developers, they’ll all have their own copies of the site database, so if you upload an image to your local development version and then commit it to the Git repository, the next time another developer pulls the repository they’ll have an orphaned image in their wp-content/uploads folder without an reference in their database. Not good. To avoid this we keep the entire uploads directory out of version control.

But, what is the alternative for website developed by multiple developers in parallel?
What's wrong with pushing and pulling db and code changes? Suppose that website users don't upload anything to uploads folder. So uploads folder is only read by its viewers.

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.
Or i miss something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment