Is there any way to use the rich_text_list format when working with blocks?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
Research direction
Start with the documentation for blocks and the GitHub Actions release: published trigger, then review how release-note Markdown is sent to Slack. Confirm whether rich_text_list is supported and record the supported path or the scope of a feature request.
Written by the indexing model from the issue text.
Description
Hello,
Our team currently writes release notes in Markdown using GitHub Releases, and we’ve implemented a workflow that uses GitHub Actions with the release: published trigger to send those release notes to Slack.
From what I can tell from the documentation, section and header blocks are supported, but it seems that formats like rich_text_list are not available. Is that correct?
In Markdown, the -, *, and + markers are rendered as lists, but in Slack they are not displayed as lists. Because of this, we would like to parse the GitHub release note message ourselves and convert it into something that uses a rich_text_list-style format when sending it to Slack.
I’d like to ask whether you have any plans to support this kind of list formatting, and whether it is currently possible to achieve this in any way. Thank you.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 200
- Avg merge
- 2h 59m
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from slackapi/slack-github-action
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
slackapi/slack-github-action#667 ·
-
discussion security semver:major
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
slackapi/slack-github-action#621 · 1 comment · 1 reaction ·
-
dependencies question
slackapi/slack-github-action#671 · 2 comments · 1 assignee ·
-
needs info question
Difficulty 3/5 1-2 days Newbie friendliness 55/100
slackapi/slack-github-action#654 · 7 comments · 5 reactions ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
slackapi/slack-github-action#511 · 2 comments · 3 reactions ·
All issues in slackapi/slack-github-action
Similar issues
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·
-
bug p1 tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100