From b309b9a787a0944c669aa582134e0f787be48fc5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Yves=20Desgagn=C3=A9?= <yves@cloudofficer.ca>
Date: Wed, 15 Apr 2026 09:57:28 -0400
Subject: [PATCH] Remove GitHub pull request template

---
 .github/pull_request_template.md | 40 --------------------------------
 1 file changed, 40 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 9edb1c3..0000000
--- a/.github/pull_request_template.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# Summary
-
-Describe the summary/big picture of your changes here to communicate to the maintainers why we should accept this pull request.
-
-## Types of changes
-
-<!--
-What types of changes does your code introduce? Put an `x` in the boxes that apply (no space around the brackets).
--->
-
-- [ ] Bugfix (fixes an issue)
-- [ ] New feature (adds functionality)
-- [ ] Refactoring (improves code without changing functionality)
-- [ ] Breaking change (incompatible changes)
-- [ ] Build or security update (updates dependencies, libraries, or security patches)
-- [ ] Code style or documentation update (formatting, renaming, or documentation changes)
-- [ ] Other (please describe):
-
-## Checklist
-
-<!--
-Put an `x` in the boxes that apply (no space around the brackets). This is simply a reminder of what we are going to look for before merging your code.
--->
-
-- [ ] Unit tests added to validate my fix/feature
-- [ ] I have manually tested my change
-- [ ] I did not add automation test. Why ?:
-- [ ] Database changes requiring migration with downtime or reprocessing of existing data
-- [ ] The SOUP file lists the risk Level, requirements and verification reasoning associated with each library
-- [ ] `readme.md` includes sections on introduction, installation, usage, and contributing
-- [ ] `docs/architecture.md` includes sections on the architecture diagram, software units, software of unknown provenance, critical algorithms and risk controls related to PII and security
-- [ ] Impact on PII, privacy regulations (CCPA/GDPR/PIPEDA), CIS benchmarks or security (availability/confidentiality/integrity); management must be notified
-
-## Further comments (if required)
-
-<!--
-Add comments here if breaking changes, complex database migration or reprocessing of existing data are required.
-
-If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
--->