This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

[jedbrown@hachyderm.io]

@dallo
It was a nice diagram, but poor workflow even in 2010. The gitworkflows(7) man page was first written in 2008 and had clear rationale. I made this figure in that era to show the parallelism exposed by the workflow. As CI has become more robust, many projects moved away from having a 'next' as a throw-away integration branch, but it is a useful strategy especially if you want user feedback on experimental features before you commit to including them by merging to 'main' (formerly 'master').
https://git-scm.com/docs/gitworkflows
@dazfuller

[dallo@pouet.chapril.org]

@jedbrown @dazfuller In 2010, we were on svn, mercurial and, in my circle, TFS. Git with the nvie workflow was another level.

[volpeon@icy.wyvern.rip]

@dazfuller Looks like Microsoft changed the image in the last 15 min or so. ​​ It was still there when I opened the link earlier.

[dazfuller@mstdn.social]

@volpeon in both happy and disappointed. But at least it will always be in the Internet Archive

[mdione@en.osm.town]

@dallo @jedbrown @dazfuller I was using nvie in 2007-08 in a startup. Later, CVS (!!!) in 2012-15 in a big company

[srazkvt@tech.lgbt]

@dazfuller the more i look at it the worst it gets

[dazfuller@mstdn.social]

@mdione @dallo @jedbrown I was trying to think what I was using around 2010. But think it was a mix of svn and TFS. Though there might have been a couple of projects still on cvs. That was for a Fortune 500 company

[bencomp@code4lib.social]

@dazfuller the course page has been updated; I don't see this image in there.

[addison@nothing-ever.works]

@thezeronine@mastodon.pnpde.social @dazfuller@mstdn.social wow that is way more clearly stolen then I thought, damn

[mdione@en.osm.town]

@dazfuller @dallo @jedbrown I checked the dates in my CV

[vladimir_lu@hachyderm.io]

@itgrrl @dazfuller this almost made me choke on my covfefe thanks

[0@corteximplant.com]

@dazfuller -squints- I think his name might be Tirm

[tessarakt@mastodon.social]

@dazfuller But you know what they mean if you already know what they teach on that page! So why be so picky?

[jigmedatse@social.openpsychology.net]

@jedbrown@hachyderm.io @dazfuller@mstdn.social Thank you... I knew it was incredibly familiar, but the familiar version, felt like it was not too bad (hey it may not be perfect, but it's certainly not confusing like, "hey what why huh..."). Much appreciated.

[geoffl@mastodon.me.uk]

@dazfuller @moira

Maybe they're thinking themselves onto existence.
https://www.peopleofar.com/2013/07/02/worlds-shortest-poem/

[klefstadmyr@social.vivaldi.net]

@be0ba @dazfuller It will happen early in last month. Aren't you going to have paid attention?

[jackeric@beige.party]

@thibaultmol @dazfuller That diagram, that branching model, fascinated me back then - I only learned of git c.2010 and have always loved using it.

[klefstadmyr@social.vivaldi.net]

@itgrrl @dazfuller Tim says it best.

[phils@social.lol]

@dazfuller I used to be an author of Learn modules. It was a few years ago, but I think they were moving heavily into AI produced documentation. I think this proves it. So sad.

[ipsavitsky@mastodon.social]

@dazfuller check out my new git flow diagram!