@ephemeromorph i wonder if it might be related to sarcastic answers it might have scraped

or those of us who early on found it a lot easier to nuke an entire repository and reupload the local project than to figure out how squashing or rebasing worked

@ephemeromorph imagine if someone tried to AI their way through an old Windows system and it just

kept

deleting system32

over every trivial inconvenience

To speed up the performance of the system, I deleted system32 which is a cache for Internet Explorer and slows down the system. Performing a reboot now to make the changes persist...

CC: @ephemeromorph@topspicy.social

@apophis i still don't know what's a squash or a rebase, git commit is short for commitment

when you're working with other people and you're developing a feature in a branch and others are reviewing it and CI jobs testing it, you probably don't want to end up merging 10 commits with earlier, worse working stuff or rejected experiments into the main branch, so before merging you squash it all together into however many commits makes sense. And rebasing is just for getting rid of merge commits all over the place. If you're working alone it probably doesn't matter unless you commit an API key or something that you want to revert or squash out.

CC: @apophis@kill-corporations.enterprises