Skip to main content

Deployment for GitHub Actionss

Deployment in GitHub Actions is using a workflow to ship a built artifact to a target such as a cloud service, container registry or static host. GitHub environments add approval gates and environment secrets, and OpenID Connect lets a workflow obtain short-lived cloud credentials instead of storing long-lived keys.

Stage: Runners and Deployment · Part of the GitHub Actions roadmap · Last reviewed 19 November 2026

What to learn in Deployment

Deployment interview questions

What is OIDC in GitHub Actions deployments?

OpenID Connect lets a workflow request a signed token that a cloud provider trusts to issue temporary credentials. It removes stored cloud keys from secrets, and trust rules can limit access by repository, branch or environment.

What does the concurrency key do in a deployment workflow?

Concurrency groups runs by a name so only one runs at a time, and can cancel in-progress runs. For deployments it prevents two pushes from deploying simultaneously and leaving the target in an inconsistent state.

Where Deployment fits in the GitHub Actions roadmap

Deployment belongs to the Runners and Deployment stage (beginner level). Run and ship.

Back to the full GitHub Actions roadmap