P005 unsupported

A step ci-parity can’t analyze, so it’s skipped and reported.

Severity: warning. Warnings don’t fail the check.

Example

jobs:
  windows:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v7
      - name: Test
        run: pnpm test
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - name: Deploy
        run: $DEPLOY_TOOL deploy

.github/workflows/ci.yml
  7:9     P005 unsupported   step uses shell 'pwsh'; not analyzed
  13:14   P005 unsupported   dynamic command name '$DEPLOY_TOOL' cannot be analyzed

0 errors, 2 warnings, 0 tolerated, 0 allowed

The windows job’s default shell is pwsh, which ci-parity doesn’t parse.

The cases

Message	Cause	What to do
step uses shell '<shell>'; not analyzed	A shell other than bash or sh, including a Windows runner’s default pwsh	Set shell: bash if the script is bash, or accept the warning
composite step has no shell; not analyzed	A run: step in a composite action without shell:	Add shell: bash
cannot parse step script: <error>	The script isn’t valid shell	Fix the script
dynamic command name '<word>' cannot be analyzed	The command is a variable or expression	Name the command, or accept the warning
allow comment has no reason	# ci-parity: allow without text after it	Add the reason

See also

• Rules
• Rules reference
• Analysis reference

Last reviewed: 2026-10-28