# 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: | |
# http://kernel.org/pub/software/scm/git/docs/gitignore.html | |
# Ignore everything in the root except the "wp-content" directory. | |
/* | |
!Vagrantfile | |
!README.md | |
!.gitignore | |
public/* | |
!public/ | |
!public/wp-content/ | |
# Ignore everything in the "wp-content" directory, except the "plugins" | |
# and "themes" directories. | |
public/wp-content/* | |
!public/wp-content/plugins/ | |
!public/wp-content/themes/ | |
# Ignore everything in the "plugins" directory, except the plugins you | |
# specify (see the commented-out examples for hints on how to do this.) | |
public/wp-content/plugins/* | |
# !public/wp-content/plugins/my-single-file-plugin.php | |
# !public/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.) | |
public/wp-content/themes/* | |
!public/wp-content/themes/my-theme | |
# !public/wp-content/themes/my-theme/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment