GitHub · GH-200
Reading runs and diagnosing failures
GH-200 · Lesson 6 of 16 · 54:05
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: reading a run summary and the Checks API, why a workflow never starts (disabled, default branch, merge conflicts, skip instructions, path filters, schedules), diagnosing failures with logs, run history, gh run view, debug logging, and the condition lines of system.txt, matrix failures by axis and reruns of failed or single jobs, and expanding anchors, aliases, and matrices before you analyze a workflow. Includes three original practice questions.
Preview the topics
- Contoso’s nightly cleanup workflow stopped running a month ago, but manual runs still work, and nobody disabled it. The engineer who last edited its cron schedule has left, and their account was deleted. What restarts the schedule?
- In Contoso’s matrix of three operating systems and two Node versions, both Windows jobs fail at the same step, and the four others pass. Where should the team look first?
- A Contoso workflow puts an anchor named build-defaults on its first job, with a 20-minute timeout, and three other jobs are aliases of build-defaults. Someone raises the timeout in the anchored job to 60. Which jobs change?