Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(hasLockfileCommit): specify origin when fetching #184

Merged
merged 2 commits into from
Jul 17, 2018
Merged

fix(hasLockfileCommit): specify origin when fetching #184

merged 2 commits into from
Jul 17, 2018

Conversation

tagoro9
Copy link
Contributor

@tagoro9 tagoro9 commented Jul 16, 2018

There is more context in #164 (comment)

When configuring the remote to use GH_TOKEN in upload.js it is only done for the gk-origin remote, but then in git-helpers#hasLockfileCommit a git fetch is done, which can fail if there is a origin remote defined, as this one is not configured with GH_TOKEN.

This PR updates hasLockfileCommit to make the fetch from gk-origin.

@@ -31,7 +31,7 @@ module.exports = {
// console.log(`git config --replace-all remote.origin.fetch +refs/heads/*:refs/remotes/origin/*`)
exec(`git config --replace-all remote.origin.fetch +refs/heads/*:refs/remotes/origin/*`)
// console.log(`git fetch`)
exec(`git fetch`)
exec(`git fetch gk-origin`)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be ideal to have this gk-origin value stored isomewhere, as it is referenced here and in upload.js but not sure where to put it.

@janl janl merged commit 63d35a9 into greenkeeperio:master Jul 17, 2018
@janl
Copy link
Contributor

janl commented Jul 17, 2018

excellent, thanks!

@greenkeeperio-bot
Copy link
Member

🎉 This PR is included in version 2.3.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@mAAdhaTTah
Copy link

This command appears to be failing for a couple people, as noted in #164. Would opening a new issue be more helpful or is this already being investigated?

@janl
Copy link
Contributor

janl commented Jul 18, 2018

I'm looking at 164, but I ran out of time to day and I'm off work now. I'll be looking at this again tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants