From 4336083e8b0c72e51d1d380ce66694ddf9dff7d0 Mon Sep 17 00:00:00 2001
From: Jirka Borovec <6035284+Borda@users.noreply.github.com>
Date: Wed, 25 Sep 2024 17:19:02 +0200
Subject: [PATCH] update PR template with hiding instructions (#297)

---
 .github/PULL_REQUEST_TEMPLATE.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 02bc9c35..aee45691 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -8,19 +8,19 @@
 
 </details>
 
-## ⚠️ How does this PR impact the user? ⚠️
+<!--
+⚠️ How does this PR impact the user? ⚠️
 Describe (in plain English, not technical Jargon) how this improves the user experience. If you can't tie it back to a real tangible, user goal or describe it in plain english, it's a hint that this is likely not needed and is probably an "engineering nit". 
 
-### GOOD:
+✅ GOOD:
 "As a user, I need to serve models faster. This PR focuses on enabling speed gains by using GPUs"
 
-### BAD:
+⛔️ BAD:
 "This PR enables GPUs". 
 This is bad because the *user problem* is not clear... instead it just jumps to the solution without any context. 
 
 PRs without this will not be merged.
-
----- 
+-->
 
 
 ## What does this PR do?