summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStephen Day <stevvooe@users.noreply.github.com>2016-09-12 14:30:24 -0700
committerGitHub <noreply@github.com>2016-09-12 14:30:24 -0700
commit4832029c0abc1574a5bb16917f19fe2150beb2e5 (patch)
treee17d34292d31aaf33c2cf328b675e5f856a32bfc
parent6edf09cf5821aa947d9d52e21d72b065184fc421 (diff)
downloaddocker-stevvooe-patch-1.tar.gz
issues: re-order issue template for more claritystevvooe-patch-1
Triaging issues has become a little challenging since the meat of the information is below a large amount of unstructured command line output. These changes add a description and move the reproduction and expected/received results above the unstructured output. This should help for initial triaging, as well as self-triaging.
-rw-r--r--.github/ISSUE_TEMPLATE.md34
1 files changed, 18 insertions, 16 deletions
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index 53e518f780..6f7d46db54 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -19,29 +19,17 @@ Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->
-**Output of `docker version`:**
-
-```
-(paste your output here)
-```
-
-
-**Output of `docker info`:**
-
-```
-(paste your output here)
-```
-
-**Additional environment details (AWS, VirtualBox, physical, etc.):**
-
+**Description**
+<!--
+Briefly describe the problem your having in a few paragraphs.
+-->
**Steps to reproduce the issue:**
1.
2.
3.
-
**Describe the results you received:**
@@ -49,3 +37,17 @@ You do NOT have to include this information if this is a FEATURE REQUEST
**Additional information you deem important (e.g. issue happens only occasionally):**
+
+**Output of `docker version`:**
+
+```
+(paste your output here)
+```
+
+**Output of `docker info`:**
+
+```
+(paste your output here)
+```
+
+**Additional environment details (AWS, VirtualBox, physical, etc.):**