From 00868ab4e2792189501c576b7de3ea61ce0c3fb7 Mon Sep 17 00:00:00 2001 From: Delyan Angelov Date: Mon, 21 Aug 2023 11:18:20 +0300 Subject: [PATCH] Move the reproduction field to the top in bug-report.yml It is confusing to have one of the most important fields buried below others. Moving it to the top makes reviewing bug reports easier and faster. --- .github/ISSUE_TEMPLATE/bug-report.yml | 28 +++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml index c590332db..1d359b211 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.yml +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -10,6 +10,20 @@ body: validations: required: true + - type: textarea + id: reproduction + attributes: + label: Reproduction Steps + description: | + Provide a self-contained, concise snippet of code that can be used to reproduce the issue. + For more complex issues provide a repo with the smallest sample that reproduces the bug. + + Avoid including business logic or unrelated code, it makes diagnosis more difficult. + The code sample should be an SSCCE. See http://sscce.org/ for details. + In short, please provide a code sample that we can copy/paste, run and reproduce. + validations: + required: true + - type: textarea id: expected attributes: @@ -30,20 +44,6 @@ body: validations: required: true - - type: textarea - id: reproduction - attributes: - label: Reproduction Steps - description: | - Provide a self-contained, concise snippet of code that can be used to reproduce the issue. - For more complex issues provide a repo with the smallest sample that reproduces the bug. - - Avoid including business logic or unrelated code, it makes diagnosis more difficult. - The code sample should be an SSCCE. See http://sscce.org/ for details. - In short, please provide a code sample that we can copy/paste, run and reproduce. - validations: - required: true - - type: textarea id: solution attributes: -- 2.39.5