Skip to main content
All products
Enterprise administrators

This version of GitHub Enterprise was discontinued on 2023-07-06. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Enabling automatic access to github.com actions using GitHub Connect

In this article

To allow GitHub Actions in your enterprise to use actions from github.com, you can connect your enterprise instance to GitHub Enterprise Cloud.

Who can use this feature

Enterprise owners can enable access to all github.com actions.

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 automatic access to github.com actions

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.

To use actions from github.com, both your GitHub Enterprise Server instance and 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 GitHub Enterprise Server instance. If the repository does not exist on your GitHub Enterprise Server instance, 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. For more information, see "Automatic retirement of namespaces for actions accessed on github.com."

Enabling automatic access to all github.com actions

Before enabling access to all actions from github.com for your enterprise, you must:

  1. In the top-right corner of GitHub Enterprise Server, click your profile photo, then click Enterprise settings.

    Screenshot of the drop-down menu that appears when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is highlighted in a dark orange outline.

  2. In the enterprise account sidebar, click GitHub Connect.

  3. Under "Users can utilize actions from github.com in workflow runs", use the drop-down menu and select Enabled.

  4. 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 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.

  1. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .

  2. If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.

  3. In the left sidebar, under Site admin click Retired namespaces.

  4. To the right of the namespace that you want use in your GitHub Enterprise Server instance, click Unretire.

  5. 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.