fix: update already present repositories#949
Merged
Merged
Conversation
7e0110d to
90cd182
Compare
tromai
reviewed
Dec 19, 2024
Signed-off-by: Ben Selwyn-Smith <benselwynsmith@googlemail.com>
90cd182 to
6aae4ef
Compare
tromai
reviewed
Dec 20, 2024
Signed-off-by: Ben Selwyn-Smith <benselwynsmith@googlemail.com>
tromai
approved these changes
Dec 20, 2024
behnazh-w
approved these changes
Jan 8, 2025
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
3 participants
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.
This fixes the issue with previously cloned repositories not updating when newer changes are present at their remote origins, by using
git fetchwhen the target directory of the clone is already present. This comes with a small performance hit for any analysis performed on a previously cloned target.Closes #948