Note: GitHub Actions was available for GitHub Enterprise Server 2.22 as a limited beta. The beta has ended. GitHub Actions is now generally available in GitHub Enterprise Server 3.0 or later. For more information, see the GitHub Enterprise Server 3.0 release notes.
- For more information about upgrading to GitHub Enterprise Server 3.0 or later, see "Upgrading GitHub Enterprise Server."
- For more information about configuring GitHub Actions after you upgrade, see the documentation for GitHub Enterprise Server 3.0.
Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.
About GitHub Actions permissions for your organization
By default, after GitHub Actions is enabled on your GitHub Enterprise Server instance, it is enabled on all repositories and organizations. You can choose to disable GitHub Actions or limit them to local actions only, which means that people can only use actions that exist in your repository. For more information about GitHub Actions, see "About GitHub Actions."
You can enable GitHub Actions for all repositories in your organization. When you enable GitHub Actions, workflows are able to run actions located within your repository and any other public repository. You can disable GitHub Actions for all repositories in your organization. When you disable GitHub Actions, no workflows run in your repository.
Alternatively, you can enable GitHub Actions for all repositories in your organization but limit the actions a workflow can run. When you enable local actions only, workflows can only run actions located in your repository, organization, or enterprise.
Managing GitHub Actions permissions for your organization
- In the top right corner of GitHub Enterprise Server, click your profile photo, then click Your organizations.
- Next to the organization, click Settings.
- In the left sidebar, click Actions.
- Under Local and third-party Actions, select an option.
- Click Save.