4.3 KiB
title, intro, redirect_from, versions, type, topics, shortTitle
| title | intro | redirect_from | versions | type | topics | shortTitle | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| About using actions in your enterprise | {% data variables.product.product_name %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}. |
|
|
overview |
|
Add actions in your enterprise |
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
About actions on {% data variables.product.product_name %}
{% data variables.product.prodname_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 {% data variables.product.prodname_dotcom %} community.
{% data reusables.actions.enterprise-no-internet-actions %}
Official actions bundled with your enterprise instance
{% data reusables.actions.actions-bundled-with-ghes %}
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. For information on how to update the bundled official actions, see "Using the latest version of the official bundled actions."
{% note %}
Note: When using setup actions (such as actions/setup-LANGUAGE) on {% data variables.product.product_name %} 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."
{% endnote %}
Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
{% ifversion ghes %} Before you can configure access to actions on {% data variables.product.prodname_dotcom_the_website %}, you must configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server." {% endif %}
{% data reusables.actions.access-actions-on-dotcom %}
The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}".
{% data reusables.actions.enterprise-limit-actions-use %}
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 {% data variables.product.prodname_dotcom_the_website %}."