Pull: stop double-fetching submodules - #135
Merged
jamiew merged 1 commit intoMay 29, 2026
Merged
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
- the explicit `git fetch` added in #133 recursed into submodules, and so does the `git pull --recurse-submodules` right after, so every submodule got fetched twice - pass `--no-recurse-submodules` to the branch-refresh fetch; the recursive pull still owns submodule updates
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
the explicit git fetch we added in #133 (to keep all branch refs fresh) recurses into submodules, and so does the git pull --recurse-submodules right after it — so on a repo with submodules every submodule gets fetched twice on every pull. this passes --no-recurse-submodules to that first fetch so submodules are only fetched once.
to test: