GitHub Actions is enabled for your enterprise by default. To get started using GitHub Actions within your enterprise, you can manage the policies that control how enterprise members use GitHub Actions and optionally add self-hosted 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."
You can use policies to control how enterprise members use GitHub Actions. For example, you can restrict which actions are allowed and configure artifact and log retention. For more information, see "Enforcing policies for GitHub Actions in your enterprise."
To run GitHub Actions workflows, you need to use runners. A runner is a server that runs your workflows when they're triggered. If you use GitHub-hosted runners, you will be be billed based on consumption after exhausting the minutes included in GitHub Enterprise Cloud, while self-hosted runners are free. For more information, see "About billing for GitHub Actions."
For more information, see "About self-hosted runners."
If you choose self-hosted runners, you can add runners at the enterprise, organization, or repository levels. For more information, see "Adding self-hosted runners."
If you want to learn more about security practices for GitHub Actions, see "Security hardening for GitHub Actions."