So, I have a Git repository that was created by a colleague and that contains a number of sub-modules. Usually, when I have worked with Git sub-modules before, then a simple clone --recursive would fetch the "main" repository and all the nested sub-modules. But, with this "problematic" repository, the sub-directories for the sub-modules are just empty after the clone (with "--recursive" flag)! There's no error message or anything. Just nothing. Of course, the subsequent build will fail with missing files 🙄
Now, we also have GitLab as a Web-GUI for our Git server. In my other repositories, when I have some sub-modules, GitLab is smart: I can just click on the sub-module "folder" and then GitLab automatically navigates to the corresponding repository. But, with the "problematic" repository, if I click on the sub-module "folder" in GitLab, simply nothing happens. Again, nor error or anything.
How can I see or change the alleged "address" (URL) of a sub-module?