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
git log --pretty=fucked-up
this post was submitted on 17 Feb 2026
313 points (98.5% liked)
Programmer Humor
29879 readers
193 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 2 years ago
MODERATORS
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.
Remember when morgius morged all over those guys?
Thank god we are going opposite to the Tim direction
Tirm
The 15yo "source" for the sloppy plagiarism: https://nvie.com/posts/a-successful-git-branching-model/
You gotto love how the AI took the axis on the left, was confused enough from its tail that it thought it must be pointing in the opposite direction to development flow and then went "welp if it is going in the other direction, the label "time" must be a typo. Ima make it Tim the time traveller instead". Ofcourse none of it happened like this, but I would like to imagine that it did.
holy fuck, it's basically the time I followed a tutorial for generating "a witch" for AI art, and ended up with a horribly mangled MTG card
It's still not a bad system if you have to support and provide bugfixes for multiple versions of software. However, if you only support the latest version and only create bug fixes and features based on the latest release or main branch, then git-flow is way overkill.
It's an atrocious, pointlessly complicated system resulting in convoluted project histories prone to confusion. Trunk-based development with sensible tags of releases & hotfixes achieves the same thing without the junk complexity. Git flow isn't overkill, it's just ill-conceived.
This is a joke, right? OneFlow isn’t trunk-based development and is actually gitflow with different steps. I have yet to see any org actually use trunk-based development mostly because I’ve not seen cherry-picking from the trunk adopted at any large scale.
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.
I dream of getting back to TBD.
What is large scale to you? We have 100-200 developers doing something fairly close to trunk based development. Including cherry picking from trunk when possible (not always practical for sufficiently old release branches)
git Morge perfec t flow for put code in to re\lease! inside very Bronch and Featue code morge continvoucly put code in Git Morge. no problems ever in gitt morge because good Flow and Barnch for code morge conflict of big code releas. Agit Morge yes a place for a code put code in git morge can trust Tirm for giveing good morge to code. friend morge
Wish I hadn't read this while drinking my tea.
I know this is a meme but what is it from
I based it on the pelcan Mouth perfec t size for put baby in pasta
Thats the one, thank you!
No worries! pelcan Mouth perfec t meme for make snowclone of.
:3
From 1985 when plutonium was pure and future considered 2015.
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.
Whats a merge? We be morging up here
It's morgin time
I feel it's a bad sign that I'm saving this meme for use at work
Everybody has a testing environment. Some people are lucky enough enough to have a totally separate environment to run production in.
And Microsoft stole it from a different developer, who posted it back in 2011... and then ran it through Copilot without even checking it thoroughly before adding it to training documentation.
Makes me wonder how much of the training documentation is AI generated...
Considering their recent output?
Probably all the latest pubs.
I love git flow but the GitHub tooling is bad. It forces you into GitHubflow which is very confusing for those building from source
I peed myself
Stat of release
The image genAI is also from Boston.
I just made master become what gets pushed to the actual website so I do have to take it into consideration
Tim is going backwards in time
Tiꦟ
Tiꦟ doesn't just morge continvoucly, he goes back in time and fixes his mistakes before they ever happen.
Major featue UwU