-
-
Notifications
You must be signed in to change notification settings - Fork 10k
[Docs] Fix indentations for 2-level items in deprecation_policy.md #20352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @windsonsea, I'm Gemini Code Assist1! 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 focuses on improving the readability and consistency of the deprecation_policy.md
documentation by addressing minor formatting issues. It ensures that nested list items are properly indented and corrects a small typographical error in a section heading.
Highlights
- Documentation Formatting: Standardized indentation for nested list items within
deprecation_policy.md
from 2 spaces to 4 spaces to improve readability and adhere to common Markdown practices. - Typographical Correction: Corrected a minor formatting inconsistency in a section heading by adding a space after the number in "2. Deprecated (Off By Default)".
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize 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 is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
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. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request fixes indentation issues in the deprecation policy document, improving readability. The review suggests ensuring consistent indentation across all similar lists in the documentation and removing an unnecessary space for formatting consistency.
Signed-off-by: windsonsea <haifeng.yao@daocloud.io>
👋 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 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 🚀 |
…llm-project#20352) Signed-off-by: windsonsea <haifeng.yao@daocloud.io>
…llm-project#20352) Signed-off-by: windsonsea <haifeng.yao@daocloud.io>
…llm-project#20352) Signed-off-by: windsonsea <haifeng.yao@daocloud.io> Signed-off-by: avigny <47987522+avigny@users.noreply.github.com>
…llm-project#20352) Signed-off-by: windsonsea <haifeng.yao@daocloud.io>
…llm-project#20352) Signed-off-by: windsonsea <haifeng.yao@daocloud.io> Signed-off-by: Jinzhen Lin <linjinzhen@hotmail.com>
…llm-project#20352) Signed-off-by: windsonsea <haifeng.yao@daocloud.io>
Fix bullet indentations from 2-spaces to 4-spaces
current website page | Preview