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 <[email protected]>
sandyskies <[email protected]>
Tim Xu <[email protected]>
titustian <[email protected]>