Drop ruff from GitHub Actions as it is covered by pre-commit.ci

[zerolab]

IMHO there is no need to do additional processing if you don't have to

[marksweb]

Yeah, that's a fair point. I think I get into the habbit of both, because not all repos are public and get the pre-commit bot.

[cclauss]

The dual processing is a red herring given that ruff (in rust) can lint the entire CPython codebase in a small fraction of a second. The setup/teardown dwarfs the ruff runtime. It is useful to add GitHub Annotation to the pull request via the option ruff --output-format=github in the GHA yaml while that setting would be misplaced in pre-commit.

[zerolab]

@cclauss Do you have an example of ruff --output-format=github in action?

[cclauss]

ruff --output-format=github gives us GitHub Actions annotations:

[zerolab]

TIL! This does look rather usefil. I had a check and the whole action takes about 5s. It all adds up in the end, but... @marksweb would you like a PR re-adding the action with --output-format=github?

[cclauss]

One performance hint is that you can skip the setup-python step in that GitHub Action because while ruff is installed via pip it is Rust code, not Python code so GHA's built-in Python is more than adequate.

[marksweb]

This is indeed useful and interesting @zerolab. I think it's worth having a dedicated ruff workflow setup like that.

Thanks @cclauss!