-
Notifications
You must be signed in to change notification settings - Fork 4.9k
chore: auto issue label #18132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: auto issue label #18132
Conversation
Walkthrough本次变更主要针对 GitHub Issue 模板配置文件,统一为“Bug 报告”和“功能增强”模板新增了“相关领域(area)”和“使用框架(framework)”下拉选项,并在“功能增强”模板中增加了“平台(platform)”复选框。部分字段描述和标签也进行了调整,同时同步更新了自动标签配置以支持新领域分类。 Changes
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 字段自动打标签
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ 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)
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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
📒 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
才能成功应用。请确认:
- 以上所有标签均已由管理员在 Settings → Labels 中创建。
- 命名保持一致(区分大小写)。
- 当前仅
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
,用户选择该项时不会有任何标签被打上。若期望落入 “待分类” 标签,可显式配置;否则可考虑去除该虚拟选项。
这个 PR 做了什么? (简要描述所做更改)
这个 PR 是什么类型? (至少选择一个)
这个 PR 涉及以下平台:
Summary by CodeRabbit