From d0002697eceb3f4d52463faf59ad600602bf096d Mon Sep 17 00:00:00 2001
From: SikkieNL <sikkienl@outlook.com>
Date: Tue, 17 Dec 2024 06:19:59 +0100
Subject: [PATCH] Delete .getea/ISSUE_TEMPLATE/bug_report.md

---
 .getea/ISSUE_TEMPLATE/bug_report.md | 41 -----------------------------
 1 file changed, 41 deletions(-)
 delete mode 100644 .getea/ISSUE_TEMPLATE/bug_report.md

diff --git a/.getea/ISSUE_TEMPLATE/bug_report.md b/.getea/ISSUE_TEMPLATE/bug_report.md
deleted file mode 100644
index b675f0b79..000000000
--- a/.getea/ISSUE_TEMPLATE/bug_report.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-name: Bug report
-about: Create a report to help us improve (use this for suspected bugs only, if not sure, open a regular issue below)
-title: ''
-labels: Bug
-assignees: ''
-
----
-
-<!-- This issue tracker is only for technical issues related to Neobytes Core.
-
-General neobytes questions and/or support requests are best directed to the Neobytes StackExchange at https://neobytes.stackexchange.com.
-
-For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/.
-
-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! -->
-
-<!-- Describe the issue -->
-
-**Expected behavior**
-
-<!--- What behavior did you expect? -->
-
-**Actual behavior**
-
-<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->
-
-**To reproduce**
-
-<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
-
-**System information**
-
-<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->
-
-<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
-
-<!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->
-
-<!-- Any extra information that might be useful in the debugging process. -->
-<!--- 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. -->