Add template to new issue and new PR (#70)

Author: lipkau

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,32 @@
+<!-- Provide a general summary of the issue in the Title above -->
+
+### Expected Behavior
+<!-- If you're describing a bug, tell us what should happen -->
+<!-- If you're suggesting a change/improvement, tell us how it should work -->
+
+### Current Behavior
+<!-- If describing a bug, tell us what happens instead of the expected behavior. If screenshot are available/relevant, please attach them -->
+<!-- If suggesting a change/improvement, explain the difference from current behavior -->
+
+### Possible Solution
+<!-- Not obligatory, but suggest a fix/reason for the bug, -->
+<!-- or ideas how to implement the addition or change -->
+
+### Steps to Reproduce (for bugs)
+<!-- Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+### Context
+<!-- How has this issue affected you? What are you trying to accomplish? -->
+<!-- Providing context helps us come up with a solution that is most useful in the real world -->
+
+### Your Environment
+<!-- Include as many relevant details about the environment you experienced the bug in -->
+<!-- The following code snip is a recommendation. You can just paste the output here. -->
+> ```posh
+> Get-Module ConfluencePS -ListAvailable | select version
+> $PSVersionTable
+> ```

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+<!-- Provide a general summary of your changes in the Title above -->
+
+### Description
+<!-- Describe your changes in detail -->
+
+### Motivation and Context
+<!-- Why is this change required? What problem does it solve? -->
+<!-- If it fixes an open issue, please link to the issue here as follows: -->
+<!-- closes #1, closes #2, ... -->
+
+### Types of changes
+<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (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 change)
+
+### Checklist:
+<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] My code follows the code style of this project.
+- [ ] I have added Pester Tests that describe what my changes should do.
+- [ ] I have updated the documentation accordingly.