786
top 50 comments
sorted by: hot top new old
[-] jaschop@awful.systems 34 points 10 months ago

It's never too late to git merge --abort!

[-] TheFriendlyDickhead@feddit.org 26 points 10 months ago

But abortion is murder?!?!?!?!?

[-] gravitas_deficiency@sh.itjust.works 10 points 10 months ago

🎶 every branch is sacred 🎶

[-] SkunkWorkz@lemmy.world 30 points 10 months ago

“Proper way to commit after merge conflict” sounds like a robot trying to save a relationship after a bad sex experience

[-] cupcakezealot@piefed.blahaj.zone 26 points 10 months ago
git reset --hard <commit-hash>  
git push -f origin main  

i didn't see anything, officer

[-] martinb@lemmy.sdf.org 20 points 10 months ago

You should be forcibly kept away from production systems...

[-] henfredemars@infosec.pub 12 points 10 months ago

We had an intern do this once. We changed our server config to make sure it wouldn’t accept such operations.

load more comments (2 replies)
[-] joyjoy@lemmy.zip 3 points 10 months ago

Never use --force. Always use --force-with-lease.

[-] enbiousenvy@lemmy.blahaj.zone 2 points 10 months ago

I've mistyped that a couple of times to be --force-with-leash

[-] joyjoy@lemmy.zip 4 points 10 months ago

git push origin master --force-with-leash

Don't do that to your master.

load more comments (2 replies)
[-] kubica@fedia.io 17 points 10 months ago
[-] errer@lemmy.world 9 points 10 months ago* (last edited 10 months ago)

git never --gonna-give-you-up

load more comments (1 replies)
[-] Kolanaki@pawb.social 13 points 10 months ago

calls suicide hotline to ask for tech support

[-] CanadaPlus@lemmy.sdf.org 2 points 10 months ago* (last edited 10 months ago)

Don't hold your breath, they're pretty mid at their actual job.

[-] magic_lobster_party@fedia.io 10 points 10 months ago

Keep your commits small. Merge often. That will reduce the likelihood of terrible merge conflicts.

If you’re not sharing your work with your team mates for a long time, then you’re setting yourself up for trouble.

[-] SpaceCowboy@lemmy.ca 4 points 10 months ago

Also rebase is usually better than merge.

[-] Anafabula@discuss.tchncs.de 10 points 10 months ago

Jujutsu (which is compatible with git) has a nice conflict resolution flow that doesn't break you workflow.

Conflicts are encoded into the commits, so that there is never a weird in between state that you have to deal with immediately before being able to do anything else.
Then you can use Jujutsu's easier history manipulation to resolve the conflict in the conflicted commits.

https://steveklabnik.github.io/jujutsu-tutorial/branching-merging-and-conflicts/conflicts.html

And you could always jj undo if you did something you didn't want to.

[-] peoplebeproblems@midwest.social 9 points 10 months ago

Been there too OP. Not a good place.

It's usually easier to find another job, it will reset your mind, and fear won't be driving you.

Or you could just commit what you have, comment "YOLO" and auto resolve conflicts and push.

[-] tomjuggler@lemmy.world 2 points 10 months ago

I prefer to just delete the whole .git and start a new repository with the new version. We are pivoting the project, new name and new repo

[-] dream_weasel@sh.itjust.works 7 points 10 months ago

No merges allowed. Rebase only.

load more comments (1 replies)
[-] schnurrito@discuss.tchncs.de 7 points 10 months ago

I remember when similar screenshots circulated for how to tell if i am running jdk or jre, which is even more surprising.

[-] echodot@feddit.uk 5 points 10 months ago* (last edited 10 months ago)

See I wasn't really going to kill myself today, but the thought of dialing that long ass number is just to much.

[-] GreenKnight23@lemmy.world 4 points 10 months ago

in life you commit to many things. you commit to yourself, to your partner, to happiness, to legacy.

when we die, is that like a push to origin?

when we die, do our commits all go to the big repo in the sky?

is god the maintainer? when you pray is that like a bug report?

so many questions...

load more comments (1 replies)
[-] Antagnostic@lemmy.world 3 points 10 months ago* (last edited 10 months ago)

If you git help, you could hash things out, rebase your commitments, and push forward to a better life. Then again I could just be cherry picking things.

[-] dubyakay@lemmy.ca 3 points 10 months ago* (last edited 10 months ago)

Google gives you results based on your prior search history.

[-] aliser@lemmy.world 3 points 10 months ago

git is like a minefield. stray away even a little bit from standard path and you are done for. I had git multiple times throw some obscure errors at me when trying some commands and then trying to undo/recover. how's "undo" is not a git command I don't understand.

load more comments (1 replies)
[-] invertedspear@lemmy.zip 3 points 10 months ago* (last edited 10 months ago)
load more comments (1 replies)
load more comments
view more: next ›
this post was submitted on 11 Oct 2025
786 points (99.2% liked)

Programmer Humor

33096 readers
487 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 3 years ago
MODERATORS