Update all files to use {% data %} (#15253)
* 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
This commit is contained in:
Jason Etcovitch
@@ -1,26 +1,26 @@
|
||||
---
|
||||
title: Manually syncing actions from GitHub.com
|
||||
intro: 'For users that need access to actions from {{ site.data.variables.product.prodname_dotcom_the_website }}, you can sync specific actions to your {{ site.data.variables.product.prodname_ghe_server }} instance.'
|
||||
intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your {% data variables.product.prodname_ghe_server %} instance.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
|
||||
versions:
|
||||
enterprise-server: '>=2.22'
|
||||
---
|
||||
|
||||
{{ site.data.reusables.actions.enterprise-beta }}
|
||||
{{ site.data.reusables.actions.enterprise-github-hosted-runners }}
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
{{ site.data.reusables.actions.enterprise-no-internet-actions }}
|
||||
{% data reusables.actions.enterprise-no-internet-actions %}
|
||||
|
||||
To make specific actions from {{ site.data.variables.product.prodname_dotcom_the_website }} available to use in workflows, you can use {{ site.data.variables.product.company_short }}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync action repositories from {{ site.data.variables.product.prodname_dotcom_the_website }} to your enterprise instance. For other ways of accessing actions from {{ site.data.variables.product.prodname_dotcom_the_website }}, see "[About using {{ site.data.variables.product.prodname_dotcom_the_website }} actions on {{ site.data.variables.product.prodname_ghe_server }}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)."
|
||||
To make specific actions from {% data variables.product.prodname_dotcom_the_website %} available to use in workflows, you can use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)."
|
||||
|
||||
### About the `actions-sync` tool
|
||||
|
||||
The `actions-sync` tool must be run on a machine that can access the {{ site.data.variables.product.prodname_dotcom_the_website }} API and your {{ site.data.variables.product.prodname_ghe_server }} instance's API. The machine doesn't need to be connected to both at the same time.
|
||||
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.prodname_ghe_server %} instance's API. The machine doesn't need to be connected to both at the same time.
|
||||
|
||||
If your machine has access to both systems at the same time, you can do the sync with a single `actions-sync sync` command. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands.
|
||||
|
||||
The `actions-sync` tool can only download actions from {{ site.data.variables.product.prodname_dotcom_the_website }} that are stored in public repositories.
|
||||
The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories.
|
||||
|
||||
### Требования
|
||||
|
||||
@@ -29,11 +29,11 @@ The `actions-sync` tool can only download actions from {{ site.data.variables.pr
|
||||
|
||||
### Example: Using the `actions-sync` tool
|
||||
|
||||
This example demonstrates using the `actions-sync` tool to sync an individual action from {{ site.data.variables.product.prodname_dotcom_the_website }} to an enterprise instance.
|
||||
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.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {{ site.data.variables.product.prodname_dotcom_the_website }} API and your {{ site.data.variables.product.prodname_ghe_server }} instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
|
||||
**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.prodname_ghe_server %} instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -56,7 +56,7 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
|
||||
* `--destination-url`: The URL of the destination enterprise instance.
|
||||
* `--repo-name`: The action repository to sync. This takes the format of `owner/repository:destination_owner/destination_repository`.
|
||||
|
||||
* The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination {{ site.data.variables.product.prodname_ghe_server }} instance. You must create the organization named `synced-actions` on your enterprise instance before running the above command.
|
||||
* The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination {% data variables.product.prodname_ghe_server %} instance. You must create the organization named `synced-actions` on your enterprise instance before running the above command.
|
||||
* If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise instance. Before running the command, you must create a new organization on your instance that matches the owner name of the action. Consider using a central organization to store the synced actions on your instance, as this means you will not need to create multiple new organizations if you sync actions from different owners.
|
||||
* You can sync multiple actions by replacing the `--repo-name` parameter with `--repo-name-list` or `--repo-name-list-file`. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync).
|
||||
1. After the action repository is created on your enterprise instance, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above:
|
||||
|
||||
Reference in New Issue
Block a user