Lines Matching +full:create +full:- +full:pull +full:- +full:request
10 Bug-fixes and features often come from users of the MPAndroidChart library and improve it greatly. …
16 Search existing [issues] to see if your bug has already been reported or if a feature request alrea…
18 ## Making Pull Requests
20 Careful! If you fail to follow these guidlines, you're pull request may be closed, *even if it's re…
22 …** open [pull requests] AND existing [issues] to make sure what you want to do isn't already being…
24 1. **Create** a new branch based on `master`, and name it according to your changes
25 1. **Add** your commits, they MUST follow the [Commit Style](#commit-style) below
26 1. **Test** your changes by actually running the example app, or create a new example
27 1. **Create** a pull request, following the auto-generated template
33 …75](https://github.com/PhilJay/MPAndroidChart/pull/3975) for an example of a good-made-better pull…
44 …You may prefer [Tim Pope's style], you might like the [commitizen-friendly] way. Regardless of the…
49 changes more thoroughly. If the change is obvious and self-explanatory
63 [pull requests]: https://github.com/PhilJay/MPAndroidChart/pulls
65 [Tim Pope's style]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
66 [commitizen-friendly]: https://github.com/commitizen/cz-cli