Finding public code that matches GitHub Copilot suggestions

This version of this article is for Copilot in Visual Studio. For Copilot on other platforms, click the appropriate tab above.

View code references for inline suggestions

You can find code references in the GitHub Copilot log in Visual Studio.

1. In the menu bar, click View.

2. In the dropdown menu, click Output.

3. In Output view, click the box to the right of "Show output from" and select GitHub Copilot.

4. Leave the log displayed while you use GitHub Copilot in Visual Studio Code.

   When you accept an inline suggestion that matches code in a public GitHub repository, an entry is added to the log.

   The log entry includes the following details:

   • The time you accepted the suggestion. Click the "Show Timestamp" clock icon if the time is not displayed.
   • The description [Completions Public Code Match Information].
   • The license type for the matching code, if found, otherwise NOASSERTION.
   • The URL of the file on GitHub.com where the similar code was found.

Example log entry

09:39:16:203	[Completions Public Code Match Information] Similar code with license type [MIT] https://github.com/octo-org/octo-repo/blob/34deb75eb6a2e22483ed465a6aec38c02eb2536e/routines/quicksort.js

Verifying the code referencing functionality

可以通过提示 Copilot 添加一些常用代码并检查日志中的输出来验证代码引用是否正常工作。

1. 创建名为 fizz-buzz.js 的文件，并在编辑器中打开它。

2. 显示前一节中描述的日志。

3. 在编辑器中，键入：

   function fizzBuzz()
   

   在右括号后加一个空格。

   GitHub Copilot 应会建议可用来完成函数的代码。 通常，建议会是一个常见的 fizz buzz 算法的实现，它将与 GitHub 网站上正式发布的代码匹配。

4. 要接受建议，请按 Tab。

5. 检查是否已将类似代码的任何条目添加到日志中。

If a response in Copilot Chat includes matching code, this is below the suggested code by the following text:

Found similar code in public repos. View matches

Click View matches to open the GitHub Copilot log, if it is not already open, and add details of the matched code.

The details include:

• The time you added the details to the log. Click the "Show Timestamp" clock icon if the time is not displayed.
• The description [Code Match] as the first log entry before the list of matching code.
• The license type—if found—for each instance of similar code.
• The URL of the file on GitHub.com where the matching code was found.
• A code snippet showing the matching code.

Logging example

09:24:10:525	[Code Match] Similar code with 2 license type(s) [MIT, NOASSERTION]
09:24:10:525	## License: MIT
09:24:10:525	https://github.com/octo-org/octo-repo/tree/127aac4ab27a42706af01be80f7aae3b83f44fbc/buzzfizz.py
09:24:10:525	```
09:24:10:525	for i in range(1, n + 1):
09:24:10:525	        if i % 3 == 0 and i % 5 == 0:
09:24:10:525	            print('FizzBuzz')
09:24:10:525	        elif i % 3 == 0:
09:24:10:525	            print('Fizz')
09:24:10:525	        elif i % 5 == 0:
09:24:10:525	```
09:24:10:525	## License: NOASSERTION
09:24:10:525	https://github.com/octo-org/monalisa/tree/011308746e53b26b128fa53c044a2527c39231f0/fizz-buzz.py
09:24:10:525	```
09:24:10:525	i % 3 == 0 and i % 5 == 0:
09:24:10:525	            print('FizzBuzz')
09:24:10:525	        elif i % 3 == 0:
09:24:10:525	            print('Fizz')
09:24:10:525	        elif i % 5 == 0:
09:24:10:525	            print('Buzz')
09:24:10:525	        else:
09:24:10:525	            print(i)
09:24:10:525	```