You have a GitHub repository that has a GitHub Actions workflow.

Target

Value

Top-level property

concurrency

Concurrency-group property

group

Cancellation property

cancel-in-progress

Result:

concurrency:

group: production

cancel-in-progress: true

The concurrency block defines a shared execution group. Assigning group: production places all production deployment runs into the same group, preventing simultaneous deployments to that target.

Setting cancel-in-progress: true changes the default behavior by cancelling an active deployment when a newer workflow run enters the group. This ensures that only the latest production deployment continues rather than allowing an outdated deployment to finish after a newer version has been requested.

The concurrency block is normally placed at the workflow level when the policy applies to the full deployment workflow. It can also be scoped to a job when only a specific deployment job needs coordination. The environment name identifies the production target, but environment configuration alone does not impose the required single-active-run and cancellation behavior.

A production concurrency group should be reserved for operations that genuinely target the same deployment resource. Reusing it for unrelated jobs would unintentionally serialize unrelated work.

Study-guide topics: deployment coordination, concurrency groups, cancellation policy, and safe production execution. Reference: GitHub Actions—Control concurrency .