PROBLEM DESCRIPTION "Could not access submodule" error when pulling recursively with Git 2.22.0. This issue causes if there is submodule in submodule.
At first, we reported this problem for Git for Windows: https://github.com/git-for-windows/git/issues/2361 But we received the answer that it was reproduced on Linux too. Also, the same problem is described here: https://gitlab.com/gitlab-org/gitlab/issues/27287 STEPS TO REPRODUCE Please use my simple test repository to reproduce the problem: https://github.com/agmikhailov/example2361.git It is just an empty repository with one submodule (https://github.com/agmikhailov/example2361M1.git) and one submodule of submodule (https://github.com/agmikhailov/example2361M2.git): git clone https://github.com/agmikhailov/example2361.git cd example2361/ git submodule init git submodule update git pull --recurse-submodules=true ACTUAL RESULT "git --recurse-submodules=true" command fails with message "Could not access submodule": $ git --recurse-submodules=true Fetching submodule example2361M1 Could not access submodule 'example2361M2' EXPECTED RESULT All submodules are successfully updated by "git --recurse-submodules=true" command. ADDITIONAL INFORMATION Git version 2.20.1 does not have this problem. So we had to downgrade Git to work with submodules. Best regards, -- Aleksey
