You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,23 @@ All notable changes to this project will be documented in this file.
4
4
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
5
5
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
6
6
7
+
# 2.15.0
8
+
9
+
### What's new?
10
+
11
+
Added the ability to change the default close message via the introduction of two config variables.
12
+
13
+
-`thread_close_response` - when someone closes the thread.
14
+
-`thread_self_close_response` - when the recipient closes their own thread.
15
+
16
+
They will be provided by string variables that you can incorporate into them:
17
+
18
+
-`closer` - the user object that closed the thread.
19
+
-`logkey` - the key for the thread logs e.g. (`5219ccc82ad4`)
20
+
-`loglink` - the full link to the thread logs e.g. (`https://logwebsite.com/logs/5219ccc82ad4`)
21
+
22
+
Example usage would be: ``?config set thread_close_message {closer.mention} closed the thread, here is the link to your logs: [**`{logkey}`**]({loglink})``
0 commit comments