Skip to content

Conversation

@DarkLight1337
Copy link
Member

@DarkLight1337 DarkLight1337 commented Jun 11, 2025

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.md and examples for a new model.

Purpose

Regarding hardware support:

Regarding model support:

Other changes:

  • Reduce nesting of the headers
  • Split up models and features into separate sub-sections

Test Plan

N/A

Test Result

N/A

(Optional) Documentation Update

@DarkLight1337 DarkLight1337 requested a review from hmellor as a code owner June 11, 2025 06:48
@DarkLight1337 DarkLight1337 added the ready ONLY add when PR is ready to merge/full CI is needed label Jun 11, 2025
@gemini-code-assist
Copy link
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@github-actions
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

@DarkLight1337 DarkLight1337 changed the title Update v1 supports [Doc] Update V1 User Guide for Hardware and Models Jun 11, 2025
@mergify mergify bot added documentation Improvements or additions to documentation frontend multi-modality Related to multi-modality (#4194) v1 labels Jun 11, 2025
@DarkLight1337 DarkLight1337 removed frontend multi-modality Related to multi-modality (#4194) labels Jun 11, 2025
Signed-off-by: DarkLight1337 <[email protected]>
@Isotr0py Isotr0py enabled auto-merge (squash) June 11, 2025 07:10
Signed-off-by: DarkLight1337 <[email protected]>
@vllm-bot vllm-bot merged commit 68b4a26 into vllm-project:main Jun 11, 2025
10 of 33 checks passed
@DarkLight1337 DarkLight1337 deleted the update-v1-supports branch June 11, 2025 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation ready ONLY add when PR is ready to merge/full CI is needed v1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants