# A good pull-request should contain

### Change list

There should be provided briefly described change list which are you going to propose. 
 
### Types of changes

What types of changes are proposed/introduced to Java client?
_Put an `x` in the boxes that apply_

- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

### Details

There should be provided more details about changes if it is necessary. If there are new features you 
can provide code samples which show the way they work and possible use cases. Also you can create [gists](https://gist.github.com) 
with pasted java code samples or put them at a PR description using markdown. About markdown please read [Mastering markdown](https://guides.github.com/features/mastering-markdown/) and [Writing on GitHub](https://help.github.com/categories/writing-on-github/) 

# Pull-request template

There is [PULL_REQUEST_TEMPLATE.md](https://github.com/appium/java-client/blob/master/PULL_REQUEST_TEMPLATE.md) which should help you to make a good pull request.
