![]() You can then customize the submoduleĬlone URLs in. When present, it will also copy the value of submodule.$name.update. Will be initialized, otherwise all submodules are initialized. ![]() Specified and submodule.active has been configured, submodules configured to be active Optional arguments limit which submodules will be initialized. If there is no default remote, the current repository will be assumed If the URL is relative, it will be resolved using theĭefault remote. Initialize the submodules recorded in the index (which were added and committedĮlsewhere) by setting submodule.$name.url in. Will provide that information too (and can also report changes to a submodule’s work Respect to the commit recorded in the index or the HEAD, git-status(1) and git-diff(1) If you are only interested in changes of the currently initialized submodules with If -recursive is specified, this command will recurse into nested submodules, and If -cached is specified, this command will instead print the SHA-1 recorded in the SHA-1 found in the index of the containing repository and U if the submodule has merge Is not initialized, + if the currently checked out submodule commit does not match the Each SHA-1 will possibly be prefixed with - if the submodule Out commit for each submodule, along with the submodule path and the output of git describe for the SHA-1. This will print the SHA-1 of the currently checked Git-submodule will correctly locate the submodule using the relative URL in The same relative location, and only the superproject’s URL needs to be provided. Presumption is the superproject and submodule repositories will be kept together in If the URL is given relative to the superproject’s repository, the gitmodules for use by subsequent users cloning the The is also used as the submodule’s logical name in itsĬonfiguration entries unless -name is used to specify a logical name. If exists and is already a valid Git repository, then it is staged for commit Repository is used ("repo" for "/path/to/repo.git" and "foo" for "host.xz:foo/.git"). ![]() If is not given, the canonical part of the source The optional argument is the relative location for the cloned submodule toĮxist in the superproject. The superproject is its own authoritative upstream and the current working directory If the superproject doesn’t have a default remote configured If no such remote-tracking branch exists or the HEAD is detached, "origin" is assumed The default remote is the remote of the remote-tracking branch of the current branch. Relative URLs - because the evaluation of relative URLs in Git is identical to that of foo.git - as one might expect when following the rules for Superproject’s default remote repository (Please note that to specify a repositoryįoo.git which is located right next to a superproject bar.git, you’ll have to use This may be eitherĪn absolute URL, or (if it begins with. is the URL of the new submodule’s origin repository. Several subcommands areĪvailable to perform operations on the submodules.Īdd [-depthĪdd the given repository as a submodule at the given path to the changeset to beĬommitted next to the current project: the current project is termed the With no arguments, shows the status of existing submodules. Inspects, updates and manages submodules.įor more information about submodules, see gitsubmodules(7). Git-submodule - Initialize, update or inspect submodules
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |