Skip to content

Conversation

@piggesthjy
Copy link
Collaborator

Description

Add a concise overview of what this PR aims to achieve. Reference related GitHub issues and PRs.

Fixes # (issue)

PR Title Format

Please format the PR title as {type}: {description}.

  • Types: feat, fix, refactor, chore, test, docs.
  • Example: feat: support new llm provider

Type of Change

  • 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, no api changes)

Testing

Please describe the tests that you ran to verify your changes. For UI changes or specific hardware integration, please provide screenshots or logs.

  • Unit Tests
  • Manual Verification
  • End-to-End Tests

API and Design Changes (Optional)

If this PR introduces API changes or complex design modifications, please describe them here.

# Example usage if applicable

Checklist

  • My code follows the style guidelines of this project.
  • I have run pre-commit run --all-files to ensure code quality.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • I have added tests that prove my fix is effective or that my feature works.

@piggesthjy piggesthjy requested a review from weilaaa December 17, 2025 23:01
Copy link
Collaborator

@weilaaa weilaaa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@weilaaa weilaaa merged commit 7a6f14d into volcengine:main Dec 19, 2025
4 checks passed
weilaaa pushed a commit that referenced this pull request Dec 23, 2025
#45)

> Add a concise overview of what this PR aims to achieve. Reference
related GitHub issues and PRs.

Fixes # (issue)

Please format the PR title as `{type}: {description}`.
- **Types**: `feat`, `fix`, `refactor`, `chore`, `test`, `docs`.
- **Example**: `feat: support new llm provider`

- [ ] 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, no api changes)

> Please describe the tests that you ran to verify your changes. For UI
changes or specific hardware integration, please provide screenshots or
logs.

- [ ] Unit Tests
- [ ] Manual Verification
- [ ] End-to-End Tests

> If this PR introduces API changes or complex design modifications,
please describe them here.

```python
```

- [ ] My code follows the style guidelines of this project.
- [ ] I have run `pre-commit run --all-files` to ensure code quality.
- [ ] I have performed a self-review of my own code.
- [ ] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added tests that prove my fix is effective or that my
feature works.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants