this post was submitted on 17 Feb 2026
0 points (NaN% liked)

Programmer Humor

34003 readers
74 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
anzo@programming.dev
Feyter@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
0
Morge continvoucly (discuss.tchncs.de)
submitted 8 months ago by state_electrician@discuss.tchncs.de to c/programmer_humor@programming.dev
3 comments fedilink hide all child comments
 

This was from official Microslop documentation https://web.archive.org/web/20260216165612/https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow

top 3 comments
sorted by: hot top controversial new old
[–] anhkagi@jlai.lu 1 points 8 months ago

Even without considering the typos, the diagram is incomprehensible with all these arrows pointing in every direction and textboxes placed randomly. I had to look at the original to understand it.

[–] pivot_root@lemmy.world 0 points 8 months ago (1 children)

Well, that explains a lot about the product quality. Their entire development workflow is a complete fucking mess.

  • Long-lived feature branches.
  • Creating merge commits to main just for the sole purpose of tagging them as releases while also maintaining separate release branches.
  • Force-pushing tags to incorporate post-release hotfixes instead of releasing minor patch updates.
  • Taking bugfixes from releases and merging them back into the development branch (have they not heard of cherry-pick?)
  • Always using merges even when a rebase would be easier to follow and keep the history more straightforward.
[–] figjam@midwest.social 1 points 8 months ago

Whats a merge? We be morging up here