Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- All guides...
- 2.32.1 → 2.36.1 no changes
- 2.32.0 06/06/21
- 2.30.2 → 2.31.3 no changes
- 2.30.1 02/08/21
- 2.28.1 → 2.30.0 no changes
- 2.28.0 07/27/20
- 2.25.1 → 2.27.1 no changes
- 2.25.0 01/13/20
- 2.24.2 → 2.24.4 no changes
- 2.24.1 12/06/19
- 2.24.0 11/04/19
- 2.23.2 → 2.23.4 no changes
- 2.23.1 12/06/19
- 2.23.0 08/16/19
- 2.22.3 → 2.22.5 no changes
- 2.22.2 12/06/19
- 2.22.1 no changes
- 2.22.0 06/07/19
- 2.21.2 → 2.21.4 no changes
- 2.21.1 12/06/19
- 2.21.0 02/24/19
- 2.20.3 → 2.20.5 no changes
- 2.20.2 12/06/19
- 2.20.1 no changes
- 2.20.0 12/09/18
- 2.19.4 → 2.19.6 no changes
- 2.19.3 12/06/19
- 2.19.2 11/21/18
- 2.19.1 no changes
- 2.19.0 09/10/18
- 2.18.3 → 2.18.5 no changes
- 2.18.2 12/06/19
- 2.18.1 no changes
- 2.18.0 06/21/18
- 2.17.4 → 2.17.6 no changes
- 2.17.3 12/06/19
- 2.17.1 → 2.17.2 no changes
- 2.17.0 04/02/18
- 2.16.6 no changes
- 2.15.4 12/06/19
- 2.14.6 no changes
- 2.13.7 05/22/18
- 2.11.4 → 2.12.5 no changes
- 2.10.5 09/22/17
- 2.9.5 07/30/17
.gitmodules file, located in the top-level directory of a Git
working tree, is a text file with a syntax matching the requirements
The file contains one subsection per submodule, and the subsection value
is the name of the submodule. The name is set to the path where the
submodule has been added unless it was customized with the
option of git submodule add. Each submodule section also contains the
following required keys:
Defines the path, relative to the top-level directory of the Git working tree, where the submodule is expected to be checked out. The path name must not end with a
/. All submodule paths must be unique within the .gitmodules file.
Defines a URL from which the submodule repository can be cloned. This may be either an absolute URL ready to be passed to git-clone or (if it begins with ./ or ../) a location relative to the superproject’s origin repository.
In addition, there are a number of optional keys:
Defines the default update procedure for the named submodule, i.e. how the submodule is updated by "git submodule update" command in the superproject. This is only used by
git submodule initto initialize the configuration variable of the same name. Allowed values here are checkout, rebase, merge or none. See description of update command in git-submodule for their meaning. For security reasons, the !command form is not accepted here.
A remote branch name for tracking updates in the upstream submodule. If the option is not specified, it defaults to master. A special value of
.is used to indicate that the name of the branch in the submodule should be the same name as the current branch in the current repository. See the
--remotedocumentation in git-submodule for details.
This option can be used to control recursive fetching of this submodule. If this option is also present in the submodules entry in .git/config of the superproject, the setting there will override the one found in .gitmodules. Both settings can be overridden on the command line by using the "--[no-]recurse-submodules" option to "git fetch" and "git pull".
Defines under what circumstances "git status" and the diff family show a submodule as modified. The following values are supported:
The submodule will never be considered modified (but will nonetheless show up in the output of status and commit when it has been staged).
All changes to the submodule’s work tree will be ignored, only committed differences between the HEAD of the submodule and its recorded state in the superproject are taken into account.
Only untracked files in submodules will be ignored. Committed differences and modifications to tracked files will show up.
No modifiations to submodules are ignored, all of committed differences, and modifications to tracked and untracked files are shown. This is the default option.
If this option is also present in the submodules entry in .git/config of the superproject, the setting there will override the one found in .gitmodules.
Both settings can be overridden on the command line by using the "--ignore-submodule" option. The git submodule commands are not affected by this setting.
When set to true, a clone of this submodule will be performed as a shallow clone (with a history depth of 1) unless the user explicitly asks for a non-shallow clone.
Consider the following .gitmodules file:
[submodule "libfoo"] path = include/foo url = git://foo.com/git/lib.git
[submodule "libbar"] path = include/bar url = git://bar.com/git/lib.git
This defines two submodules,
libbar. These are expected to
be checked out in the paths include/foo and include/bar, and for both
submodules a URL is specified which can be used for cloning the submodules.
Part of the git suite