0x4E4F@lemmy.dbzer0.com to Memes@lemmy.ml · 7 months agoSomeone should tell himlemmy.dbzer0.comimagemessage-square81fedilinkarrow-up1698arrow-down114
arrow-up1684arrow-down1imageSomeone should tell himlemmy.dbzer0.com0x4E4F@lemmy.dbzer0.com to Memes@lemmy.ml · 7 months agomessage-square81fedilink
minus-squarechtk@feddit.nllinkfedilinkarrow-up81·7 months ago merge and commit Are we talking fast-forward or squash merges?
minus-squareRouthinator@startrek.websitelinkfedilinkEnglisharrow-up40·7 months agoSquash, definitely squash.
minus-squareGork@lemm.eelinkfedilinkarrow-up14·edit-27 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-square0x4E4F@lemmy.dbzer0.comOPlinkfedilinkarrow-up8·7 months agoAnd then wonder why nothing works…
minus-squarepickman_model@lemmy.worldlinkfedilinkarrow-up6·7 months agogit push origin main --force Yolo
minus-squarePoolloverNathan@programming.devlinkfedilinkEnglisharrow-up4·7 months agoLet’s rebase, for the fun of it…
Are we talking fast-forward or squash merges?
Squash, definitely squash.
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.