From b0aad345bf9f7c7689c1717da92789b2dc5195b8 Mon Sep 17 00:00:00 2001 From: Ben Noordhuis Date: Tue, 14 Mar 2023 11:20:13 +0100 Subject: [PATCH] meta: ask expected behavior reason in bug template It happens too often that bug reporters only report _what_ they expect to see without motivating _why_. Having to repeatedly ask for that info gets old. PR-URL: https://github.com/nodejs/node/pull/47049 Reviewed-By: Moshe Atlow Reviewed-By: Debadree Chatterjee Reviewed-By: Mohammed Keyvanzadeh Reviewed-By: Yagiz Nizipli Reviewed-By: Colin Ihrig Reviewed-By: Darshan Sen Reviewed-By: Luigi Pinca --- .github/ISSUE_TEMPLATE/1-bug-report.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/1-bug-report.yml b/.github/ISSUE_TEMPLATE/1-bug-report.yml index c40644bfc6d9ba..496d06d3ad70b8 100644 --- a/.github/ISSUE_TEMPLATE/1-bug-report.yml +++ b/.github/ISSUE_TEMPLATE/1-bug-report.yml @@ -33,7 +33,7 @@ body: label: How often does it reproduce? Is there a required condition? - type: textarea attributes: - label: What is the expected behavior? + label: What is the expected behavior? Why is that the expected behavior? description: If possible please provide textual output instead of screenshots. - type: textarea attributes: