680
you are viewing a single comment's thread
view the rest of the comments
[-] xlash123@sh.itjust.works 120 points 2 months ago

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 130 points 2 months ago

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.

[-] Dultas@lemmy.world 21 points 2 months ago

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 15 points 2 months ago

Yes, that would do the trick

load more comments (2 replies)
load more comments (36 replies)
this post was submitted on 25 Apr 2024
680 points (97.4% liked)

Programmer Humor

18292 readers
1242 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS