mitmproxy/issue_template.md

##### Steps to reproduce the problem:

1.
2.
3.


##### Any other comments? What have you tried so far?


##### System information


<!--
    Cut and paste the output of "mitmproxy --version".

    If you're using an older version if mitmproxy, please specify the version
    and OS.
-->
add issue template 2016-02-17 19:38:51 +00:00			`##### Steps to reproduce the problem:`
simplify issue template 2016-02-18 10:30:16 +00:00
Adjust issue template - Mention mitmdump --sysinfo - Remove the "what went wrong" and "what was the expected behaviour" sections. It's a bit officious, and 99% of the time is explicit from the problem description. 2016-10-21 21:20:45 +00:00			`1.`
			`2.`
			`3.`
add issue template 2016-02-17 19:38:51 +00:00

Update issue_template.md 2016-05-20 02:57:25 +00:00			`##### Any other comments? What have you tried so far?`
add issue template 2016-02-17 19:38:51 +00:00


Adjust issue template - Mention mitmdump --sysinfo - Remove the "what went wrong" and "what was the expected behaviour" sections. It's a bit officious, and 99% of the time is explicit from the problem description. 2016-10-21 21:20:45 +00:00			`##### System information`

Move the admonision to use Discourse in the issue template to the bottom Github integrations get the raw issue text, which means that the context we see in-channel is mostly the admonition. I think it's visible enough at the bottom to catch most users who would have paid attention to it if it were at the top. 2016-06-02 05:11:23 +00:00
Adjust issue template - Mention mitmdump --sysinfo - Remove the "what went wrong" and "what was the expected behaviour" sections. It's a bit officious, and 99% of the time is explicit from the problem description. 2016-10-21 21:20:45 +00:00			`<!--`
provide git information with --version fixes #1848 2017-01-19 13:00:50 +00:00			`Cut and paste the output of "mitmproxy --version".`
Move the admonision to use Discourse in the issue template to the bottom Github integrations get the raw issue text, which means that the context we see in-channel is mostly the admonition. I think it's visible enough at the bottom to catch most users who would have paid attention to it if it were at the top. 2016-06-02 05:11:23 +00:00
Adjust issue template - Mention mitmdump --sysinfo - Remove the "what went wrong" and "what was the expected behaviour" sections. It's a bit officious, and 99% of the time is explicit from the problem description. 2016-10-21 21:20:45 +00:00			`If you're using an older version if mitmproxy, please specify the version`
			`and OS.`
			`-->`