When GitHub Actions misbehaves, the cause is usually one of a handful of familiar issues. Here is how to spot and fix them fast.
The usual suspects
- Using un-pinned third-party actions (tag can move under you) - pin to a SHA
- Storing cloud keys as secrets instead of using OIDC
- Over-broad GITHUB_TOKEN permissions; scope them per job
Commands for diagnosis
# Run and debug workflows locally with act
act -j test
gh run watch # follow the latest run from the CLIPrevent the repeat
- Pin actions to a commit SHA and review third-party actions before use
- Use OIDC for cloud auth and set minimal permissions blocks
- Cache dependencies and split long jobs with a matrix
Want senior help putting GitHub Actions to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.