About automatic access to GitHub.com actions
By default, GitHub Actions workflows on GitHub AE 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 AE with GitHub Enterprise Cloud.
To use actions from GitHub.com, your self-hosted runners must be able to make outbound connections to GitHub.com. No inbound connections from GitHub.com are required. For more information. For more information, see "About self-hosted runners."
Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the actions-sync tool. For more information, see "Manually syncing actions from GitHub.com."
About resolution for actions using GitHub Connect
When a workflow uses an action by referencing the repository where the action is stored, GitHub Actions will first try to find the repository on your enterprise. If the repository does not exist on your enterprise, and if you have automatic access to GitHub.com enabled, GitHub Actions will try to find the repository on GitHub.com.
If a user has already created an organization and repository in your enterprise that matches an organization and repository name on GitHub.com, the repository on your enterprise will be used instead of the GitHub.com repository. A malicious user could take advantage of this behavior to run code as part of a workflow.
Enabling automatic access to all GitHub.com actions
Before enabling access to all actions from GitHub.com for your enterprise, you must enable GitHub Connect. For more information, see "Managing GitHub Connect."
-
In the top-right corner of GitHub AE, 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 policies for GitHub Actions in your enterprise."
Automatic retirement of namespaces for actions accessed on GitHub.com
When you enable GitHub Connect, users see no change in behavior for existing workflows because GitHub Actions searches your enterprise 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 enterprise. When an action on GitHub.com is used for the first time, that namespace is retired in your enterprise. 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 enterprise with the same name, first you need to make the namespace for that organization and repository available.
-
From an administrative account on GitHub AE, in the upper-right corner of any page, click .
-
If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.
-
In the left sidebar, under Site admin click Retired namespaces.
-
To the right of the namespace that you want use in your enterprise, 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.