From 0cb4aa0680f58deca32b484bf7bdf54bcc3e51e8 Mon Sep 17 00:00:00 2001
From: theKnightsOfRohan <114779675+theKnightsOfRohan@users.noreply.github.com>
Date: Fri, 5 Jan 2024 20:48:57 -0800
Subject: [PATCH 1/2] Create bug_report.yml

---
 .github/ISSUE_TEMPLATE/bug_report.yml | 51 +++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 0000000..857fb03
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,51 @@
+name: Bug Report
+description: File a bug report
+title: "[Bug]"
+labels: bug
+body: 
+  - type: textarea
+    id: issue
+    attributes:
+      label: Description of the issue
+      description: What's the issue you encountered?
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Reproduction steps
+      description: How can the issue be reproduced?
+      placeholder: Describe each step as precisely as possible
+    validations:
+      required: true
+  - type: textarea
+    id: log
+    attributes:
+      label: Log file
+      description: Reproduce the issue exactly in a new neovim session, then run the neovim command `:lua require("harpoon.logger"):show()`
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Neovim Version
+      description: In your terminal, run `nvim --version`
+      placeholder: "e.g. 0.9.4"
+    validations:
+      required: true
+  - type: textarea
+    id: config
+    attributes:
+      label: Minimal Config
+      description: For ease of replication in the case of complex behaviour, paste a small config under which the bug occurs.
+    validations:
+      required: true
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context?
+      description: |
+        - Additional info about your environment:
+        - Any other information relevant to your issue.
+    validations:
+      required: false

From f349a66c76a82947aefb011d4c3c0f934b1c898f Mon Sep 17 00:00:00 2001
From: theKnightsOfRohan <114779675+theKnightsOfRohan@users.noreply.github.com>
Date: Fri, 5 Jan 2024 20:49:35 -0800
Subject: [PATCH 2/2] Create feature_request.yml

---
 .github/ISSUE_TEMPLATE/feature_request.yml | 31 ++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml

diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
new file mode 100644
index 0000000..8a56ea1
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,31 @@
+name: Feature Request
+description: Suggest a new feature for Harpoon.
+title: "[Feature Request]"
+body:
+  - type: textarea
+    id: overview
+    attributes:
+      label: Overview
+      description: Include the basic, high-level concepts for this feature here.
+    validations:
+      required: true
+  - type: textarea
+    id: details
+    attributes:
+      label: Smaller details
+      description: These may include specific methods of implementation etc.
+    validations:
+      required: true
+  - type: textarea
+    id: request
+    attributes:
+      label: Nature of request
+    validations:
+      required: true
+  - type: textarea
+    id: feature
+    attributes:
+      label: Why would this feature be useful?
+      description: Remember that harpoon should not solve every problem, but provide the hooks required to solve them.
+    validations:
+      required: true