[Misc] Add rules to label Speculative Decoding Related PRs

[draftbk]

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

Add rules to label Speculative Decoding Related PRs

Test Plan

Test Result

(Optional) Documentation Update

[github-actions]

👋 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.

🚀

[gemini-code-assist]

Summary of Changes

Hello @draftbk, 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 repository's Mergify configuration to improve the automatic labeling of pull requests related to speculative decoding. The changes ensure that a broader set of relevant files, including new v1 directories, examples, and specific model implementations, trigger the appropriate label, streamlining PR organization and review processes.

Highlights

• Automated Labeling: Expanded the conditions for automatically applying the 'Speculative Decoding' label to pull requests. This includes new paths for v1 specific speculative decoding components, related test files, example scripts, and model configurations for eagle, medusa, and mlp_speculator.

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

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 PR adds new rules to Mergify for automatically labeling pull requests related to speculative decoding. The new rules cover more files and directories. My review focuses on improving the precision and completeness of these new rules. I've suggested refining the regular expressions for better accuracy and adding rules for other speculative decoding models that appear to be missing, to ensure all relevant PRs are labeled correctly.

[gemini-code-assist]

This regex can be made more precise and comprehensive. Consider including ngram and mtp methods, using speculative instead of speculation for better specificity, and anchoring the regex with $ to match the end of the filename.

      - files~=^examples/.*(spec_decode|speculative|mlpspeculator|eagle|ngram|mtp).*.py$

[gemini-code-assist]

For consistency and to avoid matching partial filenames (e.g., .py.bak), it's good practice to anchor the regex to the end of the string with a $.

      - files~=^vllm/model_executor/models/.*eagle.*\.py$

[gemini-code-assist]

This regex should also be anchored to the end of the string with $ to prevent matching files with extra extensions. Additionally, to ensure comprehensive labeling for speculative decoding models, consider adding deepseek_vl2 to this regex, as it is the configuration for the deepseek_mtp model type.

      - files~=^vllm/transformers_utils/configs/(eagle|medusa|mlp_speculator|deepseek_vl2)\.py$