### Problem to solve Add a feature to update tracking submodules to tip of branch when running CI tasks. I currently use a feature in Jenkins that will automatically checkout the tip of a specified branch of git submodules. (See documentation at https://github.com/jenkinsci/git-plugin/blob/git-4.2.0/README.adoc#advanced-sub-modules-behaviours) I would like this feature to be implemented in Gitlab. Based on this [Stackoverflow question](https://stackoverflow.com/a/57770651), it appears that others would like this functionality too. ### Intended users Mainly these personas: * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> I propose adding a new value for [the git submodule variable](https://docs.gitlab.com/ee/ci/yaml/README.html#git-submodule-strategy) (name TBD) that will cause the gitlab worker to use the `--remote` flag when updating submodules. ### Documentation Unknown <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Availability & Testing TBD <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? TBD <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? This should go in the Free tier. ### Links / references Included inline above. Thank you for reading this feature request :smiley: