Beehaw
  • Communities
  • Create Post
  • search
    Search
  • Login
  • Sign Up
mesa ( mesamunefire@piefed.social )  to Programming@programming.devEnglish · 20 days ago

Copilot is now injecting ads into GitHub pull requests. It's a disaster.

www.windowscentral.com

external-link
message-square
23
link
fedilink
220
external-link

Copilot is now injecting ads into GitHub pull requests. It's a disaster.

www.windowscentral.com

mesa ( mesamunefire@piefed.social )  to Programming@programming.devEnglish · 20 days ago
message-square
23
link
fedilink
A developer caught Copilot adding promotional "tips" to code descriptions, highlighting a messy new era of AI slop.
alert-triangle
You must log in or # to comment.
  • [object Object] ( panda_abyss@lemmy.ca ) 
    link
    fedilink
    arrow-up
    65
    ·
    20 days ago

    This is fucking hilarious.

    It rewrites the description so unless you view the in app edit history it looks like you are endorsing this ad!

    Who the fuck shipped this lol

    • LurkingLuddite ( LurkingLuddite@piefed.social ) 
      link
      fedilink
      English
      arrow-up
      37
      ·
      20 days ago

      Microslop

    • Ephera ( Ephera@lemmy.ml ) 
      link
      fedilink
      English
      arrow-up
      6
      ·
      20 days ago

      Yeah, I might block a contributor on sight, if they post something like that.

  • Breezy ( Breezy@sopuli.xyz ) 
    link
    fedilink
    arrow-up
    62
    ·
    20 days ago

    I really wish more FOSS projects would move off of GitHub. It feels wrong just having an account just so I can contribute. Hopefully horrible “features” like this encourages others to migrate.

    • mesa ( mesamunefire@piefed.social ) OP
      link
      fedilink
      English
      arrow-up
      16
      ·
      20 days ago

      I have a library that has over 2 Million downloads in pip. How do you switch from github to codeberg (or any other git)? I just dont want to break things for everyone :)

      • hades ( hades@feddit.uk ) 
        link
        fedilink
        arrow-up
        41
        ·
        20 days ago

        You can start by moving your development workflows (pull requests, issue tracking, etc.) to something like codeberg. You can continue publishing your PyPI package from Github by just pushing your code from codeberg to Github.

        Eventually you can also move the publishing pipeline over as well. I don’t know how complicated your library is, of course, but in simplest cases it’s a matter of rewriting a config file in a slightly different way.

      • uuj8za ( uuj8za@piefed.social ) 
        link
        fedilink
        English
        arrow-up
        21
        ·
        20 days ago

        I mean, if Zig and Guix can do it. It’s possible.

        I’m in a similar boat. So far:

        • I started mirroring GitHub to Codeberg
        • I added CI to Codeberg

        Next I gotta update the readme on GitHub telling everyone that I’m going to move to Codeberg. I’ll let that sit for a few months.

        Also, I gotta update consumers like homebrew to consume from Codeberg instead.

        I was gonna close/merge any open PRs on GitHub.

        Issues, I’m not totally sure about. I thought I read there was a way to migrate those. Although, I’m kiiinda ok with starting fresh… not totally sure this part needs more thought.

        Once the Codeberg repo is ready, I’ll make the GitHub repo read-only, with the readme pointing to Codeberg.

        Way, way, way down the line, I’d consider deleting the GitHub repo (and finally my account).

        I’m OK with breaking things. I’m gonna try my hardest to not break stuff, but I’m not going to let the fear of breaking stuff prevent me from getting on ShitHub by Macroslop.

        • mesa ( mesamunefire@piefed.social ) OP
          link
          fedilink
          English
          arrow-up
          2
          ·
          20 days ago

          How did you get the CI working in codeberg? last time I checked, you had to get permission to do so(?). I would love to switch when I have time.

          • uuj8za ( uuj8za@piefed.social ) 
            link
            fedilink
            English
            arrow-up
            9
            ·
            20 days ago

            You do have to ask for permission. https://docs.codeberg.org/ci/

            Asking permission involves creating an issue on the Codeberg-e.V./requests repo: https://codeberg.org/Codeberg-e.V./requests/issues/new?template=ISSUE_TEMPLATE%2FWoodpecker-CI.yaml

            Here’s an example issue asking permission for CI: https://codeberg.org/Codeberg-e.V./requests/issues/1663

            They get back to you fairly quickly. I think the main thing they check for is if your project is FOSS. They don’t seem very strict otherwise.

            After you get permission, you can go to https://ci.codeberg.org/login to access CI.

            You’ll also need to create a .woodpecker folder in your repo.

            Woodpecker docs are here: https://woodpecker-ci.org/docs/usage/intro

            # .woodpecker/my-first-workflow.yaml  
            when:  
              - event: push  
                branch: main  
            
            steps:  
              - name: build  
                image: debian  
                commands:  
                  - echo "This is the build step"  
                  - echo "binary-data-123" > executable  
              - name: a-test-step  
                image: golang:1.16  
                commands:  
                  - echo "Testing ..."  
                  - ./executable  
            
      • SpikesOtherDog ( SpikesOtherDog@ani.social ) 
        link
        fedilink
        English
        arrow-up
        3
        ·
        20 days ago

        I think you would clone the repo and continue with codeberg. Announce wherever you can, and continue any new work at the new repo.

    • Mark with a Z ( markz@suppo.fi ) 
      link
      fedilink
      arrow-up
      12
      ·
      20 days ago

      The worse it gets, the faster the migration rate becomes.

  • supersquirrel ( supersquirrel@sopuli.xyz ) 
    link
    fedilink
    arrow-up
    47
    ·
    20 days ago

    Yeah, this was always the next obvious booster stage on the Slop Rocket.

  • Kissaki ( Kissaki@programming.dev ) 
    link
    fedilink
    English
    arrow-up
    46
    ·
    20 days ago

    March 30, 2026 @ 10:45 AM EST: Martin Woodward, Vice President of Developer Relations at GitHub, confimed that Copilot was injecting product tips into pull requests but that the feature has been disabled following feedback.

    They posted an update to the article about this recent update. After feedback, they decided to disable this feature.

    • TachyonTele ( TachyonTele@piefed.social ) 
      link
      fedilink
      English
      arrow-up
      35
      ·
      20 days ago

      It’ll be back. They’ll just wait a little longer to fully implement it.

      • urushitan 漆たん ( urushitan@kakera.kintsugi.moe ) 
        link
        fedilink
        arrow-up
        14
        ·
        20 days ago

        Eventually it will be This feature can only be disabled on Enterprise or Pro+ plans

        • curbstickle ( curbstickle@anarchist.nexus ) 
          link
          fedilink
          English
          arrow-up
          6
          ·
          20 days ago

          Thats a bingo

  • uuj8za ( uuj8za@piefed.social ) 
    link
    fedilink
    English
    arrow-up
    25
    ·
    20 days ago

    takes deep breath

    AHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA

    Just switch to Codeberg already.

  • Kissaki ( Kissaki@programming.dev ) 
    link
    fedilink
    English
    arrow-up
    20
    ·
    20 days ago

    Not even labeled as an ad/sponsored content/influenced “tip”/suggestion.

  • SleeplessCityLights ( SleeplessCityLights@programming.dev ) 
    link
    fedilink
    arrow-up
    16
    ·
    20 days ago

    They were successful because of VC funding, we were doomed from the start. VCs want one thing and one thing only, to back a Unicorn. Nothing else matters to them.

  • hperrin ( hperrin@lemmy.ca ) 
    link
    fedilink
    English
    arrow-up
    16
    ·
    20 days ago

    I’m in the process of switching to my own Forgejo instance. It’s been pretty easy so far.

    • mesa ( mesamunefire@piefed.social ) OP
      link
      fedilink
      English
      arrow-up
      6
      ·
      20 days ago

      Yeah I like it quite a bit.

  • kehet ( kehet@sopuli.xyz ) 
    link
    fedilink
    arrow-up
    5
    ·
    20 days ago

    Isn’t this what claude also does?

  • wonderingwanderer ( wonderingwanderer@sopuli.xyz ) 
    link
    fedilink
    arrow-up
    4
    ·
    20 days ago

    Tha fuq?

Programming@programming.dev

programming@programming.dev

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 84 users / day
  • 562 users / week
  • 1.78K users / month
  • 4.27K users / 6 months
  • 447 local subscribers
  • 26.6K subscribers
  • 2.42K Posts
  • 20K Comments
  • Modlog
  • mods:
  • snowe ( snowe@programming.dev ) 
  • Ategon ( Ategon@programming.dev ) 
  • UlrikHD ( UlrikHD@programming.dev ) 
  • bugsmith ( bugsmith@programming.dev ) 
  • Spyro ( Spyro@programming.dev ) 
  • BE: 0.19.15
  • Modlog
  • Legal
  • Instances
  • Docs
  • Code