It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or GitHub's Community Guidelines. When you lock a conversation, you can also specify a reason, which is publicly visible.
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:
- People with write access to the repository.
- Collaborators added to the repository.
- Organization members with read access where the repository is owned by an organization.
For anyone not meeting this criteria the locking actor will be anonymized.
While a conversation is locked, only people with write access and repository owners and collaborators can add, hide, and delete comments. Reactions and votes in a locked conversation are disabled for all users.
To search for locked conversations in a repository that is not archived, you can use the search qualifiers is:locked and archived:false. Conversations are automatically locked in archived repositories. For more information, see Searching issues and pull requests.
- Optionally, write a comment explaining why you're locking the conversation.
- In the right sidebar of the issue or pull request, or above the comment box on the commit page, click Lock conversation.
- Optionally, select the Choose a reason dropdown menu, then click a reason for locking the conversation.
- Read the information about locking conversations and click Lock conversation on this issue, Lock conversation on this pull request, or Lock conversation on this commit.
- When you're ready to unlock the conversation, in the right sidebar of the issue or pull request, or above the comment box on the commit page, click Unlock conversation.