4.4 KiB
title, intro, permissions, versions
| title | intro | permissions | versions | ||
|---|---|---|---|---|---|
| Moderating discussions | You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don't align with your{% ifversion fpt or ghec %} community's code of conduct{% elsif ghes > 3.5 %} organization's contribution guidelines{% endif %}. | People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization. |
|
About moderating discussions
{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization.
Marking a comment as an answer
{% data reusables.discussions.marking-a-comment-as-an-answer %}
Locking discussions
It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s Community Guidelines. You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion. {% ifversion discussions-lock-allow-reactions %}You can also allow emoji reactions to a locked discussion.{% endif %}
{% ifversion discussions-closable %} {% note %}
Note: You can also close a discussion. For more information, see "Closing a discussion."
{% endnote %} {% endif %}
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %}
-
In the list of discussions, click the discussion you want to lock.
-
In the right margin of a discussion, click Lock conversation.
-
Read the information about locking conversations.{% ifversion discussions-lock-allow-reactions %}
-
Optionally, to allow emoji reactions while the discussion is locked, select Allow reactions.{% endif %}
-
To lock the conversation, click Lock conversation.
-
When you're ready to unlock the conversation, click Unlock conversation in the right margin of a discussion, then click Unlock conversation.
{% ifversion converting-issues-to-discussions %}
Converting an issue to a discussion
When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository, or source repository for organization discussions, can bulk convert issues based on labels. For more information, see "AUTOTITLE."
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.repositories.sidebar-issues %}
- In the list of issues, click the issue you'd like to convert.
- In the right margin of an issue, click Convert to discussion.
- Select the Choose a category drop-down menu, and click a category for your discussion.
- Click I understand, convert this issue to a discussion. {% endif %}
{% ifversion discussions-hide-comments-on-block %}
Blocking a user from your organization
Organization owners and moderators can block a user from the organization if their comments don't align with the community's code of conduct. When you block a user, they will no longer be able to comment on discussions. You can also hide all of the comments a user has made in the organization. For more information, see "AUTOTITLE."
{% data reusables.organizations.blocking-a-user %} {% endif %}