Skip to main content

What the check does

Flags a job that declares an environment: (a deployment) but no resource_group:.

Why it matters

Without a resource_group, two pipelines can run the same deployment job at the same time and race on the target — producing interleaved or half-applied deploys and inconsistent state. A resource group serializes jobs so only one runs against the environment at a time. This is the GitLab analog of the GitHub Actions missing-concurrency check.