- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
Back when I was still on Reddit, I made a comment on a chess sub saying that in chess you are not allowed to make your king “commit suicide” to explain how a stalemate works. One day later I got a message about suicide prevention because someone flagged me for promoting suicide.
What a dumb site.
I mean in all fairness it was probably a bot that flagged that.
By the time I left (API shenengigans) Reddit was already a place where bots interacted with bots half the time.
One of my favorite moments on reddit was spotting a bot that spouted unrelated nonsense. I checked the comment history and found users responding earnestly to the nonsense. While it was hilarious, it was also quite sad, the state of those people.
What people? “It’s bots all the way down, of course!”
They should have known you were just horsing around.
He got pawnd!
Google helpline numbers
That’s a really long phone number. Crazy that it has 7 repeating numbers in succession.
Considering suicide? Type in these 18 numbers without mistakes while you think about it…
0118 999 88199 9119 725 3
That’s easy to remember!
It’s too late for me. My coworker pull requested before I could and now I think I’m going to commit merge conflict.
Just base your stuff on their stuff and hassle everyone to merge that other PR.
That’s not a mistake git can do that to people. Especially those who have never used git via command line.
Yeah, imagine you accidently commit over weeks of work, or hell, if it’s the main branch, and you deleted the other origin branch prior to merging, it could be a lot more than a few weeks worth of work. The revert to a previous commit… shutters.
I don’t know if you’re joking, but in case you’re not:
git reflogandgit reset --hard HEAD@{n}is your friend. You can undo almost anything. Deleted commits and branches aren’t really deleted. Remotely deleted branches can be pushed again.Except for an (accidental)
git restore/git reset. Those are permanent and can’t be undone.Even
git resetcan be undone by a lot of editors. At least IntelliJ has an excellent local history that works much like git. Sure it’s a pain if you touched several files but that’ll teach you to atomify your commits.Edit: Plus,
git resetitself does nothing of note really, but I’m sure you know. Needs the—hardflag to do any meaningful damage.
Its even scarier when master branch is prod
Don’t tell me ghost stories right now, it’s almost my bedtime.
@@ -1 +0,0 @@
-my existence
