Unable to `git submodule foreach git pull`

This question is based on this thread.

My .gitmodules is at my Home

  • How to add additional parents to old git commits?
  • Git, find out which files have had the most commits
  • git rm --cached still leaves files somewhere in repo
  • git svn ambiguous argument 'HEAD'
  • Wiki - File versioning
  • git push to remote master branch
  • [submodule "bin"]
               path = bin
               url = git://github.com/masi/bin.git

    My folder -structure at my Home:

    |-- [drwxr-xr-x] bin          // this is the folder which I make a submodule
                                  // it is also a folder where I have a Git to push my submodule's files
        | -- fileA
        ` -- folderA

    I run

    git submodule init    # I get no output from these commands
    git submodule update          

    I run

    git submodule foreach git pull

    I get

    Entering 'bin'
    fatal: Where do you want to fetch from today?
    Stopping at 'bin'; script returned non-zero status.

    My first assumption to fix the bug was to change path = bin to path = /Users/Masi/bin. However, this does not solve the problem.

    How can you upload the content from the external repository which is a submodule in my Git?

  • git branch, fork, fetch, merge, rebase and clone, what are the differences?
  • git workflow incorporating many, but not all commits from many forks
  • Git nested repos
  • How to enable `git checkout -b branch` default behavior on VSCode?
  • Encoding Issues in Eclipse for Mac and for Windows
  • How do I convert my SVN repository to Git while preserving branches?
  • 3 Solutions collect form web for “Unable to `git submodule foreach git pull`”

    This is normally the error made when there is no remote configured.
    (From this thread)

    It was a patch introduced to at least fixes the regression when running “git pull” in a repository initialized long time ago that does not use the .git/config file to specify where my remote repositories are.

    a better message would probably be something like:

    No default remote is configured for your current branch,
    and the default remote “origin” is not configured either.

    I think the message missed being made user-friendly in earlier passes due
    to being inaccessible at the time.

    So this message indicates the remote repo mentioned in .git/modules is not declared in .git/config

    From git submodule

    Submodules are not to be confused with remotes, which are meant mainly for branches of the same project;
    submodules are meant for different projects you would like to make part of your source tree, while the history of the two projects still stays completely independent and you cannot modify the contents of the submodule from within the main project.

    I believe you may have missed the step of git submodule init:

    submodule init

    Initialize the submodules, i.e. register each submodule name and url found in .gitmodules into .git/config.
    The key used in .git/config is submodule.$name.url.
    This command does not alter existing information in .git/config.
    You can then customize the submodule clone URLs in .git/config for your local setup and proceed to git submodule update; you can also just use git submodule update --init without the explicit init step if you do not intend to customize any submodule locations.

    If your remote repo (declared in .git/modules) is adequately referenced in .git/config, you should not have this error message anymore.

    Before using (pullin) submodules, the steps:

    git submodule init
    git submodule update

    remain necessary.

    What does the .git/config look like
    for your bin submodule?

    My .git/config

        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
        ignorecase = true
    [remote "github"]
        url = git@github.com:masi/Sam.git
        fetch = +refs/heads/*:refs/remotes/github/*
    [submodule "bin"]
        url = git://github.com/masi/bin.git

    I removed the submodule -part in my .git/config.

    I run

    ~ master* $ git submodule init                      #this adds it back to .git/config
    Submodule 'bin' (git://github.com/masi/bin.git) registered for path 'bin'
    ~ master* $ git submodule update 
    ~ master* $ git submodule foreach git pull
    Entering 'bin'
    fatal: Where do you want to fetch from today?
    Stopping at 'bin'; script returned non-zero status.
    ~ master* $ 

    The same problem persists.

    Git Baby is a git and github fan, let's start git clone.