alphacyberranger to Programmer [email protected]English • 1 year agoHistory repeats itselfimagemessage-square35arrow-up1498arrow-down113
arrow-up1485arrow-down1imageHistory repeats itselfalphacyberranger to Programmer [email protected]English • 1 year agomessage-square35
minus-square@[email protected]linkfedilink4•edit-21 year agofor some reason it’s easier than normal rebasing though
minus-square@[email protected]linkfedilink4•1 year agoHave you tried interactive rebase (rebase -i)? I find it very useful
minus-square@[email protected]linkfedilink2•1 year agorerere is a lifesaver here. (I’m also a fan of rebasing; but I also like to land commits that perform a logical and separable chunk of work, because I like history to have decent narrative flow.)
minus-square@[email protected]linkfedilink2•1 year agoYou can get merge conflicts in cherry picks too, it’s the same process.
for some reason it’s easier than normal rebasing though
Have you tried interactive rebase (rebase -i)? I find it very useful
Yeah, but then you deal with merge conflicts
rerere is a lifesaver here.
(I’m also a fan of rebasing; but I also like to land commits that perform a logical and separable chunk of work, because I like history to have decent narrative flow.)
You can get merge conflicts in cherry picks too, it’s the same process.