Skip to content

Conversation

ianzone
Copy link
Contributor

@ianzone ianzone commented Jul 11, 2025

这个 PR 做了什么? (简要描述所做更改)
issue中让“所有平台”和“所有小程序”也可以打标签。
各种 action 依赖项升级

这个 PR 是什么类型? (至少选择一个)

  • 错误修复 (Bugfix) issue: fix #
  • 新功能 (Feature)
  • 代码重构 (Refactor)
  • TypeScript 类型定义修改 (Types)
  • 文档修改 (Docs)
  • 代码风格更新 (Code style update)
  • 构建优化 (Chore)
  • 其他,请描述 (Other, please describe):

这个 PR 涉及以下平台:

  • 所有平台
  • Web 端(H5)
  • 移动端(React-Native)
  • 鸿蒙(Harmony)
  • 鸿蒙容器(Harmony Hybrid)
  • ASCF 元服务
  • 快应用(QuickApp)
  • 所有小程序
  • 微信小程序
  • 企业微信小程序
  • 京东小程序
  • 百度小程序
  • 支付宝小程序
  • 支付宝 IOT 小程序
  • 钉钉小程序
  • QQ 小程序
  • 飞书小程序
  • 快手小程序
  • 头条小程序

Summary by CodeRabbit

  • 文档

    • 更新了贡献指南中的代码块语法高亮,提升可读性。
    • 优化了 GitHub Issue 模板说明文字和部分描述,增加对贡献指南的引用链接。
    • 调整了“生态建设 Ecosystem”联系说明文本,细化表达。
  • 杂项

    • 改进了 GitHub Issue Labeler 的平台标签匹配逻辑,支持更广泛的平台关键词。
    • 升级了 Node.js 测试工作流中的 Codecov 上传步骤至新版 Action。
    • 更新并统一了多个 GitHub Actions 工作流中相关 Action 的版本,修正缓存键拼写错误,提升稳定性。
    • 优化了自动审查工作流中提交信息的环境变量处理,确保多行内容正确保存。

Copy link

coderabbitai bot commented Jul 11, 2025

"""

Walkthrough

本次更改主要涉及 GitHub Issue 模板、标签配置、工作流和贡献指南文档。具体包括调整 Issue 模板的标题和标签、优化描述文案、扩展自动标签器的匹配范围、升级 Codecov Action 版本,以及修改文档代码块的语法高亮标记。

Changes

文件/路径 变更简述
.github/ISSUE_TEMPLATE/bug_report.yml
.github/ISSUE_TEMPLATE/feature_request.yml
移除 title 字段,调整标签,扩展贡献意愿选项描述,优化部分描述文本。
.github/ISSUE_TEMPLATE/config.yml 更新“生态建设 Ecosystem”链接描述文本,结尾增加感叹号。
.github/advanced-issue-labeler.yml 各平台标签 keys 数组新增“所有平台”,小程序平台新增“所有小程序”,扩大标签自动匹配范围。
.github/workflows/nodejs.yml
.github/workflows/build-rust-binding.yml
.github/workflows/build-rust-wasm.yml
.github/workflows/publish.yml
.github/workflows/sync-components-types.yml
.github/workflows/auto-review.yml
多个工作流中升级 GitHub Actions 相关 action 版本(如 codecov/codecov-action、pnpm/action-setup、actions/cache),修正缓存键拼写错误,调整环境变量赋值方式,移除部分无用配置。
CONTRIBUTING.md 贡献指南代码块语法标记由 json 改为 js,内容未变。
.github/dependabot.yml 依赖更新配置格式调整,扩展 @types/node 忽略版本范围,保持其他配置结构不变。

Sequence Diagram(s)

sequenceDiagram
    participant User as 用户
    participant GitHub as GitHub
    participant Labeler as 标签器

    User->>GitHub: 提交 Issue(选择模板)
    GitHub->>Labeler: 根据模板内容自动打标签(包含所有平台/所有小程序等新 key)
    Labeler-->>GitHub: 返回匹配标签
    GitHub-->>User: 展示带新标签的 Issue
Loading

Possibly related PRs

Suggested reviewers

  • tutuxxx
  • yoyo837

Poem

🐇
模板焕新春,标签更智能,
贡献指南亮,代码高亮真。
工作流升级快,
生态描述添感叹,
代码世界更清新!

"""

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai bot requested review from tutuxxx and yoyo837 July 11, 2025 13:57
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
.github/ISSUE_TEMPLATE/config.yml (1)

17-17: 保持标点风格一致性
此处仅新增了一个感叹号,整体无功能性影响,但建议检查其它模板的 about 字段,确保同类描述的结尾标点一致,避免视觉不统一。

.github/ISSUE_TEMPLATE/bug_report.yml (1)

104-104: 链接语法 OK,但可考虑加空格避免渲染歧义
当前 Markdown 渲染正常,不过在 “[(贡献指南)]” 前后保留空格能进一步降低意外解析风险。

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9c58e28 and 68e2d94.

📒 Files selected for processing (6)
  • .github/ISSUE_TEMPLATE/bug_report.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/config.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/feature_request.yml (2 hunks)
  • .github/advanced-issue-labeler.yml (1 hunks)
  • .github/workflows/nodejs.yml (1 hunks)
  • CONTRIBUTING.md (1 hunks)
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: ianzone
PR: NervJS/taro#17937
File: .github/workflows/issue-labeler.yml:31-31
Timestamp: 2025-07-01T15:46:08.457Z
Learning: stefanbuck/github-issue-parser@v3 GitHub Action 的输出字段名称是 `jsonString`,不是 `json`。在工作流中应该使用 `${{ steps.issue-parser.outputs.jsonString }}` 来引用解析后的 JSON 数据。
Learnt from: ianzone
PR: NervJS/taro#17937
File: .github/advanced-issue-labeler.yml:17-63
Timestamp: 2025-07-01T15:49:00.336Z
Learning: In GitHub repositories, labels must be created by repository administrators before they can be configured in advanced-issue-labeler.yml. The labeler configuration can only map to existing labels, so missing platform options like "ASCF 元服务" and "支付宝 IOT 小程序" require admin action to create corresponding labels first.
CONTRIBUTING.md (1)
Learnt from: ianzone
PR: NervJS/taro#17842
File: packages/jest-helper/tsconfig.json:9-9
Timestamp: 2025-06-23T00:09:31.233Z
Learning: 在 jest-helper 包中,src 目录下没有 __tests__ 测试目录,只包含 resolver.ts、sequencer.ts 和 snapshot 目录。不要假设包中存在测试目录结构。
.github/ISSUE_TEMPLATE/feature_request.yml (1)
Learnt from: ianzone
PR: NervJS/taro#17937
File: .github/advanced-issue-labeler.yml:17-63
Timestamp: 2025-07-01T15:49:00.336Z
Learning: In GitHub repositories, labels must be created by repository administrators before they can be configured in advanced-issue-labeler.yml. The labeler configuration can only map to existing labels, so missing platform options like "ASCF 元服务" and "支付宝 IOT 小程序" require admin action to create corresponding labels first.
.github/advanced-issue-labeler.yml (1)
Learnt from: ianzone
PR: NervJS/taro#17937
File: .github/advanced-issue-labeler.yml:17-63
Timestamp: 2025-07-01T15:49:00.336Z
Learning: In GitHub repositories, labels must be created by repository administrators before they can be configured in advanced-issue-labeler.yml. The labeler configuration can only map to existing labels, so missing platform options like "ASCF 元服务" and "支付宝 IOT 小程序" require admin action to create corresponding labels first.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: Build Rust Binding / stable - aarch64-apple-darwin
  • GitHub Check: Build Rust Binding / stable - x86_64-apple-darwin
  • GitHub Check: Build Rust Binding / stable - x86_64-unknown-linux-gnu
  • GitHub Check: Build Rust Binding / stable - x86_64-pc-windows-msvc
  • GitHub Check: Build Rust WASM / stable - wasm32-wasi
🔇 Additional comments (4)
.github/workflows/nodejs.yml (1)

118-150: 确认 Codecov Action v5 的参数兼容性
已将 codecov/codecov-action 升级至 v5,但 v5 对若干输入参数及默认行为(如 fail_ci_if_errorupload_name 等)有细微变动。请确认:

  1. 现有 flagsfilestoken 参数在 v5 中仍被支持且含义一致。
  2. 如需保持遇到上传失败即 CI 报错的语义,请显式添加 fail_ci_if_error: true
  3. 若仓库为公有仓库,可考虑去掉 token,以减少权限暴露。

示例修订:

- uses: codecov/codecov-action@v5
+ uses: codecov/codecov-action@v5
+ with:
+   fail_ci_if_error: true
CONTRIBUTING.md (1)

64-71: 代码块语言高亮已更新,👍
json 改为 js 更贴合实际文件类型,阅读体验更佳。

.github/ISSUE_TEMPLATE/feature_request.yml (2)

25-25: 措辞优化已确认,无需进一步调整
调整后的描述更准确,保持现有实现即可。


38-38: 请确认复选框标签中的 Markdown 链接渲染效果
Issue Forms 的复选框标签理论上支持 Markdown,但不同渲染环境可能仅显示纯文本。建议在 PR 界面预览模板,确保链接正常可点击,避免用户界面混淆。

Copy link

codecov bot commented Jul 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.98%. Comparing base (9c58e28) to head (0a5087f).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #17993   +/-   ##
=======================================
  Coverage   54.98%   54.98%           
=======================================
  Files         417      417           
  Lines       21693    21693           
  Branches     5383     5358   -25     
=======================================
  Hits        11928    11928           
- Misses       8084     8121   +37     
+ Partials     1681     1644   -37     
Flag Coverage Δ
taro-cli 72.42% <ø> (ø)
taro-runtime 59.87% <ø> (ø)
taro-web 53.19% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 16 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/auto-review.yml (2)

21-26: 写入 $GITHUB_ENV 的脚本可以更简洁并避免潜在转义问题
当前通过 echo 拼接 here-doc,在包含特殊字符(如 \, $, `)或极端情况下 commit message 内部本身出现 EOF 时仍有概率被误解析。可用 printf 配合显式 here-doc 令实现更健壮,示例:

-          {
-            echo "commit_msg<<EOF"
-            echo "${COMMIT_MESSAGE}"
-            echo "EOF"
-          } >> "$GITHUB_ENV"
+          {
+            printf 'commit_msg<<EOF\n%s\nEOF\n' "$COMMIT_MESSAGE"
+          } >> "$GITHUB_ENV"

同时推荐统一使用大写环境变量(如 COMMIT_MSG),以符合常见 POSIX 约定。


31-31: 条件判断可改为不区分大小写,提高容错
目前 contains(env.commit_msg, '[auto review]') 仅匹配完全小写形式;若提交信息写成 [Auto Review] 将被漏判。可利用 toLower() 进行大小写归一化:

-        if: contains( env.commit_msg , '[auto review]' ) || contains(github.event.pull_request.title, '[auto review]')
+        if: contains( toLower(env.commit_msg) , '[auto review]' ) || contains( toLower(github.event.pull_request.title) , '[auto review]' )
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 68e2d94 and 0a5087f.

📒 Files selected for processing (7)
  • .github/dependabot.yml (1 hunks)
  • .github/workflows/auto-review.yml (1 hunks)
  • .github/workflows/build-rust-binding.yml (2 hunks)
  • .github/workflows/build-rust-wasm.yml (1 hunks)
  • .github/workflows/nodejs.yml (3 hunks)
  • .github/workflows/publish.yml (2 hunks)
  • .github/workflows/sync-components-types.yml (1 hunks)
✅ Files skipped from review due to trivial changes (5)
  • .github/workflows/build-rust-wasm.yml
  • .github/workflows/publish.yml
  • .github/workflows/sync-components-types.yml
  • .github/dependabot.yml
  • .github/workflows/build-rust-binding.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/nodejs.yml
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: ianzone
PR: NervJS/taro#17993
File: .github/advanced-issue-labeler.yml:20-63
Timestamp: 2025-07-11T14:04:05.533Z
Learning: 在 NervJS/taro 项目的 .github/advanced-issue-labeler.yml 中,平台标签被设计为可以多个共存。当用户选择"所有平台"时,系统会同时应用多个平台标签(如 T-h5, T-rn, T-weapp 等),这是期望的行为而非冲突。同样,"所有小程序"也会为小程序相关的标签应用多个标签。这种设计有助于跨平台问题的管理和维护者关注。
Learnt from: ianzone
PR: NervJS/taro#17937
File: .github/workflows/issue-labeler.yml:31-31
Timestamp: 2025-07-01T15:46:08.457Z
Learning: stefanbuck/github-issue-parser@v3 GitHub Action 的输出字段名称是 `jsonString`,不是 `json`。在工作流中应该使用 `${{ steps.issue-parser.outputs.jsonString }}` 来引用解析后的 JSON 数据。
Learnt from: ianzone
PR: NervJS/taro#17937
File: .github/advanced-issue-labeler.yml:17-63
Timestamp: 2025-07-01T15:49:00.336Z
Learning: In GitHub repositories, labels must be created by repository administrators before they can be configured in advanced-issue-labeler.yml. The labeler configuration can only map to existing labels, so missing platform options like "ASCF 元服务" and "支付宝 IOT 小程序" require admin action to create corresponding labels first.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: Build Rust Binding / stable - aarch64-apple-darwin
  • GitHub Check: Build Rust Binding / stable - x86_64-apple-darwin
  • GitHub Check: Build Rust Binding / stable - x86_64-unknown-linux-musl
  • GitHub Check: Build Rust Binding / stable - x86_64-unknown-linux-gnu
  • GitHub Check: Build Rust Binding / stable - x86_64-pc-windows-msvc
  • GitHub Check: Build Rust WASM / stable - wasm32-wasi
🔇 Additional comments (1)
.github/workflows/auto-review.yml (1)

28-28: 确认变量命名保持一致
此处引用的是 $commit_msg(小写),与上一步写入的同名变量保持一致即可;如采纳上一条建议改为大写,请同步调整这里的引用。

@ianzone
Copy link
Contributor Author

ianzone commented Jul 12, 2025

@yoyo837 一些CI升级,帮忙合一下哈

@ianzone ianzone deleted the action branch July 16, 2025 11:15
This was referenced Jul 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants