GitHub backs down, kills Copilot pull-request ads after backlash
What happened
"Initially I thought there was some kind of training data poisoning or novel prompt injection and the Raycast team was doing some elaborate proof of concept marketing," Manson told The Register in an email. But no: Take a look around GitHub and you'll see more than 11,400 PRs with the same tip in them, all seemingly added by Copilot. This matters for IT, Telecom & Cyber because fresh price movement and input-cost detail should reset bid assumptions, breach response slas, and negotiation guardrails with 180, 11,400, 31 as the clearest commercial anchors; expect renewal uplift asks
Buyer takeaway
For IT, Telecom & Cyber, treat this as a cost-boundary signal rather than just a headline; buyer assumptions may need refreshing before the next quote or award decision
Cost / money
Use this to refresh should-cost views and challenge any fast repricing. Keep the read-through directional unless the source itself provides hard commercial numbers
Supplier / commercial
Suppliers with fresh cost justification may push harder on reopeners, indexation, shorter quote validity, or pass-through language. Buyers should separate real drivers from negotiation posture
Safety / operations
The operational risk is indirect: tight budgets or repricing battles often reappear later as reduced slack, substitutions, or execution compromises that buyers then have to manage
What to watch
Watch for shorter quote validity, reopeners, pass-through requests, or attempts to reset pricing on the back of weak evidence
Key facts
- "Initially I thought there was some kind of training data poisoning or novel prompt injection
- But no: Take a look around GitHub and you'll see more than 11,400 PRs with the same tip in th
- " Hearing feedback from the community following Manson's post and the kerfuffle it generated
- ® Updated to add on March 31: Martin Woodward, VP of Developer Relations, GitHub, said in a s
