About GitHub Actions on GitHub AE
GitHub Actions is enabled for GitHub AE by default. To get started using GitHub Actions within your enterprise, you need to manage access permissions for GitHub Actions and add runners to run workflows.
Before you get started, you should make a plan for how you'll introduce GitHub Actions to your enterprise. For more information, see "Introducing GitHub Actions to your enterprise."
If you're migrating your enterprise to GitHub Actions from another provider, there are additional considerations. For more information, see "Migrating your enterprise to GitHub Actions."
Managing access permissions for GitHub Actions in your enterprise
You can use policies to manage access to GitHub Actions. For more information, see "Enforcing policies for GitHub Actions in your enterprise."
You must configure and host your own machines to run jobs for your enterprise on GitHub AE. Self-hosted runners allow you to host your own runners and customize the environment used to run jobs in your GitHub Actions workflows. For more information, see "Getting started with self-hosted runners for your enterprise" and "Hosting your own runners."
General security hardening for GitHub Actions
If you want to learn more about security practices for GitHub Actions, see "Security hardening for GitHub Actions."