GitHub Actions
CI/CD built into GitHub repositories. GitHub Actions is GitHub's built-in automation service. Workflows defined in YAML run on events such as pushes, pull requests or schedules, on GitHub-hosted runners or on your own self-hosted runners. A large marketplace of reusable actions covers building, testing, scanning and deploying.
When it is the right choice
- Your code already lives on GitHub
- You want CI/CD next to pull requests with little setup
- You need to deploy to clouds without long-lived secrets, using OIDC
- Costs can grow with heavy builds on hosted runners; self-hosted runners or another system may fit better
How we use it
- Build pipelines that test, scan, build images and deploy through reviewed pull requests
- Use OIDC to authenticate to AWS, Google Cloud and Azure instead of stored keys
- Run self-hosted runners on Kubernetes for speed, cost or private network access
- Add AI review steps that summarise changes and flag risks for human reviewers
Related articles
CI/CD for Models and PromptsEvaluation gates, model registries, canary releases and rollback: applying CI/CD discipline to prompts and models in LLM applications.
Simpler Infrastructure, Faster Engineering TeamsSimpler infrastructure helps engineering teams move faster, deploy more efficiently, and focus on building products.
Internal Developer Platforms (IDP): Build or Buy?Should you build your own Internal Developer Platform (IDP) or buy one? Compare costs, setup time, and focus on your core product with DoneDeploy.GitHub Actions: frequently asked
Are third-party actions safe to use?
Treat them as dependencies. Pin actions to a commit SHA, limit workflow permissions and review what each action does.
When should we use self-hosted runners?
When builds need private network access, special hardware such as GPUs, or when hosted minutes become expensive. They need patching and isolation like any server.
Running GitHub Actions, or deciding whether to? Tell us what you have; the first consultation is free.
Let's talk »

