How can I add a blank directory to a Git repository?
Solution 1:
Another way to make a directory stay (almost) empty (in the repository) is to create a .gitignore
file inside that directory that contains these four lines:
# Ignore everything in this directory
*
# Except this file
!.gitignore
Then you don't have to get the order right the way that you have to do in m104's solution.
This also gives the benefit that files in that directory won't show up as "untracked" when you do a git status.
Making @GreenAsJade's comment persistent:
I think it's worth noting that this solution does precisely what the question asked for, but is not perhaps what many people looking at this question will have been looking for. This solution guarantees that the directory remains empty. It says "I truly never want files checked in here". As opposed to "I don't have any files to check in here, yet, but I need the directory here, files may be coming later".
Solution 2:
You can't. See the Git FAQ.
Currently the design of the git index (staging area) only permits files to be listed, and nobody competent enough to make the change to allow empty directories has cared enough about this situation to remedy it.
Directories are added automatically when adding files inside them. That is, directories never have to be added to the repository, and are not tracked on their own.
You can say "
git add <dir>
" and it will add files in there.If you really need a directory to exist in checkouts you should create a file in it. .gitignore works well for this purpose; you can leave it empty, or fill in the names of files you expect to show up in the directory.
Solution 3:
Create an empty file called .gitkeep
in the directory, and add that.
Solution 4:
You could always put a README file in the directory with an explanation of why you want this, otherwise empty, directory in the repository.
Solution 5:
touch .placeholder
On Linux, this creates an empty file named .placeholder
. For what it's worth, this name is agnostic to git, and this approach is used in various other places in the system, e.g. /etc/cron.d/.placeholder
. Secondly, as another user has noted, the .git
prefix convention can be reserved for files and directories that Git itself uses for configuration purposes.
Alternatively, as noted in another answer, the directory can contain a descriptive README.md
file instead.
Either way this requires that the presence of the file won't cause your application to break.