bcfe4dab3b
* Add new product to products.yml * Move directory to its new location and rename it * Update new index page * Remove old category from GitHub product index * Add collaboration category * Add membership category * Add roles category * Add teams category * Add team discussion category * Add repo access category * Add project board access category * Add app management category * Add org settings category * Add improved org perms category * Add category for OAuth app restrictions * Add org security category * Add SAML category * Add SAML access category * Add git access category * Add redirects and update links for collaboration category * Add redirects and update links to team discussions content * Add redirects and update links to SAML access category * Update links to org security category and add redirects * Add redirects for app managers content * Add redirects for project board category * Add redirects and update links for the repo access category * Add redirects for git access category * Add redirects and update links for membership category * Add redirects and update links for org settings category * Fix links * Add redirects and update links to org access category * Add redirects and upate links to SSO category * Add redirects to improved org perms category * Add redirects and update links to teams category * Add redirects and update links to oauth apps category * Fix links * Fix links * Fix links
2.1 KiB
title, intro, versions
| title | intro | versions | ||
|---|---|---|---|---|
| Granting higher permissions to top contributors | Repository administrators can promote any community member to a moderator and maintainer. |
|
{% data reusables.discussions.beta %}
Introduction
The most helpful contributors for the past 30 days are highlighted on the {% data variables.product.prodname_discussions %} dashboard, based on how many comments were marked as answers by other community members. Helpful contributors can help drive a healthy community and moderate and guide the community space in addition to maintainers.
Step 1: Audit your discussions top contributors
{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %}
- Compare the list of contributors with their access permissions to see who qualifies to moderate the discussion.
Step 2: Review permission levels for discussions
People with triage permissions for a repository can help moderate a project's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. For more information, see "Moderating discussions."
For more information about repository permission levels and {% data variables.product.prodname_discussions %}, see "Repository permissions levels for an organization."
Step 3: Change permissions levels for top contributors
You can change a contributor's permission levels to give them more access to the tooling they need to moderate GitHub Discussions. To change a person's or team's permission levels, see "Managing teams and people with access to your repository."
Step 4: Notify community members of elevated access
When you change a collaborators permission level, they will receive a notification for the change.