Earlier quoted context omitted.
It wasn’t previously opt-in. Previously we didn’t do any training on usage. However as other products have come into the market they do train on usage. We’ve been training on our internal usage for just over a year and have seen some major improvements. For details see of the types of improvements we’ve seen from training on our internal usage check out this article: https://github.blog/news-insights/product-news/cop…
You can always ask your parent company to train on their usage. I hear they have incredibly massive codebases: Windows, Office, MSSQL, which stay out of training data for some reason. I thought neural nets never repeat the training data verbatim, and copyright does not pass through them, so what's the problem?
If you don't opt out by Apr 24 GitHub will train on your private repos
211–220 of 346 posts
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#212Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#213Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#214Earlier quoted context omitted.
It wasn’t previously opt-in. Previously we didn’t do any training on usage. However as other products have come into the market they do train on usage. We’ve been training on our internal usage for just over a year and have seen some major improvements. For details see of the types of improvements we’ve seen from training on our internal usage check out this article: https://github.blog/news-insights/product-news/cop…
You can always ask your parent company to train on their usage. I hear they have incredibly massive codebases: Windows, Office, MSSQL, which stay out of training data for some reason. I thought neural nets never repeat the training data verbatim, and copyright does not pass through them, so what's the problem?
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#215Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#216Earlier quoted context omitted.
Microsoft would never do this (-:
I don't like when people make sarcastic remarks and sign off in a way that indicates it was sarcasm. It kills it for me. Lol. Like using that /s or using that smiling emoji sign you used. A good joke would land even if some other people miss it because of the text format. "Microsoft would never do this" would have landed for me.
:)
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#217I've been saying this since 2023 > If your data is stored in a database that a company can freely read and access (i.e. not end-to-end encrypted), the company will eventually update their ToS so they can use your data for AI training — the incentives are too strong to resist https://news.ycombinator.com/item?id=37124188
Edit: Okay, sounds like you guys are pissed to the point where it seems like the pro tip here is to stop using GitHub. Pro tip: sign up for the business/enterprise version when reasonable in price. I do this with Google Workspace. You can also do it with GitHub. (Google doesn’t train on Workspace, Github doesn’t train on business customers, etc)
If the publishing industry can't win a case against the AI firms then you don't stand a chance when you finally find out they've been training on your private data the whole time.
They can tell you one thing and do the opposite and there's effectively nothing you can do about it. You'd be a fool to trust them.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#218Earlier 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.
I don't have to be a Copilot user to click on it.
This change is malicious, and it doesn't only affect Copilot users. It affects everyone on the platform!
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#219Earlier 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.
Re: If you don't opt out by Apr 24 GitHub will train on your private repos
#220Earlier quoted context omitted.
> https://github.blog/news-insights/company-news/updates-to-gi... > Should you decide to participate in this program, the interaction data we may collect and leverage includes: > - Outputs accepted or modified by you > - Inputs sent to GitHub Copilot, including code snippets shown to the model > - Code context surrounding your cursor position > - Comments and documentation you write > - File names, repository structu…
Do you use copilot?
Second response: Maybe? I press the little button to auto-generate commit titles and messages that showed up in my Github Desktop. Does that count?
I'm asking sincerely. I don't "use Copilot" as in using it in VS Code or while writing code, so I'm honestly not sure if I am.