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
Hey @dstrates and those following along 👋 We don't support a specific input parameter for the reply_broadcast parameter but this can be included in the payload with a message to decide if the threaded message should be broadcast:
This found better support in the @v2.0.0 release, where the payload is now sent to a provided Slack API method like so:
- name: Post the first example messageuses: slackapi/[email protected]id: examplewith:
method: chat.postMessagetoken: ${{ secrets.SLACK_BOT_TOKEN }}payload: | channel: ${{ secrets.SLACK_CHANNEL_ID }} text: "Something started..."
- name: Broadcast a reply to the exampleuses: slackapi/[email protected]with:
method: chat.postMessagetoken: ${{ secrets.SLACK_BOT_TOKEN }}payload: | channel: ${{ secrets.SLACK_CHANNEL_ID }} reply_broadcast: true thread_ts: "${{ steps.example.outputs.ts }}" text: "Status update: LGTM!"
This is a super great suggestion and I'll close this issue now that we're supporting it! But please write back if you're finding strangeness with these changes 🙏
Description
Would like the ability to send a threaded reply notification to a channel with thread_broadcast.
This could be surfaced as an optional flag to broadcast the threaded message to the channel, as mentioned in #119
What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:
Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.
The text was updated successfully, but these errors were encountered: