this post was submitted on 17 Feb 2026
253 points (98.8% liked)

Programmer Humor

29805 readers
1004 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 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
253
Morge continvoucly (discuss.tchncs.de)
submitted 21 hours ago by state_electrician@discuss.tchncs.de to c/programmer_humor@programming.dev
46 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

you are viewing a single comment's thread
view the rest of the comments
[–] chunkystyles@sopuli.xyz 4 points 12 hours ago

I pushed my team to use trunk based development. We did cherry-picks from trunk to release branches for a couple years with no issues. Since then, I've written a GitHub action that automates the cherry-picks based on tickets in the commit messages.

But even before the automation, it drastically improved our dev processes.

We weren't on Git Flow exactly, but it was a bastardized version of it.

Having used TBD successfully for like 5-6 years now. I can't imagine using Git Flow.