Repository navigation
chore: add issue templates for bugs and feature requests - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
改动
.github/ISSUE_TEMPLATE/bug_report.yml:结构化表单。字段按本项目真实架构设计——涉及组件(入站/出站/强亲和/new-api 透传/控制台/部署/CI)、版本(tag 或 digest)、部署方式、运行环境、复现步骤、期望与实际、日志与channel_affinity.key_source、已脱敏的配置片段,最后是脱敏与查重确认。自动打bug标签。.github/ISSUE_TEMPLATE/feature_request.yml:以「要解决什么问题」为核心,附影响范围、是否愿意提 PR。自动打enhancement标签。.github/ISSUE_TEMPLATE/config.yml:保留自由发问入口(blank_issues_enabled: true),并把部署文档与 CONTRIBUTING 挂为联系链接。为什么保留 blank issue
现有 issue(如 #3 的设计设想)是长篇自由讨论,硬塞进表单反而不合适,所以两个模板之外仍允许空白 issue。
验证
本地按 issue form schema 校验过:顶层字段、body 元素类型、
attributes.label、validations.required类型、dropdown/checkboxes 的 options 结构、id 唯一性,全部通过。