Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#520 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
github-actions, javascript
领域
ci-cd

调研方向

先从 blocks 文档和 GitHub Actions release 的 published trigger 开始,然后检查 release-note Markdown 是如何发送到 Slack 的。确认是否支持 rich_text_list,并记录受支持的路径或 feature request 的范围。

由索引模型根据 Issue 内容生成。

描述

question

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.

主要语言
JavaScript
星标
1.4k
派生
200
平均合并
1 分钟
30 天内合并 PR
8

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

slackapi/slack-github-action 的其他 Issue

查看 slackapi/slack-github-action 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。