Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. 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.

Scheduled Pinned Locked Moved Uncategorized
aislopmicroslop
142 Posts 91 Posters 2 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • dazfuller@mstdn.socialD dazfuller@mstdn.social

    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"

    Link Preview Image
    Components of the GitHub flow - Training

    Learn to use the components of the GitHub flow

    favicon

    (learn.microsoft.com)

    tmr232@mastodon.socialT This user is from outside of this forum
    tmr232@mastodon.socialT This user is from outside of this forum
    tmr232@mastodon.social
    wrote last edited by
    #23

    @dazfuller this is painful...

    dazfuller@mstdn.socialD 1 Reply Last reply
    0
    • dpnash@c.imD dpnash@c.im

      @dazfuller > don't know why Tim is working in the opposite direction

      It's not "Tim", it's "Timn" or "Tinm". No wonder everyone is confused. "Timn" is the one who's working backwards. The *real* Tim, who is working forwards and understands the details of `git morge --continvoucly`, already left for the day. The team will have to settle for a regular old non-continvoucal morge until Tim comes back and they can ask him for help.

      dazfuller@mstdn.socialD This user is from outside of this forum
      dazfuller@mstdn.socialD This user is from outside of this forum
      dazfuller@mstdn.social
      wrote last edited by
      #24

      @dpnash oh shit, sorry Tim! You should have words with Timn tomorrow before he starts working from the initial commit

      jbaggs@infosec.exchangeJ 1 Reply Last reply
      0
      • tmr232@mastodon.socialT tmr232@mastodon.social

        @dazfuller this is painful...

        dazfuller@mstdn.socialD This user is from outside of this forum
        dazfuller@mstdn.socialD This user is from outside of this forum
        dazfuller@mstdn.social
        wrote last edited by
        #25

        @tmr232 this is the future. It’s because we don’t understand how to morge code that software development will be dead in 6-12 months.

        Just don’t ask which 6-12 months

        1 Reply Last reply
        0
        • dazfuller@mstdn.socialD dazfuller@mstdn.social

          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"

          Link Preview Image
          Components of the GitHub flow - Training

          Learn to use the components of the GitHub flow

          favicon

          (learn.microsoft.com)

          johnofrobotz@mastodon.girolab.fooJ This user is from outside of this forum
          johnofrobotz@mastodon.girolab.fooJ This user is from outside of this forum
          johnofrobotz@mastodon.girolab.foo
          wrote last edited by
          #26

          @dazfuller Honestly, I think Tinn took one look at this and is headed out the door.

          1 Reply Last reply
          0
          • dazfuller@mstdn.socialD dazfuller@mstdn.social

            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"

            Link Preview Image
            Components of the GitHub flow - Training

            Learn to use the components of the GitHub flow

            favicon

            (learn.microsoft.com)

            itgrrl@infosec.exchangeI This user is from outside of this forum
            itgrrl@infosec.exchangeI This user is from outside of this forum
            itgrrl@infosec.exchange
            wrote last edited by
            #27

            @dazfuller 💁‍♀️

            Link Preview Image
            nymnympseudonymm@mstdn.scienceN gustodon@mas.toG dancast@wandering.shopD stumpythemutt@social.linux.pizzaS brouhaha@mastodon.socialB 7 Replies Last reply
            0
            • dazfuller@mstdn.socialD dazfuller@mstdn.social

              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"

              Link Preview Image
              Components of the GitHub flow - Training

              Learn to use the components of the GitHub flow

              favicon

              (learn.microsoft.com)

              sykora@tech.lgbtS This user is from outside of this forum
              sykora@tech.lgbtS This user is from outside of this forum
              sykora@tech.lgbt
              wrote last edited by
              #28

              @dazfuller My favorite part is when Tim said it's morgin time and morged all over everyone

              1 Reply Last reply
              0
              • dazfuller@mstdn.socialD dazfuller@mstdn.social

                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"

                Link Preview Image
                Components of the GitHub flow - Training

                Learn to use the components of the GitHub flow

                favicon

                (learn.microsoft.com)

                bernardsheppard@mastodon.auB This user is from outside of this forum
                bernardsheppard@mastodon.auB This user is from outside of this forum
                bernardsheppard@mastodon.au
                wrote last edited by
                #29

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

                1 Reply Last reply
                0
                • dazfuller@mstdn.socialD dazfuller@mstdn.social

                  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"

                  Link Preview Image
                  Components of the GitHub flow - Training

                  Learn to use the components of the GitHub flow

                  favicon

                  (learn.microsoft.com)

                  jackeric@beige.partyJ This user is from outside of this forum
                  jackeric@beige.partyJ This user is from outside of this forum
                  jackeric@beige.party
                  wrote last edited by
                  #30

                  @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.partyJ 1 Reply Last reply
                  0
                  • jackeric@beige.partyJ 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.partyJ This user is from outside of this forum
                    jackeric@beige.partyJ This user is from outside of this forum
                    jackeric@beige.party
                    wrote last edited by
                    #31

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

                    dazfuller@mstdn.socialD thibaultmol@en.osm.townT 2 Replies Last reply
                    0
                    • dazfuller@mstdn.socialD dazfuller@mstdn.social

                      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"

                      Link Preview Image
                      Components of the GitHub flow - Training

                      Learn to use the components of the GitHub flow

                      favicon

                      (learn.microsoft.com)

                      tezoatlipoca@mas.toT This user is from outside of this forum
                      tezoatlipoca@mas.toT This user is from outside of this forum
                      tezoatlipoca@mas.to
                      wrote last edited by
                      #32

                      @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.

                      1 Reply Last reply
                      0
                      • dazfuller@mstdn.socialD dazfuller@mstdn.social

                        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"

                        Link Preview Image
                        Components of the GitHub flow - Training

                        Learn to use the components of the GitHub flow

                        favicon

                        (learn.microsoft.com)

                        jennyfluff@chitter.xyzJ This user is from outside of this forum
                        jennyfluff@chitter.xyzJ This user is from outside of this forum
                        jennyfluff@chitter.xyz
                        wrote last edited by
                        #33

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

                        felipe@social.treehouse.systemsF 1 Reply Last reply
                        0
                        • ohmrun@indieweb.socialO ohmrun@indieweb.social

                          @dazfuller That's Tim travelling back in time to fix his morge strategy.

                          jennyfluff@chitter.xyzJ This user is from outside of this forum
                          jennyfluff@chitter.xyzJ This user is from outside of this forum
                          jennyfluff@chitter.xyz
                          wrote last edited by
                          #34

                          @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

                          ohmrun@indieweb.socialO 1 Reply Last reply
                          0
                          • itgrrl@infosec.exchangeI itgrrl@infosec.exchange

                            @dazfuller 💁‍♀️

                            Link Preview Image
                            nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                            nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                            nymnympseudonymm@mstdn.science
                            wrote last edited by
                            #35

                            @itgrrl @dazfuller cofeve!

                            1 Reply Last reply
                            0
                            • dazfuller@mstdn.socialD dazfuller@mstdn.social

                              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"

                              Link Preview Image
                              Components of the GitHub flow - Training

                              Learn to use the components of the GitHub flow

                              favicon

                              (learn.microsoft.com)

                              gustodon@mas.toG This user is from outside of this forum
                              gustodon@mas.toG This user is from outside of this forum
                              gustodon@mas.to
                              wrote last edited by
                              #36

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

                              1 Reply Last reply
                              0
                              • dazfuller@mstdn.socialD dazfuller@mstdn.social

                                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"

                                Link Preview Image
                                Components of the GitHub flow - Training

                                Learn to use the components of the GitHub flow

                                favicon

                                (learn.microsoft.com)

                                nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                                nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                                nymnympseudonymm@mstdn.science
                                wrote last edited by
                                #37

                                @dazfuller
                                Y'all will love this I bet

                                /ducks

                                Link Preview Image
                                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.

                                favicon

                                (entire.io)

                                dazfuller@mstdn.socialD 1 Reply Last reply
                                0
                                • jennyfluff@chitter.xyzJ 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

                                  ohmrun@indieweb.socialO This user is from outside of this forum
                                  ohmrun@indieweb.socialO This user is from outside of this forum
                                  ohmrun@indieweb.social
                                  wrote last edited by
                                  #38

                                  @JennyFluff
                                  The things Tim has seen.
                                  @dazfuller

                                  dazfuller@mstdn.socialD 1 Reply Last reply
                                  0
                                  • itgrrl@infosec.exchangeI itgrrl@infosec.exchange

                                    @dazfuller 💁‍♀️

                                    Link Preview Image
                                    gustodon@mas.toG This user is from outside of this forum
                                    gustodon@mas.toG This user is from outside of this forum
                                    gustodon@mas.to
                                    wrote last edited by
                                    #39

                                    @itgrrl 😂

                                    1 Reply Last reply
                                    0
                                    • dazfuller@mstdn.socialD dazfuller@mstdn.social

                                      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"

                                      Link Preview Image
                                      Components of the GitHub flow - Training

                                      Learn to use the components of the GitHub flow

                                      favicon

                                      (learn.microsoft.com)

                                      float13@masto.hackers.townF This user is from outside of this forum
                                      float13@masto.hackers.townF This user is from outside of this forum
                                      float13@masto.hackers.town
                                      wrote last edited by
                                      #40

                                      @dazfuller

                                      They should try SourceMorge

                                      1 Reply Last reply
                                      0
                                      • dazfuller@mstdn.socialD dazfuller@mstdn.social

                                        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"

                                        Link Preview Image
                                        Components of the GitHub flow - Training

                                        Learn to use the components of the GitHub flow

                                        favicon

                                        (learn.microsoft.com)

                                        aleciabatson@mastodon.socialA This user is from outside of this forum
                                        aleciabatson@mastodon.socialA This user is from outside of this forum
                                        aleciabatson@mastodon.social
                                        wrote last edited by
                                        #41

                                        @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.*

                                        dazfuller@mstdn.socialD W ghostonthehalfshell@masto.aiG 3 Replies Last reply
                                        0
                                        • dazfuller@mstdn.socialD dazfuller@mstdn.social

                                          @dpnash oh shit, sorry Tim! You should have words with Timn tomorrow before he starts working from the initial commit

                                          jbaggs@infosec.exchangeJ This user is from outside of this forum
                                          jbaggs@infosec.exchangeJ This user is from outside of this forum
                                          jbaggs@infosec.exchange
                                          wrote last edited by
                                          #42

                                          @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.

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups