From 1d3b189684426fedb706fe885caf51f6a1d45051 Mon Sep 17 00:00:00 2001
From: Marius Storhaug <marstor@hotmail.com>
Date: Sat, 31 Oct 2026 22:30:30 +0100
Subject: [PATCH] Remove repository pull request template

---
 .github/pull_request_template.md | 36 --------------------------------
 1 file changed, 36 deletions(-)
 delete mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
deleted file mode 100644
index ff2067e..0000000
--- a/.github/pull_request_template.md
+++ /dev/null
@@ -1,36 +0,0 @@
-<!-- markdownlint-disable MD041 -->
-<!--
-This description becomes the release note. Write it for users of the module, not for reviewers.
-
-Title: <Icon> [<Type>]: <User-facing outcome>
-  🌟 [Major] · 🚀 [Feature] · 🩹 [Patch] · 🪲 [Fix] · 📖 [Docs] · ⚙️ [Maintenance]
-
-Apply the matching label: Major, Minor, Patch, or NoRelease.
-Full format: https://msxorg.github.io/docs/Ways-of-Working/PR-Format/
-
-Delete the comments and any unused section before marking the pull request ready.
--->
-
-<!-- One paragraph, present tense, describing what changes for the user. -->
-
-## New: <capability>
-
-<!--
-What the user can now do, what they need to do differently, and an example.
-Use the section headers that fit the change and delete the rest:
-  ## Breaking Changes   - what stopped working or changed incompatibly (Major only)
-  ## New: <capability>  - new things the user can do
-  ## Changed: <behavior> - existing behavior that now works differently
-  ## Fixed: <problem>   - problems now resolved
--->
-
-## Technical Details
-
-<!-- For reviewers: files touched, design decisions, migration notes. Delete this section if there is nothing noteworthy. -->
-
-<details>
-<summary>Related issues</summary>
-
-<!-- Use fully qualified references, for example: Fixes PSModule/Repo#123 -->
-
-</details>