Fix handling of thread_ts and reply_to_thread in Slack messages #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… thread_id for cm logic
|
Please mark whether you used Copilot to assist coding in this PR
|
… thread_id for cm logic
cyrus2281
force-pushed
the
cyrus/sessionID
branch
from
05b647b
to
da3c35f
Compare
cyrus2281
force-pushed
the
cyrus/sessionID
branch
from
da3c35f
to
dadf4db
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes an issue where the thread_ts and reply_to_thread values were not being properly handled in Slack messages. The commit "Passing slacks ts and thread_ts as is, and using reply_to_thread and thread_id for cm logic" ensures that the correct values are assigned to the thread_ts and reply_to_thread variables in the code. This resolves the problem of messages not being sent to the correct threads in Slack.