Correct me if I'm wrong, but it's not enough to delete the files in the commit, unless you're ok with Git tracking the large amount of data that was previously committed. Your git clones will be long, my friend

[–] Backfire@lemmy.world 128 points 6 months ago (2 children)

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.

[–] Potatos_are_not_friends@lemmy.world 34 points 6 months ago (1 children)

Rewrite history? Difficult.

Start a new project and nuke the old one? Finger guns.

[–] Klear@lemmy.world 23 points 6 months ago

History is written by the victors. The rest of us have to nuke the project and start over.

[–] Dultas@lemmy.world 20 points 6 months ago (1 children)

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?

[–] Backfire@lemmy.world 14 points 6 months ago

Yes, that would do the trick

load more comments (36 replies)