An event starts the workflow
A push, pull request, schedule, or manual event can trigger a GitHub Actions workflow. The workflow definition lives in the repository.
A CI/CD pipeline
The checks and build steps between a code change and a release.
Process overview
- Trigger
- Run
- Check
- Build
- Deploy
Steps
5 stepsJobs get an environment
Jobs run on hosted or self hosted runners. Independent jobs can run in parallel; dependencies make a job wait for prerequisite jobs.
Steps validate the change
Steps run commands or reusable actions. A typical project installs dependencies, checks the code, and runs tests before attempting a release.
Produce something deployable
A build job creates the application output. The pipeline can pass that output to later work rather than rebuilding the same change.
Move the output into an environment
A deployment job publishes the build to its target. Your workflow defines dependencies, credentials, and any approval gates required for that environment.
Keyboard: ←→
Scope
An illustrative CI/CD workflow using GitHub Actions. Test strategy, release gates, rollbacks, and hosting details are project specific.
