How to Secure Your GitHub Actions

How to Secure Your GitHub Actions

NDC Conferences via YouTube Direct link

Persisting data between runs

16 of 25

16 of 25

Persisting data between runs

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

How to Secure Your GitHub Actions

Automatically move to the next video in the Classroom when playback concludes

  1. 1 GitHub Actions Security
  2. 2 What are GitHub workflows?
  3. 3 Workflow example
  4. 4 Repository security
  5. 5 Code - Who has access?
  6. 6 Configuring access
  7. 7 From the user
  8. 8 Workflow secrets
  9. 9 Who has access to your secrets?
  10. 10 Your code - Best practices
  11. 11 Your code/repo – trace changes (org level)
  12. 12 Self-hosted runners
  13. 13 Self hosted runners
  14. 14 Workflow Runners Security
  15. 15 Best practice: Run the action inside of a container
  16. 16 Persisting data between runs
  17. 17 Workflow runners - Best practice
  18. 18 Protective measures
  19. 19 Recommendation
  20. 20 Forking actions
  21. 21 Enable DevOps teams to test actions
  22. 22 Staying up to date
  23. 23 Create an update process yourself
  24. 24 Automate the update Use a workflow
  25. 25 Best practices summarized

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.