WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Is there any way to use the rich_text_list format when working with blocks? #520

@Rebwon

Description

@Rebwon

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions