Repository owners and collaborators, and people with write access to a repository, can lock conversations on issues, pull requests, and commits permanently or temporarily to defuse a heated interaction.
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:
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.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4