GitHub · GH-200
Jobs, steps, and workflow commands
GH-200 · Lesson 2 of 16 · 12:28
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: jobs and steps, defaults, timeouts, continue-on-error, and concurrency groups, job dependencies with needs, if conditions and the status check functions (success, always, cancelled, failure, and why !cancelled() is recommended), environment variables and the GITHUB_ENV, GITHUB_PATH, and GITHUB_OUTPUT files, workflow commands for annotations, groups, debug messages, masking, and stop-commands, and the GitHub Actions extension for VS Code. Includes three original practice questions.
Preview the topics
- Contoso’s workflow has build, test, and report jobs. The report job needs test, and must post the results whether test passes or fails, but not when someone cancels the run. Which condition fits the report job?
- A Contoso step computes a build number and appends it to the GITHUB_ENV file. Later in the same step, the script reads the variable, and it’s empty. What explains it?
- A Contoso developer wants mistakes in workflow files caught before committing, including wrong input names for the actions and reusable workflows they call, and wants to read run logs without leaving the editor. What should they use?