From 5da4e0f8d9e9b654c410856a57f3537ecb5c8549 Mon Sep 17 00:00:00 2001 From: Jan Schulz Date: Thu, 18 Aug 2016 10:19:17 +0200 Subject: [PATCH] Require a problem description in issues Currently some issues are just code examples without a description **why** a change should be done. This leads to problems when (years later) the current behaviour is questioned and no one can remember why it was changed. --- .github/ISSUE_TEMPLATE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index 8a9f717e1c428..227e07e96861b 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE.md @@ -1,3 +1,7 @@ +#### Problem description + +[this should explain **why** the current behaviour is a problem and why the expected output is a better solution.] + #### Code Sample, a copy-pastable example if possible #### Expected Output