From d8397a1c13b9e3cff030b02b9214df4e1a89c981 Mon Sep 17 00:00:00 2001
From: rick <rick@jenkins-zh.cn>
Date: Mon, 23 Nov 2020 11:29:12 +0800
Subject: [PATCH] Fix the potential issue caused by commented area mark

Signed-off-by: rick <rick@jenkins-zh.cn>
---
 .github/ISSUE_TEMPLATE/feature_request.md | 46 +++++++++++------------
 1 file changed, 23 insertions(+), 23 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index 43640fbff..568351145 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -41,29 +41,29 @@ In order to have a clear issue list, giving an accuracy area is necessary. If yo
 You can find some possible areas below. Please attention, sometimes crossing multiple areas might be possible. So, you 
 can keep one or more areas in this issue.
 
-/area alerting
-/area api
-/area apiserver
-/area app-management
-/area audit
-/area console
-/area devops
-/area documentation
-/area edge
-/area iam
-/area installation
-/area logging
-/area microservice
-/area monitoring
-/area multicluster
-/area networking
-/area notification
-/area observability
-/area performance
-/area security
-/area storage
-/area test
-/area upgrade
+> /area alerting
+> /area api
+> /area apiserver
+> /area app-management
+> /area audit
+> /area console
+> /area devops
+> /area documentation
+> /area edge
+> /area iam
+> /area installation
+> /area logging
+> /area microservice
+> /area monitoring
+> /area multicluster
+> /area networking
+> /area notification
+> /area observability
+> /area performance
+> /area security
+> /area storage
+> /area test
+> /area upgrade
 -->
 
 /kind feature-request