Update the issue template to be more configurable (#1307)

Author: daxian-dbw

.github/ISSUE_TEMPLATE.md renamed to .github/ISSUE_TEMPLATE/Bug_Report.md

@@ -1,19 +1,35 @@
+---
+name: "Bug report :bug:"
+about: Report errors or unexpected behaviors
+title: ''
+labels: ''
+assignees: ''
+
+---
+
 <!--
-Before submitting your bug report, please check for duplicates, and +1 the duplicate if you find one, adding additional details if you have any to add.
 
-There are a few common issues that are commonly reported.
+Before submitting your bug report ...
+- Please make sure you are able to reproduce the issue with the latest version of PSReadLine.
+- Please check for duplicates. +1 the duplicate if you find one and add additional details if you have any.
+
+The maintainer may close your issue without further explanation or engagement if:
+- You delete this entire template and go your own path;
+- You file an issue that has many duplicates;
+- You file an issue completely blank in the body.
 
-If there is an exception copying to/from the clipboard, it's probably the same as https://github.com/PowerShell/PSReadLine/issues/265
-If there is an exception shortly after resizing the console, it's probably the same as https://github.com/PowerShell/PSReadLine/issues/292
 -->
 
-Environment data
-----------------
+## Environment
+
+```none
+[run the script below and paste the output here]
+```
 
 <!--
 
 The following script will generate the environment data that helps triage and investigate the issue.
-Please run the script in the PowerShell session where you ran into the issue and provide the output here.
+Please run the script in the PowerShell session where you ran into the issue and provide the output above.
 
 & {
     $hostName = $Host.Name
@@ -49,5 +65,18 @@ Please run the script in the PowerShell session where you ran into the issue and
 
 -->
 
-Steps to reproduce or exception report
---------------------------------------
+## Exception report
+
+<!-- Copy and paste the keys and the exception stack trace printed by PSReadLine, if there is any -->
+
+## Steps to reproduce
+
+<!-- A description of how to trigger this bug. -->
+
+## Expected behavior
+
+<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->
+
+## Actual behavior
+
+<!-- What's actually happening? -->

.github/ISSUE_TEMPLATE/Documentation_Issue.md

@@ -0,0 +1,10 @@
+---
+name: "Documentation Issue :books:"
+about: Report issues in our documentation
+title: ''
+labels: Issue-Docs
+assignees: ''
+
+---
+
+<!-- Briefly describe which document needs to be corrected and why. -->

.github/ISSUE_TEMPLATE/Feature_Request.md

@@ -0,0 +1,30 @@
+---
+name: "Feature Request/Idea :rocket:"
+about: Suggest a new feature or improvement (this does not mean you have to implement it)
+title: ''
+labels: Issue-Enhancement
+assignees: ''
+
+---
+
+<!--
+
+The maintainer may close your issue without further explanation or engagement if:
+- You delete this entire template and go your own path;
+- You file an issue that has many duplicates;
+- You file an issue completely blank in the body.
+
+-->
+
+## Description of the new feature/enhancement
+
+<!--
+A clear and concise description of what the problem is that the new feature would solve.
+Describe why and how a user would use this new functionality (if applicable).
+-->
+
+## Proposed technical implementation details (optional)
+
+<!--
+A clear and concise description of what you want to happen.
+-->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false