Skip to main content
� 

� 

This version of GitHub Enterprise was discontinued on 2022-10-12. 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. 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:

  1. In the top-right corner of GitHub Enterprise Server, click your profile photo, then click Enterprise settings. "Enterprise settings" in drop-down menu for profile photo on GitHub Enterprise Server

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

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

  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 GitHub Actions policies for your enterprise."