` mais uma vez.
- {% data reusables.enterprise_installation.start-replication %}
- {% data reusables.enterprise_installation.replication-status %}
-6. Ao concluir a atualização da última réplica e quando a ressincronização terminar, desabilite o modo de manutenção para que os usuários possam trabalhar na {% data variables.product.product_location_enterprise %}.
-
-### Restaurar após uma atualização com falha
-
-Em caso de falha ou interrupção da atualização, volte a sua instância ao estado anterior. Esse processo dependerá do tipo de atualização.
-
-#### Voltar a uma versão de patch
-
-Para reverter uma versão de patch, use o comando `ghe-upgrade` com o switch `--allow-patch-rollback`. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
-
-Para obter mais informações, consulte "[Utilitários de linha de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)".
-
-#### Voltar a uma versão de recurso
-
-Para voltar a partir de uma versão de recurso, faça a restauração partindo de um instantâneo da VM para garantir o estado consistente das partições raiz e de dados. Para obter mais informações, consulte "[Obter um instantâneo](#taking-a-snapshot)".
diff --git a/translations/pt-BR/content/admin/installation/using-github-enterprise-server-with-a-load-balancer.md b/translations/pt-BR/content/admin/installation/using-github-enterprise-server-with-a-load-balancer.md
deleted file mode 100644
index a6c61fa87f25..000000000000
--- a/translations/pt-BR/content/admin/installation/using-github-enterprise-server-with-a-load-balancer.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Usar o GitHub Enterprise Server com balanceador de carga
-intro: 'Use um balanceador de carga na frente de um appliance ou de um par de appliances do {% data variables.product.prodname_ghe_server %} em uma configuração de alta disponibilidade.'
-redirect_from:
- - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer/
- - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_clustering.load_balancer_intro %}
-
-{% data reusables.enterprise_clustering.load_balancer_dns %}
-
-### Informações de conexão do cliente
-
-Como as conexões do cliente com o {% data variables.product.prodname_ghe_server %} vêm do balanceador de carga, pode ocorrer a perda do endereço IP do cliente.
-
-{% data reusables.enterprise_clustering.proxy_preference %}
-
-{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
-
-#### Habilitar o suporte de protocolo PROXY na {% data variables.product.product_location_enterprise %}
-
-É altamente recomendável ativar o suporte de protocolo PROXY para o appliance e o balanceador de carga. Use as instruções do fornecedor para habilitar o protocolo PROXY no balanceador de carga. Para obter mais informações, consulte a [documentação do protocolo PROXY](http://www.haproxy.org/download/1.6/doc/proxy-protocol.txt).
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-3. Em **External load balancers** (Balanceadores de carga externos), selecione **Enable support for PROXY protocol** (Habilitar suporte do protocolo PROXY). ![Caixa de seleção para habilitar o suporte do protocolo PROXY](/assets/images/enterprise/management-console/enable-proxy.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-{% data reusables.enterprise_clustering.proxy_protocol_ports %}
-
-#### Habilitar o suporte X-Forwarded-For na {% data variables.product.product_location_enterprise %}
-
-{% data reusables.enterprise_clustering.x-forwarded-for %}
-
-{% data reusables.enterprise_installation.terminating-tls %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-3. Em **External load balancers** (Balanceadores de carga externos), selecione **Allow HTTP X-Forwarded-For header** (Habilitar header HTTP X-Forwarded-For). ![Caixa de seleção para permitir o header HTTP X-Forwarded-For](/assets/images/enterprise/management-console/allow-xff.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-{% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
-
-### Configurar verificações de integridade
-
-As verificações de integridade permitem que um balanceador de carga pare de enviar tráfego para um nó que não responde em caso de falha na verificação pré-configurada do nó em questão. Se o appliance estiver offline devido a manutenção ou falha inesperada, o balanceador de carga poderá exibir uma página de status. Em configurações de alta disponibilidade (HA), é possível usar balanceadores de carga como parte da estratégia de failover. No entanto, não há suporte para failover automático de pares de HA. Promova manualmente o appliance réplica antes que ele comece a atender a solicitações. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_ghe_server %} para alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)".
-
-{% data reusables.enterprise_clustering.health_checks %}
-{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
diff --git a/translations/pt-BR/content/admin/installation/validating-your-domain-settings.md b/translations/pt-BR/content/admin/installation/validating-your-domain-settings.md
deleted file mode 100644
index 5afc461849fc..000000000000
--- a/translations/pt-BR/content/admin/installation/validating-your-domain-settings.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Validar configurações de domínio
-intro: 'Antes de iniciar a {% data variables.product.product_location_enterprise %} pela primeira vez, verifique se as configurações de domínio estão ajustadas adequadamente.'
-redirect_from:
- - /enterprise/admin/installation/validating-your-domain-settings
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.hostname-menu-item %}
-4. Para testar as configurações DNS e SSL, clique em **Test domain settings** (Testar configurações de domínio). ![Botão Test domain settings (Testar configurações de domínio)](/assets/images/enterprise/management-console/test-domain-settings.png)
-{% data reusables.enterprise_management_console.test-domain-settings-failure %}
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/pt-BR/content/admin/installation/viewing-push-logs.md b/translations/pt-BR/content/admin/installation/viewing-push-logs.md
deleted file mode 100644
index c4d621fe0a9b..000000000000
--- a/translations/pt-BR/content/admin/installation/viewing-push-logs.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Exibir logs de push
-intro: 'Os administradores do site podem exibir uma lista de operações push do Git para qualquer repositório na {% data variables.product.product_location_enterprise %}.'
-redirect_from:
- - /enterprise/admin/articles/viewing-push-logs/
- - /enterprise/admin/installation/viewing-push-logs
-versions:
- enterprise-server: '*'
----
-
-As entradas de log de push mostram o seguinte:
-
-- Quem iniciou o push;
-- Se o push foi forçado ou não;
-- O branch para o qual o push foi feito;
-- O protocolo usado para fazer push;
-- O endereço IP de origem;
-- O cliente Git usado para fazer push;
-- Os hashes SHA de antes e depois da operação.
-
-### Exibir os logs de push do repositório
-
-1. Navegue até um repositório.
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-3. No canto superior direito da página, clique em {% octicon "shield" aria-label="The shield" %} **Security** (Segurança). ![Guia de segurança](/assets/images/enterprise/site-admin-settings/repo/repo-security-top-tab.png)
-4. Na barra lateral esquerda, clique em **Push Log** (Log de push). ![Guia de log de push](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
-
-### Exibir os logs de push do repositório na linha de comando
-
-1. Acesse o SSH no appliance. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)".
-2. No repositório do Git adequado, abra o arquivo de log de auditoria:
- ```shell
- ghe-repo owner/repository -c "less audit_log"
- ```
diff --git a/translations/pt-BR/content/admin/migrations/about-migrations.md b/translations/pt-BR/content/admin/migrations/about-migrations.md
deleted file mode 100644
index 962990d5c89e..000000000000
--- a/translations/pt-BR/content/admin/migrations/about-migrations.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Sobre migrações
-intro: 'Migração é o processo de transferência de dados de um local de *origem* (organização do {% data variables.product.prodname_dotcom_the_website %} ou uma instância do {% data variables.product.prodname_ghe_server %}) para uma instância de *destino* do {% data variables.product.prodname_ghe_server %}. É possível usar as migrações para transferir os dados ao alterar plataformas ou atualizar o hardware na sua instância.'
-redirect_from:
- - /enterprise/admin/migrations/about-migrations
-versions:
- enterprise-server: '*'
----
-
-### Tipos de migração
-
-Você pode fazer três tipos de migração:
-
-- Migração de uma instância do {% data variables.product.prodname_ghe_server %} para outra do {% data variables.product.prodname_ghe_server %}: você pode migrar qualquer número de repositórios pertencentes a qualquer usuário ou organização na instância. Para executar a migração, você deve ter acesso de administrador do site a ambas as instâncias.
-- Migração de uma organização do {% data variables.product.prodname_dotcom_the_website %} para uma instância do {% data variables.product.prodname_ghe_server %}: você pode migrar qualquer número de repositórios pertencentes à organização. Para fazer a migração, você deve ter [acesso administrativo](/enterprise/user/articles/permission-levels-for-an-organization/) à organização do {% data variables.product.prodname_dotcom_the_website %} e acesso de administrador do site na instância de destino.
-- *Execuções de experiência* são migrações que importam dados para uma [instância de preparo](/enterprise/admin/guides/installation/setting-up-a-staging-instance/). Elas podem ser úteis para ver o que *aconteceria* se uma migração fosse aplicada à {% data variables.product.product_location_enterprise %}. **É altamente recomendável fazer uma execução de experiência em uma instância de preparo antes de importar dados para a sua instância de produção.**
-
-### Dados migrados
-
-Durante uma migração, tudo gira em torno do repositório. A maioria dos dados associados ao repositório pode ser migrada. Por exemplo, um repositório dentro de uma organização migrará o repositório *e* a organização, além dos usuários, equipes, problemas e pull requests associados ao repositório.
-
-Os itens na tabela abaixo podem ser migrados com um repositório. Não é possível migrar os itens que não constam na lista.
-
-{% data reusables.enterprise_migrations.fork-persistence %}
-
-| Dados associados a um repositório migrado | Observações |
-| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Usuários | As **@menções** aos usuários são rescritas para corresponder ao destino. |
-| Organizações | Os nomes e detalhes das organizações são migrados. |
-| Repositórios | Links para árvores, blobs, commits e linhas do Git são rescritas para corresponder ao destino. O migrador segue no máximo três redirecionamentos de repositório. |
-| Wikis | Todos os dados da wiki são migrados. |
-| Equipes | As **@menções** às equipes são rescritas para corresponder ao destino. |
-| Marcos | Os registros de data e hora são preservados. |
-| Quadros de projeto | Os quadros de projeto associados ao repositório e à organização proprietária do repositório são migrados. |
-| Questões | As referências a problemas e os registros de data e hora são preservados. |
-| Comentários dos problemas | As referências cruzadas a comentários são rescritas para a instância de destino. |
-| Pull requests | As referências cruzadas a pull requests são rescritas para corresponder ao destino. Os registros de data e hora são preservados. |
-| Revisões de pull request | As revisões de pull request e os dados associados são migrados. |
-| Comentários das revisões de pull request | As referências cruzadas aos comentários são rescritas para a instância de destino. Os registros de data e hora são preservados. |
-| Comentários de commit | As referências cruzadas a comentários são rescritas para a instância de destino. Os registros de data e hora são preservados. |
-| Versões | Todos os dados das versões são migrados. |
-| Ações feitas em problemas ou em pull requests | São preservadas todas as modificações em problemas ou pull requests, como atribuir usuários, renomear títulos e modificar etiquetas, bem como os registros de data e hora de cada ação. |
-| Anexos de arquivo | [Anexos de arquivo em problemas e pull requests](/articles/file-attachments-on-issues-and-pull-requests) são migrados. Você pode desabilitar essa opção como parte da migração. |
-| Webhooks | Somente os webhooks ativos são migrados. |
-| Chaves de implantação de repositório | As chaves de implantação de repositório são migradas. |
-| Branches protegidos | As configurações de branches protegidos e os dados associados são migrados. |
diff --git a/translations/pt-BR/content/admin/migrations/applying-the-imported-data-on-github-enterprise-server.md b/translations/pt-BR/content/admin/migrations/applying-the-imported-data-on-github-enterprise-server.md
deleted file mode 100644
index e5a1625baa39..000000000000
--- a/translations/pt-BR/content/admin/migrations/applying-the-imported-data-on-github-enterprise-server.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Aplicar dados importados no GitHub Enterprise Server
-intro: 'Depois de concluir a revisão dos dados de migração, você poderá aplicar permanentemente as alterações à instância de destino.'
-redirect_from:
- - /enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise/
- - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_installation.ssh-into-target-instance %}
-
-2. Usando o comando `ghe-migrator import`, comece o processo de importação. Você precisará do seguinte:
- * Seu Migration GUID.
- * Seu token de acesso pessoal para autenticação. O token de acesso pessoal que você usa é apenas para autenticação como administrador do site e não requer nenhum escopo específico. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
-
- ```shell
- $ ghe-migrator import /home/admin/MIGRATION_GUID.tar.gz -g MIGRATION_GUID -u username -p TOKEN
-
- > Starting GitHub::Migrator
- > Import 100% complete /
- ```
-
- * {% data reusables.enterprise_migrations.specify-staging-path %}
diff --git a/translations/pt-BR/content/admin/migrations/completing-the-import-on-github-enterprise-server.md b/translations/pt-BR/content/admin/migrations/completing-the-import-on-github-enterprise-server.md
deleted file mode 100644
index 50788f8f980c..000000000000
--- a/translations/pt-BR/content/admin/migrations/completing-the-import-on-github-enterprise-server.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Concluir a importação no GitHub Enterprise Server
-intro: 'Depois de aplicar sua migração à instância de destino e após a revisão da migração, você vai desbloquear os repositórios e excluí-los da origem. Antes de excluir os dados da origem, é recomendável aguardar cerca de duas semanas para garantir o funcionamento adequado de todos os procedimentos.'
-redirect_from:
- - /enterprise/admin/guides/migrations/completing-the-import-on-github-enterprise/
- - /enterprise/admin/migrations/completing-the-import-on-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
-### Desbloquear repositórios na instância de destino
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-{% data reusables.enterprise_migrations.unlocking-on-instances %}
-
-### Desbloquear repositórios na origem
-
-#### Desbloquear repositórios de uma organização do {% data variables.product.prodname_dotcom_the_website %}
-
-Para desbloquear repositórios em uma organização do {% data variables.product.prodname_dotcom_the_website %}, você enviará uma solicitação `DELETE` para o ponto de extremidade de desbloqueio da migração. Você precisará do seguinte:
- * Token de acesso para autenticação;
- * `id` exclusivo da migração;
- * Nome do repositório a ser desbloqueado.
-```shell
-curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \
- -H "Accept: application/vnd.github.wyandotte-preview+json" \
- https://api.github.com/orgs/orgname/migrations/id/repos/repo_name/lock
-```
-
-#### Excluir repositórios de uma organização do {% data variables.product.prodname_dotcom_the_website %}
-
-Depois de desbloquear os repositórios da organização do {% data variables.product.prodname_dotcom_the_website %}, você deve excluir todos os repositórios migrados anteriormente usando o [endpoint de exclusão de repositórios](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository). Você precisará do token de acesso para autenticação:
-```shell
-curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \
- https://api.github.com/repos/orgname/repo_name
-```
-
-#### Desbloquear repositórios de uma instância do {% data variables.product.prodname_ghe_server %}
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-{% data reusables.enterprise_migrations.unlocking-on-instances %}
diff --git a/translations/pt-BR/content/admin/migrations/exporting-migration-data-from-github-enterprise-server.md b/translations/pt-BR/content/admin/migrations/exporting-migration-data-from-github-enterprise-server.md
deleted file mode 100644
index 958e8d87d2fe..000000000000
--- a/translations/pt-BR/content/admin/migrations/exporting-migration-data-from-github-enterprise-server.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Exportar dados de migração do GitHub Enterprise Server
-intro: 'Para exportar os dados de migração de uma instância do {% data variables.product.prodname_ghe_server %}, você deverá preparar a instância, bloquear os repositórios e gerar um arquivo de migração. Você deve exportar os dados da instância do {% data variables.product.prodname_ghe_server %} se estiver planejando mudar de plataforma ou se estiver com tudo pronto para migrar de uma instância de experiência para uma instância de produção.'
-redirect_from:
- - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise/
- - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/migrations/exporting-migration-data-from-githubcom.md b/translations/pt-BR/content/admin/migrations/exporting-migration-data-from-githubcom.md
deleted file mode 100644
index 5caee79f7db4..000000000000
--- a/translations/pt-BR/content/admin/migrations/exporting-migration-data-from-githubcom.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Exportar dados de migração do GitHub.com
-intro: 'Para exportar os dados de migração de uma organização do {% data variables.product.prodname_dotcom_the_website %}, você deverá usar a API para selecionar os repositórios a serem migrados. Feito isso, você vai gerar um arquivo de migração que pode ser importado na instância do {% data variables.product.prodname_ghe_server %}.'
-redirect_from:
- - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-com
- - /enterprise/admin/migrations/exporting-migration-data-from-githubcom
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/migrations/exporting-the-github-enterprise-server-source-repositories.md b/translations/pt-BR/content/admin/migrations/exporting-the-github-enterprise-server-source-repositories.md
deleted file mode 100644
index e19b804fbd9e..000000000000
--- a/translations/pt-BR/content/admin/migrations/exporting-the-github-enterprise-server-source-repositories.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Exportar os repositórios de origem do GitHub Enterprise Server
-intro: 'Depois de bloquear os repositórios de origem, você pode exportá-los individualmente ou em lote usando uma lista de URLs de repositório em um arquivo de texto. Feito isso, você criará um único arquivo de migração para o processo de importação.'
-redirect_from:
- - /enterprise/admin/guides/migrations/exporting-the-github-enterprise-source-repositories/
- - /enterprise/admin/migrations/exporting-the-github-enterprise-server-source-repositories
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_migrations.locking-repositories %}
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. Para preparar a exportação de um repositório, use o comando `ghe-migrator add` com a URL do repositório:
- * Se você estiver bloqueando o repositório, adicione `--lock` ao comando. Se estiver executando um teste, não será necessário incluir `--lock`.
- ```shell
- $ ghe-migrator add https://hostname/username/reponame --lock
- ```
- * Você pode excluir anexos de arquivos adicionando `--exclude_attachments` ao comando. {% data reusables.enterprise_migrations.exclude-file-attachments %}
- * Para preparar a exportação de vários repositórios de uma só vez, crie um arquivo de texto listando cada URL do repositório em uma linha separada e execute o comando `ghe-migrator add` com o sinalizador `-i` e o caminho para o seu arquivo de texto.
- ```shell
- $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URLS.txt
- ```
-
-3. Quando solicitado, informe seu nome de usuário do {% data variables.product.prodname_ghe_server %}:
- ```shell
- Insira o nome de usuário autorizado para a migração: admin
- ```
-4. Quando o token de acesso pessoal for solicitado, informe o token de acesso que você criou na seção "[Preparar a instância de origem do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance/)":
- ```shell
- Insira o token de acesso pessoal: **************
- ```
-5. Após a conclusão do `ghe-migrator add`, ele imprimirá o "GUID de Migração" exclusivo gerado para identificar a exportação e a lista dos recursos adicionados à exportação. Você usará o GUID de Migração gerado nas etapas subsequentes `ghe-migrator add` e `ghe-migrator export` para informar que o `ghe-migrator` deve continuar operando na mesma exportação.
- ```shell
- > 101 models added to export
- > Migration GUID: example-migration-guid
- > Number of records in this migration:
- > users | 5
- > organizations | 1
- > repositories | 1
- > teams | 3
- > protected_branches | 1
- > pull_request_reviews | 1
- > milestones | 1
- > issues | 3
- > pull_requests | 5
- > pull_request_review_comments | 4
- > commit_comments | 2
- > issue_comments | 10
- > issue_events | 63
- > releases | 3
- > attachments | 4
- > projects | 2
- ```
- Sempre que você adicionar um novo repositório com o GUID de Migração atual, ele atualizará a exportação atual. Se você executar `ghe-migrator add` novamente sem GUID de Migração, ele vai iniciar uma nova exportação e gerar um novo GUID de Migração. **Não reutilize o GUID de Migração gerado durante uma exportação quando você começar a preparar a migração para importar**.
-
-3. Se você bloqueou o repositório de origem, é possível usar o comando `ghe-migrator target_url` para personalizar uma mensagem de bloqueio na página de repositório que vincula ao novo local do repositório. Informe a URL do repositório de origem, a URL do repositório de destino e o GUID de Migração da Etapa 5:
-
- ```shell
- $ ghe-migrator target_url https://hostname/username/reponame https://target_hostname/target_username/target_reponame -g MIGRATION_GUID
- ```
-
-6. Para adicionar mais repositórios à mesma exportação, use o comando `ghe-migrator add` com o sinalizador `-g`. Informe a nova URL do repositório e o GUID de Migração da Etapa 5:
- ```shell
- $ ghe-migrator add https://hostname/username/other_reponame -g MIGRATION_GUID --lock
- ```
-7. Quando terminar de adicionar os repositórios, gere o arquivo de migração usando o comando `ghe-migrator export` com o sinalizador `-g` e o GUID de Migração da Etapa 5:
- ```shell
- $ ghe-migrator export -g MIGRATION_GUID
- > Archive saved to: /data/github/current/tmp/MIGRATION_GUID.tar.gz
- ```
- * {% data reusables.enterprise_migrations.specify-staging-path %}
-
-8. Fechar a conexão com {% data variables.product.product_location_enterprise %}:
- ```shell
- $ exit
- > logout
- > Connection to hostname closed.
- ```
-9. Copie o arquivo de migração para o seu computador usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp). O arquivo terá o nome do GUID de Migração:
- ```shell
- $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop
- ```
-{% data reusables.enterprise_migrations.ready-to-import-migrations %}
diff --git a/translations/pt-BR/content/admin/migrations/exporting-the-githubcom-organizations-repositories.md b/translations/pt-BR/content/admin/migrations/exporting-the-githubcom-organizations-repositories.md
deleted file mode 100644
index 7fbfd43c1e67..000000000000
--- a/translations/pt-BR/content/admin/migrations/exporting-the-githubcom-organizations-repositories.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Exportar os repositórios da organização do GitHub.com
-intro: 'Usando a API de Migrações, é possível exportar os repositórios de uma organização. Após a exportação dos repositórios, você vai baixar o arquivo de migração usado para o processo de importação.'
-redirect_from:
- - /enterprise/admin/guides/migrations/exporting-the-github-com-organization-s-repositories
- - /enterprise/admin/migrations/exporting-the-githubcom-organizations-repositories
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_migrations.fork-persistence %}
-
-Para exportar os dados do repositório do {% data variables.product.prodname_dotcom_the_website %}, use a API de Migrações.
-
-No momento, a API de Migrações está em período de exibição. Ou seja, os pontos de extremidade e os parâmetros podem mudar no futuro. Para acessar a API de Migrações, você deve informar um [tipo de mídia](/v3/media) personalizado no cabeçalho `Accept`: `application/vnd.github.wyandotte-preview+json`. Os exemplos abaixo incluem o tipo de mídia personalizado.
-
-### Gerar arquivos de migração
-
-{% data reusables.enterprise_migrations.locking-repositories %}
-
-1. Informe os integrantes da organização que você fará uma migração. Dependendo do número de repositórios exportados, a exportação pode levar vários minutos. A migração completa (com importação) pode levar horas. Portanto, é recomendável fazer uma avaliação para determinar a duração do processo completo. Para obter mais informações, consulte "[Sobre migrações](/enterprise/admin/migrations/about-migrations#types-of-migrations)".
-
-2. Comece a migração fazendo `POST` no ponto de extremidade da migração. Você precisará do seguinte:
- * Token de acesso para autenticação;
- * Uma [lista de repositórios](/v3/repos/#list-organization-repositories) que você pretende migrar:
- ```shell
- curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \
- -H "Accept: application/vnd.github.wyandotte-preview+json" \
- -d'{"lock_repositories":true,"repositories":["orgname/reponame", "orgname/reponame"]}' \
- https://api.github.com/orgs/orgname/migrations
- ```
- * Se quiser bloquear os repositórios antes da migração, verifique se `lock_repositories` está definido como `true`. Fazer isso é altamente recomendável.
- * Você pode excluir anexos de arquivos adicionando `exclude_attachments: true` ao ponto de extremidade. {% data reusables.enterprise_migrations.exclude-file-attachments %} O tamanho do arquivo final deve ser menor do que 20 GB.
-
- A solicitação retorna um `id ` exclusivo que representa a migração. Você precisará dele em ações subsequentes que envolvam a API de Migrações.
-
-3. Envie uma solicitação `GET` para o ponto de extremidade de status da migração para fazer fetch do status da migração. Você precisará do seguinte:
- * Token de acesso para autenticação;
- * `id` exclusivo da migração.
- ```shell
- curl -H "Authorization: token GITHUB_ACCESS_TOKEN" \
- -H "Accept: application/vnd.github.wyandotte-preview+json" \
- https://api.github.com/orgs/orgname/migrations/id
- ```
-
- Os estados das migrações são os seguintes:
- * `pending`, a migração ainda não começou;
- * `exporting`, a migração está em andamento;
- * `exported`, a migração foi concluída com êxito;
- * `failed`, houve falha na migração.
-
-4. Depois de exportar a migração, baixe o aquivo de migração enviando uma solicitação `GET` para o ponto de extremidade de download da migração. Você precisará do seguinte:
- * Token de acesso para autenticação;
- * `id` exclusivo da migração.
- ```shell
- curl -H "Accept: application/vnd.github.wyandotte-preview+json" \
- -u GITHUB_USERNAME:GITHUB_ACCESS_TOKEN \
- -L -o migration_archive.tar.gz \
- https://api.github.com/orgs/orgname/migrations/id/archive
- ```
-
-5. O arquivo de migração é excluído automaticamente após sete dias. Para excluí-lo antes, você pode enviar a solicitação `DELETE` para o ponto de extremidade de exclusão do arquivo de migração. Você precisará do seguinte:
- * Token de acesso para autenticação;
- * `id` exclusivo da migração.
- ```shell
- curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \
- -H "Accept: application/vnd.github.wyandotte-preview+json" \
- https://api.github.com/orgs/orgname/migrations/id/archive
- ```
-{% data reusables.enterprise_migrations.ready-to-import-migrations %}
diff --git a/translations/pt-BR/content/admin/migrations/generating-a-list-of-migration-conflicts.md b/translations/pt-BR/content/admin/migrations/generating-a-list-of-migration-conflicts.md
deleted file mode 100644
index 629fd3812c7f..000000000000
--- a/translations/pt-BR/content/admin/migrations/generating-a-list-of-migration-conflicts.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Gerar uma lista de conflitos de migração
-intro: 'Se houver conflitos nos relatórios `ghe-migrator` durante a preparação dos dados para importação, você deverá gerar uma lista dos conflitos antes de se preparar para resolvê-los com mapeamentos personalizados.'
-redirect_from:
- - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts
-versions:
- enterprise-server: '*'
----
-
-1. Usando o comando `ghe-migrator conflicts` com o GUID de migração, gere um arquivo *conflicts.csv*:
- ```shell
- $ ghe-migrator conflicts -g MIGRATION_GUID > conflicts.csv
- ```
- - Se nenhum conflito for relatado, você poderá importar os dados com segurança conforme as etapas descritas em "[Aplicar os dados importados no {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)".
-2. Se houver conflitos, usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copie *conflicts.csv* para o seu computador local:
- ```shell
- $ scp -P 122 admin@hostname:conflicts.csv ~/Desktop
- ```
-3. Continue em "[Resolver conflitos de migração ou configurar mapeamentos personalizados](/enterprise/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings/)".
diff --git a/translations/pt-BR/content/admin/migrations/importing-data-from-third-party-version-control-systems.md b/translations/pt-BR/content/admin/migrations/importing-data-from-third-party-version-control-systems.md
deleted file mode 100644
index f89a22b8d5d6..000000000000
--- a/translations/pt-BR/content/admin/migrations/importing-data-from-third-party-version-control-systems.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Importar dados de sistemas de controle de versão de terceiros
-intro: 'Usando o conjunto de ferramentas git-import, é possível fazer importações dos controles de versão do Subversion, do Mercurial e do Team Foundation para repositórios do Git no {% data variables.product.prodname_ghe_server %}.'
-redirect_from:
- - /enterprise/admin/migrations/importing-data-from-third-party-version-control-systems
-versions:
- enterprise-server: '*'
----
-
-### Importar projetos do Mercurial
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. Faça um clone bruto do projeto usando o comando abaixo. Especifique a URL do projeto de origem e um caminho para um repositório temporário:
- ```shell
- $ git-import-hg-raw HG-CLONE-URL /PATH/REPO-NAME.git
- # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
- ```
-{% data reusables.enterprise_migrations.review-the-import-csv %}
-4. Rescreva os autores e branches usando o arquivo CSV:
- ```shell
- $ git-import-rewrite --flavor hg --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git
- ```
-5. Caso ainda não tenha feito isso, [crie um repositório vazio no {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository).
-{% data reusables.command_line.switching_directories_procedural %}
-7. Faça push do repositório importado para o {% data variables.product.prodname_ghe_server %}:
- ```shell
- $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE
- ```
-
-### Importar projetos do Subversion
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. Faça um clone bruto do projeto usando o comando abaixo. Especifique a URL do projeto de origem e um caminho para um repositório temporário:
- ```shell
- $ git-import-svn-raw SVN-CLONE-URL /PATH/REPO-NAME.git
- # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
- ```
-{% data reusables.enterprise_migrations.review-the-import-csv %}
-4. Rescreva os autores e branches usando o arquivo CSV:
- ```shell
- $ git-import-rewrite --flavor svn --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git
- ```
-5. Caso ainda não tenha feito isso, [crie um repositório vazio no {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository).
-{% data reusables.command_line.switching_directories_procedural %}
-7. Faça push do repositório importado para o {% data variables.product.prodname_ghe_server %}:
- ```shell
- $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE
- ```
-
-### Importar projetos do Team Foundation
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. Faça um clone bruto do projeto usando o comando abaixo. Especifique a URL do projeto de origem e um caminho para um repositório temporário:
- ```shell
- $ git-import-tfs-raw TEAM-FOUNDATION-CLONE-URL /PATH/REPO-NAME.git
- # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
- ```
-{% data reusables.enterprise_migrations.review-the-import-csv %}
-4. Rescreva os autores e branches usando o arquivo CSV:
- ```shell
- $ git-import-rewrite --flavor tfs --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git
- ```
-5. Caso ainda não tenha feito isso, [crie um repositório vazio no {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository).
-{% data reusables.command_line.switching_directories_procedural %}
-7. Faça push do repositório importado para o {% data variables.product.prodname_ghe_server %}:
- ```shell
- $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE
- ```
-
-### Leia mais
-
-- "[Command-line-utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#import-and-export)"
diff --git a/translations/pt-BR/content/admin/migrations/importing-migration-data-to-github-enterprise-server.md b/translations/pt-BR/content/admin/migrations/importing-migration-data-to-github-enterprise-server.md
deleted file mode 100644
index 2721e151627c..000000000000
--- a/translations/pt-BR/content/admin/migrations/importing-migration-data-to-github-enterprise-server.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Importar dados de migração para o GitHub Enterprise Server
-intro: 'Após gerar um arquivo de migração, você poderá importar os dados para a sua instância de destino do {% data variables.product.prodname_ghe_server %}. Antes de aplicar as alterações permanentemente na instância de destino, será possível revisá-las para resolver possíveis conflitos.'
-redirect_from:
- - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise/
- - /enterprise/admin/migrations/importing-migration-data-to-github-enterprise-server
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/migrations/index.md b/translations/pt-BR/content/admin/migrations/index.md
deleted file mode 100644
index 16e103d94c05..000000000000
--- a/translations/pt-BR/content/admin/migrations/index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: 'Migrar dados de usuário, organização e repositório'
-shortTitle: Migrando dados
-intro: 'É possível exportar dados de usuário, organização e repositório de {% data variables.product.prodname_ghe_server %} ou {% data variables.product.prodname_dotcom_the_website %}, e depois importar esses dados para o {% data variables.product.product_location_enterprise %}.'
-redirect_from:
- - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/
- - /enterprise/admin/categories/migrations-and-upgrades/
- - /enterprise/admin/migrations
-versions:
- enterprise-server: '*'
----
-
-
-### Índice
-
-{% topic_link_in_list /overview %}
- {% link_in_list /about-migrations %}
-{% topic_link_in_list /exporting-migration-data-from-github-enterprise-server %}
- {% link_in_list /preparing-the-github-enterprise-server-source-instance %}
- {% link_in_list /exporting-the-github-enterprise-server-source-repositories %}
-{% topic_link_in_list /exporting-migration-data-from-githubcom %}
- {% link_in_list /preparing-the-githubcom-source-organization %}
- {% link_in_list /exporting-the-githubcom-organizations-repositories %}
-{% topic_link_in_list /importing-migration-data-to-github-enterprise-server %}
- {% link_in_list /preparing-the-migrated-data-for-import-to-github-enterprise-server %}
- {% link_in_list /generating-a-list-of-migration-conflicts %}
- {% link_in_list /reviewing-migration-conflicts %}
- {% link_in_list /resolving-migration-conflicts-or-setting-up-custom-mappings %}
- {% link_in_list /applying-the-imported-data-on-github-enterprise-server %}
- {% link_in_list /reviewing-migration-data %}
- {% link_in_list /completing-the-import-on-github-enterprise-server %}
- {% link_in_list /importing-data-from-third-party-version-control-systems %}
diff --git a/translations/pt-BR/content/admin/migrations/overview.md b/translations/pt-BR/content/admin/migrations/overview.md
deleted file mode 100644
index 10d3ff6e76b0..000000000000
--- a/translations/pt-BR/content/admin/migrations/overview.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Visão Geral
-intro: 'Saiba mais sobre a migração de dados para {% data variables.product.product_location_enterprise %}.'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/migrations/overview
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/migrations/preparing-the-github-enterprise-server-source-instance.md b/translations/pt-BR/content/admin/migrations/preparing-the-github-enterprise-server-source-instance.md
deleted file mode 100644
index 8a7975454327..000000000000
--- a/translations/pt-BR/content/admin/migrations/preparing-the-github-enterprise-server-source-instance.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Preparar a instância de origem do GitHub Enterprise Server
-intro: 'Antes de migrar os dados do {% data variables.product.prodname_ghe_server %}, verifique se você tem a autenticação e o acesso administrativo adequados à instância.'
-redirect_from:
- - /enterprise/admin/guides/migrations/preparing-the-github-enterprise-source-instance/
- - /enterprise/admin/migrations/preparing-the-github-enterprise-server-source-instance
-versions:
- enterprise-server: '*'
----
-
-1. Verifique se você é administrador do site na origem do {% data variables.product.prodname_ghe_server %}. A melhor maneira de fazer isso é verificar se você consegue fazer [SSH na instância](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/).
-
-2. {% data reusables.enterprise_migrations.token-generation %} na instância de origem do {% data variables.product.prodname_ghe_server %}.
-
-{% data reusables.enterprise_migrations.make-a-list %}
diff --git a/translations/pt-BR/content/admin/migrations/preparing-the-githubcom-source-organization.md b/translations/pt-BR/content/admin/migrations/preparing-the-githubcom-source-organization.md
deleted file mode 100644
index 8ffafc887cad..000000000000
--- a/translations/pt-BR/content/admin/migrations/preparing-the-githubcom-source-organization.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Preparar a organização de origem do GitHub.com
-intro: 'Antes de migrar os repositórios de uma organização do {% data variables.product.prodname_dotcom_the_website %}, verifique se você tem a autenticação e o acesso administrativo adequados à instância.'
-redirect_from:
- - /enterprise/admin/guides/migrations/preparing-the-github-com-source-organization
- - /enterprise/admin/migrations/preparing-the-githubcom-source-organization
-versions:
- enterprise-server: '*'
----
-
-1. Verifique se você tem [permissões de proprietário](/articles/permission-levels-for-an-organization/) nos repositórios de origem da organização.
-
-2. {% data reusables.enterprise_migrations.token-generation %} no {% data variables.product.prodname_dotcom_the_website %}.
-
-{% data reusables.enterprise_migrations.make-a-list %}
diff --git a/translations/pt-BR/content/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server.md b/translations/pt-BR/content/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server.md
deleted file mode 100644
index 6fe76a82e663..000000000000
--- a/translations/pt-BR/content/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Preparar os dados migrados para a importação no GitHub Enterprise Server
-intro: 'Antes de aplicar os dados migrados à sua instância de destino, você terá que copiar o arquivo de migração para a instância de destino e prepará-lo para importação.'
-redirect_from:
- - /enterprise/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise/
- - /enterprise/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
-1. Usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copie o arquivo de migração gerado na organização ou instância de origem para o destino no {% data variables.product.prodname_ghe_server %}:
-
- ```shell
- $ scp -P 122 /path/to/archive/MIGRATION_GUID.tar.gz admin@hostname:/home/admin/
- ```
-
-{% data reusables.enterprise_installation.ssh-into-target-instance %}
-
-3. Use o comando `ghe-migrator prepare` para preparar o arquivo para importação na instância de destino e gerar um novo GUID de Migração para uso nas etapas subsequentes:
-
- ```shell
- ghe-migrator prepare /home/admin/MIGRATION_GUID.tar.gz
- ```
-
- * Para começar uma nova tentativa de importação, execute o comando `ghe-migrator` novamente e obtenha um novo GUID de Migração.
- * {% data reusables.enterprise_migrations.specify-staging-path %}
diff --git a/translations/pt-BR/content/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings.md b/translations/pt-BR/content/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings.md
deleted file mode 100644
index 2c43ec4a3444..000000000000
--- a/translations/pt-BR/content/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Resolver conflitos de migração ou configurar mapeamentos personalizados
-intro: 'Antes de importar os dados de migração, você pode fazer correções para resolver conflitos, renomear registros recebidos ou mapear os registros recebidos para registros existentes.'
-redirect_from:
- - /enterprise/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings
-versions:
- enterprise-server: '*'
----
-
-É possível usar as etapas a seguir para resolver conflitos ou adicionar mapeamentos personalizados à sua migração.
-
-### Resolver conflitos
-
-Se achar que o `ghe-migrator` fará uma alteração incorreta, você poderá fazer correções alterando os dados em *conflicts.csv*. Você pode alterar qualquer linha no arquivo *conflicts.csv*.
-
-Por exemplo, digamos que você perceba que o usuário `octocat` da origem está sendo mapeado para `octocat` no destino:
-
-| `nome_modelo` | `url_origem` | `url_destino` | `ação_recomendada` |
-| ------------- | ----------------------------------- | ----------------------------------- | ------------------ |
-| `usuário` | `https://exemplo-gh.source/octocat` | `https://exemplo-gh.target/octocat` | `map` |
-
-Você pode optar por mapear o usuário para outro usuário no destino. Suponha que você saiba que `octocat` deveria ser `monalisa` no destino. É possível alterar a coluna `url_destino` no arquivo *conflicts.csv* para se referir a `monalisa`:
-
-| `nome_modelo` | `url_origem` | `url_destino` | `ação_recomendada` |
-| ------------- | ----------------------------------- | ------------------------------------ | ------------------ |
-| `usuário` | `https://exemplo-gh.source/octocat` | `https://exemplo-gh.target/monalisa` | `map` |
-
-Em outra situação, se você quiser renomear o repositório `octo-org/widgets` como `octo-org/amazing-widgets` na instância de destino, altere `url_destino` para `octo-org/amazing-widgets` e `ação_recomendada` para `rename`:
-
-| `nome_modelo` | `url_origem` | `url_destino` | `ação_recomendada` |
-| ------------- | -------------------------------------------- | ---------------------------------------------------- | ------------------ |
-| `repositório` | `https://exemplo-gh.source/octo-org/widgets` | `https://exemplo-gh.target/octo-org/amazing-widgets` | `rename` |
-
-### Adicionar mapeamentos personalizados
-
-Uma situação comum durante as migrações é o cenário em que os usuários migrados têm nomes de usuários diferentes no destino e na origem.
-
-Com uma lista de nomes de usuários da origem e uma lista de nomes de usuários do destino, você pode criar um arquivo CSV com mapeamentos personalizados e aplicá-la para garantir que o nome de usuário e o conteúdo de cada usuário sejam atribuídos corretamente no fim da migração.
-
-Você pode gerar um arquivo em formato CSV dos usuários que estão sendo migrados para aplicar mapeamentos personalizados usando o comando [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data):
-
-```shell
-$ ghe-migrator audit -m user -g MIGRATION_GUID > users.csv
-```
-
-Agora você pode editar esse CSV, inserir a nova URL para cada usuário que pretende mapear ou renomear e atualizar a quarta coluna para aplicar `map` ou `rename`.
-
-Por exemplo, para renomear o usuário `octocat` como `monalisa` no destino `https://example-gh.target`, você deveria criar uma linha com o seguinte conteúdo:
-
-| `nome_modelo` | `url_origem` | `url_destino` | `estado` |
-| ------------- | ----------------------------------- | ------------------------------------ | -------- |
-| `usuário` | `https://exemplo-gh.source/octocat` | `https://exemplo-gh.target/monalisa` | `rename` |
-
-O mesmo processo pode ser usado para criar mapeamentos em cada registro compatível com mapeamentos personalizados. Para obter mais informações, consulte a nossa [tabela com as possibilidades de mapeamento em registros](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type).
-
-### Aplicar dados de migração modificados
-
-1. Depois de fazer as alterações, use o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) para aplicar seu arquivo *conflicts.csv* modificado (ou qualquer outro csv de mapeamento no formato correto) à instância de destino:
-
- ```shell
- $ scp -P 122 ~/Desktop/conflicts.csv admin@hostname:/home/admin/
- ```
-
-2. Remapeie os dados de migração usando o comando `ghe-migrator map`, passando pelo caminho do seu arquivo csv modificado e do GUID de Migração:
-
- ```shell
- $ ghe-migrator map -i conflicts.csv -g MIGRATION_GUID
- ```
-
-3. Se o comando `ghe-migrator map -i conflicts.csv -g MIGRATION_GUID` ainda reportar conflitos, execute o processo de resolução de conflitos de migração novamente.
diff --git a/translations/pt-BR/content/admin/migrations/reviewing-migration-conflicts.md b/translations/pt-BR/content/admin/migrations/reviewing-migration-conflicts.md
deleted file mode 100644
index be645c83d0b4..000000000000
--- a/translations/pt-BR/content/admin/migrations/reviewing-migration-conflicts.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Revisar conflitos de migração
-intro: 'Depois de gerar uma lista de conflitos de migração, revise-os para garantir que você concorda com as ações padrão que o `ghe-migrator` vai executar para resolvê-los.'
-redirect_from:
- - /enterprise/admin/migrations/reviewing-migration-conflicts
-versions:
- enterprise-server: '*'
----
-
-1. Usando o editor de texto ou um [software de planilha compatível com CSV](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support), abra o arquivo *conflicts.csv*.
-2. Seguindo os exemplos e tabelas de referência abaixo, revise o arquivo *conflicts.csv* para garantir a execução das ações adequadas na importação.
-
-O arquivo *conflicts.csv* contém um *mapa de migração* de conflitos e ações recomendadas. O mapa de migração lista quais dados estão sendo migrados da origem e como eles serão aplicados ao destino.
-
-| `nome_modelo` | `url_origem` | `url_destino` | `ação_recomendada` |
-| -------------- | ------------------------------------------------------ | ------------------------------------------------------ | ------------------ |
-| `usuário` | `https://exemplo-gh.source/octocat` | `https://exemplo-gh.target/octocat` | `map` |
-| `organization` | `https://exemplo-gh.source/octo-org` | `https://exemplo-gh.target/octo-org` | `map` |
-| `repositório` | `https://exemplo-gh.source/octo-org/widgets` | `https://exemplo-gh.target/octo-org/widgets` | `rename` |
-| `equipe` | `https://exemplo-gh.source/orgs/octo-org/teams/admins` | `https://exemplo-gh.target/orgs/octo-org/teams/admins` | `merge` |
-
-Cada linha do arquivo *conflicts.csv* mostra as seguintes informações:
-
-| Nome | Descrição |
-| -------------------- | ------------------------------------------------------------------------- |
-| `model_name` | Tipo de dado que está sendo alterado. |
-| `source_url` | URL de origem dos dados. |
-| `target_url` | URL esperada de destino dos dados. |
-| `recommended_action` | Ação preferencial que o `ghe-migrator` vai executar ao importar os dados. |
-
-### Mapeamentos possíveis para cada tipo de registro
-
-O `ghe-migrator` pode executar várias ações de mapeamento diferentes quando transfere os dados:
-
-| `Ação` | Descrição | Modelos aplicáveis |
-| --------------- | ------------------------------------------------------------------------------------- | ------------------------------------ |
-| `import` | (padrão) Os dados da origem são importados para o destino. | Todos os tipos de registro |
-| `map` | Os dados da origem são substituídos pelos dados existentes no destino. | Usuários, organizações, repositórios |
-| `rename` | Os dados da origem são renomeados e copiados para o destino. | Usuários, organizações, repositórios |
-| `map_or_rename` | Se houver destino, mapeie para o destino. Se não houver, renomeie o modelo importado. | Usuários |
-| `merge` | Os dados da origem são combinados com os dados existentes no destino. | Equipes |
-
-**É altamente recomendável que você revise o arquivo *conflicts.csv* e faça a [`auditoria do ghe-migrator`](/enterprise/admin/guides/migrations/reviewing-migration-data) para confirmar a execução das ações adequadas.** Se tudo estiver bem, você poderá continuar para a seção "[Aplicar os dados importados no {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)".
diff --git a/translations/pt-BR/content/admin/migrations/reviewing-migration-data.md b/translations/pt-BR/content/admin/migrations/reviewing-migration-data.md
deleted file mode 100644
index 20753ad00c59..000000000000
--- a/translations/pt-BR/content/admin/migrations/reviewing-migration-data.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Revisar dados de migração
-intro: 'Depois de cada etapa da migração, você pode revisar o estado dos dados migrados. Será possível garantir que os registros estejam sendo mapeados ou renomeados corretamente, obter as novas URLs dos registros após a etapa de importação e listar todos os registros que não foram migrados.'
-redirect_from:
- - '/enterprise/{{ currentVersion }}/admin/guides/migrations/reviewing-the-imported-data/'
- - /enterprise/admin/migrations/reviewing-migration-data
-versions:
- enterprise-server: '*'
----
-
-Por padrão, o `ghe-migrator audit` devolve todos os registros. Também é possível filtrar os registros por:
-
- * Tipos de registro;
- * Estado de registro.
-
-Os tipos de registro correspondem aos encontrados nos [dados migrados](/enterprise/admin/guides/migrations/about-migrations/#migrated-data).
-
-### Filtros por tipo de registro
-
-| Tipo de registro | Nome do filtro |
-| --------------------------------------------- | ----------------------------- |
-| Usuários | `user` |
-| Organizações | `organization` |
-| Repositórios | `repository` |
-| Equipes | `equipe` |
-| Marcos | `milestone` |
-| Quadros de projeto | `project` |
-| Problemas | `issue` |
-| Comentários dos problemas | `issue_comment` |
-| Pull requests | `pull_request` |
-| Revisões de pull request | `pull_request_review` |
-| Comentários de commit | `commit_comment` |
-| Comentários das revisões de pull request | `pull_request_review_comment` |
-| Versões | `release` |
-| Ações feitas em problemas ou em pull requests | `issue_event` |
-| Branches protegidos | `protected_branch` |
-
-### Filtros por estado de registro
-
-| Estado de registro | Descrição |
-| ------------------ | --------------------------------------- |
-| `export` | O registro será exportado. |
-| `import` | O registro será importado. |
-| `map` | O registro será mapeado. |
-| `rename` | O registro será renomeado. |
-| `merge` | O registro passará por merge. |
-| `exported` | O registro foi exportado com êxito. |
-| `imported` | O registro foi importado com êxito. |
-| `mapped` | O registro foi mapeado com êxito. |
-| `renamed` | O registro foi renomeado com êxito. |
-| `merged` | O registro passou por merge com êxito. |
-| `failed_export` | Houve falha ao exportar o registro. |
-| `failed_import` | Houve falha ao importar o registro. |
-| `failed_map` | Houve falha ao mapear o registro. |
-| `failed_rename` | Houve falha ao renomear o registro. |
-| `failed_merge` | Houve falha ao fazer merge no registro. |
-
-### Filtrar registros auditados
-
-Com o comando `ghe-migrator audit`, é possível filtrar com base no tipo de registro usando o sinalizador `-m`. Da mesma forma, você pode filtrar no estado de importação usando o sinalizador `-s`. O comando fica parecido com o seguinte:
-
-```shell
-$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION_GUID
-```
-
-Por exemplo, para visualizar todas as organizações e equipes importadas com êxito, você digitaria:
-```shell
-$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION_GUID
-> model_name,source_url,target_url,state
-> organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed
-```
-
-**É altamente recomendável fazer auditoria em todas as importações que tiveram falha.** Para fazer isso, insira:
-```shell
-$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION_GUID
-> model_name,source_url,target_url,state
-> user,https://gh.source/octocat,https://gh.target/octocat,failed
-> repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed
-```
-
-Em caso de problemas com falhas na importação, entre em contato com o {% data variables.contact.contact_ent_support %}.
diff --git a/translations/pt-BR/content/admin/user-management/about-global-webhooks.md b/translations/pt-BR/content/admin/user-management/about-global-webhooks.md
deleted file mode 100644
index ebd7663e90d5..000000000000
--- a/translations/pt-BR/content/admin/user-management/about-global-webhooks.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Sobre webhooks globais
-intro: Os webhooks globais enviam notificações sobre eventos no nível da instância.
-redirect_from:
- - /enterprise/admin/user-management/about-global-webhooks
-versions:
- enterprise-server: '*'
----
-
-Você pode usar webhooks globais para monitorar, responder ou impor regras automaticamente para o gerenciamento de usuários e de organizações na sua instância. Por exemplo, você pode configurar os webhooks para serem executados sempre que:
-- Uma conta de usuário for criada ou excluída;
-- Uma organização for criada ou excluída;
-- Um colaborador for adicionado ou removido de um repositório;
-- Um repositório tiver bifurcação.
-
-![Lista de webhooks globais](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
-
-Para obter mais informações sobre como configurar webhooks, consulte "[Gerenciar webhooks globais](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-global-webhooks)".
-
-{% data reusables.enterprise_user_management.manage-global-webhooks-api %}
diff --git a/translations/pt-BR/content/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories.md b/translations/pt-BR/content/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories.md
deleted file mode 100644
index 9e9a0469a4bc..000000000000
--- a/translations/pt-BR/content/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Permitir que administradores habilitem o acesso de leitura anônimo do Git a repositórios públicos
-intro: 'Para simplificar o funcionamento das ferramentas personalizadas na sua instância e ignorar os requisitos de autenticação, você pode permitir que os administradores de repositório habilitem o acesso de leitura anônimo do Git a repositórios públicos na {% data variables.product.product_location_enterprise %}.'
-redirect_from:
- - /enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
-
-Se o modo privado estiver habilitado, você poderá permitir que os administradores de repositório habilitem o acesso de leitura anônimo do Git a repositórios públicos na {% data variables.product.product_location_enterprise %}. Para obter mais informações sobre o modo privado, consulte "[Habilitar modo privado](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-private-mode/)".
-
-Conceder o acesso de leitura anônimo do Git permite ignorar a autenticação de ferramentas personalizadas na sua instância. Quando você ou um administrador de repositório habilitar essa configuração de acesso em um repositório, as operações não autenticadas do Git (e qualquer pessoa com acesso de rede ao {% data variables.product.prodname_ghe_server %}) terão acesso de leitura sem autenticação ao repositório.
-
-Você também pode impedir que os administradores do repositório alterem as configurações de acesso anônimo do Git a todos os repositórios ou a um repositório específico na {% data variables.product.product_location_enterprise %}. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)".
-
-{% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
-
-{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-4. Em "Anonymous Git read access" (Acesso de leitura anônimo do Git), use o menu suspenso e clique em **Enabled** (Habilitado). ![Menu suspenso de acesso de leitura anônimo do Git com as opções "Enabled" (Habilitado) e "Disabled" (Desabilitado)
-](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
-3. Para impedir que os administradores de repositório alterem as configurações de acesso de leitura anônimo do Git em todos os repositórios da instância, você também pode selecionar **Prevent repository admins from changing anonymous Git read access** (Impedir administradores de repositório de alterarem o acesso de leitura anônimo do Git). ![Marcar a caixa de seleção para impedir que administradores de repositório alterem as configurações de acesso de leitura anônimo do Git em todos os repositórios da instância](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
-
-### Habilitar o acesso de leitura anônimo do Git a determinado repositório
-
-{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-6. Em "Danger Zone" (Zona de perigo), ao lado de "Enable anonymous Git read access" (Habilitar acesso de leitura anônimo do Git), clique em **Enable** (Habilitar). ![Botão "Enabled" (Habilitado) na opção "Enable anonymous Git read access" (Habilitar acesso de leitura anônimo do Git) na zona de perigo das configurações de administração do site ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
-7. Revise as alterações. Para confirmar, clique em **Yes, enable anonymous Git read access** (Sim, permitir acesso de leitura anônimo ao Git). ![Confirmar configuração de acesso de leitura anônimo do Git na janela pop-up](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
-8. Para impedir que os administradores de repositório alterem a configuração nesse repositório, você também pode selecionar **Prevent repository admins from changing anonymous Git read access** (Impedir administradores de repositório de alterarem o acesso de leitura anônimo do Git). ![Marcar a caixa de seleção para impedir que administradores de repositório alterem as configurações de acesso de leitura anônimo do Git em todos os repositórios da instância](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
diff --git a/translations/pt-BR/content/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/pt-BR/content/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
deleted file mode 100644
index 85059843ff67..000000000000
--- a/translations/pt-BR/content/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Permitir a autenticação integrada para usuários de fora do provedor de identidade
-intro: 'Com a autenticação integrada, você pode autenticar usuários que não têm acesso ao seu provedor de identidade que usa LDAP, SAML ou CAS.'
-redirect_from:
- - /enterprise/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider
-versions:
- enterprise-server: '*'
----
-
-### Sobre a autenticação integrada para usuários de fora do provedor de identidade
-
-É possível usar a autenticação integrada para usuários externos quando você não conseguir adicionar contas específicas ao seu provedor de identidade (IdP), como contas de contratados ou usuários de máquinas. Você também pode usar a autenticação integrada para acessar uma conta de fallback se o provedor de identidade não estiver disponível.
-
-Após a configuração da autenticação integrada, quando um usuário se autenticar com êxito via SAML ou CAS, ele não poderá se autenticar com nome de usuário e senha. Se o usuário se autenticar com êxito via LDAP, as credenciais não serão mais consideradas internas.
-
-A autenticação integrada para um IdP específico fica desabilitada por padrão.
-
-{% warning %}
-
-**Aviso:** se desabilitar a autenticação integrada, você terá que suspender individualmente todos os usuários que não devem mais ter acesso à instância. Para obter mais informações, consulte "[Suspender e cancelar a suspensão de usuários](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)".
-
-{% endwarning %}
-
-### Configurar a autenticação integrada para usuários de fora do provedor de identidade
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-4. Selecione seu provedor de identidade. ![Opção Select identity provider (Selecionar provedor de identidade)
-](/assets/images/enterprise/management-console/identity-provider-select.gif)
-5. Selecione **Allow creation of accounts with built-in authentication** (Permitir a criação de contas com autenticação integrada). ![Opção Select built-in authentication (Selecionar autenticação integrada)](/assets/images/enterprise/management-console/built-in-auth-identity-provider-select.png)
-6. Leia o aviso e clique em **Ok**.
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.2fa_is_available %}
-
-### Convidar usuários de fora do provedor de identidade para autenticação na sua instância
-
-Quando aceitar o convite, o usuário poderá fazer login com seu próprio nome de usuário e senha, em vez de fazer login via IdP.
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %}
-{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %}
-
-### Leia mais
-
-- [Usar LDAP](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap)
-- [Usar SAML](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-saml)
-- [Usar CAS](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-cas)
diff --git a/translations/pt-BR/content/admin/user-management/archiving-and-unarchiving-repositories.md b/translations/pt-BR/content/admin/user-management/archiving-and-unarchiving-repositories.md
deleted file mode 100644
index 537f3a1ea78c..000000000000
--- a/translations/pt-BR/content/admin/user-management/archiving-and-unarchiving-repositories.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Arquivar e cancelar o arquivamento de repositórios
-intro: 'Como administrador do site, você pode arquivar e cancelar o arquivamento de repositórios no painel de administração.'
-redirect_from:
- - /enterprise/admin/articles/archiving-and-unarchiving-repositories/
- - /enterprise/admin/user-management/archiving-and-unarchiving-repositories
-versions:
- enterprise-server: '*'
----
-
-### Arquivar um repositório
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Em Danger Zone (Zona de perigo), clique em **Archive** (Arquivar). ![Botão Archive (Arquivar)](/assets/images/enterprise/site-admin-settings/repo-archive.png)
-6. Clique em **Archive Repository** (Arquivar repositório). ![Botão Archive repository (Arquivar repositório)](/assets/images/enterprise/site-admin-settings/repo-archive-confirm.png)
-
-### Cancelar o arquivamento de um repositório
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Em Danger Zone (Zona de perigo), clique em **Unarchive** (Cancelar o arquivamento). ![Botão Archive (Arquivar)](/assets/images/enterprise/site-admin-settings/repo-unarchive.png)
-6. Clique em **Unarchive Repository** (Cancelar o arquivamento do repositório). ![Botão Archive repository (Arquivar repositório)](/assets/images/enterprise/site-admin-settings/repo-unarchive-confirm.png)
-
-### Leia mais
-- [Sobre o arquivamento de repositórios](/enterprise/{{ currentVersion }}/user/articles/about-archiving-repositories)
diff --git a/translations/pt-BR/content/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance.md b/translations/pt-BR/content/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance.md
deleted file mode 100644
index b448120e1272..000000000000
--- a/translations/pt-BR/content/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Autenticar usuários para a instância do GitHub Enterprise Server
-intro: 'Você pode usar a autenticação integrada do {% data variables.product.prodname_ghe_server %} ou escolher entre CAS, LDAP ou SAML para integrar suas contas e gerenciar centralmente o acesso dos usuários à {% data variables.product.product_location_enterprise %}.'
-redirect_from:
- - /enterprise/admin/categories/authentication/
- - /enterprise/admin/guides/installation/user-authentication/
- - /enterprise/admin/articles/inviting-users/
- - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance/
- - /enterprise/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/user-management/basic-account-settings.md b/translations/pt-BR/content/admin/user-management/basic-account-settings.md
deleted file mode 100644
index f9c86484cd01..000000000000
--- a/translations/pt-BR/content/admin/user-management/basic-account-settings.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Configurações básicas de conta
-intro: 'Depois que conseguirem se autenticar na {% data variables.product.product_location_enterprise %}, os usuários vão querer definir algumas configurações básicas de perfil, como avatar e notificações de e-mail.'
-redirect_from:
- - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/
- - /enterprise/admin/user-management/basic-account-settings
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/user-management/changing-authentication-methods.md b/translations/pt-BR/content/admin/user-management/changing-authentication-methods.md
deleted file mode 100644
index f6021be031b2..000000000000
--- a/translations/pt-BR/content/admin/user-management/changing-authentication-methods.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Alterar os métodos de autenticação
-intro: 'A qualquer momento, você pode alterar a forma como o {% data variables.product.prodname_ghe_server %} se autentica com as contas existentes.'
-redirect_from:
- - /enterprise/admin/user-management/changing-authentication-methods
-versions:
- enterprise-server: '*'
----
-
-As contas de usuário no {% data variables.product.product_location_enterprise %} são preservadas quando você altera o método de autenticação, e os usuários continuarão fazendo login na mesma conta (desde que não haja alteração nos nomes de usuário).
-
-Se o novo método de autenticação alterar nomes de usuários, serão criadas novas contas. Como administrador, você pode renomear os usuários nas configurações de administração do site ou usando a [a API de administração do usuário](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user).
-
-Veja outras questões que você deve manter em mente:
-
-* **Senhas:** se você mudar para o uso da autenticação integrada na sua instância, os usuários deverão [definir uma senha](/enterprise/user/articles/how-can-i-reset-my-password/) após a conclusão da mudança.
-
-* **Administradores do site:** privilégios administrativos são [controlados pelo provedor de identidade quando você usa SAML](/enterprise/admin/guides/user-management/using-saml/#saml-attributes) e podem ser [controlados pela associação ao grupo quando você usa LDAP](/enterprise/admin/guides/user-management/using-ldap/#configuring-ldap-with-your-github-enterprise-server-instance).
-
-* **Associação a equipes:** somente o LDAP permite [controlar associações a equipes](/enterprise/admin/guides/user-management/using-ldap/#configuring-ldap-with-your-github-enterprise-server-instance) no servidor do diretório.
-
-* **Suspensão de usuários:** quando você usa o LDAP para fazer a autenticação, o acesso ao {% data variables.product.prodname_ghe_server %} pode ser controlado pelos _grupos restritos_. Depois de alternar para o LDAP, se os grupos restritos estiverem configurados, os usuários que não estiverem nesses grupos serão suspensos. A suspensão ocorrerá quando eles fizerem login ou durante a próxima sincronização LDAP.
-
-* **Associação a grupos:** quando você usa o LDAP para fazer a autenticação, os usuários passam automaticamente por [suspensão e cancelamento de suspensão](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) com base em associações a grupos restritos e no status da conta no Active Directory.
-
-* **Autenticação do Git:** o SAML e o CAS dão suporte à autenticação do Git somente em HTTP ou HTTPS usando um [token de acesso pessoal](/articles/creating-an-access-token-for-command-line-use). Não há suporte para a autenticação de senha em HTTP ou HTTPS. Por padrão, o LDAP dá suporte à autenticação do Git com base em senha, mas é recomendável [desabilitar esse método](/enterprise/admin/guides/user-management/using-ldap/#disabling-password-authentication-for-git-operations) e forçar a autenticação via token de acesso pessoal ou chave SSH.
-
-* **Autenticação de API:** o SAML e o CAS dão suporte à autenticação de API somente usando um [token de acesso pessoal](/articles/creating-an-access-token-for-command-line-use). Não há suporte para a autenticação básica.
-
-* **Autenticação de dois fatores:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %}
-
-* **Autenticação integrada para usuários de fora do provedor de identidade:** você pode convidar os usuários para se autenticarem na {% data variables.product.product_location_enterprise %} sem adicioná-los ao seu provedor de identidade. Para obter mais informações, consulte "[Permitir a autenticação integrada para usuários de fora do provedor de identidade](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider)".
diff --git a/translations/pt-BR/content/admin/user-management/disabling-unauthenticated-sign-ups.md b/translations/pt-BR/content/admin/user-management/disabling-unauthenticated-sign-ups.md
deleted file mode 100644
index f69d07b616b4..000000000000
--- a/translations/pt-BR/content/admin/user-management/disabling-unauthenticated-sign-ups.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Desabilitar assinaturas não autenticadas
-redirect_from:
- - /enterprise/admin/articles/disabling-sign-ups/
- - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups
-intro: 'Se você estiver usando a autenticação integrada, será possível impedir que pessoas não autenticadas criem uma conta.'
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-3. Desmarque a seleção na caixa **Enable sign-up** (Habilitar assinatura). ![Caixa de seleção Enable sign-up (Habilitar assinatura)](/assets/images/enterprise/management-console/enable-sign-up.png)
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/pt-BR/content/admin/user-management/organizations-and-teams.md b/translations/pt-BR/content/admin/user-management/organizations-and-teams.md
deleted file mode 100644
index 7b372fd172a9..000000000000
--- a/translations/pt-BR/content/admin/user-management/organizations-and-teams.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Organizações e equipes
-redirect_from:
- - /enterprise/admin/articles/adding-users-and-teams/
- - /enterprise/admin/categories/admin-bootcamp/
- - /enterprise/admin/user-management/organizations-and-teams
-intro: 'As organizações são uma forma excelente de criar conjuntos distintos de usuários na empresa, como divisões ou grupos que trabalham em projetos semelhantes. Os repositórios públicos de uma organização ficam acessíveis para os usuários de outras organizações, enquanto os repositórios privados são inacessíveis para qualquer pessoa que não seja integrante da organização.'
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/user-management/preventing-users-from-changing-a-repositorys-visibility.md b/translations/pt-BR/content/admin/user-management/preventing-users-from-changing-a-repositorys-visibility.md
deleted file mode 100644
index 6548bb8e26ed..000000000000
--- a/translations/pt-BR/content/admin/user-management/preventing-users-from-changing-a-repositorys-visibility.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Impedir os usuários de alterarem a visibilidade do repositório
-intro: 'É possível impedir que os usuários alterem a visibilidade dos repositórios pertencentes à organização no seu appliance do {% data variables.product.prodname_ghe_server %}.'
-redirect_from:
- - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility
- - /enterprise/admin/user-management/preventing-users-from-changing-a-repositorys-visibility
-versions:
- enterprise-server: '*'
----
-
-Se você impedir que os integrantes alterem a visibilidade do repositório, somente os administradores do site poderão tornar privados os repositórios públicos ou tornar públicos os repositórios privados.
-
-Se um administrador do site tiver restringido a criação do repositório somente aos proprietários da organização, os integrantes não poderão alterar a visibilidade do repositório. Além disso, se o administrador do site restringir a criação de repositórios apenas aos repositórios privados, os integrantes só conseguirão tornar privados os repositórios públicos. Para obter mais informações, consulte "[Restringir a criação de repositórios na instância](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)".
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.policies-tab %}
-{% data reusables.enterprise-accounts.repositories-tab %}
-5. Em "Repository visibility change" (Alteração da visibilidade do repositório), revise as informações sobre a alteração da configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-
-{% data reusables.enterprise-accounts.repository-visibility-policy %}
diff --git a/translations/pt-BR/content/admin/user-management/preventing-users-from-changing-anonymous-git-read-access.md b/translations/pt-BR/content/admin/user-management/preventing-users-from-changing-anonymous-git-read-access.md
deleted file mode 100644
index 17c16a3e268e..000000000000
--- a/translations/pt-BR/content/admin/user-management/preventing-users-from-changing-anonymous-git-read-access.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Impedir os usuários de alterarem o acesso de leitura anônimo do Git
-intro: 'Você pode impedir que os administradores de repositórios alterem o acesso de leitura anônimo do Git a um repositório{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.14" %} ou a todos os repositórios{% endif %}.'
-redirect_from:
- - /enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access-to-a-repository/
- - /enterprise/admin/user-management/preventing-users-from-changing-anonymous-git-read-access
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
-
-Para impedir que os administradores de repositório alterem as configurações de acesso de leitura anônimo do Git em determinado repositório, é possível bloquear as configurações de acesso do repositório. Após o bloqueio, somente um administrador de site poderá alterar a configuração do acesso de leitura anônimo do Git.
-
-Os administradores de repositório poderão alterar a configuração do acesso de leitura anônimo do Git de um repositório público se não for uma bifurcação. Para obter mais informações, consulte "[Permitir que administradores habilitem o acesso de leitura anônimo do Git a repositórios públicos](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)".
-
-{% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
-
-### Impedir os usuários de alterarem o acesso de leitura anônimo do Git no repositório
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-6. Em "Danger Zone" (Zona de perigo), selecione **Prevent repository admins from enabling anonymous Git read access** (Impedir administradores de repositório de habilitarem o acesso de leitura anônimo do Git). ![Marcar a caixa de seleção para impedir o repositório de alterar a configuração de acesso de leitura anônimo do Git](/assets/images/enterprise/site-admin-settings/lock-repo-from-changing-anonymous-git-read-access.png)
-
-### Impedir os usuários de alterarem o acesso de leitura anônimo do Git em todos os repositórios
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-3. Em "Anonymous Git read access" (Acesso de leitura anônimo do Git), confirme que a configuração está habilitada e selecione **Prevent repository admins from changing anonymous Git read access** (Impedir administradores de repositório de habilitarem o acesso de leitura anônimo do Git). ![Marcar a caixa de seleção para impedir todos os repositórios de alterarem a configuração de acesso de leitura anônimo do Git](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
-
diff --git a/translations/pt-BR/content/admin/user-management/preventing-users-from-deleting-organization-repositories.md b/translations/pt-BR/content/admin/user-management/preventing-users-from-deleting-organization-repositories.md
deleted file mode 100644
index f4557a28fc0d..000000000000
--- a/translations/pt-BR/content/admin/user-management/preventing-users-from-deleting-organization-repositories.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Impedir os usuários de excluírem repositórios da organização
-intro: 'É possível impedir que os usuários excluam ou transfiram repositórios em organizações no seu appliance do {% data variables.product.prodname_ghe_server %}.'
-redirect_from:
- - /enterprise/admin/user-management/preventing-users-from-deleting-organization-repositories
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.policies-tab %}
-{% data reusables.enterprise-accounts.repositories-tab %}
-5. Em "Repository deletion and transfer" (Exclusão e transferência de repositórios), revise as informações sobre como alterar as configurações. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-
-{% data reusables.enterprise-accounts.repository-deletion-policy %}
diff --git a/translations/pt-BR/content/admin/user-management/repositories.md b/translations/pt-BR/content/admin/user-management/repositories.md
deleted file mode 100644
index 7ba24877d699..000000000000
--- a/translations/pt-BR/content/admin/user-management/repositories.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Repositórios
-intro: 'Você pode gerenciar as configurações disponíveis para os administradores de repositório no appliance do {% data variables.product.prodname_ghe_server %}.'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/user-management/repositories
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/user-management/restricting-repository-creation-in-your-instance.md b/translations/pt-BR/content/admin/user-management/restricting-repository-creation-in-your-instance.md
deleted file mode 100644
index d6f480287039..000000000000
--- a/translations/pt-BR/content/admin/user-management/restricting-repository-creation-in-your-instance.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Restringir a criação de repositórios na instância
-intro: 'Você pode escolher se os membros da organização em seu appliance {% data variables.product.prodname_ghe_server %} podem criar repositórios e quais tipos de repositórios os membros podem criar.'
-redirect_from:
- - /enterprise/admin/user-management/restricting-repository-creation-in-your-instance
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.organizations.repo-creation-constants %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.policies-tab %}
-{% data reusables.enterprise-accounts.repositories-tab %}
-5. Em "Repository creation" (Criação de repositório), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-{% if currentVersion ver_gt "enterprise-server@2.19" %}
-{% data reusables.enterprise-accounts.repo-creation-policy %}
-{% data reusables.enterprise-accounts.repo-creation-types %}
-{% else %}
-6. Em "Repository creation" (Criação de repositórios), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de criação de repositórios](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
-{% endif %}
diff --git a/translations/pt-BR/content/admin/user-management/user-security.md b/translations/pt-BR/content/admin/user-management/user-security.md
deleted file mode 100644
index ee410abfc64c..000000000000
--- a/translations/pt-BR/content/admin/user-management/user-security.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Segurança de usuário
-intro: 'Garanta a segurança dos usuários do {% data variables.product.prodname_ghe_server %}. Você pode auditar as configurações de segurança dos usuários ou impor práticas recomendadas na sua instância.'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/user-management/user-security
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/pt-BR/content/admin/user-management/using-built-in-authentication.md b/translations/pt-BR/content/admin/user-management/using-built-in-authentication.md
deleted file mode 100644
index 40470a71f508..000000000000
--- a/translations/pt-BR/content/admin/user-management/using-built-in-authentication.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Usar a autenticação integrada
-intro: 'Quando você usa o método de autenticação padrão, todos os detalhes de autenticação ficam armazenados na {% data variables.product.product_location_enterprise %}. Se você ainda não tiver um provedor de autenticação estabelecido, como LDAP, SAML ou CAS, a autenticação integrada é o método padrão.'
-redirect_from:
- - /enterprise/admin/user-management/using-built-in-authentication
-versions:
- enterprise-server: '*'
----
-
-Você pode criar mensagens personalizadas que os usuários verão nas páginas de login e logout. Para obter mais informações, consulte "[Personalizar mensagens de usuário na instância](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)".
-
-### Configurar a autenticação integrada
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-4. Selecione **Built in authentication** (Autenticação integrada). ![Opção Select built-in authentication (Selecionar autenticação integrada)](/assets/images/enterprise/management-console/built-in-auth-select.png)
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.2fa_is_available %}
-
-### Criar uma conta e adicionar usuários
-
-Após a criação da sua instância, você terá que criar a sua conta de administrador e usá-la para provisionar os usuários.
-
-1. Na página "Create Admin Account" (Criar conta de administrador) em `http(s)://[hostname]/join`, defina seu nome de usuário, senha e endereço de e-mail. Em seguida, clique em **Create an account** (Criar conta). ![Criar conta de administrador](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png)
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %}
-{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %}
diff --git a/translations/pt-BR/content/admin/user-management/using-cas.md b/translations/pt-BR/content/admin/user-management/using-cas.md
deleted file mode 100644
index 12e804210eeb..000000000000
--- a/translations/pt-BR/content/admin/user-management/using-cas.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Usar CAS
-redirect_from:
- - /enterprise/admin/articles/configuring-cas-authentication/
- - /enterprise/admin/articles/about-cas-authentication/
- - /enterprise/admin/user-management/using-cas
-intro: 'O CAS é um protocolo de logon único (SSO) para vários aplicativos da web. Uma conta de usuário CAS não consome uma {% if currentVersion ver_gt "enterprise-server@2.16" %}licença de{% else %}usuário{% endif %} até o usuário fazer login.'
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.built-in-authentication %}
-
-### Considerações de nome de usuário no CAS
-
-{% data reusables.enterprise_management_console.username_normalization %}
-
-{% data reusables.enterprise_management_console.username_normalization_sample %}
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.external_auth_disables_2fa %}
-
-### Atributos CAS
-
-Os atributos a seguir estão disponíveis.
-
-| Nome do atributo | Tipo | Descrição |
-| ---------------- | ----------- | --------------------------------------------------------------------------- |
-| `username` | Obrigatório | Nome do usuário no {% data variables.product.prodname_ghe_server %}. |
-
-### Configurar o CAS
-{% warning %}
-
-**Aviso:** antes de configurar o CAS na {% data variables.product.product_location_enterprise %}, observe que os usuários não poderão usar seus nomes e senhas do CAS para autenticar solicitações de API ou operações do Git por HTTP/HTTPS. Para isso, eles deverão [criar tokens de acesso](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use).
-
-{% endwarning %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-3. Selecione **CAS**. ![Selecionar CAS](/assets/images/enterprise/management-console/cas-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Selecionar caixa de autenticação integrada CAS](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
-5. No campo **Server URL** (URL do servidor), digite a URL completa do seu servidor CAS. Se o servidor CAS usar um certificado que não pode ser validado pelo {% data variables.product.prodname_ghe_server %}, você poderá usar o comando `ghe-ssl-ca-certificate-install` para instalá-lo como certificado confiável.
diff --git a/translations/pt-BR/content/admin/user-management/using-ldap.md b/translations/pt-BR/content/admin/user-management/using-ldap.md
deleted file mode 100644
index 51cfb54d9824..000000000000
--- a/translations/pt-BR/content/admin/user-management/using-ldap.md
+++ /dev/null
@@ -1,190 +0,0 @@
----
-title: Usar LDAP
-redirect_from:
- - /enterprise/admin/articles/configuring-ldap-authentication/
- - /enterprise/admin/articles/about-ldap-authentication/
- - /enterprise/admin/articles/viewing-ldap-users/
- - /enterprise/admin/hidden/enabling-ldap-sync/
- - /enterprise/admin/hidden/ldap-sync/
- - /enterprise/admin/user-management/using-ldap
-intro: 'O LDAP permite autenticar o {% data variables.product.prodname_ghe_server %} em suas contas existentes e gerenciar centralmente o acesso ao repositório. O LDAP é um protocolo de aplicativo popular de acesso e manutenção dos serviços de informações de diretório, além de ser um dos protocolos mais comuns para integrar software de terceiros a diretórios de usuários em grandes empresas.'
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.built-in-authentication %}
-
-### Serviços LDAP compatíveis
-
-O {% data variables.product.prodname_ghe_server %} se integra aos seguintes serviços LDAP:
-
-* Active Directory;
-* FreeIPA;
-* Oracle Directory Server Enterprise Edition;
-* OpenLDAP;
-* Open Directory;
-* 389-ds.
-
-### Considerações de nome de usuário no LDAP
-
-{% data reusables.enterprise_management_console.username_normalization %}
-
-{% data reusables.enterprise_management_console.username_normalization_sample %}
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.2fa_is_available %}
-
-### Configurar o LDAP na {% data variables.product.product_location_enterprise %}
-
-Depois que você configurar o LDAP, os usuários poderão acessar a instância com as credenciais LDAP. Quando os usuários acessarem pela primeira vez, seus nomes de perfil, endereços de e-mail e chaves SSH serão definidos com os atributos LDAP do diretório.
-
-Quando você configurar o acesso LDAP dos usuários pelo {% data variables.enterprise.management_console %}, suas licenças de usuário não serão usadas até que o primeiro usuário faça login na sua instância. No entanto, se você criar uma conta manualmente usando as configurações de administrador do site, a licença do usuário é imediatamente contabilizada.
-
-{% warning %}
-
-**Aviso:** antes de configurar o LDAP na {% data variables.product.product_location_enterprise %}, verifique se o serviço LDAP oferece suporte a resultados paginados.
-
-{% endwarning %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-3. Em "Authentication" (Autenticação), selecione **LDAP**. ![Selecionar LDAP](/assets/images/enterprise/management-console/ldap-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Selecionar caixa de autenticação integrada](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
-5. Defina as configurações.
-
-### Atributos LDAP
-Use estes atributos para finalizar a configuração LDAP na {% data variables.product.product_location_enterprise %}.
-
-| Nome do atributo | Tipo | Descrição |
-| --------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Host` | Obrigatório | Host LDAP, por exemplo, `ldap.example.com` ou `10.0.0.30`. Se o nome do host só estiver disponível na rede interna, talvez seja necessário configurar antes o DNS da {% data variables.product.product_location_enterprise %} para que ele resolva o nome do host usando seus servidores de nomes internos. |
-| `Porta` | Obrigatório | Porta em que os serviços de host LDAP estão escutando. Por exemplo: 389 e 636 (para LDAPS). |
-| `Criptografia` | Obrigatório | Método de criptografia usado para proteger as comunicações com o servidor LDAP. Por exemplo, básico (sem criptografia), SSL/LDAPS (criptografia desde o início) e StartTLS (atualizar para comunicação com criptografia no momento da conexão). |
-| `Usuário de pesquisa de domínio` | Opcional | Usuário LDAP que faz consultas de usuários para autenticar outros usuários quando eles fazem login. Em geral, é uma conta de serviço criada especificamente para integrações de terceiros. Use um nome totalmente qualificado, como `cn=Administrador,cn=Usuários,dc=Exemplo,dc=com`. Com o Active Directory, também é possível usar a sintaxe `[DOMAIN]\[USERNAME]` (por exemplo, `WINDOWS\Administrator`) para o usuário de pesquisa de domínio. |
-| `Senha de pesquisa de domínio` | Opcional | Senha do usuário de pesquisa de domínio. |
-| `Grupos de administradores` | Opcional | Ao fazerem login no seu appliance, os usuários deste grupo são promovidos a administradores do site. Se você não configurar um grupo de administradores LDAP, a primeira conta de usuário LDAP que acessar seu appliance será automaticamente promovida a administrador do site. |
-| `Base de domínio` | Obrigatório | `Distinguished Name` (DN) totalmente qualificado de uma subárvore LDAP em que você pretende procurar usuários e grupos. Você pode adicionar quantos quiser, mas cada grupo deve ser definido na mesma base de domínio que os usuários pertencentes a ele. Se você especificar grupos de usuários restritos, somente os usuários pertencentes a esses grupos estarão no escopo. É recomendável especificar o nível superior da sua árvore de diretórios LDAP como base de domínio e usar grupos de usuários restritos para controlar o acesso. |
-| `Grupos de usuários restritos` | Opcional | Se especificados, somente os usuários desses grupos poderão efetuar login. Você só precisa especificar os nomes comuns (CNs, Common Names) dos grupos e adicionar quantos grupos quiser. Se não houver grupos especificados, *todos* os usuários no escopo da base de domínio especificada poderão fazer login na sua instância do {% data variables.product.prodname_ghe_server %}. |
-| `ID de usuário` | Obrigatório | Atributo LDAP que identifica o usuário LDAP que tenta fazer a autenticação. Quando houver mapeamento estabelecido, os usuários poderão alterar seus nomes de usuário no {% data variables.product.prodname_ghe_server %}. Este campo deve ser `sAMAccountName` para a maioria das instalações do Active Directory, mas pode ser `uid` para outras soluções LDAP, como OpenLDAP. O valor padrão é `uid`. |
-| `Nome de perfil` | Opcional | Nome exibido na págin de perfil do usuário no {% data variables.product.prodname_ghe_server %}. Se a Sincronização LDAP estiver habilitada, os usuários poderão alterar seus nomes de perfil. |
-| `E-mails` | Opcional | Endereço de e-mail para a conta de usuário no {% data variables.product.prodname_ghe_server %}. |
-| `Chaves SSH` | Opcional | Chaves SSH públicas vinculadas à conta de um usuário no {% data variables.product.prodname_ghe_server %}. As chaves devem estar no formato OpenSSH. |
-| `Chaves GPG` | Opcional | Chaves GPG vinculadas à conta de um usuário no {% data variables.product.prodname_ghe_server %}. |
-| `Desabilitar autenticação LDAP em operações no Git` | Opcional | Se estiver selecionada, essa opção [desativa](#disabling-password-authentication-for-git-operations) o recurso dos usuários para usar senhas LDAP a fim de autenticar as operações no Git. |
-| `Habilitar verificação certificada LDAP` | Opcional | Se estiver selecionada, essa opção [desativa](#enabling-ldap-certificate-verification) a verificação de certificado LDAP. |
-| `Sincronização` | Opcional | Se estiver selecionada, essa opção [ativa](#enabling-ldap-sync) a Sincronização LDAP. |
-
-#### Desabilitar autenticação de senha nas operações no Git
-
-Selecione **Disable username and password authentication for Git operations** (Desabilitar autenticação de nome de usuário e senha para operações do Git) nas configurações LDAP para impor o uso de tokens de acesso pessoal ou chaves SSH, o que pode ajudar a impedir a sobrecarga do servidor por solicitações de autenticação LDAP. Essa configuração é recomendável porque servidores LDAP com resposta lenta, especialmente combinados a um grande número de solicitações devido à sondagem, são uma causa comum de interrupções e problemas de desempenho.
-
-![Desabilitar autenticação de senha LDAP na caixa de seleção do Git](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
-
-Quando esta opção estiver selecionada, se tentar usar uma senha para as operações do Git pela linha de comando, o usuário receberá está mensagem de erro: `A autenticação de senha não é permitida para operações do Git. Use um token de acesso pessoal`.
-
-#### Habilitar verificação certificada LDAP
-
-Selecione **Enable LDAP certificate verification** (Habilitar verificação certificada LDAP) nas suas configurações LDAP para validar o certificado de servidor LDAP que você usa com o TLS.
-
-![Caixa de seleção de verificação certificada LDAP](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
-
-Quando esta opção estiver selecionada, o certificado será validado para garantir o seguinte:
-- Se o certificado contiver ao menos um nome alternativo da entidade (SAN, Subject Alternative Name), um dos SANs deve corresponder ao nome do host LDAP. Do contrário, o nome comum (CN) corresponderá ao nome de host LDAP.
-- O certificado não deve estar expirado.
-- O certificado deve estar assinado por uma autoridade de certificação (CA, Certificate Authority) confiável.
-
-#### Habilitar a Sincronização LDAP
-
-A Sincronização LDAP permite sincronizar os usuários do {% data variables.product.prodname_ghe_server %} e a associação da equipe nos seus grupos LDAP estabelecidos. Assim, é possível estabelecer o controle de acesso baseado em função para os usuários do seu servidor LDAP, em vez de fazer isso manualmente no {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Criar equipes](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)".
-
-Para habilitar a Sincronização LDAP, selecione **Synchronize Emails** (Sincronizar e-mails), **Synchronize SSH Keys** (Sincronizar chaves SSH) ou **Synchronize GPG Keys** (Sincronizar chaves GPG) nas configurações LDAP.
-
-![Caixa de seleção de sincronização](/assets/images/enterprise/management-console/ldap-synchronize.png)
-
-Depois que você habilitar a sincronização LDAP, um trabalho de sincronização será executado no período especificado para fazer as seguintes operações em cada conta de usuário:
-
-- Se você tiver permitido a autenticação integrada para usuários de fora do provedor de identidade e o usuário estiver usando a autenticação integrada, vá para o próximo usuário.
-- Se não houver mapeamento LDAP para o usuário, tente mapeá-lo para uma entrada LDAP no diretório. Se não for possível mapear o usuário para uma entrada LDAP, suspenda o usuário em questão e passe para o seguinte.
-- Se houver um mapeamento LDAP e a entrada LDAP correspondente no diretório estiver ausente, suspenda o usuário e passe para o seguinte.
-- Se a entrada LDAP correspondente tiver sido marcada como desativada e o usuário ainda não estiver suspenso, suspenda o usuário e passe para o seguinte.
-- Se a entrada LDAP correspondente não estiver marcada como desabilitada, se o usuário estiver suspenso e se a opção _Reativar usuários suspensos_ estiver habilitada na central do administrador, cancele a suspensão do usuário.
-- Se a entrada LDAP correspondente incluir um atributo `name`, atualize o nome do perfil do usuário.
-- Se a entrada LDAP correspondente estiver no grupo de administradores, promova o usuário a administrador do site.
-- Se a entrada LDAP correspondente não estiver no grupo de administradores, rebaixe o usuário para uma conta regular.
-- Se um campo LDAP User (Usuário LDAP) estiver definido para e-mails, sincronize as configurações de e-mail do usuário com a entrada LDAP. Defina a primeira entrada LDAP `mail` como e-mail principal.
-- Se um campo LDAP User (Usuário LDAP) estiver definido para chaves SSH públicas, sincronize as chaves SSH públicas do usuário com a entrada LDAP.
-- Se um campo LDAP User (Usuário LDAP) estiver definido para chaves GPG públicas, sincronize as chaves GPG públicas do usuário com a entrada LDAP.
-
-{% note %}
-
-**Observação**: as entradas LDAP só podem ser marcadas como desabilitadas se você usar o Active Directory, e se o atributo `userAccountControl` estiver presente e sinalizado com `ACCOUNTDISABLE`.
-
-{% endnote %}
-
-Um trabalho de sincronização também será executado no período especificado para fazer as seguintes operações em cada equipe mapeada para um grupo LDAP:
-
-- Se um grupo LDAP correspondente de uma equipe tiver sido removido, remova todos os integrantes da equipe.
-- Se as entradas do integrante LDAP tiverem sido removidas do grupo LDAP, remova os usuários correspondentes da equipe. Se o usuário perder o acesso a qualquer repositórios, exclua todas as bifurcações privadas que ele possa ter nesses repositórios.
-- Se as entradas do integrante LDAP tiverem sido adicionadas ao grupo LDAP, adicione os usuários correspondentes à equipe. Se o usuário recuperar o acesso a quaisquer repositórios, restaure todas as bifurcações privadas dos repositórios que foram excluídos porque o usuário perdeu o acesso nos últimos 90 dias.
-
-{% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
-
-{% warning %}
-
-**Aviso de segurança:**
-
-Quando a Sincronização LDAP está ativada, os administradores do site e os proprietários da organização podem pesquisar grupos no diretório LDAP aos quais pretendem mapear a equipe.
-
-Esse procedimento pode resultar na divulgação de informações confidenciais da organização para contratados ou outros usuários sem privilégios, inclusive:
-
-- A existência de grupos LDAP específicos visíveis para o *usuário de pesquisa de domínio*;
-- Integrantes do grupo LDAP que tenham contas de usuário no {% data variables.product.prodname_ghe_server %}, divulgadas ao criar uma equipe sincronizada com o grupo LDAP.
-
-Se não houver intenção de divulgar essas informações, sua empresa ou organização deve restringir as permissões do *usuário de pesquisa de domínio* configurado no Console de administração. Caso não seja possível fazer essa restrição, entre em contato com o {% data variables.contact.contact_ent_support %}.
-
-{% endwarning %}
-
-#### Classes de grupo de objeto LDAP compatíveis
-
-O {% data variables.product.prodname_ghe_server %} é compatível com as seguintes classes de grupo de objeto LDAP. Os grupos podem ser aninhados.
-
-- `group`
-- `groupOfNames`
-- `groupOfUniqueNames`
-- `posixGroup`
-
-### Exibir e criar usuários LDAP
-
-É possível exibir a lista completa de usuários LDAP que têm acesso à sua instância, e você também pode provisionar novos usuários.
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-3. Na barra lateral esquerda, clique em **LDAP users** (Usuários LDAP). ![Guia de usuários LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
-4. Para procurar um usuário, digite um nome (total ou parcialmente) do usuário e clique em **Search** (Pesquisar). Os usuários serão exibidos nos resultados da pesquisa. Se o usuário não existir, clique em **Create** (Criar) para provisionar a nova conta. ![Pesquisa LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
-
-### Atualizar contas LDAP
-
-Se a [Sincronização LDAP estiver desabilitada](#enabling-ldap-sync), as alterações nas contas LDAP não serão sincronizadas automaticamente com o {% data variables.product.prodname_ghe_server %}.
-
-* Para usar um novo grupo de administradores LDAP, os usuários devem ser promovidos e rebaixados manualmente no {% data variables.product.prodname_ghe_server %} a fim de refletir as mudanças no LDAP.
-* Para adicionar ou remover contas LDAP nos grupos de administração LDAP, [promova ou rebaixe as contas no {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator).
-* Para remover contas LDAP, [suspenda as contas do {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users).
-
-#### Sincronizar contas LDAP manualmente
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.search-user %}
-{% data reusables.enterprise_site_admin_settings.click-user %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Em "LDAP," clique em **Sync now** (Sincronizar agora) para atualizar manualmente a conta com os dados do seu servidor LDAP. ![Botão LDAP sync now (Sincronizar LDAP agora)](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
-
-Você também pode [usar a API para acionar uma sincronização manual](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap).
-
-### Revogar o acesso à {% data variables.product.product_location_enterprise %}
-
-Se a [Sincronização LDAP estiver habilitada](#enabling-ldap-sync), remover as credenciais LDAP do usuário suspenderá a conta do usuário após a execução de sincronização seguinte.
-
-Se a Sincronização LDAP **não** estiver habilitada, você deve suspender manualmente a conta do {% data variables.product.prodname_ghe_server %} após remover as credenciais LDAP. Para obter mais informações, consulte "[Suspender e cancelar a suspensão de usuários](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)".
diff --git a/translations/pt-BR/content/admin/user-management/using-saml.md b/translations/pt-BR/content/admin/user-management/using-saml.md
deleted file mode 100644
index 8de1ebc20208..000000000000
--- a/translations/pt-BR/content/admin/user-management/using-saml.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: Usar SAML
-redirect_from:
- - /enterprise/admin/articles/configuring-saml-authentication/
- - /enterprise/admin/articles/about-saml-authentication/
- - /enterprise/admin/user-management/using-saml
-intro: 'O SAML é um padrão de autenticação e autorização baseado em XML. O {% data variables.product.prodname_ghe_server %} pode agir como provedor de serviços (SP, Service Provider) com seu provedor de identidade (IdP, Identity Provider) SAML interno.'
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.built-in-authentication %}
-
-### Serviços SAML compatíveis
-
-{% data reusables.saml.saml-supported-idps %}
-
-{% data reusables.saml.saml-single-logout-not-supported %}
-
-### Considerações de nome de usuário no SAML
-
-Cada nome de usuário do {% data variables.product.prodname_ghe_server %} é determinado por uma das seguintes afirmações na resposta SAML, ordenada por prioridade:
-
-- Nome de usuário personalizado, se houver;
-- Declaração `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`, se houver;
-- Declaração `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`, se houver;
-- Elemento `NameID`.
-
-O elemento `NameID` é obrigatório, mesmo que os outros atributos estejam presentes.
-
-É criado um mapeamento entre `NameID` e o nome de usuário do {% data variables.product.prodname_ghe_server %}; assim, `NameID` deve ser persistente, exclusivo e não estar sujeito a alterações no ciclo de vida do usuário.
-
-{% data reusables.enterprise_management_console.username_normalization %}
-
-{% data reusables.enterprise_management_console.username_normalization_sample %}
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.external_auth_disables_2fa %}
-
-### Metadados SAML
-
-Os metadados do provedor de serviços da sua instância do {% data variables.product.prodname_ghe_server %} estão disponíveis em `http(s)://[hostname]/saml/metadata`.
-
-Para configurar seu provedor de identidade manualmente, a URL do serviço de consumidor de declaração (ACS, Assertion Consumer Service) é `http(s)://[hostname]/saml/consume` e usa a associação `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`.
-
-### Atributos SAML
-
-Os atributos a seguir estão disponíveis. Você pode alterar seus nomes no [console de gerenciamento](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), exceto o atributo `administrator`.
-
-| Nome padrão do atributo | Tipo | Descrição |
-| ----------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `NameID` | Obrigatório | Identificador de usuário persistente. Qualquer formato de identificador de nome persistente pode ser usado. O elemento `NameID` será usado para um nome de usuário do {% data variables.product.prodname_ghe_server %}, a menos que uma das declarações alternativas seja fornecida. |
-| `administrator` | Opcional | Quando o valor for 'true', o usuário será promovido automaticamente como administrador. Qualquer outro valor ou um valor não existente rebaixará o usuário para uma conta regular. |
-| `nome de usuário` | Opcional | Nome do usuário no {% data variables.product.prodname_ghe_server %}. |
-| `full_name` | Opcional | Nome do usuário exibido na página de perfil. Após o provisionamento, os usuários podem alterar seus nomes. |
-| `emails` | Opcional | Endereços de e-mail para o usuário. É possível especificar mais de um. |
-| `public_keys` | Opcional | Chaves SSH públicas para o usuário. É possível especificar mais de um. |
-| `gpg_keys` | Opcional | Chaves chaves GPG para o usuário. É possível especificar mais de um. |
-
-### Definir configurações SAML
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-3. Selecione **SAML**. ![Autenticação SAML](/assets/images/enterprise/management-console/auth-select-saml.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Selecionar caixa de autenticação integrada SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png)
-5. Para habilitar SSO de resposta não solicitada, selecione **IdP initiated SSO** (SSO iniciado pelo IdP). Por padrão, o {% data variables.product.prodname_ghe_server %} responderá a uma solicitação iniciada pelo Provedor de identidade (IdP) não solicitado com `AuthnRequest`. ![SAML idP SSO](/assets/images/enterprise/management-console/saml-idp-sso.png)
-
- {% tip %}
-
- **Observação**: é recomendável manter esse valor **desmarcado**. Você deve habilitar esse recurso **somente ** na rara instância em que sua implementação SAML não oferecer suporte ao SSO iniciado pelo provedor de serviços e quando recomendado pelo {% data variables.contact.enterprise_support %}.
-
- {% endtip %}
-
-5. Selecione **Disable administrator demotion/promotion** (Desabilitar rebaixamento/promoção do administrador) se você **não** quiser que o provedor SAML determine direitos de administrador para usuários no {% data variables.product.product_location_enterprise %}. ![Configuração desativar administrador SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png)
-6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTP ou HTTPS do seu IdP para solicitações de logon único. Esse valor é fornecido pela configuração do IdP. Se o nome do host só estiver disponível na rede interna, talvez seja necessário [configurar a {% data variables.product.product_location_enterprise %} para usar servidores de nomes internos](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). ![Autenticação SAML](/assets/images/enterprise/management-console/saml-single-sign-url.png)
-7. Como alternativa, no campo **Issuer** (Emissor), digite o nome do emissor de SAML. Fazer isso verifica a autenticidade das mensagens enviadas para a {% data variables.product.product_location_enterprise %}. ![Emissor SAML](/assets/images/enterprise/management-console/saml-issuer.png)
-8. Nos menus suspensos **Signature Method** (Método de assinatura) e **Digest Method** (Método de compilação), escolha o algoritmo de hash usado pelo emissor SAML para verificar a integridade das solicitações do {% data variables.product.product_location_enterprise %}. Especifique o formato no menu suspenso **Name Identifier Format** (Formato de identificador de nome). ![Método SAML ](/assets/images/enterprise/management-console/saml-method.png)
-9. Em **Verification certificate** (Certificado de verificação), clique em **Choose File** (Escolher arquivo) e escolha um certificado para validar as respostas SAML do IdP. ![Autenticação SAML](/assets/images/enterprise/management-console/saml-verification-cert.png)
-10. Modifique os nomes do atributo SAML para corresponder ao IdP, se necessário, ou aceite os nomes padrão. ![Nomes de atributos SAML](/assets/images/enterprise/management-console/saml-attributes.png)
-
-### Revogar o acesso à {% data variables.product.product_location_enterprise %}
-
-Se remover um usuário do seu provedor de identidade, você também deverá suspendê-lo manualmente. Caso contrário, ele continuará podendo fazer autenticação usando tokens de acesso ou chaves SSH. Para obter mais informações, consulte "[Suspender e cancelar a suspensão de usuários](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)".
-
-### Requisitos de mensagem de resposta
-
-A mensagem de resposta deve atender aos seguintes requisitos:
-
-- O `` elemento deve sempre ser fornecido no documento de resposta raiz e deve corresponder ao URL do ACS somente quando o documento de resposta raiz estiver assinado. Se for assinada, a declaração será ignorada.
-- O elemento `` deve sempre ser fornecido como parte do elemento ``. Ele corresponde ao ID da Entidade {% data variables.product.prodname_ghe_server %}. Esta é a URL para a instância do {% data variables.product.prodname_ghe_server %}, como `https://ghe.corp.example.com`.
-- Todas as declarações na resposta **devem** ser precedidas de assinatura digital. É possível fazer isso assinando cada elemento `` ou assinando o elemento ``.
-- Um elemento `` deve ser fornecido como parte do elemento ``. Qualquer formato de identificador de nome persistente pode ser usado.
-- O atributo `Recipient` deve estar presente e definido na URL do ACS. Como por exemplo:
-
-```xml
-
-
-
- ...
-
-
-
-
-
-
- monalisa
-
-
-
-
-```
-
-### Mensagens de erro
-
-Se `Recipient` não corresponder à URL do ACS, o log de autenticação mostrará a seguinte mensagem de erro:
-
-```
-Recipient na resposta SAML não era válido.
-```
-
-Se `Recipient` não for parte da mensagem de resposta, o log de autenticação mostrará a seguinte mensagem de erro:
-
-```
-Recipient na resposta SAML não pode ficar em branco.
-```
-
-Se a resposta SAML não estiver assinada ou se a assinatura não corresponder ao conteúdo, o log de autenticação mostrará a seguinte mensagem de erro:
-
-```
-Resposta SAML não assinada ou modificada.
-```
-Se `Audience` estiver ausente ou não corresponder ao ID de entidade do {% data variables.product.prodname_ghe_server %}, o log de autenticação mostrará a seguinte mensagem de erro:
-
-```
-Audience inválido. O atributo Audience não corresponde a url_sua_instância
-```
diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally.md
deleted file mode 100644
index f91f346e5416..000000000000
--- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Acessar uma pull request no local
-intro: 'É possível visualizar as alterações propostas nas pull requests em aberto no {% data variables.product.prodname_desktop %}.'
-redirect_from:
- - /desktop/contributing-to-projects/accessing-a-pull-request-locally
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.click-pull-requests %}
- ![Guia Pull requests no menu suspenso Branch atual](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png)
-{% data reusables.desktop.choose-pr-from-list %}
- ![Lista de pull requests em aberto no repositório](/assets/images/help/desktop/click-pull-request.png)
-4. Para atualizar a lista de pull requests, você também pode clicar em {% octicon "sync" aria-label="The sync icon" %}. ![Botão Sync (Sincronizar) para atualizar](/assets/images/help/desktop/pull-request-list-sync.png)
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/accessing-a-pull-request-locally.md b/translations/pt-BR/content/desktop/contributing-to-projects/accessing-a-pull-request-locally.md
deleted file mode 100644
index 2352422d2b37..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/accessing-a-pull-request-locally.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Acessar uma pull request no local
-intro: 'É possível visualizar as alterações propostas nas pull requests em aberto no {% data variables.product.prodname_desktop %}.'
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.click-pull-requests %}
- ![Guia Pull requests no menu suspenso Branch atual](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png)
-{% data reusables.desktop.choose-pr-from-list %}
- ![Lista de pull requests em aberto no repositório](/assets/images/help/desktop/click-pull-request.png)
-4. Para atualizar a lista de pull requests, você também pode clicar em {% octicon "sync" aria-label="The sync icon" %}. ![Botão Sync (Sincronizar) para atualizar](/assets/images/help/desktop/pull-request-list-sync.png)
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop.md b/translations/pt-BR/content/desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop.md
deleted file mode 100644
index ece0ef78f14f..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Adicionar um repositório do computador local ao GitHub Desktop
-intro: 'É possível adicionar qualquer repositório Git ao {% data variables.product.prodname_desktop %}, mesmo que não seja um repositório do {% data variables.product.prodname_dotcom %}.'
-versions:
- free-pro-team: '*'
----
-
-{% tip %}
-
-**Dica:** é possível adicionar um repositório Git do computador local ao GitHub Desktop arrastando a pasta para a janela do {% data variables.product.prodname_desktop %}. Ao arrastar várias pastas do Git para o {% data variables.product.prodname_desktop %} simultaneamente, cada pasta será acessada como um repositório Git individual.
-
-{% endtip %}
-
-{% mac %}
-
-1. No menu **File** (Arquivo), clique em **Add Local Repository** (Adicionar repositório local). ![Opção de menu Add Local Repository (Adicionar repositório local)](/assets/images/help/desktop/add-local-repository-mac.png)
-2. Clique em **Choose...** (Escolher...). Em seguida, navegue pela janela Finder (Localizador) até o local do repositório que você pretende adicionar. ![Campo Local Path (Caminho local) no app Mac](/assets/images/help/desktop/add-repo-choose-button-mac.png)
-4. Clique em **Add Repository** (Adicionar repositório). ![Botão Add repository (Adicionar repositório) no app Mac](/assets/images/help/desktop/add-repository-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. No menu **File** (Arquivo), clique em **Add Local Repository** (Adicionar repositório local). ![Opção de menu Add Local Repository (Adicionar repositório local)](/assets/images/help/desktop/add-local-repository-windows.png)
-2. Clique em **Choose...** (Escolher...). Em seguida, navegue pela janela Windows Explorer (Explorador do Windows) até o local do repositório que você pretende adicionar. ![Campo Local Path (Caminho local) no app Windows](/assets/images/help/desktop/add-repo-choose-button-win.png)
-4. Clique em **Add Repository** (Adicionar repositório). ![Botão Add repository (Adicionar repositório) no app Windows](/assets/images/help/desktop/add-repository-button-windows.png)
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop.md b/translations/pt-BR/content/desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop.md
deleted file mode 100644
index 42e07b6d31c6..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Adicionar um projeto ao GitHub via GitHub Desktop
-intro: 'É possível adicionar um repositório Git ao {% data variables.product.prodname_dotcom %} usando o {% data variables.product.prodname_desktop %}.'
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-{% data reusables.git.remove-git-remote %}
-2. [Adicione o repositório ao GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/).
-{% data reusables.desktop.publish-repository %}
-4. Digite o nome desejado do repositório no campo **Name** (Nome) ou use o nome padrão do repositório local. ![Campo Name (Nome)](/assets/images/help/desktop/publish-repository-name-mac.png)
-5. Para publicar um repositório público, desmarque a opção **Keep this code private** (Manter este código privado). ![Caixa de seleção Keep this code private (Manter este código privado)](/assets/images/help/desktop/publish-repository-private-checkbox-mac.png)
-6. Escolha a organização no menu suspenso **Organization** (Organização) onde você deseja publicar o repositório ou selecione **None** (Nenhum) para publicar o repositório na sua conta pessoal. ![Lista suspensa Organization (Organização)](/assets/images/help/desktop/publish-repository-org-dropdown-mac.png)
-7. Clique no botão **Publish Repository** (Publicar repositório). ![Botão Publish repository (Publicar repositório) na caixa de diálogo Publish repository (Publicar repositório)](/assets/images/help/desktop/publish-repository-dialog-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.git.remove-git-remote %}
-2. [Adicione o repositório ao GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/).
-{% data reusables.desktop.publish-repository %}
-4. Digite o nome desejado do repositório no campo **Name** (Nome) ou use o nome padrão do repositório local. ![Campo Name (Nome)](/assets/images/help/desktop/publish-repository-name-win.png)
-5. Para publicar um repositório público, desmarque a opção **Keep this code private** (Manter este código privado). ![Caixa de seleção Keep this code private (Manter este código privado)](/assets/images/help/desktop/publish-repository-private-checkbox-win.png)
-6. Escolha a organização no menu suspenso **Organization** (Organização) onde você deseja publicar o repositório ou selecione **None** (Nenhum) para publicar o repositório na sua conta pessoal. ![Lista suspensa Organization (Organização)](/assets/images/help/desktop/publish-repository-org-dropdown-win.png)
-7. Clique no botão **Publish Repository** (Publicar repositório). ![Botão Publish repository (Publicar repositório) na caixa de diálogo Publish repository (Publicar repositório)](/assets/images/help/desktop/publish-repository-dialog-button-win.png)
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/adding-and-cloning-repositories.md b/translations/pt-BR/content/desktop/contributing-to-projects/adding-and-cloning-repositories.md
deleted file mode 100644
index b619da009fbb..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/adding-and-cloning-repositories.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Adicionar e clonar repositórios
-intro: 'Adicione repositórios existentes do seu computador local ao {% data variables.product.prodname_desktop %} ou clone os repositórios do {% data variables.product.product_name %}.'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop.md b/translations/pt-BR/content/desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop.md
deleted file mode 100644
index 6a312b82b8b5..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Alterar repositório remote de URL no GitHub Desktop
-intro: 'É possível alterar a URL remota do repositório com o qual você estiver trabalhando via {% data variables.product.prodname_desktop %}. Você pode fazer isso em caso de alteração do nome do repositório, do nome do usuário ou do nome da organização proprietária do repositório.'
-redirect_from:
- - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-1. No menu **Repository** (Repositório), clique em **Repository Settings...** (Configurações do repositório...). ![Opção de menu Repository Settings (Configurações do repositório)](/assets/images/help/desktop/repository-settings-mac.png)
-2. No campo **Primary remote repository** (Repositório remote principal), digite a URL. ![Campo Primary remote repository (Repositório remote principal)](/assets/images/help/desktop/repository-settings-remote-mac.png)
-3. Clique em **Save** (Salvar). ![Botão Save (Salvar)](/assets/images/help/desktop/repository-settings-save-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. No menu **Repository** (Repositório), clique em **Repository Settings...** (Configurações do repositório...). ![Opção de menu Repository Settings (Configurações do repositório)](/assets/images/help/desktop/repository-settings-win.png)
-2. No campo **Primary remote repository** (Repositório remote principal), digite a URL. ![Campo Primary remote repository (Repositório remote principal)](/assets/images/help/desktop/repository-settings-remote-win.png)
-3. Clique em **Save** (Salvar). ![Botão Save (Salvar)](/assets/images/help/desktop/repository-settings-save-win.png)
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop.md b/translations/pt-BR/content/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop.md
deleted file mode 100644
index e3a8905aaf97..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Clonar um repositório do GitHub para o GitHub Desktop
-intro: 'É possível usar o {% data variables.product.prodname_dotcom %} a fim de clonar repositórios remote para o {% data variables.product.prodname_desktop %}.'
-versions:
- free-pro-team: '*'
----
-
-{% tip %}
-
-**Dica:** você também pode usar o {% data variables.product.prodname_desktop %} para clonar repositórios existentes no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Clonar um repositório no {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)."
-
-{% endtip %}
-
-{% mac %}
-
-1. Entre no {% data variables.product.product_location %} e no {% data variables.product.prodname_desktop %} antes de começar a clonar.
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.open-with-github-desktop %}
-5. Clique em **Choose...** (Escolher...). Em seguida, navegue pela janela Finder (Localizador) até o local em que você pretende clonar o repositório. ![Botão Choose (Escolher) na guia URL](/assets/images/help/desktop/clone-choose-button-url-mac.png)
-
- {% note %}
-
- **Observação:** se o repositório estiver configurado para usar o LFS, você deverá inicializar o {% data variables.large_files.product_name_short %}.
-
- {% endnote %}
-
-5. Clique em **Clone** (Clonar). ![Botão Clone (Clonar) na guia URL](/assets/images/help/desktop/clone-button-url-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. Entre no {% data variables.product.product_location %} e no {% data variables.product.prodname_desktop %} antes de começar a clonar.
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.open-with-github-desktop %}
-5. Clique em **Choose...** (Escolher...). Em seguida, navegue pelo Windows Explorer (Explorador do Windows) até o local em que você pretende clonar o repositório. ![Botão Choose (Escolher)](/assets/images/help/desktop/clone-choose-button-url-win.png)
-
- {% note %}
-
- **Observação:** se o repositório estiver configurado para usar o LFS, você deverá inicializar o {% data variables.large_files.product_name_short %}.
-
- {% endnote %}
-
-5. Clique em **Clone** (Clonar). ![Botão Clone (Clonar)](/assets/images/help/desktop/clone-button-url-win.png)
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop.md b/translations/pt-BR/content/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop.md
deleted file mode 100644
index 3c4c2abfc2dd..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Cloning and forking repositories from GitHub Desktop
-intro: 'É possível usar o {% data variables.product.prodname_desktop %} para clonar e bifurcar os repositórios do {% data variables.product.prodname_dotcom %}.'
-redirect_from:
- - /desktop/contributing-to-projects/cloning-a-repository-from-github-desktop
-versions:
- free-pro-team: '*'
----
-
-### Clonar repositórios
-Os repositórios no {% data variables.product.prodname_dotcom %} existem como repositórios remotos. É possível clonar repositórios públicos pertencentes a outras pessoas. É possível clonar o seu próprio repositório para criar uma cópia loca* no seu computador e fazer a sincronia entre os dois locais.
-
-Também é possível clonar um repositório diretamente no {% data variables.product.prodname_dotcom %} ou no {% data variables.product.prodname_enterprise %}. Para obter mais informações, consulte "[Clonar um repositório do {% data variables.product.prodname_dotcom %} para o {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)".
-
-{% mac %}
-
-{% data reusables.desktop.choose-clone-repository %}
- ![Opção de menu Clone (Clonar) no app Mac](/assets/images/help/desktop/clone-file-menu-mac.png)
-{% data reusables.desktop.cloning-location-tab %}
- ![Guias Location (Local) no menu Clone a repository (Clonar um repositório)](/assets/images/help/desktop/choose-repository-location-mac.png)
-{% data reusables.desktop.cloning-repository-list %}
- ![Clonar uma lista de repositórios](/assets/images/help/desktop/clone-a-repository-list-mac.png)
-4. Clique em **Choose...** (Escolher...). Em seguida, navegue pela janela Finder (Localizador) até o local em que você pretende clonar o repositório. ![Botão Choose (Escolher)](/assets/images/help/desktop/clone-choose-button-mac.png)
-5. Clique em **Clone** (Clonar). ![Botão Clone (Clonar)](/assets/images/help/desktop/clone-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.choose-clone-repository %}
- ![Opção de menu Clone (Clonar) no app Windows](/assets/images/help/desktop/clone-file-menu-windows.png)
-{% data reusables.desktop.cloning-location-tab %}
- ![Guias Location (Local) no menu Clone a repository (Clonar um repositório)](/assets/images/help/desktop/choose-repository-location-win.png)
-{% data reusables.desktop.cloning-repository-list %}
- ![Clonar uma lista de repositórios](/assets/images/help/desktop/clone-a-repository-list-win.png)
-4. Clique em **Choose...** (Escolher...). Em seguida, navegue pelo Windows Explorer (Explorador do Windows) até o local em que você pretende clonar o repositório. ![Botão Choose (Escolher)](/assets/images/help/desktop/clone-choose-button-win.png)
-5. Clique em **Clone** (Clonar). ![Botão Clone (Clonar)](/assets/images/help/desktop/clone-button-win.png)
-
-{% endwindows %}
-
-### Bifurcar os repositórios
-Para contribuir para um projeto em que você não tem acesso de gravação, você pode usar o {% data variables.product.prodname_desktop %} para criar uma bifurcação do repositório. As alterações na sua bifurcação não afetam o repositório original. Você pode fazer commit das alterações na sua bifurcação e, em seguida, abrir um pull request no repositório original com as alterações propostas. Para obter mais informações, consulte "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)".
-
-1. Se você clonar um repositório em que você não tem acesso de gravação e tentar fazer commit das alterações, {% data variables.product.prodname_desktop %} informará que "você não tem acesso de gravação para o **REPOSITÓRIO**. Clique em **criar uma bifurcação**. ![Criar um link debifurcação](/assets/images/help/desktop/create-a-fork.png)
-3. Clique em **Bifurcar este repositório**. ![Botão bifurcar este repositório](/assets/images/help/desktop/fork-this-repo-button.png)
-4. Para visualizar a sua bifurcação no {% data variables.product.prodname_dotcom %}, no canto superior direito do {% data variables.product.prodname_dotcom %}, clique na imagem do seu perfil e, em seguida, clique em **Seus repositórios**. ![Seu link para repositórios](/assets/images/help/profile/your-repositories.png)
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project.md b/translations/pt-BR/content/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project.md
deleted file mode 100644
index 3d3871dbbbe2..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: Fazer commit e revisar as alterações do projeto
-intro: 'À medida que você edita os arquivos, o {% data variables.product.prodname_desktop %} monitora todas as alterações feitas. É possível decidir como você pretende agrupar as alterações para criar commits relevantes.'
-versions:
- free-pro-team: '*'
----
-
-### Sobre commits
-
-Em um processo semelhante ao de salvar um arquivo, um commit é uma alteração em um ou mais arquivos do branch. O Git atribui um ID exclusivo (chamado SHA ou hash) a cada commit, e o ID monitora:
-
-- Cada uma das alterações feitas;
-- O momento em que as alterações foram feitas;
-- O autor das alterações.
-
-Ao fazer um commit, você deve incluir uma mensagem que descreva brevemente as alterações. Também é possível incluir um coautor em quaisquer commits que envolverem trabalho colaborativo.
-
-### 1. Escolher um branch e fazer alterações
-
-1. [Crie um branch](/desktop/guides/contributing-to-projects/managing-branches) ou selecione um branch existente clicando em {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** (Branch atual) na barra de ferramentas. Em seguida, selecione o branch na lista. ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/click-branch-in-drop-down.png)
-{% data reusables.desktop.make-changes %}
-
-### 2. Selecionar alterações para inclusão em um commit
-
-As alterações feitas nos arquivos via editor de texto e salvas no local também aparecerão no {% data variables.product.prodname_desktop %}.
-
-* O ícone vermelho {% octicon "diff-removed" aria-label="The diff removed icon color-red" %} indica os arquivos removidos.
-* O ícone amarelo {% octicon "diff-modified" aria-label="The diff modified icon color-yellow" %} indica os arquivos alterados.
-* O ícone verde {% octicon "diff-added" aria-label="The diff added icon color-green" %} indica os arquivos adicionados.
-* Para acessar as alterações stashed, clique em **Stashed Changes** (Alterações stashed). ![Opção Stashed Changes (Alterações stashed)](/assets/images/help/desktop/stashed-changes.png)
-* {% data reusables.desktop.commit-all-desc %}
-![Caixa de seleção para fazer commit em todos os arquivos alterados](/assets/images/help/desktop/commit-all.png)
-* {% data reusables.desktop.commit-some-desc %}
-![Caixas de seleção ao lado dos arquivos em que deseja fazer commit](/assets/images/help/desktop/commit-some.png)
-
-#### Criar um commit parcial
-
-Se um arquivo tiver várias alterações e você quiser incluir somente *algumas* no commit, será possível criar um commit parcial. O restante das alterações ficará intacto, de modo que você possa fazer outras modificações e commits. Essa opção permite fazer commits separados mais relevantes, como manter alterações de quebra de linha em um commit separado das alterações de código.
-
-Durante a revisão do diff do arquivo, as linhas a serem incluídas no commit ficam destacadas em azul. Para excluir a alteração, clique na linha alterada para que o destaque azul desapareça.
-
-![Linhas desmarcadas em um arquivo](/assets/images/help/desktop/partial-commit.png)
-
-#### Descartar alterações
-
-Você pode descartar todas as alterações sem commits em um arquivo ou intervalo de arquivos. Também é possível descartar todas as alterações em todos os arquivos desde a última confirmação.
-
-{% mac %}
-
-{% data reusables.desktop.select-discard-files %}
-{% data reusables.desktop.click-discard-files %}
- ![Opção Discard Changes (Descartar alterações) no menu de contexto](/assets/images/help/desktop/discard-changes-mac.png)
-{% data reusables.desktop.confirm-discard-files %}
- ![Botão Discard Changes (Descartar alterações) na caixa de diálogo Confirmation (Confirmação)](/assets/images/help/desktop/discard-changes-confirm-mac.png)
-
-{% tip %}
-
-**Dica:** as alterações descartadas são salvas em um arquivo com data em Trash (Lixeira), e será possível recuperá-las até que a lixeira seja esvaziada.
-
-{% endtip %}
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %}
- ![Opção Discard Changes (Descartar alterações) no menu de contexto](/assets/images/help/desktop/discard-changes-win.png)
-{% data reusables.desktop.confirm-discard-files %}
- ![Botão Discard Changes (Descartar alterações) na caixa de diálogo Confirmation (Confirmação)](/assets/images/help/desktop/discard-changes-confirm-win.png)
-
-{% tip %}
-
-**Dica:** as alterações descartadas são salvas em um arquivo com data em Recycle Bin (Lixo), e será possível recuperá-las até a lixeira ser esvaziada.
-
-{% endtip %}
-
-{% endwindows %}
-
-### 3. Mensagem de commit e envio das alterações
-
-Ao concluir as alterações que você decidiu fazer no commit, escreva a mensagem do commit e envie as alterações. Se o commit envolveu trabalho em colaboração, será possível atribuí-lo a mais de um autor.
-
-{% note %}
-
-**Observação**: {% data reusables.desktop.tags-push-with-commits %} Para obter mais informações, consulte "[Gerenciando tags](/desktop/contributing-to-projects/managing-tags)".
-
-{% endnote %}
-
-{% data reusables.desktop.commit-message %}
- ![Campo Commit message (Mensagem do commit)](/assets/images/help/desktop/commit-message.png)
-2. Para atribuir um commit a outro autor, você também pode clicar no ícone para adicionar coautores e digitar o(s) nome(s) de usuário que pretende incluir. ![Adicionar um coautor à mensagem do commit](/assets/images/help/desktop/add-co-author-commit.png)
-{% data reusables.desktop.commit-button %}
- ![Botão Commit (Fazer commit)](/assets/images/help/desktop/commit-button.png)
-4. Se o branch com a qual você está tentando fazer commit estiver protegido, o desktop irá avisá-lo.
- - Para mover as alterações, clique em **alternar branches**.
- - Para confirmar suas alterações no branch protegido, clique em **Commit para _BRANCH_**.
-
- Para obter mais informações sobre branches protegidos, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". ![Aviso de branch protegido](/assets/images/help/desktop/protected-branch-warning.png)
-{% data reusables.desktop.push-origin %}
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/creating-a-branch-for-your-work.md b/translations/pt-BR/content/desktop/contributing-to-projects/creating-a-branch-for-your-work.md
deleted file mode 100644
index ac0ffae89de8..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/creating-a-branch-for-your-work.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Criar um branch para teste
-intro: 'Se tiver permissões de colaborador em um repositório, você poderá criar um branch a partir do branch padrão do repositório para testar suas alterações com segurança.'
-versions:
- free-pro-team: '*'
----
-
-### Criar um branch
-
-{% tip %}
-
-**Dica:** o primeiro branch que você criar terá como base o branch padrão, que costuma ser `master`. Se houver mais de um branch, será possível basear seu novo branch no branch verificado ou no branch padrão.
-
-{% endtip %}
-
-{% mac %}
-
-{% data reusables.desktop.click-base-branch-in-drop-down %}
- ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-{% data reusables.desktop.create-new-branch %}
- ![Opção New Branch (Novo branch) no menu Branch](/assets/images/help/desktop/new-branch-button-mac.png)
-{% data reusables.desktop.name-branch %}
- ![Campo para criar um nome para o novo branch](/assets/images/help/desktop/create-branch-name-mac.png)
-{% data reusables.desktop.select-base-branch %}
- ![Opções do branch base](/assets/images/help/desktop/create-branch-choose-branch-mac.png)
-{% data reusables.desktop.confirm-new-branch-button %}
- ![Botão Create Branch (Criar branch)](/assets/images/help/desktop/create-branch-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.click-base-branch-in-drop-down %}
- ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/click-branch-in-drop-down-win.png)
-{% data reusables.desktop.create-new-branch %}
- ![Opção New Branch (Novo branch) no menu Branch](/assets/images/help/desktop/new-branch-button-win.png)
-{% data reusables.desktop.name-branch %}
- ![Campo para criar um nome para o novo branch](/assets/images/help/desktop/create-branch-name-win.png)
-{% data reusables.desktop.select-base-branch %}
- ![Opções do branch base](/assets/images/help/desktop/create-branch-choose-branch-win.png)
-{% data reusables.desktop.confirm-new-branch-button %}
- ![Botão Create branch (Criar branch)](/assets/images/help/desktop/create-branch-button-win.png)
-
-{% endwindows %}
-
-### Leia mais
-
-- "[Clonar um repositório no {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)"
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/creating-an-issue-or-pull-request.md b/translations/pt-BR/content/desktop/contributing-to-projects/creating-an-issue-or-pull-request.md
deleted file mode 100644
index 1fa2ef51ecdc..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/creating-an-issue-or-pull-request.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Criar um problema ou um pull request
-intro: É possível criar um problema ou um pull request para propor e colaborar com alterações em um repositório.
-redirect_from:
- - /desktop/contributing-to-projects/creating-a-pull-request
-versions:
- free-pro-team: '*'
----
-
-### Abrir um problema novo
-Ao encontrar um erro ou desejar sugerir uma melhoria ao trabalhar localmente com o {% data variables.product.prodname_desktop %}, você poderá abrir um novo problema no repositório em que se encontra se os problemas estiverem habilitados. Para obter mais informações sobre como trabalhar com problemas, consulte "[Sobre problemas](/github/managing-your-work-on-github/about-issues)".
-
-{% mac %}
-
-1. No canto superior esquerdo da tela, selecione o menu **Repositório**. ![Menu GitHub Desktop na barra de menu do Mac](/assets/images/help/desktop/select-repository-menu-mac.png)
-2. Clique em **Criar problema no {% data variables.product.prodname_dotcom %}**. ![Valor do repositório no menu Branch](/assets/images/help/desktop/create-issue-mac.png)
-3. Em {% data variables.product.prodname_dotcom %}, clique em **Começar** para abrir um modelo do problema ou clique em **Abrir um problema em branco**. ![Criar novas opções do problema](/assets/images/help/desktop/create-new-issue.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. No canto superior esquerdo da janela, selecione o menu **Repositório**. ![Menu GitHub Desktop na barra de menus do Mac](/assets/images/help/desktop/select-repository-menu-windows.png)
-2. Clique em **Criar problema no {% data variables.product.prodname_dotcom %}**. ![O valor do repositório no menu Branch](/assets/images/help/desktop/create-issue-windows.png)
-3. Em {% data variables.product.prodname_dotcom %}, clique em **Começar** para abrir um modelo do problema ou clique em **Abrir um problema em branco**. ![Criar novas opções do problema](/assets/images/help/desktop/create-new-issue.png)
-
-{% endwindows %}
-
-{% note %}
-
-**Observação**: Se os modelos do problema não estiverem habilitados em seu repositório atual, o {% data variables.product.prodname_desktop %} irá direcionar você para um problema em branco no {% data variables.product.prodname_dotcom %}.
-
-{% endnote %}
-
-### Criar um novo pull request
-Depois de [criar um branch](/desktop/guides/contributing-to-projects/managing-branches) e [fazer commit das alterações](/desktop/guides/contributing-to-projects/committing-and-reviewing-changes-to-your-project), você pode abrir uma pull request para receber feedback das alterações propostas.
-
-{% mac %}
-
-1. No canto superior esquerdo da tela, selecione o menu **Branch**. ![Menu GitHub Desktop na barra de menus do Mac](/assets/images/help/desktop/mac-select-branch-menu.png)
-2. Clique em **Create Pull Request** (Criar pull request). ![Valor Create pull request (Criar pull request) no menu Branch](/assets/images/help/desktop/create-pull-request-mac.png)
-3. No {% data variables.product.prodname_dotcom %}, verifique o padrão do branch _base_ e do branch _compare_ nos menus suspensos e faça a alteração, se necessário. ![Menus suspenso para escolher a base e comparar os branches](/assets/images/help/pull_requests/choose-base-and-compare-branches.png)
-{% data reusables.repositories.pr-title-description %}
-{% data reusables.repositories.create-pull-request %}
-
-{% endmac %}
-
-{% windows %}
-
-1. No canto superior esquerdo da janela, selecione o menu **Branch**. ![Menu GitHub Desktop na barra de menus do Windows](/assets/images/help/desktop/windows-select-branch-menu.png)
-2. Clique em **Create pull request** (Criar pull request). ![Valor Create pull request (Criar pull request) no menu Branch](/assets/images/help/desktop/create-pull-request-win.png)
-3. No {% data variables.product.prodname_dotcom %}, verifique o padrão do branch _base_ e do branch _compare_ nos menus suspensos e faça a alteração, se necessário. ![Menus suspenso para escolher a base e comparar os branches](/assets/images/help/pull_requests/choose-base-and-compare-branches.png)
-{% data reusables.repositories.pr-title-description %}
-{% data reusables.repositories.create-pull-request %}
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/index.md b/translations/pt-BR/content/desktop/contributing-to-projects/index.md
deleted file mode 100644
index e1ee4ca280af..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/index.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Contribuir em projetos com o GitHub Desktop
-shortTitle: Contribuir para projetos
-intro: 'Use o GitHub Desktop para gerenciar projetos, criar commits relevantes e monitorar o histórico de cada projeto em um aplicativo em vez de usar a linha de comando.'
-versions:
- free-pro-team: '*'
----
-
-
-### Índice
-
-{% topic_link_in_list /adding-and-cloning-repositories %}
- {% link_in_list /adding-a-repository-from-your-local-computer-to-github-desktop %}
- {% link_in_list /adding-an-existing-project-to-github-using-github-desktop %}
- {% link_in_list /cloning-and-forking-repositories-from-github-desktop %}
- {% link_in_list /cloning-a-repository-from-github-to-github-desktop %}
-{% topic_link_in_list /making-changes-in-a-branch %}
- {% link_in_list /managing-branches %}
- {% link_in_list /committing-and-reviewing-changes-to-your-project %}
- {% link_in_list /pushing-changes-to-github %}
- {% link_in_list /reverting-a-commit %}
- {% link_in_list /managing-tags %}
- {% link_in_list /viewing-the-branch-history %}
-{% topic_link_in_list /working-with-your-remote-repository-on-github-or-github-enterprise %}
- {% link_in_list /syncing-your-branch %}
- {% link_in_list /creating-an-issue-or-pull-request %}
- {% link_in_list /accessing-a-pull-request-locally %}
- {% link_in_list /changing-a-remotes-url-from-github-desktop %}
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/making-changes-in-a-branch.md b/translations/pt-BR/content/desktop/contributing-to-projects/making-changes-in-a-branch.md
deleted file mode 100644
index 3fe8142a050d..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/making-changes-in-a-branch.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Fazer alterações em um branch
-intro: 'Faça alterações no projeto usando seu editor de texto favorito, como o [Atom] (https://atom.io/). Em seguida, use o {% data variables.product.prodname_desktop %} para exibir commits relevantes.'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/managing-branches.md b/translations/pt-BR/content/desktop/contributing-to-projects/managing-branches.md
deleted file mode 100644
index d836ace0e4fa..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/managing-branches.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Managing branches
-intro: You can create a branch off of a repository's default branch so you can safely experiment with changes.
-redirect_from:
- - /desktop/contributing-to-projects/creating-a-branch-for-your-work
- - /desktop/contributing-to-projects/switching-between-branches
-versions:
- free-pro-team: '*'
----
-
-### About managing branches
-You can use branches to safely experiment with changes to your project. Branches isolate your development work from other branches in the repository. For example, you could use a branch to develop a new feature or fix a bug.
-
-You always create a branch from an existing branch. Typically, you might create a branch from the `master` branch of your repository. You can then work on this new branch in isolation from changes that other people are making to the repository.
-
-Once you're satisfied with your work, you can [open a pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request) to merge the changes in the current branch into another branch. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests)".
-
-You can always create a branch in {% data variables.product.prodname_desktop %} if you have read access to a repository, but you can only push the branch to {% data variables.product.prodname_dotcom %} if you have write access to the repository.
-
-{% data reusables.desktop.protected-branches %}
-
-### Criar um branch
-
-{% tip %}
-
-**Dica:** o primeiro branch que você criar terá como base o branch padrão, que costuma ser `master`. If you have more than one branch, you can choose to base the new branch on the currently checked out branch or the default branch.
-
-{% endtip %}
-
-{% mac %}
-
-{% data reusables.desktop.click-base-branch-in-drop-down %}
- ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-{% data reusables.desktop.create-new-branch %}
- ![Opção New Branch (Novo branch) no menu Branch](/assets/images/help/desktop/new-branch-button-mac.png)
-{% data reusables.desktop.name-branch %}
- ![Campo para criar um nome para o novo branch](/assets/images/help/desktop/create-branch-name-mac.png)
-{% data reusables.desktop.select-base-branch %}
- ![Opções do branch base](/assets/images/help/desktop/create-branch-choose-branch-mac.png)
-{% data reusables.desktop.confirm-new-branch-button %}
- ![Botão Create Branch (Criar branch)](/assets/images/help/desktop/create-branch-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.click-base-branch-in-drop-down %}
- ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/click-branch-in-drop-down-win.png)
-{% data reusables.desktop.create-new-branch %}
- ![Opção New Branch (Novo branch) no menu Branch](/assets/images/help/desktop/new-branch-button-win.png)
-{% data reusables.desktop.name-branch %}
- ![Campo para criar um nome para o novo branch](/assets/images/help/desktop/create-branch-name-win.png)
-{% data reusables.desktop.select-base-branch %}
- ![Opções do branch base](/assets/images/help/desktop/create-branch-choose-branch-win.png)
-{% data reusables.desktop.confirm-new-branch-button %}
- ![Botão Create branch (Criar branch)](/assets/images/help/desktop/create-branch-button-win.png)
-
-{% endwindows %}
-
-### Alternar entre branches
-É possível exibir e fazer commits em qualquer branch do seu repositório. Se houver alterações salvas sem commit, você terá que decidir o que fazer com elas antes de poder alternar entre os branches. Você pode fazer commit das alterações no branch atual, armazená-las no branch atual ou levá-las para o novo branch. Se optar por fazer commit das alterações no branch atual, siga as etapas indicadas em "[Fazer commit e revisar as alterações do projeto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)" antes de alternar entre os branches.
-
-{% tip %}
-
-**Dica**: Você pode definir um comportamento-padrão para alternar branches nas configurações **Avançadas**. For more information, see "[Configuring basic settings](/desktop/getting-started-with-github-desktop/configuring-basic-settings)."
-
-{% endtip %}
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.switching-between-branches %}
- ![Lista de branches no repositório](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-3. Se você tiver alterações salvas sem commit, escolha entre **Leave my changes** (Deixar as alterações) ou **Bring my changes** (Levar as alterações) e clique em **Switch Branch** (Alternar branch). ![Alternar branch com opções de alteração](/assets/images/help/desktop/stash-changes-options.png)
-
-### Recuperar alterações stashed
-Para acessar as alterações com stash em outro branch, volte para o branch em que foi feito o stash das alterações em questão.
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.switching-between-branches %}
- ![Lista de branches no repositório](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-3. Na barra lateral à esquerda, clique em **Stashed Changes** (Alterações stashed). ![Opção Stashed Changes (Alterações stashed)](/assets/images/help/desktop/stashed-changes.png)
-4. Para excluir as alterações stashed, clique em **Discard** (Descartar). Para usá-las, clique em **Restore** (Restaurar). ![Descartar ou restaurar alterações stashed](/assets/images/help/desktop/discard-restore-stash-buttons.png)
-
-### Excluir um branch
-
-You can't delete a branch if it's currently associated with an open pull request. You cannot undo deleting a branch.
-
-{% mac %}
-
-{% data reusables.desktop.select-branch-to-delete %}
- ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-to-delete.png)
-{% data reusables.desktop.delete-branch-mac %}
- ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.select-branch-to-delete %}
- ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-to-delete.png)
-{% data reusables.desktop.delete-branch-win %}
- ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-win.png)
-
-{% endwindows %}
-
-### Leia mais
-
-- "[Clonar um repositório no {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)"
-- "[Branch](/articles/github-glossary/#branch)" no glossário do {% data variables.product.prodname_dotcom %}
-- "[Sobre branches](/articles/about-branches)"
-- "[Branches em um Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" na documentação do Git
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/managing-tags.md b/translations/pt-BR/content/desktop/contributing-to-projects/managing-tags.md
deleted file mode 100644
index a5eafcd4e0a3..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/managing-tags.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Gerenciar tags
-intro: 'Você pode usar {% data variables.product.prodname_desktop %} para criar, fazer push e visualizar tags.'
-versions:
- free-pro-team: '*'
----
-
-### Sobre tags no {% data variables.product.prodname_desktop %}
-
-O {% data variables.product.prodname_desktop %} permite que você crie tags anotadas. É possível usar uma tag para marcar um ponto individual no histórico do seu repositório, incluindo um número de versão para uma versão. Para obter mais informações sobre tags de versão, consulte "[Sobre versões](https://help.github.com/en/github/administering-a-repository/about-releases)"
-
-{% data reusables.desktop.tags-push-with-commits %}
-
-### Criar uma tag
-
-{% data reusables.desktop.history-tab %}
-{% data reusables.desktop.create-tag %}
-{% data reusables.desktop.name-tag %}
-{% data reusables.desktop.confirm-tag %}
-
-### Visualizar tags
-
-{% data reusables.desktop.history-tab %}
-2. Clique em commit.
- {% note %}
-
- **Observação**: {% data variables.product.prodname_desktop %} exibe uma seta {% octicon "arrow-up" aria-label="The up arrow icon" %} se a tag não foi tiver sido empurrada para o repositório remoto.
-
- {% endnote %}
-
- ![Visualizar uma tag no histórico](/assets/images/help/desktop/viewing-tags-in-history.png)
-
-3. Todas as tags associadas ao commit são visíveis nos metadados desse commit. ![Visualizar uma tag no commit](/assets/images/help/desktop/viewing-tags-in-commit.png)
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/pushing-changes-to-github.md b/translations/pt-BR/content/desktop/contributing-to-projects/pushing-changes-to-github.md
deleted file mode 100644
index 89536e3d8831..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/pushing-changes-to-github.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Pushing changes to GitHub
-shortTitle: Pushing changes
-intro: 'As you commit changes to your project locally, you can push those changes to {% data variables.product.prodname_dotcom %} so that others may access them from the remote repository.'
-permissions: People with write permissions can push changes to a repository.
-versions:
- free-pro-team: '*'
----
-
-### About pushing changes to {% data variables.product.prodname_dotcom %}
-
-When you push changes, you send the committed changes in your local repository to the remote repository on {% data variables.product.prodname_dotcom %}. If you change your project locally and want other people to have access to the changes, you must push the changes to {% data variables.product.prodname_dotcom %}.
-
-Before pushing changes, you should update your local branch to include any commits that have been added to the remote repository. If someone has made commits on the remote that are not on your local branch, {% data variables.product.prodname_desktop %} will prompt you to fetch the new commits before pushing your changes to avoid merge conflicts. For more information, see "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)."
-
-{% data reusables.desktop.protected-branches %}
-
-### Pushing changes to {% data variables.product.prodname_dotcom %}
-
-{% note %}
-
-**Note:** {% data variables.product.prodname_desktop %} will reject a push if it exceeds certain limits.
-
-- A push contains a large file over 100MB in size.
-- A push is over 2GB in total size.
-
-{% endnote %}
-
-{% data reusables.desktop.push-origin %}
-2. If {% data variables.product.prodname_desktop %} prompts you to fetch new commits from the remote, click **Fetch**. ![The Fetch button](/assets/images/help/desktop/fetch-newer-commits.png)
-3. Optionally, click **Create Pull Request** to open a pull request and collaborate on your changes. For more information, see "[Creating an issue or pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" ![The Create Pull Request button](/assets/images/help/desktop/create-pull-request.png)
-
-### Leia mais
-- "[Push](/github/getting-started-with-github/github-glossary/#push)" in the {% data variables.product.prodname_dotcom %} glossary
-- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)"
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/reverting-a-commit.md b/translations/pt-BR/content/desktop/contributing-to-projects/reverting-a-commit.md
deleted file mode 100644
index 5f07fd4b44ea..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/reverting-a-commit.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Reverter um commit
-intro: Você pode reverter um commit específico para remover suas alterações do seu branch.
-versions:
- free-pro-team: '*'
----
-
-Ao reverter para um commit anterior, a reversão também passa a ser um commit. Além disso, o commit original fica no histórico do repositório.
-
-{% tip %}
-
-**Dica:** ao reverter vários commits, é melhor fazer a reversão do mais recente para o mais antigo. Reverter commits em outra ordem pode gerar conflitos de merge.
-
-{% endtip %}
-
-{% mac %}
-
-{% data reusables.desktop.history-tab %}
-{% data reusables.desktop.revert-commit %}
- ![Opção Revert (Reverter) acima da exibição diff](/assets/images/help/desktop/commit-revert-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.history-tab %}
-{% data reusables.desktop.revert-commit %}
- ![Opção Revert (Reverter) acima da exibição diff](/assets/images/help/desktop/commit-revert-win.png)
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/switching-between-branches.md b/translations/pt-BR/content/desktop/contributing-to-projects/switching-between-branches.md
deleted file mode 100644
index b14dd1d19e69..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/switching-between-branches.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Alternar entre branches
-intro: É possível exibir e fazer commits em qualquer branch do seu repositório.
-versions:
- free-pro-team: '*'
----
-
-### Alternar entre branches
-Se houver alterações salvas sem commit, você terá que decidir o que fazer com elas antes de poder alternar entre os branches. Você pode fazer commit das alterações no branch atual, armazená-las no branch atual ou levá-las para o novo branch. Se optar por fazer commit das alterações no branch atual, siga as etapas indicadas em "[Fazer commit e revisar as alterações do projeto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)" antes de alternar entre os branches.
-
-{% tip %}
-
-**Dica**: Você pode definir um comportamento-padrão para alternar branches nas configurações **Avançadas**. Para obter mais informações, consulte “[Definindo as configurações básicas](/desktop/getting-started-with-github-desktop/configuring-basic-settings)".
-
-{% endtip %}
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.switching-between-branches %}
- ![Lista de branches no repositório](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-3. Se você tiver alterações salvas sem commit, escolha entre **Leave my changes** (Deixar as alterações) ou **Bring my changes** (Levar as alterações) e clique em **Switch Branch** (Alternar branch). ![Alternar branch com opções de alteração](/assets/images/help/desktop/stash-changes-options.png)
-
-### Recuperar alterações stashed
-Para acessar as alterações com stash em outro branch, volte para o branch em que foi feito o stash das alterações em questão.
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.switching-between-branches %}
- ![Lista de branches no repositório](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-3. Na barra lateral à esquerda, clique em **Stashed Changes** (Alterações stashed). ![Opção Stashed Changes (Alterações stashed)](/assets/images/help/desktop/stashed-changes.png)
-4. Para excluir as alterações stashed, clique em **Discard** (Descartar). Para usá-las, clique em **Restore** (Restaurar). ![Descartar ou restaurar alterações stashed](/assets/images/help/desktop/discard-restore-stash-buttons.png)
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/syncing-your-branch.md b/translations/pt-BR/content/desktop/contributing-to-projects/syncing-your-branch.md
deleted file mode 100644
index ebfbde86a2ee..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/syncing-your-branch.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Sincronizar o branch
-intro: 'Ao enviar commits para o seu projeto no {% data variables.product.prodname_dotcom %}, é possível manter uma cópia local do projeto sincronizada com o repositório remote.'
-versions:
- free-pro-team: '*'
----
-
-Sincronize o branch local com o repositório remote para ver outros commits que possam ter sido adicionados ao branch upstream desde a [criação do branch original](/desktop/guides/contributing-to-projects/managing-branches).
-
-### Atualizar o branch local
-
-1. No {% data variables.product.prodname_desktop %}, alterne para o branch local que você pretende atualizar clicando em {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** (Branch atual). Em seguida, selecione o branch na lista.
-2. Clique em **Fetch origin** (Fetch de origem) para atualizar o branch. ![Botão Fetch origin (Fetch de origem)](/assets/images/help/desktop/fetch-button.png)
-3. Se houver commits no branch remote, será possível enviá-los clicando em **Pull origin** (Enviar origem) ou **Pull origin with rebase** (Enviar origem com rebase). ![Botão Pull origin (Origem do pull)](/assets/images/help/desktop/pull-button.png)
-{% data reusables.desktop.resolve-merge-conflicts %}
-
-### Fazer merge entre o branch do projeto e outro branch
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.choose-a-branch-to-merge %}
-{% data reusables.desktop.confirm-merging-branch %}
-
- {% note %}
-
- **Observação:** se houver conflitos de merge, o {% data variables.product.prodname_desktop %} enviará uma notificação acima do botão **Merge BRANCH into BRANCH** (Fazer merge de branch em branch). Não será possível fazer merge dos branches até a solução de todos os conflitos.
-
- {% endnote %}
-
- ![Botão Merge](/assets/images/help/desktop/merge-branch-button.png)
-{% data reusables.desktop.push-origin %}
-
-### Fazer rebase entre o branch do projeto e outro branch
-Alguns fluxos de trabalho exigem ou preferem o rebasing ao merging. Ao fazer o rebase, é possível reordenar, editar ou juntar commits. Para obter mais informações, consulte "[Rebase no Git](/articles/about-git-rebase)".
-
-1. Use o menu suspenso **Branch** e clique em **Rebase Current Branch** (Fazer rebase do branch atual). ![Rebase do branch atual na lista suspensa de branches](/assets/images/help/desktop/rebase-current-branch.png)
-2. Clique no branch desejado para fazer rebase com o branch atual. Em seguida, clique em **Start rebase** (Iniciar rebase). ![Botão Start rebase (Iniciar rebase)](/assets/images/help/desktop/start-rebase-button.png)
-3. Se tiver certeza da operação de rebase, clique em **Begin rebase** (Começar rebase). ![Botão Begin rebase (Começar rebase)](/assets/images/help/desktop/begin-rebase-button.png)
-{% data reusables.desktop.resolve-merge-conflicts %}
-4. Para fazer push das alterações locais, clique em **Force push origin** (Forçar push da origem). ![Force push origin (Forçar push de origem)](/assets/images/help/desktop/force-push-origin.png)
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/viewing-the-branch-history.md b/translations/pt-BR/content/desktop/contributing-to-projects/viewing-the-branch-history.md
deleted file mode 100644
index 1c802fd0d814..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/viewing-the-branch-history.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Exibir o histórico do branch
-intro: 'Você pode ver informações sobre qualquer commit no {% data variables.product.prodname_desktop %}, incluindo uma diff das alterações introduzidas pelo commit.'
-versions:
- free-pro-team: '*'
----
-
-Cada commit mostra o seguinte:
-
- - A mensagem do commit;
- - O momento em que o commit foi criado;
- - O nome de usuário e a foto de perfil do autor do commit;
- - O hash SHA-1 (ID exclusivo) do commit.
-
-{% data reusables.desktop.history-tab %}
-2. Na guia **History** (Histórico), clique no commit que deseja revisar. ![Commit na guia History (Histórico)](/assets/images/help/desktop/branch-history-commit.png)
-3. Se houver vários arquivos no commit, clique em um deles para ver as mudanças feitas no arquivo e no commit em questão. ![Arquivo no commit](/assets/images/help/desktop/branch-history-file.png)
-
-### Further reading
-
-- "[Sincronizar o branch](/desktop/guides/contributing-to-projects/syncing-your-branch/)"
diff --git a/translations/pt-BR/content/desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise.md b/translations/pt-BR/content/desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise.md
deleted file mode 100644
index f98bb0d15f6e..000000000000
--- a/translations/pt-BR/content/desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Usar repositórios remote no GitHub ou no GitHub Enterprise
-intro: 'As alterações feitas no seu projeto local podem ser refletidas no repositório remote. No Git, o termo *remote* descreve o servidor onde o seu código está armazenado. No seu caso, esse servidor é um repositório no {% data variables.product.prodname_dotcom %} ou no {% data variables.product.prodname_enterprise %}.'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/about-the-github-desktop-windows-installer-package.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/about-the-github-desktop-windows-installer-package.md
deleted file mode 100644
index 91cc2340fa58..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/about-the-github-desktop-windows-installer-package.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Sobre o pacote Windows Installer do GitHub Desktop
-intro: 'O administrador da rede pode usar o arquivo do pacote Windows Installer (`.msi`) com a Política de Grupo ou outro sistema de instalação remota para implantar o {% data variables.product.prodname_desktop %} em computadores com o Microsoft Windows em uma rede gerenciada do Active Directory.'
-versions:
- free-pro-team: '*'
----
-
-O pacote Windows Installer extrai o instalador autônomo (`.exe `) e configura o Windows para instalar o {% data variables.product.prodname_desktop %} quando um usuário faz login na estação de trabalho. Os usuários devem ter permissão para instalar o {% data variables.product.prodname_desktop %} em seus respectivos diretórios.
-
-Se executar diretamente o pacote Windows Installer do {% data variables.product.prodname_desktop %}, o usuário terá que sair e voltar à estação de trabalho para concluir a instalação.
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/authenticating-to-github.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/authenticating-to-github.md
deleted file mode 100644
index 50fcb064ea30..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/authenticating-to-github.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Autenticar com o GitHub
-intro: 'Conecte sua conta {% data variables.product.product_name %} ao {% data variables.product.prodname_desktop %}.'
-redirect_from:
- - /desktop/getting-started-with-github-desktop/authenticating-to-github-using-the-browser
-versions:
- free-pro-team: '*'
----
-
-Antes de autenticar, {% data reusables.desktop.get-an-account %}
-
-{% mac %}
-
-### Fazer a autenticação no {% data variables.product.prodname_dotcom %} usando o navegador
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-{% data reusables.desktop.mac-select-accounts %}
-4. À direita de "{% data variables.product.prodname_dotcom %}," clique **Iniciar sessão**. ![Botão Sign In (Entrar) do GitHub](/assets/images/help/desktop/mac-sign-in-github.png)
-5. No painel Sign in (Entrar), clique em **Sign in using your browser** (Entrar via navegador). ![Link Sign in using your browser (Entrar via navegador)](/assets/images/help/desktop/mac-sign-in-browser.png)
-{% data reusables.desktop.authenticate-in-browser %}
-{% data reusables.desktop.retrieve-2fa-in-browser %}
-{% data reusables.desktop.enter-2fa-in-browser %}
-9. Depois que o {% data variables.product.prodname_dotcom %} autenticar sua conta, volte ao {% data variables.product.prodname_desktop %}.
-
-### Fazer a autenticação no {% data variables.product.prodname_dotcom %} usando seu nome de usuário e senha
-
-{% data reusables.user_settings.password-authentication-deprecation-desktop %}
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-{% data reusables.desktop.mac-select-accounts %}
-{% data reusables.desktop.choose-product-authenticate %}
-5. Para adicionar uma conta do GitHub Enterprise, digite suas credenciais em "Enterprise server address" (Endereço do servidor Enterprise) e clique em **Continue** (Continuar). ![Botão Sign In (Entrar) do GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-button-enterprise.png)
-6. Para adicionar uma conta do GitHub, digite as credenciais do GitHub.com e clique em **Sign in** (Entrar). ![Botão Sign In (Entrar) do GitHub](/assets/images/help/desktop/mac-sign-in-button.png)
-{% data reusables.desktop.retrieve-2fa %}
-{% data reusables.desktop.return-to-desktop %} No prompt, insira seu código 2FA e clique em **Sign in** (Entrar). ![Solicitação do código 2FA](/assets/images/help/desktop/mac-2fa-code-prompt.png)
-
-{% endmac %}
-
-{% windows %}
-
-### Fazer a autenticação no {% data variables.product.prodname_dotcom %} usando o navegador
-
-{% data reusables.desktop.windows-choose-options %}
-{% data reusables.desktop.windows-select-accounts %}
-4. À direita do "GitHub.com", clique **Iniciar sessão**. ![Botão Sign In (Entrar) do GitHub](/assets/images/help/desktop/windows-sign-in-github.png)
-5. No painel Sign in (Entrar), clique em **Sign in using your browser** (Entrar via navegador). ![Link Sign in using your browser (Entrar via navegador)](/assets/images/help/desktop/windows-sign-in-browser.png)
-{% data reusables.desktop.authenticate-in-browser %}
-{% data reusables.desktop.retrieve-2fa-in-browser %}
-{% data reusables.desktop.enter-2fa-in-browser %}
-9. Depois que o {% data variables.product.prodname_dotcom %} autenticar sua conta, volte ao {% data variables.product.prodname_desktop %}.
-
-### Fazer a autenticação no {% data variables.product.prodname_dotcom %} usando seu nome de usuário e senha
-
-
-{% data reusables.user_settings.password-authentication-deprecation-desktop %}
-
-{% data reusables.desktop.windows-choose-options %}
-{% data reusables.desktop.windows-select-accounts %}
-{% data reusables.desktop.choose-product-authenticate %}
-5. Para adicionar uma conta do GitHub Enterprise, digite suas credenciais em "Enterprise server address" (Endereço do servidor Enterprise) e clique em **Continue** (Continuar). ![Botão Sign In (Entrar) do GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-button-enterprise.png)
-6. Para adicionar uma conta do GitHub, digite as credenciais do GitHub.com e clique em **Sign in** (Entrar). ![Botão Sign In (Entrar) do GitHub](/assets/images/help/desktop/windows-sign-in-button.png)
-{% data reusables.desktop.retrieve-2fa %}
-{% data reusables.desktop.return-to-desktop %} No prompt, insira seu código 2FA e clique em **Sign in** (Entrar). ![Solicitação do código 2FA](/assets/images/help/desktop/windows-2fa-code-prompt.png)
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-a-default-editor.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-a-default-editor.md
deleted file mode 100644
index 1b1b2a3da79b..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-a-default-editor.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Configurar o editor padrão
-intro: Você pode configurar o GitHub Desktop para abrir arquivos em seu projeto com seu editor de texto preferido ou ambiente de desenvolvimento integrado (IDE).
-versions:
- free-pro-team: '*'
----
-
-### Editores compatíveis
-
-O {% data variables.product.prodname_desktop %} é compatível com os seguintes editores.
-
-{% mac %}
-
-- [Atom](https://atom.io/)
-- [MacVim](https://macvim-dev.github.io/macvim/)
-- [Visual Studio Code](https://code.visualstudio.com/)
-- [Visual Studio Codium](https://vscodium.com/)
-- [Sublime Text](https://www.sublimetext.com/)
-- [BBEdit](http://www.barebones.com/products/bbedit/)
-- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/)
-- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/)
-- [JetBrains Rider](https://www.jetbrains.com/rider/)
-- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/)
-- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/)
-- [JetBrains IntelliJ IDEA](https://www.jetbrains.com/idea/)
-- [JetBrains GoLand](https://www.jetbrains.com/go/)
-- [TextMate](https://macromates.com/)
-- [Brackets](http://brackets.io/)
- - Para usar Brackets com {% data variables.product.prodname_desktop %}, você deve instalar o atalho da Linha de Comando. Para instalar o atalho, abra o Brackets, clique em **Arquivo** na barra de menu e, em seguida, clique em **Instalar atalho da linha de comando**.
-- [Typora](https://typora.io/)
-- [CodeRunner](https://coderunnerapp.com/)
-- [SlickEdit](https://www.slickedit.com/)
-- [Xcode](https://developer.apple.com/xcode/)
-- [Android Studio](https://developer.android.com/studio)
-
-{% endmac %}
-
-{% windows %}
-
-- [Atom](https://atom.io/)
-- [Visual Studio Code](https://code.visualstudio.com/)
-- [Visual Studio Codium](https://vscodium.com/)
-- [Sublime Text](https://www.sublimetext.com/)
-- [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html)
-- [Typora](https://typora.io/)
-- [SlickEdit](https://www.slickedit.com/)
-- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/)
-- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/)
-- [JetBrains Rider](https://www.jetbrains.com/rider/)
-- [Notepad++](https://notepad-plus-plus.org/)
-
-{% endwindows %}
-
-### Configurar o editor padrão
-
-{% mac %}
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-3. Na janela preferências, selecione **Integrações**. ![O painel integrações na janela preferências](/assets/images/help/desktop/mac-select-integrations-pane.png)
-4. Use o menu suspenso "Editor externo" e escolha o editor que deseja definir como padrão. ![Menu External editor (Editor externo) na barra de menus Preferences (Preferências)](/assets/images/help/desktop/mac-editor-menu.png)
-5. Clique em **Save** (Salvar).
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.windows-choose-options %}
-3. Na janela opções, selecione **Integrações**. ![O painel de integrações na janela opções](/assets/images/help/desktop/windows-select-integrations-pane.png)
-4. Use o menu suspenso "Editor externo" e escolha o editor que deseja definir como padrão. ![Menu External editor (Editor externo) na barra de menus Options (Opções)](/assets/images/help/desktop/windows-editor-menu.png)
-5. Clique em **Save** (Salvar).
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop.md
deleted file mode 100644
index c0a5c6b1d1f5..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Configurar e personalizar o GitHub Desktop
-intro: 'Configure o Git, conecte o seu editor-padrão e personalize as configurações para alinhar o GitHub Desktop com seu fluxo de trabalho.'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-basic-settings.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-basic-settings.md
deleted file mode 100644
index 738afbe6b904..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-basic-settings.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Definir configurações básicas
-intro: 'É possível acessar as configurações para proteger a privacidade, conectar contas ao GitHub Desktop e configurar o Git.'
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-3. Para visualizar ou alterar as suas configurações, alterne entre os painéis a seguir: ![Navegação no menu Preferences (Preferências)](/assets/images/help/desktop/mac-select-accounts-pane.png)
-{% data reusables.desktop.preferences-options-tabs %}
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.windows-choose-options %}
-2. Para visualizar ou alterar as suas configurações, alterne entre os painéis a seguir: ![Navegação no menu Options (Opções)](/assets/images/help/desktop/windows-select-accounts-pane.png)
-{% data reusables.desktop.preferences-options-tabs %}
-
-{% endwindows %}
-
-### Further reading
-
-- "[Configurar tema para o {% data variables.product.prodname_desktop %}](/desktop/guides/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)"
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop.md
deleted file mode 100644
index 37c10dc7c09f..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Configurar o Git para o GitHub Desktop
-shortTitle: Configurar o Git
-intro: 'Caso ainda não tenha o Git instalado, configure-o antes de usar o GitHub Desktop.'
-versions:
- free-pro-team: '*'
----
-
-{% data variables.product.prodname_desktop %} usa o endereço de e-mail que você definiu na configuração local do Git para conectar commits à sua conta no {% data variables.product.product_name %}.
-
-{% data reusables.desktop.update-email-address %}
-
-{% tip %}
-
-**Dica**: Qualquer pessoa poderá ver o endereço de e-mail na configuração do seu Git se fizer commits públicos. Para obter mais informações, consulte "[Configurar o endereço de e-mail do commit](/articles/setting-your-commit-email-address/)";
-
-{% endtip %}
-
-{% mac %}
-
-{% data reusables.desktop.sign-in-choose-product %}
-{% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.emails %}
-{% data reusables.desktop.copy-email-git-config %}
-{% data reusables.desktop.return-to-desktop %}
-{% data reusables.desktop.mac-select-desktop-menu %}
-7. Na janela de Preferências, clique em **Git**. ![O Painel Git no menu Preferences (Preferências)](/assets/images/help/desktop/mac-select-git-pane.png)
-{% data reusables.desktop.name-field-git-config %}
- ![O campo de nome da configuração do Git](/assets/images/help/desktop/mac-name-git-config.png)
-{% data reusables.desktop.paste-email-git-config %}
- ![Endereço de e-mail colado no campo de configuração do Git](/assets/images/help/desktop/mac-email-git-config.png)
-{% data reusables.desktop.click-save-git-config %}
- ![Botão para salvar no campo de configuração do Git](/assets/images/help/desktop/mac-save-git-config.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.sign-in-choose-product %}
-{% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.emails %}
-{% data reusables.desktop.copy-email-git-config %}
-{% data reusables.desktop.return-to-desktop %}
-{% data reusables.desktop.windows-choose-options %}
-8. Na janela de Opções, clique em **Git**. ![O Painel Git no menu Options (Opções)](/assets/images/help/desktop/windows-select-git-pane.png)
-{% data reusables.desktop.name-field-git-config %}
- ![O campo de nome da configuração do Git](/assets/images/help/desktop/windows-name-git-config.png)
-{% data reusables.desktop.paste-email-git-config %}
- ![Endereço de e-mail colado no campo de configuração do Git](/assets/images/help/desktop/windows-email-git-config.png)
-{% data reusables.desktop.click-save-git-config %}
- ![Botão para salvar no campo de configuração do Git](/assets/images/help/desktop/windows-save-git-config.png)
-
-{% endwindows %}
-
-### Further reading
-
-- "[Adicionar um endereço de e-mail à conta do GitHub](/articles/adding-an-email-address-to-your-github-account/)"
-- "[Configurar o endereço de e-mail do commit no Git](/articles/setting-your-commit-email-address/)"
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop.md
deleted file mode 100644
index 60232a17d5b2..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: Criar o primeiro repositório usando o GitHub Desktop
-intro: 'Você pode usar o {% data variables.product.prodname_desktop %} para começar a trabalhar com um repositório Git sem depender da linha de comando.'
-versions:
- free-pro-team: '*'
----
-
-### Introdução
-
-Este guia documenta o processo de uso do {% data variables.product.prodname_desktop %} para trabalhar em um repositório Git. O {% data variables.product.prodname_desktop %} amplia e simplifica o fluxo de trabalho no {% data variables.product.prodname_dotcom_the_website %} com uma interface visual, em vez de comandos de texto na linha de comando. Ao fim da leitura deste guia, você terá usado o {% data variables.product.prodname_desktop %} para criar um repositório, alterá-lo e publicar as alterações no {% data variables.product.prodname_dotcom_the_website %} ou no {% data variables.product.prodname_ghe_server %}.
-
-Depois de baixar o {% data variables.product.prodname_desktop %} e entrar no {% data variables.product.prodname_dotcom %} ou {% data variables.product.prodname_enterprise %}, você pode criar e clonar um repositório de tutorial. O tutorial apresentará os conceitos básicos de trabalhar com o Git e o {% data variables.product.prodname_dotcom %}, incluindo instalar um editor, criar um branch, fazer um commit, enviar para o {% data variables.product.prodname_dotcom_the_website %} e criar uma pull request. O tutorial será disponibilizado desde que você ainda não tenha repositórios no {% data variables.product.prodname_desktop %}.
-
-### Etapa 1. Instalar e entrar no {% data variables.product.prodname_desktop %}
-
-1. Baixe o {% data variables.product.prodname_desktop %} em {% data variables.product.desktop_link %}. O {% data variables.product.prodname_desktop %} dá suporte às versões mais recentes do Windows e do Mac. Para obter as instruções específicas de instalação no seu sistema operacional, consulte "[Instalar o {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-github-desktop)."
-
-2. Inicie o {% data variables.product.prodname_desktop %} e siga o fluxo inicial de boas-vindas para acessar sua conta do {% data variables.product.product_name %}. Na etapa "Configure Git" (Configurar Git), será possível definir seu nome e endereço de e-mail. Para garantir a atribuição adequada dos commits à sua conta do {% data variables.product.product_name %}, use o endereço de e-mail associado à conta do {% data variables.product.product_name %}. Para obter mais informações sobre a atribuição de commits, consulte "[Configurar o endereço de e-mail do commit](/articles/setting-your-commit-email-address)".
-
-### Etapa 2. Criar um repositório
-
-Você verá uma exibição "Let's get started!" (Vamos começar!), onde é possível optar por criar e clonar um repositório de tutorial, clonar um repositório existente, criar um repositório ou adicionar um repositório existente.
-
-#### Criar e clonar um repositório de tutorial
-
-1. Clique em **Create a tutorial repository and clone it** (Criar um repositório de tutorial e cloná-lo). ![Botão Create and clone a tutorial repository (Criar e clonar um repositório de tutorial)](/assets/images/help/desktop/getting-started-guide/create-and-clone-a-tutorial-repository.png)
-2. Siga as solicitações no tutorial.
-
-#### Criar um repositório
-
-1. Clique em **Create a New Repository on your hard drive** (Criar um repositório no disco rígido). ![Criar um repositório](/assets/images/help/desktop/getting-started-guide/creating-a-repository.png)
-2. Para criar um novo repositório, preencha os campos: ![Opções de criar um repositório](/assets/images/help/desktop/getting-started-guide/create-a-new-repository-options.png)
- - "Name" (Nome) define o nome do repositório no local e no {% data variables.product.product_name %}.
- - "Description" (Descrição) é um campo opcional com mais informações sobre o propósito do repositório.
- - "Local path" (Caminho local) define o local do repositório no computador. Por padrão, o {% data variables.product.prodname_desktop %} cria uma pasta _GitHub_ dentro da pasta _Documents_ (Documentos) para armazenar seus repositórios, mas é possível escolher qualquer local no computador. O novo repositório será uma pasta dentro do local escolhido. Por exemplo, se você nomear o repositório como `Tutorial`, será criada uma pasta de nome _Tutorial_ dentro da pasta no caminho selecionado. O {% data variables.product.prodname_desktop %} registra o local escolhido para as próximas vezes que você criar ou clonar repositórios.
- - A opção **Initialize this repository with a README** (Inicializar este repositório com um LEIAME) cria o commit com um arquivo _LEIAME.md_. Arquivos LEIAME ajudam as pessoas a entenderem o objetivo do seu projeto. Portanto, é recomendável usar esse item e adicionar informações úteis a ele. Quando alguém acessar seu repositório no {% data variables.product.product_name %}, a primeira informação exibida será o LEIAME. Para obter mais informações, consulte "[Sobre LEIAME](/articles/about-readmes)".
- - O menu suspenso **Git ignore** (Git para ignorar) permite incluir um arquivo personalizado para ignorar determinados arquivos no repositório local, isto é, informações que você não quer armazenar no controle de versão. Se houver uma linguagem ou framework específico para uso, você poderá selecionar uma opção na lista disponível. Se você estiver começando agora, fique à vontade para ignorar essa opção. Para obter mais informações, consulte "[Ignorar arquivos](/articles/ignoring-files)".
- - O menu suspenso **License** (Licença) permite adicionar uma licença de código aberto a um arquivo _LICENSE_ no repositório. Não se preocupe em adicionar uma licença de imediato. Para obter mais informações sobre as licenças de código aberto disponíveis e sobre como adicioná-las ao repositório, consulte "[Criar a licença de um repositório](/articles/licensing-a-repository)."
-3. Clique em **Create Repository** (Criar repositório).
-
-### Etapa 3. Explorar o {% data variables.product.prodname_desktop %}
-
-Agora que você criou um repositório, o menu de arquivos aparecerá na parte superior da tela. É nele que você pode acessar as configurações e ações possíveis no {% data variables.product.prodname_desktop %}. A maioria das ações tem atalhos de teclado para aumentar a eficiência do seu trabalho. Para obter uma lista completa de atalhos de teclado, consulte "[Atalhos de teclado](/desktop/getting-started-with-github-desktop/keyboard-shortcuts)".
-
-1. Abaixo do menu, uma barra mostra o estado atual do repositório no {% data variables.product.prodname_desktop %}:
- - **Current repository** (Repositório atual) mostra o nome do repositório em que você está trabalhando. Você pode clicar em **Current repository** (Repositório atual) para alternar entre repositórios no {% data variables.product.prodname_desktop %}.
- - **Current branch** (Branch atual) mostra o nome do branch em que você está trabalhando. Você pode clicar em **Current branch** (Branch atual) para exibir todos os branches do repositório, alternar entre branches ou criar um branch. Depois de criar pull requests no repositório, você também poderá exibi-las clicando em **Current branch** (Branch atual).
- - A opção **Publish repository** (Publicar repositório) aparece porque você ainda não publicou o repositório no {% data variables.product.product_name %}. A publicação será feita depois, em outra etapa.
-
- ![Explorar o GitHub Desktop](/assets/images/help/desktop/getting-started-guide/explore-github-desktop.png)
-
-2. Na barra lateral à esquerda, você verá **Changes** (Alterações) e **History** (Histórico).
-
- - A opção **Changes** (Alterações) mostra as mudanças que você fez nos arquivos do branch atual, mas que ainda estão sem commit no repositório local. Na parte inferior, você verá as caixas "Summary" (Resumo) e "Description" (Descrição), além do botão **Commit to master** (Fazer commit para o mestre). É nessa área que você fará o commit das novas alterações. O botão **Commit** (Fazer commit) mostra para qual branch você fará o commit das alterações. ![Área do commit](/assets/images/help/desktop/getting-started-guide/commit-area.png)
-
- - A opção **History** (Histórico) mostra os commits anteriores no branch atual do repositório. Provavelmente você verá um "Initial commit" (Commit inicial) criado pelo {% data variables.product.prodname_desktop %} quando você criou o repositório. À direita do commit, dependendo das opções escolhidas durante a criação do repositório, você poderá ver arquivos _.gitattributes_, _.gitignore_, _LICENÇA_ ou _LEIAME_. Ao clicar em cada arquivo você verá o diff, que consiste no registro das alterações feitas no arquivo do commit em questão. O diff não mostra todo o conteúdo do arquivo, mas somente as partes que foram alteradas. ![Exibição de histórico](/assets/images/help/desktop/getting-started-guide/history-view.png)
-
-### Etapa 4. Fazer push do repositório para o {% data variables.product.product_name %}
-
-No momento, o repositório só existe no seu computador e somente você pode acessá-lo. Publicar o repositório no {% data variables.product.product_name %} vai mantê-lo sincronizado em vários computadores e para todos os integrantes das equipes do projeto em questão. Para publicar o repositório, você fará o "push" dele no {% data variables.product.product_name %}, o que também o deixará disponível no {% data variables.product.prodname_dotcom_the_website %}.
-
-1. Clique em **Publish repository** (Publicar repositório). ![Publicar repositório](/assets/images/help/desktop/getting-started-guide/publish-repository.png)
- - Você verá alguns campos familiares. "Name" (Nome) e "Description" (Descrição) são os mesmos que você preencheu ao criar o repositório.
- - Você verá a opção **Keep this code private** (Manter este código privado). Selecione-a se não quiser compartilhar seu código publicamente com outros usuários no {% data variables.product.product_name %}.
- - A opção suspensa **Organization** (Organização), se houver, permite publicar o repositório em uma organização específica a que você pertença no {% data variables.product.product_name %}. Não tem problema se você ainda não for integrante de uma organização. ![Etapas para publicar repositório](/assets/images/help/desktop/getting-started-guide/publish-repository-steps.png)
-2. Clique em **Publish repository** (Publicar repositório).
-3. É possível acessar o repositório no {% data variables.product.prodname_dotcom %} pelo {% data variables.product.prodname_desktop %}. No menu do arquivo, clique em **Repository** (Repositório) e em **View on GitHub** (Exibir no GitHub). Fazer isso levará você diretamente para o repositório no seu navegador padrão.
-
-Agora que o repositório foi publicado, vamos voltar ao {% data variables.product.prodname_desktop %} e fazer mais alterações no repositório local. Começaremos mostrando como configurar um editor de texto padrão.
-
-### Etapa 5. Configurar um editor de texto
-
-Para reduzir o tempo de configuração do ambiente de desenvolvimento, é possível iniciar vários editores de texto e ambientes de desenvolvimento integrado (IDE) diretamente no {% data variables.product.prodname_desktop %}. Em um repositório no {% data variables.product.prodname_desktop %}, você pode abrir a pasta do projeto no seu editor de texto favorito.
-
-1. Clique em **File** (Arquivo), **Options** (Opções) e **Advanced** (Avançado).
-2. Use o menu suspenso **External editor** (Editor externo) e selecione um editor. A lista mostrará todos os editores instalados. Se a lista estiver vazia, instale um editor compatível, como o [Atom](https://atom.io). Para obter uma lista dos editores compatíveis, consulte a integração ["Abrir editores externos" ](https://github.com/desktop/desktop/blob/development/docs/technical/editor-integration.md#windows) no repositório do {% data variables.product.prodname_desktop %}. ![Editor externo](/assets/images/help/desktop/mac-editor-menu.png)
-3. Caso tenha instalado um editor, reinicie o {% data variables.product.prodname_desktop %} para fazê-lo aparecer na lista suspensa **External editor** (Editor externo).
-
-### Etapa 6. Fazer commit e push das alterações
-
-Agora que você configurou um editor padrão, será possível fazer alterações no projeto e começar a criar seu primeiro commit no repositório.
-
-1. Para iniciar o editor externo pelo {% data variables.product.prodname_desktop %}, clique em **Repository** (Repositório) e em **Open in EDITOR** (Abrir no EDITOR). ![Abrir no editor](/assets/images/help/desktop/getting-started-guide/open-in-editor.png)
-
-2. Comece fazendo algumas alterações no arquivo _README.md_ criado anteriormente. Adicione informações que descrevam o projeto, como a função, a relevância e a utilidade dele. Lembre-se de que esta será a primeira interação das pessoas com o seu projeto. Depois disso, estará tudo pronto para fazer o seu primeiro commit!
-3. Saia do editor de texto, volte para o {% data variables.product.prodname_desktop %} e navegue até a guia **Changes** (Alterações). Na lista de arquivos, você verá o _README.md_ alterado. A marca de verificação no arquivo _README.md_ indica que as alterações feitas serão parte do seu commit. Talvez você queira fazer alterações em vários arquivos no futuro, mas sem fazer o commit das alterações de todos eles. O {% data variables.product.prodname_desktop %} permite selecionar somente as alterações que você pretende incluir no commit. ![Exibir alterações](/assets/images/help/desktop/getting-started-guide/viewing-changes.png)
-
-4. Na parte inferior da lista **Changes** (Alterações), adicione uma mensagem ao commit. À direita da sua foto de perfil, digite uma breve descrição do commit. Já que estamos alterando o arquivo _README.md_, algo como "Adicionar informações sobre o propósito do projeto" seria um bom resumo. Abaixo do resumo, o campo de texto "Description" (Descrição) permite digitar uma descrição mais longa das alterações feitas no commit. Essa descrição pode ser útil para analisar o histórico de um projeto e entender o motivo das alterações. Como estamos fazendo uma atualização básica do arquivo _README.md_, fique à vontade para ignorar a descrição. ![Mensagem do commit](/assets/images/help/desktop/getting-started-guide/commit-message.png)
-5. Clique em **Commit to master** (Fazer commit para o mestre). O botão do commit mostra o branch atual (`mestre`, neste caso) para que você tenha certeza de fazer commit para o branch desejado. ![Fazer commit para o mestre](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png)
-6. Para fazer push das alterações no repositório remote no {% data variables.product.product_name %}, clique em **Push origin** (Fazer push da origem). ![Fazer push de origem](/assets/images/help/desktop/getting-started-guide/push-to-origin.png)
- - Você se lembra do botão **Publish** (Publicar) usado para publicar o repositório no {% data variables.product.product_name %}? Agora, ele deve mostrar `Push origin` (Fazer push da origem) com um número `1` ao lado, indicando que ainda não foi feito o push de um commit para o {% data variables.product.product_name %}.
- - O termo "origem" na opção **Push origin** (Fazer push da origem) indica que estamos fazendo push das alterações para o remote chamado `origem` que, neste caso, é o repositório do seu projeto no {% data variables.product.prodname_dotcom_the_website %}. Até você fazer o push de qualquer commit para o {% data variables.product.product_name %}, haverá diferenças entre o repositório do seu projeto no computador e o repositório do seu projeto no {% data variables.product.prodname_dotcom_the_website %}. Assim, você pode trabalhar no local e deixar para fazer push do seu trabalho no {% data variables.product.prodname_dotcom_the_website %} quando estiver tudo pronto.
-7. Na área aberta ao lado da guia **Changes** (Alterações), você verá uma série de sugestões das suas próximas ações. Para abrir o repositório no {% data variables.product.product_name %} no navegador, clique em **View on GitHub** (Exibir no GitHub). ![Exibir no GitHub](/assets/images/help/desktop/getting-started-guide/view-on-github.png)
-8. No navegador, clique em **2 commits**. Você verá uma lista dos commits neste repositório no {% data variables.product.product_name %}. O primeiro commit deve ser o que você acabou de fazer no {% data variables.product.prodname_desktop %}! ![Clicar em dois commits](/assets/images/help/desktop/getting-started-guide/click-two-commits.png)
-
-### Conclusão
-
-Parabéns! Você acabou de criar e publicar um repositório no {% data variables.product.product_name %}, e também fez um commit e fez push das alterações. Isso é apenas o começo! Você pode fazer muito mais com o {% data variables.product.product_name %} e o {% data variables.product.prodname_desktop %}. Esperamos que esse exercício estimule a sua vontade de conhecer ainda mais nossos recursos e possibilidades.
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/index.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/index.md
deleted file mode 100644
index c12b336f8a88..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/index.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Introdução ao GitHub Desktop
-shortTitle: Guia de Introdução
-intro: 'Configure o GitHub Desktop para gerenciar o trabalho no seu projeto. Faça a autenticação no GitHub.com ou no GitHub Enterprise Server, mantenha o aplicativo atualizado e revise suas configurações preferenciais.'
-redirect_from:
- - /desktop/getting-started-with-github-desktop/setting-up-github-desktop/
-versions:
- free-pro-team: '*'
----
-
-
-### Índice
-
-{% topic_link_in_list /overview %}
- {% link_in_list /creating-your-first-repository-using-github-desktop %}
- {% link_in_list /keyboard-shortcuts %}
- {% link_in_list /launching-github-desktop-from-the-command-line %}
-{% topic_link_in_list /installing-and-authenticating-to-github-desktop %}
- {% link_in_list /installing-github-desktop %}
- {% link_in_list /authenticating-to-github %}
- {% link_in_list /about-the-github-desktop-windows-installer-package %}
- {% link_in_list /updating-github-desktop %}
- {% link_in_list /uninstalling-github-desktop %}
-{% topic_link_in_list /configuring-and-customizing-github-desktop %}
- {% link_in_list /configuring-basic-settings %}
- {% link_in_list /configuring-git-for-github-desktop %}
- {% link_in_list /configuring-a-default-editor %}
- {% link_in_list /setting-a-theme-for-github-desktop %}
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop.md
deleted file mode 100644
index 3bf19e603d5b..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Instalar e efetuar a autenticação no GitHub Desktop
-intro: Instale o GitHub Desktop e conecte suas contas do GitHub ou do GitHub Enterprise.
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/installing-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/installing-github-desktop.md
deleted file mode 100644
index 936f55c7db4a..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/installing-github-desktop.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Instalar o GitHub Desktop
-intro: É possível instalar o GitHub Desktop nos sistemas operacionais Microsoft Windows ou macOS suportados.
-versions:
- free-pro-team: '*'
----
-
-Antes de configurar o {% data variables.product.prodname_desktop %}, {% data reusables.desktop.get-an-account %}
-
-### Baixar e instalar o {% data variables.product.prodname_desktop %}
-
-{% mac %}
-
-Você pode instalar o {% data variables.product.prodname_desktop %} nas versões {% data variables.desktop.mac-osx-versions %}.
-
-{% data reusables.desktop.download-desktop-page %}
-2. Escolha a opção **Download for Mac** (Baixar para Mac).
-3. Na pasta **Downloads** do computador, clique duas vezes no arquivo zip **{% data variables.product.prodname_desktop %}**.
-4. Depois de descompatar o arquivo zip, clique duas vezes no **{% data variables.product.prodname_desktop %}**.
-
-{% endmac %}
-
-{% windows %}
-
-Você pode instalar o {% data variables.product.prodname_desktop %} nas versões {% data variables.desktop.windows-versions %}.
-
-{% warning %}
-
-**Aviso**: para executar o {% data variables.product.prodname_desktop %}, o sistema operacional deve ter 64 bits.
-
-{% endwarning %}
-
-{% data reusables.desktop.download-desktop-page %}
-2. Escolha a opção **Download for Windows** (Baixar para Windows).
-
- {% note %}
-
- **Observação:** administradores de rede podem usar o [ pacote Windows Installer do {% data variables.product.prodname_desktop %}](/desktop/guides/getting-started-with-github-desktop/about-the-github-desktop-windows-installer-package/) para implantar o {% data variables.product.prodname_desktop %}.
-
- {% endnote %}
-
-3. Na pasta de **Downloads** do computador, clique duas vezes no **{% data variables.product.prodname_desktop %}**.
-4. Na janela pop-up, clique em **Install** (Instalar).
-5. Após a instalação do programa, clique em **Run** (Executar).
-
-{% endwindows %}
-
-### Configurar o {% data variables.product.prodname_desktop %}
-
-É possível configurar o {% data variables.product.prodname_desktop %} logo após iniciar o {% data variables.product.prodname_desktop %}, mas você também pode ignorar o processo de configuração.
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop.md
deleted file mode 100644
index 53a6650f66ce..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: Atalhos de teclado no GitHub Desktop
-intro: 'É possível usar atalhos de teclado no {% data variables.product.prodname_desktop %}.'
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-Atalhos de teclado do GitHub Desktop no macOS
-
-### Atalhos para o site
-
-| Atalho | Descrição |
-| ------------------------------------ | -------------------------------------------------------------------------- |
-| ⌘, | Ir para Preferences (Preferências) |
-| ⌘H | Ocultar o aplicativo do {% data variables.product.prodname_desktop %} |
-| ⌥⌘H | Ocultar todos os outros aplicativos |
-| ⌘Q | Sair do {% data variables.product.prodname_desktop %} |
-| ⌃⌘F | Alternar a exibição em tela cheia |
-| ⌘0 | Redefinir o zoom para o tamanho de texto padrão |
-| ⌘= | Aumentar o zoom em textos e imagens |
-| ⌘- | Diminuir o zoom em textos e imagens |
-| ⌥⌘I | Alternar as ferramentas de desenvolvedor |
-
-### Repositórios
-
-| Atalho | Descrição |
-| ------------------------------------ | ------------------------------------------------------------------------------------- |
-| ⌘N | Adicionar um novo repositório |
-| ⌘O | Adicionar um repositório local |
-| ⇧⌘O | Clonar um repositório do {% data variables.product.prodname_dotcom %} |
-| ⌘T | Exibir uma lista dos repositórios |
-| ⌘P | Usar os commits mais recentes do {% data variables.product.prodname_dotcom %} |
-| ⇧⌘P | Usar as alterações mais recentes do {% data variables.product.prodname_dotcom %} |
-| ⌘⌫ | Remover um repositório |
-| ⇧⌘G | Exibir o repositório no {% data variables.product.prodname_dotcom %} |
-| ⌃` | Abrir o repositório na sua ferramenta de terminal preferida |
-| ⇧⌘F | Exibir o repositório no Localizador |
-| ⇧⌘A | Abrir o repositório na sua ferramenta de edição preferida |
-| ⌘I | Criar um problema em {% data variables.product.prodname_dotcom %} |
-
-### Branches
-
-| Atalho | Descrição |
-| ------------------------------------ | -------------------------------------------------------------------------------- |
-| ⌘1 | Exibir todas as alterações antes de fazer o commit |
-| ⌘2 | Exibir o histórico de commits |
-| ⌘B | Exibir todos os branches |
-| ⌘G | Ir para o campo de resumo de commits |
-| space (Espaço) | Selecione ou desmarque todos os arquivos destacados |
-| ⇧⌘N | Criar um branch |
-| ⇧⌘R | Renomear o branch atual |
-| ⇧⌘D | Excluir o branch atual |
-| ⇧⌘U | Atualizar o branch padrão |
-| ⇧⌘B | Comparar a outro branch |
-| ⇧⌘M | Fazer um merge com o branch atual |
-| ⌃H | Exibir ou ocultar alterações stashed |
-| ⇧⌘C | Comparar branches no {% data variables.product.prodname_dotcom %} |
-| ⌘R | Exibir a pull request atual no {% data variables.product.prodname_dotcom %} |
-
-{% endmac %}
-
-{% windows %}
-
-Atalhos de teclado do GitHub Desktop no Windows
-
-### Atalhos para o site
-
-| Atalho | Descrição |
-| ------------------------------------------- | ----------------------------------------------- |
-| Ctrl, | Ir para Opções |
-| F11 | Alternar a exibição em tela cheia |
-| Ctrl0 | Redefinir o zoom para o tamanho de texto padrão |
-| Ctrl= | Aumentar o zoom em textos e imagens |
-| Ctrl- | Diminuir o zoom em textos e imagens |
-| CtrlShiftI | Alternar as ferramentas de desenvolvedor |
-
-### Repositórios
-
-| Atalho de teclado | Descrição |
-| ------------------------------------------- | ------------------------------------------------------------------------------------- |
-| CtrlN | Adicionar um novo repositório |
-| CtrlO | Adicionar um repositório local |
-| CtrlShiftO | Clonar um repositório do {% data variables.product.prodname_dotcom %} |
-| CtrlT | Exibir uma lista dos repositórios |
-| CtrlP | Usar os commits mais recentes do {% data variables.product.prodname_dotcom %} |
-| CtrlShiftP | Usar as alterações mais recentes do {% data variables.product.prodname_dotcom %} |
-| CtrlDelete | Remover um repositório |
-| CtrlShiftG | Exibir o repositório no {% data variables.product.prodname_dotcom %} |
-| Ctrl` | Abrir o repositório na sua ferramenta de linha de comando preferida |
-| CtrlShiftF | Exibir o repositório no Explorador |
-| CtrlShiftA | Abrir o repositório na sua ferramenta de edição preferida |
-| CtrlI | Criar um problema em {% data variables.product.prodname_dotcom %} |
-
-### Branches
-
-| Atalho | Descrição |
-| ------------------------------------------- | -------------------------------------------------------------------------------- |
-| Ctrl1 | Exibir todas as alterações antes de fazer o commit |
-| Ctrl2 | Exibir o histórico de commits |
-| CtrlB | Exibir todos os branches |
-| CtrlG | Ir para o campo de resumo de commits |
-| space (Espaço) | Selecionar ou desmarque todos os arquivos destacados |
-| CtrlShiftN | Criar um branch |
-| CtrlShiftR | Renomear o branch atual |
-| CtrlShiftD | Excluir o branch atual |
-| CtrlShiftU | Atualizar o branch padrão |
-| CtrlShiftB | Comparar a outro branch |
-| CtrlShiftM | Fazer um merge com o branch atual |
-| CtrlH | Exibir ou ocultar alterações stashed |
-| CtrlShiftC | Comparar branches no {% data variables.product.prodname_dotcom %} |
-| CtrlR | Exibir a pull request atual no {% data variables.product.prodname_dotcom %} |
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts.md
deleted file mode 100644
index 2858bd1e48a5..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Atalhos de teclado
-redirect_from:
- - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop/
-intro: 'É possível usar atalhos de teclado no {% data variables.product.prodname_desktop %}.'
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-Atalhos de teclado do GitHub Desktop no macOS
-
-### Atalhos para o site
-
-| Atalho | Descrição |
-| ------------------------------------ | -------------------------------------------------------------------------- |
-| ⌘, | Ir para Preferences (Preferências) |
-| ⌘H | Ocultar o aplicativo do {% data variables.product.prodname_desktop %} |
-| ⌥⌘H | Ocultar todos os outros aplicativos |
-| ⌘Q | Sair do {% data variables.product.prodname_desktop %} |
-| ⌃⌘F | Alternar a exibição em tela cheia |
-| ⌘0 | Redefinir o zoom para o tamanho de texto padrão |
-| ⌘= | Aumentar o zoom em textos e imagens |
-| ⌘- | Diminuir o zoom em textos e imagens |
-| ⌥⌘I | Alternar as ferramentas de desenvolvedor |
-
-### Repositórios
-
-| Atalho | Descrição |
-| ------------------------------------ | ------------------------------------------------------------------------------------- |
-| ⌘N | Adicionar um novo repositório |
-| ⌘O | Adicionar um repositório local |
-| ⇧⌘O | Clonar um repositório do {% data variables.product.prodname_dotcom %} |
-| ⌘T | Exibir uma lista dos repositórios |
-| ⌘P | Usar os commits mais recentes do {% data variables.product.prodname_dotcom %} |
-| ⇧⌘P | Usar as alterações mais recentes do {% data variables.product.prodname_dotcom %} |
-| ⌘⌫ | Remover um repositório |
-| ⇧⌘G | Exibir o repositório no {% data variables.product.prodname_dotcom %} |
-| ⌃` | Abrir o repositório na sua ferramenta de terminal preferida |
-| ⇧⌘F | Exibir o repositório no Localizador |
-| ⇧⌘A | Abrir o repositório na sua ferramenta de edição preferida |
-| ⌘I | Criar um problema em {% data variables.product.prodname_dotcom %} |
-
-### Branches
-
-| Atalho | Descrição |
-| ------------------------------------ | -------------------------------------------------------------------------------- |
-| ⌘1 | Exibir todas as alterações antes de fazer o commit |
-| ⌘2 | Exibir o histórico de commits |
-| ⌘B | Exibir todos os branches |
-| ⌘G | Ir para o campo de resumo de commits |
-| space (Espaço) | Selecione ou desmarque todos os arquivos destacados |
-| ⇧⌘N | Criar um branch |
-| ⇧⌘R | Renomear o branch atual |
-| ⇧⌘D | Excluir o branch atual |
-| ⇧⌘U | Atualizar o branch padrão |
-| ⇧⌘B | Comparar a outro branch |
-| ⇧⌘M | Fazer um merge com o branch atual |
-| ⌃H | Exibir ou ocultar alterações stashed |
-| ⇧⌘C | Comparar branches no {% data variables.product.prodname_dotcom %} |
-| ⌘R | Exibir a pull request atual no {% data variables.product.prodname_dotcom %} |
-
-{% endmac %}
-
-{% windows %}
-
-Atalhos de teclado do GitHub Desktop no Windows
-
-### Atalhos para o site
-
-| Atalho | Descrição |
-| ------------------------------------------- | ----------------------------------------------- |
-| Ctrl, | Ir para Opções |
-| F11 | Alternar a exibição em tela cheia |
-| Ctrl0 | Redefinir o zoom para o tamanho de texto padrão |
-| Ctrl= | Aumentar o zoom em textos e imagens |
-| Ctrl- | Diminuir o zoom em textos e imagens |
-| CtrlShiftI | Alternar as ferramentas de desenvolvedor |
-
-### Repositórios
-
-| Atalho de teclado | Descrição |
-| ------------------------------------------- | ------------------------------------------------------------------------------------- |
-| CtrlN | Adicionar um novo repositório |
-| CtrlO | Adicionar um repositório local |
-| CtrlShiftO | Clonar um repositório do {% data variables.product.prodname_dotcom %} |
-| CtrlT | Exibir uma lista dos repositórios |
-| CtrlP | Usar os commits mais recentes do {% data variables.product.prodname_dotcom %} |
-| CtrlShiftP | Usar as alterações mais recentes do {% data variables.product.prodname_dotcom %} |
-| CtrlDelete | Remover um repositório |
-| CtrlShiftG | Exibir o repositório no {% data variables.product.prodname_dotcom %} |
-| Ctrl` | Abrir o repositório na sua ferramenta de linha de comando preferida |
-| CtrlShiftF | Exibir o repositório no Explorador |
-| CtrlShiftA | Abrir o repositório na sua ferramenta de edição preferida |
-| CtrlI | Criar um problema em {% data variables.product.prodname_dotcom %} |
-
-### Branches
-
-| Atalho | Descrição |
-| ------------------------------------------- | -------------------------------------------------------------------------------- |
-| Ctrl1 | Exibir todas as alterações antes de fazer o commit |
-| Ctrl2 | Exibir o histórico de commits |
-| CtrlB | Exibir todos os branches |
-| CtrlG | Ir para o campo de resumo de commits |
-| space (Espaço) | Selecionar ou desmarque todos os arquivos destacados |
-| CtrlShiftN | Criar um branch |
-| CtrlShiftR | Renomear o branch atual |
-| CtrlShiftD | Excluir o branch atual |
-| CtrlShiftU | Atualizar o branch padrão |
-| CtrlShiftB | Comparar a outro branch |
-| CtrlShiftM | Fazer um merge com o branch atual |
-| CtrlH | Exibir ou ocultar alterações stashed |
-| CtrlShiftC | Comparar branches no {% data variables.product.prodname_dotcom %} |
-| CtrlR | Exibir a pull request atual no {% data variables.product.prodname_dotcom %} |
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line.md
deleted file mode 100644
index 90b1bc4d8b50..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Iniciar o GitHub Desktop na linha de comando
-shortTitle: Lançar a partir da linha de comando
-intro: É possível iniciar o GitHub Desktop na linha de comando.
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-1. Na barra de menu, selecione o menu **{% data variables.product.prodname_desktop %}** e, em seguida, clique em **Instalar Ferramenta da Linha de Comando**. ![Instalar opção de Ferramenta de Linha de Comando no menu suspenso {% data variables.product.prodname_desktop %}](/assets/images/help/desktop/mac-install-command-line-tool.png)
-2. Abra o terminal.
-3. {% data reusables.desktop.launch-desktop-from-command-line %}
-
- ```shell
- $ github /path/to/repo
- ```
-
- Também é possível alterar o caminho do repositório e digite o `github .` para abrir esse repositório.
-
- ```shell
- $ cd /path/to/repo
- [repo]$ github .
- ```
-
-{% endmac %}
-
-{% windows %}
-
-1. Abra um prompt de comando.
-2. {% data reusables.desktop.launch-desktop-from-command-line %}
-
- ```shell
- C:\Users\octocat> github path\to\repo
- ```
-
- Você também pode alterar para o caminho do seu repositório e, em seguida, digitar `github .` para abrir esse repositório.
-
- ```shell
- C:\Users\octocat> cd repo\myrepo
- C:\Users\octocat\repo\myrepo> github .
- ```
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/overview.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/overview.md
deleted file mode 100644
index 5eaba2191be3..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/overview.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Visão Geral
-intro: Aprenda sobre o GitHub Desktop e crie rapidamente o seu primeiro repositório.
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop.md
deleted file mode 100644
index 22eaa7644b80..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Definir um tema para o GitHub Desktop
-intro: É possível definir um tema para personalizar a aparência do GitHub Desktop.
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-{% data reusables.desktop.choose-a-theme %}
- ![The theme options on the Appearance tab for Mac](/assets/images/help/desktop/mac-appearance-tab-themes.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.windows-choose-options %}
-{% data reusables.desktop.choose-a-theme %}
- ![The theme options on the Appearance tab for Windows](/assets/images/help/desktop/windows-appearance-tab-themes.png)
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/uninstalling-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/uninstalling-github-desktop.md
deleted file mode 100644
index 30cb6444c000..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/uninstalling-github-desktop.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Desinstalar o GitHub Desktop
-intro: Você pode desinstalar o GitHub Desktop no seu computador a qualquer momento.
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-1. Em uma janela do Finder, navegue até a pasta Aplicativos. ![Pasta de aplicativos na janela do Finder](/assets/images/help/desktop/applications-folder.png)
-2. Ao pressionar o botão **Controle** no seu teclado, clique em **{% data variables.product.prodname_desktop %}**.
-3. Escolha **Move to Trash** (Mover para a lixeira). ![A opção Mover para a lixeira](/assets/images/help/desktop/mac-move-to-trash.png)
-4. Na barra do menu, use o menu suspenso **Finder** e, em seguida, clique em **Esvaziar lixeira**. ![A opção Esvaziar lixeira na barra do menu](/assets/images/help/desktop/mac-empty-trash-menu.png)
-5. Leia o aviso na caixa pop-up e clique em **Empty Trash** (Esvaziar lixeira). ![O botão de Esvaziar lixeira](/assets/images/help/desktop/mac-empty-trash-button.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. Abrir Painel de controle Para obter mais informações, consulte [Onde está o Painel de Controle?](https://support.microsoft.com/en-us/help/13764/windows-where-is-control-panel) no Windows Help.
-2. Em "Programas", clique em **Desinstalar um programa**. ![A opção Desinstalar um Programa no Painel de Controle](/assets/images/help/desktop/windows-uninstall-a-program.png)
-3. Clique com o botão direito no item denominado **{% data variables.product.prodname_desktop %}** e, em seguida, clique em **Desinstalar**. ![A opção de Desinstalar](/assets/images/help/desktop/windows-click-uninstall.png)
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/updating-github-desktop.md b/translations/pt-BR/content/desktop/getting-started-with-github-desktop/updating-github-desktop.md
deleted file mode 100644
index 4ecc153aa07f..000000000000
--- a/translations/pt-BR/content/desktop/getting-started-with-github-desktop/updating-github-desktop.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Atualizar o GitHub Desktop
-intro: O GitHub Desktop baixa atualizações automaticamente e faz essas atualizações quando você o reinicia. Também é possível verificar as atualizações manualmente.
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-1. No menu **GitHub Desktop**, clique em **About GitHub Desktop** (Sobre o GitHub Desktop). ![Opção de menu Sobre o GitHub Desktop](/assets/images/help/desktop/desktop-menu-about-desktop-mac.png)
-2. Clique em **Check for Updates** (Verificar atualizações). ![Botão Check for Updates (Verificar atualizações)](/assets/images/help/desktop/check-for-updates.png)
-3. Se houver alguma atualização disponível, saia e inicie o {% data variables.product.prodname_desktop %} novamente para fazer a instalação.
-
-{% endmac %}
-
-{% windows %}
-
-1. No menu **Help** (Ajuda), clique em **About GitHub Desktop** (Sobre o GitHub Desktop). ![Opção de menu Sobre o GitHub Desktop](/assets/images/help/desktop/help-about-desktop-win.png)
-2. Clique em **Check for Updates** (Verificar atualizações). ![Botão Check for Updates (Verificar atualizações)](/assets/images/help/desktop/check-for-updates.png)
-3. Se houver alguma atualização disponível, saia e inicie o {% data variables.product.prodname_desktop %} novamente para fazer a instalação.
-
-{% endwindows %}
diff --git a/translations/pt-BR/content/github/administering-a-repository/about-github-dependabot.md b/translations/pt-BR/content/github/administering-a-repository/about-github-dependabot.md
deleted file mode 100644
index 769b260acdd9..000000000000
--- a/translations/pt-BR/content/github/administering-a-repository/about-github-dependabot.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Sobre o GitHub Dependabot
-intro: 'Você pode usar o {% data variables.product.prodname_dependabot %} para manter os pacotes que usa atualizados para as versões mais recentes.'
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.dependabot.beta-note %}
-
-### Sobre o {% data variables.product.prodname_dependabot %}
-
-{% data variables.product.prodname_dependabot %} é um app {% data variables.product.prodname_dotcom %} que dispensa o esforço de manter suas dependências. Você pode usá-lo para garantir que seu repositório se mantenha atualizado automaticamente com as versões mais recentes dos pacotes e aplicações do qual ele depende.
-
-Você habilita o {% data variables.product.prodname_dependabot_version_updates %} verificando um arquivo de configuração no seu repositório. O arquivo de configuração especifica a localização do manifesto ou outros arquivos de definição de pacote, armazenados no seu repositório. O app usa estas informações para verificar pacotes e aplicações desatualizados. O aplicativo {% data variables.product.prodname_dependabot_short %} determina se há uma nova versão de uma dependência ao olhar para o versionamento semântico ([semver](https://semver.org/)) da dependência para decidir se ela deve atualizar para essa versão. Quando o aplicativo identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Você verifica se os seus testes passam, revisa o changelog e lança observações incluídas no resumo do pull request e, em seguida, faz a mesclagem. Para obter detalhes, consulte "[Habilitando e desabilitando atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)."
-
-Se você habilitar atualizações de segurança, {% data variables.product.prodname_dependabot %} também promove pull requests para atualizar dependências vulneráveis. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)."
-
-{% data reusables.dependabot.dependabot-tos %}
-
-### Frequência de {% data variables.product.prodname_dependabot %} pull requests
-
-Você especifica com que frequência verifica cada ecossistema para novas versões no arquivo de configuração: diariamente, semanalmente ou mensalmente.
-
-{% data reusables.dependabot.initial-updates %}
-
-Se tiver habilitado atualizações de segurança, às vezes você verá atualizações de segurança extras de pull requests. Elas são acionadas por um alerta Dependabot para uma dependência do seu branch padrão. {% data variables.product.prodname_dependabot %} gera automaticamente um pull request para atualizar a dependência vulnerável.
-
-### Repositórios e ecossistemas suportados
-
-É possível configurar atualizações de versão para repositórios que contenham um manifesto de dependência ou arquivo de bloqueio para um dos gerentes de pacotes suportados.
-
-{% data reusables.dependabot.supported-package-managers %}
-
-Se o seu repositório já usa uma integração para gerenciamento de dependências, você precisará desativar isso antes de habilitar o {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Sobre integrações](/github/customizing-your-github-workflow/about-integrations)".
diff --git a/translations/pt-BR/content/github/administering-a-repository/setting-the-default-branch.md b/translations/pt-BR/content/github/administering-a-repository/setting-the-default-branch.md
deleted file mode 100644
index 906548011b5a..000000000000
--- a/translations/pt-BR/content/github/administering-a-repository/setting-the-default-branch.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Definir o branch padrão
-intro: 'Se você tiver mais de um branch no seu repositório, você poderá escolher outro branch para ser o branch-padrão.'
-redirect_from:
- - /articles/setting-the-default-branch
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### Sobre o branch-padrão
-
-{% data reusables.branches.new-repo-default-branch %} {% data reusables.branches.default-branch-automatically-base-branch %} se você tiver mais de um branch no seu repositório, qualquer pessoa com direitos de administrador sobre um repositório pode selecionar um desses branches existentes como branch-padrão no repositório.
-
-### Definir o branch padrão
-
-{% note %}
-
-**Observação:** Para definir o branch-padrão você deve ter mais de um branch no seu repositório.
-
-{% endnote %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.repository-branches %}
-4. No menu suspenso do branch-padrão, selecione o novo branch-padrão. ![Seletor suspenso de branch padrão](/assets/images/help/repository/repository-options-defaultbranch.png)
-5. Clique em **Atualizar**.
-
-Você pode selecionar somente branches que já existem no {% data variables.product.product_location %}. Para criar um novo branch por meio da UI, consulte "[Criar e excluir branches no repositório](/articles/creating-and-deleting-branches-within-your-repository)".
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-
-Também é possível definir o nome do branch-padrão para quaisquer repositórios recém-criados, pertencentes à conta de usuário, organização ou conta corporativa. Para obter mais informações, consulte "[Gerenciar o branch-padrão para seus repositórios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)", "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization), ou "[Exigir uma política com o nome do branch-padrão](/github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)".
-
-{% endif %}
-
-{% warning %}
-
-**Aviso**: Configurar um branch-padrão diferente afeta o conteúdo de `trunk` no seu branch e na [ponte do Git-Subversion](https://github.com/blog/1178-collaborating-on-github-with-subversion) e no `HEAD` que veria ao fazer `git ls-remote` na [URL crescente do repositório](https://git-scm.com/docs/git-ls-remote.html).
-
-{% endwarning %}
diff --git a/translations/pt-BR/content/github/articles/README.md b/translations/pt-BR/content/github/articles/README.md
deleted file mode 100644
index 1654054f54e3..000000000000
--- a/translations/pt-BR/content/github/articles/README.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Artigos ocultos do GitHub.com
-
-O artigos do GitHub.com/Usuário corporativo com a página inicial `hidden: true` são encontrados neste diretório.
-
-Consulte [`content/README`](../README.md#hidden-pages) para saber mais sobre páginas ocultas.
diff --git a/translations/pt-BR/content/github/articles/about-the-github-and-visual-studio-bundle.md b/translations/pt-BR/content/github/articles/about-the-github-and-visual-studio-bundle.md
deleted file mode 100644
index c4c6ffc6f1f0..000000000000
--- a/translations/pt-BR/content/github/articles/about-the-github-and-visual-studio-bundle.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Sobre o GitHub e o pacote do Visual Studio
-hidden: true
-redirect_from:
- - /articles/about-the-github-and-visual-studio-bundle
-versions:
- free-pro-team: '*'
----
-
-{% tip %}
-
-**Dicas**:
-- Somente proprietários da organização podem convidar usuários para participar de uma organização. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization)".
-
-{% endtip %}
-
-
-### Neste artigo
-- [Sobre as licenças do {% data variables.product.prodname_enterprise %} e do pacote do Visual Studio](#about-github-enterprise-and-visual-studio-bundle-licenses)
-- [Atribuir uma licença de usuário do {% data variables.product.prodname_enterprise %}](#assigning-a-github-enterprise-user-license)
-- [Superalocação de licenças de usuário](#overallocation-of-user-licenses)
-
-
-### Sobre as licenças do {% data variables.product.prodname_enterprise %} e do pacote do Visual Studio
-
-Os clientes que compraram o pacote do Visual Studio pelo {% data variables.product.prodname_dotcom %} estão qualificados para uma licença de usuário do {% data variables.product.prodname_enterprise %}. Essas licenças são provisionadas em uma conta corporativa do {% data variables.product.prodname_dotcom %}, que é vinculada ao Microsoft Enterprise Agreement e pode ser atribuída aos integrantes da organização.
-
-Quando os proprietários das organizações em sua empresa convidam um novo usuário para ingressar em uma organização, eles podem escolher se atribuem ao novo usuário uma licença do {% data variables.product.prodname_enterprise %} ou {% data variables.product.prodname_enterprise %} com as assinaturas do Visual Studio.
-
-### Atribuir uma licença de usuário do {% data variables.product.prodname_enterprise %}
-
-{% data reusables.profile.access_profile %}
-{% data reusables.profile.access_org %}
-{% data reusables.organizations.people %}
-{% data reusables.organizations.invite_member_from_people_tab %}
-{% data reusables.organizations.invite_to_org %}
-{% data reusables.organizations.choose-to-restore-privileges %}
-{% data reusables.organizations.choose-user-role %}
-{% data reusables.organizations.choose-user-license %}
-{% data reusables.organizations.add-user-to-teams %}
-{% data reusables.organizations.send-invitation %}
-{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
-
-### Superalocação de licenças de usuário
-
-Você pode ver o número total de licenças que usou para suas assinaturas do {% data variables.product.prodname_enterprise %} e {% data variables.product.prodname_enterprise %} com Visual Studio nas configurações de cobrança da sua conta corporativa.
-
-Se a organização e os proprietários de empresa atribuírem aos usuários mais licenças de assinatura do {% data variables.product.prodname_enterprise %} (Visual Studio) do que as licenças incluídas na sua assinatura, a próxima fatura incluirá cobranças pelo número de usuários acima da quantidade permitida pela assinatura.
-
-Para obter mais informações, consulte "[Exibir a assinatura e o uso de sua conta corporativa](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)".
-
-### Leia mais
-- "[Adicionar integrantes da organização a uma equipe](/articles/adding-organization-members-to-a-team)"
-- Se sua organização [exigir que integrantes usem autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization), os usuários que você convida deverão [habilitar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de aceitar o convite.
diff --git a/translations/pt-BR/content/github/articles/managing-your-disabled-github-pages-site.md b/translations/pt-BR/content/github/articles/managing-your-disabled-github-pages-site.md
deleted file mode 100644
index b534ec783f7d..000000000000
--- a/translations/pt-BR/content/github/articles/managing-your-disabled-github-pages-site.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Gerenciar seu site GitHub Pages desabilitado
-intro: 'Repositórios privados no {% data variables.product.prodname_free_user %} não são compatíveis com {% data variables.product.prodname_pages %}, entretanto, um número limitado de sites {% data variables.product.prodname_pages %} conectados a repositórios privados grátis ficaram ativos equivocadamente. Esses sites não estão mais sendo atualizados e a publicação deles será cancelada pelo {% data variables.product.prodname_dotcom %} em 10 de maio de 2019.'
-hidden: true
-redirect_from:
- - /articles/managing-your-disabled-github-pages-site
-versions:
- free-pro-team: '*'
----
-
-{% note %}
-
-O {% data variables.product.prodname_pages %} está disponível somente em repositórios públicos com {% data variables.product.prodname_free_user %} e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, e {% data variables.product.prodname_ghe_server %}. {% data reusables.gated-features.more-info %}
-
-{% endnote %}
-
-Se você tem um site {% data variables.product.prodname_pages %} publicado em um repositório privado grátis, você tem algumas opções para continuar publicando e atualizando seu site ou para cancelar a publicação dele manualmente. Se você não tomar nenhuma medida, o {% data variables.product.prodname_dotcom %} cancelará a publicação do site por você em 10 de maio de 2019.
-
-- **Para continuar a publicar e atualizar seu site {% data variables.product.prodname_pages %}**, você pode converter seu repositório em público ou atualizar sua conta para {% data variables.product.prodname_pro %}. Para obter mais informações sobre como transformar seu repositório privado em público, consulte "[Configurar a visibilidade do repositório](/articles/setting-repository-visibility#making-a-private-repository-public)". Para obter mais informações sobre como atualizar sua conta, consulte "[Atualizar sua assinatura GitHub](/articles/upgrading-your-github-subscription)".
-
-- **Para parar de publicar seu site {% data variables.product.prodname_pages %}**, é possível [cancelar manualmente a publicação](#manually-unpublishing-your-github-pages-site) ou não fazer nada e o {% data variables.product.prodname_dotcom %} cancelará a publicação de seu site por você em 10 de maio de 2019. Se o seu site {% data variables.product.prodname_pages %} tem um domínio personalizado configurado, você deve atualizar ou remover seus registros DNS com o seu provedor DNS o quanto antes possível para evitar o risco de uma incorporação do domínio. Configurar seu domínio personalizado com seu provedor DNS enquanto o seu site {% data variables.product.prodname_pages %} está desabilitado, poderia resultar em alguma outra pessoa hospedando um site em um de seus subdomínios. Para obter mais informações, consulte "[Usar um domínio personalizado com o {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)".
-
-### Cancelar a publicação de seu site {% data variables.product.prodname_pages %} manualmente
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. Na barra lateral esquerda, clique em **Unpublish {% data variables.product.prodname_pages %}** (Cancelar publicação do {% data variables.product.prodname_pages %}). ![Configurações de repositório para cancelar publicação de site {% data variables.product.prodname_pages %}](/assets/images/help/pages/unpublish-pages-button-sidebar.png)
-4. Clique em **Unpublish this site** (Cancelar publicação deste site). ![Botão para unpublish (cancelar a publicação) de site {% data variables.product.prodname_pages %}](/assets/images/help/pages/unpublish-pages-button.png)
-
-### Leia mais
-
-- "[Cancelar publicação de um site User Pages](articles/unpublishing-a-user-pages-site)"
-- "[Cancelar a publicação de um site Project Pages](/articles/unpublishing-a-project-pages-site)"
-- "[Transferir um repositório](/articles/transferring-a-repository)"
-- "[Sobre arquivar repositórios](/articles/about-archiving-repositories)"
-- "[Excluir um repositório](/articles/deleting-a-repository)"
diff --git a/translations/pt-BR/content/github/articles/searching-and-navigating-code.md b/translations/pt-BR/content/github/articles/searching-and-navigating-code.md
deleted file mode 100644
index 2135c6db75ce..000000000000
--- a/translations/pt-BR/content/github/articles/searching-and-navigating-code.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Pesquisar e navegar no código
-intro: 'Pesquisar e navegar no código são partes críticas do fluxo de trabalho de desenvolvimento, e o GitHub está aprimorando essas áreas. Se você fizer parte de uma organização que está participando da versão beta privada de pesquisa e navegação, terá acesso a novas ferramentas avançadas de pesquisa e navegação. Para dúvidas adicionais sobre esta versão beta privada, envie um e-mail para beta@github.com.'
-hidden: true
-redirect_from:
- - /articles/searching-and-navigating-code
-versions:
- free-pro-team: '*'
----
-
-
-### Neste guia
-
-- [Pesquisa literal no código](#literal-code-search)
-- [Relevância](#relevancy)
-- [Navegação com acesso direto](#jump-to-navigation)
-
-### Pesquisa literal no código
-
-Antes dessa versão beta privada, muito símbolos eram retirados dos índices de pesquisa, e expressões comuns como `>>` não eram pesquisadas. Por exemplo, ao pesquisar `>>` em um repositório, nenhum resultado era retornado. Com a versão beta privada, você pode colocar o símbolo entre aspas duplas e ver os resultados corretos. Esse recurso vai além dos símbolos e permite pesquisar frases inteiras entre aspas, como `"return [] unless"`. Esse recurso se aplica à pesquisa de código em todas as linguagens.
-
-### Relevância
-
-Para um subconjunto de linguagens (Go, JavaScript, Python, Ruby e TypeScript), a pesquisa no código agora modula a relevância das declarações. A declaração de um método, função, classe ou outra entidade será retornada antes das chamadas ou comentários que incluem o mesmo termo.
-
-### Navegação com acesso direto
-
-Para um subconjunto de idiomas (Go, JavaScript, Python, Ruby e TypeScript), o GitHub agora oferece suporte a informações adicionais e navegação ao clicar em um símbolo. Essa navegação inclui a navegação de acesso à definição para recursos no repositório, o que aumenta a velocidade da navegação e melhora o insight.
-
-### Feedback
-
-Os usuários que estão usando a versão beta privada de pesquisa e navegação podem fornecer feedback por meio [desta pesquisa](https://www.research.net/r/CodeSearch-Navigation). Para feedback e dúvidas adicionais, envie um e-mail para search-beta@github.com.
-
-### Leia mais
-- [Sobre a pesquisa no GitHub](/articles/about-searching-on-github/)
-- [Localizar métodos e funções modificados em uma pull request](/articles/finding-changed-methods-and-functions-in-a-pull-request/)
diff --git a/translations/pt-BR/content/github/articles/using-gist-playground.md b/translations/pt-BR/content/github/articles/using-gist-playground.md
deleted file mode 100644
index 8af6697b5348..000000000000
--- a/translations/pt-BR/content/github/articles/using-gist-playground.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Usar o Gist Playground
-intro: ''
-hidden: true
-redirect_from:
- - /articles/articles/using-gist-playground
-versions:
- free-pro-team: '*'
----
-
-{% note %}
-
-**Observação:** o Gist Playground está disponível como um programa beta privado limitado e, portanto, está sujeito ao acordo de acesso antecipado.
-
-{% endnote %}
-
-### Neste artigo
-- [Sobre o Gist Playground](#about-gist-playground)
-- [Criar gists](#creating-new-gists)
-- [Salvar alterações](#saving-your-changes)
-- [Colaborar com outras pessoas](#collaborating-with-others)
-- [Reportar erros e comentários](#reporting-bugs-and-feedback)
-
-### Sobre o Gist Playground
-O Gist Playground é uma iteração experimental do [Gist](https://gist.github.com/). As alterações são salvas automaticamente enquanto você trabalha com amigos e colegas.
-
-### Criar gists
-Quando você acessa o Gist Playground, ele cria automaticamente um rascunho ou mostra seu rascunho mais recente. Quando estiver pronto, clique em **Criar gist** no cabeçalho para criar e compartilhar o gist.
-
-Todos os gists feitos no Gist Playground são *secretos*. Ainda não há nenhuma maneira de tornar um gist público a partir do Gist Playground. Caso queira fazer isso, use o [Gist](https://gist.github.com/) existente.
-
-### Salvar alterações
-As alterações são salvas automaticamente enquanto você digita. Você pode fechar a guia em qualquer ponto e voltar sem perder nenhum trabalho.
-
-Quando você estiver em um ponto de verificação, poderá atualizar o gist com essas alterações clicando em **Atualizar gist** no cabeçalho.
-
-### Colaborar com outras pessoas
-Você pode colaborar com qualquer pessoa que participe do programa beta privado Gist Playground. Em "Invite to collaborate" (Convidar a colaborar), clique na URL de colaboração para copiá-la e envie-a a um amigo. Assim vocês poderão fazer as alterações juntos.
-
-Quando você estiver em um ponto de verificação, o proprietário do gist poderá manter as alterações clicando em **Atualizar gist**.
-
-Se você quiser colaborar com alguém que não participa do beta privado Gist Playground, envie um e-mail para nós em [gist-playground@github.com](mailto:gist-playground@github.com) e verificaremos a possibilidade de adicioná-lo.
-
-### Reportar erros e comentários
-Gostaríamos muito de ouvir sua opinião sobre Gist Playground e como podemos melhorá-lo! Envie um e-mail para nós em [gist-playground@github.com](mailto:gist-playground@github.com) com ideias, erros ou comentários.
diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order.md b/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order.md
deleted file mode 100644
index f3457694e6ac..000000000000
--- a/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Por que meus commits estão na ordem errada?
-intro: 'Se você reescrever seu histórico de commits por meio de ''git rebase'' ou de um push forçado, poderá perceber que a sequência de commits está fora de ordem ao abrir uma pull request.'
-redirect_from:
- - /articles/why-are-my-commits-in-the-wrong-order
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-O GitHub enfatiza pull requests como um espaço para discussão. Todos os aspectos (comentários, referências e commits) são representados em ordem cronológica. Reescrever o histórico de commits do Git [ao executar rebases](/articles/about-git-rebase) altera o continuum espaço-tempo, o que significa que talvez os commits não sejam representados conforme esperado na interface do Github.
-
-Se você sempre quiser ver os commits em ordem, recomendamos não usar`git rebase`. No entanto, tenha certeza de que nada está errado quando você vê as coisas fora da ordem cronológica!
diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code.md b/translations/pt-BR/content/github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code.md
deleted file mode 100644
index fd97908d696e..000000000000
--- a/translations/pt-BR/content/github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Conectar-se ao seu codespace do Visual Studio Code
-intro: 'Você pode desenvolver seu codespace diretamente em {% data variables.product.prodname_vscode %}, conectando a extensão de {% data variables.product.prodname_vs_codespaces %} à sua conta no {% data variables.product.product_name %}.'
-product: '{% data reusables.gated-features.codespaces %}'
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.codespaces.release-stage %}
-
-### Conectar a extensão de {% data variables.product.prodname_vs_codespaces %} à sua conta {% data variables.product.prodname_dotcom %}
-
-Antes de poder desenvolver em um código diretamente em {% data variables.product.prodname_vscode %}, você deverá configurar a extensão {% data variables.product.prodname_vs_codespaces %} para conectar-se à sua conta do {% data variables.product.product_name %}.
-
-1. Use o {% data variables.product.prodname_vs %} Marketplace para instalar a extensão [{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline). Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode %}.
-2. Clique no ícone Extensões na barra lateral esquerda do {% data variables.product.prodname_vscode %}. ![O ícone das extensões em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-extensions-icon-vscode.png)
-3. Abaixo do {% data variables.product.prodname_vs_codespaces %}, clique no ícone Gerenciar e, em seguida, clique em **Configurações de extensão**. ![A opção Configurações de extensão](/assets/images/help/codespaces/select-extension-settings.png)
-4. Use o menu suspenso "Vsonline: Provedor de Conta", e selecione {% data variables.product.prodname_dotcom %}. ![Definir o provedor de conta para {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/select-account-provider-vscode.png)
-{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-6. Se {% data variables.product.prodname_codespaces %} não estiver selecionado no cabeçalho, clique em **{% data variables.product.prodname_codespaces %}**. ![Cabeçalho do {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png)
-7. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_codespaces %}...**. ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
-8. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**.
-9. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão.
-
-### Abrir um codespace em {% data variables.product.prodname_vscode %}
-
-Depois de conectar a sua conta do {% data variables.product.product_name %} à extensão de {% data variables.product.prodname_vs_codespaces %}, você poderá desenvolver em codespace criado no {% data variables.product.product_name %} diretamente em {% data variables.product.prodname_vscode %}.
-
-{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. Em Codespaces, clique no codespace que você deseja desenvolver.
-3. Clique no ícone Conectar-se ao Codespace. ![Ícone de conectar-se a um Codespace em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages.md
deleted file mode 100644
index 0308491030b7..000000000000
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages.md
+++ /dev/null
@@ -1,153 +0,0 @@
----
-title: Configurar varredura de código para linguagens compiladas
-shortTitle: Configurar para linguagens compiladas
-intro: 'Você pode configurar como o código {% data variables.product.prodname_dotcom %} faz a varredura de código escrito em linguagens compiladas com relação a vulnerabilidades e erros.'
-product: '{% data reusables.gated-features.code-scanning %}'
-permissions: 'Pessoas com permissões de gravação para um repositório podem configurar {% data variables.product.prodname_code_scanning %} para o repositório.'
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.code-scanning.beta %}
-
-{% note %}
-
-**Observação**: Este artigo refere-se a {% data variables.product.prodname_code_scanning %} movido por {% data variables.product.prodname_codeql %}, não a {% data variables.product.prodname_code_scanning %}, resultante do upload das ferramentas de análise estática de terceiros.
-
-{% endnote %}
-
-### Sobre {% data variables.product.prodname_code_scanning %} e linguagens compiladas
-
-Para habilitar o {% data variables.product.prodname_code_scanning %} para seu repositório, você deve adicionar ao repositório um fluxo de trabalho do {% data variables.product.prodname_actions %} que inclui análise do {% data variables.product.prodname_codeql %}. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning). ".
-
-{% data reusables.code-scanning.edit-workflow %}
-Para obter mais informações sobre a configuração de {% data variables.product.prodname_code_scanning %} e edição de arquivos do fluxo de trabalho, consulte "[Configurar o {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" e "[Configurar um fluxo de trabalho](/actions/configuring-and-managing-workflows/configuring-a-workflow)".
-
-### Sobre a autobuild para {% data variables.product.prodname_codeql %}
-
-{% data reusables.code-scanning.autobuild-compiled-languages %}
-
-{% note %}
-
-**Observação**: Se você usa executores auto-hospedados para {% data variables.product.prodname_actions %}, talvez seja necessário instalar um software adicional para usar o processo de `autobuild`. Além disso, se seu repositório precisar de uma versão específica de uma ferramenta de criação, talvez seja necessário instalá-lo manualmente. Para obter mais informações, consulte "[Software instalado nos executores hospedados no GitHub](/actions/reference/software-installed-on-github-hosted-runners)".
-
-{% endnote %}
-
-#### C/C++
-
-| Tipo de sistema compatível | Nome do sistema |
-| -------------------------- | -------------------------------------------------------- |
-| Sistema operacional | Windows e Linux |
-| Sistema de criação | Autoconf, CMake, qmake, Meson, Waf, SCons e Linux Kbuild |
-
-O comportamento da etapa de
autobuild` varia de acordo com o sistema operacional em que a extração é executada. No Windows, a etapa não tem ações-padrão. No Linux, esta etapa revisa os arquivos presentes no repositório para determinar o sistema de criação usado:
-
-
-- Procure um sistema de criação no diretório-raiz.
-- Se nenhum for encontrado, procure um diretório único nos subdiretórios com um sistema de criação para C/C++.
-- Execute um comando apropriado para configurar o sistema.
-
-
-C
-
-
-
-
- Tipo de sistema compatível |
- Nome do sistema |
-
-
-
-
- Sistema operacional |
- Windows e Linux |
-
-
- Sistema de criação |
- .NET, MSbuild e scripts de criação |
-
-
-
-
-O processo de autobuild` tenta detectar automaticamente um método de criação adequado para C# usando a seguinte abordagem:
-
-1. Invocar o arquivo `dotnet build` na solução (`.sln`) ou projeto (`.csproj`) mais próximo da raiz.
-2. Invocar `MSbuild` (Linux) ou `MSBuild.exe` (Windows) na solução ou no arquivo do projeto mais próximo da raiz. Se o `autobuild` detectar várias soluções ou arquivos de projeto na mesma profundidade (mais curta) do diretório de nível superior, ele tentará criar todos eles.
-3. Invoca um script que parece um script de criação—_build_ e _build.sh_ (nessa ordem, para o Linux) ou _build.bat_, _build.cmd_, _e build.exe_ (nessa ordem para o Windows).
-
-
-#### Java
-
-| Tipo de sistema compatível | Nome do sistema |
-| -------------------------- | -------------------------------------- |
-| Sistema operacional | Windows, macOS e Linux (sem restrição) |
-| Sistema de criação | Gradle, Maven e Ant |
-
-O processo de `autobuild` tenta determinar o sistema de criação para bases de código do Java aplicando esta estratégia:
-
-1. Procurar um arquivo de criação no diretório-raiz. Verifique o arquivos do Gradle, do Maven e, em seguida, do Ant.
-2. Execute o primeiro arquivo de criação encontrado. Se os arquivos do Gradle e do Maven estiverem presentes, será usado o arquivo do Gradle.
-3. Caso contrário, procure arquivos de criação nos subdiretórios diretos do diretório-raiz. Se apenas um subdiretório contiver arquivos de criação, execute o primeiro arquivo identificado nesse subdiretório (usando a mesma preferência de 1). Se mais de um subdiretório conter arquivos de criação, relate um erro.
-
-### Adicionar passos de criação a uma linguagem compilada
-
-{% data reusables.code-scanning.autobuild-add-build-steps %} Para obter informações sobre a edição do fluxo de trabalho, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)".
-
-Depois de remover a etapa de `autobuild`, remova o comentário da etapa `executar` e adicione comandos de criação adequados ao seu repositório. A etapa do fluxo de trabalho `executar` executa programas da linha de comando que usam o shell do sistema operacional. Você pode modificar esses comandos e adicionar mais comandos para personalizar o processo de criação.
-
-``` yaml
-- run: |
- make bootstrap
- make release
-```
-
-Para obter mais informações sobre a palavra-chave `executar`, consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)".
-
-Também é possível usar uma matriz para atualizar o fluxo de trabalho para criar mais de uma linguagem compilada, se esta for a abordagem apropriada para o seu sistema e não causar conflitos. Para obter mais informações, consulte "[Configurar uma matriz de criação](/actions/configuring-and-managing-workflows/configuring-a-workflow#configuring-a-build-matrix)".
-
-
-Por exemplo, o fluxo de trabalho abaixo executa um trabalho para análise C/C++ e outro para análise do Java.
-
-```yaml
-
-name: "Code Scanning - Action"
-
-on:
- pull_request:
- branches: [master]
- push:
- branches: [master]
-
-jobs:
- CodeQL-Build:
-
- strategy:
- fail-fast: false
- matrix:
- language: [ 'cpp', 'java']
-
- # CodeQL runs on ubuntu-latest, windows-latest, and macos-latest
- runs-on: ubuntu-latest
-
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
-
- # Initializes the CodeQL tools for scanning.
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: ${{ matrix.language }}
-
- # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
- # Se esta etapa falhar, você deverá removê-lo e executar a criação manualmente.
- - name: Autobuild
- uses: github/codeql-action/autobuild@v1
-
- - name: Perform CodeQL Analysis
- uses: github/codeql-action/analyze@v1
-```
-
-Para obter mais dicas e truques sobre por que o `autobuild` não criará seu código, consulte[Solução de problemas para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning)".
-
-Se você adicionou etapas manuais de criação para linguagens compiladas ou usou uma matriz de criação e o {% data variables.product.prodname_code_scanning %} ainda não está funcionando no seu repositório, entre em contato com {% data variables.contact.contact_support %}.
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages.md
deleted file mode 100644
index 0e452d3ab72c..000000000000
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages.md
+++ /dev/null
@@ -1,151 +0,0 @@
----
-title: Configuring the CodeQL action for compiled languages
-shortTitle: Configurar para linguagens compiladas
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.product.prodname_codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
-product: '{% data reusables.gated-features.code-scanning %}'
-permissions: 'Pessoas com permissões de gravação para um repositório podem configurar {% data variables.product.prodname_code_scanning %} para o repositório.'
-redirect_from:
- - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
-
-### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages
-
-Para habilitar o {% data variables.product.prodname_code_scanning %} para seu repositório, você deve adicionar ao repositório um fluxo de trabalho do {% data variables.product.prodname_actions %} que inclui análise do {% data variables.product.prodname_codeql %}. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning).
-
-{% data reusables.code-scanning.edit-workflow %}
-For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Configuring a workflow](/actions/configuring-and-managing-workflows/configuring-a-workflow)."
-
-### Sobre a autobuild para {% data variables.product.prodname_codeql %}
-
-{% data reusables.code-scanning.autobuild-compiled-languages %}
-
-{% note %}
-
-**Observação**: Se você usa executores auto-hospedados para {% data variables.product.prodname_actions %}, talvez seja necessário instalar um software adicional para usar o processo de `autobuild`. Além disso, se seu repositório precisar de uma versão específica de uma ferramenta de criação, talvez seja necessário instalá-lo manualmente. Para obter mais informações, consulte "[Software instalado nos executores hospedados no GitHub](/actions/reference/software-installed-on-github-hosted-runners)".
-
-{% endnote %}
-
-#### C/C++
-
-| Tipo de sistema compatível | Nome do sistema |
-| -------------------------- | -------------------------------------------------------- |
-| Sistema operacional | Windows e Linux |
-| Sistema de criação | Autoconf, CMake, qmake, Meson, Waf, SCons e Linux Kbuild |
-
-O comportamento da etapa de
autobuild` varia de acordo com o sistema operacional em que a extração é executada. No Windows, a etapa não tem ações-padrão. No Linux, esta etapa revisa os arquivos presentes no repositório para determinar o sistema de criação usado:
-
-
-- Procure um sistema de criação no diretório-raiz.
-- Se nenhum for encontrado, procure um diretório único nos subdiretórios com um sistema de criação para C/C++.
-- Execute um comando apropriado para configurar o sistema.
-
-
-C
-
-
-
-
- Tipo de sistema compatível |
- Nome do sistema |
-
-
-
-
- Sistema operacional |
- Windows e Linux |
-
-
- Sistema de criação |
- .NET, MSbuild e scripts de criação |
-
-
-
-
-O processo de autobuild` tenta detectar automaticamente um método de criação adequado para C# usando a seguinte abordagem:
-
-1. Invocar o arquivo `dotnet build` na solução (`.sln`) ou projeto (`.csproj`) mais próximo da raiz.
-2. Invocar `MSbuild` (Linux) ou `MSBuild.exe` (Windows) na solução ou no arquivo do projeto mais próximo da raiz. Se o `autobuild` detectar várias soluções ou arquivos de projeto na mesma profundidade (mais curta) do diretório de nível superior, ele tentará criar todos eles.
-3. Invoca um script que parece um script de criação—_build_ e _build.sh_ (nessa ordem, para o Linux) ou _build.bat_, _build.cmd_, _e build.exe_ (nessa ordem para o Windows).
-
-#### Java
-
-| Tipo de sistema compatível | Nome do sistema |
-| -------------------------- | -------------------------------------- |
-| Sistema operacional | Windows, macOS e Linux (sem restrição) |
-| Sistema de criação | Gradle, Maven e Ant |
-
-O processo de `autobuild` tenta determinar o sistema de criação para bases de código do Java aplicando esta estratégia:
-
-1. Procurar um arquivo de criação no diretório-raiz. Verifique o arquivos do Gradle, do Maven e, em seguida, do Ant.
-2. Execute o primeiro arquivo de criação encontrado. Se os arquivos do Gradle e do Maven estiverem presentes, será usado o arquivo do Gradle.
-3. Caso contrário, procure arquivos de criação nos subdiretórios diretos do diretório-raiz. Se apenas um subdiretório contiver arquivos de criação, execute o primeiro arquivo identificado nesse subdiretório (usando a mesma preferência de 1). Se mais de um subdiretório conter arquivos de criação, relate um erro.
-
-### Adicionar passos de criação a uma linguagem compilada
-
-{% data reusables.code-scanning.autobuild-add-build-steps %} Para obter informações sobre a edição do fluxo de trabalho, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)".
-
-Depois de remover a etapa de `autobuild`, remova o comentário da etapa `executar` e adicione comandos de criação adequados ao seu repositório. A etapa do fluxo de trabalho `executar` executa programas da linha de comando que usam o shell do sistema operacional. Você pode modificar esses comandos e adicionar mais comandos para personalizar o processo de criação.
-
-``` yaml
-- run: |
- make bootstrap
- make release
-```
-
-Para obter mais informações sobre a palavra-chave `executar`, consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)".
-
-Também é possível usar uma matriz para atualizar o fluxo de trabalho para criar mais de uma linguagem compilada, se esta for a abordagem apropriada para o seu sistema e não causar conflitos. Para obter mais informações, consulte "[Configurar uma matriz de criação](/actions/configuring-and-managing-workflows/configuring-a-workflow#configuring-a-build-matrix)".
-
-
-Por exemplo, o fluxo de trabalho abaixo executa um trabalho para análise C/C++ e outro para análise do Java.
-
-```yaml
-
-name: "CodeQL"
-
-on:
- push:
- branches: [main, ]
- pull_request:
- branches: [main]
-
-jobs:
- CodeQL-Build:
-
- strategy:
- fail-fast: false
- matrix:
- language: ['cpp', 'java']
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %} runs-on: self-hosted
-{% else %} # CodeQL runs on ubuntu-latest, windows-latest, and macos-latest
- runs-on: ubuntu-latest{% endif %}
-
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
-
- # Initializes the CodeQL tools for scanning.
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: ${{ matrix.language }}
-
- # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
- # Se esta etapa falhar, você deverá removê-lo e executar a criação manualmente.
- - name: Autobuild
- uses: github/codeql-action/autobuild@v1
-
- - name: Perform CodeQL Analysis
- uses: github/codeql-action/analyze@v1
-```
-
-Para obter mais dicas e truques sobre por que o `autobuild` não criará seu código, consulte[Solução de problemas para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning)".
-
-Se você adicionou etapas manuais de criação para linguagens compiladas ou usou uma matriz de criação e o {% data variables.product.prodname_code_scanning %} ainda não está funcionando no seu repositório, entre em contato com {% data variables.contact.contact_support %}.
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning.md
deleted file mode 100644
index 0185f99ca950..000000000000
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Habilitar a varredura de código
-intro: 'Você pode habilitar o {% data variables.product.prodname_code_scanning %} para o repositório do seu projeto.'
-product: '{% data reusables.gated-features.code-scanning %}'
-permissions: 'As pessoas com permissões de gravação em um repositório podem habilitar o {% data variables.product.prodname_code_scanning %} para o repositório.'
-redirect_from:
- - /github/managing-security-vulnerabilities/configuring-automated-code-scanning
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.code-scanning.beta %}
-
-### Habilitar o {% data variables.product.prodname_code_scanning %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-3. À direita de "Varredura de código", clique em **Configurar a varredura de código**. ![Botão de "Configurar a varredura de código" à direita de "Varredura de código" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Em "Comece com a varredura de código", clique em **Configurar este fluxo de trabalho**. ![Botão "Configurar este fluxo de trabalho" no cabeçalho "Comece com a varredura do código" cabeçalho](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)
-5. Opcionalmente, para personalizar a forma como {% data variables.product.prodname_code_scanning %} faz a varredura do seu código, edite o fluxo de trabalho. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
-6. Use o menu suspenso **Iniciar commit** e digite uma mensagem de commit. ![Iniciar commit](/assets/images/help/repository/start-commit-commit-new-file.png)
-7. Escolha se você gostaria de fazer commit diretamente no branch-padrão ou criar um novo branch e iniciar um pull request. ![Escolher onde fazer commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png)
-8. Clique em **Fazer commit do novo arquivo** ou **Propor novo arquivo**.
-
-Depois que você confirmar o arquivo de fluxo de trabalho ou criar um pull request, {% data variables.product.prodname_code_scanning %} analisará seu código de acordo com a frequência especificada no arquivo de fluxo de trabalho. Se você criou um pull request, o {% data variables.product.prodname_code_scanning %} somente analisará o código no branch de tópico do pull request até você mesclar o pull request no branch-padrão do repositório.
-
-### Próximas etapas
-
-Após ativar o {% data variables.product.prodname_code_scanning %}, você poderá monitorar a análise, visualizar os resultados e personalizar ainda mais a forma como faz a varredura do seu código.
-
-- Você pode visualizar o status de execução de {% data variables.product.prodname_code_scanning %} e obter notificações referentes às execuções concluídas. Para obter mais informações, consulte "[Gerenciar a execução de um fluxo de trabalho](/actions/configuring-and-managing-workflows/managing-a-workflow-run)" e "[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)".
-- Após a conclusão de uma varredura, você pode visualizar alertas de uma varredura concluída. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning)."
-- É possível personalizar a forma como o {% data variables.product.prodname_code_scanning %} faz a varredura do código no repositório. Para obter mais informações, consulte "[Configurar a verificação de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)".
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning.md
deleted file mode 100644
index 08e59c012917..000000000000
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Gerenciar alertas da varredura de código
-shortTitle: Gerenciando alertas
-intro: 'Você pode visualizar, corrigir e fechar alertas de possíveis vulnerabilidades ou erros no código do seu projeto.'
-product: '{% data reusables.gated-features.code-scanning %}'
-permissions: 'As pessoas com permissões de gravação em um repositório podem gerenciar os alertas de {% data variables.product.prodname_code_scanning %} para o repositório.'
-redirect_from:
- - /github/managing-security-vulnerabilities/managing-alerts-from-automated-code-scanning
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning %}
-
-### Sobre os alertas de {% data variables.product.prodname_code_scanning %}
-
-Depois que você habilitar o {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dotcom %} exibirá alertas do {% data variables.product.prodname_code_scanning %} no seu repositório. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning).
-
-Cada alerta destaca um problema com o código e o nome da ferramenta que o identificou. Você pode ver a linha de código que acionou o alerta, bem como propriedades do alerta, como, por exemplo, a gravidade e a natureza do problema. Os alertas também informam quando o problema foi introduzido pela primeira vez. Para os alertas identificados pela análise do {% data variables.product.prodname_codeql %} , você também verá informações sobre como corrigir o problema.
-
-![Exemplo de alerta de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
-
-Se você não tomar a ação recomendada pelo alerta, você poderá fechar o alerta manualmente. Por exemplo, você pode fechar um alerta para o código usado para testes ou se você achar que o alerta é um falso positivo. Você também pode querer fechar um alerta se o esforço de corrigir o erro de codificação for maior do que o benefício potencial de melhorar o código.
-
-Por padrão, o {% data variables.product.prodname_dotcom %} exibe alertas para o branch-padrão e para quaisquer branches protegidos. Você pode classificar e filtrar a lista de alertas para ver apenas os alertas pelos quais você se interessa.
-
-Você pode ver os alertas introduzidos em um pull request e tomar medidas imediatas. Quando {% data variables.product.prodname_code_scanning %} encontra vulnerabilidades ou erros em um pull request, {% data variables.product.prodname_dotcom %} exibe anotações na linha do tempo e nas visualizações diferenciais do pull request.
-
-Se você habilitar o {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_codeql %}, isso também poderá detectar problemas no fluxo de dados no seu código. A análise do fluxo de dados encontra potenciais problemas de segurança no código, tais como: usar dados de forma insegura, passar argumentos perigosos para funções e vazar informações confidenciais.
-
-Quando {% data variables.product.prodname_code_scanning %} relata alertas de fluxo de dados, {% data variables.product.prodname_dotcom %} mostra como os dados se movem através do código. {% data variables.product.prodname_code_scanning_capc %} permite que você identifique as áreas do seu código que vazam informações confidenciais que poderia ser o ponto de entrada para ataques de usuários maliciosos.
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %} {% data reusables.code-scanning.get-started-uploading-third-party-data %}
-
-Se você fizer a varredura do seu código usando uma ferramenta de terceiros ou fizer a varredura do seu código com consultas personalizadas de {% data variables.product.prodname_codeql %}, {% data variables.product.prodname_dotcom %} só usará as propriedades compatíveis do SARIF 2.1.0 para exibir alertas. Os resultados de ferramentas de terceiros ou consultas personalizadas podem não incluir todas as propriedades que você vê ao fazer a varredura do seu código usando as consultas-padrão de {% data variables.product.prodname_codeql %} no {% data variables.product.company_short %}. Para obter mais informações, consulte "[Suporte SARIF para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)".
-
-### Visualizar um alerta
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% data reusables.code-scanning.click-alert-in-list %}
-5. Opcionalmente, se o alerta destaca um problema com o fluxo de dados, clique em **Mostrar caminhos** para revisar o caminho dos dados. ![Exemplo de alerta de fluxo de dados](/assets/images/help/repository/code-scanning-show-paths.png)
-
-### Fechar um alerta
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% data reusables.code-scanning.click-alert-in-list %}
-5. Use o menu suspenso "Fechar", e clique em um motivo para fechar o alerta. ![Escolher o motivo para fechar o alerta no menu suspenso "Fechar"](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-### Leia mais
-
-- "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)"
-- "[{% data variables.product.prodname_code_scanning_capc %} API](/v3/code-scanning)"
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning.md
deleted file mode 100644
index 0853c1c0704c..000000000000
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Gerenciar resultados da varredura de código
-shortTitle: Gerenciar resultados
-intro: 'Você pode visualizar, triar, entender e resolver vulnerabilidades e erros que o {% data variables.product.prodname_code_scanning %} encontra.'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning.md
deleted file mode 100644
index 36819579483d..000000000000
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-title: Troubleshooting code scanning
-shortTitle: Troubleshooting
-intro: 'You can see tips to resolve common issues with {% data variables.product.prodname_code_scanning %}.'
-product: '{% data reusables.gated-features.code-scanning %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning %}
-
-### Automatic build for a compiled language fails
-
-If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps.
-
-- Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-- If the repository for your project contains code in a specific language that does not build, disable automatic language detection in your {% data variables.product.prodname_code_scanning %} workflow and specify only the languages you want to build. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#overriding-automatic-language-detection)."
-
-### No code found during the build
-
-If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to trace your code. Several reasons can explain such a failure:
-
-1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by updating the `init` step to specify the supported languages that are present in your repository. For example, the following configuration will analyze only Go, and JavaScript.
-
- ```yaml
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: go, javascript # Other options are csharp, python, cpp, java
- ```
-2. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually. For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-3. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis.
-4. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis.
-5. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are certain configuration options like running your build process in a container, if you're building using a distributed build system external to {% data variables.product.prodname_actions %} using a daemon process, or if {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
- 1. For C# projects using either `dotnet build` or `msbuild` which target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later.
-
- For example, the following configuration will pass the flag during the first build step.
-
- ```yaml
- - run: |
- dotnet build /p:UseSharedCompilation=false
- ```
- 2. If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
-
-For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-
-### Portions of my repository were not analyzed using `autobuild`
-
-The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. Alternatively, if more than one compiled language is present in your repository and you want {% data variables.product.prodname_code_scanning %} to analyze all these compiled languages, you can use a build matrix in your workflow. {% if currentVersion ver_gt "enterprise-server@2.21" %}To use a build matrix, you should make sure that {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location_enterprise %}. {% endif %}For more information, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)" and
-"[Configuring the {% data variables.product.prodname_codeql %} action for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-
-### Error: "Server error"
-
-If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
-
-### Error: "Out of disk" or "Out of memory"
-
-On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem.
-{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
-
-### The build takes too long
-
-If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time.
-
-#### Increase the memory or cores
-
-If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners.
-
-#### Use matrix builds to parallelize the analysis
-
-By default, {% data variables.product.prodname_codeql %} performs analysis of each language sequentially, which can impact performance, especially for repositories with more than one language. You can speed analysis up by using a build matrix that splits the analysis by language. {% if currentVersion ver_gt "enterprise-server@2.21" %}To use a build matrix, you should make sure that {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location_enterprise %}. {% endif %}For more information, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)."
-
-For example, the workflow below will be run with one job for JavaScript analysis, and another job for Go analysis.
-
-```yaml
-
-name: "Code Scanning - Action"
-
-on:
- pull_request:
- branches: [main]
- push:
- branches: [main]
-
-jobs:
- CodeQL-Build:
-
- strategy:
- fail-fast: false
- matrix:
- language: [ 'go', 'javascript']
-
- # CodeQL runs on ubuntu-latest, windows-latest, and macos-latest
- runs-on: ubuntu-latest
-
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
-
- # Initializes the CodeQL tools for scanning.
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: ${{ matrix.language }}
-
- # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
- # If this step fails, then you should remove it and run the build manually (see below).
- - name: Autobuild
- uses: github/codeql-action/autobuild@v1
-
- - name: Perform CodeQL Analysis
- uses: github/codeql-action/analyze@v1
-```
-
-#### Reduce the amount of code being analyzed in a single workflow
-
-Analysis time is typically proportional to the amount of code being analyzed. You can reduce the analysis time by reducing the amount of code being analyzed at once, for example, by excluding test code, or breaking analysis into multiple workflows that analyze only a subset of your code at a time.
-
-For compiled languages like Java, C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build only the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-
-For interpreted languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without a specific build, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#specifying-directories-to-scan)."
-
-If you split your analysis into multiple workflows as described above, we still recommend that you have at least one workflow which runs on a `schedule` which analyzes all of the code in your repository. Because {% data variables.product.prodname_codeql %} analyzes data flows between components, some complex security behaviors may only be detected on a complete build.
-
-#### Run only during a `schedule` event
-
-If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies.md
deleted file mode 100644
index 0320b1d510ec..000000000000
--- a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Sobre alertas de segurança para dependências vulneráveis
-intro: '{% data variables.product.product_name %} sends security alerts when we detect vulnerabilities affecting your repository.'
-redirect_from:
- - /articles/about-security-alerts-for-vulnerable-dependencies
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### Sobre vulnerabilidades de segurança
-
-{% data reusables.repositories.a-vulnerability-is %} Depending on the severity level and the way your project uses the dependency, vulnerabilities can cause a range of problems for your project or the people who use it. Você pode rastrear e resolver vulnerabilidades para determinados tipos de dependência no seu repositório do {% data variables.product.product_name %}.
-
-If {% data variables.product.prodname_dotcom %} detects a vulnerability from the {% data variables.product.prodname_advisory_database %} or [WhiteSource](https://www.whitesourcesoftware.com/GitHubSecurityAlerts) in one of the dependencies in your repository's dependency graph, we'll send you a security alert. For more information about the {% data variables.product.prodname_advisory_database %}, see "Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}."
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Alerts and automated security updates for vulnerable dependencies
-{% else %}
-### Alertas de segurança para dependências vulneráveis
-{% endif %}
-
-When a new vulnerability is added to the GitHub Advisory Database, we identify{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repositories{% if currentVersion == "free-pro-team@latest" %} (and private repositories that have opted in to vulnerability detection){% endif %} that use the affected version of the dependency{% if currentVersion == "free-pro-team@latest" %}, send a security alert to repository maintainers, and generate an automated security update{% else %} and send a security alert to repository maintainers{% endif %}.
-
-Each security alert includes a severity level{% if currentVersion == "free-pro-team@latest" %}, a link to the affected file in your project, and a link to a pull request containing an automated security update that resolves the vulnerability{% else %} and a link to the affected file in your project{% endif %}. Quando disponível, o alerta incluirá mais detalhes sobre a vulnerabilidade.
-
-Você pode ver todos os alertas que afetam um projeto específico{% if currentVersion == "free-pro-team@latest" %} na guia Alerts (Alertas) do repositório ou{% endif %} no gráfico de dependência do repositório.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Exibir e atualizar dependências vulneráveis no repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %}
-
-Enviamos alertas de segurança para as pessoas com permissões de administrador nos repositórios afetados por padrão. O {% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas em algum repositório.{% if currentVersion == "free-pro-team@latest" %} Você também pode habilitar alertas de segurança para mais pessoas ou equipes que trabalham nos repositórios que pertencem à organização. Para obter mais informações, consulte "[Gerenciar alertas para dependências vulneráveis nos repositórios da sua organização](/articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories)".{% endif %}
-
-{% data reusables.repositories.enable-security-alerts %}
-{% if currentVersion == "free-pro-team@latest" %}
-Automated security updates update vulnerable dependencies to the minimum version that resolves the vulnerability. Automated security updates are automatically enabled in repositories that use the dependency graph and security alerts, but you can choose to disable automatic pull requests and generate security updates manually instead. For more information, see "[Configuring automated security updates](/github/managing-security-vulnerabilities/configuring-automated-security-updates)."
-
-O {% data variables.product.prodname_dotcom %} detecta e alerta sobre dependências vulneráveis em repositórios _públicos_ por padrão. Para receber alertas de segurança para dependências vulneráveis em um repositório _privado_, um proprietário ou uma pessoa com acesso de administrador ao repositório deve habilitar o gráfico de dependência e os alertas de segurança no repositório. Para obter mais informações, consulte "[Aceitar ou recusar o uso de dados de seu repositório privado](/articles/opting-into-or-out-of-data-use-for-your-private-repository)".
-{% endif %}
-
-Para obter uma lista de linguagens aceitas em que o {% data variables.product.product_name %} pode detectar vulnerabilidades e dependências, consulte "[Listar os pacotes dos quais um repositório depende](/articles/listing-the-packages-that-a-repository-depends-on)".
-
-{% warning %}
-
-**Observação**: os recursos de segurança do {% data variables.product.product_name %}, como os alertas de segurança, não têm a pretensão de capturar todas as vulnerabilidades. Embora estejamos sempre tentando atualizar nosso banco de dados de vulnerabilidades e alertar você com nossas informações mais atualizadas, não podemos capturar tudo nem alertar sobre vulnerabilidades conhecidas dentro de um prazo garantido. Esses recursos não substituem a revisão humana de cada dependência em busca de possíveis vulnerabilidades ou algum outro problema, e nossa sugestão é consultar um serviço de segurança ou realizar uma revisão completa de vulnerabilidade quando necessário.
-
-{% endwarning %}
-
-### Configurar notificações para alertas de segurança
-
-By default, you will receive security alerts by email{% if currentVersion == "free-pro-team@latest" %}, grouped by the specific vulnerability{% endif %}. You can also choose to receive security alerts in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the {% data variables.product.product_name %} user interface. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#security-alert-options){% else %}"[Choosing the delivery method for your notifications ](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}."
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
-
-### Leia mais
-
-{% if currentVersion == "free-pro-team@latest" %}- "[Configuring automated security updates](/github/managing-security-vulnerabilities/configuring-automated-security-updates)"
-- "[Exibir e atualizar dependências vulneráveis no repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
-- [Definição de "vulnerabilidade"](https://cve.mitre.org/about/terminology.html#vulnerability) da MITRE
diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-automated-security-updates.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-automated-security-updates.md
deleted file mode 100644
index 7eae5c84bc82..000000000000
--- a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-automated-security-updates.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: Configuring automated security updates
-intro: Você pode usar pull request automatizadas ou manuais para atualizar facilmente dependências vulneráveis.
-redirect_from:
- - /articles/configuring-automated-security-fixes
- - /github/managing-security-vulnerabilities/configuring-automated-security-fixes
-versions:
- free-pro-team: '*'
----
-
-### About automated security updates
-
-You can enable automated security updates for any repository that uses security alerts and the dependency graph. You can disable automated security updates for an individual repository or for all repositories owned by your user account or organization.
-
-When you receive a security alert about a vulnerable dependency in your repository, you can resolve the vulnerability using an automated security update in a pull request that corresponds to the security alert. Automated security updates are available in repositories that use the dependency graph. Por padrão, o {% data variables.product.prodname_dotcom %} cria automaticamente uma pull request no repositório de modo a atualizar a dependência vulnerável para a menor versão segura necessária para evitar a vulnerabilidade. Se preferir, você pode desabilitar as pull requests automáticas e criá-las manualmente para atualizar dependências somente quando for conveniente.
-
-As solicitações de segurança automatizadas contêm tudo o que você precisa para fazer a revisão e o merge de modo rápido e seguro de uma correção proposta no seu projeto, incluindo informações sobre a vulnerabilidade, como notas de versão, entradas no log de mudanças e detalhes do commit.
-
-Automated security updates are opened by Dependabot on behalf of {% data variables.product.prodname_dotcom %}. The Dependabot {% data variables.product.prodname_github_app %} is automatically installed on every repository where automated security updates are enabled.
-
-As pessoas com acesso aos alertas de segurança do seu repositório verão um link para o alerta de segurança relevante, embora outras pessoas com acesso à pull request não possam ver qual vulnerabilidade a pull request resolve.
-
-When you merge a pull request that contains an automated security update, the corresponding security alert is marked as resolved for your repository.
-
-{% note %}
-
-**Note:** Automated security updates resolve security vulnerabilities only. Automated security updates are not created to resolve vulnerabilities in private registries or packages hosted in private repositories.
-
-{% endnote %}
-
-### Supported repositories
-
-{% data variables.product.prodname_dotcom %} automatically enables automated security updates for every repository that meets these requirements.
-
-{% note %}
-
-**Note**: For repositories created before November 2019, {% data variables.product.prodname_dotcom %} has automatically enabled automated security updates if the repository meets the following criteria and has received at least one push since May 23, 2019.
-
-{% endnote %}
-
-| Requirement | More information |
-| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Repository is not a fork | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |
-| Repository is not archived | "[Archiving repositories](/github/creating-cloning-and-archiving-repositories/archiving-repositories)" |
-| Repository is public, or repository is private and you have enabled read-only analysis by {% data variables.product.prodname_dotcom %}, dependency graph, and vulnerability alerts in the repository's settings | "[Opting into data use for your private repository](/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository#opting-into-data-use-for-your-private-repository)" |
-| Repository contains dependency manifest file from a package ecosystem that {% data variables.product.prodname_dotcom %} supports | "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on#supported-package-ecosystems)" |
-| Automated security updates are not disabled for the repository | "[Managing automated security updates for your repository](#managing-automated-security-updates-for-your-repository)" |
-| Repository is not already using an integration for dependency management | "[Sobre integrações](/github/customizing-your-github-workflow/about-integrations)" |
-
-If automated security updates are not enabled for your repository and you don't know why, you can [contact support](https://support.github.com/contact).
-
-### Sobre pontuações de compatibilidade
-
-Automated security updates also include compatibility scores to let you know whether updating a vulnerability could cause breaking changes to your project. We look at previously-passing CI tests from public repositories where we've generated a given automated security update to learn whether the update causes tests to fail. Uma pontuação de compatibilidade da atualização é a porcentagem de execuções de CI que foram aprovadas durante a atualização entre versões relevantes da dependência.
-
-### Managing automated security updates for your repository
-
-You can enable or disable automated security updates for an individual repository.
-
-Automated security updates require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)."
-
-{% data reusables.repositories.you-can-enable-or-disable-security-features %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-4. Above the list of alerts, use the drop-down menu and select or unselect **Automated security updates**. ![Drop-down menu with the option to enable automated security updates](/assets/images/help/repository/enable-automated-security-updates-drop-down.png)
-
-### Managing automated security updates for your user account
-
-You can disable automated security updates for all repositories owned by your user account. If you do, you can still enable automated security updates for individual repositories owned by your user account.
-
-{% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.security %}
-{% data reusables.repositories.opt-out-automated-security-updates %}
-
-### Managing automated security updates for your organization
-
-Organization owners can disable automated security updates for all repositories owned by the organization. If you do, anyone with admin permissions to an individual repository owned by the organization can still enable automated security updates on that repository.
-
-{% data reusables.repositories.you-can-enable-or-disable-security-features %}
-
-{% data reusables.profile.access_profile %}
-{% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.security %}
-{% data reusables.repositories.opt-out-automated-security-updates %}
-
-### Leia mais
-
-- "[Sobre alertas de segurança para dependências vulneráveis](/articles/about-security-alerts-for-vulnerable-dependencies)"
-- "[Opting into data use for your private repository](/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository#opting-into-data-use-for-your-private-repository)"
-- "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on#supported-package-ecosystems)"
diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization.md
deleted file mode 100644
index 3d5455fdc86f..000000000000
--- a/translations/pt-BR/content/github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Gerenciar alertas para dependências vulneráveis na organização
-intro: 'Os proprietários e administradores de repositórios da organização recebem {% data variables.product.prodname_dependabot_alerts %} quando detectamos uma dependência vulnerável no repositório de uma organização. Você pode especificar outros membros ou equipes com acesso de gravação para também receber alertas de dependências vulneráveis.'
-redirect_from:
- - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories/
- - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories/
- - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization
-versions:
- free-pro-team: '*'
----
-
-{% if currentVersion == "free-pro-team@latest" %}
-{% data reusables.repositories.you-can-manage-access-to-security-alerts %}
-{% endif %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. Na barra lateral esquerda, clique em **alertas do Dependabot**. ![Aba de alertas do Dependabot na barra lateral de configurações](/assets/images/help/settings/settings-sidebar-dependabot-alerts.png)
-4. Digite o nome da pessoa ou equipe que você gostaria de receber {% data variables.product.prodname_dependabot_alerts %} quando {% data variables.product.product_name %} detectar uma dependência vulnerável e, em seguida, clique no nome do usuário ou equipe para selecioná-lo.
-5. Após selecionar todas as pessoas ou equipes que deseja receber {% data variables.product.prodname_dependabot_alerts %}, clique em **Salvar alterações**.
-
-### Further reading
-
-- "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)"
-- "[Exibir e atualizar dependências vulneráveis no repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Gerenciando configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)"
diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-code-for-exact-matches.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-code-for-exact-matches.md
deleted file mode 100644
index 997da9383a30..000000000000
--- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-code-for-exact-matches.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Searching code for exact matches
-intro: 'You can search code for exact matches in repositories on {% data variables.product.prodname_dotcom %}.'
-redirect_from:
- - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches
-permissions: People with read permissions to a repository can search the repository's files for exact matches.
-versions:
- free-pro-team: '*'
----
-
-{% note %}
-
-{% data reusables.search.exact-match-beta %} To request access to the beta, [join the waitlist](https://github.com/features/code-search-exact-match/signup).
-
-{% endnote %}
-
-### About searching code for exact matches
-
-{% data reusables.search.exact-match %}
-
-By default, searches for exact matches are case and symbol-sensitive, and don't include partial matches or normalized grammar. For example, searching for `let ReactDOM*` will only return `let ReactDOM*`.
-
-### Searching code for exact matches
-
-{% note %}
-
-Searching files within a repository for exact matches only works with indexed repositories for the beta release.
-
-{% endnote %}
-
-{% data reusables.repositories.navigate-to-repo %}
-2. In the search field, type the string you'd like to find. ![Exact match search string](/assets/images/help/search/exact-match-search-string.png)
-3. Optionally, click the **Options** drop-down to narrow your search. ![Exact match search Options drop-down](/assets/images/help/search/exact-match-options.png)
-4. Press Enter or Return on your keyboard.
-5. In the list of results, click the file.
-
-### Leia mais
-
-- "[Pesquisar código](/github/searching-for-information-on-github/searching-code)"
-- "[Navigating code on {% data variables.product.product_name %}](/github/managing-files-in-a-repository/navigating-code-on-github)"
diff --git a/translations/pt-BR/content/github/site-policy/github-enterprise-cloud-addendum.md b/translations/pt-BR/content/github/site-policy/github-enterprise-cloud-addendum.md
deleted file mode 100644
index cb28c16aa421..000000000000
--- a/translations/pt-BR/content/github/site-policy/github-enterprise-cloud-addendum.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Adendo do GitHub Enterprise Cloud
-redirect_from:
- - /github-business-cloud-addendum/
- - /articles/github-enterprise-cloud-addendum
-versions:
- free-pro-team: '*'
----
-
-Estes são os termos adicionais para o GitHub Enterprise Cloud ("Termos do Enterprise Cloud"). Quaisquer termos capitalizados não definidos nestes Termos do Enterprise Cloud serão definidos nos [Termos de Serviço](/articles/github-terms-of-service/) ou nos [Termos de Serviço Corporativos](/articles/github-corporate-terms-of-service/). Ao concordar com estes Termos do Enterprise Cloud, você também concorda com os Termos de Serviço, conforme determinado pelo tipo de conta que você tem.
-
-O Enterprise Cloud inclui uma conta da organização, login único SAML, provisionamento de acesso e suporte 24 horas por dia, 5 dias por semana, com um tempo de resposta de 8 horas. Esta lista de recursos e serviços não é completa e pode ser atualizada de tempos em tempos. Para obter mais informações, consulte a "[página de preços do GitHub](https://github.com/pricing)".
-
-### Definições:
-- Usuário ativo: usuário que tenta acessar nosso Serviço no momento de uma pane.
-- Cliente: pessoa ou entidade que comprou o Enterprise Cloud do GitHub.
-- Usuário Elegível: um indivíduo designado como membro da organização Enterprise Cloud do cliente por ter sua conta GitHub individual associada à conta Enterprise Cloud do cliente.
-- Serviços essenciais: serviços essenciais para a funcionalidade de controle da versão principal do GitHub, incluindo recursos e serviços como criação, bifurcação e clonagem de reporsitórios; criação, commit e merge de branches; criação, revisão e merge de pull requests; e interfaces de cliente Git, API e web para os fluxos de trabalho principais do Git. Estes são exemplos de serviços e recursos periféricos não incluídos: webhooks, Gists, Pages e notificações por e-mail.
-- Pane: interrupção de um Serviço essencial que afeta mais de 50% dos Usuários Ativos.
-- Crédito de serviço: um crédito em dólar, calculado conforme estabelecido abaixo, que o GitHub pode creditar de volta em uma conta qualificada.
-
-### SLA do tempo de atividade no Enterprise Cloud
-
-Benefícios do Programa:
-- Garantimos que o serviço terá um tempo de atividade trimestral de 99,95%. Isso significa que os Serviços essenciais do GitHub não serão interrompidos por uma pane que afete mais de 50% dos Usuários ativos, por mais de 0,05% do trimestre.
-- Se não cumprirmos essa garantia de tempo de atividade trimestral de 99,95%, poderemos emitir Créditos de Serviço aos clientes.
-
-Como calculamos o Tempo de Atividade?
-- Nosso cálculo do tempo de atividade do é baseado na porcentagem de solicitações bem-sucedidas que ele atende por meio de interfaces de cliente Git, API e web.
-
-O que está excluído da nossa garantia de tempo de atividade? Panes resultantes de:
-- Atos, omissões ou uso indevido dos Serviços pelo cliente, incluindo violações dos Termos de Serviço.
-- Falhas na sua conectividade com a internet
-- Fatores fora do nosso controle razoável, incluindo problemas relacionados ao acesso à internet, eventos de força maior e serviços ou tecnologia de terceiros
-- Seus equipamentos, serviços ou outra tecnologia
-
-O que são Créditos de Serviço de Tempo de Atividade, como posso descobrir se os tenho, e como posso resgatá-los?
-- Se o percentual de tempo de atividade trimestral do GitHub cair abaixo da garantia de 99,95%, o Cliente terá direito de receber um valor equivalente a 25 vezes o valor pago pelo tempo de Pane que exceder a garantia de tempo de atividade trimestral ("Crédito de Serviço por Tempo de Atividade"), que será aplicado na próxima fatura do Cliente. Os Créditos de Serviço por Tempo de Atividade são calculados no final de cada trimestre e só podem ser concedidos mediante solicitação.
-- Para saber mais sobre o percentual de tempo de atividade do GitHub, você pode solicitar um relatório de tempo de atividade no final de cada trimestre.
-- Para receber Créditos de Serviço por Tempo de Atividade, um gerente de cobrança ou proprietário de conta deve enviar um pedido por escrito em nome do Cliente, no prazo de 30 dias a partir do final de cada trimestre. Os Créditos de Serviço por Tempo de Atividade não podem ser poupados. Após ser concedido um Crédito de Serviço por Tempo de Atividade, ele será aplicado automaticamente à próxima fatura do Cliente. Solicitações por escrito devem ser enviadas para {% data variables.contact.contact_support %}.
-
-**Isenção e Limitação de Responsabilidade:**a [Página de Status](https://www.githubstatus.com/) do GitHub não está conectada à SLA de Tempo de Atividade e não é uma representação precisa do Tempo de atividade do GitHub para fins de cálculo de Créditos de Serviço por Tempo de Atividade. Os Créditos de Serviço são limitados a 30 dias de serviço pago, por trimestre. Os Créditos de Serviço são a única reparação do Cliente por qualquer falha do GitHub em cumprir com as obrigações de Tempo de atividade identificadas neste Adendo.
diff --git a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository.md b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository.md
deleted file mode 100644
index aabdc337cd12..000000000000
--- a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Aceitar ou recusar o uso de dados no repositório privado
-intro: 'Para ajudar o {% data variables.product.product_name %} a conectar você a ferramentas, pessoas, projetos e informações relevantes, você pode aceitar o uso de dados no repositório privado. Se você aceitou o uso de dados em seu repositório privado e não quer mais que o {% data variables.product.product_name %} use seus dados, você pode recusar.'
-redirect_from:
- - /articles/opting-into-or-out-of-data-use-for-your-private-repository
-versions:
- free-pro-team: '*'
----
-
-### About data use for your private repository
-
-Ao aceitar o uso de dados no seu repositório privado, você poderá acessar o gráfico de dependências, que possibilita o rastreamento das dependências do repositório e o recebimento de alertas de segurança quando o {% data variables.product.product_name %} detecta dependências vulneráveis. Para obter mais informações, consulte "[Sobre alertas de segurança para dependências vulineráveis](/articles/about-security-alerts-for-vulnerable-dependencies)"
-
-{% data reusables.repositories.you-can-enable-or-disable-security-features %}
-
-### Aceitar o uso de dados no repositório privado
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. Em "Data services" (Serviços de Dados), selecione **Allow {% data variables.product.prodname_dotcom %} to perform read-only analysis of this repository** (Permitir que o {% data variables.product.prodname_dotcom %} faça análises somente leitura neste repositório) . ![Caixa de seleção para permitir que o {% data variables.product.prodname_dotcom %} faça análises somente leitura neste repositório](/assets/images/help/repository/private-repo-data-use-opt-in.png)
-4. Opcionalmente, marque a caixa de seleção ao lado de cada serviço adicional para o qual você deseja habilitar o uso de dados. ![Lista de serviços adicionais com as suas próprias caixas de seleção](/assets/images/help/repository/private-repo-data-use-additional-services.png)
-
-### Recusar o uso de dados no repositório privado
-
-{% tip %}
-
-**Dica:** para recusar o uso de dados em serviços específicos, desmarque a caixa de seleção ao lado do serviço.
-
-{% endtip %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. Em "Data services" (Serviços de Dados), desmarque **Allow {% data variables.product.prodname_dotcom %} to perform read-only analysis of this repository** (Permitir que o {% data variables.product.prodname_dotcom %} faça análises somente leitura neste repositório) . ![Caixa de seleção para não permitir que o {% data variables.product.prodname_dotcom %} faça análises somente leitura neste repositório](/assets/images/help/repository/private-repo-data-use-opt-out.png)
-
-### Leia mais
-
-- "[Sobre o uso de seus dados pelo {% data variables.product.prodname_dotcom %}](/articles/about-github-s-use-of-your-data)"
-- "[Exibir e atualizar dependências vulneráveis no repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Gerenciar alertas para dependências vulneráveis nos repositórios da sua organização](/articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories)"
diff --git a/translations/pt-BR/content/github/using-git/changing-author-info.md b/translations/pt-BR/content/github/using-git/changing-author-info.md
deleted file mode 100644
index f9912ac01c15..000000000000
--- a/translations/pt-BR/content/github/using-git/changing-author-info.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Alterar informações de autor
-redirect_from:
- - /change-author-info/
- - /changing-author-info/
- - /articles/changing-author-info
-intro: 'Para alterar o nome e/ou endereço de e-mail registrado em commits existentes, você deve reescrever todo o histórico do seu repositório Git.'
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-{% warning %}
-
-**Aviso**: esta ação é destrutiva para o histórico do repositório. Se você estiver colaborando em um repositório com outras pessoas, não é uma boa ideia reescrever o histórico publicado. Você só deve fazer isso em caso de emergência.
-
-{% endwarning %}
-
-### Alterar o histórico do seu repositório no Git usando um script
-
-Criamos um script que vai alterar todos os commits que anteriormente tinham o endereço de e-mail antigo em seus campos de autor ou committer para usar o nome e o endereço de e-mail corretos.
-
-{% tip %}
-
-**Observação**: executar esse script reescreve o histórico de todos os colaboradores do repositório. Após conclusão dessas etapas, qualquer pessoa com bifurcações ou clones devem fazer fetch do histórico reescrito e fazer rebase de todas as alterações locais no histórico reescrito.
-
-{% endtip %}
-
-Antes de executar esse script, você precisará:
-
-* Do endereço de e-mail antigo que aparece nos campos de autor/commiter que deseja alterar
-* Do nome e endereço de e-mail corretos aos quais deseja que os commits sejam atribuídos
-
-{% data reusables.command_line.open_the_multi_os_terminal %}
-2. Crie um clone vazio do seu repositório:
- ```shell
- git clone --bare https://{% data variables.command_line.codeblock %}/user/repo.git
- cd repo.git
- ```
-3. Copie e cole o script, substituindo as seguintes variáveis com base nas informações coletadas:
- * `OLD_EMAIL`
- * `CORRECT_NAME`
- * `CORRECT_EMAIL`
-
- ```shell
- #!/bin/sh
-
- git filter-branch --env-filter '
-
- OLD_EMAIL="your-old-email@example.com"
- CORRECT_NAME="Your Correct Name"
- CORRECT_EMAIL="your-correct-email@example.com"
-
- if [ "$GIT_COMMITTER_EMAIL" = "$OLD_EMAIL" ]
- then
- export GIT_COMMITTER_NAME="$CORRECT_NAME"
- export GIT_COMMITTER_EMAIL="$CORRECT_EMAIL"
- fi
- if [ "$GIT_AUTHOR_EMAIL" = "$OLD_EMAIL" ]
- then
- export GIT_AUTHOR_NAME="$CORRECT_NAME"
- export GIT_AUTHOR_EMAIL="$CORRECT_EMAIL"
- fi
- ' --tag-name-filter cat -- --branches --tags
- ```
-
-4. Pressione **Enter** para executar o script.
-5. Revise o novo histórico do Git a fim de verificar se há erros.
-6. Publique o histórico corrigido no {% data variables.product.product_name %}:
- ```shell
- git push --force --tags origin 'refs/heads/*'
- ```
-7. Limpe o clone temporário:
- ```shell
- cd ..
- rm -rf repo.git
- ```
diff --git a/translations/pt-BR/content/github/using-git/updating-credentials-from-the-osx-keychain.md b/translations/pt-BR/content/github/using-git/updating-credentials-from-the-osx-keychain.md
deleted file mode 100644
index fd54786c10e4..000000000000
--- a/translations/pt-BR/content/github/using-git/updating-credentials-from-the-osx-keychain.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Atualizar credenciais da keychain OSX
-intro: 'You''ll need to update your saved credentials in the `git-credential-osxkeychain` helper if you change your username, password, or personal access token on {% data variables.product.product_name %}.'
-redirect_from:
- - /articles/updating-credentials-from-the-osx-keychain
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-{% data reusables.user_settings.password-authentication-deprecation %}
-
-### Atualizar credenciais pelo Keychain Access
-
-1. Procure o app **Keychain Access** (Acesso a keychain) no Finder (Localizador). ![Barra de pesquisa do Spotlight](/assets/images/help/setup/keychain-access.png)
-2. No Keychain Access, procure por **{% data variables.command_line.backticks %}**.
-3. Localize a entrada "internet password" (senha da internet) referente a `{% data variables.command_line.backticks %}`. ![Entrada de senha do GitHub na keychain](/assets/images/help/setup/keychain-entry.png)
-4. Edite ou exclua a entrada de acordo.
-
-### Excluir credenciais pela linha de comando
-
-É possível usar o auxiliar de credenciais diretamente na linha de comando para apagar a entrada de keychain.
-
-Para fazer isso, digite este comando:
-
-```shell
-$ git credential-osxkeychain erase
-host={% data variables.command_line.codeblock %}
-protocol=https
-> [Pressione Return]
-```
-
-Se a ação for bem-sucedida, nada será impresso. Para testar se funcionou, experimente clonar um repositório do {% data variables.product.product_location %}. Se for solicitada uma senha, significa que a entrada de keychain foi excluída.
-
-### Leia mais
-
-- "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/using-git/caching-your-github-credentials-in-git/)"
diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository.md
deleted file mode 100644
index 7ba3908d5cfc..000000000000
--- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Exploring the dependencies and dependents of a repository
-intro: 'Using the dependency graph, you can see the packages your project depends on and the repositories that depend on it. In addition, you can see any vulnerabilities detected in its dependencies.'
-redirect_from:
- - /articles/listing-the-packages-that-a-repository-depends-on
- - /github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on
- - /articles/listing-the-projects-that-depend-on-a-repository
- - /github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### Viewing the dependency graph
-
-{% data reusables.repositories.enable-security-alerts %}
-
-The dependency graph has tabs that show the dependencies and dependents of your repository. For information about how these views are populated and which ecosystems are supported, see "[About the dependency graph](about-the-dependency-graph)."
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}
-4. Optionally, under "Dependency graph", click **Dependents**. ![Aba Dependents (Dependentes) na página dependency graph (gráfico de dependências)](/assets/images/help/graphs/dependency-graph-dependents-tab.png)
-
-#### Dependencies view
-
-Dependencies are grouped by ecosystem. You can expand a dependency to view its dependencies. For dependencies hosted on {% data variables.product.product_name %}, you can also click a dependency to view the repository. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}.
-
-![Gráfico de dependências](/assets/images/help/graphs/dependencies_graph.png)
-
-#### Dependents view
-
-For public repositories, the dependents view shows how the repository is used by other repositories. To show only the repositories that contain a library in a package manager, click **NUMBER Packages** immediately above the list of dependent repositories. The dependent counts are approximate and may not always match the dependents listed.
-
-![gráfico de dependentes](/assets/images/help/graphs/dependents_graph.png)
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Enabling and disabling the dependency graph for a private repository
-
-Repository administrators can enable or disable the dependency graph for private repositories.
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Read the message about granting {% data variables.product.product_name %} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**. !["Enable" button for the dependency graph](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the Security & analysis tab.
-{% endif %}
-
-### Solução de problemas para o gráfico de dependências
-
-If your dependency graph is empty, there may be a problem with the file containing your dependencies. Check the file to ensure that it's correctly formatted for the file type.
-
-{% if currentVersion == "free-pro-team@latest" %}
-If the file is correctly formatted, then check its size. The dependency graph ignores individual manifest and lock files that are over 0.5 Mb, unless you are a {% data variables.product.prodname_enterprise %} user. It processes up to 20 manifest or lock files per repository by default, so you can split dependencies into smaller files in subdirectories of the repository.{% endif %}
-
-If a manifest or lock file is not processed, its dependencies are omitted from the dependency graph and they can't be checked for vulnerable dependencies.
-
-### Leia mais
-
-- "[About the dependency graph](about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Visualizar informações da organização](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
-- "[Exibir e atualizar dependências vulneráveis no repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/github/understanding-how-github-uses-and-protects-your-data)"
-{% endif %}
diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on.md
deleted file mode 100644
index 4fd4ef35bf38..000000000000
--- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Listar os pacotes dos quais o repositório depende
-intro: 'No gráfico de dependências, você pode ver as dependências de seu projeto, assim como quaisquer vulnerabilidades detectadas.'
-redirect_from:
- - /articles/listing-the-packages-that-a-repository-depends-on
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### Sobre o gráfico de dependências
-
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that define dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
-
-{% data reusables.repositories.enable-security-alerts %}
-
-Você pode visualizar e atualizar dependências vulneráveis no gráfico de dependências do repositório. O gráfico de dependências lista dependências vulneráveis antes de outras dependências. Para obter mais informações, consulte "[Sobre alertas de segurança para dependências vulneráveis](/articles/about-security-alerts-for-vulnerable-dependencies)".
-
-{% if currentVersion == "free-pro-team@latest" %}
-Você pode visualizar as dependências usadas em repositórios da organização em um painel único. Para obter mais informações, consulte "[Visualizar informações na organização](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %}
-
-### Supported package ecosystems
-
-| Gerenciador de pacotes | Linguagem | Formatos recomendados | Formatos compatíveis |
-| ---------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- |
-| Maven | Java, Scala | `pom.xml` | `pom.xml` |
-| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
-| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
-| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* |
-| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`,`Gemfile`, `*.gemspec` |
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` |{% endif %}
-
-{% note %}
-
-**Observação:** se você listar suas dependências Python em um arquivo `setup.py`, pode não ser possível analisar, listar e alertar sobre cada dependência de seu projeto.
-
-{% endnote %}
-
-### Listar dependências em um repositório com gráfico de dependências habilitado
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Habilitar o gráfico de dependências em um repositório privado
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}
-4. Leia a mensagem sobre concessão de {% data variables.product.product_name %} acesso a dados de repositórios para habilitar o gráfico de dependências e depois clique em **Allow access** (Habilitar acesso). ![Botão para permitir acesso a dados do repositório para habilitar o gráfico de dependências](/assets/images/help/repository/dependency-graph-allow-access-button.png)
-
-Para obter mais informações, consulte "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/categories/understanding-how-github-uses-and-protects-your-data)".
-
-### Desabilitar o gráfico de dependências em um repositório privado
-
-{% data reusables.repositories.you-can-enable-or-disable-security-features %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. Em "Data services" (Serviços de dados), desmarque **Dependency graph** (Gráfico de dependências). ![Caixa de seleção para desabilitar o gráfico de dependências](/assets/images/help/repository/private-repo-data-use-dependency-graph-disabled.png)
-
-Para optar por recusar o uso de dados do repositório, consulte "[Aceitar ou recusar o uso de dados do repositório privado](/articles/opting-into-or-out-of-data-use-for-your-private-repository)".
-{% endif %}
-
-### Solução de problemas para o gráfico de dependências
-
-{% data reusables.repositories.troubleshooting-dependency-graph %}
-
-### Leia mais
-
-- "[Listar os projetos com dependências em um repositório](/articles/listing-the-projects-that-depend-on-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/categories/understanding-how-github-uses-and-protects-your-data)"
-- "[Exibir e atualizar dependências vulneráveis no repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% endif %}
diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository.md
deleted file mode 100644
index c43d4616adaa..000000000000
--- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Listar os projetos dependentes de um repositório
-intro: É possível visualizar pacotes e projetos que dependem de um repositório em um gráfico de dependentes.
-redirect_from:
- - /articles/listing-the-projects-that-depend-on-a-repository
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### Sobre o gráfico de dependentes
-O gráfico de dependentes contém dados de pacotes e aplicativos. Pacotes são repositórios que possuem uma biblioteca em um gerenciador de pacotes, enquanto aplicativos são repositórios que dependem do repositório selecionado. A lista de aplicativos no gráfico de dependentes é categorizada pelo projeto mais recente que depende de um repositório.
-
-O gráfico de dependentes contém dados para estas linguagens:
-
-- RubyGems
-- NPM
-- PyPI
-- Maven (somente pom.xml)
-- Nuget
-
-{% data reusables.repositories.enable-security-alerts %}
-
-{% note %}
-
-**Observação:** a contagem de dependentes é aproximada e pode não corresponder à lista de dependentes.
-
-{% endnote %}
-
-![gráfico de dependentes](/assets/images/help/graphs/dependents_graph.png)
-
-### Acessar o gráfico de dependentes
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}
-4. Em "Dependency graph" (Gráfico de dependências), clique em **Dependents** (Dependentes). ![Aba Dependents (Dependentes) na página dependency graph (gráfico de dependências)](/assets/images/help/graphs/dependency-graph-dependents-tab.png)
-
-### Leia mais
-
-- "[Listar os pacotes dos quais um repositório depende](/articles/listing-the-packages-that-a-repository-depends-on)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Visualizar informações da organização](/articles/viewing-insights-for-your-organization)"{% endif %}
diff --git a/translations/pt-BR/content/rest/reference/endpoints-available-for-github-apps.md b/translations/pt-BR/content/rest/reference/endpoints-available-for-github-apps.md
deleted file mode 100644
index 7444c977520a..000000000000
--- a/translations/pt-BR/content/rest/reference/endpoints-available-for-github-apps.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Endpoints available for GitHub Apps
-intro: Your app can make requests to the following REST endpoints.
-redirect_from:
- - /v3/apps/available-endpoints
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-You must use an installation access token to access endpoints using your {% data variables.product.prodname_github_app %}. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
-
-{% include rest_enabled_for_github_apps_in_current_version %}
diff --git a/translations/pt-BR/data/reusables/actions/actions-app-read-permissions-sh-org.md b/translations/pt-BR/data/reusables/actions/actions-app-read-permissions-sh-org.md
deleted file mode 100644
index 2a7ae651d6e5..000000000000
--- a/translations/pt-BR/data/reusables/actions/actions-app-read-permissions-sh-org.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s devem ter permissão da organização `self-hosted runners:read` para acessar o ponto final.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/actions-app-secrets-org-permissions.md b/translations/pt-BR/data/reusables/actions/actions-app-secrets-org-permissions.md
deleted file mode 100644
index cef21c50e488..000000000000
--- a/translations/pt-BR/data/reusables/actions/actions-app-secrets-org-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s devem ter permissão da organização `secrets` para acessar o ponto final.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/actions-app-secrets-permissions.md b/translations/pt-BR/data/reusables/actions/actions-app-secrets-permissions.md
deleted file mode 100644
index cda8c994f653..000000000000
--- a/translations/pt-BR/data/reusables/actions/actions-app-secrets-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s devem ter permissão da organização `secrets` para acessar o ponto de extremidade.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/actions-app-write-permissions-sh-org.md b/translations/pt-BR/data/reusables/actions/actions-app-write-permissions-sh-org.md
deleted file mode 100644
index 7e13e37d98e9..000000000000
--- a/translations/pt-BR/data/reusables/actions/actions-app-write-permissions-sh-org.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s devem ter permissão da organização `self-hosted runners:write` para utilizar este ponto de extremidade.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/actions-downloads.md b/translations/pt-BR/data/reusables/actions/actions-downloads.md
deleted file mode 100644
index e408dbdc760c..000000000000
--- a/translations/pt-BR/data/reusables/actions/actions-downloads.md
+++ /dev/null
@@ -1 +0,0 @@
-Chame este ponto de extremidade usando a bandeira `-v`, que permite a saída de verbose e permite que você veja a URL de download no cabeçalho. Para baixar o arquivo para o diretório de trabalho atual, especifique o nome do arquivo usando a bandeira `-o`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/actions-secret-encyption-examples.md b/translations/pt-BR/data/reusables/actions/actions-secret-encyption-examples.md
deleted file mode 100644
index 1fb937139bec..000000000000
--- a/translations/pt-BR/data/reusables/actions/actions-secret-encyption-examples.md
+++ /dev/null
@@ -1,73 +0,0 @@
-#### Exemplo de criptografia de um segredo usando Node.js
-
-Criptografe seu segredo usando a biblioteca [tweetsodium](https://github.com/github/tweetsodium).
-
-```js
-const sodium = require('tweetsodium');
-
-const key = "base64-encoded-public-key";
-const value = "plain-text-secret";
-
-// Converta a mensagem e a chave para Uint8Array's (Buffer implementa essa interface)
-const messageBytes = Buffer.from(value);
-const keyBytes = Buffer.from(key, 'base64');
-
-// Criptografe usando LibSodium.
-const encryptedBytes = sodium.seal(messageBytes, keyBytes);
-
-// Base64 o segredo criptografado
-const encrypted = Buffer.from(encryptedBytes).toString('base64');
-
-console.log(encrypted);
-```
-
-#### Exemplo de criptografar um segredo usando Python
-
-Criptografe seu segredo usando [pynacl](https://pynacl.readthedocs.io/en/stable/public/#nacl-public-sealedbox) com Python 3.
-
-```py
-from base64 import b64encode
-from nacl import encoding, public
-
-def encrypt(public_key: str, secret_value: str) -> str:
- """Encrypt a Unicode string using the public key."""
- const sodium = require('tweetsodium');
-
-const key = "base64-encoded-public-key";
-const value = "plain-text-secret";
-
-// Converta a mensagem e a chave para Uint8Array's (Buffer implementa essa interface)
-const messageBytes = Buffer.from(value);
-const keyBytes = Buffer.from(key, 'base64');
-
-// Criptografe usando LibSodium.
-```
-
-#### Exemplo de criptografar um segredo usando C\#
-
-Criptografe seu segredo usando o [Sodium. Core](https://www.nuget.org/packages/Sodium. Core/) package.
-
-```csharp
-var secretValue = System. Text. Encoding.UTF8. GetBytes("mySecret");
-var publicKey = Convert. FromBase64String("2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=");
-
-var sealedPublicKeyBox = Sodium. SealedPublicKeyBox. Create(secretValue, publicKey); Console. WriteLine(Convert. ToBase64String(sealedPublicKeyBox));
-```
-
-#### Example encrypting a secret using Ruby
-
-Criptografe seu segredo usando o gem [rbnacl](https://github.com/RubyCrypto/rbnacl).
-
-```ruby
-require "rbnacl"
-require "base64"
-
-key = Base64.decode64("+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=")
-public_key = RbNaCl::PublicKey.new(key)
-
-box = RbNaCl::Boxes::Sealed.from_public_key(public_key)
-encrypted_secret = box.encrypt("my_secret")
-
-# Print the base64 encoded secret
-puts Base64.strict_encode64(encrypted_secret)
-```
diff --git a/translations/pt-BR/data/reusables/actions/gh-app-actions-read-permissions.md b/translations/pt-BR/data/reusables/actions/gh-app-actions-read-permissions.md
deleted file mode 100644
index f5dbcc08e911..000000000000
--- a/translations/pt-BR/data/reusables/actions/gh-app-actions-read-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s deve ter permissão da `actions:read` para utilizar este ponto de extremidade.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/gh-app-actions-write-permissions.md b/translations/pt-BR/data/reusables/actions/gh-app-actions-write-permissions.md
deleted file mode 100644
index 38b4fde6144a..000000000000
--- a/translations/pt-BR/data/reusables/actions/gh-app-actions-write-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s deve ter permissão da `actions:write` para utilizar este ponto de extremidade.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/workflow-route-param-by-name.md b/translations/pt-BR/data/reusables/actions/workflow-route-param-by-name.md
deleted file mode 100644
index f8e16e923ba5..000000000000
--- a/translations/pt-BR/data/reusables/actions/workflow-route-param-by-name.md
+++ /dev/null
@@ -1 +0,0 @@
-Você também pode substituir `:workflow_id` com `:workflow_file_name`. Por exemplo, você poderia usar `main.yml`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/workflow-usage.md b/translations/pt-BR/data/reusables/actions/workflow-usage.md
deleted file mode 100644
index 9ef86059cb0c..000000000000
--- a/translations/pt-BR/data/reusables/actions/workflow-usage.md
+++ /dev/null
@@ -1 +0,0 @@
-Os minutos faturáveis só se aplicam aos fluxos de trabalho em repositórios privados que usam executores auto-hospedados do {% data variables.product.prodname_dotcom %}. O uso está listado para cada sistema operacional de executor hospedado {% data variables.product.prodname_dotcom %}- em milissegundos. Qualquer reexecução do trabalho também está incluída no uso. O uso não inclui o multiplicador para os executores do macOS e do Windows e não é arredondado para o minuto inteiro mais próximo. Para obter mais informações, consulte "[Managing billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/workflow_runs_parameters_table.md b/translations/pt-BR/data/reusables/actions/workflow_runs_parameters_table.md
deleted file mode 100644
index 2239e56ccd66..000000000000
--- a/translations/pt-BR/data/reusables/actions/workflow_runs_parameters_table.md
+++ /dev/null
@@ -1,8 +0,0 @@
-#### Parâmetros
-
-| Nome | Tipo | Descrição |
-| -------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `actor` | `string` | Retorna execuções no fluxo de trabalho de alguém. Use o login para o usuário que criou o `push` associado ao conjunto de verificação ou execução de fluxo de trabalho. |
-| `branch` | `string` | Retorna o fluxo de trabalho executado associado a um branch. Use o nome do branch do `push`. |
-| `event` | `string` | Retorna a execução do fluxo de trabalho acionada pelo evento especificado. Por exemeplo, `push`, `pull_request` ou `issue`. Para obter mais informações, consulte "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows)". |
-| `status` | `string` | Retorna fluxo de trabalho associado com o comando `status` ou `conclusion` que você especificar. Por exemplo, uma conclusão pode ser `success` ou um status pode ser `completed`. Para obter mais informações, consulte as opções de `status` e `conclusion` disponíveis em "[Create a check run](/v3/checks/runs/#create-a-check-run)." |
diff --git a/translations/pt-BR/data/reusables/apps/access_token_parameters_table_and_example.md b/translations/pt-BR/data/reusables/apps/access_token_parameters_table_and_example.md
deleted file mode 100644
index 8dc23849bf48..000000000000
--- a/translations/pt-BR/data/reusables/apps/access_token_parameters_table_and_example.md
+++ /dev/null
@@ -1,13 +0,0 @@
-#### Parâmetros
-
-| Nome | Tipo | Descrição |
-| -------------- | -------- | --------------------------------------------------------------- |
-| `access_token` | `string` | O token de acesso OAuth usado para autenticar na API do GitHub. |
-
-#### Exemplo
-
-```json
-{
- "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a"
-}
-```
diff --git a/translations/pt-BR/data/reusables/apps/app_req_account_deletion.md b/translations/pt-BR/data/reusables/apps/app_req_account_deletion.md
deleted file mode 100644
index f1054caa471f..000000000000
--- a/translations/pt-BR/data/reusables/apps/app_req_account_deletion.md
+++ /dev/null
@@ -1 +0,0 @@
-Os aplicativos devem fornecer aos clientes uma forma de excluir sua conta, sem ter que enviar um e-mail ou ligar para uma pessoa de suporte.
diff --git a/translations/pt-BR/data/reusables/apps/authenticated_user_access.md b/translations/pt-BR/data/reusables/apps/authenticated_user_access.md
deleted file mode 100644
index 26aeae031d58..000000000000
--- a/translations/pt-BR/data/reusables/apps/authenticated_user_access.md
+++ /dev/null
@@ -1 +0,0 @@
-O usuário autenticado tem permissão explícita para acessar os repositórios que eles possuem, repositórios onde são colaboradores e repositórios que podem acessar por meio de uma associação à organização.
diff --git a/translations/pt-BR/data/reusables/apps/authorizations_oauth_tokens_SAML.md b/translations/pt-BR/data/reusables/apps/authorizations_oauth_tokens_SAML.md
deleted file mode 100644
index 44025507ab50..000000000000
--- a/translations/pt-BR/data/reusables/apps/authorizations_oauth_tokens_SAML.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
-{% warning %}
-
-**Warning:** Aplicativos devem usar [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para obter tokens OAuth que funcionam com as organizações do GitHub SAML. Os tokens OAuth criados usando a API de Autorizações não poderão acessar as organizações de GitHub SAML. Para obter mais informações, consulte [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/apps/deprecating_applications_api_endpoints.md b/translations/pt-BR/data/reusables/apps/deprecating_applications_api_endpoints.md
deleted file mode 100644
index 5140abe6fc6b..000000000000
--- a/translations/pt-BR/data/reusables/apps/deprecating_applications_api_endpoints.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-{% warning %}
-
-**Aviso de método obsoleto:** {% data variables.product.prodname_dotcom %} irá substituir e descontinuar os pontos de extremidade OAuth contendo `access_token` no parâmetro de caminho. Estamos introduzindo novos pontos de extremidade que permitem gerenciar de forma segura os tokens dos aplicativos OAuth usando `access_token` como um parâmetro de entrada.{% if currentVersion == "free-pro-team@latest" %} O aplicativo OAuth API será removido em 5 de maio, 2021.{% endif %} Para mais informações,{% if currentVersion == "free-pro-team@latest" %} incluindo brownouts programados,{% endif %} ver a [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).
-
-{% if currentVersion != "free-pro-team@latest" %} Pontos de extremidade usando um `access_token` no parâmetro de caminho estão atualmente disponíveis e ainda não estão obsoletos no {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} anunciará a depreciação e fornecerá um aviso antecipadamente antes de remover o suporte para este recurso.{% endif %}
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/apps/deprecating_github_services_ghe_compact.md b/translations/pt-BR/data/reusables/apps/deprecating_github_services_ghe_compact.md
deleted file mode 100644
index 32579167b85a..000000000000
--- a/translations/pt-BR/data/reusables/apps/deprecating_github_services_ghe_compact.md
+++ /dev/null
@@ -1 +0,0 @@
-A versão 2.17 ou superior do GitHub Enterprise não permite mais que os administradores instalem Serviços GitHub. Consulte o [Replacing GitHub Services guide](/v3/guides/replacing-github-services) para obter detalhes.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/apps/deprecating_oauth_authorizations.md b/translations/pt-BR/data/reusables/apps/deprecating_oauth_authorizations.md
deleted file mode 100644
index 43321b063a66..000000000000
--- a/translations/pt-BR/data/reusables/apps/deprecating_oauth_authorizations.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-{% warning %}
-
-**Aviso de Depreciação:** {% data variables.product.prodname_dotcom %} irá cancelar a API de Autorizações OAuth, que é usado por integrações para criar tokens de acesso pessoais e tokens OAuth, e agora você deve criar esses tokens usando nosso fluxo [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow).{% if currentVersion == "free-pro-team@latest" %} A API de Autorizações OAuth será removida em 13 de Novembro 2020.{% endif %} Para mais informações,{% if currentVersion == "free-pro-team@latest" %} incluindo brownouts agendados{% endif %} veja a postagem [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).
-
-{% if currentVersion != "free-pro-team@latest" %} A API de Autorizações OAuth está disponível e ainda não está obsoleta no {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} anunciará a depreciação e fornecerá um aviso antecipadamente antes de remover o suporte para este recurso.{% endif %}
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/apps/iat_required.md b/translations/pt-BR/data/reusables/apps/iat_required.md
deleted file mode 100644
index a36e02971816..000000000000
--- a/translations/pt-BR/data/reusables/apps/iat_required.md
+++ /dev/null
@@ -1 +0,0 @@
-Você deve usar um [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) para acessar este ponto de extremidade.
diff --git a/translations/pt-BR/data/reusables/apps/iat_required_multiple_endpoints.md b/translations/pt-BR/data/reusables/apps/iat_required_multiple_endpoints.md
deleted file mode 100644
index 30be3a082d98..000000000000
--- a/translations/pt-BR/data/reusables/apps/iat_required_multiple_endpoints.md
+++ /dev/null
@@ -1 +0,0 @@
-Você deve usar um [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) para acessar estes pontos de extremidade.
diff --git a/translations/pt-BR/data/reusables/apps/jwt_or_client_secret_required.md b/translations/pt-BR/data/reusables/apps/jwt_or_client_secret_required.md
deleted file mode 100644
index c055bebb6b00..000000000000
--- a/translations/pt-BR/data/reusables/apps/jwt_or_client_secret_required.md
+++ /dev/null
@@ -1 +0,0 @@
-GitHub Apps devem usar um [JWT](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) para acessar este ponto de extremidade. Os aplicativos OAuth devem usar [basic authentication](/v3/auth/#basic-authentication) com o ID do cliente e o segredo do cliente para acessar este ponto de extremidade.
diff --git a/translations/pt-BR/data/reusables/apps/jwt_required.md b/translations/pt-BR/data/reusables/apps/jwt_required.md
deleted file mode 100644
index e8c9abc48e06..000000000000
--- a/translations/pt-BR/data/reusables/apps/jwt_required.md
+++ /dev/null
@@ -1 +0,0 @@
-Você deve usar um [JWT](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) para acessar este ponto de extremidade.
diff --git a/translations/pt-BR/data/reusables/apps/null-headbranch.md b/translations/pt-BR/data/reusables/apps/null-headbranch.md
deleted file mode 100644
index d303803f5947..000000000000
--- a/translations/pt-BR/data/reusables/apps/null-headbranch.md
+++ /dev/null
@@ -1 +0,0 @@
-A API de verificação procura apenas por pushes no repositório onde o conjunto de verificação ou a execução de verificação foram criados. Pushes para um branch em um repositório bifurcado não foi detectado e retorna um array `pull_requests` vazio e um valor `null` para `head_branch`.
diff --git a/translations/pt-BR/data/reusables/apps/pat_or_ba_required.md b/translations/pt-BR/data/reusables/apps/pat_or_ba_required.md
deleted file mode 100644
index 868f8993bb48..000000000000
--- a/translations/pt-BR/data/reusables/apps/pat_or_ba_required.md
+++ /dev/null
@@ -1 +0,0 @@
-Você deve usar um token de acesso pessoal (que pode criar através da [command line](/articles/creating-a-personal-access-token-for-the-command-line/) ou da [OAuth Authorizations API](/v3/oauth_authorizations/#create-a-new-authorization)) ou [Basic Authentication](/v3/auth/#basic-authentication) para acessar este ponto de extremidade.
diff --git a/translations/pt-BR/data/reusables/apps/u2s_required.md b/translations/pt-BR/data/reusables/apps/u2s_required.md
deleted file mode 100644
index 45dca0108a81..000000000000
--- a/translations/pt-BR/data/reusables/apps/u2s_required.md
+++ /dev/null
@@ -1 +0,0 @@
-Você deve usar um [user-to-server OAuth access token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site), criado para um usuário que autorizou seu GitHub App, para acessar este ponto de extremidade.
diff --git a/translations/pt-BR/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-runs.md b/translations/pt-BR/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-runs.md
deleted file mode 100644
index b9b3be3a368a..000000000000
--- a/translations/pt-BR/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-runs.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Nota:** A API Checks procura apenas por pushes no repositório onde o conjunto de verificação ou execução de verificação foram criadas. Pushes para uma branch em um repositório bifurcado não são detectadas e retorna uma array vazia `pull_requests`.
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/blog/affected_users.md b/translations/pt-BR/data/reusables/blog/affected_users.md
deleted file mode 100644
index 37241b0dacbe..000000000000
--- a/translations/pt-BR/data/reusables/blog/affected_users.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Nota**: Esta atualização afeta apenas os usuários do GitHub.com e futuras versões do GitHub Enterprise.
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/branches/apps-permissions.md b/translations/pt-BR/data/reusables/branches/apps-permissions.md
deleted file mode 100644
index 9513614f287a..000000000000
--- a/translations/pt-BR/data/reusables/branches/apps-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}apenas {% data variables.product.prodname_github_app %}s instalados com acesso de `write` à permissão `contents` podem ser adicionados como atores autorizados em uma branch protegida.{% endif %}
diff --git a/translations/pt-BR/data/reusables/branches/limits.md b/translations/pt-BR/data/reusables/branches/limits.md
deleted file mode 100644
index da06e0ed5ec5..000000000000
--- a/translations/pt-BR/data/reusables/branches/limits.md
+++ /dev/null
@@ -1 +0,0 @@
-**Nota**: A lista de usuários{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, aplicativos,{% endif %} e equipes no total é limitada a 100 itens.
diff --git a/translations/pt-BR/data/reusables/branches/rename-existing-branch.md b/translations/pt-BR/data/reusables/branches/rename-existing-branch.md
deleted file mode 100644
index 174a317ddc65..000000000000
--- a/translations/pt-BR/data/reusables/branches/rename-existing-branch.md
+++ /dev/null
@@ -1,3 +0,0 @@
-While you can rename your repository's existing default branch, {% data variables.product.company_short %} plans to provide tools to simplify the process of renaming the default branch. For more information on these plans, see [`github/renaming`](https://github.com/github/renaming).
-
-If you have already renamed the default branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion ver_gt "enterprise-server@2.22" %} {% data variables.product.product_location_enterprise %}{% else %}{% data variables.product.prodname_dotcom_the_website %}{% endif %} that contain a deleted `master` branch name to the equivalent link on the repository's default branch.
diff --git a/translations/pt-BR/data/reusables/checks/conclusion_values.md b/translations/pt-BR/data/reusables/checks/conclusion_values.md
deleted file mode 100644
index 0ff5afef5393..000000000000
--- a/translations/pt-BR/data/reusables/checks/conclusion_values.md
+++ /dev/null
@@ -1 +0,0 @@
-**Obrigatório de você fornecer `completed_at` ou um `status` de `completed`**. A conclusão final da verificação. Pode ser um dos `success`, `failure`, `neutral`, `cancelled`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}`skipped`, {% endif %}`timed_out`, ou `action_required`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/checks/requested_actions.md b/translations/pt-BR/data/reusables/checks/requested_actions.md
deleted file mode 100644
index a49c4f98a4e8..000000000000
--- a/translations/pt-BR/data/reusables/checks/requested_actions.md
+++ /dev/null
@@ -1 +0,0 @@
-Para saber mais sobre verificações realizadas e ações solicitadas, consulte "[Check runs and requested actions](/v3/checks/runs/#check-runs-and-requested-actions)."
diff --git a/translations/pt-BR/data/reusables/cli/beta.md b/translations/pt-BR/data/reusables/cli/beta.md
deleted file mode 100644
index 1343ae7748a1..000000000000
--- a/translations/pt-BR/data/reusables/cli/beta.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_cli %} está atualmente em beta e está sujeito a alterações.
diff --git a/translations/pt-BR/data/reusables/collaborators/collaborator-definition.md b/translations/pt-BR/data/reusables/collaborators/collaborator-definition.md
deleted file mode 100644
index 7b8183d0e594..000000000000
--- a/translations/pt-BR/data/reusables/collaborators/collaborator-definition.md
+++ /dev/null
@@ -1 +0,0 @@
-a lista de colaboradores inclui colaboradores externos, membros da organização que são colaboradores diretos, integrantes da organização com acesso por meio de associações de equipe, integrantes da organização com acesso por meio das permissões padrão da organização e proprietários da organização.
diff --git a/translations/pt-BR/data/reusables/command_line/parameters_filters.md b/translations/pt-BR/data/reusables/command_line/parameters_filters.md
deleted file mode 100644
index 818d62791c54..000000000000
--- a/translations/pt-BR/data/reusables/command_line/parameters_filters.md
+++ /dev/null
@@ -1 +0,0 @@
-Você pode usar parâmetros para restringir a lista de resultados. Para obter mais informações sobre o uso de parâmetros, consulte [Parameters](/v3/#parameters).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/commits/verification-object-definition.md b/translations/pt-BR/data/reusables/commits/verification-object-definition.md
deleted file mode 100644
index ea06a763fcc2..000000000000
--- a/translations/pt-BR/data/reusables/commits/verification-object-definition.md
+++ /dev/null
@@ -1,28 +0,0 @@
-##### Verificação de assinatura para objetos
-
-A resposta incluirá um objeto de `verification` que descreve o resultado de verificar a assinatura do commit. Os seguintes campos estão incluídos no objeto `verification`:
-
-| Nome | Tipo | Descrição |
-| ------------ | --------- | ---------------------------------------------------------------------------------------------------- |
-| `verificado` | `boolean` | Indica se o GitHub considera verificada a assinatura neste commit. |
-| `motivo` | `string` | O motivo do valor `verified`. Possíveis valores e seus significados são enumerados na tabela abaixo. |
-| `assinatura` | `string` | A assinatura que foi extraída do commit. |
-| `carga` | `string` | O valor que foi assinado. |
-
-Estes são os possíveis valores para `reason` no objeto `verification`:
-
-| Valor | Descrição |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
-| `expired_key` | A chave que fez a assinatura está expirada. |
-| `not_signing_key` | A bandeira "assinar" não está entre as bandeiras de uso na chave GPG que fez a assinatura. |
-| `gpgverify_error` | Ocorreu um erro ao se comunicar com o serviço de verificação de assinaturas. |
-| `gpgverify_unavailable` | O serviço de verificação de assinatura está indisponível no momento. |
-| `não assinado` | O objeto não inclui uma assinatura. |
-| `unknown_signature_type` | Uma assinatura não PGP foi encontrada no commit. |
-| `no_user` | Nenhum usuário foi associado ao endereço de e-mail `committer` no commit. |
-| `unverified_email` | O endereço de e-mail `committer` no commit foi associado a um usuário, mas o endereço de e-mail não é verificado na sua conta. |
-| `bad_email` | O endereço de e-mail `committer` do commit não está incluído nas identidades da chave PGP que fez a assinatura. |
-| `unknown_key` | A chave que fez a assinatura não foi registrada com a conta de nenhum usuário. |
-| `malformed_signature` | Ocorreu um erro ao analisar a assinatura. |
-| `invalid` | A assinatura não pôde ser verificada criptograficamente usando a chave cuja key-id foi encontrada na assinatura. |
-| `valid` | Nenhum dos erros acima aplicados, por isso a assinatura é considerada verificada. |
diff --git a/translations/pt-BR/data/reusables/desktop/commit-history-list.md b/translations/pt-BR/data/reusables/desktop/commit-history-list.md
deleted file mode 100644
index 8b6c93208e45..000000000000
--- a/translations/pt-BR/data/reusables/desktop/commit-history-list.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Na lista do histórico de commit, clique no commit que deseja reverter.
diff --git a/translations/pt-BR/data/reusables/desktop/enter-2fa-in-browser.md b/translations/pt-BR/data/reusables/desktop/enter-2fa-in-browser.md
deleted file mode 100644
index 3a0be4f0521f..000000000000
--- a/translations/pt-BR/data/reusables/desktop/enter-2fa-in-browser.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Retorne ao {% data variables.product.prodname_dotcom %}. No prompt, insira seu código 2FA e clique em **Verify** (Verificar). ![Campo de autenticação do código 2FA](/assets/images/help/desktop/2fa-code-field.png)
diff --git a/translations/pt-BR/data/reusables/desktop/retrieve-2fa-in-browser.md b/translations/pt-BR/data/reusables/desktop/retrieve-2fa-in-browser.md
deleted file mode 100644
index 8e78237da2d9..000000000000
--- a/translations/pt-BR/data/reusables/desktop/retrieve-2fa-in-browser.md
+++ /dev/null
@@ -1,3 +0,0 @@
-1. Se você configurou a autenticação de dois fatores no {% data variables.product.prodname_dotcom %}, execute uma das seguintes opções:
- - Se você configurou a 2FA via SMS, recupere seu código 2FA na mensagem SMS.
- - Se você configurou a 2FA com um aplicativo TOTP, gere um código 2FA.
diff --git a/translations/pt-BR/data/reusables/desktop/windows-select-file-menu.md b/translations/pt-BR/data/reusables/desktop/windows-select-file-menu.md
deleted file mode 100644
index 07711d6aea03..000000000000
--- a/translations/pt-BR/data/reusables/desktop/windows-select-file-menu.md
+++ /dev/null
@@ -1 +0,0 @@
-1. No canto superior esquerdo da janela, selecione o menu **File** (Arquivo). ![Menu do {% data variables.product.prodname_desktop %} na barra de menu do Windows](/assets/images/help/desktop/windows-select-file-menu.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/cost-management-tab.md b/translations/pt-BR/data/reusables/dotcom_billing/cost-management-tab.md
deleted file mode 100644
index c5aea0fce18b..000000000000
--- a/translations/pt-BR/data/reusables/dotcom_billing/cost-management-tab.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Em "Billing" (Faturamento), clique em **Cost management** (Gestão de Custos). ![Aba de gestão de custos](/assets/images/help/settings/cost-management-tab.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/publishing-nodejs-packages.md b/translations/pt-BR/data/reusables/dotcom_billing/publishing-nodejs-packages.md
deleted file mode 100644
index bb3e7c3a0b82..000000000000
--- a/translations/pt-BR/data/reusables/dotcom_billing/publishing-nodejs-packages.md
+++ /dev/null
@@ -1,203 +0,0 @@
----
-title: Publicar pacotes do Node.js
-intro: Você pode publicar pacotes do Node.js em um registro como parte do seu fluxo de trabalho de integração contínua (CI).
-product: '{% data reusables.gated-features.actions %}'
-productVersions:
- dotcom: '*'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
----
-
-### Introdução
-
-Este guia mostra como criar um fluxo de trabalho que publica pacotes do Node.js em {% data variables.product.prodname_registry %} e nos registros npm após os testes de integração contínua (CI) serem aprovados. Com um único fluxo de trabalho, você pode publicar pacotes em um único registro ou em vários registros.
-
-### Pré-requisitos
-
-Recomendamos que você tenha um entendimento básico das opções de configuração do fluxo de trabalho e de como criar um arquivo do fluxo de trabalho. Para obter mais informações, consulte "[Configurar fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)."
-
-Para obter mais informações sobre a criação de um fluxo de trabalho de CI para seu projeto Node.js, consulte "[Usando Node.js com {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)".
-
-Você também pode achar útil ter um entendimento básico do seguinte:
-
-- "[Conceitos básicos para{% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[Configurar o npm para uso com o {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
-- "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-- "[Criar e usar segredos criptografados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)"
-- "[Autenticando com o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)"
-
-### Sobre a configuração do pacote
-
- Os campos `nome` e `versão` no arquivo *package.json* cria um identificador único que os registros usam para vincular seu pacote a um registro. Você pode adicionar um resumo para página de listagem do pacote ao incluir um campo `descrição` no arquivo *package.json*. Para obter mais informações, consulte "[Criando um pacote package.json](https://docs.npmjs.com/creating-a-package-json-file)" e "[Criando módulos Node.js](https://docs.npmjs.com/creating-node-js-modules)" na documentação do npm.
-
-Quando um arquivo *.npmrc* local existe e tem um valor de `registro` especificado, o comando `publicação do npm` usa o registro configurado no arquivo *.npmrc*. {% data reusables.github-actions.setup-node-intro %}
-
-Você pode especificar a versão do Node.js instalada no executor usando a ação `setup-node`.
-
-Se você adicionar etapas ao seu fluxo de trabalho para configurar os campos `publishConfig` no seu arquivo *package.json*, você não precisará especificar o registry-url usando a ação de `setup-node`. No entanto, você estará limitado à publicação do pacote em um registro. Para obter mais informações, consulte "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" na documentação npm.
-
-### Publicar pacotes no registro npm
-
-Cada vez que você criar uma nova versão, você poderá acionar um fluxo de trabalho para publicar o seu pacote. O fluxo de trabalho no exemplo abaixo é executado quando o evento `versão` é acionado com o tipo `criado`. O fluxo de trabalho publica o pacote no registro npm se o teste de CI for aprovado.
-
-Para executar operações autenticadas com o registro npm em seu fluxo de trabalho, você deverá armazenar seu token de autenticação npm como um segredo nas configurações do repositório. Por exemplo, crie um segredo denominado `NPM_TOKEN`. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
-
-Por padrão, o npm usa o campo `nome` do arquivo *package.json* para determinar o registro do npm. Ao publicar em um namespace global, você precisa incluir apenas o nome do pacote. Por exemplo, você publicaria um pacote denominado `npm-hello-world-test` em `https://www.npmjs.com/package/npm-hello-world-test`.
-
-Se você estiver publicando um pacote que inclui um prefixo de escopo, inclua o escopo no nome do arquivo *package.json*. Por exemplo, se o prefixo de escopo do npm é octocat e o nome do pacote é hello-world, o `nome` no seu arquivo *package.json* deverá ser `@octocat/hello-world`. Se seu pacote npm usar um prefixo de escopo e for público, você deverá usar a opção `npm publish --access public`. Essa é uma opção que o npm requer para impedir que alguém publique um pacote privado de forma não intencional.
-
-Este exemplo armazena o segredo `NPM_TOKEN` na variável de ambiente `NODE_AUTH_TOKEN`. Quando a ação `setup-node` cria um arquivo *.npmrc*, ela faz referência ao token da variável de ambiente `NODE_AUTH_TOKEN`.
-
-{% raw %}
-```yaml
-nome: Pacote Node.js
-em:
- versão:
- tipos: [created]
-trabalhos:
- criar:
- runs-on: ubuntu-latest
- etapas:
- - usa: actions/checkout@v2
- # Configura o arquivo .npmrc a ser publicado no npm
- - usa: actions/setup-node@v1
- com:
- node-version: '12.x'
- registry-url: 'https://registry.npmjs.org'
- - executar: npm install
- - executar: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-```
-{% endraw %}
-
-No exemplo acima, a ação `setup-node` cria um arquivo *.npmrc* no executor com o conteúdo a seguir:
-
-```
-//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
-registry=https://registry.npmjs.org/
-always-auth=true
-```
-
-### Publicar pacotes em {% data variables.product.prodname_registry %}
-
-Cada vez que você criar uma nova versão, você poderá acionar um fluxo de trabalho para publicar o seu pacote. O fluxo de trabalho no exemplo abaixo é executado sempre que ocorre o evento `versão` com o tipo `criado`. O fluxo de trabalho publica o pacote em {% data variables.product.prodname_registry %} se o teste de CI for aprovado.
-
-Por padrão, o {% data variables.product.prodname_registry %} publica um pacote no repositório {% data variables.product.prodname_dotcom %} que você especificar no campo `nome` do arquivo *package.json*. Por exemplo, você publicaria um pacote denominado `@my-org/test` no repositório `my-org/test` do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte [`npm-scope`](https://docs.npmjs.com/misc/scope) na documentação do npm.
-
-Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. O `GITHUB_TOKEN` existe no repositório por padrão e tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
-
-Este exemplo armazena o segredo `GITHUB_TOKEN` na variável de ambiente `NODE_AUTH_TOKEN`. Quando a ação `setup-node` cria um arquivo *.npmrc*, ela faz referência ao token da variável de ambiente `NODE_AUTH_TOKEN`.
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # Setup .npmrc file to publish to GitHub Packages
- - uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- registry-url: 'https://npm.pkg.github.com'
- scope: '@octocat' # Defaults to the user or organization that owns the workflow file
- - run: npm install
- - run: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
-
-A ação `setup-node` cria um arquivo *.npmrc* no executor. Ao usar a entrada do `escopo` para a ação `setup-node`, o arquivo *.npmrc* incluirá o prefixo do escopo. Por padrão, a ação `setup-node` define o escopo no arquivo *.npmrc* na conta que contém esse arquivo do fluxo de trabalho.
-
-```
-//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
-@octocat:registry=https://npm.pkg.github.com
-always-auth=true
-```
-
-### Publicar pacotes usando o yarn
-
-Se você usar o gerenciador de pacotes Yarn, você poderá instalar e publicar pacotes usando o Yarn.
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # Setup .npmrc file to publish to npm
- - uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- registry-url: 'https://registry.npmjs.org'
- scope: '@octocat' # Defaults to the user or organization that owns the workflow file
- - run: yarn
- - run: yarn publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-```
-{% endraw %}
-
-### Publicar pacotes no npm e em {% data variables.product.prodname_registry %}
-
-{% note %}
-
-**Nota:** Se você precisar publicar para registros que têm diferentes prefixos de escopo, você deverá modificar o arquivo *package.json* no executor para alterar o prefixo de escopo. Por exemplo, se você publicar um pacote no escopo `@mona` para o npm e para o escopo `@octocat` para {% data variables.product.prodname_registry %}, você poderá substituir o escopo `@mona` por `@octocat` no arquivo *package.json* no executor, após fazer a publicação no npm e antes de publicar em {% data variables.product.prodname_registry %}.
-
-{% endnote %}
-
-Você pode publicar seus pacotes no registro do npm e em {% data variables.product.prodname_registry %}, usando a ação de `setup-node` para cada registro.
-
-Se você publicar um pacote em ambos os registros, você deverá garantir que seu prefixo de escopo no npm corresponda ao nome do usuário ou da organização do {% data variables.product.prodname_dotcom %}. Para publicar pacotes em um registro público com um prefixo de escopo, você pode usar o comando `npm publish --access public`. Para obter mais informações, consulte [`npm-scope`](https://docs.npmjs.com/misc/scope) e "[Criar e publicar pacotes públicos com escopos](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)" na documentação do npm.
-
-Certifique-se de que seu arquivo *package.json* inclua o escopo do seu repositório {% data variables.product.prodname_dotcom %} e o registro npm. Por exemplo, se você planeja publicar um pacote no repositório `octocat/npm-hello-world-test` em {% data variables.product.prodname_dotcom %} e em https://www.npmjs. om/package/@octocat/npm-hello-world-test, o nome no arquivo do seu *package.json* seria `"name": "@octocat/npm-hello-world-test"`.
-
-Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. O `GITHUB_TOKEN` existe no repositório por padrão e tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
-
-Ao usar a entrada do `escopo` para a ação `setup-node`, esta cria um arquivo *.npmrc* que inclui o prefixo do escopo. Por padrão, a ação `setup-node` define o escopo no arquivo *.npmrc* para o usuário ou organização proprietário do arquivo do fluxo de trabalho.
-
-Este fluxo de trabalho chama a ação `setup-node` duas vezes. Cada vez que a ação `setup-node` é executada, ela substitui o arquivo *.npmrc*. O arquivo *.npmrc* faz referência ao token que permite que você execute operações autenticadas com o registro do pacote a partir da variável de ambiente `NODE_AUTH_TOKEN`. O fluxo de trabalho define a variável de ambiente `NODE_AUTH_TOKEN` toda vez que o comando `publicação do npm` é executado. Primeiro com um token para publicar no npm (`NPM_TOKEN`) e, em seguida, com um token para publicar em {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`).
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # Setup .npmrc file to publish to npm
- - uses: actions/setup-node@v1
- with:
- node-version: '10.x'
- registry-url: 'https://registry.npmjs.org'
- - run: npm install
- # Publish to npm
- - run: npm publish --access public
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
- # Setup .npmrc file to publish to GitHub Packages
- - uses: actions/setup-node@v1
- with:
- registry-url: 'https://npm.pkg.github.com'
- scope: '@octocat' # Defaults to the user or organization that owns the workflow file
- # Publish to GitHub Packages
- - run: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/business-settings.md b/translations/pt-BR/data/reusables/enterprise-accounts/business-settings.md
deleted file mode 100644
index b4cf521f28f4..000000000000
--- a/translations/pt-BR/data/reusables/enterprise-accounts/business-settings.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Sob o nome da sua conta, clique em {% octicon "gear" aria-label="The Settings gear" %} **Settings**. ![Aba de configurações na página do perfil da empresa](/assets/images/help/business-accounts/business-account-settings-tab.png)
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/github-dotcom-connection-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/github-dotcom-connection-tab.md
deleted file mode 100644
index 24c64a38d7fc..000000000000
--- a/translations/pt-BR/data/reusables/enterprise-accounts/github-dotcom-connection-tab.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Na barra lateral esquerda, clique em **{% data variables.product.prodname_dotcom_the_website %} connection**. ![Aba de conexão GitHub.com na barra lateral de configurações da conta de negócios](/assets/images/enterprise/business-accounts/settings-github-dotcom-connection-tab.png)
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/member-privileges-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/member-privileges-tab.md
deleted file mode 100644
index 37e5b8632c64..000000000000
--- a/translations/pt-BR/data/reusables/enterprise-accounts/member-privileges-tab.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Na barra lateral de configurações de negócios, clique em **Member privileges** (privilégios de membros). ![Aba de privilégios de membro na barra lateral de configurações da conta empresarial](/assets/images/help/business-accounts/settings-member-privileges-tab.png)
diff --git a/translations/pt-BR/data/reusables/enterprise/ldap_sync_warning.md b/translations/pt-BR/data/reusables/enterprise/ldap_sync_warning.md
deleted file mode 100644
index 068c060a16f1..000000000000
--- a/translations/pt-BR/data/reusables/enterprise/ldap_sync_warning.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" %}
-
-{% warning %}
-
-Se sua instância do {% data variables.product.prodname_ghe_server %} tiver [LDAP Sync enabled and the option to synchronize emails enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync), esta API está desativada e retornará uma resposta `403`. Os usuários gerenciados no LDAP não poderão adicionar ou excluir um endereço de e-mail através da API com estas opções ativadas.
-
-{% endwarning %}
-
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/enterprise_enterprise_support/sign-in-to-enterprise-portal.md b/translations/pt-BR/data/reusables/enterprise_enterprise_support/sign-in-to-enterprise-portal.md
deleted file mode 100644
index d951b25921a2..000000000000
--- a/translations/pt-BR/data/reusables/enterprise_enterprise_support/sign-in-to-enterprise-portal.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Para entrar no portal de suporte {% data variables.contact.enterprise_portal %}, clique no canto superior direito da página em **Sign in**. ![Entre no {% data variables.contact.enterprise_portal %}](/assets/images/enterprise/support/sign-in-support-portal.png)
diff --git a/translations/pt-BR/data/reusables/enterprise_installation/increasing-cpus-max.md b/translations/pt-BR/data/reusables/enterprise_installation/increasing-cpus-max.md
deleted file mode 100644
index 0a0ebadd59cc..000000000000
--- a/translations/pt-BR/data/reusables/enterprise_installation/increasing-cpus-max.md
+++ /dev/null
@@ -1,3 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" %}
- {% data reusables.enterprise_installation.increasing-cpus-req %} Quando você usa mais de 16 CPUs, você não precisa adicionar 6.5 GB de memória para cada CPU, mas você deve monitorar sua instância para garantir que ela tenha memória suficiente.
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/enterprise_installation/resizing-root-disk.md b/translations/pt-BR/data/reusables/enterprise_installation/resizing-root-disk.md
deleted file mode 100644
index 042f68a1a65d..000000000000
--- a/translations/pt-BR/data/reusables/enterprise_installation/resizing-root-disk.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Nota:** O disco raiz pode ser redimensionado construindo um novo appliance ou usando um appliance existente. Para obter mais informações, consulte "[Increasing storage capacity](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity)."
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/enterprise_installation/root-and-data-disk-requirement.md b/translations/pt-BR/data/reusables/enterprise_installation/root-and-data-disk-requirement.md
deleted file mode 100644
index 52a3179148cc..000000000000
--- a/translations/pt-BR/data/reusables/enterprise_installation/root-and-data-disk-requirement.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_ghe_server %} requer um disco de dados persistente separado do disco raiz. Para obter mais informações, consulte "[System overview](/enterprise/admin/guides/installation/system-overview)."
diff --git a/translations/pt-BR/data/reusables/enterprise_installation/storage-disk-requirements.md b/translations/pt-BR/data/reusables/enterprise_installation/storage-disk-requirements.md
deleted file mode 100644
index ba0a45103b4c..000000000000
--- a/translations/pt-BR/data/reusables/enterprise_installation/storage-disk-requirements.md
+++ /dev/null
@@ -1 +0,0 @@
-Para seu dispositivos de armazenamento, recomendamos um SSD de alto desempenho seja anexado diretamente ou de uma rede de área de armazenamento (SAN).
diff --git a/translations/pt-BR/data/reusables/enterprise_installation/warning-on-polling.md b/translations/pt-BR/data/reusables/enterprise_installation/warning-on-polling.md
deleted file mode 100644
index a144d6e3f0b2..000000000000
--- a/translations/pt-BR/data/reusables/enterprise_installation/warning-on-polling.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% warning %}
-
-**Aviso:** Recomendamos que você use webhooks para buscar alterações de repositório para integração contínua (CI) ou sistemas similares. Verificações automáticas regulares, ou *polling*, reduzirão significativamente a escalabilidade de sua instância. Para obter mais informações, consulte "[Sobre webhooks](/enterprise/{{ currentVersion }}/user/articles/about-webhooks/)"
-
-{% endwarning %}
diff --git a/translations/pt-BR/data/reusables/gated-features/actions-api-gated.md b/translations/pt-BR/data/reusables/gated-features/actions-api-gated.md
deleted file mode 100644
index d19eef95d824..000000000000
--- a/translations/pt-BR/data/reusables/gated-features/actions-api-gated.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-
-{% data variables.product.prodname_actions %} está disponível com {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizações, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_one %}. O {% data variables.product.prodname_actions %} não está disponível para repositórios privados de contas que utilizam planos antigos por-repositório. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %}
-
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/gated-features/credential-authorizations-org.md b/translations/pt-BR/data/reusables/gated-features/credential-authorizations-org.md
deleted file mode 100644
index a0a9f2845771..000000000000
--- a/translations/pt-BR/data/reusables/gated-features/credential-authorizations-org.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-
-Listar e excluir autorizações de credenciais está disponível para organizações com {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
-
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/gated-features/draft-pull-requests.md b/translations/pt-BR/data/reusables/gated-features/draft-pull-requests.md
deleted file mode 100644
index 5cd6677339d4..000000000000
--- a/translations/pt-BR/data/reusables/gated-features/draft-pull-requests.md
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Pull requests de rascunho estão disponíveis em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações, {% data variables.product.prodname_pro %} e planos de cobrança antigos por repositório e em repositórios públicos e privados com {% data variables.product.prodname_team %}{% if currentVersion != "free-pro-team@latest" %}, {% data variables.product.prodname_ghe_server %} 2.17+,{% endif %} and {% data variables.product.prodname_ghe_cloud %}.site.data.variables.product.prodname_ghe_cloud }}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/pt-BR/data/reusables/gated-features/policies.md b/translations/pt-BR/data/reusables/gated-features/policies.md
deleted file mode 100644
index e71df97a5209..000000000000
--- a/translations/pt-BR/data/reusables/gated-features/policies.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Nota:** {% data variables.product.prodname_policies %} está atualmente em alfa. Esta documentação é confidencial e disponibilizada pela NDA. Não distribuir.
-
-{% endnote %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/gated-features/sponsors-beta.md b/translations/pt-BR/data/reusables/gated-features/sponsors-beta.md
deleted file mode 100644
index de589a316568..000000000000
--- a/translations/pt-BR/data/reusables/gated-features/sponsors-beta.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Atenção:** {% data variables.product.prodname_sponsors %} para organizações está atualmente em versão beta e sujeito a alterações.
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/gated-features/team-sync-gated.md b/translations/pt-BR/data/reusables/gated-features/team-sync-gated.md
deleted file mode 100644
index 688fc732c9ce..000000000000
--- a/translations/pt-BR/data/reusables/gated-features/team-sync-gated.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-
-A sincronização da equipe está disponível para organizações que usam {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
-
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/explains-hello-world-example.md b/translations/pt-BR/data/reusables/github-actions/explains-hello-world-example.md
deleted file mode 100644
index 802679c95086..000000000000
--- a/translations/pt-BR/data/reusables/github-actions/explains-hello-world-example.md
+++ /dev/null
@@ -1 +0,0 @@
-O `OWNER` do repositório `octocat` é a organização e o nome do `REPOSITORY` é `hello-world`.
diff --git a/translations/pt-BR/data/reusables/github-actions/github-actions-minutes-change.md b/translations/pt-BR/data/reusables/github-actions/github-actions-minutes-change.md
deleted file mode 100644
index 0d3f51e87890..000000000000
--- a/translations/pt-BR/data/reusables/github-actions/github-actions-minutes-change.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Nota:** Depois de maio, 14 de Maio, 2020, {% data variables.product.prodname_team %} incluirá 3.000 {% data variables.product.prodname_actions %} minutos por mês.
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/github-actions/github-actions-usage-limits.md b/translations/pt-BR/data/reusables/github-actions/github-actions-usage-limits.md
deleted file mode 100644
index b9c2f9f02f76..000000000000
--- a/translations/pt-BR/data/reusables/github-actions/github-actions-usage-limits.md
+++ /dev/null
@@ -1,15 +0,0 @@
-Há alguns limites no uso do {% data variables.product.prodname_actions %} , e variará dependendo se você usa executores hospedados {% data variables.product.prodname_dotcom %}ou auto-hospedados. Estes limites estão sujeitos a mudanças.
-
-- **Tempo de execução de tarefas ** - Cada trabalho em um fluxo de trabalho pode ser executado por até 6 horas de tempo de execução. Se um trabalho atingir esse limite, o trabalho será terminado e não será completado. Este limite não se aplica a executores auto-hospedados.
-- **Tempo de execução do fluxo de trabalho** - Cada execução do fluxo de trabalho é limitada a 72 horas. Se a execução de um fluxo de trabalho atingir esse limite, a execução do fluxo de trabalho será cancelada. Este limite também se aplica a executores auto-hospedados.
-- **Tempo de fila de tarefas** - Cada trabalho para executores auto-hospedados pode ser enfileirado por um máximo de 24 horas. Se um executor auto-hospedado não começar a executar a tarefa dentro deste limite, a tarefa será encerrada e não será concluída. Este limite não se aplica a executores hospedados para {% data variables.product.prodname_dotcom %}.
-- **Solicitações de API** - Você pode executar até 1000 solicitações de API por hora em todas as ações dentro de um repositório. Se excedido, as chamadas de API adicionais falharão, o que pode causar falha nas tarefas. Este limite também se aplica a executores auto-hospedados.
-- **Tarefas correntes** - O número de trabalhos simultâneos que você pode executar em sua conta depende do seu plano GitHub, conforme indicado na tabela a seguir. Se excedido, quaisquer tarefas adicionais serão colocadas na fila. Não há limites de concorrência para os executores auto-hospedados.
-
- | Plano GitHub | Total de tarefas simultâneas | Máximo de tarefas macOS simultâneas |
- | ------------ | ---------------------------- | ----------------------------------- |
- | Grátis | 20 | 5 |
- | Pro | 40 | 5 |
- | Equipe | 60 | 5 |
- | Enterprise | 180 | 50 |
-- **Matriz de vagas** - {% data reusables.github-actions.matrix-limits %}
diff --git a/translations/pt-BR/data/reusables/github-actions/matrix-limits.md b/translations/pt-BR/data/reusables/github-actions/matrix-limits.md
deleted file mode 100644
index 71fa5cb9f40e..000000000000
--- a/translations/pt-BR/data/reusables/github-actions/matrix-limits.md
+++ /dev/null
@@ -1 +0,0 @@
-Uma matriz de tarefas pode gerar 256 tarefas no máximo por execução do fluxo de trabalho. Este limite também se aplica a executores auto-hospedados.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-add-new-runner.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-add-new-runner.md
deleted file mode 100644
index 66beb5a4f020..000000000000
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-add-new-runner.md
+++ /dev/null
@@ -1,20 +0,0 @@
-1. Em "Self-hosted runners" (Executores auto-hospedados), clique em **Add runner** (Adicionar executor).
-
-1. Selecione o sistema operacional e a arquitetura da sua máquina de executor auto-hospedada. ![Selecionar sistema operacional de executor auto-hospedado](/assets/images/help/settings/actions-runner-architecture-os.png)
-
-
-1. Você verá instruções mostrando como baixar o executor e instalá-lo em sua máquina de executor auto-hospedada.
-
- Abra um shell em sua máquina de executor auto-hospedado e execute cada comando shell na ordem mostrada.
-
- {% note %}
-
- **Nota:** No Windows, se você quiser instalar a aplicação de executor auto-hospedada como um serviço, você deve abrir um shell com privilégios de administrador. Também recomendamos que você use `C:\actions-runner` como diretório para o aplicativo runner auto-hospedado para que as contas de sistema Windows possam acessar o diretório do executor.
-
- {% endnote %}
-
- As instruções te ajudam a completar estas tarefas:
- - Transferindo e extraindo o aplicativo do executor auto-hospedado.
- - Executando o script `config` para configurar a aplicação de executor auto-hospedada e registrá-lo no {% data variables.product.prodname_actions %}. O script `config` requer a URL de destino e um token de tempo limitado gerado automaticamente para autenticar a solicitação.
- - No Windows, o script `config` também pergunta se você gostaria de instalar o aplicativo de execução auto-hospedado como um serviço. Para Linux e macOS, você pode instalar um serviço depois de terminar de adicionar o executor. Para obter mais informações, consulte "[Configuring the self-hosted runner application as a service](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service)."
- - Executando o aplicativo do executor auto-hospedado para conectar a máquina ao {% data variables.product.prodname_actions %}.
diff --git a/translations/pt-BR/data/reusables/github-component-kit/intro-for-component-kit.md b/translations/pt-BR/data/reusables/github-component-kit/intro-for-component-kit.md
deleted file mode 100644
index fd264b8cff3d..000000000000
--- a/translations/pt-BR/data/reusables/github-component-kit/intro-for-component-kit.md
+++ /dev/null
@@ -1 +0,0 @@
-O {% data variables.product.prodname_component_kit %} usa {% data variables.product.prodname_github_app %} e {% data variables.product.prodname_actions %} para alimentar elementos interativos dentro da interface do usuário {% data variables.product.prodname_dotcom %} UI. Por exemplo, você pode guiar usuários do repositório com as próximas etapas ou solicitar para eles aceitarem contratos de licença.
diff --git a/translations/pt-BR/data/reusables/github-component-kit/opening-explanation-for-component-kit.md b/translations/pt-BR/data/reusables/github-component-kit/opening-explanation-for-component-kit.md
deleted file mode 100644
index 775f1eee2b73..000000000000
--- a/translations/pt-BR/data/reusables/github-component-kit/opening-explanation-for-component-kit.md
+++ /dev/null
@@ -1,3 +0,0 @@
-O {% data variables.product.prodname_component_kit %} permite que você configure um componente interativo para aparecer em uma pull request ou problema. Componentes interativos permitem que as pessoas acionem e gerenciem tarefas que aparecem na interface do usuário do {% data variables.product.prodname_dotcom %} enquanto uma {% data variables.product.prodname_github_app %} ou a ação executa as tarefas solicitadas e compartilha as atualizações.
-
-Usando o ponto de extremidade "[Criar comentário compostável](/hidden/github-component-kit/composable-comments#create-composable-comment)", um {% data variables.product.prodname_github_app %} ou ação pode criar um comentário compostável em um problema ou pull request. O comentário composable pode incluir um componente interativo, como um botão personalizado. Quando alguém interage com o comentário, o {% data variables.product.prodname_github_app %} receberá o evento webhook `interactive_component`.
diff --git a/translations/pt-BR/data/reusables/github-insights/no-configuration-file.md b/translations/pt-BR/data/reusables/github-insights/no-configuration-file.md
deleted file mode 100644
index d918cb7214ca..000000000000
--- a/translations/pt-BR/data/reusables/github-insights/no-configuration-file.md
+++ /dev/null
@@ -1 +0,0 @@
-Se você não tem um arquivo de configuração, siga as instruções para instalar {% data variables.product.prodname_insights %} pela primeira vez. Para obter mais informações, consulte "[Installing {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/installing-github-insights#installing-github-insights)."
diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/about-connected-teams.md b/translations/pt-BR/data/reusables/identity-and-permissions/about-connected-teams.md
deleted file mode 100644
index 09638cab3def..000000000000
--- a/translations/pt-BR/data/reusables/identity-and-permissions/about-connected-teams.md
+++ /dev/null
@@ -1,7 +0,0 @@
-Depois que as equipes do {% data variables.product.prodname_dotcom %} estiverem conectadas a um grupo de IdP, o administrador do IdP deve fazer as alterações na associação a equipes por meio do provedor de identidade. Se uma equipe estiver conectada a um grupo de IdP, você não poderá gerenciar a associação à equipe no {% data variables.product.product_name %} ou usando a API.
-
-Para gerenciar o acesso ao repositório de qualquer equipe do {% data variables.product.prodname_dotcom %} incluindo equipes conectadas a um grupo de IdP, você deve fazer alterações no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)" e "[Gerenciar o acesso da equipe ao repositório de uma organização](/articles/managing-team-access-to-an-organization-repository)".
-
-Você pode selecionar os repositórios aos quais você deseja que os membros da equipe tenham acesso por padrão. Os grupos de IdP conectados terão acesso automaticamente a esses repositórios. Para obter mais informações, consulte "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)."
-
-Todas as alterações de membros da equipe feitas através do seu IdP aparecerão no log de auditoria do {% data variables.product.product_name %} como alterações feitas pelo bot de sincronização de equipe. Seu IdP enviará dados de membros da equipe para {% data variables.product.prodname_dotcom %} uma vez a cada hora.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/marketplace/marketplace_RFP_deadline.md b/translations/pt-BR/data/reusables/marketplace/marketplace_RFP_deadline.md
deleted file mode 100644
index 1188c5036139..000000000000
--- a/translations/pt-BR/data/reusables/marketplace/marketplace_RFP_deadline.md
+++ /dev/null
@@ -1 +0,0 @@
-Abril de 10
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/marketplace/unverified-req.md b/translations/pt-BR/data/reusables/marketplace/unverified-req.md
deleted file mode 100644
index 8ad7359d0487..000000000000
--- a/translations/pt-BR/data/reusables/marketplace/unverified-req.md
+++ /dev/null
@@ -1 +0,0 @@
-Aplicativos não verificados não precisam atender aos "[Requisitos para listar um aplicativo no GitHub Marketplace](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)" ou passar pelo processo de "[Processo de revisão de segurança](/marketplace/getting-started/security-review-process/)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/nested-teams/include-child-team-members.md b/translations/pt-BR/data/reusables/nested-teams/include-child-team-members.md
deleted file mode 100644
index f9e06a5ef41e..000000000000
--- a/translations/pt-BR/data/reusables/nested-teams/include-child-team-members.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %}
-Se você passar pelo tipo de mídia `hellcat-preview`, os membros da equipe incluirão os membros de equipes infantis.
-{% else %}
-Os membros da equipe incluirão os membros de equipes infantis.
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/organizations/org-settings-repository-roles.md b/translations/pt-BR/data/reusables/organizations/org-settings-repository-roles.md
deleted file mode 100644
index 935d5d7e64ba..000000000000
--- a/translations/pt-BR/data/reusables/organizations/org-settings-repository-roles.md
+++ /dev/null
@@ -1 +0,0 @@
-4. Na barra lateral esquerda, clique em **Repository roles** (Funções do repositório). ![Aba de funções do repositório nas configurações da organização](/assets/images/help/organizations/org-settings-repository-roles.png)
diff --git a/translations/pt-BR/data/reusables/orgs/deprecating_creation_type.md b/translations/pt-BR/data/reusables/orgs/deprecating_creation_type.md
deleted file mode 100644
index 54c3587e500c..000000000000
--- a/translations/pt-BR/data/reusables/orgs/deprecating_creation_type.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-{% warning %}
-
-**Aviso de depreciação:** {% data variables.product.prodname_dotcom %} irá substituir e descontinuar `members_allowed_repository_creation_type` em favor de mais permissões granulares. Os novos parâmetros de entrada são `members_can_create_public_repositories`, `members_can_create_private_repositories` para todas as organizações e `members_can_create_internal_repositories` para organizações associadas a uma conta corporativa usando {% data variables.product.prodname_ghe_cloud %} ou {% data variables.product.prodname_ghe_server %} 2.20+. Para obter mais informações, consulte o [blog post](https://developer.github.com/changes/2019-12-03-internal-visibility-changes) (postagem de blog).
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/orgs/internal_repos.md b/translations/pt-BR/data/reusables/orgs/internal_repos.md
deleted file mode 100644
index 0180ce396ea5..000000000000
--- a/translations/pt-BR/data/reusables/orgs/internal_repos.md
+++ /dev/null
@@ -1 +0,0 @@
-Se sua organização está associada a uma conta corporativa usando {% data variables.product.prodname_ghe_cloud %} ou {% data variables.product.prodname_ghe_server %} 2.20+, `visibility` também pode ser `internal`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/package_registry/about-spending-limits.md b/translations/pt-BR/data/reusables/package_registry/about-spending-limits.md
deleted file mode 100644
index 817f2306a410..000000000000
--- a/translations/pt-BR/data/reusables/package_registry/about-spending-limits.md
+++ /dev/null
@@ -1 +0,0 @@
-Por padrão, sua conta terá um limite de gastos de $0 para o seu uso combinado de {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %}. Para permitir superações, você pode aumentar o limite de gastos ou permitir gastos ilimitados.
diff --git a/translations/pt-BR/data/reusables/package_registry/accessing-packages.md b/translations/pt-BR/data/reusables/package_registry/accessing-packages.md
deleted file mode 100644
index dd18a59bc1e1..000000000000
--- a/translations/pt-BR/data/reusables/package_registry/accessing-packages.md
+++ /dev/null
@@ -1,4 +0,0 @@
-Você pode acessar seus pacotes a partir deste URL substituindo `OWNER` pelo nome de usuário ou organização do {% data variables.product.prodname_dotcom %} e `REPOSITORY` pelo nome do repositório:
- ```
- https://github.com/OWNER/REPOSITORY/packages
- ```
diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry.md b/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry.md
deleted file mode 100644
index 2d9ed6226017..000000000000
--- a/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry.md
+++ /dev/null
@@ -1,18 +0,0 @@
-1. Create a new personal access token (PAT) with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token.
- - Select the `read:packages` scope to download container images and read their metadata.
- - Select the `write:packages` scope to download and upload container images and read and write their metadata.
- - Select the `delete:packages` scope to delete container images.
-
- Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)".
-
-2. Save your PAT. We recommend saving your PAT as an environment variable.
- ```shell
- $ export CR_PAT=YOUR_TOKEN
- ```
-3. Using the CLI for your container type, sign in to the {% data variables.product.prodname_github_container_registry %} service at `ghcr.io`.
- {% raw %}
- ```shell
- $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
- > Login Succeeded
- ```
- {% endraw %}
diff --git a/translations/pt-BR/data/reusables/permissions/admin-access-org.md b/translations/pt-BR/data/reusables/permissions/admin-access-org.md
deleted file mode 100644
index b4f934126644..000000000000
--- a/translations/pt-BR/data/reusables/permissions/admin-access-org.md
+++ /dev/null
@@ -1 +0,0 @@
-You must authenticate using an access token with the `admin:org` scope to use this endpoint.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/permissions/admin-access.md b/translations/pt-BR/data/reusables/permissions/admin-access.md
deleted file mode 100644
index d35e7e24173c..000000000000
--- a/translations/pt-BR/data/reusables/permissions/admin-access.md
+++ /dev/null
@@ -1 +0,0 @@
-You must authenticate using an access token with the `repo` scope to use this endpoint.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/permissions/code-scanning-app-read-permissions.md b/translations/pt-BR/data/reusables/permissions/code-scanning-app-read-permissions.md
deleted file mode 100644
index cbee5c312771..000000000000
--- a/translations/pt-BR/data/reusables/permissions/code-scanning-app-read-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s must have the `security_events` read permission to use this endpoint.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/permissions/read-access.md b/translations/pt-BR/data/reusables/permissions/read-access.md
deleted file mode 100644
index eeff40633e5b..000000000000
--- a/translations/pt-BR/data/reusables/permissions/read-access.md
+++ /dev/null
@@ -1 +0,0 @@
-Qualquer pessoa com acesso de leitura ao repositório pode usar este ponto de extremidade. Se o repositório for privado, você deverá usar um token de acesso com o escopo `repo`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/permissions/security-events-scope.md b/translations/pt-BR/data/reusables/permissions/security-events-scope.md
deleted file mode 100644
index afbd0ee17302..000000000000
--- a/translations/pt-BR/data/reusables/permissions/security-events-scope.md
+++ /dev/null
@@ -1 +0,0 @@
-Você deve usar um token de acesso com o escopo `security_events` para usar este ponto de extremidade.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/permissions/write-access.md b/translations/pt-BR/data/reusables/permissions/write-access.md
deleted file mode 100644
index d35e7e24173c..000000000000
--- a/translations/pt-BR/data/reusables/permissions/write-access.md
+++ /dev/null
@@ -1 +0,0 @@
-You must authenticate using an access token with the `repo` scope to use this endpoint.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/pre-release-program/ant-man-preview-deployments.md b/translations/pt-BR/data/reusables/pre-release-program/ant-man-preview-deployments.md
deleted file mode 100644
index 4dbd7ba1b8af..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/ant-man-preview-deployments.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% note %}
-
-**Note:** The `transient_environment` and `production_environment` parameters are currently available for developers to preview. During the preview period, the API may change without advance notice. Veja o post do [blogue](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements) para obter informações completas.
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.ant-man-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/ant-man-preview-statuses.md b/translations/pt-BR/data/reusables/pre-release-program/ant-man-preview-statuses.md
deleted file mode 100644
index ade0fcf428bc..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/ant-man-preview-statuses.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% note %}
-
-**Note:** The `inactive` state and the `log_url`, `environment_url`, and `auto_inactive` parameters are currently available for developers to preview. Veja o post do [blogue](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements) para obter informações completas.
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.ant-man-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/antiope-preview.md b/translations/pt-BR/data/reusables/pre-release-program/antiope-preview.md
deleted file mode 100644
index 96eee60b530d..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/antiope-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Checks API is currently available for developers to preview. During the preview period, the API may change without advance notice. Veja o post do [blogue](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) para obter informações completas. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.antiope-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/baptiste-keys-preview.md b/translations/pt-BR/data/reusables/pre-release-program/baptiste-keys-preview.md
deleted file mode 100644
index 1a309066ba06..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/baptiste-keys-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** The `is_template` and `template_repository` keys are currently available for developer to preview. See [Create a repository using a template](/v3/repos/#create-a-repository-using-a-template) to learn how to create template repositories. To access these new response keys during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.baptiste-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/baptiste-preview.md b/translations/pt-BR/data/reusables/pre-release-program/baptiste-preview.md
deleted file mode 100644
index 850b3f271bb4..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/baptiste-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Creating and using repository templates is currently available for developers to preview. To access this new endpoint during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.baptiste-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/batman-preview.md b/translations/pt-BR/data/reusables/pre-release-program/batman-preview.md
deleted file mode 100644
index 079a5b57c932..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/batman-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
-{% note %}
-
-**Note:** Using the {% data variables.product.prodname_component_kit %} API is currently available for developers to preview. To access these endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.batman-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/checks-public-beta.md b/translations/pt-BR/data/reusables/pre-release-program/checks-public-beta.md
deleted file mode 100644
index 9220bede6270..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/checks-public-beta.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note:** The Checks API is currently in public beta and only available for use with GitHub Apps.
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/cloak-preview.md b/translations/pt-BR/data/reusables/pre-release-program/cloak-preview.md
deleted file mode 100644
index bb8ec40692d5..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/cloak-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Commit Search API is currently available for developers to preview. During the preview period, the APIs may change without advance notice. Veja o post do [blogue](https://developer.github.com/changes/2017-01-05-commit-search-api/) para obter informações completas.
-
-To access the API you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.cloak-preview
-```
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/code-scanning-beta.md b/translations/pt-BR/data/reusables/pre-release-program/code-scanning-beta.md
deleted file mode 100644
index f9be785c151b..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/code-scanning-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** {% data variables.product.prodname_code_scanning_capc %} for open source repositories and private repositories is currently in beta and subject to change. To sign up, see [Advanced Security beta](https://github.com/features/security/advanced-security/signup).
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/comfort-fade-preview.md b/translations/pt-BR/data/reusables/pre-release-program/comfort-fade-preview.md
deleted file mode 100644
index 17e2464a7d19..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/comfort-fade-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Multi-line comments in a pull request diff is currently available for developers to preview. To access the new response fields during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.comfort-fade-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/doctor-strange-preview.md b/translations/pt-BR/data/reusables/pre-release-program/doctor-strange-preview.md
deleted file mode 100644
index 488fa5418a94..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/doctor-strange-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "enterprise-server@2.20" %}
-{% note %}
-
-**Note:** New endpoints using OAuth tokens as input parameters instead of path parameters are available for developers to preview in the [OAuth Applications API](/v3/apps/oauth_applications/). To access these endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.doctor-strange-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/dorian-preview.md b/translations/pt-BR/data/reusables/pre-release-program/dorian-preview.md
deleted file mode 100644
index d4141e00a5ab..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/dorian-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Enabling and disabling dependency alerts for a repository using the REST API is currently available for developers to preview. To access these new endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.dorian-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/drax-preview.md b/translations/pt-BR/data/reusables/pre-release-program/drax-preview.md
deleted file mode 100644
index 720c942e5f60..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/drax-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.13" %}
-{% note %}
-
-**Note:** The [Licenses API](https://developer.github.com/changes/2015-03-09-licenses-api/) is currently available for developers to preview. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.drax-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/echo-preview.md b/translations/pt-BR/data/reusables/pre-release-program/echo-preview.md
deleted file mode 100644
index d6897f7f1d82..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/echo-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}
-{% note %}
-
-**Note:** The team discussions API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-02-07-team-discussions-api) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.echo-preview+json
-```
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/flash-preview.md b/translations/pt-BR/data/reusables/pre-release-program/flash-preview.md
deleted file mode 100644
index 7492d30ea799..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/flash-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% note %}
-
-**Note:** New features in the Deployments API on {% data variables.product.product_name %} are currently available during a public beta. Veja o post do [blogue](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) para obter informações completas.
-
-To access the new `environment` parameter, the two new values for the `state` parameter (`in_progress` and `queued`), and use `auto_inactive` on production deployments during the public beta period, you must provide the following custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.flash-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/gambit-preview.md b/translations/pt-BR/data/reusables/pre-release-program/gambit-preview.md
deleted file mode 100644
index ae67b941174b..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/gambit-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %}
-{% note %}
-
-**Note:** Uninstalling {% data variables.product.prodname_github_app %}s and revoking an app's installation token are currently available for developers to preview. To access the new endpoint during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.gambit-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/giant-sentry-fist-pre-release.md b/translations/pt-BR/data/reusables/pre-release-program/giant-sentry-fist-pre-release.md
deleted file mode 100644
index 6ea06379025f..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/giant-sentry-fist-pre-release.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.8" %}
-{% note %}
-
-**Note:** {% data variables.giant-sentry-fist.product_name_long %} on {% data variables.product.product_name %} is currently available for developers to preview. To access the API, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.giant-sentry-fist-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/github-actions-public-beta.md b/translations/pt-BR/data/reusables/pre-release-program/github-actions-public-beta.md
deleted file mode 100644
index ff0a4b80f712..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/github-actions-public-beta.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% warning %}
-
-**New release:** {% data variables.product.prodname_actions %} is now available in a new limited public beta. This version offers a new workflow configuration and built-in continuous integration and continuous deployment capabilities. We strongly recommend you avoid using it for high-value workflows and content during this public beta period. To request to join the limited public beta, see the [GitHub Actions page](https://github.com/features/actions). For more information, see "[About GitHub Actions](/articles/about-github-actions)".
-
-GitHub Support will only provide support for the YAML syntax and no longer provides support for the HCL syntax.
-
-If you participated in the limited public beta and created workflows with the HCL syntax {% data variables.product.prodname_actions %}, you will need to upgrade to the new limited public beta that uses YAML syntax. When your repository is eligible to upgrade, you'll see an invitation in your repository. You must accept the invitation before you can use the new limited public beta.
-
-Once you've upgraded, any workflows that you created with the HCL syntax will need to be updated to the new YAML syntax. To automatically convert your workflows, see "[Migrating {% data variables.product.prodname_actions %} from HCL syntax to YAML syntax](/articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax)".
-
-{% endwarning %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/github-components-public-beta.md b/translations/pt-BR/data/reusables/pre-release-program/github-components-public-beta.md
deleted file mode 100644
index 2c242acbc08b..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/github-components-public-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
-{% note %}
-
-**Note:** The {% data variables.product.prodname_component_kit %} API is currently in private beta and subject to change.
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/groot-preview.md b/translations/pt-BR/data/reusables/pre-release-program/groot-preview.md
deleted file mode 100644
index 944243de7c52..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/groot-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Listing branches or pull requests for a commit in the Commits API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) for more details. To access the new endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.groot-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/hagar-preview.md b/translations/pt-BR/data/reusables/pre-release-program/hagar-preview.md
deleted file mode 100644
index e1cf318f3cc3..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/hagar-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}
-{% note %}
-
-**Note:** You can now retrieve someone's hovercard information in different contexts using the Hovercard API. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.hagar-preview+json
-```
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/hellcat-preview.md b/translations/pt-BR/data/reusables/pre-release-program/hellcat-preview.md
deleted file mode 100644
index b2268faa5418..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/hellcat-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %}
-{% note %}
-
-**Note:** The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.hellcat-preview+json
-```
-{% endnote %}
-
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/inertia-preview.md b/translations/pt-BR/data/reusables/pre-release-program/inertia-preview.md
deleted file mode 100644
index ac92f6ce6b53..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/inertia-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Projects API is currently available for developers to preview. During the preview period, the API may change without advance notice. Veja o post do [blogue](https://developer.github.com/changes/2016-10-27-changes-to-projects-api) para obter informações completas. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.inertia-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/london-preview.md b/translations/pt-BR/data/reusables/pre-release-program/london-preview.md
deleted file mode 100644
index 4fa608045abb..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/london-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Enabling or disabling automated security fixes is currently available for developers to preview. To access this new endpoint during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.london-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/luke-cage-preview.md b/translations/pt-BR/data/reusables/pre-release-program/luke-cage-preview.md
deleted file mode 100644
index a4a7cfe32bbb..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/luke-cage-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.luke-cage-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/lydian-preview.md b/translations/pt-BR/data/reusables/pre-release-program/lydian-preview.md
deleted file mode 100644
index fa5a34527bea..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/lydian-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Updating the pull request branch with latest upstream changes is currently available for developers to preview. To access this new endpoint during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.lydian-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/mercy-pre-release-replace.md b/translations/pt-BR/data/reusables/pre-release-program/mercy-pre-release-replace.md
deleted file mode 100644
index c49f66c4dba1..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/mercy-pre-release-replace.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** Repository topics on {% data variables.product.product_name %} are currently available for developers to preview. To use this endpoint, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.mercy-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/mercy-pre-release.md b/translations/pt-BR/data/reusables/pre-release-program/mercy-pre-release.md
deleted file mode 100644
index fa26dc8969ed..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/mercy-pre-release.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** {% data variables.mercy.product_name_long %} on {% data variables.product.product_name %} is currently available for developers to preview. To view the `topics` property in calls that return repository results, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.mercy-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/mister-fantastic-pre-release.md b/translations/pt-BR/data/reusables/pre-release-program/mister-fantastic-pre-release.md
deleted file mode 100644
index 4918b1477ee0..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/mister-fantastic-pre-release.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}
-{% note %}
-
-**Note:** {% data variables.mister-fantastic.product_name_long %} contains two additional fields in responses, which developers can preview: `html_url` and `source`. To see these two new fields, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.mister-fantastic-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/mockingbird-preview.md b/translations/pt-BR/data/reusables/pre-release-program/mockingbird-preview.md
deleted file mode 100644
index abc16872cb1e..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/mockingbird-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The API to get issue timeline events is currently available for developers to preview. During the preview period, the APIs may change without advance notice. Veja o post do [blogue](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) para obter informações completas. To access the API you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.mockingbird-preview
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/multi-line-comments-public-beta.md b/translations/pt-BR/data/reusables/pre-release-program/multi-line-comments-public-beta.md
deleted file mode 100644
index 5aeea167477b..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/multi-line-comments-public-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Multi-line comments on pull requests are currently in public beta and subject to change.
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/nebula-preview.md b/translations/pt-BR/data/reusables/pre-release-program/nebula-preview.md
deleted file mode 100644
index 6a2ad6065e20..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/nebula-preview.md
+++ /dev/null
@@ -1,14 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-
-{% note %}
-
-**Note:** You can set the visibility of a repository using the new `visibility` parameter in the [Repositories API](/v3/repos/), and get a repository's visibility with a new response key. Para obter mais informações, consulte o [blog post](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) (postagem de blog).
-
-To access repository visibility during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.nebula-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/nightshade-preview.md b/translations/pt-BR/data/reusables/pre-release-program/nightshade-preview.md
deleted file mode 100644
index 22172eba6443..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/nightshade-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %}
-{% note %}
-
-**Note:** The [Repository Transfer API](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) is currently available for developers to preview. To access the API, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.nightshade-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/org-self-hosted-runner-beta.md b/translations/pt-BR/data/reusables/pre-release-program/org-self-hosted-runner-beta.md
deleted file mode 100644
index 19b16aaa4842..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/org-self-hosted-runner-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% warning %}
-
-**Aviso:** A API dos executores auto-hospedados para organizações está atualmente no beta público e sujeita a alterações.
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-deployment.md b/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-deployment.md
deleted file mode 100644
index 6a888df13e51..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-deployment.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** If a deployment is created via a {% data variables.product.prodname_github_app %}, the response will include the `performed_via_github_app` object with information about the {% data variables.product.prodname_github_app %}. For more information, see the [related blog post](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access).
-
-To receive the `performed_via_github_app` object in the response, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.machine-man-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue-comment.md b/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue-comment.md
deleted file mode 100644
index ad67d849dd85..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue-comment.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** If an issue comment is created via a {% data variables.product.prodname_github_app %}, the response will include the `performed_via_github_app` object with information about the {% data variables.product.prodname_github_app %}. For more information, see the [related blog post](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access).
-
-To receive the `performed_via_github_app` object in the response, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.machine-man-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue-event.md b/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue-event.md
deleted file mode 100644
index 54e004859064..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue-event.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** If an issue event is created via a {% data variables.product.prodname_github_app %}, the response will include the `performed_via_github_app` object with information about the {% data variables.product.prodname_github_app %}. For more information, see the [related blog post](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access).
-
-To receive the `performed_via_github_app` object in the response, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.machine-man-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue.md b/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue.md
deleted file mode 100644
index ee0240792f4a..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/performed-by-integration-issue.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** If an issue is opened via a {% data variables.product.prodname_github_app %}, the response will include the `performed_via_github_app` object with information about the {% data variables.product.prodname_github_app %}. For more information, see the [related blog post](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access).
-
-To receive the `performed_via_github_app` object in the response, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.machine-man-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/scarlet-witch-key-preview.md b/translations/pt-BR/data/reusables/pre-release-program/scarlet-witch-key-preview.md
deleted file mode 100644
index a82019b82319..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/scarlet-witch-key-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** Developers can preview a new `code_of_conduct` key in responses. For more information, see [Codes of Conduct API](/v3/codes_of_conduct/).
-
-To access this new response key during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.scarlet-witch-preview+json
-```
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/scarlet-witch-preview.md b/translations/pt-BR/data/reusables/pre-release-program/scarlet-witch-preview.md
deleted file mode 100644
index 860b30d517dc..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/scarlet-witch-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Codes of Conduct API is currently available for developers to preview.
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.scarlet-witch-preview+json
-```
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/shadow-cat-preview.md b/translations/pt-BR/data/reusables/pre-release-program/shadow-cat-preview.md
deleted file mode 100644
index 3d95ab9ccae5..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/shadow-cat-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %}
-{% note %}
-
-**Note:** The Draft Pull Request API is currently available for developers to preview. You can use this API to create a draft pull request or see whether a pull request is in draft state. See the [blog post](https://developer.github.com/changes/2019-02-14-draft-pull-requests) preview for more details. To access the new `draft` parameter during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.shadow-cat-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/sombra-preview.md b/translations/pt-BR/data/reusables/pre-release-program/sombra-preview.md
deleted file mode 100644
index 9298dfa844f5..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/sombra-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** The Interactions API is currently in public preview. See the [blog post](https://developer.github.com/changes/2018-12-18-interactions-preview) preview for more details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.sombra-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/squirrel-girl-preview.md b/translations/pt-BR/data/reusables/pre-release-program/squirrel-girl-preview.md
deleted file mode 100644
index 52bd9558fc3b..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/squirrel-girl-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** APIs for managing reactions are currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2016-05-12-reactions-api-preview) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
- ```
- application/vnd.github.squirrel-girl-preview+json
- ```
- {% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/squirrel-girl-response-preview.md b/translations/pt-BR/data/reusables/pre-release-program/squirrel-girl-response-preview.md
deleted file mode 100644
index 18d162292a2d..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/squirrel-girl-response-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The [reactions API](/v3/reactions/) is available for developers to preview. The `url` can be used to construct the API location for [listing and creating](/v3/reactions) reactions. See the [blog post](https://developer.github.com/changes/2016-05-12-reactions-api-preview) for full details. To receive the `reactions` object in the response for this endpoint you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.squirrel-girl-preview
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/superpro-preview.md b/translations/pt-BR/data/reusables/pre-release-program/superpro-preview.md
deleted file mode 100644
index f0878ed234c6..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/superpro-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The [Global Webhooks API](/rest/reference/enterprise-admin#global-webhooks) is currently available for developers to preview. To access the API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header:
-
-```
-application/vnd.github.superpro-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/surtur-preview.md b/translations/pt-BR/data/reusables/pre-release-program/surtur-preview.md
deleted file mode 100644
index 9cfdfe8ad8dc..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/surtur-preview.md
+++ /dev/null
@@ -1,21 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-{% note %}
-
-**Note:** New repository creation permissions are available to preview. You can now use `members_can_create_public_repositories`, `members_can_create_private_repositories`, and `members_can_create_internal_repositories`. You can only allow members to create internal repositories if your organization is associated with an enterprise account using {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %} 2.20+. These parameters provide more granular permissions to configure the type of repositories organization members can create.
-
-To access these new parameters during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.surtur-preview+json
-```
-{% endnote %}
-{% else %}
-{% note %}
-
-**Note:** New repository creation permissions are available to preview. You can now set the `members_allowed_repository_creation_type` parameter to configure whether organization members can create repositories and the type of repositories they can create.
-
-To access this new parameter during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.surtur-preview+json
-```
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/switcheroo-preview.md b/translations/pt-BR/data/reusables/pre-release-program/switcheroo-preview.md
deleted file mode 100644
index fbbbe3817bd9..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/switcheroo-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Enabling and disabling Pages in the Pages API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) preview for more details. To access the new endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.switcheroo-preview+json
-```
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/symmetra-preview.md b/translations/pt-BR/data/reusables/pre-release-program/symmetra-preview.md
deleted file mode 100644
index c578f33898be..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/symmetra-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion != ‘dotcom’ and currentVersion ver_lt "enterprise-server@2.20" %}
-{% note %}
-
-**Note:** You can add or edit descriptions in labels. See the [blog post](https://developer.github.com/changes/2018-02-22-label-description-search-preview) for full details. To access this feature during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.symmetra-preview+json
-```
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/thor-pre-release.md b/translations/pt-BR/data/reusables/pre-release-program/thor-pre-release.md
deleted file mode 100644
index e034ce622e48..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/thor-pre-release.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.13" %}
-{% note %}
-
-**Note:** Team-based review requests in the Review Requests API on {% data variables.product.product_name %} are currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-07-26-team-review-request-thor-preview) for full details.
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.thor-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/usage-api-beta.md b/translations/pt-BR/data/reusables/pre-release-program/usage-api-beta.md
deleted file mode 100644
index 0fb7989fc11c..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/usage-api-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% warning %}
-
-**Warning:** This {% data variables.product.prodname_actions %} usage endpoint is currently in public beta and subject to change. For more information, see "[GitHub Actions API workflow usage](https://developer.github.com/changes/2020-05-15-actions-api-workflow-usage)."
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/wyandotte-preview.md b/translations/pt-BR/data/reusables/pre-release-program/wyandotte-preview.md
deleted file mode 100644
index 2d5c90f982c3..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/wyandotte-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** To access the Migrations API, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.wyandotte-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/x-ray-preview.md b/translations/pt-BR/data/reusables/pre-release-program/x-ray-preview.md
deleted file mode 100644
index c09b481483ca..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/x-ray-preview.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" %}
-{% note %}
-
-**Note:** When a GitHub Enterprise instance is in private mode, site and repository administrators can enable anonymous Git access for a public repository. This feature is currently available for developers to preview. See the [blog post](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/) for full details.
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.x-ray-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pre-release-program/zzzax-preview.md b/translations/pt-BR/data/reusables/pre-release-program/zzzax-preview.md
deleted file mode 100644
index 1614b2e1532d..000000000000
--- a/translations/pt-BR/data/reusables/pre-release-program/zzzax-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.12" %}
-{% note %}
-
-**Note:** Protected Branches API can now manage a setting for requiring signed commits. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.zzzax-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pulls/diff_location.md b/translations/pt-BR/data/reusables/pulls/diff_location.md
deleted file mode 100644
index 1176a8613265..000000000000
--- a/translations/pt-BR/data/reusables/pulls/diff_location.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% note %}
-
-**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API offers the `application/vnd.github.v3.diff` [media type](/v3/media/#commits-commit-comparison-and-pull-requests). Para ver um diff do pull request, adicione este tipo de mídia ao cabeçalho `Aceitar` de uma chamada para o ponto de extremidade do [pull request único](/v3/pulls/#get-a-pull-request).
-
-O valor da `posição` é igual ao número de linhas abaixo da primeira parte "@@@" do cabeçalho no arquivo ao qual você deseja adicionar um comentário. A linha logo abaixo da linha "@@" é a posição 1, a próxima linha é a posição 2, e assim por diante. A posição no diff continua a aumentar por meio das linhas de linhas dos espaços em branco e das partes adicionais até o início de um novo arquivo.
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pulls/multiline_comments_summary_for_responses.md b/translations/pt-BR/data/reusables/pulls/multiline_comments_summary_for_responses.md
deleted file mode 100644
index 1af24654d7ba..000000000000
--- a/translations/pt-BR/data/reusables/pulls/multiline_comments_summary_for_responses.md
+++ /dev/null
@@ -1,21 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-
-##### Resumo de comentários de linha múltipla
-
-{% note %}
-
-**Observação:** Novos parâmetros e campos de resposta estão disponíveis para os desenvolvedores visualizarem. Durante o período de visualização, esses campos de resposta podem mudar sem aviso prévio. Veja o post do [blogue](https://developer.github.com/changes/2019-10-03-multi-line-comments) para obter informações completas.
-
-{% endnote %}
-
-Use o cabeçalho de visualização `comfort-fade` e o parâmetro de `linha` para mostrar campos compatíveis com o comentário de linha múltipla na resposta.
-
-Se você usar o cabeçalho de visualização `comfort-fade` sua resposta mostrará:
-- Para comentários de linha múltipla, valores para `start_line`, `original_start_line,` `start_side`, `linha`, `original_line` e `lado`.
-- Para comentários de linha única, valores para `linha`, `original_line` e `lado` e um valor `nulo` para `start_line`, `original_start_line` e `start_side`.
-
-Se você não usar o cabeçalho de visualização `comfort-fade` serão exibidos comentários de linha múltipla e de linha única da mesma maneira na resposta com um único atributo `de posição`. Sua resposta exibirá:
-- Para comentários linha múltipla, a última linha do intervalo de comentários para o atributo de `posição`.
-- For single-line comments, the diff-positioned way of referencing comments for the `position` attribute. Para obter mais informações, consulte a `posição` na tabela [de parâmetros de entrada](/v3/pulls/comments/#parameters-2).
-
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pulls/pull_request_access.md b/translations/pt-BR/data/reusables/pulls/pull_request_access.md
deleted file mode 100644
index 49efc9f92096..000000000000
--- a/translations/pt-BR/data/reusables/pulls/pull_request_access.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-
-Para abrir ou atualizar um pull request em um repositório público, você deve ter acesso ao branch principal ou ao branch original. Para repositórios de propriedade da organização, você deve ser um integrante da organização que possui o repositório para abrir ou atualizar um pull request.
-
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/pulls/pull_request_mergeability.md b/translations/pt-BR/data/reusables/pulls/pull_request_mergeability.md
deleted file mode 100644
index 8b31478a8c2e..000000000000
--- a/translations/pt-BR/data/reusables/pulls/pull_request_mergeability.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Observação:** Você precisa [solicitar um pull request](/v3/pulls/#get-a-pull-request) explicitamente para acionar um commit de teste de merge, verifica a mesclabilidade dos pull requests. Para obter mais informações, consulte "[Verificar a mesclabilidade dos pull requests](/v3/git/#checking-mergeability-of-pull-requests)".
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/pulls/pullrequests_as_issues.md b/translations/pt-BR/data/reusables/pulls/pullrequests_as_issues.md
deleted file mode 100644
index 6d67689cc3ca..000000000000
--- a/translations/pt-BR/data/reusables/pulls/pullrequests_as_issues.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% note %}
-
-**Note**: GitHub's REST API considers every pull request an issue, but not every issue is a pull request. Por esse motivo, os pontos de extremidade dos "Problemas" podem retornar problemas e pull requests na resposta. Você pode identificar pull requests pela chave `pull_request`.
-
-Esteja ciente de que o `id` de um pull request retornado dos pontos de extremidade de "Problemas" será um _id de problema_. Para descobrir o id do pull request, use o ponto de extremidade "[List pull requests](/v3/pulls/#list-pull-requests)".
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/reminders/install-slack.md b/translations/pt-BR/data/reusables/reminders/install-slack.md
deleted file mode 100644
index 33d6c69d6bba..000000000000
--- a/translations/pt-BR/data/reusables/reminders/install-slack.md
+++ /dev/null
@@ -1 +0,0 @@
-If you'd like to install Slack on all of your repositories, select **All repositories**. If you'd like to only install Slack on select repositories, select **Only select repositories**. Then, read the list of permissions you're allowing Slack to access and click **Install**. ![Install Slack button](/assets/images/help/settings/scheduled-reminders-install-slack.png)
diff --git a/translations/pt-BR/data/reusables/reminders/scheduled-reminders-beta.md b/translations/pt-BR/data/reusables/reminders/scheduled-reminders-beta.md
deleted file mode 100644
index 05ae894babe1..000000000000
--- a/translations/pt-BR/data/reusables/reminders/scheduled-reminders-beta.md
+++ /dev/null
@@ -1 +0,0 @@
-Scheduled reminders for pull requests are currently in beta and subject to change. To request access to the next beta phase for scheduled reminders, join the waitlist at [GitHub Scheduled Reminders](https://github.com/features/reminders/signup).
diff --git a/translations/pt-BR/data/reusables/repositories/actions-new-workflow.md b/translations/pt-BR/data/reusables/repositories/actions-new-workflow.md
deleted file mode 100644
index 6af36a64692a..000000000000
--- a/translations/pt-BR/data/reusables/repositories/actions-new-workflow.md
+++ /dev/null
@@ -1,2 +0,0 @@
-1. In the upper-left corner, click **New workflow**. ![Criar um novo fluxo de trabalho](/assets/images/help/repository/actions-new-workflow.png)
-
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/repositories/actions-set-up-workflow-template.md b/translations/pt-BR/data/reusables/repositories/actions-set-up-workflow-template.md
deleted file mode 100644
index 39f55061e6c1..000000000000
--- a/translations/pt-BR/data/reusables/repositories/actions-set-up-workflow-template.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Sob, nome do template que você gostaria de usar, clique em **Configurar este fluxo de trabalho**. ![Node.js template recommendations](/assets/images/help/repository/actions-recommended-workflow-template.png)
diff --git a/translations/pt-BR/data/reusables/repositories/opt-out-automated-security-updates.md b/translations/pt-BR/data/reusables/repositories/opt-out-automated-security-updates.md
deleted file mode 100644
index b1379e869de4..000000000000
--- a/translations/pt-BR/data/reusables/repositories/opt-out-automated-security-updates.md
+++ /dev/null
@@ -1,2 +0,0 @@
-1. Under "Automated security updates", select or deselect **Opt out of automated security updates**. ![Checkbox to opt out of automated security updates](/assets/images/help/repository/opt-out-automated-security-updates.png)
-2. Clique em **Save** (Salvar).
diff --git a/translations/pt-BR/data/reusables/repositories/opt-out-dependabot-security-updates.md b/translations/pt-BR/data/reusables/repositories/opt-out-dependabot-security-updates.md
deleted file mode 100644
index 3a68c3c20731..000000000000
--- a/translations/pt-BR/data/reusables/repositories/opt-out-dependabot-security-updates.md
+++ /dev/null
@@ -1 +0,0 @@
-1. To the right of "{% data variables.product.prodname_dependabot_short %} security updates", click **Disable all** or **Enable all**. !["Disable all" or "Enable all" button for {% data variables.product.prodname_dependabot_short %} security updates](/assets/images/help/repository/opt-out-dependabot-security-updates.png)
diff --git a/translations/pt-BR/data/reusables/repositories/settings-security-and-analysis-tab-beta.md b/translations/pt-BR/data/reusables/repositories/settings-security-and-analysis-tab-beta.md
deleted file mode 100644
index a3664b8fbce9..000000000000
--- a/translations/pt-BR/data/reusables/repositories/settings-security-and-analysis-tab-beta.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note**: The new experience for managing security and analysis settings is in beta and subject to change.
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-integrations-and-services.md b/translations/pt-BR/data/reusables/repositories/sidebar-integrations-and-services.md
deleted file mode 100644
index a9ec167dd2d0..000000000000
--- a/translations/pt-BR/data/reusables/repositories/sidebar-integrations-and-services.md
+++ /dev/null
@@ -1 +0,0 @@
-1. Click **Integrations & Services**. ![Integrations and services selection](/assets/images/help/settings/integrations_and_services_menu.png)
diff --git a/translations/pt-BR/data/reusables/repositories/troubleshooting-dependency-graph.md b/translations/pt-BR/data/reusables/repositories/troubleshooting-dependency-graph.md
deleted file mode 100644
index 187ae99b2b9f..000000000000
--- a/translations/pt-BR/data/reusables/repositories/troubleshooting-dependency-graph.md
+++ /dev/null
@@ -1 +0,0 @@
-If your project has dependencies, but no dependencies are detected in your graph, there may be a problem with the file containing your dependencies. Check your project's file to ensure that it's correctly formatted for the file type.
diff --git a/translations/pt-BR/data/reusables/repositories/you-can-enable-or-disable-security-features.md b/translations/pt-BR/data/reusables/repositories/you-can-enable-or-disable-security-features.md
deleted file mode 100644
index ce70639e21b6..000000000000
--- a/translations/pt-BR/data/reusables/repositories/you-can-enable-or-disable-security-features.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note**: The code scanning and secret scanning beta includes a new experience for managing security and analysis settings. If you're participating in the beta, skip the following steps and see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/repositories/you-can-manage-access-to-security-alerts.md b/translations/pt-BR/data/reusables/repositories/you-can-manage-access-to-security-alerts.md
deleted file mode 100644
index f96057061471..000000000000
--- a/translations/pt-BR/data/reusables/repositories/you-can-manage-access-to-security-alerts.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note**: The code scanning and secret scanning beta includes a new experience for managing people and teams with access to security alerts. If you're participating in the beta, skip the following steps and see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-github-dependabot-alerts)."
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/saml/scim-unavailable-for-enterprise-accounts.md b/translations/pt-BR/data/reusables/saml/scim-unavailable-for-enterprise-accounts.md
deleted file mode 100644
index 91565a694a5d..000000000000
--- a/translations/pt-BR/data/reusables/saml/scim-unavailable-for-enterprise-accounts.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note**: SCIM support is not available for enterprise accounts on {% data variables.product.prodname_dotcom %} at this time.
-
-{% endnote %}
diff --git a/translations/pt-BR/data/reusables/scim/complete_user_example.md b/translations/pt-BR/data/reusables/scim/complete_user_example.md
deleted file mode 100644
index e444e167ecc8..000000000000
--- a/translations/pt-BR/data/reusables/scim/complete_user_example.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<%= json \ "schemas":["urn:ietf:params:scim:schemas:core:2.0:User"], "userName":"mona.octocat@okta.example.com", "name":{ "familyName":"Octocat", "givenName":"Mona" }, "emails":[
- {
- "value":"mona.octocat@okta.example.com",
- "type":"work",
- "primary": true
- }
- ] %>
diff --git a/translations/pt-BR/data/reusables/scim/user_required_values.md b/translations/pt-BR/data/reusables/scim/user_required_values.md
deleted file mode 100644
index ac21f8bdd71f..000000000000
--- a/translations/pt-BR/data/reusables/scim/user_required_values.md
+++ /dev/null
@@ -1 +0,0 @@
-Conforme mostrado no exemplo a seguir, você deve fornecer pelo menos os valores necessários para o usuário: `userName,` `nome` e `e-mails`.
diff --git a/translations/pt-BR/data/reusables/search/exact-match-beta.md b/translations/pt-BR/data/reusables/search/exact-match-beta.md
deleted file mode 100644
index b30a551b39f9..000000000000
--- a/translations/pt-BR/data/reusables/search/exact-match-beta.md
+++ /dev/null
@@ -1 +0,0 @@
-Exact matches in code search is in beta for a limited number of users and repositories on {% data variables.product.prodname_dotcom %}, and is subject to change.
diff --git a/translations/pt-BR/data/reusables/search/exact-match.md b/translations/pt-BR/data/reusables/search/exact-match.md
deleted file mode 100644
index d3563a1ef5db..000000000000
--- a/translations/pt-BR/data/reusables/search/exact-match.md
+++ /dev/null
@@ -1 +0,0 @@
-You can search code for exact matches that include any combination of letters, numbers, and symbols.
diff --git a/translations/pt-BR/data/reusables/shortdesc/2fa.md b/translations/pt-BR/data/reusables/shortdesc/2fa.md
deleted file mode 100644
index 6dd5d06a9ab1..000000000000
--- a/translations/pt-BR/data/reusables/shortdesc/2fa.md
+++ /dev/null
@@ -1 +0,0 @@
-Se você tiver configuração de autenticação de dois fatores, a autenticação básica para este ponto de extremidade exigirá que você use uma senha única (OTP) e seu nome de usuário e senha em vez de tokens. Para obter mais informações, consulte "[Trabalhando com autenticação de dois fatores](/v3/auth/#working-with-two-factor-authentication)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/shortdesc/content_reference_body.md b/translations/pt-BR/data/reusables/shortdesc/content_reference_body.md
deleted file mode 100644
index 4b89190d30bf..000000000000
--- a/translations/pt-BR/data/reusables/shortdesc/content_reference_body.md
+++ /dev/null
@@ -1 +0,0 @@
-You have used an email that already exists for the user_email_uniq field.\n \## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n\ self.save()
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/shortdesc/content_reference_title.md b/translations/pt-BR/data/reusables/shortdesc/content_reference_title.md
deleted file mode 100644
index 531d7aabf6de..000000000000
--- a/translations/pt-BR/data/reusables/shortdesc/content_reference_title.md
+++ /dev/null
@@ -1 +0,0 @@
-[A-1234] Error found in core/models.py file
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/sponsors/email-submit-bank-info.md b/translations/pt-BR/data/reusables/sponsors/email-submit-bank-info.md
deleted file mode 100644
index 8174c6976a84..000000000000
--- a/translations/pt-BR/data/reusables/sponsors/email-submit-bank-info.md
+++ /dev/null
@@ -1 +0,0 @@
-Depois de ingressar no {% data variables.product.prodname_sponsors %}, você receberá um e-mail com instruções para enviar suas informações bancárias e fiscais.
diff --git a/translations/pt-BR/data/reusables/sponsors/matching-period.md b/translations/pt-BR/data/reusables/sponsors/matching-period.md
deleted file mode 100644
index 885abc6217cc..000000000000
--- a/translations/pt-BR/data/reusables/sponsors/matching-period.md
+++ /dev/null
@@ -1 +0,0 @@
-Sponsorships may be eligible for matching within the limitations stated here for the first year that an individual is a participant in {% data variables.product.prodname_sponsors %}. Eligibility for matching begins after {% data variables.product.company_short %} admits an account to {% data variables.product.prodname_sponsors %}, which publishes the sponsorship profile for the account. O período de correspondência não pode ser prorrogado por nenhum motivo. If you leave {% data variables.product.prodname_sponsors %} and rejoin later, the gap between your participation periods may count toward your matching period or your matching period may expire.
diff --git a/translations/pt-BR/data/reusables/sponsors/org-sponsorship-dashboard.md b/translations/pt-BR/data/reusables/sponsors/org-sponsorship-dashboard.md
deleted file mode 100644
index dba6f85d626d..000000000000
--- a/translations/pt-BR/data/reusables/sponsors/org-sponsorship-dashboard.md
+++ /dev/null
@@ -1 +0,0 @@
-1. To the right of your organization, click **Sponsorship dashboard**. ![Sponsorship dashboard button](/assets/images/help/sponsors/org-sponsorship-dashboard.png)
diff --git a/translations/pt-BR/data/reusables/support/advanced-security-support-terms-differ.md b/translations/pt-BR/data/reusables/support/advanced-security-support-terms-differ.md
deleted file mode 100644
index 641a9b9bfa0b..000000000000
--- a/translations/pt-BR/data/reusables/support/advanced-security-support-terms-differ.md
+++ /dev/null
@@ -1 +0,0 @@
-The terms of this article do not apply to support for {% data variables.product.prodname_advanced_security %}. For more information, see "[About support for {% data variables.product.prodname_advanced_security %}](/enterprise/admin/enterprise-support/about-support-for-advanced-security)."
diff --git a/translations/pt-BR/data/reusables/support/ghec-premium-priority-high-description.md b/translations/pt-BR/data/reusables/support/ghec-premium-priority-high-description.md
deleted file mode 100644
index 2fb6383ca5f0..000000000000
--- a/translations/pt-BR/data/reusables/support/ghec-premium-priority-high-description.md
+++ /dev/null
@@ -1 +0,0 @@
-Account or security issues with your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are causing limited impact to your business.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/ghec-premium-priority-high-examples.md b/translations/pt-BR/data/reusables/support/ghec-premium-priority-high-examples.md
deleted file mode 100644
index 84787e3af0ab..000000000000
--- a/translations/pt-BR/data/reusables/support/ghec-premium-priority-high-examples.md
+++ /dev/null
@@ -1 +0,0 @@
-- An organization or enterprise owner has unintentionally deleted an organization
- An organization or enterprise member has uploaded sensitive data in a commit, issue, pull request, or issue attachment
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/ghec-premium-priority-low-description.md b/translations/pt-BR/data/reusables/support/ghec-premium-priority-low-description.md
deleted file mode 100644
index bc2c96abf597..000000000000
--- a/translations/pt-BR/data/reusables/support/ghec-premium-priority-low-description.md
+++ /dev/null
@@ -1 +0,0 @@
-You have a question or suggestion about your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} that is not time-sensitive, or does not otherwise block the productivity of your team.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/ghec-premium-priority-low-examples.md b/translations/pt-BR/data/reusables/support/ghec-premium-priority-low-examples.md
deleted file mode 100644
index 7d322090b60a..000000000000
--- a/translations/pt-BR/data/reusables/support/ghec-premium-priority-low-examples.md
+++ /dev/null
@@ -1 +0,0 @@
-- Excessive resource usage for your organization or enterprise
- Requests for health checks
- Help with using Gists, notifications, wikis, {% data variables.product.prodname_pages %}, {% data variables.product.prodname_desktop %}, Atom, or other peripheral services or features with your organization or enterprise
- Feature requests
- Product feedback
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/ghec-premium-priority-normal-description.md b/translations/pt-BR/data/reusables/support/ghec-premium-priority-normal-description.md
deleted file mode 100644
index 6d9c3cf6cdd1..000000000000
--- a/translations/pt-BR/data/reusables/support/ghec-premium-priority-normal-description.md
+++ /dev/null
@@ -1 +0,0 @@
-Members of your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are experiencing limited or moderate issues with {% data variables.product.prodname_dotcom_the_website %}, or you have general concerns or questions about your organization or enterprise.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/ghec-premium-priority-normal-examples.md b/translations/pt-BR/data/reusables/support/ghec-premium-priority-normal-examples.md
deleted file mode 100644
index c3e8a6d79611..000000000000
--- a/translations/pt-BR/data/reusables/support/ghec-premium-priority-normal-examples.md
+++ /dev/null
@@ -1 +0,0 @@
-- Questions about using APIs and features for your organization or enterprise
- Issues with tools for organization data migration that {% data variables.product.company_short %} provides
- Features related to your organization or enterprise not working as expected
- General security questions about your organization or enterprise
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/ghec-premium-priority-urgent-description.md b/translations/pt-BR/data/reusables/support/ghec-premium-priority-urgent-description.md
deleted file mode 100644
index 73fccecb886c..000000000000
--- a/translations/pt-BR/data/reusables/support/ghec-premium-priority-urgent-description.md
+++ /dev/null
@@ -1 +0,0 @@
-Production workflows for your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are failing due to critical service errors or outages, and the failure directly impacts the operation of your business.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/ghec-premium-priority-urgent-examples.md b/translations/pt-BR/data/reusables/support/ghec-premium-priority-urgent-examples.md
deleted file mode 100644
index e9eee27296cb..000000000000
--- a/translations/pt-BR/data/reusables/support/ghec-premium-priority-urgent-examples.md
+++ /dev/null
@@ -1 +0,0 @@
-- Errors or outages on {% data variables.product.prodname_dotcom_the_website %} affect core Git or web application functionality for all members of your organization or enterprise
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/github-one-premium-plus-response-times-differ.md b/translations/pt-BR/data/reusables/support/github-one-premium-plus-response-times-differ.md
deleted file mode 100644
index 2d2f85fe5300..000000000000
--- a/translations/pt-BR/data/reusables/support/github-one-premium-plus-response-times-differ.md
+++ /dev/null
@@ -1 +0,0 @@
-For customers who purchase {% data variables.product.prodname_ghe_one %}, support for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_insights %}, {% data variables.product.prodname_learning %}, and {% data variables.product.prodname_registry %} is available 24 hours a day, 5 days per week, excluding weekends and national U.S. holidays. The standard response time is 1 business day.
diff --git a/translations/pt-BR/data/reusables/support/github-one-premium-plus-sla-differs.md b/translations/pt-BR/data/reusables/support/github-one-premium-plus-sla-differs.md
deleted file mode 100644
index 19e43b397b04..000000000000
--- a/translations/pt-BR/data/reusables/support/github-one-premium-plus-sla-differs.md
+++ /dev/null
@@ -1 +0,0 @@
-For customers who purchase {% data variables.product.prodname_ghe_one %}, the SLA for initial response time by {% data variables.contact.premium_support %} does not apply to tickets for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_insights %}, {% data variables.product.prodname_learning %}, or {% data variables.product.prodname_registry %}.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/support/github-one-premium-plus-support-terms-differ.md b/translations/pt-BR/data/reusables/support/github-one-premium-plus-support-terms-differ.md
deleted file mode 100644
index c0712065ee8f..000000000000
--- a/translations/pt-BR/data/reusables/support/github-one-premium-plus-support-terms-differ.md
+++ /dev/null
@@ -1 +0,0 @@
-For customers who purchase {% data variables.product.prodname_ghe_one %}, support terms for the {% data variables.product.premium_plus_support_plan %} differ for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_insights %}, {% data variables.product.prodname_learning %}, and {% data variables.product.prodname_registry %}.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/teams/team-sync.md b/translations/pt-BR/data/reusables/teams/team-sync.md
deleted file mode 100644
index 88da0da1d1bd..000000000000
--- a/translations/pt-BR/data/reusables/teams/team-sync.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
- **Observação:** Quando você tiver configurado a sincronização da equipe para uma equipe com o provedor de identidade (IdP) da sua organização, você receberá uma mensagem de erro se tentar usar a API para fazer alterações na associação da equipe. Se você tiver acesso para administrar a associação do grupo em seu IdP, você pode administrar a associação da equipe do GitHub através do seu provedor de identidade, que adiciona e remove automaticamente os integrantes da equipe em uma organização. Para obter mais informações, consulte "[Sincronizar equipes entre seu provedor de identidade e o GitHub](/articles/synchronizing-teams-between-your-identity-provider-and-github/)".
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/user-settings/throttling-notice.md b/translations/pt-BR/data/reusables/user-settings/throttling-notice.md
deleted file mode 100644
index 5c6c03b83b26..000000000000
--- a/translations/pt-BR/data/reusables/user-settings/throttling-notice.md
+++ /dev/null
@@ -1 +0,0 @@
-Este ponto de extremidade aciona [notificações](/articles/about-notifications/). A criação muito rápida de conteúdo usando esse ponto final pode resultar em abuso do limite de taxa. See "[Abuse rate limits](/v3/#abuse-rate-limits)"{% if currentVersion == "free-pro-team@latest" %} and "[Dealing with abuse rate limits](/v3/guides/best-practices-for-integrators/#dealing-with-abuse-rate-limits)"{% endif %} for details.
diff --git a/translations/pt-BR/data/reusables/webhooks/interactive_component_short_desc.md b/translations/pt-BR/data/reusables/webhooks/interactive_component_short_desc.md
deleted file mode 100644
index 6ec63523f5cd..000000000000
--- a/translations/pt-BR/data/reusables/webhooks/interactive_component_short_desc.md
+++ /dev/null
@@ -1 +0,0 @@
-Triggered when a user clicks an interactive element that was created using the {% data variables.product.prodname_component_kit %}. {% data variables.product.prodname_github_app %}s are automatically subscribed to the `interactive_component` event so there's no need to manually subscribe to this event. Unlike other webhook events, the `interactive_component` event is only sent to the {% data variables.product.prodname_github_app %} that a user interacted with through an interactive component, such as in a composable comment. {% data variables.product.prodname_oauth_app %}s cannot subscribe to the `interactive_component` event and other installed {% data variables.product.prodname_github_app %}s will not receive the webhook event even if they subscribed to `interactive_component`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/webhooks/issue_comment_event_api_properties.md b/translations/pt-BR/data/reusables/webhooks/issue_comment_event_api_properties.md
deleted file mode 100644
index f9b7830f5b75..000000000000
--- a/translations/pt-BR/data/reusables/webhooks/issue_comment_event_api_properties.md
+++ /dev/null
@@ -1,3 +0,0 @@
-| Tecla | Tipo | Descrição |
-| ------ | -------- | ---------------------------------------------------------------------- |
-| `Ação` | `string` | The action that was performed on the comment. Can be one of `created`. |
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/webhooks/package_short_desc.md b/translations/pt-BR/data/reusables/webhooks/package_short_desc.md
deleted file mode 100644
index 9b2e7ed32efb..000000000000
--- a/translations/pt-BR/data/reusables/webhooks/package_short_desc.md
+++ /dev/null
@@ -1 +0,0 @@
-Activity related to GitHub Packages. {% data reusables.webhooks.action_type_desc %} For more information, see "[GitHub Packages](/packages)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_forked_repos_link.md b/translations/pt-BR/data/reusables/webhooks/pull_request_forked_repos_link.md
deleted file mode 100644
index 0fad1bebc3a1..000000000000
--- a/translations/pt-BR/data/reusables/webhooks/pull_request_forked_repos_link.md
+++ /dev/null
@@ -1 +0,0 @@
-See [below](#pull-request-events-for-forked-repositories) to learn how this event works with forked repositories.
\ No newline at end of file
diff --git a/translations/pt-BR/data/variables/ant-man.yml b/translations/pt-BR/data/variables/ant-man.yml
deleted file mode 100644
index fd9020681ae1..000000000000
--- a/translations/pt-BR/data/variables/ant-man.yml
+++ /dev/null
@@ -1,3 +0,0 @@
----
-deployments-ant-man-parameter-note: >-
- {% if currentVersion == "free-pro-team@latest" %}**Note:** This parameter requires you to use the [`application/vnd.github.ant-man-preview+json`](/v3/previews/#enhanced-deployments) custom media type.{% endif %}
diff --git a/translations/pt-BR/data/variables/cloud-9.yml b/translations/pt-BR/data/variables/cloud-9.yml
deleted file mode 100644
index 514cc607691b..000000000000
--- a/translations/pt-BR/data/variables/cloud-9.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The SCIM API
diff --git a/translations/pt-BR/data/variables/giant-sentry-fist.yml b/translations/pt-BR/data/variables/giant-sentry-fist.yml
deleted file mode 100644
index ae3a16bbeb72..000000000000
--- a/translations/pt-BR/data/variables/giant-sentry-fist.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The User Blocking API
diff --git a/translations/pt-BR/data/variables/korra.yml b/translations/pt-BR/data/variables/korra.yml
deleted file mode 100644
index a0e37a535b50..000000000000
--- a/translations/pt-BR/data/variables/korra.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The Organization Membership API
diff --git a/translations/pt-BR/data/variables/mercy.yml b/translations/pt-BR/data/variables/mercy.yml
deleted file mode 100644
index 0076f284e63b..000000000000
--- a/translations/pt-BR/data/variables/mercy.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The `topics` property for repositories
diff --git a/translations/pt-BR/data/variables/mister-fantastic.yml b/translations/pt-BR/data/variables/mister-fantastic.yml
deleted file mode 100644
index 5040343f790d..000000000000
--- a/translations/pt-BR/data/variables/mister-fantastic.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The GitHub Pages API
diff --git a/translations/pt-BR/data/variables/performed-via-integration.yml b/translations/pt-BR/data/variables/performed-via-integration.yml
deleted file mode 100644
index c2d523e86a75..000000000000
--- a/translations/pt-BR/data/variables/performed-via-integration.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: An additional `performed_via_github_app` object in the issue payload
diff --git a/translations/pt-BR/data/variables/valkyrie.yml b/translations/pt-BR/data/variables/valkyrie.yml
deleted file mode 100644
index 7b921d5113e1..000000000000
--- a/translations/pt-BR/data/variables/valkyrie.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The GitHub Marketplace API
diff --git a/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/about-continuous-integration.md b/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/about-continuous-integration.md
deleted file mode 100644
index 95f632767337..000000000000
--- a/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/about-continuous-integration.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: 关于持续集成
-intro: '您可以直接在 {% data variables.product.prodname_dotcom %} 仓库中通过 {% data variables.product.prodname_actions %} 创建自定义持续集成 (CI) 和持续部署 (CD) 工作流程。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /articles/about-continuous-integration
- - /github/automating-your-workflow-with-github-actions/about-continuous-integration
- - /actions/automating-your-workflow-with-github-actions/about-continuous-integration
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于持续集成
-
-持续集成 (CI) 是一种需要频繁提交代码到共享仓库的软件实践。 频繁提交代码能较早检测到错误,减少在查找错误来源时开发者需要调试的代码量。 频繁的代码更新也更便于从软件开发团队的不同成员合并更改。 这对开发者非常有益,他们可以将更多时间用于编写代码,而减少在调试错误或解决合并冲突上所花的时间。
-
-提交代码到仓库时,可以持续创建并测试代码,以确保提交未引入错误。 您的测试可以包括代码语法检查(检查样式格式)、安全性检查、代码覆盖率、功能测试及其他自定义检查。
-
-创建和测试代码需要服务器。 您可以在推送代码到仓库之前在本地创建并测试更新,也可以使用 CI 服务器检查仓库中的新代码提交。
-
-### 关于使用 {% data variables.product.prodname_actions %} 的持续集成
-
-使用 {% data variables.product.prodname_actions %} 的 CI 提供可以在仓库中构建代码并运行测试的工作流程。 工作流程可在 {% data variables.product.prodname_dotcom %} 托管的虚拟机或您自行托管的机器上运行。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)”和“[关于自托管运行器](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。
-
-您可以配置 CI 工作流程在 {% data variables.product.product_name %} 事件发生时运行(例如,当新代码推送到您的仓库时)、按设定的时间表运行,或者在使用仓库分发 web 挂钩的外部事件发生时运行。
-
-{% data variables.product.product_name %} 运行 CI 测试并在拉取请求中提供每次测试的结果,因此您可以查看分支中的更改是否引入错误。 如果工作流程中的所有 CI 测试通过,您推送的更改可供团队成员审查或合并 如果测试失败,则是其中某项更改导致了失败。
-
-如果在仓库中设置了 CI,{% data variables.product.product_name %} 会分析仓库中的代码,并根据仓库中的语言和框架推荐 CI 工作流程。 例如,如果您使用 [Node.js](https://nodejs.org/en/),{% data variables.product.product_name %} 将提议使用模板文件来安装 Node.js 包和运行测试。 您可以使用 {% data variables.product.product_name %} 提议的 CI 工作流程模板,自定义提议的模板,或者创建自定义工作流程文件来运行 CI 测试。
-
-![提议的持续集成模板截屏](/assets/images/help/repository/ci-with-actions-template-picker.png)
-
-除了帮助设置项目的 CI 工作流程之外,您还可以使用 {% data variables.product.prodname_actions %} 创建跨整个软件开发生命周期的工作流程。 例如,您可以使用操作来部署、封装或发行项目。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %}](/articles/about-github-actions)”。
-
-有关常用术语的定义,请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)”。
-
-### 支持的语言
-
-{% data variables.product.product_name %} 提供各种不同语言和框架的 CI 工作流程模板。
-
-更多信息请参阅“[配置工作流程](/articles/configuring-a-workflow)。
-
-### 工作流程运行通知
-
-{% data reusables.repositories.workflow-notifications %}
-
-### 工作流程运行的状态徽章
-
-{% data reusables.repositories.actions-workflow-status-badge-into %}
-
-更多信息请参阅“[配置工作流程](/articles/configuring-a-workflow)。
-
-### 延伸阅读
-
-- "[使用 {% data variables.product.prodname_actions %} 设置持续集成](/articles/setting-up-continuous-integration-using-github-actions)"
-{% if currentVersion == "free-pro-team@latest" %}
-- "[管理 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)"
-{% endif %}
diff --git a/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/index.md b/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/index.md
deleted file mode 100644
index bf6140c3f151..000000000000
--- a/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/index.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: 通过持续集成构建和测试代码
-shortTitle: 持续集成
-intro: '您可以使用 {% data variables.product.prodname_actions %} 在仓库中创建自定义持续集成 (CI) 和持续部署 (CD) 工作流程。'
-redirect_from:
- - /articles/setting-up-continuous-integration-on-github
- - /github/automating-your-workflow-with-github-actions/setting-up-continuous-integration-on-github
- - /github/automating-your-workflow-with-github-actions/creating-continuous-integration-workflows
- - /actions/automating-your-workflow-with-github-actions/creating-continuous-integration-workflows
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% link_in_list /about-continuous-integration %}
-{% link_in_list /setting-up-continuous-integration-using-github-actions %}
diff --git a/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/setting-up-continuous-integration-using-github-actions.md b/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/setting-up-continuous-integration-using-github-actions.md
deleted file mode 100644
index 327a3556c7c3..000000000000
--- a/translations/zh-CN/content/actions/building-and-testing-code-with-continuous-integration/setting-up-continuous-integration-using-github-actions.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: 使用 GitHub 操作设置持续集成
-intro: 您可以使用与您要用的语言和工具匹配的工作流程模板为项目设置持续集成。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /articles/setting-up-continuous-integration-using-github-actions
- - /github/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
- - /actions/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-对仓库具有写入权限的任何人都可以使用 {% data variables.product.prodname_actions %} 设置持续集成 (CI)。
-
-在设置 CI 后,可以根据您的需求自定义工作流程。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-3. 找到与您要用的语言和工具匹配的模板,然后单击 **Set up this workflow(设置此工作流程)**。 ![设置工作流程按钮](/assets/images/help/repository/setup-workflow-button.png)
-5. 单击 **Start commit(开始提交)**。 ![开始提交按钮](/assets/images/help/repository/start-commit.png)
-{% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %}
-{% data reusables.files.propose_new_file %}
-
-在推送到仓库后,您可以在 {% data variables.product.prodname_dotcom %} 上跟踪持续集成工作流程运行的状态和详细日志,并接收自定义的通知。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)”和“[管理工作流程运行](/articles/managing-a-workflow-run)”。
-
-{% data reusables.repositories.actions-workflow-status-badge-into %}
-
-更多信息请参阅“[配置工作流程](/articles/configuring-a-workflow)。
-
-### 延伸阅读
-
-- "[关于持续集成](/articles/about-continuous-integration)"
-- "[管理工作流程运行](/articles/managing-a-workflow-run)"
-{% if currentVersion == "free-pro-team@latest" %}
-- "[管理 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)"
-{% endif %}
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/about-service-containers.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/about-service-containers.md
deleted file mode 100644
index fe902cc99dac..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/about-service-containers.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: 关于服务容器
-intro: 您可以使用服务容器将数据库、网络服务、内存缓存及其他工具连接到您的工作流程。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/about-service-containers
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于服务容器
-
-服务容器是 Docker 容器,以简便、可携带的方式托管您可能需要在工作流程中测试或操作应用程序的服务。 例如,您的工作流程可能必须运行需要访问数据库和内存缓存的集成测试。
-
-您可以为工作流程中的每个作业配置服务容器。 {% data variables.product.prodname_dotcom %} 为工作流中配置的每个服务创建一个新的 Docker 容器,并在作业完成后销毁该服务容器。 作业中的步骤可与属于同一作业的所有服务容器通信。
-
-{% data reusables.github-actions.docker-container-os-support %}
-
-### 与服务容器通信
-
-您可以在工作流程中配置作业直接在运行器机器或 Docker 容器上运行。 作业与其服务容器之间的通信根据作业是直接在运行器上运行还是在容器中运行而有所不同。
-
-#### 在容器中运行作业
-
-在容器中运行作业时,{% data variables.product.prodname_dotcom %} 使用 Docker 的用户定义桥接网络将服务容器连接到作业。 更多信息请参阅 Docker 文档中的“[使用桥接网络](https://docs.docker.com/network/bridge/)”。
-
-在容器中运行作业和服务可简化网络访问。 您可以使用工作流程中配置的标签访问服务容器。 服务容器的主机名自动映射到标签名称。 例如,如果您创建带有标签 `redis` 的服务容器 ,则该服务容器的主机名是 `redis`。
-
-您无需为服务容器配置任何端口。 默认情况下,属于同一 Docker 网络的所有容器会相互显示所有端口,但在 Docker 网络外部不会显示任何端口。
-
-#### 在运行器机器上运行作业
-
-直接在运行器机器上运行作业时,您可以使用 `localhost:` 或 `127.0.0.1:` 访问服务容器。 {% data variables.product.prodname_dotcom %} 配置容器网络以启用从服务容器到 Docker 主机的通信。
-
-当作业直接在运行器机器上运行时, Docker 容器中运行的服务默认情况下不会向运行器上的作业显示其端口。 您需要将服务容器上的端口映射到 Docker 主机。 更多信息请参阅“[映射 Docker 主机和服务容器端口](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。
-
-### 创建服务容器
-
-您可以使用 `services` 关键字创建服务容器作为工作流程中作业的一部分。 更多信息请参阅 [`jobs..services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices)。
-
-本例在作业 `container-job` 中创建一个名为 `redis` 的服务。 本例中的 Docker 主机是 `node:10.18-jessie` 容器。
-
-{% raw %}
-```yaml
-name: Redis container example
-on: push
-
-jobs:
- # Label of the container job
- container-job:
- # Containers must run in Linux based operating systems
- runs-on: ubuntu-latest
- # Docker Hub image that `container-job` executes in
- container: node:10.18-jessie
-
- # Service containers to run with `container-job`
- services:
- # Label used to access the service container
- redis:
- # Docker Hub image
- image: redis
-```
-{% endraw %}
-
-### 映射 Docker 主机和服务容器端口
-
-如果作业在 Docker 容器中运行,则不需要映射主机或服务容器上的端口。 如果作业直接在运行器机器上运行,则需要将任何必需的服务容器端口映射到主机运行器机器上的端口。
-
-您可以使用 `ports` 关键字将服务容器端口映射到 Docker 主机。 更多信息请参阅 [`jobs..services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices)。
-
-| `ports` 的值 | 描述 |
-| ------------- | -------------------------------------------- |
-| `8080:80` | 将容器中的 TCP 端口 80 映射到 Docker 主机上的端口 8080。 |
-| `8080:80/udp` | 将容器中的 UDP 端口 80 映射到 Docker 主机上的端口 8080。 |
-| `8080/udp` | 将容器中随机选择的 UDP 端口映射到 Docker 主机上的 UDP 端口 8080。 |
-
-使用 `ports` 关键字映射端口时,{% data variables.product.prodname_dotcom %} 使用 `--publish` 命令将容器的端口发布到 Docker 主机。 更多信息请参阅 Docker 文档中的“[Docker 容器网络](https://docs.docker.com/config/containers/container-networking/)”。
-
-指定 Docker 主机端口但不指定容器端口时,容器端口将随机分配给空闲端口。 {% data variables.product.prodname_dotcom %} 在服务容器上下文中设置分配的容器端口。 例如,对于 `redis` 服务容器,如果您配置了 Docker 主机端口 5432,则您可以使用 `job.services.redis.ports[5432]` 上下文访问对应的容器端口。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions#job-context)”。
-
-#### 映射 Redis 端口的示例
-
-此示例映射服务容器 `redis` 端口 6379 到 Docker 主机端口 6379。
-
-{% raw %}
-```yaml
-name: Redis Service Example
-on: push
-
-jobs:
- # Label of the container job
- runner-job:
- # You must use a Linux environment when using service containers or container jobs
- runs-on: ubuntu-latest
-
- # Service containers to run with `runner-job`
- services:
- # Label used to access the service container
- redis:
- # Docker Hub image
- image: redis
- #
- ports:
- # Opens tcp port 6379 on the host and service container
- - 6379:6379
-```
-{% endraw %}
-
-### 延伸阅读
-
-- "[创建 Redis 服务容器](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)"
-- "[创建 PostgreSQL 服务容器](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)"
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/authenticating-with-the-github_token.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/authenticating-with-the-github_token.md
deleted file mode 100644
index 6fd6bfc808fc..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/authenticating-with-the-github_token.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: 使用 `GITHUB_TOKEN` 进行身份验证
-intro: '{% data variables.product.prodname_dotcom %} 提供一个令牌,可用于代表 {% data variables.product.prodname_actions %} 进行身份验证。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /github/automating-your-workflow-with-github-actions/authenticating-with-the-github_token
- - /actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-对仓库具有 `write` 权限的任何人都可以创建、读取和使用密码。
-
-### 关于 `GITHUB_TOKEN` 密码
-
-{% data variables.product.prodname_dotcom %} 会自动创建 `GITHUB_TOKEN` 密码以在工作流程中使用。 您可以使用 `GITHUB_TOKEN` 在工作流程运行中进行身份验证。
-
-当您启用 {% data variables.product.prodname_actions %} 时,{% data variables.product.prodname_dotcom %} 在您的仓库中安装 {% data variables.product.prodname_github_app %}。 `GITHUB_TOKEN` 密码是一种 {% data variables.product.prodname_github_app %} 安装访问令牌。 您可以使用安装访问令牌代表仓库中安装的 {% data variables.product.prodname_github_app %} 进行身份验证。 令牌的权限仅限于包含您的工作流程的仓库。 更多信息请参阅“[`GITHUB_TOKEN`](#permissions-for-the-github_token) 的权限”。
-
-在每个作业开始之前, {% data variables.product.prodname_dotcom %} 将为作业提取安装访问令牌。 令牌在作业完成后过期。
-
-令牌在 `github.token` 上下文中也可用。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)”。
-
-### 在工作流程中使用 `GITHUB_TOKEN`
-
-要使用 `GITHUB_TOKEN` 密码,必须在工作流程文件中引用它。 使用令牌可能包括将令牌作为输入传递给需要该令牌的操作,或进行经过身份验证的 {% data variables.product.prodname_dotcom %} API 调用。
-
-{% data reusables.github-actions.actions-do-not-trigger-workflows %}
-
-#### 将 `GITHUB_TOKEN` 作为输入传递的示例
-
-此示例工作流程使用[贴标器操作](https://github.com/actions/labeler),需要 `GITHUB_TOKEN` 作为 `repo-token` 输入参数的值:
-
- {% raw %}
- ```yaml
- name: Pull request labeler
- on:
- - pull_request
- jobs:
- triage:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/labeler@v2
- with:
- repo-token: ${{ secrets.GITHUB_TOKEN }}
- ```
- {% endraw %}
-
-#### 调用 REST API 的示例
-
-您可以使用 `GITHUB_TOKEN` 进行经过验证的 API 调用。 此示例工作流程使用 {% data variables.product.prodname_dotcom %} REST API 创建议题:
-
- {% raw %}
- ```yaml
- name: Create issue on commit
- on:
- - push
- jobs:
- create_commit:
- runs-on: ubuntu-latest
- steps:
- - name: Create issue using REST API
- run: |
- curl --request POST \
- --url https://api.github.com/repos/${{ github.repository }}/issues \
- --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
- --header 'content-type: application/json' \
- --data '{
- "title": "Automated issue for commit: ${{ github.sha }}",
- "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n 提交哈希是: _${{ github.sha }}_"
- }'
- ```
- {% endraw %}
-
-### `GITHUB_TOKEN` 的权限
-
-有关 {% data variables.product.prodname_github_apps %} 可通过各种权限访问的 API 端点的信息,请参阅“[{% data variables.product.prodname_github_app %} 权限](/v3/apps/permissions/)”。
-
-| 权限 | 访问类型 | 通过复刻的仓库访问 |
-| -------- | ---- | --------- |
-| 操作 | 读/写 | 读取 |
-| 检查 | 读/写 | 读取 |
-| 内容 | 读/写 | 读取 |
-| 部署 | 读/写 | 读取 |
-| issues | 读/写 | 读取 |
-| 元数据 | 读取 | 读取 |
-| 包 | 读/写 | 读取 |
-| 拉取请求 | 读/写 | 读取 |
-| 仓库项目 | 读/写 | 读取 |
-| statuses | 读/写 | 读取 |
-
-如果您需要的令牌需要 `GITHUB_TOKEN` 中未提供的权限,您可以创建个人访问令牌并将其设置为仓库中的密码:
-
-1. 使用或创建具有该仓库适当权限的令牌。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
-1. 添加令牌作为工作流程仓库中的密码,然后使用 {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} 语法进行引用。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/caching-and-storing-workflow-data.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/caching-and-storing-workflow-data.md
deleted file mode 100644
index 75e7feb0763b..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/caching-and-storing-workflow-data.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 缓存和存储工作流程数据
-intro: 缓存依赖项和存储构件以提高工作流程运行效率。
-mapTopic: true
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows.md
deleted file mode 100644
index b1fbc5c5174b..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows.md
+++ /dev/null
@@ -1,190 +0,0 @@
----
-title: 缓存依赖项以加快工作流程
-intro: 为了使工作流程更快、更高效,可以为依赖项及其他经常重复使用的文件创建和使用缓存。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
- - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
-versions:
- free-pro-team: '*'
----
-
-### 关于缓存工作流程依赖项
-
-工作流程运行通常在不同运行之间重新使用相同的输出或下载的依赖项。 例如,Maven、Gradle、npm 和 Yarn 等软件包和依赖项管理工具都会对下载的依赖项保留本地缓存。
-
-{% data variables.product.prodname_dotcom %} 托管的运行器在一个干净的虚拟环境中启动,每次都必须下载依赖项,造成网络利用率提高、运行时间延长和成本增加。 为帮助加快重新创建这些文件,{% data variables.product.prodname_dotcom %} 可以缓存您在工作流程中经常使用的依赖项。
-
-要缓存作业的依赖项,您需要使用 {% data variables.product.prodname_dotcom %} 的 `cache` 操作。 该操作检索由唯一键标识的缓存。 更多信息请参阅 [`actions/cache`](https://github.com/actions/cache)。
-
-{% warning %}
-
-**警告**:建议不要在公共仓库缓存中存储任何敏感信息。 例如,敏感信息可以包括存储在缓存路径的文件中的访问令牌或登录凭据。 此外,命令行接口 (CLI) 程序,例如 `docker login`,可以在配置文件中保存访问凭据。 具有读取访问权限的任何人都可以在仓库上创建拉取请求并访问缓存的内容。 仓库的复刻也可在基本分支上创建拉取请求,并在基本分支上访问缓存。
-
-{% endwarning %}
-
-### 比较构件和依赖项缓存
-
-构件与缓存类似,因为它们能够在 {% data variables.product.prodname_dotcom %} 上存储文件,但每项功能都提供不同的用例,不能互换使用。
-
-- 如果要在作业或工作流程运行之间重复使用不经常更改的文件,请使用缓存。
-- 如果要保存作业生成的文件,以便在工作流程结束后查看,则使用构件。 更多信息请参阅“[使用构件持久化工作流程](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
-
-### 访问缓存的限制
-
-使用 `cache` 操作的 `v2`,可以访问具有 `GITHUB_REF` 的任何事件所触发的工作流程中的缓存。 如果使用 `cache` 操作的 `v1`,您只能访问由 `push` 和 `pull_request` 事件触发的工作流程中的缓存,`pull_request` `closed` 事件除外。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。
-
-工作流程可以访问和还原当前分支、基础分支(包括复刻的仓库的基本分支)或默认分支(通常是 `master`)中创建的缓存 例如,在默认分支 `master` 上创建的缓存可从任何拉取请求访问。 另外,如果分支 `feature-b` 具有基础分支 `feature-a`,则触发于 `feature-b` 的工作流程可以访问默认分支 (`master`)、`feature-a` 和 `feature-b` 中创建的缓存。
-
-访问限制通过在不同工作流程和分支之间创建逻辑边界来提供缓存隔离和安全。 例如, 为分支 `feature-a`(具有基础分支 `master`)创建的缓存将无法访问分支 `feature-b`(具有基础分支 `master`)的拉取请求。
-
-### 使用 `cache` 操作
-
-`cache` 操作将尝试恢复基于您提供的 `key` 的缓存。 当操作找到缓存时,该操作会将缓存的文件还原到您配置的 `path`。
-
-如果没有精确匹配,操作在作业成功完成时将创建一个新的缓存条目。 新缓存将使用您提供的 `key` 并包含 `path` 目录中的文件。
-
-当 `key` 与现有缓存不匹配时,您可以选择性提供要使用的 `restore-keys` 列表。 `restore-keys` 列表很有用,因为 `restore-keys` 可以部分匹配缓存密钥。 有关匹配 `restore-keys` 的更多信息,请参阅“[匹配缓存密钥](#matching-a-cache-key)”。
-
-更多信息请参阅 [`actions/cache`](https://github.com/actions/cache)。
-
-#### `cache` 操作的输入参数
-
-- `key`:**必要** 保存缓存时创建的键,以及用于搜索缓存的键。 可以是变量、上下文值、静态字符串和函数的任何组合。 密钥最大长度为 512 个字符,密钥长度超过最大长度将导致操作失败。
-- `path`:**必要** 运行器上缓存或还原的文件路径。 路径可以是绝对路径或相对于工作目录的路径。
- - 使用 `cache` 操作的 `v2`,可以指定单个路径,或将多个路径指定为列表。 路径可以是目录或单个文件,并且支持 glob 模式。
- - 对于 `cache` 操作的 `v1`,仅支持单个路径,它必须是一个目录。 您不能缓存单个文件。
-- `restore-keys`:**可选** `key` 没有发生缓存命中时用于查找缓存的其他密钥顺序列表。
-
-#### `cache` 操作的输出参数
-
-- `cache-hit`:表示找到了密钥的精确匹配项的布尔值。
-
-#### `cache` 操作使用示例
-
-此示例在 `package-lock.json` 文件中的包更改时,或运行器的操作系统更改时,创建一个新的缓存。 缓存键使用上下文和表达式生成一个键值,其中包括运行器的操作系统和 `package-lock.json` 文件的 SHA-256 哈希。
-
-{% raw %}
-```yaml
-name: Caching with npm
-
-on: push
-
-jobs:
- build:
- runs-on: ubuntu-latest
-
- steps:
- - uses: actions/checkout@v2
-
- - name: Cache node modules
- uses: actions/cache@v2
- env:
- cache-name: cache-node-modules
- with:
- # npm cache files are stored in `~/.npm` on Linux/macOS
- path: ~/.npm
- key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
- restore-keys: |
- ${{ runner.os }}-build-${{ env.cache-name }}-
- ${{ runner.os }}-build-
- ${{ runner.os }}-
-
- - name: Install Dependencies
- run: npm install
-
- - name: Build
- run: npm build
-
- - name: Test
- run: npm test
-
-```
-{% endraw %}
-
-当 `key` 匹配现有缓存时,被称为缓存命中,并且操作会将缓存的文件还原到 `path` 目录。
-
-当 `key` 不匹配现有缓存时,则被称为缓存错过,在作业成功完成时将创建一个新缓存。 发生缓存错过时,操作将搜索称为 `restore-keys` 的替代键值。
-
-1. 如果您提供 `restore-keys`,`cache` 操作将按顺序搜索与 `restore-keys` 列表匹配的任何缓存。
- - 当精确匹配时,操作会将缓存中的文件恢复至 `path` 目录。
- - 如果没有精确匹配,操作将会搜索恢复键值的部分匹配。 当操作找到部分匹配时,最近的缓存将恢复到 `path` 目录。
-1. `cache` 操作完成,作业中的下一个工作流程步骤运行。
-1. 如果作业成功完成,则操作将创建一个包含 `path` 目录内容的新缓存。
-
-要在多个目录中缓存文件,您需要一个对每个目录使用 [`cache`](https://github.com/actions/cache) 操作的步骤。 创建缓存后,无法更改现有缓存的内容,但可以使用新键创建新缓存。
-
-#### 使用上下文创建缓存键
-
-缓存键可以包括 {% data variables.product.prodname_actions %} 支持的任何上下文、函数、文本和运算符。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。
-
-使用表达式创建 `key` 允许您在依赖项更改时自动创建新缓存。 例如,您可以使用计算 npm `package-lock.json` 文件哈希的表达式创建 `key`。
-
-{% raw %}
-```
-npm-${{ hashFiles('package-lock.json') }}
-```
-{% endraw %}
-
-{% data variables.product.prodname_dotcom %} 评估表达式 `hash "package-lock.json"` 以派生最终 `key`。
-
-```
-npm-d5ea0750
-```
-
-### 匹配缓存键
-
-`cache` 操作会先在包含工作流程运行的分支中搜索 `key` 和 `restore-key` 的缓存命中。 如果当前分支中没有命中,`cache` 操作将在父分支和上游分支中搜索 `key` 和 `restore-keys`。
-
-您可以提供一个出现 `key` 缓存错过时使用的恢复键列表。 您可以创建从最具体到最不具体的多个恢复键。 `cache` 操作按顺序搜索 `restore-keys`。 当键不直接匹配时,操作将搜索以恢复键为前缀的键。 如果恢复键值有多个部分匹配项,操作将返回最近创建的缓存。
-
-#### 使用多个恢复键值的示例
-
-{% raw %}
-```
-restore-keys: |
- npm-foobar-${{ hashFiles('package-lock.json') }}
- npm-foobar-
- npm-
-```
-{% endraw %}
-
-运行器将评估表达式,解析为以下 `restore-keys`:
-
-{% raw %}
-```
-restore-keys: |
- npm-foobar-d5ea0750
- npm-foobar-
- npm-
-```
-{% endraw %}
-
-恢复键值 `npm-foobar-` 与任何以字符串 `npm-foobar-` 开头的键值匹配。 例如,键值 `npm-foobar-fd3052de` 和 `npm-foobar-a9b253ff` 都与恢复键值匹配。 将使用创建日期最新的缓存。 此示例中的键值按以下顺序搜索:
-
-1. **`npm-foobar-d5ea0750`** 匹配特定的哈希。
-1. **`npm-foobar-`** 匹配前缀为 `npm-foobar-` 的缓存键值。
-1. **`npm-`** 匹配前缀为 `npm-` 的任何键值。
-
-##### 搜索优先级示例
-
-```yaml
-key:
- npm-feature-d5ea0750
-restore-keys: |
- npm-feature-
- npm-
-```
-
-例如,如果拉取请求包含 `feature` 分支(当前范围)并针对默认分支 (`master`),操作将按以下顺序搜索 `key` 和 `restore-keys`:
-
-1. `feature` 分支范围中的键值 `npm-feature-d5ea0750`
-1. `feature` 分支范围中的键值 `npm-feature-`
-2. `feature` 分支范围中的键值 `npm-`
-1. `master` 分支范围中的键值 `npm-feature-d5ea0750`
-3. `master` 分支范围中的键值 `npm-d5ea0750`
-4. `master` 分支范围中的键值 `npm`
-
-### 使用限制和收回政策
-
-{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 可以存储的缓存数没有限制,但存储库中所有缓存的总大小限制为 5 GB。 如果超过此限制,{% data variables.product.prodname_dotcom %} 将保存缓存,但会开始收回缓存,直到总大小小于 5 GB。
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/configuring-a-workflow.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/configuring-a-workflow.md
deleted file mode 100644
index 485d35edcdeb..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/configuring-a-workflow.md
+++ /dev/null
@@ -1,382 +0,0 @@
----
-title: 配置工作流
-intro: 您可以创建自定义工作流来自动化项目的软件开发生命周期过程。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /文章/创建 github 行动/
- - /文章/创建工作流-与 github 操作/
- - /文章/配置工作流
- - /github/自动化工作流-使用 github 操作/配置工作流
- - /操作/自动化工作流-使用 github 操作/配置工作流
- - /操作/创建工作流/工作流配置选项
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-具有对存储库具有写入或管理员权限的用户可以创建、编辑或查看工作流。
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于工作流
-
-工作流是自定义的自动化流程,您可以在存储库中设置这些流程,以便生成、测试、打包、发布或部署任何 {% data variables.product.prodname_dotcom %}。 借助工作流,您可以使用各种工具和服务实现软件开发生命周期的自动化。 有关详细信息,请参阅"[" {% data variables.product.prodname_actions %}](/articles/about-github-actions)。
-
-您可以在存储库中创建多个工作流。 您必须将工作流存储在 `.github/工作流` 存储库根目录中。
-
-工作流必须至少有一个作业,并且作业包含一组执行单个任务的步骤。 步骤可以运行命令或使用操作。 您可以创建自己的操作或使用社区共享的操作 {% data variables.product.prodname_dotcom %} 根据需要自定义它们。
-
-您可以将工作流配置为在发生 {% data variables.product.prodname_dotcom %} 、计划或外部事件时启动。
-
-您需要使用 YAML 语法配置工作流,并将其保存为存储库中的工作流文件。 成功创建 YAML 工作流文件并触发工作流后,将看到工作流的每个步骤的生成日志、测试结果、工件和状态。 有关详细信息,请参阅"[运行工作流](/articles/managing-a-workflow-run)。
-
- ![注释的工作流运行映像](/assets/images/help/repository/annotated-workflow.png)
-
-您还可以接收工作流状态更新的通知。 有关通知选项的详细信息,请参阅"[通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)。
-
-使用限制适用于各个工作流。 有关详细信息,请参阅"[工作流的使用](/articles/workflow-syntax-for-github-actions#usage-limits)。
-
-### 创建工作流文件
-
-在高级别上,这些是添加工作流文件的步骤。 您可以在以下各节中找到特定的配置示例。
-
-1. 在存储库的根目录,创建一个名为 `.github/工作流` 以存储工作流文件。
-
-1. 在 `.github/工作流`中, `为` 添加 `.yaml` 文件。 例如, `.github/工作流/连续集成工作流.yml`。
-
-1. 使用"[工作流语法 {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions)"参考文档来选择事件以触发操作、添加操作和自定义工作流。
-
-1. 将工作流文件中的更改提交到希望工作流运行的分支。
-
-#### 工作流文件示例
-
-{% raw %}
-```yaml
-名称: 问候
-@ 此工作流在推送到存储库时触发。
-上: [push]
-
-工作:
- 生成:
- = 作业名称是问候
- 名称: 问候
- = 此作业在 Linux
- 上运行: ubuntu 最新
- 步骤:
- = 此步骤使用 Github 的 hello 世界 javascript 操作: https://github.com/actions/hello-world-javascript-action
- https://github.com/actions/hello-world-javascript-action 名称: 你好世界
- 使用: 动作 / hello 世界 javascript - action@v1.1
- 与:
- 谁问候: '蒙娜的八角猫'
- id: hello
- = 此步骤打印输出 (时间) 从上一步的操作。
- - 名字: 回音问候的时间
- 运行: 回声 '时间是 ${{ steps.hello.outputs.time }}。
-```
-{% endraw %}
-
-{% data reusables.github-actions.invalid-workflow-files %}
-
-### 使用事件触发工作流
-
-您可以将工作流配置为启动一次:
-- 发生一 {% data variables.product.prodname_dotcom %} 事件,例如,当某人将提交推送到存储库时,或者当创建问题或拉取请求时。
-- 计划的事件开始。
-- 发生外部事件。
-
-若要在发生事件后触发工作流 {% data variables.product.prodname_dotcom %},请 `:` 和工作流名称后的事件值。 例如,当将更改推送到存储库中的任何分支时,将触发此工作流。
-
-```yaml
-名称:描述性工作流名称
-:推送
-```
-
-若要安排工作流,可以在工作流文件中使用 POSIX cron 语法。 可以运行计划工作流的最短间隔是每 5 分钟一次。 例如,此工作流每小时触发一次。
-
-```yaml
-上:
- 时间表:
- - cron: '0]'
-```
-
-#### 手动运行工作流
-
-若要手动运行工作流,必须首先配置工作流以使用 `workflow_dispatch` 事件。 您可以直接在工作流中配置自定义的输入属性、默认输入值和所需输入。 当工作流运行时,您可以在 github.event.输入 `中访问输入` 值。 有关详细信息,请参阅"[工作流的"](/actions/reference/events-that-trigger-workflows/#workflow_dispatch)"和"[ {% data variables.product.prodname_dotcom %} 操作的上下文](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)"。
-
-此示例定义 `和` `` 输入 `github.event.inputs.name` 和 `github.event.inputs.home` 上下文。 如果未 `提供` 名称,则打印默认值"Octocat Mona"。
-
-{% raw %}
-```yaml
-名称: 手动触发的工作流
-:
- workflow_dispatch:
- 输入:
- 名称:
- 描述: "问候的人"
- :
- 默认: "Mona Octocat"
- "蒙娜 回家:
- : 需要 "位置
- : 假作业:
-
-
- say_hello:
- 运行: ubuntu 最新
- 步骤:
- - 运行:
- 回音"你好 ${{ github.event.inputs.name }}!
- 回声 "- 在 ${{ github.event.inputs.home }}!
-```
-{% endraw %}
-
-您可以使用 REST API `workflow_dispatch` "操作"选项卡 {% data variables.product.prodname_dotcom %} 触发事件。 有关使用 REST API 的信息,请参阅"[创建工作流调度事件](/rest/reference/actions/#create-a-workflow-dispatch-event)。 使用 REST API 时,应配置 `输入` `引用` 作为请求正文参数。 如果省略输入,则使用工作流文件中定义的默认值。
-
-若要在 `workflow_dispatch` 上 {% data variables.product.prodname_dotcom %},工作流必须处于默认分支中。 按照以下步骤手动触发工作流运行。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-1. 在左侧栏中,单击要运行的工作流。 ![操作选择工作流](/assets/images/actions-select-workflow.png)
-1. 在工作流运行列表的上方,选择 **运行工作流**。 ![操作工作流调度](/assets/images/actions-workflow-dispatch.png)
-1. 选择工作流将运行的分支,并键入工作流使用的输入参数。 单击 **运行工作流**。 ![操作手动运行工作流](/assets/images/actions-manually-run-workflow.png)
-
-#### 从外部事件触发工作流
-
-若要在发生外部事件后触发工作流,可以通过调用"创建存储库调度事件"REST API 终结点来调用 `repository_dispatch` hook 事件。 有关详细信息,请参阅"[创建存储库调度事件](/v3/repos/#create-a-repository-dispatch-event)。
-
-有关详细信息和示例,请参阅"[工作流的](/articles/events-that-trigger-workflows#webhook-events)。
-
-### 筛选特定分支、标记和路径
-
-您可以将工作流设置为仅在某些分支上运行。
-
-例如,当在 `master` 分支上推送包含 测试 目录中的文件 `或推送到 v1` 标记时,
工作流将运行。
-
-```yaml
-上:
- :
- 分支:
- - 主
- 标记:
- - v1
- _ 文件路径, 在事件中要考虑。 可选;默认值。
- 路径:
- - "测试/*"
-```
-
-有关分支、标记和路径筛选器语法的信息,请参阅"[`。.`](/articles/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)" 和 "[`继续。.路径`](/articles/workflow-syntax-for-github-actions#onpushpull_requestpaths)。
-
-### 选择跑步者
-
-您可以在由托管的 {% data variables.product.prodname_dotcom %}运行程序或自托管运行程序上运行工作流。 作业可以直接在计算机或 Docker 容器中运行。
-
-您可以使用运行或运行的运行 `中为每个作业`。 有关运行 `运行`有关[,请参阅" {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idruns-on)工作流 "
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-#### 使用 {% data variables.product.prodname_dotcom %}托管的运行程序
-
-您可以选择不同类型和版本的虚拟主机,包括 Linux、Windows 和 macOS。 工作流中的每个作业在虚拟环境的新实例中执行,作业中的步骤可以使用文件系统共享信息。 有关详细信息,请参阅"[托管跑步者 {% data variables.product.prodname_actions %}的虚拟](/articles/virtual-environments-for-github-actions)。
-
-例如,您可以使用 ubuntu `的最新` 指定由托管运行程序 {% data variables.product.prodname_dotcom %}的最新版本。
-
-```yaml
-运行: ubuntu 最新
-```
-
-#### 使用自托管的运行程序
-
-您可以使用标签将作业路由到特定类型的自托管流道。 所有自托管跑步者都 `自托管` 标签,每个自托管运行程序都有其操作系统和系统体系结构的标签。 有关详细信息,请参阅"[工作流中的自托管运行程序](/actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)。
-
-例如,如果添加了具有 Linux 操作系统和 ARM32 体系结构的自托管运行程序,可以使用 `自托管`、 `linux`和 `ARM32` 标签选择该运行程序。
-
-```yaml
-运行: [自托管, linux, ARM32]
-```
-
-### 配置生成矩阵
-
-若要同时跨多个操作系统、平台和语言版本进行测试,可以配置生成矩阵。
-
-生成矩阵允许您使用不同的软件和操作系统配置测试代码。 例如,工作流可以运行语言、操作系统或工具的多个受支持版本的作业。 对于每个配置,作业的副本将运行并报告状态。
-
-您可以在工作流文件中指定生成矩阵,其中数组在"配置"策略 `:`。 例如,此生成矩阵将运行具有不同版本的 Node.js 和 Ubuntu(Linux 操作系统)的作业。
-
-{% data reusables.repositories.actions-matrix-builds-os %}
-
-{% raw %}
-```yaml
-运行: ${{ matrix.os }}
-:
- 矩阵:
- os: [ubuntu-16.04, ubuntu-18.04]
- 节点: [6, 8, 10]
-```
-{% endraw %}
-
-有关详细信息,请参阅"[的工作流 {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)。
-
-### 使用签出操作
-
-可以在工作流中使用多个标准操作。 签出操作是一个标准操作,在以下时间之前,您必须在工作流中包括该操作, 然后再执行其他操作:
-- 您的工作流需要存储库代码的副本,例如在构建和测试存储库或使用持续集成时。
-- 工作流中至少有一个操作在同一存储库中定义。 有关详细信息,请参阅"[工作流中的"引用操作](#referencing-actions-in-your-workflow)。
-
-若要在没有进一步规范的情况下使用标准签出操作,请包括以下步骤:
-```yaml
-- 使用:操作/checkout@v2
-```
-在此示例中 `使用` v2,可确保使用签出操作的稳定版本。 有关详细信息,请参阅 [结帐操作](https://github.com/actions/checkout)。
-
-### 选择工作流的操作类型
-
-工作流中可以使用不同类型的操作来满足项目的需求:
-- 码头容器操作
-- JavaScript 操作
-- 复合运行步骤操作
-
-有关详细信息,请参阅"[操作](/articles/about-actions#types-of-actions)"。
-
-在选择要在工作流中使用的操作类型时,我们建议在公共存储库或 Docker 中心上探索现有操作,并可能为项目自定义这些操作。
-
-您可以浏览和使用由用户在 {% data variables.product.prodname_dotcom %} 中构建 [github.com/actions](https://github.com/actions) 操作。 若要访问 Docker 中心,请参阅 Docker[站点上的](https://www.docker.com/products/docker-hub)"。"
-
-### 引用工作流中的操作
-
-若要使用正确的语法引用工作流文件中的操作,必须考虑操作的定义位置。
-
-工作流可以使用在以下项中定义的操作:
-- 公共存储库
-- 工作流文件引用操作的同一存储库
-- Docker 集线器上已发布的 Docker 容器映像
-
-若要使用在专用存储库中定义的操作,工作流文件和操作必须在同一个存储库中。 您的工作流不能使用在其他私有存储库中定义的操作,即使其他私有存储库位于同一组织中。
-
-若要对操作进行更新时保持工作流稳定,可以通过在工作流文件中指定 Git ref 或 Docker 标记编号来引用正在使用的操作的版本。 有关示例,请参阅"[的工作流 {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idstepsuses)。
-
-{% if currentVersion == "free-pro-team@latest" %}
-{% data reusables.dependabot.version-updates-for-actions %}
-{% endif %}
-
-有关更详细的配置选项,请参阅"[的工作流 {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)。
-
-#### 从公共存储库引用操作
-
-如果在公共存储库中定义了操作,则必须使用语法 `{owner}/{repo}_{ref}` 或 `{owner}/{repo}/{path}@{ref}`引用操作。
-
-```yaml
-作业:
- my_first_job:
- 名称: 我的作业名称
- 步骤:
- - 使用: 操作 / 设置 - node@v1
- :
- 版本: 10.x
-```
-
-若要查看完整的工作流示例,请参阅 [模板存储库](https://github.com/actions/setup-node) 设置节点。
-
-#### 引用工作流文件使用操作的同一存储库中的操作
-
-如果在工作流文件使用该操作的同一存储库中定义了操作,则可以使用工作流文件中的`{owner}/{repo}@{ref}` 或 `./path/to/dir` 语法引用该操作。
-
-存储库文件结构示例:
-
-```
-[- - 你好世界 (存储库)
-] [__. github
-] └ • 工作流
-| └ [我的第一工作流. yml
-] └[行动
-] [你好世界行动
-] └ = 行动. yml
-```
-
-工作流文件示例:
-
-```yaml
-作业:
- :
- 运行: ubuntu 最新
- 步骤:
- # 此步骤签出存储库的副本。
- - 使用:操作/checkout@v2
- # 此步骤引用包含操作的目录。
- - 使用:..github/行动/你好世界行动
-```
-
-#### 在 Docker 集线器上引用容器
-
-如果在 Docker Hub 上的已发布 Docker 容器映像中定义了操作,则必须在工作流文件中使用 `docker://{image}:{tag}` 语法引用该操作。 为了保护您的代码和数据,我们强烈建议您先在工作流中使用 Docker Hub 来验证 Docker 容器映像的完整性。
-
-```yaml
-工作:
- my_first_job:
- 步:
- - 名称: 我的第一步
- 使用: docker:: 3.8
-```
-
-有关 Docker 操作的一些示例,请参阅 [Docker-image.yml 工作流](https://github.com/actions/starter-workflows/blob/master/ci/docker-image.yml) "[创建 Docker 容器操作](/articles/creating-a-docker-container-action)。
-
-有关详细信息,请参阅"[的工作流 {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idstepsuses)。
-
-### 向存储库添加工作流状态徽章
-
-{% data reusables.repositories.actions-workflow-status-badge-into %}
-
-如果工作流使用 `关键字` ,则必须按名称引用工作流。 如果工作流的名称包含空格,则需要将该空格替换为 URL 编码的字符串 `%20`。 有关关键字名称 `有关` ,请参阅"[的工作流 {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#name)。
-
-```
-https://github.com/// 工作流 // badge. svg
-```
-
-或者,如果您的工作流没有 `名称`,则必须使用相对于存储库的根目录的文件路径引用工作流文件。
-
-{% note %}
-
-**注意:** 如果工作流具有一个包含名称的配置文件,则使用文件路径 `工作流`。
-
-{% endnote %}
-
-```
-https://github.com/// 工作流 // badge. svg
-```
-
-#### 使用工作流名称的示例
-
-此标记示例为工作流添加状态徽章,名称为"问候所有人"。 存储库 `所有者` 是 `组织` , `名称` 是 `hello world`。
-
-```
-![示例工作流名称](https://github.com/actions/hello-world/workflows/Greet%20E非常一/badge.svg)
-```
-
-#### 使用工作流文件路径的示例
-
-此 Markdown 示例为具有文件路径的工作流添加了状态徽章 `.github/工作流/main.yml`。 存储库 `所有者` 是 `组织` , `名称` 是 `hello world`。
-
-```
-![示例工作流文件路径](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg)
-```
-
-#### 使用分支 `` 示例
-
-此标记示例为名称为功能-1 的分支添加 `标记`。
-
-```
-![示例分支参数](https://github.com/actions/hello-world/workflows/Greet%20E非常一/badge.svg?branch=功能-1)
-```
-
-#### 使用事件 `` 示例
-
-此 Markdown 示例添加了一个徽章,显示由事件触发的工作流 `pull_request` 状态。
-
-```
-![示例事件参数](https://github.com/actions/hello-world/workflows/Greet%20E非常一/badge.svg?事件=pull_request)
-```
-
-{% if currentVersion == "free-pro-team@latest" %}
-### 延伸阅读
-
-- [[管理帐户的 {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)"
-{% endif %}
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/configuring-and-managing-workflow-files-and-runs.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/configuring-and-managing-workflow-files-and-runs.md
deleted file mode 100644
index 83562972b657..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/configuring-and-managing-workflow-files-and-runs.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: 配置和管理工作流程文件和运行
-intro: 创建和配置工作流程以实现部分项目开发的自动化。
-mapTopic: true
-redirect_from:
- - /articles/configuring-workflows
- - /github/automating-your-workflow-with-github-actions/configuring-workflows
- - /actions/automating-your-workflow-with-github-actions/configuring-workflows
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets.md
deleted file mode 100644
index d2c4a9ab3340..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets.md
+++ /dev/null
@@ -1,220 +0,0 @@
----
-title: 创建和存储加密密码
-intro: 加密密码允许您在仓库或组织中存储敏感信息。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
- - /actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于加密密码
-
-密码是在仓库或组织中创建的加密环境变量。 您创建的密码可用于 {% data variables.product.prodname_actions %} 工作流程。 在密码到达 {% data variables.product.prodname_dotcom %} 之前,{% data variables.product.prodname_dotcom %} 使用 [libsodium 密封盒](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)对密码加密,并且在您于工作流程中使用它们之前一直保持加密状态。
-
-{% data reusables.github-actions.secrets-org-level-overview %}
-
-#### 命名您的密码
-
-以下规则适用于密码名称:
-
-* 密码名称只能包含字母数字字符(`[a-z]`、`[A-Z]`、`[0-9]`)或下划线 (`_`)。 不允许空格。
-* 密码名称不能以 `GITHUB_` 前缀开头。
-* 密码名称不能以数字开头。
-* 密码名称在所创建的级别上必须是唯一的。 例如,在组织级别创建的密码必须在该级别具有唯一名称,而在仓库级别创建的密码必须在该仓库具有唯一名称。 如果组织级别密码的名称与仓库级别的密码相同,则仓库级别的密码优先。
-
-为帮助确保 {% data variables.product.prodname_dotcom %} 在日志中编写密码,请勿将结构化数据用作密码的值。 例如,避免创建包含 JSON 或编码 Git blob 的密码。
-
-#### 访问您的密码
-
-为使密码用于操作,必须将密码设置为工作流程文件中的输入或环境变量。 查看操作的自述文件以了解操作预期的输入和环境变量。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)”。
-
-如果您拥有编辑文件的权限,便可在工作流程文件中使用和读取加密密码。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/github/getting-started-with-github/access-permissions-on-github)”。
-
-{% warning %}
-
-**警告:**{% data variables.product.prodname_dotcom %} 自动将密码编写到日志,但您应避免有意将密码打印到日志。
-
-{% endwarning %}
-
-您还可以使用 REST API 管理密码。 更多信息请参阅“[密码](/v3/actions/secrets/)”。
-
-#### 限制凭据权限
-
-生成凭据时,建议尽可能授予最低的权限。 例如,不使用个人凭据,而使用[部署密钥](/v3/guides/managing-deploy-keys/#deploy-keys)或服务帐户。 请考虑授予只读权限(如果这是所需的全部权限)并尽可能限制访问。 生成个人访问令牌 (PAT) 时,选择所需的最小范围。
-
-### 为仓库创建加密密码
-
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
-1. 单击 **Add a new secret(添加新机密)**。
-1. 在 **Name(名称)**输入框中键入密码的名称。
-1. 输入密码的值。
-1. 单击 **Add secret(添加密码)**。
-
-如果您的仓库可以从父级组织访问密码,则此页上也会列出这些密码。
-
-### 为组织创建加密密码
-
-在组织中创建密码时,可以使用策略来限制可以访问该密码的仓库。 例如,您可以将访问权限授予所有仓库,也可以限制仅私有仓库或指定的仓库列表拥有访问权限。
-
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
-
-{% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
-1. 单击 **New secret(新建密码)**。
-1. 在 **Name(名称)**输入框中键入密码的名称。
-1. 输入密码的 **Value(值)**。
-1. 从 **Repository access(仓库访问权限)**下拉列表,选择访问策略。
-1. 单击 **Add secret(添加密码)**。
-
-### 审查对组织级别密码的访问权限
-
-您可以检查哪些访问策略正被应用于组织中的密码。
-
-{% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
-1. 密码列表包括任何已配置的权限和策略。 例如: ![密码列表](/assets/images/help/settings/actions-org-secrets-list.png)
-1. 有关已为每个密码配置的权限的更多信息,请单击 **Update(更新)**。
-
-### 在工作流程中使用加密密码
-
-除了 `GITHUB_TOKEN` 以外,从复刻的仓库触发工作流程时密码不会传递给运行程序。
-
-要提供以密码作为输入或环境变量的操作,可以使用 `secrets` 上下文访问您在仓库中创建的密码。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”和“[{% data variables.product.prodname_actions %} 的工作流程语法](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。
-
-{% raw %}
-```yaml
-steps:
- - name: Hello world action
- with: # Set the secret as an input
- super_secret: ${{ secrets.SuperSecret }}
- env: # Or as an environment variable
- super_secret: ${{ secrets.SuperSecret }}
-```
-{% endraw %}
-
-尽可能避免使用命令行在进程之间传递密码。 命令行进程可能对其他用户可见(使用 `ps` 命令)或通过[安全审计事件](https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing)获取。 为帮助保护密码,请考虑使用环境变量 `STDIN` 或目标进程支持的其他机制。
-
-如果必须在命令行中传递密码,则将它们包含在适当的引用规则中。 密码通常包含可能意外影响 shell 的特殊字符。 要转义这些特殊字符,请引用环境变量。 例如:
-
-#### 使用 Bash 的示例
-
-{% raw %}
-```yaml
-steps:
- - shell: bash
- env:
- SUPER_SECRET: ${{ secrets.SuperSecret }}
- run: |
- example-command "$SUPER_SECRET"
-```
-{% endraw %}
-
-#### 使用 PowerShell 的示例
-
-{% raw %}
-```yaml
-steps:
- - shell: pwsh
- env:
- SUPER_SECRET: ${{ secrets.SuperSecret }}
- run: |
- example-command "$env:SUPER_SECRET"
-```
-{% endraw %}
-
-#### 使用 Cmd.exe 的示例
-
-{% raw %}
-```yaml
-steps:
- - shell: cmd
- env:
- SUPER_SECRET: ${{ secrets.SuperSecret }}
- run: |
- example-command "%SUPER_SECRET%"
-```
-{% endraw %}
-
-### 密码的限制
-
-您的工作流程最多可以有 100 个密码。 密码环境变量的名称在仓库中必须是唯一的。
-
-密码大小限于 64 KB。 要使用大于 64 KB 的密码,可以将加密的密码存储在仓库中,并将解密短语在 {% data variables.product.prodname_dotcom %} 上存储为密码。 例如,在将文件检入您在 {% data variables.product.prodname_dotcom %} 上的仓库之前,可以使用 `gpg` 在本地对您的凭据加密。 更多信息请参阅“[gpg manpage](https://www.gnupg.org/gph/de/manual/r1023.html)”。
-
-{% warning %}
-
-**警告**:请注意,您的密码在操作运行时不会印出。 使用此解决方法时,{% data variables.product.prodname_dotcom %} 不会编写日志中印出的密码。
-
-{% endwarning %}
-
-1. 从终端运行以下命令,以使用 `gpg` 和 AES256 密码算法对 `my_secret.json` 文件加密。
-
- ``` shell
- $ gpg --symmetric --cipher-algo AES256 my_secret.json
- ```
-
-1. 将会提示您输入密码短语。 请记住该密码短语,因为需要在使用该密码短语作为值的 {% data variables.product.prodname_dotcom %} 上创建新密码。
-
-1. 创建包含密码短语的新密码。 例如,使用名称 `LARGE_SECRET_PASSPHRASE` 创建新密码,并将密码的值设为上一步所选的密码短语。
-
-1. 将加密的文件复制到仓库并提交。 在本例中,加密的文件是 `my_secret.json.gpg`。
-
-1. 创建 shell 脚本对密码解密。 将此文件另存为 `decrypt_secret.sh`。
-
- ``` shell
- #!/bin/sh
-
- # 解密文件
- mkdir $HOME/secrets
- # --批处理以防止交互式命令
- # --是以假定问题的回答是“是”
- gpg --quiet --batch --yes --decrypt --passphrase="$LARGE_SECRET_PASSPHRASE" \
- --output $HOME/secrets/my_secret.json my_secret.json.gpg
- ```
-
-1. 确保 shell 脚本在检入仓库之前可执行。
-
- ``` shell
- $ chmod +x decrypt_secret.sh
- $ git add decrypt_secret.sh
- $ git commit -m "Add new decryption script"
- $ git push
- ```
-
-1. 从工作流程使用 `step` 调用 shell 脚本并对密码解密。 要在工作流程运行的环境中创建仓库的副本,需要使用 [`actions/checkout`](https://github.com/actions/checkout) 操作。 使用与仓库根目录相关的 `run` 命令引用 shell 脚本。
-
-{% raw %}
- ```yaml
- 名称: 具有大机密的工作流
-
- : 推送
-
- 作业:
- 我的工作:
- 名称: 我的工作
- 运行: ubuntu 最新
- 步骤:
- - 使用: 操作 / checkout@v2
- - 名称: 解密大机密
- 运行:..github/脚本/decrypt_secret.sh
- env:
- LARGE_SECRET_PASSPHRASE: ${{ secrets.LARGE_SECRET_PASSPHRASE }}
- = 此命令只是显示您的机密被打印的示例
- # 确保删除机密的任何打印语句。 GitHub does
- # not hide secrets that use this workaround.
- - name: Test printing your secret (Remove this step in production)
- run: cat $HOME/secrets/my_secret.json
- ```
-{% endraw %}
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-postgresql-service-containers.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-postgresql-service-containers.md
deleted file mode 100644
index cf573867c58c..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-postgresql-service-containers.md
+++ /dev/null
@@ -1,335 +0,0 @@
----
-title: 创建 PostgreSQL 服务容器
-intro: 您可以创建 PostgreSQL 服务容器用于您的工作流程。 本指南举例说明如何为容器中运行或直接在运行器机器上运行的作业创建 PostgreSQL 服务。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南演示了使用 Docker Hub `postgres` 映像配置服务容器的工作流程示例。 工作流程运行脚本来创建 PostgreSQL 客户端并使用数据填充客户端。 要测试工作流程是否创建并填充 PostgreSQL 客户端,脚本会将客户端数据打印到控制台。
-
-{% data reusables.github-actions.docker-container-os-support %}
-
-### 基本要求
-
-{% data reusables.github-actions.service-container-prereqs %}
-
-你可能还会发现它也有助于基本了解 YAML、{% data variables.product.prodname_actions %} 的语法和 PostgreSQL。 更多信息请参阅:
-
-- "[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)"
-- PostgreSQL 文档中的“[PostgreSQL 教程](https://www.postgresqltutorial.com/)”
-- "[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-
-### 在容器中运行作业
-
-{% data reusables.github-actions.container-jobs-intro %}
-
-{% data reusables.github-actions.copy-workflow-file %}
-
-{% raw %}
-```yaml
-name: PostgreSQL service example
-on: push
-
-jobs:
- # Label of the container job
- container-job:
- # Containers must run in Linux based operating systems
- runs-on: ubuntu-latest
- # Docker Hub image that `container-job` executes in
- container: node:10.18-jessie
-
- # Service containers to run with `container-job`
- services:
- # Label used to access the service container
- postgres:
- # Docker Hub image
- image: postgres
- # Provide the password for postgres
- env:
- POSTGRES_PASSWORD: postgres
- # Set health checks to wait until postgres has started
- options: >-
- --health-cmd pg_isready
- --health-interval 10s
- --health-timeout 5s
- --health-retries 5
-
- steps:
- # Downloads a copy of the code in your repository before running CI tests
- - name: Check out repository code
- uses: actions/checkout@v2
-
- # Performs a clean installation of all dependencies in the `package.json` file
- # For more information, see https://docs.npmjs.com/cli/ci.html
- - name: Install dependencies
- run: npm ci
-
- - name: Connect to PostgreSQL
- # Runs a script that creates a PostgreSQL client, populates
- # the client with data, and retrieves data
- run: node client.js
- # Environment variable used by the `client.js` script to create a new PostgreSQL client.
- env:
- # The hostname used to communicate with the PostgreSQL service container
- POSTGRES_HOST: postgres
- # The default PostgreSQL port
- POSTGRES_PORT: 5432
-```
-{% endraw %}
-
-#### 配置运行器作业
-
-{% data reusables.github-actions.service-container-host %}
-
-{% data reusables.github-actions.postgres-label-description %}
-
-```yaml
-jobs:
- # Label of the container job
- container-job:
- # Containers must run in Linux based operating systems
- runs-on: ubuntu-latest
- # Docker Hub image that `container-job` executes in
- container: node:10.18-jessie
-
- # Service containers to run with `container-job`
- services:
- # Label used to access the service container
- postgres:
- # Docker Hub image
- image: postgres
- # Provide the password for postgres
- env:
- POSTGRES_PASSWORD: postgres
- # Set health checks to wait until postgres has started
- options: >-
- --health-cmd pg_isready
- --health-interval 10s
- --health-timeout 5s
- --health-retries 5
-```
-
-#### 配置步骤
-
-{% data reusables.github-actions.service-template-steps %}
-
-```yaml
-steps:
- # Downloads a copy of the code in your repository before running CI tests
- - name: Check out repository code
- uses: actions/checkout@v2
-
- # Performs a clean installation of all dependencies in the `package.json` file
- # For more information, see https://docs.npmjs.com/cli/ci.html
- - name: Install dependencies
- run: npm ci
-
- - name: Connect to PostgreSQL
- # Runs a script that creates a PostgreSQL client, populates
- # the client with data, and retrieves data
- run: node client.js
- # Environment variable used by the `client.js` script to create
- # a new PostgreSQL client.
- env:
- # The hostname used to communicate with the PostgreSQL service container
- POSTGRES_HOST: postgres
- # The default PostgreSQL port
- POSTGRES_PORT: 5432
-```
-
-{% data reusables.github-actions.postgres-environment-variables %}
-
-PostgreSQL 文档中的服务的主机名是您在工作流程中配置的标签,本例中为 `postgres`。 由于同一用户定义的网桥网络上的 Docker 容器默认打开所有端口,因此您将能够访问默认 PostgreSQL 端口 5432 上的服务容器。
-
-### 直接在运行器机器上运行作业
-
-直接在运行器机器上运行作业时,需要将服务容器上的端口映射到 Docker 主机上的端口。 您可以使用 `localhost` 和 Docker 主机端口号从 Docker 主机访问服务容器。
-
-{% data reusables.github-actions.copy-workflow-file %}
-
-{% raw %}
-```yaml
-name: PostgreSQL Service Example
-on: push
-
-jobs:
- # Label of the runner job
- runner-job:
- # You must use a Linux environment when using service containers or container jobs
- runs-on: ubuntu-latest
-
- # Service containers to run with `runner-job`
- services:
- # Label used to access the service container
- postgres:
- # Docker Hub image
- image: postgres
- # Provide the password for postgres
- env:
- POSTGRES_PASSWORD: postgres
- # Set health checks to wait until postgres has started
- options: >-
- --health-cmd pg_isready
- --health-interval 10s
- --health-timeout 5s
- --health-retries 5
- ports:
- # Maps tcp port 5432 on service container to the host
- - 5432:5432
-
- steps:
- # Downloads a copy of the code in your repository before running CI tests
- - name: Check out repository code
- uses: actions/checkout@v2
-
- # Performs a clean installation of all dependencies in the `package.json` file
- # For more information, see https://docs.npmjs.com/cli/ci.html
- - name: Install dependencies
- run: npm ci
-
- - name: Connect to PostgreSQL
- # Runs a script that creates a PostgreSQL client, populates
- # the client with data, and retrieves data
- run: node client.js
- # Environment variable used by the `client.js` script to create
- # a new PostgreSQL client.
- env:
- # The hostname used to communicate with the PostgreSQL service container
- POSTGRES_HOST: localhost
- # The default PostgreSQL port
- POSTGRES_PORT: 5432
-```
-{% endraw %}
-
-#### 配置运行器作业
-
-{% data reusables.github-actions.service-container-host-runner %}
-
-{% data reusables.github-actions.postgres-label-description %}
-
-工作流程将 PostgreSQL 服务容器上的端口 5432 映射到 Docker 主机。 有关 `ports` 关键字的更多信息,请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。
-
-```yaml
-jobs:
- # Label of the runner job
- runner-job:
- # You must use a Linux environment when using service containers or container jobs
- runs-on: ubuntu-latest
-
- # Service containers to run with `runner-job`
- services:
- # Label used to access the service container
- postgres:
- # Docker Hub image
- image: postgres
- # Provide the password for postgres
- env:
- POSTGRES_PASSWORD: postgres
- # Set health checks to wait until postgres has started
- options: >-
- --health-cmd pg_isready
- --health-interval 10s
- --health-timeout 5s
- --health-retries 5
- ports:
- # Maps tcp port 5432 on service container to the host
- - 5432:5432
-```
-
-#### 配置步骤
-
-{% data reusables.github-actions.service-template-steps %}
-
-```yaml
-steps:
- # Downloads a copy of the code in your repository before running CI tests
- - name: Check out repository code
- uses: actions/checkout@v2
-
- # Performs a clean installation of all dependencies in the `package.json` file
- # For more information, see https://docs.npmjs.com/cli/ci.html
- - name: Install dependencies
- run: npm ci
-
- - name: Connect to PostgreSQL
- # Runs a script that creates a PostgreSQL client, populates
- # the client with data, and retrieves data
- run: node client.js
- # Environment variable used by the `client.js` script to create
- # a new PostgreSQL client.
- env:
- # The hostname used to communicate with the PostgreSQL service container
- POSTGRES_HOST: localhost
- # The default PostgreSQL port
- POSTGRES_PORT: 5432
-```
-
-{% data reusables.github-actions.postgres-environment-variables %}
-
-{% data reusables.github-actions.service-container-localhost %}
-
-### 测试 PostgreSQL 服务容器
-
-您可以使用以下脚本测试工作流程,该脚本将创建 PostgreSQL 客户端,并添加包含某些占位符数据的新表。 然后,脚本将存储在 PostgreSQL 客户端中的值打印到终端。 您的脚本可以使用任何您喜欢的语言,但此示例使用 Node.js 和 `Pg` npm 模块。 更多信息请参阅 [npm pg 模块](https://www.npmjs.com/package/pg)。
-
-您可以修改 *client.js* 以包含工作流程需要的任何 PostgreSQL 操作。 在此示例中,脚本创建 PostgreSQL 客户端实例、创建表、添加占位符数据,然后检索数据。
-
-{% data reusables.github-actions.service-container-add-script %}
-
-```javascript
-const { Client } = require('pg');
-
-const pgclient = new Client({
- host: process.env.POSTGRES_HOST,
- port: process.env.POSTGRES_PORT,
- user: 'postgres',
- password: 'postgres',
- database: 'postgres'
-});
-
-pgclient.connect();
-
-const table = 'CREATE TABLE student(id SERIAL PRIMARY KEY, firstName VARCHAR(40) NOT NULL, lastName VARCHAR(40) NOT NULL, age INT, address VARCHAR(80), email VARCHAR(40))'
-const text = 'INSERT INTO student(firstname, lastname, age, address, email) VALUES($1, $2, $3, $4, $5) RETURNING *'
-const values = ['Mona the', 'Octocat', 9, '88 Colin P Kelly Jr St, San Francisco, CA 94107, United States', 'octocat@github.com']
-
-pgclient.query(table, (err, res) => {
- if (err) throw err
-});
-
-pgclient.query(text, values, (err, res) => {
- if (err) throw err
-});
-
-pgclient.query('SELECT * FROM student', (err, res) => {
- if (err) throw err
- console.log(err, res.rows) // Print the data in student table
- pgclient.end()
-});
-```
-
-该脚本创建新的 PostgreSQLL `Client`,接受 `host` 和 `port` 参数。 该脚本使用 `POSTGRES_HOST` 和 `POSTGRES_PORT` 环境变量来设置客户端的 IP 地址和端口。 如果未定义 `host` 和 `port`,则默认主机为 `localhost`,默认端口为 5432。
-
-脚本创建一个表并将用占位符数据添加。 要测试 PostgreSQL 数据库是否包含数据,脚本将会表的内容打印到控制台日志。
-
-运行此工作流程时,应会在“连接到 PostgreSQL”步骤中看到以下输出,确认您创建了 PostgreSQL 客户端并添加了数据:
-
-```
-null [ { id: 1,
- firstname: 'Mona the',
- lastname: 'Octocat',
- age: 9,
- address:
- '88 Colin P Kelly Jr St, San Francisco, CA 94107, United States',
- email: 'octocat@github.com' } ]
-```
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-redis-service-containers.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-redis-service-containers.md
deleted file mode 100644
index 722e5ba67bf5..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/creating-redis-service-containers.md
+++ /dev/null
@@ -1,325 +0,0 @@
----
-title: 创建 Redis 服务容器
-intro: 您可以使用服务容器在工作流程中创建 Redis 客户端。 本指南举例说明如何为容器中运行或直接在运行器机器上运行的作业创建 Redis 服务。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/creating-redis-service-containers
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南演示了使用 Docker Hub `redis` 映像配置服务容器的工作流程示例。 工作流程运行脚本来创建 Redis 客户端并使用数据填充客户端。 要测试工作流程是否创建并填充 Redis 客户端,脚本会将客户端数据打印到控制台。
-
-{% data reusables.github-actions.docker-container-os-support %}
-
-### 基本要求
-
-{% data reusables.github-actions.service-container-prereqs %}
-
-你可能还会发现它也有助于基本了解 YAML、{% data variables.product.prodname_actions %} 的语法和 Redis。 更多信息请参阅:
-
-- "[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)"
-- Redis 文档中的“[Redis 使用入门](https://redislabs.com/get-started-with-redis/)”
-- "[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-
-### 在容器中运行作业
-
-{% data reusables.github-actions.container-jobs-intro %}
-
-{% data reusables.github-actions.copy-workflow-file %}
-
-{% raw %}
-```yaml
-name: Redis container example
-on: push
-
-jobs:
- # Label of the container job
- container-job:
- # Containers must run in Linux based operating systems
- runs-on: ubuntu-latest
- # Docker Hub image that `container-job` executes in
- container: node:10.18-jessie
-
- # Service containers to run with `container-job`
- services:
- # Label used to access the service container
- redis:
- # Docker Hub image
- image: redis
- # Set health checks to wait until redis has started
- options: >-
- --health-cmd "redis-cli ping"
- --health-interval 10s
- --health-timeout 5s
- --health-retries 5
-
- steps:
- # Downloads a copy of the code in your repository before running CI tests
- - name: Check out repository code
- uses: actions/checkout@v2
-
- # Performs a clean installation of all dependencies in the `package.json` file
- # For more information, see https://docs.npmjs.com/cli/ci.html
- - name: Install dependencies
- run: npm ci
-
- - name: Connect to Redis
- # Runs a script that creates a Redis client, populates
- # the client with data, and retrieves data
- run: node client.js
- # Environment variable used by the `client.js` script to create a new Redis client.
- env:
- # The hostname used to communicate with the Redis service container
- REDIS_HOST: redis
- # The default Redis port
- REDIS_PORT: 6379
-```
-{% endraw %}
-
-#### 配置容器作业
-
-{% data reusables.github-actions.service-container-host %}
-
-{% data reusables.github-actions.redis-label-description %}
-
-```yaml
-jobs:
- # Label of the container job
- container-job:
- # Containers must run in Linux based operating systems
- runs-on: ubuntu-latest
- # Docker Hub image that `container-job` executes in
- container: node:10.18-jessie
-
- # Service containers to run with `container-job`
- services:
- # Label used to access the service container
- redis:
- # Docker Hub image
- image: redis
- # Set health checks to wait until redis has started
- options: >-
- --health-cmd "redis-cli ping"
- --health-interval 10s
- --health-timeout 5s
- --health-retries 5
-```
-
-#### 配置步骤
-
-{% data reusables.github-actions.service-template-steps %}
-
-```yaml
-steps:
- # Downloads a copy of the code in your repository before running CI tests
- - name: Check out repository code
- uses: actions/checkout@v2
-
- # Performs a clean installation of all dependencies in the `package.json` file
- # For more information, see https://docs.npmjs.com/cli/ci.html
- - name: Install dependencies
- run: npm ci
-
- - name: Connect to Redis
- # Runs a script that creates a Redis client, populates
- # the client with data, and retrieves data
- run: node client.js
- # Environment variable used by the `client.js` script to create a new Redis client.
- env:
- # The hostname used to communicate with the Redis service container
- REDIS_HOST: redis
- # The default Redis port
- REDIS_PORT: 6379
-```
-
-{% data reusables.github-actions.redis-environment-variables %}
-
-Redis 服务的主机名是您在工作流程中配置的标签,本例中为 `redis`。 由于同一用户定义的网桥网络上的 Docker 容器默认打开所有端口,因此您将能够访问默认 Redis 端口 6379 上的服务容器。
-
-### 直接在运行器机器上运行作业
-
-直接在运行器机器上运行作业时,需要将服务容器上的端口映射到 Docker 主机上的端口。 您可以使用 `localhost` 和 Docker 主机端口号从 Docker 主机访问服务容器。
-
-{% data reusables.github-actions.copy-workflow-file %}
-
-{% raw %}
-```yaml
-name: Redis runner example
-on: push
-
-jobs:
- # Label of the runner job
- runner-job:
- # You must use a Linux environment when using service containers or container jobs
- runs-on: ubuntu-latest
-
- # Service containers to run with `runner-job`
- services:
- # Label used to access the service container
- redis:
- # Docker Hub image
- image: redis
- # Set health checks to wait until redis has started
- options: >-
- --health-cmd "redis-cli ping"
- --health-interval 10s
- --health-timeout 5s
- --health-retries 5
- ports:
- # Maps port 6379 on service container to the host
- - 6379:6379
-
- steps:
- # Downloads a copy of the code in your repository before running CI tests
- - name: Check out repository code
- uses: actions/checkout@v2
-
- # Performs a clean installation of all dependencies in the `package.json` file
- # For more information, see https://docs.npmjs.com/cli/ci.html
- - name: Install dependencies
- run: npm ci
-
- - name: Connect to Redis
- # Runs a script that creates a Redis client, populates
- # the client with data, and retrieves data
- run: node client.js
- # Environment variable used by the `client.js` script to create
- # a new Redis client.
- env:
- # The hostname used to communicate with the Redis service container
- REDIS_HOST: localhost
- # The default Redis port
- REDIS_PORT: 6379
-```
-{% endraw %}
-
-#### 配置运行器作业
-
-{% data reusables.github-actions.service-container-host-runner %}
-
-{% data reusables.github-actions.redis-label-description %}
-
-工作流程将 Redis 服务容器上的端口 6379 映射到 Docker 主机。 有关 `ports` 关键字的更多信息,请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。
-
-```yaml
-jobs:
- # Label of the runner job
- runner-job:
- # You must use a Linux environment when using service containers or container jobs
- runs-on: ubuntu-latest
-
- # Service containers to run with `runner-job`
- services:
- # Label used to access the service container
- redis:
- # Docker Hub image
- image: redis
- # Set health checks to wait until redis has started
- options: >-
- --health-cmd "redis-cli ping"
- --health-interval 10s
- --health-timeout 5s
- --health-retries 5
- ports:
- # Maps port 6379 on service container to the host
- - 6379:6379
-```
-
-#### 配置步骤
-
-{% data reusables.github-actions.service-template-steps %}
-
-```yaml
-steps:
- # Downloads a copy of the code in your repository before running CI tests
- - name: Check out repository code
- uses: actions/checkout@v2
-
- # Performs a clean installation of all dependencies in the `package.json` file
- # For more information, see https://docs.npmjs.com/cli/ci.html
- - name: Install dependencies
- run: npm ci
-
- - name: Connect to Redis
- # Runs a script that creates a Redis client, populates
- # the client with data, and retrieves data
- run: node client.js
- # Environment variable used by the `client.js` script to create
- # a new Redis client.
- env:
- # The hostname used to communicate with the Redis service container
- REDIS_HOST: localhost
- # The default Redis port
- REDIS_PORT: 6379
-```
-
-{% data reusables.github-actions.redis-environment-variables %}
-
-{% data reusables.github-actions.service-container-localhost %}
-
-### 测试 Redis 服务容器
-
-您可以使用以下脚本测试工作流程,该脚本将创建 Redis 客户端,并使用某些占位符数据填充客户端。 然后,脚本将存储在 Redis 客户端中的值打印到终端。 您的脚本可以使用任何您喜欢的语言,但此示例使用 Node.js 和 `redis` npm 模块。 更多信息请参阅 [npm redis 模块](https://www.npmjs.com/package/redis)。
-
-您可以修改 *client.js* 以包含工作流程需要的任何 Redis 操作。 在此示例中,脚本创建 Redis 客户端实例、添加占位符数据,然后检索数据。
-
-{% data reusables.github-actions.service-container-add-script %}
-
-```javascript
-const redis = require("redis");
-
-// Creates a new Redis client
-// If REDIS_HOST is not set, the default host is localhost
-// If REDIS_PORT is not set, the default port is 6379
-const redisClient = redis.createClient({
- host: process.env.REDIS_HOST,
- port: process.env.REDIS_PORT
-});
-
-redisClient.on("error", function(err) {
- console.log("Error " + err);
-});
-
-// Sets the key "octocat" to a value of "Mona the octocat"
-redisClient.set("octocat", "Mona the Octocat", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Cat and Octopus"
-redisClient.hset("species", "octocat", "Cat and Octopus", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Dinosaur and Octopus"
-redisClient.hset("species", "dinotocat", "Dinosaur and Octopus", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Cat and Robot"
-redisClient.hset(["species", "robotocat", "Cat and Robot"], redis.print);
-// Gets all fields in "species" key
-
-redisClient.hkeys("species", function (err, replies) {
- console.log(replies.length + " replies:");
- replies.forEach(function (reply, i) {
- console.log(" " + i + ": " + reply);
- });
- redisClient.quit();
-});
-```
-
-该脚本使用 `createClient` 方法创建新的 Redis 客户端,接受 `host` 和 `port` 参数。 该脚本使用 `REDIS_HOST` 和 `REDIS_PORT` 环境变量来设置客户端的 IP 地址和端口。 如果未定义 `host` 和 `port`,则默认主机为 `localhost`,默认端口为 6379。
-
-该脚本使用 `set` 和 `hset` 方法,以一些键值、字段和值来填充数据库。 要确认 Redis 客户端是否包含数据,脚本会将数据库的内容打印到控制台日志。
-
-运行此工作流程时,应会在“连接到 Redis”步骤中看到以下输出,确认您创建了 Redis 客户端并添加了数据:
-
-```
-Reply: OK
-Reply: 1
-Reply: 1
-Reply: 1
-3 replies:
- 0: octocat
- 1: dinotocat
- 2: robotocat
-```
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/index.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/index.md
deleted file mode 100644
index 68abfdef305b..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: 配置和管理工作流程
-shortTitle: 工作流程
-intro: 您可以创建自定义工作流程并管理运行,以控制项目软件开发周期流程。
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% topic_link_in_list /configuring-and-managing-workflow-files-and-runs %}
- {% link_in_list /configuring-a-workflow %}
- {% link_in_list /managing-a-workflow-run %}
- {% link_in_list /sharing-workflow-templates-within-your-organization %}
-{% topic_link_in_list /using-variables-and-secrets-in-a-workflow %}
- {% link_in_list /creating-and-storing-encrypted-secrets %}
- {% link_in_list /using-environment-variables %}
- {% link_in_list /authenticating-with-the-github_token %}
-{% topic_link_in_list /caching-and-storing-workflow-data %}
- {% link_in_list /persisting-workflow-data-using-artifacts %}
- {% link_in_list /caching-dependencies-to-speed-up-workflows %}
-{% topic_link_in_list /using-databases-and-service-containers %}
- {% link_in_list /about-service-containers %}
- {% link_in_list /creating-redis-service-containers %}
- {% link_in_list /creating-postgresql-service-containers %}
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/managing-a-workflow-run.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/managing-a-workflow-run.md
deleted file mode 100644
index c003c88b162f..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/managing-a-workflow-run.md
+++ /dev/null
@@ -1,186 +0,0 @@
----
-title: 管理工作流程运行
-intro: 您可以查看工作流程中每个步骤的状态和结果,取消待定的工作流程,查看可计费作业执行分钟数,调试并重新运行失败的工作流程,搜索并下载日志,以及下载构件。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /articles/viewing-your-repository-s-workflows
- - /articles/viewing-your-repositorys-workflows
- - /articles/managing-a-workflow-run
- - /github/automating-your-workflow-with-github-actions/managing-a-workflow-run
- - /actions/automating-your-workflow-with-github-actions/managing-a-workflow-run
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于工作流程管理
-
-您可以从工作流程运行页面查看工作流程运行是在进行中,还是已完成。 如果运行正在进行中,您可以取消运行。 您必须登录到 {% data variables.product.prodname_dotcom %} 帐户才能查看工作流程运行信息,包括公共仓库。 更多信息请参阅“[GitHub 上的访问权限](/articles/access-permissions-on-github)”。
-
-如果运行已完成,则可查看运行结果是成功、失败、已取消还是中性。 如果运行失败,您可以查看并搜索构建日志,来诊断失败原因并重新运行工作流程。 您也可以查看可计费作业执行分钟数,或下载日志和创建构件。
-
- ![注释的工作流运行映像](/assets/images/help/repository/annotated-workflow.png)
-
-{% data variables.product.prodname_actions %} 使用 Checks API 来输出工作流程的状态、结果和日志。 {% data variables.product.prodname_dotcom %} 对每个工作流程创建新检查套件。 检查套件包含检查工作流程中每项作业的运行,而每项作业包含步骤。 {% data variables.product.prodname_actions %} 作为工作流程中的一个步骤运行。 有关检查 API 的详细信息,请参阅“[检查](/v3/checks/)”。
-
-{% data reusables.github-actions.invalid-workflow-files %}
-
-### 查看工作流程历史记录
-
-您可以查看工作流程运行中的每项作业以及作业中的每个步骤。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions#job)”。 {% data reusables.repositories.permissions-statement-read %}
-
-除了工作流程文件中配置的步骤外,每个作业还包括用于启动和完成作业执行的其他任务。 这些步骤工作流程运行中记录为"设置作业"和"完成作业"。
-
-对于在 {% data variables.product.prodname_dotcom %} 托管的运行器上运行的作业,“设置作业”记录运行器虚拟环境的详细信息。 并包含一个链接,可链接到运行器机器上的预安装工具列表。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-6. (可选)如果运行失败,要重新运行工作流程,请使用工作流程右上角的 **Re-run checks(重新运行检查)**下拉菜单,然后选择 **Re-run all checks(重新运行所有检查)**。 ![重新运行检查下拉菜单](/assets/images/help/repository/rerun-checks-drop-down.png)
-
-### 取消工作流程运行
-
-当您取消工作流程运行时,{% data variables.product.prodname_dotcom %} 会取消属于该工作流程的所有作业和步骤。 {% data reusables.repositories.permissions-statement-write %}
-
-取消工作流程运行时,您可能正在运行使用与工作流程运行相关的资源的其他软件。 为了帮助您释放与工作流程运行相关的资源,它可能有助于了解 {% data variables.product.prodname_dotcom %} 为取消工作流程运行而执行的步骤。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 取消工作流程运行所执行的步骤](#steps-github-takes-to-cancel-a-workflow-run)”。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-1. 在工作流程右上角单击 **Cancel check suite(取消检查套件)**。 ![取消检查套件按钮](/assets/images/help/repository/cancel-check-suite.png)
-1. 单击 **Cancel check suite(取消检查套件)**后。
-
-#### {% data variables.product.prodname_dotcom %} 取消工作流程运行所执行的步骤
-
-1. 要取消工作流程运行,服务器将重新评估所有正在运行的作业的 `if` 条件。 如果条件评估为 `true`,作业将不会取消。 例如,条件 `if: always()` 将评估为 true,并且作业继续运行。 没有条件时,则等同于条件 `if: success()`,仅在上一步已成功完成时才会运行。
-2. 对于需要取消的作业,服务器向包含需取消作业的所有运行器机器发送取消消息。
-3. 对于继续运行的作业,服务器将对未完成的步骤重新评估 `if` 条件。 如果条件评估为 `true`,则步骤继续运行。
-4. 对于需要取消的步骤,运行器机器发送 `SIGINT/Ctrl-C` 到该步骤的输入进程(`node` 用于 javascript 操作,`docker` 用于容器操作,`bash/cmd/pwd` 则在步骤中使用 `run` 时发送)。 如果进程未在 7500 毫秒内退出,运行器将发送 `SIGTERM/Ctrl-Break` 到此进程,然后等待 2500 毫秒让进程退出。 如果该进程仍在运行,运行器会停止进程树。
-5. 在 5 分钟取消超时期后,服务器将强制终止未完成运行或无法完成取消进程的所有作业和步骤。
-
-### 删除工作流程运行
-
-您可以删除已完成或超过 2 周的工作流程运行。 {% data reusables.repositories.permissions-statement-write %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-1. 要删除工作流程运行,请使用 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 下拉菜单并选择 **Delete workflow run(删除工作流程运行)**。
-
- ![删除工作流程运行](/assets/images/help/settings/workflow-delete-run.png)
-1. 查看确认提示并单击 **Yes, permanently delete this workflow run(是,永久删除此工作流程运行)**。
-
- ![删除工作流程运行确认](/assets/images/help/settings/workflow-delete-run-confirmation.png)
-
-{% if currentVersion == "free-pro-team@latest" %}
-
-### 查看可计费作业执行分钟数
-
-您可以查看作业的执行时间,包括某个作业累积的可计费分钟数。
-
-仅为在私有仓库上运行,使用 {% data variables.product.prodname_dotcom %}- 托管的运行器的作业显示可计费作业执行分钟数。 如果在公共仓库中使用 {% data variables.product.prodname_actions %},或在自托管的运行器中运行作业时,将没有可计费分钟数。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-1. 在作业摘要下,单击 **Run and billable time details(运行和可计费时间详细信息)**。 ![运行和可计费时间详细信息链接](/assets/images/help/repository/view-run-billable-time.png)
-
- {% note %}
-
- **注意:**显示的可计费时间不包括任何四舍五入或分钟乘数。 要查看您的 {% data variables.product.prodname_actions %} 总使用情况,包括四舍五入和分钟乘法,请参阅"[查看您的 {% data variables.product.prodname_actions %} 使用情况](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage)。"
-
- {% endnote %}
-
-{% endif %}
-
-### 查看日志以诊断故障
-
-如果工作流程运行失败,您可以查看是哪个步骤导致了失败,然后审查失败步骤的创建日志进行故障排除。 您可以查看每个步骤运行的时长。 也可以将永久链接复制到日志文件中的特定行,与您的团队分享。 {% data reusables.repositories.permissions-statement-read %}
-
-{% data variables.product.product_name %} 会将整个创建日志和构件存储 90 天。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-{% data reusables.repositories.navigate-to-job %}
-6. 要展开失败步骤的日志,请单击该步骤。 ![失败的步骤名称](/assets/images/help/repository/failed-check-step.png)
-7. (可选)要获取指向日志中特定行的链接,请单击该步骤的行号。 您可以从 web 浏览器的地址栏中复制链接。 ![复制链接的按钮](/assets/images/help/repository/copy-link-button.png)
-
-### 搜索日志
-
-您可以搜索特定步骤的创建日志。 在搜索日志时,只有展开的步骤会包含在结果中。 {% data reusables.repositories.permissions-statement-read %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-{% data reusables.repositories.navigate-to-job %}
-6. 要展开想包含在搜索中的每个步骤,请单击该步骤。 ![步骤名称](/assets/images/help/repository/failed-check-step.png)
-7. 在日志输出的右上角,在 **Search logs(搜索日志)**搜索框中输入搜索查询。 ![搜索日志的搜索框](/assets/images/help/repository/search-log-box.png)
-
-### 下载日志
-
-您可以从工作流程运行中下载日志文件。 您也可以下载工作流程的构件。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。 {% data reusables.repositories.permissions-statement-read %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-5. 要下载日志,请使用 **Download logs(下载日志)**下拉菜单,然后选择要下载的日志。 ![下载日志下拉菜单](/assets/images/help/repository/download-logs-drop-down.png)
-
-### 删除日志
-
-您可以从工作流程运行中删除日志文件。 {% data reusables.repositories.permissions-statement-write %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-5. 要删除日志文件,单击 **Delete all logs(删除所有日志)**按钮并审查确认提示。 ![删除所有日志](/assets/images/help/repository/delete-all-logs.png) 删除日志后,**Delete all logs(删除所有日志)**按钮将被删除,以表明工作流程运行中未剩下任何日志文件。
-
-### 启用调试日志
-
-如果工作流程日志没有提供足够的详细信息来诊断工作流程、作业或步骤未按预期工作的原因,您可以启用额外的调试日志。
-
-这些额外的日志将通过在包含工作流程的仓库中设置密码来启用,因此将应用相同的权限要求:
-
-- {% data reusables.github-actions.permissions-statement-secrets-organization %}
-- {% data reusables.github-actions.permissions-statement-secrets-repository %}
-- {% data reusables.github-actions.permissions-statement-secrets-api %}
-
-有关设置密码的更多信息,请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-#### 启用运行程序诊断日志
-
-Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. 两个额外的日志文件被添加到日志存档中:
-
-* 运行程序进程日志,其中包含关于如何协调和设置运行程序执行作业的信息。
-* 工作程序进程日志,用于记录作业执行情况。
-
-1. 要启用运行程序诊断日志,请在包含工作流程的仓库中设置以下密码:将 `ACTIONS_RUNNER_DEBUG` 设置为 `true`。
-
-1. 要下载运行程序诊断日志,请下载工作流程运行情况的日志存档。 运行程序诊断日志包含在 `runner-diagnostic-logs` 文件夹中。 关于下载日志的更多信息,请参阅“[下载日志](#downloading-logs)”。
-
-#### 启用步骤调试日志
-
-步骤调试日志增加了作业执行期间和执行之后的作业日志的详细程度。
-
-1. 要启用步骤调试日志,必须在包含工作流程的仓库中设置以下密码:将 `ACTIONS_STEP_DEBUG` 设置为 `true`。
-
-1. 设置密码后,步骤日志中会显示更多调试事件。 更多信息请参阅[“查看日志以诊断故障”](#viewing-logs-to-diagnose-failures)。
-
-
-### 延伸阅读
-
-- “[关于 {% data variables.product.prodname_actions %}](/articles/about-github-actions)”
-- "[配置工作流程](/articles/configuring-a-workflow)"
-- "[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions)"
-- "[触发工作流程的事件](/articles/events-that-trigger-workflows)"
-- "[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)"
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts.md
deleted file mode 100644
index 5a5ecc8aec29..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts.md
+++ /dev/null
@@ -1,249 +0,0 @@
----
-title: 使用构件持久化工作流程数据
-intro: 构件允许您在工作流程完成后,分享工作流程中作业之间的数据并存储数据。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /articles/persisting-workflow-data-using-artifacts
- - /github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts
- - /actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于工作流程构件
-
-构件允许您在作业完成后保留数据,并与同一工作流程中的另一个作业共享该数据。 构件是指在工作流程运行过程中产生的文件或文件集。 例如,在工作流程运行结束后,您可以使用构件保存您的构建和测试输出。 对于推送和拉取请求, {% data variables.product.product_name %} 会将构件存储 90 天。 每当有人推送新提交到拉取请求时,拉取请求的保存期就会重新开始计算。
-
-以下是您可以上传的一些常见构件:
-
-- 日志文件和核心转储文件
-- 测试结果、失败和屏幕截图
-- 二进制或压缩文件
-- 压力测试性能输出和代码覆盖结果
-
-{% if currentVersion == "free-pro-team@latest" %}
-
-存储构件时使用存储空间 {% data variables.product.product_name %}。 {% data reusables.github-actions.actions-billing %} 更多信息请参阅“[管理 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)”。
-
-{% else %}
-
-项目会占用外部 Blob 存储上的存储空间,该存储为 {% data variables.product.prodname_actions %} 配置 {% data variables.product.product_location %}。
-
-{% endif %}
-
-构件会在工作流程运行过程中上传,您可以在 UI 中查看构件的名称和大小。 当构件使用 {% data variables.product.product_name %} UI 下载时, 作为构件一部分单独上传的所有文件都会压缩到一个 zip 文件中。 这意味着计费是根据上传的构件大小而不是 zip 文件的大小计算的。
-
-{% data variables.product.product_name %} 提供两项可用于上传和下载构建构件的操作。 更多信息请参阅 [action/upload-artifact](https://github.com/actions/upload-artifact) 和 [download-artifact](https://github.com/actions/download-artifact) 操作。
-
-要在作业之间共享数据:
-
-* **上传文件**:为上传的文件提供名称并在作业结束前上传数据。
-* **下载文件**:您只能下载在同一工作流程运行过程中上传的构件。 下载文件时,您可以通过名称引用该文件。
-
-作业步骤共享运行器机器的相同环境,但在其各自的进程中运行。 要在作业的步骤之间传递数据,您可以使用输入和输出。 有关输入和输出的更多信息,请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions)”。
-
-### 在工作流程中作业之间传递数据
-
-您可以使用 `upload-artifact` 和 `download-artifact` 操作在工作流程中的作业之间共享数据。 此示例工作流程说明如何在相同工作流程中的任务之间传递数据。 更多信息请参阅 [action/upload-artifact](https://github.com/actions/upload-artifact) 和 [download-artifact](https://github.com/actions/download-artifact) 操作。
-
-依赖于以前作业构件的作业必须等待依赖项成功完成。 此工作流程使用 `needs` 关键词确保 `job_1`、 `job_2` 和 `job_3` 按顺序运行。 例如, `job_2` 需要 `job_1` 使用 `needs: job_1` 语法。
-
-作业1执行以下步骤:
-- 执行数学计算并将结果保存到名为 `math-home-work.txt` 的文本文件。
-- 使用 `upload-artifact` 操作上传名为 `homework` 的 `math-homework.txt` 文件。 该操作将文件置于一个名为 `homework` 的目录中。
-
-作业 2 使用上一个作业的结果:
-- 下载上一个作业中上传的 `homework` 构件。 默认情况下, `download-artifact` 操作会将构件下载到该步骤执行的工作区目录中。 您可以使用 `path` 输入参数指定不同的下载目录。
-- 读取 `homework/math-homework.txt` 文件中的值,进行数学计算,并将结果保存到 `math-homework.txt`。
-- 更新 `math-homework.txt` 文件。 此上传会覆盖之前的上传,因为两次上传共用同一名称。
-
-作业 3 显示上一个作业中上传的结果:
-- 下载 `homework` 构件。
-- 将数学方程式的结果打印到日志中。
-
-此工作流程示例中执行的完整数学运算为 `(3 + 7) x 9 = 90`。
-
-```yaml
-name: Share data between jobs
-
-on: [push]
-
-jobs:
- job_1:
- name: Add 3 and 7
- runs-on: ubuntu-latest
- steps:
- - shell: bash
- run: |
- expr 3 + 7 > math-homework.txt
- - name: Upload math result for job 1
- uses: actions/upload-artifact@v2
- with:
- name: homework
- path: math-homework.txt
-
- job_2:
- name: Multiply by 9
- needs: job_1
- runs-on: windows-latest
- steps:
- - name: Download math result for job 1
- uses: actions/download-artifact@v2
- with:
- name: homework
- - shell: bash
- run: |
- value=`cat math-homework.txt`
- expr $value \* 9 > math-homework.txt
- - name: Upload math result for job 2
- uses: actions/upload-artifact@v2
- with:
- name: homework
- path: math-homework.txt
-
- job_3:
- name: Display results
- needs: job_2
- runs-on: macOS-latest
- steps:
- - name: Download math result for job 2
- uses: actions/download-artifact@v2
- with:
- name: homework
- - name: Print the final result
- shell: bash
- run: |
- value=`cat math-homework.txt`
- echo The result is $value
-```
-
-![要在作业之间传递数据以执行数学工作流程](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png)
-
-### 在工作流程运行之间共享数据
-
-一个工作流程结束后,您可以通过在 **Actions(操作)**选项卡中找到工作流程运行,下载 {% data variables.product.product_name %} 上已上传构件的压缩文件。 您还可以使用 {% data variables.product.prodname_dotcom %} REST API 来下载构件。 更多信息请参阅“[构件](/v3/actions/artifacts/)”。
-
-如果需要从以前的工作流运行访问项目,可以使用 REST API {% data variables.product.product_name %} 检索工件。 有关详细信息,请参阅"获取[项](/rest/reference/actions#artifacts)。
-
-### 上传构建和测试构件
-
-您可以创建持续集成 (CI) 工作流程来构建和测试您的代码。 关于使用 {% data variables.product.prodname_actions %} 执行 CI 的更多信息,请参阅“[关于持续集成](/articles/about-continuous-integration)”。
-
-构建和测试代码的输出通常会生成可用于调试测试失败的文件和可部署的生产代码。 您可以配置一个工作流程来构建和测试推送到仓库中的代码,并报告成功或失败状态。 您可以上传构建和测试输出,以用于部署、调试失败的测试或崩溃以及查看测试套件范围。
-
-您可以使用 `upload-artifact` 操作上传构件。 上传构件时,您可以指定单个文件或目录,或多个文件或目录。 您还可以排除某些文件或目录,以及使用通配符模式。 我们建议您为构件提供名称,但如果未提供名称,则会使用 `artifact` 作为默认名称。 有关语法的信息,请参阅 {% if currentVersion == "free-pro-team@latest" %}[操作/上传](https://github.com/actions/upload-artifact) 执行{% else %} `/上传项目` 操作 {% data variables.product.product_location %}{% endif %}。
-
-#### 示例
-
-例如,您的仓库或 Web 应用程序可能包含必须转换为 CSS 和 JavaScript 的 SASS 和 TypeScript 文件。 假设您的构建配置输出 `dist` 目录中已编译的文件,如果所有测试均已成功完成,则可将 `dist` 目录中的文件部署到您的 Web 应用程序服务器。
-
-```
-|-- hello-world (repository)
-| └── dist
-| └── tests
-| └── src
-| └── sass/app.scss
-| └── app.ts
-| └── output
-| └── test
-|
-```
-
-本例向您展示如何创建 Node.js 项目的工作流程,该项目在 `src` 目录中 `builds` 代码,并在 `tests` 目录中运行测试。 您可以假设运行 `npm test` 会产生名为 `code-coverage.html`、存储在 `output/test/` 目录中的代码覆盖报告。
-
-工作流程上传 `dist` 目录中的生产构件,但不包括任何 markdown 文件。 它还会上传 `code-coverage.html` 报告作为另一个构件。
-
-```yaml
-name: Node CI
-
-on: [push]
-
-jobs:
- build_and_test:
- runs-on: ubuntu-latest
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
- - name: npm install, build, and test
- run: |
- npm install
- npm run build --if-present
- npm test
- - name: Archive production artifacts
- uses: actions/upload-artifact@v2
- with:
- name: dist-without-markdown
- path: |
- dist
- !dist/**/*.md
- - name: Archive code coverage results
- uses: actions/upload-artifact@v2
- with:
- name: code-coverage-report
- path: output/test/code-coverage.html
-```
-
-![工作流程上传构件工作流程运行的图像](/assets/images/help/repository/upload-build-test-artifact.png)
-
-### 下载或删除构件
-
-在工作流程运行期间,您可以下载以前在同一工作流程运行中上传的构件。 在工作流程运行完成后,您可以使用工作流程运行历史记录在 GitHub 上下载或删除构件。
-
-#### 在工作流程运行期间下载构件
-
-[actions/download-artifact](https://github.com/actions/download-artifact) 操作可用于下载工作流程运行期间之前上传的构件。
-
-{% note %}
-
-**注**:您只能下载在同一工作流程运行过程中上传的构件。
-
-{% endnote %}
-
-指定构件的名称以下载单个构件。 如果在未指定名称的情况下上传构件目,则使用默认名称 `artifact`。
-
-```yaml
-- name: Download a single artifact
- uses: actions/download-artifact@v2
- with:
- name: my-artifact
-```
-
-您还可以不指定名称而下载工作流程运行中的所有构件。 如果您在处理大量构件,此功能非常有用。
-
-```yaml
-- name: Download all workflow run artifacts
- uses: actions/download-artifact@v2
-```
-
-如果下载所有工作流程运行的构件,则每个构件使用其名称目创建目录。
-
-For more information on syntax, see the [actions/download-artifact](https://github.com/actions/download-artifact) action.
-
-#### 工作流程运行完成后下载和删除构件
-
-构件在 90 天后自动过期,但您始终可以在构件于 {% data variables.product.product_name %} 上过期之前删除它们,回收已经使用的 {% data variables.product.prodname_actions %} 存储。
-
-{% warning %}
-
-**警告:** 构件一旦删除,便无法恢复。
-
-{% endwarning %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-1. 要下载构件,请使用 **Artifacts(构件)**下拉菜单,然后选择要下载的构件。 ![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png)
-1. 要删除构件,请使用 **Artifacts(构件)**下拉菜单,然后单击 {% octicon "trashcan" aria-label="The trashcan icon" %}。 ![删除构件下拉菜单](/assets/images/help/repository/actions-delete-artifact.png)
-
-{% if currentVersion == "free-pro-team@latest" %}
-
-### 延伸阅读
-
-- "[管理 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)".
-
-{% endif %}
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization.md
deleted file mode 100644
index e0b080ad77f5..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: 在组织内共享工作流程模板
-intro: 您可以专门为您的组织创建一组标准化的工作流程模板。 然后,组织成员在组织仓库中创建新的工作流程时可以使用模板。
-product: '{% data reusables.gated-features.actions %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-对组织的 `.github` 仓库具有写入权限的用户可以创建工作流程模板。 然后,有权限创建工作流程的组织成员便可使用这些模板。
-
-工作流程模板可用于在组织的公共仓库中创建新的工作流程;要使用模板在私有仓库中创建工作流程,该组织必须是企业或 GitHub One 计划的一部分。
-
-### 创建工作流程模板
-
-此过程展示如何创建工作流程模板和元数据文件。 元数据文件描述在用户新建工作流程时如何向其显示模板。
-
-1. 如果组织中没有名为 `.github` 的公共仓库,请新建一个。
-1. 创建一个名为 `workflow-templates` 的目录。
-1. 在 `workflow-templates` 目录中创建新的工作流程文件。
-
- 如果需要引用仓库的默认分支,可以使用 `$default-branch` 占位符。 使用模板创建工作流程时,占位符将自动替换为仓库默认分支的名称。
-
- 例如,下面这个名为 `octo-organization-ci.yml` 的文件展示了一个基本的工作流程。
-
- ```yaml
- name: Octo Organization CI
-
- on:
- push:
- branches: [ $default-branch ]
- pull_request:
- branches: [ $default-branch ]
-
- jobs:
- build:
- runs-on: ubuntu-latest
-
- steps:
- - uses: actions/checkout@v2
-
- - name: Run a one-line script
- run: echo Hello from Octo Organization
- ```
-1. 在 `workflow-templates` 目录中创建元数据文件。 元数据文件必须与工作流程文件同名,但扩展名不是 `.yml`,而必须附加 `.properties.json`。 例如,下面这个名为 `octo-organization-ci.properties.json` 的文件包含名为 `octo-organization-ci.yml` 的工作流程文件的元数据:
- ```yaml
- {
- "name": "Octo Organization Workflow",
- "description": "Octo Organization CI workflow template.",
- "iconName": "example-icon",
- "categories": [
- "Go"
- ],
- "filePatterns": [
- "package.json$",
- "^Dockerfile",
- ".*\\.md$"
- ]
- }
- ```
- * `name` - **必要。**工作流程模板的名称。 这会显示在可用模板列表中。
- * `description` - **必要。**工作流程模板的描述。 这会显示在可用模板列表中。
- * `iconName` - **必要。**定义模板列表中工作流程项目的图标。 `iconName` 必须是同名的 SVG 图标,且必须存储在 `workflow-templates` 目录中。 例如,名为 `example-icon.svg` 的 SVG 文件被引用为 `example-icon`。
- * `categories` - **可选。**定义工作流程的语言类别。 当用户查看可用模板时,匹配相同语言的模板将更加突出。 有关可用语言类别的信息,请参阅https://github.com/github/linguist/blob/master/lib/linguist/languages.yml。
- * `filePatterns` - **可选。**如果用户仓库在其根目录中有符合定义的正则表达式的文件,则允许使用模板。
-
-要添加另一个工作流模板,请将您的文件添加到同一 `workflow-templates` 目录中。 例如:
-
-![工作流程模板文件](/assets/images/help/images/workflow-template-files.png)
-
-### 使用工作流程模板
-
-此程序展示组织成员如何查找并使用工作流程模板来创建新的工作流程。 只要是组织成员,都可以使用组织的工作流程模板。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-1. 如果您的仓库已经有工作流程:在左上角单击 **New workflow(新工作流程)**。 ![创建新工作流程](/assets/images/help/repository/actions-new-workflow.png)
-1. 组织的工作流程模板位于其自己名为“_组织名称_创建的工作流程”的区域中。 在您想要使用的模板名称下,单击 **Set up this workflow(设置此工作流程)**。 ![设置此工作流程](/assets/images/help/settings/actions-create-starter-workflow.png)
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-databases-and-service-containers.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-databases-and-service-containers.md
deleted file mode 100644
index 6193de6fbad0..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-databases-and-service-containers.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 使用数据库和服务容器
-intro: 连接数据库和服务容器来管理工作流程工具。
-mapTopic: true
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/using-databases-and-services
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-environment-variables.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-environment-variables.md
deleted file mode 100644
index 43570a75f41e..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-environment-variables.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: 使用环境变量
-intro: '{% data variables.product.prodname_dotcom %} 为每个 {% data variables.product.prodname_actions %} 工作流程运行设置默认环境变量。 您也可以在工作流程文件中设置自定义环境变量。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /github/automating-your-workflow-with-github-actions/using-environment-variables
- - /actions/automating-your-workflow-with-github-actions/using-environment-variables
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于环境变量
-
-{% data variables.product.prodname_dotcom %} 设置适用于工作流程运行中每个步骤的默认环境变量。 环境变量区分大小写。 在操作或步骤中运行的命令可以创建、读取和修改环境变量。
-
-要设置自定义环境变量,您需要在工作流程文件中指定变量。 您可以使用 [`jobs..steps.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)、[`jobs..env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv) 和 [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) 关键字定义步骤、作业或整个工作流程的环境变量。 有关详细信息,请参阅"[的工作流 {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)。
-
-```yaml
-步骤:
- - 名称: 你好世界
- 运行: 回声你好世界 $FIRST_NAME $middle_name $Last_Name!
- env:
- FIRST_NAME: Mona
- middle_name: The
- Last_Name: Octocat
-```
-
-您也可以使用 `set-env` 工作流程命令来设置工作流程中以下步骤可以使用的环境变量。 `set-env` 命令可直接供操作使用,或使用 `run` 关键字作为工作流程文件中的 shell 命令。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)”。
-
-### 默认环境变量
-
-强烈建议操作使用环境变量访问文件系统,而非使用硬编码的文件路径。 {% data variables.product.prodname_dotcom %} 设置供操作用于所有运行器环境中的环境变量。
-
-| 环境变量 | 描述 |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `CI` | 始终设置为 `true`。 |
-| `HOME` | 用于存储用户数据的 {% data variables.product.prodname_dotcom %} 主目录路径。 例如 `/github/home`。 |
-| `GITHUB_WORKFLOW` | 工作流程的名称。 |
-| `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} |
-| `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} |
-| `GITHUB_ACTION` | 操作唯一的标识符 (`id`)。 |
-| `GITHUB_ACTIONS` | 当 {% data variables.product.prodname_actions %} 运行工作流程时,始终设置为 `true`。 您可以使用此变量来区分测试是在本地运行还是通过 {% data variables.product.prodname_actions %} 运行。 |
-| `GITHUB_ACTOR` | 发起工作流程的个人或应用程序的名称。 例如 `octocat`。 |
-| `GITHUB_REPOSITORY` | 所有者和仓库名称。 例如 `octocat/Hello-World`。 |
-| `GITHUB_EVENT_NAME` | 触发工作流程的 web 挂钩事件的名称。 |
-| `GITHUB_EVENT_PATH` | 具有完整 web 挂钩事件有效负载的文件路径。 例如 `/github/workflow/event.json`。 |
-| `GITHUB_WORKSPACE` | {% data variables.product.prodname_dotcom %} 工作空间目录路径。 如果您的工作流程使用 [actions/checkout](https://github.com/actions/checkout) 操作,工作空间目录将包含存储仓库副本的子目录。 如果不使用 `actions/checkout` 操作,该目录将为空。 例如 `/home/runner/work/my-repo-name/my-repo-name`。 |
-| `GITHUB_SHA` | 触发工作流程的提交 SHA。 例如 `ffac537e6cbbf934b08745a378932722df287a53`。 |
-| `GITHUB_REF` | 触发工作流程的分支或标记参考。 例如 `refs/heads/feature-branch-1`。 如果分支或标记都不适用于事件类型,则变量不会存在。 |
-| `GITHUB_HEAD_REF` | 仅为复刻的仓库设置。 头部仓库的分支。 |
-| `GITHUB_BASE_REF` | 仅为复刻的仓库设置。 基础仓库的分支。 |
-| `GITHUB_SERVER_URL` | 返回 {% data variables.product.product_name %} 服务器的 URL。 当 {% data variables.product.prodname_actions %} 运行工作流程时,始终设置为 `true`。 |
-| `GITHUB_API_URL` | 返回 API URL。 返回 {% data variables.product.product_name %} 服务器的 URL。 例如:`https://github.com`。 |
-| `GITHUB_GRAPHQL_URL` | 返回 GraphQL API URL。 例如:`https://api.github.com/graphql`。 |
-
-### 环境变量命名约定
-
-{% note %}
-
-**注:** {% data variables.product.prodname_dotcom %} 会保留 `GITHUB_` 环境变量前缀供 {% data variables.product.prodname_dotcom %} 内部使用。 设置有 `GITHUB_` 前缀的环境变量或密码将导致错误。
-
-{% endnote %}
-
-您设置的指向文件系统上某个位置的任何新环境变量都应该有 `_PATH` 后缀。 `HOME` 和 `GITHUB_WORKSPACE` 默认变量例外于此约定,因为 "home" 和 "workspace" 一词已经暗示位置。
diff --git a/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow.md b/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow.md
deleted file mode 100644
index 1358ade7654e..000000000000
--- a/translations/zh-CN/content/actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 在工作流程中使用变量和密码
-intro: 在工作流中使用加密密码、变量和令牌保护仓库。
-mapTopic: true
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/getting-started-with-github-actions/about-github-actions.md b/translations/zh-CN/content/actions/getting-started-with-github-actions/about-github-actions.md
deleted file mode 100644
index df91a68a4d17..000000000000
--- a/translations/zh-CN/content/actions/getting-started-with-github-actions/about-github-actions.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: 关于 GitHub 操作
-intro: '{% data variables.product.prodname_actions %} 可让您直接在 {% data variables.product.prodname_dotcom %} 仓库中创建自定义软件开发生命周期 (SDLC) 工作流程。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax/
- - /articles/about-github-actions
- - /github/automating-your-workflow-with-github-actions/about-github-actions
- - /actions/automating-your-workflow-with-github-actions/about-github-actions
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于 {% data variables.product.prodname_actions %}
-
-{% data reusables.repositories.about-github-actions %} 工作流程是您可以在仓库中创建的自定义自动化流程,用于在 {% data variables.product.prodname_dotcom %} 上构建、测试、封装、发行或部署任何代码项目。
-
-{% data reusables.repositories.actions-ci-cd %} {% data variables.product.prodname_actions %} 支持 {% data variables.product.prodname_dotcom %} 的内置持续集成服务。 更多信息请参阅“[关于持续集成](/articles/about-continuous-integration)”。
-
-工作流程在 {% data variables.product.prodname_dotcom %} 托管的计算机(称为“运行器”)上的 Linux、macOS、Windows 和容器中运行。 或者,您也可以托管自己的运行器,以在您拥有或管理的计算机上运行工作流程。 更多信息请参阅“[关于自托管运行器](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。
-
-您可以使用仓库中定义的操作、{% data variables.product.prodname_dotcom %} 上公共仓库中的开源操作或者发布的 Docker 容器图像来创建工作流程。 复刻仓库中的工作流程默认不运行。
-
-您可以在 {% data variables.product.prodname_dotcom %} 上发现要用于工作流程的操作,以及创建要与 {% data variables.product.prodname_dotcom %} 社区共享的操作。 有关创建自定义操作的更多信息,请参阅“[创建操作](/actions/creating-actions)”。
-
-您可以创建配置为对特定事件运行的工作流程文件。 更多信息请参阅“[配置工作流程](/articles/configuring-a-workflow)”和“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions)”。
-
-有关常用术语的定义,请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)”。
-
-### 发现 {% data variables.product.prodname_dotcom %} 社区中的操作
-
-{% data variables.product.prodname_marketplace %} 是一个中心位置,您可以查找、分享和使用由 {% data variables.product.prodname_dotcom %} 社区构建的操作。 更多信息请参阅“[在工作流程中使用 {% data variables.product.prodname_marketplace %} 中的操作](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)”。
-
-您也可以使用 {% data variables.product.prodname_dotcom %} 的公共仓库中分享的开源操作自定义项目,以及使用 [actions](https://github.com/actions) 组织中 {% data variables.product.prodname_dotcom %} 构建的操作。
-
-### 禁用或限制仓库或组织的 {% data variables.product.prodname_actions %}
-
-{% data reusables.github-actions.disabling-github-actions %}
-
-更多信息请参阅“[禁用或限制仓库的 {% data variables.product.prodname_actions %}](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository)”或“[禁用或限制组织的 {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)”。
-
-### 工作流程运行通知
-
-{% data reusables.repositories.workflow-notifications %}
-
-### 使用限制
-
-{% data reusables.github-actions.github-actions-usage-limits %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-
-### 使用策略
-
-除了使用限制外,还必须确保使用 [GitHub 服务条款](/articles/github-terms-of-service/) 中的 {% data variables.product.prodname_actions %}。 有关 {% data variables.product.prodname_actions %} 特定条款的更多信息,请参阅 [GitHub 附加产品条款](/github/site-policy/github-additional-product-terms#a-actions-usage)。
-
-### 关于 {% data variables.product.prodname_actions %} 的计费
-
-{% data reusables.github-actions.actions-billing %} 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)”。
-
-### 联系支持
-
-{% data reusables.github-actions.contacting-support %}
-
-{% endif %}
-
-### 延伸阅读
-
-- "[管理工作流程运行](/articles/managing-a-workflow-run)"
-- "[触发工作流程的事件](/articles/events-that-trigger-workflows)"
-- "[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)"
-"[管理 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)"
diff --git a/translations/zh-CN/content/actions/getting-started-with-github-actions/core-concepts-for-github-actions.md b/translations/zh-CN/content/actions/getting-started-with-github-actions/core-concepts-for-github-actions.md
deleted file mode 100644
index a9ec407177b2..000000000000
--- a/translations/zh-CN/content/actions/getting-started-with-github-actions/core-concepts-for-github-actions.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: GitHub 操作的核心概念
-shortTitle: 核心概念
-intro: '下面是我们在网站和 {% data variables.product.prodname_actions %} 文档中使用的常见 {% data variables.product.prodname_actions %} 术语列表。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
- - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 操作
-
-合并为作业创建步骤的个别任务。 操作是工作流程最小的便携式构建块。 您可以创建自己的操作,使用 {% data variables.product.prodname_dotcom %} 社区共享的操作,以及自定义公共操作。 要在工作流程中使用操作,必须将其作为一个步骤。
-
-### 构件
-
-构件是创建并测试代码时所创建的文件。 例如,构件可能包含二进制或包文件、测试结果、屏幕截图或日志文件。 工件与其创建时所在的工作流程运行相关,可被另一个作业使用,也可以部署。
-
-### 持续集成 (CI)
-
-经常提交小代码更改到共享仓库的软件开发实践。 通过 {% data variables.product.prodname_actions %} 可以创建自定义 CI 工作流程,以自动构建和测试您的代码。 从您的仓库,您可以在工作流程中查看代码更改的状态和每个操作的详细日志。 CI 对代码更改提供即时反馈以便更快地检测并解决错误,从而节省开发者的时间。
-
-### 持续部署 (CD)
-
-持续部署建立在持续集成的基础上。 当新代码提交并通过您的 CI 测试时,该代码将自动部署到生产中。 通过 {% data variables.product.prodname_actions %} 可以创建自定义 CD 工作流程,以将您的代码自动从仓库部署到任何云、自托管服务或平台。 CD 通过自动执行部署过程来节省开发者的时间,并且将经过测试的稳定代码更快地部署到您的客户。
-
-### Event
-
-触发工作流程运行的特定活动。 例如,当有推送提交到仓库或者创建议题或拉取请求时,{% data variables.product.prodname_dotcom %} 就可能产生活动。 您也可以使用仓库分发 web 挂钩配置一个工作流程在外部事件发生时运行。
-
-### {% data variables.product.prodname_dotcom %} 托管的运行器
-{% data variables.product.prodname_dotcom %} 可托管 Linux、Windows 和 macOS 运行器。 作业在包含常用、预安装的软件的全新虚拟机实例中运行。 {% data variables.product.prodname_dotcom %} 对 {% data variables.product.prodname_dotcom %} 托管的运行器执行所有升级和维护。 您不能自定义 {% data variables.product.prodname_dotcom %} 托管的运行器的硬件配置。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)”。
-
-### 作业
-
-在同一运行服务器上执行的一组步骤。 您可以定义作业在工作流程文件中运行的依赖规则。 作业可以同时并行运行,也可以根据上一个作业的状态按顺序运行。 例如,工作流程可以有两个连续的任务来构建和测试代码,其中测试作业取决于构建作业的状态。 如果构建作业失败,测试作业将不会运行。 对于 {% data variables.product.prodname_dotcom %} 托管的运行器,工作流程中的每项作业都会在一个新的虚拟环境实例中运行。
-
-### 运行器
-
-已安装 {% data variables.product.prodname_actions %} 运行器应用程序的任何机器。 您可以使用 {% data variables.product.prodname_dotcom %} 托管的运行器或托管您自己的运行器。 运行器等待可用的作业。 当运行器选择作业时,它会运行该作业的操作 ,并将进度、日志和最终结果报告回 {% data variables.product.prodname_dotcom %}。 运行器一次运行一个作业。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器](#github-hosted-runner)”和“[自托管运行器](#self-hosted-runner)”。
-
-{% note %}
-
-**注意:** {% data reusables.github-actions.runner-app-open-source %}
-
-{% endnote %}
-
-### 自托管运行器
-
-您管理和维护并且安装了自托管运行器应用程序的机器。 {% data reusables.github-actions.self-hosted-runner-description %} 更多信息请参阅“[托管您自己的运行器](/github/automating-your-workflow-with-github-actions/hosting-your-own-runners)”。
-
-### 步骤
-
-步骤是可以运行命令或操作的单个任务。 作业配置一个或多个步骤。 作业中的每个步骤在同一运行器中执行,让该作业中的操作使用文件系统共享信息。
-
-### 虚拟环境
-
-{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境包括虚拟机器的硬件配置、操作系统和已安装的软件。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)”。
-
-### 工作流程
-
-您可以在仓库中创建的可配置自动化流程,用于在 {% data variables.product.prodname_dotcom %} 上构建、测试、封装、发行或部署任何项目。 工作流程由一项或多项作业组成,可以计划或由事件激活。
-
-### 工作流程文件
-
-定义至少有一项作业的工作流程配置的 YAML 文件。 此文件位于 {% data variables.product.prodname_dotcom %} 仓库根目录的 `.github/workflows` 目录下。
-
-### 工作流程运行
-
-当预配置的事件发生时运行的工作流程实例。 您可以查看每个工作流程运行的作业、操作、日志和状态。
diff --git a/translations/zh-CN/content/actions/getting-started-with-github-actions/index.md b/translations/zh-CN/content/actions/getting-started-with-github-actions/index.md
deleted file mode 100644
index 87ceaddb35c2..000000000000
--- a/translations/zh-CN/content/actions/getting-started-with-github-actions/index.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: GitHub 操作使用入门
-shortTitle: 入门指南
-intro: '{% data variables.product.prodname_actions %} 具有融入工作流程每个步骤的强大执行环境。 您可以发现、创建和分享 {% data variables.product.prodname_actions %} 以执行您喜欢的任何工作。'
-redirect_from:
- - /articles/getting-started-with-github-actions
- - /github/automating-your-workflow-with-github-actions/getting-started-with-github-actions
- - /actions/automating-your-workflow-with-github-actions/getting-started-with-github-actions
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% topic_link_in_list /overview %}
- {% link_in_list /about-github-actions %}
- {% link_in_list /core-concepts-for-github-actions %}
- {% link_in_list /security-hardening-for-github-actions %}
-{% topic_link_in_list /using-community-workflows-and-actions %}
- {% link_in_list /starting-with-preconfigured-workflow-templates %}
- {% link_in_list /using-actions-from-github-marketplace %}
diff --git a/translations/zh-CN/content/actions/getting-started-with-github-actions/overview.md b/translations/zh-CN/content/actions/getting-started-with-github-actions/overview.md
deleted file mode 100644
index 09a1e130c8c5..000000000000
--- a/translations/zh-CN/content/actions/getting-started-with-github-actions/overview.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 概览
-intro: '了解 {% data variables.product.prodname_actions %} 概念和术语。'
-mapTopic: true
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/getting-started-with-github-actions/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/getting-started-with-github-actions/security-hardening-for-github-actions.md
deleted file mode 100644
index 3da29637a21d..000000000000
--- a/translations/zh-CN/content/actions/getting-started-with-github-actions/security-hardening-for-github-actions.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: GitHub 操作的安全强化
-shortTitle: 安全强化
-intro: '使用 {% data variables.product.prodname_actions %} 功能的良好安全实践。'
-product: '{% data reusables.gated-features.actions %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-本指南介绍如何为某些 {% data variables.product.prodname_actions %} 功能配置安全强化。 如果不熟悉 {% data variables.product.prodname_actions %} 概念,请参阅“[GitHub 操作的核心概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)”。
-
-### 使用密码
-
-敏感值绝不能以明文存储在工作流程文件中,而应存储为密码。 [密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)可在组织或仓库级配置,可用于在 {% data variables.product.product_name %} 中存储敏感信息。
-
-密码使用 [Libsodium 密封箱](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes),以使它们在到达 {% data variables.product.product_name %} 前被加密处理。 [使用 UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) 或通过 [REST API](/rest/reference/actions#secrets) 提交密码时就会发生这种情况。 此客户端加密有助于最大程度地减少与 {% data variables.product.product_name %}基础架构中的意外日志记录相关的风险(例如,异常日志和请求日志等)。 密钥在上传后,{% data variables.product.product_name %} 可对其进行解密,以便它能够被注入工作流程运行时。
-
-为了帮助防止意外泄露,{% data variables.product.product_name %} 使用一种机制尝试对运行日志中显示的任何密码进行编校。 此编校会寻找任何已配置密码的精确匹配项,以及值的常见编码,如 Base64。 但是,由于密码值可以通过多种方式转换,因此不能保证此编校。 因此,你应该采取某些积极主动的步骤和良好的做法,以帮助确保密码得到编校, 并限制与密码相关的其他风险:
-
-- **切勿将结构化数据用作密码**
- - 非结构化数据可能导致日志中的密码编校失败,因为编校很大程度上取决于查找特定密码值的完全匹配项。 例如,不要使用 JSON、XML 或 YAML(或类似)的 Blob 来封装密码值,否则会显著降低密码被正确编校的可能性。 而应为每个敏感值创建单独的密码。
-- **注册工作流程中使用的所有密码**
- - 如果密码用于生成工作流程中的另一个敏感值,则该生成的值应正式[注册为密码](https://github.com/actions/toolkit/tree/master/packages/core#setting-a-secret),使其出现在日志中时将会得到编校。 例如,如果使用私钥生成签名的 JWT 来访问 Web API,请确保将该 JWT 注册为密码,否则,如果它进入日志输出,则不会得到编校。
- - 注册密码也适用于任何类型的转换/编码。 如果以某种方式(如 Base64 或 URL 编码)转换您的密码,请确保将新值也注册为密码。
-- **审核如何处理密码**
- - 审核密码的使用方式,以帮助确保按预期方式处理密码。 您可以通过检查执行工作流程的仓库的源代码并检查工作流程中使用的任何操作来进行审核。 例如,确认它们未发送到非预期主机,或明确打印到日志输出。
- - 在测试有效/无效输入后查看工作流程的运行日志,并确认密码已正确编校或未显示。 您调用的命令或工具如何向 `STDOUT` 和 `STDERR` 发送错误并不总是很明显,密码随后可能会在错误日志中生成错误。 因此,在测试有效和无效的输入后,最好是手动查看工作流程日志。
-- **使用最小范围的凭据**
- - 确保工作流程中使用的凭据具有所需的最小权限,并请注意,任何对仓库具有写入权限的用户都可访问仓库中配置的所有密码。
-- **审核并轮换注册密码**
- - 定期查查已注册的密码,以确认它们仍是必需的。 删除不再需要的密码。
- - 定期轮换密码,以减小泄露的密码有效的时间窗。
-
-### 使用第三方操作
-
-工作流程中的个别作业可以与其他作业相互作用(和妥协)。 例如,查询以后作业使用的环境变量,将文件写入以后作业处理的共享目录,或者更直接地与 Docker 套接字接交互,以及检查其他正在运行的容器并执行其中的命令。
-
-这意味着工作流程中单一操作的泄露可能很严重,因为这个泄露的操作可以访问您仓库中配置的所有密码, 并且可以使用 `GITHUB_TOKENN` 写入仓库。 因此,从 {% data variables.product.prodname_dotcom %} 上的第三方仓库获取操作的风险很大。 您可以遵循以下良好做法来帮助降低此风险:
-
-* **将操作固定到全长提交 SHA**
-
- 将操作固定到全长提交 SHA 是当前将操作用作不可变版本的唯一方法。 固定到特定 SHA 有助于降低恶意执行者向操作仓库添加后门的风险,因为他们需要为有效的 Git 对象负载生成 SHA-1 冲突。
-
- {% warning %}
-
- **警告** 提交 SHA 的简短版本不安全,绝不可用于指定操作的 Git 引用。 由于仓库网络的工作方式,任何用户都可以复刻仓库,将精心编写的提交推送到与短 SHA 冲突的仓库。 这会导致该 SHA 上的后续克隆失败,因为它成为不明确的提交。 因此,使用缩短的 SHA 的任何工作流程将立即失败。
-
- {% endwarning %}
-* **审核操作的源代码**
-
- 确保操作按照预期处理仓库和密码的内容。 例如,确认密码未发送到非预期主机,或者没有被无意中记录。
-
-* **仅当您信任创建者时,才将操作固定到标记**
-
- 尽管固定到提交 SHA 是最安全的选项,但指定标记更方便,而且被广泛使用。 如果要指定标记,请确保信任该操作的创建者。 {% data variables.product.prodname_marketplace %} 上的“已验证创建者”徽章是一个有用的信号,因为它表示该操作是由其身份已被 {% data variables.product.prodname_dotcom %} 验证的团队编写的。 请注意,即使您信任作者,这种方法也存在风险,因为如果恶意执行者获得对存储操作的仓库的访问权限,便可移动或删除标记。
-
-### 考虑跨仓库访问
-
-{% data variables.product.product_name %} 的范围有意设为每次一个仓库。 工作流程环境中使用的 `GITHUB_TOKEN` 授予与具有写入权限的用户相同的访问级别,因为任何具有写入权限的用户都可通过创建或修改工作流程文件来访问此令牌。 用户对每个仓库都有特定权限,因此,如果不谨慎实施,一个仓库的 `GITHUB_TOKEN` 库授予对另一个仓库的访问权限将会影响 {% data variables.product.prodname_dotcom %} 权限模型。 同样,在向工作流程环境添加 {% data variables.product.prodname_dotcom %} 授权令牌时也必须谨慎,因为这也会因无意中向协作者授予一般权限而影响 {% data variables.product.prodname_dotcom %} 权限模型。
-
-我们已经[制定 {% data variables.product.prodname_dotcom %} 路线图](https://github.com/github/roadmap/issues/74),以支持允许在 {% data variables.product.product_name %} 内跨仓库访问的流程,但这还不是一项受支持的功能。 目前,执行特权跨仓库交互的唯一方法就是将 {% data variables.product.prodname_dotcom %} 身份验证令牌或 SSH 密钥作为工作流程环境中的密码。 由于许多身份验证令牌类型不允许对特定资源进行细致的访问,因此使用错误的令牌类型存在很大风险,因为它可以授予比预期范围更广泛的访问。
-
-此列表描述建议用于在工作流程中访问仓库数据的方法,按优先顺序降序排列:
-
-1. **工作流程环境中的 `GITHUB_TOKEN`**
- - 此令牌的范围有意设为调用工作流程的单个仓库,并且具有与仓库具有写入权限的用户的访问级别相同。 令牌在每个作业开始之前创建,在作业完成时过期。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
- - 应尽可能使用 `GITHUB_TOKEN`。
-2. **仓库部署密钥**
- - 部署密钥是唯一授予对单个存储库的读取或写入访问权限的凭据类型之一,可用于与工作流程中的另一个仓库进行交互。 更多信息请参阅“[管理部署密钥](/developers/overview/managing-deploy-keys#deploy-keys)”。
- - 请注意,部署密钥只能使用 Git 克隆和推送到仓库,不能用于与 REST 或 GraphQL API 进行交互,因此它们可能不适合您的要求。
-3. **{% data variables.product.prodname_github_app %} 令牌**
- - {% data variables.product.prodname_github_apps %} 可以安装在选择的仓库上,甚至可以对其中的资源设置细致的访问权限。 您可以创建组织内部的 {% data variables.product.prodname_github_app %},将其安装在工作流程中您需要访问的仓库上,并在工作流程中验证为安装以访问这些仓库。
-4. **个人访问令牌**
- - 切勿使用您自己帐户的个人访问令牌。 这些令牌授予您访问组织中您有权访问的所有仓库,以及您的用户帐户中的所有个人仓库。 这间接地向所有能写入工作流程所在仓库的用户授予广泛访问权限。 此外,如果您以后离开组织,使用此令牌的工作流程将立即中断,而且调试此问题可能具有挑战性。
- - 如果使用个人访问令牌,应是为新帐户生成的令牌,该帐户仅被授予对工作流程所需的特定仓库的访问权限。 请注意,此方法不可扩展,应避免采用其他方法,例如部署密钥。
-5. **用户帐户上的 SSH 密钥**
- - 工作流程不应使用用户帐户上的 SSH 密钥。 与个人访问令牌类似,它们授予对所有个人仓库以及通过组织成员资格访问的所有仓库的读/写权限。 这间接地向所有能写入工作流程所在仓库的用户授予广泛访问权限。 如果您打算使用 SSH 密钥,因为您只需要执行仓库克隆或推送,并且不需要与公共 API 交互,则应该使用单独的部署密钥。
-
-### 自托管运行器的强化
-
-**{% data variables.product.prodname_dotcom %} 托管的**运行程序在临时和干净的隔离虚拟机中执行代码,这意味着无法持续破坏此环境,可以访问的信息不会超过引导过程中此环境中存在的信息。
-
-{% data variables.product.product_name %} 上**自托管**的运行器不能保证在临时干净的虚拟机中运行,并且可能会持续受到工作流程中不受信任的代码的损害。
-
-因此,自托管的运行器几乎[永远不能用于 {% data variables.product.product_name %} 上的公共仓库](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories),因为任何用户都可以打开针对仓库的拉取请求并破坏环境。 同样,在私有仓库上使用自托管运行器时也要小心,因为任何可以复刻仓库并打开 PR 的人(通常是对仓库具有读取权限的人)都能够破坏自托管运行器环境,包括访问密码以及可授予仓库写入权限的特权 `GITHUB_TOKEN` 。
-
-您还应考虑自托管运行器机器的环境:
-- 配置为自托管运行器的计算机上存储哪些敏感信息? 例如,私有 SSH 密钥、API 访问令牌等。
-- 计算机是否可通过网络访问敏感服务? 例如,Azure 或 AWS 元数据服务。 此环境中的敏感信息量应保持在最低水平,您应该始终注意,任何能够调用工作流程的用户都有权访问此环境。
diff --git a/translations/zh-CN/content/actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates.md b/translations/zh-CN/content/actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates.md
deleted file mode 100644
index 579f101581bd..000000000000
--- a/translations/zh-CN/content/actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 从预配置的工作流程模板开始
-intro: '{% data variables.product.prodname_dotcom %} 提供预配置的工作流程模板以自动化工作流程或为特定语言和框架创建 CI 工作流程。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/starting-with-preconfigured-workflow-templates
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于工作流程模板
-
-{% data variables.product.product_name %} 分析代码并显示最适合仓库的 CI 模板。 例如,如果仓库包含 Node.js 代码,您就会看到 Node.js 项目的建议。 您可以使用工作流程模板作为基础来构建自定义工作流程,或按原样使用模板。
-
-您可以在 [actions/starter-workflows](https://github.com/actions/starter-workflows/tree/master/ci) 仓库中浏览 CI 模板的完整列表。 您还可以查找用于自动化工作流程的模板。 您还可以查找用于自动化工作流程的模板。
-
-### 添加第一个工作流程模板
-
-如果尚未将工作流程添加到仓库,您将看到可供选择的工作流程模板列表。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.actions-set-up-workflow-template %}
-
-### 添加附加工作流程模板
-
-如果您已有工作流程并希望添加新的模板工作流程,则可以导航到工作流程模板。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.actions-new-workflow %}
-{% data reusables.repositories.actions-set-up-workflow-template %}
diff --git a/translations/zh-CN/content/actions/getting-started-with-github-actions/using-actions-from-github-marketplace.md b/translations/zh-CN/content/actions/getting-started-with-github-actions/using-actions-from-github-marketplace.md
deleted file mode 100644
index 88389e5bc657..000000000000
--- a/translations/zh-CN/content/actions/getting-started-with-github-actions/using-actions-from-github-marketplace.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: 使用 GitHub Marketplace 中的操作
-intro: '您可以在 {% data variables.product.prodname_marketplace %} 中浏览和搜索要用于工作流程的操作。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions
- - /actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于 {% data variables.product.prodname_marketplace %} 中的操作
-
-{% data variables.product.prodname_marketplace %} 是一个中心位置,可供查找由 {% data variables.product.prodname_dotcom %} 社区构建的操作。 带有徽章的操作表示 {% data variables.product.prodname_dotcom %} 已验证操作的创建者为合作伙伴组织。
-
-{% data reusables.actions.enterprise-marketplace-actions %}
-
-您可以从 {% data variables.product.prodname_dotcom %} 上的工作流程编辑器以及从 [{% data variables.product.prodname_marketplace %} 页面发现新的操作](https://github.com/marketplace/actions/)。
-
-直接在工作流程编辑器中查看操作可以快速访问 {% data variables.product.prodname_marketplace %} 中的所有操作。 {% data variables.product.prodname_marketplace %} 操作页面提供了更大的灵活性,可以按类别过滤操作。
-
-### 在工作流程编辑器中浏览操作
-
-您可以直接在仓库的工作流程编辑器中搜索和浏览操作。 从边栏可以搜索特定的操作、查看特色操作和浏览特色类别。 您也可以查看操作从 {% data variables.product.prodname_dotcom %} 社区获得的星标数。
-
-1. 在仓库中,浏览至要编辑的工作流程文件。
-1. 要打开工作流程编辑器,在文件视图右上角单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑工作流程文件按钮](/assets/images/help/repository/actions-edit-workflow-file.png)
-1. 在编辑器右侧,使用 {% data variables.product.prodname_marketplace %} 边栏浏览操作。 ![Marketplace 工作流程边栏](/assets/images/help/repository/actions-marketplace-sidebar.png)
-
-### 浏览 {% data variables.product.prodname_marketplace %} 中的操作
-
-您可以在 [{% data variables.product.prodname_marketplace %} 操作页面](https://github.com/marketplace/actions/)找到相同的操作。 在 {% data variables.product.prodname_marketplace %} 页面上,您有更大的灵活性按类别和验证过滤操作。
-
-### 从工作流程编辑器添加操作到您的工作流程
-
-操作的列表页包括操作的版本以及使用操作所需的工作流程语法。
-
-1. 导航到要在工作流程中使用的操作。
-1. 在“Installation(安装)”下,单击 {% octicon "clippy" aria-label="The edit icon" %} 复制工作流程语法。 ![查看操作列表](/assets/images/help/repository/actions-sidebar-detailed-view.png)
-1. 将语法粘贴为工作流程中的新步骤。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)”。
-1. 如果操作要求您提供变量,请将其设置在工作流程中。 有关操作可能需要哪些变量的信息,请参阅 {% data variables.product.prodname_marketplace %} 中的操作完整列表。
-
-{% if currentVersion == "free-pro-team@latest" %}
-
-{% data reusables.dependabot.version-updates-for-actions %}
-
-{% endif %}
diff --git a/translations/zh-CN/content/actions/getting-started-with-github-actions/using-community-workflows-and-actions.md b/translations/zh-CN/content/actions/getting-started-with-github-actions/using-community-workflows-and-actions.md
deleted file mode 100644
index 25d6a1907413..000000000000
--- a/translations/zh-CN/content/actions/getting-started-with-github-actions/using-community-workflows-and-actions.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 使用社区工作流程和操作
-intro: '使用其他人和组织构建的操作和工作流程,包括 {% data variables.product.prodname_dotcom %}。'
-mapTopic: true
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners.md
deleted file mode 100644
index f8e3e9639af3..000000000000
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: 管理自托管运行器的访问权限
-intro: 您可以控制哪些仓库可以将作业发送给组织的自托管运行器。
-versions:
- free-pro-team: '*'
----
-
-在组织级别添加的自托管运行器可以处理组织中所有仓库的作业。 如果需要限制对自托管运行器的访问权限,可以将策略配置为仅处理私有仓库的作业,或者定义允许的仓库列表。
-
-### 控制哪些存储库可以访问组织的运行器
-
-{% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.settings-sidebar-actions %}
-1. 在“Self-hosted runners(自托管运行器)”旁边,单击 **Manage repository permissions(管理仓库权限)**。 ![管理仓库权限](/assets/images/help/settings/actions-runner-manage-permissions.png)
-
-1. 从下拉菜单中选择以下选项之一:
-
- * **All repositories(所有仓库)** - 组织中的所有公共和私有仓库都可以向组织的自托管运行器发送作业。
- * **Private repositories(私有仓库)** - 只有组织中的私有仓库才能向组织的自托管运行器发送作业。
- * **Selected repositories(选定的仓库)** - 使用仓库选择菜单选择组织中的哪些仓库可以向组织的自托管运行器发送作业。
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-ant.md b/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-ant.md
deleted file mode 100644
index e11e40baf9f0..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-ant.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: 使用 Ant 构建和测试 Java
-intro: 您可以在 GitHub 操作中创建持续集成 (CI) 工作流程,以使用 Ant 构建和测试 Java 项目。
-product: '{% data reusables.gated-features.actions %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南介绍如何使用 Ant 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败; 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以从工作流程运行上传构件。
-
-{% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件,包括 Java Development Kits (JDKs) 和 Ant。 有关软件以及 JDK 和 Ant 预安装版本的列表,请参阅 [{% data variables.product.prodname_dotcom %} 自托管运行器上安装的软件](/actions/automating-your-workflow-with-github-actions/software-installed-on-github-hosted-runners)。
-
-### 基本要求
-
-您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅:
-- "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
-- "[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)"
-
-建议您对 Java 和 Ant 框架有个基本的了解。 更多信息请参阅“[Apache Ant 手册](https://ant.apache.org/manual/)”。
-
-{% data reusables.actions.enterprise-setup-prereq %}
-
-### 从 Ant 工作流程模板开始
-
-{% data variables.product.prodname_dotcom %} 提供有 Ant 工作流程模板,应该适用于大多数基于 Ant 的 Java 项目。 更多信息请参阅 [Ant 工作流程模板](https://github.com/actions/starter-workflows/blob/master/ci/ant.yml)。
-
-要快速开始,您可以在创建新工作流程时选择预配置的 Ant 模板。 更多信息请参阅“[从预配置的工作流程模板开始](/actions/automating-your-workflow-with-github-actions/starting-with-preconfigured-workflow-templates)”。
-
-您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。
-
-{% raw %}
-```yaml
-name: Java CI
-
-on: [push]
-
-jobs:
- build:
- runs-on: ubuntu-latest
-
- steps:
- - uses: actions/checkout@v2
- - name: Set up JDK 1.8
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Build with Ant
- run: ant -noinput -buildfile build.xml
-```
-{% endraw %}
-
-此工作流程执行以下步骤:
-
-1. `checkout` 步骤在运行器上下载仓库的副本。
-2. `setup-java` 步骤配置 Java 1.8 JDK。
-3. “使用 Ant 构建”步骤以非交互模式运行 `build.xml` 中的默认目标。
-
-在创建构建和测试工作流程时,默认工作流模板是很好的起点,然后您可以自定义模板以满足项目的需求。
-
-{% data reusables.github-actions.example-github-runner %}
-
-{% data reusables.github-actions.java-jvm-architecture %}
-
-### 构建和测试代码
-
-您可以使用与本地相同的命令来构建和测试代码。
-
-初学者工作流程将运行 _build.xml_ 文件中指定的默认目标。 默认目标通常设置为将类、运行测试和包类设置为其可分发格式,例如 JAR 文件。
-
-如果使用不同的命令来构建项目,或者想要运行不同的目标,则可以指定这些命令。 例如,您可能想要运行在 _build-ci.xml_ 文件中配置的 `jar` 目标。
-
-{% raw %}
-```yaml
-steps:
- - uses: actions/checkout@v2
- - uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Run the Ant jar target
- run: ant -noinput -buildfile build-ci.xml jar
-```
-{% endraw %}
-
-### 将工作流数据打包为构件
-
-构建成功且测试通过后,您可能想要上传生成的 Java 包作为构件。 这会将构建的包存储为工作流程运行的一部分,并允许您下载它们。 构件可帮助您在拉取请求合并之前在本地环境中测试并调试它们。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
-
-Ant 通常会在 `build/jar` 目录中创建 JAR、EAR 或 WAR 等输出文件。 您可以使用 `upload-artifact` 操作上传该目录的内容。
-
-{% raw %}
-```yaml
-steps:
- - uses: actions/checkout@v2
- - uses: actions/setup-java@v1
- - run: ant -noinput -buildfile build.xml
- - uses: actions/upload-artifact@v2
- with:
- name: Package
- path: build/jar
-```
-{% endraw %}
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-gradle.md
deleted file mode 100644
index 40069ba014bc..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-gradle.md
+++ /dev/null
@@ -1,132 +0,0 @@
----
-title: 使用 Gradle 构建和测试 Java
-intro: 您可以在 GitHub 操作中创建持续集成 (CI) 工作流程,以使用 Gradle 构建和测试 Java 项目。
-product: '{% data reusables.gated-features.actions %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南介绍如何使用 Gradle 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败; 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以缓存文件并且从工作流程运行上传构件。
-
-{% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件,包括 Java Development Kits (JDKs) 和 Gradle。 有关软件以及 JDK 和 Gradle 预安装版本的列表,请参阅 [{% data variables.product.prodname_dotcom %} 自托管运行器上安装的软件](/actions/automating-your-workflow-with-github-actions/software-installed-on-github-hosted-runners)。
-
-### 基本要求
-
-您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅:
-- "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
-- "[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)"
-
-建议您对 Java 和 Gradle 框架有个基本的了解。 更多信息请参阅 Gradle 文档中的[入门指南](https://docs.gradle.org/current/userguide/getting_started.html)。
-
-{% data reusables.actions.enterprise-setup-prereq %}
-
-### 从 Gradle 工作流程模板开始
-
-{% data variables.product.prodname_dotcom %} 提供有 Gradle 工作流程模板,应该适用于大多数基于 Gradle 的 Java 项目。 更多信息请参阅 [Gradle 工作流程模板](https://github.com/actions/starter-workflows/blob/master/ci/gradle.yml)。
-
-要快速开始,您可以在创建新工作流程时选择预配置的 Gradle 模板。 更多信息请参阅“[从预配置的工作流程模板开始](/actions/automating-your-workflow-with-github-actions/starting-with-preconfigured-workflow-templates)”。
-
-您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。
-
-{% raw %}
-```yaml
-name: Java CI
-
-on: [push]
-
-jobs:
- build:
- runs-on: ubuntu-latest
-
- steps:
- - uses: actions/checkout@v2
- - name: Set up JDK 1.8
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Build with Gradle
- run: ./gradlew build
-```
-{% endraw %}
-
-此工作流程执行以下步骤:
-
-1. `checkout` 步骤在运行器上下载仓库的副本。
-2. `setup-java` 步骤配置 Java 1.8 JDK。
-3. “使用 Gradle 构建”步骤运行 `gradlew` wrapper 脚本以确保可以创建您的代码构建、测试通过和包。
-
-在创建构建和测试工作流程时,默认工作流模板是很好的起点,然后您可以自定义模板以满足项目的需求。
-
-{% data reusables.github-actions.example-github-runner %}
-
-{% data reusables.github-actions.java-jvm-architecture %}
-
-### 构建和测试代码
-
-您可以使用与本地相同的命令来构建和测试代码。
-
-初学者工作流程默认将运行 `build` 任务。 在默认的 Gradle 配置中,此命令将下载依赖项、构建类别、运行测试并将类别打包为可分发格式,如 JAR 文件。
-
-如果使用不同的命令来构建项目,或者想要使用不同的任务,则可以指定这些命令。 例如,您可能想要运行在 _ci.gradle_ 文件中配置的 `package` 任务。
-
-{% raw %}
-```yaml
-steps:
- - uses: actions/checkout@v2
- - uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Run the Gradle package task
- run: ./gradlew -b ci.gradle package
-```
-{% endraw %}
-
-### 缓存依赖项
-
-您可以缓存依赖项来加快工作流程运行。 运行成功后,您的本地 Gradle 缓存将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中,缓存将会恢复,因此不需要从远程包仓库下载依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。
-
-{% raw %}
-```yaml
-steps:
- - uses: actions/checkout@v2
- - name: Set up JDK 1.8
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Cache Gradle packages
- uses: actions/cache@v2
- with:
- path: ~/.gradle/caches
- key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }}
- restore-keys: ${{ runner.os }}-gradle
- - name: Build with Gradle
- run: ./gradlew build
-```
-{% endraw %}
-
-此工作流程将保存本地 Gradle 缓存的内容,位于运行器主目录的 `.gradle/caches` 目录中。 缓存密钥将是 gradle 构建文件的哈希内容,因此更改它们将使缓存失效。
-
-### 将工作流数据打包为构件
-
-构建成功且测试通过后,您可能想要上传生成的 Java 包作为构件。 这会将构建的包存储为工作流程运行的一部分,并允许您下载它们。 构件可帮助您在拉取请求合并之前在本地环境中测试并调试它们。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
-
-Gradle 通常会在 `build/libs` 目录中创建 JAR、EAR 或 WAR 等输出文件。 您可以使用 `upload-artifact` 操作上传该目录的内容。
-
-{% raw %}
-```yaml
-steps:
- - uses: actions/checkout@v2
- - uses: actions/setup-java@v1
- - run: ./gradlew build
- - uses: actions/upload-artifact@v2
- with:
- name: Package
- path: build/libs
-```
-{% endraw %}
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-maven.md
deleted file mode 100644
index a97ec3a2477d..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/building-and-testing-java-with-maven.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: 使用 Maven 构建和测试 Java
-intro: 您可以在 GitHub 操作中创建持续集成 (CI) 工作流程,以使用 Maven 构建和测试 Java 项目。
-product: '{% data reusables.gated-features.actions %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南介绍如何使用 Maven 软件项目管理工具为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败; 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以缓存文件并且从工作流程运行上传构件。
-
-{% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件,包括 Java Development Kits (JDKs) 和 Maven。 有关软件以及 JDK 和 Maven 预安装版本的列表,请参阅 [{% data variables.product.prodname_dotcom %} 自托管运行器上安装的软件](/actions/automating-your-workflow-with-github-actions/software-installed-on-github-hosted-runners)。
-
-### 基本要求
-
-您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅:
-- "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
-- "[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)"
-
-建议您对 Java 和 Maven 框架有个基本的了解。 更多信息请参阅 Maven 文档中的 [Maven 入门指南](http://maven.apache.org/guides/getting-started/index.html)。
-
-{% data reusables.actions.enterprise-setup-prereq %}
-
-### 从 Maven 工作流程模板开始
-
-{% data variables.product.prodname_dotcom %} 提供有 Maven 工作流程模板,应该适用于大多数基于 Maven 的 Java 项目。 更多信息请参阅 [Maven 工作流程模板](https://github.com/actions/starter-workflows/blob/master/ci/maven.yml)。
-
-要快速开始,您可以在创建新工作流程时选择预配置的 Maven 模板。 更多信息请参阅“[从预配置的工作流程模板开始](/actions/automating-your-workflow-with-github-actions/starting-with-preconfigured-workflow-templates)”。
-
-您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。
-
-{% raw %}
-```yaml
-name: Java CI
-
-on: [push]
-
-jobs:
- build:
- runs-on: ubuntu-latest
-
- steps:
- - uses: actions/checkout@v2
- - name: Set up JDK 1.8
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Build with Maven
- run: mvn -B package --file pom.xml
-```
-{% endraw %}
-
-此工作流程执行以下步骤:
-
-1. `checkout` 步骤在运行器上下载仓库的副本。
-2. `setup-java` 步骤配置 Java 1.8 JDK。
-3. “使用 Maven 构建”步骤以非交互模式运行 Maven `package` 目标,以确保创建代码版本、测试通行证和软件包。
-
-在创建构建和测试工作流程时,默认工作流模板是很好的起点,然后您可以自定义模板以满足项目的需求。
-
-{% data reusables.github-actions.example-github-runner %}
-
-{% data reusables.github-actions.java-jvm-architecture %}
-
-### 构建和测试代码
-
-您可以使用与本地相同的命令来构建和测试代码。
-
-初学者工作流程默认将运行 `package` 目标。 在默认的 Maven 配置中,此命令将下载依赖项、构建类别、运行测试并将类别打包为可分发格式,如 JAR 文件。
-
-如果使用不同的命令来构建项目,或者想要使用不同的目标,则可以指定这些命令。 例如,您可能想要运行在 _pom-ci.xml_ 文件中配置的 `verify` 目标。
-
-{% raw %}
-```yaml
-steps:
- - uses: actions/checkout@v2
- - uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Run the Maven verify phase
- run: mvn -B verify --file pom-ci.xml
-```
-{% endraw %}
-
-### 缓存依赖项
-
-您可以缓存依赖项来加快工作流程运行。 运行成功后,您的本地 Maven 仓库将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中,缓存将会恢复,因此不需要从远程 Maven 仓库下载依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。
-
-{% raw %}
-```yaml
-steps:
- - uses: actions/checkout@v2
- - name: Set up JDK 1.8
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Cache Maven packages
- uses: actions/cache@v2
- with:
- path: ~/.m2
- key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }}
- restore-keys: ${{ runner.os }}-m2
- - name: Build with Maven
- run: mvn -B package --file pom.xml
-```
-{% endraw %}
-
-此工作流程将保存本地 Maven 存储库的内容,位于运行器主目录的 `.m2` 目录。 缓存密钥是 _pom.xml_ 的哈希内容,因此更改 _pom.xml_ 将使缓存失效。
-
-### 将工作流数据打包为构件
-
-构建成功且测试通过后,您可能想要上传生成的 Java 包作为构件。 这会将构建的包存储为工作流程运行的一部分,并允许您下载它们。 构件可帮助您在拉取请求合并之前在本地环境中测试并调试它们。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
-
-Maven 通常会在 `target` 目录中创建 JAR、EAR 或 WAR 等输出文件。 要将这些项目上传为构件,可以将它们复制到包含要上传的构件的新目录中。 例如,您可以创建一个名为 `staging` 的目录。 然后您可以使用 `upload-artifact` 操作上传该目录的内容。
-
-{% raw %}
-```yaml
-steps:
- - uses: actions/checkout@v2
- - uses: actions/setup-java@v1
- - run: mvn -B package --file pom.xml
- - run: mkdir staging && cp target/*.jar staging
- - uses: actions/upload-artifact@v2
- with:
- name: Package
- path: staging
-```
-{% endraw %}
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-docker.md b/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-docker.md
deleted file mode 100644
index 4005123d29f8..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-docker.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 用于 Docker 的 GitHub 操作
-intro: 创建用于构建和发布 Docker 项目的工作流程。
-mapTopic: true
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-java.md b/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-java.md
deleted file mode 100644
index 924386562828..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-java.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 用于 Java 的 GitHub 操作
-intro: 创建工作流程以构建和测试以 Java 编写的项目。
-mapTopic: true
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-javascript-and-typescript.md b/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-javascript-and-typescript.md
deleted file mode 100644
index 6ca98a402598..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-javascript-and-typescript.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 用于 JavaScript 和 TypeScript 的 GitHub 操作
-intro: 创建工作流程以构建和测试在 JavaScript 和 TypeScript 库中写入的项目。
-mapTopic: true
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-python.md b/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-python.md
deleted file mode 100644
index c6c6ea16f31e..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/github-actions-for-python.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 用于 Python 的 GitHub 操作
-intro: 创建工作流程以构建和测试以 Python 编写的项目。
-mapTopic: true
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/index.md b/translations/zh-CN/content/actions/language-and-framework-guides/index.md
deleted file mode 100644
index 2ffd23f9ab01..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/index.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 语言和框架指南
-intro: 您可以创建持续集成 (CI) 工作流程,以构建和测试以不同编程语言编写的项目。
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% topic_link_in_list /github-actions-for-javascript-and-typescript %}
- {% link_in_list /using-nodejs-with-github-actions %}
- {% link_in_list /publishing-nodejs-packages %}
-{% topic_link_in_list /github-actions-for-python %}
- {% link_in_list /using-python-with-github-actions %}
-{% topic_link_in_list /github-actions-for-java %}
- {% link_in_list /building-and-testing-java-with-maven %}
- {% link_in_list /building-and-testing-java-with-gradle %}
- {% link_in_list /building-and-testing-java-with-ant %}
- {% link_in_list /publishing-java-packages-with-maven %}
- {% link_in_list /publishing-java-packages-with-gradle %}
-{% topic_link_in_list /github-actions-for-docker %}
- {% link_in_list /publishing-docker-images %}
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/publishing-docker-images.md b/translations/zh-CN/content/actions/language-and-framework-guides/publishing-docker-images.md
deleted file mode 100644
index e313ba374635..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/publishing-docker-images.md
+++ /dev/null
@@ -1,157 +0,0 @@
----
-title: 发布 Docker 映像
-intro: '您可以将 Docker 映像发布到注册表,例如 Docker Hub 或 {% data variables.product.prodname_registry %},作为持续集成 (CI) 工作流程的一部分。'
-product: '{% data reusables.gated-features.actions %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南介绍如何创建执行 Docker 构建的工作流程,然后将 Docker 映像发布到 Docker Hub 或 {% data variables.product.prodname_registry %}。 通过单个工作流程,您可以将映像发布到单一注册表或多个注册表。
-
-{% note %}
-
-**注意:**如果要推送到另一个第三方 Docker 注册表,则“[发布映像到 {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)”部分可作为一个很好的模板。
-
-{% endnote %}
-
-### 基本要求
-
-建议基本了解工作流程配置选项和如何创建工作流程文件。 更多信息请参阅“[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)。
-
-您可能还发现基本了解以下内容是有帮助的:
-
-- "[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)"
-- "[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)"
-- "[配置 Docker 用于 {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)"
-
-### 关于映像配置
-
-本指南假定您对存储在 {% data variables.product.prodname_dotcom %} 仓库的 Docker 映像有完整的定义。 例如,仓库必须包含 _Dockerfile_ 以及执行 Docker 构建所需的任何其他文件才可创建映像。
-
-在本指南中,我们将使用 Docker `build-push-action` 操作来构建 Docker 映像并将其推送到一个或多个 Docker 注册表。 更多信息请参阅 [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images)。
-
-{% data reusables.actions.enterprise-marketplace-actions %}
-
-### 将映像发布到 Docker Hub
-
-{% data reusables.github-actions.release-trigger-workflow %}
-
-在下面的示例工作流程中,我们使用 Docker `build-push-action` 操作构建 Docker 映像,如果构建成功,则将构建映像推送到 Docker Hub。
-
-要推送到 Docker Hub,您需要有一个 Docker Hub 帐户,并创建一个 Docker Hub 仓库。 更多信息请参阅 Docker 文档中的“[在 Docker Hub 上共享映像](https://docs.docker.com/get-started/part3/)”。
-
-Docker Hub 需要的 `build-push-action` 选项包括:
-
-* `username` 和 `password`:这是您的 Docker Hub 用户名和密码。 建议将 Docker Hub 用户名和密码在 {% data variables.product.prodname_dotcom %} 仓库中存储为加密密码,以免它们暴露在工作流程文件中。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-* `repository`:`DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY` 格式的 Docker Hub 仓库。
-
-{% raw %}
-```yaml
-name: Publish Docker image
-on:
- release:
- types: [published]
-jobs:
- push_to_registry:
- name: Push Docker image to Docker Hub
- runs-on: ubuntu-latest
- steps:
- - name: Check out the repo
- uses: actions/checkout@v2
- - name: Push to Docker Hub
- uses: docker/build-push-action@v1
- with:
- username: ${{ secrets.DOCKER_USERNAME }}
- password: ${{ secrets.DOCKER_PASSWORD }}
- repository: my-docker-hub-namespace/my-docker-hub-repository
- tag_with_ref: true
-```
-{% endraw %}
-
-{% data reusables.github-actions.docker-tag-with-ref %}
-
-### 发布映像到 {% data variables.product.prodname_registry %}
-
-{% data reusables.github-actions.release-trigger-workflow %}
-
-在下面的示例工作流程中,我们使用 Docker `build-push-action` 操作构建 Docker 映像,如果构建成功,则将构建映像推送到 {% data variables.product.prodname_registry %}。
-
-{% data variables.product.prodname_registry %} 需要的 `build-push-action` 选项包括:
-
-* `username`:您可以使用 {% raw %}`${{ github.actor }}`{% endraw %} 上下文自动使用触发工作流程运行的用户的用户名。 更多信息请参阅“[GitHub 操作的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)”。
-* `password`:您可以使用自动生成的 `GITHUB_TOKEN` 密码作为密码。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)”。
-* `registry`:必须设置为 `docker.pkg.github.com`。
-* `repository`:必须以 `OWNER/REPOSITORY/IMAGE_NAME` 格式设置。 例如,对于 `http://github.com/octo-org/octo-repo` 上名为 `octo-image` stored on {% data variables.product.prodname_dotcom %} 的映像,`repository` 选项应设置为 `octo-org/octo-repo/octo-image`。
-
-{% raw %}
-```yaml
-name: Publish Docker image
-on:
- release:
- types: [published]
-jobs:
- push_to_registry:
- name: Push Docker image to GitHub Packages
- runs-on: ubuntu-latest
- steps:
- - name: Check out the repo
- uses: actions/checkout@v2
- - name: Push to GitHub Packages
- uses: docker/build-push-action@v1
- with:
- username: ${{ github.actor }}
- password: ${{ secrets.GITHUB_TOKEN }}
- registry: docker.pkg.github.com
- repository: my-org/my-repo/my-image
- tag_with_ref: true
-
-```
-{% endraw %}
-
-{% data reusables.github-actions.docker-tag-with-ref %}
-
-### 发布映像到 Docker Hub 和 {% data variables.product.prodname_registry %}
-
-在单一工作流程中,您可以对每个注册表使用 `build-push-action` 操作,以将 Docker 映像发布到多个注册表。
-
-下面的示例工作流程使用前面章节中的 `build-push-action` 步骤(“[发布映像到 Docker Hub](#publishing-images-to-docker-hub)”和“[发布映像到 {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)”)来创建同时推送到两个注册表的单一工作流程。
-
-{% raw %}
-```yaml
-name: Publish Docker image
-on:
- release:
- types: [published]
-jobs:
- push_to_registries:
- name: Push Docker image to multiple registries
- runs-on: ubuntu-latest
- steps:
- - name: Check out the repo
- uses: actions/checkout@v2
- - name: Push to Docker Hub
- uses: docker/build-push-action@v1
- with:
- username: ${{ secrets.DOCKER_USERNAME }}
- password: ${{ secrets.DOCKER_PASSWORD }}
- repository: my-docker-hub-namespace/my-docker-hub-repository
- tag_with_ref: true
- - name: Push to GitHub Packages
- uses: docker/build-push-action@v1
- with:
- username: ${{ github.actor }}
- password: ${{ secrets.GITHUB_TOKEN }}
- registry: docker.pkg.github.com
- repository: my-org/my-repo/my-image
- tag_with_ref: true
-```
-{% endraw %}
-
-上面的工作流程检出 {% data variables.product.prodname_dotcom %} 仓库,并且使用两次 `build-push-action` 操作构建并推送 Docker 映像到 Docker Hub 和 {% data variables.product.prodname_registry %}。 对于这两个步骤, 它设置 `build-pow-action` 选项 [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) 自动使用工作流程事件的 Git 引用标记构建的 Docker 映像。 此工作流程在发布 {% data variables.product.prodname_dotcom %} 版本时触发,因此对两个注册表的引用将是该版本的 Git 标记。
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/language-and-framework-guides/publishing-java-packages-with-gradle.md
deleted file mode 100644
index c64d12ebd715..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/publishing-java-packages-with-gradle.md
+++ /dev/null
@@ -1,218 +0,0 @@
----
-title: 使用 Gradle 发布 Java 包
-intro: 您可以使用 Gradle 将 Java 包发布到注册表,作为持续集成 (CI) 工作流程的一部分。
-product: '{% data reusables.gated-features.actions %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-{% data reusables.github-actions.publishing-java-packages-intro %}
-
-### 基本要求
-
-建议对工作流程文件和配置选项有一个基本了解。 更多信息请参阅“[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)。
-
-有关使用 Gradle 为 Java 项目创建 CI 工作流程的详细信息,请参阅“[使用 Gradle 构建和测试用 Java](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)”。
-
-您可能还发现基本了解以下内容是有帮助的:
-
-- "[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[配置 npm 用于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
-- "[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-- "[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)"
-- "[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)"
-
-### 关于包配置
-
-_build.gradle_ 文件 `MavenPublication` 部分的 `groupId` 和 `artifactId` 字段为包创建唯一标识符,供注册表用来将包链接到注册表。 这类似于 Maven _pom.xml_ 文件的 `groupId` 和 `artifactId` 字段。 更多信息请参阅 Gradle 文档中的“[Maven 发布插件](https://docs.gradle.org/current/userguide/publishing_maven.html)”。
-
-_build.gradle_ 文件还包含 Gradle 将在其中部署包的分发管理仓库的配置。 每个仓库必须有名称、部署 URL 和验证凭据。
-
-### 将包发布到 Maven 中心仓库
-
-每次创建新版本时,都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过,工作流程将包发布到 Maven 中心仓库。 有关 `release` 事件的更多信息,请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#release)”。
-
-您可以在 _build.gradle_ 文件的发布块中定义指向包仓库的新 Maven 仓库。 例如,如果您通过 OSSRH 托管项目部署到 Maven 中心仓库,则 _build.gradle_ 可以指定名称为 `"OSSRH"` 的仓库。
-
-{% raw %}
-```groovy
-publishing {
- ...
-
- repositories {
- maven {
- name = "OSSRH"
- url = "https://oss.sonatype.org/service/local/staging/deploy/maven2/"
- credentials {
- username = System.getenv("MAVEN_USERNAME")
- password = System.getenv("MAVEN_PASSWORD")
- }
- }
- }
-}
-```
-{% endraw %}
-
-使用此配置可创建一个工作流程,以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库。 您还需要提供包含用户名和密码的环境变量向仓库验证。
-
-在部署步骤中,您需要为用于向 Maven 仓库验证身份的用户名和密码或令牌设置环境变量。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-
-{% raw %}
-```yaml
-name: Publish package to the Maven Central Repository
-on:
- release:
- types: [created]
-jobs:
- publish:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- - name: Set up Java
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Publish package
- run: gradle publish
- env:
- MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
- MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-```
-{% endraw %}
-
-{% data reusables.github-actions.gradle-workflow-steps %}
-1. 运行 `gradle published` 命令以发布到 `OSSRH` Maven 仓库。 `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置,而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。
-
- 有关在工作流程中使用密码的更多信息,请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-### 发布包到 {% data variables.product.prodname_registry %}
-
-每次创建新版本时,都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过,工作流程会将包发布到 {% data variables.product.prodname_registry %}。 有关 `release` 事件的更多信息,请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#release)”。
-
-您可以在 _build.gradle_ 文件的发布块中定义指向 {% data variables.product.prodname_registry %} 的新 Maven 仓库。 在仓库配置中,您也可以利用在 CI 工作流程运行中设置的环境变量。 您可以使用 `GITHUB_ACTOR` 环境变量作为用户名,并且可以使用 `GITHUB_TOKENN` 密码设置 `GITHUB_TOKEN` 环境变量。
-
-`GITHUB_TOKEN` 默认存在于您的仓库中,并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
-
-例如,如果组织名为“octocat”且仓库名为“hello-world”,则 _build.gradle_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。
-
-{% raw %}
-```groovy
-publishing {
- ...
-
- repositories {
- maven {
- name = "GitHubPackages"
- url = "https://maven.pkg.github.com/octocat/hello-world"
- credentials {
- username = System.getenv("GITHUB_ACTOR")
- password = System.getenv("GITHUB_TOKEN")
- }
- }
- }
-}
-```
-{% endraw %}
-
-使用此配置可创建一个工作流程,以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库。
-
-{% raw %}
-```yaml
-name: Publish package to GitHub Packages
-on:
- release:
- types: [created]
-jobs:
- publish:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- - uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Publish package
- run: gradle publish
- env:
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
-
-{% data reusables.github-actions.gradle-workflow-steps %}
-1. 运行 `gradle published` 命令以发布到 {% data variables.product.prodname_registry %}。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。
-
- 有关在工作流程中使用密码的更多信息,请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-### 发布包到 Maven 中心仓库和 {% data variables.product.prodname_registry %}
-
-您可以通过在 _build.gradle_ 文件中配置每项设置,将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。
-
-确保 _build.gradle_ 文件包含用于 {% data variables.product.prodname_dotcom %} 仓库和 Maven 中心仓库提供商的仓库。
-
-例如,如果您通过 OSSRH 托管项目部署到 Maven 中心仓库,您可能想要在分发管理仓库中指定它,并将 `name` 设置为 `OSSRH`。 如果您部署到 {% data variables.product.prodname_registry %},您可能想要在分发管理仓库中指定它,并将 `name` 设置为 `GitHubPackages`。
-
-如果组织名为“octocat”且仓库名为“hello-world”,则 _build.gradle_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。
-
-{% raw %}
-```groovy
-publishing {
- ...
-
- repositories {
- maven {
- name = "OSSRH"
- url = "https://oss.sonatype.org/service/local/staging/deploy/maven2/"
- credentials {
- username = System.getenv("MAVEN_USERNAME")
- password = System.getenv("MAVEN_PASSWORD")
- }
- }
- maven {
- name = "GitHubPackages"
- url = "https://maven.pkg.github.com/octocat/hello-world"
- credentials {
- username = System.getenv("GITHUB_ACTOR")
- password = System.getenv("GITHUB_TOKEN")
- }
- }
- }
-}
-```
-{% endraw %}
-
-使用此配置可创建一个工作流程,以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。
-
-{% raw %}
-```yaml
-name: Publish package to the Maven Central Repository and GitHub Packages
-on:
- release:
- types: [created]
-jobs:
- publish:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- - name: Set up Java
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Publish to the Maven Central Repository
- run: gradle publish
- env:
- MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
- MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
-
-{% data reusables.github-actions.gradle-workflow-steps %}
-1. 运行 `gradle published` 命令以发布到 `OSSRH` Maven 仓库和 {% data variables.product.prodname_registry %}。 `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置,而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。
-
- 有关在工作流程中使用密码的更多信息,请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/publishing-java-packages-with-maven.md b/translations/zh-CN/content/actions/language-and-framework-guides/publishing-java-packages-with-maven.md
deleted file mode 100644
index 637a0a5609c4..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/publishing-java-packages-with-maven.md
+++ /dev/null
@@ -1,209 +0,0 @@
----
-title: 使用 Maven 发布 Java 包
-intro: 您可以使用 Maven 将 Java 包发布到注册表,作为持续集成 (CI) 工作流程的一部分。
-product: '{% data reusables.gated-features.actions %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-{% data reusables.github-actions.publishing-java-packages-intro %}
-
-### 基本要求
-
-建议对工作流程文件和配置选项有一个基本了解。 更多信息请参阅“[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)。
-
-有关为使用 Maven 为 Java 项目创建 CI 工作流程的详细信息,请参阅“[使用 Maven 构建和测试用 Java](/actions/language-and-framework-guides/building-and-testing-java-with-maven)”。
-
-您可能还发现基本了解以下内容是有帮助的:
-
-- "[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[配置 npm 用于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
-- "[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-- "[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)"
-- "[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)"
-
-### 关于包配置
-
-_pom.xml_ 文件中的 `groupId` 和 `artifactId` 字段为包创建唯一标识符,供注册表用来将包链接到注册表。 更多信息请参阅 Apache Maven 文档中的[将构件上传到中心仓库的指南](http://maven.apache.org/repository/guide-central-repository-upload.html)。
-
-_pom.xml_ 文件还包含 Maven 将在其中部署包的分配管理仓库的配置。 每个仓库都必须有名称和部署 URL。 这些仓库的身份验证可在运行 Maven 的用户主目录下的 _.m2/settings.xml_ 文件中配置。
-
-您可以使用 `setup-java` 操作配置部署仓库以及该仓库的身份验证。 更多信息请参阅 [`setup-java`](https://github.com/actions/setup-java)。
-
-### 将包发布到 Maven 中心仓库
-
-每次创建新版本时,都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过,工作流程将包发布到 Maven 中心仓库。 有关 `release` 事件的更多信息,请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#release)”。
-
-在此工作流程中,您可以使用 `setup-java` 操作。 此操作将 JDK 的给定版本安装到 `PATH`,但同时会配置 Maven _settings.xml_ 以发布包。 默认情况下,设置文件将配置用于 {% data variables.product.prodname_registry %},但可以将其配置为部署到另一个包注册表,如 Maven 中心仓库。 如果您已经在 _pom.xml_ 配置分配管理仓库,则可在 `setup-java` 操作调用期间指定该 `id`。
-
-例如,如果您通过 OSSRH 托管项目部署到 Maven 中心仓库,则 _pom.xml_ 可以指定 `id` 为 `ossrh` 的分发管理仓库。
-
-{% raw %}
-```xml
-
- ...
-
-
- ossrh
- Central Repository OSSRH
- https://oss.sonatype.org/service/local/staging/deploy/maven2/
-
-
-
-```
-{% endraw %}
-
-使用此配置,可通过将仓库管理 `id` 指定到 `setup-java` 操作,创建一个将包发布到 Maven 中心仓库的工作流程。 您还需要提供包含用户名和密码的环境变量向仓库验证。
-
-在部署步骤中,您需要将环境变量设置为向仓库验证的用户名,以及用密码或令牌配置为进行身份验证的密钥。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-
-{% raw %}
-```yaml
-name: Publish package to the Maven Central Repository
-on:
- release:
- types: [created]
-jobs:
- publish:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- - name: Set up Maven Central Repository
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- server-id: ossrh
- server-username: MAVEN_USERNAME
- server-password: MAVEN_PASSWORD
- - name: Publish package
- run: mvn -B deploy
- env:
- MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
- MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-```
-{% endraw %}
-
-此工作流程执行以下步骤:
-
-1. 检出项目仓库的副本。
-1. 设置 Java JDK,同时使用 `MAVEN_USERNAME` 和 `MAVEN_PASSWORD` 环境变量配置 Maven _settings.xml_ 文件为 `ossrh` 仓库添加身份验证。
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
-
- 有关在工作流程中使用密码的更多信息,请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-### 发布包到 {% data variables.product.prodname_registry %}
-
-每次创建新版本时,都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过,工作流程会将包发布到 {% data variables.product.prodname_registry %}。 有关 `release` 事件的更多信息,请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#release)”。
-
-在此工作流程中,您可以使用 `setup-java` 操作。 此操作将给定版本的 JDK 安装到 `PATH`,并且设置 Maven _settings.xml_ 以将包发布到 {% data variables.product.prodname_registry %}。 生成的 _settings.xml_ 定义使用 `github` 的 `id` 向服务器验证,使用 `GITHUB_ACTOR` 环境变量作为用户名,`GITHUB_TOKEN` 环境变量作为密码。
-
-`GITHUB_TOKEN` 默认存在于您的仓库中,并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
-
-对于基于 Maven的项目,您可以通过在 _pom.xml_ 文件中创建分发仓库来使用这些设置,该文件以 `github` 的 `id` 指向 {% data variables.product.prodname_registry %} 端点。
-
-例如,如果组织名为“octocat”且仓库名为“hello-world”,则 _pom.xml_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。
-
-{% raw %}
-```xml
-
- ...
-
-
- github
- GitHub Packages
- https://maven.pkg.github.com/octocat/hello-world
-
-
-
-```
-{% endraw %}
-
-通过此配置,您可以创建一个工作流程,以使用自动生成的 _settings.xml_ 将包发布到 {% data variables.product.prodname_registry %}。
-
-{% raw %}
-```yaml
-name: Publish package to GitHub Packages
-on:
- release:
- types: [created]
-jobs:
- publish:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- - uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Publish package
- run: mvn -B deploy
- env:
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
-
-此工作流程执行以下步骤:
-
-1. 检出项目仓库的副本。
-1. 设置 Java JDK,同时自动配置 Maven _settings.xml_ 文件为 `github` Maven 仓库添加身份验证,以使用 `GITHUB_TOKEN` 环境变量。
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
-
- 有关在工作流程中使用密码的更多信息,请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-### 发布包到 Maven 中心仓库和 {% data variables.product.prodname_registry %}
-
-您可以使用每个注册表的 `setup-node` 操作将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。
-
-确保 _pom.xml_ 文件包含用于 {% data variables.product.prodname_dotcom %} 仓库和 Maven 中心仓库提供商的分发管理仓库。 例如,如果您通过 OSSRH 托管项目部署到中心仓库,您可能想通过将 `id` 设置为 `ossrh` 在分发管理仓库中指定它,并且想通过将 `id` 设置为 `github` 在分发管理仓库中指定 {% data variables.product.prodname_registry %}。
-
-{% raw %}
-```yaml
-name: Publish package to the Maven Central Repository and GitHub Packages
-on:
- release:
- types: [created]
-jobs:
- publish:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- - name: Set up Java for publishing to Maven Central Repository
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- server-id: ossrh
- server-username: MAVEN_USERNAME
- server-password: MAVEN_PASSWORD
- - name: Publish to the Maven Central Repository
- run: mvn -B deploy
- env:
- MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
- MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
- - name: Set up Java for publishing to GitHub Packages
- uses: actions/setup-java@v1
- with:
- java-version: 1.8
- - name: Publish to GitHub Packages
- run: mvn -B deploy
- env:
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
-
-此工作流程将调用 `setup-java` 操作两次。 每次运行 `setup-java` 操作时,都会覆盖 Maven _settings.xml_ 文件以发布包。 为向仓库验证,_settings.xml_ 文件引用分发管理仓库 `id` 以及用户名和密码。
-
-此工作流程执行以下步骤:
-
-1. 检出项目仓库的副本。
-1. 第一次调用 `setup-java`。 这将为 `ossrh` 仓库配置 Maven _settings.xml_ 文件,并将身份验证选项设置为下一步定义的环境变量。
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
-1. 第二次调用 `setup-java`。 这将自动为 {% data variables.product.prodname_registry %} 配置 Maven _settings.xml_ 文件。
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
-
- 有关在工作流程中使用密码的更多信息,请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/language-and-framework-guides/publishing-nodejs-packages.md
deleted file mode 100644
index 2589b65bc449..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/publishing-nodejs-packages.md
+++ /dev/null
@@ -1,210 +0,0 @@
----
-title: 发布 Node.js 包
-intro: 您可以将 Node.js 包发布到注册表,作为持续集成 (CI) 工作流程的一部分。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南介绍如何创建一个工作流程,以在持续集成 (CI) 测试通过后将 Node.js 包发布到 {% data variables.product.prodname_registry %} 和 npm 注册表。 通过单个工作流程,您可以将包发布到单个注册表或多个注册表。
-
-### 基本要求
-
-建议基本了解工作流程配置选项和如何创建工作流程文件。 更多信息请参阅“[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)。
-
-有关为 Node.js 项目创建 CI 工作流程的更多信息,请参阅“[将 Node.js 与 {% data variables.product.prodname_actions %} 一起使用](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)。”
-
-您可能还发现基本了解以下内容是有帮助的:
-
-- "[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[配置 npm 用于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
-- "[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-- "[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)"
-- "[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)"
-
-### 关于包配置
-
- *package.json* 文件中的 `name` 和 `version` 字段创建唯一标识符,供注册表用来将包链接到注册表。 您可以在 *package.json* 文件中添加 `description` 字段,从而为包列表页面添加一个摘要。 更多信息请参阅 npm 文档中的“[创建 package.json 文件](https://docs.npmjs.com/creating-a-package-json-file)”和“[创建 Node.js 模块](https://docs.npmjs.com/creating-node-js-modules)”。
-
-当本地 *.npmrc* 文件存在且指定了 `registry` 值时,`npm publish` 命令将使用 *.npmrc* 文件中配置的注册表。 {% data reusables.github-actions.setup-node-intro %}
-
-您可以使用 `setup-node` 操作指定运行器上安装的 Node.js 版本。
-
-如果在工作流程中添加步骤来配置 *package.json* 文件中的 `publishConfig` 字段,则无需使用 `setup-node` 操作指定注册表 url,但软件包仅限于发布到一个注册表。 更多信息请参阅 npm 文档中的“[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)”。
-
-### 发布包到 npm 注册表
-
-每次创建新版本时,都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过,工作流程将包发布到 npm 注册表。
-
-要根据工作流程中的 npm 注册表执行经过身份验证的操作,您需要在仓库设置中将 npm 身份验证令牌作存储为密码。 例如,创建名为 `NPM_TOKEN` 的密码。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-默认情况下,npm 使用 *package.json* 文件的 `name` 字段来确定 npm 注册表。 当发布到全局命名空间时,您只需要包含包名称。 例如,您要发布一个名为 `npm-hello-world-test` 的包到 `https://www.npmjs.com/package/npm-hello-world-test`。
-
-如果发布一个包含范围前缀的包,请将范围包含在 *package.json* 文件的名称中。 例如,如果 npm 范围前缀是 octocat 并且包名是 hello-world,则 *package.json* 文件中的 `name` 应为 `@octocat/hello-world`。 如果 npm 包使用范围前缀且包是公开的,则需使用选项 `npm publish --access public`。 这是 npm 需要用来防止有人无意中发布私有包的选项。
-
-此示例将 `NPM_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时,会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # Setup .npmrc file to publish to npm
- - uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- registry-url: 'https://registry.npmjs.org'
- - run: npm install
- - run: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-```
-{% endraw %}
-
-在上面的示例中,`setup-node` 操作在运行器上创建一个包含以下内容的 *.npmrc* 文件:
-
-```
-//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
-registry=https://registry.npmjs.org/
-always-auth=true
-```
-
-### 发布包到 {% data variables.product.prodname_registry %}
-
-每次创建新版本时,都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件发生时运行。 如果 CI 测试通过,工作流程会将包发布到 {% data variables.product.prodname_registry %}。
-
-默认情况下,{% data variables.product.prodname_registry %} 将包发布到您在 *package.json* 文件的 `name` 字段中指定的 {% data variables.product.prodname_dotcom %} 仓库。 例如,您要发布一个名为 `@my-org/test` 的包到 `my-org/test` {% data variables.product.prodname_dotcom %} 仓库。 更多信息请参阅 npm 文档中的 [`npm-scope`](https://docs.npmjs.com/misc/scope)。
-
-要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作,可以使用 `GITHUB_TOKEN`。 `GITHUB_TOKEN` 默认存在于您的仓库中,并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-此示例将 `GITHUB_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时,会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # 设置 .npmrc 文件以发布到 GitHub 包
- - uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- registry-url: 'https://npm.pkg.github.com'
- # 默认为拥有工作流程文件的用户或组织
- scope: '@octocat'
- - run: npm install
- - run: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
-
-`setup-node` 操作在运行器上创建 *.npmrc* 文件。 使用 `scope` 输入到 `setup-node` 操作时,*.npmrc* 文件包含作用域前缀。 默认情况下,`setup-node` 操作在 *.npmrc* 文件中将作用域设置为包含该工作流程文件的帐户。
-
-```
-//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
-@octocat:registry=https://npm.pkg.github.com
-always-auth=true
-```
-
-### 使用 yarn 发布包
-
-如果您使用 Yarn 包管理器,可以使用 Yarn 安装和发布包。
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # 设置 .npmrc 文件以发布到 npm
- - uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- registry-url: 'https://registry.npmjs.org'
- # 默认为拥有工作流程文件的用户或组织
- scope: '@octocat'
- - run: yarn
- - run: yarn publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-```
-{% endraw %}
-
-### 发布包到 npm 和 {% data variables.product.prodname_registry %}
-
-{% note %}
-
-**注意:**如果需要发布到具有不同作用域前缀的注册表,则需修改运行器上的 *package.json* 文件以更改作用域前缀。 例如,如果将包发布到 npm 的 `@mona` 作用域和 {% data variables.product.prodname_registry %} 的 `@octocat` 作用域,则可在发布到 npm 之后和发布到 {% data variables.product.prodname_registry %} 之前,在运行器的 *package.json* 文件中将 `@mona` 作用域替换成 `@octocat`。
-
-{% endnote %}
-
-您可以使用每个注册表的 `setup-node` 操作将包发布到 npm 注册表和 {% data variables.product.prodname_registry %}。
-
-如果将包发布到两个注册表,则需要确保 npm 上的作用域前缀与 {% data variables.product.prodname_dotcom %} 用户或组织名称匹配。 要将包发布到具有作用域前缀的公共注册表,可以使用 `npm publish --access public`。 更多信息请参阅 [`npm-scope`](https://docs.npmjs.com/misc/scope) 和 npm 文档中的“[创建和发布作用域的公共包](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)”。
-
-确认 *package.json* 文件包含 {% data variables.product.prodname_dotcom %} 仓库和 npm 注册表的作用域。 例如,如果您计划将 `octocat/npm-hello-world-test` 仓库中的包发布到 {% data variables.product.prodname_dotcom %} 和 https://www.npmjs.com/package/@octocat/npm-hello-world-test,则 *package.json* 文件中的名称将是 `"name": "@octocat/npm-hello-world-test"`。
-
-要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作,可以使用 `GITHUB_TOKEN`。 `GITHUB_TOKEN` 默认存在于您的仓库中,并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-使用 `scope` 输入到 `setup-node` 操作时,操作将创建包含作用域前缀的 *.npmrc* 文件。 默认情况下,`setup-node` 操作在 *.npmrc* 文件中将作用域设置为拥有该工作流程文件的用户或组织。
-
-此工作流程将调用 `setup-node` 操作两次。 每当 `setup-node` 操作运行时,都会覆盖 *.npmrc* 文件。 *.npmrc* 文件引用的令牌允许您对 `NODE_AUTH_TOKEN` 环境变量中的包注册表执行验证的操作。 工作流程在 `npm publish` 命令每次运行时设置 `NODE_AUTH_TOKEN` 环境变量,先通过令牌发布到 npm (`NPM_TOKEN`),然后通过令牌发布到 {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`)。
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # 设置 .npmrc 文件以发布到 npm
- - uses: actions/setup-node@v1
- with:
- node-version: '10.x'
- registry-url: 'https://registry.npmjs.org'
- - run: npm install
- # 发布到 npm
- - run: npm publish --access public
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
- # 设置 .npmrc 文件以发布到 GitHub 包
- - uses: actions/setup-node@v1
- with:
- registry-url: 'https://npm.pkg.github.com'
- # 默认为拥有工作流程文件的用户或组织
- scope: '@octocat'
- # 发布到 GitHub 包
- - run: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/using-nodejs-with-github-actions.md b/translations/zh-CN/content/actions/language-and-framework-guides/using-nodejs-with-github-actions.md
deleted file mode 100644
index 3e161c934173..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/using-nodejs-with-github-actions.md
+++ /dev/null
@@ -1,277 +0,0 @@
----
-title: 将 Node.js 与 GitHub 操作一起使用
-intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 Node.js 项目。
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南介绍如何创建用来生成和测试 Node.js 代码的持续集成 (CI) 工作流程。 如果 CI 测试通过,您可能想要部署代码或发布包。
-
-### 基本要求
-
-建议基本了解 Node.js、YAML、工作流程配置选项以及如何创建工作流程文件。 更多信息请参阅“[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)”和“[Node.js 使用入门](https://nodejs.org/en/docs/guides/getting-started-guide/)”。
-
-您可能还发现基本了解以下内容是有帮助的:
-
-- "[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-
-{% data reusables.actions.enterprise-setup-prereq %}
-
-### 从 Node.js 工作流程模板开始
-
-{% data variables.product.prodname_dotcom %} 提供 Node.js 适用于大多数 Node.js 项目的工作流程模板。 本指南包含可用于自定义模板的 npm 和 Yarn 示例。 更多信息请参阅 [Node.js 工作流程模板](https://github.com/actions/starter-workflows/blob/master/ci/node.js.yml)。
-
-要快速开始,请将模板添加到仓库的 `.github/workflows` 目录中。
-
-{% raw %}
-```yaml
-name: Node.js CI
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ubuntu-latest
-
- strategy:
- matrix:
- node-version: [8.x, 10.x, 12.x]
-
- steps:
- - uses: actions/checkout@v2
- - name: Use Node.js ${{ matrix.node-version }}
- uses: actions/setup-node@v1
- with:
- node-version: ${{ matrix.node-version }}
- - run: npm install
- - run: npm run build --if-present
- - run: npm test
- env:
- CI: true
-```
-{% endraw %}
-
-{% data reusables.github-actions.example-github-runner %}
-
-### 指定 Node.js 版本
-
-指定 Node.js 版本的最简单方法是使用由 {% data variables.product.prodname_dotcom %} 提供的 `setup-node` 操作。 更多信息请参阅 [`setup-node`](https://github.com/actions/setup-node/)。
-
-`setup-node` 操作采用 Node.js 版本作为输入,并在运行器上配置该版本。 `setup-node` 操作从每个运行器上的工具缓存中查找特定版本的 Node.js,并将必要的二进制文件添加到 `PATH`,这可继续用于作业的其余部分。 使用 `setup-node` 操作是 Node.js 与 {% data variables.product.prodname_actions %} 结合使用时的推荐方式,因为它能确保不同运行器和不同版本的 Node.js 行为一致。 如果使用自托管运行器,则必须安装 Node.js 并将其添加到 `PATH`。
-
-模板包含一个矩阵策略:用三个 Node.js 版本 8.x、10.x 和 12.x 构建和测试代码,其中“x”是通配符,匹配可用于版本的最新次要版和补丁版。 The 'x' is a wildcard character that matches the latest minor and patch release available for a version. `node-version` 阵列中指定的每个 Node.js 版本都会创建一个运行相同步骤的作业。
-
-每个作业都可以使用 `matrix` 上下文访问矩阵 `node-version` 阵列中定义的值。 `setup-node` 操作使用上下文作为 `node-version` 输入。 `setup-node` 操作在构建和测试代码之前使用不同的 Node.js 版本配置每个作业。 有关矩阵策略和上下文的更多信息,请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)”和“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。
-
-{% raw %}
-```yaml
-strategy:
- matrix:
- node-version: [8.x, 10.x, 12.x]
-
-steps:
-- uses: actions/checkout@v2
-- name: Use Node.js ${{ matrix.node-version }}
- uses: actions/setup-node@v1
- with:
- node-version: ${{ matrix.node-version }}
-```
-{% endraw %}
-
-您也可以构建和测试精确的 Node.js 版本。
-
-```yaml
-strategy:
- matrix:
- node-version: [8.16.2, 10.17.0]
-```
-
-或者,您也可以使用单个版本的 Node.js 构建和测试。
-
-{% raw %}
-```yaml
-name: Node.js CI
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ubuntu-latest
-
- steps:
- - uses: actions/checkout@v2
- - name: Use Node.js
- uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- - run: npm install
- - run: npm run build --if-present
- - run: npm test
- env:
- CI: true
-```
-{% endraw %}
-
-如果不指定 Node.js 版本,{% data variables.product.prodname_dotcom %} 将使用环境的默认 Node.js 版本。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器上安装的软件](/actions/automating-your-workflow-with-github-actions/software-installed-on-github-hosted-runners)”。
-
-### 安装依赖项
-
-{% data variables.product.prodname_dotcom %} 托管的运行器安装了 npm 和 Yarn 依赖项管理器。 在构建和测试代码之前,可以使用 npm 和 Yarn 在工作流程中安装依赖项。 Windows 和 Linux {% data variables.product.prodname_dotcom %} 托管的运行器也安装了 Grunt、Gulp 和 Bower。
-
-您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。
-
-#### 使用 npm 的示例
-
-此示例安装 *package.json* 文件中定义的依赖项。 更多信息请参阅 [`npm install`](https://docs.npmjs.com/cli/install)。
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Use Node.js
- uses: actions/setup-node@v1
- with:
- node-version: '12.x'
-- name: Install dependencies
- run: npm install
-```
-
-使用 `npm ci` 将版本安装到 *package-lock.json* 或 *npm-shrinkwraw.json* 文件并阻止更新锁定文件。 使用 `npm ci` 通常比运行 `npm install` 更快。 更多信息请参阅 [`npm ci`](https://docs.npmjs.com/cli/ci.html) 和“[引入 `npm ci` 以进行更快、更可靠的构建](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)”。
-
-{% raw %}
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Use Node.js
- uses: actions/setup-node@v1
- with:
- node-version: '12.x'
-- name: Install dependencies
- run: npm ci
-```
-{% endraw %}
-
-#### 使用 Yarn 的示例
-
-此示例安装 *package.json* 文件中定义的依赖项。 更多信息请参阅 [`yarn install`](https://yarnpkg.com/en/docs/cli/install)。
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Use Node.js
- uses: actions/setup-node@v1
- with:
- node-version: '12.x'
-- name: Install dependencies
- run: yarn
-```
-
-或者,您可以传递 `--frozen-lockfile` 来安装 *yarn.lock* 文件中的版本,并阻止更新 *yarn.lock* 文件。
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Use Node.js
- uses: actions/setup-node@v1
- with:
- node-version: '12.x'
-- name: Install dependencies
- run: yarn --frozen-lockfile
-```
-
-#### 使用私有注册表并创建 .npmrc 文件的示例
-
-{% data reusables.github-actions.setup-node-intro %}
-
-要验证您的私有注册表,需要将 npm 身份验证令牌在仓库设置中存储为密码。 例如,创建名为 `NPM_TOKEN` 的密码。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-在下面的示例中,密码 `NPM_TOKEN` 用于存储 npm 身份验证令牌。 `setup-node` 操作配置 *.npmrc* 文件从 `NODE_AUTH_TOKEN` 环境变量读取 npm 身份验证令牌。 使用 `setup-node` 操作创建 *.npmrc* 文件时,必须使用包含 npm 身份验证令牌的密码设置 `NPM_AUTH_TOKEN` 环境变量。
-
-在安装依赖项之前,使用 `setup-node` 操作创建 *.npmrc* 文件。 该操作有两个输入参数。 `node-version` 参数设置 Node.js 版本,`registry-url` 参数设置默认注册表。 如果包注册表使用作用域,您必须使用 `scope` 参数。 更多信息请参阅 [`npm-scope`](https://docs.npmjs.com/misc/scope)。
-
-{% raw %}
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Use Node.js
- uses: actions/setup-node@v1
- with:
- always-auth: true
- node-version: '12.x'
- registry-url: https://registry.npmjs.org
- scope: '@octocat'
-- name: Install dependencies
- run: npm ci
- env:
- NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
-```
-{% endraw %}
-
-上面的示例创建了一个包含以下内容的 *.npmrc* 文件:
-
-```
-//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
-@octocat:registry=https://registry.npmjs.org/
-always-auth=true
-```
-
-#### 缓存依赖项示例
-
-您可以使用唯一的密钥缓存依赖项,并在使用 `cache` 操作运行未来的工作流程时恢复依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。
-
-{% raw %}
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Use Node.js
- uses: actions/setup-node@v1
- with:
- node-version: '12.x'
-- name: Cache Node.js modules
- uses: actions/cache@v2
- with:
- # npm cache files are stored in `~/.npm` on Linux/macOS
- path: ~/.npm
- key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }}
- restore-keys: |
- ${{ runner.OS }}-node-
- ${{ runner.OS }}-
-- name: Install dependencies
- run: npm ci
-```
-{% endraw %}
-
-### 构建和测试代码
-
-您可以使用与本地相同的命令来构建和测试代码。 例如,如果您运行 `npm run build` 来运行 *package.json* 文件中定义的构建步骤,运行 `npm test` 来运行测试套件,则要在工作流程文件中添加以下命令。
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Use Node.js
- uses: actions/setup-node@v1
- with:
- node-version: '12.x'
-- run: npm install
-- run: npm run build --if-present
-- run: npm test
-```
-
-### 将工作流数据打包为构件
-
-您可以保存构建和测试步骤中的构件以在作业完成后查看。 例如,您可能需要保存日志文件、核心转储、测试结果或屏幕截图。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
-
-### 发布到包注册表
-
-您可以配置工作流程在 CI 测试通过后将 Node.js 包发布到包注册表。 有关发布到 npm 和 {% data variables.product.prodname_registry %} 的更多信息,请参阅“[发布 Node.js 包](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)”。
diff --git a/translations/zh-CN/content/actions/language-and-framework-guides/using-python-with-github-actions.md b/translations/zh-CN/content/actions/language-and-framework-guides/using-python-with-github-actions.md
deleted file mode 100644
index 27cd8d86fb43..000000000000
--- a/translations/zh-CN/content/actions/language-and-framework-guides/using-python-with-github-actions.md
+++ /dev/null
@@ -1,499 +0,0 @@
----
-title: 将 Python 与 GitHub 操作一起使用
-intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 Python 项目。
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/using-python-with-github-actions
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-本指南介绍如何构建、测试和发布 Python 包。
-
-{% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件,包括 Python 和 PyPy。 您无需安装任何项目! 有关最新版软件以及 Python 和 PyPy 预安装版本的完整列表,请参阅 [{% data variables.product.prodname_dotcom %} 自托管运行器上安装的软件](/actions/automating-your-workflow-with-github-actions/software-installed-on-github-hosted-runners)。
-
-### 基本要求
-
-您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。
-
-建议您对 Python、PyPy 和 pip 有个基本的了解。 更多信息请参阅:
-- [开始使用 Python](https://www.python.org/about/gettingstarted/)
-- [PyPy](https://pypy.org/)
-- [Pip 包管理器](https://pypi.org/project/pip/)
-
-{% data reusables.actions.enterprise-setup-prereq %}
-
-### 从 Python 工作流程模板开始
-
-{% data variables.product.prodname_dotcom %} 提供有 Python 工作流程模板,应该适用于大多数 Python 项目。 本指南包含可用于自定义模板的示例。 更多信息请参阅 [Python 工作流程模板](https://github.com/actions/starter-workflows/blob/master/ci/python-package.yml)。
-
-要快速开始,请将模板添加到仓库的 `.github/workflows` 目录中。
-
-{% raw %}
-```yaml
-name: Python package
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ubuntu-latest
- strategy:
- matrix:
- python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
-
- steps:
- - uses: actions/checkout@v2
- - name: Set up Python ${{ matrix.python-version }}
- uses: actions/setup-python@v2
- with:
- python-version: ${{ matrix.python-version }}
- - name: Install dependencies
- run: |
- python -m pip install --upgrade pip
- pip install flake8 pytest
- if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
- - name: Lint with flake8
- run: |
- # 如果有任何 Python 语法错误或未定义的名称,停止构建
- flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
- # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
- flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
- - name: Test with pytest
- run: |
- pytest
-```
-{% endraw %}
-
-### 指定 Python 版本
-
-要在 {% data variables.product.prodname_dotcom %} 托管的运行器上使用预安装的 Python 或 PyPy 版本,请使用 `setup-python` 操作。 此操作从每个运行器上的工具缓存中查找特定版本的 Python 或 PyPy,并将必要的二进制文件添加到 `PATH`,这可继续用于作业的其余部分。 如果工具缓存中未安装特定版本的 Python,`setup-python` 操作将从 [`python-versions`](https://github.com/actions/python-versions) 仓库下载并设置适当的版本。
-
-使用 `setup-action` 是 Python 与 {% data variables.product.prodname_actions %} 结合使用时的推荐方式,因为它能确保不同运行器和不同版本的 Python 行为一致。 如果使用自托管运行器,则必须安装 Python 并将其添加到 `PATH`。 更多信息请参阅 [`setup-python` 操作](https://github.com/marketplace/actions/setup-python)。
-
-下表描述了每个 {% data variables.product.prodname_dotcom %} 托管的运行器中工具缓存的位置。
-
-| | Ubuntu | Mac | Windows |
-| --------------- | ------------------------------- | ---------------------------------------- | ------------------------------------------ |
-| **工具缓存目录** | `/opt/hostedtoolcache/*` | `/Users/runner/hostedtoolcache/*` | `C:\hostedtoolcache\windows\*` |
-| **Python 工具缓存** | `/opt/hostedtoolcache/Python/*` | `/Users/runner/hostedtoolcache/Python/*` | `C:\hostedtoolcache\windows\Python\*` |
-| **PyPy 工具缓存** | `/opt/hostedtoolcache/PyPy/*` | `/Users/runner/hostedtoolcache/PyPy/*` | `C:\hostedtoolcache\windows\PyPy\*` |
-
-如果您正在使用自托管的运行器,则可以配置运行器使用 `setup-python` 操作来管理您的依赖项。 更多信息请参阅 `setup-python` 自述文件中的
-
-将 setup-python 与自托管运行器一起使用
。
-
-{% data variables.product.prodname_dotcom %} 支持语义版本控制语法。 更多信息请参阅“[使用语义版本控制](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)”和“[语义版本控制规范](https://semver.org/)”。
-
-
-
-#### 使用多个 Python 版本
-
-{% raw %}
-
-
-```yaml
-name: Python package
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ubuntu-latest
- strategy:
- # You can use PyPy versions in python-version.
- # 例如,pypy2 和 pypy3
- matrix:
- python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
-
- steps:
- - uses: actions/checkout@v2
- - name: Set up Python ${{ matrix.python-version }}
- uses: actions/setup-python@v2
- with:
- python-version: ${{ matrix.python-version }}
- # 您可以打印当前 Python 版本以测试矩阵
- - name: Display Python version
- run: python -c "import sys; print(sys.version)"
-```
-
-
-{% endraw %}
-
-
-
-#### 使用特定的 Python 版本
-
-您可以配置 python 的特定版本。 例如,3.8。 或者,您也可以通过语义版本语法来获得最新的次要版本。 此示例使用 Python 3 最新的次要版本。
-
-{% raw %}
-
-
-```yaml
-name: Python package
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ubuntu-latest
-
- steps:
- - uses: actions/checkout@v2
- - name: Set up Python 3.x
- uses: actions/setup-python@v2
- with:
- # Python 版本的语义版本范围矩阵或准确的版本
- python-version: '3.x'
- # 可选 - x64 或 x86 架构,默认为 x64
- architecture: 'x64'
- # 您可以打印当前 Python 版本以测试矩阵
- - name: Display Python version
- run: python -c "import sys; print(sys.version)"
-```
-
-
-{% endraw %}
-
-
-
-#### 排除版本
-
-如果指定不可用的 Python 版本,`setup-python` 将会失败,且显示如下错误:`##[error]Version 3.4 with arch x64 not found`。 错误消息包含可用的版本。
-
-如果存在您不想运行的 Python 配置,您也可以在工作流程中使用 `exclude` 关键字。 For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)."
-
-{% raw %}
-
-
-```yaml
-name: Python package
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ${{ matrix.os }}
- strategy:
- matrix:
- os: [ubuntu-latest, macos-latest, windows-latest]
- python-version: [2.7, 3.6, 3.7, 3.8, pypy2, pypy3]
- exclude:
- - os: macos-latest
- python-version: 3.6
- - os: windows-latest
- python-version: 3.6
-```
-
-
-{% endraw %}
-
-
-
-#### 使用默认 Python 版本
-
-建议使用 `setup-python` 配置工作流程中使用的 Python 版本,因为它有助于使您的依赖关系变得明朗。 如果不使用 `setup-python`,调用 `python` 时将在任何 shell 中使用 `PATH` 中设置的 Python 默认版本。 {% data variables.product.prodname_dotcom %} 托管的运行器之间有不同的 Python 默认版本,这可能导致非预期的更改或使用的版本比预期更旧。
-
-| {% data variables.product.prodname_dotcom %} 托管的运行器 | 描述 |
-| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Ubuntu | Ubuntu 运行器有多个版本的系统 Python 安装在 `/usr/bin/python` 和 `/usr/bin/python3` 下。 {% data variables.product.prodname_dotcom %} 除了安装在工具缓存中的版本,还有与 Ubuntu 一起打包的 Python 版本。 |
-| Windows | 不包括工具缓存中的 Python 版本,Windows 未随附同等版本的系统 Python。 为保持与其他运行器一致的行为,并允许 Python 在没有 `setup-python` 操作的情况下开箱即用,{% data variables.product.prodname_dotcom %} 将从工具缓存中添加几个版本到 `PATH`。 |
-| macOS | 除了作为工具缓存一部分的版本外,macOS 运行器还安装了多个版本的系统 Python。 系统 Python 版本位于 `/usr/local/Cellar/python/*` 目录中。 |
-
-
-
-
-### 安装依赖项
-
-{% data variables.product.prodname_dotcom %} 托管的运行器安装了 pip 软件包管理器。 在构建和测试代码之前,您可以使用 pip 从 PyPI 软件包注册表安装依赖项。 例如,下面的 YAML 安装或升级 `pip` 软件包安装程序以及 `setuptools` 和 `wheel` 软件包。
-
-您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。
-
-{% raw %}
-
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Set up Python
- uses: actions/setup-python@v2
- with:
- python-version: '3.x'
-- name: Install dependencies
- run: python -m pip install --upgrade pip setuptools wheel
-```
-
-
-{% endraw %}
-
-
-
-#### 要求文件
-
-在更新 `pip` 后,下一步通常是从 *requires.txt* 安装依赖项。
-
-{% raw %}
-
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Set up Python
- uses: actions/setup-python@v2
- with:
- python-version: '3.x'
-- name: Install dependencies
- run: |
- python -m pip install --upgrade pip
- pip install -r requirements.txt
-```
-
-
-{% endraw %}
-
-
-
-#### 缓存依赖项
-
-您可以使用唯一密钥缓存 pip 依赖项,并在使用 [`cache`](https://github.com/marketplace/actions/cache) 操作运行未来的工作流程时恢复依赖项。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)”。
-
-Pip 根据运行器的操作系统将依赖项缓存在不同的位置。 您需要缓存的路径可能不同于下面的 Ubuntu 示例,具体取决于您使用的操作系统。 更多信息请参阅 [Python 缓存示例](https://github.com/actions/cache/blob/master/examples.md#python---pip)。
-
-{% raw %}
-
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Setup Python
- uses: actions/setup-python@v2
- with:
- python-version: '3.x'
-- name: Cache pip
- uses: actions/cache@v2
- with:
- # This path is specific to Ubuntu
- path: ~/.cache/pip
- # Look to see if there is a cache hit for the corresponding requirements file
- key: ${{ runner.os }}-pip-${{ hashFiles('requirements.txt') }}
- restore-keys: |
- ${{ runner.os }}-pip-
- ${{ runner.os }}-
-- name: Install dependencies
- run: pip install -r requirements.txt
-```
-
-
-{% endraw %}
-
-{% note %}
-
-**注意:**取决于依赖项的数量,使用依赖项缓存可能会更快。 有很多大型依赖项的项目应该能看到性能明显提升,因为下载所需的时间会缩短。 依赖项较少的项目可能看不到明显的性提升,甚至可能由于pip 安装缓存依赖项的方式而看到性能略有下降。 性能因项目而异。
-
-{% endnote %}
-
-
-
-### 测试代码
-
-您可以使用与本地相同的命令来构建和测试代码。
-
-
-
-#### 使用 pytest 和 pytest-cov 测试
-
-此示例安装或升级 `pytest` 和 `pest-cov`。 然后进行测试并以 JUnit 格式输出,而代码覆盖结果则以 Cobertura 输出。 更多信息请参阅 [JUnit](https://junit.org/junit5/) 和 [Cobertura](https://cobertura.github.io/cobertura/)。
-
-{% raw %}
-
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Set up Python
- uses: actions/setup-python@v2
- with:
- python-version: '3.x'
-- name: Install dependencies
- run: |
- python -m pip install --upgrade pip
- pip install -r requirements.txt
-- name: Test with pytest
- run: |
- pip install pytest
- pip install pytest-cov
- pytest tests.py --doctest-modules --junitxml=junit/test-results.xml --cov=com --cov-report=xml --cov-report=html
-```
-
-
-{% endraw %}
-
-
-
-#### 使用 Flake8 嵌入代码
-
-下面的示例安装或升级 `flake8` 并用它来嵌入所有文件。 更多信息请参阅 [Flake8](http://flake8.pycqa.org/en/latest/)。
-
-{% raw %}
-
-
-```yaml
-steps:
-- uses: actions/checkout@v2
-- name: Set up Python
- uses: actions/setup-python@v2
- with:
- python-version: '3.x'
-- name: Install dependencies
- run: |
- python -m pip install --upgrade pip
- pip install -r requirements.txt
-- name: Lint with flake8
- run: |
- pip install flake8
- flake8 .
-```
-
-
-{% endraw %}
-
-
-
-#### 使用 tox 运行测试
-
-通过 {% data variables.product.prodname_actions %},您可以使用 tox 运行测试并将工作分散到多个作业。 您需要使用 `-e py` 选项调用 tox,以在 `PATH` 中选择 Python 版本,而不是指定特定版本。 更多信息请参阅 [tox](https://tox.readthedocs.io/en/latest/)。
-
-{% raw %}
-
-
-```yaml
-name: Python package
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ubuntu-latest
- strategy:
- matrix:
- python: [2.7, 3.7, 3.8]
-
- steps:
- - uses: actions/checkout@v2
- - name: Setup Python
- uses: actions/setup-python@v2
- with:
- python-version: ${{ matrix.python }}
- - name: Install Tox and any other packages
- run: pip install tox
- - name: Run Tox
- # 使用 `PATH` 中的 Python 版本运行 tox
- run: tox -e py
-```
-
-
-{% endraw %}
-
-
-
-### 将工作流数据打包为构件
-
-您可以在工作流程完成后上传构件以查看。 例如,您可能需要保存日志文件、核心转储、测试结果或屏幕截图。 更多信息请参阅“[使用构件持久化工作流程](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
-
-下面的示例演示如何使用 `upload-artifact` 操作来存档运行 `pytest` 的测试结果。 更多信息请参阅 [`upload-artifact` 操作](https://github.com/actions/upload-artifact)。
-
-{% raw %}
-
-
-```yaml
-name: Python package
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ubuntu-latest
- strategy:
- matrix:
- python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
-
- steps:
- - uses: actions/checkout@v2
- - name: Setup Python # Set Python version
- uses: actions/setup-python@v2
- with:
- python-version: ${{ matrix.python-version }}
- # Install pip and pytest
- - name: Install dependencies
- run: |
- python -m pip install --upgrade pip
- pip install pytest
- - name: Test with pytest
- run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
- - name: Upload pytest test results
- uses: actions/upload-artifact@v2
- with:
- name: pytest-results-${{ matrix.python-version }}
- path: junit/test-results-${{ matrix.python-version }}.xml
- # Use always() to always run this step to publish test results when there are test failures
- if: ${{ always() }}
-```
-
-
-{% endraw %}
-
-
-
-### 发布到包注册表
-
-您可以配置工作流程在 CI 测试通过时将 Python 包发布到您想要的任何包注册表。
-
-您可以使用仓库密码存储发布软件包所需的访问令牌或凭据。 下面的示例使用 `twine` 和 `dist` 创建包并发布到 PyPI。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-{% raw %}
-
-
-```yaml
-name: Upload Python Package
-
-on:
- release:
- types: [created]
-
-jobs:
- deploy:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- - name: Set up Python
- uses: actions/setup-python@v2
- with:
- python-version: '3.x'
- - name: Install dependencies
- run: |
- python -m pip install --upgrade pip
- pip install setuptools wheel twine
- - name: Build and publish
- env:
- TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
- TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
- run: |
- python setup.py sdist bdist_wheel
- twine upload dist/*
-```
-
-
-{% endraw %}
-
-有关模板工作流程的更多信息,请参阅 [`python-published`](https://github.com/actions/starter-workflows/blob/master/ci/python-publish.yml)。
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/index.md b/translations/zh-CN/content/actions/migrating-to-github-actions/index.md
deleted file mode 100644
index 8fe3703ac50c..000000000000
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/index.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: 迁移到 GitHub 操作
-intro: '从其他持续集成 (CI) 提供程序迁移到 {% data variables.product.prodname_actions %}。'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% link_in_list /migrating-from-circleci-to-github-actions %}
-{% link_in_list /migrating-from-azure-pipelines-to-github-actions %}
-{% link_in_list /migrating-from-jenkins-to-github-actions %}
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
deleted file mode 100644
index fec437c6131b..000000000000
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
+++ /dev/null
@@ -1,366 +0,0 @@
----
-title: 从 Azure Pelines 迁移到 GitHub 操作
-intro: '{% data variables.product.prodname_actions %} 和 Azure Pipelines 具有一些相似的配置,这使得迁移到 {% data variables.product.prodname_actions %} 很简单。'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-Azure Pipelines 和 {% data variables.product.prodname_actions %} 都允许您创建能自动构建、测试、发布、发行和部署代码的工作流程。 Azure Pelines 和 {% data variables.product.prodname_actions %} 的工作流程配置有一些相似之处:
-
-- 工作流程配置文件以 YAML 编写并存储在代码仓库中。
-- 工作流程包括一项或多项作业。
-- 作业包括一个或多个步骤或单个命令。
-- 步骤或任务可以重复使用并与社区共享。
-
-更多信息请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)”。
-
-### 主要差异
-
-从 Azure Pipelines 迁移时,考虑以下差异:
-
-- Azure Pelines 支持传统的_经典编辑器_,可让您在 GUI 编辑器中定义 CI 配置,而不是在 YAML 文件中创建管道定义。 {% data variables.product.prodname_actions %} 使用 YAML 文件来定义工作流程,不支持图形编辑器。
-- Azure Pelines 允许您在作业定义中省略一些结构。 例如,如果您只有一个作业,则无需定义作业,只需要定义其步骤。 {% data variables.product.prodname_actions %} 需要明确的配置,且不能省略 YAML 结构。
-- Azure Pipelines 支持 YAML 文件中定义的_阶段_,可用于创建部署工作流程。 {% data variables.product.prodname_actions %} 要求您将阶段分成单独的 YAML 工作流程文件。
-- 可以使用功能选择本地 Azure Pipelines 构建代理。 通过标签可以选择 {% data variables.product.prodname_actions %} 自托管的运行器。
-
-### 迁移作业和步骤
-
-Azure Pelines 中的作业和步骤非常类似于 {% data variables.product.prodname_actions %} 中的作业和步骤。 在这两个系统中,作业具有以下特征:
-
-* 作业包含一系列按顺序运行的步骤。
-* 作业在单独的虚拟机或单独的容器中运行。
-* 默认情况下作业并行运行,但可以配置为按顺序运行。
-
-### 迁移脚本步骤
-
-可以将脚本或 shell 命令作为工作流程中的步骤运行。 在 Azure Pipelines 中,脚本步骤可以使用 `script` 键指定,或者使用 `bash`、`powershell` 或 `pwsh` 键指定。 脚本也可以指定为 [Bash 任务](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/bash?view=azure-devops)或 [PowerShell 任务](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/powershell?view=azure-devops)的输入。
-
-在 {% data variables.product.prodname_actions %} 中,所有脚本都使用 `run` 键来指定。 要选择特定的 shell,您可以在提供脚本时指定 `shell` 键。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。
-
-下面是每个系统的语法示例:
-
-
-
-
-Azure Pipelines
- |
-
-{% data variables.product.prodname_actions %}
- |
-
-
-
-{% raw %}
-```yaml
-jobs:
-- job: scripts
- pool:
- vmImage: 'windows-latest'
- steps:
- - script: echo "This step runs in the default shell"
- - bash: echo "This step runs in bash"
- - pwsh: Write-Host "This step runs in PowerShell Core"
- - task: PowerShell@2
- inputs:
- script: Write-Host "This step runs in PowerShell"
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-jobs:
- scripts:
- runs-on: windows-latest
- steps:
- - run: echo "This step runs in the default shell"
- - run: echo "This step runs in bash"
- shell: bash
- - run: Write-Host "This step runs in PowerShell Core"
- shell: pwsh
- - run: Write-Host "This step runs in PowerShell"
- shell: powershell
-```
-{% endraw %}
- |
-
-
-
-### 脚本错误处理中的差异
-
-在 Azure Pipelines 中,脚本可配置为有任何输出发送到 `stderr` 时出错。 {% data variables.product.prodname_actions %} 不支持此配置。
-
-{% data variables.product.prodname_actions %} 尽可能将 shell 配置为“快速失败”,如果脚本中的一个命令退出并有错误代码,则会立即停止脚本。 相反,Azure Pipelines 需要明确配置为在出错时立即退出。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)”。
-
-### Windows 上默认 shell 的差异
-
-在 Azure Pelines 中,Windows 平台上脚本的默认 shell 是命令 shell (_cmd.exe_)。 在 {% data variables.product.prodname_actions %} 中,Windows 平台上脚本的默认 shell 是 PowerShell 。 PowerShell 在内置命令、变量扩展和流控制方面存在若干差异。
-
-如果您运行的是简单的命令,则可以在 PowerShell 中运行命令 shell 脚本,而无需进行任何更改。 但在大多数情况下,您需要使用 PowerShell 语法更新脚本,或者指示 {% data variables.product.prodname_actions %} 使用命令 shell 而不是 PowerShell 来运行脚本。 您可以通过将 `shell` 指定为 `Cmd` 来完成。
-
-下面是每个系统的语法示例:
-
-
-
-
-Azure Pipelines
- |
-
-{% data variables.product.prodname_actions %}
- |
-
-
-
-{% raw %}
-```yaml
-jobs:
-- job: run_command
- pool:
- vmImage: 'windows-latest'
- steps:
- - script: echo "This step runs in CMD on Windows by default"
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-jobs:
- run_command:
- runs-on: windows-latest
- steps:
- - run: echo "This step runs in PowerShell on Windows by default"
- - run: echo "This step runs in CMD on Windows explicitly"
- shell: cmd
-```
-{% endraw %}
- |
-
-
-
-更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)”。
-
-### 迁移条件和表达式语法
-
-Azure Pipelines 和 {% data variables.product.prodname_actions %} 可以有条件地运行步骤。 在 Azure Pipelines 中,使用 `condition` 键指定条件表达式。 在 {% data variables.product.prodname_actions %} 中,条件表达式使用 `if` 键来指定。
-
-Azure Pelines 使用表达式中的函数来有条件地执行步骤。 相反,{% data variables.product.prodname_actions %} 使用 infix 表示法。 例如,必须将 Azure Pipelines 中的 `eq` 函数替换为 {% data variables.product.prodname_actions %} 中的 `==` 运算符。
-
-下面是每个系统的语法示例:
-
-
-
-
-Azure Pipelines
- |
-
-{% data variables.product.prodname_actions %}
- |
-
-
-
-{% raw %}
-```yaml
-jobs:
-- job: conditional
- pool:
- vmImage: 'ubuntu-latest'
- steps:
- - script: echo "This step runs with str equals 'ABC' and num equals 123"
- condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123))
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-jobs:
- conditional:
- runs-on: ubuntu-latest
- steps:
- - run: echo "This step runs with str equals 'ABC' and num equals 123"
- if: ${{ env.str == 'ABC' && env.num == 123 }}
-```
-{% endraw %}
- |
-
-
-
-更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。
-
-### 作业之间的依赖关系
-
-Azure Pipelines 和 {% data variables.product.prodname_actions %} 允许您为作业设置依赖项。 在这两个系统中,默认情况下作业并行运行,但可以明确指定作业依赖项。 在 Azure Pipelines 中,这通过 `dependsOn` 键来完成。 在 {% data variables.product.prodname_actions %} 中,这通过 `needs` 键来完成。
-
-下面是每个系统的语法示例: 工作流程启动第一个名为 `initial` 的作业,当该作业完成时,两个分别名为 `fanout1` 和 `fanout2` 的作业将会运行。 最后,当这些作业完成后,作业 `fanin` 将会运行。
-
-
-
-
-Azure Pipelines
- |
-
-{% data variables.product.prodname_actions %}
- |
-
-
-
-{% raw %}
-```yaml
-jobs:
-- job: initial
- pool:
- vmImage: 'ubuntu-latest'
- steps:
- - script: echo "This job will be run first."
-- job: fanout1
- pool:
- vmImage: 'ubuntu-latest'
- dependsOn: initial
- steps:
- - script: echo "This job will run after the initial job, in parallel with fanout2."
-{% raw %}
-```yaml
-jobs:
-- job: initial
- pool:
- vmImage: 'ubuntu-latest'
- steps:
- - script: echo "This job will be run first."
-- job: fanout1
- pool:
- vmImage: 'ubuntu-latest'
- dependsOn: initial
- steps:
- - script: echo "This job will run after the initial job, in parallel with fanout2."
-- job: fanout2
- pool:
- vmImage: 'ubuntu-latest'
- dependsOn: initial
- steps:
- - script: echo "This job will run after the initial job, in parallel with fanout1."
-- job: fanin:
- pool:
- vmImage: 'ubuntu-latest'
- dependsOn: [fanout1, fanout2]
- steps:
- - script: echo "This job will run after fanout1 and fanout2 have finished."
-```
-{% endraw %}
-- job: fanin:
- pool:
- vmImage: 'ubuntu-latest'
- dependsOn: [fanout1, fanout2]
- steps:
- - script: echo "This job will run after fanout1 and fanout2 have finished."
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-jobs:
- initial:
- runs-on: ubuntu-latest
- steps:
- - run: echo "This job will be run first."
- fanout1:
- runs-on: ubuntu-latest
- needs: initial
- steps:
- - run: echo "This job will run after the initial job, in parallel with fanout2."
- {% raw %}
-```yaml
-jobs:
- initial:
- runs-on: ubuntu-latest
- steps:
- - run: echo "This job will be run first."
- fanout1:
- runs-on: ubuntu-latest
- needs: initial
- steps:
- - run: echo "This job will run after the initial job, in parallel with fanout2."
- fanout2:
- runs-on: ubuntu-latest
- needs: initial
- steps:
- - run: echo "This job will run after the initial job, in parallel with fanout1."
- fanin:
- runs-on: ubuntu-latest
- needs: [fanout1, fanout2]
- steps:
- - run: echo "This job will run after fanout1 and fanout2 have finished."
-```
-{% endraw %}
- fanin:
- runs-on: ubuntu-latest
- needs: [fanout1, fanout2]
- steps:
- - run: echo "This job will run after fanout1 and fanout2 have finished."
-```
-{% endraw %}
- |
-
-
-
-更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)”。
-
-### 将任务迁移到操作
-
-Azure Pipelines 使用_任务_,这是可在多个工作流程中重复使用的应用程序组件。 {% data variables.product.prodname_actions %} 使用 _操作_,这可用于执行任务和自定义工作流程。 在这两个系统中,您可以指定要运行的任务或操作的名称,以及任何必需的输入作为键/值对。
-
-下面是每个系统的语法示例:
-
-
-
-
-Azure Pipelines
- |
-
-{% data variables.product.prodname_actions %}
- |
-
-
-
-{% raw %}
-```yaml
-jobs:
-- job: run_python
- pool:
- vmImage: 'ubuntu-latest'
- steps:
- - task: UsePythonVersion@0
- inputs:
- versionSpec: '3.7'
- architecture: 'x64'
- - script: python script.py
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-jobs:
- run_python:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/setup-python@v2
- with:
- python-version: '3.7'
- architecture: 'x64'
- - run: python script.py
-```
-{% endraw %}
- |
-
-
-
-您可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中找到可用于工作流程的操作,也可以创建自己的操作。 更多信息请参阅“[创建操作](/actions/creating-actions)”。
-
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
deleted file mode 100644
index 740c992870ca..000000000000
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
+++ /dev/null
@@ -1,445 +0,0 @@
----
-title: 从 CircleCI 迁移到 GitHub 操作
-intro: GitHub 操作和 CircleCI 在配置上具有若干相似之处,这使得迁移到 GitHub 操作相对简单。
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-CircleCI 和 {% data variables.product.prodname_actions %} 都允许您创建能自动构建、测试、发布、发行和部署代码的工作流程。 CircleCI 和 {% data variables.product.prodname_actions %} 的工作流程配置有一些相似之处:
-
-- 工作流程配置文件以 YAML 编写并存储在仓库中。
-- 工作流程包括一项或多项作业。
-- 作业包括一个或多个步骤或单个命令。
-- 步骤或任务可以重复使用并与社区共享。
-
-更多信息请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)”。
-
-### 主要差异
-
-从 CircleCI 迁移时,考虑以下差异:
-
-- CircleCI 的自动测试并行性根据用户指定的规则或历史计时信息自动对测试进行分组。 此功能未内置于 {% data variables.product.prodname_actions %}。
-- 在 Docker 容器中执行的操作对权限问题很敏感,因为容器具有不同的用户映射。 您可以通过在 *Dockerfile* 中不使用 `USER` 指令来避免这些问题。 有关 Docker 文件系统的更多信息,请参阅“[ {% data variables.product.product_name %} 托管运行器的虚拟环境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)”。
-
-### 迁移工作流程和作业
-
-CircleCI 在 *config.yml* 文件中定义 `workflows`,允许您配置多个工作流程。 {% data variables.product.product_name %} 对每个工作流程需要一个工作流程文件,因此不要求您声明 `workflows`。 您需要为 *config.yml* 中配置的每个工作流程创建一个新的工作流程文件。
-
-CircleCI 和 {% data variables.product.prodname_actions %} 在配置文件中使用相似的语法配置 `jobs`。 如果在 CircleCI 工作流程中使用 `requires` 配置作业之间的任何依赖项,您可以使用等效的 {% data variables.product.prodname_actions %} `needs` 语法。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)”。
-
-### 将 orbs 迁移到操作
-
-CircleCI 和 {% data variables.product.prodname_actions %} 都提供在工作流程中重复使用和共享任务的机制。 CircleCI 使用以 YAML 编写的概念 orbs 来提供人们可以在工作流程中重复使用的任务。 {% data variables.product.prodname_actions %} 具有强大而灵活的可重复使用的组件,称为“操作”,您可以使用 JavaScript 文件或 Docker 映像来构建操作。 您可以编写自定义代码来创建操作,以您喜欢的方式与仓库交互,包括使用 {% data variables.product.product_name %} 的 API 以及任何公开的第三方 API 进行交互。 例如,操作可以发布 npm 模块、在创建紧急议题时发送短信提醒,或者部署可用于生产的代码。 更多信息请参阅“[创建操作](/actions/creating-actions)”。
-
-CircleCI 可以使用 YAML 锚点和别名来重复使用工作流程的组件。 {% data variables.product.prodname_actions %} 支持对于重复使用构建矩阵的最常见需求。 有关构建矩阵的更多信息,请参阅“[配置工作流程](/actions/configuring-and-managing-workflows/configuring-a-workflow#configuring-a-build-matrix)。
-
-### 使用 Docker 映像
-
-
-CircleCI 和 {% data variables.product.prodname_actions %} 都支持在 Docker 映像中运行步骤。
-
-CircleCI 提供一套具有共同依赖项的预建映像。 这些映像的 `USER` 设置为 `circleci`,会导致权限与 {% data variables.product.prodname_actions %} 冲突。
-
-建议在迁移到 {% data variables.product.prodname_actions %} 时不使用 CircleCI 的预建映像。 在许多情况下,您可以使用操作来安装需要的附加依赖项。
-
-有关 Docker 文件系统的更多信息,请参阅“[ {% data variables.product.product_name %} 托管运行器的虚拟环境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)”。
-
-有关 {% data variables.product.prodname_dotcom %} 托管的虚拟环境中可用的工具和软件包的更多信息,请参阅“[GitHub 托管的运行器上安装的软件](/actions/reference/software-installed-on-github-hosted-runners)”。
-
-### 使用变量和密码
-
-CircleCI 和 {% data variables.product.prodname_actions %} 支持在配置文件中设置环境变量,并使用 CircleCI 或 {% data variables.product.product_name %} UI 创建密码。
-
-更多信息请参阅“[使用环境变量](/actions/configuring-and-managing-workflows/using-environment-variables)”和“[创建和使用加密密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)”。
-
-### 缓存
-
-CircleCI 和 {% data variables.product.prodname_actions %} 提供在配置文件中手动缓存文件的方法。
-
-下面是每个系统的语法示例:
-
-
-
-
-CircleCI
- |
-
-GitHub Actions
- |
-
-
-
-{% raw %}
-```yaml
-- restore_cache:
- keys:
- - v1-npm-deps-{{ checksum "package-lock.json" }}
- - v1-npm-deps-
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-- name: Cache node modules
- uses: actions/cache@v2
- with:
- path: ~/.npm
- key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }}
- restore-keys: v1-npm-deps-
-```
-{% endraw %}
- |
-
-
-
-更多信息请参阅“[缓存依赖项以加快工作流程](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)”。
-
-{% data variables.product.prodname_actions %} 没有 CircleCI 的 Docker 层缓存(或 DLC)的等效项。
-
-### 在作业之间保持数据
-
-CircleCI 和 {% data variables.product.prodname_actions %} 提供在作业之间保持数据的机制。
-
-下面是 CircleCI 和 {% data variables.product.prodname_actions %} 配置语法中的示例。
-
-
-
-
-CircleCI
- |
-
-GitHub Actions
- |
-
-
-
-{% raw %}
-```yaml
-- persist_to_workspace:
- root: workspace
- paths:
- - math-homework.txt
-
-...
-
-- attach_workspace:
- at: /tmp/workspace
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-- name: Upload math result for job 1
- uses: actions/upload-artifact@v2
- with:
- name: homework
- path: math-homework.txt
-
-...
-
-- name: Download math result for job 1
- uses: actions/download-artifact@v2
- with:
- name: homework
-```
-{% endraw %}
- |
-
-
-
-更多信息请参阅“[使用构件持久化工作流程](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)”。
-
-### 使用数据库和服务容器
-
-这两个系统都允许您包括用于数据库、缓存或其他依赖项的其他容器。
-
-在 CircleCI 中,*config.yaml* 中列出的第一个映像是用于运行命令的主要映像。 {% data variables.product.prodname_actions %} 使用明确的区域: `container` 用于主容器,并在 `services` 中列出附加容器。
-
-下面是 CircleCI 和 {% data variables.product.prodname_actions %} 配置语法中的示例。
-
-
-
-
-CircleCI
- |
-
-GitHub Actions
- |
-
-
-
-{% raw %}
-```yaml
----
-version: 2.1
-
-jobs:
-
- ruby-26:
- docker:
- - image: circleci/ruby:2.6.3-node-browsers-legacy
- environment:
- PGHOST: localhost
- PGUSER: administrate
- RAILS_ENV: test
- - image: postgres:10.1-alpine
- environment:
- POSTGRES_USER: administrate
- POSTGRES_DB: ruby26
- POSTGRES_PASSWORD: ""
-
- working_directory: ~/administrate
-
- steps:
- - checkout
-
- # Bundle install dependencies
- - run: bundle install --path vendor/bundle
-
- # Wait for DB
- - run: dockerize -wait tcp://localhost:5432 -timeout 1m
-
- # Setup the environment
- - run: cp .sample.env .env
-
- # Setup the database
- - run: bundle exec rake db:setup
-
- # Run the tests
- - run: bundle exec rake
-
-
-workflows:
- version: 2
- build:
- jobs:
- - ruby-26
-...
-
-- attach_workspace:
- at: /tmp/workspace
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-name: Containers
-
-on: [push]
-
-jobs:
- build:
-
- runs-on: ubuntu-latest
- container: circleci/ruby:2.6.3-node-browsers-legacy
-
- env:
- PGHOST: postgres
- PGUSER: administrate
- RAILS_ENV: test
-
- services:
- postgres:
- image: postgres:10.1-alpine
- env:
- POSTGRES_USER: administrate
- POSTGRES_DB: ruby25
- POSTGRES_PASSWORD: ""
- ports:
- - 5432:5432
- # Add a health check
- options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
-
- steps:
- # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions.
- # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem
- - name: Setup file system permissions
- run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp
- - uses: actions/checkout@v2
- - name: Install dependencies
- run: bundle install --path vendor/bundle
- - name: Setup environment configuration
- run: cp .sample.env .env
- - name: Setup database
- run: bundle exec rake db:setup
- - name: Run tests
- run: bundle exec rake
-```
-{% endraw %}
- |
-
-
-
-更多信息请参阅“[关于服务容器](/actions/configuring-and-managing-workflows/about-service-containers)”。
-
-### 完整示例
-
-下面是一个真实的示例。 左边显示用于 [thoughtbot/administrator](https://github.com/thoughtbot/administrate) 仓库的实际 CircleCI *config.yml*。 右边显示 {% data variables.product.prodname_actions %} 等效项。
-
-
-
-
-CircleCI
- |
-
-GitHub Actions
- |
-
-
-
-{% raw %}
-```yaml
----
-version: 2.1
-
-commands:
- shared_steps:
- steps:
- - checkout
-
- # Restore Cached Dependencies
- - restore_cache:
- name: Restore bundle cache
- key: administrate-{{ checksum "Gemfile.lock" }}
-
- # Bundle install dependencies
- - run: bundle install --path vendor/bundle
-
- # Cache Dependencies
- - save_cache:
- name: Store bundle cache
- key: administrate-{{ checksum "Gemfile.lock" }}
- paths:
- - vendor/bundle
-
- # Wait for DB
- - run: dockerize -wait tcp://localhost:5432 -timeout 1m
-
- # Setup the environment
- - run: cp .sample.env .env
-
- # Setup the database
- - run: bundle exec rake db:setup
-
- # Run the tests
- - run: bundle exec rake
-
-default_job: &default_job
- working_directory: ~/administrate
- steps:
- - shared_steps
- # Run the tests against multiple versions of Rails
- - run: bundle exec appraisal install
- - run: bundle exec appraisal rake
-
-jobs:
- ruby-25:
- <<: *default_job
- docker:
- - image: circleci/ruby:2.5.0-node-browsers
- environment:
- PGHOST: localhost
- PGUSER: administrate
- RAILS_ENV: test
- - image: postgres:10.1-alpine
- environment:
- POSTGRES_USER: administrate
- POSTGRES_DB: ruby25
- POSTGRES_PASSWORD: ""
-
- ruby-26:
- <<: *default_job
- docker:
- - image: circleci/ruby:2.6.3-node-browsers-legacy
- environment:
- PGHOST: localhost
- PGUSER: administrate
- RAILS_ENV: test
- - image: postgres:10.1-alpine
- environment:
- POSTGRES_USER: administrate
- POSTGRES_DB: ruby26
- POSTGRES_PASSWORD: ""
-
-
-workflows:
- version: 2
- multiple-rubies:
- jobs:
- - ruby-26
- - ruby-25
-```
-{% endraw %}
- |
-
-{% raw %}
-```yaml
-name: Containers
-
-on: [push]
-
-jobs:
- build:
-
- strategy:
- matrix:
- ruby: [2.5, 2.6.3]
-
- runs-on: ubuntu-latest
-
- env:
- PGHOST: localhost
- PGUSER: administrate
- RAILS_ENV: test
-
- services:
- postgres:
- image: postgres:10.1-alpine
- env:
- POSTGRES_USER: administrate
- POSTGRES_DB: ruby25
- POSTGRES_PASSWORD: ""
- ports:
- - 5432:5432
- # Add a health check
- options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
-
- steps:
- - uses: actions/checkout@v2
- - name: Setup Ruby
- uses: eregon/use-ruby-action@master
- with:
- ruby-version: ${{ matrix.ruby }}
- - name: Cache dependencies
- uses: actions/cache@v2
- with:
- path: vendor/bundle
- key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}
- - name: Install postgres headers
- run: sudo apt-get install libpq-dev
- - name: Install dependencies
- run: bundle install --path vendor/bundle
- - name: Setup environment configuration
- run: cp .sample.env .env
- - name: Setup database
- run: bundle exec rake db:setup
- - name: Run tests
- run: bundle exec rake
- - name: Install appraisal
- run: bundle exec appraisal install
- - name: Run appraisal
- run: bundle exec appraisal rake
-```
-{% endraw %}
- |
-
-
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
deleted file mode 100644
index f380208e6fa0..000000000000
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
+++ /dev/null
@@ -1,291 +0,0 @@
----
-title: 从 Jenkins 迁移到 GitHub 操作
-intro: '{% data variables.product.prodname_actions %} 和 Jenkins 有多种相似之处,这使得迁移到 {% data variables.product.prodname_actions %} 相对简单。'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 简介
-
-Jenkins 和 {% data variables.product.prodname_actions %} 都允许您创建能自动构建、测试、发布、发行和部署代码的工作流程。 Jenkins 和 {% data variables.product.prodname_actions %} 的工作流程配置有一些相似之处:
-
-- Jenkins 使用 _Declarative Pelines_ 创建工作流程,这些工作流程类似于 {% data variables.product.prodname_actions %} 工作流程文件。
-- Jenkins 使用_阶段_运行步骤集合,而 {% data variables.product.prodname_actions %} 则使用作业来分组一个或多个步骤或单个命令。
-- Jenkins 和 {% data variables.product.prodname_actions %} 支持基于容器的构建。 更多信息请参阅“[创建 Docker 容器操作](/articles/creating-a-docker-container-action)”。
-- 步骤或任务可以重复使用并与社区共享。
-
-更多信息请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)”。
-
-### 主要差异
-
-- Jenkins 有两种类型的语法用来创建管道:Declarative Pipeline 和 Scripted Pipeline。 {% data variables.product.prodname_actions %} 使用 YAML 创建工作流程和配置文件。 更多信息请参阅“[GitHub 操作的工作流程语法](/actions/reference/workflow-syntax-for-github-actions)”。
-- Jenkins 部署通常是自托管的,用户在自己的数据中心维护服务器。 {% data variables.product.prodname_actions %} 通过托管自己可用于运行作业的运行器提供混合云方法,同时也支持自托管运行器。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。
-
-### 比较功能
-
-#### 分发版本
-
-Jenkins 可让您发送版本到单个构建代理,或者您可以在多个代理之间进行分发。 您也可以根据不同的属性(例如操作系统类型)对这些代理进行分类。
-
-同样, {% data variables.product.prodname_actions %} 可以向 {% data variables.product.prodname_dotcom %} 托管或自托管的运行器发送作业,您可以根据不同的属性使用标签对运行器分类。 下表比较了如何对 Jenkins 和 {% data variables.product.prodname_actions %} 实施分布式构建概念。
-
-| Jenkins | {% data variables.product.prodname_actions %} |
-| ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/getting-started-with-github-actions/core-concepts-for-github-actions#runner)
[`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) |
-
-#### 使用区段组织管道
-
-Jenkins 将其 Declarative Pipelines 分为多个区段。 同样,{% data variables.product.prodname_actions %} 也将其工作流程分成单独的部分。 下表比较了Jenkins 区段与 {% data variables.product.prodname_actions %} 工作流程。
-
-| Jenkins 指令 | {% data variables.product.prodname_actions %} |
-| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [`agent`](https://jenkins.io/doc/book/pipeline/syntax/#agent) | [`jobs..runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)
[`jobs..container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) |
-| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post) | |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) |
-| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) |
-
-
-### 使用指令
-
-Jenkins 使用指令来管理 _Declarative Pipelines_。 这些指令定义工作流程的特性及其执行方式。 下表演示这些指令如何映射到 {% data variables.product.prodname_actions %} 中的概念。
-
-| Jenkins 指令 | {% data variables.product.prodname_actions %} |
-| ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment) | [`jobs..env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)
[`jobs..steps.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
-| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`jobs..strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)
[`jobs..strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)
[`jobs..timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) |
-| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)
[`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs) |
-| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on)
[`on..types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes)
[on..
](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)
[on..paths
](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
-| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs..needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) |
-| [Jenkins cron syntax](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax) | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule) |
-| [`阶段,暂存`](https://jenkins.io/doc/book/pipeline/syntax/#stage) | [`jobs.`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_id)
[`jobs..name`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idname) |
-| [`tools`](https://jenkins.io/doc/book/pipeline/syntax/#tools) | [在 GitHub 托管的运行器上安装的软件](/actions/reference/software-installed-on-github-hosted-runners) |
-| [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) |
-| [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) |
-
-
-### 使用连续阶段
-
-#### 并行作业处理
-
-Jenkins 可以并行运行 `stages` 和 `steps`,而 {% data variables.product.prodname_actions %} 目前只能并行运行作业。
-
-| Jenkins Parallel | {% data variables.product.prodname_actions %} |
-| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs..strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
-
-#### 构建矩阵
-
-{% data variables.product.prodname_actions %} 和 Jenkins 都允许您使用构建矩阵来定义各种系统组合。
-
-| Jenkins | {% data variables.product.prodname_actions %} |
-| ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [`axis`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-axes) | [`strategy/matrix`](/actions/configuring-and-managing-workflows/configuring-a-workflow#configuring-a-build-matrix)
[`context`](/actions/reference/context-and-expression-syntax-for-github-actions) |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context) |
-| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) | |
-
-#### 使用步骤执行任务
-
-Jenkins 将 `steps` 组织在 `stages`。 每个步骤都可以是脚本、函数或命令等。 同样, {% data variables.product.prodname_actions %} 使用 `job` 来执行特定的 `steps` 组。
-
-| Jenkins 步骤 | {% data variables.product.prodname_actions %} |
-| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
-| [`script`](https://jenkins.io/doc/book/pipeline/syntax/#script) | [`jobs..steps`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsteps) |
-
-### 常见任务示例
-
-#### 计划与 `cron` 一起运行的管道
-
-
-
-
-Jenkins Pipeline
- |
-
-{% data variables.product.prodname_actions %} 工作流程
- |
-
-
-
-
- ```yaml
- pipeline {
- agent any
- triggers {
- cron('H/15 * * * 1-5')
- }
- }
- ```
-
- |
-
-
- ```yaml
- on:
- schedule:
- - cron: '*/15 * * * 1-5'
- ```
-
- |
-
-
-
-#### 配置管道中的环境变量
-
-
-
-
-Jenkins Pipeline
- |
-
-{% data variables.product.prodname_actions %} 工作流程
- |
-
-
-
-
- ```yaml
- pipeline {
- agent any
- environment {
- MAVEN_PATH = '/usr/local/maven'
- }
- }
- ```
-
- |
-
-
- ```yaml
- jobs:
- maven-build:
- env:
- MAVEN_PATH: '/usr/local/maven'
-
- ```
-
- |
-
-
-
-#### 从上游项目构建
-
-
-
-
-Jenkins Pipeline
- |
-
-{% data variables.product.prodname_actions %} 工作流程
- |
-
-
-
-
- ```yaml
- pipeline {
- triggers {
- upstream(
- upstreamProjects: 'job1,job2',
- threshold: hudson.model.Result.SUCCESS)
- }
- }
- }
-
- ```
-
- |
-
-
- ```yaml
- jobs:
- job1:
- job2:
- needs: job1
- job3:
- needs: [job1, job2]
-
- ```
-
- |
-
-
-
-#### 使用多个操作系统构建
-
-
-
-
-Jenkins Pipeline
- |
-
-{% data variables.product.prodname_actions %} 工作流程
- |
-
-
-
-
- ```yaml
-pipeline {
- agent none
- stages {
- stage('Run Tests') {
- parallel {
- stage('Test On MacOS') {
- agent { label "macos" }
- tools { nodejs "node-12" }
- steps {
- dir("scripts/myapp") {
- sh(script: "npm install -g bats")
- sh(script: "bats tests")
- }
- }
- }
- stage('Test On Linux') {
- agent { label "linux" }
- tools { nodejs "node-12" }
- steps {
- dir("script/myapp") {
- sh(script: "npm install -g bats")
- sh(script: "bats tests")
- }
- }
- }
- }
- }
- }
-}
- ```
-
- |
-
-
-{% raw %}
- ```yaml
- name: demo-workflow
- on:
- push:
- jobs:
- test:
- runs-on: ${{ matrix.os }}
- strategy:
- fail-fast: false
- matrix:
- os: [macos-latest, ubuntu-latest]
- steps:
- - uses: actions/checkout@v1
- - uses: actions/setup-node@v1
- with:
- node-version: 12
- - run: npm install -g bats
- - run: bats tests
- working-directory: scripts/myapp
- ```
-{% endraw %}
-
- |
-
-
diff --git a/translations/zh-CN/content/actions/publishing-packages-with-github-actions/about-packaging-with-github-actions.md b/translations/zh-CN/content/actions/publishing-packages-with-github-actions/about-packaging-with-github-actions.md
deleted file mode 100644
index 0dcf0c0e5345..000000000000
--- a/translations/zh-CN/content/actions/publishing-packages-with-github-actions/about-packaging-with-github-actions.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: 关于使用 GitHub 操作进行打包
-intro: '您可以在 {% data variables.product.prodname_actions %} 中设置工作流程生成包并将其上传到 {% data variables.product.prodname_registry %} 或其他包托管提供程序。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/about-packaging-with-github-actions
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于打包步骤
-
-打包步骤是持续集成或持续交付工作流程的常见部分。 构建并测试应用程序后,将以包的形式生成可运行或可部署的构件。 例如,Java 项目的连续集成工作流程可能运行 `mvn package` 来生成 JAR 文件。 或者,Node.js 应用程序的 CI 工作流程可能会创建 Docker 容器。
-
-根据您构建的应用程序类型,此包可本地下载以进行手动测试、可供用户下载或部署到暂存或生产环境。
-
-### 持续集成工作流程中的打包
-
-在持续集成工作流程结束时创建包有助于拉取请求的代码审查。 构建并测试代码后,打包步骤可以生成可运行或可部署的构件。 然后,您的工作流程可提取该构件并将其上传为工作流程的一部分。
-
-现在,在审查拉取请求时,您将能够查看工作流程运行并下载生成的构件。
-
-![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png)
-
-这将允许您在计算机上运行拉取请求中的代码,有助于调试或测试拉取请求。
-
-### 发布包的工作流程
-
-除了上传打包构件以测试持续集成工作流程之外, 您还可以创建工作流程来构建项目并发布包到软件包注册表。
-
-* **将包发布到 {% data variables.product.prodname_registry %}**
- {% data variables.product.prodname_registry %} 可以充当多类软件包的软件包托管服务。 您可以选择与所有 {% data variables.product.prodname_dotcom %} 共享您的软件包,或者与合作者或组织共享私有软件包。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/about-github-packages)”。
-
- 每次推送到主分支,您可能想将软件包发布到 {% data variables.product.prodname_registry %}。 这可让项目开发者始终能够通过从 {% data variables.product.prodname_registry %} 安装,很容易地运行和测试主版本中的最新构建版本。
-
-* **将软件包发布到软件包注册表** 对于许多项目,每当发布项目的新版本时,都会执行发布到软件包注册表。 例如,生成 JAR 文件的项目可能会将新版本上传到 Maven Central 仓库。 或者,.NET 项目可能会生成一个微件包并上传到 Nuget Gallery。
-
- 您可以创建一个工作流程来自动执行此操作,在每次创建版本时将软件包发布到软件包注册表。 更多信息请参阅“[创建发行版](/github/administering-a-repository/creating-releases)”。
-
-### 延伸阅读
-
-- "[发布 Node.js 包](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)"
diff --git a/translations/zh-CN/content/actions/publishing-packages-with-github-actions/index.md b/translations/zh-CN/content/actions/publishing-packages-with-github-actions/index.md
deleted file mode 100644
index 1fea544042ee..000000000000
--- a/translations/zh-CN/content/actions/publishing-packages-with-github-actions/index.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: 使用 GitHub 操作发布包
-shortTitle: 发布包
-intro: '创建包并将其发布到 {% data variables.product.prodname_registry %} 或其他包托管提供程序。'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% link_in_list /about-packaging-with-github-actions %}
diff --git a/translations/zh-CN/content/actions/reference/software-installed-on-github-hosted-runners.md b/translations/zh-CN/content/actions/reference/software-installed-on-github-hosted-runners.md
deleted file mode 100644
index e418a6345a85..000000000000
--- a/translations/zh-CN/content/actions/reference/software-installed-on-github-hosted-runners.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: 在 GitHub 托管的运行器上安装的软件
-intro: '本文链接到 {% data variables.product.prodname_dotcom %} 托管的虚拟环境中可用包和工具的参考。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /articles/software-in-virtual-environments-for-github-actions
- - /github/automating-your-workflow-with-github-actions/software-in-virtual-environments-for-github-actions
- - /github/automating-your-workflow-with-github-actions/software-installed-on-github-hosted-runners
- - /actions/automating-your-workflow-with-github-actions/software-installed-on-github-hosted-runners
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-{% data variables.product.prodname_dotcom %} 托管的运行器中包含的工具每周更新。 有关每个运行器操作系统包含的工具最新列表,请参阅以下链接:
-
-* [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/master/images/linux/Ubuntu2004-README.md)
-* [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/master/images/linux/Ubuntu1804-README.md)
-* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/master/images/linux/Ubuntu1604-README.md)
-* [Windows Server 2019](https://github.com/actions/virtual-environments/blob/master/images/win/Windows2019-Readme.md)
-* [Windows Server 2016](https://github.com/actions/virtual-environments/blob/master/images/win/Windows2016-Readme.md)
-* [MacOS 10.15](https://github.com/actions/virtual-environments/blob/master/images/macos/macos-10.15-Readme.md)
-
-{% data reusables.github-actions.ubuntu-runner-preview %}
-
-{% data variables.product.prodname_dotcom %} 托管的运行器除了上述参考中列出的包之外,还包括操作系统的默认内置工具。 例如,Ubuntu 和 macOS 运行器除了其他默认工具之外,还包括 `grep`、`find` 和 `which`。
-
-如果有您想要请求的工具,请在 [actions/virtual-environments](https://github.com/actions/virtual-environments) 打开一个议题。
diff --git a/translations/zh-CN/content/actions/reference/virtual-environments-for-github-hosted-runners.md b/translations/zh-CN/content/actions/reference/virtual-environments-for-github-hosted-runners.md
deleted file mode 100644
index 515852e746e0..000000000000
--- a/translations/zh-CN/content/actions/reference/virtual-environments-for-github-hosted-runners.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-title: GitHub 托管的运行器的虚拟环境
-intro: '{% data variables.product.prodname_dotcom %} 提供托管的虚拟机来运行工作流程。 虚拟机包含可供 {% data variables.product.prodname_actions %} 使用的工具、包和设置。'
-product: '{% data reusables.gated-features.actions %}'
-redirect_from:
- - /articles/virtual-environments-for-github-actions
- - /github/automating-your-workflow-with-github-actions/virtual-environments-for-github-actions
- - /github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners
- - /actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-### 关于 {% data variables.product.prodname_dotcom %} 托管的运行器
-
-{% data variables.product.prodname_dotcom %} 托管的运行器是由安装了 {% data variables.product.prodname_actions %} 运行器应用程序的 {% data variables.product.prodname_dotcom %} 托管的虚拟机。 {% data variables.product.prodname_dotcom %} 提供使用 Linux、Windows 和 macOS 操作系统的运行器。
-
-使用 {% data variables.product.prodname_dotcom %} 托管的运行器时,设备维护和升级由您负责。 您可以直接在虚拟机上或 Docker 容器中运行工作流程。
-
-可以为工作流程中的每项作业指定运行器类型。 工作流程中的每项作业都在全新的虚拟机实例中执行。 作业中的所有步骤在同一虚拟机实例中执行,让该作业中的操作使用文件系统共享信息。
-
-{% data reusables.github-actions.runner-app-open-source %}
-
-#### {% data variables.product.prodname_dotcom %} 托管的运行器的云主机
-
-{% data variables.product.prodname_dotcom %} 在 Microsoft Azure 中安装了 {% data variables.product.prodname_actions %} 运行器应用程序的 Standard_DS2_v2 虚拟机上托管 Linux 和 Windows 运行器。 {% data variables.product.prodname_dotcom %} 托管的运行器应用程序是 Azure Pipelines Agent 的复刻。 入站 ICMP 数据包被阻止用于所有 Azure 虚拟机,因此 ping 或 traceroute 命令可能无效。 有关 Standard_DS2_v2 机器资源的更多信息,请参阅 Microsoft Azure 文档中的“[Dv2 和 DSv2 系列](https://docs.microsoft.com/en-us/azure/virtual-machines/dv2-dsv2-series#dsv2-series)”。
-
-{% data variables.product.prodname_dotcom %} 使用 [MacStadium](https://www.macstadium.com/) 托管 macOS 运行器。
-
-#### {% data variables.product.prodname_dotcom %} 托管的运行器的管理权限
-
-Linux 和 macOS 虚拟机都使用无密码的 `sudo` 运行。 在需要比当前用户更多的权限才能执行命令或安装工具时,您可以使用无需提供密码的 `sudo`。 更多信息请参阅“[Sudo 手册](https://www.sudo.ws/man/1.8.27/sudo.man.html)”。
-
-Windows 虚拟机配置为以禁用了用户帐户控制 (UAC) 的管理员身份运行。 更多信息请参阅 Windows 文档中的“[用户帐户控制工作原理](https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works)”。
-
-### 支持的运行器和硬件资源
-
-每台虚拟机都有相同的硬件资源。
-
-- 2 核 CPU
-- 7 GB RAM 内存
-- 14 GB SSD 硬盘空间
-
-{% data reusables.github-actions.supported-github-runners %}
-
-{% data reusables.github-actions.ubuntu-runner-preview %}
-
-有关各运行器支持的软件、工具和包的列表,请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器上安装的软件](/actions/reference/software-installed-on-github-hosted-runners)”。
-
-您可以查看工作流程运行的日志,以查看用于作业的确切运行器环境, 以及连接到运行器上预安装工具的链接。 更多信息请参阅“[管理工作流程运行](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)”。
-
-
-#### {% data variables.product.prodname_dotcom %} 托管的运行器的 IP 地址
-
-{% note %}
-
-**注意:**如果使用 {% data variables.product.prodname_dotcom %} 组织或企业帐户的 IP 地址允许列表,则无法使用 {% data variables.product.prodname_dotcom %} 托管的运行器,而必须使用自托管的运行器。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。
-
-{% endnote %}
-
-Windows 和 Ubuntu 运行程序托管在 Azure 中,具有与 Azure 数据中心相同的 IP 地址范围。 目前,所有 Windows 和 Ubuntu {% data variables.product.prodname_dotcom %} 托管的运行器都在以下 Azure 地区:
-
-- 美国东部 (`eastus`)
-- 美国东部 2 (`eastus2`)
-- 美国西部 2 (`westus2`)
-- 美国中部 (`centralus`)
-- 美国中南部 (`southcentralus`)
-
-Microsoft 每周通过 JSON 文件更新 Azure IP 地址范围,您可以从 [Azure IP 范围和服务标签 - 公共云](https://www.microsoft.com/en-us/download/details.aspx?id=56519)网站下载该文件。 如果需要一个允许列表来阻止未经授权访问您的内部资源,您可以使用此 IP 地址范围。
-
-JSON 文件包含一个名为 `values` 的数组。 例如,在该数组内,您可以通过包含 `"AzureCloud.eastus2"` 的 `name` 和 `id` 的对象找到支持的 IP 地址。
-
-您可以在 `"addressPrefixes"` 对象中找到支持的 IP 地址范围。 这是 JSON 文件的精简示例。
-
-```json
-{
- "changeNumber": 84,
- "cloud": "Public",
- "values": [
- {
- "name": "AzureCloud.eastus2",
- "id": "AzureCloud.eastus2",
- "properties": {
- "changeNumber": 33,
- "region": "eastus2",
- "platform": "Azure",
- "systemService": "",
- "addressPrefixes": [
- "13.68.0.0/17",
- "13.77.64.0/18",
- "13.104.147.0/25",
- ...
- ]
- }
- }
- ]
-}
-```
-
-### {% data variables.product.prodname_dotcom %} 托管的运行器上的文件系统
-
-{% data variables.product.prodname_dotcom %} 在虚拟机上的特定目录中执行操作和 shell 命令。 虚拟机上的文件路径不是静态的。 使用环境变量 {% data variables.product.prodname_dotcom %} 提供 `home`、`workspace` 和 `workflow` 目录的构建文件路径。
-
-| 目录 | 环境变量 | 描述 |
-| --------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------- |
-| `home` | `HOME` | 包含用户相关的数据。 例如,此目录可能包含登录凭据。 |
-| `workspace` | `GITHUB_WORKSPACE` | 在此目录中执行操作和 shell 命令。 操作可以修改此目录的内容,后续操作可以访问这些修改。 |
-| `workflow/event.json` | `GITHUB_EVENT_PATH` | 触发工作流程的 web 挂钩事件的 `POST` 有效负载。 每当操作执行时,{% data variables.product.prodname_dotcom %} 都会重写此变量,以隔离操作之间的文件内容。 |
-
-有关 {% data variables.product.prodname_dotcom %} 为每个操作创建的环境变量列表,请参阅“[使用环境变量](/github/automating-your-workflow-with-github-actions/using-environment-variables)”。
-
-#### Docker 容器文件系统
-
-在 Docker 容器中运行的操作在 `/github` 路径下有静态目录。 但强烈建议使用默认环境变量在 Docker 容器中构建文件路径。
-
-{% data variables.product.prodname_dotcom %} 保留 `/github` 路径前缀,并为操作创建三个目录。
-
-- `/github/home`
-- `/github/workspace` - {% data reusables.repositories.action-root-user-required %}
-- `/github/workflow`
-
-{% if currentVersion == "free-pro-team@latest" %}
-
-### 延伸阅读
-- [[管理帐户的 {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)"
-
-{% endif %}
diff --git a/translations/zh-CN/content/admin/articles/README.md b/translations/zh-CN/content/admin/articles/README.md
deleted file mode 100644
index 249222e41fbc..000000000000
--- a/translations/zh-CN/content/admin/articles/README.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-redirect_from:
- - /enterprise/admin/articles/README
----
-# 隐藏的企业管理文章
-
-含 `hidden: true` 前页的企业管理文章位于此目录中。
-
-有关隐藏页面的更多信息,请参阅[`内容/自述文件`](../../README.md#hidden-pages)。
diff --git a/translations/zh-CN/content/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom.md b/translations/zh-CN/content/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom.md
deleted file mode 100644
index 315803417d96..000000000000
--- a/translations/zh-CN/content/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: 在 GitHub Enterprise 和 GitHub.com 之间配置统一贡献
-intro: '作为站点管理员,如果您启用了 {% data variables.product.prodname_github_connect %},则可以允许最终用户在他们的 {% data variables.product.prodname_dotcom_the_website %} 贡献图上查看 {% data variables.product.prodname_enterprise %} 工作的匿名贡献计数。'
-hidden: true
-redirect_from:
- - /enterprise/admin/articles/configuring-unified-contributions-between-github-enterprise-and-github-com
- - /enterprise/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom
-versions:
- enterprise-server: '*'
----
-
-
-在两个环境中启用 {% data variables.product.prodname_github_connect %} 和 {% data variables.product.prodname_unified_contributions %} 后,实例上的最终用户可以连接到他们的 {% data variables.product.prodname_dotcom_the_website %} 帐户,并将贡献计数从 {% data variables.product.prodname_enterprise %} 发送到 {% data variables.product.prodname_dotcom_the_website %}。 更多信息请参阅“[在 {% data variables.product.prodname_enterprise %} 和 {% data variables.product.prodname_dotcom_the_website %} 之间启用 {% data variables.product.prodname_unified_contributions %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com)”和“[将您的 {% data variables.product.prodname_ghe_server %} 贡献发送到您的 {% data variables.product.prodname_dotcom_the_website %} 个人资料](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile/)”。
-
-如果站点管理员禁用了该功能或开发者决定退出连接,则将删除 {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.prodname_enterprise %} 贡献计数。 如果开发者在禁用它们后重新连接其个人资料,则会恢复过去 90 天的贡献计数。
-
-1. 在管理 shell 中,启用 {% data variables.product.product_location_enterprise %} 上的 {% data variables.product.prodname_unified_contributions %} 配置:
- ```shell
- $ ghe-config 'app.github.dotcom-contributions-configurable' 'true'
- $ ghe-config-apply
- ```
-2. 返回到 {% data variables.product.prodname_enterprise %}。
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.business-settings %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-7. 在“Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}(用户可将贡献计数分享到 {% data variables.product.prodname_dotcom_the_website %})”下,使用下拉菜单并单击 **Enabled(已启用)**。
-8. 重定向到 {% data variables.product.prodname_dotcom_the_website %} 之后,要将 {% data variables.product.prodname_enterprise %} 贡献帐户写入所连接的用户帐户,您必须升级 {% data variables.product.prodname_github_app %}。 {% data variables.product.prodname_dotcom_the_website %} 组织的组织管理员必须批准使用 `external_contributions` 权限来升级 {% data variables.product.prodname_github_app %}。
-
diff --git a/translations/zh-CN/content/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile.md b/translations/zh-CN/content/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile.md
deleted file mode 100644
index 2066485a8c92..000000000000
--- a/translations/zh-CN/content/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 在您的 GitHub.com 个人资料中包含 GitHub Enterprise 贡献
-redirect_from:
- - /enterprise/admin/articles/including-github-enterprise-contributions-in-your-github-com-profile
- - /enterprise/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile
-intro: '您可以将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %},并使最终用户能够将贡献作为已关闭的早期使用计划的一部分从 {% data variables.product.product_location_enterprise %} 发送到他们的 {% data variables.product.prodname_dotcom_the_website %} 个人资料。'
-hidden: true
-versions:
- enterprise-server: '*'
----
-
-在您的 {% data variables.product.prodname_dotcom_the_website %} 个人资料中包含 {% data variables.product.prodname_enterprise %} 贡献是 {% data variables.product.prodname_enterprise %} 2.14 的已关闭早期使用计划的一部分。 更多信息请参阅“[在您的 {% data variables.product.prodname_dotcom_the_website %} 个人资料中包含 {% data variables.product.prodname_enterprise %}](/enterprise/2.14/admin/hidden/including-github-enterprise-contributions-in-your-github-com-profile/)”。
diff --git a/translations/zh-CN/content/admin/articles/using-github-task-runner.md b/translations/zh-CN/content/admin/articles/using-github-task-runner.md
deleted file mode 100644
index 6a7eceddf771..000000000000
--- a/translations/zh-CN/content/admin/articles/using-github-task-runner.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: 使用 GitHub Task Runner
-intro: '您可以将 {% data variables.product.prodname_dotcom %} Task Runner 用作 CI/CD 集成系统,作为已关闭的早期使用计划的一部分。 {% data variables.product.product_name %} Task Runner 允许您根据仓库中的配置文件从 {% data variables.product.prodname_github_app %} 自动构建、测试和部署代码。'
-hidden: true
-redirect_from:
- - /enterprise/admin/articles/using-github-task-runner
-versions:
- enterprise-server: '*'
----
-
-
-{% note %}
-
-**注:**在请求访问 {% data variables.product.prodname_dotcom %} Task Runner 前,您必须在 `EARLY ACCESS LINK` 中阅读并接受我们适用于 {% data variables.product.product_location_enterprise %} 的早期使用计划免责声明和责任限制。 此文档受这些条款管辖。
-
-{% endnote %}
-
-### 本文内容
-- [关于 {% data variables.product.prodname_dotcom %} Task Runner](#about-github-task-runner)
-- [下载 {% data variables.product.prodname_dotcom %} Task Runner 二进制文件](#downloading-the-github-task-runner-binary)
-- [在您的设备上创建 {% data variables.product.prodname_dotcom %} Task Runner {% data variables.product.prodname_github_app %}](#creating-the-github-task-runner-github-app-on-your-appliance)
-- [安装 {% data variables.product.prodname_dotcom %} Task Runner 应用程序](#installing-the-github-task-runner-app)
-- [为项目运行任务](#running-tasks-for-a-project)
-
-### 关于 {% data variables.product.prodname_dotcom %} Task Runner
-
-{% data variables.product.product_name %} Task Runner 负责运行由 Dispatcher 排队的任务,Dispatcher 是一个处理 web 挂钩推送事件和排队任务的独立服务。
-
-尽管 Dispatcher 已随 {% data variables.product.product_location_enterprise %} 提供,但您必须在设备上手动安装 {% data variables.product.product_name %} Task Runner。 要设置 {% data variables.product.product_name %} Task Runner,您必须下载 Runner 二进制文件,在设备上创建一个 {% data variables.product.prodname_github_app %},并设置服务器以与 Dispatcher 交互。
-
-### 下载 {% data variables.product.prodname_dotcom %} Task Runner 二进制文件
-
-您的 {% data variables.product.product_location_enterprise %} 上必须具有 {% data variables.product.product_name %} Task Runner 应用程序二进制文件。 要下载所选平台的二进制文件,请访问 `https://HOSTNAME/_dispatcher/downloads/`,将 `hostname` 替换为 {% data variables.product.product_location_enterprise %} 主机名或 IP 地址:
-
-使用 `chmod` 命令更改在命令行上使用 {% data variables.product.product_name %} Task Runner 的权限。
-
-{% mac %}
-
-```shell
-$ chmod +x task-runner_darwin_amd64
-```
-
-{% endmac %}
-
-{% windows %}
-
-```shell
-$ move task-runner_windows_amd64 task-runner_windows_amd64.exe
-```
-
-{% endwindows %}
-
-{% linux %}
-
-```shell
-$ chmod +x task-runner_linux_amd64
-```
-
-{% endlinux %}
-
-### 在您的设备上创建 {% data variables.product.prodname_dotcom %} Task Runner {% data variables.product.prodname_github_app %}
-
-1. 在当前目录中创建 `.task-runner.yaml` 配置文件。 您可以使用 `--config` 标志将文件移动到不同目录。
-
-```shell
-task-runner 设置
-```
-
-2. 输入 {% data variables.product.product_location_enterprise %} 的主机名。
-3. 输入使用专门权限配置的个人访问令牌。 更多信息请参阅[为命令行创建个人访问令牌](/articles/creating-a-personal-access-token-for-the-command-line/)。 如果您正在为您的帐户创建 {% data variables.product.prodname_github_app %},则可以使用 `user` 权限;或者,如果您正在为组织创建 {% data variables.product.prodname_github_app %},则可以使用 `admin:org` 权限。
-4. 为 {% data variables.product.prodname_github_app %} 输入一个名称,例如 `Octocat Task Runner`。
-5. 如果您正在为组织创建 {% data variables.product.prodname_github_app %},则输入组织的名称。
-6. 启动 Task Runner。
-
-```shell
-task-runner 启动
-```
-
-### 安装 {% data variables.product.prodname_dotcom %} Task Runner 应用程序
-
-1. 在任一页面的右上角,单击您的个人资料照片,然后单击 Settings。 ![用户栏中的 Settings 图标](/assets/images/help/images/userbar-account-settings.png)
-2. 在左侧边栏中,单击 **Developer settings**。 ![Developer settings 部分](/assets/images/help/images/developer_settings.png)
-3. 在左侧边栏中,单击 **{% data variables.product.prodname_dotcom %} Apps**。 ![GitHub Apps 部分](/assets/images/help/images/github_apps.png)
-4. 单击您想要安装的应用程序。
-5. 在左侧边栏中,单击 **Public page**。 ![Public page 部分](/assets/images/help/images/public-page-tab.png)
-6. 单击 **Install**。 ![GitHub 应用程序公共页面上的 Install 按钮](/assets/images/help/images/install-runner-public-page.png)
-7. 选择 **Only select repositories** 并键入要安装 {% data variables.product.prodname_dotcom %} Task Runner 的仓库名称。 ![选择要安装到的仓库](/assets/images/help/images/repositories-install-task-runner.png)
-8. 单击 **Install**。 ![GitHub 应用程序安装页面上的 Install 按钮](/assets/images/help/images/install-runner-installation-page.png)
-9. 导航到安装应用程序的仓库。
-10. 创建一个 `github/tasks.gf` 文件,类似于:
-
- ```
-task "my task" {
-command = "command-to-run"
-runnerType = "Shell"
-env = {
- FOO="bar",
- BAR="baz"
-}
-}
- ```
-12. 打开拉取请求以将文件添加到仓库。
-13. 推送更改以查看 CI 任务是否已运行。
-
-### 为项目运行任务
-
-创建拉取请求后,{% data variables.product.prodname_github_app %} 会将事件推送到 Dispatcher,其中任务会排队发送到 {% data variables.product.prodname_dotcom %} Task Runner。 {% data variables.product.prodname_dotcom %} Task Runner 首先接收和执行任务,然后将它们报告给 Dispatcher,之后 Dispatcher 将使用结果更新拉取请求。
-
-![拉取请求 CI 测试结果](/assets/images/help/images/task-results.png)
diff --git a/translations/zh-CN/content/admin/clustering/about-cluster-nodes.md b/translations/zh-CN/content/admin/clustering/about-cluster-nodes.md
deleted file mode 100644
index a01a230719d9..000000000000
--- a/translations/zh-CN/content/admin/clustering/about-cluster-nodes.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: 关于集群节点
-intro: '*节点* 是在集群里运行的 {% data variables.product.prodname_ghe_server %} 实例。 每个节点都运行一组服务,这些服务将提供给集群,最终提供给用户。'
-redirect_from:
- - /enterprise/admin/clustering/about-cluster-nodes
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_clustering.clustering-requires-https %}
-
-### 最低硬件建议
-每个节点都必须具有根卷以及单独的数据卷。 这些是最低限度的建议。 根据您的使用情况(例如用户活动和选定的集成),可能需要更多资源。
-
-| 服务 | 需要的最小内存 | 需要的最小数据卷可用空间 |
-|:----------------------------------------------------------------------------:|:-------:|:------------:|
-| `job-server`,
`memcache-server`,
`web-server` | 14 GB | 1 GB |
-| `consul-server`,
`mysql-server`,
`redis-server` | 14 GB | 10 GB |
-| `git-server`,
`metrics-server`,
`pages-server`,
`storage-server` | 7 GB | 10 GB |
-| `elasticsearch-server` | 14 GB | 10 GB |
-
-### 集群需要的服务
-为获得足够的冗余,请使用下面列出的最少节点来运行每个服务。
-
-{% tip %}
-
-**注:**组织对可扩展性的需求取决于多种因素,包括仓库的大小和数量、用户数量以及总体利用率。
-
-{% endtip %}
-
-| 服务 | 需要的最少节点 |
-|:---------------------------------------------------------------------------:|:-------:|
-| `job-server`,
`memcache-server`,
`metrics-server`,
`web-server` | 2 |
-| `mysql-server`,
`redis-server` | 2 |
-| `consul-server` | 3 |
-| `git-server`,
`pages-server`,
`storage-server` | 3 |
-| `elasticsearch-server` | 3 |
-
-### 集群设计建议
-
-集群允许组成 {% data variables.product.prodname_ghe_server %} 的服务彼此独立地进行扩展。 这种灵活性可用于设计和实现适合具有不同可扩展性要求的组织的集群。 例如,某些组织可能需要更多的存储吞吐量来进行大量或频繁的获取,但 Web 服务器的利用率可能相对较低。 其他组织可能具有较高的性能和较少的存储资源,但需要许多节点来运行 `pages-server` 或 `elasticsearch-server`。 可以实现许多不同的组合。 与您的客户代表合作,确定满足您特定需求的最佳集群配置。
-
-- 在独立硬件上扩展冗余节点。 如果共享 CPU、内存或存储设备,则会降低性能并引发单点故障。 此外,共享网络组件还会降低吞吐量并增加在发生中断时丢失连接的风险。
-- 使用快速存储。 通常经过优化存储区域网络 (SAN),可实现最大的空间利用率、可用性和容错能力,而不是绝对的吞吐量。 {% data variables.product.prodname_ghe_server %} 集群提供冗余和可用性,可在最快的可用存储上发挥最佳性能。 建议使用本地 SSD 存储。
-- 建立对您的组织有意义的节点层。 配置示例:
- - 具有两个节点和以下服务的前端层:
- - `web-server`
- - `jobs-server`
- - `memcache-server`
- - 具有三个节点和以下服务的数据库层:
- - `consul-server`
- - `mysql-server`
- - `redis-server`
- - 具有三个节点和以下服务的搜索层:
- - `elasticsearch-server`
- - 具有三个节点和以下服务的存储层:
- - `git-server`
- - `pages-server`
- - `storage-server`
- - `metrics-server`
-
-#### 示例集群图
-{% note %}
-
-**注:这只是一个示例。**您组织的最佳集群设计将取决于您的独特需求。 与您的专业代表或 {% data variables.contact.contact_enterprise_sales %} 探讨,以便我们能帮您确定最佳集群配置。
-
-{% endnote %}
-
-
diff --git a/translations/zh-CN/content/admin/clustering/about-clustering.md b/translations/zh-CN/content/admin/clustering/about-clustering.md
deleted file mode 100644
index 82c459828ba9..000000000000
--- a/translations/zh-CN/content/admin/clustering/about-clustering.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: 关于集群
-intro: '{% data variables.product.prodname_ghe_server %} 集群允许组成 {% data variables.product.prodname_ghe_server %} 的服务跨多个节点进行扩展。'
-redirect_from:
- - /enterprise/admin/clustering/clustering-overview/
- - /enterprise/admin/clustering/about-clustering
-versions:
- enterprise-server: '*'
----
-
-### 集群架构
-
-{% data variables.product.prodname_ghe_server %} 由一组服务组成。 在集群中,这些服务跨多个节点运行,请求在它们之间进行负载均衡。 更改会与冗余副本一起自动存储在到单独的节点上。 大多数服务与相同服务的其他实例是对等的。 这种情况的例外是 `mysql-server` 和 `redis-server` 服务。 它们使用具有一个或多个_副本_节点的单个_主_节点来操作。
-
-详细了解[集群所需的服务](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-cluster-nodes#services-required-for-clustering)。
-
-### 集群是否适合我的组织?
-
-{% data reusables.enterprise_clustering.clustering-scalability %} 但是,设置冗余和可扩展的集群可能很复杂,需要仔细规划。 在安装、灾难恢复场景和升级期间,需要计划这种额外的复杂性。
-
-{% data variables.product.prodname_ghe_server %} 要求节点之间保持较低的延迟,不适用于跨地理位置的冗余。
-
-集群提供了冗余功能,但不适用于替换高可用性配置。 更多信息请参阅[高可用性配置](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability)。 主设备/辅助设备故障切换配置远比集群简单,可以满足许多组织的需求。 更多信息请参阅[集群与高可用性之间的差异](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/)。
-
-### 如何获得集群?
-
-集群针对特定扩展情况而设计,并不一定适用于每个组织。 如果想要考虑集群,请联系您的专业代表或 {% data variables.contact.contact_enterprise_sales %}。
diff --git a/translations/zh-CN/content/admin/clustering/cluster-network-configuration.md b/translations/zh-CN/content/admin/clustering/cluster-network-configuration.md
deleted file mode 100644
index 5fd36f4fad92..000000000000
--- a/translations/zh-CN/content/admin/clustering/cluster-network-configuration.md
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: 群集网络配置
-intro: '{% data variables.product.prodname_ghe_server %} 集群依靠正确的 DNS 名称解析、负载均衡以及节点之间的通信来正常运行。'
-redirect_from:
- - /enterprise/admin/clustering/network-configuration
- - /enterprise/admin/clustering/cluster-network-configuration
-versions:
- enterprise-server: '*'
----
-
-### 网络考虑因素
-
-对于集群而言,最简单的网络设计是将节点置于单个 LAN 上。 如果冗余集群必须跨越子网,则子网之间应该提供适当的路由,延迟应短于 1 毫秒。
-
-#### 最终用户的应用程序端口
-
-应用程序端口为最终用户提供 Web 应用程序和 Git 访问。
-
-| 端口 | 描述 | 加密 |
-|:-------- |:-------------------------- |:----------------------------- |
-| 22/TCP | 通过 SSH 访问 Git | 是 |
-| 25/TCP | SMTP | 需要 STARTTLS |
-| 80/TCP | HTTP | 否
(启用 SSL 时,此端口重定向到 HTTPS) |
-| 443/TCP | HTTPS | 是 |
-| 9418/TCP | 简单的 Git 协议端口
(在私有模式下禁用) | 否 |
-
-#### 管理端口
-
-最终用户在使用基本应用程序时不需要管理端口。
-
-| 端口 | Description | 加密 |
-|:-------- |:------------------------ |:----------------------------- |
-| ICMP | ICMP Ping | 否 |
-| 122/TCP | 管理 SSH | 是 |
-| 161/UDP | SNMP | 否 |
-| 8080/TCP | Management Console HTTP | 否
(启用 SSL 时,此端口重定向到 HTTPS) |
-| 8443/TCP | Management Console HTTPS | 是 |
-
-#### 集群通信端口
-
-如果节点之间存在网络级防火墙,则需要访问这些端口。 节点之间的通信未加密。 这些端口不应从外部访问。
-
-| 端口 | 描述 |
-|:--------- |:-------------- |
-| 1336/TCP | 内部 API |
-| 3033/TCP | 内部 SVN 访问 |
-| 3037/TCP | 内部 SVN 访问 |
-| 3306/TCP | MySQL |
-| 4486/TCP | 管理者访问 |
-| 5115/TCP | 存储后端 |
-| 5208/TCP | 内部 SVN 访问 |
-| 6379/TCP | Redis |
-| 8001/TCP | Grafana |
-| 8090/TCP | 内部 GPG 访问 |
-| 8149/TCP | GitRPC 文件服务器访问 |
-| 8300/TCP | Consul |
-| 8301/TCP | Consul |
-| 8302/TCP | Consul |
-| 9000/TCP | Git Daemon |
-| 9102/TCP | 页面文件服务器 |
-| 9105/TCP | LFS 服务器 |
-| 9200/TCP | Elasticsearch |
-| 9203/TCP | 语义代码服务 |
-| 9300/TCP | Elasticsearch |
-| 11211/TCP | Memcache |
-| 161/UDP | SNMP |
-| 8125/UDP | Statsd |
-| 8301/UDP | Consul |
-| 8302/UDP | Consul |
-| 25827/UDP | Collectd |
-
-
-### 配置负载均衡器
-
- 我们建议使用基于 TCP 的外部负载均衡器,它支持 PROXY 协议来跨节点分配流量。 请考虑以下负载均衡器配置:
-
- - 应将 TCP 端口(如下所示)转发到运行 `web-server` 服务的节点。 这些是提供外部客户端请求的唯一节点。
- - 不应启用粘性会话。
-
-{% data reusables.enterprise_installation.terminating-tls %}
-
-### 处理客户端连接信息
-
-由于客户端与集群的连接来自负载均衡器,因此客户端 IP 地址可能会丢失。 要正确捕获客户端连接信息,需要考虑其他因素。
-
-{% data reusables.enterprise_clustering.proxy_preference %}
-
-{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
-
-#### 在 {% data variables.product.prodname_ghe_server %} 上启用 PROXY 支持
-
-我们强烈建议您为实例和负载均衡器启用 PROXY 支持。
-
- - 对于您的实例,请使用以下命令:
- ```shell
- $ ghe-config 'loadbalancer.proxy-protocol' 'true' && ghe-cluster-config-apply
- ```
- - 对于负载均衡器,请使用供应商提供的说明。
-
- {% data reusables.enterprise_clustering.proxy_protocol_ports %}
-
-#### 在 {% data variables.product.prodname_ghe_server %} 上启用 X-Forwarded-For 支持
-
-{% data reusables.enterprise_clustering.x-forwarded-for %}
-
-要启用 `X-Fowarded-For` 标头,请使用以下命令:
-
-```shell
-$ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
-```
-
-{% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
-
-#### 配置状态检查
-如果预配置的检查在该节点上失败,则状态检查允许负载均衡器停止向未响应的节点发送流量。 如果集群节点出现故障,则与冗余节点配对的状态检查可提供高可用性。
-
-{% data reusables.enterprise_clustering.health_checks %}
-{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
-
-### DNS 要求
-
-{% data reusables.enterprise_clustering.load_balancer_dns %}
diff --git a/translations/zh-CN/content/admin/clustering/differences-between-clustering-and-high-availability-ha.md b/translations/zh-CN/content/admin/clustering/differences-between-clustering-and-high-availability-ha.md
deleted file mode 100644
index 1916e8b1a3d3..000000000000
--- a/translations/zh-CN/content/admin/clustering/differences-between-clustering-and-high-availability-ha.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: 集群与高可用性 (HA) 之间的差异
-intro: '{% data variables.product.prodname_ghe_server %} 高可用性配置 (HA) 是一种可提供冗余功能的主设备/辅助设备故障切换配置,而集群则通过在多个节点之间分配读写负载来提供冗余和可扩展性。'
-redirect_from:
- - /enterprise/admin/clustering/differences-between-clustering-and-high-availability-ha
-versions:
- enterprise-server: '*'
----
-
-### 故障场景
-
-高可用性 (HA) 和集群都通过消除作为故障点的单个节点来提供冗余。 它们能够在这些场景中提供可用性:
-
-{% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %}
-
-### 可扩展性
-
-{% data reusables.enterprise_clustering.clustering-scalability %} 在 HA 中,设备的规模完全取决于主节点,并且负载不会分发到副本服务器。
-
-### 故障切换方法和配置方面的差异
-
-| 功能 | 故障切换配置 | 故障切换方法 |
-|:------ |:-------------------------- |:----------------------------------- |
-| 高可用性配置 | TTL 较低的 DNS 记录指向主设备或负载均衡器。 | 您必须在 DNS 故障切换和负载均衡器配置中手动升级副本设备。 |
-| 集群 | DNS 记录必须指向负载均衡器。 | 如果负载均衡器后面的节点发生故障,流量将自动发送到其他正常运行的节点。 |
-
-### 备份和灾难恢复
-
-HA 或集群都不应被视为常规备份的替代品。 更多信息请参阅“[在设备上配置备份](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)”。
-
-### 监视
-
-可用性功能,尤其是具有自动故障切换的功能(如集群)可以屏蔽故障,因为在发生故障时通常不会中断服务。 无论您使用的是 HA 还是集群,监视每个实例的状态都十分重要,这样您就可以了解何时发生了故障。 有关监视的更多信息,请参阅“[建议的警报阈值](/enterprise/{{ currentVersion }}/admin/guides/installation/recommended-alert-thresholds/)”和“[监视集群节点](/enterprise/{{ currentVersion}}/admin/guides/clustering/monitoring-cluster-nodes/)”。
-
-### 延伸阅读
-- 有关 {% data variables.product.prodname_ghe_server %} 集群的更多信息,请参阅“[关于集群](/enterprise/{{ currentVersion}}/admin/guides/clustering/about-clustering/)”。
-- 有关 HA 的更多信息,请参阅“[配置 {% data variables.product.prodname_ghe_server %} 以实现高可用性](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)”。
diff --git a/translations/zh-CN/content/admin/clustering/evacuating-a-cluster-node.md b/translations/zh-CN/content/admin/clustering/evacuating-a-cluster-node.md
deleted file mode 100644
index 50e1cb33d30a..000000000000
--- a/translations/zh-CN/content/admin/clustering/evacuating-a-cluster-node.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: 撤出集群节点
-intro: 您可以撤出集群节点上的数据服务。
-redirect_from:
- - /enterprise/admin/clustering/evacuating-a-cluster-node
-versions:
- enterprise-server: '*'
----
-
-如果数据服务集群中只有三个节点,则无法撤出节点,因为 `ghe-spoke` 没有其他位置可以进行复制。 如果您有四个或更多节点,则 `ghe-spoke ` 会将所有仓库移出已撤出的节点。
-
-如果您正在使具有任何数据服务(如 git、页面或存储)的某个节点离线,请在使节点离线之前撤出每个节点。
-
-1. 用 `ghe-config` 命令查找节点的 `uuid`。
-
- ```
- $ ghe-config cluster._hostname_.uuid
- ```
-
-2. 在复制数据时,您需要监视节点的状态。 理想情况下,在复制完成之前,不应使该节点离线。 要监视节点的状态,请运行以下任意命令:
-
- 对于 Git
- ```
- ghe-spokes evac-status
- ```
- 对于 {% data variables.product.prodname_pages %}
- ```
- echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y
- ```
- 对于存储
- ```
- ghe-storage evacuation-status
- ```
-
-3. 复制完成后,您可以撤出存储服务。 运行以下任意命令:
-
- 对于 Git
- ```
- ghe-spokes server evacuate git-server-
- ```
- 对于 {% data variables.product.prodname_pages %}
- ```
- ghe-dpages evacuate pages-server-
- ```
- 对于存储,请使节点离线
- ```
- ghe-storage offline storage-server-
- ```
- 然后撤出
- ```
- ghe-storage evacuate storage-server-
- ```
diff --git a/translations/zh-CN/content/admin/clustering/index.md b/translations/zh-CN/content/admin/clustering/index.md
deleted file mode 100644
index 7a580c6f7f52..000000000000
--- a/translations/zh-CN/content/admin/clustering/index.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 设置和管理 GitHub Enterprise Server 的集群
-shortTitle: 集群
-intro: '本指南介绍了如何与您的客户代表确定 {% data variables.product.prodname_enterprise %} 集群是否适合您的组织以及如何设置集群。'
-redirect_from:
- - /enterprise/admin/clustering
-versions:
- enterprise-server: '*'
----
-
-### 目录
-
-{% topic_link_in_list /overview %}
- {% link_in_list /about-clustering %}
- {% link_in_list /differences-between-clustering-and-high-availability-ha %}
-{% topic_link_in_list /setting-up-the-cluster-instances %}
- {% link_in_list /about-cluster-nodes %}
- {% link_in_list /cluster-network-configuration %}
- {% link_in_list /initializing-the-cluster %}
-{% topic_link_in_list /managing-a-github-enterprise-server-cluster %}
- {% link_in_list /upgrading-a-cluster %}
- {% link_in_list /replacing-a-cluster-node %}
- {% link_in_list /evacuating-a-cluster-node %}
- {% link_in_list /monitoring-cluster-nodes %}
diff --git a/translations/zh-CN/content/admin/clustering/initializing-the-cluster.md b/translations/zh-CN/content/admin/clustering/initializing-the-cluster.md
deleted file mode 100644
index 8e10cb3b39fb..000000000000
--- a/translations/zh-CN/content/admin/clustering/initializing-the-cluster.md
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: 初始化集群
-intro: '{% data variables.product.prodname_ghe_server %} 集群必须使用许可进行设置,并使用管理 shell (SSH) 进行初始化。'
-redirect_from:
- - /enterprise/admin/clustering/initializing-the-cluster
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_clustering.clustering-requires-https %}
-
-### 安装 {% data variables.product.prodname_ghe_server %}
-
-1. 在每个集群节点上,提供并安装 {% data variables.product.prodname_ghe_server %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。
-2. 使用管理 shell 或 DHCP,**仅**配置每个节点的 IP 地址。 不要配置任何其他设置。
-
-### 配置第一个节点
-
-1. 连接到将在 `cluster.conf` 中被指定为 `mysql-master` 的节点。 更多信息请参阅“[关于集群配置文件](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)”。
-2. 在 Web 浏览器中,访问 `https://:8443/setup/`。
-{% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}
-{% data reusables.enterprise_installation.instance-will-restart-automatically %}
-
-### 初始化集群
-
-要初始化集群,您需要一个集群配置文件 (`cluster.conf`)。 更多信息请参阅“[关于集群配置文件](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)”。
-
-1. 从配置的第一个节点开始,运行 `ghe-cluster-config-init`。 如果集群配置文件中存在未配置的节点,此操作会初始化集群。
-2. 运行 `ghe-cluster-config-apply`。 这将验证 `cluster.conf` 文件,将配置应用于每个节点文件,并在每个节点上显示已配置的服务。
-
-要检查正在运行的集群的状态,使用 `ghe-cluster-status` 命令。
-
-### 关于集群配置文件
-
-集群配置文件 (`cluster.conf`) 会定义集群中的节点以及它们运行的服务。 更多信息请参阅“[关于集群节点](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-cluster-nodes)”。
-
-此示例 `cluster.conf` 定义了一个包含五个节点的集群。
-
- - 两个节点(称为 `ghe-app-node-\*`)运行负责响应客户端请求的 `web-server` 和 `job-server` 服务。
- - 三个节点(称为 `ghe-data-node-\*`)运行负责存储和检索 {% data variables.product.prodname_ghe_server %} 数据的服务。
-
-节点的名称可以是您选择的任何有效主机名。 名称被设置为每个节点的主机名,并且还将添加到每个节点上的 `/etc/hosts` 中,以便节点可以在本地相互解析。
-
-通过 `mysql-server` 和 `mysql-master` 指定您配置为 MySQL master 的第一个集群节点。
-
-```
-[cluster]
- mysql-master = ghe-data-node-1
- redis-master = ghe-data-node-1
- primary-datacenter = default
-[cluster "ghe-app-node-1"]
- hostname = ghe-app-node-1
- ipv4 = 192.168.0.2
- # ipv6 = fd12:3456:789a:1::2
- web-server = true
- job-server = true
-[cluster "ghe-app-node-2"]
- hostname = ghe-app-node-2
- ipv4 = 192.168.0.3
- # ipv6 = fd12:3456:789a:1::3
- web-server = true
- job-server = true
-[cluster "ghe-data-node-1"]
- hostname = ghe-data-node-1
- ipv4 = 192.168.0.4
- # ipv6 = fd12:3456:789a:1::4
- consul-server = true
- consul-datacenter = default
- git-server = true
- pages-server = true
- mysql-server = true
- elasticsearch-server = true
- redis-server = true
- memcache-server = true
- metrics-server = true
- storage-server = true
-[cluster "ghe-data-node-2"]
- hostname = ghe-data-node-2
- ipv4 = 192.168.0.5
- # ipv6 = fd12:3456:789a:1::5
- consul-server = true
- consul-datacenter = default
- git-server = true
- pages-server = true
- mysql-server = true
- elasticsearch-server = true
- redis-server = true
- memcache-server = true
- metrics-server = true
- storage-server = true
-[cluster "ghe-data-node-3"]
- hostname = ghe-data-node-3
- ipv4 = 192.168.0.6
- # ipv6 = fd12:3456:789a:1::6
- consul-server = true
- consul-datacenter = default
- git-server = true
- pages-server = true
- mysql-server = true
- elasticsearch-server = true
- redis-server = true
- memcache-server = true
- metrics-server = true
- storage-server = true
-```
-
-在配置的第一个节点上创建文件 `/data/user/common/cluster.conf`。 例如,使用 `vim`:
-
- ```shell
- ghe-data-node-1:~$ sudo vim /data/user/common/cluster.conf
- ```
-
diff --git a/translations/zh-CN/content/admin/clustering/managing-a-github-enterprise-server-cluster.md b/translations/zh-CN/content/admin/clustering/managing-a-github-enterprise-server-cluster.md
deleted file mode 100644
index 946b427f13b5..000000000000
--- a/translations/zh-CN/content/admin/clustering/managing-a-github-enterprise-server-cluster.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 管理 GitHub Enterprise Server 集群
-intro: '为 {% data variables.product.prodname_ghe_server %} 集群规划维护操作,例如升级、增加容量和替换故障节点。'
-redirect_from:
- - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster/
- - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/clustering/monitoring-cluster-nodes.md b/translations/zh-CN/content/admin/clustering/monitoring-cluster-nodes.md
deleted file mode 100644
index 77e7040949df..000000000000
--- a/translations/zh-CN/content/admin/clustering/monitoring-cluster-nodes.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-title: 监视集群节点
-intro: '{% data variables.product.prodname_ghe_server %} 集群由分布在两个或多个节点上的冗余服务组成。 如果单个服务或整个节点将要发生故障,这种情况不应立即展示给集群的用户。 但是,由于性能和冗余受到影响,因此监视 {% data variables.product.prodname_ghe_server %} 集群的状态非常重要。'
-redirect_from:
- - /enterprise/admin/clustering/monitoring-cluster-nodes
-versions:
- enterprise-server: '*'
----
-
-### 手动检查集群状态
-
-{% data variables.product.prodname_ghe_server %} 有一个内置的命令行实用程序,用于监视集群的状态。 在管理 shell 中,运行 `ghe-cluster-status` 命令会对每个节点执行一系列状态检查,包括验证连接和服务状态。 输出会显示所有测试结果,包括文本 `ok` 或 `error`。 例如,要仅显示失败的测试,请运行:
-
-```shell
-admin@ghe-data-node-0:~$ ghe-cluster-status | grep error
-> mysql-replication ghe-data-node-0: error Stopped
-> mysql cluster: error
-```
-{% note %}
-
-**注:**如果没有失败的测试,则此命令不会产生任何输出。 这表明集群的状态是健康的。
-
-{% endnote %}
-
-### 使用 Nagios 监视集群状态
-
-您可以配置 [Nagios](https://www.nagios.org/) 来监视 {% data variables.product.prodname_ghe_server %}。 除了监视每个集群节点的基本连接以外,还可以通过将 Nagios 配置为使用 `ghe-cluster-status -n` 命令来检查集群状态。 这将以 Nagios 理解的格式返回输出。
-
-#### 基本要求
-* 运行 Nagios 的 Linux 主机。
-* 对 {% data variables.product.prodname_ghe_server %} 集群的网络访问。
-
-#### 配置 Nagios 主机
-1. 使用空白密码生成 SSH 密钥。 Nagios 使用此密钥来对 {% data variables.product.prodname_ghe_server %} 集群进行身份验证。
- ```shell
- nagiosuser@nagios:~$ ssh-keygen -t rsa -b 4096
- > Generating public/private rsa key pair.
- > Enter file in which to save the key (/home/nagiosuser/.ssh/id_rsa):
- > Enter passphrase (empty for no passphrase): leave blank by pressing enter
- > Enter same passphrase again: press enter again
- > Your identification has been saved in /home/nagiosuser/.ssh/id_rsa.
- > Your public key has been saved in /home/nagiosuser/.ssh/id_rsa.pub.
- ```
- {% danger %}
-
- **安全警告:**如果授权完全访问主机,则没有密码的 SSH 密钥可能会构成安全风险。 将此密钥的授权限制为单个只读命令。
-
- {% enddanger %}
-2. 将私钥 (`id_rsa`) 复制到 `nagios` 主文件夹并设置适当的所有权。
- ```shell
- nagiosuser@nagios:~$ sudo cp .ssh/id_rsa /var/lib/nagios/.ssh/
- nagiosuser@nagios:~$ sudo chown nagios:nagios /var/lib/nagios/.ssh/id_rsa
- ```
-
-3. 要授权公钥*仅*运行 `ghe-cluster-status -n` 命令,请在 `/data/user/common/authorized_keys` 文件中使用 `command=` 前缀。 从任何节点上的管理 shell,修改此文件以添加在步骤 1 中生成的公钥。 例如:`command="/usr/local/bin/ghe-cluster-status -n" ssh-rsa AAAA....`
-
-4. 通过在修改了 `/data/user/common/authorized_keys` 文件的节点上运行 `ghe-cluster-config-apply`,验证配置并将其复制到集群中的每个节点。
-
- ```shell
- admin@ghe-data-node-0:~$ ghe-cluster-config-apply
- > Validating configuration
- > ...
- > Finished cluster configuration
- ```
-
-5. 要测试 Nagios 插件能否成功执行命令,请从 Nagios 主机以交互方式运行此命令。
- ```shell
- nagiosuser@nagios:~$ /usr/lib/nagios/plugins/check_by_ssh -l admin -p 122 -H hostname -C "ghe-cluster-status -n" -t 30
- > OK - No errors detected
- ```
-
-6. 在 Nagios 配置中创建命令定义。
-
- ###### 示例定义
-
- ```
- define command {
- command_name check_ssh_ghe_cluster
- command_line $USER1$/check_by_ssh -H $HOSTADDRESS$ -C "ghe-cluster-status -n" -l admin -p 122 -t 30
- }
- ```
-7. 将此命令添加到 {% data variables.product.prodname_ghe_server %} 集群中节点的服务定义。
-
-
- ###### 示例定义
-
- ```
- define host{
- use generic-host
- host_name ghe-data-node-0
- alias ghe-data-node-0
- address 10.11.17.180
- }
-
- define service{
- use generic-service
- host_name ghe-data-node-0
- service_description GitHub Cluster Status
- check_command check_ssh_ghe_cluster
- }
- ```
-
-将定义添加到 Nagios 后,将根据您的配置执行服务检查。 您应该能够在 Nagios Web 界面中看到新配置的服务。
-
-![Nagios 示例](/assets/images/enterprise/cluster/nagios-example.png)
diff --git a/translations/zh-CN/content/admin/clustering/overview.md b/translations/zh-CN/content/admin/clustering/overview.md
deleted file mode 100644
index 08369b0eb9ca..000000000000
--- a/translations/zh-CN/content/admin/clustering/overview.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 概览
-intro: 了解具有高可用性的集群和差异。
-mapTopic: true
-redirect_from:
- - /enterprise/admin/clustering/overview
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/clustering/replacing-a-cluster-node.md b/translations/zh-CN/content/admin/clustering/replacing-a-cluster-node.md
deleted file mode 100644
index a61bab8ac02c..000000000000
--- a/translations/zh-CN/content/admin/clustering/replacing-a-cluster-node.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 替换集群节点
-intro: '要替换 {% data variables.product.prodname_ghe_server %} 节点,必须在集群配置文件 (cluster.conf) 中将受影响的节点标记为离线,然后添加替换节点。 如果节点发生故障,或者添加具有更多资源的节点以提高性能,则可能需要执行此操作。'
-redirect_from:
- - /enterprise/admin/clustering/replacing-a-cluster-node
-versions:
- enterprise-server: '*'
----
-
-{% warning %}
-
-**警告:**替换节点必须使用先前未在集群中使用的主机名以避免冲突。
-
-{% endwarning %}
-
-### 替换功能节点
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-provision %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-admin-configure-ip %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-modify-cluster-conf %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-initialize-new-node %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-config-node %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-need-three-nodes %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-mark-offline %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-validate-config %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-replacement-name %}
-
-### 在紧急情况下替换节点
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-provision %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-admin-configure-ip %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-mark-offline %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-validate-config %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-modify-cluster-conf %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-replacement-name %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-initialize-new-node %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-config-node %}
-{% data reusables.enterprise_clustering.replacing-a-cluster-node-need-three-nodes %}
diff --git a/translations/zh-CN/content/admin/clustering/setting-up-the-cluster-instances.md b/translations/zh-CN/content/admin/clustering/setting-up-the-cluster-instances.md
deleted file mode 100644
index b1b69347c0f9..000000000000
--- a/translations/zh-CN/content/admin/clustering/setting-up-the-cluster-instances.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 设置集群实例
-intro: '{% data variables.product.prodname_ghe_server %} 集群需要设置多个实例并配置为运行 {% data variables.product.prodname_ghe_server %} 服务。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/clustering/setting-up-the-cluster-instances
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/clustering/upgrading-a-cluster.md b/translations/zh-CN/content/admin/clustering/upgrading-a-cluster.md
deleted file mode 100644
index c1608fdb708b..000000000000
--- a/translations/zh-CN/content/admin/clustering/upgrading-a-cluster.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: 升级集群
-intro: '使用管理 shell (SSH) 将 {% data variables.product.prodname_ghe_server %} 集群升级到最新版本。'
-redirect_from:
- - /enterprise/admin/clustering/upgrading-a-cluster
-versions:
- enterprise-server: '*'
----
-
-### 使用热补丁升级
-{% data reusables.enterprise_installation.hotpatching-explanation %} 热补丁安装脚本可在集群中的每个节点上安装热补丁,并按正确顺序重新启动服务以避免停机。
-
-1. 使用 [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme) 备份数据。
-2. 在任何节点的管理 shell 中,使用 `ghe-cluster-hotpatch` 命令安装最新的热补丁。 您可以为热补丁提供 URL,也可以手动下载该热补丁并指定本地文件名。
- ```shell
- $ ghe-cluster-hotpatch https://HOTPATCH-URL/FILENAME.hpkg
- ```
-
-### 使用升级包升级
-使用升级包将 {% data variables.product.prodname_ghe_server %} 集群升级到最新功能版本。 例如,您可以从 `2.11` 升级到 `2.13`。
-
-#### 准备升级
-
-1. 查看要升级到的版本的[集群网络配置](/enterprise/admin/guides/clustering/cluster-network-configuration),并根据需要更新配置。
-2. 使用 [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme) 备份数据。
-3. 为 {% data variables.product.prodname_ghe_server %} 集群的最终用户排定维护窗口,因为它在升级期间无法正常使用。 在群集群升级过程中,维护模式会阻止用户访问并防止数据更改。
-4. 在 [{% data variables.product.prodname_ghe_server %} 下载页面](https://enterprise.github.com/download)上,将 *.pkg* 升级文件的 URL 复制到剪贴板。
-5. 在任何节点的管理 shell 中,将 `ghe-cluster-each` 命令与 `curl` 结合使用,只需一步即可将发布包下载到每个节点。 使用您在上一步中复制的 URL 作为参数。
- ```shell
- $ ghe-cluster-each -- "cd /home/admin && curl -L -O https://PACKAGE-URL.pkg"
- > ghe-app-node-1: % Total % Received % Xferd Average Speed Time Time Time Current
- > ghe-app-node-1: Dload Upload Total Spent Left Speed
- > 100 496M 100 496M 0 0 24.2M 0 0:00:20 0:00:20 --:--:-- 27.4M
- > ghe-data-node-2: % Total % Received % Xferd Average Speed Time Time Time Current
- > ghe-data-node-2: Dload Upload Total Spent Left Speed
- > 100 496M 100 496M 0 0 21.3M 0 0:00:23 0:00:23 --:--:-- 25.8M
- > ghe-data-node-1: % Total % Received % Xferd Average Speed Time Time Time Current
- > ghe-data-node-1: Dload Upload Total Spent Left Speed
- > 100 496M 100 496M 0 0 19.7M 0 0:00:25 0:00:25 --:--:-- 25.6M
- > ghe-app-node-2: % Total % Received % Xferd Average Speed Time Time Time Current
- > ghe-app-node-2: Dload Upload Total Spent Left Speed
- > 100 496M 100 496M 0 0 19.8M 0 0:00:25 0:00:25 --:--:-- 17.6M
- > ghe-data-node-3: % Total % Received % Xferd Average Speed Time Time Time Current
- > ghe-data-node-3: Dload Upload Total Spent Left Speed
- > 100 496M 100 496M 0 0 19.7M 0 0:00:25 0:00:25 --:--:-- 25.5M
- ```
-6. 确定主 MySQL 节点,此节点在 `cluster.conf` 中定义为 `mysql-master = `。 此节点将最后升级。
-
-#### 升级集群节点
-
-1. 通过连接到任何集群节点的管理 shell 并运行 `ghe-cluster-maintenance -s`,根据排定的窗口启用维护模式。
-2. **除了主 MySQL 节点之外**,连接到每个 {% data variables.product.prodname_ghe_server %} 节点的管理 shell。 运行 `ghe-upgrade` 命令,提供在[准备升级](#preparing-to-upgrade)的步骤 4 中下载的包文件名:
- ```shell
- $ ghe-upgrade PACKAGE-FILENAME.pkg
- > *** verifying upgrade package signature...
- > 497MB 0:00:04 [ 117MB/s] [==========================================>] 100%
- > gpg: Signature made Fri 19 Feb 2016 02:33:50 PM UTC using RSA key ID 0D65D57A
- > gpg: checking the trustdb
- > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
- > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
- > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > "
- ```
-3. 升级过程将在完成后重启节点。 验证您可以在其重启后 `ping` 每个节点。
-4. 连接到主 MySQL 节点的管理 shell。 运行 `ghe-upgrade` 命令,提供在[准备升级](#preparing-to-upgrade)的步骤 4 中下载的包文件名:
- ```shell
- $ ghe-upgrade PACKAGE-FILENAME.pkg
- > *** verifying upgrade package signature...
- > 497MB 0:00:04 [ 117MB/s] [==========================================>] 100%
- > gpg: Signature made Fri 19 Feb 2016 02:33:50 PM UTC using RSA key ID 0D65D57A
- > gpg: checking the trustdb
- > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
- > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
- > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > "
- ```
-5. 升级过程将在完成后重启主 MySQL 节点。 验证您可以在其重启后 `ping` 每个节点。
-6. 通过运行 `ghe-cluster-maintenance -u`,从任何节点的管理 shell 退出维护模式。
diff --git a/translations/zh-CN/content/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/zh-CN/content/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
deleted file mode 100644
index c3dfb660da9c..000000000000
--- a/translations/zh-CN/content/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: 为 GitHub Enterprise Server 上易受攻击的依赖项启用安全警报
-intro: '您可以将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_ghe_cloud %},并为实例仓库中易受攻击的依赖项启用安全警报。'
-redirect_from:
- - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
- - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
-permissions: '{% data variables.product.prodname_ghe_server %} 的站点管理员(同时也是已连接 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者)可以为 {% data variables.product.prodname_ghe_server %} 上的漏洞依赖项启用安全警报。'
-versions:
- enterprise-server: '*'
----
-
-### 关于 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项的警报
-
-{% data reusables.repositories.tracks-vulnerabilities %} 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。
-
-您可以将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %},然后将漏洞数据同步到实例,并在包含易受攻击的依赖项的仓库中生成安全警报。
-
-将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %} 并为易受攻击的依赖项启用安全警报后,每个小时都会将漏洞数据从 {% data variables.product.prodname_dotcom_the_website %} 同步到您的实例一次。 您还可以随时选择手动同步漏洞数据。 代码和关于代码的信息不会从 {% data variables.product.product_location_enterprise %} 上传到 {% data variables.product.prodname_dotcom_the_website %}。
-
-当 {% data variables.product.product_location_enterprise %} 接收到有关漏洞的信息时,它将识别实例中使用受影响版本依赖项的仓库,并向这些仓库中具有管理员访问权限的所有者和人员发送安全警报。 您可以自定义接收安全警报的方式。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/#configuring-notifications-for-security-alerts)”。
-
-### 为 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项启用安全警报
-
-为 {% data variables.product.product_location_enterprise %} 上易受攻击的依赖项启用安全警报前,必须将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %}。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
-
-{% if currentVersion ver_gt "enterprise-server@2.20" %} 我们建议配置前几天的安全警报不发通知,以避免电子邮件过载。 几天后,您可以启用通知,像平常一样接收安全警报。{% endif %}
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-2. 在管理 shell 中,为 {% data variables.product.product_location_enterprise %} 上易受攻击的依赖项启用安全警报:
- ``` shell
-$ ghe-dep-graph-enable
-```
-3. 返回到 {% data variables.product.prodname_ghe_server %}。
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.github-connect-tab %}{% if currentVersion ver_gt "enterprise-server@2.20" %}
-5. 在“Repositories can be scanned for vulnerabilities(可扫描仓库漏洞)”下,使用下拉菜单,并选择 **Enabled without notifications(启用但不发通知)**。 (可选)要启用包含通知的警报,请选择 **Enabled with notifications(启用并发通知)**。{% else %}
-5. 在“Repositories can be scanned for vulnerabilities”下,使用下拉菜单,然后选择 **Enabled**。
-{% endif %}
- ![用于启用扫描仓库有无漏洞的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
-
-### 查看 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项
-
-您可以查看 {% data variables.product.product_location_enterprise %} 中的所有漏洞,然后手动同步 {% data variables.product.prodname_dotcom_the_website %} 中的漏洞数据,以更新列表。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-2. 在左侧边栏中,单击 **Vulnerabilities**。 ![站点管理员边栏中的 Vulnerabilities 选项卡](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
-3. 要同步漏洞数据,请单击 **Sync Vulnerabilities now**。 ![Sync vulnerabilities now 按钮](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
diff --git a/translations/zh-CN/content/admin/developer-workflow/about-pre-receive-hooks.md b/translations/zh-CN/content/admin/developer-workflow/about-pre-receive-hooks.md
deleted file mode 100644
index 953911b3dd66..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/about-pre-receive-hooks.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: 关于预接收挂钩
-intro: '*预接收挂钩*是在 {% data variables.product.prodname_ghe_server %} 设备上运行的脚本,可用于实施质量检查。'
-redirect_from:
- - /enterprise/admin/developer-workflow/about-pre-receive-hooks
-versions:
- enterprise-server: '*'
----
-
-当发生推送时,每个脚本都在隔离的环境中运行,并且可以对推送的内容执行检查。 如果 exit status 为 0,脚本将导致接受推送,如果 exit status 不为零,则会拒绝接受推送。
-
-### 使用场景
-使用预接收挂钩来满足业务规则、强制执行法规遵从性,并防止出现某些常见错误。
-
-如何使用预接收挂钩的示例:
-
-- 需要提交消息来遵循特定的模式或格式,例如包括有效的事件单号或超过一定长度。
-- 通过拒绝所有推送来锁定分支或仓库。
-- 通过阻止关键词、模式或文件类型来防止将敏感数据添加到仓库。
-- 防止 PR 作者合并他们自己的更改。
-
-### 对性能和工作流程的影响
-对开发者及其工作流程的影响可能很大,因此必须谨慎考虑。 基于业务需求并经过深思熟虑实施的预接收挂钩将为整个组织带来最大好处。
-
-预接收挂钩可能会对 {% data variables.product.product_location_enterprise %} 的性能产生意外影响,因此应谨慎实施和审查。
diff --git a/translations/zh-CN/content/admin/developer-workflow/about-protected-branches-and-required-status-checks.md b/translations/zh-CN/content/admin/developer-workflow/about-protected-branches-and-required-status-checks.md
deleted file mode 100644
index 2b5bcafe9fec..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/about-protected-branches-and-required-status-checks.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 关于受保护分支和必需状态检查
-intro: '受保护分支确保仓库的协作者无法对分支进行不可撤销的更改。 必需状态检查确保在协作者可以对受保护分支进行更改前,所有必需的 CI 测试都已通过。 属于组织的仓库内的分支可配置为只允许特定用户{% if currentVersion ver_gt "enterprise-server@2.18" %},{% else %}或{% endif %}团队{% if currentVersion ver_gt "enterprise-server@2.18" %}或应用{% endif %}推送到该分支。'
-redirect_from:
- - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks
-versions:
- enterprise-server: '*'
----
-
-*受保护分支*在仓库管理员选择保护的分支上阻止 Git 的多个功能。 受保护分支:
-
-* 无法被强制推送
-* 无法被删除
-* 在[必需状态检查](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks#enabling-required-status-checks)通过前,无法将更改合并到其中
-
-对仓库具有管理员权限的任何人始终能够推送到受保护分支。 如果启用*分支限制*,则只有被授予权限的用户{% if currentVersion ver_gt "enterprise-server@2.18" %},{% else %}或{% endif %}团队{% if currentVersion ver_gt "enterprise-server@2.18" %}或应用{% endif %}才能推送到受保护分支。 更多信息请参阅”[配置受保护分支和必需状态检查](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks)“。
-
-![限制的分支权限](/assets/images/help/repository/restrict-branch-users.png).
-
-{% tip %}
-
-**注:**如果选中“Include administrators(包括管理员)”,并且您对分支[启用了必需状态检查](/articles/enabling-required-status-checks),但状态检查失败,则即使是具有管理员权限的人员{% if currentVersion ver_gt "enterprise-server@2.18" %}和应用{% endif %},将更改推送到受保护分支的任何尝试也会失败。
-
-{% endtip %}
diff --git a/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-on-your-appliance.md b/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-on-your-appliance.md
deleted file mode 100644
index 56571972f3a2..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-on-your-appliance.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: 阻止您设备上的强制推送
-redirect_from:
- - /enterprise/admin/articles/blocking-force-pushes-on-your-appliance/
- - /enterprise/admin/developer-workflow/blocking-force-pushes-on-your-appliance
-intro: '任何站点管理员都可以阻止 {% data variables.product.prodname_ghe_server %} 设备上的所有强制推送 (git push --force)'
-versions:
- enterprise-server: '*'
----
-
-每个仓库都从其所属的用户帐户或组织的设置继承了默认强制推送设置。 同样,每个组织和用户帐户都会从整个设备的强制推送设置继承默认强制推送设置。 如果更改设备的强制推送设置,则会更改任何用户或组织拥有的所有仓库。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-4. 在“Force pushes(强制推送)”下,使用下拉菜单,然后单击 **Allow(允许)**、**Block(阻止)**或 **Block to the default branch(阻止到默认分支)**。 ![强制推送下拉菜单](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
-5. 可以视情况选择 **Enforce on all repositories**,这将覆盖强制推送的组织和仓库级别设置。
-
-### 延伸阅读
-
-- “[阻止对用户帐户或组织拥有的仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)”
-- “[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository)”
diff --git a/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-to-a-repository.md b/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-to-a-repository.md
deleted file mode 100644
index 69104ffe2155..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-to-a-repository.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: 阻止对仓库进行强制推送
-redirect_from:
- - /enterprise/admin/articles/blocking-force-pushes-to-a-repository/
- - /enterprise/admin/articles/block-force-pushes/
- - /enterprise/admin/developer-workflow/blocking-force-pushes-to-a-repository
-intro: 您可以阻止所有分支上的强制推送(“git push --force”)— 或者仅阻止仓库默认分支上的强制推送。
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_site_admin_settings.override-policy %}
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-4. 在 **Push and Pull(推送和拉取)**下,选择 **Block(阻止)**或 **Block to the default branch(阻止到默认分支)**。 ![阻止强制推送](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
-
-变更立即生效。 如果您以后改变主意,可以轻松重新允许强制推送。
-
-## 延伸阅读
-
-- “[阻止对用户帐户或组织拥有的仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)”
-- “[阻止设备上的强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance)”
diff --git a/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization.md b/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization.md
deleted file mode 100644
index 4a4f3e9feacf..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: 阻止对用户帐户或组织拥有的仓库进行强制推送
-redirect_from:
- - /enterprise/admin/articles/blocking-force-pushes-for-a-user-account/
- - /enterprise/admin/articles/blocking-force-pushes-for-an-organization/
- - /enterprise/admin/articles/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization/
- - /enterprise/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization
-intro: 您可以阻止所有分支上的强制推送(“git push --force”)或仅阻止用户帐户或组织拥有的仓库的默认分支上的强制推送。
-versions:
- enterprise-server: '*'
----
-
-仓库从它们所属的用户帐户或组织继承强制推送设置。 反过来,用户帐户和组织从整个设备的强制推送设置继承其强制推送设置。
-
-您可以通过配置用户帐户或组织的设置来覆盖默认的继承设置。
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.search-user-or-org %}
-{% data reusables.enterprise_site_admin_settings.click-user-or-org %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. 在“Force pushes”部分的“Repository default settings”下,选择
- - **Block** 来阻止对所有分支进行强制推送。
- - **Block to the default branch** 来仅阻止对默认分支进行强制推送。 ![阻止强制推送](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
-6. 可以视情况选择 **Enforce on all repositories** 来覆盖仓库特定的设置。 注意,这**不**会覆盖设备范围的策略。 ![阻止强制推送](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) 变更立即生效。 如果您以后改变主意,可以重新允许强制推送。
-
-### 延伸阅读
-
-- “[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository)”
-- “[阻止设备上的强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance)”
diff --git a/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes.md b/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes.md
deleted file mode 100644
index f37c83ab99c4..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/blocking-force-pushes.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 阻止强制推送
-intro: '您可以阻止 {% data variables.product.prodname_ghe_server %} 设备的所有仓库上、组织拥有的所有仓库上或特定仓库上的强制推送。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/developer-workflow/blocking-force-pushes
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/developer-workflow/configuring-protected-branches-and-required-status-checks.md b/translations/zh-CN/content/admin/developer-workflow/configuring-protected-branches-and-required-status-checks.md
deleted file mode 100644
index d519afe6cdbd..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/configuring-protected-branches-and-required-status-checks.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: 配置受保护分支和必需状态检查
-intro: 您可以启用受保护分支来限制分支操作,以及在分支合并到拉取请求中之前或在将本地分支上的提交推送到受保护远程分支之前强制执行必需状态检查。
-redirect_from:
- - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks
-versions:
- enterprise-server: '*'
----
-
-任何对仓库有管理员权限的人都可以启用分支限制。
-
-### 为仓库启用受保护分支
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.repository-branches %}
-{% data reusables.repositories.add-branch-protection-rules %}
-5. 单击 **Create(创建)**。
-
-### 必需状态检查的类型
-
-| 必需状态检查的类型 | 设置 | 合并要求 | 考虑因素 |
-| --------- | ------------------------------------------------------------------------------- | ---------------------------- | ----------------------------------------------------------------------------- |
-| **严格** | 选中 **Require branches to be up-to-date before merging(合并前需要分支保持最新状态)**复选框。 | 在合并之前,**必须**使用基础分支使分支保持最新状态。 | 这是必需状态检查的默认行为。 可能需要更多构建,因为在其他协作者将拉取请求合并到受保护基础分支后,您需要使头部分支保持最新状态。 |
-| **宽松** | **不**选中 **Require branches to be up-to-date before merging(合并前需要分支保持最新状态)**复选框。 | 在合并之前,**不**必使用基础分支使分支保持最新状态。 | 您将需要更少的构建,因为在其他协作者合并拉取请求后,您不需要使头部分支保持最新状态。 如果存在与基础分支不兼容的变更,则在合并分支后,状态检查可能会失败。 |
-| **已禁用** | **不**选中 **Require status checks to pass before merging(合并前需要状态检查通过)**复选框。 | 分支没有合并限制。 | 如果未启用必需状态检查,协作者可以随时合并分支,无论它是否使用基础分支保持最新状态。 这增加了不兼容变更的可能性。 |
-
-### 启用必需状态检查
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.repository-branches %}
-{% data reusables.repositories.add-branch-protection-rules %}
-5. 选中 **Require status checks to pass before merging(合并前必需状态检查通过)**。 ![必需状态检查选项](/assets/images/help/repository/required-status-checks.png)
-6. 从可用状态检查列表中,选择您想要设为必需的状态检查。 ![可用状态检查列表](/assets/images/help/repository/required-statuses-list.png)
-{% data reusables.repositories.include-administrators %}
-8. 视情况可以取消选中 **Require branches to be up to date before merging(在合并前要求分支保持最新状态)**。 如果选中,则可确保使用基础分支上的最新代码来测试分支。 ![宽松或严格的必需状态复选框](/assets/images/help/repository/protecting-branch-loose-status-new.png)
-9. (可选)选择 {% if currentVersion ver_gt "enterprise-server@2.18" %}**Restrict who can push to matching branches(限制谁可以推送到匹配的分支)**{% else %}**Restrict who can push to this branch(限制谁可以推送到此分支)**{% endif %}。 ![分支限制复选框]{% if currentVersion ver_gt "enterprise-server@2.18" %}(/assets/images/help/repository/restrict-branch.png){% else %}(/assets/images/help/repository/restrict-branch-push.png){% endif %}
-10. 搜索并选择将有权推送到受保护分支的人员{% if currentVersion ver_gt "enterprise-server@2.18" %}、{% else %}或{% endif %}团队{% if currentVersion ver_gt "enterprise-server@2.18" %}或应用{% endif %}。 ![分支限制搜索](/assets/images/help/repository/restrict-branch-search.png)
-11. 单击 **Create(创建)**。
-
-{% data reusables.repositories.required-status-merge-tip %}
diff --git a/translations/zh-CN/content/admin/developer-workflow/continuous-integration-using-jenkins.md b/translations/zh-CN/content/admin/developer-workflow/continuous-integration-using-jenkins.md
deleted file mode 100644
index 55832c4fe66c..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/continuous-integration-using-jenkins.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 使用 Jenkins 的持续集成
-intro: '当向 {% data variables.product.product_location_enterprise %} 中的仓库进行推送时,您可以在 Jenkins 服务器上自动触发构建作业。'
-redirect_from:
- - /enterprise/admin/developer-workflow/continuous-integration-using-jenkins
-versions:
- enterprise-server: '*'
----
-
-### 要求
-
-- 按照我们的白皮书“[使用 Jenkins 和 GitHub 实现 CI 的实用指南](https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/)”,逐步了解如何在向 {% data variables.product.product_location_enterprise %} 中的仓库进行推送时在 Jenkins 服务器上自动触发构建作业。
diff --git a/translations/zh-CN/content/admin/developer-workflow/creating-a-pre-receive-hook-environment.md b/translations/zh-CN/content/admin/developer-workflow/creating-a-pre-receive-hook-environment.md
deleted file mode 100644
index 3897e7ea48b4..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/creating-a-pre-receive-hook-environment.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: 创建预接收挂钩环境
-intro: 要执行预接收挂钩,请使用默认的预接收环境,或者创建自定义环境。
-redirect_from:
- - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-environment
-versions:
- enterprise-server: '*'
----
-
-{% data variables.product.prodname_ghe_server %} 的预接收环境是 Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot) 环境。 由于预接收挂钩会在每个推送事件上执行,因此它们应该快速且轻量化。 这类检查需要的环境通常极少。
-
-{% data variables.product.prodname_ghe_server %} 提供了一个默认环境,其中包括以下包:`awk`、`bash`、`coreutils`、`curl`、`find`、`gnupg`、`grep`、`jq`、`sed`。
-
-如果您具有此环境未满足的特定要求(例如对特定语言的支持),则可以创建并上传您自己的 64 位 Linux `chroot` 环境。
-
-### 使用 Docker 创建预接收挂钩环境
-
-您可以使用 Linux 容器管理工具来构建预接收挂钩环境。 此示例使用 [Alpine Linux](http://www.alpinelinux.org/) 和 [Docker](https://www.docker.com/)。
-
-{% data reusables.linux.ensure-docker %}
-2. 创建包含此信息的文件 `Dockerfile.alpine-3.3`:
-
- ```
- FROM gliderlabs/alpine:3.3
- RUN apk add --no-cache git bash
- ```
-3. 从包含 `Dockerfile.dev` 的工作目录中,构建一个镜像:
-
- ```shell
- $ docker build -f Dockerfile.alpine-3.3 -t pre-receive.alpine-3.3 .
- > Sending build context to Docker daemon 12.29 kB
- > Step 1 : FROM gliderlabs/alpine:3.3
- > ---> 8944964f99f4
- > Step 2 : RUN apk add --no-cache git bash
- > ---> Using cache
- > ---> 0250ab3be9c5
- > Successfully built 0250ab3be9c5
- ```
-4. 创建一个容器:
-
- ```shell
- $ docker create --name pre-receive.alpine-3.3 pre-receive.alpine-3.3 /bin/true
- ```
-5. 将 Docker 容器导出到 `gzip` 压缩的 `tar` 文件:
-
- ```shell
- $ docker export pre-receive.alpine-3.3 | gzip > alpine-3.3.tar.gz
- ```
-
- 此文件 `alpine-3.3.tar.gz` 已准备好上传到 {% data variables.product.prodname_ghe_server %} 设备。
-
-### 使用 chroot 创建预接收挂钩环境
-
-1. 创建 Linux `chroot` 环境。
-2. 创建 `chroot` 目录的 `gzip` 压缩 `tar` 文件:
- ```shell
- $ cd /path/to/chroot
- $ tar -czf /path/to/pre-receive-environment.tar.gz .
- ```
-
- {% note %}
-
- **注:**
- - 不要在 tar 存档中包含文件的主目录路径,如 `/path/to/chroot`。
- - `/bin/sh` 必须存在并且可执行,作为 chroot 环境的入口点。
- - 与传统的 chroot 不同,预接收挂钩的 chroot 环境不需要 `dev` 目录。
-
- {% endnote %}
-
-关于创建 chroot 环境的更多信息,请参阅 *Debian Wiki* 中的“[Chroot](https://wiki.debian.org/chroot)”、*Ubuntu 社区帮助 Wiki* 中的“[BasicChroot](https://help.ubuntu.com/community/BasicChroot)”,或者 *Alpine Linux Wiki* 中的“[在 chroot 中安装 Alpine Linux](http://wiki.alpinelinux.org/wiki/Installing_Alpine_Linux_in_a_chroot)”。
-
-### 在 {% data variables.product.prodname_ghe_server %} 上上传预接收挂钩环境
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.hooks-tab %}
-5. 单击 **Manage environments**。 ![管理环境](/assets/images/enterprise/site-admin-settings/manage-pre-receive-environments.png)
-6. 单击 **Add environment**。 ![添加环境](/assets/images/enterprise/site-admin-settings/add-pre-receive-environment.png)
-7. 在 **Environment name** 字段中输入所需的名称。 ![环境名称](/assets/images/enterprise/site-admin-settings/pre-receive-environment-name.png)
-8. 输入包含您的环境的 `* .tar.gz` 文件的 URL。 ![从 URL 上传环境](/assets/images/enterprise/site-admin-settings/upload-environment-from-url.png)
-9. 单击 **Add environment**。 ![Add environment 按钮](/assets/images/enterprise/site-admin-settings/add-environment-button.png)
-
-### 通过管理 shell 上传预接收挂钩环境
-1. 将包含您的环境的可读 `* .tar.gz` 文件上传到 web 主机并复制 URL 或通过 `scp` 将文件传送到 {% data variables.product.prodname_ghe_server %} 设备。 使用 `scp` 时,您可能需要调整 `* .tar.gz` 文件权限,以使该文件全局可读。
-1. 连接到管理 shell。
-2. 使用 `ghe-hook-env-create` 命令并输入所需的环境名称作为第一个参数,然后将包含环境的 `* .tar.gz` 文件的完整本地路径或 URL 作为第二个参数。
-
- ```shell
- admin@ghe-host:~$ ghe-hook-env-create AlpineTestEnv /home/admin/alpine-3.3.tar.gz
- > Pre-receive hook environment 'AlpineTestEnv' (2) has been created.
- ```
diff --git a/translations/zh-CN/content/admin/developer-workflow/creating-a-pre-receive-hook-script.md b/translations/zh-CN/content/admin/developer-workflow/creating-a-pre-receive-hook-script.md
deleted file mode 100644
index 35588a631bf7..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/creating-a-pre-receive-hook-script.md
+++ /dev/null
@@ -1,199 +0,0 @@
----
-title: 创建预接收挂钩脚本
-intro: 使用预接收挂钩脚本创建基于内容来接受或拒绝推送的要求。
-redirect_from:
- - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-script
-versions:
- enterprise-server: '*'
----
-
-您可以在 [`github/platform-samples` 仓库](https://github.com/github/platform-samples/tree/master/pre-receive-hooks)中查看 {% data variables.product.prodname_ghe_server %} 的预接收挂钩示例。
-
-### 编写预接收挂钩脚本
-预接收挂钩脚本在 {% data variables.product.prodname_ghe_server %} 设备上的预接收挂钩环境中执行。 创建预接收挂钩脚本时,请考虑可用的输入、输出、exit-status 和环境变量。
-
-#### 输入 (stdin)
-在推送发生之后以及在远程仓库上更新任何 ref 之前,`git-receive-pack` 进程会调用预接收挂钩脚本,其中要更新的每个 ref 使用一行标准输入:
-
-` SP SP LF`
-
-此字符串表示以下参数:
-
-| 参数 | 描述 |
-|:------------------- |:------------------------------------------------- |
-| `` | 存储在 `ref` 中的旧对象名称。
当您*创建*新的 `ref` 时,这等于 40 个零。 |
-| `` | 要存储在 `ref` 中的新对象名称。
当您*删除* `ref` 时,这等于 40 个零。 |
-| `` | `ref` 的全名。 |
-
-关于 `git-receive-pack` 的更多信息,请参阅 Git 文档中的“[git-receive-pack](https://git-scm.com/docs/git-receive-pack)”。 关于 `ref` 的更多信息,请参阅 *Pro Git* 中的“[Git 引用](https://git-scm.com/book/en/v2/Git-Internals-Git-References)”。
-
-#### 输出 (stdout)
-
-脚本输出 (`stdout`) 将传递回客户端,因此用户可以在命令行或用户界面中看到任意 `echo` 语句。
-
-#### Exit-status
-
-预接收脚本的 `exit-status` 决定是否接受推送。
-
-| Exit-status 值 | 操作 |
-|:-------------:|:------:|
-| 0 | 将接受推送。 |
-| 非零 | 将拒绝推送。 |
-
-#### 环境变量
-除了提供给 `stdin` 的值以外,还有一些其他变量可用于在 {% data variables.product.prodname_ghe_server %} 上运行的预接收挂钩脚本。
-
-| 变量 | 描述 |
-|:------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| $GITHUB_USER_LOGIN | 创建 `ref` 的用户 ID。 |
-| $GIT_DIR | 设备上远程仓库的路径。 |
-| $GITHUB_USER_IP | 执行推送的用户的 IP 地址。 |
-| $GITHUB_REPO_NAME | 正在更新的仓库的 `owner`/`repo` 格式的名称。 |
-| $GITHUB_PULL_REQUEST_AUTHOR_LOGIN | 在您的实例上打开的拉取请求的作者的用户 ID。 |
-| $GITHUB_REPO_PUBLIC | 一个布尔值,为 `true` 时表示公共仓库,为 `false` 时表示私有仓库。 |
-| $GITHUB_PUBLIC_KEY_FINGERPRINT | 用户的公钥指纹。 |
-| $GITHUB_PULL_REQUEST_HEAD | 格式中的字符串:`user:branch`,适用于 PR 的 HEAD。
示例:`octocat:fix-bug` |
-| $GITHUB_PULL_REQUEST_BASE | 格式中的字符串:`user:branch`,适用于 PR 的 BASE。
示例:`octocat:master` |
-| $GITHUB_VIA | 用于创建 ref 的方法。
**可选值:**
- `auto-merge deployment api`
- `blob edit`
- `branch merge api`
- `branches page delete button`
- `git refs create api`
- `git refs delete api`
- `git refs update api`
- `merge api`
- `pull request branch delete button`
- `pull request branch undo button`
- `pull request merge api`
- `pull request merge button`
- `pull request revert button`
- `releases delete button`
- `stafftools branch restore`
- `slumlord (#{sha})` |
-| $GIT_PUSH_OPTION_COUNT | 客户端发送的推送选项数。 关于推送选项的更多信息,请参阅 Git 文档中的“[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)”。 |
-| $GIT_PUSH_OPTION_N | 其中 N 是一个从 0 开始的整数,此变量包含客户端发送的推送选项字符串。 发送的第一个选项存储在 GIT_PUSH_OPTION_0 中,发送的第二个选项存储在 GIT_PUSH_OPTION_1 中,依此类推。 关于推送选项的更多信息,请参阅 Git 文档中的“[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)”。 |
-
-### 设置权限并将预接收挂钩推送到 {% data variables.product.prodname_ghe_server %}
-
-{% data variables.product.prodname_ghe_server %} 设备上的仓库中包含预接收挂钩脚本。 站点管理员必须考虑仓库权限,确保只有适当的用户才能访问。
-
-我们建议将挂钩合并到单个仓库。 如果统一的挂钩仓库是公共的,则可以使用 `README.md` 来解释策略强制实施。 此外,也可以通过拉取请求接受贡献。 但是,只能从默认分支添加预接收挂钩。 对于测试工作流程,应使用具有配置的仓库的分支。
-
-1. 对于 Mac 用户,确保脚本具有执行权限:
-
- ```shell
- $ sudo chmod +x SCRIPT_FILE.sh
- ```
- 对于 Windows 用户,确保脚本具有执行权限:
-
- ```shell
- git update-index --chmod=+x SCRIPT_FILE.sh
- ```
-
-2. 提交并推送到 {% data variables.product.prodname_ghe_server %} 实例上指定的预接收挂钩仓库。
-
- ```shell
- $ git commit -m "YOUR COMMIT MESSAGE"
- $ git push
- ```
-
-3. 在 {% data variables.product.prodname_ghe_server %} 实例上[创建预接收挂钩](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks)。
-
-### 在本地测试预接收脚本
-在 {% data variables.product.prodname_ghe_server %} 设备上创建或更新预接收挂钩脚本之前,您可以在本地对其进行测试。 一种方法是创建本地 Docker 环境以充当可以执行预接收挂钩的远程仓库。
-
-{% data reusables.linux.ensure-docker %}
-
-2. 创建一个名为 `Dockerfile.dev` 的文件,其中包含:
-
- ```
- FROM gliderlabs/alpine:3.3
- RUN \
- apk add --no-cache git openssh bash && \
- ssh-keygen -A && \
- sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \
- adduser git -D -G root -h /home/git -s /bin/bash && \
- passwd -d git && \
- su git -c "mkdir /home/git/.ssh && \
- ssh-keygen -t rsa -b 4096 -f /home/git/.ssh/id_rsa -P '' && \
- mv /home/git/.ssh/id_rsa.pub /home/git/.ssh/authorized_keys && \
- mkdir /home/git/test.git && \
- git --bare init /home/git/test.git"
-
- VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"]
- WORKDIR /home/git
-
- CMD ["/usr/sbin/sshd", "-D"]
- ```
-
-3. 创建一个名为 `always_reject.sh` 的测试预接收脚本。 此示例脚本将拒绝所有推送,这对于锁定仓库非常有用:
-
- ```
- #!/usr/bin/env bash
-
- echo "error: rejecting all pushes"
- exit 1
- ```
-
-4. 确保 `always_reject.sh` 脚本具有执行权限:
-
- ```shell
- $ chmod +x always_reject.sh
- ```
-
-5. 从包含 `Dockerfile.dev` 的目录中,构建一个镜像:
-
- ```shell
- $ docker build -f Dockerfile.dev -t pre-receive.dev .
- > Sending build context to Docker daemon 3.584 kB
- > Step 1 : FROM gliderlabs/alpine:3.3
- > ---> 8944964f99f4
- > Step 2 : RUN apk add --no-cache git openssh bash && ssh-keygen -A && sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && adduser git -D -G root -h /home/git -s /bin/bash && passwd -d git && su git -c "mkdir /home/git/.ssh && ssh-keygen -t rsa -b 4096 -f /home/git/.ssh/id_rsa -P ' && mv /home/git/.ssh/id_rsa.pub /home/git/.ssh/authorized_keys && mkdir /home/git/test.git && git --bare init /home/git/test.git"
- > ---> Running in e9d79ab3b92c
- > fetch http://alpine.gliderlabs.com/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
- > fetch http://alpine.gliderlabs.com/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
- ....truncated output....
- > OK: 34 MiB in 26 packages
- > ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
- > Password for git changed by root
- > Generating public/private rsa key pair.
- > Your identification has been saved in /home/git/.ssh/id_rsa.
- > Your public key has been saved in /home/git/.ssh/id_rsa.pub.
- ....truncated output....
- > Initialized empty Git repository in /home/git/test.git/
- > Successfully built dd8610c24f82
- ```
-
-6. 运行包含生成的 SSH 密钥的数据容器:
-
- ```shell
- $ docker run --name data pre-receive.dev /bin/true
- ```
-
-7. 将测试预接收挂钩 `always_reject.sh` 复制到数据容器中:
-
- ```shell
- $ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive
- ```
-
-8. 启动一个运行 `sshd` 的应用程序容器并执行挂钩。 记下返回的容器 ID:
-
- ```shell
- $ docker run -d -p 52311:22 --volumes-from data pre-receive.dev
- > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58
- ```
-
-9. 将生成的 SSH 密钥从数据容器复制到本地计算机:
-
- ```shell
- $ docker cp data:/home/git/.ssh/id_rsa .
- ```
-
-10. 修改远程测试仓库并将其推送到 Docker 容器中的 `test.git` 仓库。 此示例使用了 `git@github.com:octocat/Hello-World.git`,但您可以使用想要的任何仓库。 此示例假定您的本地计算机 (127.0.0.1) 绑定了端口 52311,但如果 docker 在远程计算机上运行,则可以使用不同的 IP 地址。
-
- ```shell
- $ git clone git@github.com:octocat/Hello-World.git
- $ cd Hello-World
- $ git remote add test git@127.0.0.1:test.git
- $ GIT_SSH_COMMAND="ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 52311 -i ../id_rsa" git push -u test master
- > Warning: Permanently added '[192.168.99.100]:52311' (ECDSA) to the list of known hosts.
- > Counting objects: 7, done.
- > Delta compression using up to 4 threads.
- > Compressing objects: 100% (3/3), done.
- > Writing objects: 100% (7/7), 700 bytes | 0 bytes/s, done.
- > Total 7 (delta 0), reused 7 (delta 0)
- > remote: error: rejecting all pushes
- > To git@192.168.99.100:test.git
- > ! [remote rejected] master -> master (pre-receive hook declined)
- > error: failed to push some refs to 'git@192.168.99.100:test.git'
- ```
-
- 请注意,在执行预接收挂钩并回显脚本中的输出后,将拒绝推送。
-
-### 延伸阅读
- - 来自 *Pro Git 网站*的“[自定义 Git - Git 强制实施策略示例](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)”
diff --git a/translations/zh-CN/content/admin/developer-workflow/customizing-your-instance-with-integrations.md b/translations/zh-CN/content/admin/developer-workflow/customizing-your-instance-with-integrations.md
deleted file mode 100644
index ce884e2997da..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/customizing-your-instance-with-integrations.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 使用集成自定义您的实例
-intro: '您可以将第三方应用程序与 {% data variables.product.product_location_enterprise %} 集成。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/developer-workflow/customizing-your-instance-with-integrations
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/developer-workflow/establishing-pull-request-merge-conditions.md b/translations/zh-CN/content/admin/developer-workflow/establishing-pull-request-merge-conditions.md
deleted file mode 100644
index d47f687f237d..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/establishing-pull-request-merge-conditions.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 建立拉取请求合并条件
-intro: 您可以要求拉取请求在可以合并之前先通过一组检查。 例如,您可以阻止未通过状态检查的拉取请求。
-mapTopic: true
-redirect_from:
- - /enterprise/admin/developer-workflow/establishing-pull-request-merge-conditions
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/developer-workflow/index.md b/translations/zh-CN/content/admin/developer-workflow/index.md
deleted file mode 100644
index d0c186037b4c..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: 实施策略和定制开发者工作流程
-redirect_from:
- - /enterprise/admin/guides/installation/integrations/
- - /enterprise/admin/categories/integration/
- - /enterprise/admin/developer-workflow
-intro: '本指南介绍了 {% data variables.product.prodname_enterprise %} 上的可用工具,这些工具有助于实现开发者工作流程和强制实施组织策略以降低风险和提升质量。'
-versions:
- enterprise-server: '*'
----
-
-
-### 目录
-
-{% topic_link_in_list /blocking-force-pushes %}
- {% link_in_list /blocking-force-pushes-on-your-appliance %}
- {% link_in_list /blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization %}
- {% link_in_list /blocking-force-pushes-to-a-repository %}
-{% topic_link_in_list /using-webhooks-for-continuous-integration %}
- {% link_in_list /continuous-integration-using-jenkins %}
- {% link_in_list /troubleshooting-service-hooks %}
-{% topic_link_in_list /using-pre-receive-hooks-to-enforce-policy %}
- {% link_in_list /about-pre-receive-hooks %}
- {% link_in_list /creating-a-pre-receive-hook-environment %}
- {% link_in_list /creating-a-pre-receive-hook-script %}
- {% link_in_list /managing-pre-receive-hooks-on-the-github-enterprise-server-appliance %}
-{% topic_link_in_list /establishing-pull-request-merge-conditions %}
- {% link_in_list /about-protected-branches-and-required-status-checks %}
- {% link_in_list /configuring-protected-branches-and-required-status-checks %}
-{% topic_link_in_list /customizing-your-instance-with-integrations %}
- {% link_in_list /managing-projects-using-jira %}
diff --git a/translations/zh-CN/content/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/zh-CN/content/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
deleted file mode 100644
index e1e10632bae5..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: 管理 GitHub Enterprise Server 设备上的预接收挂钩
-intro: '配置如何在 {% data variables.product.prodname_ghe_server %} 设备中使用预接收挂钩。'
-redirect_from:
- - /enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-appliance/
- - /enterprise/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
-versions:
- enterprise-server: '*'
----
-
-### 创建预接收挂钩
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.hooks-tab %}
-4. 单击 **Add pre-receive hook**。 ![添加预接收挂钩](/assets/images/enterprise/site-admin-settings/add-pre-receive-hook.png)
-5. 在 **Hook name** 字段中,输入要创建的挂钩的名称。 ![为预接收挂钩命名](/assets/images/enterprise/site-admin-settings/hook-name.png)
-6. 从 **Environment** 下拉菜单中,选择要在其上运行挂钩的环境。 ![挂钩环境](/assets/images/enterprise/site-admin-settings/environment.png)
-7. 在 **Script(脚本)**下,从 **Select hook repository(选择挂钩仓库)**下拉菜单中,选择包含预接收挂钩脚本的仓库。 从 **Select file** 下拉菜单中,选择预接收挂钩脚本的文件名。 ![挂钩脚本](/assets/images/enterprise/site-admin-settings/hook-script.png)
-8. 选择 **Use the exit-status to accept or reject pushes** 以强制执行脚本。 取消选中此选项可以在忽略 exit-status 值时测试脚本。 在此模式下,脚本的输出将在命令行中对用户可见,但在 web 界面上不可见。 ![使用 exit-status](/assets/images/enterprise/site-admin-settings/use-exit-status.png)
-9. 如果希望预接收挂钩在所有仓库上运行,请选择 **Enable this pre-receive hook on all repositories by default**。 ![为所有仓库启用挂钩](/assets/images/enterprise/site-admin-settings/enable-hook-all-repos.png)
-10. 选择 **Administrators can enable and disable this hook(管理员可以启用和禁用此挂钩)**,以允许具有管理员或所有者权限的组织成员选择要启用还是禁用此预接收挂钩。 ![管理员启用或禁用挂钩](/assets/images/enterprise/site-admin-settings/admins-enable-hook.png)
-
-### 编辑预接收挂钩
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.hooks-tab %}
-1. 在要编辑的预接收挂钩旁边,单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑预接收挂钩](/assets/images/enterprise/site-admin-settings/edit-pre-receive-hook.png)
-
-### 删除预接收挂钩
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.hooks-tab %}
-2. 在要删除的预接收挂钩旁边,单击 {% octicon "x" aria-label="X symbol" %}。 ![编辑预接收挂钩](/assets/images/enterprise/site-admin-settings/delete-pre-receive-hook.png)
-
-### 为组织配置预接收挂钩
-
-仅当站点管理员在创建预接收挂钩时选择了 **Administrators can enable or disable this hook** 选项,组织管理员才能为组织配置挂钩权限。 要为仓库配置预接收挂钩,您必须是组织管理员或所有者。
-
-{% data reusables.profile.enterprise_access_profile %}
-{% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-4. 在左侧侧边栏中,单击 **Hooks**。 ![挂钩侧边栏](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png)
-5. 在要配置的预接收挂钩旁边,单击 **Hook permissions** 下拉菜单。 选择要启用还是禁用预接收挂钩,或者允许仓库管理员对其进行配置。 ![挂钩权限](/assets/images/enterprise/orgs-and-teams/hook-permissions.png)
-
-### 为仓库配置预接收挂钩
-
-仅当站点管理员在创建预接收挂钩时选择了 **Administrators can enable or disable this hook** 选项,仓库所有者才能配置挂钩。 在组织中,组织所有者还必须选择 **Configurable** 挂钩权限。 要为仓库配置预接收挂钩,您必须是仓库所有者。
-
-{% data reusables.profile.enterprise_access_profile %}
-2. 单击 **Repositories**,然后选择要为其配置预接收挂钩的仓库。 ![仓库](/assets/images/enterprise/repos/repositories.png)
-{% data reusables.repositories.sidebar-settings %}
-4. 在左侧边栏中,单击 **Hooks & Services**。 ![挂钩和服务](/assets/images/enterprise/repos/hooks-services.png)
-5. 在要配置的预接收挂钩旁边,单击 **Hook permissions** 下拉菜单。 选择要启用还是禁用预接收挂钩。 ![仓库挂钩权限](/assets/images/enterprise/repos/repo-hook-permissions.png)
diff --git a/translations/zh-CN/content/admin/developer-workflow/managing-projects-using-jira.md b/translations/zh-CN/content/admin/developer-workflow/managing-projects-using-jira.md
deleted file mode 100644
index 13e610f93467..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/managing-projects-using-jira.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: 使用 JIRA 管理项目
-intro: '您可以将 JIRA 与 {% data variables.product.prodname_enterprise %} 集成以进行项目管理。'
-redirect_from:
- - /enterprise/admin/guides/installation/project-management-using-jira/
- - /enterprise/admin/articles/project-management-using-jira/
- - /enterprise/admin/developer-workflow/managing-projects-using-jira
-versions:
- enterprise-server: '*'
----
-
-### 将 JIRA 连接到 {% data variables.product.prodname_enterprise %} 组织
-
-1. 在 http[s]://[hostname]/login 上登录您的 {% data variables.product.prodname_enterprise %} 帐户。
-1. 在任意页面的右上角,单击帐户设置(齿轮)图标。
-1. 在左侧边栏中,单击您组织的名称。
-1. 在左侧边栏中,单击 **Applications**。
-1. 在 **Organization applications** 框的右上角,单击 **Register new application**。
-1. 填写应用程序设置:
- - 在 **Application name** 字段中,输入“JIRA”。
- - 在 **Homepage URL** 字段中,输入 JIRA 实例的完整 URL。
- - 在 **Authorization callback URL** 字段中,输入 JIRA 实例的完整 URL。
-1. 单击 **Register application(注册应用程序)**。
-1. 在页面顶部,记下 **Client ID** 和 **Client Secret**。 您将需要这些信息来配置 JIRA 实例。
-
-### 将 JIRA 连接到 {% data variables.product.prodname_enterprise %} 个人帐户
-
-1. 在 http[s]://[hostname]/login 上登录您的 {% data variables.product.prodname_enterprise %} 帐户。
-1. 在任意页面的右上角,单击帐户设置(齿轮)图标。
-1. 在左侧边栏中,单击 **Applications**。
-1. 在 **Developer applications** 框的右上角,单击 **Register new application**。
-1. 填写应用程序设置:
- - 在 **Application name** 字段中,输入“JIRA”。
- - 在 **Homepage URL** 字段中,输入 JIRA 实例的完整 URL。
- - 在 **Authorization callback URL** 字段中,输入 JIRA 实例的完整 URL。
-1. 单击 **Register application(注册应用程序)**。
-1. 在页面顶部,记下 **Client ID** 和 **Client Secret**。 您将需要这些信息来配置 JIRA 实例。
-
-### JIRA 实例配置
-
-1. 在 JIRA 实例上,登录具有管理访问权限的帐户。
-1. 在页面顶部,单击设置(齿轮)图标。
-1. 在设置下拉列表中,选择 **Add-ons**。
-1. 在左侧边栏的 **Source control** 下,单击 **DVCS accounts**。
-1. 单击 **Link Bitbucket or GitHub account**。
-1. 在 **Add New Account** 模态中,填写您的 {% data variables.product.prodname_enterprise %} 设置:
- - 从 **Host** 下拉菜单中,选择 **GitHub Enterprise**。
- - 在 **Team or User Account** 字段中,输入 {% data variables.product.prodname_enterprise %} 组织或个人帐户的名称。
- - 在 **OAuth Key** 字段中,输入 {% data variables.product.prodname_enterprise %} 开发者应用程序的客户端 ID。
- - 在 **OAuth Secret** 字段中,输入 {% data variables.product.prodname_enterprise %} 开发者应用程序的客户端密钥。
- - 如果您不想链接 {% data variables.product.prodname_enterprise %} 组织或个人帐户拥有的新仓库,请取消选择 **Auto Link New Repositories**。
- - 如果您不想启用智能提交,请取消选择 **Enable Smart Commits**。
- - 单击 **Add(添加)**。
-1. 查看您要授予 {% data variables.product.prodname_enterprise %} 帐户的权限,然后单击 **Authorize application**。
-1. 如有必要,请输入密码以继续。
diff --git a/translations/zh-CN/content/admin/developer-workflow/troubleshooting-service-hooks.md b/translations/zh-CN/content/admin/developer-workflow/troubleshooting-service-hooks.md
deleted file mode 100644
index 3ebab29b5fea..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/troubleshooting-service-hooks.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: 排查服务挂钩问题
-intro: 如果没有交付有效负载,请检查这些常见问题。
-redirect_from:
- - /enterprise/admin/articles/troubleshooting-service-hooks/
- - /enterprise/admin/developer-workflow/troubleshooting-service-hooks
-versions:
- enterprise-server: '*'
----
-
-### 获取有关交付的信息
-
-您可以在任意仓库中找到有关所有服务挂钩交付的最后响应的信息。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-2. 浏览到您要调查的仓库。
-3. 单击导航侧栏中的 **Hooks** 链接。 ![挂钩侧边栏](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. 单击有问题的服务挂钩下的 **Latest Delivery** 链接。 ![挂钩详情](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png)
-5. 在 **Remote Calls** 下,您将看到发布到远程服务器时使用的标头以及远程服务器发送回安装的响应。
-
-### 查看有效负载
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-2. 浏览到您要调查的仓库。
-3. 单击导航侧栏中的 **Hooks** 链接。 ![挂钩侧边栏](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. 单击有问题的服务挂钩下的 **Latest Delivery** 链接。
-5. 单击 **Delivery**。 ![查看有效负载](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png)
-
-### 查看过去的交付
-
-交付存储 15 天。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-2. 浏览到您要调查的仓库。
-3. 单击导航侧栏中的 **Hooks** 链接。 ![挂钩侧边栏](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. 单击有问题的服务挂钩下的 **Latest Delivery** 链接。
-5. 要查看针对该特定挂钩的其他交付,请单击 **More for this Hook ID**: ![查看更多交付](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png)
diff --git a/translations/zh-CN/content/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy.md b/translations/zh-CN/content/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy.md
deleted file mode 100644
index 5efac751dbf5..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 使用预接收挂钩来强制实施策略
-intro: 使用预接收挂钩在您的组织内强制实施工作流程标准。 预接收挂钩需要代码在推送被送入仓库之前传递一组预定义的质量检查。
-mapTopic: true
-redirect_from:
- - /enterprise/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/developer-workflow/using-webhooks-for-continuous-integration.md b/translations/zh-CN/content/admin/developer-workflow/using-webhooks-for-continuous-integration.md
deleted file mode 100644
index a6c23fe34211..000000000000
--- a/translations/zh-CN/content/admin/developer-workflow/using-webhooks-for-continuous-integration.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 使用 web 挂钩进行持续集成
-intro: '如果您已经拥有开发和部署生态系统,则可以使用 web 挂钩将其与 {% data variables.product.prodname_ghe_server %} 集成。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/developer-workflow/continuous-integration-using-travis-ci
- - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-using-analytics.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-using-analytics.md
deleted file mode 100644
index d8c8045d9104..000000000000
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-using-analytics.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Monitoring using analytics
-intro: 'You can enable web analytics tools to track and analyze traffic for your {% data variables.product.prodname_ghe_server %} instance.'
-redirect_from:
- - /enterprise/admin/enterprise-management/monitoring-using-analytics
-versions:
- enterprise-server: '>2.21'
----
-
-### Configuring Google Analytics
-
-To configure Google Analytics, you must have a [Google Analytics ID](https://analytics.google.com/) and authenticate to your {% data variables.product.prodname_ghe_server %} instance with SSH. 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)。”
-
-```shell
-$ ghe-config website-analytics.enabled true
-$ ghe-config website-analytics.google-analytics-id GOOGLE-ANALYTICS-ID
-$ ghe-config-apply
-```
diff --git a/translations/zh-CN/content/admin/installation/about-enterprise-accounts.md b/translations/zh-CN/content/admin/installation/about-enterprise-accounts.md
deleted file mode 100644
index 75c5f0f67a23..000000000000
--- a/translations/zh-CN/content/admin/installation/about-enterprise-accounts.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: 关于企业帐户
-intro: '使用 {% data variables.product.prodname_ghe_server %},可以创建企业帐户,为管理员的帐单和许可使用情况提供单一的可见点和管理点。'
-redirect_from:
- - /enterprise/admin/installation/about-enterprise-accounts
-versions:
- enterprise-server: '*'
----
-
-### 关于 {% data variables.product.prodname_ghe_server %} 上的企业账户
-
-企业帐户可用于管理多个 {% data variables.product.prodname_dotcom %} 组织和 {% data variables.product.prodname_ghe_server %} 实例。 您的企业帐户必须有操作点,如 {% data variables.product.prodname_dotcom %} 上的组织或个人帐户。 企业管理员可以管理设置和首选项,如:
-
-- 成员访问和管理(组织成员、外部协作者)
-- 帐单和使用({% data variables.product.prodname_ghe_server %} 实例、用户许可、{% data variables.large_files.product_name_short %} 包)
-- 安全性(单点登录、双重身份验证)
-- 与 {% data variables.contact.enterprise_support %} 共享的请求和支持包
-
-{% data reusables.enterprise-accounts.enterprise-accounts-billing %}
-
-有关 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_ghe_server %} 之间差异的更多信息,请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。 要升级至 {% data variables.product.prodname_enterprise %} 或开始使用企业帐户,请联系 {% data variables.contact.contact_enterprise_sales %}。
-
-### 管理链接至企业帐户的 {% data variables.product.prodname_ghe_server %} 许可
-
-{% data reusables.enterprise-accounts.admin-managing-licenses %}
diff --git a/translations/zh-CN/content/admin/installation/about-geo-replication.md b/translations/zh-CN/content/admin/installation/about-geo-replication.md
deleted file mode 100644
index 3d33092b73e4..000000000000
--- a/translations/zh-CN/content/admin/installation/about-geo-replication.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: 关于 Geo-replication
-intro: '{% data variables.product.prodname_ghe_server %} 上的 Geo-replication 使用多个活动副本满足从异地分布式数据中心发出的请求。'
-redirect_from:
- - /enterprise/admin/installation/about-geo-replication
-versions:
- enterprise-server: '*'
----
-
-多个活动副本可以提供到达最近副本的较短距离。 举例来说,一个在旧金山、纽约和伦敦均设有办事处的组织可以在靠近纽约的数据中心运行主设备,在靠近旧金山和伦敦的数据中心运行两个副本。 利用地理位置感知 DNS,用户可以转到距离最近的可用服务器,并更快地访问仓库数据。 如果将靠近旧金山的设备指定为主设备,则与伦敦的延迟会比较大,相比而言,将靠近纽约的设备指定为主设备有助于减小主机之间的延迟。
-
-活动副本会将自身无法处理的请求委托主实例代为处理。 副本用作终止所有 SSL 连接的入口点。 与没有 Geo-replication 功能的双节点高可用性配置类似,主机之间的流量通过加密 VPN 连接发送。
-
-Git 请求和特定的文件服务器请求(例如 LFS 和文件上传)可直接通过副本完成,无需从主设备加载任何数据。 Web 请求会始终传送到主设备,但在副本距离用户较近的情况下,由于 SSL 端接距离更近,请求速度更快。
-
-为了让 Geo-replication 无缝运行,需要使用 Geo DNS,例如 [Amazon 的 Route 53 服务](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo)。 实例的主机名应解析到距离用户最近的副本。
-
-### 限制
-
-将请求写入副本需要将数据发送到主设备和所有副本。 这意味着所有写入操作的性能都受限于最慢的副本{% if currentVersion ver_gt "enterprise-server@2.17" %},虽然新的地理副本可以从现有共同位置地理副本(而不是从主设备)播种大部分数据{% endif %}。 Geo-replication 不会增大 {% data variables.product.prodname_ghe_server %} 实例的容量,也不会解决与 CPU 或内存资源不足相关的性能问题。 如果主设备处于脱机状态,则活动副本将无法满足任何读取或写入请求。
-
-### 监视 Geo-replication 配置
-
-{% data reusables.enterprise_installation.monitoring-replicas %}
-
-### 延伸阅读
-- “[创建 Geo-replication 副本](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)”
diff --git a/translations/zh-CN/content/admin/installation/about-high-availability-configuration.md b/translations/zh-CN/content/admin/installation/about-high-availability-configuration.md
deleted file mode 100644
index 88bf3e7b6691..000000000000
--- a/translations/zh-CN/content/admin/installation/about-high-availability-configuration.md
+++ /dev/null
@@ -1,181 +0,0 @@
----
-title: 关于高可用性配置
-intro: '在高性能配置中,完全冗余的次级 {% data variables.product.prodname_ghe_server %} 设备通过复制所有主要数据存储与主设备保持同步。'
-redirect_from:
- - /enterprise/admin/installation/about-high-availability-configuration
-versions:
- enterprise-server: '*'
----
-
-配置高可用性时,会自动设置将所有数据存储(Git 仓库、MySQL、Redis 和 Elasticsearch)单向、异步地从主设备复制到副本。
-
-{% data variables.product.prodname_ghe_server %} 支持主动/被动配置,在这些配置下,副本作为备用设备运行,并且数据库服务在复制模式下运行,但应用程序服务将停止。
-
-### 有针对性的故障场景
-
-使用高可用性配置防护以下问题:
-
-{% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %}
-
-高可用性配置不适用于:
-
- - **扩展**。 虽然可以使用 Geo-replication 将流量分布在不同地理位置,但写入性能受限于主设备的速度和可用性。 更多信息请参阅“[关于 Geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)”。
- - **备份主设备**。 高可用性副本不会替代灾难恢复计划中的非现场备份。 某些形式的数据损坏或数据丢失可能会立即从主设备复制到副本。 为确保安全回滚到稳定的过去状态,必须通过历史快照执行定期备份。
- - **零停机时间升级**。 为避免受控升级场景下出现数据丢失和裂脑的状况,请先将主设备置于维护模式并等待所有写入操作完成,然后再对副本进行升级。
-
-### 网络流量故障转移策略
-
-在故障转移期间,您必须单独配置和管理从主设备到副本的网络流量的重定向。
-
-#### DNS 故障转移
-
-对于 DNS 故障转移,请使用 DNS 记录中指向主 {% data variables.product.prodname_ghe_server %} 设备的短 TTL 值。 建议的 TTL 值范围为 60 秒到 5 分钟。
-
-在故障转移期间,必须将主设备置于维护模式,并将其 DNS 记录重定向到副本的 IP 地址。 将流量从主设备重新定向到副本所需的时间将取决于 TTL 配置以及更新 DNS 记录所需的时间。
-
-如果您要使用 Geo-replication,则必须配置 Geo DNS,将流量定向到距离最近的副本。 更多信息请参阅“[关于 Geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)”。
-
-#### 负载均衡器
-
-{% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %}
-
-在故障转移期间,您必须将主设备置于维护模式。 您可以将负载均衡器配置为自动检测副本何时已升级为主设备,或者可能需要手动更改配置。 您必须先将副本手动升级为主设备,随后副本才能对用户流量作出响应。 更多信息请参阅“[结合使用 {% data variables.product.prodname_ghe_server %} 和负载均衡器](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)”。
-
-{% data reusables.enterprise_installation.monitoring-replicas %}
-
-### 用于复制管理的实用程序
-
-要管理 {% data variables.product.prodname_ghe_server %} 上的复制,请使用 SSH 连接到副本,以使用以下命令行实用程序。
-
-#### ghe-repl-setup
-
-`ghe-repl-setup` 命令可将 {% data variables.product.prodname_ghe_server %} 设备置于副本备用模式。
-
- - 为两个设备之间的通信配置加密的 {% if currentVersion ver_gt "enterprise-server@2.17" %}WireGuard VPN{% else %}OpenVPN{% endif %} 隧道。
- - 配置用于复制的数据库服务并启动。
- - 禁用应用程序服务。 尝试通过 HTTP、Git 或其他受支持协议访问副本将出现“设备处于副本模式”维护页面或显示错误消息。
-
-```shell
-admin@169-254-1-2:~$ ghe-repl-setup 169.254.1.1
-Verifying ssh connectivity with 169.254.1.1 ...
-Connection check succeeded.
-Configuring database replication against primary ...
-Success: Replica mode is configured against 169.254.1.1.
-To disable replica mode and undo these changes, run `ghe-repl-teardown'.
-Run `ghe-repl-start' to start replicating against the newly configured primary.
-```
-
-#### ghe-repl-start
-
-`ghe-repl-start` 命令可以启用所有数据存储的主动复制。
-
-```shell
-admin@169-254-1-2:~$ ghe-repl-start{% if currentVersion ver_lt "enterprise-server@2.18" %}
-Starting OpenVPN tunnel ... {% endif %}
-Starting MySQL replication ...
-Starting Redis replication ...
-Starting Elasticsearch replication ...
-Starting Pages replication ...
-Starting Git replication ...
-Success: replication is running for all services.
-Use `ghe-repl-status' to monitor replication health and progress.
-```
-
-#### ghe-repl-status
-
-`ghe-repl-status` 命令可以返回各数据存储复制流的 `OK`、`WARNING` 或 `CRITICAL` 状态。 如果有任何复制通道处于 `WARNING` 状态,命令将停止执行并显示代码 `1`。 同样,如果有任何通道处于 `CRITICAL` 状态,命令将停止执行并显示代码 `2`。
-
-```shell
-admin@169-254-1-2:~$ ghe-repl-status
-OK: mysql replication in sync
-OK: redis replication is in sync
-OK: elasticsearch cluster is in sync
-OK: git data is in sync (10 repos, 2 wikis, 5 gists)
-OK: pages data is in sync
-```
-
-`-v` 和 `-vv` 选项可以提供关于各数据存储复制状态的详细信息:
-
-```shell
-$ ghe-repl-status -v
-OK: mysql replication in sync
- | IO running: Yes, SQL running: Yes, Delay: 0
-
-OK: redis replication is in sync
- | master_host:169.254.1.1
- | master_port:6379
- | master_link_status:up
- | master_last_io_seconds_ago:3
- | master_sync_in_progress:0
-
-OK: elasticsearch cluster is in sync
- | {
- | "cluster_name" : "github-enterprise",
- | "status" : "green",
- | "timed_out" : false,
- | "number_of_nodes" : 2,
- | "number_of_data_nodes" : 2,
- | "active_primary_shards" : 12,
- | "active_shards" : 24,
- | "relocating_shards" : 0,
- | "initializing_shards" : 0,
- | "unassigned_shards" : 0
- | }
-
-OK: git data is in sync (366 repos, 31 wikis, 851 gists)
- | TOTAL OK FAULT PENDING DELAY
- | repositories 366 366 0 0 0.0
- | wikis 31 31 0 0 0.0
- | gists 851 851 0 0 0.0
- | total 1248 1248 0 0 0.0
-
-OK: pages data is in sync
- | Pages are in sync
-```
-
-#### ghe-repl-stop
-
-`ghe-repl-stop` 命令可以暂时禁用所有数据存储的复制并停止复制服务。 要恢复复制,请使用 [ghe-repl-start](#ghe-repl-start) 命令。
-
-```shell
-admin@168-254-1-2:~$ ghe-repl-stop
-Stopping Pages replication ...
-Stopping Git replication ...
-Stopping MySQL replication ...
-Stopping Redis replication ...
-Stopping Elasticsearch replication ...{% if currentVersion ver_lt "enterprise-server@2.18" %}
-Stopping OpenVPN tunnel ...{% endif %}
-Success: replication was stopped for all services.
-```
-
-#### ghe-repl-promote
-
-`ghe-repl-promote` 命令可以禁用复制并将副本转换为主设备。 设备会配置为使用与原主设备相同的设置,并启用所有服务。
-
-{% data reusables.enterprise_installation.promoting-a-replica %}
-
-```shell
-admin@168-254-1-2:~$ ghe-repl-promote
-Enabling maintenance mode on the primary to prevent writes ...
-Stopping replication ...
- | Stopping Pages replication ...
- | Stopping Git replication ...
- | Stopping MySQL replication ...
- | Stopping Redis replication ...
- | Stopping Elasticsearch replication ...{% if currentVersion ver_lt "enterprise-server@2.18" %}
- | Stopping OpenVPN tunnel ...{% endif %}
- | Success: replication was stopped for all services.
-Switching out of replica mode ...
- | Success: Replication configuration has been removed.
- | Run `ghe-repl-setup' to re-enable replica mode.
-Applying configuration and starting services ...
-Success: Replica has been promoted to primary and is now accepting requests.
-```
-
-#### ghe-repl-teardown
-
-`ghe-repl-teardown` 命令可以完全禁用复制模式,并移除副本配置。
-
-### 延伸阅读
-
-- “[创建高可用性副本](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)”
diff --git a/translations/zh-CN/content/admin/installation/about-the-github-enterprise-server-api.md b/translations/zh-CN/content/admin/installation/about-the-github-enterprise-server-api.md
deleted file mode 100644
index d478338fcdd4..000000000000
--- a/translations/zh-CN/content/admin/installation/about-the-github-enterprise-server-api.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: 关于 GitHub Enterprise Server API
-intro: '{% data variables.product.prodname_ghe_server %} 支持 {% data variables.product.prodname_dotcom_the_website %} 提供的强大 API 及其自身的 API 端点集合。'
-redirect_from:
- - /enterprise/admin/articles/about-the-enterprise-api/
- - /enterprise/admin/articles/using-the-api/
- - /enterprise/admin/categories/api/
- - /enterprise/admin/installation/about-the-github-enterprise-server-api
-versions:
- enterprise-server: '*'
----
-
-The complete documentation for the {% data variables.product.prodname_enterprise_api %} is available at . 利用 API,您可以自动处理多种管理任务。 包含以下例子:
-
-- 对 {% data variables.enterprise.management_console %} 进行更改。 For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)."
-- 收集关于实例的统计信息。 For more information, see "[Admin stats](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#admin-stats)."
-- 配置 LDAP 同步。 For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% if currentVersion ver_gt "enterprise-server@2.18" %}
-- 管理企业帐户。 更多信息请参阅“[企业帐户](/v4/guides/managing-enterprise-accounts)”。{% endif %}
diff --git a/translations/zh-CN/content/admin/installation/accessing-the-administrative-shell-ssh.md b/translations/zh-CN/content/admin/installation/accessing-the-administrative-shell-ssh.md
deleted file mode 100644
index aaf92104ae16..000000000000
--- a/translations/zh-CN/content/admin/installation/accessing-the-administrative-shell-ssh.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: 访问管理 shell (SSH)
-redirect_from:
- - /enterprise/admin/articles/ssh-access/
- - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access/
- - /enterprise/admin/guides/installation/administrative-shell-ssh-access/
- - /enterprise/admin/articles/troubleshooting-ssh-permission-denied-publickey/
- - /enterprise/admin/2.13/articles/troubleshooting-ssh-permission-denied-publickey/
- - /enterprise/admin/2.14/articles/troubleshooting-ssh-permission-denied-publickey/
- - /enterprise/admin/2.15/articles/troubleshooting-ssh-permission-denied-publickey/
- - /enterprise/admin/installation/accessing-the-administrative-shell-ssh
-intro: 'SSH 访问允许用户运行 {% data variables.product.prodname_ghe_server %} 命令行实用程序,可用于故障排查、运行备份和配置复制。'
-versions:
- enterprise-server: '*'
----
-
-### 关于管理 shell 访问
-
-如果您有权限通过 SSH 访问管理 shell,可运行 {% data variables.product.prodname_ghe_server %} 的命令行实用程序。 SSH 访问也可用于故障排查、运行备份和配置复制。 管理 SSH 访问与 Git SSH 访问分开管理,仅可通过端口 122 访问。
-
-### 允许通过 SSH 访问管理 shell
-
-要启用管理 SSH 访问,您必须向授权密钥的实例列表添加 SSH 公钥。
-
-{% tip %}
-
-**提示**:对授权 SSH 密钥进行的变更会立即生效。
-
-{% endtip %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-3. 在“SSH access”下,将密钥粘贴到文本框中,然后单击 **Add key**。 ![添加 SSH 密钥的文本框和按钮](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-### 通过 SSH 连接到管理 shell
-
-将 SSH 密钥添加到列表后,以 `admin` 用户的身份在端口 122 上通过 SSH 连接到实例。
-
-```shell
-$ ssh -p 122 admin@github.example.com
-Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1
-admin@github-example-com:~$ █
-```
-
-#### 排查 SSH 连接问题
-
-如果在尝试通过 SSH 连接到 {% data variables.product.product_location_enterprise %} 时发生 `Permission denied (publickey)` 错误,请确认您是否是通过端口 122 连接的。 您可能需要明确指定要使用的 SSH 私钥。
-
-要使用命令行指定 SSH 私钥,请运行包含 `-i` 参数的 `ssh`。
-
-```shell
-ssh -i /path/to/ghe_private_key -p 122 admin@hostname
-```
-
-您也可以使用 SSH 配置文件 (`~/.ssh/config`) 指定 SSH 私钥。
-
-```shell
-Host hostname
- IdentityFile /path/to/ghe_private_key
- User admin
- Port 122
-```
-
-### 使用本地控制台访问管理 shell
-
-在 SSH 不可用等紧急情况下,您可以在本地访问管理 shell。 以 `admin` 用户身份登录,并使用在 {% data variables.product.prodname_ghe_server %} 初始设置期间确定的密码。
-
-### 管理 shell 的访问限制
-
-管理 shell 访问仅可用于故障排查和执行记录的操作程序。 修改系统和应用程序文件、运行程序或安装不受支持的软件包可能导致支持合约失效。 如果您对支持合约允许的活动有任何疑问,请联系 {% data variables.contact.contact_ent_support %}。
diff --git a/translations/zh-CN/content/admin/installation/accessing-the-management-console.md b/translations/zh-CN/content/admin/installation/accessing-the-management-console.md
deleted file mode 100644
index f2d1654a7bf7..000000000000
--- a/translations/zh-CN/content/admin/installation/accessing-the-management-console.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: 访问 Management Console
-intro: '使用 {% data variables.enterprise.management_console %} 可以设置和配置 {% data variables.product.product_location %}、排定维护窗口、排查问题以及管理许可。'
-redirect_from:
- - /enterprise/admin/articles/about-the-management-console/
- - /enterprise/admin/articles/management-console-for-emergency-recovery/
- - /enterprise/admin/articles/web-based-management-console/
- - /enterprise/admin/categories/management-console/
- - /enterprise/admin/articles/accessing-the-management-console/
- - /enterprise/admin/guides/installation/web-based-management-console/
- - /enterprise/admin/installation/accessing-the-management-console
-versions:
- enterprise-server: '*'
----
-
-### 关于 {% data variables.enterprise.management_console %}
-
-使用 {% data variables.enterprise.management_console %} 执行基本管理活动:
-- **初始设置**:首次启动 {% data variables.product.product_location_enterprise %} 时,在浏览器中访问 {% data variables.product.product_location_enterprise %} 的 IP 地址,简单了解初始设置流程。
-- **配置实例的基本设置**:在“Settings”页面上配置 DNS、主机名、SSL、用户身份验证、电子邮件、监视服务和日志转发。
-- **排定维护窗口**:使用 {% data variables.enterprise.management_console %} 或管理 shell 执行维护时,使 {% data variables.product.product_location_enterprise %} 进入脱机状态。
-- **排查问题**:生成支持包或查看高级诊断信息。
-- **许可管理**:查看或更新 {% data variables.product.prodname_enterprise %} 许可。
-
-即使在实例处于维护模式,存在重大应用程序故障或者主机名或 SSL 错误配置的情况下,您也始终可以通过 {% data variables.product.product_location_enterprise %} 的 IP 地址访问 {% data variables.enterprise.management_console %}。
-
-要访问 {% data variables.enterprise.management_console %},您必须使用在 {% data variables.product.product_location_enterprise %} 初始设置期间确定的管理员密码。 您还必须能够连接到端口 8443 上的虚拟机主机。 如果无法访问 {% data variables.enterprise.management_console %},请检查中间防火墙和安全组配置。
-
-### 以站点管理员身份访问 {% data variables.enterprise.management_console %}
-
-首次以站点管理员身份访问 {% data variables.enterprise.management_console %} 时,必须上传 {% data variables.product.prodname_enterprise %} 许可文件,以便在应用程序中进行身份验证。更多信息请参阅“[管理您的 {% data variables.product.prodname_enterprise %} 许可](/enterprise/{{ currentVersion }}/admin/guides/installation/managing-your-github-enterprise-license)。”
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.type-management-console-password %}
-
-### 以未验证用户身份访问 {% data variables.enterprise.management_console %}
-
-1. 在浏览器中访问此 URL,用您的实际 {% data variables.product.prodname_ghe_server %} 主机名或 IP 地址替换 `hostname`:
- ```shell
- http(s)://HOSTNAME/setup
- ```
-{% data reusables.enterprise_management_console.type-management-console-password %}
-
-### 登录尝试失败后解锁 {% data variables.enterprise.management_console %}
-
-如果十分钟内登录尝试失败十次,{% data variables.enterprise.management_console %} 将锁定。 您必须等待登录屏幕自动解锁,然后才能再次尝试登录。 一旦前十分钟内登录尝试失败次数不足十次,登录屏幕便会自动解锁。 成功登录后,计数器会复位。
-
-要立即解锁 {% data variables.enterprise.management_console %},请通过管理 shell 使用 `ghe-reactivate-admin-login` 命令。 更多信息请参阅“[命令行实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)”和“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。
diff --git a/translations/zh-CN/content/admin/installation/accessing-the-monitor-dashboard.md b/translations/zh-CN/content/admin/installation/accessing-the-monitor-dashboard.md
deleted file mode 100644
index 7070fb845268..000000000000
--- a/translations/zh-CN/content/admin/installation/accessing-the-monitor-dashboard.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: 访问监视仪表板
-intro: '{% data variables.product.prodname_ghe_server %} 中基于 Web 的监视仪表板可以显示关于 {% data variables.product.prodname_ghe_server %} 设备的历史数据,例如 CPU 和内存使用情况、应用程序和身份验证响应时间以及整体系统健康状况。'
-redirect_from:
- - /enterprise/admin/installation/accessing-the-monitor-dashboard
-versions:
- enterprise-server: '*'
----
-
-### 访问监视仪表板
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-2. 在页面顶部,单击 **Monitor**。 ![监视仪表板链接](/assets/images/enterprise/management-console/monitor-dash-link.png)
-
-### 排查设备上的常见资源分配问题
-
-{% note %}
-
-**注**:由于通过持续集成 (CI) 或构建服务器定期轮询 {% data variables.product.product_location_enterprise %} 会引发拒绝服务攻击,从而导致问题的出现,因此,建议使用 web 挂钩推送更新。 更多信息请参阅“[关于 web 挂钩](/enterprise/{{ currentVersion }}/user/articles/about-webhooks/)”。
-
-{% endnote %}
-
-使用监视仪表板实时了解设备资源健康状况并确定如何解决高利用率问题。
-
-| 问题 | 可能原因 | 建议 |
-| ---------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| CPU 利用率高 | 在同一主机上运行的其他服务或程序争用 VM | 如有可能,请将其他服务或程序重新配置为占用较少的 CPU 资源。 要增加 VM 的总 CPU 资源,请参阅“[增加 CPU 或内存资源](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-cpu-or-memory-resources/)”。 |
-| 内存使用量高 | 在同一主机上运行的其他服务或程序争用 VM | 如有可能,请将其他服务或程序重新配置为占用较少内存。 要增加 VM 上可用的总内存大小,请参阅“[增加 CPU 或内存资源](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-cpu-or-memory-resources/)”。 |
-| 可用磁盘空间小 | 较大的二进制或日志文件占用磁盘空间 | 如有可能,请在独立服务器上托管较大的二进制文件,并压缩或存档日志文件。 如有必要,请按“[增加存储容量](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity/)”中的步骤操作,为您的平台增加 VM 的磁盘空间。 |
-| 响应时间较正常时间长 | 通常是上述问题之一造成的 | 确定并解决根本问题。 如果响应时间仍较长,请联系 {% data variables.contact.contact_ent_support %}。 |
-| 错误率提高 | 软件问题 | 联系 {% data variables.contact.contact_ent_support %} 并附上支持包。 更多信息请参阅“[向 {% data variables.product.prodname_enterprise %} Support 提供数据](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)”。 |
diff --git a/translations/zh-CN/content/admin/installation/activity-dashboard.md b/translations/zh-CN/content/admin/installation/activity-dashboard.md
deleted file mode 100644
index 3440c627ad3c..000000000000
--- a/translations/zh-CN/content/admin/installation/activity-dashboard.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: 活动仪表板
-intro: '活动仪表板提供 {% data variables.product.product_location_enterprise %} 上所有活动的概览。'
-redirect_from:
- - /enterprise/admin/articles/activity-dashboard/
- - /enterprise/admin/installation/activity-dashboard
-versions:
- enterprise-server: '*'
----
-
-活动仪表板提供以下活动数量的周图、月度图和年度图表:
-- 新拉取请求
-- 已合并拉取请求
-- 新问题
-- 已关闭问题
-- 新问题评论
-- 新仓库
-- 新用户帐户
-- 新组织
-- 新团队
-
-![活动仪表板](/assets/images/enterprise/activity/activity-dashboard-yearly.png)
-
-为获取基于 {% data variables.product.prodname_enterprise %} 中数据的更多分析,可以购买 {% data variables.product.prodname_insights %}。 更多信息请参阅“[关于 {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/about-github-insights)”。
-
-### 访问活动仪表板
-
-1. 在任一页面顶部,单击 **Explore**。 ![Explore 选项卡](/assets/images/enterprise/settings/ent-new-explore.png)
-2. 在右上角单击 **Activity**。 ![Activity 按钮](/assets/images/enterprise/activity/activity-button.png)
diff --git a/translations/zh-CN/content/admin/installation/audit-logging.md b/translations/zh-CN/content/admin/installation/audit-logging.md
deleted file mode 100644
index 4ed9fcdcb089..000000000000
--- a/translations/zh-CN/content/admin/installation/audit-logging.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: 审核日志
-intro: '{% data variables.product.prodname_enterprise %} 会保留已审核的用户、组织、仓库和系统事件的日志。 日志可用于调试以及内部和外部合规。'
-redirect_from:
- - /enterprise/admin/articles/audit-logging/
- - /enterprise/admin/installation/audit-logging
-versions:
- enterprise-server: '*'
----
-
-要获取完整列表,请参阅“[审核的操作](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)”。有关查找特定操作的详细信息,请参阅“[搜索审核日志](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)”。
-
-### 推送日志
-
-会记录每个 Git 推送操作。 更多信息请参阅“[查看推送日志](/enterprise/{{ currentVersion }}/admin/guides/installation/viewing-push-logs)”。
-
-### 系统事件
-
-所有经过审核的系统事件(包括所有推送和拉取)都会记录到 `/var/log/github/audit.log` 中。 日志每 24 小时自动轮换一次,并会保留七天。
-
-支持包中包含系统日志。 更多信息请参阅“[向 {% data variables.product.prodname_dotcom %} Support 提供数据](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support)”。
-
-### 支持包
-
-所有审核信息均会记录到任何支持包 `github-logs` 目录的 `audit.log` 文件中。 如果已启用日志转发,您可以将此数据传输到外部 syslog 流使用者,例如 [Splunk](http://www.splunk.com/) 或 [Logstash](http://logstash.net/)。 此日志中的所有条目均使用 `github_audit` 关键词,并且可以通过该关键词进行筛选。 更多信息请参阅“[日志转发](/enterprise/{{ currentVersion }}/admin/guides/installation/log-forwarding)”。
-
-例如,此条目显示已创建的新仓库。
-
-```
-Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"}
-```
-
-此示例显示提交已推送到仓库。
-
-```
-Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/master" }
-```
diff --git a/translations/zh-CN/content/admin/installation/audited-actions.md b/translations/zh-CN/content/admin/installation/audited-actions.md
deleted file mode 100644
index 5b5ef3b692d2..000000000000
--- a/translations/zh-CN/content/admin/installation/audited-actions.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: 审核的操作
-intro: 您可以在审核日志中搜索各种操作。
-redirect_from:
- - /enterprise/admin/articles/audited-actions/
- - /enterprise/admin/installation/audited-actions
-versions:
- enterprise-server: '*'
----
-
-#### 身份验证
-
-| 名称 | 描述 |
-| ------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------- |
-| `oauth_access.create` | 已为用户帐户[生成>](/articles/creating-an-access-token-for-command-line-use) [OAuth 访问令牌](/v3/oauth/)。 |
-| `oauth_access.destroy` | 已从用户帐户中删除 [OAuth 访问令牌](/v3/oauth/)。 |
-| `oauth_application.destroy` | 已从用户或组织帐户中删除 [OAuth 应用程序](/guides/basics-of-authentication/#registering-your-app)。 |
-| `oauth_application.reset_secret` | 已重置 [OAuth 应用程序](/guides/basics-of-authentication/#registering-your-app)的密钥。 |
-| `oauth_application.transfer` | 已将 [OAuth 应用程序](/guides/basics-of-authentication/#registering-your-app)从一个用户或组织帐户传送到另一个用户或组织帐户。 |
-| `public_key.create` | 已将 SSH 密钥[添加](/articles/adding-a-new-ssh-key-to-your-github-account)到用户帐户中,或者已将[部署密钥](/guides/managing-deploy-keys/#deploy-keys)添加到仓库中。 |
-| `public_key.delete` | 已从用户帐户中移除 SSH 密钥,或已从仓库中移除[部署密钥](/guides/managing-deploy-keys/#deploy-keys)。 |
-| `public_key.update` | 已更新用户帐户的 SSH 密钥或仓库的[部署密钥](/guides/managing-deploy-keys/#deploy-keys)。 |
-| `two_factor_authentication.enabled` | 已为用户帐户启用[双重身份验证](/articles/about-two-factor-authentication)。 |
-| `two_factor_authentication.disabled` | 已为用户帐户禁用[双重身份验证](/articles/about-two-factor-authentication)。 |
-
-#### 挂钩
-
-| 名称 | Description |
-| ---------------------:| ----------- |
-| `hook.create` | 已向仓库添加新挂钩。 |
-| `hook.config_changed` | 已更改挂钩的配置。 |
-| `hook.destroy` | 已删除挂钩。 |
-| `hook.events_changed` | 已更改挂钩的配置事件。 |
-
-#### 实例配置设置
-
-| 名称 | 描述 |
-| -------------------------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `business.update_member_repository_creation_permission` | 站点管理员限制在实例上的组织中创建仓库。 更多信息请参阅“[限制在实例中创建仓库](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)”。 |
-| `business.clear_members_can_create_repos` | 站点管理员取消了对在实例上的组织中创建仓库的限制。 更多信息请参阅“[限制在实例中创建仓库](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)”。 |
-| `enterprise.config.lock_anonymous_git_access` | 站点管理员锁定匿名 Git 读取权限,以防止仓库管理员更改该实例上仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。 |
-| `enterprise.config.unlock_anonymous_git_access` | 站点管理员解锁匿名 Git 读取权限,以允许仓库管理员更改该实例上仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。 |
-
-#### 议题和拉取请求
-
-| 名称 | 描述 |
-| ------------------------------------:| -------------------------------------------------------------------------------------------- |
-| `issue.update` | 问题的正文文本(初始注释)已更改。 |
-| `issue_comment.update` | 已更改问题的正文文本(初始注释)。 |
-| `pull_request_review_comment.delete` | 已删除对拉取请求的评论。 |
-| `issue.destroy` | 已从仓库中删除问题。 更多信息请参阅“[删除问题](/enterprise/{{ currentVersion }}/user/articles/deleting-an-issue)"。” |
-
-#### 组织
-
-| 名称 | 描述 |
-| ------------------:| ---------------------------------------------------------------------------------------------------------------------- |
-| `org.async_delete` | 用户发起了删除组织的后台作业。 |
-| `org.delete` | 组织已由用户发起的后台作业删除。 |
-| `org.transform` | 已将用户帐户转换为组织。 更多信息请参阅“[将用户转换为组织](/enterprise/{{ currentVersion}}/user/articles/converting-a-user-into-an-organization/)”。 |
-
-#### 受保护分支
-
-| 名称 | 描述 |
-| ------------------------------------------------------------------:| ---------------------- |
-| `protected_branch.create` | 已在分支上启用分支保护。 |
-| `protected_branch.destroy` | 已在分支上禁用分支保护。 |
-| `protected_branch.update_admin_enforced` | 已为仓库管理员强制执行分支保护。 |
-| `protected_branch.update_require_code_owner_review` | 已在分支上更新必需代码所有者审查的强制执行。 |
-| `protected_branch.dismiss_stale_reviews` | 已在分支上更新忽略旧拉取请求的强制执行。 |
-| `protected_branch.update_signature_requirement_enforcement_level` | 已在分支上更新必需提交签名的强制执行。 |
-| `protected_branch.update_pull_request_reviews_enforcement_level` | 已在分支上更新必需拉取请求审查的强制执行。 |
-| `protected_branch.update_required_status_checks_enforcement_level` | 已在分支上更新必需状态检查的强制执行。 |
-| `protected_branch.rejected_ref_update` | 分支更新尝试被拒。 |
-| `protected_branch.policy_override` | 分支保护要求被仓库管理员覆盖。 |
-
-#### 仓库
-
-| 名称 | 描述 |
-| ------------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repo.access` | 已将私有仓库设为公共,或者已将公共仓库设为私有。 |
-| `repo.archive` | 已存档仓库。 更多信息请参阅“[存档和取消存档仓库](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/)”。 |
-| `repo.add_member` | 已向仓库添加协作者。 |
-| `repo.config` | 站点管理员已阻止强制推送。 更多信息请参阅“[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)”。 |
-| `repo.create` | 已创建仓库。 |
-| `repo.destroy` | 已删除仓库。 |
-| `repo.remove_member` | 已从仓库中移除协作者。 |
-| `repo.rename` | 已重命名仓库。 |
-| `repo.transfer` | 用户已接受接收传输仓库的请求。 |
-| `repo.transfer_start` | 用户已发送向另一用户或组织传输仓库的请求。 |
-| `repo.unarchive` | 已取消存档仓库。 更多信息请参阅“[存档和取消存档仓库](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/)”。 |
-| `repo.config.disable_anonymous_git_access` | 已为公共仓库禁用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。” |
-| `repo.config.enable_anonymous_git_access` | 已为公共仓库启用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。” |
-| `repo.config.lock_anonymous_git_access` | 已锁定仓库的匿名 Git 读取权限设置,阻止仓库管理员更改(启用或禁用)此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。 |
-| `repo.config.unlock_anonymous_git_access` | 已解锁仓库的匿名 Git 读取权限设置,允许仓库管理员更改(启用或禁用)此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。 |
-
-#### 站点管理员工具
-
-| 名称 | 描述 |
-| --------------------:| ---------------------------------------------------------------------- |
-| `staff.disable_repo` | 站点管理员已禁用对仓库及其所有复刻的访问。 |
-| `staff.enable_repo` | 站点管理员已重新启用对仓库及其所有复刻的访问。 |
-| `staff.fake_login` | 站点管理员以另一用户的身份登录 {% data variables.product.prodname_enterprise %}。 |
-| `staff.repo_unlock` | 站点管理员已解锁(临时获得完全访问权限)用户的一个私有仓库。 |
-| `staff.unlock` | 站点管理员已解锁(临时获得完全访问权限)用户的所有私有仓库。 |
-
-#### 团队
-
-| 名称 | 描述 |
-| --------------:| --------------- |
-| `team.create` | 已向团队添加用户帐户或仓库。 |
-| `team.delete` | 已从团队中移除用户帐户或仓库。 |
-| `team.destroy` | 已删除团队。 |
-
-#### 用户
-
-| 名称 | 描述 |
-| ---------------------------:| ------------------------------------ |
-| `user.add_email` | 已向用户帐户添加电子邮件地址。 |
-| `user.async_delete` | 已启动异步作业,用于销毁用户帐户,最终触发 `user.delete`。 |
-| `user.change_password` | 用户已更改其密码。 |
-| `user.create` | 已创建新的用户帐户。 |
-| `user.delete` | 已通过异步作业销毁用户帐户。 |
-| `user.demote` | 已将站点管理员降级为普通用户帐户。 |
-| `user.destroy` | 用户已删除其帐户,进而触发 `user.async_delete`。 |
-| `user.failed_login` | 用户尝试登录时使用的用户名、密码或双重身份验证码不正确。 |
-| `user.forgot_password` | 用户通过登录页面请求了密码重置。 |
-| `user.login` | 用户已登录。 |
-| `user.promote` | 已将普通用户帐户升级为站点管理员。 |
-| `user.remove_email` | 已从用户帐户中移除电子邮件地址。 |
-| `user.rename` | 已更改用户名。 |
-| `user.suspend` | 站点管理员已挂起用户帐户。 |
-| `user.two_factor_requested` | 已提示用户输入双重身份验证码。 |
-| `user.unsuspend` | 站点管理员已取消挂起用户帐户。 |
diff --git a/translations/zh-CN/content/admin/installation/command-line-utilities.md b/translations/zh-CN/content/admin/installation/command-line-utilities.md
deleted file mode 100644
index 904f855cc8d2..000000000000
--- a/translations/zh-CN/content/admin/installation/command-line-utilities.md
+++ /dev/null
@@ -1,787 +0,0 @@
----
-title: 命令行实用程序
-intro: '{% data variables.product.prodname_ghe_server %} 包含的各种实用程序可以帮助解决特殊问题或执行特定任务。'
-redirect_from:
- - /enterprise/admin/articles/viewing-all-services/
- - /enterprise/admin/articles/command-line-utilities/
- - /enterprise/admin/installation/command-line-utilities
-miniTocMaxHeadingLevel: 4
-versions:
- enterprise-server: '*'
----
-
-以 SSH 管理员用户身份登录后,您可以在虚拟机上的任何位置执行这些命令。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。
-
-### 常规
-
-#### ghe-announce
-
-此实用程序会在每个 {% data variables.product.prodname_enterprise %} 页面顶部设置横幅, 您可以使用横幅向用户广播消息。
-
-```shell
-# Sets a message that's visible to everyone
-$ ghe-announce -s MESSAGE
-> Announcement message set.
-# Removes a previously set message
-$ ghe-announce -u
-> Removed the announcement message
-```
-
-#### ghe-check-disk-usage
-
-此实用程序会检查磁盘中的大文件或已删除但文件句柄仍保持打开的文件。 如果尝试释放根分区中的空间,应运行此实用程序。
-
-```shell
-ghe-check-disk-usage
-```
-
-#### ghe-cleanup-caches
-
-此实用程序会清理各种有可能占用根卷上的额外磁盘空间的缓存。 如果您发现一段时间内根卷磁盘空间的使用量显著升高,最好运行此应用程序,查看是否可以帮助降低整体使用量 。
-
-```shell
-ghe-cleanup-caches
-```
-#### ghe-cleanup-settings
-
-此实用程序会擦除所有现有的 {% data variables.enterprise.management_console %} 设置。
-
-{% tip %}
-
-**提示**:{% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %}
-
-{% endtip %}
-
-```shell
-ghe-cleanup-settings
-```
-
-#### ghe-config
-
-此实用程序可用于检索和修改 {% data variables.product.product_location_enterprise %} 的配置设置。
-
-```shell
-$ ghe-config core.github-hostname
-# Gets the configuration value of `core.github-hostname`
-$ ghe-config core.github-hostname 'example.com'
-# Sets the configuration value of `core.github-hostname` to `example.com`
-$ ghe-config -l
-# Lists all the configuration values
-```
-允许您在 `cluster.conf` 中查找节点的 uuid。
-
-``` shell
- $ ghe-config _hostname_.uuid
-```
-
-#### ghe-config-apply
-
-此实用程序会应用 {% data variables.enterprise.management_console %} 设置,重新加载系统服务,准备存储设备,重新加载应用程序服务并运行任何待处理的数据库迁移。 It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/setup/api/configure` endpoint](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console).
-
-您有可能永远不需要手动运行此实用程序,但如果希望通过 SSH 自动完成设置保存过程,也可以使用此实用程序。
-
-```shell
-ghe-config-apply
-```
-
-#### ghe-console
-
-此实用程序会在您的 {% data variables.product.prodname_enterprise %} 设备上打开 GitHub Rails 控制台。 {% data reusables.command_line.use_with_support_only %}
-
-```shell
-ghe-console
-```
-
-#### ghe-dbconsole
-
-此实用程序会在您的 {% data variables.product.prodname_enterprise %} 设备上打开 MySQL 数据库会话。 {% data reusables.command_line.use_with_support_only %}
-
-```shell
-ghe-dbconsole
-```
-
-#### ghe-es-index-status
-此实用程序会以 CSV 格式返回 ElasticSearch 索引的摘要。
-
-将包含标头行的索引摘要打印到 `STDOUT`:
-```shell
-$ ghe-es-index-status -do
-> warning: parser/current is loading parser/ruby23, which recognizes
-> warning: 2.3.3-compliant syntax, but you are running 2.3.4.
-> warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
-> Name,Primary,Searchable,Writable,UpToDate,RepairProgress,Version
-> code-search-1,true,true,true,true,100.0,72e27df7c631b45e026b42bfef059328fa040e17
-> commits-5,true,true,true,true,100.0,7ed28813100c47813ef654c0ee2bb9abf21ab744
-> gists-4,true,true,true,true,100.0,cf8e7d04fcf2564c902e2873c424a279cc41079d
-> issues-4,false,false,false,true,100.0,d0bb08f71eebf6e7b070572aa399b185dbdc8a76
-> issues-5,true,true,true,true,100.0,d0bb08f71eebf6e7b070572aa399b185dbdc8a76
-> projects-2,true,true,true,true,100.0,c5cac1c4b3c66d42e609d088d174dbc3dd44469a
-> pull-requests-6,true,true,true,true,100.0,6a466ad6b896a3499509990979bf9a18d7d41de3
-> repos-6,true,true,true,true,100.0,6c8b5fbba0fc1e409558db411d05e092c1387082
-> users-5,true,true,true,true,100.0,38984875552bb826c9ec42999f409cb2e95556eb
-> wikis-4,true,true,true,true,100.0,2613dec44bd14e14577803ac1f9e4b7e07a7c234
-```
-
-将索引摘要和管道结果打印到 `column`,以供读取:
-
-```shell
-$ ghe-es-index-status -do | column -ts,
-> warning: parser/current is loading parser/ruby23, which recognizes
-> warning: 2.3.3-compliant syntax, but you are running 2.3.4.
-> warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
-> Name Primary Searchable Writable UpToDate RepairProgress Version
-> code-search-1 true true true true 100.0 72e27df7c631b45e026b42bfef059328fa040e17
-> commits-5 true true true true 100.0 7ed28813100c47813ef654c0ee2bb9abf21ab744
-> gists-4 true true true true 100.0 cf8e7d04fcf2564c902e2873c424a279cc41079d
-> issues-4 false false false true 100.0 d0bb08f71eebf6e7b070572aa399b185dbdc8a76
-> issues-5 true true true true 100.0 d0bb08f71eebf6e7b070572aa399b185dbdc8a76
-> projects-2 true true true true 100.0 c5cac1c4b3c66d42e609d088d174dbc3dd44469a
-> pull-requests-6 true true true true 100.0 6a466ad6b896a3499509990979bf9a18d7d41de3
-> repos-6 true true true true 100.0 6c8b5fbba0fc1e409558db411d05e092c1387082
-> users-5 true true true true 100.0 38984875552bb826c9ec42999f409cb2e95556eb
-> wikis-4 true true true true 100.0 2613dec44bd14e14577803ac1f9e4b7e07a7c234
-```
-
-#### ghe-legacy-github-services-report
-
-此实用程序会列出您的设备中使用 {% data variables.product.prodname_dotcom %} Services 的仓库,作为一种集成方法,此服务将于 2018 年 10 月 1 日停用。 您的设备上的用户可能已设置 {% data variables.product.prodname_dotcom %} Services,为发往某些仓库的推送创建通知。 For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/v3/guides/replacing-github-services/)." For more information about this command or for additional options, use the `-h` flag.
-
-```shell
-ghe-legacy-github-services-report
-
-```
-
-#### ghe-logs-tail
-
-此实用程序允许跟踪记录安装中的所有相关日志文件。 您可以传入选项,将日志限制为特定集合。 使用 -h 标志表示附加选项。
-
-```shell
-ghe-logs-tail
-```
-
-#### ghe-maintenance
-
-此实用程序允许您控制安装维护模式的状态, 其设计为主要由 {% data variables.enterprise.management_console %} 在后台使用,但也可以直接使用。
-
-```shell
-ghe-maintenance -h
-```
-
-{% if currentVersion ver_gt "enterprise-server@2.17" %}
-#### ghe-motd
-
-此实用程序重新显示管理员通过管理 shell 访问实例时看到的当天消息 (MOTD)。 输出包含实例状态的概述。
-
-```shell
-ghe-motd
-```
-{% endif %}
-
-#### ghe-nwo
-
-此实用程序会根据仓库 ID 返回仓库名称和所有者。
-
-```shell
-ghe-nwo REPOSITORY_ID
-```
-
-#### ghe-org-admin-promote
-
-使用此命令可为设备上具有站点管理员权限的用户提供组织所有者权限,或者为组织中的任何用户提供组织所有者权限。 您必须指定用户和/或组织。 `ghe-org-admin-promote` 命令始终会在运行前要求确认,除非您使用 `-y` 标志绕过确认过程。
-
-您可将以下选项与实用程序配合使用:
-
-- `-u` 标志指定用户名。 使用此标志可为特定用户提供组织所有者权限。 省略 `-u` 标志会将所有站点管理员升级为指定组织的所有者。
-- `-o` 标志指定组织。 使用此标志可提供特定组织中的所有者权限。 省略 `-o` 标志会将所有组织中的所有者权限授予指定的站点管理员。
-- `-a` 标志会将所有组织中的所有者权限授予所有站点管理员。
-- `-y` 标志可绕过手动确认。
-
-此实用程序无法将非站点管理员升级为所有组织的所有者。 您可以使用 [ghe-user-promote](#ghe-user-promote) 将普通用户帐户升级为站点管理员。
-
-将特定组织中的组织所有者权限授予一个用户
-
-```shell
-ghe-org-admin-promote -u USERNAME -o ORGANIZATION
-```
-
-将所有组织中的组织所有者权限授予特定的站点管理员
-
-```shell
-ghe-org-admin-promote -u USERNAME
-```
-
-将特定组织中的组织所有者权限授予所有站点管理员
-
-```shell
-ghe-org-admin-promote -o ORGANIZATION
-```
-
-将所有组织中的组织所有者权限授予所有站点管理员
-
-```shell
-ghe-org-admin-promote -a
-```
-
-#### ghe-reactivate-admin-login
-
-在 10 分钟内登录尝试失败 10 次后,使用此命令可立即解锁 {% data variables.enterprise.management_console %}。
-
-```shell
-$ ghe-reactivate-admin-login
-```
-
-#### ghe-resque-info
-
-此实用程序会显示关于后台作业(活动作业和队列中的作业)的信息, 它提供的作业计数与每个页面顶部管理员统计信息栏中的计数相同。
-
-此实用程序可以帮助确定 Resque 服务器在处理后台作业时是否会出现问题。 下列任一场景均可能指示 Resque 存在问题:
-
-* 后台作业数增加,而活动作业数保持不变。
-* 事件源未更新。
-* Webhooks are not being triggered.
-* Web 界面在 Git 推送后未更新。
-
-如果怀疑 Resque 出现故障,请联系 {% data variables.contact.contact_ent_support %} 获取帮助。
-
-使用此命令,您还可以暂停或恢复队列中的作业。
-
-```shell
-$ ghe-resque-info
-# lists queues and the number of currently queued jobs
-$ ghe-resque-info -p QUEUE
-# pauses the specified queue
-$ ghe-resque-info -r QUEUE
-# resumes the specified queue
-```
-
-#### ghe-saml-mapping-csv
-
-此实用程序可帮助映射 SAML 记录。
-
-为 {% data variables.product.product_name %} 用户创建包含所有 SAML 映射的 CSV 文件:
-```shell
-$ ghe-saml-mapping-csv -d
-```
-
-要使用新值执行更新 SAML 映射的排演:
-```shell
-$ ghe-saml-mapping-csv -u -n -f /path/to/file
-```
-
-要使用新值更新 SAML 映射:
-```shell
-$ ghe-saml-mapping-csv -u -f /path/to/file
-```
-
-#### ghe-service-list
-
-此实用程序会列出您的设备上已启动或停止(正在运行或等待)的服务。
-
-```shell
-$ ghe-service-list
-start/running
- - github-resqued, process 12711
- - github-unicorn, process 12726
- - github-gitauth, process 12743
- - git-daemon, process 12755
- - babeld, process 12771
- - github-svn-proxy, process 12802
- - gist-unicorn, process 12832
- - gist-resqued, process 12881
- - render-unicorn, process 12939
- - hookshot-unicorn, process 13076
- - nodeload2, process 13192
- - slumlord-unicorn, process 13304
- - ghe-storage, process 2012
- - enterprise-manage-unicorn, process 2024
- - enterprise-manage-resque, process 2053
-
-stop/waiting
- - ghe-replica-mode
-```
-
-{% tip %}
-
-如有需要,可将此命令返回的服务名称与 [`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html) 命令结合使用,以手动停止、启动或重启这些服务。 例如:
-
-```shell
-$ sudo systemctl restart github-resqued
-```
-
-停止服务会导致安装停机,因此建议您在停止或重启任何服务之前联系 {% data variables.contact.contact_ent_support %}。
-
-{% endtip %}
-
-#### ghe-set-password
-
-使用 `ghe-set-password`,您可以设置新密码,在 [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console) 中进行身份验证。
-
-```shell
-ghe-set-password
-```
-
-#### ghe-ssh-check-host-keys
-
-此实用程序会对照已知泄露的 SSH 主机密钥检查现有的 SSH 主机密钥。
-
-```shell
-$ ghe-ssh-check-host-keys
-```
-
-如果发现主机密钥泄露,实用程序会以状态 `1` 退出并显示以下消息:
-```shell
-> One or more of your SSH host keys were found in the blacklist.
-> Please reset your host keys using ghe-ssh-roll-host-keys.
-```
-
-如果未发现主机密钥泄露,实用程序会以状态 `0` 退出并显示以下消息:
-```shell
-> The SSH host keys were not found in the SSH host key blacklist.
-> No additional steps are needed/recommended at this time.
-```
-
-#### ghe-ssh-roll-host-keys
-
-此实用程序会滚动 SSH 主机密钥并将其替换为新生成的密钥。
-
-```shell
-$ sudo ghe-ssh-roll-host-keys
-Proceed with rolling SSH host keys? This will delete the
-existing keys in /etc/ssh/ssh_host_* and generate new ones. [y/N]
-
-# Press 'Y' to confirm deleting, or use the -y switch to bypass this prompt
-
-> SSH host keys have successfully been rolled.
-```
-
-#### ghe-ssh-weak-fingerprints
-
-此实用程序会返回存储在 {% data variables.product.prodname_enterprise %} 设备上的已知弱 SSH 密钥的报告。 您可以选择批量撤销用户密钥。 此实用程序将报告弱系统密钥,您必须在 [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console) 中手动撤销这些密钥。
-
-```shell
-# Print a report of weak user and system SSH keys
-$ ghe-ssh-weak-fingerprints
-
-# Revoke all weak user keys
-$ ghe-ssh-weak-fingerprints --revoke
-```
-
-#### ghe-ssl-acme
-
-此实用程序允许您在 {% data variables.product.prodname_enterprise %} 设备上安装 Let's Encrypt 证书。 更多信息请参阅“[配置 TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)”。
-
-您可以使用 `-x` 标志来删除 ACME 配置。
-
-```shell
-ghe-ssl-acme -e
-```
-
-#### ghe-ssl-ca-certificate-install
-
-此实用程序允许您在 {% data variables.product.prodname_enterprise %} 服务器上安装自定义根 CA 证书。 证书必须采用 PEM 格式。 此外,如果您的证书提供者在一个文件中包含多个 CA 证书,则必须将其拆分到多个单独文件中,随后再将这些文件逐个传递到 `ghe-ssl-ca-certificate-install`。
-
-运行此实用程序可添加证书链进行 S/MIME 提交签名验证。 更多信息请参阅“[关于提交签名验证](/enterprise/{{ currentVersion }}/user/articles/about-commit-signature-verification/)”。
-
-如果 {% data variables.product.product_location_enterprise %} 无法连接到另一台服务器的原因是后者使用自签名 SSL 证书或没有为其提供必要 CA 包的 SSL 证书,请运行此实用程序。 确认这种情况的一种方法是通过 {% data variables.product.product_location_enterprise %} 运行 `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs`。 如果可以验证远程服务器的 SSL 证书,`SSL-Session` 的返回代码应为 0,如下所示。
-
-```
-SSL-Session:
- Protocol : TLSv1
- Cipher : AES128-SHA
- Session-ID: C794EBCC3CBC10F747C9AFC029C03C1048FC99CFC34D13D7444E0F267C58DF4C
- Session-ID-ctx:
- Master-Key: 02A7C47CFD6EEC87D3C710E9DD87390E04EF82DDD7514AE03127D5DC1945FC0CAEFB5395791AEA598667EFA61B9EA8C5
- Key-Arg : None
- Start Time: 1394581597
- Timeout : 300 (sec)
- Verify return code: 0 (ok)
-```
-
-另一方面,如果*无法<0>验证远程服务器的 SSL 证书,`SSL-Session` 的返回代码应为非零值:
-
-```
-SSL-Session:
- Protocol : TLSv1
- Cipher : AES128-SHA
- Session-ID: 82CB288051A6DB66094C50A69CF1292AEE7E54C6B01B659B98AB336F8C33863E
- Session-ID-ctx:
- Master-Key: 01B025B2F764043A27919A8D1355AAECD8844FF0831B1D664042334790574A6F4025BAB085D4ED71D71AAB3091B849E5
- Key-Arg : None
- Start Time: 1394581782
- Timeout : 300 (sec)
- Verify return code: 27 (certificate not trusted)
-```
-
-您可以将以下附加选项与实用程序结合使用:
-- `-r` 标志允许您卸载 CA 证书。
-- `-h` 标志可显示更多用法信息。
-
-```shell
-ghe-ssl-ca-certificate-install -c /path/to/certificate
-```
-
-#### ghe-ssl-generate-csr
-
-此实用程序允许您生成可与商业或私有证书颁发机构共享的私钥和证书签名请求 (CSR),以获取可与您的实例配合使用的有效证书。 更多信息请参阅“[配置 TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)”。
-
-如需获取关于此命令的更多信息或附加选项,请使用 `-h` 标志。
-
-```shell
-ghe-ssl-generate-csr
-```
-
-#### ghe-storage-extend
-
-某些平台需要使用此脚本扩展用户量。 更多信息请参阅“[增加存储容量](/enterprise/admin/guides/installation/increasing-storage-capacity/)”。
-
-```shell
-$ ghe-storage-extend
-```
-
-#### ghe-version
-
-此实用程序会打印 {% data variables.product.product_location_enterprise %} 的版本、平台和内部版本号。
-
-```shell
-$ ghe-version
-```
-
-#### ghe-webhook-logs
-
-此实用程序会返回 web 挂钩交付日志,供管理员审查和确定任何问题。
-
-```shell
-ghe-webhook-logs
-```
-
-要显示过去一天所有失败的挂钩交付:
-```shell
-ghe-webhook-logs -f -a YYYYMMDD
-```
-
-要显示交付的完整挂钩有效负载、结果以及任何异常:
-```shell
-ghe-webhook-logs -g delivery-guid -v
-```
-
-要显示全局 web 挂钩交付:
-```shell
-ghe-webhook-logs --global
-```
-
-### 集群
-
-#### ghe-cluster-support-bundle
-
-此实用程序创建的支持包 tarball 包含采用 Geo-replication 或集群配置的各个节点中的重要日志。
-
-默认情况下,此命令会在 */tmp* 中创建 tarball,但为了便于通过 SSH 进行传输,您也可以通过 `cat` 将打包文件创建到 `STDOUT` 中。 在 Web UI 未响应或从 */setup/support* 下载支持包失败的情况下,您可以使用此方法。 如果要生成包含旧日志的*扩展*包,则必须使用此命令。 您还可以使用此命令将集群支持包直接上传到 {% data variables.product.prodname_enterprise %} Support。
-
-要创建标准捆绑包:
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz
-```
-
-要创建扩展捆绑包:
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz
-```
-
-要将捆绑包发送至 {% data variables.contact.github_support %}:
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -u'
-```
-
-要将捆绑包发送至 {% data variables.contact.github_support %} 并关联捆绑包与事件单:
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -t ticket-id'
-```
-
-#### ghe-dpages
-
-此实用程序可用于管理分配的 {% data variables.product.prodname_pages %} 服务器。
-
-```shell
-ghe-dpages
-```
-
-要显示仓库位置和健康状态摘要:
-```shell
-ghe-dpages status
-```
-
-要在撤出集群节点之前撤出 {% data variables.product.prodname_pages %} 存储服务:
-``` shell
-ghe-dpages evacuate pages-server-
-```
-
-#### ghe-spokes
-
-此实用程序允许您管理分布式 git 服务器上各仓库的三个副本。
-
-```shell
-ghe-spokes
-```
-
-要显示仓库位置和健康状态摘要:
-
-```shell
-ghe-spokes status
-```
-
-要显示存储仓库的服务器:
-
-```shell
-ghe-spokes route
-```
-
-要撤出集群节点上的存储服务:
-
-``` shell
-ghe-spokes server evacuate git-server-
-```
-
-#### ghe-storage
-
-此实用程序允许您在撤出集群节点之前撤出所有存储服务。
-
-``` shell
-ghe-storage evacuate storage-server-
-```
-
-### Git
-
-#### ghe-btop
-
-当前 Git 操作的类 `top` 接口。
-
-```shell
-ghe-btop [ | --help | --usage ]
-```
-
-#### ghe-repo
-
-此实用程序允许您切换到仓库的目录并以 `git` 用户身份打开交互式 shell。 您可以通过 `git-*` 或 `git-nw-*` 等命令对仓库执行手动检查或维护。
-
-```shell
-ghe-repo username/reponame
-```
-
-#### ghe-repo-gc
-
-此实用程序会手动重新打包仓库网络,以优化包存储。 如果仓库较大,运行此命令有助于减小其整体大小。 {% data variables.product.prodname_enterprise %} 会在与仓库网络交互的过程中自动运行此命令。
-
-您可以添加可选的 `--prune` 参数来移除不是从分支、标记或其他任何 ref 引用的不可达 Git 对象。 此方法特别适用于立即移除[之前泄露的敏感信息](/enterprise/user/articles/remove-sensitive-data/)。
-
-```shell
-ghe-repo-gc username/reponame
-```
-
-### 导入和导出
-
-#### ghe-migrator
-
-`ghe-migrator` 属于高保真工具,可帮助用户从一个 GitHub 实例迁移到另一个实例。 您可以整合实例或将组织、用户、团队和仓库从 GitHub.com 移至 {% data variables.product.prodname_enterprise %}。
-
-更多信息请参阅[迁移用户、组织和仓库数据](/enterprise/admin/guides/migrations/)上的指南。
-
-#### git-import-detect
-
-给定一个 URL,检测哪种类型的源控制管理系统位于另一端。 在手动导入过程中,此信息很可能是已知的,但在自动执行的脚本中非常有用。
-```shell
-git-import-detect
-```
-
-#### git-import-hg-raw
-
-此实用程序可将 Mercurial 仓库导入至此 Git 仓库。 更多信息请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)。”
-```shell
-git-import-hg-raw
-```
-
-#### git-import-svn-raw
-
-此实用程序可将 Subversion 历史记录和文件数据导入至 Git 分支。 这属于直接复制树,会忽略任何主干或分支差异。 更多信息请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)。”
-```shell
-git-import-svn-raw
-```
-
-#### git-import-tfs-raw
-
-此实用程序可从 Team Foundation Version Control 导入。 更多信息请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)。”
-```shell
-git-import-tfs-raw
-```
-
-#### git-import-rewrite
-
-此实用程序可重写导入的仓库。 这样,您将有机会重命名作者,对于 Subversion 和 TFS,可基于文件夹生成 Git 分支。 更多信息请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)。”
-```shell
-git-import-rewrite
-```
-
-### 支持
-
-#### ghe-diagnostics
-
-此实用程序会执行各项检查并收集关于安装的信息,您可以将此类信息发送给支持团队,以帮助诊断您遇到的问题。
-
-目前,此实用程序的输出与下载 {% data variables.enterprise.management_console %} 中的诊断信息类似,但会逐渐增加一些 Web UI 中未提供的其他改进。 更多信息请参阅“[创建和共享诊断文件](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)”。
-
-```shell
-ghe-diagnostics
-```
-
-#### ghe-support-bundle
-
-{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %}
-此实用程序会创建一个支持包 tarball,其中包含实例中的重要日志。
-
-默认情况下,此命令会在 */tmp* 中创建 tarball,但为了便于通过 SSH 进行传输,您也可以通过 `cat` 将打包文件创建到 `STDOUT` 中。 在 Web UI 未响应或从 */setup/support* 下载支持包失败的情况下,您可以使用此方法。 如果要生成包含旧日志的*扩展*包,则必须使用此命令。 您还可以使用此命令将支持包直接上传到 {% data variables.product.prodname_enterprise %} Support。
-
-要创建标准捆绑包:
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz
-```
-
-要创建扩展捆绑包:
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -x -o' > support-bundle.tgz
-```
-
-要将捆绑包发送至 {% data variables.contact.github_support %}:
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -u'
-```
-
-要将捆绑包发送至 {% data variables.contact.github_support %} 并关联捆绑包与事件单:
-
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -t ticket-id'
-```
-
-#### ghe-support-upload
-
-此实用程序会将您的设备中的信息发送到 {% data variables.product.prodname_enterprise %} Support。 您可以指定本地文件,或通过 `STDIN` 提供最大 100MB 的数据流。 可以选择将上传的数据与支持事件单相关联。
-
-要将文件发送至 {% data variables.contact.github_support %} 并关联文件与事件单:
-```shell
-ghe-support-upload -f path/to/your/file -t ticket-id
-```
-
-要通过 `STDIN` 上传数据并关联数据与事件单:
-```shell
-ghe-repl-status -vv | ghe-support-upload -t ticket-id -d "Verbose Replication Status"
-```
-
-在本例中,`ghe-repl-status -vv` 会发送副本设备中的 verbose 状态信息。 您应将 `ghe-repl-status -vv` 替换为要传输到 `STDIN` 的特定数据,并将 `Verbose Replication Status` 替换为数据的简单说明。 {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %}
-
-### 升级 {% data variables.product.prodname_ghe_server %}
-
-#### ghe-upgrade
-
-此实用程序会安装或验证升级包。 如果升级失败或中断,您还可以使用此实用程序回滚补丁版本。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}”](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)。
-
-要验证升级包:
-```shell
-ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME
-```
-
-要安装升级包:
-```shell
-ghe-upgrade UPGRADE-PACKAGE-FILENAME
-```
-
-{% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
-
-#### ghe-upgrade-scheduler
-
-此实用程序可以管理已排定的升级包安装。 您可以显示、新建或移除已排定的安装。 您必须使用 cron 表达式创建日程。 更多信息请参阅 [Cron 维基百科词条](https://en.wikipedia.org/wiki/Cron#Overview)。
-
-要安排新的包安装:
-```shell
-$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME
-```
-
-要显示已安排的包安装:
-```shell
-$ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME
-> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s UPGRADE-PACKAGE-FILENAME > /data/user/common/UPGRADE-PACKAGE-FILENAME.log 2>&1
-```
-
-要删除已安排的包安装:
-```shell
-$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME
-```
-
-#### ghe-update-check
-
-此实用程序将检查 {% data variables.product.prodname_enterprise %} 是否有新的补丁版本可用。 如果有新的补丁版本,并且实例中有可用空间,系统将下载此包。 默认情况下,包会保存到 */var/lib/ghe-updates*。 管理员随后可[执行升级](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/)。
-
-包含下载状态的文件位于 */var/lib/ghe-updates/ghe-update-check.status*。
-
-要查看最新的 {% data variables.product.prodname_enterprise %} 版本,请使用 `-i` 开关。
-
-```shell
-$ ssh -p 122 admin@hostname -- 'ghe-update-check'
-```
-
-### 用户管理
-
-#### ghe-license-usage
-
-此实用程序可按 JSON 格式导出安装用户列表。 如果您的实例连接至 {% data variables.product.prodname_ghe_cloud %},{% data variables.product.prodname_ghe_server %} 将使用此信息向 {% data variables.product.prodname_ghe_cloud %} 报告许可信息。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接至 {% data variables.product.prodname_ghe_cloud %} ](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)。”
-
-默认情况下,生成的 JSON 文件中的用户列表为加密格式。 使用 `-h` 标志可获取更多选项。
-
-```shell
-ghe-license-usage
-```
-
-#### ghe-org-membership-update
-
-此实用程序将对您的实例中的所有成员强制实施默认的组织成员关系可见性设置。 更多信息请参阅“[配置组织成员关系的可见性](/enterprise/{{ currentVersion }}/admin/guides/user-management/configuring-visibility-for-organization-membership)”。设置选项为 `public` 或 `private`。
-
-```shell
-ghe-org-membership-update --visibility=SETTING
-```
-
-#### ghe-user-csv
-
-此实用程序可将所有安装用户列表导出为 CSV 格式。 CSV 文件包含电子邮件地址、用户所属类型(例如管理员、用户)、用户拥有的仓库数量、SSH 密钥数量、组织成员关系数量、上次登录的 IP 地址等。 使用 `-h` 标志可获取更多选项。
-
-```shell
-ghe-user-csv -o > users.csv
-```
-
-#### ghe-user-demote
-
-此实用程序会将指定用户从管理员状态降级为普通用户状态。 建议使用 Web UI 执行此操作,但会在 `ghe-user-promote` 实用程序运行出错并且需要再次通过 CLI 将用户降级的情况下提供此实用程序。
-
-```shell
-ghe-user-demote some-user-name
-```
-
-#### ghe-user-promote
-
-此实用程序会将指定用户帐户升级为站点管理员。
-
-```shell
-ghe-user-promote some-user-name
-```
-
-#### ghe-user-suspend
-
-此实用程序会挂起指定用户,避免他们登录、推送或从仓库拉取。
-
-```shell
-ghe-user-suspend some-user-name
-```
-
-#### ghe-user-unsuspend
-
-此实用程序会取消挂起指定用户,向他们授予登录、推送以及从仓库拉取的权限。
-
-```shell
-ghe-user-unsuspend some-user-name
-```
diff --git a/translations/zh-CN/content/admin/installation/configuring-a-hostname.md b/translations/zh-CN/content/admin/installation/configuring-a-hostname.md
deleted file mode 100644
index d552b3040f3c..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-a-hostname.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: 配置主机名
-intro: 我们建议为您的设备设置主机名,不建议使用硬编码 IP 地址。
-redirect_from:
- - /enterprise/admin/guides/installation/configuring-hostnames/
- - /enterprise/admin/installation/configuring-a-hostname
-versions:
- enterprise-server: '*'
----
-
-如果配置的是主机名,而不是硬编码 IP 地址,您将能够更改运行 {% data variables.product.product_location_enterprise %} 的物理硬件,而不会影响用户或客户端软件。
-
-{% data variables.enterprise.management_console %} 中的主机名设置应设置为合适的完全限定域名 (FQDN),此域名可在互联网上或您的内部网络内解析。 例如,您的主机名设置可以是 `github.companyname.com`。我们还建议为选定的主机名启用子域隔离,以缓解多种跨站点脚本样式漏洞。 更多关于主机名设置的信息,请参阅 [HTTP RFC 的第 2.1 节](https://tools.ietf.org/html/rfc1123#section-2)。
-
-{% data reusables.enterprise_installation.changing-hostname-not-supported %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.hostname-menu-item %}
-4. 输入想要为 {% data variables.product.product_location_enterprise %} 设置的主机名。 ![用于设置主机名的字段](/assets/images/enterprise/management-console/hostname-field.png)
-5. 要测试新主机名的 DNS 和 SSL 设置,请单击 **Test domain settings**。 ![测试域设置按钮](/assets/images/enterprise/management-console/test-domain-settings.png)
-{% data reusables.enterprise_management_console.test-domain-settings-failure %}
-{% data reusables.enterprise_management_console.save-settings %}
-
-配置完主机名后,建议为 {% data variables.product.product_location_enterprise %} 启用子域隔离。 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。
diff --git a/translations/zh-CN/content/admin/installation/configuring-an-outbound-web-proxy-server.md b/translations/zh-CN/content/admin/installation/configuring-an-outbound-web-proxy-server.md
deleted file mode 100644
index 58a31b7c475c..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-an-outbound-web-proxy-server.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 配置出站 Web 代理服务器
-intro: '代理服务器为 {% data variables.product.product_location_enterprise %} 额外提供了一级安全性。'
-redirect_from:
- - /enterprise/admin/guides/installation/configuring-a-proxy-server/
- - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server
-versions:
- enterprise-server: '*'
----
-
-为 {% data variables.product.product_location_enterprise %} 启用代理服务器后,除非已将目标主机添加为 HTTP 代理排除项,否则会先通过代理服务器发送由 {% data variables.product.prodname_ghe_server %} 发送的出站消息。 出站消息类型包括传出 web 挂钩、上传包和提取旧头像。 代理服务器的 URL 为协议、域或 IP 地址外加端口号,例如 `http://127.0.0.1:8123`。
-
-{% note %}
-
-**注**:要将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %},您的代理配置必须允许连接到 `github.com` 和 `api.github.com`。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)”。
-
-{% endnote %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-4. 在 **HTTP Proxy Server** 下,输入代理服务器的 URL。 ![用于输入 HTTP 代理服务器 URL 的字段](/assets/images/enterprise/management-console/http-proxy-field.png)
-5. 或者在 **HTTP Proxy Exclusion** 下输入不需要进行代理访问的任意主机,并以逗号分隔主机。 ![输入任何 HTTP 代理排除项的字段](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png)
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/installation/configuring-applications.md b/translations/zh-CN/content/admin/installation/configuring-applications.md
deleted file mode 100644
index 6b0fbc5a0856..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-applications.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: 配置应用程序
-intro: '您可以为 {% data variables.product.product_location_enterprise %} 配置内部应用程序设置。'
-redirect_from:
- - /enterprise/admin/installation/configuring-applications
-versions:
- enterprise-server: '*'
----
-
-### 调整图像缓存
-
-您可以选择 {% data variables.product.product_location_enterprise %} 缓存头像的时长。 如果您增加缓存时间,则会增加加载用户头像所需的时长。 将缓存时间值配置为过小的值会导致 {% data variables.product.product_location_enterprise %} 工作进程过载。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-3. 在左侧边栏中,单击 **Applications**。 ![设置侧边栏中的 Applications 选项卡](/assets/images/enterprise/management-console/sidebar-applications.png)
-4. 在“Avatar image cache time (seconds)(头像图像缓存时间(秒))”下,输入希望 {% data variables.product.product_location_enterprise %} 缓存头像图像的秒数。 ![头像图像缓存表单字段](/assets/images/enterprise/management-console/add-image-caching-value-field.png)
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/installation/configuring-backups-on-your-appliance.md b/translations/zh-CN/content/admin/installation/configuring-backups-on-your-appliance.md
deleted file mode 100644
index 97e5d18b21d9..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-backups-on-your-appliance.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: 在设备上配置备份
-redirect_from:
- - /enterprise/admin/categories/backups-and-restores/
- - /enterprise/admin/articles/backup-and-recovery/
- - /enterprise/admin/articles/backing-up-github-enterprise/
- - /enterprise/admin/articles/restoring-github-enterprise/
- - /enterprise/admin/articles/backing-up-repository-data/
- - /enterprise/admin/articles/restoring-enterprise-data/
- - /enterprise/admin/articles/restoring-repository-data/
- - /enterprise/admin/articles/backing-up-enterprise-data/
- - /enterprise/admin/guides/installation/backups-and-disaster-recovery/
- - /enterprise/admin/installation/configuring-backups-on-your-appliance
-intro: '作为灾难恢复计划的一部分,您可以通过配置自动备份的方式保护 {% data variables.product.product_location_enterprise %} 中的生产数据。'
-versions:
- enterprise-server: '*'
----
-
-### 关于 {% data variables.product.prodname_enterprise_backup_utilities %}
-
-{% data variables.product.prodname_enterprise_backup_utilities %} 是在单独主机上安装的备份系统,会通过安全的 SSH 网络连接定期生成 {% data variables.product.product_location_enterprise %} 的备份快照。 您可以使用快照将现有的 {% data variables.product.prodname_ghe_server %} 实例从备份主机还原为上一个状态。
-
-只有自上一个快照之后添加的数据将通过网络传输并占用额外的物理存储空间。 要最大限度地减小对性能的影响,会以最低 CPU/IO 优先级在线执行备份。 您不需要排定维护窗口来执行备份。
-
-更多关于功能、要求和高级用法的详细信息,请参阅 [{% data variables.product.prodname_enterprise_backup_utilities %} 自述文件](https://github.com/github/backup-utils#readme)。
-
-### 基本要求
-
-要使用 {% data variables.product.prodname_enterprise_backup_utilities %},您必须将 Linux 或 Unix 主机系统与 {% data variables.product.product_location_enterprise %} 分开。
-
-您还可以将 {% data variables.product.prodname_enterprise_backup_utilities %} 集成到现有环境中,以便长期、永久地存储重要数据。
-
-建议将备份主机和 {% data variables.product.product_location_enterprise %} 放置在相距较远的位置。 这样可以确保在主要站点发生重大事故或网络故障的情况下通过备份进行还原。
-
-物理存储要求将因 Git 仓库磁盘使用情况以及预计的增长情况而异:
-
-| 硬件 | 建议 |
-| -------- | ----------------- |
-| **vCPU** | 2 |
-| **内存** | 2 GB |
-| **存储器** | 等于为主要实例分配的存储空间的五倍 |
-
-根据您的使用情况(例如用户活动和选定的集成),可能需要更多资源。
-
-### 安装 {% data variables.product.prodname_enterprise_backup_utilities %}
-
-{% note %}
-
-**注**:为确保还原的设备立即可用,即使采用 Geo-replication 配置,也应针对主要实例执行备份。
-
-{% endnote %}
-
-1. 下载最新的 [{% data variables.product.prodname_enterprise_backup_utilities %} 版本](https://github.com/github/backup-utils/releases)并使用 `tar` 命令解压文件。
- ```shell
- $ tar -xzvf /path/to/github-backup-utils-vMAJOR.MINOR.PATCH.tar.gz
- ```
-2. 将包含的 `backup.config-example` 文件复制到 `backup.config`,并在编辑器中打开。
-3. 将 `GHE_HOSTNAME` 值设为主要 {% data variables.product.prodname_ghe_server %} 实例的主机名或 IP 地址。
-4. 将 `GHE_DATA_DIR` 值设为您希望存储备份快照的文件系统位置。
-5. 打开主要实例的设置页面(网址为 `https://HOSTNAME/setup/settings`),并将备份主机的 SSH 密钥添加到已授权 SSH 密钥列表中。 更多信息请参阅[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)。
-5. 使用 `ghe-host-chec` 命令确认与 {% data variables.product.product_location_enterprise %} 的 SSH 连接。
- ```shell
- $ bin/ghe-host-check
- ```
- 6. 要创建初次完整备份,请运行 `ghe-backup` 命令。
- ```shell
- $ bin/ghe-backup
- ```
-
-有关高级用法的更多信息,请参阅 [{% data variables.product.prodname_enterprise_backup_utilities %} 自述文件](https://github.com/github/backup-utils#readme)。
-
-### 排定备份
-
-您可以使用 `cron(8)` 命令或类似的命令排定服务在备份主机上排定定期备份。 配置的备份频率将决定您的恢复计划中的最坏情况恢复点目标 (RPO)。 例如,如果您已排定在每天午夜运行备份,则在发生灾难的情况下,可能丢失长达 24 小时的数据。 建议在开始时采用每小时备份日程,从而确保在主要站点数据受到破坏时,最坏情况下最多会丢失一小时的数据。
-
-如果备份尝试重复,`ghe-backup` 命令将中止并显示错误消息,指示存在同时备份。 如果出现这种情况,建议降低已排定的备份的频率。 更多信息请参阅 [{% data variables.product.prodname_enterprise_backup_utilities %} 自述文件](https://github.com/github/backup-utils#scheduling-backups)的“排定备份”部分。
-
-### 还原备份
-
-如果主要站点发生的故障或灾难性事件的时间较长,要还原 {% data variables.product.product_location_enterprise %},请提供另一个 {% data variables.product.prodname_enterprise %} 设备并从备份主机执行还原。 在还原设备之前,您必须将备份主机的 SSH 密钥作为已授权 SSH 密钥添加到目标 {% data variables.product.prodname_enterprise %} 设备。
-
-要通过上一个成功快照还原 {% data variables.product.product_location_enterprise %},请使用 `ghe-restore` 命令。 您看到的输出应类似于:
-
-```shell
-$ ghe-restore -c 169.154.1.1
-> Checking for leaked keys in the backup snapshot that is being restored ...
-> * No leaked keys found
-> Connect 169.154.1.1:122 OK (v2.9.0)
-
-> WARNING: All data on GitHub Enterprise appliance 169.154.1.1 (v2.9.0)
-> will be overwritten with data from snapshot 20170329T150710.
-> Please verify that this is the correct restore host before continuing.
-> Type 'yes' to continue: yes
-
-> Starting restore of 169.154.1.1:122 from snapshot 20170329T150710
-# ...output truncated
-> Completed restore of 169.154.1.1:122 from snapshot 20170329T150710
-> Visit https://169.154.1.1/setup/settings to review appliance configuration.
-```
-
-{% note %}
-
-**注**:网络设置不包含在备份快照中。 您必须根据环境的要求在目标 {% data variables.product.prodname_ghe_server %} 设备上手动配置网络。
-
-{% endnote %}
-
-您可以将以下附加选项与 `ghe-restore` 命令结合使用:
-- `-c` 标志会重写目标主机上的设置、证书和许可数据,即使已配置也不例外。 如果您要为测试设置暂存实例,并且希望在目标设备上保留现有配置,请省略此标志。 更多信息请参阅 [{% data variables.product.prodname_enterprise_backup_utilities %} 自述文件](https://github.com/github/backup-utils#using-the-backup-and-restore-commands)的“使用备份和还原命令”部分。
-- `-s` 标志允许您选择其他备份快照。
-
diff --git a/translations/zh-CN/content/admin/installation/configuring-built-in-firewall-rules.md b/translations/zh-CN/content/admin/installation/configuring-built-in-firewall-rules.md
deleted file mode 100644
index 074b60347978..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-built-in-firewall-rules.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: 配置内置防火墙规则
-intro: '您可以查看默认防火墙规则并自定义 {% data variables.product.product_location_enterprise %} 的规则。'
-redirect_from:
- - /enterprise/admin/guides/installation/configuring-firewall-settings/
- - /enterprise/admin/installation/configuring-built-in-firewall-rules
-versions:
- enterprise-server: '*'
----
-
-### 关于 {% data variables.product.product_location_enterprise %} 的防火墙
-
-{% data variables.product.prodname_ghe_server %} 在虚拟设备上使用 Ubuntu 的简单防火墙 (UFW)。 更多信息请参阅 Ubuntu 文档中的“[UFW](https://help.ubuntu.com/community/UFW)”。 {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release.
-
-安装 {% data variables.product.prodname_ghe_server %} 之后,所有必要的网络端口都会自动打开,以接受连接。 每个非必要的端口都会自动配置为 `deny`,默认传出策略会配置为 `allow`。 会为任何新连接启用状态跟踪;这些连接通常是 `SYN` 位置 1 的网络数据包。 更多信息请参阅“[网络端口](/enterprise/admin/guides/installation/network-ports)”。
-
-UFW 防火墙还会打开 {% data variables.product.prodname_ghe_server %} 所需的其他多个端口才能正常运行。 更多关于 UFW 规则集的信息,请参阅 [UFW 自述文件](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213)。
-
-### 查看默认防火墙规则
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. 要查看默认防火墙规则,请使用 `sudo ufw status` 命令。 您看到的输出应类似于:
- ```shell
- $ sudo ufw status
- > Status: active
- > To Action From
- > -- ------ ----
- > ghe-1194 ALLOW Anywhere
- > ghe-122 ALLOW Anywhere
- > ghe-161 ALLOW Anywhere
- > ghe-22 ALLOW Anywhere
- > ghe-25 ALLOW Anywhere
- > ghe-443 ALLOW Anywhere
- > ghe-80 ALLOW Anywhere
- > ghe-8080 ALLOW Anywhere
- > ghe-8443 ALLOW Anywhere
- > ghe-9418 ALLOW Anywhere
- > ghe-1194 (v6) ALLOW Anywhere (v6)
- > ghe-122 (v6) ALLOW Anywhere (v6)
- > ghe-161 (v6) ALLOW Anywhere (v6)
- > ghe-22 (v6) ALLOW Anywhere (v6)
- > ghe-25 (v6) ALLOW Anywhere (v6)
- > ghe-443 (v6) ALLOW Anywhere (v6)
- > ghe-80 (v6) ALLOW Anywhere (v6)
- > ghe-8080 (v6) ALLOW Anywhere (v6)
- > ghe-8443 (v6) ALLOW Anywhere (v6)
- > ghe-9418 (v6) ALLOW Anywhere (v6)
- ```
-
-### 添加自定义防火墙规则
-
-{% warning %}
-
-**警告:** 在添加自定义防火墙规则之前,请备份当前规则,以便在需要时可以重置为已知的工作状态。 如果您被锁定在服务器之外,请与 {% data variables.contact.contact_ent_support %} 联系,以重新配置原始防火墙规则。 恢复原始防火墙规则会导致服务器停机。
-
-{% endwarning %}
-
-1. 配置自定义防火墙规则。
-2. 使用`状态编号`命令检查每个新规则的状态。
- ```shell
- $ sudo ufw status numbered
- ```
-3. 要备份自定义防火墙规则,请使用 `cp` 命令将规则移至新文件。
- ```shell
- $ sudo cp -r /lib/ufw ~/ufw.backup
- ```
-
-升级 {% data variables.product.product_location_enterprise %} 后,您必须重新应用自定义防火墙规则。 我们建议您创建脚本来重新应用防火墙自定义规则。
-
-### 恢复默认防火墙规则
-
-如果更改防火墙规则后出现问题,您可以通过原始备份重置规则。
-
-{% warning %}
-
-**警告**:如果您对防火墙进行更改之前未备份原始规则,请联系 {% data variables.contact.contact_ent_support %} 获取更多帮助。
-
-{% endwarning %}
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. 要恢复之前的备份规则,请使用 `cp` 命令将规则复制到防火墙。
- ```shell
- $ sudo cp -f ~/ufw.backup/*rules /lib/ufw
- ```
-3. 使用 `systemctl` 命令重新启动防火墙。
- ```shell
- $ sudo systemctl restart ufw
- ```
-4. 使用 `ufw status` 命令确认规则已恢复为默认状态。
- ```shell
- $ sudo ufw status
- > Status: active
- > To Action From
- > -- ------ ----
- > ghe-1194 ALLOW Anywhere
- > ghe-122 ALLOW Anywhere
- > ghe-161 ALLOW Anywhere
- > ghe-22 ALLOW Anywhere
- > ghe-25 ALLOW Anywhere
- > ghe-443 ALLOW Anywhere
- > ghe-80 ALLOW Anywhere
- > ghe-8080 ALLOW Anywhere
- > ghe-8443 ALLOW Anywhere
- > ghe-9418 ALLOW Anywhere
- > ghe-1194 (v6) ALLOW Anywhere (v6)
- > ghe-122 (v6) ALLOW Anywhere (v6)
- > ghe-161 (v6) ALLOW Anywhere (v6)
- > ghe-22 (v6) ALLOW Anywhere (v6)
- > ghe-25 (v6) ALLOW Anywhere (v6)
- > ghe-443 (v6) ALLOW Anywhere (v6)
- > ghe-80 (v6) ALLOW Anywhere (v6)
- > ghe-8080 (v6) ALLOW Anywhere (v6)
- > ghe-8443 (v6) ALLOW Anywhere (v6)
- > ghe-9418 (v6) ALLOW Anywhere (v6)
- ```
diff --git a/translations/zh-CN/content/admin/installation/configuring-collectd.md b/translations/zh-CN/content/admin/installation/configuring-collectd.md
deleted file mode 100644
index 66643fb4129c..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-collectd.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: 配置 collectd
-intro: '{% data variables.product.prodname_enterprise %} 可以通过“collectd”收集数据并将数据发送到外部“collectd”服务器。 除了其他指标外,我们还会收集标准数据集,例如 CPU 利用率、内存与磁盘使用量、网络接口流量与错误,以及 VM 的总负荷。'
-redirect_from:
- - /enterprise/admin/articles/configuring-collectd/
- - /enterprise/admin/installation/configuring-collectd
-versions:
- enterprise-server: '*'
----
-
-### 设置外部 `collectd` 服务器
-
-如果您尚未设置外部 `collectd` 服务器,则需要首先进行设置,然后才能在 {% data variables.product.product_location_enterprise %} 上启用 `collectd` 转发。 您的 `collectd` 服务器运行的 `collectd` 版本不得低于 5.x。
-
-1. 登录 `collectd` 服务器。
-2. 创建或编辑 `collectd` 配置文件,以加载网络插件并为服务器和端口指令填入适当的值。 在大多数分发中,此文件位于 `/etc/collectd/collectd.conf` 中
-
-用于运行 `collectd` 服务器的示例 *collectd.conf*:
-
- LoadPlugin network
- ...
- ...
-
- Listen "0.0.0.0" "25826"
-
-
-### 在 {% data variables.product.prodname_enterprise %} 上启用 collectd 转发
-
-默认情况下,`collectd` 转发在 {% data variables.product.prodname_enterprise %} 上处于禁用状态。 请按照以下操作步骤启用并配置 `collectd` 转发:
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-1. 在日志转发设置下,选择 **Enable collectd forwarding**。
-1. 在 **Server address** 字段中,输入要将 {% data variables.product.prodname_enterprise %} 设备统计信息转发到的 `collectd` 服务器的地址。
-1. 在 **Port** 字段中,输入用于连接到 `collectd` 服务器的端口。 (默认为 25826)
-1. 在 **Cryptographic setup** 下拉菜单中,选择与 `collectd` 服务器通信的安全等级。 (无、签名数据包或加密数据包。)
-{% data reusables.enterprise_management_console.save-settings %}
-
-### 使用 `ghe-export-graphs` 导出 collectd 数据
-
-命令行工具 `ghe-export-graphs` 将导出 `collectd` 存储在 RRD 数据库中的数据。 此命令会将数据转换为 XML 格式并导出到一个 tarball (.tgz) 中。
-
-此文件的主要用途是为 {% data variables.contact.contact_ent_support %} 团队提供关于 VM 性能的数据(无需下载整个支持包), 不应包含在常规备份导出范围中,也没有对应的导入文件。 如果您联系 {% data variables.contact.contact_ent_support %},我们可能会要求您提供此数据,以便协助故障排查。
-
-#### 用法
-
-```shell
-ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz .
-```
-
-### 疑难解答
-
-#### 中央 collectd 服务器未收到数据
-
-{% data variables.product.prodname_enterprise %} 随附的 `collectd` 的版本为 5.x。`collectd` 5.x 不向后兼容 V4.x 版本系列。 中央 `collectd` 服务器的版本至少需要是 5.x 才能接受从 {% data variables.product.product_location_enterprise %} 发送的数据。
-
-要获取其他问题的帮助,请联系 {% data variables.contact.contact_ent_support %}。
diff --git a/translations/zh-CN/content/admin/installation/configuring-dns-nameservers.md b/translations/zh-CN/content/admin/installation/configuring-dns-nameservers.md
deleted file mode 100644
index 7153fae575ae..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-dns-nameservers.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: 配置 DNS 域名服务器
-intro: '在 DHCP 租约提供域名服务器时,{% data variables.product.prodname_ghe_server %} 将为 DNS 设置使用动态主机配置协议 (DHCP)。 如果域名服务器不是由动态主机配置协议 (DHCP) 租约提供,或者您需要使用特定的 DNS 设置,可以手动指定域名服务器。'
-redirect_from:
- - /enterprise/admin/guides/installation/about-dns-nameservers/
- - /enterprise/admin/installation/configuring-dns-nameservers
-versions:
- enterprise-server: '*'
----
-
-指定的域名服务器必须解析 {% data variables.product.product_location_enterprise %} 的主机名。
-
-{% data reusables.enterprise_installation.changing-hostname-not-supported %}
-
-### 使用虚拟机控制台配置域名服务器
-
-{% data reusables.enterprise_installation.open-vm-console-start %}
-2. 为实例配置域名服务器。
-{% data reusables.enterprise_installation.vm-console-done %}
-
-### 使用管理 shell 配置域名服务器
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. 要编辑域名服务器,请输入:
- ```shell
- $ sudo vim /etc/resolvconf/resolv.conf.d/head
- ```
-3. 附加任何 `nameserver` 条目,然后保存文件。
-4. 验证变更后,请保存文件。
-5. 要向 {% data variables.product.product_location_enterprise %} 添加新的域名服务器条目,请输入:
- ```shell
- $ sudo service resolvconf restart
- ```
diff --git a/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server.md b/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server.md
deleted file mode 100644
index a952457d656e..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 在 GitHub Enterprise Server 上配置 Git Large File Storage
-intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}'
-redirect_from:
- - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise/
- - /enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server.md b/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server.md
deleted file mode 100644
index 61a87bfe2624..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: 将 Git Large File Storage 配置为使用第三方服务器
-intro: '在 {% data variables.product.prodname_ghe_server %} 设备上禁用 {% data variables.large_files.product_name_short %} 并使用要存储大型资源的服务器 URL 配置 {% data variables.large_files.product_name_short %} 客户端,即可在第三方服务器上使用 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %})。'
-redirect_from:
- - /enterprise/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.large_files.storage_assets_location %}
-{% data reusables.large_files.rejected_pushes %}
-
-1. 在 {% data variables.product.prodname_ghe_server %} 设备上禁用 {% data variables.large_files.product_name_short %}。 更多信息请参阅“[配置 {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage#configuring-git-large-file-storage-for-your-appliance)”。
-
-2. 创建指向第三方服务器的 {% data variables.large_files.product_name_short %} 配置文件。
- ```shell
- # Show default configuration
- $ git lfs env
- > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
- > git version 2.7.4 (Apple Git-66)
-
- > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic)
-
- # Create .lfsconfig that points to third party server.
- $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo
- $ git lfs env
- > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
- > git version 2.7.4 (Apple Git-66)
-
- > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none)
-
- # Show the contents of .lfsconfig
- $ cat .lfsconfig
- [remote "origin"]
- lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo
- ```
-
-3. 为使各用户的 {% data variables.large_files.product_name_short %} 配置相同,请向仓库提交自定义 `.lfsconfig` 文件。
- ```shell
- $ git add .lfsconfig
- $ git commit -m "Adding LFS config file"
- ```
-3. 迁移任何现有的 {% data variables.large_files.product_name_short %} 资源。 更多信息请参阅“[迁移到其他 {% data variables.large_files.product_name_long %} 服务器](/enterprise/{{ currentVersion }}/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server)”。
-
-### 延伸阅读
-
-- "[关于 {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage/)"
-- "[配置 {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage)"
-- "[迁移到其他 {% data variables.large_files.product_name_long %} 服务器](/enterprise/{{ currentVersion }}/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server)"
-- [{% data variables.large_files.product_name_long %} 项目站点](https://git-lfs.github.com/)
diff --git a/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage.md b/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage.md
deleted file mode 100644
index ab2ac9400105..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-git-large-file-storage.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: 配置 Git Large File Storage
-intro: '安装 [{% data variables.large_files.product_name_short %}] 后 (/articles/installing-git-large-file-storage/),需要将其与仓库中的大文件相关联。'
-redirect_from:
- - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository/
- - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization/
- - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance/
- - /enterprise/admin/installation/configuring-git-large-file-storage
-versions:
- enterprise-server: '*'
----
-
-### 关于 {% data variables.large_files.product_name_long %}
-
-{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} 您可以将 {% data variables.large_files.product_name_long %} 与单一仓库、所有个人或组织仓库、{% data variables.product.product_location_enterprise %} 中的每一个仓库结合使用。 您需要先为设备启用 {% data variables.large_files.product_name_short %},然后才能为特定仓库或组织启用 {% data variables.large_files.product_name_short %}。
-
-{% data reusables.large_files.storage_assets_location %}
-{% data reusables.large_files.rejected_pushes %}
-
-更多信息请参阅“[关于 {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)”、“[大文件版本管理](/enterprise/user/articles/versioning-large-files/)”以及 [{% data variables.large_files.product_name_long %} 项目站点](https://git-lfs.github.com/)。
-
-### 为设备配置 {% data variables.large_files.product_name_long %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-4. 在“{% data variables.large_files.product_name_short %} 访问权限”下,使用下拉菜单,然后单击 **Enabled(已启用)**或 **Disabled(已禁用)**。 ![Git LFS access](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png)
-
-### 为各个仓库配置 {% data variables.large_files.product_name_long %}
-
-{% data reusables.enterprise_site_admin_settings.override-policy %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %}
-
-### 为用户帐户或组织拥有的每个仓库配置 {% data variables.large_files.product_name_long %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.search-user-or-org %}
-{% data reusables.enterprise_site_admin_settings.click-user-or-org %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %}
diff --git a/translations/zh-CN/content/admin/installation/configuring-github-enterprise-server-for-high-availability.md b/translations/zh-CN/content/admin/installation/configuring-github-enterprise-server-for-high-availability.md
deleted file mode 100644
index 47c96c15d673..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-github-enterprise-server-for-high-availability.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: 配置 GitHub Enterprise Server 以实现高可用性
-redirect_from:
- - /enterprise/admin/guides/installation/high-availability-cluster-configuration/
- - /enterprise/admin/guides/installation/high-availability-configuration/
- - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability/
- - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability
-intro: '{% data variables.product.prodname_ghe_server %} 支持高可用性操作模式,此模式设计为可在发生影响主设备的硬件故障或重大网络中断的情况下最大限度地减少服务中断。'
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/configuring-github-pages-on-your-appliance.md b/translations/zh-CN/content/admin/installation/configuring-github-pages-on-your-appliance.md
deleted file mode 100644
index a02a019a032d..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-github-pages-on-your-appliance.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: 在设备上配置 GitHub Pages
-intro: '您可以在实例上启用或禁用 {% data variables.product.prodname_pages %}。 还可以选择将 {% data variables.product.prodname_pages %} 站点设为可公开访问。'
-redirect_from:
- - /enterprise/admin/guides/installation/disabling-github-enterprise-pages/
- - /enterprise/admin/guides/installation/configuring-github-enterprise-pages/
- - /enterprise/admin/installation/configuring-github-pages-on-your-appliance
-versions:
- enterprise-server: '*'
----
-
-### 将 {% data variables.product.prodname_pages %} 设为可公开访问
-
-如果已在实例上启用私有模式,则公众无法访问在 {% data variables.product.product_location_enterprise %} 上托管的 {% data variables.product.prodname_pages %} 站点。
-
-{% warning %}
-
-**警告**:如果启用公共 {% data variables.product.prodname_pages %} 站点,则实例上每个仓库中的每一个 {% data variables.product.prodname_pages %} 站点均可由公众访问。
-
-{% endwarning %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.pages-tab %}
-4. 选择 **Public Pages**。 ![启用公共页面复选框](/assets/images/enterprise/management-console/public-pages-checkbox.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-### 在 {% data variables.product.product_location_enterprise %} 上禁用 {% data variables.product.prodname_pages %}
-
-如果为 {% data variables.product.product_location_enterprise %} 禁用了子域隔离,则还应禁用 {% data variables.product.prodname_pages %},以免遭受潜在安全漏洞的攻击。 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation)”。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.pages-tab %}
-4. 取消选择 **Enable Pages**。 ![禁用 {% data variables.product.prodname_pages %} 复选框](/assets/images/enterprise/management-console/pages-select-button.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-### 延伸阅读
-
-- "[启用私有模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-private-mode)"
diff --git a/translations/zh-CN/content/admin/installation/configuring-rate-limits.md b/translations/zh-CN/content/admin/installation/configuring-rate-limits.md
deleted file mode 100644
index b289699312c8..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-rate-limits.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: 配置速率限制
-intro: '您可以使用 {% data variables.enterprise.management_console %} 为 {% data variables.product.prodname_ghe_server %} 配置速率限制。'
-redirect_from:
- - /enterprise/admin/installation/configuring-rate-limits
-versions:
- enterprise-server: '*'
----
-
-### 为 {% data variables.product.prodname_enterprise_api %} 启用速率限制
-
-在 {% data variables.product.prodname_enterprise_api %} 上启用速率限制可以防止个别用户或未通过身份验证的用户过度使用资源。 For more information, see "[Rate Limiting](/enterprise/{{ currentVersion }}/v3/#rate-limiting)."
-
-{% note %}
-
-**注**:{% data variables.enterprise.management_console %} 列出了每种速率限制的时限(按分钟或按小时)。
-
-{% endnote %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-2. 在“Rate Limiting”下,选择 **Enable API Rate Limiting**。 ![用于启用 API 速率限制的复选框](/assets/images/enterprise/management-console/api-rate-limits-checkbox.png)
-3. 输入对每个 API 的已验证和未验证请求的限制,或者接受预先填入的默认限制。
-{% data reusables.enterprise_management_console.save-settings %}
-
-### 启用滥用率限制
-
-设置滥用率限制可保护 {% data variables.product.product_location_enterprise %} 上的整体服务等级。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-2. 在“Rate Limiting”下,选择 **Enable Abuse Rate Limiting**。 ![用于启用滥用率限制的复选框](/assets/images/enterprise/management-console/abuse-rate-limits-checkbox.png)
-3. 输入总请求限制、CPU 限制或对搜索的 CPU 限制,或接受预先填入的默认限制。
-{% data reusables.enterprise_management_console.save-settings %}
-
-### 启用 Git 速率限制
-
-您可以按仓库网络或用户 ID 应用 Git 速率限制。 Git 速率限制以每分钟并行操作数表示,不过会根据当前 CPU 负荷进行调整。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-2. 在“Rate Limiting”下,选择 **Enable Git Rate Limiting**。 ![用于启用 Git 速率限制的复选框](/assets/images/enterprise/management-console/git-rate-limits-checkbox.png)
-3. 输入对每个仓库网络或用户 ID 的限制。 ![仓库网络和用户 ID 限制的字段](/assets/images/enterprise/management-console/example-git-rate-limits.png)
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance.md b/translations/zh-CN/content/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance.md
deleted file mode 100644
index 2be6d682c3f7..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: 在设备上配置新仓库的默认可见性
-intro: '您可以将通过 {% data variables.product.prodname_ghe_server %} 设备上的 Web 界面创建的所有新仓库的默认可见性设为私有或公共。'
-redirect_from:
- - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance
-versions:
- enterprise-server: '*'
----
-
-每次有人在 {% data variables.product.product_location_enterprise %} 上创建新仓库时,此人必须为仓库选择可见性。 当您为实例配置默认可见性设置时,需要选择默认可见性。 有关仓库可见性的更多信息,请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)。”
-
-如果站点管理员不允许成员创建某种类型的仓库,成员将无法创建此类仓库,即使可见性设置默认为此类型。 更多信息请参阅“[限制在实例中创建仓库](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)”。
-
-{% tip %}
-
-**提示**:您可以将更改仓库可见性的权限仅分配给站点管理员。 更多信息请参阅“[阻止用户更改仓库可见性](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility)”。
-
-{% endnote %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-1. 在“默认仓库可见性”下,使用下拉菜单并选择默认可见性。 ![用于为实例选择默认仓库可见性的下拉菜单](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
-
-{% data reusables.enterprise_installation.image-urls-viewable-warning %}
diff --git a/translations/zh-CN/content/admin/installation/configuring-the-github-enterprise-server-appliance.md b/translations/zh-CN/content/admin/installation/configuring-the-github-enterprise-server-appliance.md
deleted file mode 100644
index 6e7e112342fe..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-the-github-enterprise-server-appliance.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: 配置 GitHub Enterprise Server 设备
-intro: '在 {% data variables.product.prodname_ghe_server %} 启动并运行后,您可以根据组织的需求对设备进行配置。'
-redirect_from:
- - /enterprise/admin/guides/installation/basic-configuration/
- - /enterprise/admin/guides/installation/administrative-tools/
- - /enterprise/admin/articles/restricting-ssh-access-to-specific-hosts/
- - /enterprise/admin/guides/installation/configuring-the-github-enterprise-appliance/
- - /enterprise/admin/installation/configuring-the-github-enterprise-server-appliance
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/zh-CN/content/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console.md
deleted file mode 100644
index 1d7f0b060406..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: 使用虚拟机控制台配置 IP 地址
-intro: '默认情况下,{% data variables.product.prodname_ghe_server %} 通过动态主机配置协议 (DHCP) 检索网络设置。 如果您的平台不支持该协议,或者 DHCP 不可用,您也可以使用虚拟机控制台配置网络设置。'
-redirect_from:
- - /enterprise/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_installation.open-vm-console-start %}
-3. 选择配置 `IPv4` 或 `IPv6` 协议。 ![用于选择 IPv4 或 IPv6 协议的选项](/assets/images/enterprise/network-configuration/IPv4-or-IPv6-protocol.png)
-4. 配置所选协议的选项。 ![含 IP 协议选项的菜单](/assets/images/enterprise/network-configuration/network-settings-selection.png)
-{% data reusables.enterprise_installation.vm-console-done %}
diff --git a/translations/zh-CN/content/admin/installation/configuring-time-synchronization.md b/translations/zh-CN/content/admin/installation/configuring-time-synchronization.md
deleted file mode 100644
index 554697d7dbb0..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-time-synchronization.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: 配置时间同步
-intro: '{% data variables.product.prodname_ghe_server %} 通过连接到 NTP 服务器自动同步其时钟。 您可以设置用于同步时钟的 NTP 服务器,也可以使用默认 NTP 服务器。'
-redirect_from:
- - /enterprise/admin/articles/adjusting-the-clock/
- - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings/
- - /enterprise/admin/articles/setting-ntp-servers/
- - /enterprise/admin/categories/time/
- - /enterprise/admin/installation/configuring-time-synchronization
-versions:
- enterprise-server: '*'
----
-
-### 更改默认 NTP 服务器
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-2. 在左侧边栏中,单击 **Time**。 ![{% data variables.enterprise.management_console %} 边栏中的 Time 按钮](/assets/images/enterprise/management-console/sidebar-time.png)
-3. 在“Primary NTP server”下,输入主 NTP 服务器的主机名。 在“Secondary NTP server”下,输入辅助 NTP 服务器的主机名。 ![{% data variables.enterprise.management_console %} 中用于主 NTP 服务器和辅助 NTP 服务器的字段](/assets/images/enterprise/management-console/ntp-servers.png)
-4. 在页面底部,单击 **Save settings**。 ![{% data variables.enterprise.management_console %} 中的 Save settings 按钮](/assets/images/enterprise/management-console/save-settings.png)
-5. 等待配置运行完毕。
-
-### 更正较大的时间偏差
-
-NTP 协议会持续更正较小的时间同步偏差。 您可以使用管理 shell 立即同步时间。
-
-{% note %}
-
-**注意:**
- - 您无法修改协调世界时 (UTC) 时区。
- - 您应阻止虚拟机监控程序设置虚拟机时钟。 更多信息请参阅虚拟化提供商提供的文档。
-
-{% endnote %}
-
-- 使用 `chronyc` 命令将服务器与配置的 NTP 服务器同步。 例如:
-
-```shell
-$ sudo chronyc -a makestep
-```
diff --git a/translations/zh-CN/content/admin/installation/configuring-tls.md b/translations/zh-CN/content/admin/installation/configuring-tls.md
deleted file mode 100644
index f672e10641c9..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-tls.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: 配置 TLS
-intro: '您可以在 {% data variables.product.product_location_enterprise %} 上配置传输层安全 (TLS),以便使用由可信证书颁发机构签名的证书。'
-redirect_from:
- - /enterprise/admin/articles/ssl-configuration/
- - /enterprise/admin/guides/installation/about-tls/
- - /enterprise/admin/installation/configuring-tls
-versions:
- enterprise-server: '*'
----
-
-### 关于传输层安全
-
-当 {% data variables.product.prodname_ghe_server %} 首次启动时,会启用 TLS(替代了 SSL)并通过自签名证书进行配置。 由于自签名证书不受 Web 浏览器和 Git 客户端的信任,因此这些客户端将报告证书警告,直至您禁用 TLS 或上传由 Let's Encrypt 等可信颁发机构签名的证书。
-
-{% data variables.product.prodname_ghe_server %} 设备将在 SSL 启用时发送 HTTP 严格传输安全标头。 禁用 TLS 会导致用户无法访问设备,因为用户的浏览器将不允许协议降级为 HTTP。 更多信息请参阅 Wikipedia 上的“[HTTP 严格传输安全 (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)”。
-
-{% data reusables.enterprise_installation.terminating-tls %}
-
-要允许用户使用 FIDO U2F 进行双重身份验证,您必须为实例启用 TLS。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。
-
-### 基本要求
-
-要在生产中使用 TLS,您必须具有由可信证书颁发机构签名的未加密 PEM 格式的证书。
-
-您的证书还需要为“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)”中列出的子域配置使用者可选名称,如果证书已由中间证书颁发机构签名,将需要包含完整的证书链。 更多信息请参阅 Wikipedia 上的“[使用者可选名称](http://en.wikipedia.org/wiki/SubjectAltName)”。
-
-您可以使用 `ghe-ssl-generate-csr` 命令为实例生成证书签名请求 (CSR)。 更多信息请参阅“[命令行实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)”。
-
-### 上传自定义 TLS 证书
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-{% data reusables.enterprise_management_console.select-tls-only %}
-4. 在“TLS Protocol support”下,选择您想要允许的协议。 ![包含用于选择 TLS 协议的选项的单选按钮](/assets/images/enterprise/management-console/tls-protocol-support.png)
-5. 在“Certificate”下,单击 **Choose File**,选择要安装的 TLS 证书或证书链(PEM 格式)。 此文件通常采用 *.pem*、*.crt* 或 *.cer* 扩展名。 ![用于查找 TLS 证书文件的按钮](/assets/images/enterprise/management-console/install-tls-certificate.png)
-6. 在“Unencrypted key”下,单击 **Choose File**,选择要安装的 TLS 密钥(PEM 格式)。 此文件通常采用 *.key* 扩展名。 ![用于查找 TLS 密钥文件的按钮](/assets/images/enterprise/management-console/install-tls-key.png)
-
- {% warning %}
-
- **警告**:您的 TLS 密钥不得包含密码。 更多信息请参阅“[将密码从密钥文件中移除](/enterprise/{{ currentVersion }}/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)”。
-
- {% endwarning %}
-{% data reusables.enterprise_management_console.save-settings %}
-
-### 关于 Let's Encrypt 支持
-
-Let's Encrypt 是公共证书颁发机构,他们使用 ACME 协议颁发受浏览器信任的免费、自动化 TLS 证书。 您可以在设备上自动获取并续订 Let's Encrypt 证书,无需手动维护。
-
-{% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
-
-在您启用通过 Let's Encrypt 自动进行 TLS 证书管理后,{% data variables.product.product_location_enterprise %} 将与 Let's Encrypt 服务器通信,以获取证书。 要续订证书,Let's Encrypt 服务器必须通过入站 HTTP 请求验证已配置域名的控制。
-
-您还可以在 {% data variables.product.product_location_enterprise %} 上使用 `ghe-ssl-acme` 命令行实用程序自动生成 Let's Encrypt 证书。 更多信息请参阅“[命令行实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)”。
-
-### 使用 Let's Encrypt 配置 TLS
-
-{% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-{% data reusables.enterprise_management_console.select-tls-only %}
-5. 选择 **Enable automation of TLS certificate management using Let's Encrypt**。 ![启用 Let's Encrypt 复选框](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
-{% data reusables.enterprise_management_console.save-settings %}
-{% data reusables.enterprise_management_console.privacy %}
-7. 单击 **Request TLS certificate**。 ![Request TLS Certificate 按钮](/assets/images/enterprise/management-console/request-tls-button.png)
-8. 单击 **Save configuration**。
diff --git a/translations/zh-CN/content/admin/installation/configuring-your-github-enterprise-server-network-settings.md b/translations/zh-CN/content/admin/installation/configuring-your-github-enterprise-server-network-settings.md
deleted file mode 100644
index b99e0752029c..000000000000
--- a/translations/zh-CN/content/admin/installation/configuring-your-github-enterprise-server-network-settings.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: 配置 GitHub Enterprise Server 网络设置
-redirect_from:
- - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl/
- - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings/
- - /enterprise/admin/articles/configuring-dns-ssl-and-subdomain-settings/
- - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings/
- - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings
-intro: '使用网络所需的 DNS 域名服务器和主机名配置 {% data variables.product.prodname_ghe_server %}。 您还可以配置代理服务器或防火墙规则。 为实现管理和用户目的,您必须允许访问某些端口。'
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/zh-CN/content/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud.md
deleted file mode 100644
index 6e06ec183b1f..000000000000
--- a/translations/zh-CN/content/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: 将 GitHub Enterprise Server 连接到 GitHub Enterprise Cloud
-intro: '启用 {% data variables.product.prodname_github_connect %} 后,您可以在 {% data variables.product.product_location_enterprise %} 与 {% data variables.product.prodname_ghe_cloud %} 之间共用特定的功能和工作流程。'
-redirect_from:
- - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/
- - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com
- - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/
- - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud
-permissions: '{% data variables.product.prodname_ghe_server %} 的站点管理员(同时也是 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者)可以启用 {% data variables.product.prodname_github_connect %}。'
-versions:
- enterprise-server: '*'
----
-
-### 关于 {% data variables.product.prodname_github_connect %}
-
-要启用 {% data variables.product.prodname_github_connect %},必须在 {% data variables.product.product_location_enterprise %} 和 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户中配置连接。
-
-要配置连接,您的代理配置必须允许连接到 `github.com` 和 `api.github.com`。 更多信息请参阅“[配置出站 Web 代理服务器](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)”。
-
-启用 {% data variables.product.prodname_github_connect %} 后,您将能够启用统一搜索和统一贡献等功能。 有关所有可用功能的更多信息,请参阅“[管理 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_ghe_cloud %} 之间的连接](/enterprise/{{ currentVersion }}/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud)”。
-
-将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_ghe_cloud %} 时,{% data variables.product.prodname_dotcom_the_website %} 上会有一条记录存储连接的相关信息:
-- {% data variables.product.prodname_ghe_server %} 许可的公钥部分
-- {% data variables.product.prodname_ghe_server %} 许可的哈希
-- {% data variables.product.prodname_ghe_server %} 许可上的客户名称
-- {% data variables.product.product_location_enterprise %} 的主机名
-- {% data variables.product.product_location_enterprise %} 的版本
-- 连接至 {% data variables.product.product_location_enterprise %} 的 {% data variables.product.prodname_dotcom_the_website %} 上的组织或企业帐户
-- {% data variables.product.product_location_enterprise %} 用于向 {% data variables.product.prodname_dotcom_the_website %} 发送请求的身份验证令牌
-
-启用 {% data variables.product.prodname_github_connect %} 也可以创建由您的 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户所拥有的 {% data variables.product.prodname_github_app %}。 {% data variables.product.prodname_ghe_server %} 使用 {% data variables.product.prodname_github_app %} 的凭据向 {% data variables.product.prodname_dotcom_the_website %} 发送请求。
-
-{% data variables.product.prodname_ghe_server %} 会存储来自 {% data variables.product.prodname_github_app %} 的凭据。 这些凭据将复制到任何高可用性或集群环境,并存储在任何备份中,包括由 {% data variables.product.prodname_enterprise_backup_utilities %} 创建的快照。
-- 有效期为一小时的身份验证令牌
-- 用于生成新的身份验证令牌的私钥
-
-启用 {% data variables.product.prodname_github_connect %} 将不允许 {% data variables.product.prodname_dotcom_the_website %} 用户对 {% data variables.product.prodname_ghe_server %} 进行更改。
-
-{% if currentVersion ver_gt "enterprise-server@2.18" %}
-For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/v4/guides/managing-enterprise-accounts)."
-{% endif %}
-### 启用 {% data variables.product.prodname_github_connect %}
-
-1. 登录到 {% data variables.product.product_location_enterprise %} 和 {% data variables.product.prodname_dotcom_the_website %}。
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-5. 在“{% data variables.product.prodname_dotcom_the_website %} is not enabled yet”下,单击 **Enable {% data variables.product.prodname_github_connect %}**。 单击 **Enable {% data variables.product.prodname_github_connect %}**,即表明您同意 {% data variables.product.prodname_enterprise %} 许可协议的 {% data variables.product.prodname_github_connect %} 附录。 ![Enable GitHub Connect 按钮](/assets/images/enterprise/business-accounts/enable-github-connect-button.png)
-6. 在要连接的企业帐户或组织旁,单击 **Connect**。 ![企业帐户或企业旁边的连接按钮](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png)
-
-### 断开 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户与 {% data variables.product.product_location_enterprise %} 的连接
-
-与 {% data variables.product.prodname_ghe_cloud %} 断开连接后,{% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} 会从企业帐户或组织中删除,{% data variables.product.product_location_enterprise %} 上存储的凭据也会删除。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-5. 在要断开连接的企业帐户或组织旁,单击 **Disable {% data variables.product.prodname_github_connect %}**。 ![企业帐户或组织名称旁的 Disable GitHub Connect 按钮](/assets/images/enterprise/business-accounts/disable-github-connect-button.png)
-6. 阅读有关断开连接的信息,并单击 **Disable {% data variables.product.prodname_github_connect %}**。 ![包含关于断开连接的警告信息和确认按钮的模式窗口](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png)
-
diff --git a/translations/zh-CN/content/admin/installation/creating-a-high-availability-replica.md b/translations/zh-CN/content/admin/installation/creating-a-high-availability-replica.md
deleted file mode 100644
index 452346c89c99..000000000000
--- a/translations/zh-CN/content/admin/installation/creating-a-high-availability-replica.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: 创建高可用性副本
-intro: 在主动/被动配置中,副本设备是主设备的冗余副本。 如果主设备发生故障,高可用性模式允许副本作为主设备运行,从而最大限度地减少服务中断。
-redirect_from:
- - /enterprise/admin/installation/creating-a-high-availability-replica
-versions:
- enterprise-server: '*'
----
-
-### 创建高可用性副本
-
-1. 在所需平台上设置新的 {% data variables.product.prodname_ghe_server %} 设备。 副本设备应镜像主设备的 CPU、RAM 和存储设置。 建议您在独立环境中安装副本设备。 底层硬件、软件和网络组件应与主设备的相应部分隔离。 如果要使用云提供商,请使用单独的区域或分区。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。
-2. 在浏览器中,导航到新副本设备的 IP 地址并上传您的 {% data variables.product.prodname_enterprise %} 许可。
-3. 设置与主设备密码匹配的管理员密码,然后继续。
-4. 单击 **Configure as Replica**。 ![包含用于将新实例配置为副本的链接的安装选项](/assets/images/enterprise/management-console/configure-as-replica.png)
-5. 在“Add new SSH key”下,输入 SSH 密钥。 ![添加 SSH 密钥](/assets/images/enterprise/management-console/add-ssh-key.png)
-6. 单击 **Add key**,然后单击 **Continue**。
-6. 使用 SSH 连接到副本设备的 IP 地址。
- ```shell
- $ ssh -p 122 admin@REPLICA IP
- ```
-7. 要为副本生成密钥对,请使用包含主设备 IP 地址的 `ghe-repl-setup` 命令,并复制该命令返回的公钥。
- ```shell
- $ ghe-repl-setup PRIMARY IP
- ```
-{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
-9. 要验证与主设备的连接并为新副本启用副本模式,请再次运行 `ghe-repl-setup`。
- ```shell
- $ ghe-repl-setup PRIMARY IP
- ```
-{% data reusables.enterprise_installation.replication-command %}
-11. 要验证各个数据存储复制通道的状态,请使用 `ghe-repl-status` 命令。
- ```shell
- $ ghe-repl-status
- ```
-
-### 创建 Geo-replication 副本
-
-此示例配置使用一个主设备和两个副本,它们位于三个不同的地理区域。 由于三个节点可以位于不同网络中,要求所有节点均可从其他所有节点到达。 必需的管理端口至少应向其他所有节点开放。 有关端口要求的更多信息,请参阅“[网络端口](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)”。
-
-1. 在第一个副本上运行 `ghe-repl-setup`,采用与创建标准双节点配置相同的方式创建第一个副本。
- ```shell
- (replica1)$ ghe-repl-setup PRIMARY IP
- (replica1)$ ghe-repl-start
- ```
-2. 创建第二个副本并使用 `ghe-repl-setup --add` 命令。 `--add` 标志可防止其覆盖现有的复制配置,并将新副本添加到配置中。
- ```shell
- (replica2)$ ghe-repl-setup --add PRIMARY IP
- (replica2)$ ghe-repl-start
- ```
-3. 默认情况下,副本被配置到同一个数据中心{% if currentVersion ver_gt "enterprise-server@2.17" %},现在将尝试从同一个数据中心中的现有节点播种{% endif %}。 为数据中心选项设置不同的值,通过这种方式为不同的数据中心配置副本。 可以随意设定特定值,只要数值彼此不同即可。 在每个节点上运行 `ghe-repl-node` 命令并指定数据中心。
-
- 在主设备上:
- ```shell
- (primary)$ ghe-repl-node --datacenter [PRIMARY DC NAME]
- ```
- 在第一个副本上:
- ```shell
- (replica1)$ ghe-repl-node --datacenter [FIRST REPLICA DC NAME]
- ```
- 在第二个副本上:
- ```shell
- (replica2)$ ghe-repl-node --datacenter [SECOND REPLICA DC NAME]
- ```
- {% tip %}
-
- **提示:**您可以同时设置 `--datacenter` 和 `--activity` 选项。
-
- {% endtip %}
-4. 活动副本节点将存储设备数据的副本并为最终用户请求提供服务。 非活动节点将存储设备数据的副本,但无法为最终用户请求提供服务。 使用 `--active` 标志启用活动模式,或使用 `--inactive` 标志启用非活动模式。
-
- 在第一个副本上:
- ```shell
- (replica1)$ ghe-repl-node --active
- ```
- 在第二个副本上:
- ```shell
- (replica2)$ ghe-repl-node --active
- ```
-5. 要应用配置,请在主设备上使用 `ghe-config-apply` 命令。
- ```shell
- (primary)$ ghe-config-apply
- ```
-
-### 为 Geo-replication 配置 DNS
-
-使用主节点和副本节点的 IP 地址配置 Geo DNS。 您还可以为主节点(例如 `primary.github.example.com`)创建 DNS CNAME,以通过 SSH 访问主节点或通过 `backup-utils` 备份主节点。
-
-要进行测试,您可以将条目添加到本地工作站的 `hosts` 文件(如 `/etc/hosts`)。 这些示例条目会将 `HOSTNAME` 的请求解析到 `replica2`。 您可以注释不同的行,以特定主机为目标。
-
-```
-# HOSTNAME
-# HOSTNAME
- HOSTNAME
-```
-
-### 延伸阅读
-
-- "[关于高可用性配置](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)"
-- "[用于复制管理的实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
-- “[关于 Geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)”
diff --git a/translations/zh-CN/content/admin/installation/disabling-git-ssh-access-on-github-enterprise-server.md b/translations/zh-CN/content/admin/installation/disabling-git-ssh-access-on-github-enterprise-server.md
deleted file mode 100644
index 48203fa351fd..000000000000
--- a/translations/zh-CN/content/admin/installation/disabling-git-ssh-access-on-github-enterprise-server.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: 在 GitHub Enterprise Server 上禁用 Git SSH 访问
-redirect_from:
- - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account/
- - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account/
- - /enterprise/admin/hidden/disabling-ssh-access-for-your-appliance/
- - /enterprise/admin/articles/disabling-ssh-access-for-your-appliance/
- - /enterprise/admin/hidden/disabling-ssh-access-for-an-organization/
- - /enterprise/admin/articles/disabling-ssh-access-for-an-organization/
- - /enterprise/admin/hidden/disabling-ssh-access-to-a-repository/
- - /enterprise/admin/articles/disabling-ssh-access-to-a-repository/
- - /enterprise/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise/
- - /enterprise/admin/installation/disabling-git-ssh-access-on-github-enterprise-server
-intro: '您可以阻止用户为 {% data variables.product.product_location_enterprise %} 上的某些仓库或所有仓库使用 Git over SSH。'
-versions:
- enterprise-server: '*'
----
-
-### 禁止对特定仓库进行 Git SSH 访问
-
-{% data reusables.enterprise_site_admin_settings.override-policy %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-1. 在“Git SSH access”下,使用下拉菜单,然后单击 **Disabled**。 ![选择了禁用选项的 Git SSH access 下拉菜单](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png)
-
-### 禁止对用户或组织拥有的所有仓库进行 Git SSH 访问
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.search-user-or-org %}
-{% data reusables.enterprise_site_admin_settings.click-user-or-org %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-7. 在“Git SSH access”下,使用下拉菜单,然后单击 **Disabled**。 然后选择 **Enforce on all repositories**。 ![选择了禁用选项的 Git SSH access 下拉菜单](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png)
-
-### 禁止对设备上的所有仓库进行 Git SSH 访问
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-7. 在“Git SSH access”下,使用下拉菜单,然后单击 **Disabled**。 然后选择 **Enforce on all repositories**。 ![选择了禁用选项的 Git SSH access 下拉菜单](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png)
diff --git a/translations/zh-CN/content/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories.md b/translations/zh-CN/content/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories.md
deleted file mode 100644
index 9dfec915f87d..000000000000
--- a/translations/zh-CN/content/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: 为仓库之间的拉取请求禁用合并冲突编辑器
-intro: '您可以在 {% data variables.product.prodname_ghe_server %} 上为基础分支和头分支位于不同仓库的拉取请求禁用合并冲突编辑器,要求用户在本地解决合并冲突。'
-redirect_from:
- - /enterprise/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories
-versions:
- enterprise-server: '*'
----
-
-要求用户在其计算机上本地解决合并冲突可以避免用户因疏忽而从分叉写入到上游仓库。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-1. 在“Conflict editor for pull requests between repositories”下,使用下拉菜单,然后单击 **Disabled**。 ![包含用于禁用合并冲突编辑器的选项的下拉菜单](/assets/images/enterprise/settings/conflict-editor-settings.png)
diff --git a/translations/zh-CN/content/admin/installation/enabling-and-scheduling-maintenance-mode.md b/translations/zh-CN/content/admin/installation/enabling-and-scheduling-maintenance-mode.md
deleted file mode 100644
index ab4a356da3bc..000000000000
--- a/translations/zh-CN/content/admin/installation/enabling-and-scheduling-maintenance-mode.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: 启用和排定维护模式
-intro: '一些标准维护程序(例如升级 {% data variables.product.product_location_enterprise %} 或还原备份)要求实例进入脱机状态才能正常使用。'
-redirect_from:
- - /enterprise/admin/maintenance-mode/
- - /enterprise/admin/categories/maintenance-mode/
- - /enterprise/admin/articles/maintenance-mode/
- - /enterprise/admin/articles/enabling-maintenance-mode/
- - /enterprise/admin/articles/disabling-maintenance-mode/
- - /enterprise/admin/guides/installation/maintenance-mode/
- - /enterprise/admin/installation/enabling-and-scheduling-maintenance-mode
-versions:
- enterprise-server: '*'
----
-
-### 关于维护模式
-
-某些操作类型要求您让 {% data variables.product.product_location_enterprise %} 进入脱机状态并将其置于维护模式:
-- 升级到新版本的 {% data variables.product.prodname_ghe_server %}
-- 增加分配给虚拟机的 CPU、内存或存储资源
-- 将数据从一台虚拟机迁移到另一台虚拟机
-- 通过 {% data variables.product.prodname_enterprise_backup_utilities %} 快照还原数据
-- 排查某些类型的关键应用程序问题
-
-我们建议您至少将维护窗口排定在 30 分钟后,以便用户提前作好准备。 排定维护窗口后,所有用户在访问站点时都会看到横幅。
-
-![关于已排定维护的最终用户横幅](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
-
-在实例进入维护模式后,所有正常 HTTP 和 Git 访问都会遭到拒绝。 Git 提取、克隆和推送操作也会被拒绝,并显示一条错误消息,指示站点暂时不可用。 在浏览器中访问该站点会显示维护页面。
-
-![维护模式启动屏幕](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
-
-### 立即启用维护模式或排定在未来的某个时间进行维护
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-2. 在 {% data variables.enterprise.management_console %} 顶部,单击 **Maintenance**。 ![Maintenance 选项卡](/assets/images/enterprise/management-console/maintenance-tab.png)
-3. 在“Enable and schedule”下,决定立即启用维护模式还是排定在未来的某个时间进行维护。
- - 要立即启用维护模式,请使用下拉菜单,然后单击 **now**。 ![包含已选择立即启用维护模式的选项的下拉菜单](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
- - 要排定在未来的某个时间进行维护,请使用下拉菜单,然后单击开始时间。 ![包含已选择排定在两小时后进行维护的选项的下拉菜单](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
-4. 选择 **Enable maintenance mode**。 ![启用或排定维护模式的复选框](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-### 通过 {% data variables.product.prodname_enterprise_api %} 排定维护模式
-
-您可以通过 {% data variables.product.prodname_enterprise_api %} 排定在其他时间或日期进行维护。 For more information, see "[Management Console](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)."
-
-### 为集群中的所有节点启用或禁用维护模式
-
-您可以通过 `ghe-cluster-maintenance` 实用程序为集群中的每个节点设置或取消设置维护模式。
-
-```shell
-$ ghe-cluster-maintenance -h
-# Shows options
-$ ghe-cluster-maintenance -q
-# Queries the current mode
-$ ghe-cluster-maintenance -s
-# Sets maintenance mode
-$ ghe-cluster-maintenance -u
-# Unsets maintenance mode
-```
diff --git a/translations/zh-CN/content/admin/installation/enabling-automatic-update-checks.md b/translations/zh-CN/content/admin/installation/enabling-automatic-update-checks.md
deleted file mode 100644
index 0f0ed14329b6..000000000000
--- a/translations/zh-CN/content/admin/installation/enabling-automatic-update-checks.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: 启用自动更新检查
-intro: '您可以启用自动更新检查,使 {% data variables.product.product_location_enterprise %} 检查和下载最新的 {% data variables.product.prodname_ghe_server %} 版本。'
-redirect_from:
- - /enterprise/admin/installation/enabling-automatic-update-checks
-versions:
- enterprise-server: '*'
----
-
-在 {% data variables.product.product_location_enterprise %} 的升级包自动下载后,您将收到一条消息,通知您可以升级 {% data variables.product.prodname_ghe_server %}。 升级包会下载到 {% data variables.product.product_location_enterprise %} 上的 `/var/lib/ghe-updates` 目录中。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)”。
-
-如果升级存在可用的热补丁,将自动下载 `.hpkg`。 在 Management Console 中,您可以选择立即安装热补丁或排定稍后安装。 更多信息请参阅“[通过热补丁升级](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)”。
-
-{% tip %}
-
-**提示**:要启用自动更新检查,{% data variables.product.product_location_enterprise %} 必须能够连接到 `https://github-enterprise.s3.amazonaws.com`。
-
-{% endtip %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.updates-tab %}
-4. 单击 **Yes, automatically check for updates**。 ![启用自动更新的按钮](/assets/images/enterprise/management-console/enable_updates_button.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-要查看您的实例是否处于最新状态,请检查 Updates 选项卡上的横幅。
-
-![指示您的 GitHub Enterprise Server 版本的横幅](/assets/images/enterprise/management-console/up-to-date-banner.png)
-
-在 **Logs** 下,您可以看到最近的更新检查的状态。
-
-![更新日志](/assets/images/enterprise/management-console/update-log.png)
diff --git a/translations/zh-CN/content/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/zh-CN/content/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
deleted file mode 100644
index aadae973d2e1..000000000000
--- a/translations/zh-CN/content/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: 在 GitHub Enterprise Server 与 GitHub Enterprise Cloud 之间启用自动用户许可同步
-intro: '您可以将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_ghe_cloud %},并允许 {% data variables.product.prodname_ghe_server %} 将用户许可信息上传到 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户。'
-permissions: '{% data variables.product.prodname_ghe_server %} 的站点管理员(同时也是已连接 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者)可以启用自动用户许可同步。'
-redirect_from:
- - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
-versions:
- enterprise-server: '*'
----
-
-### 关于许可同步
-
-After you enable license synchronization, you'll be able to view license usage for your entire enterprise account, across {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_connect %} syncs license between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly. 更多信息请参阅“[管理您的 {% data variables.product.prodname_enterprise %} 许可](/enterprise/{{currentVersion}}/admin/installation/managing-your-github-enterprise-license)。”
-
-您还可以手动将 {% data variables.product.prodname_ghe_server %} 用户许可信息上传到 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
-
-### 启用许可同步
-
-在 {% data variables.product.product_location_enterprise %} 上启用许可同步之前,您必须将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %}。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-5. 在“Server can sync user license count and usage”下,使用下拉菜单,然后选择 **Enabled**。 ![用于启用自动用户许可同步的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png)
diff --git a/translations/zh-CN/content/admin/installation/enabling-private-mode.md b/translations/zh-CN/content/admin/installation/enabling-private-mode.md
deleted file mode 100644
index b056deb61569..000000000000
--- a/translations/zh-CN/content/admin/installation/enabling-private-mode.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: 启用私有模式
-intro: '在私有模式下,{% data variables.product.prodname_ghe_server %} 要求每个用户必须登录才能访问安装。'
-redirect_from:
- - /enterprise/admin/articles/private-mode/
- - /enterprise/admin/guides/installation/security/
- - /enterprise/admin/guides/installation/securing-your-instance/
- - /enterprise/admin/installation/enabling-private-mode
-versions:
- enterprise-server: '*'
----
-
-如果 {% data variables.product.product_location_enterprise %} 可通过 Internet 公开访问,您必须启用私有模式。 在私有模式下,用户不能通过 `git://` 匿名克隆仓库。 如果还启用了内置身份验证,管理员必须邀请新用户在实例上创建帐户。 更多信息请参阅“[使用内置身份验证](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)”。
-
-{% data reusables.enterprise_installation.image-urls-viewable-warning %}
-
-启用私有模式后,您可以允许未验证的 Git 操作(以及对 {% data variables.product.product_location_enterprise %} 具有网络访问权限的任何人)读取已启用匿名 Git 读取权限的实例上的公共仓库代码。 更多信息请参阅“[允许管理员启用对公共仓库的匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)”。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-4. 选择 **Private mode**。 ![启用私有模式的复选框](/assets/images/enterprise/management-console/private-mode-checkbox.png)
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/zh-CN/content/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
deleted file mode 100644
index f057a669ba89..000000000000
--- a/translations/zh-CN/content/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: 为 GitHub Enterprise Server 上易受攻击的依赖项启用安全警报
-intro: '您可以将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_ghe_cloud %},并为实例仓库中易受攻击的依赖项启用安全警报。'
-permissions: '{% data variables.product.prodname_ghe_server %} 的站点管理员(同时也是已连接 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者)可以为 {% data variables.product.prodname_ghe_server %} 上的漏洞依赖项启用安全警报。'
-redirect_from:
- - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
-### About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}
-
-{% data reusables.repositories.tracks-vulnerabilities %} For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
-
-您可以将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %},然后将漏洞数据同步到实例,并在包含易受攻击的依赖项的仓库中生成安全警报。
-
-将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %} 并为易受攻击的依赖项启用安全警报后,每个小时都会将漏洞数据从 {% data variables.product.prodname_dotcom_the_website %} 同步到您的实例一次。 您还可以随时选择手动同步漏洞数据。 代码和关于代码的信息不会从 {% data variables.product.product_location_enterprise %} 上传到 {% data variables.product.prodname_dotcom_the_website %}。
-
-当 {% data variables.product.product_location_enterprise %} 接收到有关漏洞的信息时,它将识别实例中使用受影响版本依赖项的仓库,并向这些仓库中具有管理员访问权限的所有者和人员发送安全警报。 您可以自定义接收安全警报的方式。 For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/#configuring-notifications-for-security-alerts)."
-
-### 为 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项启用安全警报
-
-为 {% data variables.product.product_location_enterprise %} 上易受攻击的依赖项启用安全警报前,必须将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %}。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
-
-{% if currentVersion ver_gt "enterprise-server@2.20" %} We recommend configuring security alerts without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive security alerts as usual.{% endif %}
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-2. 在管理 shell 中,为 {% data variables.product.product_location_enterprise %} 上易受攻击的依赖项启用安全警报:
- ``` shell
-$ ghe-dep-graph-enable
-```
-3. 返回到 {% data variables.product.prodname_ghe_server %}。
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.github-connect-tab %}{% if currentVersion ver_gt "enterprise-server@2.20" %}
-5. Under "Repositories can be scanned for vulnerabilities", use the drop-down menu and select **Enabled without notifications**. Optionally, to enable alerts with notifications, select **Enabled with notifications**.{% else %}
-5. 在“Repositories can be scanned for vulnerabilities”下,使用下拉菜单,然后选择 **Enabled**。
-{% endif %}
- ![用于启用扫描仓库有无漏洞的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
-
-### 查看 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项
-
-您可以查看 {% data variables.product.product_location_enterprise %} 中的所有漏洞,然后手动同步 {% data variables.product.prodname_dotcom_the_website %} 中的漏洞数据,以更新列表。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-2. 在左侧边栏中,单击 **Vulnerabilities**。 ![站点管理员边栏中的 Vulnerabilities 选项卡](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
-3. 要同步漏洞数据,请单击 **Sync Vulnerabilities now**。 ![Sync vulnerabilities now 按钮](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
diff --git a/translations/zh-CN/content/admin/installation/enabling-subdomain-isolation.md b/translations/zh-CN/content/admin/installation/enabling-subdomain-isolation.md
deleted file mode 100644
index a549d0bfcd59..000000000000
--- a/translations/zh-CN/content/admin/installation/enabling-subdomain-isolation.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: 启用子域隔离
-intro: '您可以设置子域隔离,将用户提供的内容与 {% data variables.product.prodname_ghe_server %} 设备的其他部分安全地隔离。'
-redirect_from:
- - /enterprise/admin/guides/installation/about-subdomain-isolation/
- - /enterprise/admin/installation/enabling-subdomain-isolation
-versions:
- enterprise-server: '*'
----
-
-### 关于子域隔离
-
-子域隔离可以减少跨站脚本和其他相关漏洞。 更多信息请参阅 Wikipedia 上的“[跨站脚本](http://en.wikipedia.org/wiki/Cross-site_scripting)”。 我们强烈建议在 {% data variables.product.product_location_enterprise %} 上启用子域隔离。
-
-启用子域隔离后,{% data variables.product.prodname_ghe_server %} 会以子域替代多个路径。
-
-| 未使用子域隔离的路径 | 使用子域隔离的路径 |
-| ------------------------------ | ------------------------------ |
-| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
-| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
-| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
-| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
-| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
-| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
-| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
-| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
-| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
-| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
-
-### 基本要求
-
-{% data reusables.enterprise_installation.disable-github-pages-warning %}
-
-启用子域隔离之前,您必须为新域配置网络设置。
-
-- 指定有效域名作为主机名,而不是指定 IP 地址。 更多信息请参阅“[配置主机名](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)。”
-
-{% data reusables.enterprise_installation.changing-hostname-not-supported %}
-
-- 为上文列出的子域设置通配符域名系统 (DNS) 记录或单独的 DNS 记录。 建议为指向您的服务器 IP 地址的 `*.HOSTNAME` 创建一条 A 记录,从而无需为各个子域创建多条记录。
-- 为 `*.HOSTNAME` 获取一个使用者可选名称 (SAN) 同时适用于 `HOSTNAME` 和通配符域 `*.HOSTNAME` 的通配符传输层安全 (TLS) 证书。 例如,如果您的主机名为 `github.octoinc.com`,则获取一个通用名值设为 `*.github.octoinc.com`、SAN 值同时设为 `github.octoinc.com` 和 `*.github.octoinc.com` 的证书。
-- 在设备上启用 TLS。 更多信息请参阅“[配置 TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)”。
-
-### 启用子域隔离
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.hostname-menu-item %}
-4. 选择 **Subdomain isolation (recommended)**。 ![启用子域隔离的复选框](/assets/images/enterprise/management-console/subdomain-isolation.png)
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/zh-CN/content/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
deleted file mode 100644
index 006896fa3595..000000000000
--- a/translations/zh-CN/content/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: 在 GitHub Enterprise Server 与 GitHub.com 之间启用统一贡献
-intro: '启用 {% data variables.product.prodname_github_connect %} 后,您可以允许 {% data variables.product.prodname_ghe_cloud %} 成员向其 {% data variables.product.prodname_dotcom_the_website %} 个人资料发送贡献计数,以突出显示他们在 {% data variables.product.prodname_ghe_server %} 上的工作。'
-redirect_from:
- - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/
- - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/
- - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/
- - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
-permissions: '{% data variables.product.prodname_ghe_server %} 的站点管理员(同时也是已连接 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者)可以在 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_dotcom_the_website %} 之间启用统一贡献。'
-versions:
- enterprise-server: '*'
----
-
-作为站点管理员,您可以允许最终用户将进行过匿名处理的工作贡献计数从 {% data variables.product.prodname_ghe_server %} 发送到其 {% data variables.product.prodname_dotcom_the_website %} 贡献图。
-
-启用 {% data variables.product.prodname_github_connect %} 并在两个环境中启用 {% data variables.product.prodname_unified_contributions %} 后,实例上的最终用户可以连接到其 {% data variables.product.prodname_dotcom_the_website %} 帐户并将贡献计数从 {% data variables.product.prodname_ghe_server %} 发送至 {% data variables.product.prodname_dotcom_the_website %}。 {% data reusables.github-connect.sync-frequency %} 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 贡献发送至 {% data variables.product.prodname_dotcom_the_website %} 个人资料](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile/)”。
-
-如果站点管理员禁用功能或开发者选择退出连接,{% data variables.product.prodname_ghe_server %} 贡献计数将从 {% data variables.product.prodname_dotcom_the_website %} 上删除。 如果开发者在禁用它们后重新连接其个人资料,则会恢复过去 90 天的贡献计数。
-
-{% data variables.product.prodname_ghe_server %} **仅会**发送已连接用户的贡献计数和来源 ({% data variables.product.prodname_ghe_server %}), 它不会发送有关贡献或做出该贡献的方式的任何信息。
-
-在 {% data variables.product.product_location_enterprise %} 上启用 {% data variables.product.prodname_unified_contributions %} 前,必须将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %}。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)”。
-
-{% data reusables.github-connect.access-dotcom-and-enterprise %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-4. 在“Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}”下,单击 **Request access**。 ![请求访问统一贡献选项](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png)
-5. [登录](https://enterprise.github.com/login) {% data variables.product.prodname_ghe_server %} 站点以接收其他说明。
-
-请求访问时,我们会将您重定向到 {% data variables.product.prodname_ghe_server %} 站点,以查看当前服务条款。 如果 {% data variables.product.product_location_enterprise %} 使用标准服务条款,请求会自动将您重定向到关于启用 {% data variables.product.prodname_unified_contributions %} 的说明。 如果您要使用自定义服务条款,我们会记录您的请求并联系您来设置访问权限。
diff --git a/translations/zh-CN/content/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/zh-CN/content/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
deleted file mode 100644
index 75ef6ebfb048..000000000000
--- a/translations/zh-CN/content/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: 在 GitHub Enterprise Server 与 GitHub.com 之间启用统一搜索
-intro: '启用 {% data variables.product.prodname_github_connect %} 后,您可以允许从 {% data variables.product.product_location_enterprise %} 搜索 {% data variables.product.prodname_dotcom_the_website %}。'
-redirect_from:
- - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/
- - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/
- - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/
- - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom
-permissions: '{% data variables.product.prodname_ghe_server %} 的站点管理员(同时也是已连接 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者)可以在 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_dotcom_the_website %} 之间启用统一搜索。'
-versions:
- enterprise-server: '*'
----
-
-启用统一搜索后,用户可在从 {% data variables.product.product_location_enterprise %} 进行搜索时查看 {% data variables.product.prodname_dotcom_the_website %} 上公共和私有内容的搜索结果。
-
-用户将无法从 {% data variables.product.prodname_dotcom_the_website %} 搜索 {% data variables.product.product_location_enterprise %},即使他们对这两个环境都具有访问权限。 用户只能搜索您已启用 {% data variables.product.prodname_unified_search %} 的私有仓库,并且他们可以在连接的 {% data variables.product.prodname_ghe_cloud %} 组织中访问。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/articles/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)”和“[在 {% data variables.product.prodname_ghe_server %} 帐户中启用私有 {% data variables.product.prodname_dotcom_the_website %} 仓库搜索](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)”。
-
-通过 REST 和 GraphQL API 进行搜索不包含 {% data variables.product.prodname_dotcom_the_website %} 搜索结果。 不支持在 {% data variables.product.prodname_dotcom_the_website %} 中进行高级搜索和搜索 Wiki。
-
-{% data reusables.github-connect.access-dotcom-and-enterprise %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-5. 在“Users can search {% data variables.product.prodname_dotcom_the_website %}”下,使用下拉菜单,然后单击 **Enabled**。 ![在搜索 GitHub.com 下拉菜单中启用搜索选项](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png)
-6. (可选)在“用户可以在 {% data variables.product.prodname_dotcom_the_website %} 上搜索私有仓库”下,使用下拉菜单并单击 **Enabled(启用)**。 ![在搜索 GitHub.com 下拉菜单中启用私有仓库搜索选项](/assets/images/enterprise/site-admin-settings/enable-private-search.png)
-
-### 延伸阅读
-
-- "[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)"
diff --git a/translations/zh-CN/content/admin/installation/getting-started-with-github-enterprise-server.md b/translations/zh-CN/content/admin/installation/getting-started-with-github-enterprise-server.md
deleted file mode 100644
index 6ae0da445cd3..000000000000
--- a/translations/zh-CN/content/admin/installation/getting-started-with-github-enterprise-server.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 开始使用 GitHub Enterprise Server
-shortTitle: 入门指南
-intro: '了解 {% data variables.product.prodname_ghe_server %} 及如何管理您的许可。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/installation/getting-started-with-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/increasing-cpu-or-memory-resources.md b/translations/zh-CN/content/admin/installation/increasing-cpu-or-memory-resources.md
deleted file mode 100644
index 53844cba287d..000000000000
--- a/translations/zh-CN/content/admin/installation/increasing-cpu-or-memory-resources.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: 增加 CPU 或内存资源
-intro: '要将 CPU 或内存资源添加到现有的 {% data variables.product.prodname_ghe_server %} 实例,请关闭实例并使用底层虚拟平台工具为虚拟机分配资源。 新分配的资源会在启动时自动识别,无需使用其他配置。'
-redirect_from:
- - /enterprise/admin/installation/increasing-cpu-or-memory-resources
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
-
-### 为 AWS 增加 CPU 或内存资源
-
-{% note %}
-
-**注**:要为 AWS 增加 CPU 或内存资源,您必须能够熟练使用 AWS 管理控制台或 `aws ec2` 命令行接口管理 EC2 实例。 有关使用您所选 AWS 工具执行调整的背景和详细信息,请参阅关于[调整 Amazon EBS 支持的实例](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html)的 AWS 文档。
-
-{% endnote %}
-
-#### 调整的考量因素
-
-在为 {% data variables.product.product_location_enterprise %} 增加 CPU 或内存资源之前:
-{% if currentVersion != "free-pro-team@latest" %}
-- **通过 CPU 扩大内存**
- {% data reusables.enterprise_installation.increasing-cpus-max %}{% endif %}
-- **验证已为实例分配弹性 IP**
-
- 如果未分配弹性 IP,则在重启后您必须调整 {% data variables.product.prodname_ghe_server %} 主机的 DNS A 记录,以反映公共 IP 地址的变更。 在实例重新启动后,如果它启动到 VPC 中,会自动保留弹性 IP (EIP)。 如果实例启动到 EC2-Classic 中,则必须手动重新关联弹性 IP。
-
-#### 支持的 AWS 实例类型
-
-您需要根据 CPU/内存规范确定升级的目标实例类型。
-{% data reusables.enterprise_installation.aws-supported-instance-types %}
-
-#### 建议的 AWS 实例类型
-
-{% data reusables.enterprise_installation.aws-recommended-instance-types %}
-
-{% data reusables.enterprise_installation.warning-on-scaling %}
-
-#### 针对 AWS 进行调整
-
-{% note %}
-
-**注**:对于启动到 EC2-Classic 中的实例,请记下与实例关联的弹性 IP 地址以及实例的 ID。 重启实例后,请重新关联弹性 IP 地址。
-
-{% endnote %}
-
-无法将 CPU 或内存资源添加到现有的 AWS/EC2 实例。 相反,您必须执行以下操作:
-
-1. 停止实例。
-2. 更改实例类型。
-3. 启动实例。
-{% data reusables.enterprise_installation.configuration-recognized %}
-
-### 为 OpenStack KVM 增加 CPU 或内存资源
-
-无法将 CPU 或内存资源添加到现有的 OpenStack KVM 实例。 相反,您必须执行以下操作:
-
-1. 生成当前实例的快照。
-2. 停止实例。
-3. 选择包含所需 CPU 和/或内存资源的新实例。
-
-### 为 VMWare 增加 CPU 或内存资源
-
-如果 {% data variables.product.product_location_enterprise %} 上的操作速度较慢,您可能需要增加 CPU 或内存资源。
-
-{% data reusables.enterprise_installation.increasing-cpus-max %}
-
-1. 使用 vSphere Client 连接到 VMware ESXi 主机。
-2. 关闭 {% data variables.product.product_location_enterprise %}。
-3. 选择虚拟机,然后单击 **Edit Settings**。
-4. 在“Hardware”下,根据需要调整分配给虚拟机的 CPU 和/或内存资源。 ![VMware 设置资源](/assets/images/enterprise/vmware/vsphere-hardware-tab.png)
-5. 要启动虚拟机,请单击 **OK**。
-{% data reusables.enterprise_installation.configuration-recognized %}
diff --git a/translations/zh-CN/content/admin/installation/increasing-storage-capacity.md b/translations/zh-CN/content/admin/installation/increasing-storage-capacity.md
deleted file mode 100644
index 4e330891c1a0..000000000000
--- a/translations/zh-CN/content/admin/installation/increasing-storage-capacity.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: 增加存储容量
-intro: 您可以增加或更改可供 Git 仓库、数据库、搜索索引和其他持久应用程序数据使用的存储容量。
-redirect_from:
- - /enterprise/admin/installation/increasing-storage-capacity
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
-
-随着更多的用户加入 {% data variables.product.product_location_enterprise %},您可能需要调整存储卷大小。 有关调整存储容量的信息,请参阅虚拟平台的相关文档。
-
-### 要求与建议
-
-{% note %}
-
-**注**:调整用户存储卷之前,请将实例置于维护模式。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
-
-{% endnote %}
-
-{% data reusables.enterprise_installation.hardware-rec-table %}
-
-### 增加数据分区大小
-
-1. 使用虚拟平台工具调整现有用户卷磁盘大小。
-{% data reusables.enterprise_installation.ssh-into-instance %}
-3. 将设备置于维护模式。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
-4. 重启设备,以检测新存储分配。
-5. 运行 `ghe-storage-extend` 命令以展开 `/data` 文件系统:
- ```shell
- $ ghe-storage-extend
- ```
-
-### 使用新设备增加根分区大小
-
-1. 使用版本与当前设备相同的较大根磁盘来设置新的 {% data variables.product.prodname_ghe_server %} 实例。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。
-2. 关闭当前设备。
-3. 使用虚拟平台工具将数据磁盘从当前设备中拆下。
-4. 将数据磁盘安装到根磁盘较大的新设备上。
-
-### 使用现有设备增加根分区大小
-
-1. 将新磁盘连接到 {% data variables.product.prodname_ghe_server %} 设备。
-2. 运行 `parted` 命令,将磁盘格式化:
- ```shell
- $ sudo parted /dev/xvdg mklabel msdos
- $ sudo parted /dev/xvdg mkpart primary ext4 0% 50%
- $ sudo parted /dev/xvdg mkpart primary ext4 50% 100%
- ```
-3. 运行 `ghe-upgrade` 命令,将完整的平台特定包安装到新分区的磁盘中。 `github-enterprise-2.11.9.hpkg` 等通用热补丁升级包将无法按预期运行。
- ```shell
- $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
- ```
-4. 关闭设备。
-5. 在虚拟机监控程序中,移除旧的根磁盘,并将新的根磁盘连接到旧的根磁盘的位置。
-6. 启动设备。
diff --git a/translations/zh-CN/content/admin/installation/initiating-a-failover-to-your-replica-appliance.md b/translations/zh-CN/content/admin/installation/initiating-a-failover-to-your-replica-appliance.md
deleted file mode 100644
index a656f96355af..000000000000
--- a/translations/zh-CN/content/admin/installation/initiating-a-failover-to-your-replica-appliance.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: 发起到副本设备的故障转移
-intro: '您可以使用命令行故障转移到 {% data variables.product.prodname_ghe_server %} 副本设备以进行维护和测试,也可以在主设备发生故障时进行故障转移。'
-redirect_from:
- - /enterprise/admin/installation/initiating-a-failover-to-your-replica-appliance
-versions:
- enterprise-server: '*'
----
-
-故障转移所需的时间取决于手动升级副本和重定向流量所需的时长。 平均时间范围为 2-10 分钟。
-
-{% data reusables.enterprise_installation.promoting-a-replica %}
-
-1. 要允许复制在切换设备之前完成,请将主设备置于维护模式:
- - 要使用 Management Console,请参阅“[启用和排定维护模式](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)”。
- - 您也可以使用 `ghe-maintenance -s` 命令。
- ```shell
- $ ghe-maintenance -s
- ```
-2. 当活动 Git 操作的数量达到零时,请等待 30 秒。
-3. 要验证所有复制通道均报告 `OK`,请使用 `ghe-repl-status -vv` 命令。
- ```shell
- $ ghe-repl-status -vv
- ```
-4. 要停止复制并将副本设备升级为主设备,请使用 `ghe-repl-promote` 命令。 此操作还会自动将主节点(若可到达)置于维护模式。
- ```shell
- $ ghe-repl-promote
- ```
-5. 将 DNS 记录更新为指向副本的 IP 地址。 流量会在经过 TTL 周期后定向到副本。 如果您要使用负载均衡器,请务必将其配置为向副本发送流量。
-6. 通知用户他们可以恢复正常操作。
-7. 如有需要,请设置从新的主设备复制到现有设备和之前的主设备。 更多信息请参阅“[关于高可用性配置](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)”。
-
-### 延伸阅读
-
-- "[用于复制管理的实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
diff --git a/translations/zh-CN/content/admin/installation/log-forwarding.md b/translations/zh-CN/content/admin/installation/log-forwarding.md
deleted file mode 100644
index af814ae49d2c..000000000000
--- a/translations/zh-CN/content/admin/installation/log-forwarding.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 日志转发
-intro: '{% data variables.product.prodname_enterprise %} 使用“syslog-ng”将系统和应用程序日志转发到您在 {% data variables.enterprise.management_console %} 设置中指定的服务器。'
-redirect_from:
- - /enterprise/admin/articles/log-forwarding/
- - /enterprise/admin/installation/log-forwarding
-versions:
- enterprise-server: '*'
----
-
-支持使用任何支持 syslog-style 日志流的日志收集系统(例如 [Logstash](http://logstash.net/) 和 [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports))。
-
-### 启用日志转发
-
-1. 在 {% data variables.enterprise.management_console %} 设置页面的左侧边栏中,单击 **Monitoring**。
-1. 选择 **Enable log forwarding**。
-1. 在 **Server address** 字段中,输入要将日志转发到的服务器的地址。 您可以在以逗号分隔的列表中指定多个地址。
-1. 在 Protocol 下拉菜单中,选择用于与日志服务器通信的协议。 该协议将应用到所有指定的日志目标。
-1. 选择 **Enable TLS**。
-1. 单击 **Choose File** 并选择用于加密 syslog 端点间通信的 CA 证书。 将对整个证书链进行验证,且证书链必须以根证书结束。 更多信息请参阅 [syslog-ng 文档中的 TLS 选项](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599)。
-
-### 疑难解答
-
-如果您遇到日志转发方面的问题,请联系 {% data variables.contact.contact_ent_support %} 并在您的电子邮件中附上 `http(s)://[hostname]/setup/diagnostics` 的输出文件。
diff --git a/translations/zh-CN/content/admin/installation/managing-billing-for-github-enterprise.md b/translations/zh-CN/content/admin/installation/managing-billing-for-github-enterprise.md
deleted file mode 100644
index 26eac155271b..000000000000
--- a/translations/zh-CN/content/admin/installation/managing-billing-for-github-enterprise.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: 管理 GitHub Enterprise 帐单
-intro: '您可以查看企业帐户和 {% data variables.product.prodname_ghe_server %} 实例的许可使用情况、发票、付款历史记录及其他帐单信息。'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
-redirect_from:
- - /enterprise/admin/installation/managing-billing-for-github-enterprise
-versions:
- enterprise-server: '*'
----
-
-### 关于企业帐户的计费
-
-企业帐户目前适用于通过发票付款的 {% data variables.product.prodname_enterprise %} 客户。 对于所有付费 {% data variables.product.prodname_dotcom_the_website %} 服务(包括组织中的付费许可、{% data variables.large_files.product_name_long %} 数据包和 {% data variables.product.prodname_marketplace %} 应用程序订阅),连接至企业帐户的所有组织和 {% data variables.product.prodname_ghe_server %} 实例的帐单都将汇总为一个计费帐单。
-
-企业所有者和帐单管理员均可访问和管理企业帐户的所有帐单设置。 有关企业帐户的更多信息,请参阅“[企业帐户的角色](/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account)”。 有关管理帐单管理员的更多信息,请参阅“[邀请人员管理企业帐户](/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account)”。
-
-### 查看当前发票
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.billing-tab %}
-4. 在“Quick Actions(快速操作)”下,单击 **View invoice(查看发票)**。 ![查看发票链接](/assets/images/help/business-accounts/view-invoice-link.png)
-
-### 支付当前发票
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.billing-tab %}
-4. 在“Quick Actions(快速操作)”下,单击 **Pay invoice(支付发票)**。 ![支付发票链接](/assets/images/help/business-accounts/pay-invoice-link.png)
-5. 在“Pay invoice(支付发票)”下,以安全形式输入您的信用卡信息,然后单击 **Pay Invoice(支付发票)**。 ![确认和支付发票](/assets/images/help/business-accounts/pay-invoice.png)
-
-### 下载当前发票
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.billing-tab %}
-4. 在“Quick Actions(快速操作)”下,单击 **Download current invoice(下载当前发票)**。 ![下载当前发票链接](/assets/images/help/business-accounts/download-current-invoice.png)
-
-### 查看付款历史记录
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.billing-tab %}
-4. 在“"Billing(帐单)”下,单击 **Past Invoices(过去的发票)**选项卡,查看过去的帐单活动摘要。 ![查看付款历史记录选项卡](/assets/images/help/business-accounts/view-payment-history.png)
diff --git a/translations/zh-CN/content/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/zh-CN/content/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md
deleted file mode 100644
index 009c7c945146..000000000000
--- a/translations/zh-CN/content/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: 管理 GitHub Enterprise Server 与 GitHub Enterprise Cloud 之间的连接
-intro: '利用 {% data variables.product.prodname_github_connect %},您可以在 {% data variables.product.product_location_enterprise %} 与 {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户之间共享某些功能和数据。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com
- - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/
- - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/
- - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/
- - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/managing-your-github-enterprise-license.md b/translations/zh-CN/content/admin/installation/managing-your-github-enterprise-license.md
deleted file mode 100644
index 3d176d466755..000000000000
--- a/translations/zh-CN/content/admin/installation/managing-your-github-enterprise-license.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: 管理 GitHub Enterprise 许可
-intro: '您可以查看、管理和更新 {% data variables.product.prodname_enterprise %} 许可。'
-redirect_from:
- - /enterprise/admin/categories/licenses/
- - /enterprise/admin/articles/license-files/
- - /enterprise/admin/installation/about-license-files/
- - /enterprise/admin/articles/downloading-your-license/
- - /enterprise/admin/installation/downloading-your-license/
- - /enterprise/admin/articles/upgrading-your-license/
- - /enterprise/admin/installation/updating-your-license/
- - /enterprise/admin/installation/managing-your-github-enterprise-server-license
- - /enterprise/admin/installation/managing-your-github-enterprise-license
-versions:
- enterprise-server: '*'
----
-
-### 关于 {% data variables.product.prodname_enterprise %} 许可
-
-购买或续订 {% data variables.product.prodname_enterprise %} 时,您会收到用于验证应用程序的许可文件。 许可文件有到期日期,而且可以控制您添加至 {% data variables.product.prodname_enterprise %} 的用户许可数量。 下载并安装 {% data variables.product.prodname_enterprise %} 后,上传许可文件会解锁应用程序供您使用。
-
-您可以将 {% data variables.product.prodname_enterprise %} 许可中包含的用户许可分配给 {% data variables.product.product_location_enterprise %} 中的用户和 {% data variables.product.prodname_ghe_cloud %} 企业帐户。 将用户添加到任一环境时,他们都会占用一个许可。 如果用户在两种环境中都有帐户,要想仅使用一个许可,其主 {% data variables.product.prodname_enterprise %} 电子邮件地址必须与经过验证的 {% data variables.product.prodname_ghe_cloud %} 电子邮件地址相同。 您可以在两种环境之间同步许可数和使用情况。
-
-如果您的 {% data variables.product.prodname_ghe_server %} 许可到期,您将无法通过 Web 浏览器或 Git 访问 {% data variables.product.product_location_enterprise %}。 需要时,您可以使用命令行实用程序备份所有数据。 更多信息请参阅“[在设备上配置备份](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)”。 如对续订许可有任何疑问,请联系 {% data variables.contact.contact_enterprise_sales %}。
-
-### 将新许可上传到 {% data variables.product.prodname_ghe_server %}
-
-从 {% data variables.contact.contact_enterprise_sales %} 购买新许可或更新现有许可后,必须下载新许可文件,然后将此文件上传至 {% data variables.product.prodname_ghe_server %},以解锁新的用户许可。
-
-如果您想续订用户许可或将其添加至 {% data variables.product.prodname_enterprise %},请联系 {% data variables.contact.contact_enterprise_sales %}。 完成订单后,您可以立即下载新的许可文件。
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.enterprise-licensing-tab %}
-4. Under "Enterprise Server Instances", click {% octicon "download" aria-label="The download icon" %} to download your license file. ![下载 GitHub Enterprise Server 许可](/assets/images/help/business-accounts/download-ghes-license.png)
-5. Log into your {% data variables.product.prodname_ghe_server %} instance as a site administrator.
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.license-tab %}
-12. 在“Quick links”下,单击 **Update license**。 ![更新许可链接](/assets/images/enterprise/business-accounts/update-license-link.png)
-13. 要选择许可,请单击 **License file(许可文件)**,或将许可文件拖到 **License file(许可文件)**上。 ![上传许可文件](/assets/images/enterprise/management-console/upload-license.png)
-14. 单击 **Upload(上传)**。 ![开始升级](/assets/images/enterprise/management-console/begin-upload.png)
-
-### 查看许可使用情况
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.enterprise-licensing-tab %}
-4. 检查您当前的 {% data variables.product.prodname_enterprise %} 许可,以及已使用和可用的用户许可。
-
-### 自动将用户许可使用情况同步到 {% data variables.product.prodname_ghe_cloud %}
-
-您可以使用 {% data variables.product.prodname_github_connect %} 在 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 之间自动同步用户许可数量和使用情况。 更多信息请参阅“[在 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_ghe_cloud %} 之间启用自动用户许可同步](/enterprise/{{currentVersion}}/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)”。
-
-### 手动同步 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_ghe_cloud %} 之间的用户许可使用情况。
-
-您可以从 {% data variables.product.prodname_ghe_server %} 下载 JSON 文件并将文件上传到 {% data variables.product.prodname_ghe_cloud %},在两个部署之间手动同步用户许可使用情况。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.license-tab %}
-5. 在“Quick links”下,要下载包含 {% data variables.product.prodname_ghe_server %} 上当前许可使用情况的文件,请单击 **Export license usage**。 ![Export license usage 链接](/assets/images/enterprise/business-accounts/export-license-usage-link.png)
-6. 导航至 {% data variables.product.prodname_ghe_cloud %}。
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.enterprise-licensing-tab %}
-10. 在“Enterprise Server Instances(Enterprise Server 实例)”下,单击 **Add server usage(添加服务器使用情况)**。 ![Upload GitHub Enterprise Servers usage 链接](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png)
-11. 上传从 {% data variables.product.prodname_ghe_server %} 下载的 JSON 文件。 ![拖放或选择要上传的文件](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png)
diff --git a/translations/zh-CN/content/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later.md b/translations/zh-CN/content/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later.md
deleted file mode 100644
index 986a7e88e86c..000000000000
--- a/translations/zh-CN/content/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-title: 将 Elasticsearch 索引迁移到 GitHub Enterprise Server 2.14 或更高版本
-intro: '要准备升级到 {% data variables.product.prodname_ghe_server %} 2.14,您需要通过迁移脚本将索引迁移到 Elasticsearch 5.6。'
-redirect_from:
- - /enterprise/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-2-14-or-later/
- - /enterprise/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-2-14-or-later
- - /enterprise/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later
-versions:
- enterprise-server: '*'
----
-
-{% data variables.product.prodname_ghe_server %} 2.14 包含 Elasticsearch 5.6 升级。从 {% data variables.product.prodname_ghe_server %} 2.12 或 2.13 升级到 2.14 或更高版本之前,我们建议您建议下载、安装并运行 Elasticsearch 迁移工具,以便在设备仍具有在线访问权限时在线迁移最大的索引。
-
-### 搜索索引
-
-迁移脚本会在设备在线时先检查任何 `search` 索引。 迁移 `search` 索引可能需要几分钟到几天,具体时长视其大小而定。 以大索引为例,需要几天的时间才能将这类索引迁移到测试环境。
-
-```
-admin@ip-172-31-2-141:~$ curl -s http://localhost:9200/_cat/indices?v | sort -n -k 6
-green open blog-1 1 0 0 0 144b 144b
-green open projects-1 1 0 0 0 144b 144b
-green open registry-packages-1 1 0 0 0 144b 144b
-green open showcases-1 1 0 0 0 144b 144b
-health status index pri rep docs.count docs.deleted store.size pri.store.size
-green open pull-requests-1 1 0 1 0 9.3kb 9.3kb
-green open wikis-1 1 0 2 0 5kb 5kb
-green open hookshot-logs-2018-05-29 5 0 25 0 124.2kb 124.2kb
-green open repos-1 1 0 1638 1 1.4mb 1.4mb
-green open gists-1 1 0 3531 64 291.9kb 291.9kb
-green open audit_log-1-2018-06-1 1 0 11108 0 3mb 3mb
-green open users-1 1 0 19866 56 2.7mb 2.7mb
-green open hookshot-logs-2018-05-31 5 0 20000 0 33.4mb 33.4mb
-green open hookshot-logs-2018-06-04 5 0 20000 0 32.6mb 32.6mb
-green open issues-1 1 0 26405 6 82.8mb 82.8mb
-green open hookshot-logs-2018-05-30 5 0 119744 0 196.8mb 196.8mb
-green open audit_log-1-2018-05-1 1 0 191664 0 50mb 50mb
-green open code-search-1 1 0 6932626 44 42.9gb 42.9gb
-green open commits-1 1 0 63753587 1485 45.4gb 45.4gb
-```
-
-`search` 索引开头为:
-
-- blog-
-- code-search-
-- commits-
-- gists-
-- issues-
-- labels-
-- marketplace-listings-
-- non-marketplace-listings-
-- projects-
-- pull-requests-
-- registry-packages-
-- repos-
-- showcases-
-- topics-
-- users-
-
-### Web 挂钩索引
-
-在迁移脚本在线重建必要的 `search` 索引后,脚本将检查是否需要重建 `webhook` 索引。 如果运行使用 {% data variables.product.prodname_ghe_server %} 2.12 或 2.13 的设备已达到 14 天或更久,那么您很可能不需要重建 `webhook` 索引,因为 `webhook` 索引的默认保留政策为七天。 如果您要从 {% data variables.product.prodname_enterprise %} 2.11 或更早版本更新设备,则可能需要重建 `webhook` 索引。
-
-如果需要重建任何 `webhook` 索引,则系统会先提示您启用维护模式,然后脚本才能重建 `webhook` 索引。 尽管迁移 `webhook` 索引需要一定的停机时间,但不需要较长的维护窗口或停机时间。
-
-`webhook` 索引以 `hookshot-logs-` 开头。
-
-### 可用索引
-
-您可以使用 curl 查看设备上的可用索引。
-
-```
-admin@ip-172-31-2-141:~$ curl -s http://localhost:9200/_cat/indices?v | sort -n -k 6
-green open blog-1 1 0 0 0 144b 144b
-green open projects-1 1 0 0 0 144b 144b
-green open registry-packages-1 1 0 0 0 144b 144b
-green open showcases-1 1 0 0 0 144b 144b
-health status index pri rep docs.count docs.deleted store.size pri.store.size
-green open pull-requests-1 1 0 1 0 9.3kb 9.3kb
-green open wikis-1 1 0 2 0 5kb 5kb
-green open hookshot-logs-2018-05-29 5 0 25 0 124.2kb 124.2kb
-green open repos-1 1 0 1638 1 1.4mb 1.4mb
-green open gists-1 1 0 3531 64 291.9kb 291.9kb
-green open audit_log-1-2018-06-1 1 0 11108 0 3mb 3mb
-green open users-1 1 0 19866 56 2.7mb 2.7mb
-green open hookshot-logs-2018-05-31 5 0 20000 0 33.4mb 33.4mb
-green open hookshot-logs-2018-06-04 5 0 20000 0 32.6mb 32.6mb
-green open issues-1 1 0 26405 6 82.8mb 82.8mb
-green open hookshot-logs-2018-05-30 5 0 119744 0 196.8mb 196.8mb
-green open audit_log-1-2018-05-1 1 0 191664 0 50mb 50mb
-green open code-search-1 1 0 6932626 44 42.9gb 42.9gb
-green open commits-1 1 0 63753587 1485 45.4gb 45.4gb
-```
-
-### 准备 {% data variables.product.prodname_ghe_server %} 2.12 或 2.13 设备
-
-如果您在不运行迁移工具的情况下升级到 {% data variables.product.prodname_ghe_server %} 2.14 或更高版本,现有的 Elasticsearch 索引可能无效并无法正常使用。 要运行 Elasticsearch 迁移脚本,您的 {% data variables.product.prodname_ghe_server %} 设备必须运行 {% data variables.product.prodname_enterprise %} 2.12 或 2.13。
-
-{% warning %}
-
-**警告:**
-- 使用 {% data variables.product.prodname_enterprise_backup_utilities %} 将在恢复后销毁不兼容 5.X 的旧 Elasticsearch 索引。 在这种情况下,可能需要手动重新编制索引。
-- 如果 {% data variables.product.prodname_ghe_server %} 配置为高可用性,迁移脚本**必须**在复制仍在进行时运行。 开始升级之前,必须允许更改才能完全复制到其他设备。 如果迁移脚本运行时复制未运行,ElasticSearch 索引可能失效。
-
-{% endwarning %}
-
-1. 使用 SSH 向启用了高可用性的主设备进行身份验证。
-2. 将迁移脚本下载到设备并进行安装:
- ```shell
- $ wget https://github-enterprise.s3.amazonaws.com/util/es-5x-transition-tools.tar.gz
- $ sudo tar -C / -xvf es-5x-transition-tools.tar.gz
- ```
- 如果您管理 {% data variables.product.prodname_ghe_server %} 集群,则使用 SSH 向其中一个 ElasticSearch 服务器节点进行身份验证,并在该节点上安装迁移工具。 节点定位方法如下:
- ```shell
- $ ghe-cluster-each -r elasticsearch -p
- ghe-test-data-0
- ghe-test-data-1
- ghe-test-data-2
- ```
-2. 运行迁移脚本:
- ```shell
- $ /usr/local/share/enterprise/ghe-es-5x-migration -r
- ```
- {% note %}
-
- **注**:如果您有要迁移的 `webhook` 索引,运行在线迁移后,系统将提示您启用维护模式。
-
- {% endnote %}
-3. 如果您要运行 {% data variables.product.prodname_ghe_server %} 集群,请遵循单 VM 或高可用性环境的官方升级文档或集群升级指南。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)”或“[升级集群](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)”。
diff --git a/translations/zh-CN/content/admin/installation/migrating-from-github-enterprise-1110x-to-2123.md b/translations/zh-CN/content/admin/installation/migrating-from-github-enterprise-1110x-to-2123.md
deleted file mode 100644
index dd4869d22b15..000000000000
--- a/translations/zh-CN/content/admin/installation/migrating-from-github-enterprise-1110x-to-2123.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: 从 GitHub Enterprise 11.10.x 迁移到 2.1.23
-redirect_from:
- - /enterprise/admin-guide/migrating/
- - /enterprise/admin/articles/migrating-github-enterprise/
- - /enterprise/admin/guides/installation/migrating-from-github-enterprise-v11-10-34x/
- - /enterprise/admin/articles/upgrading-to-a-newer-release/
- - /enterprise/admin/guides/installation/migrating-to-a-different-platform-or-from-github-enterprise-11-10-34x/
- - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23
- - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123
-intro: '要从 {% data variables.product.prodname_enterprise %} 11.10.x 迁移到 2.1.23,您需要设置新的设备实例并迁移之前实例中的数据。'
-versions:
- enterprise-server: '*'
----
-
-支持从 {% data variables.product.prodname_enterprise %} 11.10.348 及更高版本进行迁移。 不支持从 {% data variables.product.prodname_enterprise %} 11.10.348 及更低版本进行迁移。 您必须先通过多次升级过程升级到 11.10.348。 更多信息请参阅 11.10.348 升级程序“[升级到最新版本](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)”。
-
-要升级到最新版 {% data variables.product.prodname_enterprise %},您必须先迁移到 {% data variables.product.prodname_ghe_server %} 2.1,然后才能执行正常升级过程。 更多信息请参阅“[升级 {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)”。
-
-### 准备迁移
-
-1. 查看配置和安装指南,并检查在您的环境中配置 {% data variables.product.prodname_enterprise %} 2.1.23 的所有基本要求是否已得到满足。 更多信息请参阅“[配置和安装](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)”。
-2. 验证当前实例正在运行受支持的升级版本。
-3. 设置最新版本的 {% data variables.product.prodname_enterprise_backup_utilities %}。 更多信息请参阅“[{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils)”。
- - 如果已使用 {% data variables.product.prodname_enterprise_backup_utilities %} 配置排定的备份,请确保您已更新为最新版本。
- - 如果您当前未运行排定的备份,请设置 {% data variables.product.prodname_enterprise_backup_utilities %}。
-4. 使用 `ghe-backup` 命令生成当前实例的初始完整备份快照。 如果您已为当前实例配置排定的备份,则不需要生成实例快照。
-
- {% tip %}
-
- **提示**:在快照生成期间,您可以使实例保持在线激活状态。 您将在迁移的维护过程中生成另一个快照。 由于备份的递增,此初始快照会减少在最终快照中传输的数据量,从而可能缩短维护窗口。
-
- {% endtip %}
-
-5. 确定用于将用户网络流量切换到新实例的方法。 迁移完毕后,所有 HTTP 和 Git 网络流量都将定向到新实例。
- - **DNS** - 建议为所有环境使用此方法,因为此方法简单易用,即使在从一个数据中心迁移到另一个数据中心的情况下也能正常使用。 开始迁移之前,请将现有 DNS 记录的 TTL 缩减为 5 分钟或更短时间,并允许更改传播。 迁移完成后,将 DNS 记录更新为指向新实例的 IP 地址。
- - **IP 地址分配** - 此方法仅适用于 VMware 到 VMware 的迁移,除非 DNS 方法不可用,否则不建议使用此方法。 开始迁移之前,您需要关闭旧实例并将其 IP 地址分配给新实例。
-6. 排定维护窗口。 维护窗口的时间应足够长,以便将数据从备份主机传输到新实例,并根据备份快照的大小和可用网络带宽而变化。 在此期间,如果要迁移到新实例,当前实例将不可用,且处于维护模式。
-
-### 执行迁移
-
-1. 配置新的 {% data variables.product.prodname_enterprise %} 2.1 实例。 更多信息请参阅您的目标平台的“[配置和安装](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)”指南。
-2. 在浏览器中,导航到新副本设备的 IP 地址并上传您的 {% data variables.product.prodname_enterprise %} 许可。
-3. 设置管理员密码。
-5. 单击 **Migrate**。 ![选择安装类型](/assets/images/enterprise/migration/migration-choose-install-type.png)
-6. 将备份主机访问 SSH 密钥粘贴到“Add new SSH key”中。 ![授权备份](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
-7. 单击 **Add key**,然后单击 **Continue**。
-8. 复制您将在备份主机上运行的 `ghe-restore` 命令,将数据迁移到新实例。 ![开始迁移](/assets/images/enterprise/migration/migration-restore-start.png)
-9. 在旧实例上启用维护模式,并等待所有活动进程完成。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
-
- {% note %}
-
- **注**:从现在开始,此实例将无法正常使用。
-
- {% endnote %}
-
-10. 在备份主机上,运行 `ghe-backup` 命令以生成最终的备份快照。 这样可以确保捕获来自旧实例的所有数据。
-11. 在备份主机上,运行您在新实例的恢复状态屏幕上复制的 `ghe-restore` 命令以恢复最新快照。
- ```shell
- $ ghe-restore 169.254.1.1
- The authenticity of host '169.254.1.1:122' can't be established.
- RSA key fingerprint is fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1.
- Are you sure you want to continue connecting (yes/no)? yes
- Connect 169.254.1.1:122 OK (v2.0.0)
- Starting restore of 169.254.1.1:122 from snapshot 20141014T141425
- Restoring Git repositories ...
- Restoring GitHub Pages ...
- Restoring asset attachments ...
- Restoring hook deliveries ...
- Restoring MySQL database ...
- Restoring Redis database ...
- Restoring SSH authorized keys ...
- Restoring Elasticsearch indices ...
- Restoring SSH host keys ...
- Completed restore of 169.254.1.1:122 from snapshot 20141014T141425
- Visit https://169.254.1.1/setup/settings to review appliance configuration.
- ```
-
-12. 返回到新实例的恢复状态屏幕,查看恢复是否已完成。 ![恢复整个屏幕](/assets/images/enterprise/migration/restore-complete-screen.png)
-13. 单击 **Continue to settings**,检查并调整从之前的实例中导入的配置信息和设置。 ![检查导入的设置](/assets/images/enterprise/migration/migration-status-complete.png)
-14. 单击 **Save settings(保存设置)**。
-
- {% note %}
-
- **注**:您可以在应用配置设置并重新启动服务器后使用新实例。
-
- {% endnote %}
-
-15. 使用 DNS 或 IP 地址分配将用户网络流量从旧实例切换到新实例。
-16. 升级到 {{ currentVersion }} 的最新补丁版本。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)。”
diff --git a/translations/zh-CN/content/admin/installation/migrating-to-a-different-git-large-file-storage-server.md b/translations/zh-CN/content/admin/installation/migrating-to-a-different-git-large-file-storage-server.md
deleted file mode 100644
index 71d7d284e610..000000000000
--- a/translations/zh-CN/content/admin/installation/migrating-to-a-different-git-large-file-storage-server.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: 迁移到其他 Git Large File Storage 服务器
-intro: '您可以使用 {% data variables.large_files.product_name_short %} 客户端从现有服务器提取资产并将它们推送到新位置,通过这种方式迁移到新的 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 服务器。'
-redirect_from:
- - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server/
- - /enterprise/admin/installation/migrating-to-a-different-git-large-file-storage-server
-versions:
- enterprise-server: '*'
----
-
-迁移到其他 {% data variables.large_files.product_name_long %} 服务器之前,您必须将 {% data variables.large_files.product_name_short %} 配置为使用第三方服务器。 更多信息请参阅“[将 {% data variables.large_files.product_name_long %} 配置为使用第三方服务器](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server)”。
-
-1. 使用第二个远端配置仓库。
- ```shell
- $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo
-
- $ git lfs env
- > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
- > git version 2.7.4 (Apple Git-66)
-
- > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic)
- > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none)
- ```
-
-2. 从旧远端提取所有对象。
- ```shell
- $ git lfs fetch origin --all
- > Scanning for all objects ever referenced...
- > ✔ 16 objects found
- > Fetching objects...
- > Git LFS: (16 of 16 files) 48.71 MB / 48.85 MB
- ```
-
-3. 将所有对象推送到新远端。
- ```shell
- $ git lfs push NEW-REMOTE --all
- > Scanning for all objects ever referenced...
- > ✔ 16 objects found
- > Pushing objects...
- > Git LFS: (16 of 16 files) 48.00 MB / 48.85 MB, 879.10 KB skipped
- ```
diff --git a/translations/zh-CN/content/admin/installation/migrating-to-internal-repositories.md b/translations/zh-CN/content/admin/installation/migrating-to-internal-repositories.md
deleted file mode 100644
index 959cb4dcf131..000000000000
--- a/translations/zh-CN/content/admin/installation/migrating-to-internal-repositories.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: 迁移到内部仓库
-intro: '您可以迁移到内部仓库,以便为同时使用 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 的开发者统一内源体验。'
-permissions: 站点 administrator 可以迁移到内部仓库。
-redirect_from:
- - /enterprise/admin/installation/migrating-to-internal-repositories
-versions:
- enterprise-server: '>=2.20'
----
-
-### 关于内部仓库
-
-内部仓库适用于 {% data variables.product.prodname_ghe_server %} 2.20+。 {% data reusables.repositories.about-internal-repos %} 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)。”
-
-在未来版本的 {% data variables.product.prodname_ghe_server %} 中,我们将调整仓库可见性的工作方式,以便公共、内部和私有术语对 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 上的开发者具有统一的含义。
-
-要为这些变更做准备,如果您已启用私有模式,可在实例上运行迁移,将公共仓库转换为内部仓库。 此迁移目前是可选操作,可用于测试非生产实例的变更。 此迁移未来将变成强制操作。
-
-运行迁移时,实例上的组织拥有的所有公共仓库都将变成内部仓库。 如果其中任何仓库有分支,分支将变为私有。 私有仓库依然保持私有。
-
-实例上的用户帐户拥有的所有公共仓库都将变成私有仓库。 如果其中任何仓库有分支,分支也将变为私有。 每个分支的所有者将得到对分支父项的读取权限。
-
-每个变为内部或私有仓库的公共仓库都将禁用匿名 Git 读取权限。
-
-如果仓库当前的默认可见性为公共,默认值将变为内部。 如果当前默认值为私有,默认值将保持不变。 您可以随时更改默认值。 更多信息请参阅“[为设备上的新仓库配置默认可见性](/enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance)。”
-
-实例的仓库创建策略将更改为禁用公共仓库,允许私有和内部仓库。 您可以随时更新此策略。 更多信息请参阅“[限制在实例中创建仓库](/enterprise/admin/user-management/restricting-repository-creation-in-your-instance)。”
-
-如果您未启用私有模式,迁移脚本将无效。
-
-### 运行迁移
-
-1. 连接到管理 shell。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)。”
-2. 导航至 `/data/github/current` 目录。
- ```
- cd /data/github/current
- ```
-3. 运行迁移命令。
- ```
- sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb -v -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
- ```
-
-日志输出将显示在终端和 `/tmp/convert_public_ghes_repos_to_internal.log` 中。
-
-### 延伸阅读
-
-- "[启用私人模式](/enterprise/admin/installation/enabling-private-mode)"
diff --git a/translations/zh-CN/content/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance.md b/translations/zh-CN/content/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance.md
deleted file mode 100644
index 2be7b3bd4a90..000000000000
--- a/translations/zh-CN/content/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 监视 GitHub Enterprise Server 实例上的活动
-mapTopic: true
-redirect_from:
- - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/monitoring-using-snmp.md b/translations/zh-CN/content/admin/installation/monitoring-using-snmp.md
deleted file mode 100644
index 56370a4b0149..000000000000
--- a/translations/zh-CN/content/admin/installation/monitoring-using-snmp.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: 使用 SNMP 进行监视
-intro: '{% data variables.product.prodname_enterprise %} 通过 SNMP 提供关于磁盘使用情况、CPU 利用率和内存使用情况等方面的数据。'
-redirect_from:
- - /enterprise/admin/articles/monitoring-using-snmp/
- - /enterprise/admin/installation/monitoring-using-snmp
-versions:
- enterprise-server: '*'
----
-
-SNMP 是一种用于通过网络监视设备的公共标准。 强烈建议启用 SNMP,以便监视 {% data variables.product.product_location_enterprise %} 的健康状态并了解何时向主机增加更多内存、存储空间或处理器能力。
-
-{% data variables.product.prodname_enterprise %} 采用标准 SNMP 安装,因此您可以充分利用 Nagios 或其他任何监视系统可用的[多种插件](http://www.monitoring-plugins.org/doc/man/check_snmp.html)。
-
-### 配置 SNMP v2c
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.access-monitoring %}
-{% data reusables.enterprise_management_console.enable-snmp %}
-4. 在 **Community string** 字段中,输入新的社区字符串。 如果留空,此字段将默认为 `public`。 ![添加社区字符串的字段](/assets/images/enterprise/management-console/community-string.png)
-{% data reusables.enterprise_management_console.save-settings %}
-5. 要测试 SNMP 配置,请在网络中支持 SNMP 的单独工作站上运行以下命令:
- ```shell
- # community-string is your community string
- # hostname is the IP or domain of your Enterprise instance
- $ snmpget -v 2c -c community-string -O e hostname hrSystemDate.0
- ```
-
-这应该返回 {% data variables.product.product_location_enterprise %} 主机上的系统时间。
-
-### 基于用户的安全性
-
-如果您启用 SNMP v3,则可以通过用户安全模型 (USM) 充分利用提升的基于用户的安全性。 对于每个唯一的用户,您可以指定一个安全等级:
-- `noAuthNoPriv`: 此安全等级不提供任何身份验证和隐私保护。
-- `authNoPriv`: 此安全等级提供身份验证,但不提供隐私保护。 要查询设备,您需要用户名和密码(长度必须至少为八个字符)。 与 SNMPv2 相似,发送的信息不会进行加密。 身份验证协议可以是 MD5 或 SHA,默认为 SHA。
-- `authPriv`: 这个安全等级提供身份验证和隐私保护。 要求进行身份验证(包含一个长度至少为八个字符的身份验证密码),并且会对响应进行加密。 不需要隐私密码,但如果提供隐私密码,其长度必须至少为八个字符。 如果不提供隐私密码,将使用身份验证密码。 隐私协议可以是 DES 或 AES,默认为 AES。
-
-### 配置 SNMP v3 的用户
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.access-monitoring %}
-{% data reusables.enterprise_management_console.enable-snmp %}
-4. 选择 **SNMP v3**。 ![启用 SNMP v3 的按钮](/assets/images/enterprise/management-console/enable-snmpv3.png)
-5. 在“Username(用户名)”中,输入 SNMP v3 用户的唯一用户名。 ![SNMP v3 用户名输入字段](/assets/images/enterprise/management-console/snmpv3-username.png)
-6. 在 **Security Level(安全等级)**下拉菜单中,单击 SNMP v3 用户的安全等级。 ![SNMP v3 用户安全等级下拉菜单](/assets/images/enterprise/management-console/snmpv3-securitylevel.png)
-7. 对于拥有 `authnopriv` 安全等级的 SNMP v3 用户: ![Authnopriv 安全等级设置](/assets/images/enterprise/management-console/snmpv3-authnopriv.png)
- - {% data reusables.enterprise_management_console.authentication-password %}
- - {% data reusables.enterprise_management_console.authentication-protocol %}
-8. 对于拥有 `authpriv` 安全等级的 SNMP v3 用户: ![Authpriv 安全等级设置](/assets/images/enterprise/management-console/snmpv3-authpriv.png)
- - {% data reusables.enterprise_management_console.authentication-password %}
- - {% data reusables.enterprise_management_console.authentication-protocol %}
- - (可选)在“Privacy password(隐私密码)”中输入隐私保护密码。
- - 在“Privacy password(隐私密码)”右侧,在 **Protocol(协议)** 下拉菜单中,单击您要使用的隐私协议方法。
-9. 单击 **Add user(添加用户)**。 ![用于添加 SNMP v3 用户的按钮](/assets/images/enterprise/management-console/snmpv3-adduser.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-##### 查询 SNMP 数据
-
-关于您的设备的硬件和软件级信息都适用于 SNMP v3。 由于 `noAuthNoPriv` 和 `authNoPriv` 安全等级缺乏加密和隐私,因此我们的结果 SNMP 报告中不包括 `hrSWRun` 表 (1.1.3.6.1.2.1.25.41)。 如果您使用的是 `authPriv` 安全等级,我们将包括此表。
-
-如果使用 SNMP v2c,则仅会提供关于您的设备的硬件级信息。 {% data variables.product.prodname_enterprise %} 中的应用程序和服务未配置 OID 来报告指标。 有多个 MIB 可用,在网络中 SNMP 的支持下,在单独的工作站上运行 `smpwaste` 可以看到:
-
-```shell
-# community-string is your community string
-# hostname is the IP or domain of your Enterprise instance
-$ snmpwalk -v 2c -c community-string -O e hostname
-```
-
-在 SNMP 的可用 MIB 中,最有用的是 `HOST-RESOURCES-MIB` (.1.3.6.1.2.1.25)。 请参见下表,了解此 MIB 中的一些重要对象:
-
-| 名称 | OID | 描述 |
-| -------------------------- | ------------------------- | -------------------------------------------- |
-| hrSystemDate.2 | .1.3.6.1.2.1.25.1.2 | 本地日期和时间的主机标记。 |
-| hrSystemUptime.0 | .1.3.6.1.2.1.25.1.1.0 | 自主机上次初始化以来的时间。 |
-| hrMemorySize.0 | .1.3.6.1.2.1.25.2.2.0 | 主机上 RAM 的大小。 |
-| hrSystemProcesses.0 | .1.3.6.1.2.1.25.1.6.0 | 主机上当前加载或运行的进程上下文数。 |
-| hrStorageUsed.1 | .1.3.6.1.2.1.25.2.3.1.6.1 | 主机上已占用的存储空间大小(单位为 hrStorageAllocationUnits)。 |
-| hrStorageAllocationUnits.1 | .1.3.6.1.2.1.25.2.3.1.4.1 | hrStorageAllocationUnit 的大小(单位为字节) |
-
-例如,要通过 SNMP v3 查询 `hrMemorySize`,请在您的网络中支持 SNMP 的单独工作站上运行以下命令:
-```shell
-# username is the unique username of your SNMP v3 user
-# auth password is the authentication password
-# privacy password is the privacy password
-# hostname is the IP or domain of your Enterprise instance
-$ snmpget -v 3 -u username -l authPriv \
- -A "auth password" -a SHA \
- -X "privacy password" -x AES \
- -O e hostname HOST-RESOURCES-MIB::hrMemorySize.0
-```
-
-如果使用 SNMP v2c,要查询 `hrMemorySize`,请在您的网络中支持 SNMP 的单独工作站上运行以下命令:
-```shell
-# community-string is your community string
-# hostname is the IP or domain of your Enterprise instance
-snmpget -v 2c -c community-string hostname HOST-RESOURCES-MIB::hrMemorySize.0
-```
-
-{% tip %}
-
-**注**:为避免泄漏关于设备上所运行服务的信息,我们会将 `hrSWRun` 表 (1.1.3.6.1.2.1.25.41) 从生成的 SNMP 报告中排除,除非您对 SNMP v3 使用的是 `authPriv` 安全级别。 如果您使用的安全级别为 `authPriv`,我们将包含 `hrSWRun` 表。
-
-{% endtip %}
-
-更多关于 SNMP 中常用系统属性的 OID 映射的信息,请参阅“[CPU、内存和磁盘统计信息的 Linux SNMP OID](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)”。
diff --git a/translations/zh-CN/content/admin/installation/monitoring-your-github-enterprise-server-appliance.md b/translations/zh-CN/content/admin/installation/monitoring-your-github-enterprise-server-appliance.md
deleted file mode 100644
index a4272752f4ca..000000000000
--- a/translations/zh-CN/content/admin/installation/monitoring-your-github-enterprise-server-appliance.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 监视 GitHub Enterprise Server 设备
-intro: '随着 {% data variables.product.product_location_enterprise %} 使用量的逐渐增加,系统资源(例如 CPU、内存和存储空间)的利用率也会提高。 您可以配置监视和警报来提示潜在问题,以免这些问题对应用程序性能或可用性造成严重的负面影响。'
-redirect_from:
- - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting/
- - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance/
- - /enterprise/admin/installation/monitoring-your-github-enterprise-server-appliance
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/network-ports.md b/translations/zh-CN/content/admin/installation/network-ports.md
deleted file mode 100644
index ee9b10a7a3a2..000000000000
--- a/translations/zh-CN/content/admin/installation/network-ports.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: 网络端口
-redirect_from:
- - /enterprise/admin/articles/configuring-firewalls/
- - /enterprise/admin/articles/firewall/
- - /enterprise/admin/guides/installation/network-configuration/
- - /enterprise/admin/guides/installation/network-ports-to-open/
- - /enterprise/admin/installation/network-ports
-intro: 根据您需要为管理员、最终用户和电子邮件支持显示的网络服务有选择地打开网络端口。
-versions:
- enterprise-server: '*'
----
-
-### 管理端口
-
-需要使用一些管理端口来配置 {% data variables.product.product_location_enterprise %} 和运行某些功能。 最终用户在使用基本应用程序时不需要管理端口。
-
-| 端口 | 服务 | 描述 |
-| -------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 8443 | HTTPS | 基于安全 Web 的 {% data variables.enterprise.management_console %}。 进行基本安装和配置时需要。 |
-| 8080 | HTTP | 基于纯文本 Web 的 {% data variables.enterprise.management_console %}。 除非手动禁用 SSL,否则不需要。 |
-| 122 | SSH | 对 {% data variables.product.product_location_enterprise %} 进行 Shell 访问。 对来自高可用性配置中的其他所有节点的传入连接开放时需要。 默认 SSH 端口 (22) 专用于 Git 和 SSH 应用程序网络流量。 |
-| 1194/UDP | VPN | 采用高可用性配置的安全复制网络隧道。 对配置中的其他所有节点开放时需要。 |
-| 123/UDP | NTP | 为时间协议操作所需。 |
-| 161/UDP | SNMP | 为网络监视协议操作所需。 |
-
-### 最终用户的应用程序端口
-
-应用程序端口为最终用户提供 Web 应用程序和 Git 访问。
-
-| 端口 | 服务 | 描述 |
-| ---- | ----- | ------------------------------------------- |
-| 443 | HTTPS | 通过 HTTPS 访问 Web 应用程序和 Git。 |
-| 80 | HTTP | 访问 Web 应用程序。 当 SSL 启用时,所有请求都会重定向到 HTTPS 端口。 |
-| 22 | SSH | 通过 SSH 访问 Git。 支持对公共和私有仓库执行克隆、提取和推送操作。 |
-| 9418 | Git | Git 协议端口支持通过未加密网络通信对公共仓库执行克隆和提取操作。 |
-
-{% data reusables.enterprise_installation.terminating-tls %}
-
-### 电子邮件端口
-
-电子邮件端口必须可直接访问或通过中继访问,以便为最终用户提供入站电子邮件支持。
-
-| 端口 | 服务 | 描述 |
-| -- | ---- | ------------------------ |
-| 25 | SMTP | 支持采用加密的 SMTP (STARTTLS)。 |
diff --git a/translations/zh-CN/content/admin/installation/recommended-alert-thresholds.md b/translations/zh-CN/content/admin/installation/recommended-alert-thresholds.md
deleted file mode 100644
index 6d977e28a9db..000000000000
--- a/translations/zh-CN/content/admin/installation/recommended-alert-thresholds.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: 建议的警报阈值
-intro: '您可以配置警报来提前通知系统资源问题,以免它们影响您的 {% data variables.product.prodname_ghe_server %} 设备的性能。'
-redirect_from:
- - /enterprise/admin/guides/installation/about-recommended-alert-thresholds/
- - /enterprise/admin/installation/recommended-alert-thresholds
-versions:
- enterprise-server: '*'
----
-
-### 监视存储
-
-建议您同时对根存储设备和用户存储设备进行监视,并为警报配置合适的值,在可用磁盘空间不足时提供足够长的响应时间。
-
-| 严重程度 | 阈值 |
-| ------ | ---------------- |
-| **警告** | 已用磁盘空间超出总大小的 70% |
-| **关键** | 已用磁盘空间超出总大小的 85% |
-
-您可以根据分配的总存储空间、历史增长模式和预期响应时间调整这些值。 我们建议多分配一些存储资源,以便考虑增长情况并避免因分配额外存储空间而需要停机。
-
-### 监视 CPU 和平均负载使用情况
-
-虽然 CPU 利用率随资源密集型 Git 操作上下波动属于正常情况,但我们建议配置警报来监视异常增高的 CPU 利用率,因为 CPU 利用率长时间处于高水平可能说明实例配置不足。 建议监视 15 分钟系统平均负载,以获取接近或超过分配给虚拟机的 CPU 核心数的值。
-
-| 严重程度 | 阈值 |
-| ------ | ---------------------- |
-| **警告** | 十五分钟平均负载超出 1 倍的 CPU 核心 |
-| **关键** | 十五分钟平均负载超出 2 倍的 CPU 核心 |
-
-我们还建议监视虚拟化“盗取”时间,以确保在同一主机系统上运行的虚拟机不会用掉所有实例资源。
-
-### 监视内存使用情况
-
-分配给 {% data variables.product.product_location_enterprise %} 的物理内存大小对整体性能和应用程序响应能力有着极大的影响。 系统设计为通过大量使用内核磁盘缓存来加快 Git 操作速度。 建议将正常 RSS 工作使用量设置在最高使用量时总可用 RAM 的 50% 之内。
-
-| 严重程度 | 阈值 |
-| ------ | ------------------------ |
-| **警告** | 持续 RSS 使用量超出总可用内存大小的 50% |
-| **关键** | 持续 RSS 使用量超出总可用内存大小的 70% |
-
-如果内存已耗尽,内核 OOM 终止程序将尝试终止占用 RAM 较多的应用程序进程以释放内存资源,这样可能导致服务中断。 建议为虚拟机分配的内存大小应大于正常操作过程所需的内存。
diff --git a/translations/zh-CN/content/admin/installation/recovering-a-high-availability-configuration.md b/translations/zh-CN/content/admin/installation/recovering-a-high-availability-configuration.md
deleted file mode 100644
index a0a32157a667..000000000000
--- a/translations/zh-CN/content/admin/installation/recovering-a-high-availability-configuration.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: 恢复高可用性配置
-intro: '在故障转移到 {% data variables.product.prodname_ghe_server %} 设备后,您应尽快恢复冗余,而不应依赖于一台设备。'
-redirect_from:
- - /enterprise/admin/installation/recovering-a-high-availability-configuration
-versions:
- enterprise-server: '*'
----
-
-如果故障转移是在计划内进行的,或者与设备的健康状态无关,则可以将之前的主设备用作新的副本设备。 如果故障转移与主设备的问题相关,则最好创建新的副本设备。 更多信息请参阅“[创建高可用性副本](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)”。
-
-### 将之前的主设备配置为新副本
-
-1. 使用 SSH 连接到之前的主设备的 IP 地址。
- ```shell
- $ ssh -p 122 admin@FORMER PRIMARY IP
- ```
-2. 在之前的主设备上,使用之前副本的 IP 地址运行 `ghe-repl-setup`。
- ```shell
- $ ghe-repl-setup FORMER REPLICA IP
- ```
-{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
-4. 要验证与新的主设备的连接并为新副本启用副本模式,请再次运行 `ghe-repl-setup`。
- ```shell
- $ ghe-repl-setup FORMER REPLICA IP
- ```
-{% data reusables.enterprise_installation.replication-command %}
diff --git a/translations/zh-CN/content/admin/installation/removing-a-high-availability-replica.md b/translations/zh-CN/content/admin/installation/removing-a-high-availability-replica.md
deleted file mode 100644
index 3a2481af9fe3..000000000000
--- a/translations/zh-CN/content/admin/installation/removing-a-high-availability-replica.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: 移除高可用性副本
-intro: '您可以暂时停止对 {% data variables.product.prodname_ghe_server %} 副本的复制,也可以永久地移除复制。'
-redirect_from:
- - /enterprise/admin/installation/removing-a-high-availability-replica
-versions:
- enterprise-server: '*'
----
-
-### 暂时停止复制
-
-1. 如有必要,移除副本的 Geo DNS 条目,使 Geo-replication 副本停止提供用户流量。
-2. 在您希望暂时停止复制的副本上,运行 ghe-repl-stop。
- ```shell
- $ ghe-repl-stop
- ```
-3. 要再次开始复制,请运行 `ghe-repl-start`。
- ```shell
- $ ghe-repl-start
- ```
-
-### 永久移除复制
-
-1. 如有必要,移除副本的 Geo DNS 条目,使 Geo-replication 副本停止提供用户流量。
-2. 在您希望移除复制的副本上,运行 `ghe-repl-stop`。
- ```shell
- $ ghe-repl-stop
- ```
-3. 在副本上,要移除复制状态,请运行 `ghe-repl-teardown`。
- ```shell
- $ ghe-repl-teardown
- ```
diff --git a/translations/zh-CN/content/admin/installation/searching-the-audit-log.md b/translations/zh-CN/content/admin/installation/searching-the-audit-log.md
deleted file mode 100644
index e57145dca7e4..000000000000
--- a/translations/zh-CN/content/admin/installation/searching-the-audit-log.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: 搜索审核日志
-intro: '站点管理员可以在 {% data variables.product.product_location_enterprise %} 上搜索[审核的操作](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions) 的完整列表。'
-redirect_from:
- - /enterprise/admin/articles/searching-the-audit-log/
- - /enterprise/admin/installation/searching-the-audit-log
-versions:
- enterprise-server: '*'
----
-
-### 搜索查询语法
-
-由一个或多个键值对(以 AND/OR 逻辑运算符分隔)构成一个搜索查询。
-
-| 键 | 值 |
-| --------------:| ------------------------------------------------------------------------------------ |
-| `actor_id` | 发起操作的用户帐户的 ID |
-| `actor` | 发起操作的用户帐户的名称 |
-| `oauth_app_id` | 与操作相关联的 OAuth 应用程序的 ID |
-| `action` | [审核的操作](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)的名称 |
-| `user_id` | 受操作影响的用户的 ID |
-| `用户` | 受操作影响的用户的名称 |
-| `repo_id` | 受操作影响的仓库的 ID(若适用) |
-| `repo` | 受操作影响的仓库的名称(若适用) |
-| `actor_ip` | 发起操作的 IP 地址 |
-| `created_at` | 操作发生的时间 |
-| `from` | 发起操作的视图 |
-| `note` | 事件特定的其他信息(采用纯文本或 JSON 格式) |
-| `org` | 受操作影响的组织的名称(若适用) |
-| `org_id` | 受操作影响的组织的 ID(若适用) |
-
-例如,要查看自 2017 年初开始影响仓库 `octocat/Spoon-Knife` 的所有操作:
-
- `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]`
-
-有关操作的完整列表,请参阅“[审核的操作](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)”。
-
-### 搜索审核日志
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.audit-log-tab %}
-4. 输入搜索查询。 ![搜索查询](/assets/images/enterprise/site-admin-settings/search-query.png)
diff --git a/translations/zh-CN/content/admin/installation/setting-git-push-limits.md b/translations/zh-CN/content/admin/installation/setting-git-push-limits.md
deleted file mode 100644
index 38265e6776b9..000000000000
--- a/translations/zh-CN/content/admin/installation/setting-git-push-limits.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: 设置 Git 推送限制
-intro: 您可以对仓库中的 Git 对象强制执行最大大小限制。
-redirect_from:
- - /enterprise/admin/guides/installation/git-server-settings/
- - /enterprise/admin/articles/setting-git-push-limits/
- - /enterprise/admin/installation/setting-git-push-limits
-versions:
- enterprise-server: '*'
----
-
-要使仓库大小保持可管理并防止发生性能问题,可以为实例上的仓库配置文件大小限制。
-
-默认情况下,强制执行仓库上传限制时,无法添加或上传超过 100 MB 的文件。
-
-{% if currentVersion ver_lt "enterprise-server@2.20" %}
-{% tip %}
-
-**注**:仅会根据 Git 推送限制检查大于 {% data variables.large_files.warning_size %} 的文件。 如果需要设置较低的推送限制,请联系 {% data variables.contact.contact_ent_support %} 获得帮助。
-
-{% endtip %}
-{% endif %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-4. 在“Repository upload limit”下,使用下拉菜单,然后单击最大对象大小。 ![包含最大对象大小选项的下拉菜单](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
-5. 或者,要对 {% data variables.product.product_location_enterprise %} 上的所有仓库执行最大上传限制,请选择 select **Enforce on all repositories(对所有仓库强制执行)** ![对所有仓库选项强制执行最大对象限制](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
diff --git a/translations/zh-CN/content/admin/installation/setting-up-external-monitoring.md b/translations/zh-CN/content/admin/installation/setting-up-external-monitoring.md
deleted file mode 100644
index 2ad7c09972ae..000000000000
--- a/translations/zh-CN/content/admin/installation/setting-up-external-monitoring.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: 设置外部监视
-intro: '您可以使用 SNMP 或 collectd 统计信息收集协议监视 {% data variables.product.prodname_ghe_server %} 设备上的基本系统资源。'
-redirect_from:
- - /enterprise/admin/installation/setting-up-external-monitoring
-versions:
- enterprise-server: '*'
----
-
-### 关于 SNMP
-
-简单网络管理协议 (SNMP) 是一种受到广泛支持的网络设备和服务器监视方法。 SNMP 默认禁用,但可以通过 {% data variables.product.prodname_enterprise %} 监视仪表板进行配置。 UDP 端口 161 必须打开,并且可以通过您的网络管理站到达。 更多信息请参阅“[使用 SNMP 进行监视](/enterprise/{{ currentVersion }}/admin/guides/installation/monitoring-using-snmp/)”。
-
-### 关于 collectd
-
-collectd 属于开源统计信息收集和报告守护程序,内置对写入 RRD 文件的支持。 可以将关于 CPU 利用率、内存与磁盘占用量、网络接口流量与错误以及系统负荷的统计信息转发到外部 collectd 服务器,可在该服务器中使用各种可用工具和插件配置图表、分析和警报。 要配置 `collectd` 转发,请参阅“[配置 collectd](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-collectd/)”。
-
-此外,也可以使用内置到底层虚拟化平台的监视工具对系统资源进行基本监视和警报。 更多信息请参阅 [Amazon CloudWatch](http://aws.amazon.com/cloudwatch/) 和 [VMware vSphere 监视](http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-monitoring-performance-guide.pdf)文档。
diff --git a/translations/zh-CN/content/admin/installation/site-admin-dashboard.md b/translations/zh-CN/content/admin/installation/site-admin-dashboard.md
deleted file mode 100644
index 908cb4d76bd6..000000000000
--- a/translations/zh-CN/content/admin/installation/site-admin-dashboard.md
+++ /dev/null
@@ -1,178 +0,0 @@
----
-title: 站点管理员仪表板
-intro: '站点管理员仪表板提供了多种工具,这些工具可以帮助您管理 {% data variables.product.product_location_enterprise %}。'
-redirect_from:
- - /enterprise/admin/articles/site-admin-dashboard/
- - /enterprise/admin/installation/site-admin-dashboard
-versions:
- enterprise-server: '*'
----
-
-要访问仪表板,请在任意页面的右上角中单击 {% octicon "rocket" aria-label="The rocket ship" %}。 ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
-
-### 许可信息与搜索
-
-请参照站点管理员仪表板的此部分检查您当前的 {% data variables.product.prodname_enterprise %} 许可;搜索用户和仓库;查询[审核日志](#audit-log)。
-
-### {% data variables.enterprise.management_console %}
-
-您可以在此处启动 {% data variables.enterprise.management_console %},以管理域、身份验证和 SSL 等虚拟设备设置。
-
-### 探索
-
- GitHub [趋势页面](https://github.com/blog/1585-explore-what-is-trending-on-github)中的数据按每天、每周和每月的时间跨度为仓库和开发者计算。 在 **Explore** 部分中,您可以看到此数据的最后缓存时间,并将新的趋势计算作业加入队列。
-
-### 审核日志
-
-{% data variables.product.prodname_enterprise %} 会实时记录您可以查询的审核操作。
-
-默认情况下,审核日志会按时间倒序显示所有已审核操作的列表。 要对此列表进行筛选,您可以在 **Query** 文本框中输入键值对,然后单击 **Search**,如“[搜索审核日志](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)”所述。
-
-更多关于审核日志的信息,请参阅“[审核日志](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)”。有关审核操作的完整列表,请参阅“[审核的操作](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)”。
-
-### 报告
-
-如果您需要获取关于 {% data variables.product.product_location_enterprise %} 中用户、组织和仓库的信息,正常些情况下,您将通过 [GitHub API](http://developer.github.com/v3/) 提取 JSON 数据。 但遗憾的是,此 API 可能无法提供您需要的所有数据,并且需要一定的专业技术知识才能使用。 因此,站点管理员仪表板提供 **Reports** 部分代替 API 方法,您可以通过仪表板轻松下载 CSV 报告,其中包含大部分您有可能需要的用户、组织和仓库信息。
-
-具体来讲,您可以下载列出以下信息的 CSV 报告:
-
-- 所有用户
-- 在上个月内曾处于活动状态的所有用户
-- 一个月或更长时间未活动的所有用户
-- 曾被挂起的所有用户
-- 所有组织
-- 所有仓库
-
-您还可以通过向站点管理员帐户进行标准 HTTP 身份验证,以编程方式访问这些报告。 必须使用 `site_admin` 范围的个人访问令牌。 For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-
-下面是如何使用 cURL 下载“所有用户”报告的示例:
-
-```shell
-curl -L -u username:token http(s)://hostname/stafftools/reports/all_users.csv
-```
-
-要以编程方式访问其他报告,请将 `all_users` 替换为 `active_users`、`dormant_users`、`suspended_users`、`all_organizations` 或 `all_repositories`。
-
-{% note %}
-
-**注**:如果没有可用的缓存报告,最初的 `curl` 请求会返回 202 HTTP 响应;将在后台生成报告。 您可以发送另一个请求来下载报告。 您可以使用具有 `site_admin` 作用域的密码或 OAuth 令牌代替密码。
-
-{% endnote %}
-
-#### 用户报告
-
-| 键 | 描述 |
-| -----------------:| ------------------------- |
-| `created_at` | 用户帐户的创建时间(ISO 8601 时间戳形式) |
-| `id` | 用户或组织的帐户 ID |
-| `login` | 帐户的登录名称 |
-| `电子邮件` | 帐户的主电子邮件地址 |
-| `角色` | 帐户属于管理员还是普通用户 |
-| `suspended?` | 帐户是否已挂起 |
-| `last_logged_ip` | 最近登录帐户的 IP 地址 |
-| `repos` | 帐户拥有的仓库数量 |
-| `ssh_keys` | 注册到帐户的 SSH 密钥数量 |
-| `org_memberships` | 帐户所属的组织数量 |
-| `dormant?` | 帐户是否休眠 |
-| `last_active` | 帐户上次活动时间(ISO 8601 时间戳形式) |
-| `raw_login` | 原始登录信息(JSON 格式) |
-| `2fa_enabled?` | 用户是否已启用双重身份验证 |
-
-#### 组织报告
-
-| 键 | Description |
-| ---------------:| ------------ |
-| `id` | 组织 ID |
-| `created_at` | 组织创建时间 |
-| `login` | 组织的登录名称 |
-| `电子邮件` | 组织的主电子邮件地址 |
-| `owners` | 组织所有者数量 |
-| `members` | 组织成员数量 |
-| `团队` | 组织团队数量 |
-| `repos` | 组织仓库数量 |
-| `2fa_required?` | 组织是否需要双重身份验证 |
-
-#### 仓库报告
-
-| 键 | 描述 |
-| ---------------:| -------------- |
-| `created_at` | 仓库创建时间 |
-| `owner_id` | 仓库所有者的 ID |
-| `owner_type` | 仓库由用户所有还是由组织所有 |
-| `owner_name` | 仓库所有者的名称 |
-| `id` | 仓库 ID |
-| `name` | 仓库名称 |
-| `可见性` | 仓库是公共还是私有 |
-| `readable_size` | 以人类可读格式表示的仓库大小 |
-| `raw_size` | 以数字形式表示的仓库大小 |
-| `collaborators` | 仓库协作者数量 |
-| `fork?` | 仓库是否为分叉 |
-| `deleted?` | 仓库是否已删除 |
-
-### 索引
-
- GitHub 的[代码搜索](https://github.com/blog/1381-a-whole-new-code-search)功能由 [ElasticSearch](http://www.elasticsearch.org/) 提供支持。 站点管理员仪表板的这一部分会显示 ElasticSearch 集群的当前状态,并提供多种工具来控制搜索和索引行为。 这些工具分为以下三类。
-
-#### 代码搜索
-
-此类允许您启用或禁用对源代码进行的搜索和索引操作。
-
-#### 代码搜索索引修复
-
-此类控制着代码搜索索引的修复方式。 您可以
-
-- 启用或禁用索引修复作业
-- 开始新的索引修复作业
-- 重置所有索引修复状态
-
-{% data variables.product.prodname_enterprise %} 使用修复作业协调搜索索引的状态与数据库中存储的数据(问题、拉取请求、仓库和用户)以及 Git 仓库中存储的数据(源代码)。 以下情况下会进行此操作:
-
-- 创建新的搜索索引;
-- 需要重新填入缺失的数据;或者
-- 需要更新旧的搜索数据。
-
-也就是说,修复作业是根据需要启动的,并在后台运行,而不是站点管理员通过任何方式排定的。
-
-此外,修复作业还使用“修复偏移”实现并行化。 偏移是指协调的记录在数据库表中的偏移。 多个后台作业可以基于此偏移同步工作。
-
-进度条会在所有后台工作进程中显示修复作业的当前状态。 此值是修复偏移与数据中最高记录 ID 的百分比差异。 不用担心修复作业完成后在进度条中显示的值:因为它表示的是修复偏移与数据库中最高记录 ID 之差,随着更多的仓库添加到 {% data variables.product.product_location_enterprise %} 中,即使这些仓库实际上已编制索引,此值也会减小。
-
-您可以随时启动新的代码搜索索引修复作业。 在协调搜索索引与数据库和 Git 仓库数据时,它将使用单个 CPU。 为了最大限度地减小对 I/O 性能的影响并减小操作超时的几率,请先尝试在非高峰期运行修复作业。 使用 `top` 等实用程序监视系统的平均负载和 CPU 利用率;如果您没有注意到任何显著的变化,那么在高峰期运行索引修复作业也应当是安全的。
-
-#### 问题索引修复
-
- 此类控制着[问题](https://github.com/blog/831-issues-2-0-the-next-generation)索引的修复方式。 您可以
-
-- 启用或禁用索引修复作业
-- 开始新的索引修复作业
-- 重置所有索引修复状态
-
-### 仓库
-
-这是 {% data variables.product.product_location_enterprise %} 上的仓库列表。 您可以单击仓库名称,然后访问各项功能,对仓库进行管理。
-
-- [阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)
-- [配置 {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository)
-- [存档和取消存档仓库](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/)
-
-### 所有用户
-
-您可以在此查看 {% data variables.product.product_location_enterprise %} 上的所有用户,并[发起 SSH 密钥审核](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys)。
-
-### 站点管理员
-
-您可以在此查看 {% data variables.product.product_location_enterprise %} 上的所有管理员,并[发起 SSH 密钥审核](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys)。
-
-### 休眠用户
-
-您可以在此查看并[挂起](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) {% data variables.product.product_location_enterprise %} 上的所有非活动用户。 以下情况下,会认定用户帐户处于非活动状态(“休眠”):
-
-- 存在时间长于为 {% data variables.product.product_location_enterprise %} 设置的休眠阈值。
-- 在该时间段内没有发生任何活动。
-- 不是站点管理员。
-
-{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} 更多信息请参阅“[管理休眠用户](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)”。
-
-### 已挂起的用户
-
-您可以在此查看 {% data variables.product.product_location_enterprise %} 上所有已被挂起的用户,并[发起 SSH 密钥审核](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys)。
diff --git a/translations/zh-CN/content/admin/installation/system-overview.md b/translations/zh-CN/content/admin/installation/system-overview.md
deleted file mode 100644
index 4113d5067bc1..000000000000
--- a/translations/zh-CN/content/admin/installation/system-overview.md
+++ /dev/null
@@ -1,140 +0,0 @@
----
-title: 系统概述
-intro: '{% data variables.product.prodname_ghe_server %} 是包含在虚拟设备中属于您的组织的 {% data variables.product.prodname_dotcom %} 私有副本,此虚拟设备托管在您配置和控制的本地或云中。'
-redirect_from:
- - /enterprise/admin/installation/system-overview
-versions:
- enterprise-server: '*'
----
-
-### 存储架构
-
-{% data variables.product.prodname_ghe_server %} 需要两个存储卷,一个安装在*根文件系统*路径下 (`/`),另一个安装在*用户文件系统*路径下 (`/data/user`)。 这种架构将运行软件环境与持久应用程序数据分离,从而可以简化升级、回滚和恢复程序。
-
-根文件系统包含在分布式机器映像中。 它包含基本操作系统和 {% data variables.product.prodname_ghe_server %} 应用程序环境。 根文件系统应被视为临时性的。 升级到今后的 {% data variables.product.prodname_ghe_server %} 版本时,根文件系统中的所有数据都将被替代。
-
-根文件系统包含:
- - 自定义证书颁发机构 (CA) 证书(*/usr/local/share/ca-certificates* 中)
- - 自定义网络配置
- - 自定义防火墙配置
- - 复制状态
-
-用户文件系统包含用户配置和数据,例如:
- - Git 仓库
- - 数据库
- - 搜索索引
- - 在 {% data variables.product.prodname_pages %} 站点上发布的内容
- - {% data variables.large_files.product_name_long %} 中的大文件
- - 预接收挂钩环境
-
-### 部署选项
-
-您可以将 {% data variables.product.prodname_ghe_server %} 部署为一个虚拟设备,也可采用高可用性配置。 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 以实现高可用性](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)”。
-
-某些拥有成千上万名开发者的组织还会从使用 {% data variables.product.prodname_ghe_server %} 集群中受益。 更多信息请参阅“[关于集群](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-clustering)。”
-
-### 数据保留和数据中心冗余
-
-{% danger %}
-
-在生产环境中使用 {% data variables.product.prodname_ghe_server %} 之前,我们强烈建议您设置备份和灾难恢复计划。 更多信息请参阅“[在设备上配置备份](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)”。
-
-{% enddanger %}
-
-{% data variables.product.prodname_ghe_server %} 支持通过 [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils) 进行在线和增量备份。 您可以通过安全网络链接(SSH 管理端口)远距离为场外或地理上分散的存储生成增量快照。 在主数据中心发生灾难时,您可以在恢复时通过网络将快照恢复到新配置的设备中。
-
-除网络备份外,在设备处于离线或维护模式时,还支持用户存储卷的 AWS (EBS) 和 VMware 磁盘快照。 如果您的服务级别要求允许定期离线维护,可以将定期卷快照用作低成本、低复杂性的方案,代替通过 {% data variables.product.prodname_enterprise_backup_utilities %} 进行网络备份。
-
-更多信息请参阅“[在设备上配置备份](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)”。
-
-### 安全
-
-{% data variables.product.prodname_ghe_server %} 是一个在基础设施上运行的虚拟设备,受您现有的信息安全控制(如防火墙、IAM、监控和 VPN)所管辖。 使用 {% data variables.product.prodname_ghe_server %} 可以帮助您避免因云解决方案而产生的管理合规问题。
-
-{% data variables.product.prodname_ghe_server %} 还包含额外的安全功能。
-
-- [操作系统、软件和补丁](#operating-system-software-and-patches)
-- [网络安全性](#network-security)
-- [应用程序安全性](#application-security)
-- [外部服务和支持](#external-services-and-support-access)
-- [加密通信](#encrypted-communication)
-- [用户和访问权限](#users-and-access-permissions)
-- [身份验证](#authentication)
-- [审核和访问日志记录](#audit-and-access-logging)
-
-#### 操作系统、软件和补丁
-
-{% data variables.product.prodname_ghe_server %} 运行自定义的 Linux 操作系统,其中只包含必要的应用程序和服务。 {% data variables.product.prodname_dotcom %} 将管理设备核心操作系统的补丁作为其标准产品发布周期的一部分。 补丁可解决 {% data variables.product.prodname_dotcom %} 应用程序的功能、稳定性和非关键性安全问题。 {% data variables.product.prodname_dotcom %} 还根据需要在常规发布周期之外提供重要的安全补丁。
-
-#### 网络安全性
-
-{% data variables.product.prodname_ghe_server %} 的内部防火墙限制对设备服务的网络访问。 网络上仅提供设备正常运行所需的服务。 更多信息请参阅“[网络端口](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports)”。
-
-#### 应用程序安全性
-
-{% data variables.product.prodname_dotcom %} 的应用程序安全团队全时关注 {% data variables.product.prodname_dotcom %} 产品(包括 {% data variables.product.prodname_ghe_server %})的漏洞评估、渗透测试和代码审查。 {% data variables.product.prodname_dotcom %} 还与外部安全公司签约,要求他们对 {% data variables.product.prodname_dotcom %} 产品定期进行安全性评估。
-
-#### 外部服务和支持
-
-{% data variables.product.prodname_ghe_server %} 无需从网络访问外部服务也可以正常运行。 您可以选择集成外部服务,以提供电子邮件传送、外部监控和日志转发等功能。 更多信息请参阅“[配置电子邮件通知](/enterprise/{{ currentVersion }}/admin/user-management/configuring-email-for-notifications)”、“[设置外部监控](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)”和“[日志转发](/enterprise/{{ currentVersion }}/admin/installation/log-forwarding)”。
-
-您可以手动收集故障排除数据并发送至 {% data variables.contact.github_support %}。 更多信息请参阅“[向 {% data variables.contact.github_support %} 提供数据](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)”。
-
-#### 加密通信
-
-{% data variables.product.prodname_dotcom %} 将 {% data variables.product.prodname_ghe_server %} 设计为在公司防火墙后面运行。 为确保线路通信安全,我们建议您启用传输层安全协议 (TLS)。 {% data variables.product.prodname_ghe_server %} 在 HTTPS 流量方面支持 2048 位和更高的商业 TLS 证书。 更多信息请参阅“[配置 TLS](/enterprise/{{ currentVersion }}/admin/installation/configuring-tls)”。
-
-默认情况下,该设备还为使用 Git 的仓库访问和管理目的提供安全 Shell (SSH) 访问。 更多信息请参阅“[关于 SSH](/enterprise/user/articles/about-ssh)”和“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)“。
-
-#### 用户和访问权限
-
-{% data variables.product.prodname_ghe_server %} 提供三种类型的帐户。
-
-- `管理员` Linux 用户帐户已控制对基础操作系统的访问,包括对直接文件系统和数据库的访问。 一小部分受信任的管理员应该有权访问此帐户,他们可以通过 SSH 访问。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)”。
-- 设备 Web 应用程序中的用户帐户对自己的数据以及其他用户或组织明确授予权限的任何数据具有完全访问权限。
-- 设备 Web 应用程序中的站点管理员是可以管理高级 Web 应用程序和设备设置、用户和组织帐户设置以及仓库数据的用户帐户。
-
-关于 {% data variables.product.prodname_ghe_server %} 用户权限的更多信息,请参阅“[GitHub 上的访问权限](/enterprise/user/articles/access-permissions-on-github) ”。
-
-#### 身份验证
-
-{% data variables.product.prodname_ghe_server %} 提供四种身份验证方法。
-
-- SSH 公钥身份验证提供使用 Git 的仓库访问权限和管理 shell 的访问权限。 更多信息请参阅“[关于 SSH](/enterprise/user/articles/about-ssh)”和“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)“。
-- 使用 HTTP cookie 的用户名和密码身份验证提供 Web 应用程序访问和会话管理权限,可选择双重身份验证 (2FA)。 更多信息请参阅“[使用内置身份验证](/enterprise/{{ currentVersion }}/admin/user-management/using-built-in-authentication)”。
-- 使用 LDAP 服务、SAML 身份提供程序 (IdP) 或其他兼容服务的外部 LDAP、SAML 或 CAS 身份验证提供对 Web 应用程序的访问权限。 更多信息请参阅“[为您的 GitHub Enterprise Server 实例验证用户身份](/enterprise/{{ currentVersion }}/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance)“。
-- OAuth 和个人访问令牌为外部客户端和服务提供对 Git 仓库数据和 API 的访问权限。 For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-
-#### 审核和访问日志记录
-
-{% data variables.product.prodname_ghe_server %} 存储传统的操作系统日志和应用程序日志。 应用程序还会编写详细的审核和安全日志,永久存储在 {% data variables.product.prodname_ghe_server %} 上。 您可以通过 `syslog-ng` 协议将两种类型的日志实时转发到多个目标。 更多信息请参阅“[日志转发](/enterprise/{{ currentVersion }}/admin/installation/log-forwarding)”。
-
-访问和审核日志包括如下信息。
-
-##### 访问日志
-
-- 关于浏览器和 API 访问的完整 web 服务器日志
-- 通过 Git、HTTP 和 SSH 协议访问仓库数据的完整日志
-- 通过 HTTPS 和 SSH 的管理访问日志
-
-##### 审核日志
-
-- 用户登录、密码重置、2FA 请求、电子邮件设置更改,以及对授权应用程序和 API 的更改
-- 站点管理员操作,例如解锁用户帐户和仓库
-- 仓库推送事件、访问授权、转让和重命名
-- 组织成员变更,包括团队创建和删除
-
-### {% data variables.product.prodname_ghe_server %} 的开源依赖项
-
-要查看您的设备 {% data variables.product.prodname_ghe_server %} 版本中依赖项的完整列表以及每个项目的许可,请访问 `http(s)://HOSTNAME/site/credits`。
-
-您的设备上提供包含依赖项和关联元数据完整列表的 tarball:
-- 要查看所有平台通用的依赖项,请访问 `/usr/local/share/enterprise/dependencies--base.tar.gz`
-- 要查看平台特有的依赖项,请访问 `/usr/local/share/enterprise/dependencies--.tar.gz`
-
-还提供包含依赖项和元数据完整列表的 tarball,地址为 `https://enterprise.github.com/releases//download.html`。
-
-### 延伸阅读
-
-- “[设置 {% data variables.product.prodname_ghe_server %} 的试用版](/articles/setting-up-a-trial-of-github-enterprise-server)”
-- “[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”
diff --git a/translations/zh-CN/content/admin/installation/troubleshooting-ssl-errors.md b/translations/zh-CN/content/admin/installation/troubleshooting-ssl-errors.md
deleted file mode 100644
index a4a1a58d6a2d..000000000000
--- a/translations/zh-CN/content/admin/installation/troubleshooting-ssl-errors.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: 排查 SSL 错误
-intro: 如果您的设备遇到 SSL 问题,可以采取相应措施加以解决。
-redirect_from:
- - /enterprise/admin/articles/troubleshooting-ssl-errors/
- - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration/
- - /enterprise/admin/installation/troubleshooting-ssl-errors
-versions:
- enterprise-server: '*'
----
-
-### 将密码从密钥文件中移除
-
-如果您的 Linux 机器上安装了 OpenSSL,可以移除密码。
-
-1. 重命名原始密钥文件。
- ```shell
- $ mv yourdomain.key yourdomain.key.orig
- ```
-2. 生成不含密码的新密钥。
- ```shell
- $ openssl rsa -in yourdomain.key.orig -out yourdomain.key
- ```
-
-运行此命令时系统会提示您输入密钥的密码。
-
-关于 OpenSSL 的更多信息,请参阅 [OpenSSL 的文档](https://www.openssl.org/docs/)。
-
-### 将 SSL 证书或密钥转换为 PEM 格式
-
-如果安装了 OpenSSL,您可以使用 `openssl` 命令将密钥转换为 PEM 格式。 例如,您可以将密钥从 DER 格式转换为 PEM 格式。
-
-```shell
-$ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM
-```
-
-否则,可以使用 SSL Converter 工具将证书转换为 PEM 格式。 更多信息请参阅 [SSL Converter 工具文档](https://www.sslshopper.com/ssl-converter.html)。
-
-### 上传密钥后安装无响应
-
-如果上传 SSL 密钥后 {% data variables.product.product_location_enterprise %} 无响应,请[联系 {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) 并提供具体的详细信息,并附上您的 SSL 证书的副本。
-
-### 证书有效性错误
-
-如果 Web 浏览器和命令行 Git 等客户端无法验证 SSL 证书的有效性,则会显示错误消息。 这种情况通常发生在自签名证书以及由不被客户端承认的中间根证书颁发的“链式根”证书上。
-
-如果您要使用由证书颁发机构 (CA) 签名的证书,那么您上传到 {% data variables.product.prodname_ghe_server %} 的证书文件必须包含具有该 CA 的根证书的证书链。 要创建此类文件,请将整个证书链(“或证书包”)连接到证书末端,确保包含主机名的主要证书在前。 在大多数系统中,您可以使用与下列命令相似的命令来执行此操作:
-
-```shell
-$ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt
-```
-
-您可以从证书颁发机构或 SSL 供应商处下载证书包(例如 `bundle-certificates.crt`)。
-
-### 安装自签名或不受信任的证书颁发机构 (CA) 根证书
-
-如果您的 {% data variables.product.prodname_ghe_server %} 设备与网络中使用自签名或不受信证书的其他机器进行交互,您需要将签名 CA 的根证书导入到系统范围的证书库中,以通过 HTTPS 访问这些系统。
-
-1. 从本地证书颁发机构获取 CA 的根证书并确保其为 PEM 格式。
-2. 以“admin”用户身份在端口 122 上通过 SSH 将文件复制到您的 {% data variables.product.prodname_ghe_server %} 设备。
- ```shell
- $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin
- ```
-3. 以“admin”用户身份在端口 122 上通过 SSH 连接到 {% data variables.product.prodname_ghe_server %} 管理 shell。
- ```shell
- $ ssh -p 122 admin@HOSTNAME
- ```
-4. 将证书导入到系统范围的证书库中。
- ```shell
- $ ghe-ssl-ca-certificate-install -c rootCA.crt
- ```
diff --git a/translations/zh-CN/content/admin/installation/updating-the-virtual-machine-and-physical-resources.md b/translations/zh-CN/content/admin/installation/updating-the-virtual-machine-and-physical-resources.md
deleted file mode 100644
index 620ec98033b6..000000000000
--- a/translations/zh-CN/content/admin/installation/updating-the-virtual-machine-and-physical-resources.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 更新虚拟机和物理资源
-intro: 升级虚拟软件和虚拟硬件需要您的实例停机一段时间,因此,请务必提前规划升级。
-redirect_from:
- - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm/'
- - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources/'
- - /enterprise/admin/installation/updating-the-virtual-machine-and-physical-resources
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/installation/upgrade-requirements.md b/translations/zh-CN/content/admin/installation/upgrade-requirements.md
deleted file mode 100644
index cb650e3de324..000000000000
--- a/translations/zh-CN/content/admin/installation/upgrade-requirements.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: 升级要求
-intro: '对 {% data variables.product.prodname_ghe_server %} 进行升级之前,请查阅升级策略规划的建议和要求。'
-redirect_from:
- - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release/
- - /enterprise/admin/installation/upgrade-requirements
-versions:
- enterprise-server: '*'
----
-
-{% note %}
-
-**注:**
-- 要由 {% data variables.product.prodname_enterprise %} 11.10.348 升级到 {% data variables.product.current-340-version %},您必须先迁移到 {% data variables.product.prodname_enterprise %} 2.1.23。 更多信息请参阅“[从 {% data variables.product.prodname_enterprise %} 11.10.x 迁移到 2.1.23](/enterprise/{{ currentVersion }}/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23)”。
-- 为受支持版本提供的升级包位于 [enterprise.github.com](https://enterprise.github.com/releases)。 验证完成升级所需的升级包的可用性。 如果升级包不可用,请联系 {% data variables.contact.contact_ent_support %} 获得帮助。
-- 如果您使用 {% data variables.product.prodname_ghe_server %} 集群,请参阅 {% data variables.product.prodname_ghe_server %} 集群指南中的“[升级集群](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)”,了解集群特有的说明。
-- {% data variables.product.prodname_ghe_server %} 版本说明提供了 {% data variables.product.prodname_ghe_server %} 每一版本的新功能一览表。 更多信息请参阅[版本页面](https://enterprise.github.com/releases)。
-
-{% endnote %}
-
-### 建议
-
-- 尽量减少升级过程中的升级次数。 例如,不要从 {% data variables.product.prodname_enterprise %} {{ enterpriseVersions.supported[2] }} 升级到 {{ enterpriseVersions.supported[1] }} 再升级到 {{ enterpriseVersions.latest }},而应从 {% data variables.product.prodname_enterprise %} {{ enterpriseVersions.supported[2] }} 升级到 {{ enterpriseVersions.latest }}。
-- 如果您的版本比最新版本低几个版本,请通过升级过程的每一步骤尽量将 {% data variables.product.product_location_enterprise %} 升级为更高版本。 在每次升级时尽可能使用最新版本,这样一来您可以充分利用性能改进和错误修复。 例如,您可以从 {% data variables.product.prodname_enterprise %} 2.7 升级到 2.8 再升级到 2.10,但从 {% data variables.product.prodname_enterprise %} 2.7 升级到 2.9 再升级到 2.10 会在第二步中使用更高版本。
-- 升级时使用最新补丁版本。 {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
-- 使用暂存实例测试升级步骤。 更多信息请参阅“[设置暂存实例](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)”。
-- 如果运行多次升级,两次功能升级之间至少应间隔 24 小时,以便使数据迁移和后台升级任务能够彻底完成。
-
-### 要求
-
-- 您必须从**最近**两个版本的功能版本开始升级。 例如,要升级到 {% data variables.product.prodname_enterprise %} {{ enterpriseVersions.latest }},您必须使用 {% data variables.product.prodname_enterprise %} {{ enterpriseVersions.supported[1] }} 或 {{ enterpriseVersions.supported[2] }}。
-- {% data reusables.enterprise_installation.hotpatching-explanation %}
-- 如果受影响的服务(例如内核、MySQL 或 Elasticsearch)需要重启 VM 或服务,热补丁可能需要停机一段时间。 需要重启时,系统会通知您。 您可以在稍后完成重启。
-- 通过热补丁升级时,必须提供额外的根存储,因为热补丁会安装某些服务的多个版本,直至升级完成。 如果根磁盘存储空间不足,运行前检查将发出通知。
-- 通过热补丁进行升级时,您的实例负荷不能过大,否则可能影响热补丁过程。 运行前检查将考虑平均负载,如果平均负载过高,升级将失败。- 升级至 {% data variables.product.prodname_ghe_server %} 2.17 可将您的审核日志从 Elasticsearch 迁移到 MySQL. 这种迁移还会增加恢复快照所需的时长和磁盘空间大小。 迁移之前,请使用此命令检查 ElasticSearch 审核日志索引中的字节数:
-``` shell
-curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes
-```
-使用此数字估算 MySQL 审核日志将需要的磁盘空间大小。 该脚本还会在导入过程中监视可用磁盘空间大小。 在可用磁盘空间大小接近于迁移必需的磁盘空间大小时,监视此数字尤为重要。
-
-查看这些建议和要求后,您可以对 {% data variables.product.prodname_ghe_server %} 进行升级。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}”](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)。
diff --git a/translations/zh-CN/content/admin/installation/upgrading-github-enterprise-server.md b/translations/zh-CN/content/admin/installation/upgrading-github-enterprise-server.md
deleted file mode 100644
index 4bb06cded0a8..000000000000
--- a/translations/zh-CN/content/admin/installation/upgrading-github-enterprise-server.md
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: 升级 GitHub Enterprise Server
-intro: '升级 {% data variables.product.prodname_ghe_server %},以获取最新功能和安全更新。'
-redirect_from:
- - /enterprise/admin/articles/upgrading-to-the-latest-release/
- - /enterprise/admin/articles/migrations-and-upgrades/
- - /enterprise/admin/guides/installation/upgrading-the-github-enterprise-virtual-machine/
- - /enterprise/admin/guides/installation/upgrade-packages-for-older-releases/
- - /enterprise/admin/articles/upgrading-older-installations/
- - /enterprise/admin/hidden/upgrading-older-installations/
- - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch-early-access-program/
- - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch/
- - /enterprise/admin/guides/installation/upgrading-github-enterprise/
- - /enterprise/admin/installation/upgrading-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
-### 准备升级
-
-1. 确定升级策略并选择要升级到的版本。 更多信息请参阅“[升级要求](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)”。
-3. 使用 {% data variables.product.prodname_enterprise_backup_utilities %} 创建全新的主实例备份。 更多信息请参阅 [{% data variables.product.prodname_enterprise_backup_utilities %} README.md 文件](https://github.com/github/backup-utils#readme)。
-4. 如果您要使用升级包进行升级,请为 {% data variables.product.prodname_ghe_server %} 最终用户排定维护窗口。 如果您要使用热补丁,则不需要使用维护模式。
-
- {% note %}
-
- **注**:维护窗口取决于所执行升级的类型。 使用热补丁进行升级通常不需要维护窗口。 有时需要重启,不过您可以在之后的某个时间重启。 按照 MAJOR.FEATURE.PATCH 的版本控制方案,使用升级包的补丁版本通常需要不到 5 分钟的停机时间。 包含数据迁移的功能版本需要的时间更长,具体视存储性能以及迁移的数据量而定。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
-
- {% endnote %}
-
-### 生成快照
-
-快照是虚拟机 (VM) 在某一时间点的检查点。 强烈建议在升级虚拟机之前生成快照,这样一来,如果升级失败,您可以将 VM 还原到快照状态。 如果您要升级到新的功能版本,则必须生成 VM 快照。 如果您要升级到补丁版本,可以连接现有数据磁盘。
-
-有两种类型的快照:
-
-- **VM 快照**会保存整个 VM 状态,包括用户数据和配置数据。 此快照方法需要占用大量磁盘空间,且比较耗时。
-- **数据磁盘快照**仅会保存您的用户数据。
-
- {% note %}
-
- **注:**
- - 某些平台不允许您只生成数据磁盘的快照。 对于此类平台,您需要生成整个 VM 的快照。
- - 如果您的虚拟机监控程序不支持完整的 VM 快照,您应连续、快速地生成根磁盘和数据磁盘的快照。
-
- {% endnote %}
-
-| 平台 | 快照方法 | 快照文档 URL |
-| --------------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Amazon AWS | 磁盘 | |
-| Azure | VM | |
-| Hyper-V | VM | |
-| Google Compute Engine | 磁盘 | |
-| VMware | VM | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) |
-| XenServer | VM | |
-
-### 使用热补丁升级
-
-{% data reusables.enterprise_installation.hotpatching-explanation %} 利用 {% data variables.enterprise.management_console %},您可以立即安装热补丁,也可以排定稍后安装热补丁。 您可以使用管理 shell 的 `ghe-upgrade` 实用程序安装热补丁。 更多信息请参阅“[升级要求](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)”。
-
-{% note %}
-
-**注**:无法在集群环境中使用 {% data variables.enterprise.management_console %} 安装热补丁。 要在集群环境中安装热补丁,请参阅“[升级集群](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)”。
-
-{% endnote %}
-
-#### 使用热补丁升级单个设备
-
-##### 使用 {% data variables.enterprise.management_console %} 安装热补丁
-
-1. 启用自动更新。 更多信息请参阅“[启用自动更新](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)”。
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.updates-tab %}
-4. 在新的热补丁下载完毕后,请使用 Install package 下拉菜单:
- - 要立即安装,请选择 **Now**:
- - 要稍后安装,请选择以后的日期。 ![热补丁安装日期下拉菜单](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png)
-5. 单击 **Install**。 ![热补丁安装按钮](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png)
-
-##### 使用管理 shell 安装热补丁
-
-{% data reusables.enterprise_installation.download-note %}
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} 复制升级热补丁包(*.hpkg* 文件)的 URL。
-{% data reusables.enterprise_installation.download-package %}
-4. 使用包文件名运行 `ghe-upgrade` 命令:
- ```shell
- admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.hpkg
- *** verifying upgrade package signature...
- ```
-5. 如果更新内核、MySQL、Elasticsearch 或其他程序时需要重启,热补丁升级脚本会通知您。
-
-#### 使用热补丁升级包含副本实例的设备
-
-{% note %}
-
-**注**:如果要安装热补丁,则无需进入维护模式或停止复制。
-
-{% endnote %}
-
-配置为高可用性和 Geo-replication 的设备除了会使用主实例之外,还会使用副本实例。 要升级此类设备,您需要逐个升级主实例和所有副本实例。
-
-##### 升级主实例
-
-1. 请按照“[使用管理 shell 安装热补丁](#installing-a-hotpatch-using-the-administrative-shell)”中的说明升级主实例。
-
-##### 升级副本实例
-
-{% note %}
-
-**注**:如果您要将多个副本实例作为 Geo-replication 的一部分运行,请逐一为每个副本实例重复此步骤。
-
-{% endnote %}
-
-1. 请按照“[使用管理 shell 安装热补丁](#installing-a-hotpatch-using-the-administrative-shell)”中的说明升级副本实例。如果您为 Geo-replication 使用多个副本,则必须重复此步骤,逐一升级每个副本。
-{% data reusables.enterprise_installation.replica-ssh %}
-{% data reusables.enterprise_installation.replica-verify %}
-
-### 使用升级包升级
-
-虽然您可以使用热补丁升级到功能系列中的最新补丁版本,但必须使用升级包升级到更新的功能版本。 例如,要从 `2.11.10` 升级到 `2.12.4`,您必须使用升级包,因为两者在不同的功能系列中。 更多信息请参阅“[升级要求](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)”。
-
-#### 使用升级包升级单个设备
-
-{% data reusables.enterprise_installation.download-note %}
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} 选择适当的平台并复制升级包(*.pkg* 文件)的 URL。
-{% data reusables.enterprise_installation.download-package %}
-4. 启用维护模式并等待 {% data variables.product.prodname_ghe_server %} 实例上的所有活动进程完成。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
-
- {% note %}
-
- **注**:升级采用高可用性配置的主设备时,如果您按照“[升级主实例](#upgrading-the-primary-instance)”中的说明操作,设备应当已处于维护模式。
-
- {% endnote %}
-
-5. 使用包文件名运行 `ghe-upgrade` 命令:
- ```shell
- admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.pkg
- *** verifying upgrade package signature...
- ```
-6. 确认您要继续升级,并在包签名得到验证后重新启动。 新的根文件系统会写入辅助分区,实例会在维护模式下自动重启:
- ```shell
- *** 正在应用更新...
- This package will upgrade your installation to version version-number
- Current root partition: /dev/xvda1 [version-number]
- Target root partition: /dev/xvda2
- Proceed with installation? [y/N]
- ```
-7. 对于单个设备升级,请禁用维护模式,以便用户能够使用 {% data variables.product.product_location_enterprise %}。
-
- {% note %}
-
- **注**:升级采用高可用性配置的主设备时,您应当一直处于维护模式,直至已升级所有副本,复制是最新版本。 更多信息请参阅“[升级副本实例](#upgrading-a-replica-instance)”。
-
- {% endnote %}
-
-#### 使用升级包升级包含副本实例的设备
-
-配置为高可用性和 Geo-replication 的设备除了会使用主实例之外,还会使用副本实例。 要升级此类设备,您需要逐个升级主实例和所有副本实例。
-
-##### 升级主实例
-
-{% warning %}
-
-**警告**:复制停止时,如果主实例发生故障,副本升级和复制再次开始之前执行的任何操作都将丢失。
-
-{% endwarning %}
-
-1. 在主实例上,启用维护模式并等待所有活动进程完成。 更多信息请参阅“[启用维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)”。
-{% data reusables.enterprise_installation.replica-ssh %}
-3. 在副本实例或者所有副本实例(如果您将多个副本实例作为 Geo-replication 的一部分运行)上,运行 `ghe-repl-stop` 以停止复制。
-4. 按照“[使用升级包升级单个设备](#upgrading-a-single-appliance-with-an-upgrade-package)”中的说明升级主实例。
-
-##### 升级副本实例
-
-{% note %}
-
-**注**:如果您要将多个副本实例作为 Geo-replication 的一部分运行,请逐一为每个副本实例重复此步骤。
-
-{% endnote %}
-
-1. 按照“[使用升级包升级单个设备](#upgrading-a-single-appliance-with-an-upgrade-package)”中的说明升级副本实例。如果您为 Geo-replication 使用多个副本,则必须重复此步骤,逐一升级每个副本。
-{% data reusables.enterprise_installation.replica-ssh %}
-{% data reusables.enterprise_installation.replica-verify %}
-
-{% data reusables.enterprise_installation.start-replication %}
-
-{% data reusables.enterprise_installation.replication-status %} 如果命令返回 `Replication is not running`,说明复制可能仍在启动。 等待 1 分钟左右,然后再次运行 `ghe-repl-status`。
-
- {% note %}
-
- **注**:在重新同步过程中,`ghe-repl-status` 可能返回预期消息,提示复制落后。
- 例如:`CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists`
-
- {% endnote %}
-
- 如果 `ghe-repl-status` 未返回 `OK`,请执行以下步骤手动启动复制。
-
- 1. 在副本实例上,再次运行 `ghe-repl-setup `。
- {% data reusables.enterprise_installation.start-replication %}
- {% data reusables.enterprise_installation.replication-status %}
-6. 最后一个副本升级完毕且重新同步完成后,请禁用维护模式,以便用户能够使用 {% data variables.product.product_location_enterprise %}。
-
-### 从失败的升级中恢复
-
-如果升级失败或中断,您应将实例还原为其之前的状态。 完成此操作的过程取决于升级类型。
-
-#### 回滚补丁版本
-
-要回滚补丁版本,请使用带 `--allow-patch-rollback` 开关的 `ghe-upgrade` 命令。 {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
-
-更多信息请参阅“[命令行实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)”。
-
-#### 回滚功能版本
-
-要从功能版本回滚,请从 VM 快照恢复,以确保根分区和数据分区处于一致的状态。 更多信息请参阅“[生成快照](#taking-a-snapshot)”。
diff --git a/translations/zh-CN/content/admin/installation/using-github-enterprise-server-with-a-load-balancer.md b/translations/zh-CN/content/admin/installation/using-github-enterprise-server-with-a-load-balancer.md
deleted file mode 100644
index ccbcc46d117f..000000000000
--- a/translations/zh-CN/content/admin/installation/using-github-enterprise-server-with-a-load-balancer.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: 结合使用 GitHub Enterprise Server 和负载均衡器
-intro: '在单个 {% data variables.product.prodname_ghe_server %} 设备或一对采用高可用性配置的设备前方使用负载均衡器。'
-redirect_from:
- - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer/
- - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_clustering.load_balancer_intro %}
-
-{% data reusables.enterprise_clustering.load_balancer_dns %}
-
-### 处理客户端连接信息
-
-由于与 {% data variables.product.prodname_ghe_server %} 的客户端连接来自负载均衡器,因此客户端 IP 可丢失。
-
-{% data reusables.enterprise_clustering.proxy_preference %}
-
-{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
-
-#### 在 {% data variables.product.product_location_enterprise %} 上启用 PROXY 协议支持
-
-强烈建议同时为您的设备和负载均衡器启用 PROXY 协议支持。 按照您的供应商提供的说明操作,在负载均衡器上启用 PROXY 协议。 更多信息请参阅 [PROXY 协议文档](http://www.haproxy.org/download/1.6/doc/proxy-protocol.txt)。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-3. 在 **External load balancers** 下,选择 **Enable support for PROXY protocol**。 ![启用 PROXY 协议支持的复选框](/assets/images/enterprise/management-console/enable-proxy.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-{% data reusables.enterprise_clustering.proxy_protocol_ports %}
-
-#### 在 {% data variables.product.product_location_enterprise %} 上启用 X-Forwarded-For 支持
-
-{% data reusables.enterprise_clustering.x-forwarded-for %}
-
-{% data reusables.enterprise_installation.terminating-tls %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-3. 在 **External load balancers** 下,选择 **Allow HTTP X-Forwarded-For header**。 ![允许 HTTP X-Forwarded-For 标头的复选框](/assets/images/enterprise/management-console/allow-xff.png)
-{% data reusables.enterprise_management_console.save-settings %}
-
-{% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
-
-### 配置健康状态检查
-
-如果预配置的检查在该节点上失败,则状态检查允许负载均衡器停止向未响应的节点发送流量。 如果设备因维护或计划外的故障而离线,负载均衡器可以显示状态页面。 在高可用性 (HA) 配置下,负载均衡器可用作故障转移策略的组成部分。 不过,不支持 HA 对的自动故障转移。 在副本设备开始为请求提供服务之前,您必须手动升级副本设备。 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 以实现高可用性](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)”。
-
-{% data reusables.enterprise_clustering.health_checks %}
-{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
diff --git a/translations/zh-CN/content/admin/installation/validating-your-domain-settings.md b/translations/zh-CN/content/admin/installation/validating-your-domain-settings.md
deleted file mode 100644
index 31152455b3c8..000000000000
--- a/translations/zh-CN/content/admin/installation/validating-your-domain-settings.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: 验证域设置
-intro: '首次启动 {% data variables.product.product_location_enterprise %} 之前,请确保域设置已正确配置。'
-redirect_from:
- - /enterprise/admin/installation/validating-your-domain-settings
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.hostname-menu-item %}
-4. 要测试设备的 DNS 和 SSL 设置,请单击 **Test domain settings**。 ![测试域设置按钮](/assets/images/enterprise/management-console/test-domain-settings.png)
-{% data reusables.enterprise_management_console.test-domain-settings-failure %}
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/installation/viewing-push-logs.md b/translations/zh-CN/content/admin/installation/viewing-push-logs.md
deleted file mode 100644
index c2179771beb4..000000000000
--- a/translations/zh-CN/content/admin/installation/viewing-push-logs.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: 查看推送日志
-intro: '站点管理员可以查看 {% data variables.product.product_location_enterprise %} 上任何仓库的 Git 推送操作列表。'
-redirect_from:
- - /enterprise/admin/articles/viewing-push-logs/
- - /enterprise/admin/installation/viewing-push-logs
-versions:
- enterprise-server: '*'
----
-
-推送日志条目会显示:
-
-- 推送发起人
-- 是否为强制推送
-- 某人推送到的分支
-- 推送所使用的协议
-- 发起的 IP 地址
-- 推送所使用的 Git 客户端
-- 操作前后的 SHA 哈希
-
-### 查看仓库的推送日志
-
-1. 导航到仓库。
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-3. 在页面右上角,单击 {% octicon "shield" aria-label="The shield" %} **Security**。 ![Security 选项卡](/assets/images/enterprise/site-admin-settings/repo/repo-security-top-tab.png)
-4. 在左侧边栏中,单击 **Push Log**。 ![Push Log 选项卡](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
-
-### 在命令行上查看仓库的推送日志
-
-1. 通过 SSH 登录您的设备。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。
-2. 在相应的 Git 仓库中,打开审核日志文件:
- ```shell
- ghe-repo owner/repository -c "less audit_log"
- ```
diff --git a/translations/zh-CN/content/admin/migrations/about-migrations.md b/translations/zh-CN/content/admin/migrations/about-migrations.md
deleted file mode 100644
index 9096bae878af..000000000000
--- a/translations/zh-CN/content/admin/migrations/about-migrations.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: 关于迁移
-intro: '迁移是将数据从*源*位置({% data variables.product.prodname_dotcom_the_website %} 组织或 {% data variables.product.prodname_ghe_server %} 实例)转移到*目标* {% data variables.product.prodname_ghe_server %} 实例的过程。 在更换平台或或升级实例上的硬件时,可以使用迁移转移数据。'
-redirect_from:
- - /enterprise/admin/migrations/about-migrations
-versions:
- enterprise-server: '*'
----
-
-### 迁移类型
-
-您可以执行三种类型的迁移:
-
-- 从 {% data variables.product.prodname_ghe_server %} 实例迁移到另一个 {% data variables.product.prodname_ghe_server %} 实例。 您可以迁移实例上由任何用户或组织拥有的任意数量的仓库。 在执行迁移之前,您必须具有两个实例的站点管理员访问权限。
-- 从 {% data variables.product.prodname_dotcom_the_website %} 组织迁移到 {% data variables.product.prodname_ghe_server %} 实例。 您可以迁移由组织拥有的任意数量的仓库。 在执行迁移前,您必须拥有 {% data variables.product.prodname_dotcom_the_website %} 组织的[管理访问权限](/enterprise/user/articles/permission-levels-for-an-organization/)和目标实例的站点管理员访问权限。
-- *试运行*是将数据导入[暂存实例](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)的迁移。 这些试运行非常有用,可用于查看在向 {% data variables.product.product_location_enterprise %} 应用迁移后*将要*发生的变化。 **我们强烈建议您先在暂存实例上执行试运行,然后再将数据导入生产实例。**
-
-### 迁移的数据
-
-在迁移中,一切都围绕仓库进行。 与仓库关联的大多数数据都可以迁移。 例如,组织内的仓库将迁移仓库*和*组织,以及与该仓库关联的任何用户、团队、问题和拉取请求。
-
-下表中的项可随仓库一起迁移。 迁移的数据列表中未显示的任何项都无法迁移。
-
-{% data reusables.enterprise_migrations.fork-persistence %}
-
-| 与迁移的仓库关联的数据 | 注: |
-| -------------- | --------------------------------------------------------------------------------------------- |
-| 用户 | 用户的 **@提及**将重写以匹配目标。 |
-| 组织 | 将迁移组织的名称和详细信息。 |
-| 仓库 | Git 树、blob、提交和行的链接将重写以匹配目标。 迁移程序将遵循三个仓库重定向的最大值。 |
-| Wikis | 将迁移所有 wiki 数据。 |
-| 团队 | 团队的 **@提及**将重写以匹配目标。 |
-| 里程碑 | 将保留时间戳。 |
-| 项目板 | 将迁移与仓库和拥有仓库的组织关联的项目板。 |
-| 议题 | 将保留问题引用和时间戳。 |
-| 问题评论 | 将针对目标实例重写评论的交叉引用。 |
-| 拉取请求 | 将重写拉取请求的交叉引用以匹配目标。 将保留时间戳。 |
-| 拉取请求审查 | 将迁移拉取请求审查和关联的数据。 |
-| 拉取请求审查评论 | 将针对目标实例重写评论的交叉引用。 将保留时间戳。 |
-| 提交注释 | 将针对目标实例重写评论的交叉引用。 将保留时间戳。 |
-| 版本发布 | 将迁移所有版本数据。 |
-| 在拉取请求或问题上进行的操作 | 将保留对拉取请求或问题的所有修改(例如,分配用户、重命名标题和修改标签)以及每个操作的时间戳。 |
-| 文件附件 | 将迁移[问题和拉取请求上的文件附件](/articles/file-attachments-on-issues-and-pull-requests)。 在迁移过程中,您可以选择将此禁用。 |
-| Web 挂钩 | 仅迁移有效的 web 挂钩。 |
-| 仓库部署密钥 | 将迁移仓库部署密钥。 |
-| 受保护分支 | 将迁移受保护分支设置和关联的数据。 |
diff --git a/translations/zh-CN/content/admin/migrations/applying-the-imported-data-on-github-enterprise-server.md b/translations/zh-CN/content/admin/migrations/applying-the-imported-data-on-github-enterprise-server.md
deleted file mode 100644
index 9f2ba5cd4512..000000000000
--- a/translations/zh-CN/content/admin/migrations/applying-the-imported-data-on-github-enterprise-server.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 在 GitHub Enterprise Server 上应用导入的数据
-intro: 审查完迁移数据后,您可以向目标实例永久应用变更。
-redirect_from:
- - /enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise/
- - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_installation.ssh-into-target-instance %}
-
-2. 使用 `ghe-migrator import` 命令启动导入过程。 您需要:
- * 迁移 GUID.
- * 用于身份验证的个人访问令牌。 您使用的个人访问令牌仅用于站点管理员身份验证,不需要任何特定范围。 For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-
- ```shell
- $ ghe-migrator import /home/admin/MIGRATION_GUID.tar.gz -g MIGRATION_GUID -u username -p TOKEN
-
- > Starting GitHub::Migrator
- > Import 100% complete /
- ```
-
- * {% data reusables.enterprise_migrations.specify-staging-path %}
diff --git a/translations/zh-CN/content/admin/migrations/completing-the-import-on-github-enterprise-server.md b/translations/zh-CN/content/admin/migrations/completing-the-import-on-github-enterprise-server.md
deleted file mode 100644
index 3d152b33a410..000000000000
--- a/translations/zh-CN/content/admin/migrations/completing-the-import-on-github-enterprise-server.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: 在 GitHub Enterprise Server 上完成导入
-intro: 在迁移应用到目标实例并且您已审查迁移后,您需要解锁仓库并将其从源中删除。 我们建议等待两周再删除您的源数据,以便确保所有数据都能按预期运行。
-redirect_from:
- - /enterprise/admin/guides/migrations/completing-the-import-on-github-enterprise/
- - /enterprise/admin/migrations/completing-the-import-on-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
-### 在目标实例上解锁仓库
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-{% data reusables.enterprise_migrations.unlocking-on-instances %}
-
-### 在源上解锁仓库
-
-#### 从 {% data variables.product.prodname_dotcom_the_website %} 组织解锁仓库
-
-要在 {% data variables.product.prodname_dotcom_the_website %} 组织中解锁仓库,您需要向迁移解锁端点发送 `DELETE` 请求。 您需要:
- * 身份验证的访问令牌
- * 迁移的唯一 `id`
- * 要解锁的仓库的名称
-```shell
-curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \
- -H "Accept: application/vnd.github.wyandotte-preview+json" \
- https://api.github.com/orgs/orgname/migrations/id/repos/repo_name/lock
-```
-
-#### 从 {% data variables.product.prodname_dotcom_the_website %} 组织删除仓库
-
-After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository). 您需要身份验证的访问令牌:
-```shell
-curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \
- https://api.github.com/repos/orgname/repo_name
-```
-
-#### 从 {% data variables.product.prodname_ghe_server %} 实例解锁仓库
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-{% data reusables.enterprise_migrations.unlocking-on-instances %}
diff --git a/translations/zh-CN/content/admin/migrations/exporting-migration-data-from-github-enterprise-server.md b/translations/zh-CN/content/admin/migrations/exporting-migration-data-from-github-enterprise-server.md
deleted file mode 100644
index 95e0f536bc30..000000000000
--- a/translations/zh-CN/content/admin/migrations/exporting-migration-data-from-github-enterprise-server.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 从 GitHub Enterprise Server 导出迁移数据
-intro: '要从 {% data variables.product.prodname_ghe_server %} 实例导出迁移数据,您需要准备实例,锁定仓库,并生成迁移存档。 如果您计划更换平台或已准备好从试用实例转到生产实例,则应从 {% data variables.product.prodname_ghe_server %} 实例导出数据。'
-redirect_from:
- - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise/
- - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/migrations/exporting-migration-data-from-githubcom.md b/translations/zh-CN/content/admin/migrations/exporting-migration-data-from-githubcom.md
deleted file mode 100644
index 899ccad92922..000000000000
--- a/translations/zh-CN/content/admin/migrations/exporting-migration-data-from-githubcom.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 从 GitHub.com 导出迁移数据
-intro: '要从 {% data variables.product.prodname_dotcom_the_website %} 组织导出迁移数据,您需要使用 API 选择要迁移的仓库。 之后,您将生成一个可以导入 {% data variables.product.prodname_ghe_server %} 实例的迁移存档。'
-redirect_from:
- - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-com
- - /enterprise/admin/migrations/exporting-migration-data-from-githubcom
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/migrations/exporting-the-github-enterprise-server-source-repositories.md b/translations/zh-CN/content/admin/migrations/exporting-the-github-enterprise-server-source-repositories.md
deleted file mode 100644
index 216b51cd1ad2..000000000000
--- a/translations/zh-CN/content/admin/migrations/exporting-the-github-enterprise-server-source-repositories.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: 导出 GitHub Enterprise Server 源仓库
-intro: 在锁定源仓库后,您可以一次导出一个,或者使用文本文件格式的仓库 URL 列表批量导出。 随后,您可以创建一个迁移存档,用于导入。
-redirect_from:
- - /enterprise/admin/guides/migrations/exporting-the-github-enterprise-source-repositories/
- - /enterprise/admin/migrations/exporting-the-github-enterprise-server-source-repositories
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_migrations.locking-repositories %}
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. 要准备需要导出的仓库,请使用 `ghe-migrator add` 命令和仓库的 URL:
- * 如果您要锁定仓库,请在命令后附加 `--lock`。 如果您执行的是试运行,则不需要 `--lock`。
- ```shell
- $ ghe-migrator add https://hostname/username/reponame --lock
- ```
- * 您可以将 `--exclude_attachments` 附加到命令,排除文件附件。 {% data reusables.enterprise_migrations.exclude-file-attachments %}
- * 要一次准备多个将导出的仓库,请创建一个文本文件并在单独的行中列出每个仓库 URL,然后运行包含 `-i` 标志和您的文本文件路径的 `ghe-migrator add` 命令。
- ```shell
- $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URLS.txt
- ```
-
-3. 出现提示时,请输入您的 {% data variables.product.prodname_ghe_server %} 用户名:
- ```shell
- Enter username authorized for migration: admin
- ```
-4. 出现输入个人访问令牌的提示时,请输入您在“[准备 {% data variables.product.prodname_ghe_server %} 源实例](/enterprise/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance/)”中创建的访问令牌:
- ```shell
- Enter personal access token: **************
- ```
-5. 在 `ghe-migrator add` 完成后,它将打印自身生成并用于标识此导出的唯一的“迁移 GUID”以及添加到导出中的资源列表。 在后续的 `ghe-migrator add` 和 `ghe-migrator export` 步骤中,您将使用它生成的迁移 GUID 指示 `ghe-migrator` 继续在同一个导出上操作。
- ```shell
- > 101 models added to export
- > Migration GUID: example-migration-guid
- > Number of records in this migration:
- > users | 5
- > organizations | 1
- > repositories | 1
- > teams | 3
- > protected_branches | 1
- > pull_request_reviews | 1
- > milestones | 1
- > issues | 3
- > pull_requests | 5
- > pull_request_review_comments | 4
- > commit_comments | 2
- > issue_comments | 10
- > issue_events | 63
- > releases | 3
- > attachments | 4
- > projects | 2
- ```
- 每次您添加包含现有迁移 GUID 的新仓库时,它都会更新现有导出。 如果您在没有迁移 GUID的情况下再次运行 `ghe-migrator add`,将会启动新的导出并生成新的迁移 GUID。 **开始准备要导入的迁移时,不要再次使用在导出过程中生成的迁移 GUID**。
-
-3. 如果您锁定了源仓库,则可以使用 `ghe-migrator target_url` 命令,在链接到仓库新位置的仓库页面上设置自定义锁定消息。 传递源仓库 URL、目标仓库 URL 和第 5 步中的迁移 GUID:
-
- ```shell
- $ ghe-migrator target_url https://hostname/username/reponame https://target_hostname/target_username/target_reponame -g MIGRATION_GUID
- ```
-
-6. 要向同一个导出添加更多仓库,请使用包含 `-g` 标志的 `ghe-migrator add` 命令。 您需要传入新仓库 URL 和第 5 步中的迁移 GUID:
- ```shell
- $ ghe-migrator add https://hostname/username/other_reponame -g MIGRATION_GUID --lock
- ```
-7. 添加完仓库后,请使用包含 `-g` 标志和第 5 步中的迁移 GUID 的 `ghe-migrator export` 命令生成迁移存档:
- ```shell
- $ ghe-migrator export -g MIGRATION_GUID
- > Archive saved to: /data/github/current/tmp/MIGRATION_GUID.tar.gz
- ```
- * {% data reusables.enterprise_migrations.specify-staging-path %}
-
-8. 关闭与 {% data variables.product.product_location_enterprise %} 的连接:
- ```shell
- $ exit
- > logout
- > Connection to hostname closed.
- ```
-9. 使用 [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) 命令将迁移存档复制到您的计算机。 存档文件将使用迁移 GUID 命名:
- ```shell
- $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop
- ```
-{% data reusables.enterprise_migrations.ready-to-import-migrations %}
diff --git a/translations/zh-CN/content/admin/migrations/exporting-the-githubcom-organizations-repositories.md b/translations/zh-CN/content/admin/migrations/exporting-the-githubcom-organizations-repositories.md
deleted file mode 100644
index c784e3f996af..000000000000
--- a/translations/zh-CN/content/admin/migrations/exporting-the-githubcom-organizations-repositories.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: 导出 GitHub.com 组织的仓库
-intro: 使用 Migrations API,您可以导出组织的仓库。 在导出仓库后,您可以下载能够用于导入过程的迁移存档。
-redirect_from:
- - /enterprise/admin/guides/migrations/exporting-the-github-com-organization-s-repositories
- - /enterprise/admin/migrations/exporting-the-githubcom-organizations-repositories
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_migrations.fork-persistence %}
-
-要从 {% data variables.product.prodname_dotcom_the_website %} 导出仓库数据,请使用 Migrations API。
-
-Migrations API 目前正处于预览阶段,这意味着端点和参数未来可能发生变化。 要访问 Migrations API,您必须在 `Accept` 标头中提供自定义[媒体类型](/v3/media):`application/vnd.github.wyandotte-preview+json`。 以下示例包括自定义媒体类型。
-
-### 生成迁移存档
-
-{% data reusables.enterprise_migrations.locking-repositories %}
-
-1. 向您的组织的成员发送通知,告诉他们您将执行迁移。 导出可能需要数分钟的时间,具体取决于要导出的仓库数量。 包括导入的完整迁移可能需要数小时的时间,因此我们建议执行试运行,以便确定完整过程所需的时间。 更多信息请参阅“[关于迁移](/enterprise/admin/migrations/about-migrations#types-of-migrations)”。
-
-2. 向迁移端点发送 `POST` 请求,开始迁移。 您需要:
- * 身份验证的访问令牌。
- * 想要迁移的[仓库列表](/v3/repos/#list-organization-repositories):
- ```shell
- curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X POST \
- -H "Accept: application/vnd.github.wyandotte-preview+json" \
- -d'{"lock_repositories":true,"repositories":["orgname/reponame", "orgname/reponame"]}' \
- https://api.github.com/orgs/orgname/migrations
- ```
- * 如果您想在迁移仓库之前先将其锁定,请确保 `lock_repositories` 设为 `true`。 强烈建议执行此操作。
- * 您可以向端点传递 `exclude_attachments: true`,排除文件附件。 {% data reusables.enterprise_migrations.exclude-file-attachments %}存档的最终大小必须小于 20 GB。
-
- 此请求将返回一个独一无二的 `id`,用于表示您的迁移。 后续调用 Migrations API 时需要使用此 id。
-
-3. 向迁移状态端点发送 `GET` 请求以提取迁移的状态。 您需要:
- * 身份验证的访问令牌。
- * 迁移的唯一 `id`:
- ```shell
- curl -H "Authorization: token GITHUB_ACCESS_TOKEN" \
- -H "Accept: application/vnd.github.wyandotte-preview+json" \
- https://api.github.com/orgs/orgname/migrations/id
- ```
-
- 迁移可能处于以下状态之一:
- * `pending`,表示迁移尚未开始。
- * `exporting`,表示迁移正在进行。
- * `exported`,表示迁移已成功完成。
- * `failed`,表示迁移失败。
-
-4. 在导出您的迁移后,请向迁移下载端点发送 `GET` 请求,下载迁移存档。 您需要:
- * 身份验证的访问令牌。
- * 迁移的唯一 `id`:
- ```shell
- curl -H "Accept: application/vnd.github.wyandotte-preview+json" \
- -u GITHUB_USERNAME:GITHUB_ACCESS_TOKEN \
- -L -o migration_archive.tar.gz \
- https://api.github.com/orgs/orgname/migrations/id/archive
- ```
-
-5. 迁移存档将在七天后自动删除。 如果您更喜欢提前删除,可以向迁移存档删除端点发送 `DELETE` 请求。 您需要:
- * 身份验证的访问令牌。
- * 迁移的唯一 `id`:
- ```shell
- curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \
- -H "Accept: application/vnd.github.wyandotte-preview+json" \
- https://api.github.com/orgs/orgname/migrations/id/archive
- ```
-{% data reusables.enterprise_migrations.ready-to-import-migrations %}
diff --git a/translations/zh-CN/content/admin/migrations/generating-a-list-of-migration-conflicts.md b/translations/zh-CN/content/admin/migrations/generating-a-list-of-migration-conflicts.md
deleted file mode 100644
index 9fe23d6bc3e7..000000000000
--- a/translations/zh-CN/content/admin/migrations/generating-a-list-of-migration-conflicts.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: 生成迁移冲突列表
-intro: 如果 `ghe-migrator` 在准备要导入的数据时报告冲突,您必须先生成这些冲突的列表,然后再准备使用自定义映射加以解决。
-redirect_from:
- - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts
-versions:
- enterprise-server: '*'
----
-
-1. 使用包含迁移 GUID 的 `ghe-migrator conflicts` 命令生成一个 *conflicts.csv* 文件:
- ```shell
- $ ghe-migrator conflicts -g MIGRATION_GUID > conflicts.csv
- ```
- - 如果未报告冲突,您可以按照“[在 {% data variables.product.prodname_ghe_server %} 上应用导入的数据](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)”中的步骤操作,安全地导入数据。
-2. 如果存在冲突,请使用 [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) 命令将 *conflicts.csv* 复制到您的本地计算机:
- ```shell
- $ scp -P 122 admin@hostname:conflicts.csv ~/Desktop
- ```
-3. 继续“[解决迁移冲突或设置自定义映射](/enterprise/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings/)”。
diff --git a/translations/zh-CN/content/admin/migrations/importing-data-from-third-party-version-control-systems.md b/translations/zh-CN/content/admin/migrations/importing-data-from-third-party-version-control-systems.md
deleted file mode 100644
index d030fd1022c4..000000000000
--- a/translations/zh-CN/content/admin/migrations/importing-data-from-third-party-version-control-systems.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: 从第三方版本控制系统导入数据
-intro: '使用工具的 git-import 套件,您可以将数据从 Subversion、Mercurial 和 Team Foundation Version Control 导入 {% data variables.product.prodname_ghe_server %} 上的 Git 仓库。'
-redirect_from:
- - /enterprise/admin/migrations/importing-data-from-third-party-version-control-systems
-versions:
- enterprise-server: '*'
----
-
-### 从 Mercurial 导入项目
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. 使用以下命令对项目进行原始克隆,并指定源项目的 URL 和临时仓库的路径:
- ```shell
- $ git-import-hg-raw HG-CLONE-URL /PATH/REPO-NAME.git
- # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
- ```
-{% data reusables.enterprise_migrations.review-the-import-csv %}
-4. 使用 CSV 文件重写作者和分支:
- ```shell
- $ git-import-rewrite --flavor hg --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git
- ```
-5. 如果您还没有创建,请[在 {% data variables.product.prodname_ghe_server %} 上创建新的空仓库](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository)。
-{% data reusables.command_line.switching_directories_procedural %}
-7. 将导入的仓库推送到 {% data variables.product.prodname_ghe_server %}:
- ```shell
- $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE
- ```
-
-### 从 Subversion 导入项目
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. 使用以下命令对项目进行原始克隆,并指定源项目的 URL 和临时仓库的路径:
- ```shell
- $ git-import-svn-raw SVN-CLONE-URL /PATH/REPO-NAME.git
- # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
- ```
-{% data reusables.enterprise_migrations.review-the-import-csv %}
-4. 使用 CSV 文件重写作者和分支:
- ```shell
- $ git-import-rewrite --flavor svn --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git
- ```
-5. 如果您还没有创建,请[在 {% data variables.product.prodname_ghe_server %} 上创建新的空仓库](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository)。
-{% data reusables.command_line.switching_directories_procedural %}
-7. 将导入的仓库推送到 {% data variables.product.prodname_ghe_server %}:
- ```shell
- $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE
- ```
-
-### 从 Team Foundation Version Control 导入项目
-
-{% data reusables.enterprise_installation.ssh-into-instance %}
-2. 使用以下命令对项目进行原始克隆,并指定源项目的 URL 和临时仓库的路径:
- ```shell
- $ git-import-tfs-raw TEAM-FOUNDATION-CLONE-URL /PATH/REPO-NAME.git
- # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
- ```
-{% data reusables.enterprise_migrations.review-the-import-csv %}
-4. 使用 CSV 文件重写作者和分支:
- ```shell
- $ git-import-rewrite --flavor tfs --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git
- ```
-5. 如果您还没有创建,请[在 {% data variables.product.prodname_ghe_server %} 上创建新的空仓库](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository)。
-{% data reusables.command_line.switching_directories_procedural %}
-7. 将导入的仓库推送到 {% data variables.product.prodname_ghe_server %}:
- ```shell
- $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE
- ```
-
-### 延伸阅读
-
-- "[Command-line-utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#import-and-export)"
diff --git a/translations/zh-CN/content/admin/migrations/importing-migration-data-to-github-enterprise-server.md b/translations/zh-CN/content/admin/migrations/importing-migration-data-to-github-enterprise-server.md
deleted file mode 100644
index b0cad855dfc7..000000000000
--- a/translations/zh-CN/content/admin/migrations/importing-migration-data-to-github-enterprise-server.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 将迁移数据导入 GitHub Enterprise Server
-intro: '生成迁移存档后,您可以将数据导入目标 {% data variables.product.prodname_ghe_server %} 实例。 在将变更永久应用到目标实例之前,您需要检查变更,查看有无潜在的冲突。'
-redirect_from:
- - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise/
- - /enterprise/admin/migrations/importing-migration-data-to-github-enterprise-server
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/migrations/index.md b/translations/zh-CN/content/admin/migrations/index.md
deleted file mode 100644
index 389a0d710a97..000000000000
--- a/translations/zh-CN/content/admin/migrations/index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: 迁移用户、组织和仓库数据
-shortTitle: 迁移数据
-intro: '您可以从 {% data variables.product.prodname_ghe_server %} 或 {% data variables.product.prodname_dotcom_the_website %} 导出用户、组织和仓库数据,然后将此数据导入至 {% data variables.product.product_location_enterprise %}。'
-redirect_from:
- - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/
- - /enterprise/admin/categories/migrations-and-upgrades/
- - /enterprise/admin/migrations
-versions:
- enterprise-server: '*'
----
-
-
-### 目录
-
-{% topic_link_in_list /overview %}
- {% link_in_list /about-migrations %}
-{% topic_link_in_list /exporting-migration-data-from-github-enterprise-server %}
- {% link_in_list /preparing-the-github-enterprise-server-source-instance %}
- {% link_in_list /exporting-the-github-enterprise-server-source-repositories %}
-{% topic_link_in_list /exporting-migration-data-from-githubcom %}
- {% link_in_list /preparing-the-githubcom-source-organization %}
- {% link_in_list /exporting-the-githubcom-organizations-repositories %}
-{% topic_link_in_list /importing-migration-data-to-github-enterprise-server %}
- {% link_in_list /preparing-the-migrated-data-for-import-to-github-enterprise-server %}
- {% link_in_list /generating-a-list-of-migration-conflicts %}
- {% link_in_list /reviewing-migration-conflicts %}
- {% link_in_list /resolving-migration-conflicts-or-setting-up-custom-mappings %}
- {% link_in_list /applying-the-imported-data-on-github-enterprise-server %}
- {% link_in_list /reviewing-migration-data %}
- {% link_in_list /completing-the-import-on-github-enterprise-server %}
- {% link_in_list /importing-data-from-third-party-version-control-systems %}
diff --git a/translations/zh-CN/content/admin/migrations/overview.md b/translations/zh-CN/content/admin/migrations/overview.md
deleted file mode 100644
index aa56e8065744..000000000000
--- a/translations/zh-CN/content/admin/migrations/overview.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 概览
-intro: '了解如何将数据迁移至 {% data variables.product.product_location_enterprise %}。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/migrations/overview
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/migrations/preparing-the-github-enterprise-server-source-instance.md b/translations/zh-CN/content/admin/migrations/preparing-the-github-enterprise-server-source-instance.md
deleted file mode 100644
index d810e780202e..000000000000
--- a/translations/zh-CN/content/admin/migrations/preparing-the-github-enterprise-server-source-instance.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: 准备 GitHub Enterprise Server 源实例
-intro: '在从 {% data variables.product.prodname_ghe_server %} 迁移数据之前,请确保您具有实例的适当身份验证和管理权限。'
-redirect_from:
- - /enterprise/admin/guides/migrations/preparing-the-github-enterprise-source-instance/
- - /enterprise/admin/migrations/preparing-the-github-enterprise-server-source-instance
-versions:
- enterprise-server: '*'
----
-
-1. 验证您在 {% data variables.product.prodname_ghe_server %} 源上是站点管理员。 最好的方式是验证您可以[通过 SSH 访问实例](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)。
-
-2. 在 {% data variables.product.prodname_ghe_server %} 源实例上{% data reusables.enterprise_migrations.token-generation %}。
-
-{% data reusables.enterprise_migrations.make-a-list %}
diff --git a/translations/zh-CN/content/admin/migrations/preparing-the-githubcom-source-organization.md b/translations/zh-CN/content/admin/migrations/preparing-the-githubcom-source-organization.md
deleted file mode 100644
index d5933c3eb47d..000000000000
--- a/translations/zh-CN/content/admin/migrations/preparing-the-githubcom-source-organization.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: 准备 GitHub.com 源组织
-intro: '在从 {% data variables.product.prodname_dotcom_the_website %} 组织迁移仓库之前,请确保您有适当的身份验证和管理权限。'
-redirect_from:
- - /enterprise/admin/guides/migrations/preparing-the-github-com-source-organization
- - /enterprise/admin/migrations/preparing-the-githubcom-source-organization
-versions:
- enterprise-server: '*'
----
-
-1. 确保您在源组织的仓库上具有[所有者权限](/articles/permission-levels-for-an-organization/)。
-
-2. 在 {% data variables.product.prodname_dotcom_the_website %} 上{% data reusables.enterprise_migrations.token-generation %}
-
-{% data reusables.enterprise_migrations.make-a-list %}
diff --git a/translations/zh-CN/content/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server.md b/translations/zh-CN/content/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server.md
deleted file mode 100644
index 91b97c289a61..000000000000
--- a/translations/zh-CN/content/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: 准备要导入 GitHub Enterprise Server 的迁移数据
-intro: 在将迁移的数据应用到您的目标实例之前,您需要将迁移存档复制到目标实例,并针对导入进行准备。
-redirect_from:
- - /enterprise/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise/
- - /enterprise/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server
-versions:
- enterprise-server: '*'
----
-
-1. 使用 [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) 命令将从源实例或组织生成的迁移存档复制到 {% data variables.product.prodname_ghe_server %} 目标:
-
- ```shell
- $ scp -P 122 /path/to/archive/MIGRATION_GUID.tar.gz admin@hostname:/home/admin/
- ```
-
-{% data reusables.enterprise_installation.ssh-into-target-instance %}
-
-3. 使用 `ghe-migrator prepare` 命令准备要在目标实例上导入的存档,并生成新的迁移 GUID 供您在后续步骤中使用:
-
- ```shell
- ghe-migrator prepare /home/admin/MIGRATION_GUID.tar.gz
- ```
-
- * 要开始新的导入尝试,请再次运行 `ghe-migrator prepare` 并获取新的迁移 GUID。
- * {% data reusables.enterprise_migrations.specify-staging-path %}
diff --git a/translations/zh-CN/content/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings.md b/translations/zh-CN/content/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings.md
deleted file mode 100644
index 71cb6b158d23..000000000000
--- a/translations/zh-CN/content/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: 解决迁移冲突或设置自定义映射
-intro: 在导入迁移数据之前,您可以进行修改以解决冲突、重命名传入的记录或将传入的记录映射到现有记录。
-redirect_from:
- - /enterprise/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings
-versions:
- enterprise-server: '*'
----
-
-以下步骤可用于解决冲突或向迁移添加自定义映射。
-
-### 解决冲突
-
-如果您认为 `ghe-migrator` 将执行不正确的变更,可以更改 *conflicts.csv* 中的数据,进行修改。 您可以更改 *conflicts.csv* 中的任意行。
-
-例如,我们假设您注意到源中的 `octocat` 用户正在被映射到目标上的 `octocat`:
-
-| `model_name` | `source_url` | `target_url` | `recommended_action` |
-| ------------ | ----------------------------------- | ----------------------------------- | -------------------- |
-| `用户` | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map` |
-
-您可以选择将用户映射到目标上的其他用户。 假设您知道 `octocat` 在目标上应当是 `monalisa`。 您可以更改 *conflicts.csv* 中的 `target_url` 列以指代 `monalisa`:
-
-| `model_name` | `source_url` | `target_url` | `recommended_action` |
-| ------------ | ----------------------------------- | ------------------------------------ | -------------------- |
-| `用户` | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `map` |
-
-另外,如果您想在目标实例上将 `octo-org/widgets` 仓库重命名为 `octo-org/amazing-widgets`,请将 `target_url` 更改为 `octo-org/amazing-widgets`,以及将 `recommend_action` 更改为 `rename`:
-
-| `model_name` | `source_url` | `target_url` | `recommended_action` |
-| ------------ | -------------------------------------------- | ---------------------------------------------------- | -------------------- |
-| `仓库` | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename` |
-
-### 添加自定义映射
-
-迁移过程中一个常见的情况是,迁移用户的用户名在目标上与在源上不同。
-
-如果拥有源中的用户名列表和目标上的用户名列表,您可以通过自定义映射构建一个 CSV 文件,然后应用此文件,确保迁移结束时每个用户的用户名和内容都有正确的映射。
-
-您可以使用 [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) 命令,快速生成应用自定义映射所需的迁移用户的 CSV 文件:
-
-```shell
-$ ghe-migrator audit -m user -g MIGRATION_GUID > users.csv
-```
-
-现在,您可以编辑该 CSV,并为您想要映射或重命名的每个用户输入新的 URL,然后根据需要将第四列更新为 `map` 或 `rename`。
-
-例如,要在目标 `https://example-gh.target` 上将用户 `octocat` 重命名为 `monalisa`,您需要创建一个包含以下内容的行:
-
-| `model_name` | `source_url` | `target_url` | `state` |
-| ------------ | ----------------------------------- | ------------------------------------ | -------- |
-| `用户` | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `rename` |
-
-可以使用相同的流程为支持自定义映射的每个记录创建映射。 更多信息请参见[记录的可能映射表](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type)。
-
-### 应用修改的迁移数据
-
-1. 进行更改后,请使用 [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) 命令将修改后的 *conflicts.csv*(或格式正确的任何其他映射 csv)应用到目标实例:
-
- ```shell
- $ scp -P 122 ~/Desktop/conflicts.csv admin@hostname:/home/admin/
- ```
-
-2. 使用 `ghe-migrator map` 命令重新映射迁移数据,并传入修改后的 csv 文件的路径和迁移 GUID:
-
- ```shell
- $ ghe-migrator map -i conflicts.csv -g MIGRATION_GUID
- ```
-
-3. 如果 `ghe-migrator map -i conflicts.csv -g MIGRATION_GUID` 命令报告冲突仍然存在,请重新运行迁移冲突解决流程。
diff --git a/translations/zh-CN/content/admin/migrations/reviewing-migration-conflicts.md b/translations/zh-CN/content/admin/migrations/reviewing-migration-conflicts.md
deleted file mode 100644
index 3135b823831c..000000000000
--- a/translations/zh-CN/content/admin/migrations/reviewing-migration-conflicts.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: 检查迁移冲突
-intro: 在生成迁移冲突列表后,您应当进行检查,以确保您同意解决冲突时将发生默认操作 `ghe-migrator`。
-redirect_from:
- - /enterprise/admin/migrations/reviewing-migration-conflicts
-versions:
- enterprise-server: '*'
----
-
-1. 使用文本编辑器或[与 CSV 兼容的电子表格软件](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support)打开 *conflicts.csv*。
-2. 按照示例中的指导和下面的参考表检查 *conflicts.csv* 文件,确保导入时将发生正确的操作。
-
-*conflicts.csv* 文件包含冲突的*迁移映射*和建议操作。 迁移映射列出了数据的迁移来源和数据应用到目标的方式。
-
-| `model_name` | `source_url` | `target_url` | `recommended_action` |
-| ------------ | ------------------------------------------------------ | ------------------------------------------------------ | -------------------- |
-| `用户` | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map` |
-| `组织` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `map` |
-| `仓库` | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename` |
-| `团队` | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `合并` |
-
-*conflicts.csv* 中的每一行都提供了以下信息:
-
-| 名称 | Description |
-| -------------------- | ----------------------------- |
-| `model_name` | 正在更改的数据的类型。 |
-| `source_url` | 数据的源 URL。 |
-| `target_url` | 数据的预期目标 URL。 |
-| `recommended_action` | 导入数据时,将发生首选操作 `ghe-migrator`。 |
-
-### 每个记录类型的可能映射
-
-转移数据时,`ghe-migrator` 可以进行多种不同的映射操作:
-
-| `action` | 描述 | 适用的模型 |
-| --------------- | ----------------------------- | -------- |
-| `import` | (默认)源中的数据将导入目标。 | 所有记录类型 |
-| `map` | 源中的数据将被目标上的现有数据替换。 | 用户、组织和仓库 |
-| `rename` | 源中的数据将重命名,然后复制到目标。 | 用户、组织和仓库 |
-| `map_or_rename` | 如果存在目标,请映射到该目标。 否则,请重命名导入的模型。 | 用户 |
-| `合并` | 源中的数据将与目标中的现有数据合并。 | 团队 |
-
-**我们强烈建议您检查 *conflicts.csv* 文件并使用 [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data),以便确保进行正确的操作。**如果一切正常,您可以继续“[在 {% data variables.product.prodname_ghe_server %} 上应用导入的数据](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)”。
diff --git a/translations/zh-CN/content/admin/migrations/reviewing-migration-data.md b/translations/zh-CN/content/admin/migrations/reviewing-migration-data.md
deleted file mode 100644
index 324e1c7b188d..000000000000
--- a/translations/zh-CN/content/admin/migrations/reviewing-migration-data.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: 检查迁移数据
-intro: 在迁移的每一步后,您都可以检查迁移数据的状态。 您将能够确保记录正确映射或重命名,在导入步骤后为记录获取新的 url,以及列出迁移失败的任何记录。
-redirect_from:
- - '/enterprise/{{ currentVersion }}/admin/guides/migrations/reviewing-the-imported-data/'
- - /enterprise/admin/migrations/reviewing-migration-data
-versions:
- enterprise-server: '*'
----
-
-默认情况下,`ghe-migrator audit` 将返回每一条记录。 它还可以让您按以下方式筛选记录:
-
- * 记录的类型。
- * 记录的状态。
-
-记录类型与[迁移的数据](/enterprise/admin/guides/migrations/about-migrations/#migrated-data)中的类型匹配。
-
-### 记录类型筛选器
-
-| 记录类型 | 筛选器名称 |
-| -------------- | ----------------------------- |
-| 用户 | `用户` |
-| 组织 | `组织` |
-| 仓库 | `仓库` |
-| 团队 | `团队` |
-| 里程碑 | `里程碑` |
-| 项目板 | `project` |
-| 议题 | `议题` |
-| 问题评论 | `issue_comment` |
-| 拉取请求 | `pull_request` |
-| 拉取请求审查 | `pull_request_review` |
-| 提交注释 | `commit_comment` |
-| 拉取请求审查评论 | `pull_request_review_comment` |
-| 版本发布 | `发行版` |
-| 在拉取请求或问题上进行的操作 | `issue_event` |
-| 受保护分支 | `protected_branch` |
-
-### 记录状态筛选器
-
-| 记录状态 | Description |
-| --------------- | ----------- |
-| `export` | 将导出记录。 |
-| `import` | 将导入记录。 |
-| `map` | 将映射记录。 |
-| `rename` | 将重命名记录。 |
-| `合并` | 将合并记录。 |
-| `exported` | 已成功导出记录。 |
-| `imported` | 已成功导入记录。 |
-| `mapped` | 已成功映射记录。 |
-| `renamed` | 已成功重命名记录。 |
-| `merged` | 已成功合并记录。 |
-| `failed_export` | 记录导出失败。 |
-| `failed_import` | 记录导入失败。 |
-| `failed_map` | 记录映射失败。 |
-| `failed_rename` | 记录重命名失败。 |
-| `failed_merge` | 记录合并失败。 |
-
-### 筛选审核的记录
-
-借助 `ghe-migrator audit` 命令,您可以使用 `-m` 标志基于记录类型进行筛选。 类似地,您可以使用 `-s` 标志基于导入状态进行筛选。 命令如下所示:
-
-```shell
-$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION_GUID
-```
-
-例如,要查看每个成功导入的组织和团队,您可以输入:
-```shell
-$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION_GUID
-> model_name,source_url,target_url,state
-> organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed
-```
-
-**我们强烈建议您检查失败的每个导入。**要进行检查,您可以输入:
-```shell
-$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION_GUID
-> model_name,source_url,target_url,state
-> user,https://gh.source/octocat,https://gh.target/octocat,failed
-> repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed
-```
-
-如果您对失败的导入有任何疑问,请联系 {% data variables.contact.contact_ent_support %}。
diff --git a/translations/zh-CN/content/admin/user-management/about-global-webhooks.md b/translations/zh-CN/content/admin/user-management/about-global-webhooks.md
deleted file mode 100644
index 3c5a4484c156..000000000000
--- a/translations/zh-CN/content/admin/user-management/about-global-webhooks.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: 关于全局 web 挂钩
-intro: 全局 web 挂钩会通知您实例级别的事件。
-redirect_from:
- - /enterprise/admin/user-management/about-global-webhooks
-versions:
- enterprise-server: '*'
----
-
-您可以使用全局 web 挂钩自动监视、响应或者为实例上的用户和组织管理强制执行规则。 例如,您可以将 web 挂钩配置为在以下情况下执行:
-- 创建或删除用户帐户
-- 创建或删除组织
-- 向仓库添加协作者或从仓库中移除协作者
-- 分叉仓库
-
-![全局 web 挂钩列表](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
-
-有关配置 web 挂钩的更多信息,请参阅“[管理全局 web 挂钩](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-global-webhooks)”。
-
-{% data reusables.enterprise_user_management.manage-global-webhooks-api %}
diff --git a/translations/zh-CN/content/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories.md b/translations/zh-CN/content/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories.md
deleted file mode 100644
index 96cd72033b9e..000000000000
--- a/translations/zh-CN/content/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: 允许管理员启用对公共仓库的匿名 Git 读取权限
-intro: '为了简化自定义工具在您的实例上的使用和绕过身份验证要求,您可以允许仓库管理员启用对 {% data variables.product.product_location_enterprise %} 上公共仓库的匿名 Git 读取权限。'
-redirect_from:
- - /enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
-
-如果已启用私有模式,您可以允许仓库管理员启用对 {% data variables.product.product_location_enterprise %} 上公共仓库的匿名 Git 读取权限。 有关私有模式的更多信息,请参阅“[启用私有模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-private-mode/)”。
-
-允许匿名 Git 读取权限使您能够在实例上为自定义工具绕过身份验证。 当您或仓库管理员为仓库启用此权限设置时,未经过身份验证的 Git 操作(和具有 {% data variables.product.prodname_ghe_server %} 的网络访问权限的任何人)将获得仓库的读取权限(无需身份验证)。
-
-您还可以阻止仓库管理员更改 {% data variables.product.product_location_enterprise %} 上所有仓库或特定仓库的匿名 Git 访问设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。
-
-{% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
-
-{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-4. 在“Anonymous Git read access”下,使用下列菜单并单击 **Enabled**。 ![匿名 Git 读取权限下拉菜单显示菜单选项"Enabled(已启用)"和"Disabled(已禁用)"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
-3. 或者,如果要阻止仓库管理员为实例上的所有仓库更改匿名 Git 读取权限设置,请选择 **Prevent repository admins from changing anonymous Git read access**。 ![选中复选框可阻止仓库管理员更改实例上所有仓库的匿名 Git 读取权限设置。](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
-
-### 为特定仓库启用匿名 Git 读取权限
-
-{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-6. 在“Danger Zone”下的“Enable Anonymous Git read access”旁,请单击 **Enable**。 ![仓库站点管理员设置的危险区域中“Enable anonymous Git read access”下的“Enabled”按钮 ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
-7. 审查更改。 要确认,请单击 **Yes, enable anonymous Git read access(是,启用匿名 Git 读取权限)**。 ![在弹出窗口中确认匿名 Git 读取权限设置](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
-8. 或者,如果要阻止仓库管理员为此仓库更改设置,请选择 **Prevent repository admins from changing anonymous Git read access**。 ![选中复选框可阻止仓库管理员更改此仓库的匿名 Git 读取权限。](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
diff --git a/translations/zh-CN/content/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/zh-CN/content/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
deleted file mode 100644
index 48d67cb2f187..000000000000
--- a/translations/zh-CN/content/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: 允许对身份提供程序覆盖范围以外的用户进行内置身份验证
-intro: 您可以配置内置身份验证,为无法访问使用 LDAP、SAML 或 CAS 的身份提供程序的用户验证身份。
-redirect_from:
- - /enterprise/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider
-versions:
- enterprise-server: '*'
----
-
-### 关于对您的身份提供程序覆盖范围外的用户进行内置身份验证
-
-在无法将特定帐户(例如,合同工或计算机用户的帐户)添加到身份提供程序 (IdP) 时,您可以为外部用户使用内置身份验证。 如果无法使用身份提供程序,您还可以使用内置身份验证来访问回退帐户。
-
-内置身份验证配置完成且用户使用 SAML 或 CAS 成功地进行身份验证后,他们将无法使用用户名和密码进行身份验证。 如果用户使用 LDAP 成功地完成身份验证,凭据将不再被视为内部凭据。
-
-在默认情况下,特定 IdP 的内置身份验证处于禁用状态。
-
-{% warning %}
-
-**警告**:如果您禁用内置身份验证,则必须单独挂起不应具有实例访问权限的任何用户。 更多信息请参阅“[挂起和取消挂起用户](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)”。
-
-{% endwarning %}
-
-### 为您的身份提供程序覆盖范围外的用户配置内置身份验证
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-4. 选择身份提供程序。![选择身份提供程序选项](/assets/images/enterprise/management-console/identity-provider-select.gif)
-5. 选择 **Allow creation of accounts with built-in authentication**。 ![选择内置身份验证选项](/assets/images/enterprise/management-console/built-in-auth-identity-provider-select.png)
-6. 阅读警告,然后单击 **Ok**。
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.2fa_is_available %}
-
-### 邀请您的身份提供程序覆盖范围外的用户在您的实例上进行身份验证
-
-在用户接受邀请后,他们可以使用用户名和密码登录,无需通过 IdP。
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %}
-{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %}
-
-### 延伸阅读
-
-- "[使用 LDAP](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap)"
-- "[使用 SAML](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-saml)"
-- "[使用 CAS](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-cas)"
diff --git a/translations/zh-CN/content/admin/user-management/archiving-and-unarchiving-repositories.md b/translations/zh-CN/content/admin/user-management/archiving-and-unarchiving-repositories.md
deleted file mode 100644
index c042c68c0f44..000000000000
--- a/translations/zh-CN/content/admin/user-management/archiving-and-unarchiving-repositories.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: 存档和取消存档仓库
-intro: 作为站点管理员,您可以在站点管理员仪表板中存档或取消存档仓库。
-redirect_from:
- - /enterprise/admin/articles/archiving-and-unarchiving-repositories/
- - /enterprise/admin/user-management/archiving-and-unarchiving-repositories
-versions:
- enterprise-server: '*'
----
-
-### 存档仓库
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. 在 Danger Zone 下,单击 **Archive**。 ![Archive 按钮](/assets/images/enterprise/site-admin-settings/repo-archive.png)
-6. 单击 **Archive repository** ![Archive repository 按钮](/assets/images/enterprise/site-admin-settings/repo-archive-confirm.png)
-
-### 取消存档仓库
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. 在 Danger Zone 下,单击 **Unarchive**。 ![Archive 按钮](/assets/images/enterprise/site-admin-settings/repo-unarchive.png)
-6. 单击 **Unarchive repository** ![Archive repository 按钮](/assets/images/enterprise/site-admin-settings/repo-unarchive-confirm.png)
-
-### 延伸阅读
-- "[关于存档仓库](/enterprise/{{ currentVersion }}/user/articles/about-archiving-repositories)"
diff --git a/translations/zh-CN/content/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance.md b/translations/zh-CN/content/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance.md
deleted file mode 100644
index 581f6d185cfa..000000000000
--- a/translations/zh-CN/content/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: 为您的 GitHub Enterprise Server 实例验证用户身份
-intro: '您可以使用 {% data variables.product.prodname_ghe_server %} 的内置身份验证,或者在 CAS、LDAP 或 SAML 中选择来集成您的现有帐户并集中管理 {% data variables.product.product_location_enterprise %} 的用户访问权限。'
-redirect_from:
- - /enterprise/admin/categories/authentication/
- - /enterprise/admin/guides/installation/user-authentication/
- - /enterprise/admin/articles/inviting-users/
- - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance/
- - /enterprise/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/user-management/basic-account-settings.md b/translations/zh-CN/content/admin/user-management/basic-account-settings.md
deleted file mode 100644
index 435edd5d8b44..000000000000
--- a/translations/zh-CN/content/admin/user-management/basic-account-settings.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 基本帐户设置
-intro: '在用户能够在 {% data variables.product.product_location_enterprise %} 上进行身份验证后,他们会想要设置几项基本的自定义个人资料,例如头像和电子邮件通知。'
-redirect_from:
- - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/
- - /enterprise/admin/user-management/basic-account-settings
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/user-management/changing-authentication-methods.md b/translations/zh-CN/content/admin/user-management/changing-authentication-methods.md
deleted file mode 100644
index 205fcf4a63b9..000000000000
--- a/translations/zh-CN/content/admin/user-management/changing-authentication-methods.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: 更改身份验证方法
-intro: '您可以随时更改 {% data variables.product.prodname_ghe_server %} 对您现有的帐户进行身份验证的方法。'
-redirect_from:
- - /enterprise/admin/user-management/changing-authentication-methods
-versions:
- enterprise-server: '*'
----
-
-在您更改身份验证方法时,{% data variables.product.product_location_enterprise %} 上的用户帐户将保留,只要他们的用户名没有发生变化,用户就可以继续登录原来的帐户。
-
-如果新的身份验证方法更改了用户名,将创建新帐户。 As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user).
-
-您应当考虑的其他问题包括:
-
-* **密码**:如果您为实例改为使用内置身份验证方法,则在更改完成后,用户必须[设置密码](/enterprise/user/articles/how-can-i-reset-my-password/)。
-
-* **站点管理员**:管理权限[在您使用 SAML 时由您的身份提供程序控制](/enterprise/admin/guides/user-management/using-saml/#saml-attributes),而[在您使用 LDAP 时则通过组成员关系进行控制](/enterprise/admin/guides/user-management/using-ldap/#configuring-ldap-with-your-github-enterprise-server-instance)。
-
-* **团队成员关系**:只有 LDAP 可以让您从目录服务器[控制团队成员关系](/enterprise/admin/guides/user-management/using-ldap/#configuring-ldap-with-your-github-enterprise-server-instance)。
-
-* **用户挂起**:当您使用 LDAP 进行身份验证时,可以通过_受限制的组_控制 {% data variables.product.prodname_ghe_server %} 的访问权限。 在切换到 LDAP 后,如果配置受限制的组,那么不属于其中任何一个组的现有用户将被挂起。 在用户登录或下一次 LDAP 同步期间将发生挂起。
-
-* **组成员关系**:当您使用 LDAP 进行身份验证时,系统将根据受限制组的成员关系和 Active Directory 中的帐户状态自动[挂起和取消挂起](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)用户。
-
-* **Git 身份验证**:SAML 和 CAS 仅支持使用[个人访问令牌](/articles/creating-an-access-token-for-command-line-use)通过 HTTP 或 HTTPS 进行的 Git 身份验证。 不支持通过 HTTP 或 HTTPS 进行的密码身份验证。 LDAP 默认支持基于密码的 Git 身份验证,不过,我们建议您[禁用这种方法](/enterprise/admin/guides/user-management/using-ldap/#disabling-password-authentication-for-git-operations),并强制通过个人访问令牌或 SSH 密钥进行身份验证。
-
-* **API 身份验证**:SAML 和 CAS 仅支持使用[个人访问令牌](/articles/creating-an-access-token-for-command-line-use)进行的 API 身份验证。 不支持基本身份验证。
-
-* **双重身份验证**:{% data reusables.enterprise_user_management.external_auth_disables_2fa %}
-
-* **对您的身份提供程序覆盖范围外的用户进行内置身份验证**:您可以邀请用户在 {% data variables.product.product_location_enterprise %} 中进行身份验证,无需将他们添加到您的身份提供程序中。 更多信息请参阅“[允许对身份提供程序覆盖范围以外的用户进行内置身份验证](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider)”。
diff --git a/translations/zh-CN/content/admin/user-management/disabling-unauthenticated-sign-ups.md b/translations/zh-CN/content/admin/user-management/disabling-unauthenticated-sign-ups.md
deleted file mode 100644
index a486e345a877..000000000000
--- a/translations/zh-CN/content/admin/user-management/disabling-unauthenticated-sign-ups.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: 禁用未经身份验证的注册
-redirect_from:
- - /enterprise/admin/articles/disabling-sign-ups/
- - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups
-intro: 如果您使用的是内置身份验证,可以阻止未经身份验证的人创建帐户。
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.privacy %}
-3. 取消选中 **Enable sign-up**。 ![启用注册复选框](/assets/images/enterprise/management-console/enable-sign-up.png)
-{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/user-management/organizations-and-teams.md b/translations/zh-CN/content/admin/user-management/organizations-and-teams.md
deleted file mode 100644
index df76c023b9cf..000000000000
--- a/translations/zh-CN/content/admin/user-management/organizations-and-teams.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 组织和团队
-redirect_from:
- - /enterprise/admin/articles/adding-users-and-teams/
- - /enterprise/admin/categories/admin-bootcamp/
- - /enterprise/admin/user-management/organizations-and-teams
-intro: 组织适合在您的公司内创建不同的用户组,例如部门或参与相似项目的组。 属于某个组织的公共仓库也可供其他组织的用户使用,但私有仓库仅供该组织的成员使用。
-mapTopic: true
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/user-management/preventing-users-from-changing-a-repositorys-visibility.md b/translations/zh-CN/content/admin/user-management/preventing-users-from-changing-a-repositorys-visibility.md
deleted file mode 100644
index 88a1b276c54e..000000000000
--- a/translations/zh-CN/content/admin/user-management/preventing-users-from-changing-a-repositorys-visibility.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: 阻止用户更改仓库可见性
-intro: '您可以阻止成员在 {% data variables.product.prodname_ghe_server %} 设备上更改组织拥有的仓库的可见性。'
-redirect_from:
- - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility
- - /enterprise/admin/user-management/preventing-users-from-changing-a-repositorys-visibility
-versions:
- enterprise-server: '*'
----
-
-当您阻止成员更改仓库可见性时,只有站点管理员可以将公共仓库设置为私有或者将私有仓库设置为公共。
-
-如果站点管理员仅允许组织所有者创建仓库,成员将无法更改仓库可见性。 如果站点管理员只允许成员创建私有仓库,则成员只能将仓库从公共更改为私有。 更多信息请参阅“[限制在实例中创建仓库](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)”。
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.policies-tab %}
-{% data reusables.enterprise-accounts.repositories-tab %}
-5. 在“Repository visibility change”下,检查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-
-{% data reusables.enterprise-accounts.repository-visibility-policy %}
diff --git a/translations/zh-CN/content/admin/user-management/preventing-users-from-changing-anonymous-git-read-access.md b/translations/zh-CN/content/admin/user-management/preventing-users-from-changing-anonymous-git-read-access.md
deleted file mode 100644
index 2fc3766624a8..000000000000
--- a/translations/zh-CN/content/admin/user-management/preventing-users-from-changing-anonymous-git-read-access.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: 阻止用户更改匿名 Git 读取权限
-intro: '您可以阻止仓库管理员更改一个仓库{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.14" %}或所有仓库{% endif %}的匿名 Git 读取权限。'
-redirect_from:
- - /enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access-to-a-repository/
- - /enterprise/admin/user-management/preventing-users-from-changing-anonymous-git-read-access
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
-
-要阻止仓库管理员为特定仓库更改匿名 Git 读取权限设置,您可以锁定仓库的权限设置。 在您锁定仓库的 Git 读取权限设置后,只有站点管理员可以更改设置。
-
-仓库管理员可为公共仓库(如果不是分叉)更改匿名 Git 读取权限。 更多信息请参阅“[允许管理员启用对公共仓库的匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)”。
-
-{% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
-
-### 阻止用户更改仓库的匿名 Git 读取权限
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.repository-search %}
-{% data reusables.enterprise_site_admin_settings.click-repo %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-6. 在“Danger Zone”下,选择 **Prevent repository admins from enabling anonymous Git read access**。 ![选中复选框,锁定仓库以阻止更改其匿名 Git 读取权限设置](/assets/images/enterprise/site-admin-settings/lock-repo-from-changing-anonymous-git-read-access.png)
-
-### 阻止用户为所有仓库更改匿名 Git 读取权限
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.options-tab %}
-3. 在“Anonymous Git read access”下,确认已启用此设置,然后选择 **Prevent repository admins from changing anonymous Git read access**。 ![选中复选框,全局锁定仓库以阻止更改其匿名 Git 读取权限设置](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
-
diff --git a/translations/zh-CN/content/admin/user-management/preventing-users-from-deleting-organization-repositories.md b/translations/zh-CN/content/admin/user-management/preventing-users-from-deleting-organization-repositories.md
deleted file mode 100644
index a31e6058dcf2..000000000000
--- a/translations/zh-CN/content/admin/user-management/preventing-users-from-deleting-organization-repositories.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: 阻止用户删除组织仓库
-intro: '您可以阻止成员在您的 {% data variables.product.prodname_ghe_server %} 设备上删除或转让组织中的仓库。'
-redirect_from:
- - /enterprise/admin/user-management/preventing-users-from-deleting-organization-repositories
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.policies-tab %}
-{% data reusables.enterprise-accounts.repositories-tab %}
-5. 在“Repository deletion and transfer”下,检查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-
-{% data reusables.enterprise-accounts.repository-deletion-policy %}
diff --git a/translations/zh-CN/content/admin/user-management/repositories.md b/translations/zh-CN/content/admin/user-management/repositories.md
deleted file mode 100644
index 25befb7520b4..000000000000
--- a/translations/zh-CN/content/admin/user-management/repositories.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 仓库
-intro: '您可以管理您的 {% data variables.product.prodname_ghe_server %} 设备上可供仓库管理员使用的设置。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/user-management/repositories
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/user-management/restricting-repository-creation-in-your-instance.md b/translations/zh-CN/content/admin/user-management/restricting-repository-creation-in-your-instance.md
deleted file mode 100644
index 1f082480ce0f..000000000000
--- a/translations/zh-CN/content/admin/user-management/restricting-repository-creation-in-your-instance.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: 限制在实例中创建仓库
-intro: '您可以选择 {% data variables.product.prodname_ghe_server %} 设备上的组织成员是否可以创建仓库,以及这些成员可以创建哪种仓库。'
-redirect_from:
- - /enterprise/admin/user-management/restricting-repository-creation-in-your-instance
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.organizations.repo-creation-constants %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.business %}
-{% data reusables.enterprise-accounts.policies-tab %}
-{% data reusables.enterprise-accounts.repositories-tab %}
-5. 在“Repository creation”下,检查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-{% if currentVersion ver_gt "enterprise-server@2.19" %}
-{% data reusables.enterprise-accounts.repo-creation-policy %}
-{% data reusables.enterprise-accounts.repo-creation-types %}
-{% else %}
-6. 在“Repository creation(仓库创建)”下,使用下拉菜单并选择策略。 ![包含仓库创建策略的下拉菜单](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
-{% endif %}
diff --git a/translations/zh-CN/content/admin/user-management/user-security.md b/translations/zh-CN/content/admin/user-management/user-security.md
deleted file mode 100644
index 8ef103423c71..000000000000
--- a/translations/zh-CN/content/admin/user-management/user-security.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 用户安全
-intro: '确保您的 {% data variables.product.prodname_ghe_server %} 用户安全。 您可以审核他们的安全设置或在实例内强制执行最佳实践。'
-mapTopic: true
-redirect_from:
- - /enterprise/admin/user-management/user-security
-versions:
- enterprise-server: '*'
----
-
diff --git a/translations/zh-CN/content/admin/user-management/using-built-in-authentication.md b/translations/zh-CN/content/admin/user-management/using-built-in-authentication.md
deleted file mode 100644
index 3a665801bfba..000000000000
--- a/translations/zh-CN/content/admin/user-management/using-built-in-authentication.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: 使用内置身份验证
-intro: '当您使用默认身份验证方法时,所有身份验证详细信息都将存储在 {% data variables.product.product_location_enterprise %} 中。 如果您尚未建立身份验证提供程序(例如 LDAP、SAML 或 CAS),内置身份验证将是默认方法。'
-redirect_from:
- - /enterprise/admin/user-management/using-built-in-authentication
-versions:
- enterprise-server: '*'
----
-
-您可以创建用户将在登录和注销页面上看到的自定义消息。 更多信息请参阅“[自定义您的实例上的用户消息](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)”。
-
-### 配置内置身份验证
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-4. 选择 **Built in authentication**。 ![选择内置身份验证选项](/assets/images/enterprise/management-console/built-in-auth-select.png)
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.2fa_is_available %}
-
-### 创建帐户并添加用户
-
-在实例创建完成后,您需要创建自己的管理员帐户并使用它配置用户。
-
-1. 在 `http(s)://[hostname]/join` 的“Create Admin Account”页面下,选择您的用户名、密码和电子邮件地址,然后单击 **Create an account**。 ![创建管理员帐户](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png)
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %}
-{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %}
diff --git a/translations/zh-CN/content/admin/user-management/using-cas.md b/translations/zh-CN/content/admin/user-management/using-cas.md
deleted file mode 100644
index 6abea360a3bd..000000000000
--- a/translations/zh-CN/content/admin/user-management/using-cas.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: 使用 CAS
-redirect_from:
- - /enterprise/admin/articles/configuring-cas-authentication/
- - /enterprise/admin/articles/about-cas-authentication/
- - /enterprise/admin/user-management/using-cas
-intro: 'CAS 是一种适用于多种网络应用程序的单点登录 (SSO) 协议。 在登录之前,CAS 用户帐户不会占用{% if currentVersion ver_gt "enterprise-server@2.16" %}用户许可{% else %}席位{% endif %}。'
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.built-in-authentication %}
-
-### 使用 CAS 时的用户名考量因素
-
-{% data reusables.enterprise_management_console.username_normalization %}
-
-{% data reusables.enterprise_management_console.username_normalization_sample %}
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.external_auth_disables_2fa %}
-
-### CAS 属性
-
-以下属性可用。
-
-| 属性名称 | 类型 | 描述 |
-| ----- | -- | ------------------------------------------------------------ |
-| `用户名` | 必选 | {% data variables.product.prodname_ghe_server %} 用户名。 |
-
-### 配置 CAS
-{% warning %}
-
-**警告**:请注意,在 {% data variables.product.product_location_enterprise %} 上配置 CAS 之前,用户将无法使用他们的 CAS 用户名和密码通过 HTTP/HTTPS 对 API 请求或 Git 操作进行身份验证。 相反,他们将需要[创建访问令牌](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use)。
-
-{% endwarning %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-3. 选择 **CAS**。 ![选择 CAS](/assets/images/enterprise/management-console/cas-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![选中 CAS 内置身份验证复选框](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
-5. 在 **Server URL** 字段中,输入您的 CAS 服务器的完整 URL。 如果您的 CAS 服务器使用无法由 {% data variables.product.prodname_ghe_server %} 验证的证书,您可以使用 `ghe-ssl-ca-certificate-install` 命令将其作为可信证书安装。
diff --git a/translations/zh-CN/content/admin/user-management/using-ldap.md b/translations/zh-CN/content/admin/user-management/using-ldap.md
deleted file mode 100644
index 36632dc1fcff..000000000000
--- a/translations/zh-CN/content/admin/user-management/using-ldap.md
+++ /dev/null
@@ -1,190 +0,0 @@
----
-title: 使用 LDAP
-redirect_from:
- - /enterprise/admin/articles/configuring-ldap-authentication/
- - /enterprise/admin/articles/about-ldap-authentication/
- - /enterprise/admin/articles/viewing-ldap-users/
- - /enterprise/admin/hidden/enabling-ldap-sync/
- - /enterprise/admin/hidden/ldap-sync/
- - /enterprise/admin/user-management/using-ldap
-intro: '使用 LDAP,您可以向 {% data variables.product.prodname_ghe_server %} 验证现有帐户的身份和集中管理仓库权限。 LDAP 是一种用于访问和维护目录信息服务的流行应用程序协议,是将第三方软件与大型公司用户目录相集成时使用的最常见协议之一。'
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.built-in-authentication %}
-
-### 支持的 LDAP 服务
-
-{% data variables.product.prodname_ghe_server %} 可与下列 LDAP 服务集成:
-
-* Active Directory
-* FreeIPA
-* Oracle Directory Server Enterprise Edition
-* OpenLDAP
-* Open Directory
-* 389-ds
-
-### 使用 LDAP 时的用户名考量因素
-
-{% data reusables.enterprise_management_console.username_normalization %}
-
-{% data reusables.enterprise_management_console.username_normalization_sample %}
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.2fa_is_available %}
-
-### 在 {% data variables.product.product_location_enterprise %} 上配置 LDAP
-
-在您配置 LDAP 后,用户将能够使用他们的 LDAP 凭据登录您的实例。 在用户首次登录时,他们个人资料中的姓名、电子邮件地址和 SSH 密钥将使用您的目录中的 LDAP 属性进行设置。
-
-当您通过 {% data variables.enterprise.management_console %} 为用户配置 LDAP 访问权限时,在用户首次登录您的实例前,用户许可不可用。 但是,如果您使用站点管理员设置手动创建帐户,用户许可将立即可用。
-
-{% warning %}
-
-**警告**:在 {% data variables.product.product_location_enterprise %} 上配置 LDAP 之前,请确保您的 LDAP 服务支持分页结果。
-
-{% endwarning %}
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-3. 在“Authentication”下,选择 **LDAP**。 ![选择 LDAP](/assets/images/enterprise/management-console/ldap-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![选中 LDAP 内置身份验证复选框](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
-5. 添加您的配置设置。
-
-### LDAP 属性
-使用以下属性完成 {% data variables.product.product_location_enterprise %} 的 LDAP 配置。
-
-| 属性名称 | 类型 | 描述 |
-| ------------------------------------------------ | -- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Host` | 必选 | LDAP 主机,例如 `ldap.example.com` 或 `10.0.0.30`。 如果主机名只能在您的内部网络中使用,您需要先配置 {% data variables.product.product_location_enterprise %} 的 DNS,以便它可以使用您的内部域名服务器解析主机名。 |
-| `端口` | 必选 | 主机的 LDAP 服务侦听的端口。 示例包括:389 和 636(适用于 LDAPS)。 |
-| `Encryption` | 必选 | 用于确保与 LDAP 服务器之间的通信安全的加密方法。 示例包括明文(无加密)、SSL/LDAPS(从一开始就加密)和 StartTLS(在连接后升级为加密通信)。 |
-| `Domain search user` | 可选 | 执行用户查询,在其他用户登录时对其进行身份验证的 LDAP 用户。 这一般是一个专为第三方集成创建的服务帐户。 使用完全限定名称,例如 `cn=Administrator,cn=Users,dc=Example,dc=com`。 对于 Active Directory,您还可为域搜索用户使用 `[DOMAIN]\[USERNAME]` 语法(例如 `WINDOWS\Administrator`)。 |
-| `Domain search password` | 可选 | 域搜索用户的密码。 |
-| `Administrators group` | 可选 | 登录您的设备后,此组中的用户将被升级为站点管理员。 如果您不配置 LDAP 管理员组,则登录您的设备的第一个 LDAP 用户帐户将被自动升级为站点管理员。 |
-| `Domain base` | 必选 | 您想要搜索用户和组的 LDAP 子树的完全限定 `Distinguished Name` (DN)。 您可以添加任意数量的组;不过,每个组和它所包含的用户都必须在相同的基础域中定义。 如果您指定受限的用户组,那么只有属于这些组的用户将在作用域内。 我们建议您将 LDAP 目录树的顶级指定为您的基础域,并使用受限的用户组来控制权限。 |
-| `Restricted user groups` | 可选 | 如果指定,将仅允许这些组中的用户登录。 您只需要指定组的常用名 (CN),您可以添加任意数量的组。 如果未指定组,则指定基础域作用域中的*所有*用户都将可以登录您的 {% data variables.product.prodname_ghe_server %} 实例。 |
-| `User ID` | 必选 | 标识尝试身份验证的 LDAP 用户的 LDAP 属性。 建立映射后,用户可以更改他们的 {% data variables.product.prodname_ghe_server %} 用户名。 对于大多数 Active Directory 安装来说,此字段应为 `sAMAccountName`,但对其他 LDAP 解决方案(例如 OpenLDAP)来说,可能是 `uid`。 默认值为 `uid`。 |
-| `Profile name` | 可选 | 将在用户的 {% data variables.product.prodname_ghe_server %} 个人资料页面上显示的姓名。 除非启用 LDAP 同步,否则用户可以更改他们的个人资料姓名。 |
-| `Emails` | 可选 | 用户的 {% data variables.product.prodname_ghe_server %} 帐户的电子邮件地址。 |
-| `SSH keys` | 可选 | 连接到用户的 {% data variables.product.prodname_ghe_server %} 帐户的 SSH 公钥。 密钥必须采用 OpenSSH 格式。 |
-| `GPG keys` | 可选 | 连接到用户的 {% data variables.product.prodname_ghe_server %} 帐户的 GPG 密钥。 |
-| `Disable LDAP authentication for Git operations` | 可选 | 如果选择,将[禁止](#disabling-password-authentication-for-git-operations)用户使用 LDAP 密码对 Git 操作进行身份验证。 |
-| `Enable LDAP certificate verification` | 可选 | 如果选择,将[启用](#enabling-ldap-certificate-verification) LDAP 证书验证。 |
-| `Synchronization` | 可选 | 如果选择,将[启用](#enabling-ldap-sync) LDAP 同步。 |
-
-#### 为 Git 操作禁用密码身份验证
-
-在您的 LDAP 设置中选择 **Disable username and password authentication for Git operations**,为 Git 权限强制使用个人访问令牌或 SSH 密钥,这样有助于防止您的服务器被 LDAP 身份验证请求过载。 我们建议使用此设置,因为响应慢的 LDAP 服务器是性能问题和故障的常见来源,尤其是在遇到轮询导致的大量请求时。
-
-![为 Git 禁用 LDAP 密码身份验证的复选框](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
-
-选择此选项时,如果用户通过命令行尝试为 Git 操作使用密码,他们将收到一条错误消息,内容为 `Password authentication is not allowed for Git operations. You must use a personal access token.`
-
-#### 启用 LDAP 证书验证
-
-在您的 LDAP 设置中选择 **Enable LDAP certificate verification**,验证您用于 TLS 的 LDAP 服务器证书。
-
-![LDAP 证书验证复选框](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
-
-选择此选项时,将对证书进行验证,以确保:
-- 如果证书至少包含一个使用者可选名称 (SAN),则其中的一个 SAN 将匹配 LDAP 主机名。 否则,常用名 (CN) 将匹配 LDAP 主机名。
-- 证书不会过期。
-- 证书由受信任的证书颁发机构 (CA) 签名。
-
-#### 启用 LDAP 同步
-
-借助 LDAP 同步,您可以将 {% data variables.product.prodname_ghe_server %} 用户和团队成员关系与建立的 LDAP 组同步。 这样,您可以在 LDAP 服务器中为用户建立基于角色的权限控制,而不用在 {% data variables.product.prodname_ghe_server %} 中手动建立。 更多信息请参阅“[创建团队](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)”。
-
-要启用 LDAP 同步,请在您的 LDAP 设置中选择 **Synchronize Emails(同步电子邮件)**、**Synchronize SSH Keys(同步 SSH 密钥)**或 **Synchronize GPG Keys(同步 GPG 密钥)**。
-
-![Synchronization 复选框](/assets/images/enterprise/management-console/ldap-synchronize.png)
-
-启用 LDAP 同步后,某个同步作业将以指定的时间间隔运行,在每个用户帐户上执行以下操作:
-
-- 如果您已允许对您的身份提供程序覆盖范围以外的用户进行内置身份验证,并且该用户使用内置身份验证,请前进到下一个用户。
-- 如果用户没有 LDAP 映射,请尝试将用户映射到目录中的 LDAP 条目。 如果用户无法映射到 LDAP 条目,请挂起该用户并前进到下一个用户。
-- 如果存在 LDAP 映射但目录中相应的 LDAP 条目缺失,请挂起该用户并前进到下一个用户。
-- 如果相应的 LDAP 条目已被标记为禁用并且该用户尚未被挂起,请挂起该用户并前进到下一个用户。
-- 如果相应的 LDAP 条目未被标记为禁用,用户已被挂起,并且已在 Admin Center 中启用 _Reactivate suspended users_,请取消挂起该用户。
-- 如果相应的 LDAP 条目包括 `name` 属性,请更新用户的个人资料姓名。
-- 如果相应的 LDAP 条目位于管理员组中,请将该用户升级为站点管理员。
-- 如果相应的 LDAP 条目不位于管理员组中,请将该用户降级为普通帐户。
-- 如果为电子邮件定义了一个 LDAP 用户字段,请将该用户的电子邮件设置与 LDAP 条目同步。 将第一个 LDAP `mail` 条目设为主电子邮件。
-- 如果为 SSH 公钥定义了一个 LDAP 用户字段,请将该用户的 SSH 公钥与 LDAP 条目同步。
-- 如果为 GPG 密钥定义了一个 LDAP 用户字段,请将该用户的 GPG 密钥与 LDAP 条目同步。
-
-{% note %}
-
-**注**:只有您使用 Active Directory,`userAccountControl` 属性显示并使用 `ACCOUNTDISABLE` 标记时,才可以将 LDAP 条目标记为禁用。
-
-{% endnote %}
-
-某个同步作业也将以指定的时间间隔运行,在已经映射到 LDAP 组的每个团队上执行以下操作:
-
-- 如果已移除团队的相应 LDAP 组,请移除团队中的所有成员。
-- 如果已从 LDAP 组中移除 LDAP 成员条目,请从团队中移除相应的用户。 如果用户因此失去了任何仓库的访问权限,请删除用户在这些仓库中的任何私有分叉。
-- 如果已向 LDAP 组中添加 LDAP 成员条目,请将相应的用户添加到团队中。 如果用户因此重新获得了任何仓库的访问权限,请恢复过去 90 天内因为用户失去访问权限而被删除的仓库中的任何私有分叉。
-
-{% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
-
-{% warning %}
-
-**安全警告:**
-
-启用 LDAP 同步后,站点管理员和组织所有者可以搜索要映射团队的目标组的 LDAP 目录。
-
-这样有可能将敏感的组织信息披露给合同工或其他没有权限的用户,包括:
-
-- 对*域搜索用户*可见的特定 LDAP 组的存在性。
-- 具有 {% data variables.product.prodname_ghe_server %} 用户帐户的 LDAP 组的成员,如果创建与该 LDAP 组同步的团队,此信息将被披露。
-
-如果不需要披露此类信息,您的公司或组织应在管理员控制台中限制配置的*域搜索用户*的权限。 如果无法进行此类限制,请联系 {% data variables.contact.contact_ent_support %}。
-
-{% endwarning %}
-
-#### 支持的 LDAP 组对象类
-
-{% data variables.product.prodname_ghe_server %} 支持下列 LDAP 组对象类。 可以嵌套组。
-
-- `组`
-- `groupOfNames`
-- `groupOfUniqueNames`
-- `posixGroup`
-
-### 查看和创建 LDAP 用户
-
-您可以查看具有您的实例访问权限的 LDAP 用户的完整列表和配置新用户。
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-3. 在左侧边栏中,单击 **LDAP users**。 ![LDAP users 选项卡](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
-4. 要搜索用户,请输入完整或部分用户名,然后单击 **Search**。 现有用户将显示在搜索结果中。 如果用户不存在,请单击 **Create** 以配置新用户帐户。 ![LDAP 搜索](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
-
-### 更新 LDAP 帐户
-
-除非[启用 LDAP 同步](#enabling-ldap-sync),否则 LDAP 帐户的变更将不会自动与 {% data variables.product.prodname_ghe_server %} 同步。
-
-* 要使用新的 LDAP 管理员组,必须在 {% data variables.product.prodname_ghe_server %} 上手动升级和降级用户,以反映 LDAP 中的变更。
-* 要在 LDAP 管理员组中添加或移除 LDAP 帐户,请[在 {% data variables.product.prodname_ghe_server %} 上升级或降级帐户](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator)。
-* 要移除 LDAP 帐户,请[挂起 {% data variables.product.prodname_ghe_server %} 帐户](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)。
-
-#### 手动同步 LDAP 帐户
-
-{% data reusables.enterprise_site_admin_settings.sign-in %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.search-user %}
-{% data reusables.enterprise_site_admin_settings.click-user %}
-{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
-{% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. 在“LDAP”下,单击 **Sync now**,使用您的 LDAP 服务器中的数据手动更新帐户。 ![LDAP Sync now 按钮](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
-
-You can also [use the API to trigger a manual sync](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap).
-
-### 撤销 {% data variables.product.product_location_enterprise %} 的权限
-
-如果[启用 LDAP 同步](#enabling-ldap-sync),移除用户的 LDAP 凭据将在下一次同步操作后挂起他们的帐户。
-
-如果**未**启用 LDAP 同步,您必须在移除 LDAP 凭据后手动挂起 {% data variables.product.prodname_ghe_server %} 帐户。 更多信息请参阅“[挂起和取消挂起用户](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)”。
diff --git a/translations/zh-CN/content/admin/user-management/using-saml.md b/translations/zh-CN/content/admin/user-management/using-saml.md
deleted file mode 100644
index b9e5159c2093..000000000000
--- a/translations/zh-CN/content/admin/user-management/using-saml.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: 使用 SAML
-redirect_from:
- - /enterprise/admin/articles/configuring-saml-authentication/
- - /enterprise/admin/articles/about-saml-authentication/
- - /enterprise/admin/user-management/using-saml
-intro: 'SAML 是一种基于 XML 的身份验证和授权标准。 {% data variables.product.prodname_ghe_server %} 可以作为您的内部 SAML 身份提供程序 (IdP) 的服务提供程序 (SP)。'
-versions:
- enterprise-server: '*'
----
-
-{% data reusables.enterprise_user_management.built-in-authentication %}
-
-### 支持的 SAML 服务
-
-{% data reusables.saml.saml-supported-idps %}
-
-{% data reusables.saml.saml-single-logout-not-supported %}
-
-### 使用 SAML 时的用户名考量因素
-
-每个 {% data variables.product.prodname_ghe_server %} 用户名都由 SAML 响应中的以下断言之一决定,这些断言按优先级从高到低排列的顺序为:
-
-- 自定义用户名属性(如果定义且存在)
-- `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name` 断言(如果存在)
-- `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` 断言(如果存在)
-- `NameID` 元素
-
-即使其他属性存在,也需要 `NameID` 元素。
-
-将在 `NameID` 与 {% data variables.product.prodname_ghe_server %} 用户名之间创建映射,`NameID` 应持久、唯一,并且在用户生命周期内不会发生变化。
-
-{% data reusables.enterprise_management_console.username_normalization %}
-
-{% data reusables.enterprise_management_console.username_normalization_sample %}
-
-{% data reusables.enterprise_user_management.two_factor_auth_header %}
-{% data reusables.enterprise_user_management.external_auth_disables_2fa %}
-
-### SAML 元数据
-
-您的 {% data variables.product.prodname_ghe_server %} 实例的服务提供程序元数据位于 `http(s)://[hostname]/saml/metadata` 下。
-
-要手动配置您的身份提供程序,断言使用者服务 (ACS) URL 为 `http(s)://[hostname]/saml/consume`。 它使用 `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` 绑定。
-
-### SAML 属性
-
-以下属性可用。 您可以在 [Management Console](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/) 中更改属性名称,但 `administrator` 属性除外。
-
-| 默认属性名称 | 类型 | 描述 |
-| --------------- | -- | -------------------------------------------------------------------------------------------------------------------- |
-| `NameID` | 必选 | 持久用户标识符。 可以使用任意持久名称标识符格式。 除非提供备用断言之一,否则将为 {% data variables.product.prodname_ghe_server %} 用户名使用 `NameID` 元素。 |
-| `administrator` | 可选 | 如果值为“true”,用户将被自动升级为管理员。 任何其他值或不存在的值会将用户降级为普通用户帐户。 |
-| `用户名` | 可选 | {% data variables.product.prodname_ghe_server %} 用户名。 |
-| `full_name` | 可选 | 用户的个人资料页面上显示的姓名。 用户可以在配置后更改他们的姓名。 |
-| `emails` | 可选 | 用户的电子邮件地址。 可以指定多个。 |
-| `public_keys` | 可选 | 用户的 SSH 公钥。 可以指定多个。 |
-| `gpg_keys` | 可选 | 用户的 GPG 密钥。 可以指定多个。 |
-
-### 配置 SAML 设置
-
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.authentication %}
-3. 选择 **SAML**。 ![SAML 身份验证](/assets/images/enterprise/management-console/auth-select-saml.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![选中 SAML 内置身份验证复选框](/assets/images/enterprise/management-console/saml-built-in-authentication.png)
-5. 或者,要启用非请求响应 SSO,请选择 **IdP initiated SSO**。 默认情况下,{% data variables.product.prodname_ghe_server %} 将向 IdP 发回 `AuthnRequest`,回复非请求身份提供程序 (IdP) 发起的请求。 ![SAML idP SSO](/assets/images/enterprise/management-console/saml-idp-sso.png)
-
- {% tip %}
-
- **注**:我们建议保留此值处于**未选择**状态。 您**只**应在罕见的情况下启用此功能,即您的 SAML 实现不支持服务提供程序发起的 SSO,并且 {% data variables.contact.enterprise_support %} 建议执行此操作。
-
- {% endtip %}
-
-5. 如果您**不**希望 SAML 提供程序为 {% data variables.product.product_location_enterprise %} 上的用户确定管理员权限,请选择 **Disable administrator demotion/promotion(禁用管理员降级/升级)**。 ![SAML 禁用管理员配置](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png)
-6. 在 **Single sign-on URL** 字段中,为单点登录请求输入您的 IdP 上的 HTTP 或 HTTPS 端点。 此值由您的 IdP 配置提供。 如果主机只能在您的内部网络中使用,您需要先[将 {% data variables.product.product_location_enterprise %} 配置为使用内部域名服务器](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/)。 ![SAML 身份验证](/assets/images/enterprise/management-console/saml-single-sign-url.png)
-7. (可选)在 **Issuer(签发者)** 字段中,输入您的 SAML 签发者的姓名。 这将验证发送到 {% data variables.product.product_location_enterprise %} 的消息的真实性。 ![SAML 颁发者](/assets/images/enterprise/management-console/saml-issuer.png)
-8. 在 **Signature Method(签名方法)** 和 **Digest Method(摘要方法)** 下拉菜单中,选择您的 SAML 颁发者用于验证 {% data variables.product.product_location_enterprise %} 请求完整性的哈希算法。 使用 **Name Identifier Format** 下拉菜单指定格式。 ![SAML 方法](/assets/images/enterprise/management-console/saml-method.png)
-9. 在 **Verification certificate(验证证书)**下,单击 **Choose File(选择文件)**并选择用于验证 IdP 的 SAML 响应的证书。 ![SAML 身份验证](/assets/images/enterprise/management-console/saml-verification-cert.png)
-10. 如果需要,请修改 SAML 属性名称以匹配您的 IdP,或者接受默认名称。![SAML 属性名称](/assets/images/enterprise/management-console/saml-attributes.png)
-
-### 撤销 {% data variables.product.product_location_enterprise %} 的权限
-
-如果您将某个用户从您的身份提供程序中移除,还必须手动挂起他们。 否则,他们仍可以继续使用访问令牌或 SSH 密钥进行身份验证。 更多信息请参阅“[挂起和取消挂起用户](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)”。
-
-### 响应消息的要求
-
-响应消息必须满足以下要求:
-
-- `` 元素必须在根响应文档上提供,而且只有在根响应文档签署后才匹配 ACS URL。 如果断言已签名,此元素将遭到忽略)。
-- `` 元素必须始终作为 `` 元素的一部分提供。 此元素必须匹配 {% data variables.product.prodname_ghe_server %} 实体 ID。 这是 {% data variables.product.prodname_ghe_server %} 实例的 URL,如 `https://ghe.corp.example.com`。
-- 响应中的每一个断言都**必须**由数字签名加以保护。 签署各个 `` 元素或签署 `` 元素可以实现此操作。
-- `` 元素必须作为 `` 元素的一部分提供。 可以使用任意持久名称标识符格式。
-- `Recipient` 属性必须存在并设为 ACS URL。 例如:
-
-```xml
-
-
-
- ...
-
-
-
-
-
-
- monalisa
-
-
-
-
-```
-
-### 错误消息
-
-如果 `Recipient` 与 ACS URL 不匹配,身份验证日志中将显示以下错误消息:
-
-```
-Recipient in the SAML response was not valid.
-```
-
-如果 `Recipient` 不是响应消息的一部分,身份验证日志中将显示以下错误消息:
-
-```
-Recipient in the SAML response must not be blank.
-```
-
-如果 SAML 响应未签名,或者签名与内容不匹配,身份验证日志中将显示以下错误消息:
-
-```
-SAML Response is not signed or has been modified.
-```
-如果 `Audience` 缺失或者与 {% data variables.product.prodname_ghe_server %} 实体 Id 不匹配,身份验证日志中将显示以下错误消息:
-
-```
-Audience is invalid. Audience attribute does not match your_instance_url
-```
diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally.md
deleted file mode 100644
index 60d8490edf13..000000000000
--- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: 本地访问拉取请求
-intro: '您可以在 {% data variables.product.prodname_desktop %} 上打开的拉取请求中查看提议的更改。'
-redirect_from:
- - /desktop/contributing-to-projects/accessing-a-pull-request-locally
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.click-pull-requests %}
- ![Current Branch(当前分支)下拉菜单中的 Pull Requests(拉取请求)选项卡](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png)
-{% data reusables.desktop.choose-pr-from-list %}
- ![仓库中打开的拉取请求列表](/assets/images/help/desktop/click-pull-request.png)
-4. (可选)要刷新拉取请求列表,请单击 {% octicon "sync" aria-label="The sync icon" %}。 ![用于刷新的同步按钮](/assets/images/help/desktop/pull-request-list-sync.png)
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/accessing-a-pull-request-locally.md b/translations/zh-CN/content/desktop/contributing-to-projects/accessing-a-pull-request-locally.md
deleted file mode 100644
index 469b1c39e3d0..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/accessing-a-pull-request-locally.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: 本地访问拉取请求
-intro: '您可以在 {% data variables.product.prodname_desktop %} 上打开的拉取请求中查看提议的更改。'
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.click-pull-requests %}
- ![Current Branch(当前分支)下拉菜单中的 Pull Requests(拉取请求)选项卡](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png)
-{% data reusables.desktop.choose-pr-from-list %}
- ![仓库中打开的拉取请求列表](/assets/images/help/desktop/click-pull-request.png)
-4. (可选)要刷新拉取请求列表,请单击 {% octicon "sync" aria-label="The sync icon" %}。 ![用于刷新的同步按钮](/assets/images/help/desktop/pull-request-list-sync.png)
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop.md b/translations/zh-CN/content/desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop.md
deleted file mode 100644
index b0d23275546f..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: 将仓库从本地计算机添加到 GitHub Desktop
-intro: '您可以将任何 Git 仓库添加到 {% data variables.product.prodname_desktop %} 中,即使不是 {% data variables.product.prodname_dotcom %} 仓库也可以。'
-versions:
- free-pro-team: '*'
----
-
-{% tip %}
-
-**提示:**您可以通过拖放文件夹到 {% data variables.product.prodname_desktop %} 的方式,将 Git 仓库从本地计算机添加到 GitHub Desktop。 如果同时将多个 Git 文件夹拖入 {% data variables.product.prodname_desktop %},则每个文件夹将添加为一个单独的 Git 仓库。
-
-{% endtip %}
-
-{% mac %}
-
-1. 在 **File(文件)**菜单中,单击 **Add Local Repository(添加本地仓库)**。 ![添加本地仓库菜单选项](/assets/images/help/desktop/add-local-repository-mac.png)
-2. 单击 **Choose...(选择...)**,并使用 Finder 窗口找到要添加的本地仓库。 ![Mac 应用程序中的“本地路径”字段](/assets/images/help/desktop/add-repo-choose-button-mac.png)
-4. 单击 **Add Repository(添加仓库)**。 ![Mac 应用程序中的“添加仓库”按钮](/assets/images/help/desktop/add-repository-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. 在 **File(文件)**菜单中,单击 **Add Local Repository(添加本地仓库)**。 ![添加本地仓库菜单选项](/assets/images/help/desktop/add-local-repository-windows.png)
-2. 单击 **Choose...(选择...)**,并使用 Windows 资源管理器找到要添加的本地仓库。 ![Windows 应用程序中的“本地路径”字段](/assets/images/help/desktop/add-repo-choose-button-win.png)
-4. 单击 **Add Repository(添加仓库)**。 ![Windows 应用程序中的“添加仓库”按钮](/assets/images/help/desktop/add-repository-button-windows.png)
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop.md b/translations/zh-CN/content/desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop.md
deleted file mode 100644
index 1075897f2c9d..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: 使用 GitHub Desktop 添加现有项目到 GitHub
-intro: '您可以使用 {% data variables.product.prodname_desktop %} 将现有 Git 仓库添加到 {% data variables.product.prodname_dotcom %}。'
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-{% data reusables.git.remove-git-remote %}
-2. [添加仓库到 GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/).
-{% data reusables.desktop.publish-repository %}
-4. 在 **Name(名称)**字段中键入所需的仓库名称,或者使用默认的当前本地仓库名称。 ![名称字段](/assets/images/help/desktop/publish-repository-name-mac.png)
-5. 要发布公共仓库,请取消选择 **Keep this code private(保留此代码为私有)**。 ![保留此代码为私有复选框](/assets/images/help/desktop/publish-repository-private-checkbox-mac.png)
-6. 从 **Organization(组织)**下拉菜单中选择要发布仓库到其中的组织,或者选择 **None(无)**以将仓库发布到您的个人帐户。 ![组织下拉菜单](/assets/images/help/desktop/publish-repository-org-dropdown-mac.png)
-7. 单击 **Publish Repository(发布仓库)**按钮。 ![“发布仓库”对话框中的“发布仓库”按钮](/assets/images/help/desktop/publish-repository-dialog-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.git.remove-git-remote %}
-2. [添加仓库到 GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/).
-{% data reusables.desktop.publish-repository %}
-4. 在 **Name(名称)**字段中键入所需的仓库名称,或者使用默认的当前本地仓库名称。 ![名称字段](/assets/images/help/desktop/publish-repository-name-win.png)
-5. 要发布公共仓库,请取消选择 **Keep this code private(保留此代码为私有)**。 ![保留此代码为私有复选框](/assets/images/help/desktop/publish-repository-private-checkbox-win.png)
-6. 从 **Organization(组织)**下拉菜单中选择要发布仓库到其中的组织,或者选择 **None(无)**以将仓库发布到您的个人帐户。 ![组织下拉菜单](/assets/images/help/desktop/publish-repository-org-dropdown-win.png)
-7. 单击 **Publish Repository(发布仓库)**按钮。 ![“发布仓库”对话框中的“发布仓库”按钮](/assets/images/help/desktop/publish-repository-dialog-button-win.png)
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/adding-and-cloning-repositories.md b/translations/zh-CN/content/desktop/contributing-to-projects/adding-and-cloning-repositories.md
deleted file mode 100644
index 42caad7a7c63..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/adding-and-cloning-repositories.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: 添加和克隆仓库
-intro: '将现有仓库从本地计算机添加至 {% data variables.product.prodname_desktop %},或从 {% data variables.product.product_name %} 克隆仓库。'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop.md b/translations/zh-CN/content/desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop.md
deleted file mode 100644
index 844445bcbc6c..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 从 GitHub Desktop 更改远程的 URL
-intro: '可在 {% data variables.product.prodname_desktop %} 中更改您操作的仓库的远程 URL。 如果仓库已经更名,或者拥有仓库的用户或组织已经改变,您便可执行此操作。'
-redirect_from:
- - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-1. 在 **Repository(仓库)**菜单中,单击 **Repository Settings...(仓库设置...)**。 ![仓库设置菜单选项](/assets/images/help/desktop/repository-settings-mac.png)
-2. 在 **Primary remote repository(主要远程仓库)**字段中,键入所需的 URL。 ![主要远程仓库字段](/assets/images/help/desktop/repository-settings-remote-mac.png)
-3. 单击 **Save(保存)**。 ![保存按钮](/assets/images/help/desktop/repository-settings-save-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. 在 **Repository(仓库)**菜单中,单击 **Repository Settings...(仓库设置...)**。 ![仓库设置菜单选项](/assets/images/help/desktop/repository-settings-win.png)
-2. 在 **Primary remote repository(主要远程仓库)**字段中,键入所需的 URL。 ![主要远程仓库字段](/assets/images/help/desktop/repository-settings-remote-win.png)
-3. 单击 **Save(保存)**。 ![保存按钮](/assets/images/help/desktop/repository-settings-save-win.png)
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop.md b/translations/zh-CN/content/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop.md
deleted file mode 100644
index fcd2ecbbbfb9..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: 将仓库从 GitHub 克隆到 GitHub Desktop
-intro: '您可以使用 {% data variables.product.prodname_dotcom %} 将远程仓库克隆到 {% data variables.product.prodname_desktop %}。'
-versions:
- free-pro-team: '*'
----
-
-{% tip %}
-
-**提示:**您也可以使用 {% data variables.product.prodname_desktop %} 克隆 {% data variables.product.prodname_dotcom %} 上的仓库。 更多信息请参阅“[从 {% data variables.product.prodname_desktop %} 克隆仓库](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)”。
-
-{% endtip %}
-
-{% mac %}
-
-1. 开始克隆前,请先登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_desktop %}。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.open-with-github-desktop %}
-5. 单击 **Choose...(选择...)**,并使用 Finder 窗口找到要克隆仓库的本地路径。 ![URL 选项卡中的选择按钮](/assets/images/help/desktop/clone-choose-button-url-mac.png)
-
- {% note %}
-
- **注:**如果仓库配置为使用 LFS,将会提示您初始化 {% data variables.large_files.product_name_short %}。
-
- {% endnote %}
-
-5. 单击 **Clone(克隆)**。 ![URL 选项卡中的克隆按钮](/assets/images/help/desktop/clone-button-url-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. 开始克隆前,请先登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_desktop %}。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.open-with-github-desktop %}
-5. 单击 **Choose...(选择...)**,并使用 Windows 资源管理器找到要克隆仓库的本地路径。 ![选择按钮](/assets/images/help/desktop/clone-choose-button-url-win.png)
-
- {% note %}
-
- **注:**如果仓库配置为使用 LFS,将会提示您初始化 {% data variables.large_files.product_name_short %}。
-
- {% endnote %}
-
-5. 单击 **Clone(克隆)**。 ![克隆按钮](/assets/images/help/desktop/clone-button-url-win.png)
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop.md b/translations/zh-CN/content/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop.md
deleted file mode 100644
index 42b3544c1118..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: 从 GitHub Desktop 克隆和复刻仓库
-intro: '您可以使用 {% data variables.product.prodname_desktop %} 克隆和复刻 {% data variables.product.prodname_dotcom %} 上的仓库。'
-redirect_from:
- - /desktop/contributing-to-projects/cloning-a-repository-from-github-desktop
-versions:
- free-pro-team: '*'
----
-
-### 克隆仓库
-{% data variables.product.prodname_dotcom %} 上的仓库作为远程仓库存在。 您可以克隆其他人拥有的公共仓库。 您可以克隆自己的仓库,从而在计算机上创建本地副本,并在两个本地位置之间实现同步。
-
-也可以直接从 {% data variables.product.prodname_dotcom %} 或 {% data variables.product.prodname_enterprise %} 克隆仓库。 更多信息请参阅“[将仓库从 {% data variables.product.prodname_dotcom %} 克隆至 {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)。”
-
-{% mac %}
-
-{% data reusables.desktop.choose-clone-repository %}
- ![Mac 应用程序中的克隆菜单选项](/assets/images/help/desktop/clone-file-menu-mac.png)
-{% data reusables.desktop.cloning-location-tab %}
- ![克隆仓库菜单中的 Location(位置)选项卡](/assets/images/help/desktop/choose-repository-location-mac.png)
-{% data reusables.desktop.cloning-repository-list %}
- ![克隆仓库列表](/assets/images/help/desktop/clone-a-repository-list-mac.png)
-4. 单击 **Choose...(选择...)**,并使用 Finder 窗口找到要克隆仓库的本地路径。 ![选择按钮](/assets/images/help/desktop/clone-choose-button-mac.png)
-5. 单击 **Clone(克隆)**。 ![克隆按钮](/assets/images/help/desktop/clone-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.choose-clone-repository %}
- ![Windows 应用程序中的克隆菜单选项](/assets/images/help/desktop/clone-file-menu-windows.png)
-{% data reusables.desktop.cloning-location-tab %}
- ![克隆仓库菜单中的 Location(位置)选项卡](/assets/images/help/desktop/choose-repository-location-win.png)
-{% data reusables.desktop.cloning-repository-list %}
- ![克隆仓库列表](/assets/images/help/desktop/clone-a-repository-list-win.png)
-4. 单击 **Choose...(选择...)**,并使用 Windows 资源管理器找到要克隆仓库的本地路径。 ![选择按钮](/assets/images/help/desktop/clone-choose-button-win.png)
-5. 单击 **Clone(克隆)**。 ![克隆按钮](/assets/images/help/desktop/clone-button-win.png)
-
-{% endwindows %}
-
-### 复刻仓库
-要对您没有写入权限的项目做出贡献,可以使用 {% data variables.product.prodname_desktop %} 创建仓库分支。 分支上的变更不会影响原始仓库。 您可以提交分支上的变更,然后将拉取请求对含有提议变更的原始仓库开放。 更多信息请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-forks)。”
-
-1. 如果您克隆了自己没有写入权限的仓库,并查实提交变更。{% data variables.product.prodname_desktop %} 将警告您“您对 **REPOSITORY(仓库)**没有写入权限。 单击 **create a fork(创建分支)**。 ![创建分支链接](/assets/images/help/desktop/create-a-fork.png)
-3. 单击 **Fork this repository(复刻此仓库)**。 ![复刻此仓库按钮](/assets/images/help/desktop/fork-this-repo-button.png)
-4. 要查看 {% data variables.product.prodname_dotcom %} 上的分支,请在 {% data variables.product.prodname_dotcom %} 右上角单击个人资料照片,然后再单击 **Your repositories(您的仓库)**。 ![您的仓库链接](/assets/images/help/profile/your-repositories.png)
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project.md b/translations/zh-CN/content/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project.md
deleted file mode 100644
index 4edefef0f879..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: 提交并审查对项目的更改
-intro: '{% data variables.product.prodname_desktop %} 可在您编辑时跟踪对所有文件的所有更改。 您可以决定如何对更改分组以创建有意义的提交。'
-versions:
- free-pro-team: '*'
----
-
-### 关于提交
-
-类似于保存文件,提交是对分支中一个或多个文件的更改。 Git 将为每个提交分配唯一的 ID,称为 SHA 或哈希,用于跟踪:
-
-- 具体的更改
-- 进行更改的时间
-- 更改创建者
-
-在进行提交时,必须包含简要描述更改的提交消息。 您也可以对协作处理的任何提交添加合作作者。
-
-### 1. 选择一个分支并进行更改
-
-1. [创建新分支](/desktop/guides/contributing-to-projects/managing-branches),或者单击工具栏中的 {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch(当前分支)**并从列表中选择现有分支。 ![用于切换当前分支的下拉菜单](/assets/images/help/desktop/click-branch-in-drop-down.png)
-{% data reusables.desktop.make-changes %}
-
-### 2. 选择要包含在提交中的更改
-
-在文本编辑器中更改文件并本地保存后,您会在 {% data variables.product.prodname_desktop %} 中看到更改。
-
-* 红色的 {% octicon "diff-removed" aria-label="The diff removed icon color-red" %} 图标表示删除的文件。
-* 黄色的 {% octicon "diff-modified" aria-label="The diff modified icon color-yellow" %} 图标表示修改的文件。
-* 绿色的 {% octicon "diff-added" aria-label="The diff added icon color-green" %} 图标表示添加的文件。
-* 要访问隐藏的更改,请单击 **Stashed Changes(隐藏的更改)**。 ![隐藏的更改选项](/assets/images/help/desktop/stashed-changes.png)
-* {% data reusables.desktop.commit-all-desc %}
-![选中复选框以提交所有更改的文件](/assets/images/help/desktop/commit-all.png)
-* {% data reusables.desktop.commit-some-desc %}
-![选中要提交的文件旁边的复选框](/assets/images/help/desktop/commit-some.png)
-
-#### 创建部分提交
-
-如果一个文件包含多处更改,但只有*部分*更改要包含在提交中,则可创建部分提交。 其余更改会保持不动,以便您进行其他修改和提交。 这允许您进行单独、有意义的提交,例如使提交中的换行符更改区别于代码或文字更改。
-
-在审查文件的差异时,包含在提交中的行将以蓝色高亮显示。 要排除更改,请单击更改的行让蓝色消失。
-
-![文件中取消选择的行](/assets/images/help/desktop/partial-commit.png)
-
-#### 放弃更改
-
-您可以放弃一个文件、一系列文件中所有未提交的更改,或者放弃上次提交后所有文件中的所有更改。
-
-{% mac %}
-
-{% data reusables.desktop.select-discard-files %}
-{% data reusables.desktop.click-discard-files %}
- ![上下文菜单中的 Discard Changes(放弃更改)选项](/assets/images/help/desktop/discard-changes-mac.png)
-{% data reusables.desktop.confirm-discard-files %}
- ![确认对话框中的放弃更改按钮](/assets/images/help/desktop/discard-changes-confirm-mac.png)
-
-{% tip %}
-
-**提示:**您放弃的更改保存在垃圾桶的日期文件中,在垃圾桶清空之前可以恢复。
-
-{% endtip %}
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %}
- ![上下文菜单中的 Discard Changes(放弃更改)选项](/assets/images/help/desktop/discard-changes-win.png)
-{% data reusables.desktop.confirm-discard-files %}
- ![确认对话框中的放弃更改按钮](/assets/images/help/desktop/discard-changes-confirm-win.png)
-
-{% tip %}
-
-**提示:**您放弃的更改保存在垃圾桶的文件中,在垃圾桶清空之前可以恢复。
-
-{% endtip %}
-
-{% endwindows %}
-
-### 3. 编写提交消息并推送更改
-
-对选择要包含在提交中的更改感到满意后,编写提交消息并推送更改。 如果协作处理了某个提交,也可以将提交归于多个作者。
-
-{% note %}
-
-**注**:{% data reusables.desktop.tags-push-with-commits %} 更多信息请参阅“[管理标记](/desktop/contributing-to-projects/managing-tags)。”
-
-{% endnote %}
-
-{% data reusables.desktop.commit-message %}
- ![提交消息字段](/assets/images/help/desktop/commit-message.png)
-2. (可选)要将某个提交归于另一个作者,请单击合作作者图标并输入要包含的用户名。 ![添加合作作者到提交消息](/assets/images/help/desktop/add-co-author-commit.png)
-{% data reusables.desktop.commit-button %}
- ![提交按钮](/assets/images/help/desktop/commit-button.png)
-4. 如果您尝试提交的分支受保护,Desktop 将警告您。
- - 要移动变更,请单击 **switch branches(切换分支)**。
- - 要将变更提交至受保护分支,请单击 **Commit to(提交至) _BRANCH(分支)_**。
-
- 有关受保护分支的更多信息,请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。 ![受保护分支警告](/assets/images/help/desktop/protected-branch-warning.png)
-{% data reusables.desktop.push-origin %}
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/creating-a-branch-for-your-work.md b/translations/zh-CN/content/desktop/contributing-to-projects/creating-a-branch-for-your-work.md
deleted file mode 100644
index 1b85c97f915f..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/creating-a-branch-for-your-work.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: 为您的工作创建分支
-intro: 如果您对仓库具有协作者权限,便可创建仓库默认分支以外的分支,以安全地试验更改。
-versions:
- free-pro-team: '*'
----
-
-### 创建分支
-
-{% tip %}
-
-**提示:**您创建的第一个新分支将基于默认分支,通常是 `master`。 如果有多个分支,您可以选择新分支是以当前检出的分支还是默认分支为基础。
-
-{% endtip %}
-
-{% mac %}
-
-{% data reusables.desktop.click-base-branch-in-drop-down %}
- ![用于切换当前分支的下拉菜单](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-{% data reusables.desktop.create-new-branch %}
- ![Branch(分支)菜单中的 New Branch(新分支)选项](/assets/images/help/desktop/new-branch-button-mac.png)
-{% data reusables.desktop.name-branch %}
- ![用于创建新分支名称的字段](/assets/images/help/desktop/create-branch-name-mac.png)
-{% data reusables.desktop.select-base-branch %}
- ![基础分支选项](/assets/images/help/desktop/create-branch-choose-branch-mac.png)
-{% data reusables.desktop.confirm-new-branch-button %}
- ![创建分支按钮](/assets/images/help/desktop/create-branch-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.click-base-branch-in-drop-down %}
- ![用于切换当前分支的下拉菜单](/assets/images/help/desktop/click-branch-in-drop-down-win.png)
-{% data reusables.desktop.create-new-branch %}
- ![Branch(分支)菜单中的 New Branch(新分支)选项](/assets/images/help/desktop/new-branch-button-win.png)
-{% data reusables.desktop.name-branch %}
- ![用于创建新分支名称的字段](/assets/images/help/desktop/create-branch-name-win.png)
-{% data reusables.desktop.select-base-branch %}
- ![基础分支选项](/assets/images/help/desktop/create-branch-choose-branch-win.png)
-{% data reusables.desktop.confirm-new-branch-button %}
- ![创建分支按钮](/assets/images/help/desktop/create-branch-button-win.png)
-
-{% endwindows %}
-
-### 延伸阅读
-
-- "[从 {% data variables.product.prodname_desktop %} 克隆仓库](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)"
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/creating-an-issue-or-pull-request.md b/translations/zh-CN/content/desktop/contributing-to-projects/creating-an-issue-or-pull-request.md
deleted file mode 100644
index 29fefb037dac..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/creating-an-issue-or-pull-request.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: 创建议题或拉取请求
-intro: 您可以创建议题或拉取请求,以提议并协作更改仓库。
-redirect_from:
- - /desktop/contributing-to-projects/creating-a-pull-request
-versions:
- free-pro-team: '*'
----
-
-### 打开新议题
-当您在本地处理 {% data variables.product.prodname_desktop %} 时发现漏洞或想要建议增强时,可以打开仓库中的新议题(如果议题已启用)。 有关处理议题的更多信息,请参阅“[关于议题](/github/managing-your-work-on-github/about-issues)。”
-
-{% mac %}
-
-1. 在屏幕的左上角,选择 **Repository(仓库)**菜单。 ![Mac 菜单栏中的 GitHub Desktop 菜单](/assets/images/help/desktop/select-repository-menu-mac.png)
-2. 单击**在 {% data variables.product.prodname_dotcom %} 上创建议题**。 ![分支菜单中的仓库值](/assets/images/help/desktop/create-issue-mac.png)
-3. 在 {% data variables.product.prodname_dotcom %} 上,单击 **Get started(开始使用)**打开议题模板,或单击 **Open a blank issue(打开空白议题)**。 ![创建新议题选项](/assets/images/help/desktop/create-new-issue.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. 在窗口的左上角,选择 **Repository(仓库)**菜单。 ![Mac 菜单栏中的 GitHub Desktop 菜单](/assets/images/help/desktop/select-repository-menu-windows.png)
-2. 单击**在 {% data variables.product.prodname_dotcom %} 上创建议题**。 ![分支菜单中的仓库值](/assets/images/help/desktop/create-issue-windows.png)
-3. 在 {% data variables.product.prodname_dotcom %} 上,单击 **Get started(开始使用)**打开议题模板,或单击 **Open a blank issue(打开空白议题)**。 ![创建新议题选项](/assets/images/help/desktop/create-new-issue.png)
-
-{% endwindows %}
-
-{% note %}
-
-**注**:如果您当前的仓库中未启用议题模板,{% data variables.product.prodname_desktop %} 会将您指引到 {% data variables.product.prodname_dotcom %} 上的空白议题。
-
-{% endnote %}
-
-### 创建新拉取请求
-在[创建分支](/desktop/guides/contributing-to-projects/managing-branches)和[提交一些更改](/desktop/guides/contributing-to-projects/committing-and-reviewing-changes-to-your-project)后,您可以打开拉取请求以获取对提议的更改的反馈。
-
-{% mac %}
-
-1. 在屏幕的左上角,选择 **Branch(分支)**菜单。 ![Mac 菜单栏中的 GitHub Desktop 菜单](/assets/images/help/desktop/mac-select-branch-menu.png)
-2. 单击 **Create pull request(创建拉取请求)**。 ![“分支”菜单中的“创建拉取请求”值](/assets/images/help/desktop/create-pull-request-mac.png)
-3. 在 {% data variables.product.prodname_dotcom %} 上,验证下拉菜单中的默认_基_分支和_比较_分支,并在必要时进行更改。 ![用于选择基础和比较分支的下拉菜单](/assets/images/help/pull_requests/choose-base-and-compare-branches.png)
-{% data reusables.repositories.pr-title-description %}
-{% data reusables.repositories.create-pull-request %}
-
-{% endmac %}
-
-{% windows %}
-
-1. 在窗口的左上角,选择 **Branch(分支)**菜单。 ![Windows 菜单栏中的 GitHub Desktop 菜单](/assets/images/help/desktop/windows-select-branch-menu.png)
-2. 单击 **Create pull request(创建拉取请求)**。 ![“分支”菜单中的“创建拉取请求”值](/assets/images/help/desktop/create-pull-request-win.png)
-3. 在 {% data variables.product.prodname_dotcom %} 上,验证下拉菜单中的默认_基_分支和_比较_分支,并在必要时进行更改。 ![用于选择基础和比较分支的下拉菜单](/assets/images/help/pull_requests/choose-base-and-compare-branches.png)
-{% data reusables.repositories.pr-title-description %}
-{% data reusables.repositories.create-pull-request %}
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/index.md b/translations/zh-CN/content/desktop/contributing-to-projects/index.md
deleted file mode 100644
index 1fc25fc2a0d9..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/index.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: 通过 GitHub Desktop 参与项目
-shortTitle: 参与项目
-intro: 使用 GitHub Desktop 管理项目,创建有意义的提交,并在应用程序(而非命令行)中跟踪项目的历史记录。
-versions:
- free-pro-team: '*'
----
-
-
-### 目录
-
-{% topic_link_in_list /adding-and-cloning-repositories %}
- {% link_in_list /adding-a-repository-from-your-local-computer-to-github-desktop %}
- {% link_in_list /adding-an-existing-project-to-github-using-github-desktop %}
- {% link_in_list /cloning-and-forking-repositories-from-github-desktop %}
- {% link_in_list /cloning-a-repository-from-github-to-github-desktop %}
-{% topic_link_in_list /making-changes-in-a-branch %}
- {% link_in_list /managing-branches %}
- {% link_in_list /committing-and-reviewing-changes-to-your-project %}
- {% link_in_list /pushing-changes-to-github %}
- {% link_in_list /reverting-a-commit %}
- {% link_in_list /managing-tags %}
- {% link_in_list /viewing-the-branch-history %}
-{% topic_link_in_list /working-with-your-remote-repository-on-github-or-github-enterprise %}
- {% link_in_list /syncing-your-branch %}
- {% link_in_list /creating-an-issue-or-pull-request %}
- {% link_in_list /accessing-a-pull-request-locally %}
- {% link_in_list /changing-a-remotes-url-from-github-desktop %}
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/making-changes-in-a-branch.md b/translations/zh-CN/content/desktop/contributing-to-projects/making-changes-in-a-branch.md
deleted file mode 100644
index c002e9628277..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/making-changes-in-a-branch.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: 在分支中更改
-intro: '使用您常用的文本编辑器,如 [Atom](https://atom.io/),更改您的项目,然后使用 {% data variables.product.prodname_desktop %} 可视化有用的提交。'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/managing-branches.md b/translations/zh-CN/content/desktop/contributing-to-projects/managing-branches.md
deleted file mode 100644
index ea6c318fdcd4..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/managing-branches.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Managing branches
-intro: You can create a branch off of a repository's default branch so you can safely experiment with changes.
-redirect_from:
- - /desktop/contributing-to-projects/creating-a-branch-for-your-work
- - /desktop/contributing-to-projects/switching-between-branches
-versions:
- free-pro-team: '*'
----
-
-### About managing branches
-You can use branches to safely experiment with changes to your project. Branches isolate your development work from other branches in the repository. For example, you could use a branch to develop a new feature or fix a bug.
-
-始终可以从现有分支创建分支。 通常,您可能从仓库的 `master` 分支创建分支。 然后,您可以单独处理这个新分支,不受其他人对仓库所做更改的影响。
-
-Once you're satisfied with your work, you can [open a pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request) to merge the changes in the current branch into another branch. 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests)”。
-
-You can always create a branch in {% data variables.product.prodname_desktop %} if you have read access to a repository, but you can only push the branch to {% data variables.product.prodname_dotcom %} if you have write access to the repository.
-
-{% data reusables.desktop.protected-branches %}
-
-### 创建分支
-
-{% tip %}
-
-**提示:**您创建的第一个新分支将基于默认分支,通常是 `master`。 If you have more than one branch, you can choose to base the new branch on the currently checked out branch or the default branch.
-
-{% endtip %}
-
-{% mac %}
-
-{% data reusables.desktop.click-base-branch-in-drop-down %}
- ![用于切换当前分支的下拉菜单](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-{% data reusables.desktop.create-new-branch %}
- ![Branch(分支)菜单中的 New Branch(新分支)选项](/assets/images/help/desktop/new-branch-button-mac.png)
-{% data reusables.desktop.name-branch %}
- ![用于创建新分支名称的字段](/assets/images/help/desktop/create-branch-name-mac.png)
-{% data reusables.desktop.select-base-branch %}
- ![基础分支选项](/assets/images/help/desktop/create-branch-choose-branch-mac.png)
-{% data reusables.desktop.confirm-new-branch-button %}
- ![创建分支按钮](/assets/images/help/desktop/create-branch-button-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.click-base-branch-in-drop-down %}
- ![用于切换当前分支的下拉菜单](/assets/images/help/desktop/click-branch-in-drop-down-win.png)
-{% data reusables.desktop.create-new-branch %}
- ![Branch(分支)菜单中的 New Branch(新分支)选项](/assets/images/help/desktop/new-branch-button-win.png)
-{% data reusables.desktop.name-branch %}
- ![用于创建新分支名称的字段](/assets/images/help/desktop/create-branch-name-win.png)
-{% data reusables.desktop.select-base-branch %}
- ![基础分支选项](/assets/images/help/desktop/create-branch-choose-branch-win.png)
-{% data reusables.desktop.confirm-new-branch-button %}
- ![创建分支按钮](/assets/images/help/desktop/create-branch-button-win.png)
-
-{% endwindows %}
-
-### 在分支间切换
-您可以查看并提交到任何仓库的分支。 如有未提交但已保存的更改,您需要决定如何处理更改,然后才可切换分支。 您可以在当前分支上提交更改、在当前分支上隐藏更改,或者将更改传送到新分支。 如果要在当前分支上提交更改,请在切换分支之前执行“[提交并审查对项目的更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)”中的步骤。
-
-{% tip %}
-
-**提示**:您可以在 **Advanced(高级)**设置中设置切换分支的默认行为。 For more information, see "[Configuring basic settings](/desktop/getting-started-with-github-desktop/configuring-basic-settings)."
-
-{% endtip %}
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.switching-between-branches %}
- ![仓库中的分支列表](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-3. 如有已保存但未提交的更改,请选择 **Leave my changes(留下我的更改)**或 **Bring my changes(带上我的更改)**,然后单击 **Switch Branch(切换分支)**。 ![通过更改选项切换分支](/assets/images/help/desktop/stash-changes-options.png)
-
-### 检索隐藏的更改
-要访问在另一个分支中隐藏的更改,请切换回隐藏更改的分支。
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.switching-between-branches %}
- ![仓库中的分支列表](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-3. 在左侧边栏中,单击 **Stashed Changes(隐藏的更改)**。 ![隐藏的更改选项](/assets/images/help/desktop/stashed-changes.png)
-4. 要删除隐藏的更改,请单击 **Discard(放弃)**,或者,要使用隐藏的更改,则单击 **Restore(恢复)**。 ![放弃或恢复隐藏的更改](/assets/images/help/desktop/discard-restore-stash-buttons.png)
-
-### 删除分支
-
-无法删除目前与打开的拉取请求关联的分支。 You cannot undo deleting a branch.
-
-{% mac %}
-
-{% data reusables.desktop.select-branch-to-delete %}
- ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-to-delete.png)
-{% data reusables.desktop.delete-branch-mac %}
- ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.select-branch-to-delete %}
- ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-to-delete.png)
-{% data reusables.desktop.delete-branch-win %}
- ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-win.png)
-
-{% endwindows %}
-
-### 延伸阅读
-
-- "[从 {% data variables.product.prodname_desktop %} 克隆仓库](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)"
-- {% data variables.product.prodname_dotcom %} 词汇中的“[分支](/articles/github-glossary/#branch)”
-- "[关于分支](/articles/about-branches)"
-- Git 文档中的“[Nutshell 中的分支](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)”
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/managing-tags.md b/translations/zh-CN/content/desktop/contributing-to-projects/managing-tags.md
deleted file mode 100644
index aba976ca4ad9..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/managing-tags.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: 管理标记
-intro: '您可以使用 {% data variables.product.prodname_desktop %} 创建、推送和查看标记。'
-versions:
- free-pro-team: '*'
----
-
-### 关于 {% data variables.product.prodname_desktop %} 中的标记
-
-{% data variables.product.prodname_desktop %} 可用于创建带注释的标记。 您可以使用标记在仓库的历史记录中标记单独的点,包括发行版的版本号。 有关发行版标记的更多信息,请参阅“[关于发行版](https://help.github.com/en/github/administering-a-repository/about-releases)。”
-
-{% data reusables.desktop.tags-push-with-commits %}
-
-### 创建标记
-
-{% data reusables.desktop.history-tab %}
-{% data reusables.desktop.create-tag %}
-{% data reusables.desktop.name-tag %}
-{% data reusables.desktop.confirm-tag %}
-
-### 查看标记
-
-{% data reusables.desktop.history-tab %}
-2. 单击提交。
- {% note %}
-
- **注**:如果标记未被推送至远程仓库,{% data variables.product.prodname_desktop %} 将显示箭头 {% octicon "arrow-up" aria-label="The up arrow icon" %}。
-
- {% endnote %}
-
- ![查看历史记录中的标记](/assets/images/help/desktop/viewing-tags-in-history.png)
-
-3. 与提交相关的所有标记均在提交元数据中可见。 ![查看提交中的标记](/assets/images/help/desktop/viewing-tags-in-commit.png)
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/pushing-changes-to-github.md b/translations/zh-CN/content/desktop/contributing-to-projects/pushing-changes-to-github.md
deleted file mode 100644
index 70843cb8b782..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/pushing-changes-to-github.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Pushing changes to GitHub
-shortTitle: Pushing changes
-intro: 'As you commit changes to your project locally, you can push those changes to {% data variables.product.prodname_dotcom %} so that others may access them from the remote repository.'
-permissions: People with write permissions can push changes to a repository.
-versions:
- free-pro-team: '*'
----
-
-### About pushing changes to {% data variables.product.prodname_dotcom %}
-
-When you push changes, you send the committed changes in your local repository to the remote repository on {% data variables.product.prodname_dotcom %}. If you change your project locally and want other people to have access to the changes, you must push the changes to {% data variables.product.prodname_dotcom %}.
-
-Before pushing changes, you should update your local branch to include any commits that have been added to the remote repository. If someone has made commits on the remote that are not on your local branch, {% data variables.product.prodname_desktop %} will prompt you to fetch the new commits before pushing your changes to avoid merge conflicts. For more information, see "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)."
-
-{% data reusables.desktop.protected-branches %}
-
-### Pushing changes to {% data variables.product.prodname_dotcom %}
-
-{% note %}
-
-**Note:** {% data variables.product.prodname_desktop %} will reject a push if it exceeds certain limits.
-
-- A push contains a large file over 100MB in size.
-- A push is over 2GB in total size.
-
-{% endnote %}
-
-{% data reusables.desktop.push-origin %}
-2. If {% data variables.product.prodname_desktop %} prompts you to fetch new commits from the remote, click **Fetch**. ![The Fetch button](/assets/images/help/desktop/fetch-newer-commits.png)
-3. Optionally, click **Create Pull Request** to open a pull request and collaborate on your changes. For more information, see "[Creating an issue or pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" ![The Create Pull Request button](/assets/images/help/desktop/create-pull-request.png)
-
-### 延伸阅读
-- "[Push](/github/getting-started-with-github/github-glossary/#push)" in the {% data variables.product.prodname_dotcom %} glossary
-- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)"
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/reverting-a-commit.md b/translations/zh-CN/content/desktop/contributing-to-projects/reverting-a-commit.md
deleted file mode 100644
index 32a573fe9040..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/reverting-a-commit.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: 还原提交
-intro: 您可以还原特定提交,以从分支中删除其变更。
-versions:
- free-pro-team: '*'
----
-
-在还原到上一个提交时,还原本身也是提交。 原提交仍会保留在仓库的历史记录中。
-
-{% tip %}
-
-**提示:**在还原多个提交时,最好按照从最新到最旧的顺序还原。 如果以其他顺序还原提交,可能会出现合并冲突。
-
-{% endtip %}
-
-{% mac %}
-
-{% data reusables.desktop.history-tab %}
-{% data reusables.desktop.revert-commit %}
- ![差异视图上方的还原选项](/assets/images/help/desktop/commit-revert-mac.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.history-tab %}
-{% data reusables.desktop.revert-commit %}
- ![差异视图上方的还原选项](/assets/images/help/desktop/commit-revert-win.png)
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/switching-between-branches.md b/translations/zh-CN/content/desktop/contributing-to-projects/switching-between-branches.md
deleted file mode 100644
index f4f4290cdfc9..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/switching-between-branches.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: 在分支间切换
-intro: 您可以查看并提交到任何仓库的分支。
-versions:
- free-pro-team: '*'
----
-
-### 在分支间切换
-如有未提交但已保存的更改,您需要决定如何处理更改,然后才可切换分支。 您可以在当前分支上提交更改、在当前分支上隐藏更改,或者将更改传送到新分支。 如果要在当前分支上提交更改,请在切换分支之前执行“[提交并审查对项目的更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)”中的步骤。
-
-{% tip %}
-
-**提示**:您可以在 **Advanced(高级)**设置中设置切换分支的默认行为。 更多信息请参阅“[配置基本设置](/desktop/getting-started-with-github-desktop/configuring-basic-settings)。”
-
-{% endtip %}
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.switching-between-branches %}
- ![仓库中的分支列表](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-3. 如有已保存但未提交的更改,请选择 **Leave my changes(留下我的更改)**或 **Bring my changes(带上我的更改)**,然后单击 **Switch Branch(切换分支)**。 ![通过更改选项切换分支](/assets/images/help/desktop/stash-changes-options.png)
-
-### 检索隐藏的更改
-要访问在另一个分支中隐藏的更改,请切换回隐藏更改的分支。
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.switching-between-branches %}
- ![仓库中的分支列表](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
-3. 在左侧边栏中,单击 **Stashed Changes(隐藏的更改)**。 ![隐藏的更改选项](/assets/images/help/desktop/stashed-changes.png)
-4. 要删除隐藏的更改,请单击 **Discard(放弃)**,或者,要使用隐藏的更改,则单击 **Restore(恢复)**。 ![放弃或恢复隐藏的更改](/assets/images/help/desktop/discard-restore-stash-buttons.png)
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/syncing-your-branch.md b/translations/zh-CN/content/desktop/contributing-to-projects/syncing-your-branch.md
deleted file mode 100644
index 73a3b2ebf85b..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/syncing-your-branch.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: 同步分支
-intro: '当提交推送到您在 {% data variables.product.prodname_dotcom %} 上的项目时,可与远程仓库同步保留项目的本地副本。'
-versions:
- free-pro-team: '*'
----
-
-必须将本地分支与远程仓库同步才可获得最初[创建分支](/desktop/guides/contributing-to-projects/managing-branches)后添加到上游分支的所有其他提交。
-
-### 更新本地分支
-
-1. 在 {% data variables.product.prodname_desktop %} 中,单击 {% octicon "git-branch" aria-label="The branch icon" %} **当前分支**并从列表中选择分支,以切换到要更新的本地分支。
-2. 单击 **Fetch origin(提取原点)**以更新分支。 ![提取源按钮](/assets/images/help/desktop/fetch-button.png)
-3. 如果远程分支上有提交,您可以单击 **Pull origin(拉取源)**或 **Pull origin with rebase(通过变基拉取源)**来拉取这些提交。 ![拉取源按钮](/assets/images/help/desktop/pull-button.png)
-{% data reusables.desktop.resolve-merge-conflicts %}
-
-### 将另一个分支合并到项目分支
-
-{% data reusables.desktop.current-branch-menu %}
-{% data reusables.desktop.choose-a-branch-to-merge %}
-{% data reusables.desktop.confirm-merging-branch %}
-
- {% note %}
-
- **注:**如果存在合并冲突,{% data variables.product.prodname_desktop %} 会在 **Merge BRANCH into BRANCH(合并 [分支] 到 [分支 ])**按钮上方提醒您。 在解决所有冲突之前无法合并分支。
-
- {% endnote %}
-
- ![合并按钮](/assets/images/help/desktop/merge-branch-button.png)
-{% data reusables.desktop.push-origin %}
-
-### 将项目分支变基到另一个分支
-有些工作流程需要或受益于变基而不是合并。 通过变基,可以重新排序、编辑提交或将其压缩到一起。 更多信息请参阅“[关于 Git 变基](/articles/about-git-rebase)”。
-
-1. 使用 **Branch(分支)**下拉菜单,并单击 **Rebase Current Branch(变基当前分支)**。 ![在分支中重新变基当前分支下拉菜单](/assets/images/help/desktop/rebase-current-branch.png)
-2. 单击要变基到当前分支的分支,然后单击 **Start rebase(开始变基)**。 ![开始变基按钮](/assets/images/help/desktop/start-rebase-button.png)
-3. 如果确定要变基,请单击 **Begin rebase(开始变基)**。 ![开始变基按钮](/assets/images/help/desktop/begin-rebase-button.png)
-{% data reusables.desktop.resolve-merge-conflicts %}
-4. 要上推本地更改,请单击 **Force push origin(强制推送源)**。 ![强制推送源](/assets/images/help/desktop/force-push-origin.png)
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/viewing-the-branch-history.md b/translations/zh-CN/content/desktop/contributing-to-projects/viewing-the-branch-history.md
deleted file mode 100644
index 3a72134d94e5..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/viewing-the-branch-history.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: 查看分支历史记录
-intro: '您可以在 {% data variables.product.prodname_desktop %} 中查看关于任何提交的详细信息,包括提交引入的变更差异。'
-versions:
- free-pro-team: '*'
----
-
-每个提交会显示:
-
- - 提交消息
- - 提交创建的时间
- - 提交者的用户名和头像(如果有)
- - 提交的 SHA-1 哈希(唯一 ID)
-
-{% data reusables.desktop.history-tab %}
-2. 在 **History(历史记录)**选项卡中,单击要审查的提交。 ![历史记录选项卡中的提交](/assets/images/help/desktop/branch-history-commit.png)
-3. 如果提交中有多个文件,单击个别文件可查看提交中对该文件的更改。 ![提交中的文件](/assets/images/help/desktop/branch-history-file.png)
-
-### 延伸阅读
-
-- "[同步分支](/desktop/guides/contributing-to-projects/syncing-your-branch/)"
diff --git a/translations/zh-CN/content/desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise.md b/translations/zh-CN/content/desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise.md
deleted file mode 100644
index 2cdc332fadf3..000000000000
--- a/translations/zh-CN/content/desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: 在 GitHub 或 GitHub Enterprise 上使用远程仓库
-intro: '在本地更改项目时,可以通过远程仓库持续更新它们。 在 Git 中,*远程*是存储代码的服务器。 在您的情况中,该服务器是 {% data variables.product.prodname_dotcom %} 或 {% data variables.product.prodname_enterprise %} 上的仓库。'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/about-the-github-desktop-windows-installer-package.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/about-the-github-desktop-windows-installer-package.md
deleted file mode 100644
index 862473d7a2b2..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/about-the-github-desktop-windows-installer-package.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: 关于 GitHub Desktop Windows Installer 包
-intro: '作为网络管理员,可以使用 Windows Installer 包文件 (`.msi`) 结合组策略或其他远程安装系统,将 {% data variables.product.prodname_desktop %} 部署到 Active Directory 管理的网络中的 Microsoft Windows 计算机。'
-versions:
- free-pro-team: '*'
----
-
-当用户下次登录其工作站时,Windows Installer 包将解压缩独立的安装程序 (`.exe`) 并配置 Windows 安装 {% data variables.product.prodname_desktop %}。 用户必须具有在其用户目录中安装 {% data variables.product.prodname_desktop %} 的权限。
-
-如果用户直接运行 {% data variables.product.prodname_desktop %} Windows Installer 包,他们将需要注销并再次登录到其工作站,才可完成安装。
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/authenticating-to-github.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/authenticating-to-github.md
deleted file mode 100644
index 401db3750e42..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/authenticating-to-github.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: 向 GitHub 验证
-intro: '将您的 {% data variables.product.product_name %} 帐户连接至 {% data variables.product.prodname_desktop %}。'
-redirect_from:
- - /desktop/getting-started-with-github-desktop/authenticating-to-github-using-the-browser
-versions:
- free-pro-team: '*'
----
-
-在进行身份验证之前,{% data reusables.desktop.get-an-account %}
-
-{% mac %}
-
-### 使用浏览器向 {% data variables.product.prodname_dotcom %} 验证
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-{% data reusables.desktop.mac-select-accounts %}
-4. 在“{% data variables.product.prodname_dotcom %}”右边单击 **Sign In(登录)**。 ![GitHub 的登录按钮](/assets/images/help/desktop/mac-sign-in-github.png)
-5. 在 Sign in(登录)窗格中,单击 **Sign in using your browser(使用浏览器登录)**。 ![使用浏览器链接登录](/assets/images/help/desktop/mac-sign-in-browser.png)
-{% data reusables.desktop.authenticate-in-browser %}
-{% data reusables.desktop.retrieve-2fa-in-browser %}
-{% data reusables.desktop.enter-2fa-in-browser %}
-9. 在 {% data variables.product.prodname_dotcom %} 验证帐户后,返回到 {% data variables.product.prodname_desktop %}。
-
-### 使用您的用户名和密码向 {% data variables.product.prodname_dotcom %} 验证
-
-{% data reusables.user_settings.password-authentication-deprecation-desktop %}
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-{% data reusables.desktop.mac-select-accounts %}
-{% data reusables.desktop.choose-product-authenticate %}
-5. 要添加 GitHub Enterprise 帐户,请在“Enterprise server address(企业服务器地址)”下键入您的凭据,然后单击 **Continue(继续)**。 ![GitHub Enterprise 的登录按钮](/assets/images/help/desktop/mac-sign-in-button-enterprise.png)
-6. 要添加 GitHub 帐户,请键入 GitHub.com 凭据,然后单击 **Sign in(登录)**。 ![GitHub 的登录按钮](/assets/images/help/desktop/mac-sign-in-button.png)
-{% data reusables.desktop.retrieve-2fa %}
-{% data reusables.desktop.return-to-desktop %} 在提示时,输入您的 2FA 代码,然后单击 **Sign in(登录)**。 ![2FA 代码提示](/assets/images/help/desktop/mac-2fa-code-prompt.png)
-
-{% endmac %}
-
-{% windows %}
-
-### 使用浏览器向 {% data variables.product.prodname_dotcom %} 验证
-
-{% data reusables.desktop.windows-choose-options %}
-{% data reusables.desktop.windows-select-accounts %}
-4. 在 "GitHub.com" 右边单击 **Sign in(登录)**。 ![GitHub 的登录按钮](/assets/images/help/desktop/windows-sign-in-github.png)
-5. 在 Sign in(登录)窗格中,单击 **Sign in using your browser(使用浏览器登录)**。 ![使用浏览器链接登录](/assets/images/help/desktop/windows-sign-in-browser.png)
-{% data reusables.desktop.authenticate-in-browser %}
-{% data reusables.desktop.retrieve-2fa-in-browser %}
-{% data reusables.desktop.enter-2fa-in-browser %}
-9. 在 {% data variables.product.prodname_dotcom %} 验证帐户后,返回到 {% data variables.product.prodname_desktop %}。
-
-### 使用您的用户名和密码向 {% data variables.product.prodname_dotcom %} 验证
-
-
-{% data reusables.user_settings.password-authentication-deprecation-desktop %}
-
-{% data reusables.desktop.windows-choose-options %}
-{% data reusables.desktop.windows-select-accounts %}
-{% data reusables.desktop.choose-product-authenticate %}
-5. 要添加 GitHub Enterprise 帐户,请在“Enterprise server address(企业服务器地址)”下键入您的凭据,然后单击 **Continue(继续)**。 ![GitHub Enterprise 的登录按钮](/assets/images/help/desktop/windows-sign-in-button-enterprise.png)
-6. 要添加 GitHub 帐户,请键入 GitHub.com 凭据,然后单击 **Sign in(登录)**。 ![GitHub 的登录按钮](/assets/images/help/desktop/windows-sign-in-button.png)
-{% data reusables.desktop.retrieve-2fa %}
-{% data reusables.desktop.return-to-desktop %} 在提示时,输入您的 2FA 代码,然后单击 **Sign in(登录)**。 ![2FA 代码提示](/assets/images/help/desktop/windows-2fa-code-prompt.png)
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-a-default-editor.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-a-default-editor.md
deleted file mode 100644
index 48617751412c..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-a-default-editor.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: 配置默认编辑器
-intro: 您可以配置 GitHub Desktop 在项目中使用您首选的文本编辑器或集成开发环境 (IDE) 打开文件。
-versions:
- free-pro-team: '*'
----
-
-### 支持的编辑器
-
-{% data variables.product.prodname_desktop %} 支持以下编辑器。
-
-{% mac %}
-
-- [Atom](https://atom.io/)
-- [MacVim](https://macvim-dev.github.io/macvim/)
-- [Visual Studio Code](https://code.visualstudio.com/)
-- [Visual Studio Codium](https://vscodium.com/)
-- [Sublime Text](https://www.sublimetext.com/)
-- [BBEdit](http://www.barebones.com/products/bbedit/)
-- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/)
-- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/)
-- [JetBrains Rider](https://www.jetbrains.com/rider/)
-- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/)
-- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/)
-- [JetBrains IntelliJ IDEA](https://www.jetbrains.com/idea/)
-- [JetBrains GoLand](https://www.jetbrains.com/go/)
-- [TextMate](https://macromates.com/)
-- [Brackets](http://brackets.io/)
- - 要将 Brackets 与 {% data variables.product.prodname_desktop %} 一起使用,您必须安装命令行快捷方式。 要安装快捷方式,请在菜单栏中单击 **File(文件)**,然后单击 **Install Command Line Shortcut(安装命令行快捷方式)**。
-- [Typora](https://typora.io/)
-- [CodeRunner](https://coderunnerapp.com/)
-- [SlickEdit](https://www.slickedit.com/)
-- [Xcode](https://developer.apple.com/xcode/)
-- [Android Studio](https://developer.android.com/studio)
-
-{% endmac %}
-
-{% windows %}
-
-- [Atom](https://atom.io/)
-- [Visual Studio Code](https://code.visualstudio.com/)
-- [Visual Studio Codium](https://vscodium.com/)
-- [Sublime Text](https://www.sublimetext.com/)
-- [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html)
-- [Typora](https://typora.io/)
-- [SlickEdit](https://www.slickedit.com/)
-- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/)
-- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/)
-- [JetBrains Rider](https://www.jetbrains.com/rider/)
-- [Notepad++](https://notepad-plus-plus.org/)
-
-{% endwindows %}
-
-### 配置默认编辑器
-
-{% mac %}
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-3. 在 Preferences(首选项)窗口中,选择 **Integrations(集成)**。 ![“首选项”窗口中的“集成”窗格](/assets/images/help/desktop/mac-select-integrations-pane.png)
-4. 使用“External Editor(外部编辑器)”下拉菜单,选择要设为默认的编辑器。 ![“首选项”菜单栏中的“外部编辑器”菜单](/assets/images/help/desktop/mac-editor-menu.png)
-5. 单击 **Save(保存)**。
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.windows-choose-options %}
-3. 在 Options(选项)窗口中,选择 **Integrations(集成)**。 ![“选项”窗口中的“集成”窗格](/assets/images/help/desktop/windows-select-integrations-pane.png)
-4. 使用“External Editor(外部编辑器)”下拉菜单,选择要设为默认的编辑器。 ![“选项”菜单栏中的“外部编辑器”菜单](/assets/images/help/desktop/windows-editor-menu.png)
-5. 单击 **Save(保存)**。
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop.md
deleted file mode 100644
index 441815ebcc6e..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: 配置和自定义 GitHub Desktop
-intro: 设置 Git,连接默认编辑器并自定义设置,使 GitHub Desktop 与您的工作流程保持一致。
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-basic-settings.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-basic-settings.md
deleted file mode 100644
index 3677197d8cc0..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-basic-settings.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: 配置基本设置
-intro: 您可以访问隐私保护设置,将帐户连接到 GitHub Desktop,以及配置 Git。
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-3. 要查看或更改设置,请在这些窗格之间切换: ![首选项菜单导航](/assets/images/help/desktop/mac-select-accounts-pane.png)
-{% data reusables.desktop.preferences-options-tabs %}
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.windows-choose-options %}
-2. 要查看或更改设置,请在这些窗格之间切换: ![选项菜单导航](/assets/images/help/desktop/windows-select-accounts-pane.png)
-{% data reusables.desktop.preferences-options-tabs %}
-
-{% endwindows %}
-
-### 延伸阅读
-
-- "[设置 {% data variables.product.prodname_desktop %} 的主题](/desktop/guides/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)"
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop.md
deleted file mode 100644
index 2623338f19ed..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: 配置 Git 用于 GitHub Desktop
-shortTitle: Configuring Git
-intro: 如果尚未安装 Git,在使用 GitHub Desktop 前必须先配置。
-versions:
- free-pro-team: '*'
----
-
-{% data variables.product.prodname_desktop %} uses the email address you set in your local Git configuration to connect commits with your account on {% data variables.product.product_name %}.
-
-{% data reusables.desktop.update-email-address %}
-
-{% tip %}
-
-**提示**:如果您执行公开提交,任何人都可以在您在的 Git 配置中查看电子邮件地址。 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address/)”。
-
-{% endtip %}
-
-{% mac %}
-
-{% data reusables.desktop.sign-in-choose-product %}
-{% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.emails %}
-{% data reusables.desktop.copy-email-git-config %}
-{% data reusables.desktop.return-to-desktop %}
-{% data reusables.desktop.mac-select-desktop-menu %}
-7. In the Preferences window, click **Git**. ![Preferences(首选项)菜单中的 Git 窗格](/assets/images/help/desktop/mac-select-git-pane.png)
-{% data reusables.desktop.name-field-git-config %}
- ![Git 配置的名称字段](/assets/images/help/desktop/mac-name-git-config.png)
-{% data reusables.desktop.paste-email-git-config %}
- ![Git 配置字段中粘贴的电子邮件地址](/assets/images/help/desktop/mac-email-git-config.png)
-{% data reusables.desktop.click-save-git-config %}
- ![Save button in Git configuration field](/assets/images/help/desktop/mac-save-git-config.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.sign-in-choose-product %}
-{% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.emails %}
-{% data reusables.desktop.copy-email-git-config %}
-{% data reusables.desktop.return-to-desktop %}
-{% data reusables.desktop.windows-choose-options %}
-8. In the Options window, click **Git**. ![Options(选项)菜单中的 Git 窗格](/assets/images/help/desktop/windows-select-git-pane.png)
-{% data reusables.desktop.name-field-git-config %}
- ![Git 配置的名称字段](/assets/images/help/desktop/windows-name-git-config.png)
-{% data reusables.desktop.paste-email-git-config %}
- ![Git 配置字段中粘贴的电子邮件地址](/assets/images/help/desktop/windows-email-git-config.png)
-{% data reusables.desktop.click-save-git-config %}
- ![Save button in Git configuration field](/assets/images/help/desktop/windows-save-git-config.png)
-
-{% endwindows %}
-
-### 延伸阅读
-
-- “[将电子邮件地址添加到您的 GitHub 帐户](/articles/adding-an-email-address-to-your-github-account/)”
-- "[设置提交电子邮件地址](/articles/setting-your-commit-email-address/)"
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop.md
deleted file mode 100644
index 1dc5a117a524..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: 使用 GitHub Desktop 创建第一个仓库
-intro: '您可以使用 {% data variables.product.prodname_desktop %} 快速处理 Git 仓库,而无需使用命令行。'
-versions:
- free-pro-team: '*'
----
-
-### 简介
-
-本指南将引导您使用 {% data variables.product.prodname_desktop %} 操作 Git 仓库。 {% data variables.product.prodname_desktop %} 可扩展并简化您的 {% data variables.product.prodname_dotcom_the_website %} 工作流程,它使用可视界面,而不是在命令行上使用命令文本。 在本指南结束时,您已经使用 {% data variables.product.prodname_desktop %} 创建仓库,更改仓库,并将更改推送到 {% data variables.product.prodname_dotcom_the_website %} 或 {% data variables.product.prodname_ghe_server %}。
-
-下载 {% data variables.product.prodname_desktop %} 并登录 {% data variables.product.prodname_dotcom %} 或 {% data variables.product.prodname_enterprise %} 之后,您可以创建和克隆教程仓库。 本教程将介绍使用 Git 和 {% data variables.product.prodname_dotcom %} 的基础知识,包括安装编辑器、创建分支、进行提交、推送到 {% data variables.product.prodname_dotcom_the_website %},以及创建拉取请求。 只要您在 {% data variables.product.prodname_desktop %} 上还没有任何仓库,就可以使用本教程。
-
-### 步骤 1. 安装并登录到 {% data variables.product.prodname_desktop %}
-
-1. 从 {% data variables.product.desktop_link %} 下载 {% data variables.product.prodname_desktop %}。 {% data variables.product.prodname_desktop %} 支持 Windows 和 macOS 的最新版本。 有关特定于操作系统的安装说明,请参阅“[安装 {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-github-desktop)”。
-
-2. 启动 {% data variables.product.prodname_desktop %} 并遵循初始欢迎屏幕上的流程登录到 {% data variables.product.product_name %} 帐户。 您将会看到“Configure Git(配置 Git)”步骤,用于设置名称和电子邮件地址。 为确保提交正确归因于您的 {% data variables.product.product_name %} 帐户,请使用与 {% data variables.product.product_name %} 帐户关联的电子邮件地址。 有关提交归属的更多信息,请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。
-
-### 步骤 2. 创建新仓库
-
-您会看到“Let's get started!(开始使用吧!)”视图,从中可以选择创建和克隆教程仓库、克隆现有仓库、新建仓库或添加现有仓库。
-
-#### 创建和克隆教程仓库
-
-1. 单击 **Create a tutorial repository and clone it(创建教程仓库并克隆它)**。 ![“创建和克隆教程仓库”按钮](/assets/images/help/desktop/getting-started-guide/create-and-clone-a-tutorial-repository.png)
-2. 按照教程中的提示进行操作。
-
-#### 创建新仓库
-
-1. 单击 **Create a New Repository on your Hard Drive...(在硬盘上创建新仓库...)**。 ![创建新仓库](/assets/images/help/desktop/getting-started-guide/creating-a-repository.png)
-2. 要创建新仓库,请填写以下字段: ![创建仓库选项](/assets/images/help/desktop/getting-started-guide/create-a-new-repository-options.png)
- - “Name(名称)”定义仓库在本地以及 {% data variables.product.product_name %} 上的名称。
- - “Description(说明)”是一个可选字段,可用于提供有关仓库目的的更多信息。
- - “Local path(本地路径)”设置仓库在计算机上的位置。 默认情况下,{% data variables.product.prodname_desktop %} 会在 _Documents_ 文件夹内创建 _GitHub_ 文件夹,用于存储仓库,但您也可以选择计算机上的任何位置。 您的新仓库将是所选位置内的文件夹。 例如,如果将仓库命名为 `Tutorial`,则会在为本地路径选择的文件夹内创建一个名为 _Tutorial_ 的文件夹。 下次创建或克隆新仓库时,{% data variables.product.prodname_desktop %} 会记住您选择的位置。
- - **Initialize this repository with a README(使用自述文件初始化此仓库)**创建包含 _README.md_ 文件的初始提交。 自述文件帮助人们了解项目的目的,因此建议选择此选项并加入有用的信息。 当有人访问您在 {% data variables.product.product_name %} 上的仓库时,自述文件是他们了解您的项目时看到的第一项内容。 更多信息请参阅“[关于自述文件](/articles/about-readmes)”。
- - **Git ignore(Git 忽略)**下拉菜单可让您添加自定义文件,以忽略本地仓库中您不想存储在版本控制中的特定文件。 如有您要使用的特定语言或框架,您可以从可用的列表中选择选项。 如果刚刚开始,尽请跳过此选择。 更多信息请参阅“[忽略文件](/articles/ignoring-files)”。
- - **License(许可证)**下拉菜单可让您将开源许可证添加到仓库中的 _LICENSE_ 文件。 您无需担心要立即添加许可证。 有关可用开源许可证以及如何将它们添加到仓库的更多信息,请参阅“[许可仓库](/articles/licensing-a-repository)”。
-3. 单击 **Create repository(创建仓库)**。
-
-### 步骤 3. 探索 {% data variables.product.prodname_desktop %}
-
-现在您已选择仓库,将会在屏幕顶部看到文件菜单。 在这里可以访问设置以及能在 {% data variables.product.prodname_desktop %} 中执行的操作。 大多数操作也有快捷键来帮助您提高工作效率。 有关键盘快捷键的完整列表,请参阅“[键盘快捷键](/desktop/getting-started-with-github-desktop/keyboard-shortcuts)”。
-
-1. 菜单下方的栏显示 {% data variables.product.prodname_desktop %} 中仓库的当前状态:
- - **Current repository(当前仓库)**显示您处理的仓库的名称。 您可以单击 **Current repository(当前仓库)**切换到 {% data variables.product.prodname_desktop %} 中的不同仓库。
- - **Current branch(当前分支)**显示您处理的分支的名称。 您可以单击 **Current branch(当前分支)**来查看仓库中的所有分支、切换到不同的分支或者创建新分支。 在仓库中创建拉取请求后,也可单击 **Current branch(当前分支)**查看它们。
- - **Publish repository(发布仓库)**会出现,因为您尚未将仓库发布到 {% data variables.product.product_name %},下一个步骤才发布。
-
- ![探索 GitHub Desktop](/assets/images/help/desktop/getting-started-guide/explore-github-desktop.png)
-
-2. 在左侧边栏中,您会看到 **Changes(更改)**和 **History(历史记录)**视图。
-
- - **Changes(更改)**视图显示您对当前分支中的文件已经做出但尚未提交到本地仓库的更改。 在底部,您还会看到“Summary(摘要)”框和“Description(说明)”文本框,以及 **Commit to master(提交到 master)**按钮。 这是提交新更改的位置。 **Commit(提交)**按钮指示您要将更改提交到哪个分支。 ![提交区域](/assets/images/help/desktop/getting-started-guide/commit-area.png)
-
- - **History(历史记录)**视图显示仓库当前分支上以前的提交。 您应会看到在创建仓库时 {% data variables.product.prodname_desktop %} 所创建的“初始提交”。 在提交的右侧,根据您在创建仓库时选择的选项,可能会看到 _.gitattributes_、_.gitignore_、_LICENSE_ 或 _README_ 文件。 您可以单击每个文件以查看该文件的差异,也就是提交中对该文件的更改。 差异只显示文件已更改的部分,而不显示文件的全部内容。 ![历史记录视图](/assets/images/help/desktop/getting-started-guide/history-view.png)
-
-### 步骤 4. 将仓库推送到 {% data variables.product.product_name %}
-
-目前,您的仓库只存在于您的计算机中,您是唯一能访问该仓库的人。 将仓库发布到 {% data variables.product.product_name %} 可使其在多个处理同一项目的计算机和团队成员之间保持同步。 要发布仓库,需先将其推送到 {% data variables.product.product_name %},这样它也会出现在 {% data variables.product.prodname_dotcom_the_website %} 上。
-
-1. 单击 **Publish repository(发布仓库)**。 ![发布仓库](/assets/images/help/desktop/getting-started-guide/publish-repository.png)
- - 您会看到几个熟悉的字段。 “Name(名称)”和“Description(说明)”与您创建仓库时完成的字段匹配。
- - 您会看到选项 **Keep this code private(保留此代码为私有)**。 如果不想与 {% data variables.product.product_name %} 的其他用户公开分享您的代码,请选择此选项。
- - **Organization(组织)**下拉菜单,如果有,可让您将仓库发布到 {% data variables.product.product_name %} 上您所属的特定组织。 如果您还不是组织的成员,没关系! ![发布仓库步骤](/assets/images/help/desktop/getting-started-guide/publish-repository-steps.png)
-2. 单击 **Publish repository(发布仓库)**。
-3. 您可以从 {% data variables.product.prodname_desktop %} 访问 {% data variables.product.prodname_dotcom_the_website %} 上的仓库。 在文件菜单中,单击 **Repository(仓库)**,然后单击 **View on GitHub(在 GitHub 上查看)**。 这会直接在默认浏览器中打开仓库。
-
-现在您的仓库已发布,我们回到 {% data variables.product.prodname_desktop %} 对本地仓库做其他更改。 首先,我们要设置默认文本编辑器。
-
-### 步骤 5. 设置文本编辑器
-
-为减少设置开发环境的时间,您可以直接从 {% data variables.product.prodname_desktop %} 启动多个文本编辑器和集成的开发环境 (IDE)。 从 {% data variables.product.prodname_desktop %} 中的仓库可以在常用文本编辑器中无缝打开项目文件夹。
-
-1. 依次单击 **File(文件)**、**Options(选项)**和 **Advanced(高级)**。
-2. 使用 **External editor(外部编辑器)**下拉菜单并从列表中选择编辑器。 您应该会在列表中看到所有已安装的编辑器。 如果没有看到任何编辑器,请安装支持的编辑器,如 [Atom](https://atom.io)。 有关支持的编辑器列表,请参阅 {% data variables.product.prodname_desktop %} 仓库中的[“打开外部编辑器”集成](https://github.com/desktop/desktop/blob/development/docs/technical/editor-integration.md#windows)。 ![外部编辑器](/assets/images/help/desktop/mac-editor-menu.png)
-3. 如果安装了新编辑器,请重新启动 {% data variables.product.prodname_desktop %} 以使该编辑器在 **External editor(外部编辑器)**下拉菜单中可用。
-
-### 步骤 6. 进行、提交和推送更改
-
-现在您已配置默认编辑器,可以更改项目并开始构建您自己对仓库的第一个提交。
-
-1. 要从 {% data variables.product.prodname_desktop %} 启动外部编辑器,请单击 **Repository(仓库)**,然后单击 **Open in EDITOR(在 [编辑器] 中打开)**。 ![在编辑器中打开](/assets/images/help/desktop/getting-started-guide/open-in-editor.png)
-
-2. 首先对以前创建的 _README.md_ 文件做一些更改。 添加描述项目的信息,比如它做什么,以及为什么有用。 请记住,这是人们与您的项目的第一次互动。 现在您可以进行第一次提交!
-3. 从文本编辑器切换回 {% data variables.product.prodname_desktop %},并找到 **Changes(更改)**选项卡。 在文件列表中,您应该会看到 _README.md_。 _README.md_ 文件旁边的勾选标记表示您对文件的更改将成为提交的一部分。 以后您可能会更改多个文件,但只想提交对其中部分文件所做的更改。 {% data variables.product.prodname_desktop %} 可让您选择要提交的特定更改。 ![查看更改](/assets/images/help/desktop/getting-started-guide/viewing-changes.png)
-
-4. 在 **Changes(更改)**列表底部,输入提交消息。 在头像右侧,键入提交的简短描述。 由于我们在更改 _README.md_ 文件,因此“添加关于项目目的的信息”将是比较好的提交摘要。 在摘要下方,您会看到“Description(说明)”文本字段,在其中可以键入较长的提交更改描述,这有助于回顾项目的历史记录和了解更改的原因。 由于您是对 _README.md_ 文件做基本的更新,因此可跳过描述。 ![提交消息](/assets/images/help/desktop/getting-started-guide/commit-message.png)
-5. 单击 **Commit to master(提交至 master)**。 提交按钮显示当前分支,本例中是 `master`,因此您可以确保提交到所需的分支。 ![提交到 master](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png)
-6. 要将更改推送到 {% data variables.product.product_name %} 上的远程仓库,请单击 **Push origin(推送源)**。 ![推送源](/assets/images/help/desktop/getting-started-guide/push-to-origin.png)
- - 还记得用于将仓库发布到 {% data variables.product.product_name %} 的 **Publish(发布)**按钮吗? 现在改为 `Push origin(推送源)`了,其旁边的 `1` 表示有一个提交尚未推送到 {% data variables.product.product_name %}。
- - **Push origin(推送源)**中的“源”表示我们将更改推送到名为 `origin` 的远程,在本例中是 {% data variables.product.prodname_dotcom_the_website %} 上的项目仓库。 在推送任何新提交到 {% data variables.product.product_name %} 之前,您的计算机上的项目仓库与 {% data variables.product.prodname_dotcom_the_website %} 上的项目仓库之间存在差异。 这可让您在本地工作,并且仅在准备好后才将工作推送到 {% data variables.product.prodname_dotcom_the_website %}。
-7. 在 **Changes(更改)**选项卡旁边打开的区域中,您会看到接下来可以执行的操作提示。 要在浏览器中打开 {% data variables.product.product_name %} 上的仓库,请单击 **View on GitHub(在 GitHub 中查看)**。 ![在 GitHub 上查看](/assets/images/help/desktop/getting-started-guide/view-on-github.png)
-8. 在浏览器中,单击 **2 commits(2 次提交)**。 您会看到 {% data variables.product.product_name %} 上此仓库中的提交列表。 第一个提交应是您刚才在 {% data variables.product.prodname_desktop %} 中的提交! ![单击两个提交](/assets/images/help/desktop/getting-started-guide/click-two-commits.png)
-
-### 结论
-
-恭喜! 您现已创建一个仓库,并且已将仓库发布到 {% data variables.product.product_name %},进行了提交,并且发布了更改。 我们只粗略介绍您通过 {% data variables.product.product_name %} 和 {% data variables.product.prodname_desktop %} 可以执行的操作。 希望此练习能激发您进一步探索的兴趣!
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/index.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/index.md
deleted file mode 100644
index 6a0530b6be42..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/index.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: GitHub Desktop 使用入门
-shortTitle: 入门指南
-intro: 设置 GitHub Desktop 来管理项目工作。 通过身份验证登录到 GitHub.com 或 GitHub Enterprise Server,确保应用程序为最新版本,然后审查您的偏好设置。
-redirect_from:
- - /desktop/getting-started-with-github-desktop/setting-up-github-desktop/
-versions:
- free-pro-team: '*'
----
-
-
-### 目录
-
-{% topic_link_in_list /overview %}
- {% link_in_list /creating-your-first-repository-using-github-desktop %}
- {% link_in_list /keyboard-shortcuts %}
- {% link_in_list /launching-github-desktop-from-the-command-line %}
-{% topic_link_in_list /installing-and-authenticating-to-github-desktop %}
- {% link_in_list /installing-github-desktop %}
- {% link_in_list /authenticating-to-github %}
- {% link_in_list /about-the-github-desktop-windows-installer-package %}
- {% link_in_list /updating-github-desktop %}
- {% link_in_list /uninstalling-github-desktop %}
-{% topic_link_in_list /configuring-and-customizing-github-desktop %}
- {% link_in_list /configuring-basic-settings %}
- {% link_in_list /configuring-git-for-github-desktop %}
- {% link_in_list /configuring-a-default-editor %}
- {% link_in_list /setting-a-theme-for-github-desktop %}
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop.md
deleted file mode 100644
index 90a7c61b254a..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: 安装 GitHub Desktop 并进行身份验证
-intro: 安装 GitHub Desktop,并连接您的 GitHub 或 GitHub Enterprise 帐户。
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/installing-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/installing-github-desktop.md
deleted file mode 100644
index f8f8244b1109..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/installing-github-desktop.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: 安装 GitHub Desktop
-intro: 您可以在受支持的 Microsoft Windows 或 macOS 操作系统上安装 GitHub Desktop。
-versions:
- free-pro-team: '*'
----
-
-在设置 {% data variables.product.prodname_desktop %}、{% data reusables.desktop.get-an-account %} 之前
-
-### 下载并安装 {% data variables.product.prodname_desktop %}
-
-{% mac %}
-
-您可以在 {% data variables.desktop.mac-osx-versions %} 上安装 {% data variables.product.prodname_desktop %}。
-
-{% data reusables.desktop.download-desktop-page %}
-2. 选择 **Download for Mac(为 Mac 下载)**。
-3. 在计算机的 **Downloads** 文件夹中,双击 **{% data variables.product.prodname_desktop %}** zip 文件。
-4. 在文件解压缩之后,双击 **{% data variables.product.prodname_desktop %}**。
-
-{% endmac %}
-
-{% windows %}
-
-您可以在 {% data variables.desktop.windows-versions %} 上安装 {% data variables.product.prodname_desktop %}。
-
-{% warning %}
-
-**警告**:必须有 64 位操作系统才可运行 {% data variables.product.prodname_desktop %}。
-
-{% endwarning %}
-
-{% data reusables.desktop.download-desktop-page %}
-2. 选择 **Download for Windows(为 Windows 下载)**。
-
- {% note %}
-
- **注:**如果您是网络管理员,便可使用 [{% data variables.product.prodname_desktop %} Windows 安装程序包](/desktop/guides/getting-started-with-github-desktop/about-the-github-desktop-windows-installer-package/)部署 {% data variables.product.prodname_desktop %}。
-
- {% endnote %}
-
-3. 在计算机的 **Downloads** 文件夹中,双击 **{% data variables.product.prodname_desktop %}**。
-4. 在弹出窗口中,单击 **Install(安装)**。
-5. 在程序安装后,单击 **Run(运行)**。
-
-{% endwindows %}
-
-### 设置 {% data variables.product.prodname_desktop %}
-
-在启动 {% data variables.product.prodname_desktop %} 后,可以选择立即设置 {% data variables.product.prodname_desktop %},也可以跳过设置过程。
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop.md
deleted file mode 100644
index d24f491a5307..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: GitHub Desktop 中的键盘快捷键
-intro: '您可以在 {% data variables.product.prodname_desktop %} 中使用键盘快捷键。'
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-MacOS 上的 GitHub Desktop 快捷键
-
-### 站点快捷键
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------ | ---------------------------------------------------------- |
-| ⌘, | 进入 Preferences(首选项) |
-| ⌘H | 隐藏 {% data variables.product.prodname_desktop %} 应用程序 |
-| ⌥⌘H | 隐藏所有其他应用程序 |
-| ⌘Q | 退出 {% data variables.product.prodname_desktop %} |
-| ⌃⌘F | 切换全屏视图 |
-| ⌘0 | 将缩放比例重置为默认的文本大小 |
-| ⌘= | 放大文本和图形 |
-| ⌘- | 缩小文本和图形 |
-| ⌥⌘I | 切换开发者工具 |
-
-### 仓库
-
-| 键盘快捷键 | Description |
-| ------------------------------------ | ---------------------------------------------------------- |
-| ⌘N | 新增仓库 |
-| ⌘O | 添加本地仓库 |
-| ⇧⌘O | 从 {% data variables.product.prodname_dotcom %} 克隆仓库 |
-| ⌘T | 显示仓库列表 |
-| ⌘P | 将最新提交推送到 {% data variables.product.prodname_dotcom %} |
-| ⇧⌘P | 从 {% data variables.product.prodname_dotcom %} 拉取最新更改 |
-| ⌘⌫ | 删除现有仓库 |
-| ⇧⌘G | 在 {% data variables.product.prodname_dotcom %} 上查看仓库 |
-| ⌃` | 在首选的终端工具中打开仓库 |
-| ⇧⌘F | 在 Finder 中显示仓库 |
-| ⇧⌘A | 在首选的编辑器工具中打开仓库 |
-| ⌘I | 在 {% data variables.product.prodname_dotcom %} 上创建议题 |
-
-### 分支
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------ | ------------------------------------------------------------- |
-| ⌘1 | 在提交前显示所有更改 |
-| ⌘2 | 显示提交历史记录 |
-| ⌘B | 显示所有分支 |
-| ⌘G | 转到提交摘要字段 |
-| space | Select or deselect all highlighted files |
-| ⇧⌘N | 创建新分支 |
-| ⇧⌘R | 重命名当前分支 |
-| ⇧⌘D | 删除当前分支 |
-| ⇧⌘U | 从默认分支更新 |
-| ⇧⌘B | 与现有分支比较 |
-| ⇧⌘M | 合并到当前分支 |
-| ⌃H | 显示或隐藏储存的更改 |
-| ⇧⌘C | 比较 {% data variables.product.prodname_dotcom %} 上的分支 |
-| ⌘R | 在 {% data variables.product.prodname_dotcom %} 上显示当前拉取请求 |
-
-{% endmac %}
-
-{% windows %}
-
-Windows 上的 GitHub Desktop 键盘快捷键
-
-### 站点快捷键
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------------- | --------------- |
-| Ctrl, | 转到 Options(选项) |
-| F11 | 切换全屏视图 |
-| Ctrl0 | 将缩放比例重置为默认的文本大小 |
-| Ctrl= | 放大文本和图形 |
-| Ctrl- | 缩小文本和图形 |
-| CtrlShiftI | 切换开发者工具 |
-
-### 仓库
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------------- | ---------------------------------------------------------- |
-| CtrlN | 新增仓库 |
-| CtrlO | 添加本地仓库 |
-| CtrlShiftO | 从 {% data variables.product.prodname_dotcom %} 克隆仓库 |
-| CtrlT | 显示仓库列表 |
-| CtrlP | 将最新提交推送到 {% data variables.product.prodname_dotcom %} |
-| CtrlShiftP | 从 {% data variables.product.prodname_dotcom %} 拉取最新更改 |
-| CtrlDelete | 删除现有仓库 |
-| CtrlShiftG | 在 {% data variables.product.prodname_dotcom %} 上查看仓库 |
-| Ctrl` | 在首选的命令行工具中打开仓库 |
-| CtrlShiftF | 在 Explorer 中显示仓库 |
-| CtrlShiftA | 在首选的编辑器工具中打开仓库 |
-| CtrlI | 在 {% data variables.product.prodname_dotcom %} 上创建议题 |
-
-### 分支
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------------- | ------------------------------------------------------------- |
-| Ctrl1 | 在提交前显示所有更改 |
-| Ctrl2 | 显示提交历史记录 |
-| CtrlB | 显示所有分支 |
-| CtrlG | 转到提交摘要字段 |
-| space | Select or deselect all highlighted files |
-| CtrlShiftN | 创建新分支 |
-| CtrlShiftR | 重命名当前分支 |
-| CtrlShiftD | 删除当前分支 |
-| CtrlShiftU | 从默认分支更新 |
-| CtrlShiftB | 与现有分支比较 |
-| CtrlShiftM | 合并到当前分支 |
-| CtrlH | 显示或隐藏储存的更改 |
-| CtrlShiftC | 比较 {% data variables.product.prodname_dotcom %} 上的分支 |
-| CtrlR | 在 {% data variables.product.prodname_dotcom %} 上显示当前拉取请求 |
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts.md
deleted file mode 100644
index a16e5b9e83b9..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/keyboard-shortcuts.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: 键盘快捷键
-redirect_from:
- - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop/
-intro: '您可以在 {% data variables.product.prodname_desktop %} 中使用键盘快捷键。'
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-MacOS 上的 GitHub Desktop 快捷键
-
-### 站点快捷键
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------ | ---------------------------------------------------------- |
-| ⌘, | 进入 Preferences(首选项) |
-| ⌘H | 隐藏 {% data variables.product.prodname_desktop %} 应用程序 |
-| ⌥⌘H | 隐藏所有其他应用程序 |
-| ⌘Q | 退出 {% data variables.product.prodname_desktop %} |
-| ⌃⌘F | 切换全屏视图 |
-| ⌘0 | 将缩放比例重置为默认的文本大小 |
-| ⌘= | 放大文本和图形 |
-| ⌘- | 缩小文本和图形 |
-| ⌥⌘I | 切换开发者工具 |
-
-### 仓库
-
-| 键盘快捷键 | Description |
-| ------------------------------------ | ---------------------------------------------------------- |
-| ⌘N | 新增仓库 |
-| ⌘O | 添加本地仓库 |
-| ⇧⌘O | 从 {% data variables.product.prodname_dotcom %} 克隆仓库 |
-| ⌘T | 显示仓库列表 |
-| ⌘P | 将最新提交推送到 {% data variables.product.prodname_dotcom %} |
-| ⇧⌘P | 从 {% data variables.product.prodname_dotcom %} 拉取最新更改 |
-| ⌘⌫ | 删除现有仓库 |
-| ⇧⌘G | 在 {% data variables.product.prodname_dotcom %} 上查看仓库 |
-| ⌃` | 在首选的终端工具中打开仓库 |
-| ⇧⌘F | 在 Finder 中显示仓库 |
-| ⇧⌘A | 在首选的编辑器工具中打开仓库 |
-| ⌘I | 在 {% data variables.product.prodname_dotcom %} 上创建议题 |
-
-### 分支
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------ | ------------------------------------------------------------- |
-| ⌘1 | 在提交前显示所有更改 |
-| ⌘2 | 显示提交历史记录 |
-| ⌘B | 显示所有分支 |
-| ⌘G | 转到提交摘要字段 |
-| space | 选择或取消选择所有突出显示的文件 |
-| ⇧⌘N | 创建新分支 |
-| ⇧⌘R | 重命名当前分支 |
-| ⇧⌘D | 删除当前分支 |
-| ⇧⌘U | 从默认分支更新 |
-| ⇧⌘B | 与现有分支比较 |
-| ⇧⌘M | 合并到当前分支 |
-| ⌃H | 显示或隐藏储存的更改 |
-| ⇧⌘C | 比较 {% data variables.product.prodname_dotcom %} 上的分支 |
-| ⌘R | 在 {% data variables.product.prodname_dotcom %} 上显示当前拉取请求 |
-
-{% endmac %}
-
-{% windows %}
-
-Windows 上的 GitHub Desktop 键盘快捷键
-
-### 站点快捷键
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------------- | --------------- |
-| Ctrl, | 转到 Options(选项) |
-| F11 | 切换全屏视图 |
-| Ctrl0 | 将缩放比例重置为默认的文本大小 |
-| Ctrl= | 放大文本和图形 |
-| Ctrl- | 缩小文本和图形 |
-| CtrlShiftI | 切换开发者工具 |
-
-### 仓库
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------------- | ---------------------------------------------------------- |
-| CtrlN | 新增仓库 |
-| CtrlO | 添加本地仓库 |
-| CtrlShiftO | 从 {% data variables.product.prodname_dotcom %} 克隆仓库 |
-| CtrlT | 显示仓库列表 |
-| CtrlP | 将最新提交推送到 {% data variables.product.prodname_dotcom %} |
-| CtrlShiftP | 从 {% data variables.product.prodname_dotcom %} 拉取最新更改 |
-| CtrlDelete | 删除现有仓库 |
-| CtrlShiftG | 在 {% data variables.product.prodname_dotcom %} 上查看仓库 |
-| Ctrl` | 在首选的命令行工具中打开仓库 |
-| CtrlShiftF | 在 Explorer 中显示仓库 |
-| CtrlShiftA | 在首选的编辑器工具中打开仓库 |
-| CtrlI | 在 {% data variables.product.prodname_dotcom %} 上创建议题 |
-
-### 分支
-
-| 键盘快捷键 | 描述 |
-| ------------------------------------------- | ------------------------------------------------------------- |
-| Ctrl1 | 在提交前显示所有更改 |
-| Ctrl2 | 显示提交历史记录 |
-| CtrlB | 显示所有分支 |
-| CtrlG | 转到提交摘要字段 |
-| space | 选择或取消选择所有突出显示的文件 |
-| CtrlShiftN | 创建新分支 |
-| CtrlShiftR | 重命名当前分支 |
-| CtrlShiftD | 删除当前分支 |
-| CtrlShiftU | 从默认分支更新 |
-| CtrlShiftB | 与现有分支比较 |
-| CtrlShiftM | 合并到当前分支 |
-| CtrlH | 显示或隐藏储存的更改 |
-| CtrlShiftC | 比较 {% data variables.product.prodname_dotcom %} 上的分支 |
-| CtrlR | 在 {% data variables.product.prodname_dotcom %} 上显示当前拉取请求 |
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line.md
deleted file mode 100644
index bddb3f7e7959..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: 从命令行启动 GitHub Desktop
-shortTitle: 从命令行启动
-intro: 您可以从命令行启动 GitHub Desktop。
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-1. 在菜单栏中,选择 **{% data variables.product.prodname_desktop %}** 菜单,然后单击 **Install Command Line Tool(安装命令行工具)**。 ![在 {% data variables.product.prodname_desktop %} 下拉菜单中安装命令行工具选项](/assets/images/help/desktop/mac-install-command-line-tool.png)
-2. 打开终端。
-3. {% data reusables.desktop.launch-desktop-from-command-line %}
-
- ```shell
- $ github /path/to/repo
- ```
-
- 您还可以更改为仓库路径,然后键入 `github .` 以打开该仓库。
-
- ```shell
- $ cd /path/to/repo
- [repo]$ github .
- ```
-
-{% endmac %}
-
-{% windows %}
-
-1. 打开命令提示。
-2. {% data reusables.desktop.launch-desktop-from-command-line %}
-
- ```shell
- C:\Users\octocat> github path\to\repo
- ```
-
- 您还可以更改为仓库路径,然后键入 `github .` 以打开该仓库。
-
- ```shell
- C:\Users\octocat> cd repo\myrepo
- C:\Users\octocat\repo\myrepo> github .
- ```
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/overview.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/overview.md
deleted file mode 100644
index aba96a70fcf5..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/overview.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: 概览
-intro: 了解 GitHub Desktop 并快速创建您的第一个仓库。
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop.md
deleted file mode 100644
index fab20912b4f3..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: 设置 GitHub Desktop 的主题
-intro: 您可以设置主题以自定义 GitHub Desktop 的外观。
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-{% data reusables.desktop.mac-select-desktop-menu %}
-{% data reusables.desktop.choose-a-theme %}
- ![Mac 外观选项卡上的主题选项](/assets/images/help/desktop/mac-appearance-tab-themes.png)
-
-{% endmac %}
-
-{% windows %}
-
-{% data reusables.desktop.windows-choose-options %}
-{% data reusables.desktop.choose-a-theme %}
- ![Windows 外观选项卡上的主题选项](/assets/images/help/desktop/windows-appearance-tab-themes.png)
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/uninstalling-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/uninstalling-github-desktop.md
deleted file mode 100644
index 261659b6b5c4..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/uninstalling-github-desktop.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 卸载 GitHub Desktop
-intro: You can uninstall GitHub Desktop from your computer at any time.
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-1. In a Finder window, navigate to the Applications folder. ![Applications folder in the Finder window](/assets/images/help/desktop/applications-folder.png)
-2. While pressing the **Control** button on your keyboard, click **{% data variables.product.prodname_desktop %}**.
-3. 选择 **Move to Trash(移至垃圾桶)**。 ![The Move to Trash option](/assets/images/help/desktop/mac-move-to-trash.png)
-4. In the menu bar, use the **Finder** drop-down menu, then click **Empty Trash**. ![The Empty Trash option in the menu bar](/assets/images/help/desktop/mac-empty-trash-menu.png)
-5. 阅读弹出框中的警告,并单击 **Empty Trash(清空垃圾桶)**。 ![The Empty Trash button](/assets/images/help/desktop/mac-empty-trash-button.png)
-
-{% endmac %}
-
-{% windows %}
-
-1. Open Control Panel. For more information, see [Where is Control Panel?](https://support.microsoft.com/en-us/help/13764/windows-where-is-control-panel) in Windows Help.
-2. Under "Programs", click **Uninstall a program**. ![The Uninstall a Program option in Control Panel](/assets/images/help/desktop/windows-uninstall-a-program.png)
-3. Right-click the entry named **{% data variables.product.prodname_desktop %}**, then click **Uninstall**. ![The Uninstall option](/assets/images/help/desktop/windows-click-uninstall.png)
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/updating-github-desktop.md b/translations/zh-CN/content/desktop/getting-started-with-github-desktop/updating-github-desktop.md
deleted file mode 100644
index 290fae22f681..000000000000
--- a/translations/zh-CN/content/desktop/getting-started-with-github-desktop/updating-github-desktop.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: 更新 GitHub Desktop
-intro: GitHub Desktop 在您重新启动时自动下载并安装更新。 您也可以手动检查更新。
-versions:
- free-pro-team: '*'
----
-
-{% mac %}
-
-1. 在 **GitHub Desktop** 菜单中,单击 **About GitHub Desktop(关于 GitHub Desktop)**。 ![关于 GitHub Desktop 菜单选项](/assets/images/help/desktop/desktop-menu-about-desktop-mac.png)
-2. 单击 **Check for Updates(检查更新)**。 ![检查更新按钮](/assets/images/help/desktop/check-for-updates.png)
-3. 如果更新可用,请退出并重新启动 {% data variables.product.prodname_desktop %} 以安装更新。
-
-{% endmac %}
-
-{% windows %}
-
-1. 在 **Help(帮助)** 菜单中,单击 **About GitHub Desktop(关于 GitHub Desktop)**。 ![关于 GitHub Desktop 菜单选项](/assets/images/help/desktop/help-about-desktop-win.png)
-2. 单击 **Check for Updates(检查更新)**。 ![检查更新按钮](/assets/images/help/desktop/check-for-updates.png)
-3. 如果更新可用,请退出并重新启动 {% data variables.product.prodname_desktop %} 以安装更新。
-
-{% endwindows %}
diff --git a/translations/zh-CN/content/github/administering-a-repository/about-github-dependabot.md b/translations/zh-CN/content/github/administering-a-repository/about-github-dependabot.md
deleted file mode 100644
index efc74912373f..000000000000
--- a/translations/zh-CN/content/github/administering-a-repository/about-github-dependabot.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: 关于 GitHub Dependabot
-intro: '您可以使用 {% data variables.product.prodname_dependabot %} 来确保您使用的包更新到最新版本。'
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.dependabot.beta-note %}
-
-### 关于 {% data variables.product.prodname_dependabot %}
-
-{% data variables.product.prodname_dependabot %} 是一款 {% data variables.product.prodname_dotcom %} 应用程序,它负责维护您的依赖项。 您可以使用它来确保仓库自动跟上它所依赖的包和应用程序的最新版本。
-
-通过将配置文件检入仓库,可启用 {% data variables.product.prodname_dependabot_version_updates %}。 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 该应用程序使用此信息来检查过时的包和应用程序。 The {% data variables.product.prodname_dependabot_short %} app determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. 当应用程序发现过时的依赖项时,它会发起拉取请求以将清单更新到依赖项的最新版本。 检查测试是否通过,查看拉取请求摘要中包含的更改日志和发行说明,然后合并它。 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”。
-
-如果启用安全更新,{% data variables.product.prodname_dependabot %} 还会发起拉取请求以更新易受攻击依赖项。 更多信息请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)。”
-
-{% data reusables.dependabot.dependabot-tos %}
-
-### {% data variables.product.prodname_dependabot %} 拉取请求的频率
-
-在配置文件中指定检查每个生态系统的新版本的频率:每日、每周或每月。
-
-{% data reusables.dependabot.initial-updates %}
-
-如果您启用了安全更新,有时会看到额外的安全更新拉取请求。 这些由针对默认分支上依赖项的 Dependabot 警报触发。 {% data variables.product.prodname_dependabot %} 自动提出拉取请求以更新有漏洞的依赖项。
-
-### 支持的仓库和生态系统
-
-您可以为包含其中一个受支持包管理器的依赖项清单或锁定文件的仓库配置版本更新。
-
-{% data reusables.dependabot.supported-package-managers %}
-
-如果您的仓库已使用集成进行依赖项管理,则在启用 {% data variables.product.prodname_dependabot %} 前需要禁用此集成。 更多信息请参阅“[关于集成](/github/customizing-your-github-workflow/about-integrations)”。
diff --git a/translations/zh-CN/content/github/administering-a-repository/setting-the-default-branch.md b/translations/zh-CN/content/github/administering-a-repository/setting-the-default-branch.md
deleted file mode 100644
index 5017a55a3f2c..000000000000
--- a/translations/zh-CN/content/github/administering-a-repository/setting-the-default-branch.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: 设置默认分支
-intro: 'If you have more than one branch in your repository, you can choose another branch to be the default branch.'
-redirect_from:
- - /articles/setting-the-default-branch
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### About the default branch
-
-{% data reusables.branches.new-repo-default-branch %} {% data reusables.branches.default-branch-automatically-base-branch %} If you have more than one branch in your repository, anyone with admin rights over a repository can select one of these existing branches as the default branch on the repository.
-
-### 设置默认分支
-
-{% note %}
-
-**Note:** To set the default branch you must have more than one branch in your repository.
-
-{% endnote %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.repository-branches %}
-4. In the default branch drop-down, choose the new default branch. ![默认分支下拉选择器](/assets/images/help/repository/repository-options-defaultbranch.png)
-5. Click **Update**.
-
-您只能在 {% data variables.product.product_location %} 上已存在的分支之间切换。 要通过 UI 创建新分支,请参阅“[创建和删除仓库中的分支](/articles/creating-and-deleting-branches-within-your-repository)”。
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-
-You can also set the default branch name for any newly created repositories owned by your user account, organization, or enterprise account. For more information, see "[Managing the default branch for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)", "[Managing the default branch name for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization), or "[Enforcing a policy on the default branch name](/github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)."
-
-{% endif %}
-
-{% warning %}
-
-**Warning**: Setting a different default branch affects your `trunk` branch contents on the [Git-Subversion bridge](https://github.com/blog/1178-collaborating-on-github-with-subversion) and the `HEAD` you'd see when you `git ls-remote` this [repository's upstream URL](https://git-scm.com/docs/git-ls-remote.html).
-
-{% endwarning %}
diff --git a/translations/zh-CN/content/github/articles/README.md b/translations/zh-CN/content/github/articles/README.md
deleted file mode 100644
index 1eaef8c78676..000000000000
--- a/translations/zh-CN/content/github/articles/README.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Hidden GitHub.com articles
-
-GitHub.com/Enterprise User articles that have `hidden: true` frontmatter live in this directory.
-
-See [`content/README`](../README.md#hidden-pages) for more about hidden pages.
diff --git a/translations/zh-CN/content/github/articles/about-the-github-and-visual-studio-bundle.md b/translations/zh-CN/content/github/articles/about-the-github-and-visual-studio-bundle.md
deleted file mode 100644
index 8d8be0e31af8..000000000000
--- a/translations/zh-CN/content/github/articles/about-the-github-and-visual-studio-bundle.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: 关于 GitHub 和 Visual Studio 包
-hidden: true
-redirect_from:
- - /articles/about-the-github-and-visual-studio-bundle
-versions:
- free-pro-team: '*'
----
-
-{% tip %}
-
-**提示**:
-- 仅组织所有者才可邀请用户加入组织。 更多信息请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization)”。
-
-{% endtip %}
-
-
-### 本文内容
-- [关于 {% data variables.product.prodname_enterprise %} 和 Visual Studio 包许可](#about-github-enterprise-and-visual-studio-bundle-licenses)
-- [分配 {% data variables.product.prodname_enterprise %} 用户许可](#assigning-a-github-enterprise-user-license)
-- [用户许可过度分配](#overallocation-of-user-licenses)
-
-
-### 关于 {% data variables.product.prodname_enterprise %} 和 Visual Studio 包许可
-
-已经购买 {% data variables.product.prodname_dotcom %}-Visual Studio 包的客户有资格获得 {% data variables.product.prodname_enterprise %} 用户许可。 这些许可在 {% data variables.product.prodname_dotcom %} 企业帐户中配置,与 Microsoft 企业协议关联,可分配给组织成员。
-
-当企业中的组织所有者邀请新用户加入组织时,他们可选择是否从 {% data variables.product.prodname_enterprise %} 或订阅了 Visual Studio 的 {% data variables.product.prodname_enterprise %} 分配新用户许可。
-
-### 分配 {% data variables.product.prodname_enterprise %} 用户许可
-
-{% data reusables.profile.access_profile %}
-{% data reusables.profile.access_org %}
-{% data reusables.organizations.people %}
-{% data reusables.organizations.invite_member_from_people_tab %}
-{% data reusables.organizations.invite_to_org %}
-{% data reusables.organizations.choose-to-restore-privileges %}
-{% data reusables.organizations.choose-user-role %}
-{% data reusables.organizations.choose-user-license %}
-{% data reusables.organizations.add-user-to-teams %}
-{% data reusables.organizations.send-invitation %}
-{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
-
-### 用户许可过度分配
-
-您可以在企业帐户的帐单设置中查看已经用于 {% data variables.product.prodname_enterprise %} 和订阅了 Visual Studio 的 {% data variables.product.prodname_enterprise %} 的许可总数。
-
-如果组织和企业所有者分配给用户的 {% data variables.product.prodname_enterprise %} (Visual Studio) 订阅许可超过订阅中包含的许可,则您的下一张调整发票将包含超过订阅允许数量的用户数所对应的费用。
-
-更多信息请参阅"[查看企业帐户的订阅和使用](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)"。
-
-### 延伸阅读
-- "[向团队添加组织成员](/articles/adding-organization-members-to-a-team)"
-- 如果您的组织[需要成员使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization),则您邀请的用户必须[启用双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa),然后才可接受邀请。
diff --git a/translations/zh-CN/content/github/articles/managing-your-disabled-github-pages-site.md b/translations/zh-CN/content/github/articles/managing-your-disabled-github-pages-site.md
deleted file mode 100644
index 3ee52ae9a538..000000000000
--- a/translations/zh-CN/content/github/articles/managing-your-disabled-github-pages-site.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 管理禁用的 GitHub 页面站点
-intro: '{% data variables.product.prodname_free_user %} 上的私有仓库不支持 {% data variables.product.prodname_pages %},但少量连接到免费私有仓库的 {% data variables.product.prodname_pages %} 站点被误保留为活动。 这些站点不再更新,将在 2019 年 5 月 10 日被 {% data variables.product.prodname_dotcom %} 取消发布。'
-hidden: true
-redirect_from:
- - /articles/managing-your-disabled-github-pages-site
-versions:
- free-pro-team: '*'
----
-
-{% note %}
-
-{% data variables.product.prodname_pages %} 仅可用于具有 {% data variables.product.prodname_free_user %} 的公共仓库,以及具有 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_server %} 的公共和私有仓库。 {% data reusables.gated-features.more-info %}
-
-{% endnote %}
-
-如果您在免费私有仓库中发布了 {% data variables.product.prodname_pages %} 站点,将有几个选项可用于继续发布和更新站点,或者手动取消发布站点。 如果您不执行操作,{% data variables.product.prodname_dotcom %} 将在 2019 年 5 月 10 日为您取消发布站点。
-
-- **要继续发布和更新 {% data variables.product.prodname_pages %} 站点**,您可以将仓库设为公共,或者将帐户升级到 {% data variables.product.prodname_pro %}。 有关如何将私有仓库设为公共的更多信息,请参阅“[设置仓库可见性](/articles/setting-repository-visibility#making-a-private-repository-public)”。有关升级帐户的信息,请参阅“[升级 GitHub 订阅](/articles/upgrading-your-github-subscription)”。
-
-- **要停止发布 {% data variables.product.prodname_pages %} 站点**,您可以[手动取消发布](#manually-unpublishing-your-github-pages-site),或者不采取任何措施,等到 2019 年 5 月 10 日,{% data variables.product.prodname_dotcom %} 将为您取消发布站点。 如果您的 {% data variables.product.prodname_pages %} 站点设置了自定义域,您应尽快通过 DNS 提供商更新或删除 DNS 记录,以避免域接管的风险。 在 {% data variables.product.prodname_pages %} 站点禁用时通过 DNS 提供商配置自定义域,可能导致其他人在您的一个子域上托管站点。 更多信息请参阅“[对 {% data variables.product.prodname_pages %} 使用自定义域](/articles/using-a-custom-domain-with-github-pages)”。
-
-### 手动取消发布 {% data variables.product.prodname_pages %} 站点
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. 在左侧边栏中,单击 **Unpublish {% data variables.product.prodname_pages %}(取消发布站点)**。 ![用于取消发布 {% data variables.product.prodname_pages %} 站点的 Repo 设置](/assets/images/help/pages/unpublish-pages-button-sidebar.png)
-4. 单击 **Unpublish this site(取消发布此站点)**。 ![用于取消发布 {% data variables.product.prodname_pages %} 站点的按钮](/assets/images/help/pages/unpublish-pages-button.png)
-
-### 延伸阅读
-
-- "[取消发布用户页面站点](articles/unpublishing-a-user-pages-site)"
-- "[取消发布项目页面站点](/articles/unpublishing-a-project-pages-site)"
-- "[转让仓库](/articles/transferring-a-repository)"
-- "[关于存档仓库](/articles/about-archiving-repositories)"
-- "[删除仓库](/articles/deleting-a-repository)"
diff --git a/translations/zh-CN/content/github/articles/searching-and-navigating-code.md b/translations/zh-CN/content/github/articles/searching-and-navigating-code.md
deleted file mode 100644
index 1429712693d8..000000000000
--- a/translations/zh-CN/content/github/articles/searching-and-navigating-code.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 搜索和导航代码
-intro: 搜索和导航代码是开发工作流程的重要组成部分,GitHub 正不断改进这些领域: 如果您是选择采用代码搜索和导航专用测试版的组织的成员,将可以访问功能强大的新搜索和导航工具。 有关此专用测试版的其他问题,请发送电子邮件至 search-beta@github.com。
-hidden: true
-redirect_from:
- - /articles/searching-and-navigating-code
-versions:
- free-pro-team: '*'
----
-
-
-### 本文内容
-
-- [文字代码搜索](#literal-code-search)
-- [相关性](#relevancy)
-- [跳至导航](#jump-to-navigation)
-
-### 文字代码搜索
-
-在此专用测试版之前,从搜索索引中删除了许多符号,这意味着如 `>>` 之类的惯用内容不可搜索。 例如,在仓库中搜索 `>>` 时,将返回零结果。 使用专用测试版时,您可以将符号包含在双引号中,然后便可查看正确的结果。 此功能并非仅限于符号,可让您搜索引号内的完整短语,如 `"return [] unless"`。 此功能适用于所有语言的代码搜索。
-
-### 相关性
-
-对于语言的子集(Go、JavaScript、Python、Ruby 和 TypeScript),代码搜索现在可调节声明的相关性。 方法、函数、类或其他实体的声明将在包含相同搜索词的调用或注释之前返回。
-
-### 跳至导航
-
-对于语言的子集(Go、JavaScript、Python、Ruby 和 TypeScript),GitHub 现在支持单击符号时的其他信息和导航。 此导航包括跳至仓库内资源的定义导航,从而能够更快地导航和提高洞察力。
-
-### 反馈
-
-当前选择采用代码搜索和导航专用测试版的所有用户均可通过进行[此调查](https://www.research.net/r/CodeSearch-Navigation)提供反馈。 有关其他反馈和问题,请发送电子邮件至 search-beta@github.com。
-
-### 延伸阅读
-- [关于在 GitHub 上搜索](/articles/about-searching-on-github/)
-- [在拉取请求中查找已更改的方法和函数](/articles/finding-changed-methods-and-functions-in-a-pull-request/)
diff --git a/translations/zh-CN/content/github/articles/using-gist-playground.md b/translations/zh-CN/content/github/articles/using-gist-playground.md
deleted file mode 100644
index 4f45922ea535..000000000000
--- a/translations/zh-CN/content/github/articles/using-gist-playground.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: 使用 Gist Playground
-intro: ''
-hidden: true
-redirect_from:
- - /articles/articles/using-gist-playground
-versions:
- free-pro-team: '*'
----
-
-{% note %}
-
-**注:**Gist Playground 可作为受限的专用测试版程序提供,受早期访问协议约束。
-
-{% endnote %}
-
-### 本文内容
-- [关于 Gist Playground](#about-gist-playground)
-- [创建新 gist](#creating-new-gists)
-- [保存更改](#saving-your-changes)
-- [与其他人协作](#collaborating-with-others)
-- [报告漏洞和反馈](#reporting-bugs-and-feedback)
-
-### 关于 Gist Playground
-Gist Playground 是 [Gist](https://gist.github.com/) 的实验性迭代。 当您与好友及同事一起协作时,您的更改将自动保存。
-
-### 创建新 gist
-访问 Gist Playground 时将自动创建新草稿或显示最近的草稿。 准备好创建和共享 gist 后,单击标题中的 **Create gist(创建 gist)**。
-
-Gist Playground 中创建的所有 gist 均为*机密*。 目前没有任何途径可从 Gist Playground 内将 gist 设为公开。 如果想要将 gist 设为公开,您可以使用现有的 [Gist](https://gist.github.com/) 进行此操作。
-
-### 保存更改
-您的更改随着输入自动保存。 您可以随时关闭选项卡,然后返回而不丢失任何工作。
-
-位于检查点后,您可以单击标题中的 **Update gist(更新 gist)**更新带有这些更改的 gist。
-
-### 与其他人协作
-您可以与加入 Gist Playground 专用测试版的任何其他人协作。 在“Invite to collaborate(邀请协作)”下,单击协作 URL 进行复制,将该 URL 发送给好友,然后便可一起进行更改。
-
-位于检查点后,gist 的所有者可通过单击 **Update gist(更新 gist)**保留更改。
-
-如果想要与未加入 Gist Playground 专用测试版的人员协作,请发送电子邮件至 [gist-playground@github.com](mailto:gist-playground@github.com) 联系我们,看看能否添加这些人员。
-
-### 报告漏洞和反馈
-我们很乐意聆听您关于 Gist Playground 以及如何让它变得更好的想法! 发送电子邮件至 [gist-playground@github.com](mailto:gist-playground@github.com),告诉我们您的任何想法、反馈或漏洞。
diff --git a/translations/zh-CN/content/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order.md b/translations/zh-CN/content/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order.md
deleted file mode 100644
index a55813559c61..000000000000
--- a/translations/zh-CN/content/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: 为什么我的提交顺序不正确?
-intro: 如果您通过 `git rebase` 或强制推送来重写提交历史记录,可能会发现打开拉取请求时提交顺序不正确。
-redirect_from:
- - /articles/why-are-my-commits-in-the-wrong-order
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-GitHub 强调将拉取请求视为讨论的空间。 其所有方面(评论、引用和提交)均按时间顺序显示。 [执行变基时](/articles/about-git-rebase)重写 Git 提交历史记录会更改时空连续体,这意味着提交可能不会按您预期的方式在 GitHub 界面中显示。
-
-如果想要按顺序查看提交,我们建议不要使用 `git rebase`。 不过请放心,尽管您看到的内容没有按时间顺序排列,但不会破坏任何内容!
diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code.md b/translations/zh-CN/content/github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code.md
deleted file mode 100644
index 5c0ac9cbe1cc..000000000000
--- a/translations/zh-CN/content/github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: 从 Visual Studio Code 连接到代码空间
-intro: '您可以将 {% data variables.product.prodname_vs_codespaces %} 扩展连接到您在 {% data variables.product.product_name %} 上的帐户,直接在 {% data variables.product.prodname_vscode %} 代码空间中开发。'
-product: '{% data reusables.gated-features.codespaces %}'
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.codespaces.release-stage %}
-
-### 将 {% data variables.product.prodname_vs_codespaces %} 扩展连接到您的 {% data variables.product.prodname_dotcom %} 帐户
-
-直接在 {% data variables.product.prodname_vscode %} 的代码空间中开发之前,您必须配置 {% data variables.product.prodname_vs_codespaces %} 扩展连接到您的 {% data variables.product.product_name %} 帐户。
-
-1. 使用 {% data variables.product.prodname_vs %} Marketplace 安装 [{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline) 扩展。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档中的[扩展 Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)。
-2. 在 {% data variables.product.prodname_vscode %} 中,从左侧边栏单击 Extensions(扩展)图标。 ![{% data variables.product.prodname_vscode %} 中的 Extensions(扩展)图标](/assets/images/help/codespaces/click-extensions-icon-vscode.png)
-3. 在 {% data variables.product.prodname_vs_codespaces %} 下面,单击 Manage(管理)图标,然后单击 **Extension Settings(扩展设置)**。 ![Extension Settings(扩展设置)选项](/assets/images/help/codespaces/select-extension-settings.png)
-4. 使用“Vsonline: Account Provider(Vsonline:帐户提供商)”下拉菜单,选择 {% data variables.product.prodname_dotcom %}。 ![设置帐户提供者为 {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/select-account-provider-vscode.png)
-{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-6. 如果尚未在标题中选择 {% data variables.product.prodname_codespaces %},请单击 **{% data variables.product.prodname_codespaces %}**。 ![{% data variables.product.prodname_codespaces %} 标头](/assets/images/help/codespaces/codespaces-header-vscode.png)
-7. 单击 **Sign in to view {% data variables.product.prodname_codespaces %}...(登录以查看 Codespaces...)**。 ![登录以查看 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
-8. 要授权 {% data variables.product.prodname_vscode %} 访问您在 {% data variables.product.product_name %} 上的帐户,请单击 **Allow(允许)**。
-9. 登录 {% data variables.product.product_name %} 以审批扩展。
-
-### 在 {% data variables.product.prodname_vscode %} 中打开代码空间
-
-将 {% data variables.product.product_name %} 帐户连接到 {% data variables.product.prodname_vs_codespaces %} 扩展后,您可以在 {% data variables.product.prodname_vscode %} 中的 {% data variables.product.product_name %} 上直接创建的代码空间中进行开发。
-
-{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. 在 Codespaces(代码空间)下,单击您要在其中开发的代码空间。
-3. 单击 Connect to Codespace(连接到代码空间)图标。 ![{% data variables.product.prodname_vscode %} 中的连接到代码空间图标](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages.md
deleted file mode 100644
index 6dcad5283d3b..000000000000
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: Configuring code scanning for compiled languages
-shortTitle: Configuring for compiled languages
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans code written in compiled languages for vulnerabilities and errors.'
-product: '{% data reusables.gated-features.code-scanning %}'
-permissions: '拥有仓库写入权限的人可配置仓库的 {% data variables.product.prodname_code_scanning %}。'
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.code-scanning.beta %}
-
-{% note %}
-
-**Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools.
-
-{% endnote %}
-
-### About {% data variables.product.prodname_code_scanning %} and compiled languages
-
-To enable {% data variables.product.prodname_code_scanning %} for your repository, you add to the repository a {% data variables.product.prodname_actions %} workflow which includes {% data variables.product.prodname_codeql %} analysis. 更多信息请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。
-
-{% data reusables.code-scanning.edit-workflow %}
-For more information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Configuring a workflow](/actions/configuring-and-managing-workflows/configuring-a-workflow)."
-
-### About autobuild for {% data variables.product.prodname_codeql %}
-
-{% data reusables.code-scanning.autobuild-compiled-languages %}
-
-{% note %}
-
-**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. 更多信息请参阅“[GitHub-hosted 运行器上安装的软件](/actions/reference/software-installed-on-github-hosted-runners)”。
-
-{% endnote %}
-
-#### C/C++
-
-| Supported system type | System name |
-| --------------------- | ----------------------------------------------------------- |
-| 操作系统 | Windows and Linux |
-| Build system | Autoconf, CMake, qmake, Meson, Waf, SCons, and Linux Kbuild |
-
-The behavior of the `autobuild` step varies according to the operating system that the extraction runs on. On Windows, the step has no default actions. On Linux, this step reviews the files present in the repository to determine the build system used:
-
-1. Look for a build system in the root directory.
-2. If none are found, search subdirectories for a unique directory with a build system for C/C++.
-3. Run an appropriate command to configure the system.
-
-#### C
-
-| Supported system type | System name |
-| --------------------- | ------------------------------------------ |
-| 操作系统 | Windows and Linux |
-| Build system | .NET and MSbuild, as well as build scripts |
-
-The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
-
-1. Invoke `dotnet build` on the solution (`.sln`) or project (`.csproj`) file closest to the root.
-2. Invoke `MSbuild` (Linux) or `MSBuild.exe` (Windows) on the solution or project file closest to the root. If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
-3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
-
-
-#### Java
-
-| Supported system type | System name |
-| --------------------- | ----------------------------------------- |
-| 操作系统 | Windows, macOS and Linux (no restriction) |
-| Build system | Gradle, Maven and Ant |
-
-The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
-
-1. Search for a build file in the root directory. Check for Gradle then Maven then Ant build files.
-2. Run the first build file found. If both Gradle and Maven files are present, the Gradle file is used.
-3. Otherwise, search for build files in direct subdirectories of the root directory. If only one subdirectory contains build files, run the first file identified in that subdirectory (using the same preference as for 1). If more than one subdirectory contains build files, report an error.
-
-### 添加编译语言的构建步骤
-
-{% data reusables.code-scanning.autobuild-add-build-steps %} For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)."
-
-After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. 您可以修改这些命令并添加更多命令来自定义构建过程。
-
-``` yaml
-- run: |
- make bootstrap
- make release
-```
-
-有关 `run` 关键词的更多信息,请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。
-
-You can also use a build matrix to update the workflow to build more than one compiled language, if this is the appropriate approach for your system and doesn't cause conflicts. For more information, see "[Configuring a build matrix](/actions/configuring-and-managing-workflows/configuring-a-workflow#configuring-a-build-matrix)."
-
-
-For example, the workflow below runs one job for C/C++ analysis, and another job for Java analysis.
-
-```yaml
-
-name: "Code Scanning - Action"
-
-on:
- pull_request:
- branches: [master]
- push:
- branches: [master]
-
-jobs:
- CodeQL-Build:
-
- strategy:
- fail-fast: false
- matrix:
- language: [ 'cpp', 'java']
-
- # CodeQL runs on ubuntu-latest, windows-latest, and macos-latest
- runs-on: ubuntu-latest
-
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
-
- # Initializes the CodeQL tools for scanning.
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: ${{ matrix.language }}
-
- # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
- # If this step fails, then you should remove it and run the build manually.
- - name: Autobuild
- uses: github/codeql-action/autobuild@v1
-
- - name: Perform CodeQL Analysis
- uses: github/codeql-action/analyze@v1
-```
-
-For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning)".
-
-If you added manual build steps for compiled languages or used a build matrix and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}.
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages.md
deleted file mode 100644
index c40d58784eb1..000000000000
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: Configuring the CodeQL action for compiled languages
-shortTitle: Configuring for compiled languages
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.product.prodname_codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
-product: '{% data reusables.gated-features.code-scanning %}'
-permissions: '拥有仓库写入权限的人可配置仓库的 {% data variables.product.prodname_code_scanning %}。'
-redirect_from:
- - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
-
-### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages
-
-To enable {% data variables.product.prodname_code_scanning %} for your repository, you add to the repository a {% data variables.product.prodname_actions %} workflow which includes {% data variables.product.prodname_codeql %} analysis. 更多信息请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。 For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。
-
-{% data reusables.code-scanning.edit-workflow %}
-For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Configuring a workflow](/actions/configuring-and-managing-workflows/configuring-a-workflow)."
-
-### About autobuild for {% data variables.product.prodname_codeql %}
-
-{% data reusables.code-scanning.autobuild-compiled-languages %}
-
-{% note %}
-
-**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. 更多信息请参阅“[GitHub-hosted 运行器上安装的软件](/actions/reference/software-installed-on-github-hosted-runners)”。
-
-{% endnote %}
-
-#### C/C++
-
-| Supported system type | System name |
-| --------------------- | ----------------------------------------------------------- |
-| 操作系统 | Windows and Linux |
-| Build system | Autoconf, CMake, qmake, Meson, Waf, SCons, and Linux Kbuild |
-
-The behavior of the `autobuild` step varies according to the operating system that the extraction runs on. On Windows, the step has no default actions. On Linux, this step reviews the files present in the repository to determine the build system used:
-
-1. Look for a build system in the root directory.
-2. If none are found, search subdirectories for a unique directory with a build system for C/C++.
-3. Run an appropriate command to configure the system.
-
-#### C
-
-| Supported system type | System name |
-| --------------------- | ------------------------------------------ |
-| 操作系统 | Windows and Linux |
-| Build system | .NET and MSbuild, as well as build scripts |
-
-The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
-
-1. Invoke `dotnet build` on the solution (`.sln`) or project (`.csproj`) file closest to the root.
-2. Invoke `MSbuild` (Linux) or `MSBuild.exe` (Windows) on the solution or project file closest to the root. If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
-3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
-
-#### Java
-
-| Supported system type | System name |
-| --------------------- | ----------------------------------------- |
-| 操作系统 | Windows, macOS and Linux (no restriction) |
-| Build system | Gradle, Maven and Ant |
-
-The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
-
-1. Search for a build file in the root directory. Check for Gradle then Maven then Ant build files.
-2. Run the first build file found. If both Gradle and Maven files are present, the Gradle file is used.
-3. Otherwise, search for build files in direct subdirectories of the root directory. If only one subdirectory contains build files, run the first file identified in that subdirectory (using the same preference as for 1). If more than one subdirectory contains build files, report an error.
-
-### 添加编译语言的构建步骤
-
-{% data reusables.code-scanning.autobuild-add-build-steps %} For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)."
-
-After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. 您可以修改这些命令并添加更多命令来自定义构建过程。
-
-``` yaml
-- run: |
- make bootstrap
- make release
-```
-
-有关 `run` 关键词的更多信息,请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。
-
-You can also use a build matrix to update the workflow to build more than one compiled language, if this is the appropriate approach for your system and doesn't cause conflicts. For more information, see "[Configuring a build matrix](/actions/configuring-and-managing-workflows/configuring-a-workflow#configuring-a-build-matrix)."
-
-
-For example, the workflow below runs one job for C/C++ analysis, and another job for Java analysis.
-
-```yaml
-
-name: "Code Scanning - Action"
-
-on:
- pull_request:
- branches: [master]
- push:
- branches: [master]
-
-jobs:
- CodeQL-Build:
-
- strategy:
- fail-fast: false
- matrix:
- language: [ 'cpp', 'java']
-
- # CodeQL runs on ubuntu-latest, windows-latest, and macos-latest
- runs-on: ubuntu-latest
-
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
-
- # Initializes the CodeQL tools for scanning.
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: ${{ matrix.language }}
-
- # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
- # If this step fails, then you should remove it and run the build manually.
- - name: Autobuild
- uses: github/codeql-action/autobuild@v1
-
- - name: Perform CodeQL Analysis
- uses: github/codeql-action/analyze@v1
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: ${% raw %}{{ matrix.language }}{% endraw %}
-
- # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
- # If this step fails, then you should remove it and run the build manually.
- - name: Autobuild
- uses: github/codeql-action/autobuild@v1
-
- - name: Perform CodeQL Analysis
- uses: github/codeql-action/analyze@v1
-```
-
-For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning)".
-
-If you added manual build steps for compiled languages or used a build matrix and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}.
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning.md
deleted file mode 100644
index c6030619e94b..000000000000
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: 启用代码扫描
-intro: '您可以对项目的仓库启用 {% data variables.product.prodname_code_scanning %}。'
-product: '{% data reusables.gated-features.code-scanning %}'
-permissions: '拥有仓库写入权限的人可启用仓库的 {% data variables.product.prodname_code_scanning %}。'
-redirect_from:
- - /github/managing-security-vulnerabilities/configuring-automated-code-scanning
-versions:
- free-pro-team: '*'
----
-
-{% data reusables.code-scanning.beta %}
-
-### 启用 {% data variables.product.prodname_code_scanning %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-3. 在“Code scanning(代码扫描)”右侧,单击 **Set up code scanning(设置代码扫描)**。 ![Security Overview(安全性概述)中"Code scanning(代码扫描)"右侧的"Set up code scanning(设置代码扫描)"按钮](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. 在“Get started with code scanning(开始代码扫描)”下,单击 **Set up this workflow(设置此工作流程)**。 !["Get started with code scanning(开始代码扫描)"标题下的"Set up this workflow(设置此工作流程)"按钮](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)
-5. (可选)自定义 {% data variables.product.prodname_code_scanning %} 如何扫描您的代码,编辑工作流程。 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)。”
-6. 使用 **Start commit(开始提交)**下拉菜单,并键入提交消息。 ![开始提交](/assets/images/help/repository/start-commit-commit-new-file.png)
-7. 选择您是想直接提交到默认分支,还是创建新分支并启动拉取请求。 ![选择提交位置](/assets/images/help/repository/start-commit-choose-where-to-commit.png)
-8. 单击 **Commit new file(提交新文件)**或 **Propose new file(提议新文件)**。
-
-在提交工作流程文件或创建拉取请求后,{% data variables.product.prodname_code_scanning %} 将根据您在工作流程文件中指定的频率分析代码。 如果您创建了拉取请求,则在您将拉取请求合并到仓库的默认分支之前,{% data variables.product.prodname_code_scanning %} 只会分析拉取请求主题分支上的代码。
-
-### 后续步骤
-
-在启用 {% data variables.product.prodname_code_scanning %} 后,您可以监控分析,查看结果,并进一步自定义如何扫描您的代码。
-
-- 您可以查看 {% data variables.product.prodname_code_scanning %} 的运行状态并获取已完成运行的通知。 更多信息请参阅“[管理工作流程运行](/actions/configuring-and-managing-workflows/managing-a-workflow-run)”和“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)”。
-- 扫描完成后,您可以查看已完成扫描的警报。 更多信息请参阅“[管理来自 {% data variables.product.prodname_code_scanning %} 的警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning)”。
-- 您可以自定义 {% data variables.product.prodname_code_scanning %} 如何扫描您的仓库中的代码。 更多信息请参阅“[配置代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)”。
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning.md
deleted file mode 100644
index 3c4acd7777a9..000000000000
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: 管理来自代码扫描的警报
-shortTitle: 管理警报
-intro: 您可以查看、修复和关闭项目代码中潜在漏洞或错误的警报。
-product: '{% data reusables.gated-features.code-scanning %}'
-permissions: '拥有仓库写入权限的人可管理仓库的 {% data variables.product.prodname_code_scanning %} 警报。'
-redirect_from:
- - /github/managing-security-vulnerabilities/managing-alerts-from-automated-code-scanning
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning %}
-
-### 关于 {% data variables.product.prodname_code_scanning %} 中的警报
-
-After you enable {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dotcom %} displays {% data variables.product.prodname_code_scanning %} alerts in your repository. 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。
-
-Each alert highlights a problem with the code and the name of the tool that identified it. 您可以看到触发警报的代码行以及警报的属性,例如问题的严重程度和性质。 警报还会告知该问题第一次被引入的时间。 For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
-
-![来自 {% data variables.product.prodname_code_scanning %} 的警报示例](/assets/images/help/repository/code-scanning-alert.png)
-
-如果不执行警报建议的操作,可以手动关闭警报。 例如,您可以关闭用于测试的代码的警报,或者您认为是误报的警报。 如果修复编码错误的成本大于改进代码的潜在利益,您可能还希望关闭警报。
-
-默认情况下,{% data variables.product.prodname_dotcom %} 显示默认分支和任何受保护分支的警报。 您可以对警报列表进行排序和过滤,只查看您感兴趣的警报。
-
-您可以查看拉取请求中引入的警报,并立即采取措施。 当 {% data variables.product.prodname_code_scanning %} 在拉取请求中找到漏洞或错误时,{% data variables.product.prodname_dotcom %} 会在时间线中显示注释,并显示拉取请求的差异视图。
-
-If you enable {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
-
-当 {% data variables.product.prodname_code_scanning %} 报告数据流警报时,{% data variables.product.prodname_dotcom %} 将显示数据在代码中如何移动。 {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %} {% data reusables.code-scanning.get-started-uploading-third-party-data %}
-
-If you scan your code using a third-party tool or scan your code with custom {% data variables.product.prodname_codeql %} queries, {% data variables.product.prodname_dotcom %} will only use the supported SARIF 2.1.0 properties to display alerts. 第三方工具或自定义查询的结果可能不包括在使用 {% data variables.product.company_short %} 默认 {% data variables.product.prodname_codeql %} 查询扫描代码时看到的所有属性。 更多信息请参阅“[{% data variables.product.prodname_code_scanning %} 的 SARIF 支持](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)”。
-
-### 查看警报
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% data reusables.code-scanning.click-alert-in-list %}
-5. (可选)如果警报突出显示数据流的问题,单击 **Show paths(显示路径)**可查看数据的路径。 ![数据流警报示例](/assets/images/help/repository/code-scanning-show-paths.png)
-
-### 关闭警报
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% data reusables.code-scanning.click-alert-in-list %}
-5. 使用“Close(关闭)”下拉菜单,单击关闭警报的原因。 ![选择通过 "Close(关闭)"下拉菜单关闭警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-### 延伸阅读
-
-- "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)"
-- "[{% data variables.product.prodname_code_scanning_capc %} API](/v3/code-scanning)"
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning.md
deleted file mode 100644
index ba0f31a05cf0..000000000000
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: 管理代码扫描的结果
-shortTitle: 管理结果
-intro: '您可以查看、分类、理解和解决 {% data variables.product.prodname_code_scanning %} 找到的漏洞和错误。'
-mapTopic: true
-versions:
- free-pro-team: '*'
----
-
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning.md
deleted file mode 100644
index 36819579483d..000000000000
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-title: Troubleshooting code scanning
-shortTitle: Troubleshooting
-intro: 'You can see tips to resolve common issues with {% data variables.product.prodname_code_scanning %}.'
-product: '{% data reusables.gated-features.code-scanning %}'
-versions:
- free-pro-team: '*'
- enterprise-server: '>=2.22'
----
-
-{% data reusables.code-scanning.beta %}
-{% data reusables.code-scanning.enterprise-enable-code-scanning %}
-
-### Automatic build for a compiled language fails
-
-If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps.
-
-- Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-- If the repository for your project contains code in a specific language that does not build, disable automatic language detection in your {% data variables.product.prodname_code_scanning %} workflow and specify only the languages you want to build. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#overriding-automatic-language-detection)."
-
-### No code found during the build
-
-If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to trace your code. Several reasons can explain such a failure:
-
-1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by updating the `init` step to specify the supported languages that are present in your repository. For example, the following configuration will analyze only Go, and JavaScript.
-
- ```yaml
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: go, javascript # Other options are csharp, python, cpp, java
- ```
-2. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually. For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-3. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis.
-4. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis.
-5. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are certain configuration options like running your build process in a container, if you're building using a distributed build system external to {% data variables.product.prodname_actions %} using a daemon process, or if {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
- 1. For C# projects using either `dotnet build` or `msbuild` which target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later.
-
- For example, the following configuration will pass the flag during the first build step.
-
- ```yaml
- - run: |
- dotnet build /p:UseSharedCompilation=false
- ```
- 2. If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
-
-For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-
-### Portions of my repository were not analyzed using `autobuild`
-
-The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. Alternatively, if more than one compiled language is present in your repository and you want {% data variables.product.prodname_code_scanning %} to analyze all these compiled languages, you can use a build matrix in your workflow. {% if currentVersion ver_gt "enterprise-server@2.21" %}To use a build matrix, you should make sure that {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location_enterprise %}. {% endif %}For more information, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)" and
-"[Configuring the {% data variables.product.prodname_codeql %} action for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-
-### Error: "Server error"
-
-If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
-
-### Error: "Out of disk" or "Out of memory"
-
-On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem.
-{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
-
-### The build takes too long
-
-If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time.
-
-#### Increase the memory or cores
-
-If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners.
-
-#### Use matrix builds to parallelize the analysis
-
-By default, {% data variables.product.prodname_codeql %} performs analysis of each language sequentially, which can impact performance, especially for repositories with more than one language. You can speed analysis up by using a build matrix that splits the analysis by language. {% if currentVersion ver_gt "enterprise-server@2.21" %}To use a build matrix, you should make sure that {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location_enterprise %}. {% endif %}For more information, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)."
-
-For example, the workflow below will be run with one job for JavaScript analysis, and another job for Go analysis.
-
-```yaml
-
-name: "Code Scanning - Action"
-
-on:
- pull_request:
- branches: [main]
- push:
- branches: [main]
-
-jobs:
- CodeQL-Build:
-
- strategy:
- fail-fast: false
- matrix:
- language: [ 'go', 'javascript']
-
- # CodeQL runs on ubuntu-latest, windows-latest, and macos-latest
- runs-on: ubuntu-latest
-
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
-
- # Initializes the CodeQL tools for scanning.
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: ${{ matrix.language }}
-
- # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
- # If this step fails, then you should remove it and run the build manually (see below).
- - name: Autobuild
- uses: github/codeql-action/autobuild@v1
-
- - name: Perform CodeQL Analysis
- uses: github/codeql-action/analyze@v1
-```
-
-#### Reduce the amount of code being analyzed in a single workflow
-
-Analysis time is typically proportional to the amount of code being analyzed. You can reduce the analysis time by reducing the amount of code being analyzed at once, for example, by excluding test code, or breaking analysis into multiple workflows that analyze only a subset of your code at a time.
-
-For compiled languages like Java, C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build only the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-
-For interpreted languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without a specific build, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#specifying-directories-to-scan)."
-
-If you split your analysis into multiple workflows as described above, we still recommend that you have at least one workflow which runs on a `schedule` which analyzes all of the code in your repository. Because {% data variables.product.prodname_codeql %} analyzes data flows between components, some complex security behaviors may only be detected on a complete build.
-
-#### Run only during a `schedule` event
-
-If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies.md
deleted file mode 100644
index 75806f63761e..000000000000
--- a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: 关于对有漏洞的依赖项发出安全警报
-intro: '当我们检测到影响到您的仓库的漏洞时,{% data variables.product.product_name %} 会发出安全警报。'
-redirect_from:
- - /articles/about-security-alerts-for-vulnerable-dependencies
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### 关于安全漏洞
-
-{% data reusables.repositories.a-vulnerability-is %}根据漏洞的严重性和项目使用依赖项的方式,漏洞可能对项目或者使用项目的人员造成一系列问题。 您可以跟踪并解决 {% data variables.product.product_name %} 仓库中某些依赖项类型的漏洞。
-
-如果 {% data variables.product.prodname_dotcom %} 从您的仓库依赖关系图中某个依赖项的 {% data variables.product.prodname_advisory_database %} 或 [WhiteSource](https://www.whitesourcesoftware.com/GitHubSecurityAlerts) 中检测到漏洞,我们会向您发送安全警报。 有关 {% data variables.product.prodname_advisory_database %} 的更多信息,请参阅“浏览 {% data variables.product.prodname_advisory_database %} 中的安全漏洞”。
-
-{% if currentVersion == "free-pro-team@latest" %}
-### 漏洞依赖项的警报和自动安全更新
-{% else %}
-### 对有漏洞的依赖项发出安全警报
-{% endif %}
-
-当 GitHub Advisory Database 中加入新的漏洞时,我们会识别使用受影响依赖项版本的{% if currentVersion == "free-pro-team@latest" %}公共{% endif %}仓库{% if currentVersion == "free-pro-team@latest" %}(和已经选择加入漏洞检测的私有仓库){% endif %}{% if currentVersion == "free-pro-team@latest" %},发送安全警报给仓库维护员,然后生成自动安全更新{% else %}并发送安全警报给仓库维护员{% endif %}。
-
-每个安全警报都包含严重等级{% if currentVersion == "free-pro-team@latest" %}、项目中受影响文件的链接、其中包含可解决漏洞的自动安全更新的拉取请求链接{% else %},以及项目中受影响文件的链接{% endif %}。 可用时,警报会包含有关漏洞的更多详细信息。
-
-您可以在{% if currentVersion == "free-pro-team@latest" %}仓库的 Alerts(警报)选项卡或{% endif %}仓库的依赖项图表{% if currentVersion == "free-pro-team@latest" %}中查看影响特定项目的所有警报。更多信息请参阅“[查看和更新仓库中的漏洞依赖项](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)”。{% endif %}
-
-默认情况下,我们会向具有受影响仓库管理员权限的人员发送安全警报。 {% data variables.product.product_name %} 从不公开披露在任何仓库中发现的漏洞。{% if currentVersion == "free-pro-team@latest" %} 您也可以对操作组织拥有的仓库的其他人或团队启用安全警报。 更多信息请参阅“[管理组织仓库中漏洞依赖项的警报](/articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories)”。{% endif %}
-
-{% data reusables.repositories.enable-security-alerts %}
-{% if currentVersion == "free-pro-team@latest" %}
-自动安全更新将有漏洞的依赖项更新为可解决该漏洞的最低版本。 自动安全更新会在使用依赖项图表和安全警报的仓库中自动启用,但您可以选择禁用自动拉取请求,改为手动生成安全更新。 更多信息请参阅“[配置自动安全更新](/github/managing-security-vulnerabilities/configuring-automated-security-updates)”。
-
-{% data variables.product.prodname_dotcom %} 默认会检查_公共_仓库中有漏洞的依赖项并发出警报。 要接收_私有_仓库中漏洞依赖项的安全警报,该仓库的所有者或具有管理员权限的人员必须在仓库中启用依赖项图表和安全警报。 更多信息请参阅“[选择加入或退出私有仓库的数据使用](/articles/opting-into-or-out-of-data-use-for-your-private-repository)”。
-{% endif %}
-
-有关 {% data variables.product.product_name %} 可以检测漏洞和依赖项的受支持语言列表,请参阅“[列出仓库所依赖的包](/articles/listing-the-packages-that-a-repository-depends-on)”。
-
-{% warning %}
-
-**注**:{% data variables.product.product_name %} 的安全功能(如安全警报)并不要求捕获所有漏洞。 虽然我们一直在努力更新漏洞数据库,向您提醒最新的信息,但我们无法捕获一切或在保证的时间范围内向您警示已知的漏洞。 这些功能不是要替代人工检查每个依赖项的潜在漏洞或任何其他问题,并且我们建议在必要时咨询安全服务或全面检查漏洞。
-
-{% endwarning %}
-
-### 配置安全警报通知
-
-默认情况下,您将通过电子邮件收到安全警报{% if currentVersion == "free-pro-team@latest" %},这些警报将按特定漏洞分组{% endif %}。 您也可以选择在每周电子邮件(摘要列出最多 10 个仓库的警报)、web 通知或 {% data variables.product.product_name %} 用户界面中接收安全警报。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#security-alert-options){% else %}“[选择通知递送方式](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}”。
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %}更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}”。{% endif %}
-
-### 延伸阅读
-
-{% if currentVersion == "free-pro-team@latest" %}- "[配置自动安全更新](/github/managing-security-vulnerabilities/configuring-automated-security-updates)"
-- "[查看和更新仓库中的漏洞依赖项](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[了解 {% data variables.product.product_name %} 如何使用和保护数据](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
-- MITRE 的[“漏洞”定义](https://cve.mitre.org/about/terminology.html#vulnerability)
diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-automated-security-updates.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-automated-security-updates.md
deleted file mode 100644
index 0d20644a887b..000000000000
--- a/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-automated-security-updates.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: 配置自动安全更新
-intro: 您可以使用自动或手动拉取请求轻松更新易受攻击的依赖项。
-redirect_from:
- - /articles/configuring-automated-security-fixes
- - /github/managing-security-vulnerabilities/configuring-automated-security-fixes
-versions:
- free-pro-team: '*'
----
-
-### 关于自动安全更新
-
-您可以为任何使用安全警报和依赖关系图的仓库启用自动安全更新。 您可以对个别仓库或所有由您的用户帐户或组织拥有的仓库禁用自动安全更新。
-
-收到有关仓库中易受攻击依赖项的安全警报时,您可以使用与安全警报对应的拉取请求中的自动安全更新来解决漏洞。 使用依赖关系图的仓库中提供自动安全更新功能。 默认情况下,{% data variables.product.prodname_dotcom %} 会自动在您的仓库中创建拉取请求,以将易受攻击的依赖项升级到避免漏洞所需的最低安全版本。 如果您愿意,可以禁用自动拉取请求,只在需要时选择手动创建拉取请求以升级依赖项。
-
-自动安全请求包含快速安全地审查并将提议的修复合并到项目中所需的一切,包括有关漏洞的信息,如版本说明、更改日志条目和提交详细信息。
-
-自动安全更新由 Dependabot 代表 {% data variables.product.prodname_dotcom %} 开启。 Dependabot {% data variables.product.prodname_github_app %} 会自动安装在每个启用了自动安全更新的仓库中。
-
-有权访问仓库安全警报的人可以看到指向相关安全警报的链接,但有权访问拉取请求的其他人无法看到拉取请求要解决的漏洞。
-
-当您合并包含自动安全更新的拉取请求时,仓库的相应安全警报将被标记为已解决。
-
-{% note %}
-
-**注:**自动安全更新只解决安全漏洞。 自动安全更新的目标不是解决托管在私有仓库中的私有注册表或包中的漏洞。
-
-{% endnote %}
-
-### 支持的仓库
-
-{% data variables.product.prodname_dotcom %} 自动为符合这些要求的每个仓库启用自动安全更新。
-
-{% note %}
-
-**注**:对于 2019 年 11 月之前创建的仓库,如果仓库满足以下条件,并且自 2019 年 5 月 23 日以来至少收到过一次推送,{% data variables.product.prodname_dotcom %} 已自动启用自动安全更新。
-
-{% endnote %}
-
-| 要求 | 更多信息 |
-| ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 存储库不是复刻 | "[关于复刻](/github/collaborating-with-issues-and-pull-requests/about-forks)" |
-| 仓库未存档 | "[存档仓库](/github/creating-cloning-and-archiving-repositories/archiving-repositories)" |
-| 仓库是公共的,或者仓库是私有的但您在仓库的设置中启用了 {% data variables.product.prodname_dotcom %} 只读分析、依赖关系图和漏洞警报。 | "[选择加入私有仓库的数据使用](/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository#opting-into-data-use-for-your-private-repository)" |
-| 仓库包含软件包生态系统中 {% data variables.product.prodname_dotcom %} 支持的依赖项清单文件 | "[支持的软件包生态系统](/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on#supported-package-ecosystems)" |
-| 未对仓库禁用自动安全更新 | "[管理仓库的自动安全更新](#managing-automated-security-updates-for-your-repository)" |
-| 仓库尚未使用集成进行依赖项管理 | “[关于集成](/github/customizing-your-github-workflow/about-integrations)” |
-
-如果未为存储库启用自动安全更新,而您不知道原因,您可以 [联系支持](https://support.github.com/contact)。
-
-### 关于兼容性分数
-
-自动安全更新还包括兼容性分数,以便您了解更新漏洞是否可能导致对项目的重大更改。 我们从已生成特定自动安全更新的公共仓库中查看此前通过的 CI 测试,以了解更新是否会导致测试失败。 更新的兼容性分数是在依赖项的相关版本之间进行更新时,CI 运行被视为通过的百分比。
-
-### 管理仓库的自动安全更新
-
-您可以对个别仓库启用或禁用自动安全更新。
-
-自动更新安全需要特定的仓库设置。 更多信息请参阅“[支持的仓库](#supported-repositories)”。
-
-{% data reusables.repositories.you-can-enable-or-disable-security-features %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-4. 在警报列表的上方,使用下拉菜单并选择或取消选择 **Automated security updates(自动安全更新)**。 ![包含启用自动安全更新的选项的下拉菜单](/assets/images/help/repository/enable-automated-security-updates-drop-down.png)
-
-### 管理用户帐户的自动安全更新
-
-You can disable automated security updates for all repositories owned by your user account. If you do, you can still enable automated security updates for individual repositories owned by your user account.
-
-{% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.security %}
-{% data reusables.repositories.opt-out-automated-security-updates %}
-
-### 管理组织的自动安全更新
-
-Organization owners can disable automated security updates for all repositories owned by the organization. If you do, anyone with admin permissions to an individual repository owned by the organization can still enable automated security updates on that repository.
-
-{% data reusables.repositories.you-can-enable-or-disable-security-features %}
-
-{% data reusables.profile.access_profile %}
-{% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.security %}
-{% data reusables.repositories.opt-out-automated-security-updates %}
-
-### 延伸阅读
-
-- “[关于易受攻击依赖项的安全警报](/articles/about-security-alerts-for-vulnerable-dependencies)”
-- "[选择加入私有仓库的数据使用](/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository#opting-into-data-use-for-your-private-repository)"
-- "[支持的软件包生态系统](/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on#supported-package-ecosystems)"
diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization.md
deleted file mode 100644
index bf021b08add1..000000000000
--- a/translations/zh-CN/content/github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: 管理组织中漏洞依赖项的警报
-intro: '当我们检测到组织仓库中有漏洞的依赖项时,组织所有者和仓库管理员会收到 {% data variables.product.prodname_dependabot_alerts %}。 您可以指定其他具有写入权限的组织成员或团队也接收漏洞依赖项的警报。'
-redirect_from:
- - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories/
- - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories/
- - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization
-versions:
- free-pro-team: '*'
----
-
-{% if currentVersion == "free-pro-team@latest" %}
-{% data reusables.repositories.you-can-manage-access-to-security-alerts %}
-{% endif %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. 在左侧边栏中,单击 **Dependabot alerts(Dependabot 警报)**。 ![设置侧边栏中的 Dependabot 警报选项卡](/assets/images/help/settings/settings-sidebar-dependabot-alerts.png)
-4. 输入您希望在 {% data variables.product.product_name %} 检测到漏洞依赖项时接收 {% data variables.product.prodname_dependabot_alerts %}的个人或团队名称,然后单击其用户名或团队名称以选中。
-5. 在选择您希望接收 {% data variables.product.prodname_dependabot_alerts %}的所有人员或团队后,单击 **Save changes(保存更改)**。
-
-### 延伸阅读
-
-- “[关于有易受攻击依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”
-- "[查看和更新仓库中的漏洞依赖项](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- “[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”
diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-code-for-exact-matches.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-code-for-exact-matches.md
deleted file mode 100644
index 2df2614aec99..000000000000
--- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-code-for-exact-matches.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: 搜索精确匹配的代码
-intro: '您可以在 {% data variables.product.prodname_dotcom %} 上搜索仓库中精确匹配的代码。'
-redirect_from:
- - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches
-permissions: People with read permissions to a repository can search the repository's files for exact matches.
-versions:
- free-pro-team: '*'
----
-
-{% note %}
-
-{% data reusables.search.exact-match-beta %}要申请访问测试版,请[加入等待列表](https://github.com/features/code-search-exact-match/signup)。
-
-{% endnote %}
-
-### 关于搜索精确匹配的代码
-
-{% data reusables.search.exact-match %}
-
-默认情况下,搜索精确匹配项区分大小写和符号,不包括部分匹配或规范化语法。 例如,搜索 `let ReactDOM*` 只会返回 `let ReactDOM*`。
-
-### 搜索精确匹配的代码
-
-{% note %}
-
-对于测试版,在仓库中搜索精确匹配的文件只支持编制了索引的仓库。
-
-{% endnote %}
-
-{% data reusables.repositories.navigate-to-repo %}
-2. In the search field, type the string you'd like to find. ![Exact match search string](/assets/images/help/search/exact-match-search-string.png)
-3. Optionally, click the **Options** drop-down to narrow your search. ![Exact match search Options drop-down](/assets/images/help/search/exact-match-options.png)
-4. Press Enter or Return on your keyboard.
-5. 在结果列表中,单击文件。
-
-### 延伸阅读
-
-- “[搜索代码](/github/searching-for-information-on-github/searching-code)”
-- "[在 {% data variables.product.product_name %} 上导航代码](/github/managing-files-in-a-repository/navigating-code-on-github)"
diff --git a/translations/zh-CN/content/github/site-policy/github-enterprise-cloud-addendum.md b/translations/zh-CN/content/github/site-policy/github-enterprise-cloud-addendum.md
deleted file mode 100644
index 0a0f029bc6db..000000000000
--- a/translations/zh-CN/content/github/site-policy/github-enterprise-cloud-addendum.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: GitHub 企业云附录
-redirect_from:
- - /github-business-cloud-addendum/
- - /articles/github-enterprise-cloud-addendum
-versions:
- free-pro-team: '*'
----
-
-这些条款是 GitHub Enterprise Cloud 的附加条款(“Enterprise Cloud 条款)。 在这些 Enterprise Cloud 中未定义的任何大写术语将采用[服务条款](/articles/github-terms-of-service/)或[公司服务条款](/articles/github-corporate-terms-of-service/)中的定义。 同意这些 Enterprise Cloud 条款,即表示您也同意服务条款,具体取决于您拥有的帐户类型。
-
-Enterprise Cloud 包括一个组织帐户、SAML 单点登录、访问权限配置以及 8 小时响应时间的 24/5 支持。 此功能和服务列表并不详尽,可能会不时更新。 更多信息请参阅 [GitHub 定价页面](https://github.com/pricing)。
-
-### 定义:
-- 活跃用户:在中断时尝试访问我们服务的用户。
-- 客户:从 GitHub 购买 Enterprise Cloud 的个人或实体。
-- 合格用户:通过将其个人 GitHub 帐户与客户 Enterprise Cloud 帐户相关联,指定为客户 Enterprise Cloud 组织之成员的个人。
-- 基本服务:GitHub 核心版本控制功能必要的服务,这些功能和服务包括创建、复刻和克隆仓库;创建、提交和合并分支;创建、审查和合并拉取请求;以及 web、API 和 Git 客户端连接到核心 Git 工作流程。 下面是未包含的外围功能和服务示例:web 挂钩、Gist、页面和电子邮件通知。
-- 中断:影响 50% 以上活跃用户的基本服务中断。
-- 服务积分:我们可能返还给合格帐户的美元信用,计算方式如下所述。
-
-### Enterprise Cloud 正常运行时间 SLA
-
-计划的优势:
-- 我们保证该服务的季度正常运行时间达到 99.95%。 这表示断电对 GitHub 基本服务的中断不会影响超过 50% 的活跃用户,且时间不超过季度的 .05%。
-- 如果未达到我们保证的 99.95% 的季度正常运行时间,我们可能会向客户发放服务积分。
-
-我们如何计算正常运行时间?
-- 我们的正常运行时间计算基于通过 web、API 和 Git 客户端接口成功送达服务请求的百分比。
-
-我们的正常运行时间保证不包括哪些情况? 因以下原因造成的中断:
-- 客户的行为、疏忽或滥用服务,包括违反服务条款。
-- 您的互联网连接故障
-- 超出我们合理控制范围的因素,包括互联网接入问题、不可抗力事件和第三方服务或技术问题
-- 您的设备、服务或其他技术问题
-
-什么是正常运行时间服务积分,如何确定我是否有积分,以及如何兑换积分?
-- 如果 GitHub 的季度正常运行时间百分比掉到我们保证的 99.95% 以下,则客户有权获得服务积分,该积分等于超过季度正常运行时间保证的中断时间之付费金额的 25 倍。 正常运行时间服务积分在每个季度结束时计算,只能在申请后授予。
-- 要了解 GitHub 的正常运行时间百分比,您可在每个季度结束时索取正常运行时间报告。
-- 要获得正常运行时间服务积分,帐户所有者或帐单管理员必须在每个季度结束后三十 (30) 天内代表客户发送书面申请。 正常运行时间服务积分不能积攒。 正常运行时间服务积分被授予后,会自动应用到客户的下一张帐单。 书面申请应发送至 {% data variables.contact.contact_support %}。
-
-**免责声明和责任限制:**GitHub 的[状态页面](https://www.githubstatus.com/)未连接到此正常运行时间 SLA,不能出于计算正常运行时间服务积分的目的准确呈现 GitHub 的正常运行时间。 每个季度的服务积分最高限额为 30 天的付费服务金额。 如果 GitHub 未能履行本附录所规定的任何正常运行时间义务,服务积分是对客户唯一的补救措施。
diff --git a/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository.md b/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository.md
deleted file mode 100644
index cb8eebbac1b6..000000000000
--- a/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: 选择加入或退出私有仓库的数据使用
-intro: '为帮助 {% data variables.product.product_name %} 连接到相关的工具、人员、项目和信息,您可以选择加入私有仓库的数据使用。 如已选择加入私有仓库的数据使用,但不再希望 {% data variables.product.product_name %} 使用您的数据,您可以选择退出。'
-redirect_from:
- - /articles/opting-into-or-out-of-data-use-for-your-private-repository
-versions:
- free-pro-team: '*'
----
-
-### About data use for your private repository
-
-选择加入私有仓库的数据使用后,您可以访问依赖项图,从中可以跟踪仓库的依赖项,在 {% data variables.product.product_name %} 检测到漏洞依赖项时接收安全警报。 更多信息请参阅“[关于依赖项漏洞的安全警报](/articles/about-security-alerts-for-vulnerable-dependencies)”。
-
-{% data reusables.repositories.you-can-enable-or-disable-security-features %}
-
-### 选择加入私有仓库的数据使用
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. 在 "Data services"(数据服务)下,选中 **Allow {% data variables.product.prodname_dotcom %} to perform read-only analysis of this repository(允许站点执行此仓库的只读分析)**。 ![允许 {% data variables.product.prodname_dotcom %} 对此仓库执行只读分析的复选框](/assets/images/help/repository/private-repo-data-use-opt-in.png)
-4. (可选)选中要为其启用数据使用的任何其他服务旁边的复选框。 ![自带复选框的其他服务列表](/assets/images/help/repository/private-repo-data-use-additional-services.png)
-
-### 选择退出私有仓库的数据使用
-
-{% tip %}
-
-**提示:**要选择退出特定服务的数据使用,请取消选中服务旁边的复选框。
-
-{% endtip %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. 在 "Data services"(数据服务)下,取消选中 **Allow {% data variables.product.prodname_dotcom %} to perform read-only analysis of this repository(允许站点执行此仓库的只读分析)**。 ![禁止 {% data variables.product.prodname_dotcom %} 对此仓库执行只读分析的复选框](/assets/images/help/repository/private-repo-data-use-opt-out.png)
-
-### 延伸阅读
-
-- "[关于 {% data variables.product.prodname_dotcom %} 对数据的使用](/articles/about-github-s-use-of-your-data)"
-- "[查看并更新仓库中有漏洞的依赖项](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)
-- "[管理组织仓库中漏洞依赖项的警报](/articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories)"
diff --git a/translations/zh-CN/content/github/using-git/changing-author-info.md b/translations/zh-CN/content/github/using-git/changing-author-info.md
deleted file mode 100644
index 8e144ec750a6..000000000000
--- a/translations/zh-CN/content/github/using-git/changing-author-info.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: 更改作者信息
-redirect_from:
- - /change-author-info/
- - /changing-author-info/
- - /articles/changing-author-info
-intro: 要更改现有提交中记录的名称和/或电子邮件地址,您必须重写 Git 仓库的整个历史记录。
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-{% warning %}
-
-**警告**:此操作对仓库的历史记录具有破坏性。 如果您正与其他人在仓库上协作,重写已发布的历史记录被视为不良做法。 应该只在紧急情况下才这样做。
-
-{% endwarning %}
-
-### 使用脚本更改仓库的 Git 历史记录
-
-我们创建了一个用于更改任何提交的脚本,可将此前在作者或提交者字段中填写的旧电子邮件地址更改为正确的名称和电子邮件地址。
-
-{% tip %}
-
-**注**:运行此脚本会重写所有仓库协作者的历史记录。 完成这些步骤后,任何拥有复刻或克隆的人都必须获取重写的历史记录,并将任何本地更改变基为重写的历史记录。
-
-{% endtip %}
-
-运行此脚本之前,您需要:
-
-* 显示在要更改的作者/提交者字段中的旧电子邮件地址
-* 要将此类提交归因于的正确名称和电子邮件地址
-
-{% data reusables.command_line.open_the_multi_os_terminal %}
-2. 为仓库创建一个全新的裸克隆:
- ```shell
- git clone --bare https://{% data variables.command_line.codeblock %}/user/repo.git
- cd repo.git
- ```
-3. 复制并粘贴脚本,根据您收集的信息替换以下变量:
- * `OLD_EMAIL`
- * `CORRECT_NAME`
- * `CORRECT_EMAIL`
-
- ```shell
- #!/bin/sh
-
- git filter-branch --env-filter '
-
- OLD_EMAIL="your-old-email@example.com"
- CORRECT_NAME="Your Correct Name"
- CORRECT_EMAIL="your-correct-email@example.com"
-
- if [ "$GIT_COMMITTER_EMAIL" = "$OLD_EMAIL" ]
- then
- export GIT_COMMITTER_NAME="$CORRECT_NAME"
- export GIT_COMMITTER_EMAIL="$CORRECT_EMAIL"
- fi
- if [ "$GIT_AUTHOR_EMAIL" = "$OLD_EMAIL" ]
- then
- export GIT_AUTHOR_NAME="$CORRECT_NAME"
- export GIT_AUTHOR_EMAIL="$CORRECT_EMAIL"
- fi
- ' --tag-name-filter cat -- --branches --tags
- ```
-
-4. 按 **Enter** 键以运行脚本。
-5. 审查新的 Git 历史记录以查找错误。
-6. 将更正的历史记录推送到 {% data variables.product.product_name %}:
- ```shell
- git push --force --tags origin 'refs/heads/*'
- ```
-7. 清理临时克隆:
- ```shell
- cd ..
- rm -rf repo.git
- ```
diff --git a/translations/zh-CN/content/github/using-git/updating-credentials-from-the-osx-keychain.md b/translations/zh-CN/content/github/using-git/updating-credentials-from-the-osx-keychain.md
deleted file mode 100644
index 7a94324612e3..000000000000
--- a/translations/zh-CN/content/github/using-git/updating-credentials-from-the-osx-keychain.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: 更新 OSX 密钥链中的凭据
-intro: '如果在 {% data variables.product.product_name %} 上更改您的用户名、密码或个人访问令牌,您需要在 "git-credit al-osxkeychain" 小助手中更新您保存的凭据。'
-redirect_from:
- - /articles/updating-credentials-from-the-osx-keychain
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-{% data reusables.user_settings.password-authentication-deprecation %}
-
-### 通过 Keychain Access 更新凭据
-
-1. 在 Finder 中,搜索 **Keychain Access** 应用程序。 ![Spotlight 搜索栏](/assets/images/help/setup/keychain-access.png)
-2. 在 Keychain Access 中,搜索 **{% data variables.command_line.backticks %}**。
-3. 查找 `{% data variables.command_line.backticks %}` 的“互联网密码”条目。 ![密钥链中的 GitHub 密码条目](/assets/images/help/setup/keychain-entry.png)
-4. 相应地编辑或删除该条目。
-
-### 通过命令行删除凭据
-
-通过命令行,您可以使用凭据小助手直接擦除密钥链条目。
-
-为此,请输入以下命令:
-
-```shell
-$ git credential-osxkeychain erase
-host={% data variables.command_line.codeblock %}
-protocol=https
-> [Press Return]
-```
-
-如果成功,则不会打印出任何内容。 要测试其是否有效,请尝试并克隆 {% data variables.product.product_location %} 仓库。 如果提示您输入密码,则该密钥链条目已删除。
-
-### 延伸阅读
-
-- “[在 Git 中缓存您的 {% data variables.product.prodname_dotcom %} 凭据](/github/using-git/caching-your-github-credentials-in-git/)”
diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository.md
deleted file mode 100644
index f9e8dc3a9ffc..000000000000
--- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Exploring the dependencies and dependents of a repository
-intro: 'Using the dependency graph, you can see the packages your project depends on and the repositories that depend on it. In addition, you can see any vulnerabilities detected in its dependencies.'
-redirect_from:
- - /articles/listing-the-packages-that-a-repository-depends-on
- - /github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on
- - /articles/listing-the-projects-that-depend-on-a-repository
- - /github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### Viewing the dependency graph
-
-{% data reusables.repositories.enable-security-alerts %}
-
-The dependency graph has tabs that show the dependencies and dependents of your repository. For information about how these views are populated and which ecosystems are supported, see "[About the dependency graph](about-the-dependency-graph)."
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}
-4. Optionally, under "Dependency graph", click **Dependents**. ![依赖项图中的依赖项选项卡](/assets/images/help/graphs/dependency-graph-dependents-tab.png)
-
-#### Dependencies view
-
-Dependencies are grouped by ecosystem. You can expand a dependency to view its dependencies. For dependencies hosted on {% data variables.product.product_name %}, you can also click a dependency to view the repository. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}.
-
-![依赖关系图](/assets/images/help/graphs/dependencies_graph.png)
-
-#### Dependents view
-
-For public repositories, the dependents view shows how the repository is used by other repositories. To show only the repositories that contain a library in a package manager, click **NUMBER Packages** immediately above the list of dependent repositories. The dependent counts are approximate and may not always match the dependents listed.
-
-![从属者图](/assets/images/help/graphs/dependents_graph.png)
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Enabling and disabling the dependency graph for a private repository
-
-Repository administrators can enable or disable the dependency graph for private repositories.
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Read the message about granting {% data variables.product.product_name %} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**. !["Enable" button for the dependency graph](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the Security & analysis tab.
-{% endif %}
-
-### 依赖项图疑难排解
-
-If your dependency graph is empty, there may be a problem with the file containing your dependencies. Check the file to ensure that it's correctly formatted for the file type.
-
-{% if currentVersion == "free-pro-team@latest" %}
-If the file is correctly formatted, then check its size. The dependency graph ignores individual manifest and lock files that are over 0.5 Mb, unless you are a {% data variables.product.prodname_enterprise %} user. It processes up to 20 manifest or lock files per repository by default, so you can split dependencies into smaller files in subdirectories of the repository.{% endif %}
-
-If a manifest or lock file is not processed, its dependencies are omitted from the dependency graph and they can't be checked for vulnerable dependencies.
-
-### 延伸阅读
-
-- "[About the dependency graph](about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- "[查看用于组织的洞见](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
-- "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[了解 {% data variables.product.product_name %} 如何使用和保护数据](/github/understanding-how-github-uses-and-protects-your-data)"
-{% endif %}
diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on.md
deleted file mode 100644
index 8908fd42e1ad..000000000000
--- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: 列出仓库所依赖的包
-intro: 您可以在仓库图中查看项目的依赖项以及检测到的所有漏洞。
-redirect_from:
- - /articles/listing-the-packages-that-a-repository-depends-on
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### 关于依赖项图
-
-依赖关系图适用于使用支持的文件格式、以支持的包生态系统定义依赖项的每个{% if currentVersion == "free-pro-team@latest" %}公共{% endif %}仓库。{% if currentVersion == "free-pro-team@latest" %} 仓库管理员也可对私有仓库设置依赖项图。{% endif %}
-
-{% data reusables.repositories.enable-security-alerts %}
-
-您可以在仓库的依赖项图中查看和更新有漏洞的依赖项。 依赖项图将有漏洞的依赖项列在其他依赖项前面。 更多信息请参阅“[关于依赖项漏洞的安全警报](/articles/about-security-alerts-for-vulnerable-dependencies)”。
-
-{% if currentVersion == "free-pro-team@latest" %}
-您可以在一个仪表板中查看组织仓库中使用的依赖项。 更多信息请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)”。{% endif %}
-
-### 支持的包生态系统
-
-| 包管理器 | 语言 | 建议的格式 | 支持的格式 |
-| ------------ | --------------------- | -------------------------------------------------- | -------------------------------------------------------------------- |
-| Maven | Java、Scala | `pom.xml` | `pom.xml` |
-| npm | JavaScript | `package-lock.json` | `package-lock.json`、`package.json` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`、`yarn.lock` |
-| `dotnet` CLI | .NET 语言(C#、C++、F#、VB) | `.csproj`、`.vbproj`、`.nuspec`、`.vcxproj`、`.fsproj` | `.csproj`、`.vbproj`、`.nuspec`、`.vcxproj`、`.fsproj`、`packages.config` |
-| Python PIP | Python | `requirements.txt`、`pipfile.lock` | `requirements.txt`、`pipfile.lock`、`setup.py`* |
-| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`、`Gemfile`、`*.gemspec` |
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` |{% endif %}
-
-{% note %}
-
-**注:**如果在 `setup.py` 文件中列出 Python 依赖项,我们可能无法剖析、列出和提醒项目中的每个依赖项。
-
-{% endnote %}
-
-### 为启用了依赖项图的仓库列出依赖项
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### 为私有仓库启用依赖项图
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}
-4. 阅读关于授予 {% data variables.product.product_name %} 访问仓库数据的消息,以启用依赖项图,然后单击 **Allow access(允许访问)**。 ![允许访问仓库数据以启用依赖项图的按钮](/assets/images/help/repository/dependency-graph-allow-access-button.png)
-
-更多信息请参阅“[了解 {% data variables.product.product_name %} 如何使用和保护数据](/categories/understanding-how-github-uses-and-protects-your-data)”。
-
-### 为私有仓库禁用依赖项图
-
-{% data reusables.repositories.you-can-enable-or-disable-security-features %}
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-3. 在 "Data services"(数据服务)下,取消选中 **Dependency graph(依赖项图)**。 ![禁用依赖项图的复选框](/assets/images/help/repository/private-repo-data-use-dependency-graph-disabled.png)
-
-To opt out of data use for your repository, see "[Opting into or out of data use for your private repository](/articles/opting-into-or-out-of-data-use-for-your-private-repository)."
-{% endif %}
-
-### 依赖项图疑难排解
-
-{% data reusables.repositories.troubleshooting-dependency-graph %}
-
-### 延伸阅读
-
-- "[列出依赖仓库的项目](/articles/listing-the-projects-that-depend-on-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[了解 {% data variables.product.product_name %} 如何使用和保护数据](/categories/understanding-how-github-uses-and-protects-your-data)"
-- "[查看和更新仓库中的漏洞依赖项](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% endif %}
diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository.md
deleted file mode 100644
index 5c092e5aa3dc..000000000000
--- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: 列出依赖仓库的项目
-intro: 您可以在依赖项图中查看依赖仓库的包和项目。
-redirect_from:
- - /articles/listing-the-projects-that-depend-on-a-repository
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-### 关于依赖项图
-依赖项图包含包和应用程序的数据。 包是在包管理器中包含存储库的仓库,而应用程序是依赖所选仓库的仓库。 依赖项图中的应用程序列表按依赖仓库的最近项目排序。
-
-依赖项图包含以下语言的数据:
-
-- RubyGems
-- NPM
-- PyPI
-- Maven(仅 pom.xml)
-- Nuget
-
-{% data reusables.repositories.enable-security-alerts %}
-
-{% note %}
-
-**注:**依赖项计数是近似值,可能与列出的依赖项不匹配。
-
-{% endnote %}
-
-![从属者图](/assets/images/help/graphs/dependents_graph.png)
-
-### 访问依赖项图
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}
-4. 在 "Dependency graph"(依赖项图)下,单击 **Dependents(依赖项)**。 ![依赖项图中的依赖项选项卡](/assets/images/help/graphs/dependency-graph-dependents-tab.png)
-
-### 延伸阅读
-
-- "[列出仓库所依赖的包](/articles/listing-the-packages-that-a-repository-depends-on)"{% if currentVersion == "free-pro-team@latest" %}
-- "[查看用于组织的洞见](/articles/viewing-insights-for-your-organization)"{% endif %}
diff --git a/translations/zh-CN/content/rest/reference/endpoints-available-for-github-apps.md b/translations/zh-CN/content/rest/reference/endpoints-available-for-github-apps.md
deleted file mode 100644
index 3e17fbfa0894..000000000000
--- a/translations/zh-CN/content/rest/reference/endpoints-available-for-github-apps.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: 可用于 GitHub 应用程序的端点
-intro: 您的应用程序可以向以下 REST 端点发出请求。
-redirect_from:
- - /v3/apps/available-endpoints
-versions:
- free-pro-team: '*'
- enterprise-server: '*'
----
-
-您必须使用安装访问令牌通过 {% data variables.product.prodname_github_app %} 访问端点。 更多信息请参阅“[向 {% data variables.product.prodname_github_apps %} 验证](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)”。
-
-{% include rest_enabled_for_github_apps_in_current_version %}
diff --git a/translations/zh-CN/data/reusables/actions/actions-app-read-permissions-sh-org.md b/translations/zh-CN/data/reusables/actions/actions-app-read-permissions-sh-org.md
deleted file mode 100644
index 89cc846f3e23..000000000000
--- a/translations/zh-CN/data/reusables/actions/actions-app-read-permissions-sh-org.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s must have the `self-hosted runners:read` organization permission to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/actions-app-secrets-org-permissions.md b/translations/zh-CN/data/reusables/actions/actions-app-secrets-org-permissions.md
deleted file mode 100644
index 4f41e05ae20e..000000000000
--- a/translations/zh-CN/data/reusables/actions/actions-app-secrets-org-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s must have the `secrets` organization permission to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/actions-app-secrets-permissions.md b/translations/zh-CN/data/reusables/actions/actions-app-secrets-permissions.md
deleted file mode 100644
index 7709eb5b2e53..000000000000
--- a/translations/zh-CN/data/reusables/actions/actions-app-secrets-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s must have the `secrets` repository permission to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/actions-app-write-permissions-sh-org.md b/translations/zh-CN/data/reusables/actions/actions-app-write-permissions-sh-org.md
deleted file mode 100644
index f330c2358998..000000000000
--- a/translations/zh-CN/data/reusables/actions/actions-app-write-permissions-sh-org.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s must have the `self-hosted runners:write` organization permission to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/actions-downloads.md b/translations/zh-CN/data/reusables/actions/actions-downloads.md
deleted file mode 100644
index ac085b746d74..000000000000
--- a/translations/zh-CN/data/reusables/actions/actions-downloads.md
+++ /dev/null
@@ -1 +0,0 @@
-使用 `-v` 旗标调用此端点,以启用详细输出,并允许您在标头中查看下载 URL。 要将文件下载到当前工作目录中,请使用 `-o` 指定文件名。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/actions-secret-encyption-examples.md b/translations/zh-CN/data/reusables/actions/actions-secret-encyption-examples.md
deleted file mode 100644
index 3a0d000bd9f3..000000000000
--- a/translations/zh-CN/data/reusables/actions/actions-secret-encyption-examples.md
+++ /dev/null
@@ -1,69 +0,0 @@
-#### Example encrypting a secret using Node.js
-
-使用 [tweetsodium](https://github.com/github/tweetsodium) 库对密码进行加密。
-
-```js
-const sodium = require('tweetsodium');
-
-const key = "base64-encoded-public-key";
-const value = "plain-text-secret";
-
-// Convert the message and key to Uint8Array's (Buffer implements that interface)
-const messageBytes = Buffer.from(value);
-const keyBytes = Buffer.from(key, 'base64');
-
-// Encrypt using LibSodium.
-const encryptedBytes = sodium.seal(messageBytes, keyBytes);
-
-// Base64 the encrypted secret
-const encrypted = Buffer.from(encryptedBytes).toString('base64');
-
-console.log(encrypted);
-```
-
-#### Example encrypting a secret using Python
-
-使用 [pynacl](https://pynacl.readthedocs.io/en/stable/public/#nacl-public-sealedbox) 和 Python 3 对密码进行加密。
-
-```py
-from base64 import b64encode
-from nacl import encoding, public
-
-def encrypt(public_key: str, secret_value: str) -> str:
- """Encrypt a Unicode string using the public key."""
- public_key = public.PublicKey(public_key.encode("utf-8"), encoding.Base64Encoder())
- sealed_box = public.SealedBox(public_key)
- encrypted = sealed_box.encrypt(secret_value.encode("utf-8"))
- return b64encode(encrypted).decode("utf-8")
-```
-
-#### Example encrypting a secret using C\#
-
-Encrypt your secret using the [Sodium.Core](https://www.nuget.org/packages/Sodium.Core/) package.
-
-```csharp
-var secretValue = System.Text.Encoding.UTF8.GetBytes("mySecret");
-var publicKey = Convert.FromBase64String("2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=");
-
-var sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);
-
-Console.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));
-```
-
-#### Example encrypting a secret using Ruby
-
-使用 [rbnacl](https://github.com/RubyCrypto/rbnacl) gem 对密码进行加密。
-
-```ruby
-require "rbnacl"
-require "base64"
-
-key = Base64.decode64("+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=")
-public_key = RbNaCl::PublicKey.new(key)
-
-box = RbNaCl::Boxes::Sealed.from_public_key(public_key)
-encrypted_secret = box.encrypt("my_secret")
-
-# Print the base64 encoded secret
-puts Base64.strict_encode64(encrypted_secret)
-```
diff --git a/translations/zh-CN/data/reusables/actions/gh-app-actions-read-permissions.md b/translations/zh-CN/data/reusables/actions/gh-app-actions-read-permissions.md
deleted file mode 100644
index 08998b6efb12..000000000000
--- a/translations/zh-CN/data/reusables/actions/gh-app-actions-read-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s must have the `actions:read` permission to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/gh-app-actions-write-permissions.md b/translations/zh-CN/data/reusables/actions/gh-app-actions-write-permissions.md
deleted file mode 100644
index c7c714441f31..000000000000
--- a/translations/zh-CN/data/reusables/actions/gh-app-actions-write-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s must have the `actions:write` permission to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/workflow-route-param-by-name.md b/translations/zh-CN/data/reusables/actions/workflow-route-param-by-name.md
deleted file mode 100644
index 697b1a078ad1..000000000000
--- a/translations/zh-CN/data/reusables/actions/workflow-route-param-by-name.md
+++ /dev/null
@@ -1 +0,0 @@
-您也可以将 `:workflow_id` 替换为 `:workflow_file_name`。 例如,您可以使用 `main.yml`。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/workflow-usage.md b/translations/zh-CN/data/reusables/actions/workflow-usage.md
deleted file mode 100644
index 90836167de81..000000000000
--- a/translations/zh-CN/data/reusables/actions/workflow-usage.md
+++ /dev/null
@@ -1 +0,0 @@
-Billable minutes only apply to workflows in private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners. Usage is listed for each {% data variables.product.prodname_dotcom %}-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)".
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/workflow_runs_parameters_table.md b/translations/zh-CN/data/reusables/actions/workflow_runs_parameters_table.md
deleted file mode 100644
index ac4cb844fe4f..000000000000
--- a/translations/zh-CN/data/reusables/actions/workflow_runs_parameters_table.md
+++ /dev/null
@@ -1,8 +0,0 @@
-#### 参数
-
-| 名称 | 类型 | 描述 |
-| ------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `actor` | `字符串` | Returns someone's workflow runs. Use the login for the user who created the `push` associated with the check suite or workflow run. |
-| `分支` | `字符串` | Returns workflow runs associated with a branch. Use the name of the branch of the `push`. |
-| `event` | `字符串` | Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows)". |
-| `状态` | `字符串` | Returns workflow runs associated with the check run `status` or `conclusion` you specify. For example, a conclusion can be `success` or a status can be `completed`. For more information, see the `status` and `conclusion` options available in "[Create a check run](/v3/checks/runs/#create-a-check-run)." |
diff --git a/translations/zh-CN/data/reusables/apps/access_token_parameters_table_and_example.md b/translations/zh-CN/data/reusables/apps/access_token_parameters_table_and_example.md
deleted file mode 100644
index 167aaa920510..000000000000
--- a/translations/zh-CN/data/reusables/apps/access_token_parameters_table_and_example.md
+++ /dev/null
@@ -1,13 +0,0 @@
-#### 参数
-
-| 名称 | 类型 | 描述 |
-| -------------- | ----- | ------------------------------ |
-| `access_token` | `字符串` | 用于向 GitHub API 验证的 OAuth 访问令牌。 |
-
-#### 示例
-
-```json
-{
- "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a"
-}
-```
diff --git a/translations/zh-CN/data/reusables/apps/app_req_account_deletion.md b/translations/zh-CN/data/reusables/apps/app_req_account_deletion.md
deleted file mode 100644
index fc8f7cc458bd..000000000000
--- a/translations/zh-CN/data/reusables/apps/app_req_account_deletion.md
+++ /dev/null
@@ -1 +0,0 @@
-Apps must provide customers with a way to delete their account, without having to email or call a support person.
diff --git a/translations/zh-CN/data/reusables/apps/authenticated_user_access.md b/translations/zh-CN/data/reusables/apps/authenticated_user_access.md
deleted file mode 100644
index 1e4977d57512..000000000000
--- a/translations/zh-CN/data/reusables/apps/authenticated_user_access.md
+++ /dev/null
@@ -1 +0,0 @@
-经过身份验证的用户对其拥有的仓库、他们作为协作者的仓库以及他们可通过组织成员资格访问的仓库具有明确的访问权限。
diff --git a/translations/zh-CN/data/reusables/apps/authorizations_oauth_tokens_SAML.md b/translations/zh-CN/data/reusables/apps/authorizations_oauth_tokens_SAML.md
deleted file mode 100644
index 04c8f7f4dbfc..000000000000
--- a/translations/zh-CN/data/reusables/apps/authorizations_oauth_tokens_SAML.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
-{% warning %}
-
-**警告:**应用程序必须使用 [web 应用程序流程](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)来获取适用于 GitHub SAML 组织的 OAuth 令牌。 使用授权 API 创建的 OAuth 令牌将无法访问 GitHub SAML 组织。 更多信息请参阅[博客帖子](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api)。
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/apps/deprecating_applications_api_endpoints.md b/translations/zh-CN/data/reusables/apps/deprecating_applications_api_endpoints.md
deleted file mode 100644
index d9a22f21ade8..000000000000
--- a/translations/zh-CN/data/reusables/apps/deprecating_applications_api_endpoints.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-{% warning %}
-
-**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will replace and discontinue OAuth endpoints containing `access_token` in the path parameter. We are introducing new endpoints that allow you to securely manage tokens for OAuth Apps by using `access_token` as an input parameter.{% if currentVersion == "free-pro-team@latest" %} The OAuth Application API will be removed on May 5, 2021.{% endif %} For more information,{% if currentVersion == "free-pro-team@latest" %} including scheduled brownouts,{% endif %} see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).
-
-{% if currentVersion != "free-pro-team@latest" %} OAuth endpoints using an `access_token` in the path parameter are currently available and not yet deprecated in {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} will announce the deprecation and provide advanced notice before removing support for this feature.{% endif %}
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/apps/deprecating_github_services_ghe_compact.md b/translations/zh-CN/data/reusables/apps/deprecating_github_services_ghe_compact.md
deleted file mode 100644
index 6ffb0325d760..000000000000
--- a/translations/zh-CN/data/reusables/apps/deprecating_github_services_ghe_compact.md
+++ /dev/null
@@ -1 +0,0 @@
-GitHub Enterprise release 2.17 and higher no longer allows admins to install GitHub Services. Please see the [Replacing GitHub Services guide](/v3/guides/replacing-github-services) for details.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/apps/deprecating_oauth_authorizations.md b/translations/zh-CN/data/reusables/apps/deprecating_oauth_authorizations.md
deleted file mode 100644
index 1ba5d7242e26..000000000000
--- a/translations/zh-CN/data/reusables/apps/deprecating_oauth_authorizations.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-{% warning %}
-
-**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow).{% if currentVersion == "free-pro-team@latest" %} The OAuth Authorizations API will be removed on November, 13, 2020.{% endif %} For more information,{% if currentVersion == "free-pro-team@latest" %} including scheduled brownouts,{% endif %} see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).
-
-{% if currentVersion != "free-pro-team@latest" %} The OAuth Authorizations API is currently available and not yet deprecated in {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} will announce the deprecation and provide advanced notice before removing support for this feature.{% endif %}
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/apps/iat_required.md b/translations/zh-CN/data/reusables/apps/iat_required.md
deleted file mode 100644
index c15c5042f1d1..000000000000
--- a/translations/zh-CN/data/reusables/apps/iat_required.md
+++ /dev/null
@@ -1 +0,0 @@
-您必须使用[安装设施访问令牌](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)才能访问此端点。
diff --git a/translations/zh-CN/data/reusables/apps/iat_required_multiple_endpoints.md b/translations/zh-CN/data/reusables/apps/iat_required_multiple_endpoints.md
deleted file mode 100644
index 2147de3e7766..000000000000
--- a/translations/zh-CN/data/reusables/apps/iat_required_multiple_endpoints.md
+++ /dev/null
@@ -1 +0,0 @@
-You must use an [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access these endpoints.
diff --git a/translations/zh-CN/data/reusables/apps/jwt_or_client_secret_required.md b/translations/zh-CN/data/reusables/apps/jwt_or_client_secret_required.md
deleted file mode 100644
index 7d5a916ec3cd..000000000000
--- a/translations/zh-CN/data/reusables/apps/jwt_or_client_secret_required.md
+++ /dev/null
@@ -1 +0,0 @@
-GitHub 应用程序必须使用 [JWT](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) 才能访问此端点。 OAuth 应用程序必须使用[基本身份验证](/v3/auth/#basic-authentication)及其客户端 ID 和客户端密钥才能访问此端点。
diff --git a/translations/zh-CN/data/reusables/apps/jwt_required.md b/translations/zh-CN/data/reusables/apps/jwt_required.md
deleted file mode 100644
index 16bc911537e0..000000000000
--- a/translations/zh-CN/data/reusables/apps/jwt_required.md
+++ /dev/null
@@ -1 +0,0 @@
-您必须使用 [JWT](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) 才能访问此端点。
diff --git a/translations/zh-CN/data/reusables/apps/null-headbranch.md b/translations/zh-CN/data/reusables/apps/null-headbranch.md
deleted file mode 100644
index 9909557ac600..000000000000
--- a/translations/zh-CN/data/reusables/apps/null-headbranch.md
+++ /dev/null
@@ -1 +0,0 @@
-The Checks API only looks for pushes in the repository where the check suite or check run were created. 未检测到向复刻的仓库中分支的推送,为 `head_branch` 返回空的 `pull_requests` 数组和 `null` 值。
diff --git a/translations/zh-CN/data/reusables/apps/pat_or_ba_required.md b/translations/zh-CN/data/reusables/apps/pat_or_ba_required.md
deleted file mode 100644
index a595ba312649..000000000000
--- a/translations/zh-CN/data/reusables/apps/pat_or_ba_required.md
+++ /dev/null
@@ -1 +0,0 @@
-必须使用个人访问令牌(您可以通过[命令行](/articles/creating-a-personal-access-token-for-the-command-line/)或[OAuth 授权 API](/v3/oauth_authorizations/#create-a-new-authorization) 来创建)或[基本身份验证](/v3/auth/#basic-authentication)才能访问此端点。
diff --git a/translations/zh-CN/data/reusables/apps/u2s_required.md b/translations/zh-CN/data/reusables/apps/u2s_required.md
deleted file mode 100644
index 5a72c38bf14c..000000000000
--- a/translations/zh-CN/data/reusables/apps/u2s_required.md
+++ /dev/null
@@ -1 +0,0 @@
-必须使用为授权 GitHub 应用程序的用户而创建的 [user-to-server OAuth 访问令牌](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site),才能访问此端点。
diff --git a/translations/zh-CN/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-runs.md b/translations/zh-CN/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-runs.md
deleted file mode 100644
index f6ba9c704203..000000000000
--- a/translations/zh-CN/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-runs.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注:**检查 API 仅在创建检查套件或检查运行的仓库中搜索推送。 未检测到向复刻的仓库中分支的推送,返回一个空的 `pull_requests` 数组。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/blog/affected_users.md b/translations/zh-CN/data/reusables/blog/affected_users.md
deleted file mode 100644
index a390a81ab553..000000000000
--- a/translations/zh-CN/data/reusables/blog/affected_users.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note**: This update only affects users of GitHub.com and future versions of GitHub Enterprise.
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/branches/apps-permissions.md b/translations/zh-CN/data/reusables/branches/apps-permissions.md
deleted file mode 100644
index a549fc7d28dd..000000000000
--- a/translations/zh-CN/data/reusables/branches/apps-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}Only installed {% data variables.product.prodname_github_app %}s with `write` access to the `contents` permission can be added as authorized actors on a protected branch.{% endif %}
diff --git a/translations/zh-CN/data/reusables/branches/limits.md b/translations/zh-CN/data/reusables/branches/limits.md
deleted file mode 100644
index 1242d37342d9..000000000000
--- a/translations/zh-CN/data/reusables/branches/limits.md
+++ /dev/null
@@ -1 +0,0 @@
-**Note**: The list of users{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, apps,{% endif %} and teams in total is limited to 100 items.
diff --git a/translations/zh-CN/data/reusables/branches/rename-existing-branch.md b/translations/zh-CN/data/reusables/branches/rename-existing-branch.md
deleted file mode 100644
index 174a317ddc65..000000000000
--- a/translations/zh-CN/data/reusables/branches/rename-existing-branch.md
+++ /dev/null
@@ -1,3 +0,0 @@
-While you can rename your repository's existing default branch, {% data variables.product.company_short %} plans to provide tools to simplify the process of renaming the default branch. For more information on these plans, see [`github/renaming`](https://github.com/github/renaming).
-
-If you have already renamed the default branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion ver_gt "enterprise-server@2.22" %} {% data variables.product.product_location_enterprise %}{% else %}{% data variables.product.prodname_dotcom_the_website %}{% endif %} that contain a deleted `master` branch name to the equivalent link on the repository's default branch.
diff --git a/translations/zh-CN/data/reusables/checks/conclusion_values.md b/translations/zh-CN/data/reusables/checks/conclusion_values.md
deleted file mode 100644
index 5d19b1ca702c..000000000000
--- a/translations/zh-CN/data/reusables/checks/conclusion_values.md
+++ /dev/null
@@ -1 +0,0 @@
-**在提供 `completed_at` 或 `completed` 的 `status` 时需要**。 检查的最后结论。 Can be one of `success`, `failure`, `neutral`, `cancelled`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}`skipped`, {% endif %}`timed_out`, or `action_required`.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/checks/requested_actions.md b/translations/zh-CN/data/reusables/checks/requested_actions.md
deleted file mode 100644
index 1c040984c463..000000000000
--- a/translations/zh-CN/data/reusables/checks/requested_actions.md
+++ /dev/null
@@ -1 +0,0 @@
-要了解有关检查运行和请的求操作的详细信息,请参阅“[检查运行和请求的操作](/v3/checks/runs/#check-runs-and-requested-actions)”。
diff --git a/translations/zh-CN/data/reusables/cli/beta.md b/translations/zh-CN/data/reusables/cli/beta.md
deleted file mode 100644
index 43174757dd1d..000000000000
--- a/translations/zh-CN/data/reusables/cli/beta.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_cli %} 目前处于测试阶段,可能会有变化。
diff --git a/translations/zh-CN/data/reusables/collaborators/collaborator-definition.md b/translations/zh-CN/data/reusables/collaborators/collaborator-definition.md
deleted file mode 100644
index af37fe0d3162..000000000000
--- a/translations/zh-CN/data/reusables/collaborators/collaborator-definition.md
+++ /dev/null
@@ -1 +0,0 @@
-the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.
diff --git a/translations/zh-CN/data/reusables/command_line/parameters_filters.md b/translations/zh-CN/data/reusables/command_line/parameters_filters.md
deleted file mode 100644
index 39cfa8cc3a31..000000000000
--- a/translations/zh-CN/data/reusables/command_line/parameters_filters.md
+++ /dev/null
@@ -1 +0,0 @@
-您可以使用参数缩小结果列表。 有关使用参数的更多信息,请参阅 [参数](/v3/#parameters)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/commits/verification-object-definition.md b/translations/zh-CN/data/reusables/commits/verification-object-definition.md
deleted file mode 100644
index d9b31285cf7f..000000000000
--- a/translations/zh-CN/data/reusables/commits/verification-object-definition.md
+++ /dev/null
@@ -1,28 +0,0 @@
-##### 签名验证对象
-
-响应将包含一个 `verification` 对象,以描述验证提交签名的结果。 以下字段包含在 `verification` 对象中:
-
-| 名称 | 类型 | 描述 |
-| ----------- | ----- | -------------------------------------------------------------------------------------------------- |
-| `已验证` | `布尔值` | Indicates whether GitHub considers the signature in this commit to be verified. |
-| `原因` | `字符串` | The reason for `verified` value. Possible values and their meanings are enumerated in table below. |
-| `signature` | `字符串` | The signature that was extracted from the commit. |
-| `payload` | `字符串` | The value that was signed. |
-
-以下是 `verification` 对象中 `reason` 的可能值:
-
-| 值 | 描述 |
-| ------------------------ | ------------------------------------------------- |
-| `expired_key` | 表示签名过期的键。 |
-| `not_signing_key` | “签名”标志不在生成签名的 GPG 密钥的使用标志中。 |
-| `gpgverify_error` | 与签名验证服务通信时出错。 |
-| `gpgverify_unavailable` | 签名验证服务当前不可用。 |
-| `unsigned` | 对象不包括签名。 |
-| `unknown_signature_type` | 在提交中发现非 PGP 签名。 |
-| `no_user` | 没有用户与提交中的 `committer` 电子邮件地址相关联。 |
-| `unverified_email` | 提交中的 `committer` 电子邮件地址与某个用户相关联,但未在其帐户中验证该电子邮件地址。 |
-| `bad_email` | 提交中的 `committer` 电子邮件地址未包含在生成签名的 PGP 密钥的标识中。 |
-| `unknown_key` | 进行签名的密钥尚未向任何用户帐户注册。 |
-| `malformed_signature` | 解析签名时出错。 |
-| `invalid` | 无法使用在签名中找到密钥 ID 的密钥进行加密验证签名。 |
-| `有效` | 未出现上述任何错误,因此该签名被视为已验证。 |
diff --git a/translations/zh-CN/data/reusables/desktop/commit-history-list.md b/translations/zh-CN/data/reusables/desktop/commit-history-list.md
deleted file mode 100644
index 5de60e700713..000000000000
--- a/translations/zh-CN/data/reusables/desktop/commit-history-list.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 在提交历史记录列表中,单击要还原的提交。
diff --git a/translations/zh-CN/data/reusables/desktop/enter-2fa-in-browser.md b/translations/zh-CN/data/reusables/desktop/enter-2fa-in-browser.md
deleted file mode 100644
index 7e98e9551a27..000000000000
--- a/translations/zh-CN/data/reusables/desktop/enter-2fa-in-browser.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 返回到 {% data variables.product.prodname_dotcom %}。 在提示符中,输入 2FA 代码,然后单击**Verify(验证)**。 ![2FA 验证码字段](/assets/images/help/desktop/2fa-code-field.png)
diff --git a/translations/zh-CN/data/reusables/desktop/retrieve-2fa-in-browser.md b/translations/zh-CN/data/reusables/desktop/retrieve-2fa-in-browser.md
deleted file mode 100644
index ec706b49887b..000000000000
--- a/translations/zh-CN/data/reusables/desktop/retrieve-2fa-in-browser.md
+++ /dev/null
@@ -1,3 +0,0 @@
-1. 如果已为 {% data variables.product.prodname_dotcom %} 配置双重身份验证,请执行以下操作之一:
- - 如果通过 SMS 设置 2FA,则从 SMS 消息检索 2FA 代码 。
- - 如果使用 TOTP 应用程序设置 2FA,则生成 2FA 代码。
diff --git a/translations/zh-CN/data/reusables/desktop/windows-select-file-menu.md b/translations/zh-CN/data/reusables/desktop/windows-select-file-menu.md
deleted file mode 100644
index 69a41cebf73b..000000000000
--- a/translations/zh-CN/data/reusables/desktop/windows-select-file-menu.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 在窗口的左上角,选择 **File(文件)** 菜单。 ![Windows 菜单栏中的 {% data variables.product.prodname_desktop %} 菜单](/assets/images/help/desktop/windows-select-file-menu.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/cost-management-tab.md b/translations/zh-CN/data/reusables/dotcom_billing/cost-management-tab.md
deleted file mode 100644
index dcea12c5035d..000000000000
--- a/translations/zh-CN/data/reusables/dotcom_billing/cost-management-tab.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 在“Billing(帐单)”下,单击 **Cost management(成本管理)**。 ![成本管理选项卡](/assets/images/help/settings/cost-management-tab.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/publishing-nodejs-packages.md b/translations/zh-CN/data/reusables/dotcom_billing/publishing-nodejs-packages.md
deleted file mode 100644
index ee10b383281d..000000000000
--- a/translations/zh-CN/data/reusables/dotcom_billing/publishing-nodejs-packages.md
+++ /dev/null
@@ -1,203 +0,0 @@
----
-title: 发布 Node.js 包
-intro: 您可以将 Node.js 包发布到注册表,作为持续集成 (CI) 工作流程的一部分。
-product: '{% data reusables.gated-features.actions %}'
-productVersions:
- dotcom: '*'
-redirect_from:
- - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
----
-
-### 简介
-
-本指南介绍如何创建一个工作流程,以在持续集成 (CI) 测试通过后将 Node.js 包发布到 {% data variables.product.prodname_registry %} 和 npm 注册表。 通过单个工作流程,您可以将包发布到单个注册表或多个注册表。
-
-### 基本要求
-
-建议基本了解工作流程配置选项和如何创建工作流程文件。 更多信息请参阅“[配置工作流程](/actions/automating-your-workflow-with-github-actions/configuring-a-workflow)。
-
-有关为 Node.js 项目创建 CI 工作流程的更多信息,请参阅“[将 Node.js 与 {% data variables.product.prodname_actions %} 一起使用](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)。”
-
-您可能还发现基本了解以下内容是有帮助的:
-
-- "[{% data variables.product.prodname_actions %} 的核心概念](/actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)"
-- "[配置 npm 用于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
-- "[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-- "[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)"
-- "[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)"
-
-### 关于包配置
-
- *package.json* 文件中的 `name` 和 `version` 字段创建唯一标识符,供注册表用来将包链接到注册表。 您可以在 *package.json* 文件中添加 `description` 字段,从而为包列表页面添加一个摘要。 更多信息请参阅 npm 文档中的“[创建 package.json 文件](https://docs.npmjs.com/creating-a-package-json-file)”和“[创建 Node.js 模块](https://docs.npmjs.com/creating-node-js-modules)”。
-
-当本地 *.npmrc* 文件存在且指定了 `registry` 值时,`npm publish` 命令将使用 *.npmrc* 文件中配置的注册表。 {% data reusables.github-actions.setup-node-intro %}
-
-您可以使用 `setup-node` 操作指定运行器上安装的 Node.js 版本。
-
-如果在工作流程中添加步骤来配置 *package.json* 文件中的 `publishConfig` 字段,则无需使用 `setup-node` 操作指定注册表 url,但软件包仅限于发布到一个注册表。 更多信息请参阅 npm 文档中的“[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)”。
-
-### 发布包到 npm 注册表
-
-每次创建新版本时,都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过,工作流程将包发布到 npm 注册表。
-
-要根据工作流程中的 npm 注册表执行经过身份验证的操作,您需要在仓库设置中将 npm 身份验证令牌作存储为密码。 例如,创建名为 `NPM_TOKEN` 的密码。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-默认情况下,npm 使用 *package.json* 文件的 `name` 字段来确定 npm 注册表。 当发布到全局命名空间时,您只需要包含包名称。 例如,您要发布一个名为 `npm-hello-world-test` 的包到 `https://www.npmjs.com/package/npm-hello-world-test`。
-
-如果发布一个包含范围前缀的包,请将范围包含在 *package.json* 文件的名称中。 例如,如果 npm 范围前缀是 octocat 并且包名是 hello-world,则 *package.json* 文件中的 `name` 应为 `@octocat/hello-world`。 如果 npm 包使用范围前缀且包是公开的,则需使用选项 `npm publish --access public`。 这是 npm 需要用来防止有人无意中发布私有包的选项。
-
-此示例将 `NPM_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时,会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # Setup .npmrc file to publish to npm
- - uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- registry-url: 'https://registry.npmjs.org'
- - run: npm install
- - run: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-```
-{% endraw %}
-
-在上面的示例中,`setup-node` 操作在运行器上创建一个包含以下内容的 *.npmrc* 文件:
-
-```
-//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
-registry=https://registry.npmjs.org/
-always-auth=true
-```
-
-### 发布包到 {% data variables.product.prodname_registry %}
-
-每次创建新版本时,都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件发生时运行。 如果 CI 测试通过,工作流程会将包发布到 {% data variables.product.prodname_registry %}。
-
-默认情况下,{% data variables.product.prodname_registry %} 将包发布到您在 *package.json* 文件的 `name` 字段中指定的 {% data variables.product.prodname_dotcom %} 仓库。 例如,您要发布一个名为 `@my-org/test` 的包到 `my-org/test` {% data variables.product.prodname_dotcom %} 仓库。 更多信息请参阅 npm 文档中的 [`npm-scope`](https://docs.npmjs.com/misc/scope)。
-
-要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作,可以使用 `GITHUB_TOKEN`。 `GITHUB_TOKEN` 默认存在于您的仓库中,并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-此示例将 `GITHUB_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时,会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # Setup .npmrc file to publish to GitHub Packages
- - uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- registry-url: 'https://npm.pkg.github.com'
- scope: '@octocat' # Defaults to the user or organization that owns the workflow file
- - run: npm install
- - run: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
-
-`setup-node` 操作在运行器上创建 *.npmrc* 文件。 使用 `scope` 输入到 `setup-node` 操作时,*.npmrc* 文件包含作用域前缀。 默认情况下,`setup-node` 操作在 *.npmrc* 文件中将作用域设置为包含该工作流程文件的帐户。
-
-```
-//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
-@octocat:registry=https://npm.pkg.github.com
-always-auth=true
-```
-
-### 使用 yarn 发布包
-
-如果您使用 Yarn 包管理器,可以使用 Yarn 安装和发布包。
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # Setup .npmrc file to publish to npm
- - uses: actions/setup-node@v1
- with:
- node-version: '12.x'
- registry-url: 'https://registry.npmjs.org'
- scope: '@octocat' # Defaults to the user or organization that owns the workflow file
- - run: yarn
- - run: yarn publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-```
-{% endraw %}
-
-### 发布包到 npm 和 {% data variables.product.prodname_registry %}
-
-{% note %}
-
-**注意:**如果需要发布到具有不同作用域前缀的注册表,则需修改运行器上的 *package.json* 文件以更改作用域前缀。 例如,如果将包发布到 npm 的 `@mona` 作用域和 {% data variables.product.prodname_registry %} 的 `@octocat` 作用域,则可在发布到 npm 之后和发布到 {% data variables.product.prodname_registry %} 之前,在运行器的 *package.json* 文件中将 `@mona` 作用域替换成 `@octocat`。
-
-{% endnote %}
-
-您可以使用每个注册表的 `setup-node` 操作将包发布到 npm 注册表和 {% data variables.product.prodname_registry %}。
-
-如果将包发布到两个注册表,则需要确保 npm 上的作用域前缀与 {% data variables.product.prodname_dotcom %} 用户或组织名称匹配。 要将包发布到具有作用域前缀的公共注册表,可以使用 `npm publish --access public`。 更多信息请参阅 [`npm-scope`](https://docs.npmjs.com/misc/scope) 和 npm 文档中的“[创建和发布作用域的公共包](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)”。
-
-确认 *package.json* 文件包含 {% data variables.product.prodname_dotcom %} 仓库和 npm 注册表的作用域。 例如,如果您计划将 `octocat/npm-hello-world-test` 仓库中的包发布到 {% data variables.product.prodname_dotcom %} 和 https://www.npmjs.com/package/@octocat/npm-hello-world-test,则 *package.json* 文件中的名称将是 `"name": "@octocat/npm-hello-world-test"`。
-
-要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作,可以使用 `GITHUB_TOKEN`。 `GITHUB_TOKEN` 默认存在于您的仓库中,并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-使用 `scope` 输入到 `setup-node` 操作时,操作将创建包含作用域前缀的 *.npmrc* 文件。 默认情况下,`setup-node` 操作在 *.npmrc* 文件中将作用域设置为拥有该工作流程文件的用户或组织。
-
-此工作流程将调用 `setup-node` 操作两次。 每当 `setup-node` 操作运行时,都会覆盖 *.npmrc* 文件。 *.npmrc* 文件引用的令牌允许您对 `NODE_AUTH_TOKEN` 环境变量中的包注册表执行验证的操作。 工作流程在 `npm publish` 命令每次运行时设置 `NODE_AUTH_TOKEN` 环境变量,先通过令牌发布到 npm (`NPM_TOKEN`),然后通过令牌发布到 {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`)。
-
-{% raw %}
-```yaml
-name: Node.js Package
-on:
- release:
- types: [created]
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v2
- # Setup .npmrc file to publish to npm
- - uses: actions/setup-node@v1
- with:
- node-version: '10.x'
- registry-url: 'https://registry.npmjs.org'
- - run: npm install
- # Publish to npm
- - run: npm publish --access public
- env:
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
- # Setup .npmrc file to publish to GitHub Packages
- - uses: actions/setup-node@v1
- with:
- registry-url: 'https://npm.pkg.github.com'
- scope: '@octocat' # Defaults to the user or organization that owns the workflow file
- # Publish to GitHub Packages
- - run: npm publish
- env:
- NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-{% endraw %}
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/business-settings.md b/translations/zh-CN/data/reusables/enterprise-accounts/business-settings.md
deleted file mode 100644
index 4a140dfc6780..000000000000
--- a/translations/zh-CN/data/reusables/enterprise-accounts/business-settings.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 在企业帐户名称下,单击 {% octicon "gear" aria-label="The Settings gear" %} **Settings(设置)**。 ![企业帐户资料页面上的“设置”选项卡](/assets/images/help/business-accounts/business-account-settings-tab.png)
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/github-dotcom-connection-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/github-dotcom-connection-tab.md
deleted file mode 100644
index 273437af2dfe..000000000000
--- a/translations/zh-CN/data/reusables/enterprise-accounts/github-dotcom-connection-tab.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 在左侧边栏中,单击 **{% data variables.product.prodname_dotcom_the_website %} connection(连接)**。 ![企业帐户设置侧边栏中的“GitHub.com 连接”选项卡](/assets/images/enterprise/business-accounts/settings-github-dotcom-connection-tab.png)
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/member-privileges-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/member-privileges-tab.md
deleted file mode 100644
index 4bd05ae51151..000000000000
--- a/translations/zh-CN/data/reusables/enterprise-accounts/member-privileges-tab.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 在企业设置侧边栏中,单击 **Member privileges(成员权限)**。 ![企业帐户设置侧边栏中的“成员权限”选项卡](/assets/images/help/business-accounts/settings-member-privileges-tab.png)
diff --git a/translations/zh-CN/data/reusables/enterprise/ldap_sync_warning.md b/translations/zh-CN/data/reusables/enterprise/ldap_sync_warning.md
deleted file mode 100644
index d3e1470f9bce..000000000000
--- a/translations/zh-CN/data/reusables/enterprise/ldap_sync_warning.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" %}
-
-{% warning %}
-
-If your {% data variables.product.prodname_ghe_server %} instance has [LDAP Sync enabled and the option to synchronize emails enabled](/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync), this API is disabled and will return a `403` response. Users managed in LDAP won't be able to add or delete an email address via the API with these options enabled. 在启用了这些选项的情况下,在 LDAP 中管理的用户将无法通过 API 添加或删除电子邮件地址。
-
-{% endwarning %}
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise_enterprise_support/sign-in-to-enterprise-portal.md b/translations/zh-CN/data/reusables/enterprise_enterprise_support/sign-in-to-enterprise-portal.md
deleted file mode 100644
index f177a262e5bb..000000000000
--- a/translations/zh-CN/data/reusables/enterprise_enterprise_support/sign-in-to-enterprise-portal.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 要登录支持门户,请在页面的右上角单击 **Sign in(登录)**。 ![登录 {% data variables.contact.enterprise_portal %}](/assets/images/enterprise/support/sign-in-support-portal.png)
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/increasing-cpus-max.md b/translations/zh-CN/data/reusables/enterprise_installation/increasing-cpus-max.md
deleted file mode 100644
index e35e4f01e316..000000000000
--- a/translations/zh-CN/data/reusables/enterprise_installation/increasing-cpus-max.md
+++ /dev/null
@@ -1,3 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" %}
- {% data reusables.enterprise_installation.increasing-cpus-req %} 如果您使用的 CPU 超过 16 个,则无需为每个 CPU 添加 6.5 GB 内存,但应监控您的实例以确保其有足够的内存。
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/resizing-root-disk.md b/translations/zh-CN/data/reusables/enterprise_installation/resizing-root-disk.md
deleted file mode 100644
index 7ff95a5dfb1f..000000000000
--- a/translations/zh-CN/data/reusables/enterprise_installation/resizing-root-disk.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注意:** 可以构建新设备或使用现有设备来调整根磁盘的大小。 更多信息请参阅“[增加存储容量](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity)”。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/root-and-data-disk-requirement.md b/translations/zh-CN/data/reusables/enterprise_installation/root-and-data-disk-requirement.md
deleted file mode 100644
index 43adc8197342..000000000000
--- a/translations/zh-CN/data/reusables/enterprise_installation/root-and-data-disk-requirement.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_ghe_server %} 需要一个与根磁盘分开的持久性数据磁盘。 更多信息请参阅“[系统概述](/enterprise/admin/guides/installation/system-overview)”。
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/storage-disk-requirements.md b/translations/zh-CN/data/reusables/enterprise_installation/storage-disk-requirements.md
deleted file mode 100644
index 1d5d0b2aa63b..000000000000
--- a/translations/zh-CN/data/reusables/enterprise_installation/storage-disk-requirements.md
+++ /dev/null
@@ -1 +0,0 @@
-对于存储设备,我们建议您使用直接附加的或来自存储区域网络 (SAN) 的高性能 SSD。
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/warning-on-polling.md b/translations/zh-CN/data/reusables/enterprise_installation/warning-on-polling.md
deleted file mode 100644
index a51e0236970c..000000000000
--- a/translations/zh-CN/data/reusables/enterprise_installation/warning-on-polling.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% warning %}
-
-**警告:**建议使用 web 挂钩获取用于持续集成 (CI) 或类似系统的仓库更改。 定期自动检查或*投票*将大大降低实例的可扩展性。 更多信息请参阅“[关于 web 挂钩](/enterprise/{{ currentVersion }}/user/articles/about-webhooks/)”。
-
-{% endwarning %}
diff --git a/translations/zh-CN/data/reusables/gated-features/actions-api-gated.md b/translations/zh-CN/data/reusables/gated-features/actions-api-gated.md
deleted file mode 100644
index 7adac77883df..000000000000
--- a/translations/zh-CN/data/reusables/gated-features/actions-api-gated.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-
-{% data variables.product.prodname_actions %} 可用于 {% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、组织的 {% data variables.product.prodname_free_team %}、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_one %}。 {% data variables.product.prodname_actions %} 不适用于使用旧版按仓库计划的帐户所拥有的私有仓库。 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %}
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/gated-features/credential-authorizations-org.md b/translations/zh-CN/data/reusables/gated-features/credential-authorizations-org.md
deleted file mode 100644
index e095cbb82136..000000000000
--- a/translations/zh-CN/data/reusables/gated-features/credential-authorizations-org.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-
-Listing and deleting credential authorizations is available to organizations with {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/gated-features/draft-pull-requests.md b/translations/zh-CN/data/reusables/gated-features/draft-pull-requests.md
deleted file mode 100644
index 6d54a6cdd3a6..000000000000
--- a/translations/zh-CN/data/reusables/gated-features/draft-pull-requests.md
+++ /dev/null
@@ -1,2 +0,0 @@
-
-拉取请求草稿可用于具有 {% data variables.product.prodname_free_user %} 和组织的 {% data variables.product.prodname_free_team %}、{% data variables.product.prodname_pro %} 及传统按仓库结算方案的公共仓库,以及具有 {% data variables.product.prodname_team %}{% if currentVersion != "free-pro-team@latest" %}、{% data variables.product.prodname_ghe_server %} 2.17+、{% endif %} 和 {% data variables.product.prodname_ghe_cloud %} 的公共和私有仓库。 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/zh-CN/data/reusables/gated-features/policies.md b/translations/zh-CN/data/reusables/gated-features/policies.md
deleted file mode 100644
index f826eda65ff1..000000000000
--- a/translations/zh-CN/data/reusables/gated-features/policies.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note:** {% data variables.product.prodname_policies %} is currently in alpha. This documentation is confidential and made available under NDA. Do not distribute.
-
-{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/gated-features/sponsors-beta.md b/translations/zh-CN/data/reusables/gated-features/sponsors-beta.md
deleted file mode 100644
index 8836f21641dd..000000000000
--- a/translations/zh-CN/data/reusables/gated-features/sponsors-beta.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注意:**用于组织的 {% data variables.product.prodname_sponsors %} 目前处于测试阶段,可能会更改。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/gated-features/team-sync-gated.md b/translations/zh-CN/data/reusables/gated-features/team-sync-gated.md
deleted file mode 100644
index a09ca7594688..000000000000
--- a/translations/zh-CN/data/reusables/gated-features/team-sync-gated.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-
-团队同步可用于使用 {% data variables.product.prodname_ghe_cloud %} 的组织。 {% data reusables.gated-features.more-info %}
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/github-actions/explains-hello-world-example.md b/translations/zh-CN/data/reusables/github-actions/explains-hello-world-example.md
deleted file mode 100644
index 0e3f4f264ed3..000000000000
--- a/translations/zh-CN/data/reusables/github-actions/explains-hello-world-example.md
+++ /dev/null
@@ -1 +0,0 @@
-仓库的 `OWNER` 为 `octocat` 组织,`REPOSITORY` 名称为 `hello-world`。
diff --git a/translations/zh-CN/data/reusables/github-actions/github-actions-minutes-change.md b/translations/zh-CN/data/reusables/github-actions/github-actions-minutes-change.md
deleted file mode 100644
index 231564765711..000000000000
--- a/translations/zh-CN/data/reusables/github-actions/github-actions-minutes-change.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注:**2020 年 5 月 14 日之后,{% data variables.product.prodname_team %} 将每月自带 3,000 {% data variables.product.prodname_actions %} 分钟。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/github-actions/github-actions-usage-limits.md b/translations/zh-CN/data/reusables/github-actions/github-actions-usage-limits.md
deleted file mode 100644
index 2ee4dcde704d..000000000000
--- a/translations/zh-CN/data/reusables/github-actions/github-actions-usage-limits.md
+++ /dev/null
@@ -1,15 +0,0 @@
-{% data variables.product.prodname_actions %} 的使用受到一些不同限制,具体取决于您使用的是 {% data variables.product.prodname_dotcom %} 托管的运行器还是自托管的运行器。 这些限制可能会有变动。
-
-- **作业执行时间** - 工作流程中的每个作业最多可以运行 6 个小时。 如果作业达到此限制,该作业将会终止而无法完成。 此限制不适用于自托管运行器。
-- **工作流程运行时间** - 每个工作流程的运行时限为 72 小时。 如果工作流程运行时间达到此限制,其运行将被取消。 此限制也适用于自托管运行器。
-- **作业排队时间** - 自托管运行器的每个作业最多可排队 24 小时。 如果自托管运行器在此限制内没有开始执行作业,则作业将被终止,并且无法完成。 此限制不适用于 {% data variables.product.prodname_dotcom %} 托管的运行器。
-- **API 请求** - 在一个仓库的所有操作中,一个小时内最多可执行 1000 个 API 请求。 如果超出,额外的 API 调用将失败,这可能导致作业失败。 此限制也适用于自托管运行器。
-- **并发作业** - 您的帐户中可并发运行的作业数量,具体取决于您的 GitHub 计划,如下表所示。 如果超出,任何额外的作业都会排队。 对于自托管运行器没有并发限制。
-
- | GitHub 计划 | 同时运行的作业总数 | MacOS 作业同时运行的最大数量 |
- | --------- | --------- | ----------------- |
- | 免费 | 20 | 5 |
- | Pro | 40 | 5 |
- | 团队 | 60 | 5 |
- | 企业 | 180 | 50 |
-- **作业矩阵** - {% data reusables.github-actions.matrix-limits %}
diff --git a/translations/zh-CN/data/reusables/github-actions/matrix-limits.md b/translations/zh-CN/data/reusables/github-actions/matrix-limits.md
deleted file mode 100644
index 4516fbd36512..000000000000
--- a/translations/zh-CN/data/reusables/github-actions/matrix-limits.md
+++ /dev/null
@@ -1 +0,0 @@
-作业矩阵在每次工作流程运行时最多可生成 256 个作业。 此限制也适用于自托管运行器。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-add-new-runner.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-add-new-runner.md
deleted file mode 100644
index 2aadab0e5954..000000000000
--- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-add-new-runner.md
+++ /dev/null
@@ -1,20 +0,0 @@
-1. 在“Self-hosted runners(自托管运行器)”下,单击 **Add runner(添加运行器)**。
-
-1. 选择自托管运行器机器的操作系统和架构。 ![选择自托管运行器操作系统](/assets/images/help/settings/actions-runner-architecture-os.png)
-
-
-1. 您将看到指示您如何下载运行器应用程序并安装到自托管运行器机器上的说明。
-
- 在自托管运行器机器上打开 shell,并按显示的顺序运行每个 shell 命令。
-
- {% note %}
-
- **注意:** 在 Windows上,如果要将自托管运行器应用程序安装为服务,必须打开具有管理员权限的 shell。 我们还建议您使用 `C:\actions-runner` 作为自托管运行器应用程序的目录,以便 Windows 系统帐户可以访问运行器目录。
-
- {% endnote %}
-
- 这些说明将指导您完成以下任务:
- - 下载并提取自托管运行器应用程序。
- - 运行 `config` 脚本配置自托管运行器应用程序,并向 {% data variables.product.prodname_actions %} 注册。 `config` 脚本需要目标 URL 和自动生成的时间限制令牌来验证请求。
- - 在 Windows上,`config` 脚本还会询问您是否想将自托管运行器应用程序安装为服务。 对于 Linux 和 macOS,您可以在完成添加运行器后安装服务。 更多信息请参阅“[将自托管运行器应用程序配置为服务](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service)”。
- - 运行自托管运行器应用程序以将机器连接到 {% data variables.product.prodname_actions %}。
diff --git a/translations/zh-CN/data/reusables/github-component-kit/intro-for-component-kit.md b/translations/zh-CN/data/reusables/github-component-kit/intro-for-component-kit.md
deleted file mode 100644
index d58b67db5962..000000000000
--- a/translations/zh-CN/data/reusables/github-component-kit/intro-for-component-kit.md
+++ /dev/null
@@ -1 +0,0 @@
-The {% data variables.product.prodname_component_kit %} uses {% data variables.product.prodname_github_app %}s and {% data variables.product.prodname_actions %} to power interactive elements within the {% data variables.product.prodname_dotcom %} UI. For example, you can guide repository users with next steps or prompt them to accept license agreements.
diff --git a/translations/zh-CN/data/reusables/github-component-kit/opening-explanation-for-component-kit.md b/translations/zh-CN/data/reusables/github-component-kit/opening-explanation-for-component-kit.md
deleted file mode 100644
index 9e7d48686861..000000000000
--- a/translations/zh-CN/data/reusables/github-component-kit/opening-explanation-for-component-kit.md
+++ /dev/null
@@ -1,3 +0,0 @@
-The {% data variables.product.prodname_component_kit %} enables you to configure an interactive component to appear in a pull request or issue. Interactive components enable people to trigger and manage tasks that appear in the {% data variables.product.prodname_dotcom %} UI while a {% data variables.product.prodname_github_app %} or action performs the requested tasks and shares updates.
-
-Using the "[Create composable comment](/hidden/github-component-kit/composable-comments#create-composable-comment)" endpoint, a {% data variables.product.prodname_github_app %} or action can create a composable comment in an issue or pull request. The composable comment can include an interactive component, such as a custom button. When someone interacts with the comment, the {% data variables.product.prodname_github_app %} will receive the `interactive_component` webhook event.
diff --git a/translations/zh-CN/data/reusables/github-insights/no-configuration-file.md b/translations/zh-CN/data/reusables/github-insights/no-configuration-file.md
deleted file mode 100644
index b2a5e8dc9955..000000000000
--- a/translations/zh-CN/data/reusables/github-insights/no-configuration-file.md
+++ /dev/null
@@ -1 +0,0 @@
-如果没有配置文件,请按照首次安装 {% data variables.product.prodname_insights %} 的说明进行操作。 更多信息请参阅“[安装 {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/installing-github-insights#installing-github-insights)。”
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/about-connected-teams.md b/translations/zh-CN/data/reusables/identity-and-permissions/about-connected-teams.md
deleted file mode 100644
index 654d522dffa8..000000000000
--- a/translations/zh-CN/data/reusables/identity-and-permissions/about-connected-teams.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后,您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 如果团队连接至 IdP 组,则无法在 {% data variables.product.product_name %} 上或使用 API 管理团队成员。
-
-要管理任何 {% data variables.product.prodname_dotcom %} 团队的仓库访问权限,包括连接至 IdP 组的团队,必须在 {% data variables.product.product_name %} 上进行变更。 更多信息请参阅“[关于团队](/articles/about-teams)”和“[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)”。
-
-默认情况下,您可以选择想要团队成员访问的仓库。 连接的 IdP 组将自动拥有这些仓库的访问权限。 更多信息请参阅“[管理团队的组织仓库访问权限](/articles/managing-team-access-to-an-organization-repository)”。
-
-通过 IdP 进行的所有团队成员资格更改都将在 {% data variables.product.product_name %} 审核日志中显示为团队同步自动程序所进行的更改。 您的 IdP 会将团队成员数据发送至 {% data variables.product.prodname_dotcom %},每小时一次。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/marketplace/marketplace_RFP_deadline.md b/translations/zh-CN/data/reusables/marketplace/marketplace_RFP_deadline.md
deleted file mode 100644
index bd557da1572d..000000000000
--- a/translations/zh-CN/data/reusables/marketplace/marketplace_RFP_deadline.md
+++ /dev/null
@@ -1 +0,0 @@
-10年4月
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/marketplace/unverified-req.md b/translations/zh-CN/data/reusables/marketplace/unverified-req.md
deleted file mode 100644
index f7e6e688b552..000000000000
--- a/translations/zh-CN/data/reusables/marketplace/unverified-req.md
+++ /dev/null
@@ -1 +0,0 @@
-Unverified apps do not need to meet the "[Requirements for listing an app on GitHub Marketplace](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)" or go through the "[Security review process](/marketplace/getting-started/security-review-process/)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/nested-teams/include-child-team-members.md b/translations/zh-CN/data/reusables/nested-teams/include-child-team-members.md
deleted file mode 100644
index 6813efb68e75..000000000000
--- a/translations/zh-CN/data/reusables/nested-teams/include-child-team-members.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %}
-如果您传递 `hellcat-preview` 媒体类型,团队成员将包含子团队的成员。
-{% else %}
-团队成员将包括子团队的成员。
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/org-settings-repository-roles.md b/translations/zh-CN/data/reusables/organizations/org-settings-repository-roles.md
deleted file mode 100644
index f5e6c3cb09eb..000000000000
--- a/translations/zh-CN/data/reusables/organizations/org-settings-repository-roles.md
+++ /dev/null
@@ -1 +0,0 @@
-4. In the left sidebar, click **Repository roles**. ![Repository roles tab in organization settings](/assets/images/help/organizations/org-settings-repository-roles.png)
diff --git a/translations/zh-CN/data/reusables/orgs/deprecating_creation_type.md b/translations/zh-CN/data/reusables/orgs/deprecating_creation_type.md
deleted file mode 100644
index 9a0c49442825..000000000000
--- a/translations/zh-CN/data/reusables/orgs/deprecating_creation_type.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-{% warning %}
-
-**Parameter Deprecation Notice:** {% data variables.product.prodname_dotcom %} will replace and discontinue `members_allowed_repository_creation_type` in favor of more granular permissions. The new input parameters are `members_can_create_public_repositories`, `members_can_create_private_repositories` for all organizations and `members_can_create_internal_repositories` for organizations associated with an enterprise account using {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %} 2.20+. 更多信息请参阅[博客帖子](https://developer.github.com/changes/2019-12-03-internal-visibility-changes)。
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/orgs/internal_repos.md b/translations/zh-CN/data/reusables/orgs/internal_repos.md
deleted file mode 100644
index e432538b3738..000000000000
--- a/translations/zh-CN/data/reusables/orgs/internal_repos.md
+++ /dev/null
@@ -1 +0,0 @@
-If your organization is associated with an enterprise account using {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %} 2.20+, `visibility` can also be `internal`.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/package_registry/about-spending-limits.md b/translations/zh-CN/data/reusables/package_registry/about-spending-limits.md
deleted file mode 100644
index 156bd181ff42..000000000000
--- a/translations/zh-CN/data/reusables/package_registry/about-spending-limits.md
+++ /dev/null
@@ -1 +0,0 @@
-默认情况下,您帐户对 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 综合使用支出限额为 0 美元。 若要允许超支,可以提高支出限额或允许无限支出。
diff --git a/translations/zh-CN/data/reusables/package_registry/accessing-packages.md b/translations/zh-CN/data/reusables/package_registry/accessing-packages.md
deleted file mode 100644
index c4ac2d7d5548..000000000000
--- a/translations/zh-CN/data/reusables/package_registry/accessing-packages.md
+++ /dev/null
@@ -1,4 +0,0 @@
-您可以通过以下 URL 访问您的包(使用您的 {% data variables.product.prodname_dotcom %} 用户或组织名称替换 `OWNER`,使用您的仓库名称替换 `REPOSITORY`):
- ```
- https://github.com/OWNER/REPOSITORY/packages
- ```
diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry.md b/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry.md
deleted file mode 100644
index 8f890e99b499..000000000000
--- a/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry.md
+++ /dev/null
@@ -1,18 +0,0 @@
-1. Create a new personal access token (PAT) with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token.
- - Select the `read:packages` scope to download container images and read their metadata.
- - Select the `write:packages` scope to download and upload container images and read and write their metadata.
- - Select the `delete:packages` scope to delete container images.
-
- 更多信息请参阅“[创建用于命令行的个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)。”
-
-2. Save your PAT. We recommend saving your PAT as an environment variable.
- ```shell
- $ export CR_PAT=YOUR_TOKEN
- ```
-3. Using the CLI for your container type, sign in to the {% data variables.product.prodname_github_container_registry %} service at `ghcr.io`.
- {% raw %}
- ```shell
- $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
- > Login Succeeded
- ```
- {% endraw %}
diff --git a/translations/zh-CN/data/reusables/permissions/admin-access-org.md b/translations/zh-CN/data/reusables/permissions/admin-access-org.md
deleted file mode 100644
index b4f934126644..000000000000
--- a/translations/zh-CN/data/reusables/permissions/admin-access-org.md
+++ /dev/null
@@ -1 +0,0 @@
-You must authenticate using an access token with the `admin:org` scope to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/permissions/admin-access.md b/translations/zh-CN/data/reusables/permissions/admin-access.md
deleted file mode 100644
index d35e7e24173c..000000000000
--- a/translations/zh-CN/data/reusables/permissions/admin-access.md
+++ /dev/null
@@ -1 +0,0 @@
-You must authenticate using an access token with the `repo` scope to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/permissions/code-scanning-app-read-permissions.md b/translations/zh-CN/data/reusables/permissions/code-scanning-app-read-permissions.md
deleted file mode 100644
index cbee5c312771..000000000000
--- a/translations/zh-CN/data/reusables/permissions/code-scanning-app-read-permissions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_github_app %}s must have the `security_events` read permission to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/permissions/read-access.md b/translations/zh-CN/data/reusables/permissions/read-access.md
deleted file mode 100644
index b6226713702c..000000000000
--- a/translations/zh-CN/data/reusables/permissions/read-access.md
+++ /dev/null
@@ -1 +0,0 @@
-对仓库具有读取权限的任何人都可以使用此端点。 如果是私有仓库,您的必须使用具有 `repo` 作用域的访问令牌。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/permissions/security-events-scope.md b/translations/zh-CN/data/reusables/permissions/security-events-scope.md
deleted file mode 100644
index a208a8e98059..000000000000
--- a/translations/zh-CN/data/reusables/permissions/security-events-scope.md
+++ /dev/null
@@ -1 +0,0 @@
-您必须使用具有 `security_events` 作用域的访问令牌才能使用此端点。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/permissions/write-access.md b/translations/zh-CN/data/reusables/permissions/write-access.md
deleted file mode 100644
index d35e7e24173c..000000000000
--- a/translations/zh-CN/data/reusables/permissions/write-access.md
+++ /dev/null
@@ -1 +0,0 @@
-You must authenticate using an access token with the `repo` scope to use this endpoint.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/pre-release-program/ant-man-preview-deployments.md b/translations/zh-CN/data/reusables/pre-release-program/ant-man-preview-deployments.md
deleted file mode 100644
index c94ec3ff8af4..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/ant-man-preview-deployments.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% note %}
-
-**Note:** The `transient_environment` and `production_environment` parameters are currently available for developers to preview. During the preview period, the API may change without advance notice. 有关完整详情,请参阅[博客文章](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements)。
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.ant-man-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/ant-man-preview-statuses.md b/translations/zh-CN/data/reusables/pre-release-program/ant-man-preview-statuses.md
deleted file mode 100644
index edadedc237e1..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/ant-man-preview-statuses.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% note %}
-
-**Note:** The `inactive` state and the `log_url`, `environment_url`, and `auto_inactive` parameters are currently available for developers to preview. 有关完整详情,请参阅[博客文章](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements)。
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.ant-man-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/antiope-preview.md b/translations/zh-CN/data/reusables/pre-release-program/antiope-preview.md
deleted file mode 100644
index 4c0be72ee067..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/antiope-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Checks API is currently available for developers to preview. During the preview period, the API may change without advance notice. 有关完整详情,请参阅[博客文章](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/)。 To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.antiope-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/baptiste-keys-preview.md b/translations/zh-CN/data/reusables/pre-release-program/baptiste-keys-preview.md
deleted file mode 100644
index 1a309066ba06..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/baptiste-keys-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** The `is_template` and `template_repository` keys are currently available for developer to preview. See [Create a repository using a template](/v3/repos/#create-a-repository-using-a-template) to learn how to create template repositories. To access these new response keys during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.baptiste-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/baptiste-preview.md b/translations/zh-CN/data/reusables/pre-release-program/baptiste-preview.md
deleted file mode 100644
index 850b3f271bb4..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/baptiste-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Creating and using repository templates is currently available for developers to preview. To access this new endpoint during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.baptiste-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/batman-preview.md b/translations/zh-CN/data/reusables/pre-release-program/batman-preview.md
deleted file mode 100644
index 079a5b57c932..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/batman-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
-{% note %}
-
-**Note:** Using the {% data variables.product.prodname_component_kit %} API is currently available for developers to preview. To access these endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.batman-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/checks-public-beta.md b/translations/zh-CN/data/reusables/pre-release-program/checks-public-beta.md
deleted file mode 100644
index 9220bede6270..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/checks-public-beta.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note:** The Checks API is currently in public beta and only available for use with GitHub Apps.
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/cloak-preview.md b/translations/zh-CN/data/reusables/pre-release-program/cloak-preview.md
deleted file mode 100644
index 53e95b0793c8..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/cloak-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Commit Search API is currently available for developers to preview. During the preview period, the APIs may change without advance notice. 有关完整详情,请参阅[博客文章](https://developer.github.com/changes/2017-01-05-commit-search-api/)。
-
-To access the API you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.cloak-preview
-```
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/code-scanning-beta.md b/translations/zh-CN/data/reusables/pre-release-program/code-scanning-beta.md
deleted file mode 100644
index f9be785c151b..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/code-scanning-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** {% data variables.product.prodname_code_scanning_capc %} for open source repositories and private repositories is currently in beta and subject to change. To sign up, see [Advanced Security beta](https://github.com/features/security/advanced-security/signup).
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/comfort-fade-preview.md b/translations/zh-CN/data/reusables/pre-release-program/comfort-fade-preview.md
deleted file mode 100644
index 17e2464a7d19..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/comfort-fade-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Multi-line comments in a pull request diff is currently available for developers to preview. To access the new response fields during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.comfort-fade-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/doctor-strange-preview.md b/translations/zh-CN/data/reusables/pre-release-program/doctor-strange-preview.md
deleted file mode 100644
index 488fa5418a94..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/doctor-strange-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "enterprise-server@2.20" %}
-{% note %}
-
-**Note:** New endpoints using OAuth tokens as input parameters instead of path parameters are available for developers to preview in the [OAuth Applications API](/v3/apps/oauth_applications/). To access these endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.doctor-strange-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/dorian-preview.md b/translations/zh-CN/data/reusables/pre-release-program/dorian-preview.md
deleted file mode 100644
index d4141e00a5ab..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/dorian-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Enabling and disabling dependency alerts for a repository using the REST API is currently available for developers to preview. To access these new endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.dorian-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/drax-preview.md b/translations/zh-CN/data/reusables/pre-release-program/drax-preview.md
deleted file mode 100644
index 720c942e5f60..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/drax-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.13" %}
-{% note %}
-
-**Note:** The [Licenses API](https://developer.github.com/changes/2015-03-09-licenses-api/) is currently available for developers to preview. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.drax-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/echo-preview.md b/translations/zh-CN/data/reusables/pre-release-program/echo-preview.md
deleted file mode 100644
index d6897f7f1d82..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/echo-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}
-{% note %}
-
-**Note:** The team discussions API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-02-07-team-discussions-api) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.echo-preview+json
-```
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/flash-preview.md b/translations/zh-CN/data/reusables/pre-release-program/flash-preview.md
deleted file mode 100644
index b19c0fb7321a..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/flash-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% note %}
-
-**Note:** New features in the Deployments API on {% data variables.product.product_name %} are currently available during a public beta. 有关完整详情,请参阅[博客文章](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)。
-
-To access the new `environment` parameter, the two new values for the `state` parameter (`in_progress` and `queued`), and use `auto_inactive` on production deployments during the public beta period, you must provide the following custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.flash-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/gambit-preview.md b/translations/zh-CN/data/reusables/pre-release-program/gambit-preview.md
deleted file mode 100644
index ae67b941174b..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/gambit-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %}
-{% note %}
-
-**Note:** Uninstalling {% data variables.product.prodname_github_app %}s and revoking an app's installation token are currently available for developers to preview. To access the new endpoint during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.gambit-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/giant-sentry-fist-pre-release.md b/translations/zh-CN/data/reusables/pre-release-program/giant-sentry-fist-pre-release.md
deleted file mode 100644
index 6ea06379025f..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/giant-sentry-fist-pre-release.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.8" %}
-{% note %}
-
-**Note:** {% data variables.giant-sentry-fist.product_name_long %} on {% data variables.product.product_name %} is currently available for developers to preview. To access the API, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.giant-sentry-fist-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/github-actions-public-beta.md b/translations/zh-CN/data/reusables/pre-release-program/github-actions-public-beta.md
deleted file mode 100644
index ff0a4b80f712..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/github-actions-public-beta.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% warning %}
-
-**New release:** {% data variables.product.prodname_actions %} is now available in a new limited public beta. This version offers a new workflow configuration and built-in continuous integration and continuous deployment capabilities. We strongly recommend you avoid using it for high-value workflows and content during this public beta period. To request to join the limited public beta, see the [GitHub Actions page](https://github.com/features/actions). For more information, see "[About GitHub Actions](/articles/about-github-actions)".
-
-GitHub Support will only provide support for the YAML syntax and no longer provides support for the HCL syntax.
-
-If you participated in the limited public beta and created workflows with the HCL syntax {% data variables.product.prodname_actions %}, you will need to upgrade to the new limited public beta that uses YAML syntax. When your repository is eligible to upgrade, you'll see an invitation in your repository. You must accept the invitation before you can use the new limited public beta.
-
-Once you've upgraded, any workflows that you created with the HCL syntax will need to be updated to the new YAML syntax. To automatically convert your workflows, see "[Migrating {% data variables.product.prodname_actions %} from HCL syntax to YAML syntax](/articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax)".
-
-{% endwarning %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/github-components-public-beta.md b/translations/zh-CN/data/reusables/pre-release-program/github-components-public-beta.md
deleted file mode 100644
index 2c242acbc08b..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/github-components-public-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
-{% note %}
-
-**Note:** The {% data variables.product.prodname_component_kit %} API is currently in private beta and subject to change.
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/groot-preview.md b/translations/zh-CN/data/reusables/pre-release-program/groot-preview.md
deleted file mode 100644
index 944243de7c52..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/groot-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Listing branches or pull requests for a commit in the Commits API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) for more details. To access the new endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.groot-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/hagar-preview.md b/translations/zh-CN/data/reusables/pre-release-program/hagar-preview.md
deleted file mode 100644
index e1cf318f3cc3..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/hagar-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}
-{% note %}
-
-**Note:** You can now retrieve someone's hovercard information in different contexts using the Hovercard API. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.hagar-preview+json
-```
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/hellcat-preview.md b/translations/zh-CN/data/reusables/pre-release-program/hellcat-preview.md
deleted file mode 100644
index b2268faa5418..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/hellcat-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %}
-{% note %}
-
-**Note:** The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.hellcat-preview+json
-```
-{% endnote %}
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/inertia-preview.md b/translations/zh-CN/data/reusables/pre-release-program/inertia-preview.md
deleted file mode 100644
index 2953c8de442f..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/inertia-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Projects API is currently available for developers to preview. During the preview period, the API may change without advance notice. 有关完整详情,请参阅[博客文章](https://developer.github.com/changes/2016-10-27-changes-to-projects-api)。 To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.inertia-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/london-preview.md b/translations/zh-CN/data/reusables/pre-release-program/london-preview.md
deleted file mode 100644
index 4fa608045abb..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/london-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Enabling or disabling automated security fixes is currently available for developers to preview. To access this new endpoint during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.london-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/luke-cage-preview.md b/translations/zh-CN/data/reusables/pre-release-program/luke-cage-preview.md
deleted file mode 100644
index a4a7cfe32bbb..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/luke-cage-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.luke-cage-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/lydian-preview.md b/translations/zh-CN/data/reusables/pre-release-program/lydian-preview.md
deleted file mode 100644
index fa5a34527bea..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/lydian-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Updating the pull request branch with latest upstream changes is currently available for developers to preview. To access this new endpoint during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.lydian-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/mercy-pre-release-replace.md b/translations/zh-CN/data/reusables/pre-release-program/mercy-pre-release-replace.md
deleted file mode 100644
index c49f66c4dba1..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/mercy-pre-release-replace.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** Repository topics on {% data variables.product.product_name %} are currently available for developers to preview. To use this endpoint, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.mercy-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/mercy-pre-release.md b/translations/zh-CN/data/reusables/pre-release-program/mercy-pre-release.md
deleted file mode 100644
index fa26dc8969ed..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/mercy-pre-release.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** {% data variables.mercy.product_name_long %} on {% data variables.product.product_name %} is currently available for developers to preview. To view the `topics` property in calls that return repository results, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.mercy-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/mister-fantastic-pre-release.md b/translations/zh-CN/data/reusables/pre-release-program/mister-fantastic-pre-release.md
deleted file mode 100644
index 4918b1477ee0..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/mister-fantastic-pre-release.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}
-{% note %}
-
-**Note:** {% data variables.mister-fantastic.product_name_long %} contains two additional fields in responses, which developers can preview: `html_url` and `source`. To see these two new fields, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.mister-fantastic-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/mockingbird-preview.md b/translations/zh-CN/data/reusables/pre-release-program/mockingbird-preview.md
deleted file mode 100644
index 7d0dd736932d..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/mockingbird-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The API to get issue timeline events is currently available for developers to preview. During the preview period, the APIs may change without advance notice. 有关完整详情,请参阅[博客文章](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)。 To access the API you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.mockingbird-preview
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/multi-line-comments-public-beta.md b/translations/zh-CN/data/reusables/pre-release-program/multi-line-comments-public-beta.md
deleted file mode 100644
index 5aeea167477b..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/multi-line-comments-public-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Multi-line comments on pull requests are currently in public beta and subject to change.
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/nebula-preview.md b/translations/zh-CN/data/reusables/pre-release-program/nebula-preview.md
deleted file mode 100644
index a3f822e627dd..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/nebula-preview.md
+++ /dev/null
@@ -1,14 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-
-{% note %}
-
-**Note:** You can set the visibility of a repository using the new `visibility` parameter in the [Repositories API](/v3/repos/), and get a repository's visibility with a new response key. 更多信息请参阅[博客帖子](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)。
-
-To access repository visibility during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.nebula-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/nightshade-preview.md b/translations/zh-CN/data/reusables/pre-release-program/nightshade-preview.md
deleted file mode 100644
index 22172eba6443..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/nightshade-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %}
-{% note %}
-
-**Note:** The [Repository Transfer API](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) is currently available for developers to preview. To access the API, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.nightshade-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/org-self-hosted-runner-beta.md b/translations/zh-CN/data/reusables/pre-release-program/org-self-hosted-runner-beta.md
deleted file mode 100644
index ad73731c18b6..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/org-self-hosted-runner-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% warning %}
-
-**警告:** 组织的自托管运行器 API 当前处于公开测试阶段,可能会发生变化。
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-deployment.md b/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-deployment.md
deleted file mode 100644
index 6a888df13e51..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-deployment.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** If a deployment is created via a {% data variables.product.prodname_github_app %}, the response will include the `performed_via_github_app` object with information about the {% data variables.product.prodname_github_app %}. For more information, see the [related blog post](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access).
-
-To receive the `performed_via_github_app` object in the response, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.machine-man-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue-comment.md b/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue-comment.md
deleted file mode 100644
index ad67d849dd85..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue-comment.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** If an issue comment is created via a {% data variables.product.prodname_github_app %}, the response will include the `performed_via_github_app` object with information about the {% data variables.product.prodname_github_app %}. For more information, see the [related blog post](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access).
-
-To receive the `performed_via_github_app` object in the response, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.machine-man-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue-event.md b/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue-event.md
deleted file mode 100644
index 54e004859064..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue-event.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** If an issue event is created via a {% data variables.product.prodname_github_app %}, the response will include the `performed_via_github_app` object with information about the {% data variables.product.prodname_github_app %}. For more information, see the [related blog post](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access).
-
-To receive the `performed_via_github_app` object in the response, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.machine-man-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue.md b/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue.md
deleted file mode 100644
index ee0240792f4a..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/performed-by-integration-issue.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** If an issue is opened via a {% data variables.product.prodname_github_app %}, the response will include the `performed_via_github_app` object with information about the {% data variables.product.prodname_github_app %}. For more information, see the [related blog post](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access).
-
-To receive the `performed_via_github_app` object in the response, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.machine-man-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/scarlet-witch-key-preview.md b/translations/zh-CN/data/reusables/pre-release-program/scarlet-witch-key-preview.md
deleted file mode 100644
index a82019b82319..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/scarlet-witch-key-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** Developers can preview a new `code_of_conduct` key in responses. For more information, see [Codes of Conduct API](/v3/codes_of_conduct/).
-
-To access this new response key during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.scarlet-witch-preview+json
-```
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/scarlet-witch-preview.md b/translations/zh-CN/data/reusables/pre-release-program/scarlet-witch-preview.md
deleted file mode 100644
index 860b30d517dc..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/scarlet-witch-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The Codes of Conduct API is currently available for developers to preview.
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.scarlet-witch-preview+json
-```
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/shadow-cat-preview.md b/translations/zh-CN/data/reusables/pre-release-program/shadow-cat-preview.md
deleted file mode 100644
index 3d95ab9ccae5..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/shadow-cat-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %}
-{% note %}
-
-**Note:** The Draft Pull Request API is currently available for developers to preview. You can use this API to create a draft pull request or see whether a pull request is in draft state. See the [blog post](https://developer.github.com/changes/2019-02-14-draft-pull-requests) preview for more details. To access the new `draft` parameter during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.shadow-cat-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/sombra-preview.md b/translations/zh-CN/data/reusables/pre-release-program/sombra-preview.md
deleted file mode 100644
index 9298dfa844f5..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/sombra-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** The Interactions API is currently in public preview. See the [blog post](https://developer.github.com/changes/2018-12-18-interactions-preview) preview for more details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.sombra-preview
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/squirrel-girl-preview.md b/translations/zh-CN/data/reusables/pre-release-program/squirrel-girl-preview.md
deleted file mode 100644
index 52bd9558fc3b..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/squirrel-girl-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** APIs for managing reactions are currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2016-05-12-reactions-api-preview) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
- ```
- application/vnd.github.squirrel-girl-preview+json
- ```
- {% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/squirrel-girl-response-preview.md b/translations/zh-CN/data/reusables/pre-release-program/squirrel-girl-response-preview.md
deleted file mode 100644
index 18d162292a2d..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/squirrel-girl-response-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The [reactions API](/v3/reactions/) is available for developers to preview. The `url` can be used to construct the API location for [listing and creating](/v3/reactions) reactions. See the [blog post](https://developer.github.com/changes/2016-05-12-reactions-api-preview) for full details. To receive the `reactions` object in the response for this endpoint you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.squirrel-girl-preview
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/superpro-preview.md b/translations/zh-CN/data/reusables/pre-release-program/superpro-preview.md
deleted file mode 100644
index f0878ed234c6..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/superpro-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% note %}
-
-**Note:** The [Global Webhooks API](/rest/reference/enterprise-admin#global-webhooks) is currently available for developers to preview. To access the API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header:
-
-```
-application/vnd.github.superpro-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/surtur-preview.md b/translations/zh-CN/data/reusables/pre-release-program/surtur-preview.md
deleted file mode 100644
index 9cfdfe8ad8dc..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/surtur-preview.md
+++ /dev/null
@@ -1,21 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-{% note %}
-
-**Note:** New repository creation permissions are available to preview. You can now use `members_can_create_public_repositories`, `members_can_create_private_repositories`, and `members_can_create_internal_repositories`. You can only allow members to create internal repositories if your organization is associated with an enterprise account using {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %} 2.20+. These parameters provide more granular permissions to configure the type of repositories organization members can create.
-
-To access these new parameters during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.surtur-preview+json
-```
-{% endnote %}
-{% else %}
-{% note %}
-
-**Note:** New repository creation permissions are available to preview. You can now set the `members_allowed_repository_creation_type` parameter to configure whether organization members can create repositories and the type of repositories they can create.
-
-To access this new parameter during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.surtur-preview+json
-```
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/switcheroo-preview.md b/translations/zh-CN/data/reusables/pre-release-program/switcheroo-preview.md
deleted file mode 100644
index fbbbe3817bd9..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/switcheroo-preview.md
+++ /dev/null
@@ -1,8 +0,0 @@
-{% note %}
-
-**Note:** Enabling and disabling Pages in the Pages API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) preview for more details. To access the new endpoints during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.switcheroo-preview+json
-```
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/symmetra-preview.md b/translations/zh-CN/data/reusables/pre-release-program/symmetra-preview.md
deleted file mode 100644
index c578f33898be..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/symmetra-preview.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% if currentVersion != ‘dotcom’ and currentVersion ver_lt "enterprise-server@2.20" %}
-{% note %}
-
-**Note:** You can add or edit descriptions in labels. See the [blog post](https://developer.github.com/changes/2018-02-22-label-description-search-preview) for full details. To access this feature during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.symmetra-preview+json
-```
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/thor-pre-release.md b/translations/zh-CN/data/reusables/pre-release-program/thor-pre-release.md
deleted file mode 100644
index e034ce622e48..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/thor-pre-release.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.13" %}
-{% note %}
-
-**Note:** Team-based review requests in the Review Requests API on {% data variables.product.product_name %} are currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-07-26-team-review-request-thor-preview) for full details.
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.thor-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/usage-api-beta.md b/translations/zh-CN/data/reusables/pre-release-program/usage-api-beta.md
deleted file mode 100644
index 0fb7989fc11c..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/usage-api-beta.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% warning %}
-
-**Warning:** This {% data variables.product.prodname_actions %} usage endpoint is currently in public beta and subject to change. For more information, see "[GitHub Actions API workflow usage](https://developer.github.com/changes/2020-05-15-actions-api-workflow-usage)."
-
-{% endwarning %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/wyandotte-preview.md b/translations/zh-CN/data/reusables/pre-release-program/wyandotte-preview.md
deleted file mode 100644
index 2d5c90f982c3..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/wyandotte-preview.md
+++ /dev/null
@@ -1,10 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** To access the Migrations API, you must provide a custom [media type](/v3/media) in the `Accept` header:
-```
-application/vnd.github.wyandotte-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/x-ray-preview.md b/translations/zh-CN/data/reusables/pre-release-program/x-ray-preview.md
deleted file mode 100644
index c09b481483ca..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/x-ray-preview.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% if currentVersion != "free-pro-team@latest" %}
-{% note %}
-
-**Note:** When a GitHub Enterprise instance is in private mode, site and repository administrators can enable anonymous Git access for a public repository. This feature is currently available for developers to preview. See the [blog post](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/) for full details.
-
-To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.x-ray-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pre-release-program/zzzax-preview.md b/translations/zh-CN/data/reusables/pre-release-program/zzzax-preview.md
deleted file mode 100644
index 1614b2e1532d..000000000000
--- a/translations/zh-CN/data/reusables/pre-release-program/zzzax-preview.md
+++ /dev/null
@@ -1,11 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.12" %}
-{% note %}
-
-**Note:** Protected Branches API can now manage a setting for requiring signed commits. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) for full details. To access the API during the preview period, you must provide a custom [media type](/v3/media) in the `Accept` header:
-
-```
-application/vnd.github.zzzax-preview+json
-```
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pulls/diff_location.md b/translations/zh-CN/data/reusables/pulls/diff_location.md
deleted file mode 100644
index 18c8c130d5dc..000000000000
--- a/translations/zh-CN/data/reusables/pulls/diff_location.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% note %}
-
-**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API offers the `application/vnd.github.v3.diff` [media type](/v3/media/#commits-commit-comparison-and-pull-requests). 要查看拉取请求差异,请将此媒体类型添加到[单一拉取请求](/v3/pulls/#get-a-pull-request)端点的 `Accept` 标头。
-
-`position` 值等于要添加注释的文件中从第一个 "@@" 块标头向下的行数。 "@@" 行正下方的行是位置 1,下一行是位置 2,依此类推。 差异中的位置继续通过空白行和附加块继续增加,直到新文件开始。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pulls/multiline_comments_summary_for_responses.md b/translations/zh-CN/data/reusables/pulls/multiline_comments_summary_for_responses.md
deleted file mode 100644
index bafcecefc018..000000000000
--- a/translations/zh-CN/data/reusables/pulls/multiline_comments_summary_for_responses.md
+++ /dev/null
@@ -1,21 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
-
-##### 多行评论摘要
-
-{% note %}
-
-**注:**开发人员可以预览新的参数和响应字段。 在预览期间,这些响应字段可能会更改,恕不提前通知。 有关完整详情,请参阅[博客文章](https://developer.github.com/changes/2019-10-03-multi-line-comments)。
-
-{% endnote %}
-
-使用 `comfort-fade` 预览标头和 `line` 参数在响应中显示多行评论支持的字段。
-
-如果使用 `comfort-fade` 预览标头,您的响应将显示:
-- 对于多行评论,显示 `start_line`、`original_start_line`、`start_side`、`line`、`original_line` 和 `side` 的值。
-- 对于单行评论,显示 `line`、`original_line` 和 `side` 的值,以及 `start_line`、`original_start_line` 和 `start_side` 的 `null` 值。
-
-如果不使用 `comfort-fade` 预览标头,多行和单行评论将在具有单个 `position` 属性的响应中以相同的方式显示。 您的响应将会显示:
-- 对于多行评论,显示 `position` 属性的评论范围的最后一行。
-- For single-line comments, the diff-positioned way of referencing comments for the `position` attribute. 更多信息请参阅[输入参数](/v3/pulls/comments/#parameters-2)表中的 `position`。
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pulls/pull_request_access.md b/translations/zh-CN/data/reusables/pulls/pull_request_access.md
deleted file mode 100644
index 7938d686c5bd..000000000000
--- a/translations/zh-CN/data/reusables/pulls/pull_request_access.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-
-要在公共仓库中打开或更新拉取请求,您必须对头部或源分支具有写入访问权限。 对于组织拥有的仓库,您必须是拥有该仓库的组织的成员才能打开或更新拉取请求。
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/pulls/pull_request_mergeability.md b/translations/zh-CN/data/reusables/pulls/pull_request_mergeability.md
deleted file mode 100644
index 1ce16ace0c7c..000000000000
--- a/translations/zh-CN/data/reusables/pulls/pull_request_mergeability.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注:**您需要明确[请求拉取请求](/v3/pulls/#get-a-pull-request)以触发测试合并提交,检查拉取请求的可合并性。 更多信息请参阅“[检查拉取请求的可合并性](/v3/git/#checking-mergeability-of-pull-requests)”。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/pulls/pullrequests_as_issues.md b/translations/zh-CN/data/reusables/pulls/pullrequests_as_issues.md
deleted file mode 100644
index ccc51e284311..000000000000
--- a/translations/zh-CN/data/reusables/pulls/pullrequests_as_issues.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% note %}
-
-**Note**: GitHub's REST API considers every pull request an issue, but not every issue is a pull request. 因此,“议题”端点可能返回响应中的议题和拉取请求。 您可以通过 `pull_request` 键识别拉取请求。
-
-请注意,从“议题”端点返回的拉取请求的 `id` 将是 _issue id_。 要查找拉取请求 id,请使用“[列出拉取请求](/v3/pulls/#list-pull-requests)”端点。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/reminders/install-slack.md b/translations/zh-CN/data/reusables/reminders/install-slack.md
deleted file mode 100644
index 0b6f1c886cc6..000000000000
--- a/translations/zh-CN/data/reusables/reminders/install-slack.md
+++ /dev/null
@@ -1 +0,0 @@
-如果要在所有仓库安装 Slack,请选择 **All repositories(所有仓库)**。 如果只想在选择的仓库中安装 Slack,则选择 **Only select repositories(仅选定仓库)**。 然后,查看您允许 Slack 访问的权限列表并单击 **Install(安装)**。 ![安装 Slack 按钮](/assets/images/help/settings/scheduled-reminders-install-slack.png)
diff --git a/translations/zh-CN/data/reusables/reminders/scheduled-reminders-beta.md b/translations/zh-CN/data/reusables/reminders/scheduled-reminders-beta.md
deleted file mode 100644
index 700ce5808414..000000000000
--- a/translations/zh-CN/data/reusables/reminders/scheduled-reminders-beta.md
+++ /dev/null
@@ -1 +0,0 @@
-拉取请求的预定提醒正在测试中,可能会有更改。 要申请参加预定提醒的下一个测试阶段,请在 [GitHub 预定提醒](https://github.com/features/reminders/signup)加入等待列表。
diff --git a/translations/zh-CN/data/reusables/repositories/actions-new-workflow.md b/translations/zh-CN/data/reusables/repositories/actions-new-workflow.md
deleted file mode 100644
index 0489b25a781b..000000000000
--- a/translations/zh-CN/data/reusables/repositories/actions-new-workflow.md
+++ /dev/null
@@ -1,2 +0,0 @@
-1. 在左上角单击 **New workflow(新建工作流程)**。 ![创建新工作流程](/assets/images/help/repository/actions-new-workflow.png)
-
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/repositories/actions-set-up-workflow-template.md b/translations/zh-CN/data/reusables/repositories/actions-set-up-workflow-template.md
deleted file mode 100644
index e83050d31324..000000000000
--- a/translations/zh-CN/data/reusables/repositories/actions-set-up-workflow-template.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 在您想要使用的模板名称下,单击 **Set up this workflow(设置此工作流程)**。 ![Node.js 模板建议](/assets/images/help/repository/actions-recommended-workflow-template.png)
diff --git a/translations/zh-CN/data/reusables/repositories/opt-out-automated-security-updates.md b/translations/zh-CN/data/reusables/repositories/opt-out-automated-security-updates.md
deleted file mode 100644
index 3256fd9eeb0a..000000000000
--- a/translations/zh-CN/data/reusables/repositories/opt-out-automated-security-updates.md
+++ /dev/null
@@ -1,2 +0,0 @@
-1. 在“Automated security updates(自动安全更新)”下,选择或取消选择 **Opt out of automated security updates(退出自动安全更新)**。 ![选择退出自动安全更新复选框](/assets/images/help/repository/opt-out-automated-security-updates.png)
-2. 单击 **Save(保存)**。
diff --git a/translations/zh-CN/data/reusables/repositories/opt-out-dependabot-security-updates.md b/translations/zh-CN/data/reusables/repositories/opt-out-dependabot-security-updates.md
deleted file mode 100644
index 3a68c3c20731..000000000000
--- a/translations/zh-CN/data/reusables/repositories/opt-out-dependabot-security-updates.md
+++ /dev/null
@@ -1 +0,0 @@
-1. To the right of "{% data variables.product.prodname_dependabot_short %} security updates", click **Disable all** or **Enable all**. !["Disable all" or "Enable all" button for {% data variables.product.prodname_dependabot_short %} security updates](/assets/images/help/repository/opt-out-dependabot-security-updates.png)
diff --git a/translations/zh-CN/data/reusables/repositories/settings-security-and-analysis-tab-beta.md b/translations/zh-CN/data/reusables/repositories/settings-security-and-analysis-tab-beta.md
deleted file mode 100644
index a87278175cef..000000000000
--- a/translations/zh-CN/data/reusables/repositories/settings-security-and-analysis-tab-beta.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注**:管理安全和分析设置的新功能处于测试阶段,可能会有变动。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-integrations-and-services.md b/translations/zh-CN/data/reusables/repositories/sidebar-integrations-and-services.md
deleted file mode 100644
index b76bd9f19176..000000000000
--- a/translations/zh-CN/data/reusables/repositories/sidebar-integrations-and-services.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 单击 **Integrations & Services(集成和服务)**。 ![集成和服务选择](/assets/images/help/settings/integrations_and_services_menu.png)
diff --git a/translations/zh-CN/data/reusables/repositories/troubleshooting-dependency-graph.md b/translations/zh-CN/data/reusables/repositories/troubleshooting-dependency-graph.md
deleted file mode 100644
index 6607b47d2b06..000000000000
--- a/translations/zh-CN/data/reusables/repositories/troubleshooting-dependency-graph.md
+++ /dev/null
@@ -1 +0,0 @@
-如果您的项目有依赖关系,但在图表中未检测到依赖关系,则可能是包含依赖关系的文件有问题。 检查项目的文件以确保其格式对文件类型是正确的。
diff --git a/translations/zh-CN/data/reusables/repositories/you-can-enable-or-disable-security-features.md b/translations/zh-CN/data/reusables/repositories/you-can-enable-or-disable-security-features.md
deleted file mode 100644
index 7380459e1916..000000000000
--- a/translations/zh-CN/data/reusables/repositories/you-can-enable-or-disable-security-features.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注**:代码扫描和密码扫描测试版新增了管理安全和分析设置的功能。 如果您正在参与测试,请跳过以下步骤,并参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/repositories/you-can-manage-access-to-security-alerts.md b/translations/zh-CN/data/reusables/repositories/you-can-manage-access-to-security-alerts.md
deleted file mode 100644
index 60ccfc3c01fb..000000000000
--- a/translations/zh-CN/data/reusables/repositories/you-can-manage-access-to-security-alerts.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注**:代码扫描和密码扫描测试版新增了管理具有安全警报访问权限的人员及团队的功能。 如果您正在参与测试,请跳过以下步骤,并参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-github-dependabot-alerts)”。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/saml/scim-unavailable-for-enterprise-accounts.md b/translations/zh-CN/data/reusables/saml/scim-unavailable-for-enterprise-accounts.md
deleted file mode 100644
index f5af0d8ed5cb..000000000000
--- a/translations/zh-CN/data/reusables/saml/scim-unavailable-for-enterprise-accounts.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**注**:SCIM 支持目前不适用于 {% data variables.product.prodname_dotcom %} 上的企业帐户。
-
-{% endnote %}
diff --git a/translations/zh-CN/data/reusables/scim/complete_user_example.md b/translations/zh-CN/data/reusables/scim/complete_user_example.md
deleted file mode 100644
index e444e167ecc8..000000000000
--- a/translations/zh-CN/data/reusables/scim/complete_user_example.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<%= json \ "schemas":["urn:ietf:params:scim:schemas:core:2.0:User"], "userName":"mona.octocat@okta.example.com", "name":{ "familyName":"Octocat", "givenName":"Mona" }, "emails":[
- {
- "value":"mona.octocat@okta.example.com",
- "type":"work",
- "primary": true
- }
- ] %>
diff --git a/translations/zh-CN/data/reusables/scim/user_required_values.md b/translations/zh-CN/data/reusables/scim/user_required_values.md
deleted file mode 100644
index 06e7fd92a8ca..000000000000
--- a/translations/zh-CN/data/reusables/scim/user_required_values.md
+++ /dev/null
@@ -1 +0,0 @@
-如以下示例所示,您必须至少提供用户的必要值:`userName`、`name` 和 `emails`。
diff --git a/translations/zh-CN/data/reusables/search/exact-match-beta.md b/translations/zh-CN/data/reusables/search/exact-match-beta.md
deleted file mode 100644
index 369be0d54947..000000000000
--- a/translations/zh-CN/data/reusables/search/exact-match-beta.md
+++ /dev/null
@@ -1 +0,0 @@
-代码搜索中的精确匹配在测试阶段,只面向 {% data variables.product.prodname_dotcom %} 上有限的用户和仓库,可能会有更改。
diff --git a/translations/zh-CN/data/reusables/search/exact-match.md b/translations/zh-CN/data/reusables/search/exact-match.md
deleted file mode 100644
index 5b193e43efc1..000000000000
--- a/translations/zh-CN/data/reusables/search/exact-match.md
+++ /dev/null
@@ -1 +0,0 @@
-您可以搜索包含任何字母、数字和符号组合的精确匹配代码。
diff --git a/translations/zh-CN/data/reusables/shortdesc/2fa.md b/translations/zh-CN/data/reusables/shortdesc/2fa.md
deleted file mode 100644
index ebe6b6b59371..000000000000
--- a/translations/zh-CN/data/reusables/shortdesc/2fa.md
+++ /dev/null
@@ -1 +0,0 @@
-如果您设置了双重身份验证,则此端点的基本身份验证会要求您使用一次性密码 (OTP) 以及您的用户名和密码,而不是令牌。 更多信息请参阅“[使用双重身份验证](/v3/auth/#working-with-two-factor-authentication)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/shortdesc/content_reference_body.md b/translations/zh-CN/data/reusables/shortdesc/content_reference_body.md
deleted file mode 100644
index 4b89190d30bf..000000000000
--- a/translations/zh-CN/data/reusables/shortdesc/content_reference_body.md
+++ /dev/null
@@ -1 +0,0 @@
-You have used an email that already exists for the user_email_uniq field.\n \## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n\ self.save()
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/shortdesc/content_reference_title.md b/translations/zh-CN/data/reusables/shortdesc/content_reference_title.md
deleted file mode 100644
index 531d7aabf6de..000000000000
--- a/translations/zh-CN/data/reusables/shortdesc/content_reference_title.md
+++ /dev/null
@@ -1 +0,0 @@
-[A-1234] Error found in core/models.py file
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/sponsors/email-submit-bank-info.md b/translations/zh-CN/data/reusables/sponsors/email-submit-bank-info.md
deleted file mode 100644
index 8824d6656e00..000000000000
--- a/translations/zh-CN/data/reusables/sponsors/email-submit-bank-info.md
+++ /dev/null
@@ -1 +0,0 @@
-加入 {% data variables.product.prodname_sponsors %} 后,您会收到一封电子邮件,其中包含有关提交您的银行和税务信息的说明。
diff --git a/translations/zh-CN/data/reusables/sponsors/matching-period.md b/translations/zh-CN/data/reusables/sponsors/matching-period.md
deleted file mode 100644
index b32073fb0dac..000000000000
--- a/translations/zh-CN/data/reusables/sponsors/matching-period.md
+++ /dev/null
@@ -1 +0,0 @@
-在个人参与 {% data variables.product.prodname_sponsors %} 的第一年,赞助资格匹配可能受限于此处规定的限制。 在 {% data variables.product.company_short %} 许可帐户使用 {% data variables.product.prodname_sponsors %}(可发布帐户的赞助个人资料)之后开始资格匹配。 匹配期不能因任何原因而延长。 如果您离开 {% data variables.product.prodname_sponsors %} 后重新加入,参与期与匹配期之间可能有差距,或者您的匹配期可能过期。
diff --git a/translations/zh-CN/data/reusables/sponsors/org-sponsorship-dashboard.md b/translations/zh-CN/data/reusables/sponsors/org-sponsorship-dashboard.md
deleted file mode 100644
index aaaa68a03301..000000000000
--- a/translations/zh-CN/data/reusables/sponsors/org-sponsorship-dashboard.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 在组织的右侧,单击 **Sponsorship dashboard(赞助仪表板)**。 ![赞助仪表板按钮](/assets/images/help/sponsors/org-sponsorship-dashboard.png)
diff --git a/translations/zh-CN/data/reusables/support/advanced-security-support-terms-differ.md b/translations/zh-CN/data/reusables/support/advanced-security-support-terms-differ.md
deleted file mode 100644
index 27879d29e768..000000000000
--- a/translations/zh-CN/data/reusables/support/advanced-security-support-terms-differ.md
+++ /dev/null
@@ -1 +0,0 @@
-本文的条款不适用于 {% data variables.product.prodname_advanced_security %} 的支持服务。 更多信息请参阅“[关于 {% data variables.product.prodname_advanced_security %} 的支持](/enterprise/admin/enterprise-support/about-support-for-advanced-security)”。
diff --git a/translations/zh-CN/data/reusables/support/ghec-premium-priority-high-description.md b/translations/zh-CN/data/reusables/support/ghec-premium-priority-high-description.md
deleted file mode 100644
index 7833873a9167..000000000000
--- a/translations/zh-CN/data/reusables/support/ghec-premium-priority-high-description.md
+++ /dev/null
@@ -1 +0,0 @@
-在 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业的帐户或安全问题对您的业务产生了有限的影响。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/ghec-premium-priority-high-examples.md b/translations/zh-CN/data/reusables/support/ghec-premium-priority-high-examples.md
deleted file mode 100644
index e82374be2180..000000000000
--- a/translations/zh-CN/data/reusables/support/ghec-premium-priority-high-examples.md
+++ /dev/null
@@ -1 +0,0 @@
-- 组织或企业所有者无意中删除了组织
- 组织或企业成员在提交、议题、拉取请求或议题附件中上传了敏感数据
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/ghec-premium-priority-low-description.md b/translations/zh-CN/data/reusables/support/ghec-premium-priority-low-description.md
deleted file mode 100644
index 44ceb3fc3033..000000000000
--- a/translations/zh-CN/data/reusables/support/ghec-premium-priority-low-description.md
+++ /dev/null
@@ -1 +0,0 @@
-您对于 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业有问题或建议,但并不紧迫,或者该问题不影响团队的生产力。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/ghec-premium-priority-low-examples.md b/translations/zh-CN/data/reusables/support/ghec-premium-priority-low-examples.md
deleted file mode 100644
index 746049c6218e..000000000000
--- a/translations/zh-CN/data/reusables/support/ghec-premium-priority-low-examples.md
+++ /dev/null
@@ -1 +0,0 @@
-- 您的组织或企业过度使用资源
- 请求状态检查
- 您的组织或企业在使用 Gist、通知、wiki、{% data variables.product.prodname_pages %}、{% data variables.product.prodname_desktop %}、Atom 或其他外围服务或功能方面需要帮助
- 功能请求
- 产品反馈
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/ghec-premium-priority-normal-description.md b/translations/zh-CN/data/reusables/support/ghec-premium-priority-normal-description.md
deleted file mode 100644
index 6be8fa03365d..000000000000
--- a/translations/zh-CN/data/reusables/support/ghec-premium-priority-normal-description.md
+++ /dev/null
@@ -1 +0,0 @@
-在 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业成员使用 {% data variables.product.prodname_dotcom_the_website %} 时遇到了有限或普通问题,或者您对于自己的组织或企业有一般性疑虑或问题。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/ghec-premium-priority-normal-examples.md b/translations/zh-CN/data/reusables/support/ghec-premium-priority-normal-examples.md
deleted file mode 100644
index 5b858db82417..000000000000
--- a/translations/zh-CN/data/reusables/support/ghec-premium-priority-normal-examples.md
+++ /dev/null
@@ -1 +0,0 @@
-- 有关为组织或企业使用 API 和功能的问题
- 有关 {% data variables.product.company_short %} 提供的组织数据迁移工具的问题
- 组织或企业的相关功能未按预期工作
- 有关组织或企业的一般安全问题
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/ghec-premium-priority-urgent-description.md b/translations/zh-CN/data/reusables/support/ghec-premium-priority-urgent-description.md
deleted file mode 100644
index 26dafe1cc986..000000000000
--- a/translations/zh-CN/data/reusables/support/ghec-premium-priority-urgent-description.md
+++ /dev/null
@@ -1 +0,0 @@
-在 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业的生产工作流程由于严重服务错误或中断而失败,并且该失败直接影响您的业务运营。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/ghec-premium-priority-urgent-examples.md b/translations/zh-CN/data/reusables/support/ghec-premium-priority-urgent-examples.md
deleted file mode 100644
index 1758586a3e9f..000000000000
--- a/translations/zh-CN/data/reusables/support/ghec-premium-priority-urgent-examples.md
+++ /dev/null
@@ -1 +0,0 @@
-- {% data variables.product.prodname_dotcom_the_website %} 上的错误或中断影响您组织或企业所有成员的核心 Git 或 web 应用程序功能
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/github-one-premium-plus-response-times-differ.md b/translations/zh-CN/data/reusables/support/github-one-premium-plus-response-times-differ.md
deleted file mode 100644
index 63a153624d38..000000000000
--- a/translations/zh-CN/data/reusables/support/github-one-premium-plus-response-times-differ.md
+++ /dev/null
@@ -1 +0,0 @@
-对于购买 {% data variables.product.prodname_ghe_one %} 的客户,对 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_insights %}、{% data variables.product.prodname_learning %} 和 {% data variables.product.prodname_registry %} 的支持服务为每周 5 天,每天 24 小时,不包括周末和美国国家法定节假日。 标准响应时间为 1 个工作日
diff --git a/translations/zh-CN/data/reusables/support/github-one-premium-plus-sla-differs.md b/translations/zh-CN/data/reusables/support/github-one-premium-plus-sla-differs.md
deleted file mode 100644
index cba18a090a6d..000000000000
--- a/translations/zh-CN/data/reusables/support/github-one-premium-plus-sla-differs.md
+++ /dev/null
@@ -1 +0,0 @@
-对于购买 {% data variables.product.prodname_ghe_one %} 的客户,{% data variables.contact.premium_support %} 的初始响应时间 SLA 不适用于 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_insights %}、{% data variables.product.prodname_learning %} 或 {% data variables.product.prodname_registry %} 事件单。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/support/github-one-premium-plus-support-terms-differ.md b/translations/zh-CN/data/reusables/support/github-one-premium-plus-support-terms-differ.md
deleted file mode 100644
index fb4e6cab9349..000000000000
--- a/translations/zh-CN/data/reusables/support/github-one-premium-plus-support-terms-differ.md
+++ /dev/null
@@ -1 +0,0 @@
-对于购买 {% data variables.product.prodname_ghe_one %} 的客户,{% data variables.product.premium_plus_support_plan %} 的支持条款不同于 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_insights %}、{% data variables.product.prodname_learning %} 和 {% data variables.product.prodname_registry %} 的支持条款。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/teams/team-sync.md b/translations/zh-CN/data/reusables/teams/team-sync.md
deleted file mode 100644
index be08a6112626..000000000000
--- a/translations/zh-CN/data/reusables/teams/team-sync.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
- **注:**当您为具有组织身份提供程序 (IdP) 的团队设置了团队同步时,如果尝试使用 API 更改团队的成员身份,则会看到错误。 如果您有权访问 IdP 中的组成员身份,可以通过身份提供程序管理 GitHub 团队成员身份,该提供程序会自动添加和删除组织的成员。 更多信息请参阅“[在身份提供程序与 GitHub 之间同步团队](/articles/synchronizing-teams-between-your-identity-provider-and-github/)”。
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/user-settings/throttling-notice.md b/translations/zh-CN/data/reusables/user-settings/throttling-notice.md
deleted file mode 100644
index f858b00d9bfa..000000000000
--- a/translations/zh-CN/data/reusables/user-settings/throttling-notice.md
+++ /dev/null
@@ -1 +0,0 @@
-此端点触发[通知](/articles/about-notifications/)。 使用此端点创建内容过快可能会导致滥用率限制。 See "[Abuse rate limits](/v3/#abuse-rate-limits)"{% if currentVersion == "free-pro-team@latest" %} and "[Dealing with abuse rate limits](/v3/guides/best-practices-for-integrators/#dealing-with-abuse-rate-limits)"{% endif %} for details.
diff --git a/translations/zh-CN/data/reusables/webhooks/interactive_component_short_desc.md b/translations/zh-CN/data/reusables/webhooks/interactive_component_short_desc.md
deleted file mode 100644
index 6ec63523f5cd..000000000000
--- a/translations/zh-CN/data/reusables/webhooks/interactive_component_short_desc.md
+++ /dev/null
@@ -1 +0,0 @@
-Triggered when a user clicks an interactive element that was created using the {% data variables.product.prodname_component_kit %}. {% data variables.product.prodname_github_app %}s are automatically subscribed to the `interactive_component` event so there's no need to manually subscribe to this event. Unlike other webhook events, the `interactive_component` event is only sent to the {% data variables.product.prodname_github_app %} that a user interacted with through an interactive component, such as in a composable comment. {% data variables.product.prodname_oauth_app %}s cannot subscribe to the `interactive_component` event and other installed {% data variables.product.prodname_github_app %}s will not receive the webhook event even if they subscribed to `interactive_component`.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/webhooks/issue_comment_event_api_properties.md b/translations/zh-CN/data/reusables/webhooks/issue_comment_event_api_properties.md
deleted file mode 100644
index a1ba5e394e0f..000000000000
--- a/translations/zh-CN/data/reusables/webhooks/issue_comment_event_api_properties.md
+++ /dev/null
@@ -1,3 +0,0 @@
-| 键 | 类型 | 描述 |
-| -------- | ----- | ---------------------------------------------------------------------- |
-| `action` | `字符串` | The action that was performed on the comment. Can be one of `created`. |
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/webhooks/package_short_desc.md b/translations/zh-CN/data/reusables/webhooks/package_short_desc.md
deleted file mode 100644
index 9b2e7ed32efb..000000000000
--- a/translations/zh-CN/data/reusables/webhooks/package_short_desc.md
+++ /dev/null
@@ -1 +0,0 @@
-Activity related to GitHub Packages. {% data reusables.webhooks.action_type_desc %} For more information, see "[GitHub Packages](/packages)".
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_forked_repos_link.md b/translations/zh-CN/data/reusables/webhooks/pull_request_forked_repos_link.md
deleted file mode 100644
index 0fad1bebc3a1..000000000000
--- a/translations/zh-CN/data/reusables/webhooks/pull_request_forked_repos_link.md
+++ /dev/null
@@ -1 +0,0 @@
-See [below](#pull-request-events-for-forked-repositories) to learn how this event works with forked repositories.
\ No newline at end of file
diff --git a/translations/zh-CN/data/variables/ant-man.yml b/translations/zh-CN/data/variables/ant-man.yml
deleted file mode 100644
index fd9020681ae1..000000000000
--- a/translations/zh-CN/data/variables/ant-man.yml
+++ /dev/null
@@ -1,3 +0,0 @@
----
-deployments-ant-man-parameter-note: >-
- {% if currentVersion == "free-pro-team@latest" %}**Note:** This parameter requires you to use the [`application/vnd.github.ant-man-preview+json`](/v3/previews/#enhanced-deployments) custom media type.{% endif %}
diff --git a/translations/zh-CN/data/variables/cloud-9.yml b/translations/zh-CN/data/variables/cloud-9.yml
deleted file mode 100644
index 514cc607691b..000000000000
--- a/translations/zh-CN/data/variables/cloud-9.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The SCIM API
diff --git a/translations/zh-CN/data/variables/giant-sentry-fist.yml b/translations/zh-CN/data/variables/giant-sentry-fist.yml
deleted file mode 100644
index ae3a16bbeb72..000000000000
--- a/translations/zh-CN/data/variables/giant-sentry-fist.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The User Blocking API
diff --git a/translations/zh-CN/data/variables/korra.yml b/translations/zh-CN/data/variables/korra.yml
deleted file mode 100644
index a0e37a535b50..000000000000
--- a/translations/zh-CN/data/variables/korra.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The Organization Membership API
diff --git a/translations/zh-CN/data/variables/mercy.yml b/translations/zh-CN/data/variables/mercy.yml
deleted file mode 100644
index 0076f284e63b..000000000000
--- a/translations/zh-CN/data/variables/mercy.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The `topics` property for repositories
diff --git a/translations/zh-CN/data/variables/mister-fantastic.yml b/translations/zh-CN/data/variables/mister-fantastic.yml
deleted file mode 100644
index 5040343f790d..000000000000
--- a/translations/zh-CN/data/variables/mister-fantastic.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The GitHub Pages API
diff --git a/translations/zh-CN/data/variables/performed-via-integration.yml b/translations/zh-CN/data/variables/performed-via-integration.yml
deleted file mode 100644
index c2d523e86a75..000000000000
--- a/translations/zh-CN/data/variables/performed-via-integration.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: An additional `performed_via_github_app` object in the issue payload
diff --git a/translations/zh-CN/data/variables/valkyrie.yml b/translations/zh-CN/data/variables/valkyrie.yml
deleted file mode 100644
index 7b921d5113e1..000000000000
--- a/translations/zh-CN/data/variables/valkyrie.yml
+++ /dev/null
@@ -1,2 +0,0 @@
----
-product_name_long: The GitHub Marketplace API