Rule: label-documentation (label)

• any of:
  • files~=^[^/]+\.md$
  • files~=^docs/

Rule: label-ci-build (label)

• any of:
  • files=CMakeLists.txt
  • files=setup.py
  • files~=\.buildkite/
  • files~=^Dockerfile
  • files~=^\.github/
  • files~=^cmake/
  • files~=^requirements.*\.txt

Rule: label-frontend (label)

• files~=^vllm/entrypoints/

Rule: label-structured-output (label)

• any of:
  • files=benchmarks/benchmark_guided.py
  • files=benchmarks/benchmark_serving_guided.py
  • files=tests/entrypoints/llm/test_guided_generate.py
  • files=tests/model_executor/test_guided_processors.py
  • files~=^vllm/model_executor/guided_decoding/

Rule: label-speculative-decoding (label)

• any of:
  • files=vllm/model_executor/layers/spec_decode_base_sampler.py
  • files~=^tests/spec_decode/
  • files~=^vllm/spec_decode/

Rule: label-v1 (label)

• any of:
  • files~=^tests/v1/
  • files~=^vllm/v1/

Rule: ping author on conflicts and add 'needs-rebase' label (comment, label)

• conflict
• -closed

✅ Rule: remove 'needs-rebase' label when conflict is resolved (label)

• -closed
• -conflict

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com