greenkeeperio / greenkeeper-lockfile

:lock: Your lockfile, up to date, all the time
https://greenkeeper.io
182 stars 73 forks source link

greenkeeper-lockfile-update fails with git merge error #216

Closed lewisakura closed 5 years ago

lewisakura commented 5 years ago

CI Greenkeeper issue on my repo

Got this error where greenkeeper-lockfile-update fails with a git merge error relating to package-lock.json. This could perfectly be caused by the fact that we pull out an older copy of package-lock.json earlier when we restore the cache, but I've never seen this issue occur before.

For example, this worked perfectly fine with the current CI setup.

I have no clue how to fix this.

janl commented 5 years ago

@LewisTehMinerz sorry for the trouble here. Just checking, because there might be an easy way out: if you have only public dependencies (npm registry or git), you don’t need greenkeeper-lockfile anymore.

If you have private dependencies, you’ll need it for now, and we can look into debugging your problem, just let us know here.

lewisakura commented 5 years ago

@janl So we don't actually need to run greenkeeper-lockfile?

cfanoulis commented 5 years ago

Holds E to revive this chat

Hello there. I am working with @LewisTehMinerz on the same project that errors. Should we remove the lockfile stage on our CI?

lewisakura commented 5 years ago

we've removed greenkeeper-lockfile from our CI stage, we'll see what happens

lewisakura commented 5 years ago

everything works.