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
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.
I love git flow but the GitHub tooling is bad. It forces you into GitHubflow which is very confusing for those building from source
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
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
Thank god we are going opposite to the Tim direction
Tirm
Yeah, Fuck Tim
The 15yo “source” for the sloppy plagiarism: https://nvie.com/posts/a-successful-git-branching-model/
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.
Tim is going backwards in time
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.
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.
Major featue UwU
deleted by creator
