代码拉取完成，页面将自动刷新
If you have any comment or advice, please report your issue, or make any change as you wish and submit a PR.
AntV group members will confirm the purpose of the issue, replace more accurate labels for it, identify related milestone, and assign developers working on it.
If you are developer of AntV repo and you are willing to contribute, feel free to create a new branch, finish your modification and submit a PR. AntV group will review your work and merge it to master branch.
# Create a new branch for development. The name of branch should be semantic, avoiding words like 'update' or 'tmp'. We suggest to use feature/xxx, if the modification is about to implement a new feature.
$ git checkout -b branch-name
# Run the test after you finish your modification. Add new test cases or change old ones if you feel necessary
$ npm test
# If your modification pass the tests, congradulations it's time to push your work back to us. Notice that the commit message should be wirtten in the following format.
$ git add . # git add -u to delete files
$ git commit -m "fix(role): role.use must xxx"
$ git push origin branch-name
Then you can create a Pull Request at x6.
No one can guarantee how much will be remembered about certain PR after some time. To make sure we can easily recap what happened previously, please provide the following information in your PR.
eslint can help to identify styling issues that may exist in your code. Your code is required to pass the test from eslint. Run the test locally by $ yarn lint.
You are encouraged to use angular commit-message-format to write commit message. In this way, we could have a more trackable history and an automatically generated changelog.
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
（1）type
Must be one of the following:
（2）scope
The scope could be anything specifying place of the commit change.
（3）subject
Use succinct words to describe what did you do in the commit change.
（4）body
Feel free to add more content in the body, if you think subject is not self-explanatory enough, such as what it is the purpose or reasons of you commit.
（5）footer
Closes #1, Closes #2, #3
e.g.
fix($compile): [BREAKING_CHANGE] couple of unit tests for IE9
Older IEs serialize html uppercased, but IE9 does not...
Would be better to expect case insensitive, unfortunately jasmine does
not allow to user regexps for throw expectations.
Document change on antvis/x6#123
Closes #392
BREAKING CHANGE:
Breaks foo.bar api, foo.baz should be used instead
Look at these files for more details.
X6 uses semantic versioning in release process based on semver.
master branch is the latest stable version.
master
master or next branch as well as all bug-fix except security issues. In such way, we can motivate developers to update to the latest stable version.In the release of every stable version, there will be a PM who has the following responsibilities in different stages of the release.
History as node CHANGELOG. Don't forget to correct content in documentation which is related to the releasing version.此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。