Maven (famous) to Programmer [email protected] • 9 months agoGOD DAMMIT STEVEN! NOT AGAIN!imagemessage-square72arrow-up1691arrow-down119
arrow-up1672arrow-down1imageGOD DAMMIT STEVEN! NOT AGAIN!Maven (famous) to Programmer [email protected] • 9 months agomessage-square72
minus-square@Backfirelink126•9 months agoYou’d have to rewrite the history as to never having committed those files in the first place, yes. And then politely ask all your coworkers to reset their working environments to the “new” head of the branch, same as the old head but not quite. Chaos ensues. Sirens in the distance wailing.
minus-square@Potatos_are_not_friendslink32•9 months agoRewrite history? Difficult. Start a new project and nuke the old one? Finger guns.
minus-square@Klearlink23•9 months agoHistory is written by the victors. The rest of us have to nuke the project and start over.
minus-square@Dultaslink19•9 months agoIf this was committed to a branch would doing a squash merge into another branch and then nuking the old one not do the trick?
You’d have to rewrite the history as to never having committed those files in the first place, yes.
And then politely ask all your coworkers to reset their working environments to the “new” head of the branch, same as the old head but not quite.
Chaos ensues. Sirens in the distance wailing.
Rewrite history? Difficult.
Start a new project and nuke the old one? Finger guns.
History is written by the victors. The rest of us have to nuke the project and start over.
If this was committed to a branch would doing a squash merge into another branch and then nuking the old one not do the trick?
Yes, that would do the trick