Lines Matching refs:Pull
12 - If you know how to fix a problem, please fix it and open a pull request instead of opening an issue.
18 Our development workflow is based on Pull Request. If you are not familiar with the Pull Requests, we suggest you to checkout the [Github Documentation](https://help.github.com/articles/creating-a-pull-request/) for more information.
21 2. In your forked project, **create a branch** related to the issue you are working on. This is important to ensure that your pull request will not contain unrelated work.
23 4. Go back to the [javaparser project site](https://github.com/javaparser/javaparser) and it should have a message offering to **create a pull request**. If it doesn't you can [create one manually](https://github.com/javaparser/javaparser/compare).
26 - A pull request should include tests. You can either use BDD ([more information here](https://github.com/javaparser/javaparser/wiki/Testing)) or JUnit.
27 - Every pull request will automatically be checked by a few tools. Make sure AppVeyor and Travis are green.
28 - Pull requests often stay open for at least a few days to give people a chance to review it.
29 - A pull request is merged when all comments on it have been resolved.
30 - If you create a pull request for an issue, mention the issue in the format #123 to make github link it automatically.
