Update bug_report.yml

[w-e-w]

Description

update bug report template

add a checklist with simple debug instruction

use placehoder for example of what should be filled in
so that people have to actually fill in and not just leave the template in

and give actual examples of what we actually expect

perfect example of a type of issue post that I'm trying to avoid
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/12996

demo of how it looks when filling the form
https://github.com/w-e-w/ext-temp-test/issues/new?assignees=&labels=bug-report&projects=&template=bug_report.yml&title=%5BBug%5D%3A+
demo of how it looks after it's posted
w-e-w/ext-temp-test#31

Checklist:

• I have read contributing wiki page
• I have performed a self-review of my own code
• My code follows the style guidelines
• My code passes tests

[AUTOMATIC1111]

Those placeholders look weird...

Can we instead put those texts into the description above the edit box and explicitly mention that the are examples?

[w-e-w]

which placeholder you think it's weird specifically, or do you mean all of them

as we have seen in practice, people don't read descriptions
lots of people don't know what is sysinfo and those who do often upload it as raw text

it's driving me insane, I have mentally copied and then re-uploaded it has file several times now

I think placeholder makes it more obvious and can give actual demonstration of what we want

if you think some placeholder is too much feel free to change them
feel free to make suggestions or change them

[AUTOMATIC1111]

People who don't read descriptions will not read placeholders. The way it is in the PR is confusing even for me. I feel that all placeholders are too much and all examples should be in descriptions, not in placeholders.

[w-e-w]

less placeholder version
Issue: Bug Report v2

original for comparison

only on test report not pushed to this branch yet

[AUTOMATIC1111]

Looks great!

[w-e-w]

pushed less placeholder version