Learning path to help enterprises adopt Actions (#22513)

content/actions/guides.md

@@ -13,6 +13,7 @@ learningTracks:
   - continuous_integration
   - continuous_deployment
   - deploy_to_the_cloud
+  - '{% ifversion ghec or ghes or ghae %}adopting_github_actions_for_your_enterprise{% endif %}'
   - hosting_your_own_runners
   - create_actions
 includeGuides:

content/actions/learn-github-actions/understanding-github-actions.md

@@ -23,7 +23,7 @@ topics:
 
 ## Overview
 
-{% data variables.product.prodname_actions %} help you automate tasks within your software development life cycle. {% data variables.product.prodname_actions %} are event-driven, meaning that you can run a series of commands after a specified event has occurred. For example, every time someone creates a pull request for a repository, you can automatically run a command that executes a software testing script.
+{% data reusables.actions.about-actions %} {% data variables.product.prodname_actions %} are event-driven, meaning that you can run a series of commands after a specified event has occurred. For example, every time someone creates a pull request for a repository, you can automatically run a command that executes a software testing script.
 
 This diagram demonstrates how you can use {% data variables.product.prodname_actions %} to automatically run your software testing scripts. An event automatically triggers the _workflow_, which contains a _job_. The job then uses _steps_ to control the order in which _actions_ are run. These actions are the commands that automate your software testing.
 
@@ -59,7 +59,7 @@ _Actions_ are standalone commands that are combined into _steps_ to create a _jo
 
 {% ifversion ghae %}A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. For {% data variables.product.prodname_ghe_managed %}, you can use the security hardened {% data variables.actions.hosted_runner %}s which are bundled with your instance in the cloud. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. {% data variables.actions.hosted_runner %}s run each workflow job in a fresh virtual environment. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)."
 {% else %}
-A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS, and each job in a workflow runs in a fresh virtual environment.  For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+{% data reusables.actions.about-runners %} A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS, and each job in a workflow runs in a fresh virtual environment.  For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
 {% endif %}
 
 ## Create an example workflow

content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md

@@ -6,7 +6,6 @@ versions:
 topics:
   - Enterprise
 children:
-  - /getting-started-with-github-actions-for-github-enterprise-server
   - /enabling-github-actions-with-azure-blob-storage
   - /enabling-github-actions-with-amazon-s3-storage
   - /enabling-github-actions-with-minio-gateway-for-nas-storage

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md

@@ -1,7 +1,7 @@
 ---
 title: Getting started with GitHub Actions for GitHub AE
-shortTitle: Getting started with GitHub Actions
+shortTitle: Get started
-intro: 'Learn configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.'
+intro: 'Learn about configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   ghae: '*'
@@ -11,12 +11,21 @@ topics:
   - Enterprise
 redirect_from:
   - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+  - /admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae
 ---
 
 {% data reusables.actions.ae-beta %}
 
+## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}
+
 This article explains how site administrators can configure {% data variables.product.prodname_ghe_managed %} to use {% data variables.product.prodname_actions %}.
 
+{% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_managed %} by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you need to manage access permissions for {% data variables.product.prodname_actions %} and add runners to run workflows.
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
 ## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise
 
 You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
@@ -31,7 +40,4 @@ You can use policies to manage access to {% data variables.product.prodname_acti
 
 To run {% data variables.product.prodname_actions %} workflows, you need to add runners. You can add runners at the enterprise, organization, or repository levels. For more information, see  "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)."
 
-
+{% data reusables.actions.general-security-hardening %}
-## General security hardening for {% data variables.product.prodname_actions %} 
-
-If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)."

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md

@@ -0,0 +1,34 @@
+---
+title: Getting started with GitHub Actions for GitHub Enterprise Cloud
+shortTitle: Get started
+intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %}.'
+permissions: 'Enterprise owners can configure {% data variables.product.prodname_actions %}.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+---
+
+## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %}
+
+{% data variables.product.prodname_actions %} is enabled for your enterprise by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you can manage the policies that control how enterprise members use {% data variables.product.prodname_actions %} and optionally add self-hosted runners to run workflows.
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+## Managing policies for {% data variables.product.prodname_actions %}
+
+You can use policies to control how enterprise members use {% data variables.product.prodname_actions %}. For example, you can restrict which actions are allowed and configure artifact and log retention. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+
+## Adding runners
+
+To run {% data variables.product.prodname_actions %} workflows, you need to use runners. {% data reusables.actions.about-runners %} If you use {% data variables.product.company_short %}-hosted runners, you will be be billed based on consumption after exhausting the minutes included in {% data variables.product.product_name %}, while self-hosted runners are free. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+
+For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+
+If you choose self-hosted runners, you can add runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)"
+
+{% data reusables.actions.general-security-hardening %}

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md

@@ -1,12 +1,13 @@
 ---
 title: Getting started with GitHub Actions for GitHub Enterprise Server
-shortTitle: Getting started with GitHub Actions
+shortTitle: Get started
 intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 redirect_from:
   - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage
   - /admin/github-actions/enabling-github-actions-and-configuring-storage
   - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server
 versions:
   ghes: '*'
 type: how_to
@@ -18,11 +19,15 @@ topics:
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% ifversion ghes %}
+## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}
 
-This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies.
+This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. 
 
-{% endif %}
+{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
 
 ## Review hardware considerations
 
@@ -137,9 +142,7 @@ You can control which actions your users are allowed to use in your enterprise.
 
 For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
-## General security hardening for {% data variables.product.prodname_actions %} 
+{% data reusables.actions.general-security-hardening %}
-
-If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)."
 
 {% endif %}
 

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md

@@ -0,0 +1,19 @@
+---
+title: Getting started with GitHub Actions for your enterprise
+intro: "Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise."
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+  - Actions
+children:
+  - /introducing-github-actions-to-your-enterprise
+  - /migrating-your-enterprise-to-github-actions
+  - /getting-started-with-github-actions-for-github-enterprise-cloud
+  - /getting-started-with-github-actions-for-github-enterprise-server
+  - /getting-started-with-github-actions-for-github-ae
+shortTitle: Get started
+---
+

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md

@@ -0,0 +1,124 @@
+---
+title: Introducing GitHub Actions to your enterprise
+shortTitle: Introduce Actions
+intro: "You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise."
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+---
+
+## About {% data variables.product.prodname_actions %} for enterprises
+
+{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information about the basics of {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
+
+![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png)
+
+Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs.
+
+## Governance and compliance
+
+Your should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations. 
+
+Determine which actions your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."
+
+Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions that were not created by {% data variables.product.company_short %}. You can configure the actions that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions, you can limit allowed actions to those created by verified creators or a list of specific actions. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)", and "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)."
+
+![Screenshot of {% data variables.product.prodname_actions %} policies](/assets/images/help/organizations/enterprise-actions-policy.png)
+
+{% ifversion ghec or ghae-issue-4757-and-5856 %}
+Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)."
+{% endif %}
+
+You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %}
+
+![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+
+## Security
+
+You should plan your approach to security hardening for {% data variables.product.prodname_actions %}.
+
+### Security hardening individual workflows and repositories
+
+Make a plan to enforce good security practices for people using {% data variables.product.prodname_actions %} features within your enterprise. For more information about these practices, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions)."
+
+You can also encourage reuse of workflows that have already been evaluated for security. For more information, see "[Innersourcing](#innersourcing)."
+
+### Securing access to secrets and deployment resources
+
+You should plan where you'll store your secrets. We recommend storing secrets in {% data variables.product.prodname_dotcom %}, but you might choose to store secrets in a cloud provider.
+
+In {% data variables.product.prodname_dotcom %}, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+![Screenshot of a list of secrets](/assets/images/help/settings/actions-org-secrets-list.png)
+
+You should consider adding manual approval protection for sensitive environments, so that workflows must be approved before getting access to the environments' secrets. For more information, see "[Using environments for deployments](/actions/deployment/targeting-different-environments/using-environments-for-deployment)."
+
+### Security considerations for third-party actions
+
+There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that enourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)."
+
+## Innersourcing
+
+Think about how your enterprise can use features of {% data variables.product.prodname_actions %} to innersource workflows. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see [An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/) in {% data variables.product.company_short %} Resources.
+
+{% ifversion ghec or ghes > 3.3 or ghae-issue-4757 %}
+With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+{% endif %}
+
+To provide a starting place for developers building new workflows, you can use workflow templates. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+
+Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)."
+
+## Managing resources
+
+You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
+
+### Runners
+
+{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
+
+{% ifversion ghec %}If you are using self-hosted runners, you have to decide whether you want to use physical machines, virtual machines, or containers.{% else %}Decide whether you want to use physical machines, virtual machines, or containers for your self-hosted runners.{% endif %} Physical machines will retain remnants of previous jobs, and so will virtual machines unless you use a fresh image for each job or clean up the machines after each job run. If you choose containers, you should be aware that the runner auto-updating will shut down the container, which can cause workflows to fail. You should come up with a solution for this by preventing auto-updates or skipping the command to kill the container.
+
+You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
+
+{% ifversion ghec or ghes %}
+You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+{% endif %}
+
+Finally, you should consider security hardening for self-hosted runners. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
+
+### Storage
+
+{% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)."
+
+![Screenshot of artifact](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png)
+
+{% ifversion ghes %}
+You must configure external blob storage for these artifacts. Decide which supported storage provider your enterprise will use. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)."
+{% endif %}
+
+{% data reusables.github-actions.artifact-log-retention-statement %}
+
+If you want to retain logs and artifacts longer than the upper limit you can configure in {% data variables.product.product_name %}, you'll have to plan how to export and store the data.
+
+{% ifversion ghec %}
+Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+{% endif %}
+
+## Tracking usage
+
+You should consider making a plan to track your enterprise's usage of {% data variables.product.prodname_actions %}, such as how often workflows are running, how many of those runs are passing and failing, and which repositories are using which workflows.
+
+{% ifversion ghec %}
+You can see basic details of storage and data transfer usage of {% data variables.product.prodname_actions %} for each organization in your enterprise via your billing settings. For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-enterprise-account)."
+
+For more detailed usage data, you{% else %}You{% endif %} can use webhooks to subscribe to information about workflow jobs and workflow runs. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)."
+
+Make a plan for how your enterprise can pass the information from these webhooks into a data archiving system. You can consider using "CEDAR.GitHub.Collector", an open source tool that collects and processes webhook data from {% data variables.product.prodname_dotcom %}. For more information, see the [`Microsoft/CEDAR.GitHub.Collector` repository](https://github.com/microsoft/CEDAR.GitHub.Collector/).
+
+You should also plan how you'll enable your teams to get the data they need from your archiving system.

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md

@@ -0,0 +1,87 @@
+---
+title: Migrating your enterprise to GitHub Actions
+shortTitle: Migrate to Actions
+intro: "Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider."
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+---
+
+## About enterprise migrations to {% data variables.product.prodname_actions %}
+
+To migrate your enterprise to {% data variables.product.prodname_actions %} from an existing system, you can plan the migration, complete the migration, and retire existing systems.
+
+This guide addresses specific considerations for migrations. For additional information about introducing {% data variables.product.prodname_actions %} to your enterprise, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)."
+
+## Planning your migration
+
+Before you begin migrating your enterprise to {% data variables.product.prodname_actions %}, you should identify which workflows will be migrated and how those migrations will affect your teams, then plan how and when you will complete the migrations.
+
+### Leveraging migration specialists
+
+{% data variables.product.company_short %} can help with your migration, and you may also benefit from purchasing {% data variables.product.prodname_professional_services %}. For more information, contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}.
+
+### Identifying and inventorying migration targets
+
+Before you can migrate to {% data variables.product.prodname_actions %}, you need to have a complete understanding of the workflows being used by your enterprise in your existing system.
+
+First, create an inventory of the existing build and release workflows within your enterprise, gathering information about which workflows are being actively used and need to migrated and which can be left behind.
+
+Next, learn the differences between your current provider and {% data variables.product.prodname_actions %}. This will help you assess any difficulties in migrating each workflow, and where your enterprise might experience differences in features. For more information, see "[Migrating to {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)."
+
+With this information, you'll be able to determine which workflows you can and want to migrate to {% data variables.product.prodname_actions %}.
+
+### Determine team impacts from migrations
+
+When you change the tools being used within your enterprise, you influence how your team works. You'll need to consider how moving a workflow from your existing systems to {% data variables.product.prodname_actions %} will affect your developers' day-to-day work.
+
+Identify any processes, integrations, and third-party tools that will be affected by your migration, and make a plan for any updates you'll need to make.
+
+Consider how the migration may affect your compliance concerns. For example, will your existing credential scanning and security analysis tools work with {% data variables.product.prodname_actions %}, or will you need to use new tools?
+
+Identify the gates and checks in your existing system and verify that you can implement them with {% data variables.product.prodname_actions %}.
+
+### Identifying and validating migration tools
+
+Automated migration tools can translate your enterprise's workflows from the existing system's syntax to the syntax required by {% data variables.product.prodname_actions %}. Identify third-party tooling or contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %} to ask about tools that {% data variables.product.company_short %} can provide.
+
+After you've identified a tool to automate your migrations, validate the tool by running the tool on some test workflows and verifying that the results are as expected.
+
+Automated tooling should be able to migrate the majority of your workflows, but you'll likely need to manually rewrite at least a small percentage. Estimate the amount of manual work you'll need to complete.
+
+### Deciding on a migration approach
+
+Determine the migration approach that will work best for your enterprise. Smaller teams may be able to migrate all their workflows at once, with a "rip-and-replace" approach. For larger enterprises, an iterative approach may be more realistic. You can choose to have a central body manage the entire migration or you can ask individual teams to self serve by migrating their own workflows.
+
+We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too.
+
+Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired. 
+
+Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable.
+
+### Defining your migration schedule
+
+After you decide on a migration approach, build a schedule that outlines when each of your teams will migrate their workflows to {% data variables.product.prodname_actions %}.
+
+First, decide the date you'd like your migration to be complete. For example, you can plan to complete your migration by the time your contract with your current provider ends.
+
+Then, work with your teams to create a schedule that meets your deadline without sacrificing their team goals. Look at your business's cadence and the workload of each individual team you're asking to migrate. Coordinate with each team to understand their delivery schedules and create a plan that allows the team to migrate their workflows at a time that won't impact their ability to deliver.
+
+## Migrating to {% data variables.product.prodname_actions %}
+
+When you're ready to start your migration, translate your existing workflows to {% data variables.product.prodname_actions %} using the automated tooling and manual rewriting you planned for above.
+
+You may also want to maintain old build artifacts from your existing system, perhaps by writing a scripted process to archive the artifacts.
+
+## Retiring existing systems
+
+After your migration is complete, you can think about retiring your existing system.
+
+You may want to run both systems side-by-side for some period of time, while you verify that your {% data variables.product.prodname_actions %} configuration is stable, with no degradation of experience for developers.
+
+Eventually, decommission and shut off the old systems, and ensure that no one within your enterprise can turn the old systems back on.

content/admin/github-actions/index.md

@@ -4,11 +4,13 @@ intro: 'Enable {% data variables.product.prodname_actions %} on {% ifversion gha
 redirect_from:
   - /enterprise/admin/github-actions
 versions:
+  ghec: '*'
   ghes: '*'
   ghae: '*'
 topics:
   - Enterprise
 children:
+  - /getting-started-with-github-actions-for-your-enterprise
   - /using-github-actions-in-github-ae
   - /enabling-github-actions-for-github-enterprise-server
   - /managing-access-to-actions-from-githubcom

content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md

@@ -26,7 +26,7 @@ shortTitle: Add actions in your enterprise
 
 ## 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 %}.
+{% 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: <code>https://<em>HOSTNAME</em>/actions</code>.
 
@@ -40,7 +40,7 @@ Each action is a repository in the `actions` organization, and each action repos
 
 ## 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.
+{% 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 %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %}
 

content/admin/github-actions/using-github-actions-in-github-ae/index.md

@@ -4,7 +4,6 @@ intro: 'Learn how to configure {% data variables.product.prodname_actions %} on
 versions:
   ghae: '*'
 children:
-  - /getting-started-with-github-actions-for-github-ae
   - /using-actions-in-github-ae
 shortTitle: Use Actions in GitHub AE
 ---

content/admin/guides.md

@@ -9,14 +9,15 @@ versions:
   ghes: '*'
   ghae: '*'
 learningTracks:
+  - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}'
   - '{% ifversion ghae %}get_started_with_github_ae{% endif %}'
   - '{% ifversion ghes %}deploy_an_instance{% endif %}'
   - '{% ifversion ghes %}upgrade_your_instance{% endif %}'
+  -  adopting_github_actions_for_your_enterprise
   - '{% ifversion ghes %}increase_fault_tolerance{% endif %}'
   - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}'
   - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}'
   - '{% ifversion ghes > 2.22 %}configure_github_advanced_security{% endif %}'
-  - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}'
 includeGuides:
   - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
   - /admin/authentication/changing-authentication-methods

data/learning-tracks/actions.yml

@@ -36,6 +36,17 @@ deploy_to_the_cloud:
     - /actions/deployment/deploying-to-amazon-elastic-container-service
     - /actions/deployment/deploying-to-azure-app-service
     - /actions/deployment/deploying-to-google-kubernetes-engine
+adopting_github_actions_for_your_enterprise:
+  title: 'Adopt GitHub Actions for your enterprise'
+  description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.'
+  guides:
+    - /actions/learn-github-actions/understanding-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae
+    - /actions/security-guides/security-hardening-for-github-actions
 hosting_your_own_runners:
   title: 'Host your own runners'
   description: 'You can create self-hosted runners to run workflows in a highly customizable environment.'

data/learning-tracks/admin.yml

@@ -31,6 +31,18 @@ upgrade_your_instance:
     - /admin/configuration/enabling-and-scheduling-maintenance-mode
     - /admin/enterprise-management/upgrading-github-enterprise-server
 
+adopting_github_actions_for_your_enterprise:
+  title: 'Adopt GitHub Actions for your enterprise'
+  description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.'
+  guides:
+    - /actions/learn-github-actions/understanding-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae
+    - /actions/security-guides/security-hardening-for-github-actions
+
 increase_fault_tolerance:
   title: 'Increase the fault tolerance of your instance'
   description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment."

data/reusables/actions/about-actions.md

@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %} helps you automate tasks within your software development life cycle.

data/reusables/actions/about-runners.md

@@ -0,0 +1 @@
+A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. 

data/reusables/actions/access-actions-on-dotcom.md

@@ -0,0 +1 @@
+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.

data/reusables/actions/actions-bundled-with-ghes.md

@@ -0,0 +1 @@
+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 %}.

data/reusables/actions/general-security-hardening.md

@@ -0,0 +1,3 @@
+## General security hardening for {% data variables.product.prodname_actions %} 
+
+If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)."

data/reusables/actions/introducing-enterprise.md

@@ -0,0 +1 @@
+Before you get started, you should make a plan for how you'll introduce {% data variables.product.prodname_actions %} to your enterprise. For more information, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)."

data/reusables/actions/migrating-enterprise.md

@@ -0,0 +1 @@
+If you're migrating your enterprise to {% data variables.product.prodname_actions %} from another provider, there are additional considerations. For more information, see "[Migrating your enterprise to {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions)."

translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md

@@ -1,149 +0,0 @@
----
-title: Iniciar con GitHub Actions para GitHub Enterprise Server
-shortTitle: Comenzar con Acciones de GitHub
-intro: 'Aprende cómo habilitar y configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} por primera vez.'
-permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
-redirect_from:
-  - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage
-  - /admin/github-actions/enabling-github-actions-and-configuring-storage
-  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
-versions:
-  ghes: '*'
-type: how_to
-topics:
-  - Actions
-  - Enterprise
----
-
-{% data reusables.actions.enterprise-beta %}
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% ifversion ghes %}
-
-Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_server %} para utilizar {% data variables.product.prodname_actions %}. Esto cubre los requisitos de hardware y software, presenta las opciones de almacenamiento y describe las políticas de administración de seguridad.
-
-{% endif %}
-
-## Revisar las consideraciones de hardware
-
-{% ifversion ghes = 3.0 %}
-
-{% note %}
-
-**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."
-
-{% endnote %}
-
-{% endif %}
-
-{%- ifversion ghes < 3.2 %}
-
-Los recursos de CPU y de memoria que están disponibles para {% data variables.product.product_location %} determinan el rendimiento máximo de jobs para {% data variables.product.prodname_actions %}.
-
-Las pruebas internas de {% data variables.product.company_short %} demostraron el siguiente rendimiento máximo para las instancias de {% data variables.product.prodname_ghe_server %} con un rango de CPU y configuraciones de memoria. Puede que vas rendimientos diferentes dependiendo de los niveles generales de actividad en tu instancia.
-
-{%- endif %}
-
-{%- ifversion ghes > 3.1 %}
-
-Los recursos de memoria y CPU que {% data variables.product.product_location %} tiene disponibles determinan la cantidad de jobs que se pueden ejecutar simultáneamente sin pérdida de rendimiento.
-
-La cantidad máxima de ejecución simultánea de jobs sin pérdida de rendimiento depende de factores tales como la duración de los jobs, el uso de artefactos, la cantidad de repositorios ejecutando acciones y qué tanto trabajo adicional sin relación a las acciones ejecuta tu instancia. Las pruebas internas en GitHub demostraron los siguientes objetivos de rendimiento para GitHub Enterprise Server en un rango de configuraciones de memoria y CPU:
-
-{% endif %}
-
-{%- ifversion ghes < 3.2 %}
-
-| vCPU | Memoria | Rendimiento máximo del job |
-|:---- |:------- |:-------------------------- |
-| 4    | 32 GB   | Demo o pruebas leves       |
-| 8    | 64 GB   | 25 puestos de trabajo      |
-| 16   | 160 GB  | 35 puestos de trabajo      |
-| 32   | 256 GB  | 100 puestos de trabajo     |
-
-{%- endif %}
-
-{%- ifversion ghes > 3.1 %}
-
-| vCPU | Memoria | Simultaneidad máxima*   |
-|:---- |:------- |:----------------------- |
-| 32   | 128 GB  | 1500 puestos de trabajo |
-| 64   | 256 GB  | 1900 puestos de trabajo |
-| 96   | 384 GB  | 2200 puestos de trabajo |
-
-*La simultaneidad máxima se midió utilizando repositorios múltiples, una duración de los jobs de aproximadamente 10 minutos y 10 MB de cargas de artefactos. Puedes experimentar rendimientos diferentes dependiendo de los niveles de actividad generales de tu instancia.
-
-{%- endif %}
-
-If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. Para obtener más información acerca de cómo monitorear la capacidad y rendimiento de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Monitorear tu aplicativo](/admin/enterprise-management/monitoring-your-appliance)".
-
-Para obtener más información acerca de los requisitos mínimos de {% data variables.product.product_location %}, consulta las consideraciones de hardware para la plataforma de tu instancia.
-
-- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
-- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
-- [Plataforma de Google Cloud](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
-- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
-- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
-- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
-- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations)
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-## Requisitos de almacenamiento externo
-
-Para habilitar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}, debes tener acceso al almacenamiento externo de blobs.
-
-{% data variables.product.prodname_actions %} utiliza el almacenamiento de blobs para almacenar artefactos que se generan con las ejecuciones de flujo de trabajo, tales como las bitácoras de flujo de trabajo y los artefactos de compilaciones que sube el usuario. La cantidad de almacenamiento requerida dependerá de tu uso de {% data variables.product.prodname_actions %}. Sólo se admite una sola configuración de almacenamiento externo y no puedes utilizar varios proveedores de almacenamiento al mismo tiempo.
-
-{% data variables.product.prodname_actions %} es compatible con estos proveedores de almacenamiento:
-
-* Azure Blob storage
-* Amazon S3
-* S3-compatible MinIO Gateway para NAS
-
-{% note %}
-
-**Nota:** Estos son los únicos proveedores de almacenamiento compatibles con {% data variables.product.company_short %} y sobre los que éste puede proporcionar asistencia. Es muy poco probable que otros proveedores de almacenamiento de S3 compatibles con la API funcionen, debido a las diferencias de la API de S3. [Contáctanos](https://support.github.com/contact) para solicitar soporte para proveedores de almacenamiento adicionales.
-
-{% endnote %}
-
-## Consideraciones de las conexiones
-
-{% data reusables.actions.proxy-considerations %} Para obtener más información sobre cómo utilizar un proxy con {% data variables.product.prodname_ghe_server %}, consulta la sección "[Configurar un servidor proxy saliente](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)".
-
-{% ifversion ghes %}
-
-## Habilitar las {% data variables.product.prodname_actions %} con tu proveedor de almacenamiento
-
-Sigue uno de los procedimientos siguientes para habilitar las {% data variables.product.prodname_actions %} con el proveedor de almacenamiento de tu elección:
-
-* [Habilitar las GitHub Actions con el almacenamiento de Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
-* [Habilitar las GitHub Actions con el almacenamiento de Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
-* [Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
-
-## Administrar los permisos de acceso para {% data variables.product.prodname_actions %} en tu empresa
-
-Puedes utilizar políticas para administrar el acceso a las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
-
-## Agrega ejecutores auto-hospedados
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores auto-hospedados a nivel de empresa, organización o repositorio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
-
-## Administrar qué acciones pueden utilizarse en tu empresa
-
-Puedes controlar las acciones que pueden utilizar tus usuarios en tu empresa. Esto incluye el configurar {% data variables.product.prodname_github_connect %} para el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %}, o sincronizar las acciones de {% data variables.product.prodname_dotcom_the_website %} manualmente.
-
-Para obtener más información, consulta la sección "[Acerca de utilizar las acciones en tu empresa](/admin/github-actions/about-using-actions-in-your-enterprise)".
-
-## Fortalecimiento de seguridad general para las {% data variables.product.prodname_actions %}
-
-Si quieres aprender más acerca de las prácticas de seguridad para {% data variables.product.prodname_actions %}, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)".
-
-{% endif %}
-
-## Nombres reservados
-
-Cuando habilitas las {% data variables.product.prodname_actions %} para tu empresa, se crean dos organizaciones: `github` y `actions`. Si tu empresa utiliza el nombre de organización `github`, `github-org` (o `github-github-org` si `github-org` también se está utilizando) se utilizará en su lugar. Si tu empresa ya utiliza el nombre de organización `actions`, `github-actions` (or `github-actions-org` si `github-actions` también se está utilizando) se utilizará en su lugar. Una vez que se habiliten las acciones, ya no podrás utilizar estos nombres.

translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md

@@ -1,37 +0,0 @@
----
-title: Comenzar con las GitHub Actions para GitHub AE
-shortTitle: Comenzar con Acciones de GitHub
-intro: 'Aprende a configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_managed %}.'
-permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
-versions:
-  ghae: '*'
-type: how_to
-topics:
-  - Actions
-  - Enterprise
-redirect_from:
-  - /admin/github-actions/getting-started-with-github-actions-for-github-ae
----
-
-{% data reusables.actions.ae-beta %}
-
-Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_managed %} para utilizar {% data variables.product.prodname_actions %}.
-
-## Administrar los permisos de acceso para {% data variables.product.prodname_actions %} en tu empresa
-
-Puedes utilizar políticas para administrar el acceso a las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
-
-## Agregar ejecutores
-
-{% note %}
-
-**Nota:** Para agregar {% data variables.actions.hosted_runner %} a {% data variables.product.prodname_ghe_managed %}, tendrás que contactar al soporte de {% data variables.product.prodname_dotcom %}.
-
-{% endnote %}
-
-Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores a nivel de empresa, organización o repositorio. Para obtener más información, consulta la sección "[Acerca de los {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)".
-
-
-## Fortalecimiento de seguridad general para las {% data variables.product.prodname_actions %}
-
-Si quieres aprender más acerca de las prácticas de seguridad para {% data variables.product.prodname_actions %}, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)".

translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md

@@ -1,149 +0,0 @@
----
-title: GitHub Enterprise Server の GitHub Actions を使い始める
-shortTitle: GitHub Actionsを使ってみる
-intro: '{% data variables.product.prodname_ghe_server %} での {% data variables.product.prodname_actions %} の有効化と設定について初めて学びます。'
-permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
-redirect_from:
-  - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage
-  - /admin/github-actions/enabling-github-actions-and-configuring-storage
-  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
-versions:
-  ghes: '*'
-type: how_to
-topics:
-  - Actions
-  - Enterprise
----
-
-{% data reusables.actions.enterprise-beta %}
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% ifversion ghes %}
-
-この記事では、サイト管理者が {% data variables.product.prodname_actions %} を使用するように {% data variables.product.prodname_ghe_server %} を設定する方法について説明しています。 ハードウェアとソフトウェアの要件、ストレージオプション、セキュリティ管理ポリシーについて説明します。
-
-{% endif %}
-
-## ハードウェアについての留意点を確認する
-
-{% ifversion ghes = 3.0 %}
-
-{% note %}
-
-**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. 詳細は「[{% data variables.product.prodname_ghe_server %} をアップグレードする](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)」を参照してください。
-
-{% endnote %}
-
-{% endif %}
-
-{%- ifversion ghes < 3.2 %}
-
-{% data variables.product.product_location %} で使用可能な CPU およびメモリリソースによって、{% data variables.product.prodname_actions %} の最大ジョブスループットが決まります。
-
-{% data variables.product.company_short %} での内部テストでは、さまざまな CPU およびメモリ設定の {% data variables.product.prodname_ghe_server %} インスタンスで次の最大スループットが実証されました。 インスタンスのアクティビティの全体的なレベルに応じて、スループットが異なる場合があります。
-
-{%- endif %}
-
-{%- ifversion ghes > 3.1 %}
-
-The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss.
-
-The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:
-
-{% endif %}
-
-{%- ifversion ghes < 3.2 %}
-
-| vCPUs | メモリ    | 最大ジョブスループット数 |
-|:----- |:------ |:------------ |
-| 4     | 32 GB  | デモまたは軽いテスト   |
-| 8     | 64 GB  | 25ジョブ        |
-| 16    | 160 GB | 35ジョブ        |
-| 32    | 256 GB | 100ジョブ       |
-
-{%- endif %}
-
-{%- ifversion ghes > 3.1 %}
-
-| vCPUs | メモリ    | Maximum Concurrency* |
-|:----- |:------ |:-------------------- |
-| 32    | 128 GB | 1500ジョブ              |
-| 64    | 256 GB | 1900ジョブ              |
-| 96    | 384 GB | 2200ジョブ              |
-
-*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
-
-{%- endif %}
-
-If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. {% data variables.product.prodname_ghe_server %}のキャパシティとパフォーマンスのモニタリングに関する詳しい情報については「[アプラインアンスのモニタリング](/admin/enterprise-management/monitoring-your-appliance)」を参照してください。
-
-{% data variables.product.product_location %} の最小ハードウェア要件の詳細については、インスタンスのプラットフォームのハードウェアに関する考慮事項を参照してください。
-
-- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
-- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
-- [Google Cloud Plafform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
-- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
-- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
-- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %}
-- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-## 外部ストレージの要件
-
-{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効にするには、外部 Blob ストレージにアクセスできる必要があります。
-
-{% data variables.product.prodname_actions %} は、blob ストレージを使用して、ワークフローログやユーザがアップロードしたビルドアーティファクトなど、ワークフロー実行によって生成されたアーティファクトを保存します。 必要なストレージ容量は、{% data variables.product.prodname_actions %} の使用状況によって異なります。 単一の外部ストレージ設定のみがサポートされており、複数のストレージプロバイダを同時に使用することはできません。
-
-{% data variables.product.prodname_actions %} は、次のストレージプロバイダをサポートしています。
-
-* Azure Blob ストレージ
-* Amazon S3
-* NAS ストレージ用の S3 対応 MinIO ゲートウェイ
-
-{% note %}
-
-**注釈:** これらは、{% data variables.product.company_short %} がサポートし、支援を提供できる唯一のストレージプロバイダです。 他の S3 API 互換のストレージプロバイダは、S3 API との違いにより、機能しない可能性があります。 追加のストレージプロバイダのサポートをリクエストするには、[お問い合わせ](https://support.github.com/contact)ください。
-
-{% endnote %}
-
-## Networking considerations
-
-{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)."
-
-{% ifversion ghes %}
-
-## ストレージプロバイダで {% data variables.product.prodname_actions %} を有効化する
-
-以下の手順のいずれかに従って、選択したストレージプロバイダで {% data variables.product.prodname_actions %} を有効にします。
-
-* [Azure Blob ストレージで GitHub Actions を有効化する](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
-* [Amazon S3 ストレージで GitHub Actions を有効化する](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
-* [NAS ストレージ用の MinIO ゲートウェイで GitHub Actions を有効化する](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
-
-## Enterprise 内の {% data variables.product.prodname_actions %} のアクセス権限を管理する
-
-ポリシーを使用して、{% data variables.product.prodname_actions %} へのアクセスを管理できます。 詳しい情報については、「[Enterprise に GitHub Actions のポリシーを施行する](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)」を参照してください。
-
-## セルフホストランナーの追加
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% data variables.product.prodname_actions %} ワークフローを実行するには、セルフホストランナーを追加する必要があります。 Enterprise、Organization、リポジトリレベルでセルフホストランナーを追加できます。 詳しい情報については「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。
-
-## Enterprise で使用できるアクションを管理する
-
-ユーザーが Enterprise で使用できるアクションを制御できます。 これには、{% data variables.product.prodname_dotcom_the_website %} からのアクションへの自動アクセス用の {% data variables.product.prodname_github_connect %} の設定、または {% data variables.product.prodname_dotcom_the_website %} からのアクションの手動同期が含まれます。
-
-詳しい情報については、「[Enterprise でのアクションの使用について](/admin/github-actions/about-using-actions-in-your-enterprise)」を参照してください。
-
-## {% data variables.product.prodname_actions %} の一般的なセキュリティ強化
-
-{% data variables.product.prodname_actions %} のセキュリティプラクティスについて詳しく学ぶには、「[{% data variables.product.prodname_actions %} のセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions)」を参照してください。
-
-{% endif %}
-
-## Reserved Names
-
-When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore.

translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md

@@ -1,37 +0,0 @@
----
-title: GitHub AE の GitHub Actions を使い始める
-shortTitle: GitHub Actionsを使ってみる
-intro: '{% data variables.product.prodname_ghe_managed %} で {% data variables.product.prodname_actions %} を設定する方法を学びます。'
-permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
-versions:
-  ghae: '*'
-type: how_to
-topics:
-  - Actions
-  - Enterprise
-redirect_from:
-  - /admin/github-actions/getting-started-with-github-actions-for-github-ae
----
-
-{% data reusables.actions.ae-beta %}
-
-この記事では、サイト管理者が {% data variables.product.prodname_actions %} を使用するように {% data variables.product.prodname_ghe_managed %} を設定する方法について説明しています。
-
-## Enterprise 内の {% data variables.product.prodname_actions %} のアクセス権限を管理する
-
-ポリシーを使用して、{% data variables.product.prodname_actions %} へのアクセスを管理できます。 詳しい情報については、「[Enterprise に GitHub Actions のポリシーを施行する](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)」を参照してください。
-
-## ランナーを追加する
-
-{% note %}
-
-**Note:** To add {% data variables.actions.hosted_runner %}s to {% data variables.product.prodname_ghe_managed %}, you will need to contact {% data variables.product.prodname_dotcom %} support.
-
-{% endnote %}
-
-{% data variables.product.prodname_actions %} ワークフローを実行するには、ランナーを追加する必要があります。 Enterprise、Organization、またはリポジトリレベルでランナーを追加できます。 詳しい情報については、「[{% data variables.actions.hosted_runner %} について](/actions/using-github-hosted-runners/about-ae-hosted-runners)」を参照してください。
-
-
-## {% data variables.product.prodname_actions %} の一般的なセキュリティ強化
-
-{% data variables.product.prodname_actions %} のセキュリティプラクティスについて詳しく学ぶには、「[{% data variables.product.prodname_actions %} のセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions)」を参照してください。

translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md

@@ -1,149 +0,0 @@
----
-title: Primeiros passos com o GitHub Actions para o GitHub Enterprise Server
-shortTitle: Indrodução ao GitHub Actions
-intro: 'Saiba mais sobre como habilitar e configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} pela primeira vez.'
-permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
-redirect_from:
-  - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage
-  - /admin/github-actions/enabling-github-actions-and-configuring-storage
-  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
-versions:
-  ghes: '*'
-type: how_to
-topics:
-  - Actions
-  - Enterprise
----
-
-{% data reusables.actions.enterprise-beta %}
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% ifversion ghes %}
-
-Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_server %} para usar {% data variables.product.prodname_actions %}. Ele abrange os requisitos de hardware e software, apresenta as opções de armazenamento e descreve as políticas de gestão de segurança.
-
-{% endif %}
-
-## Revise as considerações de hardware
-
-{% ifversion ghes = 3.0 %}
-
-{% note %}
-
-**Observação**: Se você estiver atualizando uma instância de {% data variables.product.prodname_ghe_server %} existente para 3.0 ou posterior e deseja configurar {% data variables.product.prodname_actions %}, observe que os requisitos mínimos de hardware aumentaram. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".
-
-{% endnote %}
-
-{% endif %}
-
-{%- ifversion ghes < 3.2 %}
-
-Os recursos da CPU e memória disponíveis para {% data variables.product.product_location %} determinam o rendimento máximo do trabalho para {% data variables.product.prodname_actions %}.
-
-O teste interno em {% data variables.product.company_short %} demonstrou o rendimento máximo a seguir para instâncias de {% data variables.product.prodname_ghe_server %} com um intervalo de configurações da CPU e memória. Você pode ver diferentes tipos de transferência, dependendo dos níveis gerais de atividade na sua instância.
-
-{%- endif %}
-
-{%- ifversion ghes > 3.1 %}
-
-Os recursos de CPU e memória disponíveis para {% data variables.product.product_location %} determinam o número de trabalhos que podem ser executados simultaneamente sem perda de desempenho.
-
-O pico de trabalhos simultâneos rodando sem perda de desempenho depende de fatores como duração do trabalho, uso de artefatos, número de repositórios em execução de ações, e quanto outro trabalho sua instância está fazendo não relacionado a ações. Os testes internos no GitHub demonstraram os objetivos de desempenho a seguir para o GitHub Enterprise Server em uma série de configurações de CPU e memória:
-
-{% endif %}
-
-{%- ifversion ghes < 3.2 %}
-
-| vCPUs | Memória | Rendimento máximo do trabalho  |
-|:----- |:------- |:------------------------------ |
-| 4     | 32 GB   | Demonstração ou testes rápidos |
-| 8     | 64 GB   | 25 trabalhos                   |
-| 16    | 160 GB  | 35 trabalhos                   |
-| 32    | 256 GB  | 100 trabalhos                  |
-
-{%- endif %}
-
-{%- ifversion ghes > 3.1 %}
-
-| vCPUs | Memória | Simultaneidade máxima* |
-|:----- |:------- |:---------------------- |
-| 32    | 128 GB  | 1500 trabalhos         |
-| 64    | 256 GB  | 1900 trabalhos         |
-| 96    | 384 GB  | 2200 trabalhos         |
-
-*A simultaneidade máxima foi medida usando vários repositórios, a duração do trabalho de aproximadamente 10 minutos e o upload de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância.
-
-{%- endif %}
-
-Se você planeja habilitar {% data variables.product.prodname_actions %} para os usuários de uma instância existente, revise os níveis de atividade para usuários e automações na instância e garanta que você tenha fornecido CPU e memória adequadas para seus usuários. Para obter mais informações sobre o monitoramento da capacidade e desempenho de {% data variables.product.prodname_ghe_server %}, consulte "[Monitoramento do seu aplicativo](/admin/enterprise-management/monitoring-your-appliance)".
-
-Para obter mais informações sobre os requisitos mínimos de hardware para {% data variables.product.product_location %}, consulte as considerações sobre hardware para a plataforma da sua instância.
-
-- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
-- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
-- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
-- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
-- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
-- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %}
-- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-## Requisitos de armazenamento externo
-
-Para habilitar o {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, você deve ter acesso ao armazenamento externo do blob.
-
-O {% data variables.product.prodname_actions %} usa armazenamento do blob para armazenar artefatos gerados pelas execuções do fluxo de trabalho, como registros de fluxo de trabalho e artefatos de criação enviados pelo usuário. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_actions %}. Somente uma única configuração de armazenamento externo é compatível, e você não pode usar vários provedores de armazenamento ao mesmo tempo.
-
-{% data variables.product.prodname_actions %} é compatível com estes provedores de armazenamento:
-
-* Armazenamento do Azure Blob
-* Amazon S3
-* MinIO Gateway compatível com S3 para NAS
-
-{% note %}
-
-**Observação:** Estes são os únicos provedores de armazenamento com os quais {% data variables.product.company_short %} é compatível e podem fornecer ajuda. Outros provedores de armazenamento compatíveis com a API do S3 provavelmente não funcionarão devido a diferenças em relação à API do S3. [Entre em contato conosco](https://support.github.com/contact) para pedir suporte para provedores de armazenamento adicionais.
-
-{% endnote %}
-
-## Considerações de rede
-
-{% data reusables.actions.proxy-considerations %} Para obter mais informações sobre o uso de um proxy com {% data variables.product.prodname_ghe_server %}, consulte "[Configurando um servidor de proxy web de saída](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)".
-
-{% ifversion ghes %}
-
-## Habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento
-
-Siga um dos procedimentos abaixo para habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento escolhido:
-
-* [Habilitar o o GitHub Actions com armazenamento do Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
-* [Habilitar o GitHub Actions com armazenamento do Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
-* [Habilitar o GitHub Actions com MinIO Gateway para armazenamento NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
-
-## Gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} na sua empres
-
-Você pode usar políticas para gerenciar o acesso a {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
-
-## Adicionar executores auto-hospedados
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-Para executar fluxos de trabalho de {% data variables.product.prodname_actions %}, você deve adicionar executores auto-hospedados. Você pode adicionar executores auto-hospedados nos níveis da empresa, organização ou repositório. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
-
-## Gerenciar quais ações podem ser usadas na sua empresa
-
-Você pode controlar quais ações os usuários têm permissão para usar na sua empresa. Isso inclui a configuração de {% data variables.product.prodname_github_connect %} para acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %}, ou a sincronização manual das ações de {% data variables.product.prodname_dotcom_the_website %}.
-
-Para obter mais informações, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/about-using-actions-in-your-enterprise)".
-
-## Fortalecimento geral de segurança para {% data variables.product.prodname_actions %}
-
-Se você quiser saber mais sobre as práticas de segurança para {% data variables.product.prodname_actions %}, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)".
-
-{% endif %}
-
-## Nomes reservados
-
-Ao habilitar {% data variables.product.prodname_actions %} para a sua empresa, serão criadas duas organizações: `github` e `actions`. Se sua empresa já usa o nome da organização `github`, `github-org` (ou `github-github-org` se `github-org` também estiver em uso) será usado. Se sua empresa já usa o nome da organização `actions`, `github-actions` (ou `github-actions-org` se `github-actions` também estiver em uso) será usado. Uma vez que as ações são habilitadas, você não poderá usar mais esses nomes.

translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md

@@ -1,37 +0,0 @@
----
-title: Introdução ao GitHub Actions para GitHub AE
-shortTitle: Indrodução ao GitHub Actions
-intro: 'Aprenda a configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_managed %}.'
-permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
-versions:
-  ghae: '*'
-type: how_to
-topics:
-  - Actions
-  - Enterprise
-redirect_from:
-  - /admin/github-actions/getting-started-with-github-actions-for-github-ae
----
-
-{% data reusables.actions.ae-beta %}
-
-Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_managed %} para usar {% data variables.product.prodname_actions %}.
-
-## Gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} na sua empres
-
-Você pode usar políticas para gerenciar o acesso a {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
-
-## Adicionar executores
-
-{% note %}
-
-**Observação:** Para adicionar {% data variables.actions.hosted_runner %}a {% data variables.product.prodname_ghe_managed %}, você precisará entrar em contato com o suporte de {% data variables.product.prodname_dotcom %}.
-
-{% endnote %}
-
-Para executar fluxos de trabalho de {% data variables.product.prodname_actions %}, você deve adicionar executores. Você pode adicionar executores aos níveis da empresa, organização ou repositório. Para obter mais informações, consulte "[Sobre {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)".
-
-
-## Fortalecimento geral de segurança para {% data variables.product.prodname_actions %}
-
-Se você quiser saber mais sobre as práticas de segurança para {% data variables.product.prodname_actions %}, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions)".

translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md

@@ -1,149 +0,0 @@
----
-title: GitHub Actions for GitHub Enterprise Server 使用入门
-shortTitle: GitHub Actions 使用入门
-intro: '了解首次在 {% data variables.product.prodname_ghe_server %} 上启用和配置 {% data variables.product.prodname_actions %}。'
-permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
-redirect_from:
-  - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage
-  - /admin/github-actions/enabling-github-actions-and-configuring-storage
-  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
-versions:
-  ghes: '*'
-type: how_to
-topics:
-  - Actions
-  - Enterprise
----
-
-{% data reusables.actions.enterprise-beta %}
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% ifversion ghes %}
-
-本文介绍站点管理员如何配置 {% data variables.product.prodname_ghe_server %} 来使用 {% data variables.product.prodname_actions %}。 它涵盖了硬件和软件需求、存储选项以及安全管理策略。
-
-{% endif %}
-
-## 查看硬件注意事项
-
-{% ifversion ghes = 3.0 %}
-
-{% note %}
-
-**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)。”
-
-{% endnote %}
-
-{% endif %}
-
-{%- ifversion ghes < 3.2 %}
-
-{% data variables.product.product_location %} 可用的 CPU 和内存资源决定了 {% data variables.product.prodname_actions %} 的最大作业吞吐量。
-
-{% data variables.product.company_short %} 的内部测试展示了具有系列 CPU 和内存配置的 {% data variables.product.prodname_ghe_server %} 实例的以下最大吞吐量。 您可能会看到不同的吞吐量，具体取决于实例的总体活动水平。
-
-{%- endif %}
-
-{%- ifversion ghes > 3.1 %}
-
-可用于 {% data variables.product.product_location %} 的 CPU 和内存资源可确定可同时运行且不造成绩效损失的工作数量。
-
-在没有性能损失的情况下并行工作的高峰数量取决于作业持续时间限、构件使用、运行操作的仓库数量，以及实例所做的与操作无关的其他工作量等。 GitHub 的内部测试在一系列 CPU 和内存配置中证明了 GitHub Enterprise Server 的以下性能目标：
-
-{% endif %}
-
-{%- ifversion ghes < 3.2 %}
-
-| vCPU | 内存     | 最大作业吞吐量 |
-|:---- |:------ |:------- |
-| 4    | 32 GB  | 演示或轻量测试 |
-| 8    | 64 GB  | 25 个作业  |
-| 16   | 160 GB | 35 个作业  |
-| 32   | 256 GB | 100 个作业 |
-
-{%- endif %}
-
-{%- ifversion ghes > 3.1 %}
-
-| vCPU | 内存     | 最大并行数*   |
-|:---- |:------ |:-------- |
-| 32   | 128 GB | 1500 个作业 |
-| 64   | 256 GB | 1900 个作业 |
-| 96   | 384 GB | 2200 个作业 |
-
-*最大并行数使用多个仓库、约 10 分钟的作业持续时间以及 10 MB 构件上传测得。 您可能会经历不同的性能，具体取决于实例的总体活动水平。
-
-{%- endif %}
-
-If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. 有关监控 {% data variables.product.prodname_ghe_server %} 容量和性能的更多信息，请参阅“[监控您的设备](/admin/enterprise-management/monitoring-your-appliance)”。
-
-有关 {% data variables.product.product_location %} 的最低硬件要求的更多信息，请参阅实例平台的硬件考虑因素。
-
-- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
-- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
-- [Google Cloud 平台](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
-- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
-- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
-- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %}
-- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-## 外部存储要求
-
-要在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %}，您必须有权访问外部 Blob 存储。
-
-{% data variables.product.prodname_actions %} 使用 Blob 存储来存储工作流程运行生成的构件，如工作流程日志和用户上传的构建构件。 所需存储量取决于您使用 {% data variables.product.prodname_actions %} 的情况。 仅支持单个外部存储配置，不能同时使用多个存储提供程序。
-
-{% data variables.product.prodname_actions %} 支持以下存储提供商：
-
-* Azure Blob 存储
-* Amazon S3
-* S3 兼容的 MinIO Gateway for NAS
-
-{% note %}
-
-**注：**只有这些是 {% data variables.product.company_short %} 支持并可以提供帮助的存储提供程序。 由于 S3 API 的差异，其他 S3 API 兼容的存储提供程序难以正常工作。 [联系我们](https://support.github.com/contact) 以请求支持额外的存储提供程序。
-
-{% endnote %}
-
-## 网络考虑因素
-
-{% data reusables.actions.proxy-considerations %} 有关使用 {% data variables.product.prodname_ghe_server %} 代理的更多信息，请参阅“[配置出站网络代理服务器](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)”。
-
-{% ifversion ghes %}
-
-## 使用您的存储提供程序启用 {% data variables.product.prodname_actions %}
-
-请按照以下过程之一使用所选存储提供程序启用 {% data variables.product.prodname_actions %}：
-
-* [使用 Azure Blob 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
-* [使用 Amazon S3 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
-* [使用 MinIO Gateway for NAS 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
-
-## 管理企业中 {% data variables.product.prodname_actions %} 的访问权限
-
-您可以使用策略来管理 {% data variables.product.prodname_actions %} 的访问。 更多信息请参阅“[为企业执行 GitHub Actions 策略](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)”。
-
-## 添加自托管的运行器
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-要运行 {% data variables.product.prodname_actions %} 工作流程，您需要添加自托管运行器。 您可以在企业、组织或仓库级别添加自托管运行器。 更多信息请参阅“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。
-
-## 管理哪些操作可用于您的企业
-
-您可以控制允许用户在企业中使用哪些操作。 这包括设置 {% data variables.product.prodname_github_connect %} 以自动访问来自 {% data variables.product.prodname_dotcom_the_website %} 的操作，或手动同步来自 {% data variables.product.prodname_dotcom_the_website %} 的操作。
-
-更多信息请参阅“[关于使用企业中的操作](/admin/github-actions/about-using-actions-in-your-enterprise)”。
-
-## {% data variables.product.prodname_actions %} 的一般安全性增强
-
-如需了解有关 {% data variables.product.prodname_actions %} 安全实践的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的安全性增强](/actions/learn-github-actions/security-hardening-for-github-actions)”。
-
-{% endif %}
-
-## 保留名称
-
-为企业启用 {% data variables.product.prodname_actions %} 时，将创建两个组织：`github` 和 `actions`。 如果您的企业已经使用 `github` 组织名称，则将改用 `github-org` （如果 `github-org` 也在使用中，则改用 `github-github-org`）。 如果您的企业已经使用 `actions` 组织名称，则将改用 `github-actions`（如果 `github-actions` 也在使用中，则改用 `github-actions-org`）。 启用操作后，您将无法再使用这些名称。

translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md

@@ -1,37 +0,0 @@
----
-title: GitHub Actions for GitHub AE 使用入门
-shortTitle: GitHub Actions 使用入门
-intro: '了解在 {% data variables.product.prodname_ghe_managed %} 上配置 {% data variables.product.prodname_actions %}。'
-permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
-versions:
-  ghae: '*'
-type: how_to
-topics:
-  - Actions
-  - Enterprise
-redirect_from:
-  - /admin/github-actions/getting-started-with-github-actions-for-github-ae
----
-
-{% data reusables.actions.ae-beta %}
-
-本文介绍站点管理员如何配置 {% data variables.product.prodname_ghe_managed %} 来使用 {% data variables.product.prodname_actions %}。
-
-## 管理企业中 {% data variables.product.prodname_actions %} 的访问权限
-
-您可以使用策略来管理 {% data variables.product.prodname_actions %} 的访问。 更多信息请参阅“[为企业执行 GitHub Actions 策略](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)”。
-
-## 添加运行器
-
-{% note %}
-
-**注意：**要添加 {% data variables.actions.hosted_runner %} 到 {% data variables.product.prodname_ghe_managed %}，您需要联系 {% data variables.product.prodname_dotcom %} 支持。
-
-{% endnote %}
-
-要运行 {% data variables.product.prodname_actions %} 工作流程，您需要添加运行器。 您可以在企业、组织或仓库级别添加运行器。 更多信息请参阅“[关于 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)”。
-
-
-## {% data variables.product.prodname_actions %} 的一般安全性增强
-
-如需了解有关 {% data variables.product.prodname_actions %} 安全实践的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的安全性增强](/actions/learn-github-actions/security-hardening-for-github-actions)”。