Copilot 에이전트에 대한 GitHub 앱 구성

Once you have configured your server and created your GitHub App, you need to configure your GitHub App for use with your Copilot agent.

Prerequisites

• You have configured your server to deploy your Copilot agent, and you have your hostname (aka forwarding endpoint). For more information, see Configuring your server to deploy your Copilot agent.
• You have created a GitHub App for your Copilot agent. For more information, see Creating a GitHub App for your Copilot Extension.

Configuring your GitHub App

1. In the upper-right corner of any page on GitHub, click your profile photo.

2. Navigate to your account settings.

   • For an app owned by a personal account, click Settings.
   • For an app owned by an organization:
     1. Click Your organizations.
     2. To the right of the organization, click Settings.
   • For an app owned by an enterprise:
     1. If you use Enterprise Managed Users, click Your enterprise to go directly to the enterprise account settings.
     2. If you use personal accounts, click Your enterprises and then to the right of the enterprise, click Settings.

3. Navigate to the GitHub App settings.

   • For an app owned by a personal account or organization:
     1. In the left sidebar, click Developer settings, then click GitHub Apps.
   • For an app owned by an enterprise:
     1. In the left sidebar, under "Settings", click GitHub Apps.

4. To the right of the GitHub App you want to configure for your Copilot Extension, click Edit.

5. In the "Identifying and authorizing users" section, under "Callback URL", enter your server's hostname, then click Save changes.

   Note

   This step is only required if you intend to request user authorization (OAuth) during installation.

   Your server's hostname is the forwarding endpoint that you copied from your terminal when you configured your server. For more information, see "Configuring your server to deploy your Copilot agent."

   If you are using an ephemeral domain in ngrok, you will need to update this URL every time you restart your ngrok server.

6. In the left sidebar, click Permissions & events.

7. To expand the "Account permissions" section, click anywhere in the section.

8. In the "GitHub Copilot Chat" row, select the Access: dropdown menu, then click Read-only. Click Save changes.

9. In the left sidebar, click Copilot.

10. Read the GitHub Marketplace Developer Agreement and the GitHub Pre-release License Terms, then accept the terms for creating a Copilot Extension.

11. In the "App type" section, select the dropdown menu, then click Agent.

12. Under "URL," enter your server's hostname (aka forwarding endpoint) that you copied from your terminal.

    Note

    If you are using an ephemeral domain in ngrok, you will need to update this URL every time you restart your ngrok server.

13. Under "Inference description", type a brief description of your agent, then click Save. This will be the description users see when they hover over your agent's slug in the chat window.

14. Your pre-authorization URL is a link on your website that starts the authorization process for your extension. Users will be redirected to this URL when they decide to authorize your extension. If you are using a pre-authorization URL, under "Pre-authorization URL," enter the URL, then click Save changes.

15. In your GitHub App settings, in the left sidebar, click Install App, then, next to the account you want to install your app on, click Install.

16. On any page on GitHub, click the GitHub Copilot icon at the bottom right of the page.

    The GitHub Copilot Chat panel is displayed. To resize the panel, click and drag the top or left edge.

17. If the panel contains a previous conversation you had with Copilot, click the "New conversation" icon (a plus sign) at the top right of the panel.

    

18. Invoke your extension by typing @EXTENSION-NAME, replacing any spaces in the extension name with -, then press Enter.

19. If this is your first time using the extension, you will be prompted to authenticate. Follow the steps on screen to authenticate your extension.

20. Ask your extension a question in the chat window. For example, What is the software development lifecycle?.