Add issue templates for bugs & features, based off of lazy.nvim

Author: MeanderingProgrammer

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,41 @@
+name: Bug Report
+description: File a bug / issue
+title: "bug: "
+labels: [bug]
+body:
+  - type: input
+    attributes:
+      label: "Neovim version (nvim -v)"
+      placeholder: "0.9.5"
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: "Operating system"
+      placeholder: "MacOS"
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: "Terminal emulator / GUI"
+      placeholder: "WezTerm"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the bug
+      description: A description of what the bug is. Please include any related errors you see.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: A description of what you expected to happen.
+    validations:
+      required: true 
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Any additional information you would like to provide.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,29 @@
+name: Feature Request
+description: Suggest a new feature
+title: "feature: "
+labels: [enhancement]
+body:
+  - type: textarea
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A description of what the problem is. Ex. I'm always frustrated when [...]
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: A description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      description: A description of any alternative solutions or features you've considered.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Any additional information you would like to provide.
+    validations:
+      required: false

TROUBLESHOOTING.md

@@ -31,17 +31,7 @@ the `filetype` of the current buffer and make sure it is in that list:
 :lua vim.print(vim.bo.filetype)
 ```
 
-## Create an Issue
-
-Create an issue in this repo with the following information:
-
-- Description of your problem
-- Operating system
-- Version of neovim
-- Terminal emulator / GUI
-- Debug logs, steps to generate these are below
-
-### Generating debug logs
+## Generating debug logs
 
 If all else fails hopefully the logs can provide some insight. This plugin
 ships with logging, however it only includes errors by default.
@@ -53,7 +43,7 @@ To help debug your issue you'll need to go through the following steps:
 3. Generate logs from the test file
 4. Provide the logs in the issue
 
-#### Update the log level to `debug`
+### Update the log level to `debug`
 
 Change the plugin configuration to:
 
@@ -63,7 +53,7 @@ require('render-markdown').setup({
 })
 ```
 
-#### Create a test file
+### Create a test file
 
 Create a new `markdown` file locally with the following content:
 
@@ -80,13 +70,13 @@ Create a new `markdown` file locally with the following content:
 - [x] Checked
 ```
 
-#### Generate logs from the test file
+### Generate logs from the test file
 
 To do this restart Neovim and open the `markdown` file from the previous step.
 
 This should trigger the render function by default, then close Neovim.
 
-#### Provide the logs in the issue
+### Provide the logs in the issue
 
 Logs are written to a file typically located at: `~/.local/state/nvim/render-markdown.log`.