From bb10888357153084142d86c1eb1c7ffc19b726c6 Mon Sep 17 00:00:00 2001
From: Tobias Diez <code@tobiasdiez.de>
Date: Wed, 8 Feb 2023 18:41:30 +0800
Subject: [PATCH] Add best-practices for PR titles to PR template

---
 .github/PULL_REQUEST_TEMPLATE.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index b6763ce2883..0ba5857b820 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,6 +1,11 @@
+<!-- ^^^^^
+Please provide a concise, informative and self-explanatory title.
+Don't put issue numbers in there, do this in the PR body below.
+For example, instead of "Fixes #1234" use "Introduce new method to calculate 1+1"
+-->
 ### 📚 Description
 
-<!-- Describe your changes in detail -->
+<!-- Describe your changes here in detail -->
 <!-- Why is this change required? What problem does it solve? -->
 <!-- If it resolves an open issue, please link to the issue here. For example "Closes #1337" -->
 
@@ -10,6 +15,7 @@
 <!-- If your change requires a documentation PR, please link it appropriately -->
 <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
 
+- [ ] I have made sure that the title is self-explanatory and the description concisely explains the PR.
 - [ ] I have linked an issue or discussion.
 - [ ] I have created tests covering the changes.
 - [ ] I have updated the documentation accordingly.