Lines Matching +full:- +full:- +full:github +full:- +full:issue

4 - There is some interesting information on the [wiki](https://github.com/javaparser/javaparser/wiki…
5 - We work on JavaParser because we like to, not because it earns us money. Please remember that we …
6 - Be sure to check [the coding guidelines](https://github.com/javaparser/javaparser/wiki/Coding-Gui…
7 - If you're new and like to casually contribute something, check out the [easy issues](https://gith…
8 - If you're new and would like to become a member, start your own project that uses JavaParser.
10 Here are [some fun project ideas](https://github.com/javaparser/javaparser/labels/fun%20project%20i…
11 - If you start working on an issue, please say so with a comment in the issue.
12 - If you know how to fix a problem, please fix it and open a pull request instead of opening an iss…
18 …equests, we suggest you to checkout the [Github Documentation](https://help.github.com/articles/cr…
21 2. In your forked project, **create a branch** related to the issue you are working on. This is imp…
23 …github.com/javaparser/javaparser) and it should have a message offering to **create a pull request…
26 - A pull request should include tests. You can either use BDD ([more information here](https://gith…
27 - Every pull request will automatically be checked by a few tools. Make sure AppVeyor and Travis ar…
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 li…