github-actions-debugginglisted

# GitHub Actions Debugging Work out whether the problem is the trigger, the permissions, the runner, or the job itself. ## Purpose **Use this when:** - A workflow does not run when you expect it to. - A job fails with a permissions error, or an OIDC role assumption fails. - The cache never hits, or builds are much slower than they should be. - A step passes locally and fails in CI, or the reverse. - A deployment job hangs, or deploys the wrong thing. **Do not use this when:** - The application code is broken — CI is correctly reporting a real failure. - The failure is in the infrastructure being deployed — use `terraform-troubleshooting` or the relevant layer skill. **What this skill assumes:** access to the workflow file and the run logs. The `gh` CLI is used throughout; everything is also available in the web UI. ## Operating Procedure 1. **Determine whether it ran at all.** "Failed" and "never triggered" are different problems with no overlap. 2. **Read the log from the failing step**, including the setup steps above it. The cause is frequently in a step that reported success. 3. **Classify**: trigger, permissions, environment, dependency, or the command itself. 4. **Reproduce as narrowly as possible.** A container that matches the runner, or a debug run. 5. **Check what differs from local.** Environment variables, secrets, working directory, the checkout's depth, and the runner image contents. 6. **Fix and re-run** the failed jobs, not the whole workfl