zlacker

What does

> with "public code" blocked

mean? Are you able set a setting in GitHub to tell GitHub that you don't want your code used for Copilot training data? Is this an abuse of the license you sign with GitHub, or did they update it at some point to allow your code to be automatically used in Copilot? I'm not crazy about the idea of paying GitHub for them to make money off of my code/data.

>>bmitc+(OP)
The option to omit "public code" means it should, in theory, omit code that is licensed under such banners as the GPL. It does not mean "omit private repositories".

>>bmitc+(OP)
> We built a filter to help detect and suppress the rare instances where a GitHub Copilot suggestion contains code that matches public code on GitHub. You have the choice to turn that filter on or off during setup. With the filter on, GitHub Copilot checks code suggestions with its surrounding code for matches or near matches (ignoring whitespace) against public code on GitHub of about 150 characters. If there is a match, the suggestion will not be shown to you. We plan on continuing to evolve this approach and welcome feedback and comment.

From the FAQ https://github.com/features/copilot/

>>galley+u2
I should have pointed out that those were two separate questions.

Public code is a weird name to use for that use case.

>>defasd+Wb
That is for people using Copilot. I’d like a setting that tells GitHub to not scan my code at all. And I am curious about that sneaking into the terms in between me signing up and paying and them taking code for free.

I have also never heard of “public code” being used in that way.

>>bmitc+Ol
> I’d like a setting that tells GitHub to not scan my code at all.

What about people forking/mirroring your code? Or people merely contributing code? There is no one-to-one correspondence between copyright holders and Github users.

Copilot should just comply with the license, that's it.

>>defasd+Wb
WTF is «public code»?

>>leni53+NK
It seems they don't comply with licenses. And it's not possible to fork or mirror to private repositories.

It would be a lot less trouble for everyone if it was just a per repository setting.

>>bmitc+Ol
A good first approximation of such a setting is to never publish on Github in the first place.

Of course, someone else can still upload your elsewhere-published code to GH. You cannot win.