#GIT SUBMODULE SET BRANCH UPDATE#
#GIT SUBMODULE SET BRANCH CODE#

# which will fix the states for both submodule and parent since # since you did not push you submodule chage commit to remote. # from remote master which is 1 commit behind your local branch

#GIT SUBMODULE SET BRANCH UPDATE#

# since at this point you just asked git to update your submodule # as you see you are DETACHED and you are lucky if you found out now $ git status # will show again that (submodule has new commits) Submodule path 'path/to/submodule': checked out 'commit-hash' Nothing to commit, working directory clean # As normally you would commit new commit hash to your parent repo Modified: path/to/submodule (new commits) $ git commit -m'Your modification' # Let's say you forgot to push it to remote. update = checkout $ cd # and make modification to your submodule In the common cases, you already have fixed by now your DETACHED HEAD since it was related to one of the configuration issues above.įixing DETACHED HEAD when. # is here path releative to parent repo root First you want to make sure that your submodule has the branch checked out which you want to be tracked.If you haven't added your existing submodule like this you can easily fix that:.you tell git to update your submodule from remote.you tell git to perform rebase or merge instead of checkout.First you tell git to track your remote.Solution: Make your submodule track its remote branch by adding new submodules with the following two commands. Cause: Your parent repo is not configured to track submodules branch.# If no is specified, then it defaults to the current branch. # if the master branch already exists locally: Solution: Make sure your submodule is tracking the correct branch Cause: Your submodule is not tracking correct branch (default master).I believe that I am correct in stating, that we all have been there at some point where our submodule's HEAD gets detached. This is a common case when one does not use submodules too often or has just started with submodules. So back to the question: Why does it happen?Īfter pulling changes from server, many times my submodule head gets detached from master branch. Personally I hate answers here which direct to external links which may stop working over time and check my answer here (Unless question is duplicate) - directing to question which does cover subject between the lines of other subject, but overall equals: 'I'm not answering, read the documentation.' is what you want to change, see the docs - default checkout submodule.branch specify remote branch to be tracked - default master

Gitlab runner with the Kubernetes Executor.

#GIT SUBMODULE SET BRANCH CODE#

From ************/test/mymodule * branch 31d631ca35bad5f5b9647500f3a7604b70501542 -> FETCH_HEAD Submodule path 'mymodule': checked out '31d631ca35bad5f5b9647500f3a7604b70501542' Entering 'mymodule' Entering 'mymodule' Executing 'step_script' stage of the job script 00:01 $ cd mymodule $ git checkout dev error: pathspec 'dev' did not match any file (s ) known to git Cleaning up file based variables 00:00 ERROR: Job failed: command terminated with exit code 1 Environment description Submodule 'mymodule' *************/test/mymodule.git ) registered for path 'mymodule' Cloning into '/builds/ZNjBtxc3/0/test/test/mymodule'. Updating/initializing submodules recursively with git depth set to 50. Initialized empty Git repository in /builds/ZNjBtxc3/0/test/tes/.git/ Created fresh repository. Getting source from Git repository 00:02 Fetching changes with git depth set to 50. Preparing environment 00:06 Waiting for pod ********************* to be running, status is Pending Waiting for pod ********************* to be running, status is Pending ContainersNotReady: 'containers with unready status: ' ContainersNotReady: 'containers with unready status: ' Running on runner-znjbtxc3-project-1471-concurrent-0fwjvh via *********************. Using attach strategy to execute scripts.

Git submodule set branch