Prevent overlapping GitHub Actions deployments with one environment key

For GitHub Actions concurrency deployment, the safest approach is a bounded operational change, not a command pasted without context. This runbook starts with effective state, shows the smallest candidate action, and finishes by repeating the real user or system path.

TL;DR: A concurrency group allows one running and one pending job or workflow per key; cancel-in-progress determines whether a newer run interrupts active work. Capture a baseline with rg -n 'concurrency:|environment:' .github/workflows, make the reviewed change only when the evidence matches, then verify with gh run list --workflow deploy.yml --limit 10 and keep the rollback ready.

Audience: repository maintainers who can edit Actions workflows and control the production environment they deploy to. This guide assumes familiarity with GitHub Actions delivery and a change window appropriate to the system.

The direct answer

Production has one stable concurrency key and deployment history shows serialized state transitions. That is the success condition for GitHub Actions concurrency deployment; command completion by itself is not enough.

The important boundary is workflow trigger, token permissions, runner trust, artifact identity, environment protection, and target-host change. A concurrency group allows one running and one pending job or workflow per key; cancel-in-progress determines whether a newer run interrupts active work. If an observation does not identify which side of that boundary failed, collect a narrower observation before changing state.

How the mechanism works

For GitHub Actions concurrency deployment, use this mental model: GitHub Actions evaluates a workflow event, grants a job-scoped identity and permissions, schedules a runner, executes third-party and shell steps, then records job and deployment state. The model prevents a common mistake—treating configuration text, control-plane acceptance, process state, and end-user behavior as the same proof.

Follow four stages:

1. Observe: identify the exact host, object, version, owner, and active configuration.
2. Interpret: write the expected result, the abnormal result, and what would remain inconclusive.
3. Change: apply one reviewed action at the narrowest layer that contradicts the baseline.
4. Verify: repeat the original path and compare the same evidence, including adjacent safety controls.

Preflight and safety boundary

Pin actions, minimize token permissions, protect the production environment, and keep a rollback artifact independent of the runner performing the deployment.

Before GitHub Actions concurrency deployment, record UTC time, the current version or digest, the exact target, recent changes, and who owns the workload. The rollback for this runbook is: finish or roll back the interrupted deployment, restore the prior workflow, and use a non-canceling production group until steps are resumable.

Do not continue if the target identity is ambiguous, the current state cannot be saved, the only recovery session would be at risk, or the proposed command affects more objects than the brief names.

Capture the read-only baseline

Run these commands one at a time. Replace example names and addresses deliberately; do not paste production secrets into a transcript.

rg -n 'concurrency:|environment:' .github/workflows
gh run list --workflow deploy.yml --limit 10
gh api repos/{owner}/{repo}/deployments?per_page=10

Interpret the baseline before moving on:

• Expected: production has one stable concurrency key and deployment history shows serialized state transitions.
• Abnormal: expressions produce different case-insensitive keys, reusable workflows choose another key, or cancellation interrupts a non-idempotent step.
• Inconclusive: missing output can also mean the wrong context, permissions, namespace, log window, binary, or target. Prove those assumptions before treating absence as health.

Save the decisive output, exit status, and timestamp. Redact credentials, customer data, private topology, tokens, and complete environment dumps.

Apply the smallest candidate change

The following is state-changing example syntax, not an instruction to run it unchanged:

gh workflow run deploy.yml -f environment=production

For GitHub Actions concurrency deployment, the proposed change is acceptable only when the read-only baseline predicts its effect and the rollback is available. The key risk is: canceling an in-flight database or traffic migration can leave production between states.

Prefer an immutable artifact, validated configuration, dry-run, transaction, candidate object, or staged target when the tool supports one. Record the exact command and UTC time so later telemetry can be correlated to the change.

Verify the result from the outside in

gh run list --workflow deploy.yml --limit 10
gh run view --log-failed
gh api repos/{owner}/{repo}/deployments?per_page=10

Verification for GitHub Actions concurrency deployment has three layers:

1. The control plane or command reports the intended effective state.
2. The process, resource, or data path reflects that state without a new pressure signal.
3. The original user-visible or dependent-system path succeeds from an independent vantage point.

If gh run list --workflow deploy.yml --limit 10 succeeds but the original path still fails, stop. The change may have repaired a local symptom while DNS, policy, routing, caching, dependency, or client state remains broken.

Failure branches

The baseline does not match this runbook

When expressions produce different case-insensitive keys, reusable workflows choose another key, or cancellation interrupts a non-idempotent step, do not force the candidate command. Return to identity and scope, compare a healthy peer only through effective settings, and name a new falsifiable mechanism.

The change succeeds but behavior does not

A successful gh workflow run deploy.yml -f environment=production proves that one interface accepted a request. It does not prove convergence, readiness, data compatibility, external routing, or client recovery. Re-run the same evidence at each downstream boundary.

The change makes the system worse

Execute the written rollback: finish or roll back the interrupted deployment, restore the prior workflow, and use a non-canceling production group until steps are resumable. Preserve the failed candidate and relevant logs long enough to explain the outcome; do not destroy the evidence with broad cleanup or repeated restarts.

Operator checklist

• Confirm the exact target, context, identity, version, and active owner.
• Capture the read-only baseline and one disconfirming observation.
• Label gh workflow run deploy.yml -f environment=production as state-changing during review.
• Keep recovery access and rollback independent of the path being edited.
• Change one layer, record UTC time, and wait for its real convergence boundary.
• Verify the original path, adjacent controls, resource pressure, and persistence.
• Update the runbook when observed behavior differs from the source-reviewed model.

Investigate it in Tryssh

$ gh run list --workflow deploy.yml --limit 10
Expected: production has one stable concurrency key and deployment history shows serialized state transitions.

Tryssh can preserve this evidence loop and show a state-changing command for human approval. It does not make the operator's identity, recovery access, rollback, or platform authority decisions.

Evidence and review status

This GitHub Actions concurrency deployment runbook was source-reviewed on 2026-07-29 against current first-party documentation. The commands are illustrative and use example targets. The page does not claim that the change was reproduced across every distribution, managed service, version, network, or workload.

Limitations and trade-offs

Canceling an in-flight database or traffic migration can leave production between states. Managed platforms may generate configuration, restrict privileges, replace local state, or expose a different control plane than the upstream project. Confirm the installed version and provider contract before applying a repair.

Search visibility is not proof of operational correctness. Treat this page as a decision aid, preserve independent recovery, and stop when the evidence contradicts its assumptions.

Related operator runbooks

Continue with GitHub Actions environment approval, GitHub Actions SSH known_hosts, the GitHub Actions delivery foundation guide, and the SSH hardening checklist.

Sources and further reading

• GitHub Actions concurrency deployment first-party reference
• GitHub Actions documentation
• GitHub Actions secure use reference
• GitHub Actions deployment controls