代码拉取完成，页面将自动刷新
同步操作将从 TarsCloud/TarsGo 强制同步，此操作会覆盖自 Fork 仓库以来所做的任何修改，且无法恢复！！！
确定后同步将在后台操作，完成时将刷新页面，请耐心等待。
All pull request must use dev branch as base branch, not master , master is used for publishing.
Use English as u can.
if you want to report a bug, use this template in issue:
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
** Version info
Which go version :
Which tars version (git commit id or branch name):
Which os:
**Expected behavior**
A clear and concise description of what you expected to happen.
**Additional context**
Add any other context about the problem here.
if you want to propose a feature ,use this template in issue :
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
click the fork button on the right top of the project.
if you want to create a pull request, you must create a issue first.
In the pr, you should give the related issue.
All pull request must go to dev branch, not master.
ALL go file must be formated by gofmt and must be fixed after golint.
After your pr is merged, your name and github email will be showed in AUTHORS like following.
# This file lists all individuals having contributed content to the repository.
# For how it is generated, see `hack/generate-authors.sh`.
ChenMingjie <15210875043@sina.cn>
sandyskies <chenmingjie0828@163.com>
Tim Xu <xiaoxubeii@gmail.com>
titustian <titustian@tencent.com>
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。