From 74cd510a36d72a3e3b37ea2135a1eeaba9bedabc Mon Sep 17 00:00:00 2001
From: gkodinov <joro@mariadb.com>
Date: Wed, 17 Dec 2025 15:32:53 +0200
Subject: [PATCH] MDEV-38363 Remove pull_request_template.md

The template in pull_request_template.md is out of date and a documentation
rather than a pull request description. This was not really contriburing
a lot towards good pull request descriptions as most of the time it had to
be removed first before the actual descrption is written down.
Removed the pull_request_template.md as discussed in PR#4209

Note that there is a follow-up work in progress (and it will eventually
result in a pull request) to update the text in other contribution
related documents.
But removing this not-really-a-template template is going to produce
an immediate improvement into the contribution process.
---
 .github/pull_request_template.md | 51 --------------------------------
 1 file changed, 51 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 7a34e193b3548..0000000000000
--- a/.github/pull_request_template.md
+++ /dev/null
@@ -1,51 +0,0 @@
-<!--
-Thank you for contributing to the MariaDB Server repository!
-
-You can help us review your changes faster by filling in this template <3
-
-If you have any questions related to MariaDB or you just want to hang out and meet other community members, please join us on https://mariadb.zulipchat.com/ .
--->
-
-<!--
-If you've already identified a https://jira.mariadb.org/ issue that seems to track this bug/feature, please add its number below.
--->
-- [x] *The Jira issue number for this PR is: MDEV-______*
-
-<!--
-An amazing description should answer some questions like:
-1. What problem is the patch trying to solve?
-2. If some output changed that is not visible in a test case, what was it looking like before the change and how it's looking with this patch applied?
-3. Do you think this patch might introduce side-effects in other parts of the server?
--->
-## Description
-TODO: fill description here
-
-## Release Notes
-TODO: What should the release notes say about this change?
-Include any changed system variables, status variables or behaviour. Optionally list any https://mariadb.com/kb/ pages that need changing.
-
-## How can this PR be tested?
-
-TODO: modify the automated test suite to verify that the PR causes MariaDB to behave as intended.
-Consult the documentation on ["Writing good test cases"](https://mariadb.org/get-involved/getting-started-for-developers/writing-good-test-cases-mariadb-server).
-<!--
-In many cases, this will be as simple as modifying one `.test` and one `.result` file in the `mysql-test/` subdirectory.
-Without automated tests, future regressions in the expected behavior can't be automatically detected and verified.
--->
-
-If the changes are not amenable to automated testing, please explain why not and carefully describe how to test manually.
-
-<!--
-Tick one of the following boxes [x] to help us understand if the base branch for the PR is correct.
--->
-## Basing the PR against the correct MariaDB version
-- [ ] *This is a new feature or a refactoring, and the PR is based against the `main` branch.*
-- [ ] *This is a bug fix, and the PR is based against the earliest maintained branch in which the bug can be reproduced.*
-
-<!--
-  All code merged into the MariaDB codebase must meet a quality standard and coding style.
-  Maintainers are happy to point out inconsistencies but in order to speed up the review and merge process we ask you to check the CODING standards.
--->
-## PR quality check
-- [ ] I checked the [CODING_STANDARDS.md](https://github.com/MariaDB/server/blob/-/CODING_STANDARDS.md) file and my PR conforms to this where appropriate.
-- [ ] For any trivial modifications to the PR, I am ok with the reviewer making the changes themselves.