diff --git a/translations/log/msft-pt-resets.csv b/translations/log/msft-pt-resets.csv
index 6824ccc761..f9dff3e0b0 100644
--- a/translations/log/msft-pt-resets.csv
+++ b/translations/log/msft-pt-resets.csv
@@ -343,6 +343,7 @@ translations/pt-BR/data/release-notes/enterprise-server/3-2/6.yml,file deleted b
translations/pt-BR/data/release-notes/enterprise-server/3-2/7.yml,file deleted because it no longer exists in main
translations/pt-BR/data/release-notes/enterprise-server/3-2/8.yml,file deleted because it no longer exists in main
translations/pt-BR/data/release-notes/enterprise-server/3-2/9.yml,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md,file deleted because it no longer exists in main
translations/pt-BR/data/reusables/actions/hardware-requirements-3.6.md,file deleted because it no longer exists in main
translations/pt-BR/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main
translations/pt-BR/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main
@@ -542,6 +543,7 @@ translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-mach
translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
+translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,broken liquid tags
translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,rendering error
translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
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,rendering error
@@ -671,6 +673,7 @@ translations/pt-BR/content/code-security/adopting-github-advanced-security-at-sc
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
+translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,broken liquid tags
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
@@ -730,6 +733,7 @@ translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-de
translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md,broken liquid tags
translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,broken liquid tags
translations/pt-BR/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md,broken liquid tags
+translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md,broken liquid tags
translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,broken liquid tags
translations/pt-BR/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md,broken liquid tags
translations/pt-BR/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md,broken liquid tags
@@ -757,6 +761,7 @@ translations/pt-BR/content/codespaces/troubleshooting/exporting-changes-to-a-bra
translations/pt-BR/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags
translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md,broken liquid tags
translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md,broken liquid tags
+translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md,broken liquid tags
translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,broken liquid tags
translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md,broken liquid tags
translations/pt-BR/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md,broken liquid tags
@@ -789,6 +794,7 @@ translations/pt-BR/content/developers/overview/about-githubs-apis.md,broken liqu
translations/pt-BR/content/developers/overview/managing-deploy-keys.md,broken liquid tags
translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
+translations/pt-BR/content/developers/webhooks-and-events/webhooks/creating-webhooks.md,broken liquid tags
translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
@@ -971,6 +977,7 @@ translations/pt-BR/content/rest/enterprise-admin/scim.md,rendering error
translations/pt-BR/content/rest/enterprise-admin/users.md,broken liquid tags
translations/pt-BR/content/rest/gitignore.md,broken liquid tags
translations/pt-BR/content/rest/guides/building-a-ci-server.md,broken liquid tags
+translations/pt-BR/content/rest/guides/delivering-deployments.md,broken liquid tags
translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md,broken liquid tags
translations/pt-BR/content/rest/guides/traversing-with-pagination.md,rendering error
translations/pt-BR/content/rest/guides/working-with-comments.md,broken liquid tags
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 3b28d5dcd9..f60689bd6e 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: 'Você pode habilitar o {% data variables.product.prodname_actions %} no {% data variables.product.prodname_ghe_server %} e usar o armazenamento do Amazon S3 para armazenar dados gerados por execuções de fluxo de trabalho.'
+title: Enabling GitHub Actions with Amazon S3 storage
+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.'
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
versions:
ghes: '*'
@@ -13,34 +13,39 @@ topics:
redirect_from:
- /admin/github-actions/enabling-github-actions-with-amazon-s3-storage
shortTitle: Amazon S3 storage
-ms.openlocfilehash: 405a728eddcc751de8acd49af82783502f70b396
-ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 10/25/2022
-ms.locfileid: '148107984'
---
-## Pré-requisitos
+## Prerequisites
-{% data reusables.actions.enterprise-s3-support-warning %}
+{% note %}
-Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos:
+**Note:** The only {% data variables.product.prodname_dotcom %}-supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS.
-* 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-s3-tech-partners %}
+
+{% endnote %}
+
+Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
+
+* Create your Amazon S3 bucket for storing data generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
{% data reusables.actions.enterprise-common-prereqs %}
-## Habilitar {% data variables.product.prodname_actions %} com armazenamento do Amazon S3
+## Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage
-{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
-1. Em "Armazenamento de Logs e Artefatos", selecione **Amazon S3** e insira os detalhes do bucket de armazenamento:
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.actions %}
+{% data reusables.actions.enterprise-enable-checkbox %}
+1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
- * **URL de Serviço da AWS**: a URL de serviço do bucket. Por exemplo, se o bucket S3 foi criado na região `us-west-2`, esse valor deve ser `https://s3.us-west-2.amazonaws.com`.
+ * **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`.
- Para obter mais informações, confira "[Pontos de extremidade de serviço da AWS](https://docs.aws.amazon.com/general/latest/gr/rande.html)" na documentação da AWS.
- * **Bucket da AWS S3**: o nome do bucket S3.
- * **Chave de Acesso da AWS S3** e **Chave Secreta da AWS S3**: a ID da chave de acesso da AWS e a chave secreta do bucket. Para obter mais informações sobre como gerenciar chaves de acesso da AWS, confira a "[Documentação de gerenciamento de identidades e acesso da AWS](https://docs.aws.amazon.com/iam/index.html)".
+ For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation.
+ * **AWS S3 Bucket**: The name of your S3 bucket.
+ * **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)."
-  {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
+ 
+{% data reusables.enterprise_management_console.test-storage-button %}
+{% data reusables.enterprise_management_console.save-settings %}
{% data reusables.actions.enterprise-postinstall-nextsteps %}
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 fd0656617f..b4868411b1 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
@@ -135,7 +135,9 @@ To enable {% data variables.product.prodname_actions %} on {% data variables.pro
{% note %}
-**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers.
+**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with.
+
+{% data reusables.actions.enterprise-s3-tech-partners %}
{% endnote %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index aef08b7c8f..a7b2138769 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -1,7 +1,7 @@
---
-title: Configuração do fluxo de trabalho do CodeQL para linguagens compiladas
+title: Configuring the CodeQL workflow for compiled languages
shortTitle: Configure compiled languages
-intro: 'Você pode configurar como o {% data variables.product.prodname_dotcom %} usa o {% data variables.product.prodname_codeql_workflow %} para varrer o código escrito em linguagens compiladas para obter vulnerabilidades e erros.'
+intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.product.prodname_codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
product: '{% data reusables.gated-features.code-scanning %}'
permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.'
redirect_from:
@@ -25,102 +25,107 @@ topics:
- C/C++
- C#
- Java
-ms.openlocfilehash: 3be843fdc441e925569208defdd8412851609cef
-ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 10/27/2022
-ms.locfileid: '148111534'
---
-{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
-## Sobre o {% data variables.product.prodname_codeql_workflow %} e linguagens compiladas
-Você configurou {% data variables.product.prodname_dotcom %} para executar {% data variables.product.prodname_code_scanning %} para o seu repositório, adicionando um fluxo de trabalho de {% data variables.product.prodname_actions %} ao repositório. Para {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, você adiciona o {% data variables.product.prodname_codeql_workflow %}. Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
-{% data reusables.code-scanning.edit-workflow %} Para obter informações gerais sobre como configurar a {% data variables.product.prodname_code_scanning %} e editar arquivos de fluxo de trabalho, confira "[Como configurar a {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" e "[Aprenda a usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
+## About the {% data variables.product.prodname_codeql_workflow %} and compiled languages
-## Sobre a autobuild para {% data variables.product.prodname_codeql %}
+You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
-A {% data variables.product.prodname_code_scanning_capc %} funciona executando consultas em um ou mais bancos de dados. Cada banco de dados contém uma representação de todo o código em uma linguagem única no seu repositório.
-Para as linguagens compiladas C/C++, C#,{% ifversion codeql-go-autobuild %} Go{% endif %} e Java, o processo de população desse banco de dados envolve a construção do código e a extração de dados. {% data reusables.code-scanning.analyze-go %}
+{% data reusables.code-scanning.edit-workflow %}
+For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+
+## About autobuild for {% data variables.product.prodname_codeql %}
+
+{% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository.
+For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
{% data reusables.code-scanning.autobuild-compiled-languages %}
-Se o fluxo de trabalho usar uma matriz `language`, `autobuild` tentará criar cada uma das linguagens compiladas listadas na matriz. Sem uma matriz, `autobuild` tentará criar a linguagem compilada compatível que tem mais arquivos de origem no repositório. Com exceção de Go, a análise de outras linguagens compatíveis no repositório irá falhar, a menos que você forneça comandos de criação explícitos.
+If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands.
{% note %}
-{% ifversion ghae %} **Observação**: {% data reusables.actions.self-hosted-runners-software %} {% else %} **Observação**: caso você use executores auto-hospedados para o {% data variables.product.prodname_actions %}, talvez seja necessário instalar um software adicional para usar o processo `autobuild`. Além disso, se seu repositório precisar de uma versão específica de uma ferramenta de criação, talvez seja necessário instalá-lo manualmente. Para obter mais informações, confira "[Especificações para os executores hospedados no {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% ifversion ghae %}
+**Note**: {% data reusables.actions.self-hosted-runners-software %}
+{% else %}
+**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
{% endif %}
{% endnote %}
### C/C++
-| Tipo de sistema compatível | Nome do sistema |
+| Supported system type | System name |
|----|----|
-| Sistema operacional | Windows, macOS e Linux |
-| Sistema de criação | Windows: MSbuild e scripts de build
Linux e macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild e scripts de build |
+| Operating system | Windows, macOS, and Linux |
+| Build system | Windows: MSbuild and build scripts
Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts |
-O comportamento da etapa `autobuild` varia de acordo com o sistema operacional em que a extração é executada. No Windows, a etapa `autobuild` tenta fazer a detecção automática de um método de build adequado para C/C++ usando a seguinte abordagem:
+The behavior of the `autobuild` step varies according to the operating system that the extraction runs on. On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach:
-1. Invocar `MSBuild.exe` no arquivo de solução (`.sln`) ou de projeto (`.vcxproj`) mais próximo da raiz.
-Se `autobuild` detectar vários arquivos de solução ou de projeto na mesma profundidade (mais curta) do diretório de nível superior, ele tentará compilar todos eles.
-2. Invocar um script parecido com um script de build: _build.bat_, _build.cmd_ e _build.exe_ (nessa ordem).
+1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root.
+If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
+2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order).
-No Linux e no macOS, a etapa `autobuild` revisa os arquivos presentes no repositório para determinar o sistema de build usado:
+On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
-1. Procure um sistema de criação no diretório-raiz.
-2. Se nenhum for encontrado, procure um diretório único nos subdiretórios com um sistema de criação para C/C++.
-3. Execute um comando apropriado para configurar o sistema.
+1. Look for a build system in the root directory.
+2. If none are found, search subdirectories for a unique directory with a build system for C/C++.
+3. Run an appropriate command to configure the system.
### C#
-| Tipo de sistema compatível | Nome do sistema |
+| Supported system type | System name |
|----|----|
-| Sistema operacional | Windows e Linux |
-| Sistema de criação | .NET, MSbuild e scripts de criação |
+| Operating system | Windows and Linux |
+| Build system | .NET and MSbuild, as well as build scripts |
-O processo `autobuild` tenta fazer a detecção automática de um método de build adequado para C# usando a seguinte abordagem:
+The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
-1. Invocar `dotnet build` no arquivo de solução (`.sln`) ou de projeto (`.csproj`) mais próximo da raiz.
-2. Invocar `MSbuild` (Linux) ou `MSBuild.exe` (Windows) no arquivo de solução ou de projeto mais próximo da raiz.
-Se `autobuild` detectar vários arquivos de solução ou de projeto na mesma profundidade (mais curta) do diretório de nível superior, ele tentará compilar todos eles.
-3. Invocar um script parecido com um script de build: _build_ e _build.sh_ (nessa ordem, para o Linux) ou _build.bat_, _build.cmd_ e _build.exe_ (nessa ordem, para o Windows).
+1. Invoke `dotnet build` on the solution (`.sln`) or project (`.csproj`) file closest to the root.
+2. Invoke `MSbuild` (Linux) or `MSBuild.exe` (Windows) on the solution or project file closest to the root.
+If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
+3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
+
+{% ifversion codeql-go-autobuild %}
### Go
-| Tipo de sistema compatível | Nome do sistema |
+| Supported system type | System name |
|----|----|
-| Sistema operacional | Windows, macOS e Linux |
-| Sistema de criação | Módulos Go, `dep` e Glide, bem como scripts de build, incluindo Makefiles e scripts Ninja |
+| Operating system | Windows, macOS, and Linux |
+| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts |
-O processo `autobuild` tenta fazer a detecção automática de uma forma adequada para instalar as dependências necessárias em um repositório Go antes de extrair todos os arquivos `.go`:
+The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files:
-1. Invoque `make`, `ninja`, `./build` ou `./build.sh` (nessa ordem) até que um desses comandos seja bem-sucedido e um próximo `go list ./...` também seja bem-sucedido, indicando que as dependências necessárias foram instaladas.
-2. Se nenhum desses comandos for bem-sucedido, procure `go.mod`, `Gopkg.toml` ou `glide.yaml` e execute `go get` (a menos que a cópia para a pasta Vendor esteja em uso), `dep ensure -v` ou `glide install`, respectivamente, para tentar instalar as dependências.
-3. Por fim, se os arquivos de configurações desses gerenciadores de dependência não forem encontrados, reorganize a estrutura de diretório do repositório adequada para adição a `GOPATH` e use `go get` para instalar as dependências. A estrutura de diretório é revertida para normal após a conclusão da extração.
-4. Extraia todo o código Go no repositório, semelhante à execução de `go build ./...`.
+1. Invoke `make`, `ninja`, `./build` or `./build.sh` (in that order) until one of these commands succeeds and a subsequent `go list ./...` also succeeds, indicating that the needed dependencies have been installed.
+2. If none of those commands succeeded, look for `go.mod`, `Gopkg.toml` or `glide.yaml`, and run `go get` (unless vendoring is in use), `dep ensure -v` or `glide install` respectively to try to install dependencies.
+3. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes.
+4. Extract all Go code in the repository, similar to running `go build ./...`.
+
+{% endif %}
### Java
-| Tipo de sistema compatível | Nome do sistema |
+| Supported system type | System name |
|----|----|
-| Sistema operacional | Windows, macOS e Linux (sem restrição) |
-| Sistema de criação | Gradle, Maven e Ant |
+| Operating system | Windows, macOS, and Linux (no restriction) |
+| Build system | Gradle, Maven and Ant |
-O processo `autobuild` tenta determinar o sistema de build para bases de código Java aplicando esta estratégia:
+The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
-1. Procurar um arquivo de criação no diretório-raiz. Verifique o arquivos do Gradle, do Maven e, em seguida, do Ant.
-2. Execute o primeiro arquivo de criação encontrado. Se os arquivos do Gradle e do Maven estiverem presentes, será usado o arquivo do Gradle.
-3. Caso contrário, procure arquivos de criação nos subdiretórios diretos do diretório-raiz. Se apenas um subdiretório contiver arquivos de criação, execute o primeiro arquivo identificado nesse subdiretório (usando a mesma preferência de 1). Se mais de um subdiretório conter arquivos de criação, relate um erro.
+1. Search for a build file in the root directory. Check for Gradle then Maven then Ant build files.
+2. Run the first build file found. If both Gradle and Maven files are present, the Gradle file is used.
+3. Otherwise, search for build files in direct subdirectories of the root directory. If only one subdirectory contains build files, run the first file identified in that subdirectory (using the same preference as for 1). If more than one subdirectory contains build files, report an error.
-## Adicionar passos de criação a uma linguagem compilada
+## Adding build steps for a compiled language
-{% data reusables.code-scanning.autobuild-add-build-steps %} Para obter informações sobre como editar o arquivo de fluxo de trabalho, confira "[Como configurar a {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)".
+{% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
-Depois de remover a etapa `autobuild`, remova o comentário da etapa `run` e adicione comandos de build adequados ao seu repositório. A etapa `run` do fluxo de trabalho executa programas de linha de comando usando o shell do sistema operacional. Você pode modificar esses comandos e adicionar mais comandos para personalizar o processo de compilação.
+After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process.
``` yaml
- run: |
@@ -128,9 +133,9 @@ Depois de remover a etapa `autobuild`, remova o comentário da etapa `run` e adi
make release
```
-Para obter mais informações sobre a palavra-chave `run`, confira "[Sintaxe de fluxo de trabalho do {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)".
+For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
-Se o repositório contiver várias linguagens compiladas, você poderá especificar comandos de compilação específicos da linguagem. Por exemplo, se o repositório contiver C/C++, C# e Java e `autobuild` compilar corretamente C/C++ e C#, mas não compila Java, você poderá usar a configuração a seguir no seu fluxo de trabalho, após a etapa `init`. Isso especifica as etapas de compilação para Java enquanto ainda usa `autobuild` para C/C++ e C#:
+If your repository contains multiple compiled languages, you can specify language-specific build commands. For example, if your repository contains C/C++, C# and Java, and `autobuild` correctly builds C/C++ and C# but fails to build Java, you could use the following configuration in your workflow, after the `init` step. This specifies build steps for Java while still using `autobuild` for C/C++ and C#:
```yaml
- if: matrix.language == 'cpp' || matrix.language == 'csharp'
@@ -144,8 +149,8 @@ Se o repositório contiver várias linguagens compiladas, você poderá especifi
make release
```
-Para obter mais informações sobre o condicional `if`, confira "[Sintaxe de fluxo de trabalho do GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)".
+For more information about the `if` conditional, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)."
-Para obter mais dicas e truques sobre por que o `autobuild` não compilará seu código, confira "[Solução de problemas de fluxo de trabalho do {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)".
+For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
-Se você adicionou etapas de criação manual para linguagens compiladas, mas o {% data variables.product.prodname_code_scanning %} ainda não está funcionando no seu repositório, entre em contato com {% data variables.contact.contact_support %}.
+If you added manual build steps for compiled languages and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}.
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
index 91f2e8d064..fe75305ec3 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
+++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
@@ -47,7 +47,8 @@ You can configure notification settings for yourself or your organization from t
{% data reusables.notifications.vulnerable-dependency-notification-options %}
{% ifversion update-notification-settings-22 %}
-{% else %}
+{% endif %}{% ifversion ghes > 3.7 or ghae > 3.7 %}
+{% endif %}{% ifversion ghes < 3.8 or ghae < 3.8 %}
{% endif %}
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
index 31a25942fb..92f2d38704 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
@@ -1,8 +1,8 @@
---
-title: Variáveis de ambiente padrão para seu codespace
+title: Default environment variables for your codespace
shortTitle: Default environment variables
product: '{% data reusables.gated-features.codespaces %}'
-intro: 'O {% data variables.product.prodname_dotcom %} define variáveis de ambiente padrão para cada codespace.'
+intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each codespace.'
versions:
fpt: '*'
ghec: '*'
@@ -11,34 +11,30 @@ topics:
- Codespaces
- Fundamentals
- Developer
-ms.openlocfilehash: bcff0f06aad7eb930b47f4b9cb32e42c067d07cf
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147614340'
---
-## Sobre as variáveis de ambiente padrão
-O {% data variables.product.prodname_dotcom %} define variáveis de ambiente padrão para cada codespace. Os comandos executados nos codespaces podem criar, ler e modificar as variáveis de ambiente.
+## About default environment variables
+
+{% data variables.product.prodname_dotcom %} sets default environment variables for every codespace. Commands run in codespaces can create, read, and modify environment variables.
{% note %}
-**Observação**: as variáveis de ambiente diferenciam maiúsculas de minúsculas.
+**Note**: Environment variables are case-sensitive.
{% endnote %}
-## Lista de variáveis de ambiente padrão
+## List of default environment variables
-| Variável de ambiente | Descrição |
+| Environment variable | Description |
| ---------------------|------------ |
-| `CODESPACE_NAME` | O nome do codespace Por exemplo, `monalisa-github-hello-world-2f2fsdf2e` |
-| `CODESPACES` | Sempre `true` em um codespace |
-| `GIT_COMMITTER_EMAIL` | O email para o campo "autor" de commits `git` futuros. |
-| `GIT_COMMITTER_NAME` | O nome do campo "autor do commit" de commits `git` futuros. |
-| `GITHUB_API_URL` | Retorna a URL da API. Por exemplo, `{% data variables.product.api_url_code %}`. |
-| `GITHUB_GRAPHQL_URL` | Retorna a URL API do GraphQL. Por exemplo, `{% data variables.product.graphql_url_code %}`. |
-| `GITHUB_REPOSITORY` | Nome do repositório e o proprietário. Por exemplo, `octocat/Hello-World`. |
-| `GITHUB_SERVER_URL`| Retorna a URL do servidor {% data variables.product.product_name %}. Por exemplo, `https://{% data variables.product.product_url %}`. |
-| `GITHUB_TOKEN` | Um token de autenticação assinado que representa o usuário no codespace. Você pode usar isso para fazer chamadas autenticadas para a API do GitHub. Para obter mais informações, confira "[Autenticação](/codespaces/codespaces-reference/security-in-codespaces#authentication)". |
-| `GITHUB_USER` | O nome do usuário que iniciou o codespace. Por exemplo, `octocat`. |
+| `CODESPACE_NAME` | The name of the codespace For example, `monalisa-github-hello-world-2f2fsdf2e` |
+| `CODESPACES` | Always `true` while in a codespace |
+| `GIT_COMMITTER_EMAIL` | The email for the "author" field of future `git` commits. |
+| `GIT_COMMITTER_NAME` | The name for the "committer" field of future `git` commits. |
+| `GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN`| Returns the domain of the {% data variables.product.prodname_github_codespaces %} forwarded port. For example, `preview.app.github.dev`. |
+| `GITHUB_API_URL` | Returns the API URL. For example, `{% data variables.product.api_url_code %}`. |
+| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example, `{% data variables.product.graphql_url_code %}`. |
+| `GITHUB_REPOSITORY` | The owner and repository name. For example, `octocat/Hello-World`. |
+| `GITHUB_SERVER_URL`| Returns the URL of the {% data variables.product.product_name %} server. For example, `https://{% data variables.product.product_url %}`. |
+| `GITHUB_TOKEN` | A signed auth token representing the user in the codespace. You can use this to make authenticated calls to the GitHub API. For more information, see "[Authentication](/codespaces/codespaces-reference/security-in-codespaces#authentication)." |
+| `GITHUB_USER` | The name of the user that initiated the codespace. For example, `octocat`. |
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
index c5cea6210c..e1530b56ef 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -23,6 +23,8 @@ When an application running inside a codespace prints output to the terminal tha
+{% data reusables.codespaces.forwarded-ports-environment-variable %}
+
You can also forward a port manually, label forwarded ports, share forwarded ports with members of your organization, share forwarded ports publicly, and add forwarded ports to the codespace configuration.
{% note %}
@@ -48,7 +50,7 @@ You can manually forward a port that wasn't forwarded automatically.
## Using HTTPS forwarding
-By default, {% data variables.product.prodname_github_codespaces %} forwards ports using HTTP but you can update any port to use HTTPS, as needed.
+By default, {% data variables.product.prodname_github_codespaces %} forwards ports using HTTP but you can update any port to use HTTPS, as needed. If you update a port with public visibility to use HTTPS, the port's visibility will automatically change to private.
{% data reusables.codespaces.navigate-to-ports-tab %}
1. Right click the port you want to update, then hover over **Change Port Protocol**.
diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md
index c612034994..882d706aba 100644
--- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md
+++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md
@@ -1,6 +1,6 @@
---
-title: Solução de problemas de encaminhamento de porta para o GitHub Codespaces
-intro: Etapas de solução de problemas para problemas comuns de encaminhamento de portas.
+title: Troubleshooting port forwarding for GitHub Codespaces
+intro: Troubleshooting steps for common port forwarding issues.
product: '{% data reusables.gated-features.codespaces %}'
versions:
fpt: '*'
@@ -11,20 +11,17 @@ topics:
shortTitle: Port forwarding
redirect_from:
- /codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces
-ms.openlocfilehash: 326c96e86883604ecc1f4ebcb81be98dae23bf84
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147111417'
---
-Quando um aplicativo em execução em um codespace tiver saída gerada em uma porta para o console, o {% data variables.product.prodname_github_codespaces %} detectará o padrão da URL do localhost e encaminhará a porta automaticamente. Para obter mais informações, confira "[Como encaminhar portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)".
-Se uma porta não for redirecionada automaticamente, você poderá redirecioná-la manualmente. Para obter mais informações, confira "[Como encaminhar uma porta](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)".
+When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_github_codespaces %} detects the localhost URL pattern and automatically forwards the port. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-Se o encaminhamento de porta estiver configurado, verifique o seguinte:
+If a port is not automatically forwarded, you can forward it manually. For more information, see "[Forwarding a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)."
-- Use o alerta de notificação ou clique no URL no Terminal para abrir a porta encaminhada. Se você digitar `localhost:8000` (por exemplo) no computador local, isso não funcionará se você estiver conectado ao codespace por meio do navegador.
-- Certifique-se de verificar se seu aplicativo ainda está sendo executado dentro do seu codespace. Se seu codespace parou após um período de inatividade, você deverá certificar-se de reiniciar o seu aplicativo depois que o codespace for reiniciado.
+If port forwarding is set up, check the following:
-Normalmente, você pode tornar uma porta encaminhada acessível publicamente ou dentro da organização que é o proprietário de um repositório. Para obter mais informações, confira "[Como encaminhar portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". Se uma ou ambas as opções de visibilidade pública ou da organização não estiverem disponíveis, isso indicará que uma política no nível da organização foi configurada. Para obter mais informações, confira "[Como restringir a visibilidade das portas encaminhadas](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)".
+- Use the notification toast or click the URL in Terminal to open the forwarded port. Typing in `localhost:8000` (as an example) to your local machine will not work if you're connected to the codespace via the browser.
+- Make sure to check that your application is still running from within your codespace. If your codespace has stopped after a period of inactivity, you'll need to ensure to restart your application once the codespace has restarted.
+
+Typically, you can make a forwarded port accessible publicly, or within the organization that owns a repository. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." If either, or both, of the options for public or organization visibility are not available, this indicates that an organization-level policy has been configured. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
+
+{% data reusables.codespaces.forwarded-ports-environment-variable %}
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/creating-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
index 42a224ad27..db196327e8 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
@@ -1,6 +1,6 @@
---
-title: Criar webhooks
-intro: 'Aprenda a criar um webhook, escolhendo os eventos que seu webhook irá ouvir em {% data variables.product.prodname_dotcom %} e como configurar um servidor para receber e gerenciar a carga de webhook.'
+title: Creating webhooks
+intro: 'Learn to build a webhook, choosing the events your webhook will listen for on {% data variables.product.prodname_dotcom %} and how to set up a server to receive and manage the webhook payload.'
redirect_from:
- /webhooks/creating
- /developers/webhooks-and-events/creating-webhooks
@@ -11,79 +11,85 @@ versions:
ghec: '*'
topics:
- Webhooks
-ms.openlocfilehash: f07c5de7acd3c5be5236765236d24a6938e3b91f
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145093890'
---
-Agora que entendemos os [conceitos básicos dos webhooks][webhooks-overview], vamos ver o processo de criação da nossa integração habilitada para webhook. Neste tutorial, vamos criar um webhook de repositório que será responsável por listar quão popular é o nosso repositório, com base no número de problemas que recebe por dia.
+Now that we understand [the basics of webhooks][webhooks-overview], let's go through the process of building out our own webhook-powered integration. In this tutorial, we'll create a repository webhook that will be responsible for listing out how popular our repository is, based on the number of issues it receives per day.
-Criar um webhook é um processo de duas etapas. Primeiro, você deverá configurar como deseja que seu webhook se comporte através do {% data variables.product.product_name %}: quais eventos devem ser ouvidos. Em seguida, você irá configurar seu servidor para receber e gerenciar a carga.
+Creating a webhook is a two-step process. You'll first need to set up what events you webhook should listen to. After that, you'll set up your server to receive and manage the payload.
{% data reusables.webhooks.webhooks-rest-api-links %}
-## Expor o host local na internet
+## Exposing localhost to the internet
-Para fins deste tutorial, vamos usar um servidor local para receber mensagens de {% data variables.product.prodname_dotcom %}. Portanto, em primeiro lugar, temos de expor o nosso ambiente de desenvolvimento local à internet. Nós usaremos ngrok para fazer isso. Ngrok está disponível, gratuitamente, para todos os principais sistemas operacionais. Para obter mais informações, confira a [página de download do `ngrok`](https://ngrok.com/download).
+For the purposes of this tutorial, we're going to use a local server to receive webhook events from {% data variables.product.prodname_dotcom %}.
-Depois de instalar `ngrok`, você poderá expor o localhost executando `./ngrok http 4567` na linha de comando. 4567 é o número da porta em que o nosso servidor ouvirá mensagens. Você deve ver uma linha parecida mais ou menos com isso:
+First of all, we need to expose our local development environment to the internet so {% data variables.product.prodname_dotcom %} can deliver events. We'll use [`ngrok`](https://ngrok.com) to do this.
+
+{% ifversion cli-webhook-forwarding %}
+{% note %}
+
+**Note:** Alternatively, you can use webhook forwarding to set up your local environment to receive webhooks. For more information, see "[Receiving webhooks with the GitHub CLI](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli)."
+
+{% endnote %}
+{% endif %}
+
+`ngrok` is available, free of charge, for all major operating systems. For more information, see [the `ngrok` download page](https://ngrok.com/download).
+
+After installing `ngrok`, you can expose your localhost by running `./ngrok http 4567` on the command line. `4567` is the port number on which our server will listen for messages. You should see a line that looks something like this:
```shell
-$ Forwarding http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567
+$ Forwarding http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567
```
-Anote a URL do `*.ngrok.io`. Vamos usá-lo para configurar nosso webhook.
+Make a note of the `*.ngrok.io` URL. We'll use it to set up our webhook.
-## Configurando um webhook
+## Setting up a webhook
-É possível instalar webhooks em uma organização ou em um repositório específico.
+You can install webhooks on an organization or on a specific repository.
-Para configurar um webhook, vá para a página de configurações do seu repositório ou organização. Nela, clique em **Webhooks** e em **Adicionar webhook**.
+To set up a webhook, go to the settings page of your repository or organization. From there, click **Webhooks**, then **Add webhook**.
-Como alternativa, você pode optar por criar e gerenciar um webhook [por meio da API de Webhooks][webhook-api].
+Alternatively, you can choose to build and manage a webhook [through the Webhooks API][webhook-api].
-Os webhooks exigem algumas opções de configuração antes de você poder usá-los. Iremos analisar cada uma destas configurações abaixo.
+Webhooks require a few configuration options before you can make use of them. We'll go through each of these settings below.
-## URL do conteúdo
+## Payload URL
{% data reusables.webhooks.payload_url %}
-Como estamos fazendo o desenvolvimento local para nosso tutorial, vamos defini-la como a URL `*.ngrok.io`, seguido de `/payload`. Por exemplo, `http://7e9ea9dc.ngrok.io/payload`.
+Since we're developing locally for our tutorial, we'll set it to the `*.ngrok.io` URL, followed by `/payload`. For example, `http://7e9ea9dc.ngrok.io/payload`.
-## Tipo de conteúdo
+## Content type
-{% data reusables.webhooks.content_type %} Para este tutorial, o tipo de conteúdo padrão `application/json` é adequado.
+{% data reusables.webhooks.content_type %} For this tutorial, the default content type of `application/json` is fine.
-## Segredo
+## Secret
{% data reusables.webhooks.secret %}
-## Verificação SSL
+## SSL verification
{% data reusables.webhooks.webhooks_ssl %}
-## Ativo
+## Active
-Por padrão, as entregas de webhook estão "Ativas". Você pode optar por desativar a entrega das cargas de webhook, desmarcando "Ativo".
+By default, webhook deliveries are "Active." You can choose to disable the delivery of webhook payloads by deselecting "Active."
-## Eventos
+## Events
-Os eventos encontram-se no núcleo dos webhooks. Esses webhooks são acionados sempre que uma determinada ação é tomada no repositório, a qual a URL da carga do seu servidor intercepta e e sobre a qual atua.
+Events are at the core of webhooks. These webhooks fire whenever a certain action is taken on the repository, which your server's payload URL intercepts and acts upon.
-Encontre uma lista completa de eventos de webhook e quando eles podem ser executados na referência da [API de webhooks][hooks-api].
+A full list of webhook events, and when they execute, can be found in [the webhooks API][hooks-api] reference.
-Como o webhook está lidando com problemas em um repositório, clicaremos em **Deixar-me selecionar eventos individuais** e em **Problemas**. Verifique se você selecionou **Ativo** para receber eventos de problema para webhooks disparados. Você também pode selecionar todos os eventos usando a opção-padrão.
+Since our webhook is dealing with issues in a repository, we'll click **Let me select individual events** and then **Issues**. Make sure you select **Active** to receive issue events for triggered webhooks. You can also select all events using the default option.
-Quando terminar, clique em **Adicionar webhook**.
+When you're finished, click **Add webhook**.
-Agora que você criou o webhook, é hora de configurar nosso servidor local para testar o webhook. Acesse [Como configurar o servidor](/webhooks/configuring/) para saber como fazer isso.
+Now that you've created the webhook, it's time to set up our local server to test the webhook. Head on over to [Configuring Your Server](/webhooks/configuring/) to learn how to do that.
-### Evento curinga
+### Wildcard event
-Para configurar um webhook para todos os eventos, use o caractere curinga (`*`) para especificar os eventos de webhook. Ao adicionar o evento curinga, substituiremos todos os eventos existentes que você tenha configurado pelo evento curinga e enviaremos todas as cargas para os eventos compatíveis. Você também obterá automaticamente todos os novos eventos que possamos adicionar no futuro.
+To configure a webhook for all events, use the wildcard (`*`) character to specify the webhook events. When you add the wildcard event, we'll replace any existing events you have configured with the wildcard event and send you payloads for all supported events. You'll also automatically get any new events we might add in the future.
[webhooks-overview]: /webhooks/
[webhook-api]: /rest/reference/repos#hooks
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/index.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/index.md
index 3adcdcc86f..4adaff922a 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/index.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/index.md
@@ -14,12 +14,13 @@ children:
- /configuring-your-server-to-receive-payloads
- /testing-webhooks
- /securing-your-webhooks
+ - /receiving-webhooks-with-the-github-cli
- /webhook-events-and-payloads
-ms.openlocfilehash: a483c6d35ee1b7fee5e7dec948abdc5c65cc2400
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: a73820b100e94caa7c5eabe2f01a4814fe0df2a3
+ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
ms.translationtype: HT
ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145093888'
+ms.lasthandoff: 11/04/2022
+ms.locfileid: '148132952'
---
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
index 4b24db3264..8a787770e7 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -62,7 +62,7 @@ Problemas e pull requests possuem um conjunto de filtros padrão que podem ser a
- Todos os problemas e pull requests abertos
- Problemas e pull requests criados
- Problemas e pull requests atribuídos a você
-- Problemas e solicitações de pull em que você é [ **@mentioned** ](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+- Problemas e solicitações de pull em que você é [ **@mentioned**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
{% data reusables.cli.filter-issues-and-pull-requests-tip %}
@@ -163,7 +163,7 @@ gh pr list --search "team:octo-org/octo-team"
Com os termos da pesquisa de problemas e pull requests, é possível:
- Filtrar problemas e solicitações de pull por autor: `state:open type:issue author:octocat`
-- Filtrar problemas e solicitações de pull que envolvem, mas não necessariamente [ **@mention** ](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), determinadas pessoas: `state:open type:issue involves:octocat`
+- Filtrar problemas e solicitações de pull que envolvem, mas não necessariamente [ **@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), determinadas pessoas: `state:open type:issue involves:octocat`
- Filtrar problemas e solicitações de pull por destinatário: `state:open type:issue assignee:octocat`
- Filtrar problemas e solicitações de pull por rótulo: `state:open type:issue label:"bug"`
- Filtrar os termos de pesquisa usando `-` antes do termo: `state:open type:issue -author:octocat`
diff --git a/translations/pt-BR/content/rest/guides/building-a-ci-server.md b/translations/pt-BR/content/rest/guides/building-a-ci-server.md
index afe94b461f..2bb9ae3ff5 100644
--- a/translations/pt-BR/content/rest/guides/building-a-ci-server.md
+++ b/translations/pt-BR/content/rest/guides/building-a-ci-server.md
@@ -29,9 +29,17 @@ Our CI system and host server will be figments of our imagination. They could be
Travis, Jenkins, or something else entirely. The crux of this guide will be setting up
and configuring the server managing the communication.
-If you haven't already, be sure to [download ngrok][ngrok], and learn how
+If you haven't already, [download `ngrok`][ngrok], and learn how
to [use it][using ngrok]. We find it to be a very useful tool for exposing local
-connections.
+applications to the internet.
+
+{% ifversion cli-webhook-forwarding %}
+{% note %}
+
+**Note:** Alternatively, you can use webhook forwarding to set up your local environment to receive webhooks. For more information, see "[Receiving webhooks with the GitHub CLI](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli)."
+
+{% endnote %}
+{% endif %}
Note: you can download the complete source code for this project
[from the platform-samples repo][platform samples].
@@ -54,14 +62,14 @@ end
(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
Start this server up. By default, Sinatra starts on port `4567`, so you'll want
-to configure ngrok to start listening for that, too.
+to configure `ngrok` to start listening for that, too.
In order for this server to work, we'll need to set a repository up with a webhook.
The webhook should be configured to fire whenever a Pull Request is created, or merged.
Go ahead and create a repository you're comfortable playing around in. Might we
suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
After that, you'll create a new webhook in your repository, feeding it the URL
-that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the
+that `ngrok` gave you, and choosing `application/x-www-form-urlencoded` as the
content type:
diff --git a/translations/pt-BR/content/rest/guides/delivering-deployments.md b/translations/pt-BR/content/rest/guides/delivering-deployments.md
index 07192c4003..48dab8b880 100644
--- a/translations/pt-BR/content/rest/guides/delivering-deployments.md
+++ b/translations/pt-BR/content/rest/guides/delivering-deployments.md
@@ -1,6 +1,6 @@
---
-title: Entregar implantações
-intro: 'Ao usar a API RESt de implantações, você pode criar ferramentas personalizadas que interagem com seu servidor e um aplicativo de terceiros.'
+title: Delivering deployments
+intro: 'Using the Deployments REST API, you can build custom tooling that interacts with your server and a third-party app.'
redirect_from:
- /guides/delivering-deployments
- /guides/automating-deployments-to-integrators
@@ -12,32 +12,45 @@ versions:
ghec: '*'
topics:
- API
-ms.openlocfilehash: 60ef610d4134eaddee3f40c5d50d72e463fedd27
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145126775'
---
-A [API de Implantações][deploy API] fornece aos seus projetos hospedados no {% data variables.product.product_name %} a capacidade de iniciá-los em um servidor do qual você é o proprietário. Quando ela é combinada com [a API de Status][status API], você pode coordenar suas implantações no momento em que o código chega ao branch padrão.
+
+
-Este guia usará a API para demonstrar uma configuração que você pode usar.
-No nosso cenário, iremos:
+The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with
+the capability to launch them on a server that you own. Combined with
+[the Status API][status API], you'll be able to coordinate your deployments
+the moment your code lands on the default branch.
-* Fazer merge de um pull request.
-* Quando a CI terminar, definiremos o status do pull request.
-* Quando o pull request for mesclado, executaremos a nossa implantação no nosso servidor.
+This guide will use that API to demonstrate a setup that you can use.
+In our scenario, we will:
-O nosso sistema de CI e servidor de hospedagem serão imaginários. Eles podem ser o Heroku, o Amazon ou qualquer outro completamente diferente. O aspecto fundamental deste guia será configurar o servidor que gerencia a comunicação.
+* Merge a pull request.
+* When the CI is finished, we'll set the pull request's status accordingly.
+* When the pull request is merged, we'll run our deployment to our server.
-Caso ainda não tenha feito isso, [baixe o ngrok][ngrok] e saiba como [usá-lo][using ngrok]. Achamos que ele é uma ferramenta muito útil para expor conexões locais.
+Our CI system and host server will be figments of our imagination. They could be
+Heroku, Amazon, or something else entirely. The crux of this guide will be setting up
+and configuring the server managing the communication.
-Observação: baixe o código-fonte completo deste projeto [no repositório platform-samples][platform samples].
+If you haven't already, be sure to [download `ngrok`][ngrok], and learn how
+to [use it][using ngrok]. We find it to be a very useful tool for exposing local
+applications to the internet.
-## Escrever o seu servidor
+{% ifversion cli-webhook-forwarding %}
+{% note %}
-Vamos escrever um aplicativo rápido do Sinatra para provar que nossas conexões locais estão funcionando.
-Vamos começar com isso:
+**Note:** Alternatively, you can use webhook forwarding to set up your local environment to receive webhooks. For more information, see "[Receiving webhooks with the GitHub CLI](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli)."
+
+{% endnote %}
+{% endif %}
+
+Note: you can download the complete source code for this project
+[from the platform-samples repo][platform samples].
+
+## Writing your server
+
+We'll write a quick Sinatra app to prove that our local connections are working.
+Let's start with this:
``` ruby
require 'sinatra'
@@ -49,25 +62,31 @@ post '/event_handler' do
end
```
-(Se você não estiver familiarizado com o funcionamento do Sinatra, recomendamos [ler o guia do Sinatra][Sinatra]).
+(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
-Inicie este servidor. Por padrão, o Sinatra começará na porta `4567`, ou seja, o ideal será configurar o ngrok para começar a escutá-la também.
+Start this server up. By default, Sinatra starts on port `4567`, so you'll want
+to configure `ngrok` to start listening for that, too.
-Para que esse servidor funcione, precisamos configurar um repositório com um webhook.
-O webhook deve ser configurado para ser acionado sempre que um pull request for criado ou mesclado.
-Vá em frente e crie um repositório com o qual você esteja confortável para fazer testes. Podemos sugerir [o repositório do Spoon/do Knife de @octocat](https://github.com/octocat/Spoon-Knife)?
-Depois disso, você criará um webhook no seu repositório, alimentando-o com a URL fornecida pelo ngrok e escolhendo `application/x-www-form-urlencoded` como o tipo de conteúdo:
+In order for this server to work, we'll need to set a repository up with a webhook.
+The webhook should be configured to fire whenever a pull request is created, or merged.
+Go ahead and create a repository you're comfortable playing around in. Might we
+suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
+After that, you'll create a new webhook in your repository, feeding it the URL
+that `ngrok` gave you, and choosing `application/x-www-form-urlencoded` as the
+content type:
-
+
-Clique em **Atualizar webhook**. Você verá a resposta de corpo `Well, it worked!`.
-Ótimo! Clique em **Deixe-me selecionar eventos individuais** e selecione o seguinte:
+Click **Update webhook**. You should see a body response of `Well, it worked!`.
+Great! Click on **Let me select individual events.**, and select the following:
-* Implantação
-* Status da Implantação
+* Deployment
+* Deployment status
* Pull Request
-Esses são os eventos que o {% data variables.product.product_name %} enviará ao nosso servidor sempre que ocorrer a ação relevante. Vamos configurar nosso servidor para *apenas* tratar as solicitações de pull quando elas forem mescladas agora:
+These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action
+occurs. We'll configure our server to *just* handle when pull requests are merged
+right now:
``` ruby
post '/event_handler' do
@@ -82,15 +101,20 @@ post '/event_handler' do
end
```
-O que está havendo? Cada evento que o {% data variables.product.product_name %} envia anexa um cabeçalho HTTP `X-GitHub-Event`. Por enquanto, nos importaremos apenas com os eventos do PR. Quando uma solicitação de pull for mesclada (o estado dela é `closed`, e `merged` é `true`), iniciaremos uma implantação.
+What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event`
+HTTP header. We'll only care about the PR events for now. When a pull request is
+merged (its state is `closed`, and `merged` is `true`), we'll kick off a deployment.
-Para testar esta prova de conceito, faça algumas alterações em um branch no repositório de teste, abra uma solicitação de pull e mescle-a. Seu servidor deve responder de acordo!
+To test out this proof-of-concept, make some changes in a branch in your test
+repository, open a pull request, and merge it. Your server should respond accordingly!
-## Trabalhando com implantações
+## Working with deployments
-Como o servidor implementado, o código sendo revisado e a solicitação de pull mesclada, queremos implantar nosso projeto.
+With our server in place, the code being reviewed, and our pull request
+merged, we want our project to be deployed.
-Vamos começar modificando o ouvinte de evento para processar as solicitações de pull quando elas forem mescladas e começar a prestar atenção às implantações:
+We'll start by modifying our event listener to process pull requests when they're
+merged, and start paying attention to deployments:
``` ruby
when "pull_request"
@@ -104,7 +128,8 @@ when "deployment_status"
end
```
-Com base nas informações da solicitação de pull, começaremos preenchendo o método `start_deployment`:
+Based on the information from the pull request, we'll start by filling out the
+`start_deployment` method:
``` ruby
def start_deployment(pull_request)
@@ -114,13 +139,19 @@ def start_deployment(pull_request)
end
```
-As implantações podem ter alguns metadados anexados na forma de um `payload` e uma `description`. Embora esses valores sejam opcionais, é útil usá-los para registrar em log e representar informações.
+Deployments can have some metadata attached to them, in the form of a `payload`
+and a `description`. Although these values are optional, it's helpful to use
+for logging and representing information.
-Quando uma nova implantação é criada, um evento completamente separado é acionado. É por isso que temos um novo caso `switch` no manipulador de eventos para `deployment`. Você pode usar essas informações para receber uma notificação de quando uma implantação é disparada.
+When a new deployment is created, a completely separate event is triggered. That's
+why we have a new `switch` case in the event handler for `deployment`. You can
+use this information to be notified when a deployment has been triggered.
-As implantações podem demorar um pouco. Portanto, vamos precisar ouvir vários eventos, como quando a implantação foi criada e em que estado se ela encontra.
+Deployments can take a rather long time, so we'll want to listen for various events,
+such as when the deployment was created, and what state it's in.
-Vamos simular uma implantação que realiza um trabalho e observar o efeito que ela tem na saída. Primeiro, vamos concluir o método `process_deployment`:
+Let's simulate a deployment that does some work, and notice the effect it has on
+the output. First, let's complete our `process_deployment` method:
``` ruby
def process_deployment
@@ -134,7 +165,7 @@ def process_deployment
end
```
-Por fim, vamos fazer a simulação do armazenamento da informação de status como a saída do console:
+Finally, we'll simulate storing the status information as console output:
``` ruby
def update_deployment_status
@@ -142,21 +173,27 @@ def update_deployment_status
end
```
-Vamos dividir o que está acontecendo. Uma nova implantação é criada por `start_deployment`, que dispara o evento `deployment`. Nele, chamamos `process_deployment` para simular o trabalho que está sendo feito. Durante esse processamento, também fazemos uma chamada a `create_deployment_status`, que permite que um destinatário saiba o que está acontecendo, à medida que alternamos o status para `pending`.
+Let's break down what's going on. A new deployment is created by `start_deployment`,
+which triggers the `deployment` event. From there, we call `process_deployment`
+to simulate work that's going on. During that processing, we also make a call to
+`create_deployment_status`, which lets a receiver know what's going on, as we
+switch the status to `pending`.
-Após a conclusão da implantação, definimos o status como `success`.
+After the deployment is finished, we set the status to `success`.
-## Conclusão
+## Conclusion
-No GitHub, há vários anos, usamos uma versão do [Heaven][heaven] para gerenciar nossas implantações. Um fluxo comum é essencialmente o mesmo que o servidor que criamos acima:
+At GitHub, we've used a version of [Heaven][heaven] to manage
+our deployments for years. A common flow is essentially the same as the
+server we've built above:
-* Aguarde uma resposta sobre o estado das verificações de CI (sucesso ou falha)
-* Se as verificações forem bem-sucedidas, faça o merge do pull request
-* Heaven toma o código mesclado e o implementa nos servidores de teste e produção
-* Enquanto isso, o Heaven também notifica todos sobre o build por meio do [Hubot][hubot] sentado nas salas de chat
+* Wait for a response on the state of the CI checks (success or failure)
+* If the required checks succeed, merge the pull request
+* Heaven takes the merged code, and deploys it to staging and production servers
+* In the meantime, Heaven also notifies everyone about the build, via [Hubot][hubot] sitting in our chat rooms
-É isso! Você não precisa criar sua própria configuração de implantação para usar este exemplo.
-Você sempre pode contar com as [integrações do GitHub][integrations].
+That's it! You don't need to build your own deployment setup to use this example.
+You can always rely on [GitHub integrations][integrations].
[deploy API]: /rest/reference/repos#deployments
[status API]: /guides/building-a-ci-server
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 6d6f18542f..9d89b94984 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
@@ -85,7 +85,7 @@ Você pode filtrar problemas com base no motivo informado quando o problema foi
| Qualificador | Exemplo
| ------------- | -------------
| `reason:completed` | [**libraries is:closed reason:complete**](https://github.com/search?q=libraries+is%3Aclosed+reason%3Acompleted&type=Issues) corresponde a problemas com a palavra "libraries" que foram fechados como "completed".
-| `reason:"not planned"` | [**libraries is:closed reason:"not planned"** ](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) corresponde a problemas com a palavra "libraries" que foram fechados como "não planejados".
+| `reason:"not planned"` | [**libraries is:closed reason:"not planned"**](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) corresponde a problemas com a palavra "libraries" que foram fechados como "não planejados".
{% endif %}
@@ -119,7 +119,7 @@ O qualificador `mentions` encontra os problemas que mencionam um usuário espec
| Qualificador | Exemplo
| ------------- | -------------
-| mentions:USERNAME | [ **`resque mentions:defunkt`** ](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) corresponde aos problemas com a palavra "resque" que mencionam @defunkt.
+| mentions:USERNAME | [ **`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) corresponde aos problemas com a palavra "resque" que mencionam @defunkt.
## Pesquisar por menção da equipe
@@ -174,8 +174,8 @@ O qualificador `milestone` encontra problemas ou solicitações de pull que faze
| Qualificador | Exemplo
| ------------- | -------------
-| milestone:MILESTONE | [**milestone:"overhaul"** ](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) corresponde aos problemas que estão em um marco chamado "overhaul".
-| | [**milestone:"bug fix"** ](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) corresponde aos problemas que estão em um marco chamado "bug fix".
+| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) corresponde aos problemas que estão em um marco chamado "overhaul".
+| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) corresponde aos problemas que estão em um marco chamado "bug fix".
## Pesquisar por quadro de projeto
@@ -308,7 +308,7 @@ Esse qualificador usa a data como parâmetro. {% data reusables.time_date.date_f
| Qualificador | Exemplo
| ------------- | -------------
-| merged:YYYY-MM-DD | [ **`language:javascript merged:<2011-01-01`** ](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) corresponde às solicitações de pull em repositórios JavaScript que foram mescladas antes de 2011.
+| merged:YYYY-MM-DD | [ **`language:javascript merged:<2011-01-01`**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) corresponde às solicitações de pull em repositórios JavaScript que foram mescladas antes de 2011.
| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) corresponde às solicitações de pull no Ruby com a palavra "fast" no título que foram mescladas após maio de 2014.
## Pesquisar somente pull request com merge ou sem merge
diff --git a/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md b/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md
deleted file mode 100644
index 7cb280898c..0000000000
--- a/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-ms.openlocfilehash: 993a49348ec6d3041377512d70efa3d192cbb4d0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145094416"
----
-{% warning %}
-
-**Aviso:** os únicos provedores de armazenamento S3 com suporte são o Amazon S3 e o Gateway do MinIO para NAS. Os outros provedores de armazenamento compatíveis com a API do S3 não são compatíveis. Para obter mais informações sobre os provedores de armazenamento com suporte, confira "[Introdução ao GitHub Actions para GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)".
-
-{% endwarning %}
diff --git a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md
index 4f702e6e70..35a05a1c1a 100644
--- a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md
+++ b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md
@@ -1,10 +1,11 @@
{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %}
-- by email, an email is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option).
-- in the user interface, a warning is shown in your repository's file and code views if there are any insecure dependencies (**UI alerts** option).
-- on the command line, warnings are displayed as callbacks when you push to repositories with any insecure dependencies (**Command Line** option).
-- in your inbox, as web notifications. A web notification is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Web** option).{% ifversion not ghae %}
-- on {% data variables.product.prodname_mobile %}, as web notifications. For more information, see "[Enabling push notifications with GitHub Mobile](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."{% endif %}
+- in your inbox, as web notifications. A web notification is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**On {% data variables.product.prodname_dotcom %}** option).
+- by email, an email is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Email** option).{% ifversion ghes < 3.8 or ghae < 3.8 %}
+- in the user interface, a warning is shown in your repository's file and code views if there are any insecure dependencies (**UI alerts** option).{% endif %}
+- on the command line, warnings are displayed as callbacks when you push to repositories with any insecure dependencies (**CLI** option).
+{% ifversion not ghae %}
+- on {% data variables.product.prodname_mobile %}, as web notifications. For more information, see "[Enabling push notifications with {% data variables.product.prodname_mobile %}](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."{% endif %}
{% note %}
diff --git a/translations/pt-BR/data/reusables/organizations/org_settings.md b/translations/pt-BR/data/reusables/organizations/org_settings.md
index 7679eb58d9..bf5a8d290e 100644
--- a/translations/pt-BR/data/reusables/organizations/org_settings.md
+++ b/translations/pt-BR/data/reusables/organizations/org_settings.md
@@ -1,10 +1,10 @@
---
-ms.openlocfilehash: ddc27b0ace0d5be48f1d93fe36ed27cc1a16184f
-ms.sourcegitcommit: 0c000ebc6e405c1d634fe370f834cd6dce35124b
+ms.openlocfilehash: d126bcc398466f97770101d43c275a5e1fdda16a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
ms.translationtype: HT
ms.contentlocale: pt-BR
-ms.lasthandoff: 11/02/2022
-ms.locfileid: "148130905"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107928"
---
1. No nome da sua organização, clique em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**.
-{% ifversion fpt or ghes or ghec %}  {% else %}  {% endif %}
+ {% ifversion fpt or ghes or ghec %}  {% else %}  {% endif %}
diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 3d68fc424b..ca4af641d0 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -10,10 +10,10 @@ Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret
Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id amazon_oauth_client_secret{% endif %}
Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id aws_secret_access_key
Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token aws_temporary_access_key_id aws_secret_access_key
-Asana | Asana {% data variables.product.pat_generic %} | asana_personal_access_token
+Asana | Asana {% data variables.product.pat_generic_title_case %} | asana_personal_access_token
Atlassian | Atlassian API Token | atlassian_api_token
Atlassian | Atlassian JSON Web Token | atlassian_jwt
-Atlassian | Bitbucket Server {% data variables.product.pat_generic %} | bitbucket_server_personal_access_token
+Atlassian | Bitbucket Server {% data variables.product.pat_generic_title_case %} | bitbucket_server_personal_access_token
{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %}
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
@@ -22,7 +22,7 @@ Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %}
Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %}
-Azure | Azure DevOps {% data variables.product.pat_generic %} | azure_devops_personal_access_token
+Azure | Azure DevOps {% data variables.product.pat_generic_title_case %} | azure_devops_personal_access_token
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
Azure | Azure ML Studio (classic) Web Service Key | azure_ml_studio_classic_web_service_key{% endif %}
Azure | Azure SAS Token | azure_sas_token
@@ -35,14 +35,14 @@ Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_k
Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key
Clojars | Clojars Deploy Token | clojars_deploy_token
CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential
-Contentful | Contentful {% data variables.product.pat_generic %} | contentful_personal_access_token
+Contentful | Contentful {% data variables.product.pat_generic_title_case %} | contentful_personal_access_token
Databricks | Databricks Access Token | databricks_access_token
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
DevCycle | DevCycle Client API Key | devcycle_client_api_key
DevCycle | DevCycle Server API Key | devcycle_server_api_key
DevCycle | DevCycle Mobile API Key | devcycle_mobile_api_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
-DigitalOcean | DigitalOcean {% data variables.product.pat_generic %} | digitalocean_personal_access_token
+DigitalOcean | DigitalOcean {% data variables.product.pat_generic_title_case %} | digitalocean_personal_access_token
DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token
DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token
DigitalOcean | DigitalOcean System Token | digitalocean_system_token{% endif %}
@@ -67,7 +67,7 @@ Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key
Frame.io | Frame.io JSON Web Token | frameio_jwt
Frame.io| Frame.io Developer Token | frameio_developer_token
FullStory | FullStory API Key | fullstory_api_key
-GitHub | GitHub {% data variables.product.pat_generic %} | github_personal_access_token
+GitHub | GitHub {% data variables.product.pat_generic_title_case %} | github_personal_access_token
GitHub | GitHub OAuth Access Token | github_oauth_access_token
GitHub | GitHub Refresh Token | github_refresh_token
GitHub | GitHub App Installation Access Token | github_app_installation_access_token
@@ -95,7 +95,7 @@ HashiCorp | HashiCorp Vault Root Service Token | hashicorp_vault_root_service_to
HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token
Hubspot | Hubspot API Key | hubspot_api_key
Intercom | Intercom Access Token | intercom_access_token
-Ionic | Ionic {% data variables.product.pat_generic %} | ionic_personal_access_token
+Ionic | Ionic {% data variables.product.pat_generic_title_case %} | ionic_personal_access_token
Ionic | Ionic Refresh Token | ionic_refresh_token
{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %}
@@ -192,7 +192,7 @@ Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key
Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret
{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
Supabase | Supabase Service Key | supabase_service_key{% endif %}
-Tableau | Tableau {% data variables.product.pat_generic %} | tableau_personal_access_token
+Tableau | Tableau {% data variables.product.pat_generic_title_case %} | tableau_personal_access_token
Telegram | Telegram Bot Token | telegram_bot_token
Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id
{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
@@ -200,7 +200,7 @@ Twilio | Twilio Access Token | twilio_access_token{% endif %}
Twilio | Twilio Account String Identifier | twilio_account_sid
Twilio | Twilio API Key | twilio_api_key
{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
-Typeform | Typeform {% data variables.product.pat_generic %} | typeform_personal_access_token{% endif %}
+Typeform | Typeform {% data variables.product.pat_generic_title_case %} | typeform_personal_access_token{% endif %}
{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
Uniwise | WISEflow API Key | wiseflow_api_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
index 599d5d86a8..1474a37c80 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -12,7 +12,7 @@ Atlassian | Atlassian JSON Web Token
Azure | Azure Active Directory Application Secret
Azure | Azure Batch Key Identifiable
Azure | Azure CosmosDB Key Identifiable
-Azure | Azure DevOps {% data variables.product.pat_generic %}
+Azure | Azure DevOps {% data variables.product.pat_generic_title_case %}
Azure | Azure ML Studio (classic) Web Service Key
Azure | Azure SAS Token
Azure | Azure Service Management Certificate
@@ -28,7 +28,7 @@ Databricks | Databricks Access Token
Datadog | Datadog API Key
DevCycle | DevCycle Client API Key
DevCycle | DevCycle Server API Key
-DigitalOcean | DigitalOcean {% data variables.product.pat_generic %}
+DigitalOcean | DigitalOcean {% data variables.product.pat_generic_title_case %}
DigitalOcean | DigitalOcean OAuth Token
DigitalOcean | DigitalOcean Refresh Token
DigitalOcean | DigitalOcean System Token
@@ -46,7 +46,7 @@ Finicity | Finicity App Key
Frame.io | Frame.io JSON Web Token
Frame.io| Frame.io Developer Token
FullStory| FullStory API Key
-GitHub | GitHub {% data variables.product.pat_generic %}
+GitHub | GitHub {% data variables.product.pat_generic_title_case %}
GitHub | GitHub OAuth Access Token
GitHub | GitHub Refresh Token
GitHub | GitHub App Installation Access Token
@@ -57,7 +57,7 @@ Google Cloud | Google API Key
Google Cloud | Google Cloud Private Key ID
Hashicorp Terraform | Terraform Cloud / Enterprise API Token
Hubspot | Hubspot API Key
-Ionic | Ionic {% data variables.product.pat_generic %}
+Ionic | Ionic {% data variables.product.pat_generic_title_case %}
Ionic | Ionic Refresh Token
JD Cloud | JD Cloud Access Key
Linear | Linear API Key
@@ -110,7 +110,7 @@ Supabase | Supabase Service Key
Tencent Cloud | Tencent Cloud Secret ID
Twilio | Twilio Account String Identifier
Twilio | Twilio API Key
-Typeform | Typeform {% data variables.product.pat_generic %}
+Typeform | Typeform {% data variables.product.pat_generic_title_case %}
Uniwise | WISEflow API Key
Valour | Valour Access Token
Yandex | Yandex.Cloud API Key
diff --git a/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md
index 016e7b23c1..9e9def0bbc 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md
@@ -5,15 +5,15 @@ Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret
Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id amazon_oauth_client_secret
Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id aws_secret_access_key
Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token aws_temporary_access_key_id aws_secret_access_key
-Asana | Asana {% data variables.product.pat_generic %} | asana_personal_access_token
-Atlassian | Bitbucket Server {% data variables.product.pat_generic %} | bitbucket_server_personal_access_token
+Asana | Asana {% data variables.product.pat_generic_title_case %} | asana_personal_access_token
+Atlassian | Bitbucket Server {% data variables.product.pat_generic_title_case %} | bitbucket_server_personal_access_token
Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %}
Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %}
-Azure | Azure DevOps {% data variables.product.pat_generic %} | azure_devops_personal_access_token
+Azure | Azure DevOps {% data variables.product.pat_generic_title_case %} | azure_devops_personal_access_token
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
Azure | Azure ML Studio (classic) Web Service Key | azure_ml_studio_classic_web_service_key{% endif %}
{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
@@ -25,7 +25,7 @@ Databricks | Databricks Access Token | databricks_access_token
DevCycle | DevCycle Client API Key | devcycle_client_api_key
DevCycle | DevCycle Server API Key | devcycle_server_api_key
DevCycle | DevCycle Mobile API Key | devcycle_mobile_api_key{% endif %}
-DigitalOcean | DigitalOcean {% data variables.product.pat_generic %} | digitalocean_personal_access_token
+DigitalOcean | DigitalOcean {% data variables.product.pat_generic_title_case %} | digitalocean_personal_access_token
DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token
DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token
DigitalOcean | DigitalOcean System Token | digitalocean_system_token
@@ -40,7 +40,7 @@ Duffel | Duffel Live Access Token | duffel_live_access_token
EasyPost | EasyPost Production API Key | easypost_production_api_key
Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key
Fullstory | FullStory API Key | fullstory_api_key
-GitHub | GitHub {% data variables.product.pat_generic %} | github_personal_access_token
+GitHub | GitHub {% data variables.product.pat_generic_title_case %} | github_personal_access_token
GitHub | GitHub OAuth Access Token | github_oauth_access_token
GitHub | GitHub Refresh Token | github_refresh_token
GitHub | GitHub App Installation Access Token | github_app_installation_access_token
@@ -58,7 +58,7 @@ Intercom | Intercom Access Token | intercom_access_token
{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
JFrog | JFrog Platform Access Token | jfrog_platform_access_token
JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %}
-Ionic | Ionic {% data variables.product.pat_generic %} | ionic_personal_access_token
+Ionic | Ionic {% data variables.product.pat_generic_title_case %} | ionic_personal_access_token
Ionic | Ionic Refresh Token | ionic_refresh_token
Linear | Linear API Key | linear_api_key
Linear | Linear OAuth Access Token | linear_oauth_access_token
@@ -96,7 +96,7 @@ Shopify | Shopify Access Token | shopify_access_token
Slack | Slack API Token | slack_api_token
Stripe | Stripe Live API Secret Key | stripe_api_key
Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id
-Typeform | Typeform {% data variables.product.pat_generic %} | typeform_personal_access_token
+Typeform | Typeform {% data variables.product.pat_generic_title_case %} | typeform_personal_access_token
{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
Uniwise | WISEflow API Key | wiseflow_api_key{% endif %}
WorkOS | WorkOS Production API Key | workos_production_api_key
diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml
index eab46df50e..6c890174f3 100644
--- a/translations/pt-BR/data/variables/product.yml
+++ b/translations/pt-BR/data/variables/product.yml
@@ -88,6 +88,7 @@ prodname_project_v1_caps: >-
# Personal access tokens
pat_generic: 'personal access token'
pat_generic_caps: 'Personal access token'
+pat_generic_title_case: 'Personal Access Token'
pat_v2: 'fine-grained personal access token'
pat_v2_caps: 'Fine-grained personal access token'
pat_v1: >-