Skip to content

Conversation

@wzshiming
Copy link
Contributor

@wzshiming wzshiming commented Nov 28, 2025

https://github.com/wzshiming/vllm/actions/workflows/stale.yml

This isn't really useful for forked repositories. Perhaps we could add a check for that.

Purpose

Test Plan

Test Result


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.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.
@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

…ository Signed-off-by: Shiming Zhang <wzshiming@hotmail.com>
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a repository check to the stale issue/PR workflow to prevent it from running on forked repositories, which is a sensible optimization since the workflow is only needed on the main vllm-project/vllm repository.

Key Changes

  • Added a conditional check to the close-issues-and-pull-requests job to only run when the repository is vllm-project/vllm

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Member

@russellb russellb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@russellb russellb enabled auto-merge (squash) December 1, 2025 21:19
@github-actions github-actions bot added the ready ONLY add when PR is ready to merge/full CI is needed label Dec 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci/build ready ONLY add when PR is ready to merge/full CI is needed

2 participants