caaee7a124
* Add back changes from prior to purge * Manually fix some invalid Liquid * Updoot render-content * Improve test messages to show correct output * Run el scripto * Pass the remaining test
3.3 KiB
title, intro, redirect_from, versions
| title | intro | redirect_from | versions | |||
|---|---|---|---|---|---|---|
| About using GitHub.com actions on GitHub Enterprise Server | {% data variables.product.prodname_ghe_server %} 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 %}. |
|
|
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
{% data reusables.actions.enterprise-no-internet-actions %}
Official actions bundled with {% data variables.product.prodname_ghe_server %}
Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_server %} 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://{% data variables.product.product_url %}/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 %}
Note: When using setup actions (such as actions/setup-LANGUAGE) on {% data variables.product.prodname_ghe_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."
{% endnote %}
Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
If users on your enterprise instance need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, 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 {% data variables.product.prodname_dotcom_the_website %}."
Alternatively, you can enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %} by connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} using {% data variables.product.prodname_github_connect %}. For more information, see "Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}".