ci: 更新git action某些文件

[teacher-zhou]

• 新增git-version.yml
• 新增 pr-conflict.yml

本次提交包含什么范围

• [fix]修复（对缺陷的修复）
• [feat]功能（新功能、特性的开发）
• [docs]文档（仅对当前版本的文档进行增加、完善和更新）
• [pref]性能（改进性能的代码更改）
• [refactor]重构（既不修复bug也不添加特性的代码更改）
• [style]风格（不影响代码含义的更改(空白、格式化、缺少分号等)
• [test]测试（添加缺失的测试或修改现有的测试）
• [build]编译（影响构建系统或外部依赖的更改）
• [ci]集成（对CI配置文件和脚本的更改）
• [others]其他，请说明：

参考 https://www.conventionalcommits.org/zh-hans/v1.0.0/

关联的 ISSUE 编号（一行一个）

[github-actions]

Unit Test Results

🟢  Tests Passed      |      ⏱️ 3.1s

📝 Total	✔️ Passed	❌ Failed	⚠️ Skipped
93	93	0	0

✏️ updated for commit 06fac6c

[github-actions]

查看测试结果 https://github.com/AchievedOwner/TDesignBlazor/runs/9932288199

[github-actions]

Expected release notes (by @AchievedOwner)

fixes:
环境变量确实 $ 符号 (2823a5c)
环境变量错误的输出格式 (9c0ac65)

others (will not be included in Semantic-Release notes):
测试环境变量 (da1cd4b)
在 pull-request.yml 中使用环境变量 (5157f2e)
更新git action某些文件 (74f43c5)
更新了贡献指南和 pr 模板 (#193) (07cc897)
增加 other 英文在其他处 (7a76f60)
新增 release-note 预览的脚本 (efd5dd5)
删除 pull-request.yml 的环境变量 (129a894)
更新了贡献指南和 pr 模板 (4db40af)
bade2a5 fixBug readme.md (#192)
5e7aea9 Update readme.md
4640f1b 修复 源码地址错误 (#187)
92d9cb5 修复 源码地址错误
78041ab 修复 git page 的快速上手 404 (#182)
097862c 修复 git page 的快速上手 404
5f75b7b Update release.yml (#178)
def8baf 更新 git page 路径错误 (#179)
4510661 Update pull-request.yml
5c6380e Update pull-request.yml
5af2eb7 更新 git page 路径错误
70f0be1 Update pull-request.yml
b061095 Update release.yml
47c9b34 【更新】文档不正确的文本 (#176)
e5aaeea [fixed]页面标题多出一个 T 字母 [update]页面的 title 标题
edd7264 [update]WebAssembly index.html [update]logo image [update]readme.md
2897cd2 add logo
56f56ed 【新增】Affix 固钉组件 (#175)
3f46446 [style] 删除了多余的变量和代码
97d45c4 [style] rename 成员变量 affixId 改为 _affixId
ab6d579 [perf] js export 所有的导出对象应该写到一个export下
25a2828 [feature] 完成Affix组件的AffixedChange事件，并补全文档
3d74e3c [fix] bug OffsetTop 功能滚动bug
d91bf00 [feature] 实现了固钉组件的OffsetTop功能
cfdedb8 【新增】Popup 组件 (#173)
32870fb [doc]增加自定义内容
7177440 [feat]write a test case
b390393 [doc]更新 Popup 文档
798e650 [update] 将所有的基类改为 TDesignBlazorComponentBase
e5b9fd5 [bugfix]Popup 组件搞定
3328de1 [feat]Popup 组件，方案不够满意，需要继续设计
b855c96 [fix] bug 构建style应该重写BuildStyle方法
e235594 [conflict] 合并 master 并解决冲突
3912901 [新增] Timeline 组件 (#172)
f921b33 [feat] Timeline 组件
e7f08e5 [fix] bug 修复合并最新master产生的报错
86e4ba6 [style] 修改了js文件affix.init方法的注释
4fa9efd 【更新】tdesign.css 到 0.5 (#165)
95502b3 [bugfix]the release.yml support .NET 7
eedebc1 [bugifx] github action yml support .NET 7
54b251f [bugfix]Update test project to support .NET 7
a3417d0 [feature] 实现了top和bottom 固定的基础代码
4e0255d [update]change github action support 7.0
9b22fba [feat]update css to 0.5
fe83e44 [feat]update readme
2d7e913 [feat] update ComponentBuilder to 2.0 [feat]support .NET 7
e6889b2 [feat] 更新版本 (#163)
c3c8044 [feat] update the version
cd5636c [feat]GridTest
fde563e [faeture] 新增TAffix组件的部分代码（未完成）
bb7e4c3 暂时不用 ts
66a8b74 终于完成了 TPopup 的显示功能，但是位置显示不正确
7be7d6d 显示出来了，但是无法销毁
1db6b92 AddElementReferenceCapture 会报错很奇怪
f3170a9 【新增】Popup 组件
6799454 【新增】Popup 组件 但是位置不太准确

• I hereby acknowledge these release notes are 🥙 AWESOME 🥙

[github-actions]

查看测试结果 https://github.com/AchievedOwner/TDesignBlazor/runs/9933167739

[pull-request-quantifier-deprecated]

This PR has 55 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Small
Size       : +33 -22
Percentile : 22%

Total files changed: 4

Change summary by file extension:
.yml : +31 -22
.gitignore : +2 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[github-actions]

查看测试结果 https://github.com/AchievedOwner/TDesignBlazor/runs/9933296721