github: make issue templates less annoying

Signed-off-by: Bobby DeSimone <bobbydesimone@gmail.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -3,39 +3,35 @@ name: Bug report
 about: Let us know about a bug!
 ---
 
-<!-- Please reserve GitHub issues for bug reports and feature requests. -->
+## What happened?
 
- **Describe the bug** A clear and concise description of what the bug is.
+## What did you expect to happen?
 
-**To Reproduce** Steps to reproduce the behavior:
+## How'd it happen?
 
 1. Ran `x`
 2. Clicked `y`
 3. Saw error `z`
 
-**Expected behavior**
+## What's your environment like?
 
-A clear and concise description of what you expected to happen.
+- Pomerium version (retrieve with `pomerium --version` or `/ping` endpoint):
-
-**Environment:**
-
-- Pomerium version (retrieve with `pomerium --version`):
 - Server Operating System/Architecture/Cloud:
 
-Configuration file(s):
+## What's your config.yaml?
 
-```text
+```config.yaml
 # Paste your configs here
 # Be sure to scrub any sensitive values
 ```
 
-Logs(s):
+## What did you see in the logs?
 
-```text
+```logs
-# Paste your configs here.
+# Paste your logs here.
 # Be sure to scrub any sensitive values
 ```
 
-**Additional context**
+## Additional context
 
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -9,12 +9,8 @@ A clear and concise description of what the problem is. Ex. I'm always frustrate
 
 **Describe the solution you'd like**
 
-A clear and concise description of what you want to happen.
-
 **Describe alternatives you've considered**
 
-A clear and concise description of any alternative solutions or features you've considered.
-
 **Explain any additional use-cases**
 
 If there are any use-cases that would help us understand the use/need/value please share them as they can help us decide on acceptance and prioritization.

.github/PULL_REQUEST_TEMPLATE

@@ -1,25 +1,22 @@
-<!--  
+## Summary
-Thanks for sending a pull request!
+<!--  For example...
-We generally follow Go coding and contributing conventions
+The existing implementation has poor numerical properties for
-https://golang.org/doc/contribute.html#commit_messages
+large arguments, so use the McGillicutty algorithm to improve
+accuracy above 1e10.
 
-Here's an example of a good PR/Commit:
+The algorithm is described at https://wikipedia.org/wiki/McGillicutty_Algorithm
+-->
 
-    math: improve Sin, Cos and Tan precision for very large arguments
+## Related issues
-
+<!-- For example...
-    The existing implementation has poor numerical properties for
+Fixes #159 
-    large arguments, so use the McGillicutty algorithm to improve
-    accuracy above 1e10.
-
-    The algorithm is described at https://wikipedia.org/wiki/McGillicutty_Algorithm
-
-    Fixes #159
 -->
 
 
 **Checklist**:
+- [ ] add related issues
 - [ ] updated docs
-- [ ] unit tests added
+- [ ] updated unit tests
-- [ ] related issues referenced
 - [ ] updated CHANGELOG.md
+- [ ] updated UPGRADING.md
 - [ ] ready for review