[RFC] Update issue template#12989
Conversation
|
|
What about a part to instruct how to setup the logging to debug and post the logs? |
.github/ISSUE_TEMPLATE.md
Outdated
|
|
||
|
|
||
| **Problem-relevant `configuration.yaml` entries and steps to reproduce:** | ||
| **Related `configuration.yaml` entries (fill out even if it seems unimportant):** |
There was a problem hiding this comment.
What about a link if they have public config?
|
We can certainly add all kinds of questions, instructions and alternatives to the template. In my opinion, though, it should be short and relevant so submitters do not get annoyed halfway through and skip important parts. A documentation page on reporting bugs might be an idea. It could go into much more detail and the user would be in a frame of mind where he was willing to digest the information. |
|
Details are now available in the documentation as well -> #5025 |
|
I removed a single word because we do not need to know the "first broken" release when we also ask for the "last working" release. |
Description:
While cleaning up several platforms, I have gone through a lot of issues. This PR updates the issue template with my experience from that activity: