David Taylor 0522ad6414 FIX: Always use parent thread_ts for slack threads (#159) ... Previously we were using the `ts` of the previous message we sent to the thread. While this did work under some situations, it's not recommended in the Slack API docs, and can lead to some unexpected behavior (e.g. when one of the threaded messages is deleted). This commit updates our logic to always use Slack's returned `thread_ts`, which represents the thread's parent.		2023-01-26 12:18:48 +00:00
..
discord	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
flowdock	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
gitter	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
google	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
groupme	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
guilded	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
matrix	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
mattermost	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
rocketchat	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
slack	FIX: Always use parent thread_ts for slack threads (#159)	2023-01-26 12:18:48 +00:00
teams	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
telegram	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
webex	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00
zulip	DEV: Introduce syntax_tree for ruby formatting (#149)	2022-12-29 13:31:05 +01:00