Skip to content

Commit be3bc48

Browse files
committed
issues: re-order issue template for more clarity
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. Signed-off-by: Stephen J Day <[email protected]>
1 parent 6edf09c commit be3bc48

File tree

1 file changed

+18
-16
lines changed

1 file changed

+18
-16
lines changed

.github/ISSUE_TEMPLATE.md

+18-16
Original file line numberDiff line numberDiff line change
@@ -19,33 +19,35 @@ Use the commands below to provide key information from your environment:
1919
You do NOT have to include this information if this is a FEATURE REQUEST
2020
-->
2121

22-
**Output of `docker version`:**
23-
24-
```
25-
(paste your output here)
26-
```
27-
28-
29-
**Output of `docker info`:**
30-
31-
```
32-
(paste your output here)
33-
```
34-
35-
**Additional environment details (AWS, VirtualBox, physical, etc.):**
36-
22+
**Description**
3723

24+
<!--
25+
Briefly describe the problem your having in a few paragraphs.
26+
-->
3827

3928
**Steps to reproduce the issue:**
4029
1.
4130
2.
4231
3.
4332

44-
4533
**Describe the results you received:**
4634

4735

4836
**Describe the results you expected:**
4937

5038

5139
**Additional information you deem important (e.g. issue happens only occasionally):**
40+
41+
**Output of `docker version`:**
42+
43+
```
44+
(paste your output here)
45+
```
46+
47+
**Output of `docker info`:**
48+
49+
```
50+
(paste your output here)
51+
```
52+
53+
**Additional environment details (AWS, VirtualBox, physical, etc.):**

0 commit comments

Comments
 (0)