diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md index c83d3f8c4e..875661ff8a 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md @@ -45,7 +45,8 @@ Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actio Usando, por exemplo, [CLI AWS](https://aws.amazon.com/cli/): {% raw %}```bash{:copy} - aws ecr create-repository \ --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION + aws ecr create-repository \ + --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION ```{% endraw %} Certifique-se de usar o mesmo nome de repositório do Amazon ECR (representado aqui por `MY_ECR_REPOSITORY`) para a variável `ECR_REPOSITORY` no fluxo de trabalho abaixo. diff --git a/translations/pt-BR/content/authentication/index.md b/translations/pt-BR/content/authentication/index.md index a33c89418b..e831015d85 100644 --- a/translations/pt-BR/content/authentication/index.md +++ b/translations/pt-BR/content/authentication/index.md @@ -18,6 +18,30 @@ versions: ghes: '*' ghae: '*' ghec: '*' +introLinks: + overview: /authentication/keeping-your-account-and-data-secure/about-authentication-to-github +featuredLinks: + guides: + - /authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent + - /authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token + - /authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication + - '{% ifversion ghae %}/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials{% endif %}' + popular: + - /authentication/troubleshooting-ssh + - /authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys + - /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account + - '{% ifversion ghae %}/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection{% endif %}' + - /authentication/authenticating-with-saml-single-sign-on + - /authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits + guideCards: + - /authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials + - /authentication/troubleshooting-ssh/error-permission-denied-publickey + - /authentication/keeping-your-account-and-data-secure/creating-a-strong-password + - '{% ifversion ghae %}/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials{% endif %}' + - '{% ifversion ghae %}/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on{% endif %}' +changelog: + label: '2FA,authentication,security keys,SSH,token authentication' +layout: product-landing topics: - 2FA - Identity diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md index ea6083fd93..91b7a8c7c6 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md @@ -464,7 +464,7 @@ jobs: ### Habilitar o merge automático em um pull request -Se você quiser fazer merge automático dos seus pull requests, você poderá usar a funcionalidade de merge automático de {% data variables.product.prodname_dotcom %}. Isto permite que o pull request seja mesclado quando todos os testes e aprovações forem cumpridos com sucesso. Para obter mais informações sobre merge automático, consulte "[Fazer merge automático de um pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)". +Se você quiser fazer merge automático dos seus pull requests, você poderá usar a funcionalidade de merge automático de {% data variables.product.prodname_dotcom %}. Isto permite que o pull request seja mesclado quando todos os testes e aprovações forem cumpridos com sucesso. For more information on auto-merge, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." Aqui está um exemplo de como habilitar o merge automático para todas as atualizações de patch para `my-dependency`: diff --git a/translations/pt-BR/content/graphql/overview/resource-limitations.md b/translations/pt-BR/content/graphql/overview/resource-limitations.md index 951111d2af..169d0e72f1 100644 --- a/translations/pt-BR/content/graphql/overview/resource-limitations.md +++ b/translations/pt-BR/content/graphql/overview/resource-limitations.md @@ -24,7 +24,9 @@ Para passar a validação do [esquema](/graphql/guides/introduction-to-graphql#s Estes dois exemplos mostram como calcular os nós totais em uma chamada. -1. Consulta simples: 
query {
+1. Consulta simples:
+
+  
query {
     viewer {
       repositories(first: 50) {
         edges {
@@ -46,13 +48,17 @@ Estes dois exemplos mostram como calcular os nós totais em uma chamada.
     }
   }

 
-  Cálculo: 
50         = 50 repositories
+  Cálculo:
+
+  
50         = 50 repositories
    +
   50 x 10  = 500 repository issues
 
               = 550 total nodes

 
-2. Consulta complexa: 
query {
+2. Consulta complexa:
+
+  
query {
     viewer {
       repositories(first: 50) {
         edges {
@@ -106,7 +112,9 @@ Estes dois exemplos mostram como calcular os nós totais em uma chamada.
     }
   }

 
-  Cálculo: 
50              = 50 repositories
+  Cálculo:
+
+  
50              = 50 repositories
    +
   50 x 20       = 1,000 pullRequests
    +
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md
deleted file mode 100644
index fa7aed1fd4..0000000000
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Adicionando um pull request à fila de merge
-intro: 'Se as filas de merge estiverem habilitadas para o repositório, você poderá adicionar seus pull requests à fila de merge assim que todas as verificações necessárias tiverem passado. {% data variables.product.product_name %} fará merge dos pull requests para você.'
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Pull requests
-shortTitle: Adicionar PR à fila de merge
-redirect_from:
-  - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue
----
-
-{% data reusables.pull_requests.merge-queue-beta %}
-
-## Sobre a a fila de merge do pull request
-
-{% data reusables.pull_requests.merge-queue-overview-short %}
-{% data reusables.pull_requests.merge-queue-references %}
-
-## Adicionando um pull request à fila de merge
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-pr %}
-1. Na lista "Pull Requests", clique no pull request que você deseja adicionar à fila de merge.
-1. Clique **Adicionar à fila de merge** para adicionar seu pull request à fila de merge. Isso habilita a opção padrão **Fila e merge em um grupo**. Como alternativa, você pode:
-   - Adicione seu pull request à frente da fila, selecionando o menu suspenso **Adicionar à gila de merge** e clicando em **Pular a fila** (disponível apenas para mantenedores e administradores do repositório).
-   - Faça o merge direto do seu pull request selecionando o menu suspenso **Adicionar à fila de merge** e clicando em **Fazer merge diretamente** (disponível apenas para administradores do repositório). ![Opções da fila de merge](/assets/images/help/pull_requests/merge-queue-options.png)
-
-   {% tip %}
-
-   **Dica:** O botão **Adicionar à fila de merge** só é habilitado quando o pull request atender a todos os requisitos de revisão/aprovação e verificação de status.
-
-   {% endtip %}
-2. Confirme que você deseja adicionar o pull request à fila de merge clicando em **Confirmar a adição à fila de merge**.
-   {% data variables.product.product_name %} adiciona o pull request à fila de merge e irá fazer o merge para você.
-
-## Visualizando a fila de merge
-
-Você pode visualizar a fila de merge em vários lugares em {% data variables.product.product_name %}.
-
-   - Na página **Branches** para o repositório. Recomendamos que você use encaminhamento rota se você não tiver ou não conhecer um pull request já na fila e se você quiser ver o que está na fila. Para obter mais informações, consulte "[Visualizar branches no seu repositório](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository)".
-
-  ![Visualizar fila de merge na página de Branches](/assets/images/help/pull_requests/merge-queue-branches-page.png)
-
-- Na página **Pull requests** do seu repositório, clique em {% octicon "clock" aria-label="The clock symbol" %}.
-
-  ![Visualizar fila de merge na página de Pull requests](/assets/images/help/pull_requests/clock-icon-in-pull-request-list.png)
-
-- No seu pull request, role para baixo para a seção com as verificações e clique em **Visualizar fila de merge**.
-
-  ![Ver botão de fila de merge no pull request](/assets/images/help/pull_requests/view-merge-queue-button.png)
-
-A exibição da fila de merge mostra os pull requests que estão atualmente na fila, com seus pull requests claramente marcados.
-
-![Visualização da fila de merge](/assets/images/help/pull_requests/merge-queue-view.png)
-
-## Manipulação de pull requests removidos da fila de merge
-
-{% data reusables.pull_requests.merge-queue-reject %}
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
index bc98066bdd..946121e076 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
@@ -16,7 +16,7 @@ children:
   - /about-pull-request-merges
   - /merging-a-pull-request
   - /automatically-merging-a-pull-request
-  - /adding-a-pull-request-to-the-merge-queue
+  - /merging-a-pull-request-with-a-merge-queue
   - /closing-a-pull-request
   - /reverting-a-pull-request
 shortTitle: Incorporar alterações
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
new file mode 100644
index 0000000000..b66f195726
--- /dev/null
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
@@ -0,0 +1,72 @@
+---
+title: Merging a pull request with a merge queue
+intro: 'If a merge queue is required by the branch protection setting for the branch, you can add your pull requests to a merge queue and {% data variables.product.product_name %} will merge the pull requests for you once all required checks have passed.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Merge PR with merge queue
+redirect_from:
+  - /pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue
+---
+
+{% data reusables.pull_requests.merge-queue-beta %}
+
+## About merge queues
+
+{% data reusables.pull_requests.merge-queue-overview %}
+{% data reusables.pull_requests.merge-queue-references %}
+
+## Adding a pull request to a merge queue
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-pr %}
+
+1. In the "Pull Requests" list, click the pull request you would like to add to a merge queue.
+
+1. Click **Merge when ready** to add the pull request to the merge queue. Alternatively, if you are an administrator, you can:
+   -  Directly merge the pull request by checking **Merge without waiting for requirements to be met (administrators only)**, if allowed by branch protection settings, and follow the standard flow. ![Opções da fila de merge](/assets/images/help/pull_requests/merge-queue-options.png)
+
+  {% tip %}
+
+  **Tip:** You can click  **Merge when ready** whenever you're ready to merge your proposed changes. {% data variables.product.product_name %} will automatically add the pull request to the merge queue once required approval and status checks conditions are met.
+
+  {% endtip %}
+
+1. Confirm you want to add the pull request to the merge queue by clicking  **Confirm merge when ready**.
+
+## Removing a pull request from a merge queue
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-pr %}
+
+1. In the "Pull Requests" list, click the pull request you would like to remove from a merge queue.
+
+1. To remove the pull request from the queue, click **Remove from queue**. ![Remove pull request from queue](/assets/images/help/pull_requests/remove-from-queue-button.png)
+
+Alternatively, you can navigate to the merge queue page for the base branch, click **...** next to the pull request you want to remove, and select **Remove from queue**. For information on how to get to the merge queue page for the base branch, see the section below.
+
+## Viewing merge queues
+
+You can view the merge queue for a base branch in various places on {% data variables.product.product_name %}.
+
+- Na página **Branches** para o repositório. We recommend you use this route if you don't have or don't know about a pull request already in a queue, and if you want to see what's in that queue. Para obter mais informações, consulte "[Visualizar branches no seu repositório](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository)".
+
+  ![Visualizar fila de merge na página de Branches](/assets/images/help/pull_requests/merge-queue-branches-page.png)
+
+- On the **Pull requests** page of your repository, click {% octicon "clock" aria-label="The clock symbol" %} next to any pull request in the merge queue.
+
+  ![Visualizar fila de merge na página de Pull requests](/assets/images/help/pull_requests/clock-icon-in-pull-request-list.png)
+
+- On the pull request page when merge queue is required for merging, scroll to the bottom of the timeline and click **the merge queue** link.
+
+  ![Merge queue link on pull request](/assets/images/help/pull_requests/merge-queue-link.png)
+
+- A exibição da fila de merge mostra os pull requests que estão atualmente na fila, com seus pull requests claramente marcados.
+
+  ![Visualização da fila de merge](/assets/images/help/pull_requests/merge-queue-view.png)
+
+## Manipulação de pull requests removidos da fila de merge
+
+{% data reusables.pull_requests.merge-queue-reject %}
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
index 1ae9d3859a..a9e57a6fec 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
@@ -15,7 +15,7 @@ children:
   - /about-merge-methods-on-github
   - /configuring-commit-squashing-for-pull-requests
   - /configuring-commit-rebasing-for-pull-requests
-  - /using-a-merge-queue
+  - /managing-a-merge-queue
   - /managing-suggestions-to-update-pull-request-branches
   - /managing-auto-merge-for-pull-requests-in-your-repository
   - /managing-the-automatic-deletion-of-branches
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md
new file mode 100644
index 0000000000..bf6e706c48
--- /dev/null
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md
@@ -0,0 +1,58 @@
+---
+title: Managing a merge queue
+intro: You can increase development velocity with a merge queue for pull requests in your repository.
+versions:
+  fpt: '*'
+  ghec: '*'
+permissions: People with admin permissions can manage merge queues for pull requests targeting selected branches of a repository.
+topics:
+  - Repositories
+  - Pull requests
+shortTitle: Managing merge queue
+redirect_from:
+  - /repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue
+---
+
+{% data reusables.pull_requests.merge-queue-beta %}
+
+## About merge queues
+
+{% data reusables.pull_requests.merge-queue-overview %}
+
+The merge queue creates temporary branches with a special prefix to validate pull request changes. The changes in the pull request are then grouped with the latest version of the `base_branch` as well as changes ahead of it in the queue. {% data variables.product.product_name %} will merge all these changes into `base_branch` once the checks required by the branch protections of `base_branch` pass.
+
+You may need to update your Continuous Integration (CI) configuration to trigger builds on branch names that begin with the special prefix `gh-readonly-queue/{base_branch}` after the group is created.
+
+For example, with {% data variables.product.prodname_actions %}, a workflow with the following trigger will run each time a pull request that targets the base branch `main` is queued to merge.
+
+```yaml
+on:
+  push:
+    branches:
+    - gh-readonly-queue/main/**
+```
+
+{% data reusables.pull_requests.merge-queue-merging-method %}
+
+Para obter informações sobre métodos de merge, consulte "[Sobre merges de pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)".
+
+{% note %}
+
+**Observação:**
+
+* A merge queue cannot be enabled with branch protection rules that use wildcard characters (`*`) in the branch name pattern.
+
+{% endnote %}
+
+{% data reusables.pull_requests.merge-queue-reject %}
+
+## Managing a merge queue
+
+Repository administrators can require a merge by enabling the branch protection setting "Require merge queue" in the protection rules for the base branch.
+
+Para obter informações sobre como habilitar a configuração de proteção de fila de merge, consulte "[Gerenciando uma regra de proteção de branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule). "
+
+## Leia mais
+
+* "[Merging a pull request with a merge queue](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue)"
+* "[Sobre branches protegidos](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)"
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
deleted file mode 100644
index 7dd520d636..0000000000
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Usando uma fila de merge
-intro: É possível aumentar a velocidade de desenvolvimento permitindo o merge das filas para pull requests no seu repositório.
-versions:
-  fpt: '*'
-  ghec: '*'
-permissions: People with admin permissions can configure merge queues for pull requests targeting selected branches of a repository.
-topics:
-  - Repositories
-  - Pull requests
-shortTitle: Usar fila de merge
----
-
-{% data reusables.pull_requests.merge-queue-beta %}
-
-## Sobre a a fila de merge do pull request
-
-{% data reusables.pull_requests.merge-queue-overview %}
-
-A fila de merge cria branches preparatórios temporários para validar pull requests com a versão mais recente do branch base. Para garantir que {% data variables.product.prodname_dotcom %} irá validar esses branches preparatórios, é possível você precise atualizar sua configuração de CI para acionar compilações em nomes de branch que começam com `gh-readonly-queue/{base_branch}`.
-
-Por exemplo, com {% data variables.product.prodname_actions %}, adicionar a opção a seguir no fluxo de trabalho fará com que o fluxo de trabalho seja executado quando qualquer push for feito em um branch preparatório da fila de merge que tem o `principal` como destino.
-
-```
-on:
-  push:
-    branches:
-    - main
-    - gh-readonly-queue/main/**
-```
-
-{% data reusables.pull_requests.merge-queue-merging-method %}
-
-Para obter informações sobre métodos de merge, consulte "[Sobre merges de pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)". Para obter informações sobre a configuração de proteção do branch "Exigir histórico linear", consulte "[Sobre branches protegidos](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)".
-
-{% note %}
-
-**Observação:** durante o beta, existem algumas limitações ao usar a fila de merge:
-
-* A fila de mergenão pode ser habilitada nas regras de proteção do branch que usam curinga (`*`) no nome.
-* Não há suporte para os commits de merge de combinação por squash. (Somente commits de merge e commits de "rebase e merge" são compatíveis.)
-
-{% endnote %}
-
-{% data reusables.pull_requests.merge-queue-reject %}
-## Gerenciando a fila de merge do pull request
-
-Os administradores de repositório podem configurar filas de merge para pull requests direcionando branches selecionados de um repositório. O requisito para usar uma fila de merge é uma configuração de proteção de branch denominado "Exigir fila de merge" que pode ser habilitado nas regras de proteção do branch.
-
-Para obter informações sobre como habilitar a configuração de proteção de fila de merge, consulte "[Gerenciando uma regra de proteção de branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule). "
-
-## Leia mais
-
-- "[Adicionando uma pull request à fila de merge](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)"
-- "[Sobre branches protegidos](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)"
diff --git a/translations/pt-BR/content/rest/overview/api-previews.md b/translations/pt-BR/content/rest/overview/api-previews.md
index 8656133f76..c43360b191 100644
--- a/translations/pt-BR/content/rest/overview/api-previews.md
+++ b/translations/pt-BR/content/rest/overview/api-previews.md
@@ -4,10 +4,8 @@ intro: Você pode usar pré-visualizações da API para testar novos recursos e
 redirect_from:
   - /v3/previews
 versions:
-  fpt: '*'
   ghes: '*'
   ghae: '*'
-  ghec: '*'
 topics:
   - API
 ---
@@ -118,16 +116,6 @@ Agora você pode [exigir múltiplas revisões de aprovação](/rest/reference/re
 
 {% endif %}
 
-
-{% ifversion ghes %}
-
-## Acesso de Git anônimo aos repositórios
-
-Quando uma instância do {% data variables.product.prodname_ghe_server %} estiver em modo privado, os administradores do site e do repositório podem habilitar o acesso anônimo ao Git para um repositório público.
-
-**Tipo de mídia personalizada:** `x ray-preview` **Anunciado:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
-
-{% endif %}
 {% ifversion ghes < 3.3 %}
 
 ## Detalhes do cartão de projeto
@@ -136,15 +124,6 @@ As respostas da API REST para [eventos de problemas](/rest/reference/issues#even
 
 **Tipo de mídia personalizada:** `starfox-preview` **Anunciado:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
 
-{% endif %}
-{% ifversion fpt or ghec %}
-
-## Manifestoes do aplicativo GitHub
-
-Os manifestos do aplicativo GitHub permitem que pessoas criem aplicativos GitHub pré-configurados. Veja "[Criar aplicativos GitHub a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para obter mais inoformações.
-
-**Tipo de mídia personalizada:** `fury-preview`
-
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
diff --git a/translations/pt-BR/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md b/translations/pt-BR/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
index 8ef32eba24..44b87b58a9 100644
--- a/translations/pt-BR/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
+++ b/translations/pt-BR/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
@@ -109,4 +109,6 @@ Interpretaremos nossas políticas e resolveremos nossas disputas a favor de prot
 
 ---
 
-O GitHub mantém total discrição para [tomar a ação](/github/site-policy/github-community-guidelines#what-happens-if-someone-violates-githubs-policies) em resposta a uma violação dessas políticas, incluindo a suspensão da conta, [cancelamento](/github/site-policy/github-terms-of-service#3-github-may-terminate) da conta ou [remoção](/github/site-policy/github-terms-of-service#2-github-may-remove-content) de conteúdo.
+**Enforcement.** GitHub retains full discretion to [take action](/github/site-policy/github-community-guidelines#what-happens-if-someone-violates-githubs-policies) in response to a violation of these policies, including account suspension, account [termination](/github/site-policy/github-terms-of-service#3-github-may-terminate), or [removal](/github/site-policy/github-terms-of-service#2-github-may-remove-content) of content. Please also see our [Community Guidelines](/site-policy/github-terms/github-community-guidelines) for actions you can take if something or someone offends you.
+
+**Reinstatement and appeal.** If your content or account has been disabled or restricted and you seek reinstatement or wish to appeal, please see our [Appeal and Reinstatement page](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement) for information about the process and use our [Appeal and Reinstatement form](https://support.github.com/contact/reinstatement) to submit a request.
diff --git a/translations/pt-BR/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md b/translations/pt-BR/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
index b49ec39d44..a216a12ef4 100644
--- a/translations/pt-BR/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
+++ b/translations/pt-BR/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
@@ -17,7 +17,7 @@ Ser parte de uma comunidade inclui não tirar proveito de outros integrantes da
 
   Em casos raros de abuso muito generalizado de conteúdo de dupla utilização, podemos restringir o acesso a essa instância específica do conteúdo para interromper um ataque ilegal ou uma campanha de malware que aproveita a plataforma GitHub como um exploit ou malware CDN. Na maioria dessas instâncias, a restrição assume a forma de colocar o conteúdo por trás da autenticação. No entanto, como opção de último recurso, pode envolver a desabilitação do acesso ou a remoção total quando isso não for possível (p. ex., quando postado como um gist). Também entraremos em contato com os proprietários dos projetos sobre restrições implementadas sempre que possível.
 
-  As restrições são temporárias quando possíveis e não servem o propósito de eliminar ou restringir qualquer conteúdo específico de dupla utilização ou cópias desse conteúdo da plataforma. Embora procuremos fazer desses raros casos de restrição um processo de colaboração com os proprietários do projeto, se você sentir que seu conteúdo foi restrito indevidamente, temos um [processo de recursos](/github/site-policy/github-community-guidelines#appeal-and-reinstatement) em vigor.
+  As restrições são temporárias quando possíveis e não servem o propósito de eliminar ou restringir qualquer conteúdo específico de dupla utilização ou cópias desse conteúdo da plataforma. While we aim to make these rare cases of restriction a collaborative process with project owners, if you do feel your content was unduly restricted, we have an [appeals process](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement) in place.
 
   Para facilitar um caminho para a resolução de abuso com os próprios mantenedores do projeto, antes da escalada aos relatórios de abuso do GitHub, recomendamos, embora não exigimos, que os proprietários do repositório sigam as etapas a seguir ao postar conteúdo de pesquisa de segurança potencialmente prejudicial:
 
diff --git a/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md b/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md
index 90dea21aac..d31e45f4a6 100644
--- a/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md
+++ b/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md
@@ -71,13 +71,7 @@ Nos casos em que decidimos que se justifica uma ação de moderação, estas sã
 
 ## Apelação e reinstauração
 
-Em alguns casos, pode haver justificativa para reverter uma ação de moderação tomada pela equipe do GitHub.
-
-* **Restabelecimento**: Quando um usuário deseja corrigir a violação e está disposto a aceitar o cumprimento de nossas Políticas de Uso Aceitáveis dali em diante, podemos optar por restabelecar a sua conta ou conteúdo dependendo da gravidade da violação inicial.
-
-* **Recurso**: Se um usuário deseja contestar o fundamento de uma ação de execução e puder fornecer informações adicionais sobre a alegada violação, reanalisaremos essas informações e poderemos interpor recurso sempre que tivermos determinado que não ocorreu uma violação.
-
-Se você procurar restabelecer ou recorrer de uma ação de execução, entre em contato com [suporte](https://support.github.com/contact?tags=docs-policy).
+If your content or account has been disabled or restricted and you seek reinstatement or wish to appeal, please see our [Appeal and Reinstatement page](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement) for information about the process and use our [Appeal and Reinstatement form](https://support.github.com/contact/reinstatement) to submit a request.
 
 ## Avisos Legais
 
diff --git a/translations/pt-BR/content/site-policy/privacy-policies/github-data-protection-agreement.md b/translations/pt-BR/content/site-policy/privacy-policies/github-data-protection-agreement.md
index b3d0f3a842..a85f1c83f7 100644
--- a/translations/pt-BR/content/site-policy/privacy-policies/github-data-protection-agreement.md
+++ b/translations/pt-BR/content/site-policy/privacy-policies/github-data-protection-agreement.md
@@ -378,7 +378,8 @@ Os detalhes das transferências e, em particular, as categorias de dados pessoai
 
 O exportador de dados garante que empregou esforços razoáveis para determinar se o importador de dados poderá, por meio da implementação de medidas técnicas e organizacionais adequadas, cumprir as suas obrigações ao abrigo destas Cláusulas.
 
-**8.1 Instruções** 
    
+**8.1 Instruções**
+  
      
       
    1. O importador de dados processará os dados pessoais somente com base em instruções documentadas do exportador de dados. O exportador de dados pode fornecer essas instruções durante o período do contrato.
      2. 
       
    2. O importador de dados informará imediatamente o exportador de dados se este não puder seguir essas instruções.
      3. 
   
    
diff --git a/translations/pt-BR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/pt-BR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
index dbb5acee22..654df34b29 100644
--- a/translations/pt-BR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
+++ b/translations/pt-BR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
@@ -42,13 +42,6 @@ upcoming_changes:
     date: '2020-07-01T00:00:00+00:00'
     criticality: breaking
     owner: BrentWheeldon
-  - 
-    location: EnterpriseOwnerInfo.pendingCollaborators
-    description: '`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso.'
-    reason: Os convites de repositório agora podem ser associados a um email, não apenas a um convidado.
-    date: '2020-10-01T00:00:00+00:00'
-    criticality: breaking
-    owner: jdennes
   - 
     location: Issue.timeline
     description: '`timeline` será removido. Use Issue.timelineItems em vez disso.'
@@ -63,13 +56,6 @@ upcoming_changes:
     date: '2020-10-01T00:00:00+00:00'
     criticality: breaking
     owner: mikesea
-  - 
-    location: RepositoryInvitationOrderField.INVITEE_LOGIN
-    description: '`INVITEE_LOGIN` será removido.'
-    reason: '`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado.'
-    date: '2020-10-01T00:00:00+00:00'
-    criticality: breaking
-    owner: jdennes
   - 
     location: EnterpriseMemberEdge.isUnlicensed
     description: '`isUnlicensed` será removido.'
@@ -84,13 +70,6 @@ upcoming_changes:
     date: '2021-01-01T00:00:00+00:00'
     criticality: breaking
     owner: BrentWheeldon
-  - 
-    location: EnterprisePendingCollaboratorEdge.isUnlicensed
-    description: '`isUnlicensed` será removido.'
-    reason: Todos os colaboradores pendentes consomem uma licença
-    date: '2021-01-01T00:00:00+00:00'
-    criticality: breaking
-    owner: BrentWheeldon
   - 
     location: MergeStateStatus.DRAFT
     description: 'O `DRAFT` será removido. Use PullRequest.isDraft.'
@@ -126,3 +105,17 @@ upcoming_changes:
     date: '2022-04-01'
     criticality: breaking
     owner: colinshum
+  - 
+    location: AddPullRequestToMergeQueueInput.branch
+    description: '`branch` will be removed.'
+    reason: PRs are added to the merge queue for the base branch, the `branch` argument is now a no-op
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jhunschejones
+  - 
+    location: Enterprise.userAccounts
+    description: '`userAccounts` will be removed. Use the `Enterprise.members` field instead.'
+    reason: The `Enterprise.userAccounts` field is being removed.
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
diff --git a/translations/pt-BR/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/pt-BR/data/graphql/ghec/graphql_upcoming_changes.public.yml
index d1c952e335..6740127d2e 100644
--- a/translations/pt-BR/data/graphql/ghec/graphql_upcoming_changes.public.yml
+++ b/translations/pt-BR/data/graphql/ghec/graphql_upcoming_changes.public.yml
@@ -49,13 +49,6 @@ upcoming_changes:
     date: '2020-07-01T00:00:00+00:00'
     criticality: breaking
     owner: BrentWheeldon
-  - 
-    location: EnterpriseOwnerInfo.pendingCollaborators
-    description: '`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso.'
-    reason: Os convites de repositório agora podem ser associados a um email, não apenas a um convidado.
-    date: '2020-10-01T00:00:00+00:00'
-    criticality: breaking
-    owner: jdennes
   - 
     location: Issue.timeline
     description: '`timeline` será removido. Use Issue.timelineItems em vez disso.'
@@ -70,13 +63,6 @@ upcoming_changes:
     date: '2020-10-01T00:00:00+00:00'
     criticality: breaking
     owner: mikesea
-  - 
-    location: RepositoryInvitationOrderField.INVITEE_LOGIN
-    description: '`INVITEE_LOGIN` será removido.'
-    reason: '`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado.'
-    date: '2020-10-01T00:00:00+00:00'
-    criticality: breaking
-    owner: jdennes
   - 
     location: Sponsorship.sponsor
     description: '`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso.'
@@ -98,13 +84,6 @@ upcoming_changes:
     date: '2021-01-01T00:00:00+00:00'
     criticality: breaking
     owner: BrentWheeldon
-  - 
-    location: EnterprisePendingCollaboratorEdge.isUnlicensed
-    description: '`isUnlicensed` será removido.'
-    reason: Todos os colaboradores pendentes consomem uma licença
-    date: '2021-01-01T00:00:00+00:00'
-    criticality: breaking
-    owner: BrentWheeldon
   - 
     location: MergeStateStatus.DRAFT
     description: 'O `DRAFT` será removido. Use PullRequest.isDraft.'
@@ -140,6 +119,20 @@ upcoming_changes:
     date: '2022-04-01'
     criticality: breaking
     owner: colinshum
+  - 
+    location: AddPullRequestToMergeQueueInput.branch
+    description: '`branch` will be removed.'
+    reason: PRs are added to the merge queue for the base branch, the `branch` argument is now a no-op
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jhunschejones
+  - 
+    location: Enterprise.userAccounts
+    description: '`userAccounts` will be removed. Use the `Enterprise.members` field instead.'
+    reason: The `Enterprise.userAccounts` field is being removed.
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
   - 
     location: Query.sponsorables.dependencyEcosystem
     description: '`dependencyEcosystem` será removido. Use o argumento do ecossistema.'
diff --git a/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml b/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml
index d1c952e335..6740127d2e 100644
--- a/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml
+++ b/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml
@@ -49,13 +49,6 @@ upcoming_changes:
     date: '2020-07-01T00:00:00+00:00'
     criticality: breaking
     owner: BrentWheeldon
-  - 
-    location: EnterpriseOwnerInfo.pendingCollaborators
-    description: '`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso.'
-    reason: Os convites de repositório agora podem ser associados a um email, não apenas a um convidado.
-    date: '2020-10-01T00:00:00+00:00'
-    criticality: breaking
-    owner: jdennes
   - 
     location: Issue.timeline
     description: '`timeline` será removido. Use Issue.timelineItems em vez disso.'
@@ -70,13 +63,6 @@ upcoming_changes:
     date: '2020-10-01T00:00:00+00:00'
     criticality: breaking
     owner: mikesea
-  - 
-    location: RepositoryInvitationOrderField.INVITEE_LOGIN
-    description: '`INVITEE_LOGIN` será removido.'
-    reason: '`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado.'
-    date: '2020-10-01T00:00:00+00:00'
-    criticality: breaking
-    owner: jdennes
   - 
     location: Sponsorship.sponsor
     description: '`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso.'
@@ -98,13 +84,6 @@ upcoming_changes:
     date: '2021-01-01T00:00:00+00:00'
     criticality: breaking
     owner: BrentWheeldon
-  - 
-    location: EnterprisePendingCollaboratorEdge.isUnlicensed
-    description: '`isUnlicensed` será removido.'
-    reason: Todos os colaboradores pendentes consomem uma licença
-    date: '2021-01-01T00:00:00+00:00'
-    criticality: breaking
-    owner: BrentWheeldon
   - 
     location: MergeStateStatus.DRAFT
     description: 'O `DRAFT` será removido. Use PullRequest.isDraft.'
@@ -140,6 +119,20 @@ upcoming_changes:
     date: '2022-04-01'
     criticality: breaking
     owner: colinshum
+  - 
+    location: AddPullRequestToMergeQueueInput.branch
+    description: '`branch` will be removed.'
+    reason: PRs are added to the merge queue for the base branch, the `branch` argument is now a no-op
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jhunschejones
+  - 
+    location: Enterprise.userAccounts
+    description: '`userAccounts` will be removed. Use the `Enterprise.members` field instead.'
+    reason: The `Enterprise.userAccounts` field is being removed.
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
   - 
     location: Query.sponsorables.dependencyEcosystem
     description: '`dependencyEcosystem` será removido. Use o argumento do ecossistema.'
diff --git a/translations/pt-BR/data/reusables/actions/usage-workflow-run-time.md b/translations/pt-BR/data/reusables/actions/usage-workflow-run-time.md
index 83c4302345..6abb26d2ef 100644
--- a/translations/pt-BR/data/reusables/actions/usage-workflow-run-time.md
+++ b/translations/pt-BR/data/reusables/actions/usage-workflow-run-time.md
@@ -1 +1 @@
-- **Tempo de execução do fluxo de trabalho** - Cada execução do fluxo de trabalho é limitada a 72 horas. Se a execução de um fluxo de trabalho atingir esse limite, a execução do fluxo de trabalho será cancelada.
+- **Workflow run time** - {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-6469 %}Each workflow run is limited to 35 days. Se a execução de um fluxo de trabalho atingir esse limite, a execução do fluxo de trabalho será cancelada. This period includes execution duration, and time spent on waiting and approval.{% else %}Each workflow run is limited to 72 hours. If a workflow run reaches this limit, the workflow run is cancelled.{% endif %}
diff --git a/translations/pt-BR/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md b/translations/pt-BR/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md
index 1506dbe44c..c7b2b48044 100644
--- a/translations/pt-BR/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md
+++ b/translations/pt-BR/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md
@@ -1,4 +1,6 @@
-1. Para adicionar o novo nó de substituição provisionado, em qualquer nó, modifique o arquivo `cluster.conf` para remover o nó com falha e adicionar o nó de substituição. Por exemplo, este arquivo modificado `cluster.conf` substitui `ghe-data-node-3` pelo novo nó provisionado, `ghe-replacement-data-node-3`: 
    +1. Para adicionar o novo nó de substituição provisionado, em qualquer nó, modifique o arquivo `cluster.conf` para remover o nó com falha e adicionar o nó de substituição. Por exemplo, este arquivo modificado `cluster.conf` substitui `ghe-data-node-3` pelo novo nó provisionado, `ghe-replacement-data-node-3`:
+
+  
       [cluster "ghe-replacement-data-node-3"]
     hostname = ghe-replacement-data-node-3
     ipv4 = 192.168.0.7
diff --git a/translations/pt-BR/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md b/translations/pt-BR/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md
index 132d61ff33..b3b0aeb594 100644
--- a/translations/pt-BR/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md
+++ b/translations/pt-BR/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md
@@ -1,6 +1,8 @@
 1. Se você estiver substituindo o nó primário do MySQL ou Redis, no `cluster.conf`, modifique o valor de `mysql-master` ou `redis-master` com o nome do nó de substituição.
 
-  Por exemplo, o arquivo `cluster.conf` modificado especifica um novo nó de cluster provisionado, `ghe-replacement-data-node-1` como o nó principal do MySQL e do Redis: 
    +  Por exemplo, o arquivo `cluster.conf` modificado especifica um novo nó de cluster provisionado, `ghe-replacement-data-node-1` como o nó principal do MySQL e do Redis:
+
+  
       mysql-master = ghe-replacement-data-node-1
   redis-master = ghe-replacement-data-node-1
   
    
diff --git a/translations/pt-BR/data/reusables/pull_requests/merge-queue-merging-method.md b/translations/pt-BR/data/reusables/pull_requests/merge-queue-merging-method.md
index d1f2bac8d7..835c80cbc7 100644
--- a/translations/pt-BR/data/reusables/pull_requests/merge-queue-merging-method.md
+++ b/translations/pt-BR/data/reusables/pull_requests/merge-queue-merging-method.md
@@ -1,2 +1,3 @@
-Once CI checks pass, {% data variables.product.product_name %} merges the pull request by fast-forwarding the default branch. The merge queue will use merge commits if the "Require linear history" branch protection setting is turned off, and the "Rebase and merge" method otherwise. 
- 
+{% data variables.product.product_name %} merges the pull request according to the merge strategy configured in the branch protection once all required CI checks pass.
+
+![Merge queue merging method](/assets/images/help/pull_requests/merge-queue-merging-method.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/pull_requests/merge-queue-overview-short.md b/translations/pt-BR/data/reusables/pull_requests/merge-queue-overview-short.md
deleted file mode 100644
index 4b2b9145bf..0000000000
--- a/translations/pt-BR/data/reusables/pull_requests/merge-queue-overview-short.md
+++ /dev/null
@@ -1,3 +0,0 @@
-If repository administrators enable merge queues for pull requests targeting selected branches within a repository, contributors to these branches can add their pull requests to a merge queue once the required checks have passed.
-
-{% data variables.product.product_name %} will process the merge queue, and will merge the pull requests on your behalf if you're a contributor, by fast-forwarding the default branch.
diff --git a/translations/pt-BR/data/reusables/pull_requests/merge-queue-overview.md b/translations/pt-BR/data/reusables/pull_requests/merge-queue-overview.md
index 6e2a7cdd0f..2b04ff117f 100644
--- a/translations/pt-BR/data/reusables/pull_requests/merge-queue-overview.md
+++ b/translations/pt-BR/data/reusables/pull_requests/merge-queue-overview.md
@@ -1,5 +1,5 @@
-Merge queues for pull requests can increase the rate at which pull requests are merged into a busy default branch, whilst ensuring that CI checks pass.
+A merge queue can increase the rate at which pull requests are merged into a busy target branch while ensuring that all required branch protection checks pass.
 
-Merge queues use {% data variables.product.prodname_actions %}. For more information about actions, see "[{% data variables.product.prodname_actions %}](/actions/)."
+Once a pull request has passed all of the required branch protection checks, a user with write access to the repository can add that pull request to a merge queue.
 
-Once a pull request has passed any required checks and approvals, a contributor with write access can add the pull request to the merge queue. The queue then creates a temporary branch with that pull request and any pull requests ahead of it in the queue, and triggers any required continuous integration (CI) checks.
+A merge queue may use {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[{% data variables.product.prodname_actions %}](/actions/)".
diff --git a/translations/pt-BR/data/reusables/pull_requests/merge-queue-references.md b/translations/pt-BR/data/reusables/pull_requests/merge-queue-references.md
index a0247330e7..ed073e1647 100644
--- a/translations/pt-BR/data/reusables/pull_requests/merge-queue-references.md
+++ b/translations/pt-BR/data/reusables/pull_requests/merge-queue-references.md
@@ -1,2 +1,2 @@
 
-For more information about merge queues, see "[Using a merge queue](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue)."
+For information about merge queue, see "[Managing a merge queue](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)."
diff --git a/translations/pt-BR/data/reusables/pull_requests/merge-queue-reject.md b/translations/pt-BR/data/reusables/pull_requests/merge-queue-reject.md
index 49a59dca54..d7a40d1716 100644
--- a/translations/pt-BR/data/reusables/pull_requests/merge-queue-reject.md
+++ b/translations/pt-BR/data/reusables/pull_requests/merge-queue-reject.md
@@ -1,2 +1,2 @@
 
-If there are failed status checks or conflicts with the base branch, {% data variables.product.product_name %} will remove the pull request from the queue. The pull request timeline will display the reason why the pull request has been removed from the queue.
+After grouping a pull request with the latest version of the target branch and changes ahead of it in the queue, if there are failed required status checks or conflicts with the base branch, {% data variables.product.product_name %} will remove the pull request from the queue. The pull request timeline will display the reason why the pull request was removed from the queue.