Using the latest version of the official bundled actions

You can update the actions that are bundled with your enterprise, or use actions directly from GitHub.com.

In this article

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.

Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "Official actions bundled with your enterprise instance."

These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the actions-sync tool to update these actions, or you can configure GitHub Connect to allow access to the latest actions on GitHub.com. These options are described in the following sections.

Using actions-sync to update the bundled actions

To update the bundled actions, you can use the actions-sync tool to update the snapshot. For more information on using actions-sync, see "Manually syncing actions from GitHub.com."

Using GitHub Connect to access the latest actions

You can use GitHub Connect to allow GitHub Enterprise Server to use actions from GitHub.com. For more information, see "Enabling automatic access to GitHub.com actions using GitHub Connect."

Once GitHub Connect is configured, you can use the latest version of an action by deleting its local repository in the actions organization on your instance. For example, if your enterprise instance is using the actions/checkout@v1 action, and you need to use actions/checkout@v2 which isn't available on your enterprise instance, perform the following steps to be able to use the latest checkout action from GitHub.com:

  1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the checkout repository, use the ghe-org-admin-promote command to promote a user to be an owner of the bundled actions organization. For more information, see "Accessing the administrative shell (SSH)" and "ghe-org-admin-promote." For example:

    $ ghe-org-admin-promote -u octocat -o actions
     Do you want to give organization admin privileges for actions to octocat? (y/N) y
     Making octocat an admin of actions
      --> Adding octocat as an admin of actions
      --> octocat is now an admin of the actions organization
      --> Done.
  2. On your GitHub Enterprise Server instance, delete the checkout repository within the actions organization. For information on how to delete a repository, see "Deleting a repository ."

  3. It is recommended that you leave the actions organization once you no longer require administrative access. For more information, see "Removing yourself from an organization ."

  4. Configure your workflow's YAML to use actions/checkout@v2.

  5. Each time your workflow runs, the runner will use the v2 version of actions/checkout from GitHub.com.

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.