this post was submitted on 06 Jul 2023

187 points (98.4% liked)

Programmer Humor

19555 readers

1203 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

187

GitHub achievements that did not make the cut (github.com)

submitted 1 year ago by ono@lemmy.ca to c/programmer_humor@programming.dev

10 comments fedilink hide all child comments

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

[–] CoderKat@lemm.ee 2 points 1 year ago (1 children)

Oof, I think I'd have a couple of these.

I also once broke a completely different repo with a history rewrite and force push once. Turned out some repo had some odd form of reference to one of mine that depended on a specific commit hash, so the commit hashes changing (even though the files they cared about didn't change) broke them. Oops. I didn't even know anyone else was using it and thought it was safe!

[–] ono@lemmy.ca 2 points 1 year ago

Sometimes that's done after security reviewing a dependency, to make sure an alarm is raised if anything at all changes.