Recursive Submodule Update on Pull #1595
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Will this be merged somewhere soon? As I need this in a project. |
|
@mawit Cloud you describe how do you use Semaphore? It is important for project development. Please contact me by email fiftin@outlook.com. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR adjusts the
RecurseSubmodulesoption in thepullmethod to ensure recursive updating of submodules. Previously, submodules weren't being recursively updated during a pull operation. With this change, submodules will also be updated up to a depth as defined byDefaultSubmoduleRecursionDepth, which is currently set to 10.Changes:
RecurseSubmodulesto usegit.DefaultSubmoduleRecursionDepthin thepullmethod.