Esta versión de GitHub Enterprise se discontinuó el 2021-09-23. No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener un mejor desempeño, más seguridad y nuevas características, actualiza a la última versión de GitHub Enterprise. Para obtener ayuda con la actualización, contacta al soporte de GitHub Enterprise.

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

Note: GitHub Actions support on Servidor de GitHub Enterprise 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "Enabling GitHub Actions and configuring storage."

Note: GitHub-hosted runners are not currently supported on Servidor de GitHub Enterprise. You can see more information about planned future support on the Itinerario público de GitHub.

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, 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 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"

Using GitHub Connect to access the latest actions

You can use GitHub Connect to allow GitHub Enterprise to use actions from For more information, see "Enabling automatic access to 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

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