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.
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.
Note: With GitHub Connect enabled, GitHub Actions will try to find the repository on your GitHub Enterprise Server instance first before falling back to GitHub. If a user creates an organization and repository in your enterprise that matches an organization and repository name on GitHub, the repository on your enterprise will be used in place of the GitHub repository. A malicious user could take advantage of this behavior to run code as part of a workflow.
By default, GitHub Actions workflows on GitHub Enterprise Server cannot use actions directly from GitHub.com or GitHub Marketplace.
To make all actions from GitHub.com available on your enterprise instance, you can use GitHub Connect to integrate GitHub Enterprise Server with GitHub Enterprise Cloud. For other ways of accessing actions from GitHub.com, see "About using actions in your enterprise."
Before enabling access to all actions from GitHub.com on your enterprise instance, you must connect your enterprise to GitHub.com. For more information, see "Connecting your enterprise to GitHub Enterprise Cloud."
In the top-right corner of GitHub Enterprise Server, click your profile photo, then click Enterprise settings.
In the enterprise account sidebar, click Settings.
In the left sidebar, click GitHub Connect.
Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select Enabled.
After you enable GitHub Connect, you can use policies to restrict which public actions can be used in repositories in your enterprise. For more information, see "Enforcing GitHub Actions policies for your enterprise."