Add ISSUE and PR templates

Author: jlblcc

ISSUE_TEMPLATE.md

@@ -0,0 +1,39 @@
+### Before submitting an issue to I have first:
+
+- [ ] read the [contribution guidelines](https://github.com/adiwg/mdEditor/blob/develop/CONTRIBUTING.md)
+- [ ] searched for similar already [existing issue](https://github.com/adiwg/mdEditor/issues)
+- [ ] read the documentation and [wiki](https://github.com/adiwg/mdEditor/wiki)
+
+If you have performed all the above, continue describing the issue with template below.
+
+Please:
+
+- *be as explicit has you can*
+- *if reporting a bug*
+    - *describe the problem and its symptoms*
+    - *explain how to reproduce*
+- *attach whatever information that can help understanding the context (screen capture, log files)*
+- *do your best to use correct English (re-read yourself)*
+
+## Issue
+**mdEditor Version** (find version under settings):
+
+**mdEditor Web Address** (enter the URL):
+
+### Issue Description:
+
+*Provide a general description of the problem. If issue is a feature request, tell us why this feature is useful.*
+
+### Steps to reproduce (Bug reports only):
+
+  1. _____
+  2. _____
+  3. _____
+
+### Observed Results (Bug reports only):
+
+  *What happened?  This could be a description, log output, etc.*
+
+### Expected Results (Bug reports only):
+
+  *What did you expect to happen?*

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,47 @@
+## Guidelines
+
+### Create issue first
+
+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.
+
+### Test plan
+
+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.
+
+### Code formatting
+
+See the CONTRIBUTING.md
+
+### Closing issues
+
+Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).
+
+## Pull Request
+
+* **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**: