hyprlock/.github/ISSUE_TEMPLATE/bug.yml
Maximilian Seidler 3e71799b30
misc: add issue templates (#440)
* misc: add issue templates

Copied from Hyprland and slightly modified

* misc: but template --version and minor improvements

* misc: fix bug template closing tag
2024-07-24 17:52:15 +02:00

104 lines
2.8 KiB
YAML

name: Bug Report
description: Something is not working right
labels: ["bug"]
body:
- type: markdown
attributes:
value: |
## Before opening a new issue, please take a moment to search through the current open and closed issues to check if it already exists.
---
- type: dropdown
id: type
attributes:
label: Regression?
description: |
Regression means that something used to work but no longer does.
**BEFORE CONTINUING**, please check if this bug is a regression or not, and if it is, we need you to bisect with the help of the wiki: https://wiki.hyprland.org/Crashes-and-Bugs/#bisecting-an-issue
multiple: true
options:
- "Yes"
- "No"
validations:
required: true
- type: textarea
id: ver
attributes:
label: Hyprlock Info and Version
description: |
Please enter your hyprlock version and config.
Use `hyprlock --version` if it is available (Introduced after v0.4.1).
Otherwise please figure out the hyprlock version via your distribution.
If you built it yourself, post the commit hash.
Provide your hyprlock config. Usually `~/.config/hypr/hyprlock.conf`.
value: "<Enter your hyprlock version here>
<details>
<summary>Hyprlock config</summary>
```sh
<Paste your hyprlock config here>
```
</details>"
validations:
required: true
- type: textarea
id: compositor
attributes:
label: Compositor Info and Version
description: |
If you are on hyprland, paste the output of `hyprctl systeminfo` here.
If you are on another compositor, enter the compositor name and version you are on.
value: "<details>
<summary>System/Version info</summary>
```sh
<Paste the output of the command here>
```
</details>"
validations:
required: true
- type: textarea
id: desc
attributes:
label: Description
description: "What went wrong?"
validations:
required: true
- type: textarea
id: repro
attributes:
label: How to reproduce
description: "How can someone else reproduce the issue?"
validations:
required: true
- type: textarea
id: logs
attributes:
label: Crash reports, logs, images, videos
description: |
Anything that can help. Please always ATTACH and not paste them.
To get hyprlock logs, start it from the commandline.
If you are using hypridle/swayidle as a systemd service, you can use `journalctl -b0 --user -u hypridle/swayidle` to get some logs.
Compositor logs and crashes are sometimes relevant as well.
Hyprland logs can be found in $XDG_RUNTIME_DIR/hypr.
Hyprland crash reports are stored in ~/.cache/hyprland or $XDG_CACHE_HOME/hyprland.