diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md index cf77b48a2c..56c61d9b6d 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md @@ -4,8 +4,9 @@ shortTitle: Deploying to your cloud provider intro: 'You can deploy to various cloud providers, such as AWS, Azure, and GKE.' versions: fpt: '*' - ghae: 'issue-4856' + ghae: '*' ghec: '*' + ghes: '*' children: - /deploying-to-amazon-elastic-container-service - /deploying-to-azure diff --git a/translations/pt-BR/data/glossaries/README.md b/translations/pt-BR/data/glossaries/README.md index 7cc5bdeed1..c6bc4f4688 100644 --- a/translations/pt-BR/data/glossaries/README.md +++ b/translations/pt-BR/data/glossaries/README.md @@ -3,5 +3,6 @@ Os seguintes arquivos compreendem o nosso [Glossário Crowdin](https://support.crowdin.com/glossary/): * `external.yml` contém entradas do glossário voltadas para o cliente. + * Strings within `external.yml` support Liquid conditionals. See [contributing/liquid-helpers.md](/contributing/liquid-helpers.md). * `internal.yml` contém entradas utilizadas apenas pelos tradutores. Estes termos são exibidos na interface do usuário Crowdin para dar aos tradutores um contexto adicional sobre o que eles estão traduzindo, além de uma string localizada sugerida para esse termo. * `candidates.yml` contém termos que devem estar potencialmente no glossário interno ou externo, mas que ainda não foram definidos. diff --git a/translations/pt-BR/data/learning-tracks/README.md b/translations/pt-BR/data/learning-tracks/README.md index bf9e189ab6..db563b2c48 100644 --- a/translations/pt-BR/data/learning-tracks/README.md +++ b/translations/pt-BR/data/learning-tracks/README.md @@ -33,7 +33,10 @@ O versionamento para faixas de aprendizagem é processado na página tempo de in Condicionais líquidas **não** tem que ser usadas para versionamento no arquivo YAML para guias. Apenas os guias do caminho de aprendizagem que se aplicam à versão atual serão processados automaticamente. Se não houver nenhuma faixa com guias que pertençam à versão atual, a seção de faixas de aprendizado não será interpretada. -versionamento explícito dentro das faixas de aprendizado de um produto YML também é compatível. Por exemplo: +versionamento explícito dentro das faixas de aprendizado de um produto YML também é compatível. O formato e os valores permitidos são os mesmos que [frontmatter versions property](/content#versions). + +Por exemplo: + ``` learning_track_name: title: 'Learning track title' @@ -45,6 +48,7 @@ learning_track_name: - /path/to/guide1 - /path/to/guide2 ``` + Se a propriedade de `versões` não estiver incluída, deduz-se que a faixa está disponível em todas as versões. ## Aplicação de esquema diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/22.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/22.yml index 8dd825f030..ad7ce5b33a 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-0/22.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/22.yml @@ -3,6 +3,7 @@ date: '2021-12-13' sections: security_fixes: - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.' + - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.' known_issues: - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. - As regras de firewall personalizadas são removidas durante o processo de atualização. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/14.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/14.yml index 50f3d13fa5..b52984f9d5 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/14.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/14.yml @@ -3,6 +3,7 @@ date: '2021-12-13' sections: security_fixes: - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.' + - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.' known_issues: - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/6.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/6.yml index 035066bb18..38bcf6b53e 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/6.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/6.yml @@ -3,6 +3,7 @@ date: '2021-12-13' sections: security_fixes: - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.' + - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.' known_issues: - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. - As regras de firewall personalizadas são removidas durante o processo de atualização. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-3/1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-3/1.yml index 79b273b96a..14731f057d 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-3/1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-3/1.yml @@ -3,6 +3,7 @@ date: '2021-12-13' sections: security_fixes: - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.' + - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.' known_issues: - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command. - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. diff --git a/translations/pt-BR/data/reusables/actions/create-azure-app-plan.md b/translations/pt-BR/data/reusables/actions/create-azure-app-plan.md index cfa4a2b1c5..c16562f449 100644 --- a/translations/pt-BR/data/reusables/actions/create-azure-app-plan.md +++ b/translations/pt-BR/data/reusables/actions/create-azure-app-plan.md @@ -1,6 +1,6 @@ -1. Create an Azure App Service plan. +1. Crie um plano do Azure App Service. - For example, you can use the Azure CLI to create a new App Service plan: + Por exemplo, você pode usar o CLI do Azure para criar um novo plano de App Service: ```bash{:copy} az appservice plan create \ @@ -9,9 +9,9 @@ --is-linux ``` - In the command above, replace `MY_RESOURCE_GROUP` with your pre-existing Azure Resource Group, and `MY_APP_SERVICE_PLAN` with a new name for the App Service plan. + No comando acima, substitua `MY_RESOURCE_GROUP` pelo seu Grupo de Recursos do Azure pré-existente, e `MY_APP_SERVICE_PLAN` por um novo nome para o plano do App Service. - See the Azure documentation for more information on using the [Azure CLI](https://docs.microsoft.com/cli/azure/): + Para obter mais informações, consulte a documentação do Azure usando o [CLI do Azure](https://docs.microsoft.com/cli/azure/): - * For authentication, see "[Sign in with Azure CLI](https://docs.microsoft.com/cli/azure/authenticate-azure-cli)." - * If you need to create a new resource group, see "[az group](https://docs.microsoft.com/cli/azure/group?view=azure-cli-latest#az_group_create)." \ No newline at end of file + * Para autenticação, consulte "[Efetuar login com o CLI do Azure](https://docs.microsoft.com/cli/azure/authenticate-azure-cli)." + * Se você precisar criar um novo grupo de recursos, consulte "[grupo az](https://docs.microsoft.com/cli/azure/group?view=azure-cli-latest#az_group_create)". \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/create-azure-publish-profile.md b/translations/pt-BR/data/reusables/actions/create-azure-publish-profile.md index fc7ad43671..280425461e 100644 --- a/translations/pt-BR/data/reusables/actions/create-azure-publish-profile.md +++ b/translations/pt-BR/data/reusables/actions/create-azure-publish-profile.md @@ -1,5 +1,5 @@ -1. Configure an Azure publish profile and create an `AZURE_WEBAPP_PUBLISH_PROFILE` secret. +1. Configure um perfil de publicação do Azure e crie um segredo de `AZURE_WEBAPP_PUBLISH_PROFILE`. - Generate your Azure deployment credentials using a publish profile. For more information, see "[Generate deployment credentials](https://docs.microsoft.com/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials)" in the Azure documentation. + Gere suas credenciais de implantação do Azure usando um perfil de publicação. Para obter mais informações, consulte "[Gerar credenciais de implantação](https://docs.microsoft.com/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials)" na documentação do Azure. - In your {% data variables.product.prodname_dotcom %} repository, create a secret named `AZURE_WEBAPP_PUBLISH_PROFILE` that contains the contents of the publish profile. For more information on creating secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." \ No newline at end of file + No seu repositório {% data variables.product.prodname_dotcom %}, crie um segredo denominado `AZURE_WEBAPP_PUBLISH_PROFILE` que contém o conteúdo do perfil de publicação. Para obter mais informações sobre a criação de segredos, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md b/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md index edc5821cce..cd5f83499a 100644 --- a/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md +++ b/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md @@ -1 +1 @@ -**Note:** It can take up to 10 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}. If your don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." \ No newline at end of file +**Observação:** podem ser necessários até 10 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}. If your don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." \ No newline at end of file diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml index 06dbf1c8e1..b7806ff31d 100644 --- a/translations/pt-BR/data/ui.yml +++ b/translations/pt-BR/data/ui.yml @@ -29,7 +29,7 @@ toc: popular: Popular guides: Guias whats_new: O que há de novo - videos: Videos + videos: Vídeos pages: article_version: 'Versão do artigo' miniToc: Neste artigo