(maint) Add PR and Issue templates

.github/ISSUE_TEMPLATE/AskQuestion.md

@@ -0,0 +1,18 @@
+---
+name: Ask Question
+about: Do you have a question?
+---
+
+STOP RIGHT HERE - DO NOT CREATE A TICKET FOR A QUESTION ON THIS REPOSITORY
+
+1. Start with https://docs.chocolatey.org/en-us/troubleshooting (Troubleshooting) and https://docs.chocolatey.org/en-us/faqs (FAQs) to see if your question or issue already has an answer. You can also explore https://docs.chocolatey.org/en-us/ (which are pretty comprehensive, but not always the most searchable).
+2. If not found or resolved, please see https://chocolatey.org/support to see what avenues are available to you based on whether you are an open source user or a licensed customer (have a commercial edition).
+
+
+The best routes for getting questions answered when the documentation doesn't serve what you need is the mailing list or in chat:
+- email - http://groups.google.com/group/chocolatey
+- chat - https://gitter.im/chocolatey/choco
+
+
+
+NOTE: Keep in mind we have a [Code of Conduct](./CODE_OF_CONDUCT.md) that we expect folks to observe when they are looking for support in the Chocolatey community.

.github/ISSUE_TEMPLATE/config.yml

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

.github/ISSUE_TEMPLATE/zFeatureRequest.md

@@ -0,0 +1,10 @@
+---
+name: Enhancement / Feature Request
+about: Is there additional functionality you would love us to consider?
+---
+
+<!--
+Please observe [CONTRIBUTING.md](https://github.com/chocolatey/.github/blob/main/CONTRIBUTING.md) guidelines prior to creating your issue.
+
+NOTE: Keep in mind we have a [Code Of Conduct](https://github.com/chocolatey/.github/blob/main/CODE_OF_CONDUCT.md) that we expect folks to observe when they are looking for support in the Chocolatey community.
+-->

.github/ISSUE_TEMPLATE/zReportIssue.md

@@ -0,0 +1,55 @@
+---
+name: Report Issue
+about: Did you find unexpected behavior?
+---
+
+<!--
+Ensure you have read over [Submitting Issues](https://github.com/chocolatey/.github/blob/main/SUBMITTING_ISSUES.md)
+
+Please check to see if your issue already exists with a quick search of the issues. Start with one relevant term and then add if you get too many results.
+
+NOTE: Keep in mind we have a [Code Of Conduct](https://github.com/chocolatey/.github/blob/main/CODE_OF_CONDUCT.md) that we expect folks to observe when they are looking for support in the Chocolatey community.
+
+Name your issue appropriately: give it a sentence that reads well enough for anyone seeing this in the release notes to what it is.
+
+When writing out the issue details please ensure you are writing it as if you were explaining it to somebody else.
+Even if you will be working on and resolving the issue yourself. This helps others to understand the reasons for the
+pull request and for it to be searchable in future.
+-->
+
+### What You Are Seeing?
+
+### What is Expected?
+
+### How Did You Get This To Happen? (Steps to Reproduce)
+
+### System Details
+
+* OS Build (In PowerShell run `[System.Environment]::OSVersion.version.tostring()`):
+* Windows PowerShell version (Run: `$PSVersionTable`):
+* Chocolatey version (Run `choco --version`):
+
+### Output Log
+<!--
+When including the log information, please ensure you have run the command with --debug --verbose. It provides important information for determining an issue
+
+- Make sure there is no sensitive data shared.
+- We need ALL output, not just what you may believe is relevant.
+- We need ALL OUTPUT (including the configuration information), see https://gist.github.com/ferventcoder/b1300b91c167c8ac8205#file-error-txt-L1-L41 for what we need.
+- If it is hard to reproduce with debug/verbose, the log file already logs with those parameters, just grab the relevant section from the log file (in the logs directory of your Chocolatey install).
+-->
+
+
+<details>
+<summary>Full Log Output</summary>
+
+<p>
+
+~~~sh
+IF YOUR LOG CONTENT IS SHORT, PLACE IT HERE - WE NEED _ALL_ DETAILED OUTPUT BASED ON THE ABOVE TO BE ABLE TO PROVIDE SUPPORT (YOU WILL FIND THAT IN THE $env:ChocolateyInstall\logs\chocolatey.log between the `=====`)
+IF YOUR LOG CONTENT IS LONG, PLEASE LINK TO A GIST (see https://docs.github.com/en/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)
+~~~
+
+</p>
+
+</details>

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,63 @@
+<!--
+BEFORE YOU CREATE A PULL REQUEST:
+
+Ensure you have read over [CONTRIBUTING.md](./CONTRIBUTING.md). We provide VERY defined guidance (as such, we strongly adhere to it).
+
+A summary of our expectations:
+ - You are not submitting a pull request from your MASTER / MAIN branch.
+ - You are able to sign the Contributor License Agreement (CLA).
+ - YOUR GIT COMMIT MESSAGE FORMAT IS EXTREMELY IMPORTANT. We have a very defined expectation for this format and are sticklers about it. Really, READ the entire Contributing document. It will save you and us pain.
+ - Do not reformat code, it makes it hard to see what has changed. Leave the formatting to us.
+
+THANKS! We appreciate you reading the entire Contributing document and not just scanning through it.
+
+Name your issue appropriately: give it a sentence that reads well enough for anyone seeing this in release notes to know what the issue is.
+
+When writing out the pull request details please ensure you are writing it as
+if you were explaining it to somebody else.
+Even if you will be working on and resolving the issue yourself.
+This helps others to understand the reasons for the pull request and for it to be searchable in future.
+
+Please do not remove any of the headings.
+If a heading is not applicable then enter N/A: Why it's not applicable
+
+Make sure you have raised an issue for this pull request before continuing.
+
+Please remove all comments before submitting.
+-->
+
+## Description Of Changes
+<!-- Enter a description of the pull request changes -->
+
+## Motivation and Context
+<!-- Why is this change necessary and under what context is it being done -->
+
+## Testing
+<!-- How has this change been tested? If multiple different tests have been done please list them.
+1. Tested this way
+1. Tested that way
+-->
+
+## Change Types Made
+<!-- Tick the boxes for the type of changes that have been made -->
+
+* [ ] Bug fix (non-breaking change)
+* [ ] Feature / Enhancement (non-breaking change)
+* [ ] Breaking change (fix or feature that could cause existing functionality to change)
+* [ ] PowerShell code changes.
+
+## Related Issue
+<!-- Make sure you have raised an issue for this pull request before
+continuing. -->
+
+Fixes #
+
+## Change Checklist
+
+* [ ] Requires a change to the documentation
+* [ ] Documentation has been updated
+* [ ] Tests to cover my changes, have been added
+* [ ] All new and existing tests passed.
+* [ ] PowerShell v2 compatibility checked.
+
+<!-- PLEASE REMOVE ALL COMMENTS BEFORE SUBMITTING -->