fix(backend): Explicitly set refspec on fetch #497
Merged
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.
For certain repos, re-indexing would fail when calling
git fetchwith error messagefatal: couldn't find remote ref HEAD. The theory is that while we did have a refspec forremote.origin.fetch, it was not being resolved since we were fetching against the remote url and notorigin. The solution is to specify the refspec inline with the fetch command.Fixes #492