From ccce89961727f591b08289e4a56d1eab684bf926 Mon Sep 17 00:00:00 2001
From: "John Paul E. Balandan, CPA" <paulbalandan@gmail.com>
Date: Tue, 1 Nov 2022 14:17:09 +0800
Subject: [PATCH] Update PR template

---
 .github/PULL_REQUEST_TEMPLATE.md | 14 ++------------
 1 file changed, 2 insertions(+), 12 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 5caa82fddd4f..98aa948b795e 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -2,6 +2,8 @@
 
 Each pull request should address a single issue and have a meaningful title.
 
+- Pull requests must be in English.
+- If a pull request fixes an issue, reference the issue with a suitable keyword (e.g., Fixes <issue number>).
 - All bug fixes should be sent to the __"develop"__ branch, this is where the next bug fix version will be developed.
 - PRs with any enhancement should be sent to the next minor version branch, e.g. __"4.3"__
 
@@ -15,15 +17,3 @@ Explain what you have changed, and why.
 - [ ] Unit testing, with >80% coverage
 - [ ] User guide updated
 - [ ] Conforms to style guide
-
-<!--
-
-**Notes**
-- Pull requests must be in English
-- If the PR solves an issue, reference it with a suitable verb and the issue number
-(e.g. fixes <hash>12345)
-- Unsolicited pull requests will be considered, but there is no guarantee of acceptance
-- Pull requests should be from a feature branch in the contributor's fork of the repository
-  to the develop branch of the project repository
-
--->