26 lines
976 B
Markdown
26 lines
976 B
Markdown
**IMPORTANT: Please do not create a Pull Request without creating an issue first.**
|
|
|
|
*Any change needs to be discussed before proceeding. Not doing so may result in the rejection of the pull request without much notice.*
|
|
|
|
Please provide enough information so that others can review your pull request:
|
|
|
|
<!-- You can skip this if you're fixing a typo or adding an app to the Showcase. -->
|
|
|
|
Explain the **details** for making this change. What existing problem does the pull request solve?
|
|
|
|
<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
|
|
|
|
**Test plan (required)**
|
|
|
|
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 and Circle CI. -->
|
|
|
|
**Code formatting**
|
|
|
|
<!-- See the simple style guide. -->
|
|
|
|
**Closing issues**
|
|
|
|
Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes.
|