Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Updates to GitHub Copilot interaction data usage policy

github.blog

Post reply on HN
Print view View original

141–150 of 193 posts

Re: Updates to GitHub Copilot interaction data usage policy

#141

Post by verdverm »

0xbadcafebee wrote: post #97
QuadrupleA wrote: post #79

Fun fact: Copilot gives you no way to ignore sensitive files with API keys, passwords, DB credentials, etc.: https://github.com/orgs/community/discussions/11254#discussi... So by default you send all this to Microsoft by opening your IDE.

Separate fun fact: Gemini CLI blocks env vars with strings like 'AUTH' in the name. They have two separate configuration options that both let you allow specific env vars. Neither work (bad vibe coding). Tried opening an issue and a PR, and two separate vibe-coding bots picked up my issue and wrote PRs, but nobody has looked at them. Bug's still there, so can't do git code signing via ssh agent socket. Only choice is…

I use Gemini 3 to edit multiple forks. Your statement is false based on stuff I actually do.

Re: Updates to GitHub Copilot interaction data usage policy

#142

Post by verdverm »

crashingintoyou wrote: post #30
archb wrote: post #10

Earlier quoted context omitted.

Interestingly, it is disabled by default for me.

Reading the github blog post "If you previously opted out of the setting allowing GitHub to collect this data for product improvements, your preference has been retained—your choice is preserved, and your data will not be used for training unless you opt in."

Is this the new name for the setting? I cannot find one that sounds like the previous one you mention

Notable that they have no "privacy" section in account settings

Re: Updates to GitHub Copilot interaction data usage policy

#143

Post by mirekrusin »

rzmmm wrote: post #69
mirekrusin wrote: post #63

Earlier quoted context omitted.

The feature is that your coding style will be in next models!

I wish my GPL license would transit along with my code.

I said it few years back that code license doesn't exist anymore, some people just haven't realized it yet.

Re: Updates to GitHub Copilot interaction data usage policy

#144

Post by AbanoubRodolf »

hrmtst93837 wrote: post #43
DavidSJ wrote: post #31

Earlier quoted context omitted.

> Do they have this set on business accounts also by default? If so, this is really shady. Looks like not, but would it actually have been shadier, or are we just used to individual users being fucked over?

[flagged]

[flagged]

Re: Updates to GitHub Copilot interaction data usage policy

#145

Post by pred_ »

martinwoodward wrote: post #129
gpm wrote: post #19

Earlier quoted context omitted.

Me too, which is making me wonder if they're planning on silently flipping this setting on April 24th (making it impossible to opt out in advance).

We are not. The reason we wanted to announce early was so that folks had plenty of time to opt-out now. We've also added the opt-out setting even if you don't use Copilot so that you can opt-out now before you forget and then if you decide to use Copilot in the future it will remember your preference.

Would you be able to comment on https://news.ycombinator.com/item?id=47522876, i.e. explain the legal basis for this change for EU based users? If there is none, you may have to expect that people will exercise their right to lodge a complaint with a supervisory authority.

Re: Updates to GitHub Copilot interaction data usage policy

#147

Post by 0xbadcafebee »

verdverm wrote: post #141
0xbadcafebee wrote: post #97

Earlier quoted context omitted.

Separate fun fact: Gemini CLI blocks env vars with strings like 'AUTH' in the name. They have two separate configuration options that both let you allow specific env vars. Neither work (bad vibe coding). Tried opening an issue and a PR, and two separate vibe-coding bots picked up my issue and wrote PRs, but nobody has looked at them. Bug's still there, so can't do git code signing via ssh agent socket. Only choice is…

I use Gemini 3 to edit multiple forks. Your statement is false based on stuff I actually do.

Well it's true based on my running into the issue 8 hours ago

Re: Updates to GitHub Copilot interaction data usage policy

#148

Post by TJ_FLEET »

stefankuehnel wrote: post #18

If you scroll down to "Allow GitHub to use my data for AI model training" in GitHub settings, you can enable or disable it. However, what really gets me is how they pitch it like it’s some kind of user-facing feature: Enabled = You will have access to the feature Disabled = You won't have access to the feature As if handing over your data for free is a perk. Kinda hilarious.

[flagged]

Re: Updates to GitHub Copilot interaction data usage policy

#149

Post by miohtama »

inetknght wrote: post #60
lenova wrote: post #36

Earlier quoted context omitted.

Ugh, can't believe they made this opt-in by default, and didn't even post the direct URLs to disable in their blog post. To add on to your (already helpful!) instructions: - Go to https://github.com/settings/copilot/features - Go to the "Privacy" section - Find: "Allow GitHub to use my data for AI model training" - Set to disabled

> can't believe they made this opt-in by default You can't believe Microslop is force-feeding people Copilot in yet another way? > and didn't even post the direct URLs to disable in their blog post You can't believe Microshaft didn't tell you how to not get shafted?

He must be new here

Re: Updates to GitHub Copilot interaction data usage policy

#150

Post by latand6 »

danelski wrote: post #107
latand6 wrote: post #83

Why won't people like to make the models better? Aren't we all getting the benefit after all?

That's akin to being grateful for your local shop owner that they allowed you to sweep the floor for other customers.

Please don’t strawman me, I asked completely different question.

It’s not about being grateful or something, but that many people (devs) are too concerned about their code being stolen as if they’ve come up with something unique and the LLMs are some kind of database (which it isn’t).

At the end of the day we’re going to be using AI to write all the code, many of us already doing that. And if some GitHub copilot model would be better - we’re getting more quality code that is generally available for next pretraining runs (for your and other models). Some would even switch to copilot if it’s good.

What do you think about it?

Post reply on HN