Quick answer
A valid CI config must define at least one job.
CI Config Missing Jobs
A valid CI config must define at least one job. In GitHub Actions, 'jobs' is required and must be a non-empty object; in GitLab CI, you need at least one job key (e.g. build, test).
Common causes
- Empty or missing 'jobs' block in a GitHub Actions workflow.
- Only reserved keys (stages, variables) in GitLab CI with no actual jobs.
How to fix
- Add a 'jobs' object with at least one job (e.g. jobs: build: ...) for GitHub Actions.
- Add at least one job (e.g. build:, test:) under the root for GitLab CI.
- Use the CI Config Linter to check structure.
FAQ
- Can a GitHub Actions workflow have no jobs?
- No. The 'jobs' key is required and must contain at least one job.
Fix it now
Try in validator (prefill this example)