-
Notifications
You must be signed in to change notification settings - Fork 60.1k
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: add chinese template #4984
Conversation
@RubuJam is attempting to deploy a commit to the NextChat Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughThe changes introduce new templates for GitHub issue reports and pull requests. Specific templates are created for bug reports and feature requests, available in both English and Chinese. These templates standardize the information that users need to provide, enhancing clarity and consistency in issue and feature request submissions. Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configration 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: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (5)
- .github/ISSUE_TEMPLATE/1_bug_report.yml (1 hunks)
- .github/ISSUE_TEMPLATE/1_bug_report_cn.yml (1 hunks)
- .github/ISSUE_TEMPLATE/2_feature_request.yml (1 hunks)
- .github/ISSUE_TEMPLATE/2_feature_request_cn.yml (1 hunks)
- .github/PULL_REQUEST_TEMPLATE.md (1 hunks)
Files skipped from review due to trivial changes (3)
- .github/ISSUE_TEMPLATE/2_feature_request.yml
- .github/ISSUE_TEMPLATE/2_feature_request_cn.yml
- .github/PULL_REQUEST_TEMPLATE.md
Additional comments not posted (22)
.github/ISSUE_TEMPLATE/1_bug_report_cn.yml (11)
1-4
: Template Metadata: Looks GoodThe name, description, title, and labels fields are correctly defined and provide a clear indication of the purpose of the template.
6-19
: Dropdown for Deployment Method: Comprehensive OptionsThe dropdown for deployment method includes a comprehensive list of options, covering most common methods.
20-24
: Input for Software Version: Mandatory FieldThe input field for software version is correctly marked as required.
26-40
: Dropdown for System Environment: Comprehensive OptionsThe dropdown for system environment includes a comprehensive list of options, covering most common systems.
41-45
: Input for System Version: Mandatory FieldThe input field for system version is correctly marked as required.
47-57
: Dropdown for Browser: Comprehensive OptionsThe dropdown for browser includes a comprehensive list of options, covering most common browsers.
58-62
: Input for Browser Version: Mandatory FieldThe input field for browser version is correctly marked as required.
63-68
: Textarea for Issue Description: Clear InstructionsThe textarea for issue description provides clear instructions for the user.
69-73
: Textarea for Reproduction Steps: Clear InstructionsThe textarea for reproduction steps provides clear instructions for the user.
74-77
: Textarea for Expected Result: Clear InstructionsThe textarea for expected result provides clear instructions for the user.
78-80
: Textarea for Additional Information: Clear InstructionsThe textarea for additional information provides clear instructions for the user.
.github/ISSUE_TEMPLATE/1_bug_report.yml (11)
1-4
: Template Metadata: Looks GoodThe name, description, title, and labels fields are correctly defined and provide a clear indication of the purpose of the template.
6-19
: Dropdown for Deployment Method: Comprehensive OptionsThe dropdown for deployment method includes a comprehensive list of options, covering most common methods.
20-24
: Input for Version: Mandatory FieldThe input field for version is correctly marked as required.
26-40
: Dropdown for Operating System: Comprehensive OptionsThe dropdown for operating system includes a comprehensive list of options, covering most common systems.
41-45
: Input for System Version: Mandatory FieldThe input field for system version is correctly marked as required.
47-57
: Dropdown for Browser: Comprehensive OptionsThe dropdown for browser includes a comprehensive list of options, covering most common browsers.
58-62
: Input for Browser Version: Mandatory FieldThe input field for browser version is correctly marked as required.
63-68
: Textarea for Bug Description: Clear InstructionsThe textarea for bug description provides clear instructions for the user.
69-73
: Textarea for Recurrence Steps: Clear InstructionsThe textarea for recurrence steps provides clear instructions for the user.
74-77
: Textarea for Expected Behavior: Clear InstructionsThe textarea for expected behavior provides clear instructions for the user.
78-80
: Textarea for Additional Information: Clear InstructionsThe textarea for additional information provides clear instructions for the user.
新增中文模板的时候,是不是应该新加一个相同结构的yml,而不是把旧模板结构也改变了? |
When adding a new Chinese template, should I add a new yml with the same structure instead of changing the old template structure? |
我个人倾向于彻底重写整个模板,原有的感觉过于繁杂 已将
|
Personally, I prefer to completely rewrite the entire template. The original one feels too complicated.
|
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: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (4)
- .github/ISSUE_TEMPLATE/1_bug_report.yml (1 hunks)
- .github/ISSUE_TEMPLATE/1_bug_report_cn.yml (1 hunks)
- .github/ISSUE_TEMPLATE/2_feature_request.yml (1 hunks)
- .github/ISSUE_TEMPLATE/2_feature_request_cn.yml (1 hunks)
Files skipped from review as they are similar to previous changes (4)
- .github/ISSUE_TEMPLATE/1_bug_report.yml
- .github/ISSUE_TEMPLATE/1_bug_report_cn.yml
- .github/ISSUE_TEMPLATE/2_feature_request.yml
- .github/ISSUE_TEMPLATE/2_feature_request_cn.yml
Your build has completed! |
引入
PR
模板修改
问题报告
和功能请求
模板添加
问题报告
和功能请求
中文模版Introduce
PR
templateModify
Issues Report
andFeature Request
templatesAdd Chinese templates for
Issues Report
andFeature Request
Summary by CodeRabbit