GitHub · GH-200
Caching, artifacts, outputs, and job summaries
GH-200 · Lesson 5 of 16 · 35:20
YouTube loads only after you press play. This chapter opens at its timestamp in the full course. Watch on YouTube ↗
In this lesson
Prepare for the GH-200 exam (GitHub Actions). In this lesson: dependency caching with keys, restore keys, scopes, and limits, artifacts with upload-artifact and download-artifact, retention periods and the artifact-and-log-retention REST API, outputs between steps and jobs, job summaries with GITHUB_STEP_SUMMARY, status badges, and environment protections. Includes three original practice questions.
Preview the topics
- Contoso’s workflow caches npm downloads under a key that never changes. After the team upgrades several packages, builds still restore the old cache, and download the new packages every time. What should the key include?
- Contoso’s build job writes a version to GITHUB_OUTPUT in a step with the id ver, and the deploy job, which needs build, reads the version from needs, but gets an empty value. What’s missing?
- Contoso wants production deployments to wait for approval from the release team, to come only from the main branch, and to keep the deploy key out of reach until then. What should they configure?