Post

RIP "continvoucly morged". Looks like they replaced it with a new diagram. Honestly I’m still a bit suspicious of this one. There are some inconsistent design choices that make me think this could’ve been generated as well. Though maybe it was a human in a hurry. 😅

David Bushell 👻@dbushell.com

have a chuckle at this "Git flow" slop might explain GitHub's recent outages learn.microsoft.com/en-us/traini...

learn.microsoft.comComponents of the GitHub flow - TrainingLearn to use the components of the GitHub flow

patak

@patak.cat

17 Feb

oh, no. the curves aren't consistent at all. I don't think a designer would have made these choices. @scott.hanselman.com do you know if the new diagram was fully crafted by a professional human?

Scott Hanselman 🌮

@scott.hanselman.com

17 Feb

Yes it was a human but they were rushed for sure over the weekend to get the bad content off. They are gonna do a full pass over the whole thing this week

Peter Magenheimer

@peterjmags.com

18 Feb

I don't mean to pile on here, but it looks like the updated version of the diagram was heavily cribbed (if not outright ripped off) from Atlassian's docs without attribution

Peter Magenheimer

@peterjmags.com

Oops added the link to the alt text but I meant to include it in the post body too: www.atlassian.com/git/tutorial...

atlassian.comGitflow Workflow | Atlassian Git TutorialA deep dive into the Gitflow Workflow. Learn if this Git workflow is right for you and your team with this comprehensive tutorial.

18/2/26, 1:09 pm0 reposts1 like

Peter Magenheimer

@peterjmags.com

18 Feb

Incidentally, the Atlassian doc does a decent job of giving historical context. Given that the original git flow blog post is nearly 16 years old now, I feel like the MS doc should do the same (and/or as @nvie.com suggested, link back to his own blog post, which includes a helpful update from 2020)