Fixes #16627
Can be tested via https://github.com/MarcoFalke/bitcoin/issues
Fixes #16627
Can be tested via https://github.com/MarcoFalke/bitcoin/issues
Concept ACK, I like how this provides the help text in comments instead of in-line, making it harder to have it accidentally end up in the issue text itself.
Concept ACK.
Concept ACK
0 | @@ -0,0 +1,41 @@ 1 | +--- 2 | +name: Bug report 3 | +about: Create a report to help us improve 4 | +title: '' 5 | +labels: bug
Good catch
33 | + 34 | +<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? --> 35 | + 36 | +<!-- What type of machine are you observing the error on (OS/CPU and disk type)? --> 37 | + 38 | +<!-- For the GUI-related issue on Linux provide names and versions of a distro, a desktop environment and a graphical shell (if relevant). -->
GUI-related issue? What is your operation system and its version? If Linux, what is your desktop environment and graphical shell?
Changed
35 | + 36 | +<!-- What type of machine are you observing the error on (OS/CPU and disk type)? --> 37 | + 38 | +<!-- For the GUI-related issue on Linux provide names and versions of a distro, a desktop environment and a graphical shell (if relevant). --> 39 | + 40 | +<!-- Any extra information that might be useful in the debugging process. -->
. -> ?
I think it is fine as is
ACK; Some suggestions
Addressed feedback by @ch4ot1c
16 | @@ -17,7 +17,7 @@ If the node is "stuck" during sync or giving "block checksum mismatch" errors, p 17 | 18 | <!-- What type of machine are you observing the error on (OS/CPU and disk type)? --> 19 | 20 | -<!-- For the GUI-related issue on Linux provide names and versions of a distro, a desktop environment and a graphical shell (if relevant). --> 21 | +<!-- GUI-related issue? What is your operation system and its version? If Linux, what is your desktop environment and graphical shell? --> 22 | 23 | <!-- Any extra information that might be useful in the debugging process. --> 24 | <!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->
These <!--- could be explained as a leading MD - , but don't look great in the issue preview plaintext and never get rendered as Markdown. Maybe instead add a : e.g. Describe the issue:?
I think it is fine to keep this as it was previously
16 | @@ -17,7 +17,7 @@ If the node is "stuck" during sync or giving "block checksum mismatch" errors, p 17 | 18 | <!-- What type of machine are you observing the error on (OS/CPU and disk type)? --> 19 | 20 | -<!-- For the GUI-related issue on Linux provide names and versions of a distro, a desktop environment and a graphical shell (if relevant). --> 21 | +<!-- GUI-related issue? What is your operation system and its version? If Linux, what is your desktop environment and graphical shell? -->
operating
Fixed typo
ACK fabca7756d6908ad581f3a699f1be6ecc9f62e03
ACK fabca7756d6908ad581f3a699f1be6ecc9f62e03
23 | + 24 | +**Actual behavior** 25 | + 26 | +<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? --> 27 | + 28 | +**To reproduce**
Suggest: s/To reproduce/How to reproduce/
This is take from the "official" GitHub template, so I am leaving it for now (unless there is other stuff to fix up)
Concept ACK
Concept ACK.
Could the legacy .github/ISSUE_TEMPLATE.md be removed at all?

Could the legacy .github/ISSUE_TEMPLATE.md be removed at all?
Why? It doesn't cause any harm and it mentions useful advice for non-bug-reports (e.g. that support requests should go to stackexchange)