Skip to content

Instantly share code, notes, and snippets.

@pixeline pixeline/.gitignore forked from redoPop/.gitignore
Last active Jan 20, 2020

Embed
What would you like to do?
Default Wordpress .gitignore file
# 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
# CLEANING THE REPOSITORY
# If you've added this .gitignore file in an existing repository, you may want to remove the content that should be ignored. Here is how to do that.
# you can use a wildcard to remove all files, and then add all the files back, and then commit the updates.
# $ git commit -m "Pre Cleanup"
# $ git rm -r --cached .
# $ git add .
# $ git commit -m ".gitignore setup and cleaned up"
# Ignore everything in the root except the "wp-content" directory.
/*
!.gitignore
!wp-content/
!wp-config.php
# Ignore everything in the "wp-content" directory, except the "plugins"
# and "themes" directories.
wp-content/*
!wp-content/plugins/
!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.)
wp-content/plugins/*
# !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/*
# !wp-content/themes/my-theme/
@erchaves

This comment has been minimized.

Copy link

erchaves commented Mar 19, 2018

Just stumbled on this.. I don't think you mean to add !wp-config.php which has secure keys in it... The original gist that this was forked from does not include that file.

@v3nt

This comment has been minimized.

Copy link

v3nt commented Apr 23, 2018

i can't seem to un-ignore my theme folder? No changes are noticed and re-tried from scratch several times. Any ideas?

@fredrick-contributions

This comment has been minimized.

Copy link

fredrick-contributions commented Feb 15, 2019

The below command will help you to ignore the wp-config.php when it will be on tracking mode even it has been mentioned in the .gitignore file to be ignored.

git update-index --assume-unchanged -- wp-config.php

or

git update-index --skip-worktree -- wp-config.php

you should use assume-unchanged or skip-worktree instead.

@gnanet

This comment has been minimized.

Copy link

gnanet commented Jan 20, 2020

Just stumbled on this.. I don't think you mean to add !wp-config.php which has secure keys in it... The original gist that this was forked from does not include that file.

The best would be a big NOTE, that clarifies why it is not desied to track wp-config.php, and the few special use-cases where tracking wp-config.php is indeed desired. One such special case is, where the git repository is not visible, nor available publicly, and only authenticated users can access it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.