Files
MINGW-packages/.github/ISSUE_TEMPLATE/bug_report.yml
Christoph Reiter 752ef871dd bug_report template: try to simplify it a bit
There are two main changes:

* Description and reproduction steps are merged at the top, so
  users don't descripe the bug and then later on have to fill
  out the steps again, possibly writing the same things twice slightly differently.
  This flow feels more natural imo.

* Recomend "uname" instead of "cmd.exe /c ver", the later is tricky
  because of path conversion of "/c", and uname has the same info basically.
2022-12-17 17:14:20 +01:00

62 lines
1.8 KiB
YAML

name: Bug Report
description: Submit a bug report.
labels: [bug]
body:
- type: textarea
attributes:
label: Description / Steps to reproduce the issue
description: A clear and concise description of what the bug is, and why you consider it to be a bug, and steps for how to reproduce it
placeholder: |
A description with steps to reproduce the issue.
1. Step 1
2. Step 2
validations:
required: true
- type: textarea
attributes:
label: Expected behavior
description: A description of what you expected to happen.
validations:
required: true
- type: textarea
attributes:
label: Actual behavior
description: A description of what is actually happening.
validations:
required: true
- type: checkboxes
attributes:
label: Verification
description: Please verify that you've followed these steps.
options:
- label: I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)
required: true
- type: input
attributes:
label: Windows Version
description: Please run `uname` to get the build of Windows you are on.
placeholder: "MSYS_NT-10.0-22621"
validations:
required: true
- type: checkboxes
attributes:
label: MINGW environments affected
description: The environment name can be found in shell prompt. Or run `echo $MSYSTEM` to get the MINGW environment.
options:
- label: MINGW64
- label: MINGW32
- label: UCRT64
- label: CLANG64
- label: CLANG32
- label: CLANGARM64
- type: input
attributes:
label: Are you willing to submit a PR?
description: We accept contributions!