table of contents
other versions
- wheezy 1:1.7.10.4-1+wheezy3
- wheezy-backports 1:1.9.1-1~bpo70+2
- jessie 1:2.1.4-2.1+deb8u2
- jessie-backports 1:2.11.0-3~bpo8+1
- testing 1:2.11.0-3
- unstable 1:2.11.0-4
- experimental 1:2.13.1+next.20170610-1
GIT-INIT(1) | Git Manual | GIT-INIT(1) |
NAME¶
git-init - Create an empty git repository or reinitialize an existing oneSYNOPSIS¶
git init [-q | --quiet] [--bare] [--template=<template_directory>] [--separate-git-dir <git dir>] [--shared[=<permissions>]] [directory]
DESCRIPTION¶
This command creates an empty git repository - basically a .git 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.OPTIONS¶
-q, --quietOnly print error and warning messages, all
other output will be suppressed.
--bare
Create a bare repository. If GIT_DIR
environment is not set, it is set to the current working directory.
--template=<template_directory>
Specify the directory from which templates
will be used. (See the "TEMPLATE DIRECTORY" section below.)
--separate-git-dir=<git dir>
Instead of initializing the repository where
it is supposed to be, place a filesytem-agnostic git symbolic link there,
pointing to the specified git path, and initialize a git repository at the
path. The result is git repository can be separated from working tree. If this
is reinitialization, the repository will be moved to the specified path.
--shared[=(false|true|umask|group|all|world|everybody|0xxx)]
Specify that the git repository is to be
shared amongst several users. This 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 requested permissions. When not specified, git
will use permissions reported by umask(2).
•
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.
•
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.
TEMPLATE DIRECTORY¶
The template directory contains files and directories that will be copied to the $GIT_DIR after it is created.•The argument given with the --template
option.
•The contents of the $GIT_TEMPLATE_DIR
environment variable.
•The init.templatedir configuration
variable.
•The default template directory:
/usr/share/git-core/templates.
EXAMPLES¶
Start a new git repository for an existing code base$ cd /path/to/my/codebase $ git init (1) $ git add . (2)
GIT¶
Part of the git(1) suite03/19/2016 | Git 1.7.10.4 |