From 0cb4cd159e4fba6644db4a7b43183c9fd45ed7cd Mon Sep 17 00:00:00 2001 From: metagn Date: Thu, 27 Feb 2025 18:48:53 +0300 Subject: [PATCH] move nim version in issue template to the top (#24733) The point is to move it out of the current place between "Description" and "Current Output" as often these are related to each other and including the nim version in the middle breaks the flow of reading. I also thought of moving it below "Expected Output" but this felt too low for a required field and also has the same problem of overshadowing the remaining sections. Not sure if it being at the top is annoying in some other way though. --- .github/ISSUE_TEMPLATE/bug_report.yml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 1e46e05448..52b2d80b44 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -10,6 +10,16 @@ body: Please provide a minimal code example that reproduces the bug if possible. Reports with a reproducible example or detailed information will likely receive fixes faster. +- type: textarea + id: nim-version + attributes: + label: Nim Version + description: | + Can be obtained from `nim -v` on the command line along with the OS/architecture. + For development versions, including the commit hash may help. + validations: + required: true + - type: textarea id: description attributes: @@ -19,16 +29,6 @@ body: placeholder: Bug reports with reproducible code or detailed information will be fixed faster. validations: required: true - -- type: textarea - id: nim-version - attributes: - label: Nim Version - description: | - Can be obtained from `nim -v` on the command line along with the OS/architecture. - For development versions, make sure to include the commit hash. - validations: - required: true - type: textarea id: current-logs