@[email protected] to [email protected] • 9 months agoSomeone should tell himlemmy.dbzer0.comimagemessage-square117fedilinkarrow-up1804arrow-down114
arrow-up1790arrow-down1imageSomeone should tell himlemmy.dbzer0.com@[email protected] to [email protected] • 9 months agomessage-square117fedilink
minus-square@[email protected]linkfedilink104•9 months ago merge and commit Are we talking fast-forward or squash merges?
minus-square@[email protected]linkfedilink3•9 months agoLet’s just blame the Nazis to avoid making anyone too upset.
minus-square@[email protected]linkfedilink16•edit-29 months 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@[email protected]linkfedilink2•9 months 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.