# git-init(1) - man - phpMan

[GIT-INIT(1)](https://www.chedong.com/phpMan.php/man/GIT-INIT/1/markdown)                                  Git Manual                                  [GIT-INIT(1)](https://www.chedong.com/phpMan.php/man/GIT-INIT/1/markdown)



## NAME
       git-init - Create an empty Git repository or reinitialize an existing one

## SYNOPSIS
       _git_ _init_ [-q | --quiet] [--bare] [--template=<template_directory>]
                 [--separate-git-dir <git dir>] [--object-format=<format>]
                 [-b <branch-name> | --initial-branch=<branch-name>]
                 [--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 branch without any commits
       will be created (see the **--initial-branch** option below for its name).

       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 rerunning _git_ _init_ is to pick up newly added templates
       (or to move the repository to another place if --separate-git-dir is given).

## OPTIONS
### -q, --quiet
           Only 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.

       --object-format=<format>
           Specify the given object format (hash algorithm) for the repository. The valid values are
           _sha1_ and (if enabled) _sha256_.  _sha1_ is the default.

           THIS OPTION IS EXPERIMENTAL! SHA-256 support is experimental and still in an early stage.
           A SHA-256 repository will in general not be able to share work with "regular" SHA-1
           repositories. It should be assumed that, e.g., Git internal file formats in relation to
           SHA-256 repositories may change in backwards-incompatible ways. Only use
           **--object-format=sha256** for testing purposes.

       --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 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.

       -b <branch-name>, --initial-branch=<branch-name>
           Use the specified name for the initial branch in the newly created repository. If not
           specified, fall back to the default name (currently **master**, but this is subject to change
           in the future; the name can be customized via the **init.defaultBranch** configuration
           variable).

### --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)](https://www.chedong.com/phpMan.php/man/umask/2/markdown).

           The option can have the following values, defaulting to _group_ if no value is given:

           _umask_ (or _false_)
               Use permissions reported by [umask(2)](https://www.chedong.com/phpMan.php/man/umask/2/markdown). 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)](https://www.chedong.com/phpMan.php/man/umask/2/markdown) 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)](https://www.chedong.com/phpMan.php/man/umask/2/markdown) 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.

       By default, the configuration flag **receive.denyNonFastForwards** is enabled in shared
       repositories, so that you cannot force a non fast-forwarding push into it.

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

## TEMPLATE DIRECTORY
       Files and directories in the template directory whose name do not start with a dot will be
       copied to the **$GIT**___**DIR** after it is created.

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

       •   the argument given with the **--template** option;

       •   the contents of the **$GIT**___**TEMPLATE**___**DIR** environment variable;

       •   the **init.templateDir** configuration variable; or

       •   the default template directory: **/usr/share/git-core/templates**.

       The default template directory includes some directory structure, suggested "exclude
       patterns" (see [**gitignore**(5)](https://www.chedong.com/phpMan.php/man/gitignore/5/markdown)), and sample hook files.

       The sample hooks are all disabled by default. To enable one of the sample hooks rename it by
       removing its **.sample** suffix.

       See [**githooks**(5)](https://www.chedong.com/phpMan.php/man/githooks/5/markdown) for more general info on hook execution.

## EXAMPLES
       Start a new Git repository for an existing code base

               $ cd /path/to/my/codebase
               $ git init      **(1)**
               $ git add .     **(2)**
               $ git commit    **(3)**

           **1.** Create a /path/to/my/codebase/.git directory.
           **2.** Add all existing files to the index.
           **3.** Record the pristine state as the first commit in the history.

## GIT
       Part of the [**git**(1)](https://www.chedong.com/phpMan.php/man/git/1/markdown) suite



Git 2.34.1                                   02/26/2026                                  [GIT-INIT(1)](https://www.chedong.com/phpMan.php/man/GIT-INIT/1/markdown)
