-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
[CI/Build] Always run the ruff workflow #10092
Conversation
A prior PR, vllm-project#9928, modified this workflow to only run when relevant files have changed. However, github is configured to expect and require this workflow to run and pass before a PR can be auto-merged. GitHub configuration is not quite flexible enough to say "require this workflow to pass before merging, but only if we plan to run it." This change is the simplest: just run it always. The change also leaves a comment in the workflow explaining why it is this way. An alternative in the future could be to switch to a different framework for doing auto-merges. Mergify, which is already in use for some things, has flexible enough policy configuration to capture more complex merge criteria. Swithing to it just because of this is not necessary. Signed-off-by: Russell Bryant <[email protected]>
👋 Hi! Thank you for contributing to the vLLM project. 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 do one of these:
🚀 |
Signed-off-by: Russell Bryant <[email protected]> Signed-off-by: Loc Huynh <[email protected]>
Signed-off-by: Russell Bryant <[email protected]> Signed-off-by: Sumit Dubey <[email protected]>
Signed-off-by: Russell Bryant <[email protected]>
Signed-off-by: Russell Bryant <[email protected]> Signed-off-by: Maxime Fournioux <[email protected]>
Signed-off-by: Russell Bryant <[email protected]> Signed-off-by: Tyler Michael Smith <[email protected]>
Signed-off-by: Russell Bryant <[email protected]>
A prior PR, #9928, modified this workflow to only run when relevant
files have changed. However, github is configured to expect and
require this workflow to run and pass before a PR can be auto-merged.
GitHub configuration is not quite flexible enough to say "require this
workflow to pass before merging, but only if we plan to run it."
This change is the simplest: just run it always. The change also
leaves a comment in the workflow explaining why it is this way.
An alternative in the future could be to switch to a different
framework for doing auto-merges. Mergify, which is already in use for
some things, has flexible enough policy configuration to capture more
complex merge criteria. Swithing to it just because of this is not
necessary.
Signed-off-by: Russell Bryant [email protected]