The Lock Issue bot automatically locks the conversation when an issue is closed. When a conversation is locked, only collaborators can add comments to it. Optionally the bot can also post a comment to the issue first, giving you an opportunity to explain to contributors why the conversation is locked.
Placing the following configuration in .devbots/lock-issue.yml in your repository will instruct the bot to post a comment to the issue and then lock the conversation.
enabled: true
comment: >
This issue's conversation has been locked. Please file
a [new issue](/user/project/issues/new) if you would
like to continue the discussion.
The Lock Issue bot automatically locks the conversation when an issue is closed. When a conversation is locked, only collaborators can add comments to it. Optionally the bot can also post a comment to the issue first, giving you an opportunity to explain to contributors why the conversation is locked.
enabled |
boolean | whether the bot is active or not |
comment |
string | the comment to add before the conversation is locked |
The comment option may contain GitHub MarkDown and emojis.
Placing the following configuration in .devbots/lock-issue.yml will make the bot immediately lock the conversation as soon as the issue is closed.
enabled: true
Placing the following configuration in .devbots/lock-issue.yml will make the bot first post a comment and then lock the conversation when the issue is closed.
enabled: true
comment: >
This issue's conversation has been locked. Please
file a [new issue](/user/project/issues/new) if you would
like to continue the discussion.