# request_factory client
[![Build Status](https://travis-ci.org/tinyclues/request_factory.svg?branch=master)](https://travis-ci.org/tinyclues/request_factory) [![Coverage Status](https://coveralls.io/repos/github/tinyclues/request_factory/badge.svg?branch=delete_package)](https://coveralls.io/github/tinyclues/request_factory?branch=delete_package)
This is for simplify the request management.
Actually support :
## Contributing to request_factory client
All contributions, bug reports, bug fixes, documentation improvements, enhancements and ideas are welcome.
### Working with the code
Now that you have an issue you want to fix, enhancement to add, or documentation to improve, you need to learn how to work with GitHub.
We use the [Github Flow](https://guides.github.com/introduction/flow/)
Finally, commit your changes to your local repository with an explanatory message, request_factory client uses a convention for commit message prefixes.
Here are some common prefixes along with general guidelines for when to use them:
* ENH: Enhancement, new functionality
* BUG: Bug fix
* DOC: Additions/updates to documentation
* TST: Additions/updates to tests
* BLD: Updates to the build process/scripts
* PERF: Performance improvement
* CLN: Code cleanup
* NOBUILD: special tag to skip test & build
TODO: Brief introduction on what you do with files - including link to relevant help section.