Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

About using actions on GitHub Enterprise Server

Servidor de GitHub Enterprise includes most GitHub-authored actions, and has options for enabling access to other actions from and Mercado GitHub.

En este artículo

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.

GitHub Actions on Servidor de GitHub Enterprise is designed to work in environments without internet access. By default, workflows cannot use actions from and Mercado GitHub.

Official actions bundled with Servidor de GitHub Enterprise

Most official GitHub-authored actions are automatically bundled with Servidor de GitHub Enterprise, and are captured at a point in time from Mercado GitHub. When your Servidor de GitHub Enterprise instance receives updates, the bundled official actions are also updated.

The bundled official actions include actions/checkout, actions/upload-artifact, actions/download-artifact, actions/labeler, and various actions/setup- actions, among others. To see all the official actions included on your enterprise instance, browse to the actions organization on your instance: https://[hostname]/actions.

Each action is a repository in the actions organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action.

Note: When using setup actions (such as actions/setup-LANGUAGE) on Servidor de GitHub Enterprise with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "Setting up the tool cache on self-hosted runners without internet access."

Configuring access to actions on

If users on your enterprise instance need access to other actions from or Mercado GitHub, there are a few configuration options.

You can manually download and sync actions onto your enterprise instance using the actions-sync tool. For more information, see "Manually syncing actions from"

Alternatively, you can enable automatic access to all actions from by connecting Servidor de GitHub Enterprise to GitHub Enterprise Cloud using GitHub Connect. For more information, see "Enabling automatic access to actions using GitHub Connect".

¿Te ayudó este documento?

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

O, learn how to contribute.