# Contribution Guide If you have any comment or advice, please report your [issue](https://github.com/antvis/g2/issues), or make any change as you wish and submit an [PR](https://github.com/antvis/g2/pulls). ## Reporting New Issues - Please specify what kind of issue it is. - Before you report an issue, please search for related issues. Make sure you are not going to open a duplicate issue. - Explain your purpose clearly in tags(see **Useful Tags**), title, or content. AntV group members will confirm the purpose of the issue, replace more accurate tags for it, identify related milestone, and assign developers working on it. ## Submitting Code ### Pull Request Guide 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. ```bash # 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 [g2](https://github.com/antvis/g2/pulls). 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. 1. Need: What function you want to achieve (Generally, please point out which issue is related). 2. Updating Reason: Different with issue. Briefly describe your reason and logic about why you need to make such modification. 3. Related Testing: Briefly describe what part of testing is relevant to your modification. 4. User Tips: Notice for g2 users. You can skip this part, if the PR is not about update in API or potential compatibility problem. ### Style Guide 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 `$ npm run lint`. ### Commit Message Format You are encouraged to use [angular commit-message-format](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format) to write commit message. In this way, we could have a more trackable history and an automatically generated changelog. ```xml ():