From eb68e1d29461efae84c7a47e17746ce381182e3b Mon Sep 17 00:00:00 2001
From: Andrew Pareles <43356051+andrewpareles@users.noreply.github.com>
Date: Thu, 17 Apr 2025 18:38:55 -0700
Subject: [PATCH] Update issue_template.md

---
 .github/issue_template.md | 35 +++++------------------------------
 1 file changed, 5 insertions(+), 30 deletions(-)

diff --git a/.github/issue_template.md b/.github/issue_template.md
index 232373d8..fe17c58e 100644
--- a/.github/issue_template.md
+++ b/.github/issue_template.md
@@ -1,35 +1,10 @@
 ---
-name: Pull Request
-about: Submit a pull request to Void
-title: ''
-labels: ''
-assignees: ''
+name: Issue
+about: Submit an Issue to Void
 ---
 
-**Please provide the following information before submitting:**
+1. For VSCode-related issues, please start the title with `[App]`. Otherwise, start it with `[Bug]` or `[Feature]`.
 
-*   **Operating System Information:**
-    *   Press `Ctrl+Shift+P` (or `Cmd+Shift+P` on macOS).
-    *   Type `> Help: About`.
-    *   Copy the full version and OS information shown and paste it below:
-    ```
-    (Paste OS Information Here)
-    ```
+2. Press `Cmd+Shift+P` in Void, and type `Help: About`. Paste the information here!
 
-**Pull Request Title Convention:**
-
-*   For **new features** or feature requests, please start the title with `[Feature]`. Example: `[Feature] Add user login functionality`
-*   For **bugs**, please start the title with `[Bug]`. Example: `[Bug] Fix alignment issue on settings page`
-*   For **other types of changes** (e.g., documentation, refactoring, chores), use a descriptive title without a specific prefix or choose an appropriate one (e.g., `[Docs]`, `[Refactor]`).
-
-**Description of Changes:**
-
-Tell us a bit about what you did. We prefer concise descriptions :)
-
-**Related Issue(s):**
-
-If this issue is related to any PRs, please link them here (or vice versa).
-
-**Checklist:**
-*   [ ] I have read the **CONTRIBUTING.md** document.
-*   [ ] The title of this PR follows the specified convention.
+3. Tell us a bit about the issue. We prefer concise descriptions :) Don't forget to link to related issues/PRs with #number.