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

[bernardsheppard@mastodon.au]

@dazfuller this can all be fixed by cherry pitting morges and squash morging, or if you don't like squash, pumpkin morgues.

[jackeric@beige.party]

@dazfuller this... this... this is a pastiche of a beautiful diagram of a Git branching model published in the late 2000s and later disowned by its authors as obsolete in an era of continuous delivery

[jackeric@beige.party]

@dazfuller Look!
https://nvie.com/posts/a-successful-git-branching-model/

[tezoatlipoca@mas.to]

@dazfuller I'm showing this to my boss tomorrow as exhibit no one as why ai cannot document software properly or replace us technical writers.

[jennyfluff@chitter.xyz]

@dazfuller it gets better the more you try to understand the graph

[jennyfluff@chitter.xyz]

@ohmrun @dazfuller and don't forget to completely ignore your release branch after 1.0, from now on development gets morged to master. In the past. Because Tim flows backwards

[nymnympseudonymm@mstdn.science]

@itgrrl @dazfuller cofeve!

[gustodon@mas.to]

@dazfuller It's old-fashioned but I'm against morging.

[nymnympseudonymm@mstdn.science]

@dazfuller
Y'all will love this I bet

/ducks

Entire · A new developer platform is coming

We are going beyond repositories, building a developer platform where agents and humans can collaborate, interact, and grow. The birth of a new galaxy in this universe draws near.

(entire.io)

[ohmrun@indieweb.social]

@JennyFluff
The things Tim has seen.
@dazfuller

[gustodon@mas.to]

@itgrrl

[float13@masto.hackers.town]

@dazfuller

They should try SourceMorge

[aleciabatson@mastodon.social]

@dazfuller as I shared with @munin

I love the English #language! Ever-evolving with new verbs and terms. (Now, with #slopification!) In this instance, I’ll gladly employ “to morg” because, based purely on context, it seems to be defined as

morg / mɔrg /
verb
to cause a deadly or grossly negligent outcome upon merge

Use in a sentence
*After the changes were shipped, they published just before failover and morged the live, resulting in an outage for the on call.*

[jbaggs@infosec.exchange]

@dazfuller @dpnash Tinm or timn (I'm still not sure myself.) Is not bound by the law of entropy, and therefore has been made responsible for making any git morges that need to occur in the past. I hope that clears things up.

[skrlet13@sc.skrlet13.xyz]

@dazfuller
That reminds me, what happened to the original Learn Microsoft documentation??? Was it archived at least??

[bstacey@icosahedron.website]

@dazfuller it's morgin' time

[sellout@mastodon.social]

@dazfuller

“But surely, Eddington, your theory implies an ‘arrow of Tim’ that runs counter to your expectations?”

“Don’t call me Shirley.”

[theorangetheme@en.osm.town]

@dazfuller Everyone involved in this should be in prison. I can't believe THIS is why 32 gigs of RAM costs $500.

[brouhaha@mastodon.social]

@dazfuller
Tim keeps on slipping, slipping, slipping
Into the future

[damonwakes@mastodon.sdf.org]

@dazfuller The best part was when Tinm said "IT'S MORGIN' TIME!" and then morged continvoucly all over the repository.