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은(는) 함수를 완료하기 위한 코드를 제안해야 합니다. 일반적으로 제안은 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	```