Skip to content

Commit 5373283

Browse files
LisaKrMattamorphicsophietheking
authored
Adjust the locking-conversation file (#54072)
Co-authored-by: Matt B <[email protected]> Co-authored-by: Sophie <[email protected]>
1 parent 7366ff7 commit 5373283

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

content/communities/moderating-comments-and-conversations/locking-conversations.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,15 @@ topics:
1212
- Community
1313
---
1414

15-
It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct{% ifversion fpt or ghec %} or GitHub's [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines){% endif %}. When you lock a conversation, you can also specify a reason, which is publicly visible.
15+
It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct{% ifversion fpt or ghec %} or {% data variables.product.github %}'s [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines){% endif %}. When you lock a conversation, you can also specify a reason, which is publicly visible.
1616

17-
Locking a conversation creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who locked the conversation is only visible to people with write access to the repository. For anyone without write access, the timeline event is anonymized.
17+
Locking a conversation creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who locked the conversation is only visible to the following group of people:
1818

19+
* People with write access to the repository.
20+
* Collaborators added to the repository.
21+
* Organization members with read access where the repository is owned by an organization.
22+
23+
For anyone not meeting this criteria the locking actor will be anonymized.
1924
![Screenshot of a timeline event, which says "octo-org locked as too heated and limited conversation to collaborators 2 minutes ago."](/assets/images/help/issues/anonymized-timeline-entry-for-locked-conversation.png)
2025

2126
While a conversation is locked, only [people with write access](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization) and [repository owners and collaborators](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) can add, hide, and delete comments. Reactions and votes in a locked conversation are disabled for all users.

0 commit comments

Comments
 (0)