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)

    qccechris@mastodon.socialQ This user is from outside of this forum
    qccechris@mastodon.socialQ This user is from outside of this forum
    qccechris@mastodon.social
    wrote last edited by
    #104

    @dazfuller Tim with and extra ∩ 😆

    1 Reply Last reply
    0
    • jedbrown@hachyderm.ioJ jedbrown@hachyderm.io

      @dazfuller
      And this is the figure from the 2010 blog post that their machine plagiarized (badly).
      https://nvie.com/posts/a-successful-git-branching-model/

      Link Preview Image
      dallo@pouet.chapril.orgD This user is from outside of this forum
      dallo@pouet.chapril.orgD This user is from outside of this forum
      dallo@pouet.chapril.org
      wrote last edited by
      #105

      @jedbrown @dazfuller and it is not even good nowadays. Was by 2010 standard.

      jedbrown@hachyderm.ioJ 1 Reply Last reply
      0
      • jedbrown@hachyderm.ioJ jedbrown@hachyderm.io

        @dazfuller
        And this is the figure from the 2010 blog post that their machine plagiarized (badly).
        https://nvie.com/posts/a-successful-git-branching-model/

        Link Preview Image
        doragasu@mastodon.sdf.orgD This user is from outside of this forum
        doragasu@mastodon.sdf.orgD This user is from outside of this forum
        doragasu@mastodon.sdf.org
        wrote last edited by
        #106

        @jedbrown @dazfuller Indeed the slop machine can only make what already exists but worse.

        1 Reply Last reply
        0
        • jennyfluff@chitter.xyzJ jennyfluff@chitter.xyz

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

          felipe@social.treehouse.systemsF This user is from outside of this forum
          felipe@social.treehouse.systemsF This user is from outside of this forum
          felipe@social.treehouse.systems
          wrote last edited by
          #107

          @dazfuller @JennyFluff the funniest thing to me is how simple the original is to understand

          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)

            lettosprey@tech.lgbtL This user is from outside of this forum
            lettosprey@tech.lgbtL This user is from outside of this forum
            lettosprey@tech.lgbt
            wrote last edited by
            #108

            @dazfuller People: "GIt is too complicated", Microsoft: "Not anywhere near enough!"

            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)

              avuko@infosec.exchangeA This user is from outside of this forum
              avuko@infosec.exchangeA This user is from outside of this forum
              avuko@infosec.exchange
              wrote last edited by
              #109

              @dazfuller doesn’t the existence of Tim n suggests a range of integer Tims working on this?

              1 Reply Last reply
              0
              • dallo@pouet.chapril.orgD dallo@pouet.chapril.org

                @jedbrown @dazfuller and it is not even good nowadays. Was by 2010 standard.

                jedbrown@hachyderm.ioJ This user is from outside of this forum
                jedbrown@hachyderm.ioJ This user is from outside of this forum
                jedbrown@hachyderm.io
                wrote last edited by
                #110

                @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

                Link Preview Image
                dallo@pouet.chapril.orgD 1 Reply Last reply
                0
                • jedbrown@hachyderm.ioJ 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

                  Link Preview Image
                  dallo@pouet.chapril.orgD This user is from outside of this forum
                  dallo@pouet.chapril.orgD This user is from outside of this forum
                  dallo@pouet.chapril.org
                  wrote last edited by
                  #111

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

                  mdione@en.osm.townM 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)

                    volpeon@icy.wyvern.ripV This user is from outside of this forum
                    volpeon@icy.wyvern.ripV This user is from outside of this forum
                    volpeon@icy.wyvern.rip
                    wrote last edited by
                    #112

                    @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.socialD 1 Reply Last reply
                    0
                    • volpeon@icy.wyvern.ripV 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.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
                      #113

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

                      1 Reply Last reply
                      0
                      • dallo@pouet.chapril.orgD 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.

                        mdione@en.osm.townM This user is from outside of this forum
                        mdione@en.osm.townM This user is from outside of this forum
                        mdione@en.osm.town
                        wrote last edited by
                        #114

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

                        dazfuller@mstdn.socialD 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)

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

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

                          1 Reply Last reply
                          0
                          • mdione@en.osm.townM 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 🙂

                            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
                            #116

                            @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

                            mdione@en.osm.townM 1 Reply Last reply
                            0
                            • dazfuller@mstdn.socialD dazfuller@mstdn.social

                              Damn! Posted this yesterday as I found it funny, but nothing prepared me for the howling laughter I would get from the comments 😆

                              bencomp@code4lib.socialB This user is from outside of this forum
                              bencomp@code4lib.socialB This user is from outside of this forum
                              bencomp@code4lib.social
                              wrote last edited by
                              #117

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

                              rmflight@mastodon.socialR 1 Reply Last reply
                              0
                              • thezeronine@mastodon.pnpde.socialT thezeronine@mastodon.pnpde.social

                                @dazfuller and stolen from sources like https://nvie.com/posts/a-successful-git-branching-model/

                                addison@nothing-ever.worksA This user is from outside of this forum
                                addison@nothing-ever.worksA This user is from outside of this forum
                                addison@nothing-ever.works
                                wrote last edited by
                                #118

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

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

                                  mdione@en.osm.townM This user is from outside of this forum
                                  mdione@en.osm.townM This user is from outside of this forum
                                  mdione@en.osm.town
                                  wrote last edited by
                                  #119

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

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

                                    @dazfuller 💁‍♀️

                                    Link Preview Image
                                    vladimir_lu@hachyderm.ioV This user is from outside of this forum
                                    vladimir_lu@hachyderm.ioV This user is from outside of this forum
                                    vladimir_lu@hachyderm.io
                                    wrote last edited by
                                    #120

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

                                    itgrrl@infosec.exchangeI 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)

                                      0@corteximplant.com0 This user is from outside of this forum
                                      0@corteximplant.com0 This user is from outside of this forum
                                      0@corteximplant.com
                                      wrote last edited by
                                      #121

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

                                      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)

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

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

                                        1 Reply Last reply
                                        0
                                        • jedbrown@hachyderm.ioJ jedbrown@hachyderm.io

                                          @dazfuller
                                          And this is the figure from the 2010 blog post that their machine plagiarized (badly).
                                          https://nvie.com/posts/a-successful-git-branching-model/

                                          Link Preview Image
                                          jigmedatse@social.openpsychology.netJ This user is from outside of this forum
                                          jigmedatse@social.openpsychology.netJ This user is from outside of this forum
                                          jigmedatse@social.openpsychology.net
                                          wrote last edited by
                                          #123

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

                                          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