blob: ea4d849aa3a1d48b83a6df24299155b4171d6315 [file] [log] [blame]
git-init-db - Creates an empty git repository
'git-init-db' [--template=<template_directory>] [--shared]
Provide the directory in from which templates will be used.
Specify that the git repository is to be shared amongst several users.
This simply creates an empty git repository - basically a `.git` directory
and `.git/object/??/`, `.git/refs/heads` and `.git/refs/tags` directories,
and links `.git/HEAD` symbolically to `.git/refs/heads/master`.
If the `$GIT_DIR` environment variable is set then it specifies a path
to use instead of `./.git` for the base of the repository.
If the object storage directory is specified via the `$GIT_OBJECT_DIRECTORY`
environment variable then the sha1 directories are created underneath -
otherwise the default `$GIT_DIR/objects` directory is used.
A shared repository allows users belonging to the same group to push into that
repository. When specifying `--shared` the config variable "core.sharedRepository"
is set to 'true' so that directories under `$GIT_DIR` are made group writable
(and g+sx, since the git group may be not the primary group of all users).
Running `git-init-db` in an existing repository is safe. It will not overwrite
things that are already there. The primary reason for rerunning `git-init-db`
is to pick up newly added templates.
Start a new git repository for an existing code base::
$ cd /path/to/my/codebase
$ git-init-db <1>
$ git-add . <2>
<1> prepare /path/to/my/codebase/.git directory
<2> add all existing file to the index
Written by Linus Torvalds <>
Documentation by David Greaves, Junio C Hamano and the git-list <>.
Part of the gitlink:git[7] suite