Rearrange issue template and condense to be more readable
Molly committed
Nov 12, 2018 at 14:12 UTC
3d2d0535b7273d4df273fceb5e596e99caaadafb
1 file changed
+12
-27
ISSUE_TEMPLATE.md
+12
-27
@@ -1,39 +1,24 @@
1
-<!--
2
-🔥❓ If you have a *SUPPORT QUESTION*, please direct it to our forum at https://discuss.ipfs.io. 🔥❓
1
+<!-- 🔥❓ If you have a *QUESTION* about IPFS, please direct it to our forum at https://discuss.ipfs.io. 🔥❓
2
4
-If you haven't yet searched the issue tracker for an existing report concerning your issue, please do so now.
5
-
6
-The go-ipfs issues are only for bug reports and directly actionable feature requests. Read https://github.com/ipfs/community/blob/master/contributing.md#reporting-issues if your issue doesn't fit either of those categories.
7
-
8
-
9
-Read https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue.
10
-
11
-This text is for you; please delete it before posting.
12
--->
3
+The go-ipfs issues are *only for bug reports and directly actionable feature requests*. Please direct all other questions, ideas, or suggestions to our discuss forum. Remember to search the issue tracker for an existing report concerning your issue before posting, and see https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue. -->
4
5
#### Version information:
15
-<!--
16
-Output From `ipfs version --all`
6
+<!-- Output From `ipfs version --all`
7
18
-Please check dist.ipfs.io for a newer version of go-ipfs
19
-and update if neccessary, then check again if the problem persists.
20
--->
8
+Please check dist.ipfs.io for a newer version of go-ipfs and update if necessary, report back if the problem persists. -->
9
10
#### Type:
11
<!-- Bug, Feature, Enhancement, Etc -->
12
13
#### Description:
26
-<!--
27
-This is where you get to tell us what went wrong or what feature you need. When doing so, please make sure to include *all* relevant information.
28
-
29
-When requesting a feature, please be sure to include:
30
-
31
-* Your motivation. Why do you need the feature?
32
-* How the feature should work.
14
+<!-- This is where you get to tell us what went wrong or your specific feature request. When doing so, please make sure to include *all* relevant information.
15
34
-When reporting a bug, please try to include:
16
+When _reporting a bug_, please try to include:
17
+ * What you were doing when you experienced the bug.
18
+ * Any error messages you saw, *where* you saw them, and what you believe may have caused them (if you have any ideas).
19
+ * When possible, steps to reliably produce the bug.
20
36
-* What you were doing when you experienced the bug.
37
-* Any error messages you saw, *where* you saw them, and what you believe may have caused them (if you have any ideas).
38
-* When possible, steps to reliably produce the bug.
21
+When requesting a _feature_, please be sure to include:
22
+ * Your motivation. Why do you need the feature?
23
+ * How the feature should work.
24
-->