Skip to content

chore: 为提出新功能或改进建议的 issue 模版添加必填描述和日志文件限制#1772

Merged
MistEO merged 2 commits intoMaaEnd:v2from
ocsin1:ci/issue
Mar 31, 2026
Merged

chore: 为提出新功能或改进建议的 issue 模版添加必填描述和日志文件限制#1772
MistEO merged 2 commits intoMaaEnd:v2from
ocsin1:ci/issue

Conversation

@ocsin1
Copy link
Copy Markdown
Member

@ocsin1 ocsin1 commented Mar 31, 2026

Summary by Sourcery

在功能请求问题模板中强制填写更完整的信息,以改进问题分诊流程,并更好地区分功能请求与缺陷(bug)。

新功能:

  • 在功能请求问题模板中新增必填的日志上传字段,并提供导出和附加日志文件的指导。

改进:

  • 将功能请求问题模板中的功能描述字段设为必填项。
  • 明确“附加信息”字段的用途,强调用于提供软件和游戏截图,而非日志。
Original summary in English

Summary by Sourcery

Enforce more complete information in the feature request issue template to improve triage and distinguish feature requests from bugs.

New Features:

  • Add a mandatory logs upload field to the feature request issue template with guidance on exporting and attaching log files.

Enhancements:

  • Make the feature description field in the feature request issue template mandatory.
  • Clarify the purpose of the additional information field to focus on software and game screenshots rather than logs.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

你好——我发现了 1 个问题,并提供了一些总体反馈:

  • 将日志字段设为功能请求必填项可能有点过于严格,因为很多纯功能想法本身不会有相关日志;建议改为可选,或者仅在涉及具体行为时才是必填。
  • 日志文本框的描述大量强调“区分缺陷和新功能”,在一个专门用于功能请求的模板里可能会让用户感到困惑;建议收紧文案,重点说明在什么情况下日志对功能提案真正有帮助。
  • 在更新后的 additional 描述中似乎有一个小拼写错误(“软件和游戏截图截图等”);建议删去重复的“截图”。
给 AI Agent 的提示
Please address the comments from this code review:

## Overall Comments
- Making the logs field required for feature requests may be too strict, since many pure feature ideas won’t have relevant logs; consider making it optional or conditionally required based on whether behavior is involved.
- The logs textarea description heavily references distinguishing bugs vs new features, which might confuse users in a feature-request-specific template; consider tightening the wording to focus on when logs are truly useful for feature proposals.
- There appears to be a small typo in the updated `additional` description (`软件和游戏截图截图等`); consider removing the duplicated “截图”.

## Individual Comments

### Comment 1
<location path=".github/ISSUE_TEMPLATE/feature_request.yml" line_range="39" />
<code_context>
     attributes:
       label: 其他信息
-      description: 日志、截图等
+      description: 软件和游戏截图截图等
     validations:
       required: false
</code_context>
<issue_to_address>
**nitpick (typo):** There’s a duplicated word in the Chinese description for additional information.

The phrase "软件和游戏截图截图等" repeats "截图". Consider changing it to "软件和游戏截图等" or "软件和游戏的截图等".

```suggestion
      description: 软件和游戏截图等
```
</issue_to_address>

Sourcery 对开源项目免费——如果你觉得我们的代码评审对你有帮助,欢迎分享 ✨
帮我变得更有用!请在每条评论上点 👍 或 👎,我会根据你的反馈改进后续评审。
Original comment in English

Hey - I've found 1 issue, and left some high level feedback:

  • Making the logs field required for feature requests may be too strict, since many pure feature ideas won’t have relevant logs; consider making it optional or conditionally required based on whether behavior is involved.
  • The logs textarea description heavily references distinguishing bugs vs new features, which might confuse users in a feature-request-specific template; consider tightening the wording to focus on when logs are truly useful for feature proposals.
  • There appears to be a small typo in the updated additional description (软件和游戏截图截图等); consider removing the duplicated “截图”.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Making the logs field required for feature requests may be too strict, since many pure feature ideas won’t have relevant logs; consider making it optional or conditionally required based on whether behavior is involved.
- The logs textarea description heavily references distinguishing bugs vs new features, which might confuse users in a feature-request-specific template; consider tightening the wording to focus on when logs are truly useful for feature proposals.
- There appears to be a small typo in the updated `additional` description (`软件和游戏截图截图等`); consider removing the duplicated “截图”.

## Individual Comments

### Comment 1
<location path=".github/ISSUE_TEMPLATE/feature_request.yml" line_range="39" />
<code_context>
     attributes:
       label: 其他信息
-      description: 日志、截图等
+      description: 软件和游戏截图截图等
     validations:
       required: false
</code_context>
<issue_to_address>
**nitpick (typo):** There’s a duplicated word in the Chinese description for additional information.

The phrase "软件和游戏截图截图等" repeats "截图". Consider changing it to "软件和游戏截图等" or "软件和游戏的截图等".

```suggestion
      description: 软件和游戏截图等
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
@ocsin1 ocsin1 linked an issue Mar 31, 2026 that may be closed by this pull request
@MistEO MistEO changed the title ci: 为提出新功能或改进建议的 issue 模版添加必填描述和日志文件限制 chore: 为提出新功能或改进建议的 issue 模版添加必填描述和日志文件限制 Mar 31, 2026
@MistEO MistEO merged commit 8d1117b into MaaEnd:v2 Mar 31, 2026
1 check passed
@ocsin1 ocsin1 deleted the ci/issue branch March 31, 2026 09:06
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