Skip to content

Conversation

ianzone
Copy link
Contributor

@ianzone ianzone commented Aug 3, 2025

这个 PR 做了什么? (简要描述所做更改)

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

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

这个 PR 涉及以下平台:

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

Summary by CodeRabbit

  • 文档
    • 更新了 Bug 报告和功能增强(原功能请求)Issue 模板,新增“相关领域”“使用框架”等下拉选项,并优化了描述与标签,提升问题分类和反馈准确性。
    • Issue 模板新增“平台”多选项,便于指定相关平台。
    • 优化了贡献选项的表述,更加贴合开源贡献场景。
    • 增强了自动标签配置,支持根据“领域”自动分配标签,提升 Issue 管理效率。

Copy link

coderabbitai bot commented Aug 3, 2025

Walkthrough

本次变更主要针对 GitHub Issue 模板配置文件,统一为“Bug 报告”和“功能增强”模板新增了“相关领域(area)”和“使用框架(framework)”下拉选项,并在“功能增强”模板中增加了“平台(platform)”复选框。部分字段描述和标签也进行了调整,同时同步更新了自动标签配置以支持新领域分类。

Changes

Cohort / File(s) Change Summary
Bug 报告模板优化
.github/ISSUE_TEMPLATE/bug_report.yml
新增“相关领域”和“使用框架”下拉字段,移除底部重复的“使用框架”字段,贡献代码复选框标签改为“开源贡献”。
功能增强模板优化
.github/ISSUE_TEMPLATE/feature_request.yml
模板名称由“功能请求”改为“功能增强”,新增“area”“framework”下拉字段与“platform”复选框,标签由“triage, feat”改为“enhancement”,字段描述调整。
自动标签配置扩展
.github/advanced-issue-labeler.yml
为 bug 报告和功能增强模板新增“area”标签类别,包含多个领域标签及关键词映射,结构与现有 platform、framework 保持一致,仅为新增。

Sequence Diagram(s)

sequenceDiagram
    participant User as 用户
    participant GitHub as GitHub Issue 模板
    participant Labeler as 自动标签器

    User->>GitHub: 填写 Bug 报告或功能增强 Issue
    GitHub->>User: 展示 area、framework(及 platform)下拉/复选项
    User->>GitHub: 选择相关领域、框架、平台等
    GitHub->>Labeler: 提交 Issue,触发自动标签配置
    Labeler->>GitHub: 根据 area、framework、platform 字段自动打标签
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • chore: issue template #17477:该 PR 为本次修改的 Issue 模板提供了初始版本,当前 PR 在其基础上进行字段和结构调整,两者直接相关。
  • auto issue label #17937:该 PR 与本次 PR 一样,涉及 Issue 模板中“area”与“framework”下拉字段的新增或调整,变更内容高度重叠。

Suggested reviewers

  • tutuxxx
  • yoyo837

Poem

兔子写表单,字段添新颜,
领域与平台,框架细细选。
自动标签跳,协作更方便,
Issue 模板新升级,
贡献开源乐无边!

((\
( -.-)
o_(")(")

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e0b1deb and d038c0d.

📒 Files selected for processing (1)
  • .github/ISSUE_TEMPLATE/feature_request.yml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/ISSUE_TEMPLATE/feature_request.yml
⏰ 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). (1)
  • GitHub Check: Testing on Node.js (windows-latest)
✨ 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 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 August 3, 2025 11:56
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/bug_report.yml (1)

44-54: 字段命名保持一致以避免混淆

在 Bug 模板中使用 label: 使用框架,Feature 模板中使用 label: 相关框架。建议统一两处文案,提升填写体验与后续统计的一致性。

.github/ISSUE_TEMPLATE/feature_request.yml (1)

44-67: 平台选项缺少对应 Label 映射

新增 “新的平台” 同样缺少 label 映射,且列表仍包含 ASCF 元服务 / 支付宝 IOT 小程序 等此前未创建的标签,自动贴标签仍会失败。请与仓库管理员确认并在 labeler 配置中补全映射或删除无效选项。

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d5b4e83 and e0b1deb.

📒 Files selected for processing (3)
  • .github/ISSUE_TEMPLATE/bug_report.yml (2 hunks)
  • .github/ISSUE_TEMPLATE/feature_request.yml (3 hunks)
  • .github/advanced-issue-labeler.yml (1 hunks)
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: ianzone
PR: NervJS/taro#17993
File: .github/advanced-issue-labeler.yml:20-63
Timestamp: 2025-07-11T14:04:05.557Z
Learning: 在 NervJS/taro 项目的 .github/advanced-issue-labeler.yml 中,平台标签被设计为可以多个共存。当用户选择"所有平台"时,系统会同时应用多个平台标签(如 T-h5, T-rn, T-weapp 等),这是期望的行为而非冲突。同样,"所有小程序"也会为小程序相关的标签应用多个标签。这种设计有助于跨平台问题的管理和维护者关注。
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.
📚 Learning: in github repositories, labels must be created by repository administrators before they can be confi...
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.

Applied to files:

  • .github/ISSUE_TEMPLATE/bug_report.yml
  • .github/advanced-issue-labeler.yml
  • .github/ISSUE_TEMPLATE/feature_request.yml
📚 Learning: 在 nervjs/taro 项目的 .github/advanced-issue-labeler.yml 中,平台标签被设计为可以多个共存。当用户选择"所有平台"时,系统会同时应用多个平台标签(如 t...
Learnt from: ianzone
PR: NervJS/taro#17993
File: .github/advanced-issue-labeler.yml:20-63
Timestamp: 2025-07-11T14:04:05.557Z
Learning: 在 NervJS/taro 项目的 .github/advanced-issue-labeler.yml 中,平台标签被设计为可以多个共存。当用户选择"所有平台"时,系统会同时应用多个平台标签(如 T-h5, T-rn, T-weapp 等),这是期望的行为而非冲突。同样,"所有小程序"也会为小程序相关的标签应用多个标签。这种设计有助于跨平台问题的管理和维护者关注。

Applied to files:

  • .github/ISSUE_TEMPLATE/bug_report.yml
  • .github/advanced-issue-labeler.yml
  • .github/ISSUE_TEMPLATE/feature_request.yml
📚 Learning: stefanbuck/github-issue-parser@v3 github action 的输出字段名称是 `jsonstring`,不是 `json`。在工作流中应该使用 `${{ steps...
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 数据。

Applied to files:

  • .github/ISSUE_TEMPLATE/bug_report.yml
🪛 YAMLlint (1.37.1)
.github/ISSUE_TEMPLATE/feature_request.yml

[error] 1-1: wrong new line character: expected \n

(new-lines)

⏰ 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 WASM / stable - wasm32-wasi
  • GitHub Check: Build Rust Binding / stable - x86_64-pc-windows-msvc
🔇 Additional comments (3)
.github/advanced-issue-labeler.yml (1)

77-106: 需预先创建对应 area 标签,否则自动贴标签会失败

新增加的 15 个 area 标签(如 A-api, A-cli, perf 等)在仓库中必须已存在,advanced-issue-labeler 才能成功应用。请确认:

  1. 以上所有标签均已由管理员在 Settings → Labels 中创建。
  2. 命名保持一致(区分大小写)。
    • 当前仅 perf 未采用 A- 前缀,风格上与其他标签不一致,建议统一为 A-perf 或放在单独类别。

未提前创建会导致 Action 运行报错并且新 Issue 无法自动分类。

.github/ISSUE_TEMPLATE/bug_report.yml (1)

24-43: area 下拉未设置 required,易被忽略

area 字段是后续自动贴标签的关键,但目前未加 validations.required: true,用户可跳过填写,导致无法匹配标签。建议补充必填校验:

   options:
@@
         - 性能问题
+    validations:
+      required: true

[ suggest_essential_refactor ]

.github/ISSUE_TEMPLATE/feature_request.yml (1)

14-32: “新的领域” 选项不会被自动贴标签

advanced-issue-labeler.yml 中未配置与 “新的领域” 对应的 keys,用户选择该项时不会有任何标签被打上。若期望落入 “待分类” 标签,可显式配置;否则可考虑去除该虚拟选项。

@yoyo837 yoyo837 merged commit ae19ce5 into NervJS:main Aug 4, 2025
14 checks passed
@ianzone ianzone deleted the label branch August 4, 2025 06:45
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