Locking conversations - GitHub Docs

https://docs.github.com/en/communities/moderating-comments-and-conversations/locking-conversations • 108 KB fetched
Open original page

Locking conversations - GitHub Docs Skip to main content
GitHub Docs Version: Free, Pro, & Team
Search or ask Copilot Search or ask Copilot

Select language: current language is English

Search or ask Copilot Search or ask Copilot

Open menu

Collapse sidebar Expand sidebar
Scroll breadcrumbs left
* Home

* Building communities

* Moderation

* Locking conversations

Scroll breadcrumbs right

Building communities

*
*

* Healthy contributions

* Management & moderation

* Community profiles

* Access community profiles

* Add a code of conduct

* Contributor guidelines

* Add a license to a repo

* Add support resources

* Community health file

* Encourage contributions

* Issue & PR templates

* About templates

* Configure

* Syntax for issue forms

* Syntax for GitHub's form schema

* Create a PR template

* Common validation errors when creating issue forms

* Moderation

* Manage comments

* Locking conversations

* Archive pull requests

* Limit interactions in repo

* Limit interactions in account

* Limit interactions in org

* Track comment changes

* Manage abuse in your org

* Manage reported content

* Maintaining safety

* Block from your account

* View blocked users in account

* Unblock from your account

* Block from your org

* View blocked users in org

* Unblock from your org

* Reporting abuse or spam

* Using wikis

* About wikis

* Manage wiki pages

* Create footer or sidebar

* Editing wiki content

* View a history of changes

* Change access permissions

* Disabling wikis

Locking conversations

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.

Copy as Markdown

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 .

Further reading

* Setting up your project for healthy contributions

* Using templates to encourage useful issues and pull requests

* Managing disruptive comments

* Maintaining your safety on GitHub

* Reporting abuse or spam

Back to top

Help and support
Was this Doc helpful?
Yes No

Help us make GitHub Docs great!
All Docs are open source. See something that's wrong or unclear? Submit a pull request.
Make a contribution

Still need help?
Ask the GitHub community Contact support Expert services Blog

GitHub Inc. © 2026 Terms Privacy Status Pricing

Links found on this page

1. Skip to main content [direct]
2. GitHub Docs [direct]
3. Building communities [direct]
4. Moderation [direct]
5. Management & moderation [direct]
6. Community profiles [direct]
7. Access community profiles [direct]
8. Add a code of conduct [direct]
9. Contributor guidelines [direct]
10. Add a license to a repo [direct]
11. Add support resources [direct]
12. Community health file [direct]
13. Encourage contributions [direct]
14. About templates [direct]
15. Configure [direct]
16. Syntax for issue forms [direct]
17. Syntax for GitHub's form schema [direct]
18. Create a PR template [direct]
19. Common validation errors when creating issue forms [direct]
20. Manage comments [direct]
21. Archive pull requests [direct]
22. Limit interactions in repo [direct]
23. Limit interactions in account [direct]
24. Limit interactions in org [direct]
25. Track comment changes [direct]
26. Manage abuse in your org [direct]
27. Manage reported content [direct]
28. Block from your account [direct]
29. View blocked users in account [direct]
30. Unblock from your account [direct]
31. Block from your org [direct]
32. View blocked users in org [direct]
33. Unblock from your org [direct]
34. Reporting abuse or spam [direct]
35. About wikis [direct]
36. Manage wiki pages [direct]
37. Create footer or sidebar [direct]
38. Editing wiki content [direct]
39. View a history of changes [direct]
40. Change access permissions [direct]
41. Disabling wikis [direct]
42. Community Guidelines [direct]
43. people with write access [direct]
44. repository owners and collaborators [direct]
45. Searching issues and pull requests [direct]
46. Setting up your project for healthy contributions [direct]
47. Using templates to encourage useful issues and pull requests [direct]
48. Maintaining your safety on GitHub [direct]
49. Make a contribution [direct]
50. Ask the GitHub community [direct]
51. Contact support [direct]
52. Expert services [direct]
53. Blog [direct]
54. Terms [direct]
55. Privacy [direct]
56. Status [direct]
57. Pricing [direct]