--- title: About using GitHub.com actions on GitHub Enterprise Server intro: '{{ site.data.variables.product.prodname_ghe_server }} includes most {{ site.data.variables.product.prodname_dotcom }}-authored actions, and has options for enabling access to other actions from {{ site.data.variables.product.prodname_dotcom_the_website }} and {{ site.data.variables.product.prodname_marketplace }}.' redirect_from: - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server versions: enterprise-server: '>=2.22' --- {{ site.data.reusables.actions.enterprise-beta }} {{ site.data.reusables.actions.enterprise-github-hosted-runners }} {{ site.data.reusables.actions.enterprise-no-internet-actions }} ### Official actions bundled with {{ site.data.variables.product.prodname_ghe_server }} Most official {{ site.data.variables.product.prodname_dotcom }}-authored actions are automatically bundled with {{ site.data.variables.product.prodname_ghe_server }}, and are captured at a point in time from {{ site.data.variables.product.prodname_marketplace }}. When your {{ site.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://{{ site.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 {{ site.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](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." {% endnote %} ### Configuring access to actions on {{ site.data.variables.product.prodname_dotcom_the_website }} If users on your enterprise instance need access to other actions from {{ site.data.variables.product.prodname_dotcom_the_website }} or {{ site.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 {{ site.data.variables.product.prodname_dotcom_the_website }}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." Alternatively, you can enable automatic access to all actions from {{ site.data.variables.product.prodname_dotcom_the_website }} by connecting {{ site.data.variables.product.prodname_ghe_server }} to {{ site.data.variables.product.prodname_ghe_cloud }} using {{ site.data.variables.product.prodname_github_connect }}. For more information, see "[Enabling automatic access to {{ site.data.variables.product.prodname_dotcom_the_website }} actions using {{ site.data.variables.product.prodname_github_connect }}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".