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
Supporting an array type for the channel-id property seems like a reasonable feature, I went ahead and labeled the issue as an enhancement.
In the mean time I believe using something like multiple steps in a job could be a valid work around for the issue
on: [push]jobs:
new_push_job:
runs-on: ubuntu-latestname: Post to slack channelssteps:
- name: Publish to slack channel A via bot tokenid: slackuses: slackapi/slack-github-action@v1.21.0with:
channel-id: 'CHANNEL_ID_A'slack-message: 'posting from a github action to channel A!'env:
SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
- name: Publish to slack channel B via bot tokenid: slackuses: slackapi/slack-github-action@v1.21.0with:
channel-id: 'CHANNEL_ID_B'slack-message: 'posting from a github action to channel B!'env:
SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
Thanks! What about message updates. How does it work in this case? I tried passing multiple channels and then updating the messages with the same returned ts. It only updates the message in one of the channels and returns this error: Error: An API error occurred: message_not_found.
Description
The
channel-id
input supports a single channel ID. Can this be updated to support multiple comma-separated channel ID's?What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)The text was updated successfully, but these errors were encountered: