Managing Community Discussions: Pinning, Moving, and Closing Threads FAQ
Maintaining an active community space requires clear structural moderation. When project maintainers and moderators need to spotlight key guidelines, keep topics correctly sorted, or conclude finished debates, platform tools provide specific controls. This practical question-and-answer guide outlines how discussions can be pinned, transferred across categories, migrated between repositories, or closed when resolved.
Which roles hold permission to triage and organize community discussions?
To administer discussions within a repository, GitHub Discussions must first be enabled for that repository. At the organization level, the feature must be enabled for the organization. According to the Managing discussions documentation from GitHub Docs, discussions can be managed by repository administrators as well as collaborators granted triage access or higher. For organization-wide conversations, management rights belong to repository administrators and members holding triage or greater access within the specific source repository designated for organization discussions.
Organization owners maintain authority to select the specific permission levels necessary for users to start new discussions across repositories owned by the organization. To regulate discussion creation for organization-level forums, owners adjust the required creation permissions within the underlying source repository. Maintainers often pair these controls with clear community resources, such as contributor guidelines and a code of conduct, to set operational expectations as covered in our Forum Moderation Guide for New Community Owners.
How many discussions can you pin at once, and where do they appear?
Community managers can spotlight prominent notices to ensure essential information remains readily visible. Discussions can be pinned at two distinct levels:
- Globally pinned discussions: You can pin up to four discussions above the primary discussion list for a repository or organization.
- Category pinned discussions: You can pin up to four discussions above the discussion listings inside an individual category.
When discussions are pinned globally, they display alongside any threads pinned to a specific category, such as an Ideas board. To pin a topic, open the discussion, navigate to the right sidebar, and click the pin option for the repository or the specific category. Moderators also have the option to customize the visual appearance of a pinned discussion before confirming. If you modify or edit a pinned discussion later, that edit does not change the category assigned to the thread.
Unpinning a topic requires clicking the unpin option in the right sidebar and confirming the prompt. Unpinning removes the thread from the top spotlight area, but it does not delete the discussion from the forum.
What rules and restrictions apply when moving threads between categories?
Re-sorting topics helps participants locate relevant conversations without cluttering unrelated sections. While planning board layouts as outlined in our guide on How to Structure Forum Categories (Without Creating Ghost Boards), moderators frequently encounter misplaced posts that need manual relocation.
To change the category of an existing thread:
- Go to the main page of the repository or organization and select the discussions area.
- Open the specific discussion that needs to be moved.
- In the right sidebar, click the control next to the category label.
- Click the target category to complete the change.
A critical rule applies during reorganization: it is not possible to move any discussion into or out of the polls category. Additionally, maintainers can apply granular repository labels to categorize threads by triaging status. Labels are shared across issues, pull requests, and discussions within each repository.
How do repository transfers work for active discussions?
Moving a conversation entirely outside its current repository requires specific conditions. The GitHub Docs guide to managing discussions details that transfers can only occur between repositories owned by the exact same user account or organization account. You must hold discussion creation permissions within the destination repository. If moving a thread to an organization forum, you need permissions to create discussions within the designated source repository.
Strict boundaries restrict certain transfers:
- Discussions cannot be transferred from a private repository to a public repository.
- Discussions classified as announcements cannot be transferred.
When requirements are met, moderators click the transfer option in the right sidebar, select or search for the destination repository, and confirm the transfer.
When should you close a discussion or convert it into a task?
Discussions should be closed when the conversation reaches a resolution, becomes outdated, or duplicates an existing subject. To conclude a thread, navigate below the comment box at the bottom of the discussion and click the close button. A dropdown menu directly adjacent to the close button allows moderators to designate a formal closing reason.
If an ongoing discussion produces an actionable idea or identifies a bug ready for implementation, maintainers can convert the finding into direct work by creating a new issue directly from the discussion thread. If a discussion must be permanently removed rather than closed, moderators select the delete option in the right sidebar, review the warning confirmation, and approve the permanent deletion.
Sources
Managing discussions - GitHub Docs
Published October 31, 2026. No affiliate links on this page. Facts come from the sources linked above; check them for updates.