6 git-init - Create an empty git repository or reinitialize an existing one
11 'git-init' [-q | --quiet] [--bare] [--template=<template_directory>] [--shared[=<permissions>]]
21 Only print error and warning messages, all other output will be suppressed.
25 Create a bare repository. If GIT_DIR environment is not set, it is set to the
26 current working directory.
28 --template=<template_directory>::
30 Provide the directory from which templates will be used. The default template
31 directory is `/usr/share/git-core/templates`.
33 When specified, `<template_directory>` is used as the source of the template
34 files rather than the default. The template files include some directory
35 structure, some suggested "exclude patterns", and copies of non-executing
36 "hook" files. The suggested patterns and hook files are all modifiable and
39 --shared[={false|true|umask|group|all|world|everybody|0xxx}]::
41 Specify that the git repository is to be shared amongst several users. This
42 allows users belonging to the same group to push into that
43 repository. When specified, the config variable "core.sharedRepository" is
44 set so that files and directories under `$GIT_DIR` are created with the
45 requested permissions. When not specified, git will use permissions reported
48 The option can have the following values, defaulting to 'group' if no value
51 - 'umask' (or 'false'): Use permissions reported by umask(2). The default,
52 when `--shared` is not specified.
54 - 'group' (or 'true'): Make the repository group-writable, (and g+sx, since
55 the git group may be not the primary group of all users).
57 - 'all' (or 'world' or 'everybody'): Same as 'group', but make the repository
58 readable by all users.
60 - '0xxx': '0xxx' is an octal number and each file will have mode '0xxx'
61 Any option except 'umask' can be set using this option. '0xxx' will
62 override users umask(2) value, and thus, users with a safe umask (0077)
63 can use this option. '0640' will create a repository which is group-readable
64 but not writable. '0660' is equivalent to 'group'.
66 By default, the configuration flag receive.denyNonFastForwards is enabled
67 in shared repositories, so that you cannot force a non fast-forwarding push
75 This command creates an empty git repository - basically a `.git` directory
76 with subdirectories for `objects`, `refs/heads`, `refs/tags`, and
78 An initial `HEAD` file that references the HEAD of the master branch
81 If the `$GIT_DIR` environment variable is set then it specifies a path
82 to use instead of `./.git` for the base of the repository.
84 If the object storage directory is specified via the `$GIT_OBJECT_DIRECTORY`
85 environment variable then the sha1 directories are created underneath -
86 otherwise the default `$GIT_DIR/objects` directory is used.
88 Running `git-init` in an existing repository is safe. It will not overwrite
89 things that are already there. The primary reason for rerunning `git-init`
90 is to pick up newly added templates.
92 Note that `git-init` is the same as `git-init-db`. The command
93 was primarily meant to initialize the object database, but over
94 time it has become responsible for setting up the other aspects
95 of the repository, such as installing the default hooks and
96 setting the configuration variables. The old name is retained
97 for backward compatibility reasons.
103 Start a new git repository for an existing code base::
106 $ cd /path/to/my/codebase
111 <1> prepare /path/to/my/codebase/.git directory
112 <2> add all existing file to the index
117 Written by Linus Torvalds <torvalds@osdl.org>
121 Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
125 Part of the linkgit:git[1] suite