Update issue templates

Adds Legality, crash, and feature request templates.
This commit is contained in:
Kurt 2019-10-27 21:13:44 -07:00 committed by GitHub
parent a6b6383538
commit a03dfd12b5
3 changed files with 72 additions and 0 deletions

View File

@ -0,0 +1,27 @@
---
name: Bug report (non-Legality)
about: Create a report to help us fix a crash / incorrect behavior
title: ''
labels: bug
assignees: ''
---
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
Add any other context about the problem here.

View File

@ -0,0 +1,22 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: enhancement
assignees: ''
---
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
Note: Requesting new editing features that *require research* are not Feature Requests. This is only for improving interactions and/or leveraging the current code in new/interesting ways.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.

View File

@ -0,0 +1,23 @@
---
name: Legality parsing report
about: Legality check returned an unexpected result
title: ''
labels: bug
assignees: ''
---
**Describe the problem**
A clear and concise description of what the bug is. This is not to ask why fabricated data does not pass the legality check.
**To Reproduce**
Please provide a PKM file or adequate information so that we may quickly replicate the parsing behavior on our end.
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
Add any other context about the problem here.