Skip to main content

Managing the availability of your Copilot Extension

After you build your Copilot Extension, you can change it's visibility or publish it on the GitHub Marketplace.

Note

GitHub Copilot Extensions is in public beta and subject to change.

When you build a Copilot Extension, you have two options for the visibility of your GitHub App:

  • Public: Any user or organization account with the link to your app's installation page can install it. Making your app public automatically creates a public installation page, but does not list the app on the GitHub Marketplace.
  • Private: Only the user or organization account that created the app can install it.

If you make your app public, you can choose to publish it on the GitHub Marketplace. To list your Copilot Extension on the GitHub Marketplace, you must meet the following requirements:

Changing the visibility of your Copilot Extension

  1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.
  2. Under "Organizations", next to the name of your organization, click Settings.
  3. At the bottom of the sidebar, select Developer settings, then click GitHub Apps.
  4. In the "GitHub Apps" section, next to the name of your Copilot Extension, click Edit.
  5. In the sidebar, click Advanced. At the bottom of the "Danger Zone" section, you will see one of two options:
    • Make public: If you see the Make public option, your GitHub App is currently private, and can only be installed by the organization or user that created the app. You can click Make public to allow any other account with the link to your app's installation page to install your Copilot Extension, or leave your settings as they are to keep your app private.
    • Make private: If you see the Make private option, your GitHub App is currently public, and can be installed by any account with the link to your app's installation page. You can click Make private to only allow the organization or user that created the app to install it, or leave your settings as they are to keep your app public.
  6. Optionally, if your GitHub App is public, you can share the link to the installation page for your Copilot Extension. In the sidebar, click Public page in the sidebar, then copy the link for your listing.

Listing your Copilot Extension on the GitHub Marketplace

Once your public app is owned by a verified publisher, you can apply to list it on the GitHub Marketplace.

  1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.
  2. Under "Organizations", next to the name of your organization, click Settings.
  3. At the bottom of the sidebar, select Developer settings, then click GitHub Apps.
  4. Select the app you'd like to add to GitHub Marketplace.
  5. On the app settings landing page, scroll down to the Marketplace section, then click List in Marketplace. The Marketplace section is only visible if your app is public.
  6. Once you've created a new draft listing, you'll see an overview of the sections that you'll need to visit before your GitHub Marketplace listing will be complete. Complete the required sections.
    1. When naming your listing for your Copilot Extension, use any of the following naming conventions:
      • YOUR-PRODUCT-NAME (example: "Copilot")
      • YOUR-COMPANY-NAME (example: "GitHub")
      • YOUR-COMPANY-AND-PRODUCT-NAMES (example: "GitHub Copilot")
      • YOUR-COMPANY-OR-PRODUCT-NAME for GitHub Copilot (example: "Docker for GitHub Copilot")
    2. When choosing the slug users will type to invoke your Copilot Extension, use the name of your listing, substituting dashes for spaces. If that slug is taken, try appending -app.
  7. In the sidebar, click Overview, then read and accept the GitHub Marketplace Developer Agreement.
  8. To submit your listing, click Submit for review. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process.

Note

GitHub reviews all Copilot Extension submissions to ensure they meet our standards for quality, performance, reliability, and security. We may deny submissions at our discretion, but we will provide reasons for any rejections. You are welcome to address any issues and resubmit your extension for review.