GitHub: Improved issue templates

[Lamparter]

Simple change, just added a remarks/comments section to the bug report template to make it match that of the feature/code quality issue templates. Might be useful if the user wants to add a remark such as what they think might be the problem, screenshots, etc. Also fixed a few minor issues in the YAML comments.

[yaira2]

We used to have a longer template, but came to the realization that it's best to keep the form as simple as possible. If applicable, comments can be added to the description section.

[yaira2]

@Lamparter looking at the template, we can further optimize it by removing the requirements section. In most cases, the requirements can be inferred from the description and the steps to reproduce sections.

[0x5bfa]

@yaira2 do you like this?

[yaira2]

Do you mean the tips?

[Lamparter]

Do you mean the tips?

Yes, as in using a blockquote.
I think it's a good idea but ultimately it's up to you 🙂

[0x5bfa]

Yep

[yaira2]

We can try it. So in summary, these are the requested changes:

• Remove comments section
• Remove requirements section
• Add the tips as discussed above

[Lamparter]

It might also be worth it to add a little section asking the user if they've updated Files and see if their issue is fixed on the latest version, like how it used to be in FluentHub.

[yaira2]

Most users tend to be on the latest version, so I think we're okay without that.

[0x5bfa]

Good to me.

[Lamparter]

This PR should probably be renamed.

[yaira2]

I'm not sure if it's because of the wording, but the tip seems to have made things worse.

[Lamparter]

Maybe I should rethink it.

[yaira2]

Perhaps it's the word pasting, should we try Please **upload** the log file by clicking "Attach files".?

[Lamparter]

I think that's better probably, @0x5bfa what do you think?

[0x5bfa]

I don't have preference

[Lamparter]

It would be interesting to see if there's a bot that could automate this by detecting a log in text and wrapping it with a <details/> block.