Sandbox::https://github.com/wp-cli/wp-cli/blob/main/.github/actionlint.yml

Repository navigation

# Configuration for actionlint, run by the `actionlint` job in

# `.github/workflows/reusable-code-quality.yml`.

paths:

.github/workflows/**/*.{yml,yaml}:

ignore:

# `copilot-requests` is a real permission scope - it is what lets a

# workflow authenticate the Copilot CLI with the built-in `GITHUB_TOKEN`

# instead of a personal access token - but actionlint's hard-coded scope

# list has not caught up with it yet, so it reports every use as unknown.

# Drop this entry once actionlint ships the scope, and it will go back to

# catching genuine typos in permission names.

# See https://docs.github.com/en/copilot/how-tos/copilot-cli/use-copilot-cli-in-actions

- 'unknown permission scope "copilot-requests"'

# Steps can run in parallel through the `background`, `wait`, `wait-all`,

# `cancel` and `parallel` keywords, but actionlint does not know them yet:

# it rejects `background` as an unexpected key, and a `wait-all` or

# `parallel` step as one that has neither `run` nor `uses`. Drop these

# entries once actionlint supports the keywords. Until then, a step that is

# genuinely missing both `run` and `uses` is no longer reported.

# See https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsparallel

- 'unexpected key "background" for step'

- 'step must run script with "run" section or run action with "uses" section'