Update issue templates

This commit is contained in:
BlackyHawky 2024-03-09 23:04:16 +01:00 committed by GitHub
parent f9ddcfb434
commit 1eb5fff9bc
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 32 additions and 1 deletions

View file

@ -2,7 +2,7 @@
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
labels: bug
assignees: ''
---

View file

@ -0,0 +1,31 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: enhancement
assignees: ''
---
<!--
Please search open and closed issues to avoid duplicates. Maybe what you want has already been discussed or is mentioned in the Readme.
If you have more than one feature request, open multiple issues (one for each) unless the requests are closely related.
Note that given the number of feature requests and available developer time, it may take a long time until the feature request gets attention.
When a "PR" or "contributor needed" label is added, the feature request is accepted, and interested contributors are welcome to work on this (please comment when you're working on an issue).
-->
**Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of what the problem is. -->
**Describe the solution you'd like**
<!-- A clear and concise description of what you want to happen. -->
**Use case**
<!-- Provide a clear and concise description of *your use case* and what you thus think is missing, and why. -->
**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered (if you can think of any). -->
**Additional context**
<!-- Add any other context or screenshots about the feature request here if suitable and useful.
If you add screenshots, reduce the size or use thumbnails to keep the issue nicely readable. -->