fix(hasLockfileCommit): specify origin when fetching #184
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.
There is more context in #164 (comment)
When configuring the remote to use
GH_TOKEN
inupload.js
it is only done for thegk-origin
remote, but then ingit-helpers#hasLockfileCommit
agit fetch
is done, which can fail if there is aorigin
remote defined, as this one is not configured withGH_TOKEN
.This PR updates
hasLockfileCommit
to make the fetch fromgk-origin
.