@fitlab-ai/agent-infra 0.3.1 → 0.4.0

package/templates/.github/ISSUE_TEMPLATE/05_other.yml

@@ -1,147 +0,0 @@
-name: 🔧 其他问题 / Other Issues
-description: 报告不属于上述分类的其他问题或建议 / Report other issues or suggestions that don't fit the above categories
-labels:
-  - "status: waiting-for-triage"
-type: Task
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## 提交其他类型的问题 / Submit Other Types of Issues
-
-        如果您的问题不属于问题报告、问题咨询、功能请求或文档问题，请使用此模板。
-        If your issue doesn't belong to bug reports, questions, feature requests or documentation issues, please use this template.
-
-        **在提交前，请确认您的问题确实不属于以下类别：**
-        **Before submitting, please confirm your issue doesn't belong to the following categories:**
-        - 🐛 [问题报告 / Bug Report](./issues/new?template=01_bug_report.yml) - 项目功能错误
-        - ❓ [问题咨询 / Question](./issues/new?template=02_question.yml) - 使用相关问题
-        - ✨ [功能请求 / Feature Request](./issues/new?template=03_feature_request.yml) - 新功能建议
-        - 📚 [文档问题 / Documentation](./issues/new?template=04_documentation.yml) - 文档相关问题
-
-  - type: input
-    id: summary
-    attributes:
-      label: 问题摘要 / Issue Summary
-      description: 用一句话简要描述您的问题或建议 / Briefly describe your issue or suggestion in one sentence
-      placeholder: |
-        例如：建议添加 GitHub Actions CI/CD 工作流
-        Example: Suggest adding GitHub Actions CI/CD workflow
-    validations:
-      required: true
-
-  - type: dropdown
-    id: category
-    attributes:
-      label: 问题类别 / Issue Category
-      description: 请选择最接近的问题类别 / Please select the closest issue category
-      options:
-        - "项目管理 / Project Management"
-        - "开发工具 / Development Tools"
-        - "CI/CD相关 / CI/CD Related"
-        - "安全相关 / Security Related"
-        - "许可证问题 / License Issues"
-        - "社区建议 / Community Suggestions"
-        - "第三方集成 / Third-party Integration"
-        - "环境配置 / Environment Setup"
-        - "版本发布 / Release Management"
-        - "其他 (请在描述中说明) / Other (please specify in description)"
-    validations:
-      required: true
-
-  - type: dropdown
-    id: priority
-    attributes:
-      label: 优先级 / Priority
-      description: 您认为这个问题的重要程度如何？/ How important do you think this issue is?
-      options:
-        - "高 - 影响项目正常运行 / High - Affects normal project operation"
-        - "中 - 有一定影响 / Medium - Has some impact"
-        - "低 - 优化改进建议 / Low - Optimization/improvement suggestion"
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: 详细描述 / Detailed Description
-      description: |
-        详细描述您的问题、建议或需求
-        Describe your issue, suggestion, or requirement in detail
-      placeholder: |
-        请详细说明... / Please explain in detail...
-
-        包括但不限于 / Including but not limited to:
-        - 问题的背景和原因 / Background and reasons for the issue
-        - 具体的需求或建议 / Specific requirements or suggestions
-        - 对项目的影响 / Impact on the project
-        - 您认为的解决方案 / Your proposed solution
-    validations:
-      required: true
-
-  - type: textarea
-    id: context
-    attributes:
-      label: 相关背景 / Related Context
-      description: |
-        提供任何相关的背景信息
-        Provide any relevant background information
-      placeholder: |
-        相关信息... / Related information...
-
-        例如 / Example:
-        - 相关的外部工具或服务 / Related external tools or services
-        - 类似项目的实现方式 / Implementation approaches in similar projects
-        - 相关的讨论或文章链接 / Links to relevant discussions or articles
-
-  - type: textarea
-    id: impact
-    attributes:
-      label: 影响评估 / Impact Assessment
-      description: |
-        这个问题或建议会对项目产生什么影响？
-        What impact would this issue or suggestion have on the project?
-      placeholder: |
-        可能的影响... / Potential impacts...
-
-        例如 / Example:
-        - 对开发流程的影响 / Impact on development workflow
-        - 对用户体验的影响 / Impact on user experience
-        - 对项目维护的影响 / Impact on project maintenance
-
-  - type: textarea
-    id: additional-info
-    attributes:
-      label: 补充信息 / Additional Information
-      description: |
-        添加任何其他有用的信息，如截图、链接、参考资料等
-        Add any other useful information such as screenshots, links, references, etc.
-
-  - type: checkboxes
-    id: confirmations
-    attributes:
-      label: 确认事项 / Confirmations
-      description: |
-        提交前请确认以下事项
-        Please confirm the following before submitting
-      options:
-        - label: |
-            我已经确认这个问题不属于Bug报告、功能请求、问题咨询或文档问题
-            I have confirmed this issue doesn't belong to bug reports, feature requests, questions, or documentation issues
-          required: true
-        - label: |
-            我已经搜索了现有的issues，确认这不是重复问题
-            I have searched existing issues and confirmed this is not a duplicate
-          required: true
-        - label: |
-            我提供的信息清晰准确
-            The information I provided is clear and accurate
-          required: true
-        - label: |
-            我理解这类问题可能需要更多时间来评估和处理
-            I understand this type of issue may require more time to evaluate and process
-          required: true
-        - label: |
-            我愿意提供更多信息或协助解决 (可选)
-            I'm willing to provide more information or help resolve the issue (optional)
-          required: false

package/templates/.github/ISSUE_TEMPLATE/config.yml

@@ -1,11 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: 📖 项目文档 / Project Documentation
-    url: https://github.com/{{org}}/{{project}}/wiki
-    about: 查看项目文档和使用指南 / View project documentation and usage guides
-  - name: 💬 讨论区 / Discussions
-    url: https://github.com/{{org}}/{{project}}/discussions
-    about: 加入社区讨论，分享想法和经验 / Join community discussions, share ideas and experiences
-  - name: 🆘 获取帮助 / Get Help
-    url: https://github.com/{{org}}/{{project}}/discussions/categories/q-a
-    about: 在Q&A区域获取使用帮助 / Get usage help in the Q&A section

package/templates/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,123 +0,0 @@
-<!--
-如果您正在寻求帮助，请先在我们的讨论区中进行交流。
-If you're looking for help, please check our Discussions section first.
-
-我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。
-Please try to use English to describe your issue, or at least provide a snippet of English translation.
-
-请不要在没有创建 Issue 的情况下创建 Pull Request。
-Please do not create a Pull Request without creating an issue first.
-
-微小的变更（如错别字修复）不需要创建 Issue。
-Trivial changes like typos do not require a Github issue.
-
-提交 PR 之前请务必先阅读我们的贡献指南。
-Please read our Contributing Guide(CONTRIBUTING.md) before submitting your Pull Request.
-
-⚠️ 注意 / Note：
-
-不要重复创建类似的 PR，当你发现需要调整一个 PR 的时候，优先选择编辑修改它，而不是关闭之后再创建一个。
-Do not create a Pull Request without creating an issue first.
--->
-
-## 🔗 相关问题 / Related Issue
-
-<!-- 请先创建 Issue 讨论，然后在这里链接 -->
-<!-- Please create an issue for discussion first, then link it here -->
-
-**Issue 链接 / Issue Link:** <mark>#{$IssueNumber}</mark> 👈👈
-
-<!-- 请修改 {$IssueNumber} 为真实的编号。 -->
-<!-- Please update {$IssueNumber} to an actual number. -->
-
-- [ ] 我已经创建了相关 Issue 并进行了讨论 / I have created and discussed the related issue
-- [ ] 这是一个微小的修改（如错别字），不需要 Issue / This is a trivial change (like typo fix) that doesn't need an issue
-
-## 📋 变更类型 / Type of Change
-
-- [ ] 🐛 Bug 修复 / Bug fix (non-breaking change which fixes an issue)
-- [ ] ✨ 新功能 / New feature (non-breaking change which adds functionality)
-- [ ] 💥 破坏性变更 / Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] 📚 文档更新 / Documentation update
-- [ ] 🔧 重构 / Refactoring (no functional changes)
-- [ ] ⚡ 性能优化 / Performance improvement
-- [ ] 📦 依赖升级 / Dependency upgrade (update dependencies to newer versions)
-- [ ] 🚀 功能增强 / Feature enhancement (improve existing functionality without breaking changes)
-- [ ] 🧹 代码清理 / Code cleanup
-
-## 📝 变更目的 / Purpose of the Change
-
-<!-- 详细描述这个变更的目的和必要性 -->
-<!-- Detailed description of the purpose and necessity of this change -->
-
-## 📋 主要变更 / Brief Changelog
-
-<!-- 列出主要的变更内容 -->
-<!-- List the main changes -->
-
--
--
--
-
-## 🧪 验证变更 / Verifying this Change
-
-<!-- 描述如何验证这个变更是正确的 -->
-<!-- Describe how to verify that this change is correct -->
-
-### 测试步骤 / Test Steps
-
-1.
-2.
-3.
-
-### 测试覆盖 / Test Coverage
-
-- [ ] 我已经添加了单元测试 / I have added unit tests
-- [ ] 所有现有测试都通过 / All existing tests pass
-- [ ] 我已经进行了手动测试 / I have performed manual testing
-
-## 📸 截图 / Screenshots
-
-<!-- 如果适用，请添加截图来展示变更效果 -->
-<!-- If applicable, add screenshots to demonstrate the changes -->
-
-## ✅ 贡献者检查清单 / Contributor Checklist
-
-请确保你的 Pull Request 符合以下要求 / Please ensure your Pull Request meets the following requirements:
-
-**基本要求 / Basic Requirements:**
-
-- [ ] 确保有 GitHub Issue 对应这个变更（微小变更如错别字除外）/ Make sure there is a Github issue filed for the change (trivial changes like typos excluded)
-- [ ] 你的 Pull Request 只解决一个 Issue，没有包含其他不相关的变更 / Your PR addresses just this issue, without pulling in other changes - one PR resolves one issue
-- [ ] PR 中的每个 commit 都有有意义的主题行和描述 / Each commit in the PR has a meaningful subject line and body
-
-**代码质量 / Code Quality:**
-
-- [ ] 我的代码遵循项目的代码规范 / My code follows the project's coding standards
-- [ ] 我已经进行了自我代码审查 / I have performed a self-review of my code
-- [ ] 我已经为复杂的代码添加了必要的注释 / I have commented my code, particularly in hard-to-understand areas
-
-**测试要求 / Testing Requirements:**
-
-- [ ] 我已经编写了必要的单元测试来验证逻辑正确性 / I have written necessary unit-tests to verify the logic correction
-- [ ] 当存在跨模块依赖时，我尽量使用了 mock / I have used mocks when cross-module dependencies exist
-- [ ] 代码检查通过 / Lint checks pass
-- [ ] 单元测试通过 / Unit tests pass
-
-**文档和兼容性 / Documentation and Compatibility:**
-
-- [ ] 我已经更新了相应的文档 / I have made corresponding changes to the documentation
-- [ ] 如果有破坏性变更，我已经在 PR 描述中详细说明 / If there are breaking changes, I have documented them in detail
-- [ ] 我已经考虑了向后兼容性 / I have considered backward compatibility
-
-## 📋 附加信息 / Additional Notes
-
-<!-- 任何其他相关信息，如已知问题、后续计划等 -->
-<!-- Any other relevant information, such as known issues, future plans, etc. -->
-
----
-
-**审查者注意事项 / Reviewer Notes:**
-
-<!-- 为审查者提供的特殊说明或需要重点关注的地方 -->
-<!-- Special instructions for reviewers or areas that need special attention -->

package/templates/.github/dependabot.yml

@@ -1,17 +0,0 @@
-version: 2
-updates:
-  # TODO: add your project's package ecosystem (npm, pip, maven, gradle, etc.)
-  # - package-ecosystem: "npm"
-  #   directory: "/"
-  #   schedule:
-  #     interval: "weekly"
-  #   labels:
-  #     - "dependencies"
-  #   open-pull-requests-limit: 10
-
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-    labels:
-      - "dependencies"

package/templates/.github/hooks/check-utf8-encoding.sh

@@ -1,25 +0,0 @@
-#!/bin/sh
-set -e
-
-echo "UTF-8 check script is running..."
-
-# Iterate over every file that is in the staging area
-for FILE in $(git diff --cached --name-only); do
-    # If file exists
-    # shellcheck disable=SC2039
-    if [[ -e "$FILE" ]]; then
-        if [[ $(file -bi "$FILE") != *"charset=binary"* ]]; then
-            # Get file encoding
-            encoding=$(file -bi "$FILE" | sed -e 's/.*[ ]charset=//')
-            echo "Checking file $FILE (encoding: $encoding)"
-
-            # If encoding is not utf-8 or us-ascii, exit with failure status
-            if ! echo "$encoding" | grep -q -e 'utf-8' -e 'us-ascii'; then
-                echo "Error: File $FILE is not UTF-8 encoded or US-ASCII, it is $encoding. Please convert it to UTF-8."
-                exit 1
-            fi
-        fi
-    fi
-done
-
-echo "UTF-8 check completed successfully."

package/templates/.github/release.yml

@@ -1,27 +0,0 @@
-changelog:
-  exclude:
-    labels:
-      - skip-changelog
-    authors:
-      - dependabot
-  categories:
-    - title: "⚠️ Breaking Changes"
-      labels:
-        - breaking
-    - title: "✨ Enhancement"
-      labels:
-        - enhancement
-        - feature
-    - title: "🐛 Bug Fixes"
-      labels:
-        - bug
-        - fix
-    - title: "📚 Documentation"
-      labels:
-        - documentation
-    - title: "📦 Dependencies"
-      labels:
-        - dependencies
-    - title: "Other Changes"
-      labels:
-        - "*"

package/templates/.github/workflows/pr-title-check.yml

@@ -1,42 +0,0 @@
-name: PR Title Check
-
-on:
-  pull_request_target:
-    types: [opened, edited, synchronize]
-
-permissions:
-  pull-requests: write
-  statuses: write
-
-jobs:
-  validate:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: amannn/action-semantic-pull-request@v6.1.1
-        with:
-          # 允许的提交类型
-          types: |
-            feat
-            fix
-            docs
-            style
-            refactor
-            perf
-            test
-            chore
-            build
-            ci
-            revert
-
-          # 不限制 scope，允许任意模块名
-          # requireScope: false - scope 是可选的
-
-          # 标题描述长度 5-100 字符
-          subjectPattern: '^.{5,100}$'
-          subjectPatternError: '标题描述长度应在 5-100 字符之间'
-
-          # 支持 WIP 前缀标记进行中的工作
-          wip: true
-
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

package/templates/.mailmap

@@ -1,4 +0,0 @@
-Claude <noreply@anthropic.com>
-Codex <noreply@openai.com>
-Gemini <noreply@google.com>
-OpenCode <noreply@opencode.ai>

package/templates/CONTRIBUTING.md

@@ -1,126 +0,0 @@
-# Developer Guide
-
-## Introduction
-
-This guide provides detailed development guidance for contributors, including branch management, tagging, commit rules, and code review.
-
-## Development Model
-
-We use [Git](https://git-scm.com/) for version control, following a multi-version Git-Flow model:
-
-- `main` branch is the primary development branch; all features branch from and merge into it
-- `{{project}}-feature-*` branches for feature development
-- `{{project}}-{majorVersion}.{minorVersion}.x` for version branches
-- `{{project}}-bugfix-*` branches for bug fixes
-- All bug fixes or enhancements must start from the lowest applicable version branch and merge upward to `main`
-
-## Environment Setup
-
-### Prerequisites
-
-<!-- TODO: Add your project's prerequisites here -->
-
-### Quick Start
-
-```bash
-# Clone the project
-git clone <repository-url>
-
-# Install dependencies
-# TODO: Add your project's install command
-
-# Build
-# TODO: Add your project's build command
-
-# Run tests
-# TODO: Add your project's test command
-
-# Lint
-# TODO: Add your project's lint command
-```
-
-See the project's `README.md` for more details on configuring the development environment.
-
-## Branch Management
-
-- Create a new branch for each feature or bug fix; never develop directly on `main`.
-- Branch naming should be concise and describe the branch's purpose.
-  - Branches start with `{{project}}-`.
-  - Feature branches: `{{project}}-feature-*`, enhancements: `{{project}}-enhancement-*`, tasks: `{{project}}-task-*`, bug fixes: `{{project}}-bugfix-*`.
-  - Use hyphens `-` to separate words.
-  - Version branches end with two version numbers and `x`: `{{project}}-1.0.x`.
-  - Release branches end with three version numbers: `{{project}}-1.0.0`.
-
-### Version Branch Merge Rules
-
-- Version branches must merge from lower to higher versions, without skipping.
-- After any feature, enhancement, or bugfix merges into a version branch, it must be merged upward through each subsequent version branch until reaching `main`.
-
-## Tag Management
-
-- Tag names must match release branch names, e.g. `{{project}}-1.0.0`.
-- Purely numeric versions use a `v` prefix, e.g. `v0.1.0`.
-- Release candidates use special suffixes, e.g. `{{project}}-1.0.0-alpha1`.
-- After a tag is created, the corresponding release branch should be deleted.
-- All Issues and PRs must have at least two labels: `in: {module}` and `type: {type}`.
-
-## Development Standards
-
-### Code Style
-
-<!-- TODO: Add your project's code style requirements here -->
-
-### Comments
-
-- Each module file should include comments explaining its purpose.
-- All exported classes, functions, and interfaces need documentation comments.
-
-## Commit Rules
-
-### Commit Message Format
-
-We follow [Conventional Commits](https://www.conventionalcommits.org/):
-`<type>(<scope>): <subject>`
-
-- **type**: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`
-- **scope**: Module name. Use `*` or leave empty for cross-module changes.
-- **subject**: Brief description in English imperative mood, max 50 characters, no trailing period.
-
-Add a blank line after the subject for detailed description if necessary.
-
-**Examples:**
-- `feat(ai): add multi-agent collaboration workflow`
-- `fix(github): fix PR title validation regex`
-- `docs(ai): update collaboration quick start guide`
-
-## Code Review
-
-- Create a pull request to merge changes into the main branch. Describe your changes and invite team members for review.
-- Keep the main branch always deployable; ensure merged code is tested and follows coding standards.
-
-## Testing
-
-<!-- TODO: Add your project's testing requirements here -->
-
-## Release Process
-
-Follow the project's release plan. When releasing a new version, create a tag per the tag management rules.
-
-## Issue and Requirement Tracking
-
-Use the project's Issue tracker to report and track issues, requirements, and feature suggestions. Provide detailed information when creating new Issues.
-
-## Contribution Guide
-
-For contributors:
-
-1. Fork the project.
-2. Clone your fork locally.
-3. Create a new branch for development.
-4. Follow the commit conventions in this document.
-5. Create a PR to merge into the corresponding branch (one commit per PR).
-6. Participate in code review and make necessary changes.
-7. Once accepted and merged, your contribution becomes part of the project.
-
-> - Maintainers may suggest modifications. Stay open and communicate actively.
-> - If you find an issue but don't plan to fix it, submit an Issue. For questions, use the Discussions section.

package/templates/CONTRIBUTING.zh-CN.md

@@ -1,124 +0,0 @@
-# 开发者指导手册
-
-## 简介
-
-本指导手册旨在为项目的开发者提供一份详细的开发指导，包括分支管理、标签管理、提交规则、代码审查等内容。遵循这些指导有助于项目的高效开发和良好协作。
-
-## 开发模式
-
-我们使用 [Git](https://git-scm.com/) 作为版本控制工具，项目开发模式遵从多版本的 `Git-Flow` 模式：
-
-- `main` 分支为主干开发分支，所有特性都从该分支检出并合入
-- `{{project}}-feature-*` 分支为特性开发分支
-- `{{project}}-{$majorVersion}.{$minorVersion}.x` 为指定版本分支
-- `{{project}}-bugfix-*` 分支为问题修复分支
-- 所有问题修复或者功能增强，均需要找到合适的最低版本分支进行处理，然后逐级分支往上合入，最终合入 `main` 分支
-
-## 环境配置
-
-### 前置条件
-
-<!-- TODO: 在此添加你的项目前置条件 -->
-
-### 快速开始
-
-```bash
-# 克隆项目
-git clone <repository-url>
-
-# 安装依赖
-# TODO: 添加你的项目安装命令
-
-# 构建
-# TODO: 添加你的项目构建命令
-
-# 运行测试
-# TODO: 添加你的项目测试命令
-
-# 代码检查
-# TODO: 添加你的项目检查命令
-```
-
-请参考项目的 `README.md` 文件以获取更多关于如何配置开发环境的指导。
-
-## 分支管理
-
-- 为每个功能或问题修复创建一个新的分支，避免在主分支（如 `main`）上直接开发。
-- 分支命名应简洁明了，描述分支的主要目的。
-  - 分支以 `{{project}}-` 开头。
-  - 特性分支以 `{{project}}-feature-` 开头，功能增强分支以 `{{project}}-enhancement-` 开头，任务型分支以 `{{project}}-task-` 开头，问题修复分支以 `{{project}}-bugfix-` 开头。
-  - 使用短划线 `-` 来分隔单词。
-  - 版本分支最后跟两个版本号和一个 `x` 字母，例如：`{{project}}-1.0.x`。
-  - 发布分支后面跟三个版本号，例如：`{{project}}-1.0.0`。
-
-### 版本分支合并规则
-
-- 版本分支合并必须遵循低版本向高版本合并的原则，且不可跨越某一个版本。
-- 当任意 `feature`、`enhancement` 或 `bugfix` 合入指定版本分支之后，需要依次向上合并直到 `main` 分支为止。
-
-## 标签管理
-
-- 每个标签的名字和发布分支的名字需要保持一致，例如：`{{project}}-1.0.0`。
-- 纯数字版本的分支需要以 `v` 开头，例如：`v0.1.0`。
-- 候选版本以特殊词组结尾，例如：`{{project}}-1.0.0-alpha1`。
-- 当标签被打出后，对应的发布分支应当删除。
-- 所有的 Issue 和 PR 都需要至少包含两种标签：`in: {$module}` 和 `type: {$type}`。
-
-## 开发规范
-
-### 代码风格
-
-<!-- TODO: 在此添加你的项目代码风格要求 -->
-
-### 注释信息
-
-- 每一个模块文件都建议包含注释，说明其职责和用途。
-- 所有被 `export` 的类、函数、接口等都需要添加文档注释。
-
-## 提交规则
-
-### 提交信息格式
-
-我们采用 [Conventional Commits](https://www.conventionalcommits.org/) 规范：
-`<type>(<scope>): <subject>`
-
-- **type（类型）**：`feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`
-- **scope（范围/模块）**：对应项目模块名。如果涉及多个模块或全局变动，可以使用 `*` 或留空。
-- **subject（描述）**：简短描述主要内容，使用英文祈使语气，不超过 50 字符，结尾不需要句号。
-
-**样例：**
-- `feat(ai): add multi-agent collaboration workflow`
-- `fix(github): fix PR title validation regex`
-- `docs(ai): update collaboration quick start guide`
-
-## 代码审查
-
-- 开发完成后，通过创建合并请求将变更合并到主分支。在合并请求中描述所做的更改，并邀请其他项目成员进行代码审查。
-- 保持主分支始终可部署，确保合并的代码经过充分测试。
-
-## 测试
-
-<!-- TODO: 在此添加你的项目测试要求 -->
-
-## 发布流程
-
-遵循项目的发布计划和流程。在发布新版本时，请按照标签管理的规定创建一个新的 `tag`。
-
-## 问题和需求跟踪
-
-使用项目的 `Issue` 跟踪器来报告和跟踪问题、需求和功能建议。在创建新 `Issue` 时，请尽量提供详细的信息。
-
-## 贡献指南
-
-对于希望参与项目的贡献者，请遵循以下步骤：
-
-1. Fork 当前项目。
-2. 克隆 Fork 后的仓库到本地。
-3. 在本地仓库中创建一个新的分支，进行开发。
-4. 遵循本文档中的提交规范，将更改提交到新分支。
-5. 通过页面创建一个 PR，请求将更改合并到该项目的对应分支，PR 中仅能包含一次提交。
-6. 参与代码审查和讨论，根据反馈进行必要的修改。
-7. 一旦更改被接受并合并，您的贡献将成为项目的一部分。
-
-> - 项目维护者可能会提出修改建议，请保持开放态度并积极沟通。
-> - 如果您发现了一个问题但并不准备自己修复，可以仅提交一个 Issue。如果对方案存在疑问，可以在"讨论"模块中提问。