See submodule.propagateBranches inĬurrently, only branch creation is supported. Recurse into submodules if submodule.propagateBranches isĮnabled. THIS OPTION IS EXPERIMENTAL! Causes the current command to Git branch now includes in its man page: -recurse-submodules recurse-submodules will now consider branches. recurse-submodules and certain commands that already accept Using -recurse-submodules or submodule.recurse=true.Įnabling this will allow certain commands to accept A boolean that enables branching support when branch is supported only if submodule.propagateBranches is.Reset, restore and switch are always supported. checkout, fetch, grep, pull, push, read-tree,.recurse-submodules and whether they are supported by this The following list shows the commands that accept Git fetch but does not have a -no-recurse-submodules option.įor these commands a workaround is to temporarily change theĬonfiguration value by using git -c submodule.recurse=0.
GIT SUBMODULE ADD UPDATE
Submodule.recurse for instance git remote update will call Lacking this option may call some of the above commands affected by When set to true, it can be deactivated via the Git config now includes in its man page: submodule.recurse:Ī boolean indicating if commands should enable the -recurse-submodules option by default. Git config now includes in its man page: submodulesNotUpdatedĪdvice shown when a user runs a submodule command that failsīecause git submodule update -init was not run. Incidentally, fix an incorrect usage string that combined the 'list' usage of git branch (-l) with the 'create' usage this string has been incorrect since its inception, a8dfd5e ("Make builtin-branch.c use parse_options.",, Git v1.5.4-rc0 - merge). add the "submoduleNotUpdated" advice to advise users to update the submodules in their trees.add is_tree_submodule_active() by adding a treeish_name parameter to is_submodule_active().path and oid) and initializes the repository add a submodules_of_tree() helper that gives the relevant information of an in-tree submodule (e.g.gitmodules and gitlinks from the superproject commit, but submodules are typically read from the filesystem's. This commit also includes changes that support working with submodules from a superproject commit because " branch -recurse-submodules" (and future commands) need to read. The plan is for Git commands to prioritize submodule ref store information over superproject gitlinks if this value is true.īecause " git branch -recurse-submodules" writes to submodule ref stores, for the sake of clarity, it will not function unless this configuration value is set.
Start this process by teaching " git branch" ( man) the -recurse-submodules option so that git branch -recurse-submodules ( man) topic will create the topic branch in the superproject and its submodules.Īlthough this commit does not introduce breaking changes, it does not work well with existing -recurse-submodules commands because git branch -recurse-submodules" writes to the submodule ref store, but most commands only consider the superproject gitlink and ignore the submodule ref store.įor example, " git checkout -recurse-submodules" ( man) will check out the commits in the superproject gitlinks (and put the submodules in detached HEAD) instead of checking out the submodule branches.īecause of this, this commit introduces a new configuration value, submodule.propagateBranches. To improve the submodules UX, we would like to teach Git to handle branches in submodules.
(Merged by Junio C Hamano - gitster - in commit 5cc9522, ) branch: add -recurse-submodules option for branch creation See commit 679e369, commit 961b130, commit 6e0a2ca, commit 3f3e760, commit bc0893c, commit e89f151 () by Glen Choo ( chooglen). See commit 09e0be1 () by Junio C Hamano ( gitster). " git branch" ( man) learned the -recurse-submodules option. This will be officially supported (in an experimental mode at first) with Git 2.36 (Q2 2022). I would like to create a branch across all submodules including the parent Unable to find current origin/branch_name revision in submodule path 'submodule_1' Git returns: fatal: Needed a single revision gitmodules submodule.submodule_1.branch branch_name $ git submodule foreach "(git checkout branch_name git pull)&" Tried the following steps: $ git submodule foreach -b branch_name After which all branches are pushed remote to each submodules and their respected repos. I would like to create a branch across all submodules including the parent. (feature/my_feature) $ git push -u origin feature/my_feature (feature/my_feature) $ git commit -m "created my_feature" If I create a branch on parent repo: (master) $ git checkout -b feature/my_feature
GIT SUBMODULE ADD HOW TO
Struggling with understanding how to create branches across the board and adding them to all the remote repos.Ĭurrently my file structure resembles the following: -parent_repo
I am working with git submodules for the first time.
0 kommentar(er)
