zlacker

>>davidg+(OP)
I just tested it myself on a random c file I created in the middle of a rust project I'm working on, it reproduced his full code verbatim from just the function header so clearly it does regurgitate proprietary code unlike some people have said, I do not have his source so co-pilot isn't just using existing context.

I've been finding co-pilot really useful but I'll be pausing it for now, and I'm glad I have only been using it on personal projects and not anything for work. This crosses the line in my head from legal ambiguity to legal "yeah that's gonna have to stop".

>>ianbut+ce
So I’m working on a side project and it’s hosted on GitHub, does this mean the code (which I consider precious and my own) can just be stolen and injected into my competitors codebase who is using co-pilot?

If this is the case, I can imagine people migrating of GitHub very quickly. I can also imagine some pretty nice lawsuits opening up.

>>bamboo+Qg1
A good rule of thumb is if you're worried about code being copied you really shouldn't put it on github. Even if most large companies respect copyright, that small studio in Russia certainly won't.

>>concor+0y1
How would the small studio access my private repo ?

>>bamboo+7X2
They wouldn't. If you have it in a private repository and you are the only one with access to it, you'll likely not run into this issue.

From other comments, this developers "private" code was found in 30k+ public repositories with public attribution which is what created this issue.

Presumably your private code is not also present or leaked to any public repositories.