Skip to content

Commit 5b4e688

Browse files
author
MarcoFalke
committed
Merge #16806: doc: Add issue templates for bug and feature request
fabca77 doc: Add issue templates for bug and feature request (MarcoFalke) Pull request description: Fixes #16627 Can be tested via https://github.com/MarcoFalke/bitcoin/issues ACKs for top commit: jb55: ACK fabca77 fanquake: ACK fabca77 Tree-SHA512: 1ebe58f9c0110a9332adf1d80001cd9ed6fe60208e387c93b8564dc66821f753e34b23cb6f4cae45168024862ee884913976e132820b7a4759fa6391b0d1127c
2 parents 4c329d4 + fabca77 commit 5b4e688

File tree

3 files changed

+62
-1
lines changed

3 files changed

+62
-1
lines changed

.github/ISSUE_TEMPLATE.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ If the node is "stuck" during sync or giving "block checksum mismatch" errors, p
1717

1818
<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
1919

20-
<!-- For the GUI-related issue on Linux provide names and versions of a distro, a desktop environment and a graphical shell (if relevant). -->
20+
<!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->
2121

2222
<!-- Any extra information that might be useful in the debugging process. -->
2323
<!--- 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. -->

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: Bug
6+
assignees: ''
7+
8+
---
9+
10+
<!-- This issue tracker is only for technical issues related to Bitcoin Core.
11+
12+
General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com.
13+
14+
For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/.
15+
16+
If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->
17+
18+
<!-- Describe the issue -->
19+
20+
**Expected behavior**
21+
22+
<!--- What behavior did you expect? -->
23+
24+
**Actual behavior**
25+
26+
<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->
27+
28+
**To reproduce**
29+
30+
<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
31+
32+
**System information**
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+
<!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->
39+
40+
<!-- Any extra information that might be useful in the debugging process. -->
41+
<!--- 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. -->
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: Feature
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
12+
13+
**Describe the solution you'd like**
14+
<!-- A clear and concise description of what you want to happen. -->
15+
16+
**Describe alternatives you've considered**
17+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
18+
19+
**Additional context**
20+
<!-- Add any other context or screenshots about the feature request here. -->

0 commit comments

Comments
 (0)