Rearrange issue template and condense to be more readable

This commit is contained in:
Molly 2018-11-12 14:12:23 -08:00 committed by GitHub
parent 750052f491
commit 3d2d0535b7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -1,39 +1,24 @@
<!--
🔥❓ If you have a *SUPPORT QUESTION*, please direct it to our forum at https://discuss.ipfs.io. 🔥❓
<!-- 🔥❓ If you have a *QUESTION* about IPFS, please direct it to our forum at https://discuss.ipfs.io. 🔥❓
If you haven't yet searched the issue tracker for an existing report concerning your issue, please do so now.
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.
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.
This text is for you; please delete it before posting.
-->
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. -->
#### Version information:
<!--
Output From `ipfs version --all`
<!-- Output From `ipfs version --all`
Please check dist.ipfs.io for a newer version of go-ipfs
and update if neccessary, then check again if the problem persists.
-->
Please check dist.ipfs.io for a newer version of go-ipfs and update if necessary, report back if the problem persists. -->
#### Type:
<!-- Bug, Feature, Enhancement, Etc -->
#### Description:
<!--
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.
<!-- 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.
When requesting a feature, please be sure to include:
When _reporting a bug_, please try to include:
* What you were doing when you experienced the bug.
* Any error messages you saw, *where* you saw them, and what you believe may have caused them (if you have any ideas).
* When possible, steps to reliably produce the bug.
* Your motivation. Why do you need the feature?
* How the feature should work.
When reporting a bug, please try to include:
* What you were doing when you experienced the bug.
* Any error messages you saw, *where* you saw them, and what you believe may have caused them (if you have any ideas).
* When possible, steps to reliably produce the bug.
When requesting a _feature_, please be sure to include:
* Your motivation. Why do you need the feature?
* How the feature should work.
-->