Setting fetch-depth #2031
Merged
Setting fetch-depth #2031
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
|
Do we need to make the same change to |
ehildenb
approved these changes
Aug 23, 2023
Lets do it, to avoid this issue if it were to affect those locations as well. Will commit in a moment |
ehildenb
approved these changes
Aug 23, 2023
iFrostizz
pushed a commit
that referenced
this pull request
Aug 28, 2023
* Setting fetch-depth * Set Version: 1.0.273 * Set Version: 1.0.275 * Resolve possible future issues on recursive checkouts of submodules --------- Co-authored-by: devops <devops@runtimeverification.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.
I think this may resolve the issues we've been seeing @dwightguth with corrupted submodule checkouts.
With a related issue noted here: This could be a fix for it.
https://stackoverflow.com/questions/66460369/git-submodule-update-failure