From 17622fdc6ce2f79d77e3a2eba456557513fd8743 Mon Sep 17 00:00:00 2001
From: Jefffrey <jeffrey.vo.australia@gmail.com>
Date: Mon, 15 Dec 2025 12:41:35 +0900
Subject: [PATCH] minor: Add comment blocks to PR template

---
 .github/pull_request_template.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 49b34c6137f7..c2d07f49ab88 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,28 +1,38 @@
 # Which issue does this PR close?
 
+<!--
 We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax.
+-->
 
 - Closes #NNN.
 
 # Rationale for this change
 
+<!--
 Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed.
 Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes.
+-->
 
 # What changes are included in this PR?
 
+<!--
 There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR.
+-->
 
 # Are these changes tested?
 
+<!--
 We typically require tests for all PRs in order to:
 1. Prevent the code from being accidentally broken by subsequent changes
 2. Serve as another way to document the expected behavior of the code
 
 If tests are not included in your PR, please explain why (for example, are they covered by existing tests)?
+-->
 
 # Are there any user-facing changes?
 
+<!--
 If there are user-facing changes then we may require documentation to be updated before approving the PR.
 
 If there are any breaking changes to public APIs, please call them out.
+-->