Heh. I had a comment written earlier, but decided not to post it since I’ve been hating on git enough recently. Your first remark reminded me of it, though.
I immediately picked the option that I would like to pull and merge with few conflicts. Who wouldn’t? :)
Saw the solution was git pull --rebase and googled “git pull rebase”. The resulting recommendations varied from always use pull rebase to never use pull rebase.
My understanding is limited, but that does seem like a command that could also go on the “how to break git” website.
I like the idea, but I can’t imagine a time in the past where my git troubles were solved in a few simple commands.
https://github.com/k88hudson/git-flight-rules
http://thechangelog.com/git-flight-rules/
https://lobste.rs/s/vn3t17/flight_rules_for_git
I broke git while trying to rebase from upstream using git pull –rebase
While trying to rebase master onto my branch
While trying to push a rebased branch up to remote
Heh. I had a comment written earlier, but decided not to post it since I’ve been hating on git enough recently. Your first remark reminded me of it, though.
I immediately picked the option that I would like to pull and merge with few conflicts. Who wouldn’t? :)
Saw the solution was
git pull --rebaseand googled “git pull rebase”. The resulting recommendations varied from always use pull rebase to never use pull rebase.My understanding is limited, but that does seem like a command that could also go on the “how to break git” website.
The document On undoing, fixing, or removing commits in git – “a git choose-your-own adventure” – is very easy to follow when you need it.