docs(github): update template

Author: chuangker

.github/CONTRIBUTING.md

@@ -1,24 +1,24 @@
-## Easy Mock 贡献指南
+## Easy Mock Contributing Guide
 
-Hi，感谢你使用 Easy Mock。
+Hi, Thank you for your attention to Easy Mock.
 
-如果你愿意为 Easy Mock 贡献代码或提供建议，请阅读以下内容。
+If you are willing to contribute code or provide suggestions for Easy Mock, please make sure to take a moment and read through the following guidelines.
 
 ### Issue
 
-- issue 仅用于提交 Bug 或 Feature 相关的内容，其它内容可能会被直接关闭。
-- 在提交 issue 之前，请搜索相关内容是否已被提出。
+- Issues are exclusively for bug reports and feature requests. Other questions may be closed directly.
+- Before submitting an issue, please check if similar problems have already been issued.
 
 ### Pull Request
 
-- 请先 fork 一份到自己的项目下。
-- commit 提交规范参考 [angular](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines)。
-- 创建一个新的分支来让你完成 **修复/改进**。
-- 添加相关测试用例，并通过测试。
-- 提交 PR 前请 rebase，确保 commit 记录的整洁。
-- 确保 PR 是提交到 dev 分支，而不是 master 分支。
-- 在 PR 中给出相关的描述信息。
+- Fork this repository to your own account.
+- Commit Messages should conform to [Angular's guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines).
+- Create a new topic branch to contain your feature, change, or fix.
+- Make sure `npm test` passes.
+- Rebase before creating a PR to keep commit history clear.
+- Make sure PRs are created to `dev` branch instead of `master` branch.
+- If you are fixing a bug, please include detailed description of the bug in the PR.
 
-### 代码规范
+### Code Style
 
-遵循 Standard [ESLint](http://standardjs.com) 即可。
+Just comply with the ESLint configuration of [Standard](http://standardjs.com).

.github/ISSUE_TEMPLATE.md

@@ -1,11 +1,11 @@
-<!-- 问题可能已经存在！请在创建之前搜索相关问题。 -->
+<!-- Before submitting an issue, please check if similar problems have already been issued. -->
 
-## 出现什么问题？
+## OS / Browser Version
 
-## 如何能重现这个问题？
+## Node.js / MongoDB Version
 
-## 期望的结果？
+## Steps to reproduce
 
-## 操作系统版本 / 浏览器版本？
+## What is Expected？
 
-<!-- 如果是部署出现问题，还应提供 Node、MongoDB、服务器 的版本信息与错误日志。 -->
+## What is actually happening？

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,25 +1,25 @@
-**这个 PR 中做了哪方面的改变?** (至少选一个)
+**What kind of change does this PR introduce?**
 
 - [ ] Bugfix
 - [ ] Feature
 - [ ] Code style update
 - [ ] Refactor
 - [ ] Build-related changes
-- [ ] 其它, 请描述:
+- [ ] Other, please describe:
 
-**这个 PR 是否有突破性改变:** (选一个)
+**Does this PR introduce a breaking change?**
 
-- [ ] 是
-- [ ] 否
+- [ ] Yes
+- [ ] No
 
-如果是，请描述出对现在的应用程序的影响以及迁移方案或兼容方案：
+If yes, please describe the impact and migration path for existing applications:
 
-**这个 PR 应该满足以下条件:**
+**The PR fulfills these requirements:**
 
-- [ ] 提交到 dev 分支，而不是 master 分支
-- [ ] 遵循 Standard [ESLint](http://standardjs.com)
-- [ ] 提交前已完成 rebase，确保 commit 记录的整洁
-- [ ] 解决具体问题时，应该在 PR 的标题中体现出来。（例如：fix #xxx: 描述，xxx 指具体 issue 的编号）
-- [ ] 通过所有测试用例
+- [ ] It's submitted to the `dev` branch, not the `master` branch
+- [ ] comply with the ESLint configuration of [Standard](http://standardjs.com)
+- [ ] Rebase before creating a PR to keep commit history clear
+- [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
+- [ ] All tests are passing
 
-**其它信息:**
+**Other information:**