hsliu
4422acb185
- Add PULL_REQUEST_TEMPLATE.md with vLLM-style PR template - Add comprehensive issue templates: - Bug report template (400-bug-report.yml) - Feature request template (500-feature-request.yml) - New model support template (600-new-model.yml) - Documentation template (100-documentation.yml) - Installation template (200-installation.yml) - Performance discussion template (700-performance-discussion.yml) - Issue template configuration (config.yml) - Templates adapted for vLLM-omni with multimodal context - Force added YAML files to override .gitignore exclusion
943 B
943 B
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, such as providing test command.
- The test results, such as pasting the results comparison before and after, or e2e results
- (Optional) The necessary documentation update, such as updating
supported_models.mdandexamplesfor a new model. - (Optional) Release notes update. If your change is user facing, please update the release notes draft.
BEFORE SUBMITTING, PLEASE READ https://github.com/hsliuustc0106/vllm-omni/blob/main/CONTRIBUTING.md (anything written below this line will be removed by GitHub Actions)