updating content files
This commit is contained in:
Grace Park
@@ -22,7 +22,7 @@ topics:
|
||||
|
||||
{% data reusables.actions.enterprise-no-internet-actions %}
|
||||
|
||||
### Official actions bundled with your enterprise instance
|
||||
## Official actions bundled with your enterprise instance
|
||||
|
||||
Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}.
|
||||
|
||||
@@ -36,7 +36,7 @@ Each action is a repository in the `actions` organization, and each action repos
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
|
||||
## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
If users in your enterprise 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.
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ By default, {% data variables.product.prodname_actions %} workflows on {% data v
|
||||
|
||||
To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
|
||||
|
||||
### Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
|
||||
## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
|
||||
|
||||
Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)."
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ The recommended approach of enabling access to actions from {% data variables.pr
|
||||
|
||||
However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise.
|
||||
|
||||
### About the `actions-sync` tool
|
||||
## About the `actions-sync` tool
|
||||
|
||||
The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.product_name %} instance's API. The machine doesn't need to be connected to both at the same time.
|
||||
|
||||
@@ -28,7 +28,7 @@ If your machine has access to both systems at the same time, you can do the sync
|
||||
|
||||
The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories.
|
||||
|
||||
### Prerequisites
|
||||
## Prerequisites
|
||||
|
||||
* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
|
||||
* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
@@ -46,7 +46,7 @@ The `actions-sync` tool can only download actions from {% data variables.product
|
||||
ghe-org-admin-promote -u <em>USERNAME</em> -o actions
|
||||
```
|
||||
|
||||
### Example: Using the `actions-sync` tool
|
||||
## Example: Using the `actions-sync` tool
|
||||
|
||||
This example demonstrates using the `actions-sync` tool to sync an individual action from {% data variables.product.prodname_dotcom_the_website %} to an enterprise instance.
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ topics:
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
{% data reusables.actions.ae-beta %}
|
||||
|
||||
### About the included setup actions and the runner tool cache
|
||||
## About the included setup actions and the runner tool cache
|
||||
|
||||
{% data reusables.actions.enterprise-no-internet-actions %}
|
||||
|
||||
@@ -30,13 +30,13 @@ You can populate the runner tool cache by running a {% data variables.product.pr
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Prerequisites
|
||||
## Prerequisites
|
||||
|
||||
* Determine which development environments your self-hosted runners will need. The following example demonstrates how to populate a tool cache for the `setup-node` action, using Node.js versions 10 and 12.
|
||||
* Access to a repository on {% data variables.product.prodname_dotcom_the_website %} that you can use to run a workflow.
|
||||
* Access to your self-hosted runner's file system to populate the tool cache folder.
|
||||
|
||||
### Populating the tool cache for a self-hosted runner
|
||||
## Populating the tool cache for a self-hosted runner
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repository that you can use to run a {% data variables.product.prodname_actions %} workflow.
|
||||
1. Create a new workflow file in the repository's `.github/workflows` folder that uploads an artifact containing the {% data variables.product.prodname_dotcom %}-hosted runner's tool cache.
|
||||
|
||||
@@ -17,11 +17,11 @@ Your enterprise instance includes a number of built-in actions that you can use
|
||||
|
||||
These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections.
|
||||
|
||||
### Using `actions-sync` to update the bundled actions
|
||||
## Using `actions-sync` to update the bundled actions
|
||||
|
||||
To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
|
||||
|
||||
### Using {% data variables.product.prodname_github_connect %} to access the latest actions
|
||||
## Using {% data variables.product.prodname_github_connect %} to access the latest actions
|
||||
|
||||
You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
|
||||
|
||||
|
||||
Reference in New Issue
Block a user