hsliuandClaude Opus 4.7
fb472ecfc7
- Fix NPU skill name in readme to match declared name - Fix base-branch detection to use explicit fallback - Fix title format reference to point to docs/contributing/README.md - Move /precheck-pr prompt to top of PR template Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Signed-off-by: hsliu <liuhongsheng4@huawei.com>
1.4 KiB
1.4 KiB
Before submitting: run /precheck-pr in Claude Code for a self-check against project conventions — catches dead code, missing benchmarks, and title format issues.
PLEASE FILL IN THE PR DESCRIPTION HERE ENSURING ALL CHECKLIST ITEMS (AT THE BOTTOM) HAVE BEEN CONSIDERED.
Purpose
Test Plan
Test Result
Essential Elements of an Effective PR Description Checklist
- The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
- The test plan. Please provide the test scripts & test commands. Please state the reasons if your codes don't require additional test scripts. For test file guidelines, please check the test style doc
- The test results. Please paste the results comparison before and after, or the e2e results.
- (Optional) The necessary documentation update, such as updating
supported_models.mdandexamplesfor a new model. Please runmkdocs serveto sync the documentation editions to./docs. - (Optional) Release notes update. If your change is user-facing, please update the release notes draft.
BEFORE SUBMITTING, please read https://github.com/vllm-project/vllm-omni/blob/main/CONTRIBUTING.md (anything written below this line will be removed by GitHub Actions)