Skip to main content

About using actions in your enterprise

GitHub Enterprise Server includes most GitHub-authored actions, and has options for enabling access to other actions from GitHub.com and GitHub Marketplace.

Remarque : Les exécuteurs hébergés sur GitHub ne sont pas pris en charge sur GitHub Enterprise Server. Vous pouvez voir plus d’informations sur le support futur planifié dans la GitHub public roadmap.

About actions on GitHub Enterprise Server

GitHub Actions workflows can use actions, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the GitHub community.

GitHub Actions sur GitHub Enterprise Server est conçu pour fonctionner dans des environnements n’ayant pas un accès à Internet complet. Par défaut, les workflows ne peuvent pas utiliser les actions de GitHub.com et de GitHub Marketplace. You can restrict your developers to using actions that are stored on votre instance GitHub Enterprise Server, which includes most official GitHub-authored actions, as well as any actions your developers create. Alternatively, to allow your developers to benefit from the full ecosystem of actions built by industry leaders and the open source community, you can configure access to other actions from GitHub.com.

We recommend allowing automatic access to all actions from GitHub.com. However, this does require GitHub Enterprise Server to make outbound connections to GitHub.com. If you don't want to allow these connections, or you want to have greater control over which actions are used on your enterprise, you can manually sync specific actions from GitHub.com.

Official actions bundled with your enterprise instance

La plupart des actions officielles créées par GitHub sont automatiquement groupées avec GitHub Enterprise Server, et capturées à un moment donné à partir de GitHub Marketplace.

The bundled official actions include the following, among others.

  • actions/checkout
  • actions/upload-artifact
  • actions/download-artifact
  • actions/labeler
  • Various actions/setup- actions

To see all the official actions included on your enterprise instance, browse to the actions organization on your instance: https://HOSTNAME/actions.

There is no connection required between votre instance GitHub Enterprise Server and GitHub.com to use these 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. For information on how to update the bundled official actions, see "Using the latest version of the official bundled actions."

Notes:

  • When using setup actions (such as actions/setup-LANGUAGE) on GitHub Enterprise Server 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."
  • When GitHub Enterprise Server is updated, bundled actions are automatically replaced with default versions in the upgrade package.

Configuring access to actions on GitHub.com

Dans votre entreprise, si les utilisateurs ont besoin d’accéder à d’autres actions de GitHub.com ou GitHub Marketplace, il existe quelques options de configuration.

The recommended approach is to enable automatic access to all actions from GitHub.com. You can do this by using GitHub Connect to integrate GitHub Enterprise Server with GitHub Enterprise Cloud. For more information, see "Enabling automatic access to GitHub.com actions using GitHub Connect".

Note: Before you can configure access to actions on GitHub.com, you must configure votre instance GitHub Enterprise Server to use GitHub Actions. For more information, see "Getting started with GitHub Actions for GitHub Enterprise Server."

Pour utiliser des actions à partir de GitHub.com, votre instance GitHub Enterprise Server et vos exécuteurs auto-hébergés doivent être en mesure d’établir des connexions sortantes à GitHub.com. Aucune connexion entrante à partir de GitHub.com n’est obligatoire. Pour plus d’informations, consultez Pour plus d’informations, consultez « À propos des exécuteurs auto-hébergés ».

Après avoir activé GitHub Connect, vous pouvez utiliser des stratégies pour restreindre les actions publiques utilisables dans les dépôts de votre entreprise. Pour plus d’informations, consultez « Enforcing policies for GitHub Actions in your enterprise ».

Alternatively, if you want stricter control over which actions are allowed in your enterprise, or you do not want to allow outbound connections to GitHub.com, 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."