Recursively set up Git submodules credentials
What does this MR do?
Previously if you used GIT_SUBMODULE_STRATEGY: normal and accessed
nested submodules,
!5962 (merged) only
initialized the credentials for the top-level submodules. However, there
are existing workflows that rely on git submodule update --init to
just work from the nested directory.
To preserve existing workflows, recursively update the nested submodules credentials.
Why was this MR needed?
What's the best way to test this MR?
- Find/create a project with nested submodules.
- Set
GIT_SUBMODULE_STRATEGY: normalin the.gitlab-ci.ymlvariables. - Run a pipeline.
- Verify that running
cd path/to/nested-submodule && git submodule update --initworks.
What are the relevant issue numbers?
Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/583366
Edited by Stan Hu