GitHub · GH-200
Action types and metadata
GH-200 · Lesson 9 of 16 · 1:24: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: JavaScript, Docker container, and composite actions and when to use each, the action.yml metadata file (inputs, outputs, runs, branding), files and folders for shared and local actions, bundled JavaScript code, and workflow commands inside actions with the Actions toolkit. Includes three original practice questions.
Preview the topics
- Contoso’s security scanner needs a specific Linux tool and its libraries, and must behave the same everywhere it runs, on Ubuntu runners. Which action type fits?
- Contoso’s notify action declares its webhook-url input as required, yet a workflow that omits it still runs the action, which fails later with a confusing error. What should the action do?
- Contoso’s composite action runs its install script with a relative path, and the step fails with file not found in every repository that uses it. What should the step use?