chore: migrate issue templates from markdown to YAML forms (#171)

Replaces placeholder-text markdown templates with structured YAML
issue forms. Dropdowns for installation method, display server, and
audio backend. Required fields for description, steps, and version.
Same output format when reading submitted issues.

cc
This commit is contained in:
vicrodh committed 2026-03-19 13:56:44 -06:00
1 parent 50b9ecb85e
commit f055f53ed5
6 files changed
+230 -142

No files matched your search

-82
View File
@@ -1,82 +0,0 @@
---
name: Bug report
about: Report something that is not working as expected
title: "[Bug] "
labels: bug
assignees: ""
---
## Description
A clear and concise description of the problem.
## Steps to reproduce
1.
2.
3.
## Expected behavior
What you expected to happen.
## Actual behavior
What actually happened.
## Environment
- QBZ version:
- Installation method: <!-- AppImage / .deb / .rpm / AUR / Tarball / Flatpak / Built from source -->
- Distribution:
- Desktop environment / WM:
- Display server: <!-- Wayland / X11 -->
- GPU: <!-- e.g. NVIDIA RTX 3070, AMD RX 6600 XT, Intel Iris Xe -->
- Audio backend (PipeWire / ALSA Direct / PulseAudio):
- Audio device / DAC (if relevant):
## Logs
Logs help us diagnose problems much faster. To share them:
1. Open **Settings > Developer Mode > View Logs**
2. Click **Upload** on both the **Terminal** and **Console** tabs
3. Paste both URLs here:
- Terminal log URL:
- Console log URL:
<details>
<summary><strong>If QBZ crashes on startup</strong> (click to expand)</summary>
Run QBZ from a terminal to capture the output. Use the command that matches your installation:
```bash
# AppImage
./QBZ*.AppImage 2>&1 | tee /tmp/qbz-crash.log
# AUR / Tarball
qbz 2>&1 | tee /tmp/qbz-crash.log
# .deb / .rpm
qbz 2>&1 | tee /tmp/qbz-crash.log
# Flatpak
flatpak run com.blitzfc.qbz 2>&1 | tee /tmp/qbz-crash.log
```
Then upload the log and paste the URL here:
```bash
curl -F'file=@/tmp/qbz-crash.log' https://0x0.st
```
</details>
## Screenshots
If applicable, add screenshots to help illustrate the issue.
## Additional context
Anything else that may help reproduce or understand the issue.
+134
View File
@@ -0,0 +1,134 @@
name: Bug report
description: Report something that is not working as expected
title: "[Bug] "
labels: ["bug"]
body:
- type: textarea
id: description
attributes:
label: Description
description: A clear and concise description of the problem.
validations:
required: true
- type: textarea
id: steps
attributes:
label: Steps to reproduce
value: |
1.
2.
3.
validations:
required: true
- type: textarea
id: expected
attributes:
label: Expected behavior
description: What you expected to happen.
validations:
required: true
- type: textarea
id: actual
attributes:
label: Actual behavior
description: What actually happened.
validations:
required: true
- type: input
id: version
attributes:
label: QBZ version
placeholder: e.g. v1.1.20
validations:
required: true
- type: dropdown
id: install
attributes:
label: Installation method
options:
- AppImage
- .deb
- .rpm
- AUR
- Tarball
- Flatpak
- Built from source
validations:
required: true
- type: input
id: distro
attributes:
label: Distribution
placeholder: e.g. Arch Linux, Ubuntu 24.04, Fedora 43
- type: input
id: de
attributes:
label: Desktop environment / WM
placeholder: e.g. KDE Plasma 6, GNOME 46
- type: dropdown
id: display
attributes:
label: Display server
options:
- Wayland
- X11
- type: input
id: gpu
attributes:
label: GPU
placeholder: e.g. NVIDIA RTX 3070, AMD RX 6600 XT, Intel Iris Xe
- type: dropdown
id: audio_backend
attributes:
label: Audio backend
options:
- PipeWire
- ALSA Direct
- PulseAudio
- Auto
- type: input
id: dac
attributes:
label: Audio device / DAC
placeholder: e.g. Schiit Bifrost 2, FiiO K17
- type: textarea
id: logs
attributes:
label: Logs
description: |
Logs help us diagnose problems much faster.
1. Open **Settings > Developer Mode > View Logs**
2. Click **Upload** on both the **Terminal** and **Console** tabs
3. Paste both URLs here
**If QBZ crashes on startup**, run from terminal:
`flatpak run com.blitzfc.qbz 2>&1 | tee /tmp/qbz-crash.log`
Then upload: `curl -F'file=@/tmp/qbz-crash.log' https://0x0.st`
value: |
- Terminal log URL:
- Console log URL:
- type: textarea
id: screenshots
attributes:
label: Screenshots
description: If applicable, add screenshots to help illustrate the issue.
- type: textarea
id: context
attributes:
label: Additional context
description: Anything else that may help reproduce or understand the issue.
-29
View File
@@ -1,29 +0,0 @@
---
name: Feature request
about: Suggest an idea or improvement
title: "[Feature] "
labels: enhancement
assignees: ""
---
## Problem statement
What problem are you trying to solve?
Why is the current behavior insufficient?
## Proposed solution
Describe the feature or change you would like to see.
## Alternatives considered
Any alternative solutions or workarounds you’ve considered.
## Scope / impact
- Does this affect audio, UI, performance, or packaging?
- Is this platform-specific?
## Additional context
Mockups, references, or related projects are welcome.
@@ -0,0 +1,42 @@
name: Feature request
description: Suggest an idea or improvement
title: "[Feature] "
labels: ["enhancement"]
body:
- type: textarea
id: problem
attributes:
label: Problem statement
description: |
What problem are you trying to solve?
Why is the current behavior insufficient?
validations:
required: true
- type: textarea
id: solution
attributes:
label: Proposed solution
description: Describe the feature or change you would like to see.
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Alternatives considered
description: Any alternative solutions or workarounds you've considered.
- type: textarea
id: scope
attributes:
label: Scope / impact
description: |
- Does this affect audio, UI, performance, or packaging?
- Is this platform-specific?
- type: textarea
id: context
attributes:
label: Additional context
description: Mockups, references, or related projects are welcome.
-31
View File
@@ -1,31 +0,0 @@
---
name: Feedback
about: General feedback, UX thoughts, or non-bug discussion
title: "[Feedback] "
labels: feedback
assignees: ""
---
## Feedback
Share your thoughts, impressions, or experience using QBZ.
## What works well?
(Optional)
## What could be improved?
(Optional)
## Environment (optional)
- QBZ version:
- Installation method: <!-- AppImage / .deb / .rpm / AUR / Tarball / Flatpak / Built from source -->
- Distribution:
- Desktop environment:
- Audio backend:
## Additional notes
Anything else you'd like to share.
+54
View File
@@ -0,0 +1,54 @@
name: Feedback
description: General feedback, UX thoughts, or non-bug discussion
title: "[Feedback] "
labels: ["feedback"]
body:
- type: textarea
id: feedback
attributes:
label: Feedback
description: Share your thoughts, impressions, or experience using QBZ.
validations:
required: true
- type: textarea
id: works-well
attributes:
label: What works well?
- type: textarea
id: improvements
attributes:
label: What could be improved?
- type: input
id: version
attributes:
label: QBZ version (optional)
placeholder: e.g. v1.1.20
- type: dropdown
id: install
attributes:
label: Installation method (optional)
options:
- ""
- AppImage
- .deb
- .rpm
- AUR
- Tarball
- Flatpak
- Built from source
- type: input
id: distro
attributes:
label: Distribution (optional)
placeholder: e.g. Arch Linux, Ubuntu 24.04
- type: textarea
id: notes
attributes:
label: Additional notes
description: Anything else you'd like to share.