HN Summary: Copilot Ad Injection Into PRs

Microsoft’s GitHub Copilot quietly injected promotional content into pull request descriptions — advertising competing products like Raycast without the affected companies’ knowledge or consent. With an estimated 1.5 million PRs already affected, this incident reignited debate over Microsoft’s pattern of leveraging its platform dominance for anticompetitive gain.

The Story

Developer Zach Manson’s PR description was silently edited by Copilot to include a promotional tip for Raycast — a direct competitor to GitHub’s own Copilot. Investigation revealed this wasn’t isolated: over 1.5 million GitHub pull requests contained similar injected content, with Copilot suggesting integrations for Jira, Linear, Slack, and Teams. Notably, Raycast’s team confirmed they had no knowledge of or involvement in this “advertising.”

GitHub PM Tim Rogers responded in the HN thread, acknowledging the misjudgment and stating the feature had been disabled for future PRs. Microsoft framed the content as “tips” rather than ads — a distinction HN users roundly rejected.

Key Takeaways

• Microsoft used its dominant code-hosting platform to advertise competing developer tools without consent
• 1.5 million PRs affected, suggesting this was a deliberate scaled feature, not a bug
• The incident echoes “Embrace, Extend, Extinguish” — a phrase cited repeatedly in the thread
• Copilot has had ads baked in since May 2025 launch, per follow-up research
• Questions raised about what else Copilot could silently insert — and what Microsoft already accesses via ToS

Community Reaction

The response was scathing. Commenters drew parallels to Ken Thompson’s “Reflections on Trusting Trust”:

“If Microsoft is willing to put ads into your PRs via Copilot, imagine what they could put into your codebase itself with Copilot.” — heavyset_go

“Microsoft has been testing exactly how much you can abuse the user before they move somewhere else. Windows is a prime example.” — Gigachad

Raycast employees confirmed they learned of this from the HN thread. Several argued the company should pursue legal action for brand damage. A Tim Rogers response in the related thread acknowledged the error: “This was the wrong judgement call. We won’t do something like this again.”

Media & Sources

💬 Discussion: HN Thread #1 — 1,446 pts, 604 comments 💬 Discussion: HN Thread #2 (duplicate) — 339 pts, 10 comments 🔗 Read: Original post — firsthand account with screenshot 🔗 Read: Neowin: 1.5M PRs affected — scale analysis 🖼️ Visual: