GitHub Actions "Job is about to start running but no steps"

By Daniel Zoghalchali·Latchkey

A job needs at least one step. If the steps list is empty or fully resolved away (all skipped by an if), the runner has nothing to do and the job is effectively a no-op.

What this error means

A job is picked up by a runner but finishes immediately with no logged commands. The expected build/test work never ran, and downstream jobs that needed its output see nothing.

Job is about to start running on the runner but no steps were defined to run

Common causes

Empty or missing steps list

The job declares runs-on but the steps: key is empty, commented out, or absent.

Every step skipped by a condition

All steps carry an if that evaluated false, so nothing executed even though the job was acquired.

How to fix it

Define at least one runnable step

1. Add a steps: list with at least one uses or run step.
2. Review per-step if conditions so they do not all evaluate false.
3. Use actions/checkout plus the actual build/test commands.

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test

How to prevent it

• Lint workflows so jobs without steps are flagged.
• Avoid blanket if conditions that can skip every step.
• Treat an instantly-finishing job as suspicious in review.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions