github: make issue templates less annoying

Signed-off-by: Bobby DeSimone <bobbydesimone@gmail.com>
This commit is contained in:
Bobby DeSimone 2019-10-02 15:25:07 -07:00
parent 1e4496c2b9
commit 9c4bd38624
No known key found for this signature in database
GPG key ID: AEE4CF12FE86D07E
3 changed files with 24 additions and 35 deletions

View file

@ -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.
**Environment:**
- Pomerium version (retrieve with `pomerium --version`):
- Pomerium version (retrieve with `pomerium --version` or `/ping` endpoint):
- 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
# Paste your configs here.
```logs
# Paste your logs here.
# Be sure to scrub any sensitive values
```
**Additional context**
## Additional context
Add any other context about the problem here.

View file

@ -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.

View file

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