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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller not Tim but Timmmmmmm
-
@dazfuller I will now pronounce "merged" as "morged" until my dying breath
@LibertyForward1 @dazfuller To morg is to merge code that can’t compile and uses letters that don’t exist in human language into the release.
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller in the top left there it doesnt even say time, its “timn”(???) the last latter of that isnt a real letter. i assume that means time but backwards bc the arrow is backwards
-
@jackeric basically the same picture right
-
@itgrrl @dazfuller
You are not Morg! You are not I-Morg! -
@JennyFluff
The things Tim has seen.
@dazfuller@ohmrun @JennyFluff don’t talk to Tim about the old Morging, he was there (or will be eventually) at the beginning
-
@jackeric @dazfuller so they also stole this essentially then?
-
@Nymnympseudonymm this is great
Now excuse me while I cleanse it with fire
-
That was the beginning of the great Tim wars, which continue to this day
-
@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 mergeUse 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.*@aleciabatson @munin if this isn’t standard terminology by middle of the year then I’ll be devastated
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller no wonder they are barely able to make working software anymore.
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller There is a theory that all merges and commits are just a single Tim moving backwards and forward in the git history...
-
@dazfuller WHAT IS THAT VERTICAL ARROW? WHO IS TINM? NM ISN'T EVEN A DEFINED LIGATURE
(as far as I can tell)
(but it does exist maybe? maybe as a phonetic marker:
https://commons.wikimedia.org/wiki/File:Nm_ligature.svg
)
I am so confused
@moira Maybe Tinm is real, they’re going back to save us
-
@dazfuller this is embarrassing, I will bitch internally
@mapache just please don’t throw Tinm under the bus, it’ll disrupt the space time continuum
-
@jackeric @dazfuller so they also stole this essentially then?
@thibaultmol @jackeric stole "and improved with AI"
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller Tim with and extra ∩
-
@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 -
@dazfuller the course page has been updated; I don't see this image in there.
-
@dazfuller and stolen from sources like https://nvie.com/posts/a-successful-git-branching-model/
@thezeronine@mastodon.pnpde.social @dazfuller@mstdn.social wow that is way more clearly stolen then I thought, damn
-
@itgrrl @dazfuller this almost made me choke on my covfefe thanks
️
