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.
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."
To use actions from GitHub.com, your self-hosted runners must be able to download public actions from
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.com. If a user has already created 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. For more information, see "Automatic retirement of namespaces for actions accessed on GitHub.com."
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 GitHub Connect.
Under "Users can utilize actions from GitHub.com in workflow 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."
When you enable GitHub Connect, users see no change in behavior for existing workflows because GitHub Actions searches your GitHub Enterprise Server instance for each action before falling back to GitHub.com. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on GitHub.com.
Automatic retirement of namespaces for actions accessed on GitHub.com blocks the potential for a man-in-the-middle attack by a malicious user with access to your GitHub Enterprise Server instance. When an action on GitHub.com is used for the first time, that namespace is retired in your GitHub Enterprise Server instance. This blocks any user creating an organization and repository in your enterprise that matches that organization and repository name on GitHub.com. This ensures that when a workflow runs, the intended action is always run.
After using an action from GitHub.com, if you want to create an action in your GitHub Enterprise Server instance with the same name, first you need to make the namespace for that organization and repository available.
From an administrative account on GitHub Enterprise Server, click in the upper-right corner of any page.
In the left sidebar, under Site admin click Retired namespaces.
Locate the namespace that you want use in your GitHub Enterprise Server instance and click Unretire.
Go to the relevant organization and create a new repository.
Tip: When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on GitHub.com before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository.