851

submitted 4 months ago by ipconf@lemmy.ml to c/programmer_humor@programming.dev

137 comments fedilink hide all child comments

Yeah learned this the hard way.

you are viewing a single comment's thread
view the rest of the comments

[-] fibojoly@sh.itjust.works 3 points 4 months ago

You're confusing errors in your code, and errors while doing some git command you thought you knew. Lucky you, it's clearly never happened to you because you don't mess around with it.

[-] cmhe@lemmy.world 1 points 4 months ago* (last edited 4 months ago)

Sure, I sometimes messed up with git, but a git reset , checkout, rebase or filter-branch (In the extreme cases) normally fixes it, but real issues are very rare. And I use git a lot... But only the CLI, maybe people have issues with GUIs?

[-] AeonFelis@lemmy.world 7 points 4 months ago

[-] ezterry@lemmy.zip 2 points 4 months ago

Funny those are commands I avoid.. They all have to do with editing history which I know there is a vocal group here that loves "clean" history but that isn't what happened.

sure merge full features so you can roll back a feature.. And if something is really off I might start from a snapshot commit and cherry pick/merge a bunch in but usually history is histoy.. If submitting to a public project I may make a new branch with the cleaned version but why edit in line. That is risking issues.