Warning updating the currently checked out branch may cause confusion speed dating stories

Posted by / 26-Jan-2021 15:29

You can rinse and repeat this for just about any error :') I've bumped into this a couple of times and was scratching my head as to why it worked on some of my repos and not others.

So while NPM is the only outlier, it's for good reason, and we likely want to follow the lead of other package managers that actually do dependency resolution.My view is that the lockfile is always supposed to be timeless and canonical -- it should be .If it can't be that, then it's not living up to the promise of a lockfile, imho :) //cc @yfeldblum @Rob Loach EDIT: I've since realized that npm doesn't actually do any dependency resolution, and instead recursively stores every version of a required module at each level.The problem could be easily mitigated by extending the response of , instead of making them search for an answer.I've used Composer for quite a while and I still stumble upon this issue every now and then.

warning updating the currently checked out branch may cause confusion-85warning updating the currently checked out branch may cause confusion-66warning updating the currently checked out branch may cause confusion-89

dev-master always checking the actual master and then checking out the latest commit.

One thought on “warning updating the currently checked out branch may cause confusion”

  1. so, i flooded the help central with the only form provided to me for that type of problem. this time i spoke with a different clueless girl who was twice as rude as the first, and who told me “there is no one who can help you.” the temporary error is now over three weeks old, and although i have not received any assistance, i've been polite and patient through it all. i would just like to be able to access my e-mail folders and salvage whatever i can.i'm also trying to access two accounts!