GitHub · GH-200
Governing actions and workflows
GH-200 · Lesson 11 of 16 · 1:39:46
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: allowed actions and reusable workflows with allow and block lists, requiring full-length SHA pinning and workflow dependency lockfiles, organization defaults for the GITHUB_TOKEN, pull request creation, fork approvals, and runners, Actions policies with actor and event rules, and managing shared components with CODEOWNERS and Dependabot. Includes three original practice questions.
Preview the topics
- Contoso’s organization now allows only the actions and reusable workflows of the organization itself, and every workflow fails on its checkout step. What’s the cause, and the fix?
- Contoso wants contractors to keep write access to the game repository, but only the release team may start its deployment workflow by hand. What should the platform team configure?
- Contoso wants every change to the workflow files of its repositories to be reviewed by the platform team before merging. What should each repository use?