From bb581c0b9b98b6b59c2af6cbbbef9ef31f66c37e Mon Sep 17 00:00:00 2001
From: Ben Hodgkiss <ben.hodgkiss@levellingup.gov.uk>
Date: Mon, 6 Jul 2026 16:34:23 +0100
Subject: [PATCH] Delete .github/PULL_REQUEST_TEMPLATE.md

Want to use the default one in the `.github` repo
---
 .github/PULL_REQUEST_TEMPLATE.md | 68 --------------------------------
 1 file changed, 68 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 d745a6fff..000000000
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,68 +0,0 @@
-<!--
-     For Work In Progress Pull Requests, please use the Draft PR feature,
-     see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details.
-
-     For a timely review/response, please avoid force-pushing additional
-     commits if your PR already received reviews or comments.
-
-     Before submitting a Pull Request, please ensure you've done the following:
-     - 👷‍♀️ Create small PRs. In most cases, this will be possible.
-     - ✅ Provide tests for your changes.
-     - 📝 Use descriptive commit messages.
-     - 📗 Update any related documentation and include any relevant screenshots.
--->
-
-## Description
-
-_Please replace this line with a brief description of the changes made._
-
-## What type of PR is this? (check all applicable)
-
-- [ ] Refactor
-- [ ] Feature
-- [ ] Bug Fix
-- [ ] Optimization
-- [ ] Documentation Update
-
-## Related Tickets & Documents
-
-<!--
-For pull requests that relate to or close an issue, please include them
-below.  We like to follow [Github's guidance on linking issues to pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
-
-For example, having the text: "closes #1234" would connect the current pull
-request to issue 1234.  And when we merge the pull request, GitHub will
-automatically close the issue.
--->
-- Closes #
-
-## QA Instructions, Screenshots, Recordings
-
-<!--
-Instructions on how to test your changes, a note
-on the devices and browsers, this has been tested on, as well as any relevant
-images for UI changes.
--->
-### Before
-
-_Before screenshot here_
-
-### After
-
-_After screenshot here_
-
-## Added/updated tests?
-_We encourage you to keep the code coverage percentage at 80% and above._
-
-- [ ] Yes
-- [ ] No, and this is why: _Please replace this line with details on why tests have not been included_
-- [ ] I need help with writing tests
-
-## QA sign off
-- [ ] Code has been checked and approved
-- [ ] Design has been checked and approved
-- [ ] Product and business logic has been checked and proved
-
-## [optional] Are there any post-deployment tasks we need to perform?
-
-## [optional] Are there any dependencies on other PRs or Work?