19
submitted 1 month ago* (last edited 1 month ago) by OliMoli2137@piefed.social to c/software_gore@programming.dev

github at its finest ^

top 5 comments
sorted by: hot top new old
[-] SirHaxalot@nord.pub 9 points 1 month ago

I don’t get how this is software gore? It’s a merge conflict, a kind of common thing in Git.

[-] smaximov@lemmy.world 6 points 1 month ago

"Changes can be cleanly merged" — it says at the same time.

[-] eager_eagle@lemmy.world 6 points 1 month ago

yeah, I've seen this bs multiple times now. Also tired of github rewriting commits and changing hashes when they can just be fastforwrded onto the merging branch. So for a while now I almost exclusively use the command line to merge.

[-] Ephera@lemmy.ml 1 points 1 month ago

Would really prefer they didn't have these buttons, if they're not implemented correctly. Similarly, there's a setting to uses rebases throughout the UI instead of merge commits. And it works everywhere, except when updating PR branch. It has a button "Update branch", which does the wrong thing, with a dropdown where you can select "Rebase branch" instead. So many times, I've had to tell people to not click that button...

[-] ImgurRefugee114@reddthat.com 5 points 1 month ago
this post was submitted on 25 Sep 2026
19 points (85.2% liked)

Software Gore

1341 readers
1 users here now

A community for posting software malfunctions

Deliberately bad software or bad design is not software gore, it must be something unintentional

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient and shear it



founded 3 years ago
MODERATORS