[BUG]: actionlint in pre-commit doesn't pass

[mdboom]

Is this a duplicate?

• I confirmed there appear to be no duplicate issues for this bug and that I agree to the Code of Conduct

Type of Bug

Something else

Component

General cuda-python

Describe the bug

When actionlint was added to the pre-commit config in #1018, it looks like none of our actions were actually fixed up to comply with the linter. This is one of the gotchas of pre-commit that I've run into in the past -- new lints don't get run on existing code until you edit those files, so you have to run pre-commit run --all-files to test.

This currently is blocking making changes to any of the GHA config.

Should we remove that linter and come back to it when we've fixed all the errors? (There's a lot of them, and bash isn't something I know well...)

How to Reproduce

$ pre-commit run --all-files

...dozens of errors...

Expected behavior

pre-commit run --all-files should pass cleanly.

Operating System

No response

nvidia-smi output

No response

[cpcloud]

Yeah, go ahead and remove it and I will add it back later and fix the problems. Bash is (un)fortunately a thing I have spent plenty of time with 😂

[cpcloud]

When I run pre-commit run -a, I don't see any issues reported:

❯ git rev-parse upstream/main
972ea4a5ee32acc1097ef7c20b4be48e9bd27057
…/cuda-python on  fix-actionlint via 🐍 via ❄️  impure (pixi-env-shell-env-env)
❯ pixi exec -w pre-commit -- pre-commit run -a
ruff (legacy alias)......................................................Passed
ruff format..............................................................Passed
Check SPDX Headers.......................................................Passed
Prevent markdown files in docs/source directories....(no files to check)Skipped
check for added large files..............................................Passed
check for case conflicts.................................................Passed
check docstring is first.................................................Passed
check for merge conflicts................................................Passed
check for broken symlinks................................................Passed
check toml...............................................................Passed
check yaml...............................................................Passed
debug statements (python)................................................Passed
fix end of files.........................................................Passed
mixed line ending........................................................Passed
trim trailing whitespace.................................................Passed
rst ``code`` is two backticks............................................Passed
rst directives end with two colons.......................................Passed
rst ``inline code`` next to normal text..................................Passed
mypy-pathfinder..........................................................Passed
Lint GitHub Actions workflow files.......................................Passed
cython-lint..............................................................Passed

@mdboom What are you seeing?

[cpcloud]

When I run actionlint as an executable, I get lots of errors. Seems like something is off with the pre-commit config.

[cpcloud]

Weird, the actionlint hook doesn't report anything, and the actionlint-docker hook does. Seems like an upstream bug.

I definitely ran pre-commit all before merging the original PR.