From 9a1e391b0d01144f44e271c0740bd299369c6ede Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Thu, 12 May 2022 17:52:04 -0500 Subject: [PATCH 1/3] New translation batch for pt (#27652) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=pt * run script/i18n/reset-known-broken-translation-files.js Co-authored-by: Robert Sese --- .../building-and-testing-java-with-gradle.md | 4 +- .../building-and-testing-java-with-maven.md | 4 +- .../building-and-testing-nodejs.md | 4 +- .../building-and-testing-powershell.md | 2 +- .../building-and-testing-python.md | 6 +-- .../building-and-testing-ruby.md | 4 +- .../building-and-testing-swift.md | 2 +- ...-security-hardening-with-openid-connect.md | 10 ++-- ...g-openid-connect-in-amazon-web-services.md | 2 +- ...openid-connect-in-google-cloud-platform.md | 2 +- ...uring-openid-connect-in-hashicorp-vault.md | 4 +- .../actions/learn-github-actions/contexts.md | 28 +++++----- .../environment-variables.md | 2 +- .../manually-running-a-workflow.md | 2 +- ...igrating-from-jenkins-to-github-actions.md | 2 +- ...rating-from-travis-ci-to-github-actions.md | 4 +- .../publishing-docker-images.md | 16 +++--- .../using-a-matrix-for-your-jobs.md | 28 +++++----- .../using-workflows/about-workflows.md | 10 ++-- ...hing-dependencies-to-speed-up-workflows.md | 22 ++++---- .../using-workflows/reusing-workflows.md | 6 +-- .../storing-workflow-data-as-artifacts.md | 6 +-- .../workflow-commands-for-github-actions.md | 30 +++++------ .../workflow-syntax-for-github-actions.md | 14 ++--- .../about-github-connect.md | 30 +++++------ ...c-user-license-sync-for-your-enterprise.md | 2 +- ...enabling-dependabot-for-your-enterprise.md | 2 +- ...g-server-statistics-for-your-enterprise.md | 18 +++---- .../enabling-subdomain-isolation.md | 2 +- .../configuring-backups-on-your-appliance.md | 2 +- .../configuring-email-for-notifications.md | 14 ++--- .../configuring-web-commit-signing.md | 40 +++++++------- ...nabling-and-scheduling-maintenance-mode.md | 16 +++--- .../increasing-storage-capacity.md | 2 +- .../upgrading-github-enterprise-server.md | 2 +- ...g-github-actions-with-amazon-s3-storage.md | 4 +- ...-github-actions-with-azure-blob-storage.md | 4 +- ...ions-with-minio-gateway-for-nas-storage.md | 4 +- .../about-github-actions-for-enterprises.md | 2 +- ...ub-actions-for-github-enterprise-server.md | 18 ++++++- ...ucing-github-actions-to-your-enterprise.md | 6 +-- .../about-using-actions-in-your-enterprise.md | 2 +- .../about-enterprise-managed-users.md | 6 +-- ...ling-github-enterprise-server-on-vmware.md | 2 +- .../about-server-statistics.md | 52 +++++++++---------- .../exporting-server-statistics.md | 34 ++++++------ .../index.md | 6 +-- ...ng-server-statistics-using-the-rest-api.md | 12 ++--- .../creating-a-personal-access-token.md | 9 ++-- .../about-commit-signature-verification.md | 2 +- ...-github-using-two-factor-authentication.md | 8 ++- .../troubleshooting-the-codeql-workflow.md | 2 + .../about-dependabot-alerts.md | 2 +- .../about-dependabot-version-updates.md | 2 +- ...ion-options-for-the-dependabot.yml-file.md | 2 +- ...ing-custom-patterns-for-secret-scanning.md | 15 +++++- .../codespaces/getting-started/quickstart.md | 4 +- .../introduction-to-dev-containers.md | 2 +- .../get-started/quickstart/fork-a-repo.md | 2 +- .../about-issues.md | 2 + .../linking-a-pull-request-to-an-issue.md | 5 +- ...ring-commit-squashing-for-pull-requests.md | 5 +- .../pt-BR/content/rest/overview/libraries.md | 2 +- .../searching-issues-and-pull-requests.md | 8 +-- .../about-github-support.md | 14 +++-- .../dependabot-grouped-dependencies.yml | 8 +++ .../secret-scanning-enterprise-dry-runs.yml | 7 +++ .../enterprise-server/3-5/0-rc1.yml | 3 +- .../actions/hardware-requirements-3.5.md | 7 +++ .../secret-scanning-dry-run-results.md | 2 +- .../secret-scanning-dry-run-select-repos.md | 2 + .../hardware-rec-table.md | 6 +++ .../password-authentication-deprecation.md | 2 +- translations/pt-BR/data/variables/product.yml | 2 +- 74 files changed, 348 insertions(+), 273 deletions(-) create mode 100644 translations/pt-BR/data/features/dependabot-grouped-dependencies.yml create mode 100644 translations/pt-BR/data/features/secret-scanning-enterprise-dry-runs.yml create mode 100644 translations/pt-BR/data/reusables/actions/hardware-requirements-3.5.md create mode 100644 translations/pt-BR/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index e96e3b98e6..6b89e9f5c0 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -22,7 +22,7 @@ shortTitle: Criar & testar Java & Gradle ## Introdução -Este guia mostra como criar um fluxo de trabalho que realiza a integração contínua (CI) para o seu projeto Java usando o sistema de criação do Gradle. O fluxo de trabalho que você criar permitirá que você veja quando commits em um pull request gerarão falhas de criação ou de teste em comparação com o seu branch-padrão. Essa abordagem pode ajudar a garantir que seu código seja sempre saudável. You can extend your CI workflow to {% if actions-caching %}cache files and{% endif %} upload artifacts from a workflow run. +Este guia mostra como criar um fluxo de trabalho que realiza a integração contínua (CI) para o seu projeto Java usando o sistema de criação do Gradle. O fluxo de trabalho que você criar permitirá que você veja quando commits em um pull request gerarão falhas de criação ou de teste em comparação com o seu branch-padrão. Essa abordagem pode ajudar a garantir que seu código seja sempre saudável. Você pode estender seu fluxo de trabalho de CI para {% if actions-caching %}arquivos de cache e{% endif %} fazer o upload de artefatos a partir da execução de um fluxo de trabalho. {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} @@ -114,7 +114,7 @@ steps: ## Memorizar dependências -Your build dependencies can be cached to speed up your workflow runs. Após uma execução bem-sucedida, a ação `gradle/gradle-build-action` armazena em cache partes importantes do diretório inicial do usuário do Gradle. Em trabalhos futuros, o cache será restaurado para que os scripts de compilação não precisem ser recalculados e as dependências não precisem ser baixadas a partir de repositórios remotos de pacotes. +Suas dependências de compilação podem ser armazenadas em cache para acelerar as execuções do seu fluxo de trabalho. Após uma execução bem-sucedida, a ação `gradle/gradle-build-action` armazena em cache partes importantes do diretório inicial do usuário do Gradle. Em trabalhos futuros, o cache será restaurado para que os scripts de compilação não precisem ser recalculados e as dependências não precisem ser baixadas a partir de repositórios remotos de pacotes. O cache é habilitado por padrão ao usar a ação `grades/gradle-build-action`. Para obter mais informações, consulte [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action#caching). diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index 7407889062..4edfe976b6 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -22,7 +22,7 @@ shortTitle: Criar & testar o Java com o Maven ## Introdução -Este guia mostra como criar um fluxo de trabalho que realiza a integração contínua (CI) para o seu projeto Java usando a ferramenta de gerenciamento de projeto do software Maven. O fluxo de trabalho que você criar permitirá que você veja quando commits em um pull request gerarão falhas de criação ou de teste em comparação com o seu branch-padrão. Essa abordagem pode ajudar a garantir que seu código seja sempre saudável. You can extend your CI workflow to {% if actions-caching %}cache files and{% endif %} upload artifacts from a workflow run. +Este guia mostra como criar um fluxo de trabalho que realiza a integração contínua (CI) para o seu projeto Java usando a ferramenta de gerenciamento de projeto do software Maven. O fluxo de trabalho que você criar permitirá que você veja quando commits em um pull request gerarão falhas de criação ou de teste em comparação com o seu branch-padrão. Essa abordagem pode ajudar a garantir que seu código seja sempre saudável. Você pode estender seu fluxo de trabalho de CI para {% if actions-caching %}arquivos de cache e{% endif %} fazer o upload de artefatos a partir da execução de um fluxo de trabalho. {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} @@ -103,7 +103,7 @@ steps: ## Memorizar dependências -Você pode armazenar as suas dependências para acelerar as execuções do seu fluxo de trabalho. After a successful run, your local Maven repository will be stored in a cache. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Você pode armazenar dependências simplesmente usando a ação [`setup-java`](https://github.com/marketplace/actions/setup-java-jdk) ou pode usar a ação [`cache` ](https://github.com/actions/cache) para uma configuração mais avançada e personalizada. +Você pode armazenar as suas dependências para acelerar as execuções do seu fluxo de trabalho. Depois de uma execução bem-sucedida, seu repositório Maven local será armazenado em um cache. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Você pode armazenar dependências simplesmente usando a ação [`setup-java`](https://github.com/marketplace/actions/setup-java-jdk) ou pode usar a ação [`cache` ](https://github.com/actions/cache) para uma configuração mais avançada e personalizada. ```yaml{:copy} steps: diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index ca942e1e19..0b09cf173b 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -136,7 +136,7 @@ Se você não especificar uma versão do Node.js, o {% data variables.product.pr Executores hospedados em {% data variables.product.prodname_dotcom %} têm gerenciadores de dependências npm e Yarn instalados. Você pode usar o npm e o Yarn para instalar dependências no seu fluxo de trabalho antes de criar e testar seu código. Os executores do Windows e Linux hospedados em {% data variables.product.prodname_dotcom %} também têm o Grunt, Gulp, e Bower instalado. -{% if actions-caching %}You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %} +{% if actions-caching %}Você também pode armazenar dependências em cache para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "[Armazenando as dependências em cache para acelerar fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".{% endif %} ### Exemplo de uso do npm @@ -232,7 +232,7 @@ always-auth=true ### Exemplo de memorização de dependências -You can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node). +Você pode armazenar em cache e restaurar as dependências usando a ação [`setup-node`](https://github.com/actions/setup-node). O exemplo a seguir armazena dependências do npm. diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index 4210c8345f..89edae9033 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -104,7 +104,7 @@ Executores hospedados em {% data variables.product.prodname_dotcom %} têm Power {% endnote %} -{% if actions-caching %}You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %} +{% if actions-caching %}Você também pode armazenar dependências em cache para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "[Armazenando as dependências em cache para acelerar fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".{% endif %} Por exemplo, o trabalho a seguir instala os módulos `SqlServer` e `PSScriptAnalyzer`: diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md index 8d89d00408..09afe8240e 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -197,7 +197,7 @@ Recomendamos usar `setup-python` para configurar a versão do Python usada nos s Os executores hospedados em {% data variables.product.prodname_dotcom %} têm instalado o gerenciador do pacote pip. Você pode usar o pip para instalar dependências do registro de pacotes do PyPI antes de criar e testar o seu código. Por exemplo, o YAML abaixo instala ou atualiza o instalador de pacotes `pip` e as os pacotes `setuptools` e `wheel`. -{% if actions-caching %}You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %} +{% if actions-caching %}Você também pode armazenar dependências em cache para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "[Armazenando as dependências em cache para acelerar fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".{% endif %} ```yaml{:copy} steps: @@ -231,7 +231,7 @@ steps: ### Memorizar dependências -You can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python). +Você pode armazenar em cache e restaurar as dependências usando a ação [`setup-python`](https://github.com/actions/setup-python). O exemplo a seguir armazena dependências para pip. @@ -246,7 +246,7 @@ steps: - run: pip test ``` -Por padrão, a ação `setup-python` busca o arquivo de dependência (`requirements.txt` para pip ou `Pipfile.lock` para pipenv) em todo o repositório. For more information, see "[Caching packages dependencies](https://github.com/actions/setup-python#caching-packages-dependencies)" in the `setup-python` README. +Por padrão, a ação `setup-python` busca o arquivo de dependência (`requirements.txt` para pip ou `Pipfile.lock` para pipenv) em todo o repositório. Para obter mais informações, consulte "[Armazenando em cache as dependências de pacotes](https://github.com/actions/setup-python#caching-packages-dependencies)" no README do `setup-python`. Se você tiver um requisito personalizado ou precisar de melhores controles para cache, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). O Pip armazena dependências em diferentes locais, dependendo do sistema operacional do executor. O caminho que você precisa efetuar o armazenamento em cache pode ser diferente do exemplo do Ubuntu acima, dependendo do sistema operacional que você usa. Para obter mais informações, consulte [Exemplos de armazenamento em cache do Python](https://github.com/actions/cache/blob/main/examples.md#python---pip) no repositório de ação `cache`. diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index cd1d5dfa7f..8f41555e6e 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -161,11 +161,11 @@ steps: ``` {% endraw %} -Isso irá configurar o bundler para instalar seus gems em `vendor/cache`. For each successful run of your workflow, this folder will be cached by {% data variables.product.prodname_actions %} and re-downloaded for subsequent workflow runs. São usados um hash do seu gemfile.lock e versão do Ruby como a chave de cache. Se você instalar qualquer novo gem, ou mudar uma versão, o cache será invalidado e o bundler fará uma nova instalação. +Isso irá configurar o bundler para instalar seus gems em `vendor/cache`. Para cada execução bem-sucedida do seu fluxo de trabalho, esta pasta será armazenada em cache por {% data variables.product.prodname_actions %} e baixada novamente para as execuções subsequentes do fluxo de trabalho. São usados um hash do seu gemfile.lock e versão do Ruby como a chave de cache. Se você instalar qualquer novo gem, ou mudar uma versão, o cache será invalidado e o bundler fará uma nova instalação. **Fazer armazenamento em cache sem o setup-ruby** -For greater control over caching, you can use the `actions/cache` action directly. Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)". +Para maior controle sobre o cache, você pode usar a ação `actions/cache` diretamente. Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)". ```yaml steps: diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md index cd0e7105ff..74478cc0ce 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -65,7 +65,7 @@ Os exemplos abaixo demonstram o uso da ação `fwal/setup-fast`. ### Usando várias versões do Swift -You can configure your job to use multiple versions of Swift in a matrix. +Você pode configurar seu trabalho para usar várias versões do Swift em uma matriz. ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md index 4079f3a0ee..de8f1ed041 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md @@ -92,7 +92,7 @@ O exemplo a seguir do token do OIDC usa um assunto (`sub`) que faz referência a } ``` -To see all the claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, review the `claims_supported` entries at +Para ver todas as reivindicações compatíveis com o provedor do OIDC de {% data variables.product.prodname_dotcom %}, revise as entradas `claims_supported` em {% ifversion ghes %}`https://HOSTNAME/_services/token/.well-known/openid-configuration`{% else %}https://token.actions.githubusercontent.com/.well-known/openid-configuration{% endif %}. O token inclui as reivindicações padrão de audiência, emissor e assunto: @@ -100,7 +100,7 @@ O token inclui as reivindicações padrão de audiência, emissor e assunto: | Reivindicação | Descrição | | ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `aud` | _(Audiência)_ por padrão, esta é a URL do proprietário do repositório, como a organização proprietária do repositório. Esta é a única reivindicação que pode ser personalizada. Você pode definir um público personalizado com um comando de conjunto de ferramentas: [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0) | -| `iss` | _(Issuer)_ The issuer of the OIDC token: | +| `iss` | _(Emissor)_ O emissor do token do OIDC: | | {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} | | | | | | `sub` | _(Assunto)_ Define o assunto indicado para ser validado pelo provedor da nuvem. Esta configuração é essencial para garantir que os tokens de acesso sejam apenas alocados de forma previsível. | @@ -122,7 +122,7 @@ O token também inclui reivindicações personalizadas fornecidas por {% data va | Reivindicação | Descrição | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `actor` | A conta pessoal que iniciou a execução do fluxo de trabalho. | -| `actor_id` | The ID of personal account that initiated the workflow run. | +| `actor_id` | O ID da conta pessoal que iniciou a execução do fluxo de trabalho. | | `base_ref` | O branch de destino do pull request na execução de um fluxo de trabalho. | | `ambiente` | O nome do ambiente usado pelo trabalho. | | `event_name` | Nome do evento que acionou a execução do fluxo de trabalho. | @@ -131,9 +131,9 @@ O token também inclui reivindicações personalizadas fornecidas por {% data va | `ref` | _(Referência)_ A ref do git que acionou a execução do fluxo de trabalho. | | `ref_type` | O tipo de `ref`, por exemplo: "branch". | | `repositório` | O repositório de onde o fluxo de trabalho está sendo executado. | -| `repository_id` | The ID of the repository from where the workflow is running. | +| `repository_id` | O ID do repositório de onde o fluxo de trabalho está sendo executado. | | `repository_owner` | O nome da organização em que o `repositório` é armazenado. | -| `repository_owner_id` | The ID of the organization in which the `repository` is stored. | +| `repository_owner_id` | O ID da organização em que o `repositório` é armazenado. | | `run_id` | O ID da execução do fluxo de trabalho que acionou o fluxo de trabalho. | | `run_number` | O número de vezes que este fluxo de trabalho foi executado. | | `run_attempt` | O número de vezes que este fluxo de trabalho foi executado. | diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md index cb0ed6b50e..4c8ffc0b47 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md @@ -32,7 +32,7 @@ Este guia explica como configurar o AWS para confiar no OIDC de {% data variable Para adicionar o provedor OIDC de {% data variables.product.prodname_dotcom %} ao IAM, consulte a [documentação AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html). -- For the provider URL: Use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} +- Para o URL do provedor: Use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} - Para o "público": Use `sts.amazonaws.com` se você estiver usando a [ação oficial](https://github.com/aws-actions/configure-aws-credentials). ### Configurando a função e a política de confiança diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md index 34883a1ce7..c178375bb9 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md @@ -40,7 +40,7 @@ Orientação adicional para a configuração do provedor de identidade: - Para aumentar a segurança, verifique se você revisou ["Configurando a confiança do OIDC com a nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). Por exemplo, consulte ["Configurar o assunto no seu provedor de nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider). - Para a conta de serviço estar disponível para configuração, ela deverá ser atribuída à função `roles/iam.workloadIdentityUser`. Para obter mais informações, consulte [a documentação do GCP](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions). -- The Issuer URL to use: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} +- O URL do emissor a usar: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} ## Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %} diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md index d1828dba2c..7014cad6f4 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md @@ -33,8 +33,8 @@ Este guia fornece uma visão geral sobre como configurar o cofre HashiCorp para Para usar OIDC com oHashiCorp Vault, você deverá adicionar uma configuração de confiança ao provedor do OIDC de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a [documentação](https://www.vaultproject.io/docs/auth/jwt) do HashiCorp Vault. Configure o cofre para aceitar tokens web do JSON (JWT) para a autenticação: -- For the `oidc_discovery_url`, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} -- For `bound_issuer`, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} +- Para o `oidc_discovery_url`, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} +- Para `bound_issuer`, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} - Certifique-se de que `bound_subject` esteja corretamente definido para seus requisitos de segurança. Para obter mais informações, consulte ["Configurar a confiança do OIDC com a nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud) e [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action). ## Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md index f8f857ba34..d279def997 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md +++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md @@ -23,7 +23,7 @@ miniTocMaxHeadingLevel: 3 Os contextos são uma forma de acessar informações sobre execuções de fluxo de trabalho, ambientes dos executores, trabalhos e etapas. Cada contexto é um objeto que contém propriedades, que podem ser strings ou outros objetos. -{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). +{% data reusables.actions.context-contents %} Por exemplo, o contexto `matriz` só é povoado para trabalhos em uma matriz[matriz](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). Você pode acessar contextos usando a sintaxe da expressão. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". @@ -537,19 +537,19 @@ O conteúdo de exemplo do contexto dos `segredos` mostra o `GITHUB_TOKEN` autom ## Contexto `estratégia` -For workflows with a matrix, the `strategy` context contains information about the matrix execution strategy for the current job. +Para fluxos de trabalho com uma matriz, o contexto `estratégia` contém informações sobre a estratégia de execução da matriz para o trabalho atual. | Nome da propriedade | Tipo | Descrição | | ----------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `strategy` | `objeto` | Esse contexto altera cada trabalho em uma execução de fluxo de trabalho. Você pode acessar este contexto a partir de qualquer trabalho ou etapa em um fluxo de trabalho. Este objeto contém todas as propriedades listadas abaixo. | -| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a matrix fails. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)". | -| `strategy.job-index` | `string` | The index of the current job in the matrix. **Observação:** Este número é um número baseado em zero. The first job's index in the matrix is `0`. | -| `strategy.job-total` | `string` | The total number of jobs in the matrix. **Observação:** Este número **não é** um número baseado em zero. For example, for a matrix with four jobs, the value of `job-total` is `4`. | +| `strategy.fail-fast` | `string` | Quando `verdadeiro`, todos os trabalhos em andamento são cancelados se qualquer trabalho em uma matriz falhar. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)". | +| `strategy.job-index` | `string` | O índice do trabalho atual na matriz. **Observação:** Este número é um número baseado em zero. O primeiro índice do trabalho na matriz é `0`. | +| `strategy.job-total` | `string` | O número total de trabalhos na matriz. **Observação:** Este número **não é** um número baseado em zero. Por exemplo, para uma matriz com quatro trabalhos, o valor de `job-total` é `4`. | | `strategy.max-parallel` | `string` | Número máximo de trabalhos que podem ser executados simultaneamente ao usar uma estratégia de trabalho de `matrix`. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)". | ### Exemplo de conteúdo do contexto `estratégia` -The following example contents of the `strategy` context is from a matrix with four jobs, and is taken from the final job. Observe a diferença entre o número de `job-index` baseado em zero e o total de `job-job` que não é baseado em zero. +O conteúdo de exemplo a seguir do contexto `estratégia` é de uma matriz com quatro trabalhos, e é tirada do trabalho final. Observe a diferença entre o número de `job-index` baseado em zero e o total de `job-job` que não é baseado em zero. ```yaml { @@ -562,7 +562,7 @@ The following example contents of the `strategy` context is from a matrix with f ### Exemplo de uso do contexto `estratégia` -This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a matrix. +Esse exemplo de fluxo de trabalho usa a propriedade `strategy.job-index` para definir um nome exclusivo para um arquivo de registro para cada trabalho em uma matriz. ```yaml{:copy} name: Test matrix @@ -587,18 +587,18 @@ jobs: ## Contexto `matriz` -For workflows with a matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job. +Para fluxos de trabalho com uma matriz, o contexto `matriz` contém as propriedades definidas no arquivo do fluxo de trabalho que se aplicam ao trabalho atual. Por exemplo, se você configurar uma matriz com as chaves `os` e `nó`, o objeto do contexto `matriz` irá incluir as propriedades `os` e `nó` com os valores usados para o trabalho atual. Não há propriedades padrão no contexto `matriz`, apenas as que são definidas no arquivo do fluxo de trabalho. -| Nome da propriedade | Tipo | Descrição | -| ------------------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `matrix` | `objeto` | This context is only available for jobs in a matrix, and changes for each job in a workflow run. Você pode acessar este contexto a partir de qualquer trabalho ou etapa em um fluxo de trabalho. Este objeto contém as propriedades listadas abaixo. | -| `matrix.` | `string` | O valor da propriedade de uma matriz. | +| Nome da propriedade | Tipo | Descrição | +| ------------------------------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `matrix` | `objeto` | Esse contexto só está disponível para trabalhos em uma matriz e alterações para cada trabalho na execução de um fluxo de trabalho. Você pode acessar este contexto a partir de qualquer trabalho ou etapa em um fluxo de trabalho. Este objeto contém as propriedades listadas abaixo. | +| `matrix.` | `string` | O valor da propriedade de uma matriz. | ### Exemplo de conteúdo do contexto `matriz` -The following example contents of the `matrix` context is from a job in a matrix that has the `os` and `node` matrix properties defined in the workflow. O trabalho está executando a combinação matriz de um `ubuntu-latest` OS e do Node.js versão `16`. +O exemplo a seguir do contexto `matriz` é de um trabalho em uma matriz que tem as propriedades de matriz `os` e `nó` definidas no fluxo de trabalho. O trabalho está executando a combinação matriz de um `ubuntu-latest` OS e do Node.js versão `16`. ```yaml { @@ -609,7 +609,7 @@ The following example contents of the `matrix` context is from a job in a matrix ### Exemplo de uso do contexto `matriz` -This example workflow creates a matrix with `os` and `node` keys. Ele usa a propriedade `matriz.os` para definir o tipo de executor para cada trabalho e usa a propriedade `matrix.node` para definir a versão do Node.js para cada trabalho. +Este exemplo de fluxo de trabalho cria uma matriz com as chaves `os` e `nós`. Ele usa a propriedade `matriz.os` para definir o tipo de executor para cada trabalho e usa a propriedade `matrix.node` para definir a versão do Node.js para cada trabalho. ```yaml{:copy} name: Test matrix diff --git a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md index f64a45e502..90c08b4b91 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md +++ b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md @@ -149,7 +149,7 @@ As variáveis de ambiente padrão que os conjuntos de {% data variables.product. {%- endif %} | `GITHUB_REPOSITORY` | O nome do proprietário e do repositório. Por exemplo, `octocat/Hello-World`. | | `GITHUB_REPOSITORY_OWNER` | O nome do proprietário do repositório. Por exemplo, `octocat`. | | `GITHUB_RETENTION_DAYS` | O número de dias que os registros da execução do fluxo de trabalho e os artefatos são mantidos. Por exemplo, `90`. | | `GITHUB_RUN_ATTEMPT` | Um número único para cada tentativa da execução de um fluxo de trabalho particular em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. Por exemplo, `3`. | | `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} Por exemplo, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} Por exemplo, `3`. | | `GITHUB_SERVER_URL`| A URL do servidor de {% data variables.product.product_name %} server. Por exemplo: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | O SHA do commit que acionou o fluxo de trabalho. O valor do commit deste SHA depende do evento que acionou o fluxo de trabalho. Para obter mais informações, consulte [Eventos que acionam fluxos de trabalho](/actions/using-workflows/events-that-trigger-workflows). Por exemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | {%- if actions-job-summaries %} -| `GITHUB_STEP_SUMMARY` | The path on the runner to the file that contains job summaries from workflow commands. Este arquivo é único para a etapa atual e alterações para cada etapa de um trabalho. For example, `/home/rob/runner/_layout/_work/_temp/_runner_file_commands/step_summary_1cb22d7f-5663-41a8-9ffc-13472605c76c`. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)." | +| `GITHUB_STEP_SUMMARY` | O caminho no executor para o arquivo que contém resumos de trabalho dos comandos de fluxo de trabalho. Este arquivo é único para a etapa atual e alterações para cada etapa de um trabalho. Por exemplo, `/home/rob/runner/_layout/_work/_temp/_runner_file_commands/step_summary_1cb22d7f-5663-41a8-9ffc-13472605c76c`. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)." | {%- endif %} | `GITHUB_WORKFLOW` | O nome do fluxo de trabalho. Por exemplo, `My test workflow`. Se o fluxo de trabalho não determinar um `nome`, o valor desta variável será o caminho completo do arquivo do fluxo de trabalho no repositório. | | `GITHUB_WORKSPACE` | O diretório de trabalho padrão no executor para as etapas e para a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). Por exemplo, `/home/runner/work/my-repo-name/my-repo-name`. | {%- if actions-runner-arch-envvars %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 28b67a1b8d..b0f09c74aa 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -72,7 +72,7 @@ Ao usar a API REST, você configura as `entradas` e `ref` como parâmetros do te {% note %} -**Note:** You can define up to 10 `inputs` for a `workflow_dispatch` event. +**Nota:** Você pode definir até 10 `entradas` para um evento de `workflow_dispatch`. {% endnote %} diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 10215c92ff..09f3b8d9ad 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -85,7 +85,7 @@ O Jenkins pode executar os `stages` e as `etapas` em paralelo, enquanto o {% dat ### Matrix -Both {% data variables.product.prodname_actions %} and Jenkins let you use a matrix to define various system combinations. +Tanto o {% data variables.product.prodname_actions %} quanto o Jenkins permitem que você use uma matriz para definir várias combinações de sistema. | Jenkins | {% data variables.product.prodname_actions %} | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index 939a21b0c9..30bf1058b5 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -59,9 +59,9 @@ O Travis CI pode usar `stages` para executar trabalhos em paralelo. Da mesma for O Travis CI e {% data variables.product.prodname_actions %} são compatíveis com selos de status, o que permite que você indique se uma criação está sendo aprovada ou falhando. Para obter mais informações, consulte ["Adicionar um selo de status de fluxo de trabalho ao seu repositório](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". -### Using a matrix +### Usando uma matriz -Travis CI and {% data variables.product.prodname_actions %} both support a matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." +O Travis CI e {% data variables.product.prodname_actions %} são compatíveis com uma matriz, o que permite que você realize testes usando combinações de sistemas operacionais e pacotes de software. Para obter mais informações, consulte "[Usando uma matriz para seus trabalhos](/actions/using-jobs/using-a-matrix-for-your-jobs)". Abaixo, há um exemplo de comparação da sintaxe para cada sistema: diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md index c81cda4fba..4b4fa64619 100644 --- a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md @@ -116,10 +116,10 @@ O fluxo de trabalho acima verifica o repositório {% data variables.product.prod {% data reusables.actions.release-trigger-workflow %} -In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}. +No exemplo abaixo, usamos a `login-action do Docker`{% ifversion fpt or ghec %}, `metadados-ação`,{% endif %} e ações de `build-push-action` para construir a imagem Docker e, se a criação for bem-sucedida, faça push da imagem criada para {% data variables.product.prodname_registry %}. As opções de `login-action` de login necessárias para {% data variables.product.prodname_registry %} são: -* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}. +* `registro`: Deve ser definido como {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}. * `nome de usuário`: Você pode usar o contexto {% raw %}`${{ github.actor }}`{% endraw %} para usar automaticamente o nome de usuário que acionou a execução do fluxo de trabalho. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#github-context)". * `senha`: Você pode usar o segredo `GITHUB_TOKEN` gerado automaticamente para a senha. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". @@ -128,15 +128,15 @@ A opção `metadata-action` obrigatória para {% data variables.product.prodname * `imagens`: O espaço do nome e o nome da imagem Docker que você está criando. {% endif %} -The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %} +As opções de `build-push-action` necessárias para {% data variables.product.prodname_registry %} são:{% ifversion fpt or ghec %} * `contexto`: Define o contexto da criação como o conjunto de arquivos localizados no caminho especificado.{% endif %} * `push`: Se definido como `verdadeiro`, a imagem será enviada por push para o registo se for criada com êxito.{% ifversion fpt or ghec %} * `tags` e `etiquetas`: são preenchidas pela saída de `metadados`.{% else %} -* `tags`: Must be set in the format {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. +* `tags`: Deve ser definido no formato {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. - For example, for an image named `octo-image` stored on {% data variables.product.prodname_ghe_server %} at `https://HOSTNAME/octo-org/octo-repo`, the `tags` option should be set to `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. + Por exemplo, para uma imagem chamada `octo-image` armazenada em {% data variables.product.prodname_ghe_server %} em `https://HOSTNAME/octo-org/octo-repo`, a opção de `tags` deve ser definida como `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. - For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}. Você pode definir uma única tag, conforme mostrado abaixo, ou especificar várias tags em uma lista.{% endif %} + Por exemplo, para uma imagem denominada `octo-image` armazenada em {% data variables.product.prodname_dotcom %} em `http://github. om/octo-org/octo-repo`, a opção `tags` deve estar definida como `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`.{% endif %}. Você pode definir uma única tag, conforme mostrado abaixo, ou especificar várias tags em uma lista.{% endif %} {% ifversion fpt or ghec or ghes > 3.4 %} {% data reusables.package_registry.publish-docker-image %} @@ -180,7 +180,7 @@ jobs: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %} ``` -The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags. +O fluxo de trabalho acima faz o check-out do repositório {% data variables.product.product_name %}, usa o `login-action` para efetuar o login no registro e, em seguida, usa a ação `build-push-action` para criar uma imagem Docker com base no `arquivo Docker` do seu repositório; fazer push da imagem para o registro Docker e aplicar o commit SHA e a versão como tags de imagem. {% endif %} ## Publicar imagens no Docker Hub e {% data variables.product.prodname_registry %} @@ -243,4 +243,4 @@ jobs: labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %} ``` -The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action. Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}. +O fluxo de trabalho acima faz checkout do repositório {% data variables.product.product_name %} usa o `login-action` duas vezes para fazer login em ambos os registros e gerar etiquetas com a ação `metadata-action`. Em seguida, a ação `build-push-action` cria e faz push da imagem do Docker para o Docker Hub e, posteriormente, o {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}registro do Docker{% endif %}. diff --git a/translations/pt-BR/content/actions/using-jobs/using-a-matrix-for-your-jobs.md b/translations/pt-BR/content/actions/using-jobs/using-a-matrix-for-your-jobs.md index 40615bed48..8a288023e0 100644 --- a/translations/pt-BR/content/actions/using-jobs/using-a-matrix-for-your-jobs.md +++ b/translations/pt-BR/content/actions/using-jobs/using-a-matrix-for-your-jobs.md @@ -1,7 +1,7 @@ --- -title: Using a matrix for your jobs -shortTitle: Using a matrix -intro: Create a matrix to define variations for each job. +title: Usando uma matriz para seus trabalhos +shortTitle: Usando uma matriz +intro: Crie uma matriz para definir variações para cada trabalho. versions: fpt: '*' ghes: '*' @@ -15,46 +15,46 @@ redirect_from: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## About matrix strategies +## Sobre estratégias da matriz {% data reusables.actions.jobs.about-matrix-strategy %} -## Using a matrix strategy +## Usando uma estratégia da matriz {% data reusables.actions.jobs.using-matrix-strategy %} -### Example: Using a single-dimension matrix +### Exemplo: Usando uma matriz de dimensão única {% data reusables.actions.jobs.single-dimension-matrix %} -### Example: Using a multi-dimension matrix +### Exemplo: Usando uma matriz de múltiplas dimensões {% data reusables.actions.jobs.multi-dimension-matrix %} -### Example: Using contexts to create matrices +### Exemplo: Usando contextos para criar matrizes {% data reusables.actions.jobs.matrix-from-context %} -## Expanding or adding matrix configurations +## Expansão ou adição de configurações da matriz {% data reusables.actions.jobs.matrix-include %} -### Example: Expanding configurations +### Exemplo: Expandir configurações {% data reusables.actions.jobs.matrix-expand-with-include %} -### Example: Adding configurations +### Exemplo: Adicionar configurações {% data reusables.actions.jobs.matrix-add-with-include %} -## Excluding matrix configurations +## Excluindo configurações de matriz {% data reusables.actions.jobs.matrix-exclude %} -## Handling failures +## Gerenciando as falhas {% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %} -## Defining the maximum number of concurrent jobs +## Definindo o número máximo de trabalhos simultâneos {% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %} diff --git a/translations/pt-BR/content/actions/using-workflows/about-workflows.md b/translations/pt-BR/content/actions/using-workflows/about-workflows.md index 40876ef0ea..e48f532730 100644 --- a/translations/pt-BR/content/actions/using-workflows/about-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/about-workflows.md @@ -28,7 +28,7 @@ Um fluxo de trabalho deve conter os seguintes componentes básicos: 1. Um ou mais _trabalhos_, cada uma das quais será executado em uma máquina de _executor_ e executará uma série de uma ou mais _etapas_. 1. Cada etapa pode executar um script que você define ou executa uma ação, que é uma extensão reutilizável que pode simplificar seu fluxo de trabalho. -For more information on these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)." +Para obter mais informações sobre esses componentes básicos, consulte "[Entendendo GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)". ![Visão geral do fluxo de trabalho](/assets/images/help/images/overview-actions-simple.png) @@ -105,9 +105,9 @@ jobs: Para obter mais informações, consulte[Definindo trabalhos de pré-requisito](/actions/using-jobs/using-jobs-in-a-workflow#defining-prerequisite-jobs)". -### Using a matrix +### Usando uma matriz -{% data reusables.actions.jobs.about-matrix-strategy %} The matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this matrix will run the job multiple times, using different versions of Node.js: +{% data reusables.actions.jobs.about-matrix-strategy %} A matriz é criada usando a palavra-chave `estratégia`, que recebe as opções de construção como uma matriz. Por exemplo, essa matriz irá executar o trabalho várias vezes, usando diferentes versões do Node.js: ```yaml jobs: @@ -122,12 +122,12 @@ jobs: node-version: {% raw %}${{ matrix.node }}{% endraw %} ``` -For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." +Para obter mais informações, consulte "[Usando uma matriz para seus trabalhos](/actions/using-jobs/using-a-matrix-for-your-jobs)". {% if actions-caching %} ### Memorizar dependências -If your jobs regularly reuse dependencies, you can consider caching these files to help improve performance. Após a criação do armazenamento em cache, ele fica disponível para todos os fluxos de trabalho no mesmo repositório. +Se seus trabalhos reutilizam dependências regularmente, você pode considerar armazenar em cache esses arquivos para ajudar a melhorar o desempenho. Após a criação do armazenamento em cache, ele fica disponível para todos os fluxos de trabalho no mesmo repositório. Este exemplo demonstra como armazenar em cache o diretório `~/.npm`: diff --git a/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index 76db7c5c1d..35f834bf05 100644 --- a/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -55,22 +55,22 @@ To cache dependencies for a job, you can use {% data variables.product.prodname_ **Warning**: {% ifversion fpt or ghec %}Be mindful of the following when using caching with {% data variables.product.prodname_actions %}: -* {% endif %}We recommend that you don't store any sensitive information in the cache. Por exemplo, as informações confidenciais podem incluir tokens de acesso ou credenciais de login armazenadas em um arquivo no caminho da cache. Além disso, os programas de interface da linha de comando (CLI) como o `login do Docker` pode salvar as credenciais de acesso em um arquivo de configuração. Anyone with read access can create a pull request on a repository and access the contents of a cache. As bifurcações de um repositório também podem criar pull requests no branch-base e acessar as caches no branch-base. +* {% endif %}Recomendamos que você não armazene nenhuma informação confidencial no cache. Por exemplo, as informações confidenciais podem incluir tokens de acesso ou credenciais de login armazenadas em um arquivo no caminho da cache. Além disso, os programas de interface da linha de comando (CLI) como o `login do Docker` pode salvar as credenciais de acesso em um arquivo de configuração. Qualquer pessoa com acesso de leitura pode criar um pull request em um repositório e acessar o conteúdo do cache. As bifurcações de um repositório também podem criar pull requests no branch-base e acessar as caches no branch-base. {%- ifversion fpt or ghec %} -* When using self-hosted runners, caches from workflow runs are stored on {% data variables.product.company_short %}-owned cloud storage. A customer-owned storage solution is only available with {% data variables.product.prodname_ghe_server %}. +* Ao usar executores auto-hospedados, os caches de execução de fluxo de trabalho são armazenados na nuvem pertencente a {% data variables.product.company_short %}. Uma solução de armazenamento pertencente ao cliente só está disponível com {% data variables.product.prodname_ghe_server %}. {%- endif %} {% endwarning %} {% data reusables.actions.comparing-artifacts-caching %} -For more information on workflow run artifacts, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." +Para obter mais informações sobre artefatos da execução do fluxo de trabalho, consulte "[Persistir dados de fluxo de trabalho usando artefatos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". ## Restrições para acessar uma cache Um fluxo de trabalho pode acessar e restaurar um cache criado no branch atual, no branch de base (incluindo branches base de repositórios bifurcados) ou no branch-padrão (geralmente `principal`). Por exemplo, um cache criado no branch-padrão pode ser acessado a partir de qualquer pull request. Além disso, se o branch `feature-b` tiver o branch de base `feature-a`, um fluxo de trabalho acionado em `feature-b` teria acesso a caches criados no branch-padrão (`principal`), `feature-a` e `feature-b`. -As restrições de acesso fornecem o isolamento da cache e a segurança ao criar um limite lógico entre os diferentes branches. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-c` (with the base `main`). +As restrições de acesso fornecem o isolamento da cache e a segurança ao criar um limite lógico entre os diferentes branches. Por exemplo, um cache criado para o branch `feature-a` (com a base no `principal`) não seria acessível para um pull request para o branch `feature-b` (com a base no `principal`). Vários fluxos de trabalho dentro de um repositório compartilham entradas de cache. Uma cache criada para um branch de um fluxo de trabalho pode ser acessada e restaurada a partir de outro fluxo de trabalho para o mesmo repositório e branch. @@ -78,15 +78,15 @@ Vários fluxos de trabalho dentro de um repositório compartilham entradas de ca The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. Quando a ação encontrar uma cache, ela irá restaurar os arquivos memorizados no `caminho` que você configurar. -If there is no exact match, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`. +Se não houver correspondência exata, a ação criará automaticamente um novo cache se o trabalho for concluído com sucesso. O novo cache usará a `chave` que você forneceu e que contém os arquivos que você especificar no `caminho`. Como alternativa, você pode fornecer uma lista de `chaves de restauração` a serem usadas quando a `chave` não corresponder à cache existente. Uma lista de `chaves de restauração` é importante quando você está tentando restaurar uma cache de outro branch, pois `as chaves de restauração`> $GITHUB_STEP_SUMMARY {% endpowershell %} -You can set some custom Markdown for each job so that it will be displayed on the summary page of a workflow run. You can use job summaries to display and group unique content, such as test result summaries, so that someone viewing the result of a workflow run doesn't need to go into the logs to see important information related to the run, such as failures. +Você pode definir algum Markdown personalizado para cada trabalho para que seja exibido na página de resumo da execução de um fluxo de trabalho. Você pode usar resumos de trabalho para exibir e agrupar conteúdo único, como resumos de resultados de teste, para que alguém que visualizar o resultado da uma execução de um fluxo de trabalho não precise entrar nos registros para ver informações importantes relacionadas à execução como, por exemplo, falhas. -Job summaries support [{% data variables.product.prodname_dotcom %} flavored Markdown](https://github.github.com/gfm/), and you can add your Markdown content for a step to the `GITHUB_STEP_SUMMARY` environment file. `GITHUB_STEP_SUMMARY` is unique for each step in a job. For more information about the per-step file that `GITHUB_STEP_SUMMARY` references, see "[Environment files](#environment-files)." +Job summaries support [{% data variables.product.prodname_dotcom %} flavored Markdown](https://github.github.com/gfm/), and you can add your Markdown content for a step to the `GITHUB_STEP_SUMMARY` environment file. `GITHUB_STEP_SUMMARY` é único para cada etapa de um trabalho. Para obter mais informações sobre o arquivo por etapa, ao qual o `GITHUB_STEP_SUMMARY` faz referência, consulte "[Arquivos do ambiente](#environment-files)". -When a job finishes, the summaries for all steps in a job are grouped together into a single job summary and are shown on the workflow run summary page. If multiple jobs generate summaries, the job summaries are ordered by job completion time. +Quando um trabalho é concluído, os resumos de todas as etapas de um trabalho é agrupado em um único resumo do trabalho e exibido na página de resumo do fluxo de trabalho. Se vários trabalhos gerarem resumos, os resumos dos trabalhos serão ordenados por tempo de conclusão do trabalho. ### Exemplo @@ -700,11 +700,11 @@ echo "### Hello world! :rocket:" >> $GITHUB_STEP_SUMMARY {% endpowershell %} -![Markdown summary example](/assets/images/actions-job-summary-simple-example.png) +![Exemplo de resumo de Markdown](/assets/images/actions-job-summary-simple-example.png) ### Multiline Markdown content -For multiline Markdown content, you can use `>>` to continuously append content for the current step. With every append operation, a newline character is automatically added. +For multiline Markdown content, you can use `>>` to continuously append content for the current step. A cada operação adicionada, um caractere de nova linha é adicionado automaticamente. #### Exemplo @@ -736,9 +736,9 @@ For multiline Markdown content, you can use `>>` to continuously append content {% endpowershell %} -### Overwriting job summaries +### Sobrescrevendo resumos de trabalho -To clear all content for the current step, you can use `>` to overwrite any previously added content. +Para limpar todo o conteúdo da etapa atual, você pode usar `>` para sobrescrever qualquer conteúdo adicionado anteriormente. #### Exemplo @@ -764,9 +764,9 @@ To clear all content for the current step, you can use `>` to overwrite any prev {% endpowershell %} -### Removing job summaries +### Removendo resumos de trabalho -To completely remove a summary for the current step, the file that `GITHUB_STEP_SUMMARY` references can be deleted. +Para remover completamente um resumo para a etapa atual, o arquivo ao qual `GITHUB_STEP_SUMMARY` faz referência pode ser excluído. #### Exemplo @@ -792,11 +792,11 @@ To completely remove a summary for the current step, the file that `GITHUB_STEP_ {% endpowershell %} -After a step has completed, job summaries are uploaded and subsequent steps cannot modify previously uploaded Markdown content. Summaries automatically mask any secrets that might have been added accidentally. If a job summary contains sensitive information that must be deleted, you can delete the entire workflow run to remove all its job summaries. For more information see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)." +Depois que uma etapa for concluída, faz-se o upload dos resumos dos trabalhos e as etapas subsequentes não podem modificar o conteúdo Markdown previamente carregado. Resumos mascaram automaticamente todos os segredos que possam ter sido adicionados acidentalmente. Se o resumo de um trabalho contiver informações sensíveis que devem ser excluídas, você poderá excluir todo o fluxo de trabalho executado para remover todos os resumos do trabalho. Para obter mais informações, consulte "[Excluir a execução de um fluxo de trabalho](/actions/managing-workflow-runs/deleting-a-workflow-run)". -### Step isolation and limits +### Etapa de isolamento e limites -Job summaries are isolated between steps and each step is restricted to a maximum size of 1MiB. Isolation is enforced between steps so that potentially malformed Markdown from a single step cannot break Markdown rendering for subsequent steps. If more than 1MiB of content is added for a step, then the upload for the step will fail and an error annotation will be created. Upload failures for job summaries do not affect the overall status of a step or a job. A maximum of 20 job summaries from steps are displayed per job. +Os resumos de trabalho são isolados entre as etapas e cada etapa é restrita ao tamanho máximo de 1 MiB. Isolamento é imposto entre os passos para que um Markdown potencialmente mal formado a partir de uma única etapa não possa quebrar a renderização Markdown para etapas subsequentes. Se mais de 1 MiB de conteúdo for adicionado para uma etapa, ocorrerá uma falha no upload para a etapa e será criado um erro de anotação. As falhas no upload de resumos de trabalhos não afetam o status geral de uma etapa ou trabalho. Um máximo de 20 resumos de trabalho das etapas são exibidos por trabalho. {% endif %} diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md index e6a1a6b64a..29dc892269 100644 --- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -161,7 +161,7 @@ jobs: #### `on.workflow_call.secrets.inherit` -Use the `inherit` keyword to pass all the calling workflow's secrets to the called workflow. This includes all secrets the calling workflow has access to, namely organization, repository, and environment secrets. The `inherit` keyword can be used to pass secrets across repositories within the same organization, or across organizations within the same enterprise. +Use a a palavra-chave `herdar` para passar todos os segredos do fluxo de trabalho chamando para o fluxo de trabalho. Isso inclui todos os segredos aos quais o fluxo de trabalho da chamada tem acesso, nomeadamente organização, repositório e segredos de ambiente. A palavra-chave `herdar` pode ser usada para passar segredos por meio de repositórios dentro da mesma organização ou em organizações dentro da mesma empresa. #### Exemplo @@ -781,21 +781,21 @@ Se o tempo-limite exceder o tempo limite de execução do trabalho para o runner ## `jobs..strategy` -Use `jobs..strategy` to use a matrix strategy for your jobs. {% data reusables.actions.jobs.about-matrix-strategy %} For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." +Use `trabalhos..strategy` para usar uma estratégia matriz para seus trabalhos. {% data reusables.actions.jobs.about-matrix-strategy %} Para obter mais informações, consulte "[Usando uma matriz para seus trabalhos "](/actions/using-jobs/using-a-matrix-for-your-jobs)". ### `jobs..strategy.matrix` {% data reusables.actions.jobs.using-matrix-strategy %} -#### Example: Using a single-dimension matrix +#### Exemplo: Usando uma matriz de dimensão única {% data reusables.actions.jobs.single-dimension-matrix %} -#### Example: Using a multi-dimension matrix +#### Exemplo: Usando uma matriz de múltiplas dimensões {% data reusables.actions.jobs.multi-dimension-matrix %} -#### Example: Using contexts to create matrices +#### Exemplo: Usando contextos para criar matrizes {% data reusables.actions.jobs.matrix-from-context %} @@ -803,11 +803,11 @@ Use `jobs..strategy` to use a matrix strategy for your jobs. {% data reu {% data reusables.actions.jobs.matrix-include %} -#### Example: Expanding configurations +#### Exemplo: Expandir configurações {% data reusables.actions.jobs.matrix-expand-with-include %} -#### Example: Adding configurations +#### Exemplo: Adicionar configurações {% data reusables.actions.jobs.matrix-add-with-include %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md index ab7c726064..06f24815ea 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -26,14 +26,14 @@ Após habilitar a licença {% data variables.product.prodname_github_connect %}, Após configurar a conexão entre {% data variables.product.product_location %} e {% data variables.product.prodname_ghe_cloud %}, você pode habilitar funcionalidades individuais de {% data variables.product.prodname_github_connect %} para a sua empresa. -| Funcionalidade | Descrição | Mais informações | -| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} +| Funcionalidade | Descrição | Mais informações | +| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} | Sincronização automática da licença do usuário | Gerencie o uso da licença entre as suas implantações de {% data variables.product.prodname_enterprise %} sincronizando automaticamente as licenças de usuários de {% data variables.product.product_location %} para {% data variables.product.prodname_ghe_cloud %}. | "[Habilitando a sincronização automática de licença de usuário para sua empresa](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} | {% data variables.product.prodname_dependabot %} | Permite aos usuários encontrar e corrigir vulnerabilidades nas dependências do código. | "[Habilitando {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} -| Ações de {% data variables.product.prodname_dotcom_the_website %} | Permitir que os usuários usem ações de {% data variables.product.prodname_dotcom_the_website %} em arquivos de fluxo de trabalho. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} -| {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} -| Pesquisa unificada | Permitir que os usuários incluam repositórios em {% data variables.product.prodname_dotcom_the_website %} nos seus resultados de pesquisa ao pesquisar em {% data variables.product.product_location %}. | "[Habilitando {% data variables.product.prodname_unified_search %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | -| Contribuições unificadas | Permitir que os usuários incluam o número de contribuições anonimizadas pelo trabalho deles em {% data variables.product.product_location %} nos seus gráficos de contribuição em {% data variables.product.prodname_dotcom_the_website %}. | "[Habilitando {% data variables.product.prodname_unified_contributions %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | +| Ações de {% data variables.product.prodname_dotcom_the_website %} | Permitir que os usuários usem ações de {% data variables.product.prodname_dotcom_the_website %} em arquivos de fluxo de trabalho. | "[Hbilitando o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} +| {% data variables.product.prodname_server_statistics %} | Analise os seus próprios dados agregados do servidor do GitHub Enterprise e ajude-nos a melhorar os produtos do GitHub. | "[Habilitando {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} +| Pesquisa unificada | Permitir que os usuários incluam repositórios em {% data variables.product.prodname_dotcom_the_website %} nos seus resultados de pesquisa ao pesquisar em {% data variables.product.product_location %}. | "[Habilitando {% data variables.product.prodname_unified_search %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | +| Contribuições unificadas | Permitir que os usuários incluam o número de contribuições anonimizadas pelo trabalho deles em {% data variables.product.product_location %} nos seus gráficos de contribuição em {% data variables.product.prodname_dotcom_the_website %}. | "[Habilitando {% data variables.product.prodname_unified_contributions %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | ## Transmissão de dados para {% data variables.product.prodname_github_connect %} @@ -62,15 +62,15 @@ Ao habilitar {% data variables.product.prodname_github_connect %} ou funcionalid Os dados adicionais são transmitidos se você habilitar as funcionalidades individuais de {% data variables.product.prodname_github_connect %}. -| Funcionalidade | Dados | Para onde os dados são transmitidos? | Onde os dados são usados? | -| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Sincronização automática da licença do usuário | O ID de usuário de cada {% data variables.product.product_name %} e endereço de e-mail | De {% data variables.product.product_name %} para {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} -| {% data variables.product.prodname_dependabot_alerts %} | Alertas de vulnerabilidade | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} -| {% data variables.product.prodname_dependabot_updates %} | As dependências e metadados para o repositório de cada dependência

Se uma dependência for armazenada em um repositório privado em {% data variables.product.prodname_dotcom_the_website %}, os dados só serão transmitidos se {% data variables.product.prodname_dependabot %} estiver configurado e autorizado para acessar esse repositório. | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} -| Ações de {% data variables.product.prodname_dotcom_the_website %} | Nome da ação, ação (arquivo YAML de {% data variables.product.prodname_marketplace %}) | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} -| {% data variables.product.prodname_server_statistics %} | Aggregate {% data variables.product.prodname_ghe_server %} usage metrics
For the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | De {% data variables.product.product_name %} para {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} -| Pesquisa unificada | Termos de pesquisa, resultados de pesquisa | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} -| Contribuições unificadas | Contagens de contribuição | De {% data variables.product.product_name %} paraa {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} +| Funcionalidade | Dados | Para onde os dados são transmitidos? | Onde os dados são usados? | +| ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} +| Sincronização automática da licença do usuário | O ID de usuário de cada {% data variables.product.product_name %} e endereço de e-mail | De {% data variables.product.product_name %} para {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} +| {% data variables.product.prodname_dependabot_alerts %} | Alertas de vulnerabilidade | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} +| {% data variables.product.prodname_dependabot_updates %} | As dependências e metadados para o repositório de cada dependência

Se uma dependência for armazenada em um repositório privado em {% data variables.product.prodname_dotcom_the_website %}, os dados só serão transmitidos se {% data variables.product.prodname_dependabot %} estiver configurado e autorizado para acessar esse repositório. | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} +| Ações de {% data variables.product.prodname_dotcom_the_website %} | Nome da ação, ação (arquivo YAML de {% data variables.product.prodname_marketplace %}) | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} +| {% data variables.product.prodname_server_statistics %} | Agrege métricas de uso de {% data variables.product.prodname_ghe_server %}
Para a lista de métricas agregadas coletadas, consulte "[dados coletados de {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | De {% data variables.product.product_name %} para {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} +| Pesquisa unificada | Termos de pesquisa, resultados de pesquisa | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} +| Contribuições unificadas | Contagens de contribuição | De {% data variables.product.product_name %} paraa {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} ## Leia mais diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md index 78dbb6fb4b..2d5a3a6d17 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md @@ -22,7 +22,7 @@ shortTitle: Sincronização automática da licença do usuário {% data reusables.enterprise-licensing.about-license-sync %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_connect %}de](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)." -If you enable automatic user license sync for your enterprise, {% data variables.product.prodname_github_connect %} will automatically synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly.{% ifversion ghes > 3.4 %} You can also synchronize your license data at any time outside of the automatic weekly sync, by manually triggering a license sync job. For more information, see "[Triggering a license sync job](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#triggering-a-license-sync-job)."{% endif %} +Se você habilitar a sincronização automática da licença de usuário para sua empresa, {% data variables.product.prodname_github_connect %} irá sincronizar automaticamente o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %} semanalmente.{% ifversion ghes > 3.4 %} Você também pode sincronizar os dados da sua licença a qualquer momento fora da sincronização automática semanal, acionando manualmente um trabalho de sincronização. Para obter mais informações, consulte "[Acionar um trabalho de sincronização de licença](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#triggering-a-license-sync-job)".{% endif %} Se você usar várias instâncias de {% data variables.product.prodname_ghe_server %}, você pode habilitar a sincronização automática de licença entre cada uma de suas instâncias e a mesma organização ou conta corporativa em {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 2eb302561d..6b90321137 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -43,7 +43,7 @@ Também é possível sincronizar os dados de vulnerabilidade manualmente a qualq {% note %} -**Note:** When you enable {% data variables.product.prodname_dependabot_alerts %}, no code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. +**Observação:** Ao habilitar {% data variables.product.prodname_dependabot_alerts %}, nenhum código ou informação sobre o código de {% data variables.product.product_location %} será enviado para {% data variables.product.prodname_dotcom_the_website %}. {% endnote %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md index dd5d784b14..944ace1a94 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md @@ -1,31 +1,31 @@ --- -title: Enabling Server Statistics for your enterprise -intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.' +title: Habilitando as estatísticas do servidor para a sua empresa +intro: 'Você pode analisar seus próprios dados agregados de {% data variables.product.prodname_ghe_server %} e nos ajudar a melhorar {% data variables.product.company_short %} produtos, habilitando {% data variables.product.prodname_server_statistics %}.' versions: feature: server-statistics redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics/enabling-server-statistics topics: - Enterprise -shortTitle: Server Statistics +shortTitle: Estatísticas do servidor --- {% data reusables.server-statistics.release-phase %} ## Sobre {% data variables.product.prodname_server_statistics %} -{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.product.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. +{% data variables.product.prodname_server_statistics %} coleta os dados de uso agregados de {% data variables.product.product_location %}, os quais você pode usar para prever melhor as necessidades da sua organização, entender como a sua equipe funciona e mostrar o valor que você obtém de {% data variables.product.prodname_ghe_server %}. -{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." +{% data variables.product.prodname_server_statistics %} coleta apenas certas métricas agregadas em repositórios, problemas, pull requests e outras funcionalidades.{% data variables.product.prodname_dotcom %} conteúdo, como código, problemas, comentários ou conteúdo do pull request, não é coletado. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." -By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you. +Ao habilitar, {% data variables.product.prodname_server_statistics %}, você também está ajudando a melhorar {% data variables.product.company_short %}. Os dados agregados que você fornecerá nos ajuda a entender como nossos clientes estão usando {% data variables.product.prodname_dotcom %} e a tomar decisões melhores e mais informadas sobre o produto, o que beneficia você. ## Habilitar o {% data variables.product.prodname_server_statistics %} -Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)". +Antes de poder habilitar {% data variables.product.prodname_server_statistics %}, primeiro você deve conectar sua instância do {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %} através de {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)". -You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time. +Você pode desabilitar {% data variables.product.prodname_server_statistics %} de {% data variables.product.prodname_ghe_server %} a qualquer momento. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**. ![Screenshot of {% data variables.product.prodname_server_statistics %} drop-down menu with disabled or enabled options](/assets/images/help/server-statistics/server-statistics-enable-disable-options.png) +4. Em "Compartilhar as estatísticas do servidor de GitHub.com", selecione o menu suspenso e clique em **Habilitado** ou **Desabilitado**. ![Captura de tela do menu suspenso de {% data variables.product.prodname_server_statistics %} com opções habilitadas ou desabilitadas](/assets/images/help/server-statistics/server-statistics-enable-disable-options.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md index 9098aa7a4a..bd103d384f 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md @@ -41,7 +41,7 @@ Quando o isolamento do subdomínio está ativado, o {% data variables.product.pr | `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | | `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | | `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %} -| Not supported | `https://containers.HOSTNAME/` +| Não compatível | `https://containers.HOSTNAME/` {% endif %} ## Pré-requisitos diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md index bbcf7da2bb..976d5635cb 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md @@ -131,7 +131,7 @@ $ ghe-restore -c 169.154.1.1 ``` {% if ip-exception-list %} -Optionally, to validate the restore, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." +Opcionalmente, para validar a restauração, configure uma lista de exceções IP para permitir o acesso a uma lista especificada de endereços IP. Para obter mais informações, consulte "[Validando as alterações no modo de manutenção usando a lista de exceção de IP](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)". {% endif %} {% note %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md index 3b19ff2620..911fda26ea 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md @@ -35,9 +35,9 @@ Os proprietários das empresas podem configurar e-mails para notificações. - Selecione o menu suspenso **Autenticação** e escolha o tipo de criptografia usado pelo seu servidor SMTP. - No campo **No-reply email address** (Endereço de e-mail no-reply), digite o endereço de e-mail para usar nos campos De e Para em todos os e-mails de notificação. 6. Se você quiser descartar todos os e-mails recebidos destinados ao endereço no-reply, selecione **Discard email addressed to the no-reply email address** (Descartar e-mails recebidos no endereço no-reply). ![Caixa de seleção para descartar e-mails destinados ao endereço no-reply](/assets/images/enterprise/management-console/discard-noreply-emails.png) -7. Under **Support**, choose a type of link to offer additional support to your users. - - **Email:** An internal email address. - - **URL:** A link to an internal support site. Você deve incluir `http://` ou `https://`. ![E-mail ou URL de suporte](/assets/images/enterprise/management-console/support-email-url.png) +7. Em **Suporte**, escolha um tipo de link para dar suporte adicional aos seus usuários. + - **Email:** Endereço de e-mail interno. + - **URL:** Link para um site interno de suporte. Você deve incluir `http://` ou `https://`. ![E-mail ou URL de suporte](/assets/images/enterprise/management-console/support-email-url.png) 8. [Teste a entrega de e-mails](#testing-email-delivery). {% elsif ghae %} {% data reusables.enterprise-accounts.access-enterprise %} @@ -86,7 +86,7 @@ Se quiser permitir o recebimento de respostas para os e-mails de notificação, ### Criar um pacote de suporte -If you cannot determine what is wrong from the displayed error message, you can download a [support bundle](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) containing the entire SMTP conversation between your mail server and {% data variables.product.prodname_ghe_server %}. Once you've downloaded and extracted the bundle, check the entries in *enterprise-manage-logs/unicorn.log* for the entire SMTP conversation log and any related errors. +Se não for possível determinar o que houve de errado na mensagem de erro exibida, você pode fazer o download de um [pacote de suporte](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) com toda a conversa SMTP entre o seu servidor de e-mail e o {% data variables.product.prodname_ghe_server %}. Depois de fazer o download e extrair o pacote, verifique as entradas em *enterprise-manage-logs/unicorn.log* e veja o log completo de conversas do SMTP com os erros relacionados. O log unicorn mostrará uma transação semelhante a esta: @@ -131,7 +131,7 @@ Esse log mostra que o appliance: Se você tiver de verificar o funcionamento do dos e-mails de entrada, examine dois arquivos de log na sua instância: */var/log/mail.log* e */var/log/mail-replies/metroplex.log*. -*/var/log/mail.log* verifies that messages are reaching your server. Veja um exemplo de resposta de e-mail com êxito: +*/var/log/mail.log* verifica se as mensagens estão chegando ao seu servidor. Veja um exemplo de resposta de e-mail com êxito: ``` Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: conectado de st11p06mm-asmtp002.mac.com[17.172.124.250] @@ -145,7 +145,7 @@ Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: desconectado de st11p06mm-asm Observe que o cliente se conecta e depois a fila fica ativa. Em seguida, a mensagem é entregue, o cliente é removido da fila e a sessão é desconectada. -*/var/log/mail-replies/metroplex.log* shows whether inbound emails are being processed to add to issues and pull requests as replies. Veja um exemplo de mensagem com êxito: +*/var/log/mail-replies/metroplex.log* mostra se os e-mails de entrada estão sendo processados para adicionar problemas e pull requests como respostas. Veja um exemplo de mensagem com êxito: ``` [2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing @@ -161,7 +161,7 @@ Para processar corretamente os e-mails de entrada, você deve configurar um regi ### Verificar as configurações de firewall ou grupo de segurança do AWS -If {% data variables.product.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`. +Se a {% data variables.product.product_location %} estiver atrás de um firewall ou estiver funcionando com um grupo de segurança do AWS, verifique se a porta 25 está aberta para todos os servidores de e-mail que enviam mensagens para `reply@reply.[hostname]`. ### Entrar em contato com o suporte {% ifversion ghes %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md index d7d7d34dc7..e736c95b0e 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md @@ -1,7 +1,7 @@ --- -title: Configuring web commit signing -shortTitle: Configure web commit signing -intro: 'You can enable auto-signing of commits made in the web interface of {% data variables.product.product_name %}.' +title: Configurando assinatura do commit da web +shortTitle: Configurar assinatura do commit da web +intro: 'Você pode habilitar a assinatura automática de commits criados na interface web de {% data variables.product.product_name %}.' versions: ghes: '>=3.5' type: how_to @@ -14,57 +14,57 @@ topics: permissions: 'Site administrators can configure web commit signing for {% data variables.product.product_location %}.' --- -## About web commit signing +## Sobre a assinatura do commit da web -If you enable web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits users make on the web interface of {% data variables.product.product_location %}. Commits signed by {% data variables.product.product_name %} will have a verified status. Para obter mais informações, consulte "[Sobre verificação de assinatura commit](/authentication/managing-commit-signature-verification/about-commit-signature-verification)". +Se você habilitar a assinatura de commit da web, {% data variables.product.product_name %} usará o GPG automaticamente para assinar commits que os usuários fazem na interface web de {% data variables.product.product_location %}. Os commits assinados por {% data variables.product.product_name %} terão um status verificado. Para obter mais informações, consulte "[Sobre verificação de assinatura commit](/authentication/managing-commit-signature-verification/about-commit-signature-verification)". -You can enable web commit signing, rotate the private key used for web commit signing, and disable web commit signing. +Você pode habilitar a assinatura do commit da web, girar a chave privada usada para a assinatura de web commit e desabilitar a assinatura do commit da web. -## Enabling web commit signing +## Habilitando a assinatura de commit da web {% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %} - - If you have a no-reply email address defined in the {% data variables.enterprise.management_console %}, use that email address. If not, use any email address, such as `web-flow@my-company.com`. The email address does not need to be valid. + - Se você tiver um endereço de e-mail sem resposta definido em {% data variables.enterprise.management_console %}, use esse endereço de e-mail. Caso contrário, use qualquer endereço de e-mail, como `web-flow@my-company.com`. O endereço de e-mail não precisa ser válido. {% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} {% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} {% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} -1. Enable web commit signing. +1. Habilitar assinatura do commit da web. ```bash{:copy} ghe-config app.github.web-commit-signing-enabled true ``` -1. Apply the configuration, then wait for the configuration run to complete. +1. Aplique a configuração e, em seguida, aguarde até que a configuração seja concluída. ```bash{:copy} ghe-config-apply ``` -1. Create a new user on {% data variables.product.product_location %} via built-in authentication or external authentication. Para obter mais informações, consulte "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". - - The user's username must be `web-flow`. - - The user's email address must be the same address you used for the PGP key. +1. Crie um novo usuário em {% data variables.product.product_location %} por meio da autenticação integrada ou autenticação externa. Para obter mais informações, consulte "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". + - O nome de usuário do usuário deve ser `web-flow`. + - O endereço de e-mail do usuário deve ser o mesmo endereço usado para a chave PGP. {% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} {% data reusables.enterprise_site_admin_settings.email-settings %} -1. Under "No-reply email address", type the same email address you used for the PGP key. +1. Em "Endereço de e-mail de não responda", digite o mesmo endereço de e-mail que você usou para a chave PGP. {% note %} - **Note:** The "No-reply email address" field will only be displayed if you've enabled email for {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar e-mail para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-smtp-for-your-enterprise). + **Observação:** O campo "Endereço de e-mail não responda" será exibido somente se você habilitou o e-mail para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar e-mail para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-smtp-for-your-enterprise). {% endnote %} {% data reusables.enterprise_management_console.save-settings %} -## Rotating the private key used for web commit signing +## Girando a chave privada usada para a assinatura do commit web {% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %} - - Use the no-reply email address defined in the {% data variables.enterprise.management_console %}, which should be the same as the email address of the `web-flow` user. + - Use o endereço de e-mail de não responda definido no {% data variables.enterprise.management_console %}, que deve ser o mesmo que o endereço de e-mail do usuário de `web-flow`. {% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} {% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} {% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} {% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} -## Disabling web commit signing +## Desabilitar a assinatura do commit da web -You can disable web commit signing for {% data variables.product.product_location %}. +Você pode desabilitar a assinatura do commit da web para {% data variables.product.product_location %}. -1. In the administrative shell, run the following command. +1. No terminal administrativo, execute o seguinte comando. ```bash{:copy} ghe-config app.github.web-commit-signing-enabled false diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md index 9ad1706f5e..e9cd2dea6c 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md @@ -43,7 +43,7 @@ Quando a instância estiver em modo de manutenção, todos os acessos regulares {% if ip-exception-list %} -You can perform initial validation of your maintenance operation by configuring an IP exception list to allow access to {% data variables.product.product_location %} from only the IP addresses and ranges provided. Attempts to access {% data variables.product.product_location %} from IP addresses not specified on the IP exception list will receive a response consistent with those sent when the instance is in maintenance mode. +Você pode executar a validação inicial da sua operação de manutenção configurando uma lista de exceção de IP para permitir acesso a {% data variables.product.product_location %} apenas dos endereços IP e das faixas fornecidas. As tentativas de acessar {% data variables.product.product_location %} de endereços IP não especificados na lista de exceções IP receverão uma resposta consistente com aquelas enviadas quando a instância estiver em modo de manutenção. {% endif %} @@ -60,18 +60,18 @@ You can perform initial validation of your maintenance operation by configuring {% if ip-exception-list %} -## Validating changes in maintenance mode using the IP exception list +## Validando alterações no modo de manutenção usando a lista de exceção de IP -The IP exception list provides controlled and restricted access to {% data variables.product.product_location %}, which is ideal for initial validation of server health following a maintenance operation. Once enabled, {% data variables.product.product_location %} will be taken out of maintenance mode and available only to the configured IP addresses. The maintenance mode checkbox will be updated to reflect the change in state. +A lista de exceções de IP fornece acesso controlado e restrito a {% data variables.product.product_location %}, o que é ideal para validação inicial de saúde do servidor após uma operação de manutenção. Uma vez habilitado, {% data variables.product.product_location %} será retirado do modo de manutenção e disponibilizado apenas para os endereços IP configurados. A caixa de seleção do modo de manutenção será atualizada para refletir a alteração no estado. -If you re-enable maintenance mode, the IP exception list will be disabled and {% data variables.product.product_location %} will return to maintenance mode. If you just disable the IP exception list, {% data variables.product.product_location %} will return to normal operation. +Se você reabilitar o modo de manutenção, a lista de exceções de IP será desabilitada e {% data variables.product.product_location %} retornará ao modo de manutenção. Se você desabilitar a lista de exceção de IP, {% data variables.product.product_location %} retornará para a operação normal. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -1. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**, and confirm maintenance mode is already enabled. ![Guia de manutenção](/assets/images/enterprise/management-console/maintenance-tab.png) -1. Select **Enable IP exception list**. ![Checkbox for enabling ip exception list](/assets/images/enterprise/maintenance/enable-ip-exception-list.png) -1. In the text box, type a valid list of space-separated IP addresses or CIDR blocks that should be allowed to access {% data variables.product.product_location %}. ![completed field for IP addresses](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png) -1. Clique em **Salvar**. ![after IP excetpion list has saved](/assets/images/enterprise/maintenance/ip-exception-save.png) +1. Na parte superior do {% data variables.enterprise.management_console %}, clique em **Manutenção** e confirme que o modo de manutenção já está habilitado. ![Guia de manutenção](/assets/images/enterprise/management-console/maintenance-tab.png) +1. Selecione **Habilitar lista de exceção de IP**. ![Caixa de seleção para habilitar lista de exceções de IP](/assets/images/enterprise/maintenance/enable-ip-exception-list.png) +1. Na caixa de texto, digite uma lista válida de endereços IP separados por espaço ou blocos CIDR que devem ter permissão para acessar {% data variables.product.product_location %}. ![campo concluído para endereços IP](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png) +1. Clique em **Salvar**. ![após a lista de excetpion IP ter salvo](/assets/images/enterprise/maintenance/ip-exception-save.png) {% endif %} diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md index 843fd39ad7..61e4e25984 100644 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md +++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md @@ -24,7 +24,7 @@ shortTitle: Aumentar capacidade de armazenamento {% note %} -**Note:** Before resizing any storage volume, put your instance in maintenance mode.{% if ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +**Observação:** Antes de redimensionar qualquer volume de armazenamento, coloque sua instância no modo de manutenção.{% if ip-exception-list %} Você pode validar as alterações configurando uma lista de exceção IP para permitir o acesso a endereços IP especificados. {% endif %} Para obter mais informações, consulte "[Habilitando e agendando o modo de manutenção](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)". {% endnote %} diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 0dd51a2a1a..ec138c0fda 100644 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -175,7 +175,7 @@ Mesmo que seja possível usar um hotpatch para fazer a atualização do patch em Proceed with installation? [y/N] ``` {% if ip-exception-list %} -1. Optionally, to validate the upgrade, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." +1. Opcionalmente, para validar a atualização, configure uma lista de exceções IP para permitir o acesso a uma lista especificada de endereços IP. Para obter mais informações, consulte "[Validando as alterações no modo de manutenção usando a lista de exceção de IP](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)". {% endif %} 7. Em atualizações de appliance único, desabilite o modo de manutenção para os usuários poderem trabalhar com a {% data variables.product.product_location %}. diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md index 2c4bfa1d87..0eda60bf7b 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md @@ -1,6 +1,6 @@ --- title: Habilitar o GitHub Actions com armazenamento do Amazon S3 -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store data generated by workflow runs.' +intro: 'Você pode habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} e usar o armazenamento Amazon S3 para armazenar dados gerados por execuções de fluxo de trabalho.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghes: '*' @@ -21,7 +21,7 @@ shortTitle: Armazenamento do Amazon S3 Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: -* Create your Amazon S3 bucket for storing data generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} +* Crie seu bucket do Amazon S3 para armazenar dados gerados pelas execuções do fluxo de trabalho. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md index 468838ed57..5d93e29f6c 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md @@ -1,6 +1,6 @@ --- title: Habilitar o o GitHub Actions com armazenamento do Azure Blob -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store data generated by workflow runs.' +intro: 'Você pode habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} e usar o Azure Blob Storage para armazenar dados gerados por execuções do fluxo de trabalho.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghes: '*' @@ -19,7 +19,7 @@ shortTitle: Armazenamento do Azure Blob Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: -* Create your Azure storage account for storing workflow data. {% data variables.product.prodname_actions %} armazena seus dados como blobs de bloco, e dois tipos de conta de armazenamento são compatíveis: +* Crie sua conta de armazenamento do Azure para armazenar dados de fluxo de trabalho. {% data variables.product.prodname_actions %} armazena seus dados como blobs de bloco, e dois tipos de conta de armazenamento são compatíveis: * Uma conta de armazenamento para **propósitos gerais** (também conhecida como `propósito geral v1` ou `propósito geral v2`) que usa o nível de desempenho **padrão**. {% warning %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index a6bb252222..b8dd73765e 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -1,6 +1,6 @@ --- title: Habilitar o GitHub Actions com MinIO Gateway para armazenamento NAS -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store data generated by workflow runs.' +intro: 'Você pode habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} e usar MinIO Gateway para armazenamento NAS para armazenar dados gerados por execuções de fluxo de trabalho.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghes: '*' @@ -22,7 +22,7 @@ shortTitle: MinIO Gateway para armazenamento NAS Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: * Para evitar contenção de recursos no dispositivo, recomendamos que o MinIO seja hospedado separadamente de {% data variables.product.product_location %}. -* Create your bucket for storing workflow data. Para configurar seu bucket e chave de acesso, consulte a [Documentação do MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} +* Crie seu bucket para armazenar dados de fluxo de trabalho. Para configurar seu bucket e chave de acesso, consulte a [Documentação do MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %} diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index 7e7be8d6ef..82d7b03806 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -39,7 +39,7 @@ Você pode criar suas próprias automações exclusivas ou você pode usar e ada {% ifversion ghec %}Você pode desfrutar da conveniência de executores hospedados em {% data variables.product.company_short %}, que são mantidos e atualizados por {% data variables.product.company_short %} ou você{% else %}{% endif %} pode controlar a sua própria infraestrutura privada de CI/CD usando executores auto-hospedados. Os executores auto-hospedados permitem que você determine o ambiente exato e os recursos que completam suas compilações, testes e implantações sem expor o seu ciclo de desenvolvimento de software à internet. Para obter mais informações, consulte {% ifversion ghec %}"[Sobre executores auto-hospedados em {% data variables.product.company_short %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" e {% endif %} "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)." -{% data variables.product.prodname_actions %} fornece maior controle sobre implantações. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 or ghes > 3.4 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC fornece benefícios de segurança, como eliminar a necessidade de armazenar credenciais como segredos de longa duração. Para obter mais informações, consulte[Sobre segurança fortalecida com OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %} +{% data variables.product.prodname_actions %} fornece maior controle sobre implantações. Por exemplo, você pode usar ambientes para exigir aprovação para um trabalho prosseguir ou restringir quais branches podem acionar um fluxo de trabalho, ou limitar o acesso a segredos.{% ifversion ghec or ghae-issue-4856 or ghes > 3.4 %} Se os seus fluxos de trabalho precisarem acessar recursos de um provedor de nuvem compatível com o OpenID Connect (OIDC), você poderá configurar seus fluxos de trabalho para efetuar a autenticação diretamente no provedor de nuvem. OIDC fornece benefícios de segurança, como eliminar a necessidade de armazenar credenciais como segredos de longa duração. Para obter mais informações, consulte[Sobre segurança fortalecida com OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %} {% data variables.product.prodname_actions %} também inclui ferramentas para governar o ciclo de desenvolvimento de software da sua empresa e atender às obrigações de conformidade. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)". diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index 3b766c94b2..227b3603dd 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -26,7 +26,7 @@ Este artigo explica como os administradores do site podem configurar {% data var {% data reusables.enterprise.upgrade-ghes-for-actions %} -{% data reusables.actions.ghes-actions-not-enabled-by-default %} Você deberá determinar se a sua instância possui recursos adequados de CPU e memória para lidar com a carga do {% data variables.product.prodname_actions %} sem causar perda de desempenho e possivelmente aumentar esses recursos. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% if actions-caching %} and caches{% endif %} generated by workflow runs. Em seguida, você irá habilitar {% data variables.product.prodname_actions %} para a sua empresa, gerenciar permissões de acesso e adicionar executores auto-hospedados para executar fluxos de trabalho. +{% data reusables.actions.ghes-actions-not-enabled-by-default %} Você deberá determinar se a sua instância possui recursos adequados de CPU e memória para lidar com a carga do {% data variables.product.prodname_actions %} sem causar perda de desempenho e possivelmente aumentar esses recursos. Você também precisará decidir qual provedor de armazenamento irá usar para o armazenamento do blob necessário para armazenar os artefatos{% if actions-caching %} e caches{% endif %} gerados pela execução do fluxo de trabalho. Em seguida, você irá habilitar {% data variables.product.prodname_actions %} para a sua empresa, gerenciar permissões de acesso e adicionar executores auto-hospedados para executar fluxos de trabalho. {% data reusables.actions.introducing-enterprise %} @@ -81,6 +81,20 @@ A simultaneidade máxima foi medida usando vários repositórios, a duração do {%- endif %} +{%- ifversion ghes = 3.5 %} + +{% data reusables.actions.hardware-requirements-3.5 %} + +{% data variables.product.company_short %} measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância. + +{% note %} + +**Note:** Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}. + +{% endnote %} + +{%- endif %} + Se você planeja habilitar {% data variables.product.prodname_actions %} para os usuários de uma instância existente, revise os níveis de atividade para usuários e automações na instância e garanta que você tenha fornecido CPU e memória adequadas para seus usuários. Para obter mais informações sobre o monitoramento da capacidade e desempenho de {% data variables.product.prodname_ghe_server %}, consulte "[Monitoramento do seu aplicativo](/admin/enterprise-management/monitoring-your-appliance)". Para obter mais informações sobre os requisitos mínimos de hardware para {% data variables.product.product_location %}, consulte as considerações sobre hardware para a plataforma da sua instância. @@ -105,7 +119,7 @@ Opcionalmente, você pode limitar o consumo de recursos em {% data variables.pro Para habilitar o {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, você deve ter acesso ao armazenamento externo do blob. -{% data variables.product.prodname_actions %} uses blob storage to store data generated by workflow runs, such as workflow logs{% if actions-caching %}, caches,{% endif %} and user-uploaded build artifacts. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_actions %}. Somente uma única configuração de armazenamento externo é compatível, e você não pode usar vários provedores de armazenamento ao mesmo tempo. +{% data variables.product.prodname_actions %} usa armazenamento do blob para armazenar dados gerados pela execução de fluxo de trabalho, tais como logs de fluxo de trabalho{% if actions-caching %}, caches,{% endif %} e artefatos de compilação enviados pelo usuário. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_actions %}. Somente uma única configuração de armazenamento externo é compatível, e você não pode usar vários provedores de armazenamento ao mesmo tempo. {% data variables.product.prodname_actions %} é compatível com estes provedores de armazenamento: diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index 8596efe5e2..e9b8f3c9f6 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -111,15 +111,15 @@ Finalmente, você deve considerar o fortalecimento da segurança para os executo {% data reusables.actions.about-artifacts %} Para obter mais informações, consulte "[Armazenar dados do fluxo de trabalho como artefatos](/actions/advanced-guides/storing-workflow-data-as-artifacts)". -{% if actions-caching %}{% data variables.product.prodname_actions %} also has a caching system that you can use to cache dependencies to speed up workflow runs. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %} +{% if actions-caching %}{% data variables.product.prodname_actions %} também tem um sistema de cache que você pode usar para armazenar dependências de cache a fim de acelerar as execuções do fluxo de trabalho. Para obter mais informações, consulte "[Armazenando as dependências em cache para acelerar fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".{% endif %} {% ifversion ghes %} -You must configure external blob storage for workflow artifacts{% if actions-caching %}, caches,{% endif %} and other workflow logs. Escolha qual provedor de armazenamento compatível a sua empresa irá usar. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)". +Você deve configurar o armazenamento externo de blob para artefatos de fluxo de trabalho{% if actions-caching %}, caches,{% endif %} e outros logs de fluxo de trabalho. Escolha qual provedor de armazenamento compatível a sua empresa irá usar. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)". {% endif %} {% ifversion ghec or ghes %} -You can use policy settings for {% data variables.product.prodname_actions %} to customize the storage of workflow artifacts{% if actions-caching %}, caches,{% endif %} and log retention. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)". +Você pode usar as configurações de política para {% data variables.product.prodname_actions %} para personalizar o armazenamento de artefatos de fluxo de trabalho{% if actions-caching %}, caches,{% endif %} e retenção de logs. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)". {% endif %} diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index de1f4ddbbe..a19b6c20ac 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -48,7 +48,7 @@ Cada ação é um repositório na organização de `ações`, e cada repositóri **Notas:** - Ao usar ações de configuração (como `actions/setup-LANGUAGE`) em {% data variables.product.product_name %} com executores auto-hospedados, você pode precisar configurar o armazenamento de ferramentas em executores que não possuem acesso à internet. Para obter mais informações, consulte "[Configurar o cache da ferramenta em executores auto-hospedados sem acesso à internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)". -- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated. +- As ações agrupadas são atualizadas automaticamente quando {% data variables.product.product_name %} é atualizado. {% endnote %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md index 8632f236a0..0c3be480eb 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md @@ -56,7 +56,7 @@ O {% data variables.product.prodname_managed_users_caps %} só pode contribuir p * Outros usuários de {% data variables.product.prodname_dotcom %} não podem ver, mencionar ou convidar um {% data variables.product.prodname_managed_user %} para colaborar. * {% data variables.product.prodname_managed_users_caps %} só pode criar repositórios privados e {% data variables.product.prodname_managed_users %} só pode convidar outros integrantes da empresa para colaborar nos seus próprios repositórios. * Apenas repositórios privados e internos podem ser criados em organizações pertencentes a um {% data variables.product.prodname_emu_enterprise %}, dependendo das configurações de visibilidade da organização e do repositório corporativo. -* {% data variables.product.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)". +* {% data variables.product.prodname_managed_users_caps %} são limitados em seu uso de {% data variables.product.prodname_pages %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)". ## Sobre empresas com usuários gerenciados @@ -88,8 +88,8 @@ O nome do usuário de configuração é o código curto da sua empresa com o suf ## Nome de usuário e informações de perfil -{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. Para obter mais informações, consulte "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". +{% data variables.product.product_name %} cria automaticamente um nome de usuário para cada pessoa normalizando um identificador fornecido pelo seu IdP. Para obter mais informações, consulte "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". -A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username conflicts](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts)." +Um conflito pode ocorrer quando os usuários de provisionamento das partes únicas do identificador fornecido pelo IdP são removidos durante a normalização. Se você não puder provisionar um usuário devido a um conflito de nome de usuário, você deverá modificar o nome de usuário fornecido pelo seu IdP. Para obter mais informações, consulte "[Resolvendo conflitos de nome de usuário](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts). " O nome do perfil e endereço de email de um {% data variables.product.prodname_managed_user %} também é fornecido pelo IdP. {% data variables.product.prodname_managed_users_caps %} não pode alterar seu nome de perfil ou endereço de e-mail em {% data variables.product.prodname_dotcom %}. diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md index db632b10f8..a1a9fb1206 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md @@ -33,7 +33,7 @@ shortTitle: Instalar em VMware {% data reusables.enterprise_installation.download-license %} {% data reusables.enterprise_installation.download-appliance %} -4. Under "{% data variables.product.prodname_dotcom %} On-premises", select the "Select your hypervisor" dropdown menu and click **VMware ESXi/vSphere (OVA)**. +4. Em "{% data variables.product.prodname_dotcom %} nas instalações", selecione o menu suspenso "Selecionar seu hipervisor" e clique em **VMware ESXi/vSphere (OVA)**. 5. Clique em **Download for VMware ESXi/vSphere (OVA)** (Baixar para VMware ESXi/vSphere [OVA]). ## Criar a instância do {% data variables.product.prodname_ghe_server %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md index 5896390e5c..c088fd950f 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md @@ -1,6 +1,6 @@ --- -title: About Server Statistics -intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.' +title: Sobre as estatísticas do servidor +intro: 'Você pode usar {% data variables.product.prodname_server_statistics %} para analisar seus próprios dados agregados de {% data variables.product.prodname_ghe_server %} e nos ajudar a melhorar os produtos de {% data variables.product.company_short %}.' versions: feature: server-statistics permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.' @@ -12,47 +12,47 @@ topics: {% data reusables.server-statistics.release-phase %} -## About the benefits of {% data variables.product.prodname_server_statistics %} +## Sobre os benefícios de {% data variables.product.prodname_server_statistics %} -{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. +{% data variables.product.prodname_server_statistics %} pode ajudar você a antecipar as necessidades da sua organização, entender como sua equipe funciona e mostrar o valor que você obtém de {% data variables.product.prodname_ghe_server %}. -Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +Uma vez habilitado, {% data variables.product.prodname_server_statistics %} coleta dados agregados sobre quanto determinadas funcionalidades são usadas na sua instância ao longo do tempo. Ao contrário de outros pontos de extremidade de [Estatísticas da administração da API](/rest/reference/enterprise-admin#admin-stats), que só retornam dados para o último dia, {% data variables.product.prodname_server_statistics %} fornece dados históricos de todas as métricas de {% data variables.product.prodname_server_statistics %} coletadas desde o dia em que você habilitou o recurso. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you. +Ao habilitar {% data variables.product.prodname_server_statistics %}, você está ajudando a construir um {% data variables.product.prodname_dotcom %} melhor. Os dados agregados que você nos fornece nos dão informações sobre como {% data variables.product.prodname_dotcom %} agrega valor para nossos clientes. Essas informações permite que {% data variables.product.company_short %} tome decisões de produtos melhores e mais informadas, o que irá beneficiar você. -## About data security +## Sobre a segurança de dados -We respect your data. We will never transmit data from {% data variables.product.product_location %} unless you have first given us permission to do so. +Nós respeitamos seus dados. Nunca transmitiremos dados de {% data variables.product.product_location %}, a menos que você tenha nos dado autorização para fazê-lo. -We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content. +Não coletamos dados pessoais. Também não coletamos nenhum conteúdo de {% data variables.product.company_short %}, como código, problemas, comentários ou conteúdo de pull request. -Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data. +Somente proprietários da conta corporativa conectada ou organização em {% data variables.product.prodname_ghe_cloud %} podem acessar os dados. -Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." +Apenas certas métricas agregadas são coletadas em repositórios, problemas, pull requests e outras funcionalidades. Para ver a lista de métricas agregadas coletadas, consulte "[dados coletados de {% data variables.product.prodname_server_statistics %}](#server-statistics-data-collected). " -Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates. +Quaisquer atualizações das métricas coletadas ocorrerão em versões futuras de {% data variables.product.prodname_ghe_server %} e serão descritas nas [ observações da versão de {% data variables.product.prodname_ghe_server %}](/admin/release-notes). Além disso, vamos atualizar este artigo com todas as atualizações das métricas. -For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)." +Para obter uma melhor compreensão de como armazenamos e protegemos os dados de {% data variables.product.prodname_server_statistics %}, consulte "[Segurança do GitHub](https://github.com/security)". -### About data retention and deletion +### Sobre a retenção e exclusão de dados -{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled. +{% data variables.product.company_short %} coleta dados de {% data variables.product.prodname_server_statistics %} enquanto a licença do seu {% data variables.product.prodname_ghe_server %} estiver ativa e o recurso de {% data variables.product.prodname_server_statistics %} estiver habilitado. -If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation. +If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Geralmente, excluímos dados no período de tempo especificado na nossa declaração de privacidade. Para obter mais informações, consulte [Declaração de privacidade de {% data variables.product.company_short %}](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) na documentação do {% data variables.product.prodname_dotcom_the_website %}. -### About data portability +### Sobre a portabilidade de dados -As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)." +Como proprietário de uma organização de empresa em {% data variables.product.prodname_ghe_cloud %}, você pode acessar os dados de {% data variables.product.prodname_server_statistics %} exportando os dados em um arquivo CSV ou JSON ou através da API REST DE {% data variables.product.prodname_server_statistics %}. Para obter mais informações, consulte "[Solicitando que {% data variables.product.prodname_server_statistics %} use a API REST](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" ou "[Exportando {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)". -## About disabling data collection +## Sobre desabilitar a coleta de dados -You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +Você pode desabilitar o recurso de {% data variables.product.prodname_server_statistics %} a qualquer momento. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -## {% data variables.product.prodname_server_statistics %} data collected +## Dados de {% data variables.product.prodname_server_statistics %} coletados -After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.product.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.product.product_location %}. +Após habilitar o {% data variables.product.prodname_server_statistics %}, as métricas são coletadas através de um trabalho diário executado em {% data variables.product.product_location %}. As métricas agregadas são armazenadas na conta da sua organização ou na sua conta corporativa em {% data variables.product.prodname_ghe_cloud %} e não são armazenadas em {% data variables.product.product_location %}. -The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day: +As seguintes métricas agregadas serão coletadas e transmitidas diariamente e representam a contagem total do dia: - `active_hooks` - `admin_users` - `closed_issues` @@ -95,8 +95,8 @@ The following aggregate metrics will be collected and transmitted on a daily bas - `total_wikis` - `unmergeable_pulls` -## {% data variables.product.prodname_server_statistics %} payload example +## Exemplo de carga de {% data variables.product.prodname_server_statistics %} -To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)." +Para ver um exemplo da carga de resposta para a API de {% data variables.product.prodname_server_statistics %}, consulte "[Solicitando que {% data variables.product.prodname_server_statistics %} use a API REST](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)". -To see a list of the data collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." +Para ver uma lista dos dados coletados, consulte "[ dados coletdos de {% data variables.product.prodname_server_statistics %}"](#server-statistics-data-collected)". diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md index 4e0674188b..cbff923767 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md @@ -1,7 +1,7 @@ --- -title: Exporting Server Statistics -shortTitle: Export Server Statistics -intro: 'You can use your own tools to analyze your {% data variables.product.prodname_ghe_server %} usage over time by downloading your {% data variables.product.prodname_server_statistics %} metrics in a CSV or JSON file.' +title: Exportando as estatísticas do servidor +shortTitle: Exportação das estatísticas do servidor +intro: 'Você pode usar suas próprias ferramentas para analisar seu uso de {% data variables.product.prodname_ghe_server %} ao longo do tempo, fazendo o download das suas métricas de {% data variables.product.prodname_server_statistics %} para um arquivo CSV ou JSON.' versions: feature: server-statistics redirect_from: @@ -10,34 +10,34 @@ redirect_from: {% data reusables.server-statistics.release-phase %} -You can download up to the last 365 days of {% data variables.product.prodname_server_statistics %} data in a CSV or JSON file. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. +Você pode fazer o download dos últimos 365 dias de dados de {% data variables.product.prodname_server_statistics %} para um arquivo CSV ou JSON. Estes dados, que incluem métricas agregadas em repositórios, problemas e pull requests, podem ajudar você a antecipar as necessidades da sua organização, entender como sua equipe funciona e mostrar o valor que você obtém de {% data variables.product.prodname_ghe_server %}. -Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +Antes de poder fazer o download desses dados, você deverá habilitar {% data variables.product.prodname_server_statistics %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -To preview the metrics available to download, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." +Para visualizar as métricas disponíveis para fazer o download, consulte "[Sobre {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." -To download these metrics, you must be an enterprise owner or organization owner on {% data variables.product.prodname_ghe_cloud %}. - - If {% data variables.product.product_location %} is connected to an enterprise account on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your enterprise account](#downloading-metrics-from-your-enterprise-account)." - - If {% data variables.product.product_location %} is connected to an organization on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your organization](#downloading-metrics-from-your-organization)." +Para fazer o download dessas métricas, você deve ser um proprietário de uma empresa ou de uma organização em {% data variables.product.prodname_ghe_cloud %}. + - Se {% data variables.product.product_location %} estiver conectado a uma conta corporativa em {% data variables.product.prodname_ghe_cloud %}, consulte "[Fazendo o download das métricas da sua conta corporativa](#downloading-metrics-from-your-enterprise-account)". + - Se {% data variables.product.product_location %} estiver conectado a uma organização em {% data variables.product.prodname_ghe_cloud %}, consulte "[Fazendo o download das métricas da sua organização](#downloading-metrics-from-your-organization)". Para saber mais sobre {% data variables.product.prodname_github_connect %}, consulte "[Sobre {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." -## Downloading metrics from your enterprise account +## Fazendo o download das métricas da sua conta corporativa -1. No canto superior direito de {% data variables.product.prodname_ghe_cloud %}, clique na sua foto de perfil e, em seguida, clique em **Suas empresas**. ![Drop down menu with "Your enterprises" option](/assets/images/help/enterprises/enterprise-admin-account-settings.png) +1. No canto superior direito de {% data variables.product.prodname_ghe_cloud %}, clique na sua foto de perfil e, em seguida, clique em **Suas empresas**. ![Menu suspenso com a opção "Suas empresas"](/assets/images/help/enterprises/enterprise-admin-account-settings.png) -2. Next to your desired enterprise account, click **Settings**. ![Settings button next to Enterprise admin account](/assets/images/help/enterprises/enterprise-admin-account-settings-button.png) +2. Ao lado da conta corporativa desejada, clique em **Configurações**. ![Botão de configurações ao lado da conta do administrador da empresa](/assets/images/help/enterprises/enterprise-admin-account-settings-button.png) -3. On the left, click **GitHub Connect**. ![GitHub Connect option under enterprise admin account](/assets/images//help/enterprises/enterprise-admin-github-connect.png) +3. À esquerda, clique em **GitHub Connect**. ![Opção GitHub Connect na conta do administrador corporativo](/assets/images//help/enterprises/enterprise-admin-github-connect.png) {% data reusables.server-statistics.csv-download %} -## Downloading metrics from your organization +## Fazendo o download das métricas da conta da sua organização -1. In the top-right corner of {% data variables.product.prodname_ghe_cloud %}, click your profile photo, then click **Your organizations**. ![Drop down menu with "Your organizations" option](/assets/images/help/enterprises/github-enterprise-cloud-organizations.png) +1. No canto superior direito do {% data variables.product.prodname_ghe_cloud %}, clique na sua foto do seu perfil e, em seguida, clique em **Suas organizações**. ![Menu suspenso com a opção "Suas organizações"](/assets/images/help/enterprises/github-enterprise-cloud-organizations.png) -2. In the list of organizations, next to the organization that's connected to {% data variables.product.product_location %}, click **Settings**. ![Settings button next to {% data variables.product.prodname_ghe_cloud %} organization](/assets/images/help/enterprises/settings-for-ghec-org.png) +2. Na lista de organizações, ao lado da organização conectada ao {% data variables.product.product_location %}, clique em **Configurações**. ![Botão de configurações ao lado da organização de {% data variables.product.prodname_ghe_cloud %}](/assets/images/help/enterprises/settings-for-ghec-org.png) -3. On the left, click **GitHub Connect**. ![GitHub Connect option in an organization account settings left sidebar](/assets/images/help/enterprises/github-connect-option-for-ghec-org.png) +3. À esquerda, clique em **GitHub Connect**. ![Opção do GitHub Connect em configurações de uma conta à esquerda da barra lateral](/assets/images/help/enterprises/github-connect-option-for-ghec-org.png) {% data reusables.server-statistics.csv-download %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md index 507a57ae5f..9ad0d3a101 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md @@ -1,7 +1,7 @@ --- -title: Analyzing how your team works with Server Statistics -shortTitle: Server Statistics -intro: 'To analyze how your team works, understand the value you get from {% data variables.product.prodname_ghe_server %}, and help us improve our products, you can use {% data variables.product.prodname_server_statistics %} to review your usage data for {% data variables.product.prodname_ghe_server %} and share this aggregate data with {% data variables.product.company_short %}.' +title: Analisando como sua equipe funciona com as estatísticas do servidor +shortTitle: Estatísticas do servidor +intro: 'Para analisar como a sua equipe funciona, entenda o valor que você obtém da {% data variables.product.prodname_ghe_server %} e ajude-nos a melhorar nossos produtos, você pode usar {% data variables.product.prodname_server_statistics %} para revisar ps seus dados de uso para {% data variables.product.prodname_ghe_server %} e compartilhar esses dados agregados com {% data variables.product.company_short %}.' versions: feature: server-statistics children: diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md index 3ea9101516..987ab1bb94 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md @@ -1,7 +1,7 @@ --- -title: Requesting Server Statistics using the REST API -shortTitle: Server Statistics and REST API -intro: 'You can use your own tools to analyze your {% data variables.product.prodname_ghe_server %} usage over time by requesting the {% data variables.product.prodname_server_statistics %} metrics collected using the REST API.' +title: Solicitando as estatísticas do servidor usando a API REST +shortTitle: Estatísticas do servidor e API REST +intro: 'Você pode usar suas próprias ferramentas para analisar seu uso de {% data variables.product.prodname_ghe_server %} ao longo do tempo, solicitando as métricas de {% data variables.product.prodname_server_statistics %} coletadas usando a API REST.' versions: feature: server-statistics redirect_from: @@ -10,8 +10,8 @@ redirect_from: {% data reusables.server-statistics.release-phase %} -You can request up to 365 days of metrics in a single {% data variables.product.prodname_server_statistics %} REST API request. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. For a list of the metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." +Você pode solicitar até 365 dias de métricas em um único pedido da API REST de {% data variables.product.prodname_server_statistics %}. Estes dados, que incluem métricas agregadas em repositórios, problemas e pull requests, podem ajudar você a antecipar as necessidades da sua organização, entender como sua equipe funciona e mostrar o valor que você obtém de {% data variables.product.prodname_ghe_server %}. Para ver uma lista das métricas coletadas, consulte "[ dados coletdos de {% data variables.product.prodname_server_statistics %}"](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)". -Before you can use the {% data variables.product.prodname_server_statistics %} REST API, you must enable {% data variables.product.prodname_server_statistics %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +Antes de poder usar a API REST {% data variables.product.prodname_server_statistics %}, você deve habilitar {% data variables.product.prodname_server_statistics %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -For more information about using the REST API to request server statistics, see "[Get {% data variables.product.prodname_ghe_server %} statistics](/enterprise-cloud@latest/rest/enterprise-admin/admin-stats#get-github-enterprise-server-statistics)" in the {% data variables.product.prodname_ghe_cloud %} REST API documentation. +Para obter mais informações sobre o uso da API REST para solicitar estatísticas do servidor, consulte "[Obter estatísticas de {% data variables.product.prodname_ghe_server %}](/enterprise-cloud@latest/rest/enterprise-admin/admin-stats#get-github-enterprise-server-statistics)" na documentação da API REST de {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index e1e9be8117..ada4ab71e7 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -1,6 +1,6 @@ --- title: Criar um token de acesso pessoal -intro: Você deve criar um token de acesso pessoal para usar no lugar de uma senha com a linha de comando ou com a API. +intro: You can create a personal access token to use in place of a password with the command line or with the API. redirect_from: - /articles/creating-an-oauth-token-for-command-line-use - /articles/creating-an-access-token-for-command-line-use @@ -22,7 +22,10 @@ shortTitle: Criar um PAT {% note %} -**Observação:** Se você usar {% data variables.product.prodname_cli %} para efetuar a autenticação para {% data variables.product.product_name %} na linha de comando você poderá ignorar a geração de um token de acesso pessoal e efetuar a autenticação por meio da web. Para mais informações sobre a autenticação com {% data variables.product.prodname_cli %}, consulte [`login gh`](https://cli.github.com/manual/gh_auth_login). +**Notas:** + +- If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. Para mais informações sobre a autenticação com {% data variables.product.prodname_cli %}, consulte [`login gh`](https://cli.github.com/manual/gh_auth_login). +- [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure, cross-platform alternative to using personal access tokens (PATs) and eliminates the need to manage PAT scope and expiration. For installation instructions, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository. {% endnote %} @@ -77,5 +80,5 @@ Em vez de inserir manualmente seu PAT para cada operação de HTTPS do Git, voc ## Leia mais -- "[Sobre a autenticação no GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} - "[Vencimento e revogação do Token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index d53d83c034..2f18f49404 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -50,7 +50,7 @@ Os administradores do repositório podem impor a assinatura de commit obrigatór {% data reusables.identity-and-permissions.verification-status-check %} {% ifversion fpt or ghec or ghes > 3.4 %} -{% ifversion ghes %}If a site administrator has enabled web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the web interface. Commits signed by {% data variables.product.product_name %} will have a verified status. You can verify the signature locally using the public key available at `https://HOSTNAME/web-flow.gpg`. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)." +{% ifversion ghes %}If a site administrator has enabled web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the web interface. Os commits assinados por {% data variables.product.product_name %} terão um status verificado. You can verify the signature locally using the public key available at `https://HOSTNAME/web-flow.gpg`. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)." {% else %}{% data variables.product.prodname_dotcom %} will automatically use GPG to sign commits you make using the web interface. Commits signed by {% data variables.product.prodname_dotcom %} will have a verified status. É possível verificar a assinatura localmente usando a chave pública disponível em https://github.com/web-flow.gpg. A impressão digital completa da chave é `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. Opcionalmente, você pode escolher que {% data variables.product.prodname_dotcom %} assine os commits que você fizer em {% data variables.product.prodname_codespaces %}. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)."{% endif %} diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md index a80f740d07..8dad1eb70c 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md @@ -59,7 +59,13 @@ Se você tiver instalado e conectado a {% data variables.product.prodname_mobile ## Usar a autenticação de dois fatores com a linha de comando -Após habilitação da 2FA, você deverá usar um token de acesso pessoal ou uma chave SSH em vez da senha ao acessar o {% data variables.product.product_name %} na linha de comando. +After you've enabled 2FA, you will no longer use your password to access {% data variables.product.product_name %} on the command line. Instead, use Git Credential Manager, a personal access token, or an SSH key. + +### Authenticating on the command line using Git Credential Manager + +[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure Git credential helper that runs on Windows, macOS, and Linux. For more information about Git credential helpers, see [Avoiding repetition](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) in the Pro Git book. + +Setup instructions vary based on your computer's operating system. For more information, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository. ### Autenticar na linha de comando usando HTTPS diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index dd0a5dedf5..748321e32b 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -98,6 +98,8 @@ Se ocorrer uma falha na uma criação automática de código para uma linguagem Se seu fluxo de trabalho falhar com um erro `Nenhum código fonte foi visto durante a criação` ou `O processo '/opt/hostedtoolcache/CodeQL/0. .0-20200630/x64/codeql/codeql' falhou com o código de saída 32`, isto indica que {% data variables.product.prodname_codeql %} não foi capaz de monitorar o seu código. Há várias explicações para essa falha: +1. The repository may not contain source code that is written in languages supported by {% data variables.product.prodname_codeql %}. Check the list of supported languages and, if this is the case, remove the {% data variables.product.prodname_codeql %} workflow. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql) + 1. A detecção automática da linguagem identificou uma linguagem compatível, mas não há código analisável dessa linguagem no repositório. Um exemplo típico é quando nosso serviço de detecção de linguagem encontra um arquivo associado a uma determinada linguagem de programação, como um arquivo `.h`, or `.gyp`, mas nenhum código executável correspondente está presente no repositório. Para resolver o problema, você pode definir manualmente as linguagens que você deseja analisar atualizando a lista de linguagens na matriz de linguagem`. Por exemplo, a configuração a seguir analisará somente Go, e JavaScript. 
  strategy:
     fail-fast: false
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
index 19c9dff39c..199bba4572 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
+++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
@@ -85,7 +85,7 @@ Para repositórios em que {% data variables.product.prodname_dependabot_security
 
 É possível ver todos os alertas que afetam um determinado projeto{% ifversion fpt or ghec %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório. Para obter mais informações, consulte "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
 
-Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para pessoas ou repositórios de trabalho de equipes adicionais que você possui ou para os quais tem permissões de administrador. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
+Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
 {% endif %}
 
 {% data reusables.notifications.vulnerable-dependency-notification-enable %}
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
index 973c48b0a7..20ebeef41d 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
+++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -30,7 +30,7 @@ shortTitle: Atualizações de versão do Dependabot
 
 O {% data variables.product.prodname_dependabot %} facilita a manutenção de 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 de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário.
+You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_configuration file into your repository. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário.
 
 Quando {% data variables.product.prodname_dependabot %} identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Para dependências de vendor, {% data variables.product.prodname_dependabot %} levanta um pull request para substituir diretamente a dependência desatualizada pela nova versão. 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 mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)".
 
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
index 6ba353a4bd..9d487e1c2a 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@@ -322,7 +322,7 @@ Para obter mais informações sobre os comandos `@dependabot ignore`, consulte [
 
 Você pode usar a opção `ignore` para personalizar quais dependências são atualizadas. A opção `ignore` suporta as seguintes opções.
 
-- `dependency-name`—use para ignorar atualizações para dependências com nomes correspondentes, opcionalmente usando `*` para corresponder a zero ou mais caracteres. Para dependências do Java, o formato do atributo `dependency-name` é: `groupId:artifactId` (por exemplo: `org.kohsuke:github-api`).
+- `dependency-name`—use para ignorar atualizações para dependências com nomes correspondentes, opcionalmente usando `*` para corresponder a zero ou mais caracteres. Para dependências do Java, o formato do atributo `dependency-name` é: `groupId:artifactId` (por exemplo: `org.kohsuke:github-api`). {% if dependabot-grouped-dependencies %} To prevent {% data variables.product.prodname_dependabot %} from automatically updating TypeScript type definitions from DefinitelyTyped, use `@types/*`.{% endif %}
 - `versions`—use para ignorar versões específicas ou intervalos de versões. Se você deseja definir um intervalo, use o padrão pattern para o gerenciador de pacotes (por exemplo: `^1.0.0` para npm, ou `~> 2.0` para o Bundler).
 - `update-types`—use para ignorar tipos de atualizações, como semver `major`, `minor` ou `atualizações de atualização de versão` (por exemplo: `version-update:semver-patch` ignorará atualizações de patch). Você pode combinar isso com a `dependency-name: "*"` para ignorar em `update-types` específicos para todas as dependências. Atualmente, `version-update:semver-major`, `version-update:semver-minor` e `version-update:semver-patch` são as únicas opções compatíveis. As atualizações de segurança não afetadas por esta configuração.
 
diff --git a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index 2d9eb73182..e4c74991cf 100644
--- a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -124,8 +124,7 @@ Antes de definir um padrão personalizado, você deverá habilitar {% data varia
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
 {%- if secret-scanning-org-dry-runs %}
 1. Quando você estiver pronto para testar seu novo padrão personalizado, para identificar correspondências em repositórios selecionados sem criar alertas, clique em **Salvar e testar**.
-1. Pesquise e selecione os repositórios onde você deseja executar o teste. Você pode selecionar até 10 repositórios. ![Captura de tela que mostra os repositórios selecionados para o teste](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
-1. Quando estiver pronto para testar seu novo padrão personalizado, clique em **Testar**.
+{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
 {% data reusables.advanced-security.secret-scanning-dry-run-results %}
 {%- endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
@@ -142,8 +141,15 @@ Antes de definir um padrão personalizado, você deverá garantir que você habi
 
 {% note %}
 
+{% if secret-scanning-enterprise-dry-runs %}
+**Notas:**
+- At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run.
+- Enterprise owners can only make use of dry runs on repositories that they have access to, and enterprise owners do not necessarily have access to all the organizations or repositories within the enterprise.
+{% else %}
 **Observação:** Como não há nenhuma funcionalidade de teste, recomendamos que você teste seus padrões personalizados em um repositório antes de defini-los para toda sua empresa. Dessa forma, você pode evitar criar alertas falsos-positivos de {% data variables.product.prodname_secret_scanning %}.
 
+{% endif %}
+
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
@@ -152,6 +158,11 @@ Antes de definir um padrão personalizado, você deverá garantir que você habi
 {% data reusables.enterprise-accounts.advanced-security-security-features %}
 1. Em "Padrões de personalização de digitalização de segredos", clique em {% ifversion ghes = 3.2 %}**Novo padrão personalizado**{% else %}**Novo padrão**{% endif %}.
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{%- if secret-scanning-enterprise-dry-runs %}
+1. Quando estiver pronto para testar seu novo padrão personalizado, para identificar correspondências no repositório sem criar alertas, clique em **Salvar testar**.
+{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
+{% data reusables.advanced-security.secret-scanning-dry-run-results %}
+{%- endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 Depois que o seu padrão for criado, {% data variables.product.prodname_secret_scanning %} irá digitalizar qualquer segredo em repositórios nas organizações da sua empresa com {% data variables.product.prodname_GH_advanced_security %} habilitado, incluindo todo seu histórico do Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)".
diff --git a/translations/pt-BR/content/codespaces/getting-started/quickstart.md b/translations/pt-BR/content/codespaces/getting-started/quickstart.md
index 5a7022695b..862cc4ff01 100644
--- a/translations/pt-BR/content/codespaces/getting-started/quickstart.md
+++ b/translations/pt-BR/content/codespaces/getting-started/quickstart.md
@@ -15,7 +15,7 @@ redirect_from:
 
 ## Introdução
 
-Neste guia, você irá criar um codespace a partir de um [repositório modelo](https://github.com/2percentsilk/haikus-for-codespaces) e explorar algumas das funcionalidades essenciais disponíveis para você dentro do codespace.
+Neste guia, você irá criar um codespace a partir de um [repositório modelo](https://github.com/github/haikus-for-codespaces) e explorar algumas das funcionalidades essenciais disponíveis para você dentro do codespace.
 
 Neste início rápido, você aprenderá a criar um codespace, conectar-se a uma porta encaminhada para ver seu aplicativo em execução, usar o controle de versões em um codespace e personalizar a sua configuração com extensões.
 
@@ -23,7 +23,7 @@ Para obter mais informações sobre exatamente como {% data variables.product.pr
 
 ## Criando seu codespace
 
-1. Acesse o r[repositório do modelo](https://github.com/2percentsilk/haikus-for-codespaces) e selecione **Usar este modelo**.
+1. Acesse o r[repositório do modelo](https://github.com/github/haikus-for-codespaces) e selecione **Usar este modelo**.
 
 2. Nomeie seu repositório, selecione sua configuração de privacidade preferida e clique em **Criar repositório a partir do modelo**.
 
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
index 7d2223aecb..95de7f8801 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
@@ -114,7 +114,7 @@ Para obter mais informações sobre como usar um arquivo Docker em uma configura
 
 ## Usando a configuração padrão do contêiner de desenvolvimento
 
-Se você não definir uma configuração no repositório, o {% data variables.product.prodname_dotcom %} criará um codespace que usa uma imagem padrão do Linux. This Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the URL that the command outputs.
+Se você não definir uma configuração no repositório, o {% data variables.product.prodname_dotcom %} criará um codespace que usa uma imagem padrão do Linux. This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the URL that the command outputs.
 
 Alternatively, for more information about everything that's included in the default Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository.
 
diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
index 90f7ac7310..cc71020e46 100644
--- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
@@ -154,7 +154,7 @@ Ao bifurcar um projeto para propor mudanças no repositório original, é possí
 
 6. Digite `git remote add upstream`, cole o URL que você copiou na etapa 3 e pressione **Enter**. Ficará assim:
   ```shell
-  $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
+  $ git remote add upstream https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/Spoon-Knife.git
   ```
 
 7. Para verificar o novo repositório upstream que você especificou para sua bifurcação, digite novamente `git remote -v`. Você deverá visualizar a URL da sua bifurcação como `origin` (origem) e a URL do repositório original como `upstream`.
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
index b29359bd6c..25da083395 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -22,6 +22,8 @@ topics:
 
 Os problemas permitem que você acompanhe seu trabalho em {% data variables.product.company_short %}, onde o desenvolvimento acontece. Ao mencionar um problema em outro problema ou pull request, a linha do tempo do problema reflete a referência cruzada para que você possa acompanhar o trabalho relacionado. Para indicar que o trabalho está em andamento, você pode vincular um problema a um pull request. Quando o pull request faz merge, o problema vinculado é fechado automaticamente.
 
+For more information on keywords, see "[Linking a pull request to an issue](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)."
+
 ## Crie problemas rapidamente
 
 Os problemas podem ser criados de várias maneiras. Portanto, você pode escolher o método mais conveniente para seu fluxo de trabalho. Por exemplo, você pode criar um problema a partir de um repositório,{% ifversion fpt or ghec %} um item em uma lista de tarefas,{% endif %} uma observação em um projeto, um comentário em um problema ou pull request, uma linha de código específica ou uma consulta de URL. Você também pode criar um problema a partir da sua plataforma de escolha: por meio da interface do usuário web {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL e APIs REST ou {% data variables.product.prodname_mobile %}. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)".
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 3087436fe6..2851b5402f 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -35,7 +35,7 @@ Quando você mescla uma pull request vinculada no branch padrão de um repositó
 
 ## Vinculando uma pull request a um problema usando uma palavra-chave
 
-Você pode vincular uma solicitação de pull a um problema usando uma palavra-chave compatível na descrição do pull request ou em uma mensagem de commit (observe que a solicitação do pull deve estar no branch-padrão).
+You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message. The pull request **must be** on the default branch.
 
 * close
 * closes
@@ -47,7 +47,7 @@ Você pode vincular uma solicitação de pull a um problema usando uma palavra-c
 * resolve
 * resolved
 
-Se você usar uma palavra-chave para fazer referência a um comentário de um pull request em outr pull request, os pull requests serão vinculados. Merging the referencing pull request will also close the referenced issue.
+Se você usar uma palavra-chave para fazer referência a um comentário de um pull request em outr pull request, os pull requests serão vinculados. Merging the referencing pull request also closes the referenced pull request.
 
 A sintaxe para fechar palavras-chave depende se o problema está no mesmo repositório que a pull request.
 
@@ -61,7 +61,6 @@ A sintaxe para fechar palavras-chave depende se o problema está no mesmo reposi
 
 Você também pode usar palavras-chave de fechamento em uma mensagem de commit. O problema será encerrado quando você mesclar o commit no branch padrão, mas o pull request que contém o commit não será listado como um pull request vinculado.
 
-
 {% ifversion fpt or ghes or ghae or ghec %}
 ## Vinculando manualmente uma pull request a um problema
 
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
index 88e3b0d69c..fca55fb795 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -22,7 +22,10 @@ shortTitle: Configurar combinação por squash de commit
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 3. Em {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Botão de merge"{% endif %}, opcionalmente, selecione **Permitir commits de merge**. Isso permite que os contribuidores façam merge de uma pull request com um histórico completo de commits. ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
-4. Em {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Botão de merge"{% endif %}, selecione **Permitir merge de combinação por squash**. Isso permite que os contribuidores façam merge de uma pull request combinando por squash todos os commits em um único commit. Se você selecionar outro método além de **Allow squash merging** (Permitir merge de combinação por squash), os colaboradores poderão escolher o tipo de commit do merge ao fazer merge de uma pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Commits de combinação por squash da pull request](/assets/images/help/repository/pr-merge-squash.png)
+4. Em {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Botão de merge"{% endif %}, selecione **Permitir merge de combinação por squash**. Isso permite que os contribuidores façam merge de uma pull request combinando por squash todos os commits em um único commit. The squash message automatically defaults to the title of the pull request if it contains more than one commit. {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}If you want to use the title of the pull request as the default merge message for all squashed commits, regardless of the number of commits in the pull request, select **Default to PR title for squash merge commits**. ![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png){% else %}
+![Pull request squashed commits](/assets/images/enterprise/3.5/repository/pr-merge-squash.png){% endif %}
+
+If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %}
 
 ## Leia mais
 
diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md
index 4dbfea1008..2ece9c9dc9 100644
--- a/translations/pt-BR/content/rest/overview/libraries.md
+++ b/translations/pt-BR/content/rest/overview/libraries.md
@@ -42,7 +42,7 @@ Warning: As of late October 2021, the offical Octokit libraries are not currentl
 
 | Nome da Biblioteca | Repositório                                                             |
 | ------------------ | ----------------------------------------------------------------------- |
-| **github.dart**    | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) |
+| **github.dart**    | [SpinlockLabs/github.dart](https://github.com/SpinlockLabs/github.dart) |
 
 ### Emacs Lisp
 
diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index e98acad006..c1d14b1627 100644
--- a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -300,10 +300,10 @@ Esse qualificador usa a data como parâmetro. {% data reusables.time_date.date_f
 
 Você pode filtrar as pull requests com ou sem merge usando o qualificador `is`.
 
-| Qualifier     | Exemplo                                                                                                                                                               |
-| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `is:merged`   | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) identifica as pull requests com merge que têm a palavra "bug". |
-| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) identifica problemas e pull requests fechados com a palavra "error".    |
+| Qualifier     | Exemplo                                                                                                                                                                                             |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:merged`   | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) identifica as pull requests com merge que têm a palavra "bug".                               |
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches pull requests with the word "error" that are either open or were closed without being merged. |
 
 ## Pesquisar com base no fato de o repositório estar arquivado
 
diff --git a/translations/pt-BR/content/support/learning-about-github-support/about-github-support.md b/translations/pt-BR/content/support/learning-about-github-support/about-github-support.md
index ca56371f79..c9590fdb76 100644
--- a/translations/pt-BR/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/pt-BR/content/support/learning-about-github-support/about-github-support.md
@@ -73,7 +73,7 @@ To report account, security, and abuse issues, or to receive assisted support fo
 {% ifversion fpt %}
 If you have any paid product or are a member of an organization with a paid product, you can contact {% data variables.contact.github_support %} in English.
 {% else %} 
-With {% data variables.product.product_name %}, you have access to support in English{% ifversion ghes %} and Japanese{% endif %}.
+With {% data variables.product.product_name %}, you have access to support in English and Japanese.
 {% endif %}
 
 {% ifversion ghes or ghec %}
@@ -135,18 +135,24 @@ To learn more about training options, including customized trainings, see [{% da
 
 {% endif %}
 
-{% ifversion ghes %}
+{% ifversion ghes or ghec %}
 ## Hours of operation
 
 ### Support in English
 
 For standard non-urgent issues, we offer support in English 24 hours per day, 5 days per week, excluding weekends and national U.S. holidays. The standard response time is 24 hours.
 
+{% ifversion ghes %}
 For urgent issues, we are available 24 hours per day, 7 days per week, even during national U.S. holidays.
+{% endif %}
 
 ### Support in Japanese
 
-For non-urgent issues, support in Japanese is available Monday through Friday from 9:00 AM to 5:00 PM JST, excluding national holidays in Japan. For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays.
+For standard non-urgent issues, support in Japanese is available Monday through Friday from 9:00 AM to 5:00 PM JST, excluding national holidays in Japan. 
+
+{% ifversion ghes %}
+For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays.
+{% endif %}
 
 For a complete list of U.S. and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."
 
@@ -164,7 +170,7 @@ For urgent issues, we can help you in English 24 hours per day, 7 days per week,
 
 {% data variables.contact.enterprise_support %} does not provide Japanese-language support on December 28th through January 3rd as well as on the holidays listed in [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html).
 
-{% data reusables.enterprise_enterprise_support.installing-releases %}
+{% ifversion ghes %}{% data reusables.enterprise_enterprise_support.installing-releases %}{% endif %}
 
 {% endif %}
 
diff --git a/translations/pt-BR/data/features/dependabot-grouped-dependencies.yml b/translations/pt-BR/data/features/dependabot-grouped-dependencies.yml
new file mode 100644
index 0000000000..2dd2406822
--- /dev/null
+++ b/translations/pt-BR/data/features/dependabot-grouped-dependencies.yml
@@ -0,0 +1,8 @@
+---
+#Reference: #6913
+#Dependabot support for TypeScript @types/*
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6913'
diff --git a/translations/pt-BR/data/features/secret-scanning-enterprise-dry-runs.yml b/translations/pt-BR/data/features/secret-scanning-enterprise-dry-runs.yml
new file mode 100644
index 0000000000..1ce219308f
--- /dev/null
+++ b/translations/pt-BR/data/features/secret-scanning-enterprise-dry-runs.yml
@@ -0,0 +1,7 @@
+---
+#Issue #6904
+#Documentation for the "enterprise account level dry runs (Public Beta)" for custom patterns under secret scanning
+versions:
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6904'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml
index 8612544a8c..468369aa10 100644
--- a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml
@@ -46,7 +46,7 @@ sections:
       heading: Server Statistics in public beta
       notes:
         - |
-          You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see "[About Server Statistics](/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." **Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content.  For a better understanding of how we store and secure Server Statistics data, see "[GitHub Security](https://github.com/security)."**  For more information about Server Statistics, see "[Analyzing how your team works with Server Statistics](/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics)." This feature is available in public beta.
+          You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." **Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content.  For a better understanding of how we store and secure Server Statistics data, see "[GitHub Security](https://github.com/security)."**  For more information about Server Statistics, see "[Analyzing how your team works with Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics)." This feature is available in public beta.
     - 
       heading: GitHub Actions rate limiting is now configurable
       notes:
@@ -101,7 +101,6 @@ sections:
           - You can pass environment secrets to reusable workflows.
           - The audit log includes information about which reusable workflows are used.
           - Reusable workflows in the same repository as the calling repository can be referenced with just the path and filename (`PATH/FILENAME`). The called workflow will be from the same commit as the caller workflow.
-          - Reusable workflows are subject to your organization's actions access policy. Previously, even if your organization had configured the "Allow select actions" policy, you were still able to use a reusable workflow from any location. Now if you use a reusable workflow that falls outside of that policy, your run will fail. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)."
     - 
       heading: Self-hosted runners for GitHub Actions can now disable automatic updates
       notes:
diff --git a/translations/pt-BR/data/reusables/actions/hardware-requirements-3.5.md b/translations/pt-BR/data/reusables/actions/hardware-requirements-3.5.md
new file mode 100644
index 0000000000..8ef9fd0fca
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/hardware-requirements-3.5.md
@@ -0,0 +1,7 @@
+| vCPUs | Memória | Simultaneidade máxima |
+|:----- |:------- |:--------------------- |
+| 8     | 64 GB   | 740 trabalhos         |
+| 16    | 128 GB  | 1250 trabalhos        |
+| 32    | 160 GB  | 2700 trabalhos        |
+| 64    | 256 GB  | 4500 trabalhos        |
+| 96    | 384 GB  | 7000 trabalhos        |
diff --git a/translations/pt-BR/data/reusables/advanced-security/secret-scanning-dry-run-results.md b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-dry-run-results.md
index 07d550f662..1e35f21f02 100644
--- a/translations/pt-BR/data/reusables/advanced-security/secret-scanning-dry-run-results.md
+++ b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-dry-run-results.md
@@ -1,3 +1,3 @@
-1. Quando o teste terminar, você verá uma amostra de resultados (até 1000) do repositório. Revise os resultados e identifique quaisquer resultados falso-positivos. ![Captura de tela que exibe os resultados do teste](/assets/images/help/repository/secret-scanning-publish-pattern.png)
+1. When the dry run finishes, you'll see a sample of results (up to 1000). Revise os resultados e identifique quaisquer resultados falso-positivos. ![Captura de tela que exibe os resultados do teste](/assets/images/help/repository/secret-scanning-publish-pattern.png)
 1. Edit the new custom pattern to fix any problems with the results, then, to test your changes, click **Save and dry run**.
 {% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
new file mode 100644
index 0000000000..820bdad08b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
@@ -0,0 +1,2 @@
+1. Search for and select up to 10 repositories where you want to perform the dry run. ![Captura de tela que mostra os repositórios selecionados para o teste](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
+1. Quando estiver pronto para testar seu novo padrão personalizado, clique em **Testar**.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md
index c36d662411..f6851efb87 100644
--- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md
+++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md
@@ -48,6 +48,12 @@ If you plan to enable {% data variables.product.prodname_actions %} for the user
 
 {%- endif %}
 
+{%- ifversion ghes = 3.5 %}
+
+{% data reusables.actions.hardware-requirements-3.5 %}
+
+{%- endif %}
+
 For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
 
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md b/translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md
index 93ada78fc5..a5047a9b64 100644
--- a/translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md
+++ b/translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md
@@ -1 +1 @@
-When Git prompts you for your password, enter your personal access token (PAT) instead.{% ifversion not ghae %} Password-based authentication for Git has been removed, and using a PAT is more secure.{% endif %} For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+When Git prompts you for your password, enter your personal access token (PAT). Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." 
diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml
index 31248e354e..16b56fedec 100644
--- a/translations/pt-BR/data/variables/product.yml
+++ b/translations/pt-BR/data/variables/product.yml
@@ -159,7 +159,7 @@ prodname_copilot_short: 'Copilot'
 #Command Palette
 prodname_command_palette: 'Paleta de comando do GitHub'
 #Server Statistics
-prodname_server_statistics: 'Server Statistics'
+prodname_server_statistics: 'Estatísticas do servidor'
 #Links
 product_url: >-
   {% ifversion fpt or ghec %}github.com{% else %}[hostname]{% endif %}

From ee7787cd20ed06c25dbd1030d6b731a5278b55c0 Mon Sep 17 00:00:00 2001
From: docubot <67483024+docubot@users.noreply.github.com>
Date: Thu, 12 May 2022 18:05:23 -0500
Subject: [PATCH 2/3] New translation batch for es (#27658)

* Add crowdin translations

* Run script/i18n/homogenize-frontmatter.js

* Run script/i18n/fix-translation-errors.js

* Run script/i18n/lint-translation-files.js --check rendering

* run script/i18n/reset-files-with-broken-liquid-tags.js --language=es

* run script/i18n/reset-known-broken-translation-files.js

Co-authored-by: Robert Sese 
---
 ...ithub-actions-for-github-enterprise-server.md | 14 ++++++++++++++
 .../creating-a-personal-access-token.md          |  9 ++++++---
 ...ing-github-using-two-factor-authentication.md | 10 ++++++++--
 .../troubleshooting-the-codeql-workflow.md       |  2 ++
 .../dependabot-alerts/about-dependabot-alerts.md |  2 +-
 .../about-dependabot-version-updates.md          |  2 +-
 ...ration-options-for-the-dependabot.yml-file.md |  2 +-
 ...fining-custom-patterns-for-secret-scanning.md | 16 +++++++++++++---
 .../codespaces/getting-started/quickstart.md     |  4 ++--
 .../introduction-to-dev-containers.md            |  2 +-
 .../get-started/quickstart/fork-a-repo.md        |  2 +-
 .../about-issues.md                              |  2 ++
 .../linking-a-pull-request-to-an-issue.md        |  5 ++---
 ...iguring-commit-squashing-for-pull-requests.md |  7 +++++--
 .../es-ES/content/rest/overview/libraries.md     |  2 +-
 .../searching-issues-and-pull-requests.md        |  2 +-
 .../about-github-support.md                      | 14 ++++++++++----
 .../features/dependabot-grouped-dependencies.yml |  8 ++++++++
 .../secret-scanning-enterprise-dry-runs.yml      |  7 +++++++
 .../enterprise-server/3-5/0-rc1.yml              |  4 ++--
 .../actions/hardware-requirements-3.5.md         |  7 +++++++
 .../secret-scanning-dry-run-results.md           |  2 +-
 .../secret-scanning-dry-run-select-repos.md      |  2 ++
 .../hardware-rec-table.md                        |  6 ++++++
 .../password-authentication-deprecation.md       |  2 +-
 25 files changed, 105 insertions(+), 30 deletions(-)
 create mode 100644 translations/es-ES/data/features/dependabot-grouped-dependencies.yml
 create mode 100644 translations/es-ES/data/features/secret-scanning-enterprise-dry-runs.yml
 create mode 100644 translations/es-ES/data/reusables/actions/hardware-requirements-3.5.md
 create mode 100644 translations/es-ES/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md

diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 2c7ee51e44..5849e1e2b7 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -81,6 +81,20 @@ La simultaneidad máxima se midió utilizando repositorios múltiples, una durac
 
 {%- endif %}
 
+{%- ifversion ghes = 3.5 %}
+
+{% data reusables.actions.hardware-requirements-3.5 %}
+
+{% data variables.product.company_short %} measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. Puedes experimentar rendimientos diferentes dependiendo de los niveles de actividad generales de tu instancia.
+
+{% note %}
+
+**Note:** Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}.
+
+{% endnote %}
+
+{%- endif %}
+
 Si planeas habilitar las {% data variables.product.prodname_actions %} para los usuarios de una instancia existente, revisa los niveles de actividad para los usuarios y automatizaciones en la instancia y asegúrate de haber proporcionado memoria y CPU adecuados para tus usuarios. Para obtener más información acerca de cómo monitorear la capacidad y rendimiento de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Monitorear tu aplicativo](/admin/enterprise-management/monitoring-your-appliance)".
 
 Para obtener más información acerca de los requisitos mínimos de {% data variables.product.product_location %}, consulta las consideraciones de hardware para la plataforma de tu instancia.
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index c14ba702a6..569faa19b0 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
 title: Crear un token de acceso personal
-intro: Debes crear un token de acceso personal para utilizar como contraseña con la línea de comandos o con la API.
+intro: You can create a personal access token to use in place of a password with the command line or with the API.
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -22,7 +22,10 @@ shortTitle: Crear un PAT
 
 {% note %}
 
-**Nota:** Si utilizas el {% data variables.product.prodname_cli %} para autenticarte en {% data variables.product.product_name %} en la línea de comandos, puedes omitir el generar un token de acceso personal y autenticarte a través del buscador web en su lugar. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+**Notas:**
+
+- If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+-  [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure, cross-platform alternative to using personal access tokens (PATs) and eliminates the need to manage PAT scope and expiration. For installation instructions, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository.
 
 {% endnote %}
 
@@ -77,5 +80,5 @@ En vez de ingresar tu PAT manualmente para cada operación de HTTPS de Git, pued
 
 ## Leer más
 
-- "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
+- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
 - "[Vencimiento y revocación de token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
index 8b58baf53c..66f70a76be 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -59,9 +59,15 @@ Si instalaste e iniciaste sesión en {% data variables.product.prodname_mobile %
 
 ## Usar autenticación de dos factores con la línea de comando
 
-Después de haber habilitado 2FA, debes usar un token de acceso personal o una clave SSH en lugar de tu contraseña al acceder a {% data variables.product.product_name %} en la línea de comando.
+After you've enabled 2FA, you will no longer use your password to access {% data variables.product.product_name %} on the command line. Instead, use Git Credential Manager, a personal access token, or an SSH key.
 
-### Autenticar en la línea de comando mediante HTTPS
+### Authenticating on the command line using Git Credential Manager
+
+[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure Git credential helper that runs on Windows, macOS, and Linux. For more information about Git credential helpers, see [Avoiding repetition](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) in the Pro Git book.
+
+Setup instructions vary based on your computer's operating system. For more information, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository.
+
+### Autenticación en la línea de comando mediante HTTPS
 
 Después de haber habilitado 2FA, debes crear un token de acceso personal para usar una contraseña al autenticar a {% data variables.product.product_name %} en la línea de comando mediante las URL HTTPS.
 
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 23b3029c1c..10182aec4a 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -98,6 +98,8 @@ Si una compilación automática de código para un lenguaje compilado dentro de
 
 Si tu flujo de trabajo falla con un error de `No source code was seen during the build` o de `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, esto indica que {% data variables.product.prodname_codeql %} no pudo monitorear tu código. Hay muchas razones que podrían explicar esta falla:
 
+1. The repository may not contain source code that is written in languages supported by {% data variables.product.prodname_codeql %}. Check the list of supported languages and, if this is the case, remove the {% data variables.product.prodname_codeql %} workflow. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql)
+
 1. La detección automática del lenguaje identificó un lenguaje compatible, pero no hay código analizable en dicho lenguaje dentro del repositorio. Un ejemplo típico es cuando nuestro servicio de detección de lenguaje encuentra un archivo que se asocia con un lenguaje de programación específico como un archivo `.h`, o `.gyp`, pero no existe el código ejecutable correspondiente a dicho lenguaje en el repositorio. Para resolver el problema, puedes definir manualmente los lenguajes que quieras analizar si actualizas la lista de éstos en la matriz de `language`. Por ejemplo, la siguiente configuración analizará únicamente a Go y a Javascript.
 
   ```yaml
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
index ac43e5ff46..2225d13a1d 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
@@ -85,7 +85,7 @@ Para los repositorios en donde están habilitadas las {% data variables.product.
 
 Puedes ver todas las alertas que afectan un proyecto en particular{% ifversion fpt or ghec %} en la pestaña de Seguridad del repositorio o{% endif %} en la gráfica de dependencias del repositorio. Para obtener más información, consulta la sección "[Visualizar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".
 
-Predeterminadamente, notificamos a las personas con permisos administrativos en los repositorios afectados sobre las {% data variables.product.prodname_dependabot_alerts %} nuevas. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga públicamente las vulnerabilidades identificadas de ningún repositorio. También puedes hacer que las {% data variables.product.prodname_dependabot_alerts %} sean visibles para más personas o equipos que trabajen en los repositorios que te pertenecen o para los cuales tienes permisos administrativos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
+Predeterminadamente, notificamos a las personas con permisos administrativos en los repositorios afectados sobre las {% data variables.product.prodname_dependabot_alerts %} nuevas. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga públicamente las vulnerabilidades identificadas de ningún repositorio. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
 {% endif %}
 
 {% data reusables.notifications.vulnerable-dependency-notification-enable %}
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
index 26d7de3bcf..b505b983bc 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -30,7 +30,7 @@ shortTitle: Actualizaciones de versión del dependabot
 
 El {% data variables.product.prodname_dependabot %} hace el esfuerzo de mantener tus dependencias. Puedes utilizarlo para garantizar que tu repositorio se mantenga automáticamente con los últimos lanzamientos de los paquetes y aplicaciones de los que depende.
 
-Se habilitan las {% data variables.product.prodname_dependabot_version_updates %} al registrar un archivo de configuración en tu repositorio. Este archivo de configuración especifica la ubicación del manifiesto o de otros archivos de definición de paquetes almacenados en tu repositorio. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas (o almacenadas en caché) son aquellas que se registran en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario.
+You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_configuration file into your repository. Este archivo de configuración especifica la ubicación del manifiesto o de otros archivos de definición de paquetes almacenados en tu repositorio. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas (o almacenadas en caché) son aquellas que se registran en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario.
 
 Cuando el {% data variables.product.prodname_dependabot %} identifica una dependencia desactualizada, levanta una solicitud de extracción para actualizar el manifiesto a su última versión de la dependencia. Lara las dependencias delegadas a proveedores, el {% data variables.product.prodname_dependabot %} levanta una solicitud de cambios para reemplazar la dependencia desactualizada directamente con la versión nueva. Verificas que tu prueba pase, revisas el registro de cambios y notas de lanzamiento que se incluyan en el resumen de la solicitud de extracción y, posteriormente, lo fusionas. Para obtener más información, consulta la sección "[Configurar las actualizaciones de versión del {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)".
 
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
index 51bac31dfd..389899643f 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@@ -322,7 +322,7 @@ Para obtener más información acerca de los comandos de `@dependabot ignore`, c
 
 Puedes utilizar la opción `ignore` para personalizar qué dependencias se actualizarán. La opción `ignore` es compatible con las siguientes opciones.
 
-- `dependency-name`—se utiliza para ignorar actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId` (por ejemplo: `org.kohsuke:github-api`).
+- `dependency-name`—se utiliza para ignorar actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId` (por ejemplo: `org.kohsuke:github-api`). {% if dependabot-grouped-dependencies %} To prevent {% data variables.product.prodname_dependabot %} from automatically updating TypeScript type definitions from DefinitelyTyped, use `@types/*`.{% endif %}
 - `versions`—se utiliza para ignorar versiones o rangos específicos de las versiones. Si quieres definir un rango, utiliza el patrón estándar del administrador de paquetes (por ejemplo: `^1.0.0` para npm, o `~> 2.0` para Bundler).
 - `update-types`—Se utiliza para ignorar tipos de actualizaciones tales como las de tipo `major`, `minor`, o `patch` en actualizaciones de versión (por ejemplo: `version-update:semver-patch` ignorará las actualizaciones de parche). Puedes combinar esto con `dependency-name: "*"` para ignorar algún `update-types` en particular en todas las dependencias. Actualmente, `version-update:semver-major`, `version-update:semver-minor`, y `version-update:semver-patch` son las únicas opciones compatibles. Este ajuste no afectará a las actualizaciones de seguridad.
 
diff --git a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index a47d902311..751f502bac 100644
--- a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -124,9 +124,7 @@ Before defining a custom pattern, you must ensure that you enable {% data variab
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
 {%- if secret-scanning-org-dry-runs %}
 1. When you're ready to test your new custom pattern, to identify matches in select repositories without creating alerts, click **Save and dry run**.
-1. Search for and select the repositories where you want to perform the dry run. You can select up to 10 repositories.
-   ![Screenshot showing repositories selected for the dry run](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
-1. When you're ready to test your new custom pattern, click **Dry run**.
+{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
 {% data reusables.advanced-security.secret-scanning-dry-run-results %}
 {%- endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
@@ -143,8 +141,15 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
 
 {% note %}
 
+{% if secret-scanning-enterprise-dry-runs %}
+**Notes:**
+- At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run. 
+- Enterprise owners can only make use of dry runs on repositories that they have access to, and enterprise owners do not necessarily have access to all the organizations or repositories within the enterprise.
+{% else %}
 **Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts.
 
+{% endif %}
+
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
@@ -153,6 +158,11 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
 {% data reusables.enterprise-accounts.advanced-security-security-features %}
 1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}.
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{%- if secret-scanning-enterprise-dry-runs %}
+1. When you're ready to test your new custom pattern, to identify matches in the repository without creating alerts, click **Save and dry run**.
+{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
+{% data reusables.advanced-security.secret-scanning-dry-run-results %}
+{%- endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
diff --git a/translations/es-ES/content/codespaces/getting-started/quickstart.md b/translations/es-ES/content/codespaces/getting-started/quickstart.md
index c1b96e7236..34c97a07b0 100644
--- a/translations/es-ES/content/codespaces/getting-started/quickstart.md
+++ b/translations/es-ES/content/codespaces/getting-started/quickstart.md
@@ -15,7 +15,7 @@ redirect_from:
 
 ## Introducción
 
-En esta guía, crearás un codespace desde un [repositorio de plantilla](https://github.com/2percentsilk/haikus-for-codespaces) y explorarás algunas de las características esenciales disponibles para ti dentro del codespace.
+En esta guía, crearás un codespace desde un [repositorio de plantilla](https://github.com/github/haikus-for-codespaces) y explorarás algunas de las características esenciales disponibles para ti dentro del codespace.
 
 Desde esta guía de inicio rápido, aprenderás cómo crear un codespace, cómo conectarte a un puerto reenviado para ver tu aplicación ejecutándose, cómo utilizar el control de versiones en un codespace y cómo personalizar tu configuración con extensiones.
 
@@ -23,7 +23,7 @@ Para obtener más información sobre cómo funcionan los {% data variables.produ
 
 ## Crea tu codespace
 
-1. Navega al [repositorio de plantilla](https://github.com/2percentsilk/haikus-for-codespaces) y selecciona **Utilizar esta plantilla**.
+1. Navega al [repositorio de plantilla](https://github.com/github/haikus-for-codespaces) y selecciona **Utilizar esta plantilla**.
 
 2. Nombra a tu repositorio, selecciona tu configuración de privacidad preferido y haz clic en **Crear repositorio desde plantilla**.
 
diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
index 71fa4e8590..3e1090accc 100644
--- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
+++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
@@ -114,7 +114,7 @@ Para obtener más información sobre cómo utilizar un Dockerfile en una configu
 
 ## Utilizar la configuración de contenedor dev predeterminada
 
-Si no defines una configuración en tu repositorio, {% data variables.product.prodname_dotcom %} creará un codespace utilizando una imagen de Linux predeterminada. Esta imagen de Linux incluye lenguajes y tiempos de ejecución como Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby y Rust. También incluye otras herramientas y utilidades de desarrollador como Git, el CLI de GitHub, yarn, openssh y vim. Para ver todos los lenguajes, tiempos de ejecución y herramientas que se incluyen, utiliza el comando `devcontainer-info content-url` dentro de tu terminal del codespace y sigue la URL que este produce.
+Si no defines una configuración en tu repositorio, {% data variables.product.prodname_dotcom %} creará un codespace utilizando una imagen de Linux predeterminada. This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. Para ver todos los lenguajes, tiempos de ejecución y herramientas que se incluyen, utiliza el comando `devcontainer-info content-url` dentro de tu terminal del codespace y sigue la URL que este produce.
 
 Como alternativa, para obtener más información sobre todo lo que incluye la imagen predeterminada de Linux, consulta el archivo más reciente del repositorio [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux).
 
diff --git a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md
index dd6c00221e..4f88dbce63 100644
--- a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md
@@ -154,7 +154,7 @@ When you fork a project in order to propose changes to the original repository,
 
 6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. It will look like this:
   ```shell
-  $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
+  $ git remote add upstream https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/Spoon-Knife.git
   ```
 
 7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
index 1cc8afcba3..00691e74a8 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -22,6 +22,8 @@ topics:
 
 Las propuestas te permiten rastrear tu trabajo en {% data variables.product.company_short %}, donde sucede el desarrollo. Cuando mencionas una propuesta en otra propuesta o solicitud de cambios, la línea de tiempo de la propuesta refleja la referencia cruzada para que puedas rastrear el trabajo relacionado. Para indicar que el trabajo está en curso, puedes enlazar una propeusta a una solicitud de cambios. Cuando la solicitud de cambios se fusiona, la propuesta enlazada se cierra automáticamente.
 
+For more information on keywords, see "[Linking a pull request to an issue](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)."
+
 ## Crea propuestas rápidamente
 
 Las propuestas pueden crearse de varias formas, así que puedes elegir el método más conveniente para tu flujo de trabajo. Por ejemplo, puedes crear una propuesta desde un repositorio,{% ifversion fpt or ghec %} un elemento en una lista de tareas,{% endif %} una nota en un proyecto, un comentario en una propuesta o solicitud de cambios, una línea específica de código o una consulta de URL. También puedes crear una propuesta desde tu plataforma de elección: a través de la UI web, {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, las API de GraphQL y de REST o desde {% data variables.product.prodname_mobile %}. Para obtener más información, consulta la sección "[Crear una propuesta](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)".
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index e9fabac7b7..2f4e2d02b8 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -34,7 +34,7 @@ When you merge a linked pull request into the default branch of a repository, it
 
 ## Linking a pull request to an issue using a keyword
 
-You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message (please note that the pull request must be on the default branch).
+You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message. The pull request **must be** on the default branch.
 
 * close
 * closes
@@ -46,7 +46,7 @@ You can link a pull request to an issue by using a supported keyword in the pull
 * resolves
 * resolved
 
-If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request will also close the referenced issue.
+If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request also closes the referenced pull request.
 
 The syntax for closing keywords depends on whether the issue is in the same repository as the pull request.
 
@@ -60,7 +60,6 @@ Multiple issues | Use full syntax for each issue | `Resolves #10, resolves #123,
 
 You can also use closing keywords in a commit message. The issue will be closed when you merge the commit into the default branch, but the pull request that contains the commit will not be listed as a linked pull request.
 
-
 {% ifversion fpt or ghes or ghae or ghec %}
 ## Manually linking a pull request to an issue
 
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
index eac9f7a42c..063e0ea22f 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -22,8 +22,11 @@ shortTitle: Configure commit squashing
 {% data reusables.repositories.sidebar-settings %}
 3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, optionally select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.
 ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
-4. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. If you select another merge method besides **Allow squash merging**, collaborators will be able to choose the type of merge commit when merging a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %}
-![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png)
+4. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. The squash message automatically defaults to the title of the pull request if it contains more than one commit. {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}If you want to use the title of the pull request as the default merge message for all squashed commits, regardless of the number of commits in the pull request, select **Default to PR title for squash merge commits**. 
+![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png){% else %}
+![Pull request squashed commits](/assets/images/enterprise/3.5/repository/pr-merge-squash.png){% endif %}
+
+If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %}
 
 ## Further reading
 
diff --git a/translations/es-ES/content/rest/overview/libraries.md b/translations/es-ES/content/rest/overview/libraries.md
index fc6538e121..8665fd2dbd 100644
--- a/translations/es-ES/content/rest/overview/libraries.md
+++ b/translations/es-ES/content/rest/overview/libraries.md
@@ -42,7 +42,7 @@ Advertencia: Desde la segunda mitad de octubre del 2021, ya no se están manteni
 
 | Nombre de la librería | Repositorio                                                             |
 | --------------------- | ----------------------------------------------------------------------- |
-| **github.dart**       | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) |
+| **github.dart**       | [SpinlockLabs/github.dart](https://github.com/SpinlockLabs/github.dart) |
 
 ### Emacs Lisp
 
diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index 1d716bc101..dd17c6fc17 100644
--- a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -309,7 +309,7 @@ You can filter pull requests based on whether they're merged or unmerged using t
 | Qualifier        | Example
 | ------------- | -------------
 | `is:merged` | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bug."
-| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches closed issues and pull requests with the word "error."
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches pull requests with the word "error" that are either open or were closed without being merged.
 
 ## Search based on whether a repository is archived
 
diff --git a/translations/es-ES/content/support/learning-about-github-support/about-github-support.md b/translations/es-ES/content/support/learning-about-github-support/about-github-support.md
index ca56371f79..c9590fdb76 100644
--- a/translations/es-ES/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/es-ES/content/support/learning-about-github-support/about-github-support.md
@@ -73,7 +73,7 @@ To report account, security, and abuse issues, or to receive assisted support fo
 {% ifversion fpt %}
 If you have any paid product or are a member of an organization with a paid product, you can contact {% data variables.contact.github_support %} in English.
 {% else %} 
-With {% data variables.product.product_name %}, you have access to support in English{% ifversion ghes %} and Japanese{% endif %}.
+With {% data variables.product.product_name %}, you have access to support in English and Japanese.
 {% endif %}
 
 {% ifversion ghes or ghec %}
@@ -135,18 +135,24 @@ To learn more about training options, including customized trainings, see [{% da
 
 {% endif %}
 
-{% ifversion ghes %}
+{% ifversion ghes or ghec %}
 ## Hours of operation
 
 ### Support in English
 
 For standard non-urgent issues, we offer support in English 24 hours per day, 5 days per week, excluding weekends and national U.S. holidays. The standard response time is 24 hours.
 
+{% ifversion ghes %}
 For urgent issues, we are available 24 hours per day, 7 days per week, even during national U.S. holidays.
+{% endif %}
 
 ### Support in Japanese
 
-For non-urgent issues, support in Japanese is available Monday through Friday from 9:00 AM to 5:00 PM JST, excluding national holidays in Japan. For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays.
+For standard non-urgent issues, support in Japanese is available Monday through Friday from 9:00 AM to 5:00 PM JST, excluding national holidays in Japan. 
+
+{% ifversion ghes %}
+For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays.
+{% endif %}
 
 For a complete list of U.S. and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."
 
@@ -164,7 +170,7 @@ For urgent issues, we can help you in English 24 hours per day, 7 days per week,
 
 {% data variables.contact.enterprise_support %} does not provide Japanese-language support on December 28th through January 3rd as well as on the holidays listed in [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html).
 
-{% data reusables.enterprise_enterprise_support.installing-releases %}
+{% ifversion ghes %}{% data reusables.enterprise_enterprise_support.installing-releases %}{% endif %}
 
 {% endif %}
 
diff --git a/translations/es-ES/data/features/dependabot-grouped-dependencies.yml b/translations/es-ES/data/features/dependabot-grouped-dependencies.yml
new file mode 100644
index 0000000000..2dd2406822
--- /dev/null
+++ b/translations/es-ES/data/features/dependabot-grouped-dependencies.yml
@@ -0,0 +1,8 @@
+---
+#Reference: #6913
+#Dependabot support for TypeScript @types/*
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6913'
diff --git a/translations/es-ES/data/features/secret-scanning-enterprise-dry-runs.yml b/translations/es-ES/data/features/secret-scanning-enterprise-dry-runs.yml
new file mode 100644
index 0000000000..1ce219308f
--- /dev/null
+++ b/translations/es-ES/data/features/secret-scanning-enterprise-dry-runs.yml
@@ -0,0 +1,7 @@
+---
+#Issue #6904
+#Documentation for the "enterprise account level dry runs (Public Beta)" for custom patterns under secret scanning
+versions:
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6904'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml
index ab0183da3e..2b25759a98 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml
@@ -18,7 +18,7 @@ sections:
         - "Dependabot version and security updates are now generally available in GitHub Enterprise Server 3.5. All the popular ecosystems and features that work on GitHub.com repositories now can be set up on your GitHub Enterprise Server instance. Dependabot on GitHub Enterprise Server requires GitHub Actions and a pool of self-hosted Dependabot runners, GitHub Connect enabled, and Dependabot enabled by an admin.\n\nFollowing on from the public beta release, we will be supporting the use of GitHub Actions runners hosted on a Kubernetes setup.\n\nFor more information, see \"[Setting up Dependabot updates](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates).\"\n"
     - heading: 'Server Statistics in public beta'
       notes:
-        - "You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see \"[About Server Statistics](/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected).\" **Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content.  For a better understanding of how we store and secure Server Statistics data, see \"[GitHub Security](https://github.com/security).\"**  For more information about Server Statistics, see \"[Analyzing how your team works with Server Statistics](/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics).\" This feature is available in public beta.\n"
+        - "You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see \"[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected).\" **Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content.  For a better understanding of how we store and secure Server Statistics data, see \"[GitHub Security](https://github.com/security).\"**  For more information about Server Statistics, see \"[Analyzing how your team works with Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics).\" This feature is available in public beta.\n"
     - heading: 'GitHub Actions rate limiting is now configurable'
       notes:
         - "Site administrators can now enable and configure a rate limit for GitHub Actions. By default, the rate limit is disabled. When workflow jobs cannot immediately be assigned to an available runner, they will wait in a queue until a runner is available. However, if GitHub Actions experiences a sustained high load, the queue can back up faster than it can drain and the performance of the GitHub Enterprise Server instance may degrade. To avoid this, an administrator can configure a rate limit. When the rate limit is exceeded, additional workflow runs will fail immediately rather than being put in the queue. Once the rate has stabilized below the threshold, new runs can be queued again. For more information, see \"[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions).\"\n"
@@ -39,7 +39,7 @@ sections:
         - "For customers that sync license usage between GitHub Enterprise Server and GitHub Enterprise Cloud automatically using GitHub Connect, you now have the ability to sync your license usage independently of the automatic weekly sync. This feature also reports the status of sync job. For more information, see \"[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#manually-syncing-license-usage).\"\n"
     - heading: 'Reusable workflows for GitHub Actions are generally available'
       notes:
-        - "Reusable workflows are now generally available. Reusable workflows help you reduce duplication by enabling you to reuse an entire workflow as if it were an action. With the general availability release, a number of improvements are now available for GitHub Enterprise Server. For more information, see \"[Reusing workflows](/actions/using-workflows/reusing-workflows).\"\n\n- You can utilize outputs to pass data from reusable workflows to other jobs in the caller workflow.\n- You can pass environment secrets to reusable workflows.\n- The audit log includes information about which reusable workflows are used.\n- Reusable workflows in the same repository as the calling repository can be referenced with just the path and filename (`PATH/FILENAME`). The called workflow will be from the same commit as the caller workflow.\n- Reusable workflows are subject to your organization's actions access policy. Previously, even if your organization had configured the \"Allow select actions\" policy, you were still able to use a reusable workflow from any location. Now if you use a reusable workflow that falls outside of that policy, your run will fail. For more information, see \"[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise).\"\n"
+        - "Reusable workflows are now generally available. Reusable workflows help you reduce duplication by enabling you to reuse an entire workflow as if it were an action. With the general availability release, a number of improvements are now available for GitHub Enterprise Server. For more information, see \"[Reusing workflows](/actions/using-workflows/reusing-workflows).\"\n\n- You can utilize outputs to pass data from reusable workflows to other jobs in the caller workflow.\n- You can pass environment secrets to reusable workflows.\n- The audit log includes information about which reusable workflows are used.\n- Reusable workflows in the same repository as the calling repository can be referenced with just the path and filename (`PATH/FILENAME`). The called workflow will be from the same commit as the caller workflow.\n"
     - heading: 'Self-hosted runners for GitHub Actions can now disable automatic updates'
       notes:
         - "You now have more control over when your self-hosted runners perform software updates. If you specify the `--disableupdate` flag to the runner then it will not try to perform an automatic software update if a newer version of the runner is available. This allows you to update the self-hosted runner on your own schedule, and is especially convenient if your self-hosted runner is in a container.\n\n For compatibility with the GitHub Actions service, you will need to manually update your runner within 30 days of a new runner version being available.  For instructions on how to install the latest runner version, please see the installation instructions for [the latest release in the runner repo](https://github.com/actions/runner/releases).\n"
diff --git a/translations/es-ES/data/reusables/actions/hardware-requirements-3.5.md b/translations/es-ES/data/reusables/actions/hardware-requirements-3.5.md
new file mode 100644
index 0000000000..0748c0dd77
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/hardware-requirements-3.5.md
@@ -0,0 +1,7 @@
+| vCPU | Memoria | Simultaneidad máxima    |
+|:---- |:------- |:----------------------- |
+| 8    | 64 GB   | 740 puestos de trabajo  |
+| 16   | 128 GB  | 1250 puestos de trabajo |
+| 32   | 160 GB  | 2700 puestos de trabajo |
+| 64   | 256 GB  | 4500 puestos de trabajo |
+| 96   | 384 GB  | 7000 puestos de trabajo |
diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-dry-run-results.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-dry-run-results.md
index 800d3e31bf..3b3fc81b90 100644
--- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-dry-run-results.md
+++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-dry-run-results.md
@@ -1,3 +1,3 @@
-1. Cuando termine la simulación, verás un ejemplo de los resultados (hasta 1000) del repositorio. Revisa los resultados e identifica cualquier falso positivo. ![Captura de pantalla mostrando los resultados de una simulación](/assets/images/help/repository/secret-scanning-publish-pattern.png)
+1. When the dry run finishes, you'll see a sample of results (up to 1000). Revisa los resultados e identifica cualquier falso positivo. ![Captura de pantalla mostrando los resultados de una simulación](/assets/images/help/repository/secret-scanning-publish-pattern.png)
 1. Edit the new custom pattern to fix any problems with the results, then, to test your changes, click **Save and dry run**.
 {% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
new file mode 100644
index 0000000000..6d0b478ab1
--- /dev/null
+++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
@@ -0,0 +1,2 @@
+1. Search for and select up to 10 repositories where you want to perform the dry run. ![Screenshot showing repositories selected for the dry run](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
+1. Cuando estés listo para probar tu nuevo patrón personalizado, haz clic en **Simulacro**.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md
index 6c9f70f04b..cd537bdc66 100644
--- a/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md
+++ b/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md
@@ -48,6 +48,12 @@ Si planeas habilitar las {% data variables.product.prodname_actions %} para los
 
 {%- endif %}
 
+{%- ifversion ghes = 3.5 %}
+
+{% data reusables.actions.hardware-requirements-3.5 %}
+
+{%- endif %}
+
 Para obtener más información sobre estos requisitos, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".
 
 {% endif %}
diff --git a/translations/es-ES/data/reusables/user-settings/password-authentication-deprecation.md b/translations/es-ES/data/reusables/user-settings/password-authentication-deprecation.md
index 5d4caff597..a5047a9b64 100644
--- a/translations/es-ES/data/reusables/user-settings/password-authentication-deprecation.md
+++ b/translations/es-ES/data/reusables/user-settings/password-authentication-deprecation.md
@@ -1 +1 @@
-Cuando Git pide tu contraseña, ingresa tu token de acceso personal (PAT) en su lugar.{% ifversion not ghae %} Se ha eliminado la autenticación con contraseña para Git y es más seguro utilizar un PAT.{% endif %} Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
+When Git prompts you for your password, enter your personal access token (PAT). Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." 

From 7f8a4c77635b8110963d1d4fb7a94b153e2cb0ed Mon Sep 17 00:00:00 2001
From: docubot <67483024+docubot@users.noreply.github.com>
Date: Thu, 12 May 2022 18:09:39 -0500
Subject: [PATCH 3/3] New translation batch for cn (#27661)

* Add crowdin translations

* Run script/i18n/homogenize-frontmatter.js

* Run script/i18n/lint-translation-files.js --check rendering

* run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn

* run script/i18n/reset-known-broken-translation-files.js

* Check in cn CSV report

Co-authored-by: Robert Sese 
---
 translations/log/cn-resets.csv                |  5 ++-
 ...ub-actions-for-github-enterprise-server.md | 14 +++++++
 ...n-organization-owned-by-your-enterprise.md |  2 +-
 .../creating-a-personal-access-token.md       |  8 ++--
 .../token-expiration-and-revocation.md        |  2 +-
 .../about-two-factor-authentication.md        |  2 +-
 ...-github-using-two-factor-authentication.md |  8 +++-
 ...n-azure-subscription-to-your-enterprise.md | 12 +++---
 .../troubleshooting-the-codeql-workflow.md    |  2 +
 .../about-dependabot-alerts.md                |  2 +-
 .../about-dependabot-version-updates.md       |  2 +-
 ...ion-options-for-the-dependabot.yml-file.md |  2 +-
 ...ing-custom-patterns-for-secret-scanning.md | 15 ++++++-
 .../codespaces/getting-started/quickstart.md  |  4 +-
 .../managing-prebuilds.md                     | 16 ++++----
 .../introduction-to-dev-containers.md         |  8 ++--
 .../troubleshooting-prebuilds.md              |  4 +-
 .../managing-disruptive-comments.md           |  8 ++--
 .../following-organizations.md                | 40 +++++++++----------
 .../get-started/quickstart/fork-a-repo.md     |  2 +-
 .../basic-writing-and-formatting-syntax.md    |  2 +-
 .../about-issues.md                           |  2 +
 .../linking-a-pull-request-to-an-issue.md     |  5 +--
 .../creating-a-project.md                     |  2 +-
 ...visibility-changes-in-your-organization.md |  6 +--
 ...he-visibility-of-your-github-pages-site.md |  2 +-
 ...ring-commit-squashing-for-pull-requests.md |  5 ++-
 .../about-protected-branches.md               |  6 +--
 .../managing-a-branch-protection-rule.md      |  4 +-
 .../zh-CN/content/rest/overview/libraries.md  |  2 +-
 .../searching-issues-and-pull-requests.md     |  8 ++--
 .../about-github-support.md                   | 14 +++++--
 .../dependabot-grouped-dependencies.yml       |  8 ++++
 .../secret-scanning-enterprise-dry-runs.yml   |  7 ++++
 .../enterprise-server/3-5/0-rc1.yml           |  3 +-
 .../actions/hardware-requirements-3.5.md      |  7 ++++
 .../secret-scanning-dry-run-results.md        |  2 +-
 .../secret-scanning-dry-run-select-repos.md   |  2 +
 .../hardware-rec-table.md                     |  6 +++
 .../password-authentication-deprecation.md    |  2 +-
 40 files changed, 164 insertions(+), 89 deletions(-)
 create mode 100644 translations/zh-CN/data/features/dependabot-grouped-dependencies.yml
 create mode 100644 translations/zh-CN/data/features/secret-scanning-enterprise-dry-runs.yml
 create mode 100644 translations/zh-CN/data/reusables/actions/hardware-requirements-3.5.md
 create mode 100644 translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md

diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv
index 757146fd9e..66301482ae 100644
--- a/translations/log/cn-resets.csv
+++ b/translations/log/cn-resets.csv
@@ -205,6 +205,7 @@ translations/zh-CN/content/education/manage-coursework-with-github-classroom/int
 translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
 translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
 translations/zh-CN/content/get-started/customizing-your-github-workflow/index.md,broken liquid tags
+translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md,broken liquid tags
 translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md,broken liquid tags
 translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags
 translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
@@ -360,9 +361,9 @@ translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_reposi
 translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
 translations/zh-CN/data/reusables/repositories/github-reviews-security-advisories.md,broken liquid tags
 translations/zh-CN/data/reusables/repositories/select-marketplace-apps.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/saml-session-oauth.md,broken liquid tags
+translations/zh-CN/data/reusables/saml/saml-session-oauth.md,rendering error
 translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,Listed in localization-support#489
-translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
+translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error
 translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags
 translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
 translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md,broken liquid tags
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 73c5b2b8bc..6d4d77f85e 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -80,6 +80,20 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
 
 {%- endif %}
 
+{%- ifversion ghes = 3.5 %}
+
+{% data reusables.actions.hardware-requirements-3.5 %}
+
+{% data variables.product.company_short %} measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+
+{% note %}
+
+**Note:** Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}.
+
+{% endnote %}
+
+{%- endif %}
+
 If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)."
 
 For more information about minimum hardware requirements for {% data variables.product.product_location %}, see the hardware considerations for your instance's platform.
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
index 3ce9d22ae1..27e7b636c0 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
@@ -30,7 +30,7 @@ shortTitle: 管理您的组织角色
 {% endwarning %}
 {% endif %}
 
-For information about managing other people's roles in an organization, see "[Managing membership in your organization](/organizations/managing-membership-in-your-organization)" and "[Managing people's access to your organization with roles](/organizations/managing-peoples-access-to-your-organization-with-roles)."
+有关管理组织中其他人的角色的信息，请参阅“[管理组织中的成员身份](/organizations/managing-membership-in-your-organization)”和“[使用角色管理人员对组织的访问权限](/organizations/managing-peoples-access-to-your-organization-with-roles)”。
 
 ## 使用企业设置管理您的角色
 
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index c0f1c336dd..cf241ab5cd 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
 title: Creating a personal access token
-intro: You should create a personal access token to use in place of a password with the command line or with the API.
+intro: You can create a personal access token to use in place of a password with the command line or with the API.
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -19,10 +19,12 @@ topics:
   - Access management
 shortTitle: Create a PAT
 ---
-
 {% note %}
 
-**Note:** If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+**Notes:**
+
+- If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+-  [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure, cross-platform alternative to using personal access tokens (PATs) and eliminates the need to manage PAT scope and expiration. For installation instructions, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository.
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
index c194c88d14..0d6d387f01 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
@@ -54,7 +54,7 @@ redirect_from:
 
 {% data variables.product.prodname_oauth_app %} 的所有者可以撤销帐户对其应用程序的授权，这也会吊销与授权关联的任何令牌。 有关撤销 OAuth 应用程序的授权的详细信息，请参阅“[删除应用程序授权](/rest/reference/apps#delete-an-app-authorization)”。
 
-{% data variables.product.prodname_oauth_app %} owners can also revoke individual tokens associated with an authorization. For more information about revoking individual tokens for your OAuth app, see "[Delete an app token](/rest/apps/oauth-applications#delete-an-app-token)".
+{% data variables.product.prodname_oauth_app %} 所有者还可以吊销与授权关联的单个令牌。 有关吊销 OAuth 应用的单个令牌的详细信息，请参阅“[删除应用令牌](/rest/apps/oauth-applications#delete-an-app-token)”。
 
 ## 令牌由于具有相同作用域的 {% data variables.product.prodname_oauth_app %} 的令牌过多而被吊销
 
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
index fd0b044ffc..e5954069a7 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
@@ -19,7 +19,7 @@ shortTitle: 关于 2FA
 {% data reusables.two_fa.after-2fa-add-security-key %}
 
 {% ifversion fpt or ghec %}
-除了安全密钥之外，您还可以在配置 TOTP 移动应用程序或短信后使用 {% data variables.product.prodname_mobile %} 进行双重身份验证。 {% data variables.product.prodname_mobile %} uses public-key cryptography to secure your account, allowing you to use any mobile device that you've used to sign in to {% data variables.product.prodname_mobile %} as your second factor.
+除了安全密钥之外，您还可以在配置 TOTP 移动应用程序或短信后使用 {% data variables.product.prodname_mobile %} 进行双重身份验证。 {% data variables.product.prodname_mobile %} 使用公钥加密来保护您的帐户，允许您使用用于登录 {% data variables.product.prodname_mobile %} 的任何移动设备作为第二重身份验证。
 {% endif %}
 
 您还可以配置其他恢复方法，以防无法访问双重身份验证凭据。 有关设置 2FA 的更多信息，请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”和“[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)”。
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
index 9a2cc92078..b43d13298a 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -59,7 +59,13 @@ If you have installed and signed in to {% data variables.product.prodname_mobile
 
 ## Using two-factor authentication with the command line
 
-After you've enabled 2FA, you must use a personal access token or SSH key instead of your password when accessing {% data variables.product.product_name %} on the command line.
+After you've enabled 2FA, you will no longer use your password to access {% data variables.product.product_name %} on the command line. Instead, use Git Credential Manager, a personal access token, or an SSH key.
+
+### Authenticating on the command line using Git Credential Manager
+
+[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure Git credential helper that runs on Windows, macOS, and Linux. For more information about Git credential helpers, see [Avoiding repetition](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) in the Pro Git book.
+
+Setup instructions vary based on your computer's operating system. For more information, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository.
 
 ### Authenticating on the command line using HTTPS
 
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
index 70d1413411..f21773f504 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
 title: 将 Azure 订阅连接到您的企业
-intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %} usage.'
+intro: '您可以使用 Microsoft 企业协议启用并支付 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_codespaces %} 的使用。'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
@@ -16,15 +16,15 @@ shortTitle: 连接 Azure 订阅
 
 {% note %}
 
-**Note:** If your enterprise account is on a Microsoft Enterprise Agreement, connecting an Azure subscription is the only way to use {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} beyond the included amounts, or to use {% data variables.product.prodname_codespaces %} at all.
+**注意：** 如果您的企业帐户使用 Microsoft 企业协议，则连接 Azure 订阅是使用超出 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 所包含金额或使用 {% data variables.product.prodname_codespaces %} 的唯一方法。
 
 {% endnote %}
 
-After you connect an Azure subscription, you can also manage your spending limits.
+连接 Azure 订阅后，您还可以管理您的支出限制。
 
-- "[Managing your spending limit for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)"
-- "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)"
-- "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
+- “[管理 {% data variables.product.prodname_registry %} 的支出限额](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)”
+- “[管理 {% data variables.product.prodname_actions %} 的支出限额](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)”
+- “[管理 {% data variables.product.prodname_codespaces %} 的支出限额](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)”
 
 ## 将 Azure 订阅连接到您的企业帐户
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 19757d0512..f4eca2bb3b 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -98,6 +98,8 @@ If an automatic build of code for a compiled language within your project fails,
 
 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 monitor your code. Several reasons can explain such a failure:
 
+1. The repository may not contain source code that is written in languages supported by {% data variables.product.prodname_codeql %}. Check the list of supported languages and, if this is the case, remove the {% data variables.product.prodname_codeql %} workflow. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql)
+
 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 list of languages in the `language` matrix. For example, the following configuration will analyze only Go, and JavaScript.
 
   ```yaml
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
index d129ffa2e8..233364f4bf 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
@@ -84,7 +84,7 @@ For repositories where {% data variables.product.prodname_dependabot_security_up
 
 You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
 
-By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
+By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
 {% endif %}
 
 {% data reusables.notifications.vulnerable-dependency-notification-enable %}
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
index 8073272f73..f79b7a54da 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -30,7 +30,7 @@ shortTitle: Dependabot 版本更新
 
 {% data variables.product.prodname_dependabot %} 负责维护您的依赖项。 您可以使用它来确保仓库自动跟上它所依赖的包和应用程序的最新版本。
 
-通过将配置文件检入仓库，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。
+You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_configuration file into your repository. 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。
 
 当 {% data variables.product.prodname_dependabot %} 发现过时的依赖项时，它会发起拉取请求以将清单更新到依赖项的最新版本。 对于供应和依赖项，{% data variables.product.prodname_dependabot %} 提出拉取请求以直接将过时的依赖项替换为新版本。 检查测试是否通过，查看拉取请求摘要中包含的更改日志和发行说明，然后合并它。 更多信息请参阅“[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)”。
 
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
index 9db3d4fa91..24470d277e 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@@ -322,7 +322,7 @@ updates:
 
 可以使用 `ignore` 选项自定义更新哪些依赖项。 `ignore` 选项支持以下选项。
 
-- `dependency-name`—用于忽略名称匹配的依赖项，可以选择使用 `*` 来匹配零个或更多字符。 对于 Java 依赖项，`dependency-name` 属性的格式为：`groupId:artifactId`（例如：`org.kohsuke:github-api`）。
+- `dependency-name`—用于忽略名称匹配的依赖项，可以选择使用 `*` 来匹配零个或更多字符。 对于 Java 依赖项，`dependency-name` 属性的格式为：`groupId:artifactId`（例如：`org.kohsuke:github-api`）。 {% if dependabot-grouped-dependencies %} To prevent {% data variables.product.prodname_dependabot %} from automatically updating TypeScript type definitions from DefinitelyTyped, use `@types/*`.{% endif %}
 - `versions`—用于忽略特定版本或版本范围。 如果要定义范围，请使用包管理器的标准模式（例如：对 npm 使用 `^1.0.0`，对 Bundler 使用 `~> 2.0`）。
 - `update-types`—用于忽略更新类型，如关于版本更新的 semver `major`、`minor` 或 `patch` 更新（例如：`version-update:semver-patch` 将忽略补丁更新）。 您可以将此与 `dependency-name: "*"` 结合，以忽略所有依赖项的特定 `update-types`。 目前，`version-update:semver-major`、`version-update:semver-minor` 和 `version-update:semver-patch` 是唯一支持的选项。 安全更新不受此设置的影响。
 
diff --git a/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index 8a6fc12866..1470c20035 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -124,8 +124,7 @@ aAAAe9
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
 {%- if secret-scanning-org-dry-runs %}
 1. 当您准备好测试新的自定义模式时，要识别所选存储库中的匹配项而不创建警报，请单击 **Save and dry run（保存并试运行）**。
-1. 搜索并选择要在其中执行试运行的存储库。 您最多可以选择 10 个存储库。 ![显示为试运行选择的存储库的屏幕截图](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
-1. 当您准备好测试新的自定义模式时，请单击 **Dry run（试运行）**。
+{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
 {% data reusables.advanced-security.secret-scanning-dry-run-results %}
 {%- endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
@@ -142,8 +141,15 @@ aAAAe9
 
 {% note %}
 
+{% if secret-scanning-enterprise-dry-runs %}
+**注意：**
+- At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run.
+- Enterprise owners can only make use of dry runs on repositories that they have access to, and enterprise owners do not necessarily have access to all the organizations or repositories within the enterprise.
+{% else %}
 **注意：** 由于没有试运行功能，我们建议您先在存储库中测试自定义模式，然后再为整个企业定义它们。 这样，可以避免创建过多的误报 {% data variables.product.prodname_secret_scanning %} 警报。
 
+{% endif %}
+
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
@@ -152,6 +158,11 @@ aAAAe9
 {% data reusables.enterprise-accounts.advanced-security-security-features %}
 1. 在“Secret scanning custom patterns（机密扫描自定义模式）”下，单击 {% ifversion ghes = 3.2 %}**New custom pattern（新建自定义模式）**{% else %}**New pattern（新建模式）**{% endif %}。
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{%- if secret-scanning-enterprise-dry-runs %}
+1. 当您准备好测试新的自定义模式时，要识别存储库中的匹配项而不创建警报，请单击 **Save and dry run（保存并空运行）**。
+{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
+{% data reusables.advanced-security.secret-scanning-dry-run-results %}
+{%- endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 创建模式后，{% data variables.product.prodname_secret_scanning %} 扫描企业组织内存储库中的任何机密，并启用 {% data variables.product.prodname_GH_advanced_security %}，包括其所有分支上的整个 Git 历史记录。 组织所有者和仓库管理员将会收到发现的任何密钥警报通知，并且可以审查发现密钥的仓库中的警报。 有关查看 {% data variables.product.prodname_secret_scanning %} 警报的详细信息，请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/code-security/secret-security/managing-alerts-from-secret-scanning)”。
diff --git a/translations/zh-CN/content/codespaces/getting-started/quickstart.md b/translations/zh-CN/content/codespaces/getting-started/quickstart.md
index 5807cf92cb..133be8baec 100644
--- a/translations/zh-CN/content/codespaces/getting-started/quickstart.md
+++ b/translations/zh-CN/content/codespaces/getting-started/quickstart.md
@@ -15,7 +15,7 @@ redirect_from:
 
 ## 简介
 
-在本指南中，您将从[模板存储库](https://github.com/2percentsilk/haikus-for-codespaces)创建代码空间，并探索代码空间中可用的一些基本功能。
+在本指南中，您将从[模板存储库](https://github.com/github/haikus-for-codespaces)创建代码空间，并探索代码空间中可用的一些基本功能。
 
 在本快速入门中，您将了解如何创建代码空间、连接到转发的端口以查看正在运行的应用程序、在代码空间中使用版本控制以及使用扩展个性化设置。
 
@@ -23,7 +23,7 @@ redirect_from:
 
 ## 创建代码空间
 
-1. 导航到 [template repository（模板存储库）](https://github.com/2percentsilk/haikus-for-codespaces) 并选择 **Use this template（使用此模板）**。
+1. 导航到 [template repository（模板存储库）](https://github.com/github/haikus-for-codespaces) 并选择 **Use this template（使用此模板）**。
 
 2. 命名存储库，选择首选隐私设置，然后单击 **Create repository from template（从模板创建存储库）**。
 
diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
index fa4c2d0088..90494d097a 100644
--- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
@@ -58,20 +58,20 @@ miniTocMaxHeadingLevel: 3
 
 1. 对预构建配置进行所需的更改，然后单击 **Update（更新）**。
 
-### Disabling a prebuild configuration
+### 禁用预构建配置
 
-To pause the update of prebuild templates for a configuration, you can disable workflow runs for the configuration. Disabling the workflow runs for a prebuild configuration does not delete any previously created prebuild templates for that configuration and, as a result, codespaces will continue to be generated from an existing prebuild template.
+要暂停更新配置的预构建模板，可以禁用配置的工作流程运行。 为预构建配置禁用工作流程不会删除以前为该配置创建的任何预构建模板，因此，代码空间将继续从现有预构建模板生成。
 
-Disabling the workflow runs for a prebuild configuration is useful if you need to investigate template creation failures.
+如果需要调查模板创建失败，则禁用工作流程运行预构建配置非常有用。
 
-1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to disable.
-1. In the dropdown menu, click **Disable runs**.
+1. 在存储库设置的 {% data variables.product.prodname_codespaces %} 页面上，单击要禁用的预构建配置右侧的省略号。
+1. 在下拉菜单中，单击 **Disable runs（禁用运行）**。
 
-   ![The 'Disable runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-disable.png)
+   ![下拉菜单中的“Disable runs（禁用运行）”选项](/assets/images/help/codespaces/prebuilds-disable.png)
 
-1. To confirm that you want to disable this configuration, click **OK**.
+1. 要确认是否要禁用此配置，请单击“ **OK（确定）**”。
 
-### Deleting a prebuild configuration
+### 删除预构建配置
 
 删除预构建配置也会删除以前为该配置创建的所有预构建模板。 因此，在删除配置后不久，在创建新代码空间时，由该配置生成的预构建将不再可用。
 
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
index 2b917fb848..fa715ae175 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
@@ -114,7 +114,7 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
 
 ## 使用默认开发容器配置
 
-如果未在存储库中定义配置，{% data variables.product.prodname_dotcom %} 使用默认 Linux 映像创建代码空间。 这个 Linux 镜像包括 Python、Node.js、JavaScript、TypeScript、C++、Java、.NET、PHP、PowerShell、Go、Ruby 和 Rust 等语言和运行时。 它还包括其他开发工具和实用程序，例如 Git、GitHub CLI、yarn、openssh 和 vim。 要查看包含的所有语言、运行时和工具，请在代码空间终端内使用 `devcontainer-info content-url` 命令，然后遵循命令输出的 URL。
+如果未在存储库中定义配置，{% data variables.product.prodname_dotcom %} 使用默认 Linux 映像创建代码空间。 This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. 要查看包含的所有语言、运行时和工具，请在代码空间终端内使用 `devcontainer-info content-url` 命令，然后遵循命令输出的 URL。
 
 或者，要详细了解默认 Linux 映像中包含的所有内容，请参阅 [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) 仓库中的最新文件。
 
@@ -138,7 +138,7 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
 
    ![确定按钮](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
 
-1. 如果在代码空间中工作，请应用更改，方法是单击窗口右下角消息中的**立即重新构建**。 For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)."
+1. 如果在代码空间中工作，请应用更改，方法是单击窗口右下角消息中的**立即重新构建**。 有关重建容器的更多信息，请参阅“[应用对配置的更改](#applying-configuration-changes-to-a-codespace)”。
 
    ![{% data variables.product.prodname_vscode_command_palette %} 中的"Codespaces：重新构建容器"](/assets/images/help/codespaces/rebuild-prompt.png)
 
@@ -163,7 +163,7 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
 
    ![容器配置期间的选择其他功能菜单。](/assets/images/help/codespaces/select-additional-features.png)
 
-1. 要应用更改，请在屏幕右下角单击 **Rebuild now（立即重建）**。 For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)."
+1. 要应用更改，请在屏幕右下角单击 **Rebuild now（立即重建）**。 有关重建容器的更多信息，请参阅“[应用对配置的更改](#applying-configuration-changes-to-a-codespace)”。
 
    ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/rebuild-prompt.png)
 
@@ -211,7 +211,7 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
 * 在存储库的 `.vscode/settings.json` 文件中定义的编辑器设置将作为代码空间中_工作区_范围的设置进行应用。
 * `devcontainer.json` 文件的 `settings` 键中定义的编辑器设置在代码空间中用作 _Remote [Codespaces]_ 范围的设置。
 
-## Applying configuration changes to a codespace
+## 将配置更改应用于代码空间
 
 {% data reusables.codespaces.apply-devcontainer-changes %}
 
diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index e72e2655d3..86c1abd921 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -57,9 +57,9 @@ cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME
 * 检查最近是否将对开发容器配置的更改推送到启用了预构建的分支。 如果是这样，通常必须等到为此推送运行的预构建工作流程完成，然后预构建才会再次可用。
 * 如果最近未进行任何配置更改，请转到存储库的“ **操作** ”选项卡，单击工作流程列表中的 **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} 预构建** ，然后检查分支的预构建工作流程运行是否成功。 如果工作流程的最新运行失败，并且其中一个或多个失败的运行包含对开发容器配置的更改，则关联分支将没有可用的预构建。
 
-## Troubleshooting failed workflow runs for prebuilds
+## 预构建工作流程运行失败疑难解答
 
-If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
+如果为预构建配置运行的工作流程失败，则可以在调查时暂时禁用预构建配置。 更多信息请参阅“[管理预构建](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)”。
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
index 67582aae15..25bee075ec 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -47,13 +47,13 @@ shortTitle: 管理评论
 
 编辑评论和删除无助于促进对话以及违反社区行为准则{% ifversion fpt or ghec %} 或 GitHub [社区指导方针](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %} 的内容是明智之举。
 
-Sometimes it may make sense to clearly indicate edits and their justification.
+有时，明确指出编辑及其理由可能是有意义的。
 
-That said, anyone with read access to a repository can view a comment's edit history. 评论顶部的 **edited（已编辑）**下拉菜单包含编辑历史记录，其中会显示每次编辑的用户和时间戳。
+也就是说，对存储库具有读取访问权限的任何人都可以查看评论的编辑历史记录。 评论顶部的 **edited（已编辑）**下拉菜单包含编辑历史记录，其中会显示每次编辑的用户和时间戳。
 
 ![添加了表示内容编辑过的注释的评论](/assets/images/help/repository/content-redacted-comment.png)
 
-## Redacting sensitive information
+## 编辑敏感信息
 
 评论作者和具有仓库写入权限的任何人也都可以删除评论编辑历史记录中的敏感信息。 更多信息请参阅“[跟踪评论中的更改](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)”。
 
@@ -81,7 +81,7 @@ That said, anyone with read access to a repository can view a comment's edit his
 
 {% endnote %}
 
-### Steps to delete a comment
+### 删除评论的步骤
 
 1. 导航到您要删除的评论。
 2. 在评论的右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Delete（删除）**。 ![显示编辑、隐藏、删除和报告选项的水平烤肉串图标和评论调解菜单](/assets/images/help/repository/comment-menu.png)
diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md
index 9d5de728df..ab98ff230a 100644
--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md
@@ -1,6 +1,6 @@
 ---
-title: 关注组织
-intro: '您可以关注 {% data variables.product.product_name %} 上的组织，以接收有关其活动的通知。'
+title: Following organizations
+intro: 'You can follow organizations on {% data variables.product.product_name %} to receive notifications about their activity.'
 versions:
   feature: for-you-feed
 topics:
@@ -9,42 +9,42 @@ topics:
 
 {% note %}
 
-**注意：** 关注组织的功能目前处于公开测试阶段，可能会发生变化。
+**Note:** The ability to follow organizations is currently in public beta and subject to change.
 
 {% endnote %}
 
-## 关于 {% data variables.product.product_name %} 上的关注者
+## About followers on {% data variables.product.product_name %}
 
-当您关注组织时，您将在个人仪表板上看到他们的公共活动。 更多信息请参阅“[关于个人仪表板](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)”。
+When you follow organizations, you'll see their public activity on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)."
 
 You can unfollow an organization if you do not wish to see their {% ifversion fpt or ghec %}public{% endif %} activity on {% data variables.product.product_name %}.
 
-## 在 {% data variables.product.product_name %} 上关注组织
+## Following an organization on {% data variables.product.product_name %}
 
-1. 转到要关注的组织页面
-2. 点击标题右上角的 **Follow（关注）**
+1. Go to the organization page you want to follow
+2. Click **Follow** in the top-right corner of the header
 
-  ![组织标题的屏幕截图，突出显示了“关注”按钮](/assets/images/help/profile/organization-profile-following.png)
+  ![Screenshot of the organization header, with the follow button highlighted](/assets/images/help/profile/organization-profile-following.png)
 
-## 在 {% data variables.product.product_name %} 上取消关注组织
+## Unfollowing an organization on {% data variables.product.product_name %}
 
-1. 转到要取消关注的组织页面
-2. 点击标题右上角的 **Unfollow（取消关注）**。
+1. Go to the organization page you want to unfollow
+2. Click **Unfollow** in the top-right corner of the header.
 
-  ![组织标题的屏幕截图，突出显示了“取消关注”按钮](/assets/images/help/profile/organization-profile-unfollowing.png)
+  ![Screenshot of the organization header, with the unfollow button highlighted](/assets/images/help/profile/organization-profile-unfollowing.png)
 
-## 查看用户在 {% data variables.product.product_name %} 上关注的人员和组织
+## Viewing people and organizations a user follows on {% data variables.product.product_name %}
 
-1. 单击用户图像以显示该用户的配置文件。
+1. Click a user image to display that user's profile.
 
-  ![用户图像](/assets/images/help/profile/user-profile-image.png)
+  ![User image](/assets/images/help/profile/user-profile-image.png)
 
-2. 在其个人资料图片下点击**关注**。
+2. Click **following** under their profile image.
 
-  ![用户关注](/assets/images/help/profile/user-profile-following.png)
+  ![User following](/assets/images/help/profile/user-profile-following.png)
 
 {% ifversion fpt or ghec %}
-## 延伸阅读
+## Further reading
 
-- “[关注人员](/get-started/exploring-projects-on-github/following-people)”
+- "[Following people](/get-started/exploring-projects-on-github/following-people)"
 {% endif %}
diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
index fab84e17e6..ed35a2fcd1 100644
--- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
@@ -154,7 +154,7 @@ gh repo fork repository --clone=true
 
 6. 键入 `git remote add upstream`，然后粘贴您在第 3 步中复制的 URL 并按 **Enter** 键。 它将如下所示：
   ```shell
-  $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
+  $ git remote add upstream https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/Spoon-Knife.git
   ```
 
 7. 要验证为复刻指定的新上游仓库，请再次键入 `git remote -v`。 您应该看到复刻的 URL 为 `origin`，原始仓库的 URL 为 `upstream`。
diff --git a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index b7d84a2064..b649f2889b 100644
--- a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -239,7 +239,7 @@ git commit
 
 {% note %}
 
-**Note:** A person will only be notified about a mention if the person has read access to the repository and, if the repository is owned by an organization, the person is a member of the organization.
+**注意：**某人仅在其对存储库具有读取权限以及为组织成员（如果存储库归组织所有）时，才会收到有关提及的通知。
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
index 0bdcdbafe9..df2599c695 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -22,6 +22,8 @@ topics:
 
 议题让您可以在进行开发的 {% data variables.product.company_short %} 上跟踪您的工作。 当您在议题中提到另一个议题或拉取请求时，该议题的时间表会反映交叉参考，以便你能够跟踪相关的工作。 要表示工作正在进行中，您可以将议题链接到拉取请求。 当拉取请求合并时，链接的议题会自动关闭。
 
+For more information on keywords, see "[Linking a pull request to an issue](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)."
+
 ## 快速创建议题
 
 议题可以通过多种方式创建，因此您可以为工作流程选择最方便的方法。 例如，您可以从仓库创建议题、{% ifversion fpt or ghec %} 任务列表中的项目、{% endif %} 项目中的注释、议题或拉取请求中的评论、特定代码行或 URL 查询。 您也可以从选择的平台创建议题：通过 Web 界面、{% data variables.product.prodname_desktop %}、{% data variables.product.prodname_cli %}、GraphQL 和 REST API 或 {% data variables.product.prodname_mobile %}。 更多信息请参阅“[创建议题](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)”。
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 64fc4c2aee..fd9d632f4c 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -35,7 +35,7 @@ shortTitle: 将 PR 链接到议题
 
 ## 使用关键词将拉取请求链接到议题
 
-您可以在拉取请求说明或提交消息中使用支持的关键字将拉取请求链接到议题（请注意，拉取请求必须在默认分支上）。
+You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message. The pull request **must be** on the default branch.
 
 * close
 * closes
@@ -47,7 +47,7 @@ shortTitle: 将 PR 链接到议题
 * resolves
 * resolved
 
-如果使用关键字在另一个拉取请求中引用拉取请求注释，则将链接拉取请求。 Merging the referencing pull request will also close the referenced issue.
+如果使用关键字在另一个拉取请求中引用拉取请求注释，则将链接拉取请求。 Merging the referencing pull request also closes the referenced pull request.
 
 关闭关键词的语法取决于议题是否与拉取请求在同一仓库中。
 
@@ -61,7 +61,6 @@ shortTitle: 将 PR 链接到议题
 
 您也可以在提交消息中使用关闭关键词。 议题将在提交合并到默认分支时关闭，但包含提交的拉取请求不会列为链接的拉取请求。
 
-
 {% ifversion fpt or ghes or ghae or ghec %}
 ## 手动将拉取请求链接到议题
 
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
index fcc2e7fa11..02198ad9a0 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
@@ -163,7 +163,7 @@ topics:
 6. 如果您指定**单选**为类型，请输入选项。
 7. 如果指定**迭代**为类型，请输入第一个迭代的开始日期和迭代的持续时间。 将自动创建三个迭代，您可以在项目的设置页上添加其他迭代。
 
-You can also edit your custom fields.
+您还可以编辑自定义字段。
 
 {% data reusables.projects.project-settings %}
 1. 在 **Fields（字段）**下，选择要编辑的字段。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
index ece1da96e7..2c78a26a77 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -16,13 +16,13 @@ shortTitle: 设置可见性更改策略
 permissions: Organization owners can restrict repository visibility changes for an organization.
 ---
 
-You can restrict who has the ability to change the visibility of repositories in your organization, such as changing a repository from private to public. For more information about repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+您可以限制谁能够更改组织中存储库的可见性，例如将存储库从私有更改为公共存储库。 有关存储库可见性的更多信息，请参阅“[关于存储库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。
 
-You can restrict the ability to change repository visibility to organization owners only, or you can allow anyone with admin access to a repository to change visibility.
+您可以将更改存储库可见性的功能限制为仅组织所有者，也可以允许对存储库具有管理员访问权限的任何人更改可见性。
 
 {% warning %}
 
-**Warning**: If enabled, this setting allows people with admin access to choose any visibility for an existing repository, even if you do not allow that type of repository to be created. 有关在创建过程中限制仓库可见性的更多信息，请参阅“[限制组织中的仓库创建](/articles/restricting-repository-creation-in-your-organization)”。
+**警告**：如果启用，则此设置允许具有管理员访问权限的人员选择现有存储库的任何可见性，即使您不允许创建该类型的存储库也是如此。 有关在创建过程中限制仓库可见性的更多信息，请参阅“[限制组织中的仓库创建](/articles/restricting-repository-creation-in-your-organization)”。
 
 {% endwarning %}
 
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
index b5e4f2c00e..5229b2851a 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
@@ -15,7 +15,7 @@ shortTitle: 更改站点可见性
 
 {% data reusables.pages.privately-publish-ghec-only %}
 
-If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. 有关 {% data variables.product.prodname_emus %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)”。
+如果您的企业使用 {% data variables.product.prodname_emus %}，则访问控制不可用，并且所有 {% data variables.product.prodname_pages %} 站点仅供其他企业成员访问。 有关 {% data variables.product.prodname_emus %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)”。
 
 如果您的组织使用 {% data variables.product.prodname_ghe_cloud %} 而没有 {% data variables.product.prodname_emus %}，您可以选择在互联网上私下或公开地向任何人发布您的站点。 从组织拥有的私人或内部仓库发布的项目站点可使用访问控制。 您无法管理组织站点的访问控制。 有关 {% data variables.product.prodname_pages %} 站点类型的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。
 
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
index 57f4eeb67f..69d2cfe6c9 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -22,7 +22,10 @@ shortTitle: 配置提交压缩
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 3. 在 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"拉取请求"{% else %}"合并按钮"{% endif %} 下，可以选择 **Allow merge commits（允许合并提交）**。 这将允许贡献者合并具有完整提交历史记录的拉取请求。 ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
-4. 在 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}“拉取请求”{% else %}“合并按钮”{% endif %} 下，选择 **Allow squash merging（允许压缩合并）**。 这将允许贡献者通过将所有提交压缩到单个提交中来合并拉取请求。 如果除了 **Allow squash merging（允许压缩合并）**之外，您还选择了另一种合并方法，则贡献者在合并拉取请求时能够选择合并提交的类型。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![拉取请求压缩提交](/assets/images/help/repository/pr-merge-squash.png)
+4. 在 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}“拉取请求”{% else %}“合并按钮”{% endif %} 下，选择 **Allow squash merging（允许压缩合并）**。 这将允许贡献者通过将所有提交压缩到单个提交中来合并拉取请求。 The squash message automatically defaults to the title of the pull request if it contains more than one commit. {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}If you want to use the title of the pull request as the default merge message for all squashed commits, regardless of the number of commits in the pull request, select **Default to PR title for squash merge commits**. ![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png){% else %}
+![Pull request squashed commits](/assets/images/enterprise/3.5/repository/pr-merge-squash.png){% endif %}
+
+If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %}
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index 7108cb73f1..f133179605 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -162,13 +162,13 @@ remote: error: Changes have been requested.
 如果您的仓库为使用 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %} 的组织所拥有，您可以启用分支限制。
 {% endif %}
 
-启用分支限制时，只有已授予权限的用户、团队或应用程序才能推送到受保护的分支。 您可以在受保护分支的设置中查看和编辑对受保护分支具有推送权限的用户、团队或应用程序。 When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging into the branch when the required checks fail. 当需要拉取请求时，有权推送到受保护分支的人员、团队和应用仍需要创建拉取请求。
+启用分支限制时，只有已授予权限的用户、团队或应用程序才能推送到受保护的分支。 您可以在受保护分支的设置中查看和编辑对受保护分支具有推送权限的用户、团队或应用程序。 当需要状态检查时，如果所需的检查失败，仍会阻止有权推送到受保护分支的人员、团队和应用合并到分支。 当需要拉取请求时，有权推送到受保护分支的人员、团队和应用仍需要创建拉取请求。
 
 {% if restrict-pushes-create-branch %}
-Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`.
+（可选）您可以对创建与规则匹配的分支应用相同的限制。 例如，如果创建的规则仅允许某个团队推送到包含 `release` 一词的任何分支，则只有该团队的成员才能创建包含 `release` 一词的新分支。
 {% endif %}
 
-You can only give push access to a protected branch, or give permission to create a matching branch, to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch or create a matching branch.
+您只能向具有存储库写入访问权限的用户、团队或已安装 {% data variables.product.prodname_github_apps %} 授予对受保护分支的推送访问权限，或授予创建匹配分支的权限。 对存储库具有管理员权限的人员和应用始终能够推送到受保护的分支或创建匹配的分支。
 
 ### 允许强制推送
 
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index 88ca6b8ea5..49ac86c24d 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -89,8 +89,8 @@ shortTitle: 分支保护规则
 1. （可选）选择 **Apply the rules above to administrators（将上述规则应用于管理员）**。 ![将上述规则应用于管理员复选框](/assets/images/help/repository/include-admins-protected-branches.png)
 1. （可选）{% ifversion fpt or ghec %}如果仓库由组织拥有，可使用 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %}{% endif %} 启用分支限制。
    - 选择 **Restrict who can push to matching branches（限制谁可以推送到匹配分支）**。 ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png){% if restrict-pushes-create-branch %}
-   - Optionally, to also restrict the creation of matching branches, select **Restrict pushes that create matching branches**. ![Branch creation restriction checkbox](/assets/images/help/repository/restrict-branch-create.png){% endif %}
-   - Search for and select the people, teams, or apps who will have permission to push to the protected branch or create a matching branch. ![Branch restriction search]{% if restrict-pushes-create-branch %}(/assets/images/help/repository/restrict-branch-search-with-create.png){% else %}(/assets/images/help/repository/restrict-branch-search.png){% endif %}
+   - （可选）要同时限制创建匹配分支，请选择 **Restrict pushes that create matching branches（限制创建匹配分支的推送）**。 ![Branch creation restriction checkbox](/assets/images/help/repository/restrict-branch-create.png){% endif %}
+   - 搜索并选择将有权推送到受保护分支或创建匹配分支的人员、团队或应用。 ![分支限制搜索]{% if restrict-pushes-create-branch %}(/assets/images/help/repository/restrict-branch-search-with-create.png){% else %}(/assets/images/help/repository/restrict-branch-search.png){% endif %}
 1. （可选）在“Rules applied to everyone including administrators（适用于包括管理员在内的所有人规则）”下，选择 **Allow force pushes（允许强制推送）**。 ![允许强制推送选项](/assets/images/help/repository/allow-force-pushes.png)
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %}
   然后，选择谁可以强制推送到分支。
diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md
index d4b1b55702..fe8c8fe76f 100644
--- a/translations/zh-CN/content/rest/overview/libraries.md
+++ b/translations/zh-CN/content/rest/overview/libraries.md
@@ -42,7 +42,7 @@ topics:
 
 | 库名称             | 仓库                                                                      |
 | --------------- | ----------------------------------------------------------------------- |
-| **github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) |
+| **github.dart** | [SpinlockLabs/github.dart](https://github.com/SpinlockLabs/github.dart) |
 
 ### Emacs Lisp
 
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index 4814f98857..fcf63a9e86 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -300,10 +300,10 @@ shortTitle: 搜索议题和 PR
 
 您可以使用 `is` 限定符基于拉取请求已合并还是未合并进行过滤。
 
-| 限定符           | 示例                                                                                                                            |
-| ------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `is:merged`   | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) 匹配含有 "bug" 字样的已合并拉取请求。 |
-| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) 匹配含有 "error" 字样的已关闭议题和拉取请求。     |
+| 限定符           | 示例                                                                                                                                                                                                  |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:merged`   | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) 匹配含有 "bug" 字样的已合并拉取请求。                                                                       |
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches pull requests with the word "error" that are either open or were closed without being merged. |
 
 ## 基于仓库是否已存档搜索
 
diff --git a/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md b/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
index ca56371f79..c9590fdb76 100644
--- a/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
@@ -73,7 +73,7 @@ To report account, security, and abuse issues, or to receive assisted support fo
 {% ifversion fpt %}
 If you have any paid product or are a member of an organization with a paid product, you can contact {% data variables.contact.github_support %} in English.
 {% else %} 
-With {% data variables.product.product_name %}, you have access to support in English{% ifversion ghes %} and Japanese{% endif %}.
+With {% data variables.product.product_name %}, you have access to support in English and Japanese.
 {% endif %}
 
 {% ifversion ghes or ghec %}
@@ -135,18 +135,24 @@ To learn more about training options, including customized trainings, see [{% da
 
 {% endif %}
 
-{% ifversion ghes %}
+{% ifversion ghes or ghec %}
 ## Hours of operation
 
 ### Support in English
 
 For standard non-urgent issues, we offer support in English 24 hours per day, 5 days per week, excluding weekends and national U.S. holidays. The standard response time is 24 hours.
 
+{% ifversion ghes %}
 For urgent issues, we are available 24 hours per day, 7 days per week, even during national U.S. holidays.
+{% endif %}
 
 ### Support in Japanese
 
-For non-urgent issues, support in Japanese is available Monday through Friday from 9:00 AM to 5:00 PM JST, excluding national holidays in Japan. For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays.
+For standard non-urgent issues, support in Japanese is available Monday through Friday from 9:00 AM to 5:00 PM JST, excluding national holidays in Japan. 
+
+{% ifversion ghes %}
+For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays.
+{% endif %}
 
 For a complete list of U.S. and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."
 
@@ -164,7 +170,7 @@ For urgent issues, we can help you in English 24 hours per day, 7 days per week,
 
 {% data variables.contact.enterprise_support %} does not provide Japanese-language support on December 28th through January 3rd as well as on the holidays listed in [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html).
 
-{% data reusables.enterprise_enterprise_support.installing-releases %}
+{% ifversion ghes %}{% data reusables.enterprise_enterprise_support.installing-releases %}{% endif %}
 
 {% endif %}
 
diff --git a/translations/zh-CN/data/features/dependabot-grouped-dependencies.yml b/translations/zh-CN/data/features/dependabot-grouped-dependencies.yml
new file mode 100644
index 0000000000..2dd2406822
--- /dev/null
+++ b/translations/zh-CN/data/features/dependabot-grouped-dependencies.yml
@@ -0,0 +1,8 @@
+---
+#Reference: #6913
+#Dependabot support for TypeScript @types/*
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6913'
diff --git a/translations/zh-CN/data/features/secret-scanning-enterprise-dry-runs.yml b/translations/zh-CN/data/features/secret-scanning-enterprise-dry-runs.yml
new file mode 100644
index 0000000000..1ce219308f
--- /dev/null
+++ b/translations/zh-CN/data/features/secret-scanning-enterprise-dry-runs.yml
@@ -0,0 +1,7 @@
+---
+#Issue #6904
+#Documentation for the "enterprise account level dry runs (Public Beta)" for custom patterns under secret scanning
+versions:
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6904'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml
index 268445d726..943d30bd05 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml
@@ -46,7 +46,7 @@ sections:
       heading: Server Statistics in public beta
       notes:
         - |
-          You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see "[About Server Statistics](/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." **Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content.  For a better understanding of how we store and secure Server Statistics data, see "[GitHub Security](https://github.com/security)."**  For more information about Server Statistics, see "[Analyzing how your team works with Server Statistics](/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics)." This feature is available in public beta.
+          You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." **Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content.  For a better understanding of how we store and secure Server Statistics data, see "[GitHub Security](https://github.com/security)."**  For more information about Server Statistics, see "[Analyzing how your team works with Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics)." This feature is available in public beta.
     - 
       heading: GitHub Actions rate limiting is now configurable
       notes:
@@ -101,7 +101,6 @@ sections:
           - You can pass environment secrets to reusable workflows.
           - The audit log includes information about which reusable workflows are used.
           - Reusable workflows in the same repository as the calling repository can be referenced with just the path and filename (`PATH/FILENAME`). The called workflow will be from the same commit as the caller workflow.
-          - Reusable workflows are subject to your organization's actions access policy. Previously, even if your organization had configured the "Allow select actions" policy, you were still able to use a reusable workflow from any location. Now if you use a reusable workflow that falls outside of that policy, your run will fail. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)."
     - 
       heading: Self-hosted runners for GitHub Actions can now disable automatic updates
       notes:
diff --git a/translations/zh-CN/data/reusables/actions/hardware-requirements-3.5.md b/translations/zh-CN/data/reusables/actions/hardware-requirements-3.5.md
new file mode 100644
index 0000000000..d3549be8a1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/hardware-requirements-3.5.md
@@ -0,0 +1,7 @@
+| vCPU | 内存     | 最大并行数    |
+|:---- |:------ |:-------- |
+| 8    | 64 GB  | 740 个作业  |
+| 16   | 128 GB | 1250 个作业 |
+| 32   | 160 GB | 2700 个作业 |
+| 64   | 256 GB | 4500 个作业 |
+| 96   | 384 GB | 7000 个作业 |
diff --git a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-results.md b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-results.md
index 703f7837f0..ab68fadc11 100644
--- a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-results.md
+++ b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-results.md
@@ -1,3 +1,3 @@
-1. 空运行完成后，您将看到存储库中的结果示例（最多 1000 个）。 查看结果并确定任何误报结果。 ![显示空运行结果的屏幕截图](/assets/images/help/repository/secret-scanning-publish-pattern.png)
+1. When the dry run finishes, you'll see a sample of results (up to 1000). 查看结果并确定任何误报结果。 ![显示空运行结果的屏幕截图](/assets/images/help/repository/secret-scanning-publish-pattern.png)
 1. Edit the new custom pattern to fix any problems with the results, then, to test your changes, click **Save and dry run**.
 {% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
new file mode 100644
index 0000000000..aecd72898f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
@@ -0,0 +1,2 @@
+1. Search for and select up to 10 repositories where you want to perform the dry run. ![显示为试运行选择的存储库的屏幕截图](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
+1. 当您准备好测试新的自定义模式时，请单击 **Dry run（试运行）**。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md
index 69ea46920d..b629736d74 100644
--- a/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md
+++ b/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md
@@ -48,6 +48,12 @@ If you plan to enable {% data variables.product.prodname_actions %} for the user
 
 {%- endif %}
 
+{%- ifversion ghes = 3.5 %}
+
+{% data reusables.actions.hardware-requirements-3.5 %}
+
+{%- endif %}
+
 For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
 
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md b/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md
index 5baccfd169..a5047a9b64 100644
--- a/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md
+++ b/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md
@@ -1 +1 @@
-当 Git 提示您输入密码时，请输入您的个人访问令牌 (PAT)。{% ifversion not ghae %} 基于密码的身份验证对 Git 已删除，使用 PAT 更安全。{% endif %} 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
+When Git prompts you for your password, enter your personal access token (PAT). Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."