Practice & Assessment
Test your understanding of GitHub Actions and CI/CD Automation
Multiple Choice Questions
6In GitHub Actions, what is a 'runner'?
Where must workflow YAML files be stored in a GitHub repository?
How do you reference a secret named API_KEY inside a GitHub Actions workflow?
What does the 'needs' keyword do in a GitHub Actions workflow?
What is the advantage of using OIDC (OpenID Connect) in GitHub Actions over storing cloud credentials as secrets?
What is a matrix strategy in GitHub Actions?
Mini Project
Automated Multi-Environment Deployment Pipeline
Build a full GitHub Actions CI/CD pipeline for a web application with three environments: development, staging, and production. The pipeline should: automatically run lint and tests on every PR, deploy to development on every push to the develop branch, deploy to staging on every push to main with required reviewer approval, and deploy to production only when a tag matching v*.*.* is pushed. Use GitHub Environments for each stage, add deployment protection rules, store all credentials as secrets, and use OIDC if deploying to a cloud provider. Add a workflow that auto-tags a patch release when PRs with the label 'release' are merged.