Make all issue templates into forms

This commit is contained in:
doregon committed 2021-07-20 22:03:36 -04:00
1 parent aa6e72f49b
commit 62393ca10c
7 files changed
+83 -78

No files matched your search

+1 -1
View File
@@ -7,7 +7,7 @@ body:
id: version
attributes:
label: Describe the bug
description: >-
description: |
A clear and concise description of what the bug is.
placeholder: 'Example: Login results in a crash'
validations:
-34
View File
@@ -1,34 +0,0 @@
---
name: Feature request
about: Got an idea for PojavLauncher?
title: "[F-Req]"
labels: enhancement
assignees: ''
---
<!--
To use this template:
* CHECK OTHER ISSUES and see if anyone else has requested the same functionality. We will close any duplicate requests.
* Don't delete any of the words between asterisks.
* Add something descriptive to the title (ex. [F-Req] Controller Support)
* Follow all of the steps. If you do not provide an answer to each section in this template, the issue will be closed.
-->
**Is your feature request related to a problem? Please describe.**
<!-- Give us some details into the problem, and how this affects it. -->
**Describe the solution you'd like**
<!-- What do you want to see changed, added, or removed? Make sure to be specific. -->
**Describe alternatives you've considered**
<!--Is there anything else you've thought of but crossed off? If so, tell us why.-->
**Additional context**
<!-- Have a mock-up? Perhaps a template or set of files. Share them here! -->
**Make sure you’ve dine the following:**
- [ ] Provided a clear description into what the feature request is
- [ ] (If applicable) provided an issue that this request would fix
- [ ] (If applicable) presented potential possibilities into adding this request
- [ ] (If applicable) Provided evidence such as a drawing, log file, file, etc. of what you wish to see reflected
@@ -0,0 +1,31 @@
name: Feature request
description: 'Ask for new features.'
title: "[F-Req] <Short description>"
labels: [enhancement]
body:
- type: textarea
id: version
attributes:
label: Is this request related to a bug?
description: |
Give us some details into the problem, and how this affects it.
placeholder: 'Example: You should add a version selector because of the text box being too small.'
validations:
required: false
- type: textarea
attributes:
label: Describe the request.
description: |
What do you want to see changed, added, or removed? Make sure to be specific.
placeholder: 'Example: A scrollable version picker.'
validations:
required: false
- type: textarea
attributes:
label: Anything else?
description: |
Add any other context about the problem here.
validations:
required: false
-25
View File
@@ -1,25 +0,0 @@
---
name: Informational
about: Quick and dirty docs, where they're needed.
title: "[Info]"
labels: documentation
assignees: ''
---
<!--
To use this template:
* CHECK OTHER ISSUES and see if anyone else has provided the same information. We will close any duplicates.
* Feel free to delete any words between asterisks, but make your type ledgible and easy to read.
* Add something descriptive to the title (ex. [Info] iOS Memory Issues)
* Follow all of the steps. If you do not provide an answer to each section in this template, the issue will be closed.
-->
**Add some background.**
<!-- What's this documentation for? If it's a solution doc, what's causing the issue? Why is it important to document? -->
**The guts.**
<!-- Write the documentation here. Solutions, simple tricks, screenshots and other goodies belong in this section. -->
**Disclaimers.**
<!-- If you're posting a solution this risky, post a disclaimer saying it is! -->
+37
View File
@@ -0,0 +1,37 @@
name: Informational
description: 'Quick docs, when they're needed.'
title: "[Info] <Short description>"
labels: [documentation]
body:
- type: textarea
id: version
attributes:
label: Describe the bug
description: |
A clear and concise description of what the bug is.
placeholder: 'Example: Login results in a crash'
validations:
required: true
- type: textarea
attributes:
label: Add some background
description: |
What's this documentation for? If it's a solution doc, what's causing the issue? Why is it important to document?
validations:
required: true
- type: textarea
attributes:
label: Time to document.
description: |
Write the documentation here. Solutions, simple tricks, screenshots and other goodies belong in this section.
validations:
required: true
- type: textarea
attributes:
label: Disclaimers
description: If you're posting a solution this risky, post a disclaimer saying it is!
validations:
required: false
-18
View File
@@ -1,18 +0,0 @@
---
name: Question
about: Want to learn more about PojavLauncher?
title: "[Question]"
labels: question
assignees: ''
---
<!--
To use this template:
* CHECK OTHER ISSUES and see if anyone else has asked the same question. We will close any duplicate requests.
* Don't delete any of the words between asterisks.
* Add a key part of the question to the title (ex. [Question] Does Zink work?)
* Follow all of the steps. If you do not provide an answer to each section in this template, the issue will be closed.
-->
**Ask your question here!**
<!-- Be descriptive in your question so that we can provide an equally descriptive answer. Make sure you've checked out the subreddit or the README before asking, as your question might already have an answer. -->
+14
View File
@@ -0,0 +1,14 @@
name: Question
description: 'Want to learn more about the launcher?'
title: "[Question] <Short description>"
labels: [question]
body:
- type: textarea
id: version
attributes:
label: Ask the question here.
description: |
Be descriptive in your question so that we can provide an equally descriptive answer. Make sure you've checked out the subreddit or the README before asking, as your question might already have an answer.
placeholder: 'Example: Login results in a crash'
validations:
required: true