git/modules/ new/path/to/config file, make sure that worktree item points to the new locations, so in this example it should be worktree =. git/modules/ new/path/to/module.Įdit the. git/modules/ old/path/to/module with all its content to. Remove the old directory with git rm -cached old/path/to/module. Make sure Git tracks this directory ( git add new/path/to). Move all content from the old to the new directory ( mv -vi old/path/to/module new/path/to/submodule). If needed, create the parent directory of the new location of the submodule ( mkdir -p new/path/to). gitmodules and change the path of the submodule appropriately, and put it in the index with git add. Or configured (for an existing submodule) to follow a branch: cd /path/to/parent/repo Įither added with a branch to follow: git submodule -b abranch - /url/of/submodule/repo Since the SHA1 of the submodule would change, you would still need to follow that with: git add.
Git add remote submodule update#
Rather than going in each submodule, doing a git checkout abranch -track origin/abranch, git pull, you can simply do (from the parent repo) a: git submodule update -remote -recursive To checkout the latest state of a specific submodule, you can use : git submodule update -remote Ī submodule is always checked out at a specific commit SHA1 (the "gitlink", special entry in the index of the parent repo)īut one can request to update that submodule to the latest commit of a branch of the submodule remote repo. There might be some changes you have that can have merge conflict if you use git pull so you can use git pull -rebase to rewind your changes to top, most of the time it decreases the chances of conflict. To update your repository to reference the new state instead, you have to commit the changes: git add Running git status will list the submodule directory as dirty if it changed because of this command. Note that this will just update your local working copy. Or use the default git pull arguments git submodule foreach git pull
To check out all submodules to the latest state on the remote with a single command, you can use git submodule foreach git pull Sometimes instead of using the state that is referenced you want to update to your local checkout to the latest state of that submodule on a remote. To check out the exact state that is referenced for all submodules, run git submodule update -recursive Updating a SubmoduleĪ submodule references a specific commit in another repository. This is equivalent to running git submodule update -init -recursive immediately after the clone is finished.
This will clone the referenced submodules and place them in the appropriate folders (including submodules within submodules). When you clone a repository that uses submodules, you'll need to initialize and update them. Cloning a Git repository having submodules gitmodules file this tells Git what submodules should be cloned when git submodule update is run. You can include another Git repository as a folder within your project, tracked by Git: $ git submodule add Tidying up your local and remote repository.Reflog - Restoring commits not shown in git log.Display commit history graphically with Gitk.mailmap file: Associating contributor and email aliases
0 kommentar(er)
