diff options
| author | trwnh <a@trwnh.com> | 2021-11-24 13:24:09 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-11-24 20:24:09 +0100 |
| commit | 08a7c5139d34050061b17d9ea562ab29aec81a45 (patch) | |
| tree | 791362d420f3019e5fb9e93467eef3de845c619e /.github | |
| parent | 02a87431cf260e466ff58cc159b52cbce9aaef6b (diff) | |
Better ordering for bug report issue template (#17019)
Logically, it makes more sense to provide the steps leading up to the bug before asking what the bug is. This change moves "steps to reproduce" above "expected behavior" and "actual behavior" to enforce the above progression and logical flow.
Diffstat (limited to '.github')
| -rw-r--r-- | .github/ISSUE_TEMPLATE/1.bug_report.yml | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/.github/ISSUE_TEMPLATE/1.bug_report.yml b/.github/ISSUE_TEMPLATE/1.bug_report.yml index 4f420416b..9cdf813f7 100644 --- a/.github/ISSUE_TEMPLATE/1.bug_report.yml +++ b/.github/ISSUE_TEMPLATE/1.bug_report.yml @@ -8,6 +8,17 @@ body: Make sure that you are submitting a new bug that was not previously reported or already fixed. Please use a concise and distinct title for the issue. + - type: textarea + attributes: + label: Steps to reproduce the problem + description: What were you trying to do? + value: | + 1. + 2. + 3. + ... + validations: + required: true - type: input attributes: label: Expected behaviour @@ -22,17 +33,6 @@ body: required: true - type: textarea attributes: - label: Steps to reproduce the problem - description: What were you trying to do? - value: | - 1. - 2. - 3. - ... - validations: - required: true - - type: textarea - attributes: label: Specifications description: | What version or commit hash of Mastodon did you find this bug in? |