From 22019f88e79778a2a8036b0d4d8ca66ff2bc1940 Mon Sep 17 00:00:00 2001
From: afc163 <afc163@gmail.com>
Date: Wed, 3 Jul 2024 17:24:03 +0800
Subject: [PATCH] chore: update pr-open-check content (#49701)

---
 .github/workflows/pr-open-check.yml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/.github/workflows/pr-open-check.yml b/.github/workflows/pr-open-check.yml
index 736dcb0979..35909a4ae2 100644
--- a/.github/workflows/pr-open-check.yml
+++ b/.github/workflows/pr-open-check.yml
@@ -39,14 +39,14 @@ jobs:
           require-include: '🇺🇸 English, 🇨🇳 Chinese, 🇺🇸 英文, 🇨🇳 中文'
           comment-body: |
             - 🚨 @${{ github.event.pull_request.user.login }}, Please fill changelog in the PR
-              - Write with a **developer-oriented perspective** and **narrative method**, without describing the details of the repair
-              - **Describing the problem and the impact on the developer**
-              - **describing the user-first site problem**, not your solution
-              - Refer: https://ant.design/changelog#501
+              - Use a developer-oriented tone and narrative style.
+              - Describe the user's first-hand experience of the issue and its impact on developers, rather than your solution approach.
+              - Refer to: ant.design/changelog#501
 
             - 🚨 @${{ github.event.pull_request.user.login }}, 请填写 PR 中的 changelog
-              - 请用**面向开发者的角度**和**叙述方式撰写**，不描述修复细节
-              - **描述问题和对开发者的影响**
-              - **描述用户第一现场的问题**，而非你的解决方式
+              - 请用面向开发者的角度和叙述方式撰写 changelog
+              - 描述用户第一现场的问题，对开发者有哪些影响，而非你的解决方式
               - 参考：https://ant.design/changelog-cn#501
+
+            ![](https://github.com/ant-design/ant-design/assets/507615/14c767db-e40f-42a1-9aab-553037eb1ab6)
           skip-title-start: 'docs, chore, test, ci'