Please do not create a Pull Request without creating an issue first. Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
Make sure tests pass on both Travis CI.
See the CONTRIBUTING.md
Put closes #XXXX
in your comment to auto-close the issue that your PR fixes (if such).
-
Please check if the PR fulfills these requirements
- The commit message follows our guidelines
- Tests for the changes have been added (for bug fixes / features)
- Docs have been added / updated (for bug fixes / features)
-
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
-
What is the current behavior? (You can also link to an open issue here)
-
What is the new behavior (if this is a feature change)?
-
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
-
Other information: