Update PR template, add issue templates

Author: buzzsurfr

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,15 @@
+For this bug report, be sure to include:
+* A short, descriptive title. Ideally, other community members should be able to get a good idea of the issue just from reading the title.
+* A detailed description of the problem you're experiencing. This should include:
+  * Expected behavior of the workshop and the actual behavior exhibited.
+  * Any details of your application environment that may be relevant.
+  * Commands and output used to reproduce the issue.
+* [Markdown][https://guides.github.com/features/mastering-markdown/] formatting as appropriate to make the report easier to read; for example use code blocks when pasting a code snippet and exception stacktraces.
+
+*Description:*
+
+
+*Expected vs. Actual Behavior:*
+
+
+*Environment Details:*

.github/ISSUE_TEMPLATE/ENHANCEMENT.md

@@ -0,0 +1,14 @@
+For this enhancement, be sure to include:
+* A short, descriptive title. Ideally, other community members should be able to get a good idea of the enhancement just from reading the title.
+* A detailed description of the the proposed enhancement. Include justification for why it should be added to the workshop, and possibly example code to illustrate how it should work.
+* link:https://guides.github.com/features/mastering-markdown/[Markdown] formatting as appropriate to make the request easier to read.
+* If you intend to implement this enhancement, indicate that you'd like to the issue to be assigned to you.
+
+
+*Description:*
+
+
+*Justification (Why should this be added?):*
+
+
+*Assigned to you? (Y/N)*

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,4 +1,4 @@
-*Issue #, if available:*
+*Issue #, if available (include [keywords](https://help.github.com/articles/closing-issues-using-keywords/) to close issue as applicable, e.g. "fixes <##>"):*
 
 *Description of changes:*