slackapi/slack-github-action
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: remove confusing words around providing a payload to send

Browse Source
This commit is contained in:
@zimeg
2024-11-04 11:43:45 -08:00
parent 30943b5b49
commit 10260d319e
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -4
View File
@@ -54,8 +54,8 @@ Start in Slack to create a Slack workflow:
1. [Create a Slack workflow][wfb-create] that starts from a webhook.
2. Copy the webhook URL and [add it as a repository secret][repo-secret] called
`SLACK_WEBHOOK_URL`.
3. [Add this Action as a step][job-step] to your GitHub workflow and set the
input payload to send.
3. [Add this Action as a step][job-step] to your GitHub workflow and provide an
input payload to send to the webhook.
4. Configure your Slack workflow to use the payload variables sent from the
GitHub Action. You can then update the steps of the Slack workflow to use
these values in creative and clever ways.
@@ -144,8 +144,8 @@ setup should be similar for all methods:
**OAuth & Permissions** page.
5. Add the token as [a repository secret][repo-secret] called `SLACK_BOT_TOKEN`
or something similar and memorable.
6. [Add this Action as a step][job-step] to your GitHub workflow and set the
input payload to send.
6. [Add this Action as a step][job-step] to your GitHub workflow and provide an
input payload to send as a message.
Methods that require an app configuration token should gather this token from
the [app configuration token][config-tokens] settings instead of from a specific