Skip to content

Instantly share code, notes, and snippets.

@samselikoff
Created March 24, 2018 14:26
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save samselikoff/3dc840cd56140d47fbbb04577d01aedf to your computer and use it in GitHub Desktop.
Save samselikoff/3dc840cd56140d47fbbb04577d01aedf to your computer and use it in GitHub Desktop.

The approach that has worked for me so far is this:

git rebase origin/master

When the first conflict arises, I checkout the yarn.lock then re-perform the installation

git checkout origin/master -- yarn.lock
yarn install

This generates a new yarn.lock based on the origin/master version of yarn.lock, but including the changes I made to my package.json. Then it's just a matter of:

git add yarn.lock
git rebase --continue

And I'm back in business.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment