Copilot is now injecting ads into GitHub pull requests. It's a disaster. (www.windowscentral.com)
from mesamunefire@piefed.social to programming@programming.dev on 30 Mar 15:08
https://piefed.social/c/programming/p/1933354/copilot-is-now-injecting-ads-into-github-pull-requests-it-s-a-disaster

#programming

threaded - newest

abbadon420@sh.itjust.works on 30 Mar 15:16 next collapse

Makes it easier to recognize the slop

JoeKrogan@lemmy.world on 30 Mar 15:36 next collapse

Next will be weaponized ads.

Marshezezz@lemmy.blahaj.zone on 30 Mar 16:00 next collapse

Pay now or the trigger pulls!

Natanael@slrpnk.net on 30 Mar 16:48 collapse

Drink a verification can

snooggums@piefed.world on 30 Mar 16:35 collapse

These are weaponized ads.

supersquirrel@sopuli.xyz on 30 Mar 15:40 next collapse

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

Kissaki@programming.dev on 30 Mar 15:47 next collapse

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

Kissaki@programming.dev on 30 Mar 15:47 next collapse

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@piefed.social on 30 Mar 16:20 collapse

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

urushitan@kakera.kintsugi.moe on 30 Mar 18:18 collapse

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

curbstickle@anarchist.nexus on 30 Mar 18:41 collapse

Thats a bingo

hperrin@lemmy.ca on 30 Mar 16:03 next collapse

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

mesamunefire@piefed.social on 30 Mar 16:06 collapse

Yeah I like it quite a bit.

panda_abyss@lemmy.ca on 30 Mar 16:06 next collapse

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@piefed.social on 30 Mar 17:41 next collapse

Microslop

Ephera@lemmy.ml on 30 Mar 19:03 collapse

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

Breezy@sopuli.xyz on 30 Mar 16:52 next collapse

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.

mesamunefire@piefed.social on 30 Mar 16:57 next collapse

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@feddit.uk on 30 Mar 17:18 next collapse

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@piefed.social on 30 Mar 18:11 next collapse

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.

mesamunefire@piefed.social on 30 Mar 18:41 collapse

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@piefed.social on 30 Mar 18:54 collapse

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@ani.social on 30 Mar 18:15 collapse

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

mindbleach@sh.itjust.works on 30 Mar 17:24 next collapse

> Decentralized protocol implemented by Torvalds himself
> Community gravitates around one decent website
> Microsoft buys that website

This is why we can’t have nice things.

terabyterex@lemmy.world on 30 Mar 17:59 next collapse

explain how you contribute with out an account? is there a hosting service that lets you do that?

Flipper@feddit.org on 30 Mar 18:17 next collapse

Sourcehut duports git-email.

django@discuss.tchncs.de on 30 Mar 19:01 collapse

They also created very good documentation: git-send-email.io

Breezy@sopuli.xyz on 30 Mar 18:48 next collapse

I currently have a GitHub account in order to contribute to projects hosted on GitHub, because I don’t think there is currently a way possible to do thinks like open up an issue without an account.

Ephera@lemmy.ml on 30 Mar 19:01 collapse

In case, you’re not aware, you can also email the dev. You can code up your commits as normal and then use e.g. git format-patch -3 to put the last 3 commits patch files. You can then attach those files to an e-mail and the dev can apply those patches with git am.

It takes a bit of playing around, but it’s actually really easy.
The Linux kernel, one of the most complex projects on the planet, develops like this.

markz@suppo.fi on 30 Mar 19:17 collapse

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

uuj8za@piefed.social on 30 Mar 16:58 collapse

takes deep breath

AHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA

Just switch to Codeberg already.