News for hackers. Stuff that matters.
Re:GitHub Copi­lot inves­ti­ga­tion by SahAssar on Tuesday October 18, 2022 @03:38AM (#33244168)
> Or they could integrate a way to find the produced output back in the corpus if it's sufficiently close and provide a reference/attribution. Basically whatever tool a copyright lawyer would use to track down original work.

That assumes that the licenses of your code and the original code are compatible which often isn't the case.

Re:GitHub Copi­lot inves­ti­ga­tion by sooyoo on Tuesday October 18, 2022 @05:40PM (#33254399)
No, it doesn't assume that. Ensuring that they are compatible would be the next step. Either manually by the user or automatically by showing a fat warning or retracting the suggested code completion.