ci: ruff runs three times per pull request, once per Python version, checking the same thing

[LeyckerS]

.github/workflows/lint.yml runs the ruff steps inside the syntax-check job, and #69 put that job on a [3.10, 3.11, 3.12] matrix. So pip install ruff and ruff check . now execute three times on every pull request.

Linting is independent of the interpreter version — ruff.toml pins target-version = "py310" explicitly, so all three runs check identical rules against identical files and always reach the same verdict. Two of the three are pure cost, and they also make a lint failure show up as three red checks instead of one.

Byte-compiling genuinely does need the matrix: that is the part that can differ between versions, and it should stay where it is.

The change

Move the two ruff steps out of syntax-check into their own job that does not use a matrix. Something like:

  ruff:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v7

      - name: Set up Python
        uses: actions/setup-python@v6
        with:
          python-version: "3.10"

      - name: Install ruff
        run: pip install "ruff==0.16.1"

      - name: Lint with ruff
        run: ruff check .

Keep the version pin. An unpinned linter turns an unrelated pull request red the day upstream adds a rule.

Acceptance criteria

• ruff check . runs exactly once per pull request
• The syntax-check matrix still byte-compiles on 3.10, 3.11 and 3.12
• All jobs green

One file, no Windows machine needed. Worth pairing with #74, which fixes the other problem in the same workflow.

[nightcityblade]

I'm taking this one. I'll split Ruff into a single non-matrix job while keeping byte-compilation on all three Python versions, then run the repository's verification commands.

[LeyckerS]

@nightcityblade — yours, assigned.

One thing that will save you a round trip: keep the version pin. ruff==0.16.1 is deliberate — an unpinned linter turns somebody else's unrelated pull request red on the day upstream adds a rule, and they have no idea why.

Also worth knowing, since it landed after the issue was written: #77 changed the byte-compile step to git ls-files '*.py' | xargs python -m compileall -q and added lint.yml to the workflow's own paths trigger. Pull main before you start. The upside is that your change to lint.yml will now actually run CI on itself, which was not true this morning.

[LeyckerS]

@nightcityblade — still yours, no pressure. Writing because the file moved under you and that changes the issue.

When you claimed this, ruff ran three times per pull request. #129 has since added 3.13 and 3.14 to the matrix, so it now runs five times — five installs and five identical lint passes where one would do. The waste this issue is about roughly doubled, which makes it more worth doing, not less.

Two other things landed in .github/workflows/lint.yml since:

• ci: derive compileall file list from git ls-files #77 replaced the byte-compile list with git ls-files '*.py' | xargs python -m compileall -q and added the workflow's own path to its paths: trigger
• chore(deps): bound runtime dependencies and add tested constraints #136 added a separate dependency-contract job and extended paths: again to cover requirements.txt, constraints.txt and dependabot.yml

So pull main before you start — and the second one is useful precedent: it shows what a standalone job looks like in this file, which is exactly the shape the ruff steps need.

Nothing has changed about the fix itself. Keep the ruff==0.16.1 pin, keep syntax-check on the matrix since byte-compiling genuinely is version-dependent, and move only the two ruff steps out.

If you would rather hand it back, say so and I will mark it free with no hard feelings — and if you want it and life got busy, one sentence here keeps it yours indefinitely.