[Doc][Misc] Add deployment reference notice for GLM-5

[wangzhishenghw]

What this PR does / why we need it?

This PR adds a notice and a reference link to Chapter 5 (Online Service Deployment) in the GLM-5 tutorial. This helps users find complete startup commands and parameter descriptions, and reminds them to configure max-model-len and max-num-seqs according to their actual usage scenarios.

Does this PR introduce any user-facing change?

No, this is a documentation-only update.

How was this patch tested?

Documentation changes only, verified markdown rendering.

• vLLM version: v0.26.0
• vLLM main: vllm-project/vllm@d02df74

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the GLM5 tutorial documentation to provide clearer guidance on deployment parameters and references to the relevant configuration chapter, improving the user experience for those setting up the model.

Highlights

• Documentation Update: Added a notice and reference link to the deployment section in the GLM5 tutorial documentation.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the GLM-5 tutorial documentation by adding a notice and reference link to Chapter 5 (Online Service Deployment) to guide users on configuring max-model-len and max-num-seqs. The reviewer noted that the PR title and description do not adhere to the repository's Pull Request Summary Style Guide and provided a compliant template to use.

[gemini-code-assist]

The current Pull Request title and description do not follow the repository's Pull Request Summary Style Guide. Please update them to match the required format.\n\nSuggested PR Title:\n\nmarkdown\n[Doc][Misc] Add deployment reference notice for GLM-5\n\n\nSuggested PR Summary:\n\nmarkdown\n### What this PR does / why we need it?\n\nThis PR adds a notice and a reference link to Chapter 5 (Online Service Deployment) in the GLM-5 tutorial. This helps users find complete startup commands and parameter descriptions, and reminds them to configure `max-model-len` and `max-num-seqs` according to their actual usage scenarios.\n\n### Does this PR introduce _any_ user-facing change?\n\nNo, this is a documentation-only update.\n\n### How was this patch tested?\n\nDocumentation changes only, verified markdown rendering.\n

References

1. The Pull Request title and summary must follow the specified format and be output in markdown code blocks. ^(link)

[github-actions]

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

• A PR should do only one thing, smaller PRs enable faster reviews.
• Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
• Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.

[wangzhishenghw]

/cherry-pick releases/v0.24.0rc
[Bot]: cherry-pick completed successfully. New PR created: #12961

[wangzhishenghw]

/cherry-pick releases/v0.23.0
[Bot]: cherry-pick completed successfully. New PR created: #12960

[wangzhishenghw]

/cherry-pick releases/v0.23.0
[Bot]: cherry-pick branch has been refreshed. Existing PR: #12960

[wangzhishenghw]

/cherry-pick releases/v0.24.0rc
[Bot]: cherry-pick branch has been refreshed. Existing PR: #12961

[wangzhishenghw]

/cherry-pick releases/v0.23.0
[Bot]: cherry-pick command failed. Please check the workflow run for details.

[wangzhishenghw]

/cherry-pick releases/v0.24.0rc
[Bot]: cherry-pick branch has been refreshed. Existing PR: #12961