CI/CD with GitHub Actions · 12-day planAll days
Day 8 of 12 30 minSecretspermissionsForks
Workflows hold the keys to your production systems, so treat them carefully. Store credentials as secrets and see how they're masked, give the GITHUB_TOKEN only the permissions a job needs, understand why pull requests from forks get no secrets, guard deployments with environments, and pin third-party actions.
By the end of today you can
- Store and use credentials as repository secrets
- Explain masking and why secrets must still be handled carefully
- Set least-privilege permissions for the GITHUB_TOKEN
- Explain why pull requests from forks don't receive secrets
- Pin third-party actions and protect deployments with environments
What's inside
- 5 sections
- 2 diagrams and mind maps
- 3 code examples you can run
- 5-question quiz
- 1Secrets
- 2Pull requests from forks
- 3The GITHUB_TOKEN and permissions
- 4Pinning actions
- 5Environments
Sign in free to read this lesson
Get the full lesson with diagrams, runnable code and the quiz. Your progress is saved across devices.
Sign in free