[CI/Build] Limit github CI jobs based on files changed

[russellb]

I noticed that these github CI jobs run against all PRs, including ones where
the job is not relevant. We can save a bit of time and resources by only running
jobs when relevant files have changed.

This PR would reduce the jobs that run by quite a bit on a PR that only changes
docs, for example.

8f2f678 [CI/Build] Conditionally run clang-format
b1daf19 [CI/Build] Conditionally run mypy job
692d7cf [CI/Build] Conditionally run ruff job
bd611ca [CI/Build] Conditionally run yapf job
b837e46 [CI/Build] Add actionlint error matcher to job paths
18fc405 [CI/Build] Move codespell to its own job
8dbb595 [CI/Build] Only run the ruff job with one Python version
3942c38 Run mypy job when pyproject.toml changes
faff4e6 Only run yapf with Python 3.12

commit 8f2f678
Author: Russell Bryant [email protected]
Date: Fri Nov 1 17:18:49 2024 +0000

[CI/Build] Conditionally run clang-format

Update the `clang-format` job to only run when relevant files have
changed: `*.h`, `*.cpp`, `*.cu`, or `*.cuh`. This matches the patterns
in the `find` command in this job. Also run the workflow when the
workflow definition itself changes.

Signed-off-by: Russell Bryant <[email protected]>

commit b1daf19
Author: Russell Bryant [email protected]
Date: Fri Nov 1 17:23:07 2024 +0000

[CI/Build] Conditionally run mypy job

Only run the `mypy` CI job when the following paths change:

- any Python file, `*.py`
- the workflow definition
- `tools/mypy.sh`

Signed-off-by: Russell Bryant <[email protected]>

commit 692d7cf
Author: Russell Bryant [email protected]
Date: Fri Nov 1 17:26:23 2024 +0000

[CI/Build] Conditionally run ruff job

Only run the `ruff` CI job when relevant paths change:

- the workflow file, or the error matching config
- pyproject.toml
- any Python file, `*.py`
- requirements-lint.txt

Signed-off-by: Russell Bryant <[email protected]>

commit bd611ca
Author: Russell Bryant [email protected]
Date: Fri Nov 1 17:28:19 2024 +0000

[CI/Build] Conditionally run yapf job

Only run `yapf` job when the following paths change:

- any python file, `*.py`
- the workflow definition file

Signed-off-by: Russell Bryant <[email protected]>

commit b837e46
Author: Russell Bryant [email protected]
Date: Fri Nov 1 17:29:13 2024 +0000

[CI/Build] Add actionlint error matcher to job paths

Run the actionlint job if the error matching config changes.

Signed-off-by: Russell Bryant <[email protected]>

commit 18fc405
Author: Russell Bryant [email protected]
Date: Fri Nov 1 17:43:15 2024 +0000

[CI/Build] Move codespell to its own job

Move `codespell` out of the `ruff` job because `codespell` checks more
file types than `ruff`. This one needs to run on doc-only changes,
whiel `ruff` does not.

Signed-off-by: Russell Bryant <[email protected]>

commit 8dbb595
Author: Russell Bryant [email protected]
Date: Fri Nov 1 17:44:34 2024 +0000

[CI/Build] Only run the ruff job with one Python version

Ruff itself is not a Python tool, so running it in 5 different Python
environments doesn't provide much value, other than ensuring
`requirements-lint.txt` can be installed in all of these versions.
That doesn't seem like enough value to run 5 copies of the job all the
time.

Coverage using different Python versions makes more sense for jobs
that are actually running the code.

Signed-off-by: Russell Bryant <[email protected]>

commit 3942c38
Author: Russell Bryant [email protected]
Date: Mon Nov 4 20:57:39 2024 +0000

Run mypy job when pyproject.toml changes

Signed-off-by: Russell Bryant <[email protected]>

commit faff4e6
Author: Russell Bryant [email protected]
Date: Mon Nov 4 20:59:52 2024 +0000

Only run yapf with Python 3.12

There does not seem to be much benefit of running several versions of
this.

Signed-off-by: Russell Bryant <[email protected]>

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
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 do one of these:

• Add ready label to the PR
• Enable auto-merge.

🚀

[russellb]

I mentioned this on Slack, too, but this isn't merging because the repo is still configured to expect ruff (3.8) to pass before it merges. That requirement must be updated to expect ruff (3.12).