-
Notifications
You must be signed in to change notification settings - Fork 177
Open
Labels
auto-triage-skipPrevent this issue from being closed due to lack of activityPrevent this issue from being closed due to lack of activitybugSomething isn't workingSomething isn't workingquestionFurther information is requestedFurther information is requestedserver-side issue
Description
Hey folks, I'm trying to send a message with some markdown in it, but its not being honored.
According to the reference these should work?
https://api.slack.com/reference/block-kit/blocks#markdown
Here's my example with inline blocks
- name: Announce Release
uses: slackapi/[email protected]
with:
webhook: ${{ secrets.MY_SECRET }}
webhook-type: incoming-webhook
errors: true
payload: |
text: "New Release: Shared Helm Chart: 1.2.3"
blocks:
- type: header
text:
type: plain_text
text: ":tada: New Release: Shared Helm Chart: 1.2.3"
- type: divider
- type: section
text:
type: mrkdwn
text: "## :notebook: Release notes"
- type: section
text:
type: mrkdwn
text: Blah
- type: divider
- type: section
text:
type: mrkdwn
text: "** :computer: Release URL**"
- type: section
text:
type: mrkdwn
text: http://my_url.com
And this is what it ends up looking like:

I have also tried with a payload file:
GHA
- name: Announce Release
if: github.event_name == 'push' && github.ref == 'refs/heads/slack-releases3'
uses: slackapi/[email protected]
with:
payload-file-path: .github/workflows/payload.json
webhook: ${{ secrets.MY_SECRET }}
webhook-type: incoming-webhook
errors: true
JSON
{
"channel": "${{ env.SLACK_CHANNEL_ID }}",
"text": "Messages met made meetings meet",
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "# Slack notifications sound following the most recent commit pushed"
}
}
]
}
I would expect to be able to use bold and
HEADER
and other markdown fun in a block called mrkdwn.
Am I doing something wrong?
CRC-Mismatch
Metadata
Metadata
Assignees
Labels
auto-triage-skipPrevent this issue from being closed due to lack of activityPrevent this issue from being closed due to lack of activitybugSomething isn't workingSomething isn't workingquestionFurther information is requestedFurther information is requestedserver-side issue
