@@ -41,7 +41,7 @@ Add this Action as a [step][job-step] to your project's GitHub Action Workflow f
41
41
``` yaml
42
42
- name : Send GitHub Action trigger data to Slack workflow
43
43
id : slack
44
- uses : slackapi/slack-github-action@v1.24 .0
44
+ uses : slackapi/slack-github-action@v1.25 .0
45
45
env :
46
46
SLACK_WEBHOOK_URL : ${{ secrets.SLACK_WEBHOOK_URL }}
47
47
` ` `
51
51
` ` ` yaml
52
52
- name : Send custom JSON data to Slack workflow
53
53
id : slack
54
- uses : slackapi/slack-github-action@v1.24 .0
54
+ uses : slackapi/slack-github-action@v1.25 .0
55
55
with :
56
56
# This data can be any valid JSON from a previous step in the GitHub Action
57
57
payload : |
69
69
` ` ` yaml
70
70
- name: Send custom JSON data to Slack workflow
71
71
id: slack
72
- uses: slackapi/slack-github-action@v1.24 .0
72
+ uses: slackapi/slack-github-action@v1.25 .0
73
73
with:
74
74
payload-file-path: "./payload-slack-content.json"
75
75
env:
@@ -95,7 +95,7 @@ Add this Action as a [step][job-step] to your project's GitHub Action Workflow f
95
95
` ` ` yaml
96
96
- name: Post to a Slack channel
97
97
id: slack
98
- uses: slackapi/slack-github-action@v1.24 .0
98
+ uses: slackapi/slack-github-action@v1.25 .0
99
99
with:
100
100
# Slack channel id, channel name, or user id to post message.
101
101
# See also: https://api.slack.com/methods/chat.postMessage#channels
@@ -112,7 +112,7 @@ Using JSON payload for constructing a message is also available:
112
112
` ` ` yaml
113
113
- name: Post to a Slack channel
114
114
id: slack
115
- uses: slackapi/slack-github-action@v1.24 .0
115
+ uses: slackapi/slack-github-action@v1.25 .0
116
116
with:
117
117
# Slack channel id, channel name, or user id to post message.
118
118
# See also: https://api.slack.com/methods/chat.postMessage#channels
@@ -143,7 +143,7 @@ Please note that **the message update step does not accept a channel name.** Set
143
143
144
144
` ` ` yaml
145
145
- id: slack
146
- uses: slackapi/slack-github-action@v1.24 .0
146
+ uses: slackapi/slack-github-action@v1.25 .0
147
147
with:
148
148
# The following message update step does not accept a channel name.
149
149
# Setting a channel ID here for consistency is highly recommended.
@@ -167,7 +167,7 @@ Please note that **the message update step does not accept a channel name.** Set
167
167
}
168
168
env:
169
169
SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN}}
170
- - uses: slackapi/slack-github-action@v1.24 .0
170
+ - uses: slackapi/slack-github-action@v1.25 .0
171
171
with:
172
172
# Unlike the step posting a new message, this step does not accept a channel name.
173
173
# Please use a channel ID, not a name here.
@@ -213,7 +213,7 @@ Incoming Webhooks conform to the same rules and functionality as any of Slack's
213
213
` ` ` yaml
214
214
- name: Send custom JSON data to Slack workflow
215
215
id: slack
216
- uses: slackapi/slack-github-action@v1.24 .0
216
+ uses: slackapi/slack-github-action@v1.25 .0
217
217
with:
218
218
# For posting a rich message using Block Kit
219
219
payload: |
@@ -241,7 +241,7 @@ If you need to use a proxy to connect with Slack, you can use the `HTTPS_PROXY`
241
241
` ` ` yaml
242
242
- name: Post to a Slack channel via a proxy
243
243
id: slack
244
- uses: slackapi/slack-github-action@v1.24 .0
244
+ uses: slackapi/slack-github-action@v1.25 .0
245
245
with:
246
246
channel-id: 'CHANNEL_ID'
247
247
slack-message: 'This message was sent through a proxy'
0 commit comments