Time to put adversarial code into GitHub to pollute the training set?
`:(){ :|:& };:`s all the way down.
Ah, yes, the ol' Bobby Tables maneuver. Haha.
If you don't opt out by Apr 24 GitHub will train on your private repos
171–180 of 346 posts
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#172No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…
I think the problem is more with using PRIVATE repos. My letters are also private and I would be pretty pissed if the mail carrier was reading them. Why does GitHub think it has the right to do this?
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#173To Github's credit, they have been showing a banner consistently. To my discredit - I never bothered to read that banner until I saw this HN headline
I have never seen any app reset/loose setting before.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#174No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…
Thats still pretty bad. Its no longer private if all your code goes through LLM training set and is resurfable to everyone publicly. Why would I ever use copilot on any code Id want to be kept private? Labling it a private repo and having a tiny clause in the TOS saying we can take your code and show it to everybody is just an upright lie
I mean, you shouldn't send data to any SaaS LLM for code you want to be private, unless you have had them sign some sort of contract saying they will not train on your use. In fact, it is probably never a good idea to send anything you want to be private off premises unencrypted.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#175Thanks for posting this, I was never made aware of this by GitHub..
If you use Github, you should have an email from ~2 days ago with the subject "Important Update to GitHub Copilot Interaction Data Usage Policy". Easy to skip over assuming it's just one of a million private policy update emails.
If you don't use Github Copilot, this shouldn't effect you, and may be why you got no email. The current headline is fairly misleading--it's about Copilot usage, not private repos per se.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#176Earlier quoted context omitted.
No it isn't. Most people don't use Copilot, so this term change won't effect most people. You can reasonably be unhappy about it anyways (or unreasonably still be using Copilot in 2026), but it's still ultra-useful information for them to add to the discussion.
I don't use copilot, but somehow was subscribed... I probably clicked something long ago and it just remained active.
They're only training on interactions with Copilot, not with the full contents of repos that happen to be subscribed to Copilot.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#177Earlier quoted context omitted.
It's unnecessarily splitting hairs. > interaction data—specifically inputs, outputs, code snippets, and associated context [...] will be used to train and improve our AI models So using Copilot in a private repo, where lots of that repo will be used as context for Copilot, means GitHub will be using your private repo as training data when they were not before.
No it isn't. Most people don't use Copilot, so this term change won't effect most people. You can reasonably be unhappy about it anyways (or unreasonably still be using Copilot in 2026), but it's still ultra-useful information for them to add to the discussion.
Next step they'll rebrand search as "Copilot Search" or auto enable pull-request AI reviews (unless you hear about it and turn each off) and we'll all be "users".
Boiling the frog with a Venn diagram.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#178No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…
Yes, you will. This is what the setting says on my account when I clicked the link: > model training > Allow GitHub to collect and use my Inputs, Outputs, and associated context to train and improve AI models. Read more in the Privacy Statement Are you seriously trying to claim that the code isn't input, output, or associated context of Copilot operating on a private repo? What term do you think better applies to the…
If you are not willing to migrate out of GitHub, what you can do is to avoid using Copilot on your private repository.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#179There is always other peoples ftp servers as Linus used to say.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#180The UI options are also shady af. The setting reads Enabled - " You will have access to this feature" as help text. Disabled - " You will not have access to this feature". WTF does that mean?
I saw that too, it feels like it's worded to make it sound like it's mandatory for Copilot. Based on their blog post the "feature" is them training on your data.