docs: github issue templates [skip ci]

.github/ISSUE_TEMPLATE/BUG_TEMPLATE.md

@@ -0,0 +1,22 @@
+---
+name: Bug Report
+about: If something isn't working as expected
+labels: "Status: Untriaged"
+---
+
+### Description
+<!--- Briefly describe the issue -->
+
+### Setup
+(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)
+
+### Steps to Reproduce Issue
+<!--- Steps to take to replicate your problem. -->
+(Include debug logs if possible and relevant.)
+
+### Versions Report
+(Provided by running `salt --versions-report and mention any differences in master/minion versions.
+Include Chef test kitchen and inspec versions if applicable.)
+
+## Client Output
+<!--- The relevant output of  or a link to a gist of the entire run, if there is one.

.github/PUTT_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+### What does this PR do?
+
+### What issues does this PR fix or reference?
+
+### Previous Behavior
+Remove this section if not relevant
+
+### New Behavior
+Remove this section if not relevant
+
+### Tests written?
+**[NOTICE] Bug fixes or added features require tests.**
+Please review the documentaiton for [saltstack test](https://docs.saltstack.com/en/latest/topics/tutorials/writing_tests.html), [test kitchen](https://www.saltstack.com/blog/testing-your-salt-states-with-kitchen-salt/), [kitchen-salt](https://kitchen.saltstack.com/) and [inspec](https://www.inspec.io/docs/) where appropriate.
+
+Yes/No
+
+### Commits signed with GPG?
+
+Yes/No
+
+See GitHub's [page on GPG signing](https://help.github.com/articles/signing-commits-using-gpg/) for more information about signing commits with GPG.