# GitHub Community Discussions: How GitHub Collects Public Product Feedback > The community/community repository is not a software project to install. It is the GitHub-hosted public discussion forum where users report feedback on GitHub products including Actions, Codespaces, Copilot, and Mobile. GitHub's product team reads the discussions but does not commit to responding to every submission. **community/community** — Public feedback discussions for: GitHub Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more! - Repository: https://github.com/community/community - Stars: 8,806 · Forks: 4,541 - Language: Ruby - License: CC-BY-4.0 - Published: 2026-09-21 · Updated: 2026-09-21 · Language: en - Canonical page: https://hysenlabs.com/projects/community-community ## What this repository is and what it is not The community/community repository is the GitHub-run public feedback forum for GitHub's own products. The README identifies it as a place to share feedback, discuss topics with other community members, and ask questions about specific GitHub features. The Issues feature is deliberately disabled; all interaction happens through GitHub Discussions, which is the product the forum itself demonstrates in use. The repository does not contain deployable software. The Ruby files in the root (Gemfile, .rubocop.yml, .ruby-version) are infrastructure for the repository's own tooling, not an application for external use. Anyone looking for a software library or a tool to install has arrived at the wrong repository. The audience is GitHub users who want to influence the direction of GitHub products through public discussion. ## The 19 discussion categories and their product areas The README lists categories organized by product area. Accessibility covers GitHub's accessibility settings. Actions is for GitHub's CI/CD automation. Apps, API and Webhooks covers GitHub Apps, the REST API, the GraphQL API, and Webhooks. Code Security maps to GitHub's security scanning features. Codespaces covers the cloud development environment. Copilot Conversations is for feedback on GitHub Copilot. Discussions covers the Discussions feature itself. Enterprise is for GitHub Enterprise questions and feedback. GitHub Education covers the education program. GitHub Learn covers GitHub Certifications, Learning Pathways, and GitHub Skills. Mobile is for the GitHub mobile apps. npm is for the npm package registry. Packages covers GitHub Packages. Programming Help is a general category for programming questions not tied to a specific GitHub product. Projects and Issues covers GitHub Projects and Issues. Pull Requests covers pull request functionality. Repositories covers repository management. Welcome to GitHub is a community introduction space. Other Features and Feedback covers Code Search, Feed, Lists, Models, Pages, Profile, and Sponsors. ## How to participate: finding the right category and posting effectively Participation requires a GitHub account. The README gives clear guidance on the preferred process. Before creating a new discussion, check whether an existing thread already addresses the same suggestion. If a matching thread exists, reply with additional context or use upvotes to signal agreement rather than opening a duplicate. When no existing thread addresses the issue, open a new discussion in the category that most closely maps to the relevant product. The README asks contributors to review the Code of Conduct at docs.github.com/en/site-policy/github-terms/github-community-forum-code-of-conduct before participating. The description of the suggestion does not need to include a proposed solution; the README explicitly says you do not need to have a solution to the problem you are facing to start a discussion. ## The feedback pipeline from discussion to shipped feature The README describes a structured path from community feedback to product work. When a discussion gains enough signal, GitHub's product team evaluates the feedback. If the team decides to prioritize a feature, they may open an issue in the public roadmap at github.com/github/roadmap and track development there. The community/community repository and the github/roadmap repository work together: community is where feedback accumulates, and roadmap is where prioritized work becomes visible. The README is explicit that the team cannot respond to every submission. This means high-engagement threads with clear problem statements are more likely to receive attention than isolated posts. There is no mechanism in the repository for tracking which suggestions were accepted or rejected; outcomes become visible through activity in the roadmap repository. ## What the repository cannot do and where its limits are The repository is not a technical support channel. Questions about billing, account issues, or product bugs are better directed to GitHub Support. The Issues feature is disabled, so there is no traditional bug tracker in this repository. The product team does not commit to a timeline for any discussed feature. The README does not document any SLA or response time for community submissions. For topics that fall outside the defined categories, the README notes that discussions will be moved to the General category. The repository works with Discussions categories set up in advance; ad hoc categories are not something contributors can create. This means the structure of the feedback channels reflects GitHub's current product organization, not the taxonomy that any particular user might prefer. ## The CC-BY-4.0 license and the relationship with github/roadmap The repository is licensed under CC-BY-4.0, which applies to the content contributed to discussions. This is a Creative Commons Attribution license, not a software license. There is no code to distribute; the license governs the textual contributions to the forum. The connection to github/roadmap is documented in the README: the roadmap is described as the place where users can learn what features GitHub is working on and when they will be available. Community discussions that result in a roadmap item become trackable through the roadmap repository's Issues. The community/community repository does not track those connections internally. The last push to the repository was on 2026-09-09, reflecting ongoing moderation and configuration of the discussion forum. ## Community forum versus GitHub Support: different channels for different problems The community/community repository is designed for product feedback and discussion, not for resolving individual technical problems. GitHub Support handles account issues, billing, and private matters that should not be publicly visible. The community forum is for ideas, suggestions, and questions that benefit from input from other users. An engineer who encounters a bug in GitHub Actions should consider whether the issue is a general product behavior worth discussing publicly (community/community) or a specific malfunction requiring a private support ticket (GitHub Support). For open source project maintainers who want to influence GitHub's roadmap decisions, the Discussions categories tied to specific products (Actions, Codespaces, Pull Requests) are the appropriate venue. The Programming Help category is the only one without a direct GitHub product tie; it is for general coding questions. ## Conclusion The community/community repository is the right place to post feedback when you want GitHub's product team to see it alongside other public discussion. It is not a bug tracker, not a support channel, and not a place where responses are guaranteed. Suggestions that gain traction may appear in the github/roadmap repository as tracked work items. Check the Discussions tab at github.com/orgs/community/discussions before opening a new post, because an existing thread with upvotes is more useful to the product team than a duplicate. ## FAQ ### How do I submit feedback about a GitHub feature using community/community? Go to the Discussions tab at github.com/orgs/community/discussions, choose the category that matches the product you are giving feedback on, and open a new discussion. The README recommends checking for existing threads on the same topic before posting and upvoting existing threads rather than duplicating them. ### What is the difference between community/community Discussions and GitHub Issues? The Issues feature in community/community is disabled. All interaction happens through GitHub Discussions. Issues are used in the separate github/roadmap repository to track features that the GitHub product team has decided to build. community/community is for feedback gathering; github/roadmap is for work tracking. ### How does GitHub's product team respond to suggestions in community/community? The README states that the product team will evaluate feedback but cannot respond to every submission. If a suggestion is prioritized, they may open an issue in the public roadmap at github.com/github/roadmap. There is no guaranteed response time or process for communicating rejections. ## Sources - [community/community on GitHub](https://github.com/community/community) - [Issues](https://github.com/community/community/issues) - [License: CC-BY-4.0](https://github.com/community/community/blob/main/LICENSE) - [README](https://github.com/community/community/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/community-community