Fix "GitObjectDoesNotExistException" error when not using targetRepositoryName config
#1478
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
rhyskoedijk
changed the title
targetRepositoryName config
|
I suspect this will also fix #1427, but am not 100% sure yet; Will ask OP to re-test once this is merged. |
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.
Fixes #1413.
This reverts the part of #1382 that was added to stop Dependabot re-cloning the repo if it already existed locally. It seems that in some situations, this can cause Dependabot to base its PR on a dirty/uncommitted working state.
Dependabot will now always clone the source repo, even if it already exists locally; This is less efficient, but ensures that the correct files will be used for the update.