@0x4E4F@lemmy.dbzer0.com to Memes@lemmy.ml • 1 year agoSomeone should tell himlemmy.dbzer0.comimagemessage-square132fedilinkarrow-up1863arrow-down115
arrow-up1848arrow-down1imageSomeone should tell himlemmy.dbzer0.com@0x4E4F@lemmy.dbzer0.com to Memes@lemmy.ml • 1 year agomessage-square132fedilink
minus-squarechtklinkfedilink107•1 year ago merge and commit Are we talking fast-forward or squash merges?
minus-square@Artyom@lemm.eelinkfedilink3•1 year agoLet’s just blame the Nazis to avoid making anyone too upset.
minus-square@Gork@lemm.eelinkfedilink16•edit-21 year agoBonus points if the different branches are all large, have a decent amount of overlap, and rely on different revision dependencies. And pushed through with minimal review or oversight.
minus-square@PoolloverNathan@programming.devlinkfedilinkEnglish5•1 year agoLet’s rebase, for the fun of it…
minus-square@navi@lemmy.tespia.orglinkfedilink2•1 year agoRebase/squash merge for sure. Definitely lost some history in there.
Are we talking fast-forward or squash merges?
Squash, definitely squash.
Who do we git blame ?
Let’s just blame the Nazis to avoid making anyone too upset.
Bonus points if the different branches are all large, have a decent amount of overlap, and rely on different revision dependencies. And pushed through with minimal review or oversight.
And then wonder why nothing works…
git push origin main --force
Yolo
Let’s rebase, for the fun of it…
But they don’t need SQL.
Rebase/squash merge for sure.
Definitely lost some history in there.