GitHub · GH-200
Triggers and events
GH-200 · Lesson 1 of 16 · 4:04
YouTube loads only after you press play. Watch on YouTube ↗
In this lesson
Prepare for the GH-200 exam (GitHub Actions). In this lesson: repository events with branches, paths, and activity type filters, schedules with cron, time zones, and the default branch, manual runs with workflow_dispatch, webhook events and repository_dispatch, choosing events for their security context (pull_request, pull_request_target and its default policy in public repositories, workflow_run), least-privilege permissions for the GITHUB_TOKEN, typed workflow_dispatch inputs, and inputs and secrets for reusable workflows with workflow_call and secrets: inherit. Includes three original practice questions.
Preview the topics
- Contoso’s nightly test workflow has a schedule trigger, but it has never run. The workflow file only exists on the feature branch where the team is still editing it. Why doesn’t it run?
- In Contoso’s private SDK repository, a workflow adds labels to every new pull request, including pull requests from forks. It needs write access to pull requests, but must never run code from the fork. Which event fits?
- Contoso’s release workflow calls a reusable deploy workflow from another repository in the same organization. The called workflow declares a required secret DEPLOY_KEY, the caller only passes an environment input, and the run fails. What should the calling job add?