Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
dazfuller :rickwhoah:
dazfuller :rickwhoah:
@dazfuller@mstdn.social  ·  activity timestamp last week

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"

https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow

A visual representation of what should be the GitFlow process, showing how changes move from feature branches, to develop, release, and master. The diagram is a mess of arrows with some pointing in the wrong directions, and with multiple AI induced sentences such as "Bugfixes from rel, branch may be continvoucly morged back into develop", and no, that's honestly what is says
A visual representation of what should be the GitFlow process, showing how changes move from feature branches, to develop, release, and master. The diagram is a mess of arrows with some pointing in the wrong directions, and with multiple AI induced sentences such as "Bugfixes from rel, branch may be continvoucly morged back into develop", and no, that's honestly what is says
A visual representation of what should be the GitFlow process, showing how changes move from feature branches, to develop, release, and master. The diagram is a mess of arrows with some pointing in the wrong directions, and with multiple AI induced sentences such as "Bugfixes from rel, branch may be continvoucly morged back into develop", and no, that's honestly what is says

Components of the GitHub flow - Training

Learn to use the components of the GitHub flow
4
  • Copy link
  • Flag this post
  • Block
';DROP TABLE foxes;--
';DROP TABLE foxes;--
@DropTableFoxes@social.stackunderflow.com  ·  activity timestamp last week

@dazfuller Because Tim's a -10x developer, ruining the codebase with AI slop.

  • Copy link
  • Flag this comment
  • Block
Florian
Florian
@fmasy@piaille.fr  ·  activity timestamp last week

@dazfuller I have no words ... what is the point of generating a slop version of an already existing image ?!!

How can we wake up of this nightmare !?

#aislop #microslop

  • Copy link
  • Flag this comment
  • Block
davidvedvick
davidvedvick
@davidvedvick@fosstodon.org  ·  activity timestamp last week

@dazfuller thank god we've finally found a use for all of those GPUs

  • Copy link
  • Flag this comment
  • Block
Jed Brown
Jed Brown
@jedbrown@hachyderm.io  ·  activity timestamp last week

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

Original Git Flow cartoon, Time pointed downwards showing the branching model. In this model, feature branches merge to develop and releases are tagged on master.
Original Git Flow cartoon, Time pointed downwards showing the branching model. In this model, feature branches merge to develop and releases are tagged on master.
Original Git Flow cartoon, Time pointed downwards showing the branching model. In this model, feature branches merge to develop and releases are tagged on master.
nvie.com

A successful Git branching model

In this post I present a Git branching strategy for developing and releasing software as I’ve used it in many of my projects, and which has turned out to be very successful.
  • Copy link
  • Flag this comment
  • Block

Kakapo Social

Kakapo Social: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.2-alpha.34 no JS en
Automatic federation enabled
Log in
Instance logo
  • Explore
  • About
  • Members
  • Code of Conduct