Feedback Hub for Copilot Extensions

Welcome to the Copilot Extensions Feedback Hub. This public repository is designed to facilitate feedback exchanges between users, builders, clients, and GitHub. It serves as the primary channel for direct feedback.

If you’re looking for GitHub product updates and discussions, visit our Community Discussions forum.

For Users: Submitting feedback for the GitHub Product Team, Client Teams, and Builders

Feedback to the GitHub Product Team

If your feedback pertains to GitHub Copilot Extensions in general (e.g. bugs, feature requests) or the GitHub Marketplace (publishing, verifying, listing), please:

1. Open a new issue in this repository and add the "github team" label
2. Fill out the Extension Developer Survey for detailed feedback and feature requests

Feedback to Client Teams

A client team is the team that owns the surface where users would interface with a Copilot Extension. Client teams that support GitHub Copilot Extensions today are Visual Studio Code, Visual Studio, Chat in github.com, and Chat in GitHub Mobile. You can see a list of all supported clients here.

If your feedback is specific to Copilot Extensions in a specific IDE or surface (e.g. client side capabilities, IDE related bugs) please follow these steps:

1. Identify the correct label

2. Create a GitHub Issue in this repository

   • Navigate to the "Issues" tab in this repository.
   • Click on "New Issue" and describe your feedback in detail.
   • Apply the appropriate label using the IDE name.

3. Engage with client teams: After submitting your issue, the client team may respond to gather more details or provide updates. Keep an eye on the issue thread for any follow-up.

4. Stay organized: Ensure your feedback is directed to the correct client by applying the corresponding label. For status updates, you can turn on Issue notifications in the right-hand sidebar.

Feedback to Builders

If you’re using a Copilot Extension and would like to provide feedback directly to the builder, please follow these steps:

1. Identify the correct label:

   • Each Copilot Extension listed in the GitHub Marketplace typically has a label corresponding to its slug name (part of the URL in its listing).
   • Use the slug name as the label if your feedback is intended for the publisher of that extension.

2. Create a GitHub Issue in this repository:

   • Navigate to the "Issues" tab in this repository.
   • Click on "New Issue" and describe your feedback in detail.
   • Apply the appropriate label using the extension’s slug name.

3. Engage with builderes: After submitting your issue, the extension builders may respond to gather more details or provide updates. Keep an eye on the issue thread for any follow-up.

4. Stay organized: Ensure your feedback is directed to the specific Copilot Extension by applying the corresponding label. For status updates, you can turn on Issue notifications in the right-hand sidebar.

---

If you are unsure which label is most applicable for your feedback, please include the “githubproduct” label and our team will route your request.

Your feedback is essential in helping builders, clients, and the GitHub Product team improve the overall Copilot Extensions experience during this public preview phase.

---

For Builders and Client Teams: Monitoring & Managing Feedback

As a builder of or an IDE supporting a Copilot Extension, this repository allows you to monitor and manage the feedback that users provide. Feedback issues are tagged with labels corresponding to your extension’s slug name or your IDE name. Here’s how to get started:

1. Reviewing feedback via Issues:

   • Navigate to the "Issues" tab to see all feedback in a list format.
   • Use the "Filter" dropdown to select your label and view relevant feedback.

2. Reviewing feedback via Project Boards:

   • Access the feedback board through the "Projects" tab in this repository.
   • Filter the board by your label to see all associated feedback in one place.
   • You can use this Project board to manage and track the status of each feedback issue. Make sure to regularly review and update the board to resolve feedback in a timely manner.

3. Responding to feedback:

   • Engage with users by commenting on issues.
   • Keep the discussion constructive and focused on resolving or addressing the feedback.
   • Once feedback has been addressed, you can close the issue.

---

This repository is the main channel for sharing feedback to builders, IDEs and the GitHub product team during the public preview of Copilot Extensions.

For release updates from the GitHub Product Team, please visit our Community Discussions forum.