GitHub Community Discussions
In this repository, you will find categories for various product areas. Feel free to share feedback, discuss topics with other community members, or ask questions.
|Feedback Category||About the Product|
|GitHub Actions and GitHub Packages|
|GitHub API and GitHub Webhooks|
|Code Search & Navigation|
|GitHub Copilot (Technical Preview)|
|GitHub Code Security|
|GitHub Lists (Public Beta)|
|GitHub Pull Requests|
|General Feedback||GitHub Docs|
These discussions are where you can share suggestions for how the products should be improved and discuss those improvements with the community, including members of the GitHub product team. Check out Making suggestions to learn how to provide feedback.
You will also find previous Discourse Community Forum categories that have since been updated in GitHub Discussions categories below:
|Discourse Category||New Discussions Category|
|GitHub Help||New to GitHub|
|Code to Cloud||Actions and Packages|
|GitHub Ecosystem||APIs and Integrations|
When creating a new post, make sure to choose the predetermined category that best fits your topic. This will ensure that conversations are indexed by their corresponding product or feature, to help community members quickly find answers to their questions.
This repository works in conjunction with the GitHub public product roadmap, which is where you can learn about what features we're working on, and when they'll be available. Accordingly, the Issues feature of this repository has been disabled. Discussion categories have been established for specific features listed above, as well as a general category for other topics. Additional categories may be added in the future. In the meantime, topics outside of the listed categories above, will be transferred into the General category. Please review the CODE OF CONDUCT before participating in discussions.
We encourage you to open a discussion if you have suggestions for how we can improve our products. You don't need to have a solution to the problem you are facing to kick off a discussion. We hope to foster productive and collaborative conversations, so please check out how to give good feedback for guidance on how to kick off a successful discussion.
Prior to creating a new discussion, please take a look at previous discussions to see if someone else has already shared your suggestion(s). If you find a similar discussion, reply with additional details or upvote the discussion to signal your support rather than creating a new one.
From a suggestion to a shipped feature
Once you kick off a discussion, the GitHub product team will evaluate the feedback but will not be able to respond to every submission. From there, we will work with you, and the entire community, to ensure we understand the current capabilities GitHub doesn’t have and explore the space for potential solutions to your problem statement:
- If the product team determines that we are going to prioritize a feature to solve the problem you've identified, we may open an issue and track its development in the public roadmap.
- If the product team determines that we will not be working to solve the problem you have identified, we may comment on the discussion describing our reasoning so our decisions can remain transparent.
Any statement in this repository that is not purely historical is considered a forward-looking statement. Forward-looking statements included in this repository are based on information available to GitHub as of the date they are made, and GitHub assumes no obligation to update any forward-looking statements. The forward-looking comments in the public feedback discussions do not represent a commitment, guarantee, obligation or promise to deliver any product or feature, or to deliver any product and feature by any particular date, and are intended to outline the general development plans. Customers should not rely on these public feedback discussions to make any purchasing decision.