GitHub · GH-200
Secrets and variables
GH-200 · Lesson 13 of 16 · 1:55:40
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: secrets and variables at the organization, repository, and environment levels, access policies and precedence, naming rules, limits and timing, using them in workflows, composite actions, and reusable workflows, and managing them with gh secret set and the REST API, with libsodium encryption. Includes three original practice questions.
Preview the topics
- Contoso has a secret named STORE_KEY at the organization level, at the repository level, and in the production environment. A job that targets production reads it. Which value does it get?
- Contoso’s composite action needs the store’s API key, and its steps reference the secrets context, which comes back empty. What’s the fix?
- A Contoso rotation script sends the new store key to the REST API in plain text, and the call is rejected. What should the script do?