From 22f7a5bd02c4c1cf782612cb268db3d79a5bdb31 Mon Sep 17 00:00:00 2001 From: RoboMWM Date: Mon, 23 Sep 2019 16:39:38 -0700 Subject: [PATCH] Provide an actual example in the feature request template A lot of feature requests are butchering the gherkin statement, so hopefully an example shows that the format and flow should be formatted as such. This format makes it very easy to see what the feature request is and why it is wanted. --- .github/ISSUE_TEMPLATE/feature-request.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/feature-request.md b/.github/ISSUE_TEMPLATE/feature-request.md index 4000e14..945f10a 100644 --- a/.github/ISSUE_TEMPLATE/feature-request.md +++ b/.github/ISSUE_TEMPLATE/feature-request.md @@ -7,8 +7,8 @@ assignees: '' --- -**AS** a player/administrator/etc. -**I WANT** a feature -**BECAUSE** I want to be satisfied with my Minecrafting experience +**As** a player +**I want** to capture animals in a snowball +**Because** I wanna be the very best, Like no one ever was. Here's how to increase your chances of your feature request being understood (and potentially considered for implementation): https://content.pivotal.io/blog/how-to-write-well-formed-user-stories