upa

.github/ba.txt

@@ -0,0 +1 @@
+全是中文

.github/pull_request_template.md

@@ -1,3 +1,40 @@
-如果我这么写
+<!--
+🎉 Thanks for sending a pull request to Kratos! Here are some tips for you:
 
-阁下又该如何应对
+1. If this is your first time contributing to Kratos, please read our contribution guide: https://go-kratos.dev/en/docs/community/contribution/
+2. Ensure you have added or ran the appropriate tests and lint for your PR, please use `make lint` and `make test` before filing your PR, use `make clean` to tidy your go mod.
+3. If the PR is unfinished, you may need to mark it as a WIP(Work In Progress) PR or Draft PR
+4. Please use a semantic commits format title, such as `<type>[optional scope]: <description>`, see: https://go-kratos.dev/docs/community/contribution#type
+5. at the same time, please note that similar work should be submitted in one PR as far as possible to reduce the workload of reviewers. Do not split a work into multiple PR unless it should.
+-->
+
+<!--
+🎉 感谢您向 Kratos 发送 PR！以下是一些提示：
+如果这是你第一次为 Kratos 贡献，请阅读我们的贡献指南：https://go-kratos.dev/en/docs/community/contribution/
+2、确保您已经为您的 PR 添加或运行了适当的测试和lint，请在提交PR之前使用“make lint”和“make test”，使用“make clean”整理您的 go.mod。
+3、如果 PR 未完成，您可能需要将其标记为 WIP（Work In Progress）PR 或 Draft PR
+4、请使用语义提交格式标题，如“<类型>[可选范围]：<说明>`，请参阅：https://go-kratos.dev/docs/community/contribution#type
+5. 同时请注意，同类的工作请尽量在一个PR中提交，以减轻 review 者的工作负担，不要把一项工作拆分成很多个PR，除非它应该这样做。
+-->
+
+
+#### Description (what this PR does / why we need it):
+<!--
+* The description should include the motivation for this PR or contrast this with previous behavior
+-->
+
+
+#### Which issue(s) this PR fixes (resolves / be part of):
+<!--
+* Automatically closes linked issue when PR is merged.
+* If your PR is not fully resolved the issue, please use `part of #<issue number>` instead.
+
+Usage: `fixes/resolves #<issue number>`, or `fixes/resolves (paste link of issue)`.
+-->
+
+
+#### Other special notes for the reviewers:
+<!--
+* Somethings that need extra attention for the reviewers
+* Some additional notes, TODO list, etc.
+-->

.github/workflows/a.yml

@@ -0,0 +1 @@
+# 中秋快乐

.github/workflows/cn.txt

@@ -0,0 +1 @@
+中文

.github/workflows/comment-check.yml

@@ -79,7 +79,6 @@ jobs:
 
       #     # Get the list of files changed in this PR compared to the base branch
       #     changed_files=$(git diff --name-only ${{ github.event.pull_request.base.sha }} ${{ github.event.pull_request.head.sha }})
-
 
       #     # Loop over each changed file
       #     for file in $changed_files; do
@@ -113,7 +112,6 @@ jobs:
       #         echo "$formatted_output" >> non_english_comments.txt  # Save to file
       #       fi
       #     done
-
 
       - name: Store non-English comments in ENV
         run: |
@@ -158,12 +156,12 @@ jobs:
             ```
             ${{ env.NON_ENGLISH_COMMENTS }}
             ```
-            
-            
+
+
 ## true test 爱来自瓷器
   ### 这就是中文的含金量
 
 # 现在测试的只有diff , no include entire repo
 
 
-# 再加一点改动后的情况 bot 会是edited
+# 再加一点改动后的情况 bot 会是edited

.github/workflows/pull_request_template.md

@@ -1,3 +1,14 @@
 如果我这么写
 
-阁下又该如何应对
+阁下又该如何应对
+
+
+<!--
+🎉 感谢您向 Kratos 发送 PR！以下是一些提示：
+如果这是你第一次为 Kratos 贡献，请阅读我们的贡献指南：https://go-kratos.dev/en/docs/community/contribution/
+2、确保您已经为您的 PR 添加或运行了适当的测试和lint，请在提交PR之前使用“make lint”和“make test”，使用“make clean”整理您的 go.mod。
+3、如果 PR 未完成，您可能需要将其标记为 WIP（Work In Progress）PR 或 Draft PR
+4、请使用语义提交格式标题，如“<类型>[可选范围]：<说明>`，请参阅：https://go-kratos.dev/docs/community/contribution#type
+5. 同时请注意，同类的工作请尽量在一个PR中提交，以减轻 review 者的工作负担，不要把一项工作拆分成很多个PR，除非它应该这样做。
+-->
+

.github/workflows/t.mdx

@@ -1 +1,4 @@
 你好
+
+
+auok