feat: add English contributor guide and update issue templates (#5300)

- Introduced a new English version of the contributor guide (CONTRIBUTING_EN.md) to enhance accessibility for non-Chinese speakers.
- Updated issue templates to use more specific labels (kind/bug, kind/enhancement, kind/question) for better categorization.
- Added a testing section in the developer guide to clarify testing procedures.

.github/ISSUE_TEMPLATE/#0_bug_report.yml

@@ -1,7 +1,7 @@
 name: 🐛 错误报告 (中文)
 description: 创建一个报告以帮助我们改进
 title: '[错误]: '
-labels: ['bug']
+labels: ['kind/bug']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/#1_feature_request.yml

@@ -1,7 +1,7 @@
 name: 💡 功能建议 (中文)
 description: 为项目提出新的想法
 title: '[功能]: '
-labels: ['enhancement']
+labels: ['kind/enhancement']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/#2_question.yml

@@ -1,7 +1,7 @@
 name: ❓ 讨论 & 提问 (中文)
 description: 寻求帮助、讨论问题、提出疑问等...
 title: '[讨论]: '
-labels: ['question']
+labels: ['kind/question']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/0_bug_report.yml

@@ -1,7 +1,7 @@
 name: 🐛 Bug Report (English)
 description: Create a report to help us improve
 title: '[Bug]: '
-labels: ['bug']
+labels: ['kind/bug']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/1_feature_request.yml

@@ -1,7 +1,7 @@
 name: 💡 Feature Request (English)
 description: Suggest an idea for this project
 title: '[Feature]: '
-labels: ['enhancement']
+labels: ['kind/enhancement']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/2_question.yml

@@ -1,7 +1,7 @@
 name: ❓ Discussion & Questions
 description: Seeking help, discussing issues, asking questions, etc...
 title: '[Discussion]: '
-labels: ['question']
+labels: ['kind/question']
 body:
   - type: markdown
     attributes:

.github/pull_request_template.md

@@ -1,30 +1,54 @@
-### Description
+<!-- Template from https://github.com/kubevirt/kubevirt/blob/main/.github/PULL_REQUEST_TEMPLATE.md?-->
+<!--  Thanks for sending a pull request!  Here are some tips for you:
+1. Consider creating this PR as draft: https://github.com/CherryHQ/cherry-studio/blob/main/CONTRIBUTING.md
+-->
 
-<!-- Please include a summary of the change and which issue is fixed. -->
-<!-- Please also include relevant motivation and context. -->
+### What this PR does
+
+Before this PR:
+
+After this PR:
+
+<!-- (optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: -->
 
-#### Which issue(s) this PR fixes:
-<!-- Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. -->
 Fixes #
 
+### Why we need it and why it was done in this way
+
+The following tradeoffs were made:
+
+The following alternatives were considered:
+
+Links to places where the discussion took place: <!-- optional: slack, other GH issue, mailinglist, ... -->
+
+### Breaking changes
+
+<!-- optional -->
+
+If this PR introduces breaking changes, please describe the changes and the impact on users.
+
+### Special notes for your reviewer
+
+<!-- optional -->
+
 ### Checklist
 
-- [ ] I have explained the need for this PR and the problem it solves
-- [ ] I have explained the changes or the new features added to this PR
-- [ ] I have added tests corresponding to this change
-- [ ] I have updated the documentation to reflect this change
-- [ ] I have verified that this change is backward compatible
+This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
+Approvers are expected to review this list.
 
-<!--
+- [ ] PR: The PR description is expressive enough and will help future contributors
+- [ ] Code: [Write code that humans can understand](https://en.wikiquote.org/wiki/Martin_Fowler#code-for-humans) and [Keep it simple](https://en.wikipedia.org/wiki/KISS_principle)
+- [ ] Refactor: You have [left the code cleaner than you found it (Boy Scout Rule)](https://learning.oreilly.com/library/view/97-things-every/9780596809515/ch08.html)
+- [ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
+- [ ] Documentation: A [user-guide update](https://docs.cherry-ai.com) was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature.
 
-Note
-
-1. Mark the PR as draft until it's ready to be reviewed.
-2. Always add/update tests for any changes unless you have a good reason.
-3. Always update the documentation to reflect the changes made in the PR.
-4. Make a new commit to resolve conversations instead of `push -f`.
-5. To resolve merge conflicts, merge master instead of rebasing.
-6. Use "request review" to notify the reviewer after making changes.
-7. Only a reviewer can mark a conversation as resolved.
+### Release note
 
+<!--  Write your release note:
+1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required".
+2. If no release note is required, just write "NONE".
 -->
+
+```release-note
+
+```

CONTRIBUTING.md

@@ -1,5 +1,7 @@
 # Cherry Studio 贡献者指南
 
+[**中文**](./CONTRIBUTING.md) | [**English**](./CONTRIBUTING_EN.md)
+
 欢迎来到 Cherry Studio 的贡献者社区！我们致力于将 Cherry Studio 打造成一个长期提供价值的项目，并希望邀请更多的开发者加入我们的行列。无论您是经验丰富的开发者还是刚刚起步的初学者，您的贡献都将帮助我们更好地服务用户，提升软件质量。
 
 ## 如何贡献
@@ -20,20 +22,50 @@
 
 7. **推广使用**：通过博客、社交媒体等渠道推广 Cherry Studio，吸引更多用户和开发者。
 
+## 开始之前
+
+请确保阅读了[行为准则](CODE_OF_CONDUCT.md)和[LICENSE](LICENSE)。
+
 ## 开始贡献
 
-1. **Fork 仓库**：在 GitHub 上 fork 我们的仓库，并将其克隆到本地。
+为了让您更熟悉代码，建议您处理一些标记有以下标签之一或多个的问题：[good-first-issue](https://github.com/CherryHQ/cherry-studio/labels/good%20first%20issue)、[help-wanted](https://github.com/CherryHQ/cherry-studio/labels/help%20wanted) 或 [kind/bug](https://github.com/CherryHQ/cherry-studio/labels/kind%2Fbug)。任何帮助都会收到欢迎。
 
-2. **创建分支**：为您要进行的更改创建一个新的分支。
+### 测试
 
-3. **提交更改**：在本地进行更改并提交。请确保您的提交信息清晰明了。
+未经测试的功能等同于不存在。为确保代码真正有效，应通过单元测试和功能测试覆盖相关流程。因此，在考虑贡献时，也请考虑可测试性。所有测试均可本地运行，无需依赖 CI。请参阅[开发者指南](docs/dev.md#test)中的“Test”部分。
 
-4. **发起 Pull Request**：将您的更改推送到 GitHub，并发起 Pull Request。请描述您的更改内容和原因。
+### 拉取请求的自动化测试
+
+自动化测试会在 Cherry Studio 组织成员开启的拉取请求（PR）上触发，草稿 PR 除外。新贡献者开启的 PR 最初会标记为 needs-ok-to-test 标签且不自动测试。待 Cherry Studio 组织成员在 PR 上添加 /ok-to-test 后，测试通道将被创建。
+
+### 考虑将您的拉取请求作为草稿打开
+
+并非所有拉取请求在创建时就准备好接受审查。这可能是因为作者想发起讨论，或者他们不完全确定更改是否朝着正确的方向发展，甚至可能是因为更改尚未完成。请考虑将这些 PR 创建为[草稿拉取请求](https://github.blog/2019-02-14-introducing-draft-pull-requests/)。草稿 PR 会被CI跳过，从而节省CI资源。这也意味着审阅者不会被自动分配，社区会理解此 PR 尚未准备好接受审阅。
+在您将草稿拉取请求标记为准备审核后，审核人员将被分配
+
+### 贡献者遵守项目条款
+
+我们要求每位贡献者证明他们有权合法地为我们的项目做出贡献。贡献者通过有意识地签署他们的提交来表达这一点，并通过这一行为表明他们遵守许可证[LICENSE](LICENSE)。
+签名提交是指提交信息中包含以下内容的提交：
+
+```
+Signed-off-by: Your Name <your.email@example.com>
+```
+
+您可以通过以下命令[git commit --signoff](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff)生成签名提交：
+
+```
+git commit --signoff -m "Your commit message"
+```
+
+### 获取代码审查/合并
+
+维护者在此帮助您在合理时间内实现您的用例。他们会尽力在合理时间内审查您的代码并提供建设性反馈。但如果您在审查过程中受阻，或认为您的 Pull Request 未得到应有的关注，请通过 Issue 中的评论或者[社群](README.md#-community)联系我们
 
 ### 其他建议
 
 - **联系开发者**：在提交 PR 之前，您可以先和开发者进行联系，共同探讨或者获取帮助。
-- **成为核心开发者**：如果您能够稳定为项目贡献，恭喜您可以成为项目核心开发者，获取到项目成员身份。
+- **成为核心开发者**：如果您能够稳定为项目贡献，恭喜您可以成为项目核心开发者，获取到项目成员身份。请查看我们的[成员指南](https://github.com/CherryHQ/community/blob/main/membership.md)
 
 ## 联系我们
 

CONTRIBUTING_EN.md

@@ -0,0 +1,73 @@
+[中文](./CONTRIBUTING.md) | [English](./CONTRIBUTING_EN.md)
+
+# Cherry Studio Contributor Guide
+
+Welcome to the Cherry Studio contributor community! We are committed to making Cherry Studio a project that provides long-term value and hope to invite more developers to join us. Whether you are an experienced developer or a beginner just starting out, your contributions will help us better serve users and improve software quality.
+
+## How to Contribute
+
+Here are several ways you can participate:
+
+1.  **Contribute Code**: Help us develop new features or optimize existing code. Please ensure your code adheres to our coding standards and passes all tests.
+
+2.  **Fix Bugs**: If you find a bug, you are welcome to submit a fix. Please confirm the issue is resolved before submitting and include relevant tests.
+
+3.  **Maintain Issues**: Help us manage issues on GitHub by assisting with tagging, classifying, and resolving problems.
+
+4.  **Product Design**: Participate in product design discussions to help us improve user experience and interface design.
+
+5.  **Write Documentation**: Help us improve the user manual, API documentation, and developer guides.
+
+6.  **Community Maintenance**: Participate in community discussions, help answer user questions, and promote community activity.
+
+7.  **Promote Usage**: Promote Cherry Studio through blogs, social media, and other channels to attract more users and developers.
+
+## Before You Start
+
+Please make sure you have read the [Code of Conduct](CODE_OF_CONDUCT.md) and the [LICENSE](LICENSE).
+
+## Getting Started
+
+To help you get familiar with the codebase, we recommend tackling issues tagged with one or more of the following labels: [good-first-issue](https://github.com/CherryHQ/cherry-studio/labels/good%20first%20issue), [help-wanted](https://github.com/CherryHQ/cherry-studio/labels/help%20wanted), or [kind/bug](https://github.com/CherryHQ/cherry-studio/labels/kind%2Fbug). Any help is welcome.
+
+### Testing
+
+Features without tests are considered non-existent. To ensure code is truly effective, relevant processes should be covered by unit tests and functional tests. Therefore, when considering contributions, please also consider testability. All tests can be run locally without dependency on CI. Please refer to the "Testing" section in the [Developer Guide](docs/dev.md).
+
+### Automated Testing for Pull Requests
+
+Automated tests are triggered on pull requests (PRs) opened by members of the Cherry Studio organization, except for draft PRs. PRs opened by new contributors will initially be marked with the `needs-ok-to-test` label and will not be automatically tested. Once a Cherry Studio organization member adds `/ok-to-test` to the PR, the test pipeline will be created.
+
+### Consider Opening Your Pull Request as a Draft
+
+Not all pull requests are ready for review when created. This might be because the author wants to start a discussion, they are not entirely sure if the changes are heading in the right direction, or the changes are not yet complete. Please consider creating these PRs as [draft pull requests](https://github.blog/2019-02-14-introducing-draft-pull-requests/). Draft PRs are skipped by CI, thus saving CI resources. This also means reviewers will not be automatically assigned, and the community will understand that this PR is not yet ready for review.
+Reviewers will be assigned after you mark the draft pull request as ready for review.
+
+### Contributor Compliance with Project Terms
+
+We require every contributor to certify that they have the right to legally contribute to our project. Contributors express this by consciously signing their commits, thereby indicating their compliance with the [LICENSE](LICENSE).
+A signed commit is one where the commit message includes the following:
+
+You can generate a signed commit using the following command [git commit --signoff](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff):
+
+```
+git commit --signoff -m "Your commit message"
+```
+
+### Getting Code Reviewed/Merged
+
+Maintainers are here to help you implement your use case within a reasonable timeframe. They will do their best to review your code and provide constructive feedback promptly. However, if you get stuck during the review process or feel your Pull Request is not receiving the attention it deserves, please contact us via comments in the Issue or through the [Community](README.md#-community).
+
+### Other Suggestions
+
+- **Contact Developers**: Before submitting a PR, you can contact the developers first to discuss or get help.
+- **Become a Core Developer**: If you contribute to the project consistently, congratulations, you can become a core developer and gain project membership status. Please check our [Membership Guide](https://github.com/CherryHQ/community/blob/main/docs/membership.en.md).
+
+## Contact Us
+
+If you have any questions or suggestions, feel free to contact us through the following ways:
+
+- WeChat: kangfenmao
+- [GitHub Issues](https://github.com/CherryHQ/cherry-studio/issues)
+
+Thank you for your support and contributions! We look forward to working with you to make Cherry Studio a better product.

docs/dev.md

@@ -37,6 +37,12 @@ yarn install
 yarn dev
 ```
 
+### Test
+
+```bash
+yarn test
+```
+
 ### Build
 
 ```bash