git-init.txt 4.7 KB
Newer Older
J
Junio C Hamano 已提交
1 2 3 4 5
git-init(1)
===========

NAME
----
6
git-init - Create an empty Git repository or reinitialize an existing one
J
Junio C Hamano 已提交
7 8 9 10


SYNOPSIS
--------
11
[verse]
12
'git init' [-q | --quiet] [--bare] [--template=<template_directory>]
13
	  [--separate-git-dir <git dir>]
14
	  [--shared[=<permissions>]] [directory]
J
Junio C Hamano 已提交
15 16


17 18 19
DESCRIPTION
-----------

20
This command creates an empty Git repository - basically a `.git`
21 22 23 24 25 26 27 28 29 30 31 32 33 34
directory with subdirectories for `objects`, `refs/heads`,
`refs/tags`, and template files.  An initial `HEAD` file that
references the HEAD of the master branch is also created.

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.

Running 'git init' in an existing repository is safe. It will not
overwrite things that are already there. The primary reason for
35 36
rerunning 'git init' is to pick up newly added templates (or to move
the repository to another place if --separate-git-dir is given).
37

J
Junio C Hamano 已提交
38 39 40 41 42
OPTIONS
-------

--

43 44
-q::
--quiet::
45

46
Only print error and warning messages; all other output will be suppressed.
47

L
Luciano Rocha 已提交
48 49 50 51 52
--bare::

Create a bare repository. If GIT_DIR environment is not set, it is set to the
current working directory.

J
Junio C Hamano 已提交
53 54
--template=<template_directory>::

55 56
Specify the directory from which templates will be used.  (See the "TEMPLATE
DIRECTORY" section below.)
J
Junio C Hamano 已提交
57

58 59
--separate-git-dir=<git dir>::

60 61 62 63 64 65
Instead of initializing the repository as a directory to either `$GIT_DIR` or
`./.git/`, create a text file there containing the path to the actual
repository.  This file acts as filesystem-agnostic Git symbolic link to the
repository.
+
If this is reinitialization, the repository will be moved to the specified path.
66

67
--shared[=(false|true|umask|group|all|world|everybody|0xxx)]::
J
Junio C Hamano 已提交
68

69
Specify that the Git repository is to be shared amongst several users.  This
J
Junio C Hamano 已提交
70 71 72
allows users belonging to the same group to push into that
repository.  When specified, the config variable "core.sharedRepository" is
set so that files and directories under `$GIT_DIR` are created with the
73
requested permissions.  When not specified, Git will use permissions reported
J
Junio C Hamano 已提交
74
by umask(2).
75
+
J
Junio C Hamano 已提交
76 77
The option can have the following values, defaulting to 'group' if no value
is given:
78 79 80 81 82 83 84 85 86 87 88 89 90 91 92
+
--
'umask' (or 'false')::

Use permissions reported by umask(2). The default, when `--shared` is not
specified.

'group' (or 'true')::

Make the repository group-writable, (and g+sx, since the git group may be not
the primary group of all users). This is used to loosen the permissions of an
otherwise safe umask(2) value. Note that the umask still applies to the other
permission bits (e.g. if umask is '0022', using 'group' will not remove read
privileges from other (non-group) users). See '0xxx' for how to exactly specify
the repository permissions.
J
Junio C Hamano 已提交
93

94 95 96 97 98 99 100 101 102 103 104 105
'all' (or 'world' or 'everybody')::

Same as 'group', but make the repository readable by all users.

'0xxx'::

'0xxx' is an octal number and each file will have mode '0xxx'. '0xxx' will
override users' umask(2) value (and not only loosen permissions as 'group' and
'all' does). '0640' will create a repository which is group-readable, but not
group-writable or accessible to others. '0660' will create a repo that is
readable and writable to the current user and group, but inaccessible to others.
--
106

107
By default, the configuration flag `receive.denyNonFastForwards` is enabled
J
Junio C Hamano 已提交
108 109 110
in shared repositories, so that you cannot force a non fast-forwarding push
into it.

111 112
If you provide a 'directory', the command is run inside it. If this directory
does not exist, it will be created.
113

J
Junio C Hamano 已提交
114 115
--

116 117 118 119 120 121
TEMPLATE DIRECTORY
------------------

The template directory contains files and directories that will be copied to
the `$GIT_DIR` after it is created.

122
The template directory will be one of the following (in order):
123

124
 - the argument given with the `--template` option;
125

126
 - the contents of the `$GIT_TEMPLATE_DIR` environment variable;
127

128
 - the `init.templateDir` configuration variable; or
129

130
 - the default template directory: `/usr/share/git-core/templates`.
131

132 133
The default template directory includes some directory structure, suggested
"exclude patterns" (see linkgit:gitignore[5]), and sample hook files (see linkgit:githooks[5]).
J
Junio C Hamano 已提交
134 135 136 137

EXAMPLES
--------

138
Start a new Git repository for an existing code base::
J
Junio C Hamano 已提交
139 140 141
+
----------------
$ cd /path/to/my/codebase
142 143
$ git init      <1>
$ git add .     <2>
144
$ git commit    <3>
J
Junio C Hamano 已提交
145 146
----------------
+
147 148
<1> Create a /path/to/my/codebase/.git directory.
<2> Add all existing files to the index.
149
<3> Record the pristine state as the first commit in the history.
J
Junio C Hamano 已提交
150 151 152

GIT
---
153
Part of the linkgit:git[1] suite