This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@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.
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@dazfuller@mstdn.social "On a scale of zero to Tim"
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@dazfuller it gets better the more you try to understand the graph
-
@dazfuller That's Tim travelling back in time to fix his morge strategy.
@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
-
@itgrrl @dazfuller cofeve!
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@dazfuller It's old-fashioned but I'm against morging.
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
-
@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
@JennyFluff
The things Tim has seen.
@dazfuller -
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
They should try SourceMorge
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@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
a deadly or grossly negligent outcome upon mergeTo use it in a sentence:
*After the changes were shipped, they published just before failover and morged the live which resulted in the outage for the on call.* -
@dpnash oh shit, sorry Tim! You should have words with Timn tomorrow before he starts working from the initial commit
@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 morgesthat need to occur in the past. I hope that clears things up. -
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@dazfuller
That reminds me, what happened to the original Learn Microsoft documentation??? Was it archived at least?? -
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@dazfuller it's morgin' time
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
“But surely, Eddington, your theory implies an ‘arrow of Tim’ that runs counter to your expectations?”
“Don’t call me Shirley.”
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@dazfuller Everyone involved in this should be in prison. I can't believe THIS is why 32 gigs of RAM costs $500.
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@dazfuller
Tim keeps on slipping, slipping, slipping
Into the future -
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@dazfuller The best part was when Tinm said "IT'S MORGIN' TIME!" and then morged continvoucly all over the repository.
-
@itgrrl @dazfuller the only way to morg
-
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
@benrfairless I’m not going to disagree with my latest find @MattHatton : AI is mad cow disease for computers
️
