run-name | github, inputs | |
+{%- endif %}
| concurrency | github, inputs | |
| env | github, secrets, inputs | |
| jobs.<job_id>.concurrency | github, needs, strategy, matrix, inputs | |
diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md
index 1f5c9d723f..b83df0ebe2 100644
--- a/translations/pt-BR/content/actions/quickstart.md
+++ b/translations/pt-BR/content/actions/quickstart.md
@@ -1,6 +1,6 @@
---
-title: Início rápido para GitHub Actions
-intro: 'Experimente as funcionalidades de {% data variables.product.prodname_actions %} em 5 minutos ou menos.'
+title: Quickstart for GitHub Actions
+intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.'
allowTitleToDifferFromFilename: true
redirect_from:
- /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates
@@ -13,84 +13,85 @@ type: quick_start
topics:
- Fundamentals
shortTitle: Quickstart
-ms.openlocfilehash: 164aef041c509264c9e8440d5339bce3cf4aaaca
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146139454'
---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
-## Introdução
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
-Você precisa apenas de um repositório de {% data variables.product.prodname_dotcom %} para criar e executar um fluxo de trabalho de {% data variables.product.prodname_actions %}. Neste guia, você adicionará um fluxo de trabalho que demonstra algumas das funcionalidades essenciais de {% data variables.product.prodname_actions %}.
+## Introduction
-O exemplo a seguir mostra como os trabalhos de {% data variables.product.prodname_actions %} podem ser acionados automaticamente, onde são executados e como podem interagir com o código no seu repositório.
+You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}.
-## Criar o seu primeiro fluxo de trabalho
+The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository.
-1. Crie um diretório `.github/workflows` no seu repositório do {% data variables.product.prodname_dotcom %} caso ele ainda não exista.
-2. No diretório `.github/workflows`, crie um novo arquivo chamado `github-actions-demo.yml`. Para obter mais informações, confira "[Como criar arquivos](/github/managing-files-in-a-repository/creating-new-files)".
-3. Copie o seguinte conteúdo YAML para o arquivo `github-actions-demo.yml`: {% raw %}
- ```yaml{:copy}
- name: GitHub Actions Demo
- on: [push]
- jobs:
- Explore-GitHub-Actions:
- runs-on: ubuntu-latest
- steps:
- - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."{% endraw %}
- - name: Check out repository code
- uses: {% data reusables.actions.action-checkout %}{% raw %}
- - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- - run: echo "🖥️ The workflow is now ready to test your code on the runner."
- - name: List files in the repository
- run: |
- ls ${{ github.workspace }}
- - run: echo "🍏 This job's status is ${{ job.status }}."
+## Creating your first workflow
- ```
- {% endraw %}
-3. Vá até o final da página e selecione **Criar um branch para este commit e iniciar uma solicitação de pull**. Em seguida, para criar uma solicitação de pull, clique em **Propor novo arquivo**.
- 
+1. Create a `.github/workflows` directory in your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist.
+1. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
+1. Copy the following YAML contents into the `github-actions-demo.yml` file:
-O commit do arquivo de fluxo de trabalho em um branch no repositório dispara o evento `push` e executa o fluxo de trabalho.
+ ```yaml{:copy}
+ name: GitHub Actions Demo
+ {%- ifversion actions-run-name %}
+ run-name: {% raw %}${{ github.actor }}{% endraw %} is testing out GitHub Actions 🚀
+ {%- endif %}
+ on: [push]
+ jobs:
+ Explore-GitHub-Actions:
+ runs-on: ubuntu-latest
+ steps:
+ - run: echo "🎉 The job was automatically triggered by a {% raw %}${{ github.event_name }}{% endraw %} event."
+ - run: echo "🐧 This job is now running on a {% raw %}${{ runner.os }}{% endraw %} server hosted by GitHub!"
+ - run: echo "🔎 The name of your branch is {% raw %}${{ github.ref }}{% endraw %} and your repository is {% raw %}${{ github.repository }}{% endraw %}."
+ - name: Check out repository code
+ uses: {% data reusables.actions.action-checkout %}
+ - run: echo "💡 The {% raw %}${{ github.repository }}{% endraw %} repository has been cloned to the runner."
+ - run: echo "🖥️ The workflow is now ready to test your code on the runner."
+ - name: List files in the repository
+ run: |
+ ls {% raw %}${{ github.workspace }}{% endraw %}
+ - run: echo "🍏 This job's status is {% raw %}${{ job.status }}{% endraw %}."
+ ```
+1. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
-## Visualizar os resultados do seu fluxo de trabalho
+ 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja ver.
+Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow.
- 
-1. Na lista de execuções do fluxo de trabalho, clique no nome da execução que você deseja visualizar.
+## Viewing your workflow results
- 
-1. Em **Trabalhos**, clique no trabalho **Explore-GitHub-Actions**.
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to see.
- 
-1. O registro mostra como cada uma das etapas foi processada. Expanda qualquer um dos passos para ver seus detalhes.
+ 
+1. From the list of workflow runs, click the name of the run you want to see.
- 
+ 
+1. Under **Jobs** , click the **Explore-GitHub-Actions** job.
+
+ 
+1. The log shows you how each of the steps was processed. Expand any of the steps to view its details.
+
+ 
- Por exemplo, você pode ver a lista de arquivos no repositório: 
+ For example, you can see the list of files in your repository:
+ 
-## Mais fluxos de trabalho iniciais
+## More starter workflows
{% data reusables.actions.workflow-template-overview %}
-## Exemplos mais complexos
+## More complex examples
{% data reusables.actions.link-to-example-library %}
-## Próximas etapas
+## Next steps
-O exemplo do fluxo de trabalho que você acabou de adicionar é executado cada vez que o código for enviado para o branch e mostra como {% data variables.product.prodname_actions %} pode funcionar com o conteúdo do seu repositório. Mas este é apenas o começo do que você pode fazer com o {% data variables.product.prodname_actions %}.
+The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}:
-- O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos.
-- Você pode usar um fluxo de trabalho para instalar aplicativos de teste de software e fazer com que testem automaticamente seu código nos executores de {% data variables.product.prodname_dotcom %}.
+- Your repository can contain multiple workflows that trigger different jobs based on different events.
+- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners.
-O {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_actions %}:
+{% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
-- "[Saiba como usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para ver um tutorial detalhado.
+- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial.
diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 5033dda0ed..0db7b2a3d4 100644
--- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -27,7 +27,23 @@ You must store workflow files in the `.github/workflows` directory of your repos
## `name`
-The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's actions page. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
+The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's "Actions" tab. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
+
+{% ifversion actions-run-name %}
+## `run-name`
+
+The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If you omit `run-name`, the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
+
+This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts.
+
+### Example
+
+{% raw %}
+```yaml
+run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
+```
+{% endraw %}
+{% endif %}
## `on`
diff --git a/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md
index c768525303..3944c4fa55 100644
--- a/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md
@@ -30,13 +30,15 @@ The {% data variables.product.prodname_serverless %} provides many of the benefi
The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.
+You must be signed in to use the web-based editor.
+
## Opening the {% data variables.product.prodname_serverless %}
You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways:
-- To open the repository in the same browser tab, press `.` while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
+- To open the repository in the same browser tab, press . while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
- To open the repository in a new browser tab, hold down the shift key and press `.`.
+ To open the repository in a new browser tab, press >.
- Change the URL from "github.com" to "github.dev".
- When viewing a file, use the dropdown menu next to {% octicon "pencil" aria-label="The edit icon" %} and select **Open in github.dev**.
diff --git a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
index 4516f39f99..bbd743e04a 100644
--- a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
@@ -50,7 +50,8 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
| Keyboard shortcut | Description
|-----------|------------{% ifversion fpt or ghec %}
-|. | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
+|. | Opens a repository or pull request in the web-based editor in the same browser tab. You must be signed in to use the editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."
+|> | Opens a repository or pull request in the web-based editor in a new browser tab. You must be signed in to use the editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
|Command+B (Mac) or Ctrl+B (Windows/Linux) | Inserts Markdown formatting for bolding text
|Command+I (Mac) or Ctrl+I (Windows/Linux) | Inserts Markdown formatting for italicizing text
|Command+K (Mac) or Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
index b9f2330d04..2910a6472f 100644
--- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
@@ -11,6 +11,7 @@ children:
- /managing-access-to-your-projects
- /closing-and-deleting-your-projects
- /adding-your-project-to-a-repository
+ - /adding-your-project-to-a-team
allowTitleToDifferFromFilename: true
ms.openlocfilehash: ca7c42e8dcb3daf477c70248eb79d12ca9670052
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
index eef3ab1749..e5f823f24e 100644
--- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
+++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
@@ -1,115 +1,117 @@
---
-title: 'Gerenciar o acesso aos {% data variables.projects.projects_v2 %}'
+title: 'Managing access to your {% data variables.projects.projects_v2 %}'
shortTitle: 'Managing {% data variables.projects.project_v2 %} access'
-intro: 'Saiba como gerenciar o acesso individual e de equipe ao seu {% data variables.projects.project_v2 %}.'
+intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.'
miniTocMaxHeadingLevel: 3
versions:
- feature: projects-v2
+ feature: "projects-v2"
redirect_from:
- /issues/trying-out-the-new-projects-experience/managing-access-to-projects
type: tutorial
topics:
- Projects
allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 05fa60d5690074c217db87cd52a44b46433c014e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423749'
---
-## Sobre o acesso ao projeto
-Os administradores de projetos no nível de organização podem gerenciar acesso para toda a organização, equipes, integrantes individuais da organização e para colaboradores externos.
-Os administradores de projetos de nível de usuário podem convidar colaboradores individuais e gerenciar seu acesso.
+## About project access
-Administradores do projeto também podem controlar a visibilidade do seu projeto para todos na internet. Para obter mais informações, confira "[Como gerenciar a visibilidade dos seus projetos](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)".
+Admins of organization-level projects can manage access for the entire organization, for teams, for individual organization members, and for outside collaborators.
-## Gerenciar acesso para projetos no nível da organização
+Admins of user-level projects can invite individual collaborators and manage their access.
-### Gerenciando o acesso para todos na sua organização
+Project admins can also control the visibility of their project for everyone on the internet. For more information, see "[Managing the visibility of your projects](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)."
-A função base padrão é `write`, o que significa que todos na organização podem ver e editar seu projeto. Para alterar o acesso ao projeto para todos da organização, você pode alterar a função-base. As alterações na função-base afetam apenas os integrantes da organização que não são proprietários da organização e a quem não é concedido acesso individual.
+## Managing access for organization-level projects
+
+### Managing access for everyone in your organization
+
+The default base role is `write`, meaning that everyone in the organization can see and edit your project. To change project access for everyone in the organization, you can change the base role. Changes to the base role only affect organization members who are not organization owners and who are not granted individual access.
{% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
- 
-2. Na **função Base**, selecione a função padrão.
- 
- - **Sem acesso**: somente os proprietários e os usuários da organização que receberam acesso individual podem ver o projeto. Os proprietários da organização também são administradores do projeto.
- - **Leitura**: todos na organização podem ver o projeto. Os proprietários da organização também são administradores do projeto.
- - **Gravação**: todos na organização podem ver e editar o projeto. Os proprietários da organização também são administradores do projeto.
- - **Administrador**: todos na organização são administradores do projeto.
+1. Click **Manage access**.
+ 
+2. Under **Base role**, select the default role.
+ 
+ - **No access**: Only organization owners and users granted individual access can see the project. Organization owners are also admins for the project.
+ - **Read**: Everyone in the organization can see the project. Organization owners are also admins for the project.
+ - **Write**: Everyone in the organization can see and edit the project. Organization owners are also admins for the project.
+ - **Admin**: Everyone in the organization is an admin for the project.
-### Gerenciando o acesso de equipes e integrantes individuais da sua organização
+### Managing access for teams and individual members of your organization
-Também é possível adicionar equipes, colaboradores externos e integrantes da organização individuais como colaboradores em um projeto no nível da organização. Para obter mais informações, confira "[Sobre as equipes](/organizations/organizing-members-into-teams/about-teams)".
+You can also add teams, external collaborators, and individual organization members as collaborators for an organization-level project. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
-Você pode apenas convidar um usuário individual para colaborar no projeto a nível da organização se ele já for integrante da organização ou colaborador externo em pelo menos um repositório na organização.
+{% ifversion projects-v2-add-to-team %}
+
+If you grant a team read permissions or greater for a project, the project is also displayed on the team's projects page. You can also add projects to a team on the team's projects page. For more information, see "[Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)."
+
+{% endif %}
+
+You can only invite an individual user to collaborate on your organization-level project if they are already a member of the organization or an outside collaborator on at least one repository in the organization.
{% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
- 
-2. Em **Convidar colaboradores**, procure a equipe ou o usuário individual que deseja convidar.
- 
-3. Selecione a função para o colaborador.
- 
- - **Leitura**: a equipe ou a pessoa pode ver o projeto.
- - **Gravação**: a equipe ou a pessoa pode ver e editar o projeto.
- - **Administrador**: a equipe ou a pessoa pode ver, editar e adicionar novos colaboradores ao projeto.
-4. Clique em **Convidar**.
- 
+1. Click **Manage access**.
+ 
+2. Under **Invite collaborators**, search for the team or individual user that you want to invite.
+ 
+3. Select the role for the collaborator.
+ 
+ - **Read**: The team or individual can view the project.
+ - **Write**: The team or individual can view and edit the project.
+ - **Admin**: The team or individual can view, edit, and add new collaborators to the project.
+4. Click **Invite**.
+ 
-### Gerenciando o acesso de um colaborador existente no seu projeto
+### Managing access of an existing collaborator on your project
{% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
- 
-1. Em **Gerenciar acesso**, localize os colaboradores cujas permissões você deseja modificar.
+1. Click **Manage access**.
+ 
+1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
- Use os menus suspensos **Tipo** e **Função** para filtrar a lista de acesso.
- 
+ You can use the **Type** and **Role** drop-down menus to filter the access list.
+ 
-1. Edite a função dos colaboradores.
- 
-1. Como opção, clique em **Remover** para remover os colaboradores.
- 
+1. Edit the role for the collaborator(s).
+ 
+1. Optionally, click **Remove** to remove the collaborator(s).
+ 
-## Gerenciando acesso para projetos no nível do usuário
+## Managing access for user-level projects
-### Concedendo acesso de colaborador ao seu projeto
+### Granting a collaborator access to your project
{% note %}
-Isto afeta apenas os colaboradores do projeto, não os repositórios do projeto. Para visualizar um item no projeto, alguém deverá ter as permissões necessárias para o repositório ao qual o item pertence. Se o seu projeto incluir itens de um repositório privado, pessoas que não forem colaboradores no repositório não poderão visualizar os itens desse repositório. Para obter mais informações, confira "[Como configurar a visibilidade do repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" e "[Como gerenciar equipes e pessoas com acesso no seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)".
+This only affects collaborators for your project, not for repositories in your project. To view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository. For more information, see "[Setting repository visibility](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
{% endnote %}
{% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
- 
-2. Em **Convidar colaboradores**, procure o usuário que deseja convidar.
- 
-3. Selecione a função para o colaborador.
- 
- - **Leitura**: a pessoa pode ver o projeto.
- - **Gravação**: a pessoa pode ver e editar o projeto.
- - **Administrador**: a pessoa pode ver, editar e adicionar novos colaboradores ao projeto.
-4. Clique em **Convidar**.
- 
+1. Click **Manage access**.
+ 
+2. Under **Invite collaborators**, search for the user that you want to invite.
+ 
+3. Select the role for the collaborator.
+ 
+ - **Read**: The individual can view the project.
+ - **Write**: The individual can view and edit the project.
+ - **Admin**: The individual can view, edit, and add new collaborators to the project.
+4. Click **Invite**.
+ 
-### Gerenciando o acesso de um colaborador existente no seu projeto
+### Managing access of an existing collaborator on your project
{% data reusables.projects.project-settings %}
-1. Clique em **Gerenciar acesso**.
- 
-1. Em **Gerenciar acesso**, localize os colaboradores cujas permissões você deseja modificar.
+1. Click **Manage access**.
+ 
+1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
- Use os menus suspensos **Tipo** e **Função** para filtrar a lista de acesso.
- 
+ You can use the **Type** and **Role** drop-down menus to filter the access list.
+ 
-1. Edite a função dos colaboradores.
- 
-1. Como opção, clique em **Remover** para remover os colaboradores.
- 
+1. Edit the role for the collaborator(s).
+ 
+1. Optionally, click **Remove** to remove the collaborator(s).
+ 
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index d628f4d73e..522bc91b7a 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -1,6 +1,6 @@
---
-title: 'Gerenciar o acesso de uma equipe ao {% data variables.product.prodname_project_v1 %} de uma organização'
-intro: 'Como proprietário da organização ou administrador do {% data variables.projects.projects_v1_board %}, você pode dar a uma equipe acesso a um {% data variables.projects.projects_v1_board %} pertencente à sua organização.'
+title: Managing team access to an organization {% data variables.product.prodname_project_v1 %}
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
redirect_from:
- /articles/managing-team-access-to-an-organization-project-board
- /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board
@@ -14,46 +14,58 @@ topics:
- Teams
shortTitle: Manage team access
allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 9672dddc31d39349ec99488313e021bca0c12c60
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422858'
---
+
{% data reusables.projects.project_boards_old %}
{% warning %}
-**Avisos:**
-- Você pode alterar os níveis de permissões de uma equipe se ela tiver acesso direto a um {% data variables.projects.projects_v1_board %}. Se o acesso da equipe ao {% data variables.projects.projects_v1_board %} for herdado de uma equipe pai, você deverá alterar o acesso da equipe pai para {% data variables.projects.projects_v1_board %}.
-- Se você adicionar ou remover acesso ao {% data variables.projects.projects_v1_board %} para uma equipe pai, cada uma das equipes filho desse pai também receberá ou perderá o acesso ao {% data variables.projects.projects_v1_board %}. Para obter mais informações, confira "[Sobre as equipes](/articles/about-teams)".
+**Warnings:**
+- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}.
+- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. For more information, see "[About teams](/articles/about-teams)."
{% endwarning %}
-## Dar a uma equipe acesso a um {% data variables.projects.projects_v1_board %}
+## Giving a team access to a {% data variables.projects.projects_v1_board %}
-Você pode dar a toda uma equipe o mesmo nível de permissão para um {% data variables.projects.projects_v1_board %}.
+You can give an entire team the same permission level to a {% data variables.projects.projects_v1_board %}.
{% note %}
-**Observação:** {% data reusables.project-management.cascading-permissions %} Por exemplo, se um proprietário da organização dar a uma equipe permissões de leitura em um {% data variables.projects.projects_v1_board %} e um administrador do {% data variables.projects.projects_v1_board %} conceder permissões de administrador a esse quadro a um membro da equipe como um colaborador individual, essa pessoa terá permissões de administrador no {% data variables.projects.projects_v1_board %}. Para obter mais informações, confira "[Permissões de {% data variables.product.prodname_project_v1_caps %} para uma organização](/articles/project-board-permissions-for-an-organization)".
+**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the {% data variables.projects.projects_v1_board %}. For more information see, "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
{% endnote %}
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. Clique em **Projetos (clássicos)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %}
-8. Na barra lateral esquerda, clique em **Equipes**.
-9. Para adicionar uma equipe, clique em **Adicionar uma equipe: Selecionar equipe**. Depois, escolha uma equipe no menu suspenso ou pesquise a equipe que você deseja adicionar.
- 
-10. Ao lado do nome da equipe, use o menu suspenso usado para selecionar o nível de permissão desejado: **Leitura**, **Gravação** ou **Administrador**. 
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+8. In the left sidebar, click **Teams**.
+9. To add a team, click **Add a team: Select team**. Then, choose a team from the drop-down menu or search for the team you'd like to add.
+ 
+10. Next to the team name, use the drop-down menu to select the desired permission level: **Read**, **Write**, or **Admin**.
+ 
-## Configurar o acesso de uma equipe a um {% data variables.projects.projects_v1_board %}
+## Configuring a team's access to a {% data variables.projects.projects_v1_board %}
-Se o acesso de uma equipe a um {% data variables.projects.projects_v1_board %} for herdado de uma equipe pai, você deverá alterar o acesso da equipe pai ao{% data variables.projects.projects_v1_board %} para atualizar o acesso às equipes filho.
+If a team's access to a {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %} to update access to the child teams.
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %}
-4. Acima da conversa da equipe, clique em {% octicon "project" aria-label="The Projects icon" %} **Projetos**.
- 
-5. Para alterar os níveis de permissão, à direita do {% data variables.projects.projects_v1_board %} que deseja atualizar, use o menu suspenso. Para remover um {% data variables.projects.projects_v1_board %}, clique em **{% octicon "trash" aria-label="The trash icon" %}** .
- 
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.specific_team %}
+4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
+ 
+5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**.
+ 
+
+{% ifversion projects-v2-add-to-team %}
+
+## Further reading
+
+- [Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)
+
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md
index b866e36b70..2257eb1ecd 100644
--- a/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md
+++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md
@@ -49,9 +49,20 @@ You can search for archived repositories. For more information, see "[Searching
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", click **Archive this repository** or **Unarchive this repository**.
+3. Under "Danger Zone", click **Archive this repository**
4. Read the warnings.
-5. Type the name of the repository you want to archive or unarchive.
+5. Type the name of the repository you want to archive.
6. Click **I understand the consequences, archive this repository**.
+
+## Unarchiving a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Danger Zone", click **Unarchive this repository**
+ 
+4. Read the warnings.
+5. Type the name of the repository you want to unarchive.
+ 
+6. Click **I understand the consequences, unarchive this repository**.
diff --git a/translations/pt-BR/data/features/GH-advisory-db-erlang-support.yml b/translations/pt-BR/data/features/GH-advisory-db-erlang-support.yml
new file mode 100644
index 0000000000..2548be6c39
--- /dev/null
+++ b/translations/pt-BR/data/features/GH-advisory-db-erlang-support.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #6207.
+# We have added support for Elixir advisories to the Advisory Database.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-6207'
diff --git a/translations/pt-BR/data/features/actions-cache-list-delete-apis.yml b/translations/pt-BR/data/features/actions-cache-list-delete-apis.yml
new file mode 100644
index 0000000000..8cb742d808
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-cache-list-delete-apis.yml
@@ -0,0 +1,8 @@
+# Reference: #7340
+# Extends actions-cache-management.yml (Issue #6154)
+# Documentation for Actions cache list and delete APIs
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '> 3.6'
+ ghae: 'issue-7340'
diff --git a/translations/pt-BR/data/features/actions-hosted-runners.yml b/translations/pt-BR/data/features/actions-hosted-runners.yml
new file mode 100644
index 0000000000..d7b08dee74
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-hosted-runners.yml
@@ -0,0 +1,5 @@
+# Reference: #6458
+# Larger GitHub-hosted runners
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/actions-inherit-secrets-reusable-workflows.yml b/translations/pt-BR/data/features/actions-inherit-secrets-reusable-workflows.yml
new file mode 100644
index 0000000000..23f0487364
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-inherit-secrets-reusable-workflows.yml
@@ -0,0 +1,7 @@
+# Reference: #6920
+# Documentation for inheriting secrets from the calling workflow
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>= 3.6'
+ ghae: 'issue-6920'
diff --git a/translations/pt-BR/data/features/actions-job-summaries.yml b/translations/pt-BR/data/features/actions-job-summaries.yml
new file mode 100644
index 0000000000..b1da5052e0
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-job-summaries.yml
@@ -0,0 +1,7 @@
+# Reference: #6405
+# Documentation for job summaries for jobs on the workflow run summary page.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.5'
+ ghae: 'issue-6405'
diff --git a/translations/pt-BR/data/features/actions-oidc-hardening-config.yml b/translations/pt-BR/data/features/actions-oidc-hardening-config.yml
new file mode 100644
index 0000000000..bd23498113
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-oidc-hardening-config.yml
@@ -0,0 +1,6 @@
+# Reference: #7336
+# General versioning for oidc hardening options
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
diff --git a/translations/pt-BR/data/features/actions-reusable-workflow-matrix.yml b/translations/pt-BR/data/features/actions-reusable-workflow-matrix.yml
new file mode 100644
index 0000000000..cf3b99d4f9
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-reusable-workflow-matrix.yml
@@ -0,0 +1,7 @@
+# Reference: #7094
+# Documentation for allowing matrix jobs to call reusable workflows.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7094'
diff --git a/translations/pt-BR/data/features/actions-stable-actor-ids.yml b/translations/pt-BR/data/features/actions-stable-actor-ids.yml
new file mode 100644
index 0000000000..14ab57db8e
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-stable-actor-ids.yml
@@ -0,0 +1,7 @@
+# Issue 7387
+# Differentiating triggering actor from executing actor
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7387'
diff --git a/translations/pt-BR/data/features/actions-starter-template-ui.yml b/translations/pt-BR/data/features/actions-starter-template-ui.yml
new file mode 100644
index 0000000000..37e13246f1
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-starter-template-ui.yml
@@ -0,0 +1,7 @@
+# Reference: #5169.
+# Documentation for the Actions starter template UI updates
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.4'
+ ghae: 'issue-5169'
diff --git a/translations/pt-BR/data/features/actions-unified-inputs.yml b/translations/pt-BR/data/features/actions-unified-inputs.yml
new file mode 100644
index 0000000000..931447f5d0
--- /dev/null
+++ b/translations/pt-BR/data/features/actions-unified-inputs.yml
@@ -0,0 +1,6 @@
+# Issue 6921
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6921'
diff --git a/translations/pt-BR/data/features/allow-actions-to-approve-pr.yml b/translations/pt-BR/data/features/allow-actions-to-approve-pr.yml
new file mode 100644
index 0000000000..0f1c36ad0e
--- /dev/null
+++ b/translations/pt-BR/data/features/allow-actions-to-approve-pr.yml
@@ -0,0 +1,7 @@
+# Reference: #6926.
+# Versioning for org policy settings for workflow PR approval permission. This is only org setting! For the later separate ship for the enterprise and repo setting, see the allow-actions-to-approve-pr-with-ent-repo flag.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.5'
+ ghae: 'issue-6926'
diff --git a/translations/pt-BR/data/features/audit-log-sso-response-events.yml b/translations/pt-BR/data/features/audit-log-sso-response-events.yml
new file mode 100644
index 0000000000..53f67d03b1
--- /dev/null
+++ b/translations/pt-BR/data/features/audit-log-sso-response-events.yml
@@ -0,0 +1,6 @@
+# Documentation for adding business.sso_response and org.sso_repsonse
+
+versions:
+ ghec: '*'
+ ghes: '>=3.8'
+ ghae: 'issue-7939'
diff --git a/translations/pt-BR/data/features/autolink-reference-alphanumeric.yml b/translations/pt-BR/data/features/autolink-reference-alphanumeric.yml
new file mode 100644
index 0000000000..abb953835f
--- /dev/null
+++ b/translations/pt-BR/data/features/autolink-reference-alphanumeric.yml
@@ -0,0 +1,7 @@
+# Reference: #7370.
+# Versioning for autolinks being able to accept alphanumeric chars.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7370'
diff --git a/translations/pt-BR/data/features/build-pages-with-actions.yml b/translations/pt-BR/data/features/build-pages-with-actions.yml
new file mode 100644
index 0000000000..458017e24d
--- /dev/null
+++ b/translations/pt-BR/data/features/build-pages-with-actions.yml
@@ -0,0 +1,5 @@
+# Issue 7584
+# Building Pages sites with Actions [GA]
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/bypass-branch-protections.yml b/translations/pt-BR/data/features/bypass-branch-protections.yml
new file mode 100644
index 0000000000..5c7d792866
--- /dev/null
+++ b/translations/pt-BR/data/features/bypass-branch-protections.yml
@@ -0,0 +1,7 @@
+# Issue: 6667
+# Description: Allow merging pull requests without complying with branch protection rules.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-6667'
diff --git a/translations/pt-BR/data/features/classic-project-visibility-permissions-or-projects-v2.yml b/translations/pt-BR/data/features/classic-project-visibility-permissions-or-projects-v2.yml
new file mode 100644
index 0000000000..83d76ca5c9
--- /dev/null
+++ b/translations/pt-BR/data/features/classic-project-visibility-permissions-or-projects-v2.yml
@@ -0,0 +1,7 @@
+# Issue 7720
+# Organization owners can restrict public classic projects /OR/ Projects V2
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-7720'
diff --git a/translations/pt-BR/data/features/classic-project-visibility-permissions.yml b/translations/pt-BR/data/features/classic-project-visibility-permissions.yml
new file mode 100644
index 0000000000..277aaaf083
--- /dev/null
+++ b/translations/pt-BR/data/features/classic-project-visibility-permissions.yml
@@ -0,0 +1,7 @@
+# Issue 7720
+# Organization owners can restrict public classic projects.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-7720'
diff --git a/translations/pt-BR/data/features/code-scanning-exclude-queries-from-analysis.yml b/translations/pt-BR/data/features/code-scanning-exclude-queries-from-analysis.yml
new file mode 100644
index 0000000000..ee8634cf6b
--- /dev/null
+++ b/translations/pt-BR/data/features/code-scanning-exclude-queries-from-analysis.yml
@@ -0,0 +1,7 @@
+# Issue 7617
+# Users can easily exclude CodeQL queries from code scanning analyses - [GA]
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-7617'
diff --git a/translations/pt-BR/data/features/code-scanning-task-lists.yml b/translations/pt-BR/data/features/code-scanning-task-lists.yml
new file mode 100644
index 0000000000..29408f5d1f
--- /dev/null
+++ b/translations/pt-BR/data/features/code-scanning-task-lists.yml
@@ -0,0 +1,4 @@
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghae: 'issue-5036'
diff --git a/translations/pt-BR/data/features/codeql-action-debug-logging.yml b/translations/pt-BR/data/features/codeql-action-debug-logging.yml
new file mode 100644
index 0000000000..76008d8e4c
--- /dev/null
+++ b/translations/pt-BR/data/features/codeql-action-debug-logging.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #2499 in the codeql-core repository, and issue #7626 in the docs-content repository
+# We have added one-click re-running in debug mode for code scanning CodeQL.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-7626'
diff --git a/translations/pt-BR/data/features/codeql-runner-supported.yml b/translations/pt-BR/data/features/codeql-runner-supported.yml
new file mode 100644
index 0000000000..897bc7a079
--- /dev/null
+++ b/translations/pt-BR/data/features/codeql-runner-supported.yml
@@ -0,0 +1,5 @@
+# Tracking deprecation of CodeQL runner
+# https://github.blog/changelog/2022-04-05-codeql-runner-is-now-deprecated/
+
+versions:
+ ghes: '<=3.3'
diff --git a/translations/pt-BR/data/features/comment-dismissed-code-scanning-alert.yml b/translations/pt-BR/data/features/comment-dismissed-code-scanning-alert.yml
new file mode 100644
index 0000000000..2aba7b4d97
--- /dev/null
+++ b/translations/pt-BR/data/features/comment-dismissed-code-scanning-alert.yml
@@ -0,0 +1,5 @@
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-2191'
diff --git a/translations/pt-BR/data/features/commit-signoffs.yml b/translations/pt-BR/data/features/commit-signoffs.yml
new file mode 100644
index 0000000000..26fe611963
--- /dev/null
+++ b/translations/pt-BR/data/features/commit-signoffs.yml
@@ -0,0 +1,5 @@
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6049'
diff --git a/translations/pt-BR/data/features/commit-tree-view.yml b/translations/pt-BR/data/features/commit-tree-view.yml
new file mode 100644
index 0000000000..249c627ec1
--- /dev/null
+++ b/translations/pt-BR/data/features/commit-tree-view.yml
@@ -0,0 +1,7 @@
+# Issue 6662
+# Commit file tree view
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6662'
diff --git a/translations/pt-BR/data/features/create-branch-from-overview.yml b/translations/pt-BR/data/features/create-branch-from-overview.yml
new file mode 100644
index 0000000000..a51e624c41
--- /dev/null
+++ b/translations/pt-BR/data/features/create-branch-from-overview.yml
@@ -0,0 +1,5 @@
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-6670'
diff --git a/translations/pt-BR/data/features/custom-pattern-dry-run-ga.yml b/translations/pt-BR/data/features/custom-pattern-dry-run-ga.yml
new file mode 100644
index 0000000000..1533fe096d
--- /dev/null
+++ b/translations/pt-BR/data/features/custom-pattern-dry-run-ga.yml
@@ -0,0 +1,5 @@
+# Secret scanning: custom pattern dry run GA #7527
+versions:
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-7527'
diff --git a/translations/pt-BR/data/features/debug-reruns.yml b/translations/pt-BR/data/features/debug-reruns.yml
new file mode 100644
index 0000000000..320c5e6a88
--- /dev/null
+++ b/translations/pt-BR/data/features/debug-reruns.yml
@@ -0,0 +1,7 @@
+# Issue 6629
+# Enabling debug logging when re-running jobs or workflows
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6629'
diff --git a/translations/pt-BR/data/features/default-merge-squash-commit-message.yml b/translations/pt-BR/data/features/default-merge-squash-commit-message.yml
new file mode 100644
index 0000000000..301e82a199
--- /dev/null
+++ b/translations/pt-BR/data/features/default-merge-squash-commit-message.yml
@@ -0,0 +1,7 @@
+# Reference: issue #7597
+# Admin can control default PR merge/ squash commit messages
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7597'
diff --git a/translations/pt-BR/data/features/dependabot-alerts-development-label.yml b/translations/pt-BR/data/features/dependabot-alerts-development-label.yml
new file mode 100644
index 0000000000..6ebf9611d3
--- /dev/null
+++ b/translations/pt-BR/data/features/dependabot-alerts-development-label.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #6631 - Dependabot alerts: surface information about development dependencies - [GA]
+
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-6631'
diff --git a/translations/pt-BR/data/features/dependabot-alerts-dismissal-comment.yml b/translations/pt-BR/data/features/dependabot-alerts-dismissal-comment.yml
new file mode 100644
index 0000000000..255ea4a959
--- /dev/null
+++ b/translations/pt-BR/data/features/dependabot-alerts-dismissal-comment.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #7673 - Dependabot alerts: optional comment with dismissal - [GA]
+
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-7673'
diff --git a/translations/pt-BR/data/features/dependabot-alerts-vulnerable-calls.yml b/translations/pt-BR/data/features/dependabot-alerts-vulnerable-calls.yml
new file mode 100644
index 0000000000..5b3645f3c5
--- /dev/null
+++ b/translations/pt-BR/data/features/dependabot-alerts-vulnerable-calls.yml
@@ -0,0 +1,5 @@
+# Reference: Issue #6076 introduction of label for "vulnerable calls" in Dependabot alerts
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghae: 'issue-6076'
diff --git a/translations/pt-BR/data/features/dependabot-bulk-alerts.yml b/translations/pt-BR/data/features/dependabot-bulk-alerts.yml
new file mode 100644
index 0000000000..df64f29646
--- /dev/null
+++ b/translations/pt-BR/data/features/dependabot-bulk-alerts.yml
@@ -0,0 +1,6 @@
+# Reference: Issue #6076 ability to dismiss or re-open multiple Dependabot alerts
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.5'
+ ghae: 'issue-6628'
diff --git a/translations/pt-BR/data/features/dependabot-most-important-sort-option.yml b/translations/pt-BR/data/features/dependabot-most-important-sort-option.yml
new file mode 100644
index 0000000000..cf0c3b6f18
--- /dev/null
+++ b/translations/pt-BR/data/features/dependabot-most-important-sort-option.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #7510 - Dependabot alerts: "Most important" sort (prioritization score) - [GA]
+
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-7510'
diff --git a/translations/pt-BR/data/features/dependabot-settings-update-37.yml b/translations/pt-BR/data/features/dependabot-settings-update-37.yml
new file mode 100644
index 0000000000..bd8344f33b
--- /dev/null
+++ b/translations/pt-BR/data/features/dependabot-settings-update-37.yml
@@ -0,0 +1,6 @@
+# Reference: Issue #7044 Update repository settings for Dependabot to include shortcut for Version updates
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-7044'
diff --git a/translations/pt-BR/data/features/dependency-review-action-ghes.yml b/translations/pt-BR/data/features/dependency-review-action-ghes.yml
new file mode 100644
index 0000000000..5ce8fa024a
--- /dev/null
+++ b/translations/pt-BR/data/features/dependency-review-action-ghes.yml
@@ -0,0 +1,4 @@
+# Reference: Issue #7753 Dependency review action has shipped with GHES 3.6 and needs admin docs
+versions:
+ ghes: '>3.5'
+ ghae: 'issue-7753'
diff --git a/translations/pt-BR/data/features/dependency-review-action-licenses.yml b/translations/pt-BR/data/features/dependency-review-action-licenses.yml
new file mode 100644
index 0000000000..ec85ab9be0
--- /dev/null
+++ b/translations/pt-BR/data/features/dependency-review-action-licenses.yml
@@ -0,0 +1,4 @@
+# Reference: Issue #7486 Configuring the dependency review action - [Public Beta] for GHES
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/dependency-submission-api.yml b/translations/pt-BR/data/features/dependency-submission-api.yml
new file mode 100644
index 0000000000..6ab5ae4ed1
--- /dev/null
+++ b/translations/pt-BR/data/features/dependency-submission-api.yml
@@ -0,0 +1,7 @@
+# Reference: #6397
+# Documentation for dependency submission API (beta)
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.6'
+ ghae: 'issue-6397'
diff --git a/translations/pt-BR/data/features/device-flow-is-opt-in.yml b/translations/pt-BR/data/features/device-flow-is-opt-in.yml
new file mode 100644
index 0000000000..543d525448
--- /dev/null
+++ b/translations/pt-BR/data/features/device-flow-is-opt-in.yml
@@ -0,0 +1,6 @@
+# docs-content 6307. OAuth device auth flow is opt in.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.4'
+ ghae: 'issue-6307'
diff --git a/translations/pt-BR/data/features/discussions.yml b/translations/pt-BR/data/features/discussions.yml
new file mode 100644
index 0000000000..66a3bb8592
--- /dev/null
+++ b/translations/pt-BR/data/features/discussions.yml
@@ -0,0 +1,4 @@
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
diff --git a/translations/pt-BR/data/features/docker-ghcr-enterprise-migration.yml b/translations/pt-BR/data/features/docker-ghcr-enterprise-migration.yml
new file mode 100644
index 0000000000..993fa2f523
--- /dev/null
+++ b/translations/pt-BR/data/features/docker-ghcr-enterprise-migration.yml
@@ -0,0 +1,4 @@
+# Reference: #7360
+# Documentation for migration from Docker registry to Container registry for enterprise products
+versions:
+ ghes: '>= 3.6'
diff --git a/translations/pt-BR/data/features/enable-git-events.yml b/translations/pt-BR/data/features/enable-git-events.yml
new file mode 100644
index 0000000000..29ac43099f
--- /dev/null
+++ b/translations/pt-BR/data/features/enable-git-events.yml
@@ -0,0 +1,5 @@
+# Reference: #7283
+# Documentation for enabling Git events in the audit log
+versions:
+ ghes: '>=3.5'
+ ghae: 'issue-7283'
diff --git a/translations/pt-BR/data/features/enterprise-membership-view-improvements.yml b/translations/pt-BR/data/features/enterprise-membership-view-improvements.yml
new file mode 100644
index 0000000000..27d315b816
--- /dev/null
+++ b/translations/pt-BR/data/features/enterprise-membership-view-improvements.yml
@@ -0,0 +1,4 @@
+versions:
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6344'
diff --git a/translations/pt-BR/data/features/enterprise-namespace-repo-setting.yml b/translations/pt-BR/data/features/enterprise-namespace-repo-setting.yml
new file mode 100644
index 0000000000..0902b94af9
--- /dev/null
+++ b/translations/pt-BR/data/features/enterprise-namespace-repo-setting.yml
@@ -0,0 +1,6 @@
+# Reference: #7757
+# Setting to disable personal namespace repo creation for EMUs, GHES 3.7+ and GHAE 3.7+ users
+versions:
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7757'
diff --git a/translations/pt-BR/data/features/enterprise-owner-join-org.yml b/translations/pt-BR/data/features/enterprise-owner-join-org.yml
new file mode 100644
index 0000000000..7ed560a15f
--- /dev/null
+++ b/translations/pt-BR/data/features/enterprise-owner-join-org.yml
@@ -0,0 +1,4 @@
+versions:
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-5740'
diff --git a/translations/pt-BR/data/features/file-finder-exclusion-controls.yml b/translations/pt-BR/data/features/file-finder-exclusion-controls.yml
new file mode 100644
index 0000000000..3c23123536
--- /dev/null
+++ b/translations/pt-BR/data/features/file-finder-exclusion-controls.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #7579 - Improved file finder exclusion controls
+
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7579'
diff --git a/translations/pt-BR/data/features/geoJSON-with-MapBox.yml b/translations/pt-BR/data/features/geoJSON-with-MapBox.yml
new file mode 100644
index 0000000000..d53d3e1d6d
--- /dev/null
+++ b/translations/pt-BR/data/features/geoJSON-with-MapBox.yml
@@ -0,0 +1,5 @@
+# Reference: #7429
+# Dotcom now uses Azure maps for geoJSON, but GHES/AE will still use the existing MapBox system
+versions:
+ ghes: '*'
+ ghae: '*'
diff --git a/translations/pt-BR/data/features/ghas-enablement-webhook.yml b/translations/pt-BR/data/features/ghas-enablement-webhook.yml
new file mode 100644
index 0000000000..402540e12c
--- /dev/null
+++ b/translations/pt-BR/data/features/ghas-enablement-webhook.yml
@@ -0,0 +1,5 @@
+# docs-content 7314. GHAS enablement webhook
+versions:
+ ghec: '*'
+ ghes: '>= 3.6'
+ ghae: 'issue-7314'
diff --git a/translations/pt-BR/data/features/ghe-announce-dismiss.yml b/translations/pt-BR/data/features/ghe-announce-dismiss.yml
new file mode 100644
index 0000000000..f0efe090f4
--- /dev/null
+++ b/translations/pt-BR/data/features/ghe-announce-dismiss.yml
@@ -0,0 +1,5 @@
+# Reference: #2221.
+# Documentation for dismissing GHES announcement banner
+versions:
+ ghes: '>=3.6'
+ ghae: 'issue-6764'
diff --git a/translations/pt-BR/data/features/internal-actions.yml b/translations/pt-BR/data/features/internal-actions.yml
new file mode 100644
index 0000000000..e4420a21cf
--- /dev/null
+++ b/translations/pt-BR/data/features/internal-actions.yml
@@ -0,0 +1,4 @@
+versions:
+ ghec: '*'
+ ghes: '>=3.5'
+ ghae: 'issue-5610'
diff --git a/translations/pt-BR/data/features/ip-allow-list-address-check.yml b/translations/pt-BR/data/features/ip-allow-list-address-check.yml
new file mode 100644
index 0000000000..c4dda87a70
--- /dev/null
+++ b/translations/pt-BR/data/features/ip-allow-list-address-check.yml
@@ -0,0 +1,3 @@
+versions:
+ ghec: '*'
+ ghae: 'issue-7818'
diff --git a/translations/pt-BR/data/features/issue-close-reasons.yml b/translations/pt-BR/data/features/issue-close-reasons.yml
new file mode 100644
index 0000000000..13589fc25c
--- /dev/null
+++ b/translations/pt-BR/data/features/issue-close-reasons.yml
@@ -0,0 +1,7 @@
+# Issues 6363
+# Closed issue states
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6363'
diff --git a/translations/pt-BR/data/features/job-hooks-for-runners.yml b/translations/pt-BR/data/features/job-hooks-for-runners.yml
new file mode 100644
index 0000000000..568ccdec80
--- /dev/null
+++ b/translations/pt-BR/data/features/job-hooks-for-runners.yml
@@ -0,0 +1,7 @@
+# Reference: #6530
+# Running scripts before or after a job
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6530'
diff --git a/translations/pt-BR/data/features/keyboard-shortcut-accessibility-setting.yml b/translations/pt-BR/data/features/keyboard-shortcut-accessibility-setting.yml
new file mode 100644
index 0000000000..df13e39e00
--- /dev/null
+++ b/translations/pt-BR/data/features/keyboard-shortcut-accessibility-setting.yml
@@ -0,0 +1,7 @@
+# Reference: #4999.
+# Documentation for the security manager org-level role
+versions:
+ fpt: '*'
+ ghes: '>=3.4'
+ ghae: 'issue-5430'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/math.yml b/translations/pt-BR/data/features/math.yml
new file mode 100644
index 0000000000..82aceb6233
--- /dev/null
+++ b/translations/pt-BR/data/features/math.yml
@@ -0,0 +1,7 @@
+# Issues 6054
+# Math support using LaTeX syntax
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6054'
diff --git a/translations/pt-BR/data/features/mermaid.yml b/translations/pt-BR/data/features/mermaid.yml
new file mode 100644
index 0000000000..60c43d802c
--- /dev/null
+++ b/translations/pt-BR/data/features/mermaid.yml
@@ -0,0 +1,7 @@
+# Issues 5812 and 6172, also 6411
+# Mermaid syntax support, also ASCII STL and geoJSON/topoJSON syntax support
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-6172'
diff --git a/translations/pt-BR/data/features/motion-management.yml b/translations/pt-BR/data/features/motion-management.yml
new file mode 100644
index 0000000000..82f51d11f5
--- /dev/null
+++ b/translations/pt-BR/data/features/motion-management.yml
@@ -0,0 +1,7 @@
+# Issue 6523
+# Support for customizing the automatic playback of animated images in the web interface
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6523'
diff --git a/translations/pt-BR/data/features/multiple-accounts-one-workstation.yml b/translations/pt-BR/data/features/multiple-accounts-one-workstation.yml
new file mode 100644
index 0000000000..8f0bbb69e8
--- /dev/null
+++ b/translations/pt-BR/data/features/multiple-accounts-one-workstation.yml
@@ -0,0 +1,6 @@
+# Issue #7330
+# Documentation for managing multiple GitHub accounts on one workstation
+
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/nested-reusable-workflow.yml b/translations/pt-BR/data/features/nested-reusable-workflow.yml
new file mode 100644
index 0000000000..702f7ac1c1
--- /dev/null
+++ b/translations/pt-BR/data/features/nested-reusable-workflow.yml
@@ -0,0 +1,7 @@
+# Issues 7093
+# Reusable workflows can call other reusable workflows
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7093'
diff --git a/translations/pt-BR/data/features/org-profile-pin-private.yml b/translations/pt-BR/data/features/org-profile-pin-private.yml
new file mode 100644
index 0000000000..bd30226a3e
--- /dev/null
+++ b/translations/pt-BR/data/features/org-profile-pin-private.yml
@@ -0,0 +1,7 @@
+# Issue #6171
+# Documentation for the "Org profile pin private/internal repos"
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-6171'
diff --git a/translations/pt-BR/data/features/packages-npm-v2.yml b/translations/pt-BR/data/features/packages-npm-v2.yml
new file mode 100644
index 0000000000..aaebb7fbfc
--- /dev/null
+++ b/translations/pt-BR/data/features/packages-npm-v2.yml
@@ -0,0 +1,5 @@
+# Issue 7039
+# npm Package Registry Improvements (v2) GA
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/pages-custom-workflow.yml b/translations/pt-BR/data/features/pages-custom-workflow.yml
new file mode 100644
index 0000000000..94ab08b480
--- /dev/null
+++ b/translations/pt-BR/data/features/pages-custom-workflow.yml
@@ -0,0 +1,5 @@
+# Issue 7066
+# Publishing Pages via custom Actions workflow
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/partial-reruns-with-reusable.yml b/translations/pt-BR/data/features/partial-reruns-with-reusable.yml
new file mode 100644
index 0000000000..4ef640e20f
--- /dev/null
+++ b/translations/pt-BR/data/features/partial-reruns-with-reusable.yml
@@ -0,0 +1,6 @@
+# Issue #7062
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.5'
+ ghae: 'issue-7062'
diff --git a/translations/pt-BR/data/features/pr-tree-view.yml b/translations/pt-BR/data/features/pr-tree-view.yml
new file mode 100644
index 0000000000..7e93dea288
--- /dev/null
+++ b/translations/pt-BR/data/features/pr-tree-view.yml
@@ -0,0 +1,7 @@
+# Issue 5892
+# PR file tree view
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-5892'
diff --git a/translations/pt-BR/data/features/project-beta-webhooks.yml b/translations/pt-BR/data/features/project-beta-webhooks.yml
new file mode 100644
index 0000000000..757aa1a65b
--- /dev/null
+++ b/translations/pt-BR/data/features/project-beta-webhooks.yml
@@ -0,0 +1,5 @@
+# Issue 6981
+# Projects (beta) webhooks
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/projects-oauth-scope.yml b/translations/pt-BR/data/features/projects-oauth-scope.yml
new file mode 100644
index 0000000000..5e7e86fd1c
--- /dev/null
+++ b/translations/pt-BR/data/features/projects-oauth-scope.yml
@@ -0,0 +1,5 @@
+# Issue 7302
+# ProjectV2 GraphQL API
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/projects-v1.yml b/translations/pt-BR/data/features/projects-v1.yml
new file mode 100644
index 0000000000..c217fc003d
--- /dev/null
+++ b/translations/pt-BR/data/features/projects-v1.yml
@@ -0,0 +1,8 @@
+# Issue 6980
+# Projects (classic)
+# n.b. /managing-project-boards/copying-a-project-board.md retains ghec/fpt versioning.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '*'
+ ghae: '*'
diff --git a/translations/pt-BR/data/features/projects-v2.yml b/translations/pt-BR/data/features/projects-v2.yml
new file mode 100644
index 0000000000..54ea4f28ad
--- /dev/null
+++ b/translations/pt-BR/data/features/projects-v2.yml
@@ -0,0 +1,6 @@
+# Issue 6980
+# ProjectV2 GA
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghae: 'issue-6980'
diff --git a/translations/pt-BR/data/features/push-protection-custom-link-orgs-beta.yml b/translations/pt-BR/data/features/push-protection-custom-link-orgs-beta.yml
new file mode 100644
index 0000000000..c418fb2a45
--- /dev/null
+++ b/translations/pt-BR/data/features/push-protection-custom-link-orgs-beta.yml
@@ -0,0 +1,8 @@
+# Issue 7299
+# Push protection custom links beta flags
+# See "push-protection-custom-link-orgs" for the feature
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7299'
diff --git a/translations/pt-BR/data/features/push-protection-custom-link-orgs.yml b/translations/pt-BR/data/features/push-protection-custom-link-orgs.yml
new file mode 100644
index 0000000000..56d088a28e
--- /dev/null
+++ b/translations/pt-BR/data/features/push-protection-custom-link-orgs.yml
@@ -0,0 +1,8 @@
+# Issue 7299
+# Push protection custom links
+# See "push-protection-custom-link-orgs-beta" for the beta flags
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7299'
diff --git a/translations/pt-BR/data/features/re-run-jobs.yml b/translations/pt-BR/data/features/re-run-jobs.yml
new file mode 100644
index 0000000000..31a13136ba
--- /dev/null
+++ b/translations/pt-BR/data/features/re-run-jobs.yml
@@ -0,0 +1,7 @@
+# Issue 4722
+# Re-running failed jobs in an Actions workflow
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.5'
+ ghae: 'issue-4722'
diff --git a/translations/pt-BR/data/features/remove-enterprise-members.yml b/translations/pt-BR/data/features/remove-enterprise-members.yml
new file mode 100644
index 0000000000..cdeeceb969
--- /dev/null
+++ b/translations/pt-BR/data/features/remove-enterprise-members.yml
@@ -0,0 +1,3 @@
+versions:
+ ghec: '*'
+ ghae: 'issue-5739'
diff --git a/translations/pt-BR/data/features/require-tls-for-smtp.yml b/translations/pt-BR/data/features/require-tls-for-smtp.yml
new file mode 100644
index 0000000000..4f9de7ca76
--- /dev/null
+++ b/translations/pt-BR/data/features/require-tls-for-smtp.yml
@@ -0,0 +1,4 @@
+# Reference 7394
+# Documentation for the option to enforce TLS encryption for incoming SMTP connections
+versions:
+ ghes: '>=3.6'
diff --git a/translations/pt-BR/data/features/required-deployments.yml b/translations/pt-BR/data/features/required-deployments.yml
new file mode 100644
index 0000000000..c1b7fc94d1
--- /dev/null
+++ b/translations/pt-BR/data/features/required-deployments.yml
@@ -0,0 +1,7 @@
+# Issue 6384
+# Required deployments branch protection rule
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.5'
+ ghae: 'issue-6384'
diff --git a/translations/pt-BR/data/features/secret-scanning-custom-enterprise-35.yml b/translations/pt-BR/data/features/secret-scanning-custom-enterprise-35.yml
new file mode 100644
index 0000000000..3b1d15f788
--- /dev/null
+++ b/translations/pt-BR/data/features/secret-scanning-custom-enterprise-35.yml
@@ -0,0 +1,6 @@
+# Issues: changes to custom patterns for secret scanning
+# #6367: updates for the "organization level dry runs (Public Beta)"
+# #5499: updates for the "repository level dry runs (Public Beta)"
+versions:
+ ghes: '>3.4 <3.7'
+ ghae: 'issue-6367'
diff --git a/translations/pt-BR/data/features/secret-scanning-custom-enterprise-36.yml b/translations/pt-BR/data/features/secret-scanning-custom-enterprise-36.yml
new file mode 100644
index 0000000000..a7bdd6be2e
--- /dev/null
+++ b/translations/pt-BR/data/features/secret-scanning-custom-enterprise-36.yml
@@ -0,0 +1,6 @@
+# Issues: changes to custom patterns for secret scanning
+# #6904: updates for "enterprise account level dry runs (Public Beta)"
+# #7297: updates for dry runs on editing patterns (Public Beta)
+versions:
+ ghes: '>3.5 <3.7'
+ ghae: 'issue-6904'
diff --git a/translations/pt-BR/data/features/secret-scanning-push-protection.yml b/translations/pt-BR/data/features/secret-scanning-push-protection.yml
new file mode 100644
index 0000000000..cdc8054e09
--- /dev/null
+++ b/translations/pt-BR/data/features/secret-scanning-push-protection.yml
@@ -0,0 +1,6 @@
+# Reference: #5620.
+# Documentation for secret scanning as a push protection
+versions:
+ ghes: '>=3.5'
+ ghae: 'issue-5620'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/security-advisories-ghes-ghae.yml b/translations/pt-BR/data/features/security-advisories-ghes-ghae.yml
new file mode 100644
index 0000000000..bec5d8f035
--- /dev/null
+++ b/translations/pt-BR/data/features/security-advisories-ghes-ghae.yml
@@ -0,0 +1,4 @@
+# Reference: Issue #6982 Community Contributions to Security Advisories - Enterprise 3.6
+versions:
+ ghes: '>=3.6'
+ ghae: 'issue-6982'
diff --git a/translations/pt-BR/data/features/security-overview-displayed-alerts.yml b/translations/pt-BR/data/features/security-overview-displayed-alerts.yml
new file mode 100644
index 0000000000..47e4cc9c48
--- /dev/null
+++ b/translations/pt-BR/data/features/security-overview-displayed-alerts.yml
@@ -0,0 +1,6 @@
+# Reference: #7114.
+# Documentation for security overview availability to all enterprise accounts.
+versions:
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7114'
diff --git a/translations/pt-BR/data/features/security-overview-feature-specific-alert-page.yml b/translations/pt-BR/data/features/security-overview-feature-specific-alert-page.yml
new file mode 100644
index 0000000000..a3ac7515ce
--- /dev/null
+++ b/translations/pt-BR/data/features/security-overview-feature-specific-alert-page.yml
@@ -0,0 +1,7 @@
+# Reference: #7028.
+# Documentation for feature-specific page for security overview at enterprise-level.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.5'
+ ghae: 'issue-7028'
diff --git a/translations/pt-BR/data/features/ssh-commit-verification.yml b/translations/pt-BR/data/features/ssh-commit-verification.yml
new file mode 100644
index 0000000000..87f1f3d243
--- /dev/null
+++ b/translations/pt-BR/data/features/ssh-commit-verification.yml
@@ -0,0 +1,8 @@
+# Reference: github/docs-content#6709
+# Initial docs for showing SSH signed commits as verified and
+# uploading SSH signing keys
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>= 3.7'
+ ghae: '*'
diff --git a/translations/pt-BR/data/features/svg-support.yml b/translations/pt-BR/data/features/svg-support.yml
new file mode 100644
index 0000000000..0203d64cb9
--- /dev/null
+++ b/translations/pt-BR/data/features/svg-support.yml
@@ -0,0 +1,5 @@
+# Releases issue #1951
+# Support upload of SVG files
+versions:
+ fpt: '*'
+ ghec: '*'
diff --git a/translations/pt-BR/data/features/syncing-fork-web-ui.yml b/translations/pt-BR/data/features/syncing-fork-web-ui.yml
new file mode 100644
index 0000000000..05f39707de
--- /dev/null
+++ b/translations/pt-BR/data/features/syncing-fork-web-ui.yml
@@ -0,0 +1,7 @@
+# Issue 7629
+# Improved UI for manually syncing a fork
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.7'
+ ghae: 'issue-7629'
diff --git a/translations/pt-BR/data/features/totp-and-mobile-sudo-challenge.yml b/translations/pt-BR/data/features/totp-and-mobile-sudo-challenge.yml
new file mode 100644
index 0000000000..caf7524585
--- /dev/null
+++ b/translations/pt-BR/data/features/totp-and-mobile-sudo-challenge.yml
@@ -0,0 +1,6 @@
+# TOTP and mobile challenge for sudo mode prompt.
+
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>= 3.7'
diff --git a/translations/pt-BR/data/features/upload-expired-or-revoked-gpg-key.yml b/translations/pt-BR/data/features/upload-expired-or-revoked-gpg-key.yml
new file mode 100644
index 0000000000..f11ff75cbd
--- /dev/null
+++ b/translations/pt-BR/data/features/upload-expired-or-revoked-gpg-key.yml
@@ -0,0 +1,8 @@
+# Issue: 7123
+# Description: Allow adding expired and revoked GPG keys for verifying commit and tag signatures
+# Usage: {% ifversion upload-expired-or-revoked-gpg-key %} ... {% endif %}
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>=3.6'
+ ghae: 'issue-7123'
diff --git a/translations/pt-BR/data/learning-tracks/admin.yml b/translations/pt-BR/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..5c6d8ced33
--- /dev/null
+++ b/translations/pt-BR/data/learning-tracks/admin.yml
@@ -0,0 +1,139 @@
+get_started_with_github_ae:
+ title: 'Introdução ao {% data variables.product.prodname_ghe_managed %}'
+ description: 'Saiba mais sobre {% data variables.product.prodname_ghe_managed %} e realize a configuração inicial de uma nova empresa.'
+ featured_track: true
+ versions:
+ ghae: '*'
+ guides:
+ - /admin/overview/about-github-ae
+ - /admin/overview/about-data-residency
+ - /admin/configuration/configuring-your-enterprise/deploying-github-ae
+ - /admin/configuration/initializing-github-ae
+ - /admin/configuration/restricting-network-traffic-to-your-enterprise
+ - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+
+deploy_an_instance:
+ title: 'Implante uma instância'
+ description: 'Instale {% data variables.product.prodname_ghe_server %} na sua plataforma de escolha e configure a autenticação SAML.'
+ featured_track: true
+ versions:
+ ghes: '*'
+ guides:
+ - /admin/overview/system-overview
+ - /admin/installation
+ - /admin/configuration/accessing-the-management-console
+ - /admin/configuration/configuring-a-hostname
+ - /admin/authentication/using-saml
+ - /admin/configuration/site-admin-dashboard
+
+upgrade_your_instance:
+ title: 'Atualize sua instância'
+ description: 'Teste as atualizações no treinamento, notifique os usuários de manutenção e atualize sua instância para os recursos e atualizações de segurança mais recentes.'
+ versions:
+ ghes: '*'
+ guides:
+ - /admin/enterprise-management/enabling-automatic-update-checks
+ - /admin/installation/setting-up-a-staging-instance
+ - /admin/enterprise-management/upgrade-requirements
+ - /admin/user-management/customizing-user-messages-for-your-enterprise
+ - /admin/configuration/enabling-and-scheduling-maintenance-mode
+ - /admin/enterprise-management/upgrading-github-enterprise-server
+
+adopting_github_actions_for_your_enterprise_ghec:
+ title: 'Adote o GitHub Actions na sua empresa'
+ description: 'Saiba como planejar e implementar uma implantação de {% data variables.product.prodname_actions %} na sua empresa.'
+ versions:
+ ghec: '*'
+ guides:
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
+ - /actions/learn-github-actions/understanding-github-actions
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
+ - /actions/security-guides/security-hardening-for-github-actions
+ - /billing/managing-billing-for-github-actions/about-billing-for-github-actions
+
+adopting_github_actions_for_your_enterprise_ghes_and_ghae:
+ title: 'Adote o GitHub Actions na sua empresa'
+ description: 'Saiba como planejar e implementar uma implantação de {% data variables.product.prodname_actions %} na sua empresa.'
+ versions:
+ ghes: '*'
+ ghae: '*'
+ guides:
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
+ - /actions/learn-github-actions/understanding-github-actions
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server
+ - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise
+ - /actions/security-guides/security-hardening-for-github-actions
+ - /billing/managing-billing-for-github-actions/about-billing-for-github-actions
+
+increase_fault_tolerance:
+ title: 'Aumente a tolerância de falha da instância'
+ description: "Faça backup do código de seus desenvolvedores e configure HA (alta disponibilidade) para garantir a confiabilidade do {% data variables.product.prodname_ghe_server %} em seu ambiente."
+ versions:
+ ghes: '*'
+ guides:
+ - /admin/configuration/accessing-the-administrative-shell-ssh
+ - /admin/configuration/configuring-backups-on-your-appliance
+ - /admin/enterprise-management/about-high-availability-configuration
+ - /admin/enterprise-management/creating-a-high-availability-replica
+ - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+
+improve_security_of_your_instance:
+ title: 'Melhore a segurança da sua instância'
+ description: "Revise a configuração de rede e as funcionalidades de segurança e reforce a instância do {% data variables.product.prodname_ghe_server %} em execução para proteger os dados da sua empresa."
+ versions:
+ ghes: '*'
+ guides:
+ - /admin/configuration/enabling-private-mode
+ - /admin/guides/installation/configuring-tls
+ - /admin/configuration/troubleshooting-ssl-errors
+ - /admin/configuration/enabling-subdomain-isolation
+ - /admin/configuration/accessing-the-administrative-shell-ssh
+ - /admin/configuration/network-ports
+ - /admin/configuration/configuring-built-in-firewall-rules
+ - /admin/user-management/best-practices-for-user-security
+ - /admin/user-management/promoting-or-demoting-a-site-administrator
+
+configure_github_actions:
+ title: 'Configure o {% data variables.product.prodname_actions %}'
+ description: 'Permita que seus desenvolvedores criem, automatizem, personalizem e executem fluxos de trabalho de desenvolvimento avançados de software em {% data variables.product.product_location %} com {% data variables.product.prodname_actions %}.'
+ versions:
+ ghes: '*'
+ guides:
+ - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+ - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+ - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+ - /admin/github-actions/high-availability-for-github-actions
+ - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+ - /admin/github-actions/using-a-staging-environment
+
+configure_github_advanced_security:
+ title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
+ description: "Melhore a qualidade e a segurança do código do seu desenvolvedor com {% data variables.product.prodname_GH_advanced_security %}."
+ versions:
+ ghes: '*'
+ guides:
+ - /admin/advanced-security/about-licensing-for-github-advanced-security
+ - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+ - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+ - /admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance
+ - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+ - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
+
+get_started_with_your_enterprise_account:
+ title: 'Comece a usar a sua conta corporativa'
+ description: 'Comece com sua conta corporativa para gerenciar centralmente várias organizações em {% data variables.product.product_name %}.'
+ versions:
+ ghes: '*'
+ ghec: '*'
+ guides:
+ - /admin/overview/about-enterprise-accounts
+ - /billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise
+ - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
+ - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
+ - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
+ - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
diff --git a/translations/pt-BR/data/learning-tracks/code-security.yml b/translations/pt-BR/data/learning-tracks/code-security.yml
index 115c9f45b7..52a08b1d42 100644
--- a/translations/pt-BR/data/learning-tracks/code-security.yml
+++ b/translations/pt-BR/data/learning-tracks/code-security.yml
@@ -1,7 +1,7 @@
# Feature available only on dotcom
security_advisories:
- title: 'Fix and disclose a security vulnerability'
- description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
+ title: 'Corrigir e divulgar uma vulnerabilidade de segurança'
+ description: 'Uso de consultorias de segurança do repositório para corrigir de forma privada uma vulnerabilidade relatada e obter um CVE.'
featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
guides:
- /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
@@ -15,8 +15,8 @@ security_advisories:
# Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
dependabot_alerts:
- title: 'Get notifications for insecure dependencies'
- description: 'Set up Dependabot to alert you to new vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your dependencies.'
+ title: 'Obter notificações para dependências inseguras'
+ description: 'Configure o Dependabot para alertar sobre novas vulnerabilidades{% ifversion GH-advisory-db-supports-malware %} ou malware{% endif %} em suas dependências.'
guides:
- /code-security/dependabot/dependabot-alerts/about-dependabot-alerts
- '{% ifversion fpt or ghec or ghes > 3.2 %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
@@ -28,8 +28,8 @@ dependabot_alerts:
# Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
dependabot_security_updates:
- title: 'Get pull requests to update your vulnerable dependencies'
- description: 'Set up Dependabot to create pull requests when new vulnerabilities are reported.'
+ title: 'Obtenha solicitações de pull para atualizar suas dependências vulneráveis'
+ description: 'Configure o Dependabot para criar solicitações de pull quando novas vulnerabilidades forem relatadas.'
guides:
- /code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates
- /code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates
@@ -40,8 +40,8 @@ dependabot_security_updates:
# Feature available only on dotcom and GHES 3.3+
dependency_version_updates:
- title: 'Keep your dependencies up-to-date'
- description: 'Use Dependabot to check for new releases and create pull requests to update your dependencies.'
+ title: 'Mantenha suas dependências atualizadas'
+ description: 'Use o Dependabot para verificar novas versões e criar solicitações de pull para atualizar suas dependências.'
guides:
- /code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates
- /code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates
@@ -56,8 +56,8 @@ dependency_version_updates:
# Feature available in GHEC, GHES 3.0 up, and GHAE. Feature limited on FPT so hidden there.
secret_scanning:
- title: 'Scan for secrets'
- description: 'Set up secret scanning to guard against accidental check-ins of tokens, passwords, and other secrets to your repository.'
+ title: 'Examinar em busca de segredos'
+ description: 'Configure o exame de segredos para evitar verificações acidentais de tokens, senhas e outros segredos do seu repositório.'
guides:
- '{% ifversion not fpt %}/code-security/secret-scanning/about-secret-scanning{% endif %}'
- '{% ifversion not fpt %}/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories{% endif %}'
@@ -69,8 +69,8 @@ secret_scanning:
# Security overview feature available in GHEC and GHES 3.2+, so other articles hidden to hide the learning path in other versions
security_alerts:
- title: 'Explore and manage security alerts'
- description: 'Learn where to find and resolve security alerts.'
+ title: 'Explore e gerencie alertas de segurança'
+ description: 'Saiba onde encontrar e como resolver alertas de segurança.'
guides:
- '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/about-the-security-overview {% endif %}'
- '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/viewing-the-security-overview {% endif %}'
@@ -81,8 +81,8 @@ security_alerts:
# Feature available in all versions from GHES 2.22 up
code_security_actions:
- title: 'Run code scanning with GitHub Actions'
- description: 'Check your default branch and every pull request to keep vulnerabilities and errors out of your repository.'
+ title: 'Execute o exame de código com o GitHub Actions'
+ description: 'Verifique seu branch padrão e cada solicitação de pull para manter seu repositório sem vulnerabilidades e erros.'
featured_track: '{% ifversion ghae or ghes %}true{% else %}false{% endif %}'
guides:
- /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
@@ -94,8 +94,8 @@ code_security_actions:
# Feature available in all versions from GHES 2.22 up
code_security_integration:
- title: 'Integrate with code scanning'
- description: 'Upload code analysis results from third-party systems to GitHub using SARIF.'
+ title: 'Integrar com o exame de código'
+ description: 'Faça o upload de resultados da análises de código de sistemas de terceiros para o GitHub usando o SARIF.'
guides:
- /code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning
- /code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github
@@ -104,8 +104,8 @@ code_security_integration:
# Feature available in all versions from GHES 2.22 up
code_security_ci:
- title: 'Run CodeQL code scanning in your CI'
- description: 'Set up CodeQL within your existing CI and upload results to GitHub code scanning.'
+ title: 'Execute o exame de código CodeQL na sua CI'
+ description: 'Configure o CodeQL dentro da sua CI existente e faça o upload dos resultados para o exame de código do GitHub.'
guides:
- /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
- /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system
@@ -115,8 +115,8 @@ code_security_ci:
# Feature available in all versions
end_to_end_supply_chain:
- title: 'End-to-end supply chain'
- description: 'How to think about securing your user accounts, your code, and your build process.'
+ title: 'Cadeia de suprimentos de ponta a ponta'
+ description: 'Como considerar a proteção de suas contas de usuário, códigos e processos de criação.'
guides:
- /code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview
- /code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/0.yml
new file mode 100644
index 0000000000..dc785881df
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/0.yml
@@ -0,0 +1,44 @@
+date: '2020-02-11'
+sections:
+ features:
+ - 'Em um branch de repositório, os administradores do repositório podem rejeitar qualquer push que contenha um commit de merge, habilitando "Exigir histórico linear" ao usar [regras de proteção de branch](https://help.github. om/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}'
+ - 'Os administradores de repositório podem conceder a todos os usuários com acesso push a capacidade de fazer push forçado para um branch protegido, habilitando "Permitir pushes forçados" e usando [regras de proteção de branch](https://help. ithub.com/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}'
+ - 'Os administradores do repositório podem conceder a todos os usuários com acesso push a capacidade de excluir um branch protegido, habilitando "Permitir exclusões" e usando [regras de proteção de branch](https://help.github. om/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}'
+ - 'Os administradores podem definir um limite "maxobjectsize" nos repositórios, [limitando o tamanho do commits de push](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) para um repositório que não estão em [Git LFS](https://help.github. om/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}'
+ - 'Os proprietários da organização podem criar um conjunto de etiquetas-padrão ao criar um novo repositório.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}'
+ security_fixes:
+ - Os pacotes foram atualizados para as últimas versões de segurança.
+ bugs:
+ - 'Quando um integrante de uma organização tentou visualizar um repositório público nessa organização, um prompt SSO poderia corromper a exibição da página. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}'
+ - "Ao visualizar o perfil de usuários, os links para as equipes dos usuários poderiam estar corrompidos. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}"
+ - 'Usuários com a função "manter" não conseguiram editar os tópicos do repositório. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}'
+ - "Um usuário que não é um administrador em uma organização receberá um erro 500 ao tentar acessar a página de inscrição. {% comment %} https://github. om/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}"
+ - 'O pop-up de histórico de edição não apareceria nos comentários do gist. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}'
+ - 'Foi possível registrar uma nova conta com um e-mail que já foi registrado. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}'
+ - 'Um serviço de armazenamento estava atingindo um limite de descritor de arquivos e deixando o kernel pendurado e outros serviços de log de erros. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}'
+ - 'Quando uma referência de link automático fazia parte de uma url, era possível remover o hiperlink. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}'
+ - 'Ao adicionar um comentário a um pull request, a seção "Problemas vinculados" da barra lateral poderia desaparecer. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}'
+ - 'Ao editar um convite existente de organização para um usuário, é possível que um cabeçalho duplicado apareça na tabela "Equipes". {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}'
+ - 'O serviço "resqued" conseguiu parar de registrar eventos quando as filas se tornaram grandes demais. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}'
+ - 'Certificados autoassinados não são gerados automaticamente ao executar o comando "ghe-config-apply" para cluster e alta disponibilidade. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}'
+ changes:
+ - 'Nenhum logotipo será exibido para um tópico se um não tiver sido carregado. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}'
+ - 'Ao ver um problema em um navegador móvel, os metadados do problema serão listados na parte superior da página. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}'
+ - 'O domínio de nível superior do Cônsul mudou de ".consul" para ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}'
+ - 'O serviço de hookshot não depende mais do ElasticSearch e usa apenas o MySQL como uma loja de banco de dados. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}'
+ - 'Implementou-se uma distinção visual aprimorada entre problema, projeto e discussão nos cartões de notas do projeto. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}'
+ - 'Em uma revisão de pull request, um aviso é exibido se um comentário linha múltipla for truncado. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}'
+ - 'Os usuários podem ver seus logs de auditoria na aba "Log de segurança" nas suas configurações pessoais. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}'
+ known_issues:
+ - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Arquivos LFS do Git [enviados através da interface Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de maneira incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'Ao efetuar push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
+ - "Entradas duplicadas de webhook no banco de dados podem gerar falha de atualizações de versões anteriores. (atualizada 2020-02-26)"
+ - 'As atualizações e as definições de atualização falharão se as configurações em segundo plano do trabalhador forem personalizadas. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}'
+ - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Ao atualizar de versões anteriores, os trabalhadores dos trabalho em segundo plano podem não ser gerados, evitando recursos essenciais como fazer mesclagem de solicitações de pull. (atualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}'
+ - 'Os alertas de segurança não são relatados ao efetuar push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'O grafo de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/14.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/14.yml
new file mode 100644
index 0000000000..9db47f4b27
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/14.yml
@@ -0,0 +1,13 @@
+date: '2020-08-12'
+sections:
+ bugs:
+ - 'Solucionado um problema que poderia gerar alto uso da CPU ao gerar modelos de configuração do sistema. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}'
+ - 'Alterações recentes nas alocações de memória podem gerar uma degradação no desempenho do sistema {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}'
+ known_issues:
+ - 'Em uma nova configuração do servidor do GitHub Enterprise sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'As regras personalizadas do firewall não são mantidas em uma atualização. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não são incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml
new file mode 100644
index 0000000000..01f9c1eed7
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml
@@ -0,0 +1,25 @@
+date: '2020-08-26'
+sections:
+ security_fixes:
+ - >-
+ {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
+ https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %}
+ - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}'
+ - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}'
+ bugs:
+ - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}'
+ - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}'
+ - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}"
+ - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}'
+ changes:
+ - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}'
+ - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}"
+ - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}'
+ known_issues:
+ - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'When a replica node is offline in a high availability configuration, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/17.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/17.yml
new file mode 100644
index 0000000000..8e91656787
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/17.yml
@@ -0,0 +1,13 @@
+date: '2020-09-23'
+sections:
+ security_fixes:
+ - '**MÉDIO**: ImageMagick foi atualizado para o endereço [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}'
+ - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}'
+ known_issues:
+ - 'Em uma nova configuração do servidor do GitHub Enterprise sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'As regras personalizadas do firewall não são mantidas em uma atualização. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não são incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/18.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/18.yml
new file mode 100644
index 0000000000..18b083cf4b
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/18.yml
@@ -0,0 +1,26 @@
+date: '2020-10-09'
+sections:
+ security_fixes:
+ - 'Um usuário, cujo nome de usuário de diretório de LDAP está padronizado em um login de conta GHES existente, pode efetuar a autenticação na conta existente. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}'
+ - 'Os pacotes foram atualizados para as versões de segurança mais recentes. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}'
+ bugs:
+ - 'O menu suspenso formato do ID do nome no Console de Gerenciamento seria redefinido para "não especificado" depois de configurado como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}'
+ - 'Salvar as configurações por meio do [console de gerenciamento](/admin/configuration/accessing-the-management-console) acrescentaria uma nova linha aos arquivos [certificado TLS/SSL e chave](/admin/configuration/configuring-tls) que acionou o recarregamento desnecessário de alguns serviços. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}'
+ - 'Os logs do sistema do Grafo de dependência não estavam em rotação, permitindo um crescimento ilimitado no armazenamento. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}'
+ - 'Os links para as Consultorias de Segurança do GitHub usariam uma URL com o nome de host da instância do GitHub Enterprise Server em vez do GitHub.com, direcionando o usuário para uma URL inexistente. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}'
+ - 'Importar um repositório com "ghe-migrator" poderá gerar uma exceção inesperada quando dados inconsistentes estiverem presentes. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}'
+ - 'Ao usar "ghe-migrator" para importar solicitações de revisão de PR, os registros associados com usuários excluídos resultariam em registros incorretos no banco de dados. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}'
+ - 'Ao importar usuários com "ghe-migrator", ocorreria o erro "Email é inválido" se o endereço de email gerado pelo sistema tivesse mais de 100 caracteres. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}'
+ - 'Registrar a atividade do webhook poderia usar uma grande quantidade de espaço no disco e fazer com que o disco raiz ficasse cheio. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}'
+ changes:
+ - 'O suporte é adicionado ao tipo de instância "m5.16xlarge" do AWS EC2. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}'
+ - 'Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}'
+ - 'Os manifestos do aplicativo GitHub agora incluem o campo "request_oauth_on_install". {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}'
+ known_issues:
+ - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Arquivos LFS do Git [enviados através da interface Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de maneira incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'Quando a opção "Usuários podem pesquisar no GitHub.com" está habilitada com o GitHub Connect, os problemas nos repositórios privados e internos não são incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Os alertas de segurança não são relatados ao efetuar push para um repositório com a linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/21.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/21.yml
new file mode 100644
index 0000000000..30da788556
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/21.yml
@@ -0,0 +1,15 @@
+date: '2020-11-17'
+sections:
+ security_fixes:
+ - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}'
+ bugs:
+ - 'Os logs de babeld não tinham um separador entre segundos e microssegundos. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}'
+ - 'Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}'
+ known_issues:
+ - 'Em uma nova configuração do servidor do GitHub Enterprise sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'As regras personalizadas do firewall não são mantidas em uma atualização. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não são incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/23.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/23.yml
new file mode 100644
index 0000000000..3d700229fa
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/23.yml
@@ -0,0 +1,13 @@
+date: '2020-12-17'
+sections:
+ security_fixes:
+ - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}'
+ - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}'
+ known_issues:
+ - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Arquivos LFS do Git [enviados através da interface Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de maneira incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/24.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/24.yml
new file mode 100644
index 0000000000..00e55b9137
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/24.yml
@@ -0,0 +1,28 @@
+date: '2021-03-02'
+sections:
+ security_fixes:
+ - '**ALTO:** Foi identificada uma vulnerabilidade de controle de acesso impróprio em GitHub Enterprise Server que permitia que usuários autenticados da instância obtivessem acesso de gravação à repositórios não autorizados via solicitações especificamente criadas de pull e de API REST. Um invasor precisaria ser capaz de bifurcar o repositório de destino, uma configuração que está desabilitada por padrão para repositórios privados pertencentes à organização. Proteções de branch como revisões de solicitação de pull ou verificações de status impediriam que commits não autorizados fossem mesclados sem revisão ou validação adicional. Esta vulnerabilidade foi designada CVE-2021-22861. Esse problema foi relatado pelo [Programa de Recompensas por Bugs do GitHub](https://bounty.github.com).'
+ - '**ALTO:** Foi identificada uma vulnerabilidade de controle de acesso impróprio na API do GitHub Enterprise Server GraphQL que permitia que usuários autenticados de instância modificassem a permissão de colaboração do mantenedor de uma solicitação de pull sem autorização adequada. Ao explorar esta vulnerabilidade, um invasor seria capaz de obter acesso aos branches principais de solicitações de pull abertas em repositórios dos quais é mantenedor. A bifurcação é desabilitada por padrão para repositórios privados pertencentes à organização e iriam evitar esta vulnerabilidade. Adicionalmente, as proteções de branch como revisões de solicitação de pull ou verificações de status impediriam que commits não autorizados fossem mesclados sem revisão ou validação adicional. Esta vulnerabilidade foi designada CVE-2021-22863. Esse problema foi relatado pelo [Programa de Recompensas por Bugs do GitHub](https://bounty.github.com).'
+ - '**ALTO:** Foi identificada uma vulnerabilidade de execução de código remoto no GitHub Enterprise Server que poderia ser explorada ao compilar um site GitHub Pages. A configuração controlada por usuário dos analisadores subjacentes usados pelo GitHub Pages não eram suficientemente restritos e tornaram possível executar comandos na instância do GitHub Enterprise Server. Para explorar esta vulnerabilidade, um invasor precisaria de permissão para criar e compilar um site GitHub Pages na instância do GitHub Enterprise Server. Essa vulnerabilidade foi designada CVE-2020-10519 e foi relatada pelo [Programa de Recompensas por Bugs do GitHub](https://bounty.github.com).'
+ - '**BAIXO:** Uma solicitação especialmente trabalhada para a ponte SVN poderia ser acionada muito tempo antes de a falha resultar em uma negação de serviço (DoS).'
+ - 'Os pacotes foram atualizados para as últimas versões de segurança.'
+ bugs:
+ - 'Uma mensagem informativa foi registrada involuntariamente como erro nos instantâneos dos utilitários do GitHub Enterprise Backup, o que gerou o envio de e-mails desnecessários quando os backups eram programados por trabalhos do cron que ouvem a saída para o stderr.'
+ - 'Ao restaurar um backup grande, o registro de exceções relacionado à exaustão de memória do Redis pode gerar falha na restauração devido a um disco completo.'
+ - 'Ao editar uma página wiki, um usuário pode ter um erro 500 ao clicar no botão Salvar.'
+ - 'Um commit S/MIME assinado utilizando um certificado com vários nomes no nome alternativo do assunto seria exibido incorretamente como "Não verificado" no selo do commit.'
+ - 'O usuário suspenso recebeu e-mails quando adicionado a uma equipe.'
+ - 'Ao fazer o upload de um novo arquivo de licença com um número diferente de estações do arquivo de licença anterior, a diferença de estações não estava corretamente representada nas configurações da conta corporativa -> página de licença.'
+ - 'A caixa de seleção "Evitar que os administradores do repositório alterem o acesso de leitura anônimo do Git, disponível nas configurações da conta corporativa, não pode ser habilitada ou desabilitada com sucesso.'
+ - 'Durante um ano bissexto, o usuário recebeu uma resposta 404 ao tentar ver a atividade de Contribuição na segunda-feira.'
+ changes:
+ - 'Adicionou-se suporte para [tipos de instância AWS EC2 r5b](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).'
+ - 'Priorização da fila de segundo plano ajustada para distribuir trabalhos de forma mais equilibrada.'
+ known_issues:
+ - 'Em uma nova configuração do GitHub Enterprise Server sem nenhum usuário, um invasor pode criar o primeiro usuário administrador.'
+ - 'As regras personalizadas de firewall não são mantidas durante uma atualização.'
+ - 'Arquivos LFS do Git [enviados através da interface da Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório onde o caminho do arquivo tem mais de 255 caracteres.'
+ - 'Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.'
+ - 'Os alertas de segurança não são relatados ao efetuar push em um repositório na linha de comando.'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/6.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/6.yml
new file mode 100644
index 0000000000..473c90290f
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/6.yml
@@ -0,0 +1,27 @@
+date: '2020-04-23'
+sections:
+ security_fixes:
+ - '**ALTO**: o OpenSSL foi atualizado para o endereço [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). {% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}'
+ - '**ALTO**: o Git foi atualizado para o endereço [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) e [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). Novas restrições evitam que seja feito o push de repositórios mal-intencionados para a instância de servidor, protegendo clientes que ainda não haviam recebido as correções. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}'
+ - '**BAIXO**: o ImageMagick foi atualizado para o endereço [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}'
+ - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}'
+ bugs:
+ - 'O usuário do Git não tinha permissões para invocar os processos necessários para converter repositórios existentes usando Subversion, do formato da v4 ao LRS da v3. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}'
+ - 'Uma incompatibilidade nas configurações do MySQL pode fazer com que os backups falhem em grandes instalações. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}'
+ - 'Ao atualizar de versões anteriores, trabalhadores em segundo plano às vezes não seriam gerados, o que impediria funcionalidades essenciais, como mesclar solicitações de pull. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}'
+ - 'Quando uma licença do GitHub Enterprise Server continha caracteres diferentes dos da ASCII, as solicitações do tipo "GET" para o ponto de extremidade "/setup/api/settings" da API do console de gerenciamento resultaria em um erro de servidor interno. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}'
+ - 'O console de recuperação solicitaria uma senha raiz, mesmo se a conta raiz estiver bloqueada. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}'
+ - 'Um arquivo CODEOWNERS com Marca de ordem de byte UTF-8 faria com que todas as regras de todos os códigos fossem ignoradas. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}'
+ changes:
+ - 'Quando o trabalho do cron do orchestrator-cliente falhou, vários emails foram enviados para a conta raiz. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}'
+ - 'Quando um provedor de identidade externo controlou o status de administrador do site do usuário, não foi possível rebaixar os usuários por meio do utilitário da linha de comando. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}'
+ known_issues:
+ - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Arquivos LFS do Git [enviados através da interface Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de maneira incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'Ao efetuar push em um gist, uma exceção poderia ser acionada durante o hook de pós-recebimento. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
+ - 'Quando a opção "Usuários podem pesquisar no GitHub.com" está habilitada com o GitHub Connect, os problemas nos repositórios privados e internos não são incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Os alertas de segurança não são relatados ao efetuar push para um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'O grafo de dependências não detecta dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-21/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-21/0.yml
new file mode 100644
index 0000000000..1169ba8e97
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-21/0.yml
@@ -0,0 +1,73 @@
+date: '2020-06-09'
+sections:
+ features:
+ - 'Os usuários podem [gerenciar notificações](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) sobre problemas, solicitações de pull e outros assuntos ao navegar a partir de uma notificação na web. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}'
+ - 'Os usuários podem [converter uma solicitação de pull novamente para um "Rascunho"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}'
+ - '[Sugestões de linha múltipla](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-disponibiliy/) permitem que um usuário sugira uma mudança específica em várias linhas de código ao analisar uma solicitação de pull. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}'
+ - 'Os usuários com acesso de gravação em um repositório podem [ocultar um comentário em um problema ou solicitação de pull como "Duplicado" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}'
+ - 'Ao [criar um repositório a partir de um modelo](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template), um usuário pode optar por incluir todas as ramificações, em vez apenas da ramificação padrão. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}'
+ - '[Os cartões de problemas de projeto incluem uma seção de solicitações de pull vinculada](https://github. log/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) para que um usuário possa ver qual trabalho de desenvolvimento está relacionado ao problema diretamente no quadro de projeto. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}'
+ - 'Há um conjunto novo de [Pontos de extremidade de "exclusão de reações"](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) na API de Reações. Os pontos de extremidade existentes de "exclusão de reações" serão preteridos no início de 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}'
+ - 'Há um novo conjunto de [Pontos de extremidade de API do Teams](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) que permitirão ao GitHub escalar e dar suporte à API do Teams a longo prazo. Os pontos de extremidade existentes de API serão preteridos no início de 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}'
+ - 'Os usuários podem [criar links entre problemas e solicitações de pull](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) sem a necessidade de usar palavras-chave de fechamento na descrição da solicitação de pull. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}'
+ security_fixes:
+ - 'Foi identificada uma vulnerabilidade de controle de acesso impróprio na API do GitHub Enterprise Server que permitia que um membro da organização escalonasse permissões e obtivesse acesso a repositórios não autorizados dentro de uma organização. Essa vulnerabilidade afetou todas as versões do GitHub Enterprise Server anteriores à 2.21. Emitimos [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) em resposta a esse problema. A vulnerabilidade foi relatada pelo [Programa de recompensas por bugs do GitHub](https://bounty.github.com). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}'
+ bugs:
+ - 'Se um usuário com acesso push minimizou o comentário de outro usuário, o autor do comentário poderia desfazer a minimização, mesmo se não tivesse privilégios suficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}'
+ - 'Os usuários poderiam acidentalmente mesclar no mestre a partir do editor de modelos de problemas e blob. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}'
+ - 'Quando um usuário excluiu uma conta do GitHub, os registros do log de auditoria não mostraram corretamente os registros de remoção da organização. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}'
+ - 'O avatar do gist para o usuário atual faria um link para uma URL inexistente. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}'
+ - 'A contagem da guia de repositórios da organização não incluiu repositórios internos. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}'
+ - 'Ao transferir um repositório, clicar no botão "Mostrar Todas as Equipes" gerou um erro 500. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}'
+ - 'Os nomes de arquivos longos poderiam gerar problemas de estouro ao mostrar o rótulo "Alterado desde a última exibição" ou o botão de alternância diff "Mostrar avançado" na exibição de arquivos diferencial. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}'
+ - 'Os cartões hovercard para equipes da organização reportaram incorretamente o tamanho do membro. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}'
+ - 'A janela pop-up de comentário de revisão da solicitação de pull teve um problema de rolamento. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}'
+ - 'Haproxy poderia saturar, gerando lentidão nas operações do git. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}'
+ - 'O recurso Grafo de Dependência não foi automaticamente habilitado após a promoção da réplica de HA. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}'
+ - 'Um tempo limite poderia ser acionado na página de índice de lançamentos para repositórios com milhares de rascunhos de solicitações de pull. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}'
+ - 'Não foi possível filtrar as solicitações de pull por estado e rascunho ao mesmo tempo. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}'
+ - 'Se uma solicitação de pull mudou um ponteiro do submódulo, clicar em "Editar arquivo" nesse arquivo do submódulo na guia "Arquivos alterados" da página de solicitação de pull gerou um erro 404. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}'
+ - 'Não foi possível adicionar usuários a uma organização ou excluir a organização após a remoção em massa de todos os usuários e administradores dessa organização. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}'
+ - 'Os comentários de revisão em arquivos que contêm sinais diacríticos e caracteres não latinos no nome do arquivo na página "Arquivos alterados" desapareceriam quando a página fosse recarregada. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}'
+ - 'O estado da caixa de seleção "Visualizado" não foi mantido para arquivos que contêm diacríticos e caracteres não latinos no nome do arquivo na página "Arquivos alterados". {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}'
+ - 'As solicitações de pull mostraram o selo "Aprovado" quando nem todas as revisões necessárias estavam em vigor. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}'
+ - 'O menu suspenso de marcações estava vazio ao procurar uma marcação em repositórios com mais de 100 marcações. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}'
+ - 'As páginas de solicitação de pull que mostram anotações com títulos diferentes de UTF-8 puderam encontrar erros de codificação na representação da exibição. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}'
+ - 'Uma condição de corrida para atualização na página OAuth poderia fazer com que um redirecionamento fosse executado duas vezes. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}'
+ - 'A página "Tokens de Acesso Pessoal" teria o tempo limite esgotado, se houvesse mais de 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}'
+ - 'Trabalhos de sincronização de equipe e usuário LDAP agendados poderiam ser iniciados enquanto trabalhos de sincronização agendados anteriormente ainda estivessem em andamento. Implementou-se um mecanismo de bloqueio para evitar que os novos trabalhos de sincronização começassem, caso um deles ainda estivesse sendo executado. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}'
+ changes:
+ - 'A interface de notificações web foi atualizada, incluindo novos [estados](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options), [filtros](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) e [atalhos](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications). {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}'
+ - 'Agora é possível desabilitar a reativação de usuários de LDAP na sincronização de LDAP. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}'
+ - 'A redação de ramificação protegida por push foi atualizada para esclarecer que os administradores sempre podem efetuar push e que os usuários com a função de Manutenção podem efetuar push quando as verificações de status forem aprovadas. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}'
+ - 'Evitar confirmação em branco quando a sugestão for idêntica ao texto original. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}'
+ - 'A paginação é compatível como uma forma de obter mais arquivos no diff associado a uma confirmação por meio da API REST. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}'
+ - 'Os administradores podem habilitar, desabilitar, excluir e pesquisar webhooks usando a ID do webhook a partir da linha de comando usando `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}'
+ - 'O redirecionamento automático de base acontecerá após a limpeza manual de referência de cabeça para uma solicitação de pull mesclada. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}'
+ - 'Os arquivos SVG são tratados como texto e como imagens no visualizador de diff. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}'
+ - 'A configuração "excluir ramificações automaticamente ao mesclar" pode ser definida ao criar e atualizar repositórios usando a API REST. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}'
+ - 'Um novo ponto de extremidade foi adicionado para excluir uma implantação por meio da API REST. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}'
+ - 'Os administradores podem [habilitar alertas de segurança](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server), mas desabilitar todas as notificações desses alertas. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}'
+ - 'O registro de Páginas mostra o login do usuário que está acessando o site Páginas do GitHub. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}'
+ - 'Os integrantes corporativos podem ver todas as organizações às quais pertencem como parte da sua conta corporativa em apenas uma visualização, acessando `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}'
+ - '[Suporte da API REST para triagem e manutenção de funções](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) foi expandido. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}'
+ - 'Um usuário pode criar e compartilhar consultas de pesquisa que resolvam para o usuário atual, se utilizar a sintaxe de pesquisa `@me`. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}'
+ - 'Novas opções de configuração de modelo de problema foram [adicionadas](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}'
+ - 'A confiabilidade e o tempo para a conclusão do backup e restauração do MySQL foram aprimorados. {% comment %} https://github.com/github/ghes-infrare/issues/162 {% endcomment %}'
+ - '[Visibilidade aprimorada](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) de solicitações de pull e referências de problemas na barra lateral de problemas, cartões de problemas e lista de problemas. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}'
+ - 'Os usuários podem filtrar e pesquisar por `linked:pr` ou `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}'
+ - 'Agora é possível o failover automático do MySQL dentro de apenas uma região para implantações de cluster. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}'
+ - 'Um usuário pode comparar marcações entre duas versões para determinar quais alterações foram feitas na página de versões. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}'
+ - 'Comentários desatualizados não ficam mais recolhidos por padrão na linha do tempo da solicitação de pull. Eles podem ser recolhidos resolvendo o thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}'
+ - 'Os administradores podem ver uma lista de logins reservados para uso interno, indo a guia de ferramentas de equipe "Logins reservados". {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}'
+ known_issues:
+ - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor poderia criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
+ - 'As regras personalizadas do firewall não são mantidas em uma atualização. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
+ - 'Arquivos rastreados LFS do Git [enviados por upload pela interface da web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
+ - 'Os problemas não podem ser fechados, se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
+ - 'Ao efetuar push em um gist, uma exceção poderia ser acionada durante o gancho de pós-recebimento. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
+ - 'Quando a opção "Usuários podem pesquisar no GitHub.com" está habilitada com o GitHub Connect, problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
+ - 'Os alertas de segurança não são relatados ao efetuar push em um repositório na linha de comando. (atualizado em 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
+ - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1, em vez do endereço IP de origem real. (atualizado em 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}'
+ - 'Ocorre uma falha na configuração da permissão de um repositório para `Triagem` ou `Manter` com uma mensagem de erro.'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-21/17.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-21/17.yml
new file mode 100644
index 0000000000..9c2b33be60
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-21/17.yml
@@ -0,0 +1,27 @@
+date: '2021-03-23'
+intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch.
+sections:
+ security_fixes:
+ - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.'
+ - Packages have been updated to the latest security versions.
+ bugs:
+ - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks.
+ changes:
+ - Logs will rotate based on size in addition to time.
+ - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down.
+ known_issues:
+ - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+ - Custom firewall rules are not maintained during an upgrade.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - Security alerts are not reported when pushing to a repository on the command line.
+ - |
+ Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion.
+ To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance:
+
+ ```
+ printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate
+ sudo /usr/sbin/logrotate -f /etc/logrotate.conf
+ ```
+ - When a replica node is offline in a high availability configuration, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users.
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-21/20.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-21/20.yml
new file mode 100644
index 0000000000..cd26312f9c
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-21/20.yml
@@ -0,0 +1,19 @@
+date: '2021-04-28'
+sections:
+ security_fixes:
+ - 'Os pacotes foram atualizados para as últimas versões de segurança.'
+ bugs:
+ - 'O script de configuração em execução na replicação do MySQL pode ter causado uma nova propagação desnecessária do banco de dados durante a falha do banco de dados.'
+ - 'O arquivo `config-apply` pode levar mais tempo do que o necessário devido ao chamado desnecessário de `rake db:migrate`.'
+ - 'O Orchestrator poderia ter falhado para uma réplica do MySQL que não estava sendo replicada a partir do primário durante a fase de propagação quando não era possível conectar o primário.'
+ - 'Organizações ou projetos com erros bloquearam a migração e não puderam ser excluídos.'
+ changes:
+ - 'Verificações de preliminares permitem todos os tipos de instância de AWS por padrão.'
+ known_issues:
+ - 'Em uma nova configuração do servidor do GitHub Enterprise sem nenhum usuário, um invasor pode criar o primeiro usuário administrador.'
+ - 'As regras personalizadas de firewall não são mantidas durante uma atualização.'
+ - 'Arquivos LFS do Git [enviados através da interface da Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório onde o caminho do arquivo tem mais de 255 caracteres.'
+ - 'Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.'
+ - 'Os alertas de segurança não são relatados ao efetuar push em um repositório na linha de comando.'
+ - 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-22/11.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-22/11.yml
new file mode 100644
index 0000000000..bd6ba43022
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/2-22/11.yml
@@ -0,0 +1,19 @@
+date: '2021-04-14'
+sections:
+ security_fixes:
+ - Os pacotes foram atualizados para as últimas versões de segurança.
+ bugs:
+ - 'Uma mensagem de aviso `jq: error (at ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}.
+
+ # https://github.com/github/releases/issues/1250
+ - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."
+
+ - heading: 'Markdown changes'
+ notes:
+ # https://github.com/github/releases/issues/1477
+ - The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."
+
+ # https://github.com/github/releases/issues/1169
+ - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
+
+ # https://github.com/github/releases/issues/1269
+ - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported.
+
+ # https://github.com/github/releases/issues/1294
+ - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.'
+
+ # https://github.com/github/releases/issues/1474
+ - Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."
+
+ - heading: 'Issues and pull requests changes'
+ notes:
+ # https://github.com/github/releases/issues/1413
+ - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).
+
+ # https://github.com/github/releases/issues/1419
+ - A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."
+
+ # https://github.com/github/releases/issues/1279
+ - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+
+ # https://github.com/github/releases/issues/1550
+ - People with maintain permissions can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin permissions could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)."
+
+ # https://github.com/github/releases/issues/1201
+ - The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name.
+
+ # https://github.com/github/releases/issues/1430
+ - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams.
+
+ # https://github.com/github/releases/issues/1293
+ - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}.
+
+ # https://github.com/github/releases/issues/1300
+ - Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."
+
+ - heading: 'Branches changes'
+ notes:
+ # https://github.com/github/releases/issues/885
+ - |
+ The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted.
+
+ If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings.
+
+ # https://github.com/github/releases/issues/981
+ - |
+ Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated.
+
+ Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches.
+
+ To help make the change as seamless as possible for users:
+
+ * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository.
+ * Web requests to the old branch will be redirected.
+ * A "moved permanently" HTTP response will be returned to REST API calls.
+ * An informational message is displayed to Git command line users that push to the old branch.
+
+ For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)."
+
+ - heading: 'GitHub Actions changes'
+ notes:
+ # https://github.com/github/releases/issues/1227
+ - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."'
+
+ # https://github.com/github/releases/issues/1280
+ - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).'
+
+ # https://github.com/github/releases/issues/1157
+ - The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."
+
+ # https://github.com/github/releases/issues/1587
+ - |
+ {% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
+ * The "Maximum Concurrency" values were modified to reflect our most up to date performance testing. [Updated: 2021-12-07]
+
+ - The [{% data variables.product.prodname_actions %} Runner](https://github.com/actions/runner) application in {% data variables.product.prodname_ghe_server %} 3.2 has been updated to [v2.279.0](https://github.com/actions/runner/releases/tag/v2.279.0).
+
+ - heading: 'GitHub Packages changes'
+ notes:
+ # https://github.com/github/releases/issues/1088
+ - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)".
+
+ - heading: 'Dependabot and Dependency graph changes'
+ notes:
+ # https://github.com/github/releases/issues/1537
+ - The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+
+ # https://github.com/github/releases/issues/1153
+ - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).
+
+ # https://github.com/github/releases/issues/1371
+ - Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository's `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."
+
+ # https://github.com/github/releases/issues/1538
+ - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. For more information see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+ - heading: 'Code scanning and secret scanning changes'
+ notes:
+ # https://github.com/github/releases/issues/1352
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."'
+
+ # https://github.com/github/releases/issues/1360
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."'
+
+ # https://github.com/github/releases/issues/1160
+ - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.'
+
+ # https://github.com/github/releases/issues/1454
+ - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.'
+
+ # https://github.com/github/releases/issues/1375
+ - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).
+
+ # https://github.com/github/releases/issues/1335
+ # https://github.com/github/releases/issues/1314
+ - |
+ {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure.
+
+ Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure.
+
+ For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."
+
+ 
+
+ # https://github.com/github/releases/issues/1324
+ - |
+ Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar.
+
+ The search syntax has also been simplified to `branch:http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ changes:
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ known_issues:
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - |
+ After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
+ - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
+ - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml
new file mode 100644
index 0000000000..378a8b6706
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml
@@ -0,0 +1,421 @@
+date: '2022-05-10'
+release_candidate: true
+deprecated: true
+intro: |
+ {% note %}
+
+ **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+
+ {% endnote %}
+
+ For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+ features:
+ - heading: IP exception list for validation testing after maintenance
+ notes:
+ # https://github.com/github/releases/issues/2109
+ - |
+ You can now configure an allow list of IP addresses that can access application services on your GitHub Enterprise Server instance while maintenance mode is enabled. Administrators who visit the instance's web interface from an allowed IP address can validate the instance's functionality post-maintenance and before disabling maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)."
+
+ - heading: Custom repository roles are generally available
+ notes:
+ # https://github.com/github/releases/issues/1945
+ - |
+ With custom repository roles, organizations now have more granular control over the repository access permissions they can grant to users. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+
+ A custom repository role is created by an organization owner, and is available across all repositories in that organization. Each role can be given a custom name, and a description. It can be configured from a set of over 40 fine grained permissions. Once created, repository admins can assign a custom role to any user, team or outside collaborator in their repository.
+
+ Custom repository roles can be created, viewed, edited and deleted via the new **Repository roles** tab in an organization's settings. A maximum of 3 custom roles can be created within an organization.
+
+ Custom repository roles are also fully supported in the GitHub Enterprise Server REST APIs. The Organizations API can be used to list all custom repository roles in an organization, and the existing APIs for granting repository access to individuals and teams have been extended to support custom repository roles. For more information, see "[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)" in the REST API documentation.
+
+ - heading: GitHub Container registry in public beta
+ notes:
+ # https://github.com/github/releases/issues/2005
+ - |
+ The GitHub Container registry (GHCR) is now available in GitHub Enterprise Server 3.5 as a public beta, offering developers the ability to publish, download, and manage containers. GitHub Packages container support implements the OCI standards for hosting Docker images. For more information, see "[GitHub Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+ - heading: Dependabot updates are generally available
+ notes:
+ # https://github.com/github/releases/issues/2089
+ - |
+ Dependabot version and security updates are now generally available in GitHub Enterprise Server 3.5. All the popular ecosystems and features that work on GitHub.com repositories now can be set up on your GitHub Enterprise Server instance. Dependabot on GitHub Enterprise Server requires GitHub Actions and a pool of self-hosted Dependabot runners, GitHub Connect enabled, and Dependabot enabled by an admin. For more information, see "[Setting up Dependabot updates](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
+
+
+
+ - heading: Server Statistics in public beta
+ notes:
+ # https://github.com/github/releases/issues/2183
+ - |
+ You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content. For a better understanding of how we store and secure Server Statistics data, see "[GitHub Security](https://github.com/security)." For more information about Server Statistics, see "[Analyzing how your team works with Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics)." This feature is available in public beta.
+
+ - heading: GitHub Actions rate limiting is now configurable
+ notes:
+ # https://github.com/github/releases/issues/2123
+ - |
+ Site administrators can now enable and configure a rate limit for GitHub Actions. By default, the rate limit is disabled. When workflow jobs cannot immediately be assigned to an available runner, they will wait in a queue until a runner is available. However, if GitHub Actions experiences a sustained high load, the queue can back up faster than it can drain and the performance of the GitHub Enterprise Server instance may degrade. To avoid this, an administrator can configure a rate limit. When the rate limit is exceeded, additional workflow runs will fail immediately rather than being put in the queue. Once the rate has stabilized below the threshold, new runs can be queued again. For more information, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)."
+
+ - heading: OpenID Connect (OIDC) for secure deployments with GitHub Actions
+ notes:
+ # https://github.com/github/releases/issues/2066
+ - |
+ GitHub Actions on GitHub Enterprise Server now supports OIDC for secure deployments to cloud providers, which uses short-lived tokens that are automatically rotated for each deployment. OIDC enables the following functionality.
+
+ - Seamless authentication between cloud providers and GitHub Enterprise Server without the need for storing any long-lived cloud secrets on your instance
+ - Cloud administrators can rely on the security mechanisms of a particular cloud provider to ensure that GitHub Actions workflows have minimal access to cloud resources. There is no duplication of secret management between GitHub Enterprise Server and the cloud.
+
+ For more information, see "[Security hardening your deployments](/actions/deployment/security-hardening-your-deployments)."
+
+ - heading: Sharing GitHub Actions within your enterprise is generally available
+ notes:
+ # https://github.com/github/releases/issues/2085
+ - |
+ Support for GitHub Actions in internal repositories is now generally available for organizations on your GitHub Enterprise Server instance. You can innersource automation by sharing actions in internal repositories. You can manage a repository's settings or use the REST API to allow access to workflows in other repositories within the organization or in any organization on the instance. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)," "[Managing GitHub Actions settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)," and "[Actions Permissions](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository)" in the REST API documentation.
+
+ - heading: Cache support for GitHub Actions on GitHub Enterprise Server is now generally available
+ notes:
+ # https://github.com/github/releases/issues/2110
+ - |
+ You can now use dependency caching to speed up your GitHub Actions workflows. To cache dependencies for a job, you can include the [actions/cache](https://github.com/actions/cache) action to create a cache with a unique key. You can share caches across all workflows in the same repository. These workflows can then restore the cache and run faster.
+
+ Actions users can also use our cache APIs to:
+
+ - Define the enterprise policy for cache size range allowed per repository.
+ - Query the cache usage within each repository and monitor if the total size of all caches is reaching the upper limit.
+ - Increase the maximum cache size for a repository within the allowed enterprise limits, based on the cache requirements of the repository.
+ - Monitor aggregate cache usage at organization level or at enterprise level.
+
+ The external blob storage that is configured within your enterprise account will now be shared across workflow artifacts, logs, and also the caches. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."
+
+
+ - heading: Automatically sign commits made in the web UI
+ notes:
+ # https://github.com/github/releases/issues/1963
+ - |
+ You can now configure GitHub Enterprise Server to automatically sign commits made in the web interface, such as from editing a file or merging a pull request. Signed commits increase confidence that changes come from trusted sources. This feature allows the [Require signed commits](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-signed-commits) branch protection setting to block unsigned commits from entering a repository, while allowing entry of signed commits – even those made in the web interface. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)."
+
+ - heading: Sync license usage any time
+ notes:
+ # https://github.com/github/releases/issues/2201
+ - |
+ For customers that sync license usage between GitHub Enterprise Server and GitHub Enterprise Cloud automatically using GitHub Connect, you now have the ability to sync your license usage independently of the automatic weekly sync. This feature also reports the status of sync job. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#manually-syncing-license-usage)."
+
+ - heading: Reusable workflows for GitHub Actions are generally available
+ notes:
+ # https://github.com/github/releases/issues/1767
+ # https://github.com/github/releases/issues/1950
+ # https://github.com/github/releases/issues/2114
+ - |
+ Reusable workflows are now generally available. Reusable workflows help you reduce duplication by enabling you to reuse an entire workflow as if it were an action. With the general availability release, a number of improvements are now available for GitHub Enterprise Server. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
+
+ - You can utilize outputs to pass data from reusable workflows to other jobs in the caller workflow.
+ - You can pass environment secrets to reusable workflows.
+ - The audit log includes information about which reusable workflows are used.
+ - Reusable workflows in the same repository as the calling repository can be referenced with just the path and filename (`PATH/FILENAME`). The called workflow will be from the same commit as the caller workflow.
+
+ - heading: Self-hosted runners for GitHub Actions can now disable automatic updates
+ notes:
+ # https://github.com/github/releases/issues/2014
+ - |
+ You now have more control over when your self-hosted runners perform software updates. If you specify the `--disableupdate` flag to the runner then it will not try to perform an automatic software update if a newer version of the runner is available. This allows you to update the self-hosted runner on your own schedule, and is especially convenient if your self-hosted runner is in a container.
+
+ For compatibility with the GitHub Actions service, you will need to manually update your runner within 30 days of a new runner version being available. For instructions on how to install the latest runner version, please see the installation instructions for [the latest release in the runner repo](https://github.com/actions/runner/releases).
+
+ - heading: Secure self-hosted runners for GitHub Actions by limiting workflows
+ notes:
+ # https://github.com/github/releases/issues/2013
+ - |
+ Organization owners can now increase the security of CI/CD workflows on self-hosted runners by choosing which workflows can access a runner group. Previously, any workflow in a repository, such as an issue labeler, could access the self-hosted runners available to an organization. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)" and the [GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/).
+
+ - heading: Prevent GitHub Actions from approving pull requests
+ notes:
+ # https://github.com/github/releases/issues/1959
+ - |
+ You can now control whether GitHub Actions can approve pull requests. This feature protects against a user using GitHub Actions to satisfy the "Required approvals" branch protection requirement and merging a change that was not reviewed by another user. To prevent breaking existing workflows, **Allow GitHub Actions reviews to count towards required approval** is enabled by default. Organization owners can disable the feature in the organization's GitHub Actions settings. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)."
+
+ - heading: Re-run failed or individual GitHub Actions jobs
+ notes:
+ # https://github.com/github/releases/issues/1503
+ - |
+ You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+
+ - heading: Dependency graph supports GitHub Actions
+ notes:
+ # https://github.com/github/releases/issues/1913
+ - |
+ The dependency graph now detects YAML files for GitHub Actions workflows. GitHub Enterprise Server will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the "Used By" control on the repository homepage. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+
+ - heading: Security overview for enterprises in public beta
+ notes:
+ # https://github.com/github/releases/issues/2040
+ - |
+ GitHub Advanced Security customers can now view an overview of security alerts at the enterprise level. The new **Security** tab at the enterprise level provides a repository-centric view of application security risks, as well as an alert-centric view of all secret scanning alerts. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+ - heading: Security view for organizations is generally available
+ notes:
+ # https://github.com/github/releases/issues/2096
+ - |
+ The overview of security alerts at the organization level is now generally available. GitHub Advanced Security customers can use the security overview to view a repository-centric view of application security risks, or an alert-centric view of all code scanning, Dependabot, and secret scanning alerts for all repositories in an organization. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+ - heading: Code scanning detects more security issues, supports new language versions
+ notes:
+ # https://github.com/github/releases/issues/2097
+ - |
+ Code scanning now detects a larger number of CWEs, and CodeQL code scanning fully supports the standard language features in the following language releases.
+
+ - C# 10 / .NET 6
+ - Python 3.10
+ - Java 17
+ - TypeScript 4.5
+
+ For more information, see the [GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/).
+
+ - heading: View code scanning alerts across an organization
+ notes:
+ # https://github.com/github/releases/issues/1792
+ - |
+ GitHub Advanced Security customers can now view code scanning alerts in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+ # https://github.com/github/releases/issues/1763
+ - |
+ Users can now retrieve code scanning alerts for an organization on your GitHub Enterprise Server instance via the REST API. This new API endpoint supplements the existing [endpoint for repositories](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository). For more information, see [Code Scanning](/rest/code-scanning) in the REST API documentation.
+
+ - heading: Secret scanning available as a push protection
+ notes:
+ #
+ - |
+ GitHub Enterprise Server can now block any pushes where a token is detected with high confidence. Developers can bypass the block by providing details of why the secret needs to be committed via a web UI. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+
+ - heading: Dry runs for custom patterns with secret scanning
+ notes:
+ # https://github.com/github/releases/issues/1703
+ # https://github.com/github/releases/issues/2084
+ - |
+ GitHub Advanced Security customers can now dry run custom secret scanning patterns at the organization or repository level. Dry runs allow people with owner or admin access to review and hone their patterns before publishing them and generating alerts. You can compose a pattern, then use **Save and dry run** to retrieve results. The scans typically take just a few seconds, but GitHub Enterprise Server will also notify organization owners or repository admins via email when dry run results are ready. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)" and "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+ - heading: Secret scanning custom pattern events now in the audit log
+ notes:
+ # https://github.com/github/releases/issues/2154
+ - |
+ The audit log now includes events associated with secret scanning custom patterns. This data helps GitHub Advanced Security customers understand actions taken on their [repository](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)-, [organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)-, or [enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)-level custom patterns for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)" or "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)."
+
+ - heading: Configure permissions for secret scanning with custom repository roles
+ notes:
+ # https://github.com/github/releases/issues/1909
+ - |
+ You can now configure two new permissions for secret scanning when managing custom repository roles.
+
+ - View secret scanning results
+ - Dismiss or reopen secret scanning results
+
+ For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+
+ - heading: Secret scanning now supports archived repositories
+ notes:
+ # https://github.com/github/releases/issues/2076
+ - |
+ GitHub Advanced Security customers can now enable secret scanning for archived repositories via the UI and API. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)," "[About archived repositories](/repositories/archiving-a-github-repository/archiving-repositories)," and "[Repositories](/rest/repos/repos#update-a-repository)" in the REST API documentation.
+
+ - heading: Secret scanning webhooks for alert locations
+ notes:
+ # https://github.com/github/releases/issues/2149
+ - |
+ GitHub Advanced Security customers using secret scanning can now opt to receive a webhook each time a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)."
+
+ - heading: View Dependabot alerts across an organization
+ notes:
+ # https://github.com/github/releases/issues/1992
+ - |
+ GitHub Advanced Security customers can now view Dependabot alerts in in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+ - heading: Configure permissions for Dependabot alerts with custom repository roles
+ notes:
+ # https://github.com/github/releases/issues/1958
+ - |
+ You can now configure two new permissions for Dependabot alerts when managing custom repository roles.
+
+ - View Dependabot alerts
+ - Dismiss or reopen Dependabot alerts
+
+ For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+
+ - heading: Reopen dismissed Dependabot alerts
+ notes:
+ # https://github.com/github/releases/issues/1923
+ - |
+ You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
+
+ - heading: Pub support for Dependabot version updates is in public beta
+ notes:
+ # https://github.com/github/releases/issues/2086
+ - |
+ Users of Dependabot version updates can now proactively update dependencies for Flutter or Dart projects that use the Pub package manager.
+
+ To test [version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates) on your own Dart or Flutter repository, add the following configuration file in [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates). Note the `package-ecosystem: "pub"` and `enable-beta-ecosystems: true` flags.
+ ```yaml
+ version: 2
+ enable-beta-ecosystems: true
+ updates:
+ - package-ecosystem: "pub"
+ directory: "/"
+ schedule:
+ interval: "weekly"
+ ```
+
+ - heading: See pull request associated with a repository's Dependabot alerts via GraphQL API
+ notes:
+ # https://github.com/github/releases/issues/2088
+ - |
+ The new `DependabotUpdate` GraphQL object lets you view information about what happens to your repository's security updates. When GitHub Enterprise Server detects that a dependency in your repository is vulnerable, Dependabot will attempt to open a pull request to update that dependency to a non-vulnerable version. You can now see the pull request that fixes the vulnerability. In some cases, Dependabot fails to open a pull request. Previously, the error message that Dependabot generated was only visible in the "Dependabot Alerts" section of the **Security** tab. Now, if Dependabot runs into an error when trying to open a pull request for a security alert, you can determine the reason using the GraphQL API. For more information, see "[Objects](/graphql/reference/objects#dependabotupdate)" in the GraphQL API documentation.
+
+ - heading: Access more information about Dependabot alerts via GraphQL API
+ notes:
+ # https://github.com/github/releases/issues/1922
+ - |
+ You can now view fixed alerts from Dependabot with the GraphQL API. You can also access and filter by state, as well as by unique numeric identifier, and you can filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`.
+
+ - `number`
+ - `fixed_at`
+ - `fix_reason`
+ - `state`
+
+ For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation.
+
+ - heading: Git events in the enterprise audit log
+ notes:
+ # https://github.com/github/releases/issues/2205
+ - |
+ The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV.
+
+ - `git.clone`
+ - `git.fetch`
+ - `git.push`
+
+ Due to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
+
+ - heading: Improvements to CODEOWNERS
+ notes:
+ # https://github.com/github/releases/issues/1994
+ - |
+ This release includes improvements to CODEOWNERS.
+
+ - Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation.
+ - After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review.
+ - Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines.
+
+ For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)."
+
+ - heading: More ways to keep a pull request's topic branch up to date
+ notes:
+ # https://github.com/github/releases/issues/1566
+ - |
+ The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date.
+
+ - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
+
+ - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)."
+
+ - heading: Configure custom HTTP headers for GitHub Pages sites
+ notes:
+ # https://github.com/github/releases/issues/2124
+ - |
+ You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see "[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)."
+
+ - heading: Ignore commits in blame view
+ notes:
+ # https://github.com/github/releases/issues/2090
+ - |
+ It's now possible to ignore revisions in the blame view by creating a _.git-blame-ignore-revs_ file in the root of your repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)."
+
+ - heading: Light high contrast theme is generally available
+ notes:
+ # https://github.com/github/releases/issues/2011
+ - |
+ A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
+
+ - heading: Tag protection rules
+ notes:
+ # https://github.com/github/releases/issues/1793
+ - |
+ Repository owners can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with the Maintain or Admin role in the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)."
+
+ bugs:
+ # https://github.com/github/releases/issues/1934
+ - |
+ It is now possible for GitHub Apps to upload release assets.
+
+ changes:
+ # https://github.com/github/releases/issues/2063
+ - |
+ To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)."
+
+ # https://github.com/github/releases/issues/2049
+ - |
+ The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into your code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
+
+ The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation.
+
+ # https://github.com/github/releases/issues/2050
+ - |
+ Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. You can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)."
+
+ # https://github.com/github/releases/issues/2071
+ - |
+ Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories.
+
+ # https://github.com/github/releases/issues/1947
+ - |
+ GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)."
+
+ # https://github.com/github/releases/issues/2054
+ - |
+ New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)."
+
+ # https://github.com/github/releases/issues/2028
+ - |
+ Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)."
+
+ # https://github.com/github/releases/issues/2036
+ - |
+ Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/).
+
+ # https://github.com/github/releases/issues/2129
+ - |
+ Focusing or hovering over a label now displays the label description in a tooltip.
+
+ # https://github.com/github/releases/issues/1983
+ - |
+ Creating and removing repository invitations, whether done through the API or web interface, are now subject to rate limits that may be enabled on your GitHub Enterprise Server instance. For more information about rate limits, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)."
+
+ # https://github.com/github/releases/issues/2291
+ - |
+ MinIO has announced the removal of the MinIO Gateways starting June 1st, 2022. While MinIO Gateway for NAS continues to be one of the supported storage providers for Github Actions and Github Packages, we recommend moving to MinIO LTS support to avail support and bug fixes from MinIO. For more information about rate limits, see "[Scheduled removal of MinIO Gateway for GCS, Azure, HDFS in the minio/minio repository](https://github.com/minio/minio/issues/14331)."
+
+
+ deprecations:
+ - heading: Change to the format of authentication tokens
+ notes:
+ # https://github.com/github/releases/issues/1235
+ - |
+ GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. For more information, see the [GitHub changelog](https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/).
+
+ - heading: CodeQL runner deprecated in favor of CodeQL CLI
+ notes:
+ # https://github.com/github/releases/issues/1632
+ - |
+ The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)."
+
+ - heading: Theme picker for GitHub Pages has been removed
+ notes:
+ - |
+ The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)."
+
+ known_issues:
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/4.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/4.yml
new file mode 100644
index 0000000000..b5a846e1c3
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/4.yml
@@ -0,0 +1,30 @@
+date: '2022-08-11'
+sections:
+ security_fixes:
+ - |
+ **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf).
+ - |
+ **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com).
+ bugs:
+ - In some cases, GitHub Enterprise Server instances on AWS that used the `r4.4xlarge` instance type would fail to boot.
+ - In some cases, UI elements within a pull request's **Files changed** tab could overlap.
+ - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+ - When calculating committers for GitHub Advanced Security, it was not possible to specify individual repositories. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."
+ - In some cases, Elasticsearch's post-upgrade `es:upgrade` process could crash before completion.
+ - The script for migration to internal repositories failed to convert the visibility for public repositories to internal or private. For more information about the migration, see "[Migrating to internal repositories](/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories)."
+ - Detection of GitHub Actions workflow files for the dependency graph was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#supported-package-ecosystems)."
+ - The ability to reopen dismissed Dependabot alerts was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-updating-closed-alerts)."
+ - The ability to always suggest updates from the base branch to a pull request's HEAD was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)."
+ - The light high contrast theme was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)."
+ changes:
+ - '`pre_receive_hook.rejected_push` events were not displayed in the enterprise audit log.'
+ known_issues:
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+ - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
\ No newline at end of file
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/5.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/5.yml
new file mode 100644
index 0000000000..7407eb973b
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/5.yml
@@ -0,0 +1,27 @@
+date: '2022-08-30'
+sections:
+ bugs:
+ - 'Após desbloquear um repositório para acesso temporário, o administrador do site não conseguiu gerenciar as configurações dos produtos de segurança no repositório.'
+ - 'Chaves SSH administrativas duplicadas podem aparecer tanto no Console de Gerenciamento quanto no arquivo `/home/admin/.ssh/authorized_keys`.'
+ - 'A página de administração do site para usuários individuais em http(s)://HOSTNAME/stafftools/users/USERNAME/admin continha funcionalidades não destinadas ao Servidor do GitHub Enterprise.'
+ - 'Em alguns casos, executar `ghe-cluster-config-apply` pode replicar uma configuração vazia para nós existentes em um cluster.'
+ - 'Em alguns casos, as execuções de configuração iniciadas com `ghe-config-apply` não foram concluídas ou retornaram um erro `Incompatibilidade de contagem de contêiner`.'
+ - 'Depois de atualizar um certificado TLS autoassinado em uma instância de servidor do GitHub Enterprise, os elementos da interface do usuário em algumas páginas da interface da Web não apareciam.'
+ - 'A barra de administração do site na parte superior da interface da Web continha um link desfeito para o SHA da versão do aplicativo em execução no momento.'
+ - 'Em alguns casos, as tarefas em segundo plano podem parar devido ao uso concomitante de uma biblioteca, embora não seja thread-safe.'
+ - 'Alertas da verificação de segredo para clientes da Segurança Avançada do GitHub ficariam ausentes na interface do usuário da Web e na API REST se um administrador do site não atualizasse diretamente para o GitHub Enterprise Server 3.4. Os alertas agora estão visíveis.'
+ - 'Quando um usuário bifurcava um repositório em uma organização, uma longa lista de organizações não era renderizada corretamente.'
+ changes:
+ - 'Como resultado da sanitização de log paralelizada, a geração de pacotes de suporte ficou mais rápida. Para ver mais informações sobre pacotes de suporte, confira "[Como fornecer dados ao suporte do GitHub](/support/contacting-github-support/providing-data-to-github-support)."'
+ - 'As APIs que contêm a rota `organização` ou `org` agora aceitam o slug ou a ID da organização. Anteriormente, as APIs aceitavam apenas slugs, o que fazia com que os cabeçalhos `Link` dos pontos de extremidade do GitHub Advanced Security ficassem inacessíveis. Para ver mais informações, confira "[Organizações](https://docs.github.com/rest/orgs/orgs)" na documentação da API REST.'
+ - 'O log de auditoria empresarial agora inclui mais eventos gerados pelo usuário, como `project.create`. A API REST também retorna eventos adicionais gerados pelo usuário, como `repo.create`. Para ver mais informações, confira "[Como acessar o log de auditoria da sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" e "[Como usar a API de log de auditoria da sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."'
+ - 'Em alguns casos, as réplicas de cache podem rejeitar algumas operações do Git em repositórios atualizados recentemente. Para ver mais informações sobre o armazenamento em cache do repositório, confira "[Sobre o armazenamento em cache do repositório](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
+ known_issues:
+ - 'Em uma instância de {% data variables.product.prodname_ghe_server %} recém-configurada sem usuários, um invasor pode criar o primeiro usuário administrador.'
+ - 'As regras de firewall personalizadas são removidas durante o processo de atualização.'
+ - 'Arquivos LFS do Git [enviados através da interface Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de maneira incorreta.'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, em que o caminho do arquivo blob''s é maior que 255 caracteres.'
+ - 'Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.'
+ - 'O registro npm {% data variables.product.prodname_registry %} não retorna mais um valor temporal em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para retornar um valor temporal como parte da resposta de metadados e continuaremos a retornar este valor no futuro quando tivermos resolvido os problemas de desempenho existentes.'
+ - 'Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive.'
+ - 'Os serviços de ação devem ser reiniciados após a restauração de um dispositivo a partir do backup tomado em um host diferente.'
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml
new file mode 100644
index 0000000000..fc7707911b
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml
@@ -0,0 +1,298 @@
+date: '2022-07-26'
+release_candidate: true
+deprecated: true
+intro: |
+ {% note %}
+
+ **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment.
+
+ {% endnote %}
+
+ For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+ features:
+ - heading: Infrastructure
+ notes:
+ # https://github.com/github/releases/issues/2002
+ - |
+ Repository caching is generally available. Repository caching increases Git read performance for distributed developers, providing the data locality and convenience of geo-replication without impact on push workflows. With the general availability release, GitHub Enterprise Server caches both Git and Git LFS data. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+
+ - heading: Instance security
+ notes:
+ # https://github.com/github/releases/issues/1569
+ - |
+ GitHub has changed the supported algorithms and hash functions for all SSH connections to GitHub Enterprise Server, disabled the unencrypted and unauthenticated Git protocol, and optionally allowed the advertisement of an Ed25519 host key. For more information, see the [GitHub Blog](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server/) and the following articles.
+
+ - "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)"
+ - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)"
+ - "[Configuring host keys for your instance](/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance)"
+
+ # https://github.com/github/releases/issues/2341
+ - |
+ You can require TLS encryption for incoming SMTP connections to your instance. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)."
+
+ - heading: Audit logs
+ notes:
+ # https://github.com/github/releases/issues/1438
+ - |
+ You can stream audit log and Git events for your instance to Amazon S3, Azure Blob Storage, Azure Event Hubs, Google Cloud Storage, or Splunk. Audit log streaming is in public beta and subject to change. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+
+ - heading: GitHub Connect
+ notes:
+ # https://github.com/github/releases/issues/2306
+ - |
+ Server Statistics is now generally available. Server Statistics collects aggregate usage data from your GitHub Enterprise Server instance, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from GitHub Enterprise Server. For more information, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+
+ - heading: Administrator experience
+ notes:
+ # https://github.com/github/releases/issues/2351
+ - |
+ Enterprise owners can join organizations on the instance as a member or owner from the enterprise account's **Organizations** page. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
+
+ # https://github.com/github/releases/issues/2221
+ - |
+ Enterprise owners can allow users to dismiss the configured global announcement banner. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+
+ - heading: GitHub Advanced Security
+ notes:
+ # https://github.com/github/releases/issues/2321
+ - |
+ Users on an instance with a GitHub Advanced Security license can opt to receive a webhook event that triggers when an organization owner or repository administrator enables or disables a code security or analysis feature. For more information, see the following documentation.
+
+ - "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#security_and_analysis)" in the webhook documentation
+ - "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)"
+ - "[Managing security and analysis features for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
+
+ # https://github.com/github/releases/issues/2191
+ - |
+ Users on an instance with a GitHub Advanced Security license can optionally add a comment when dismissing a code scanning alert in the web UI or via the REST API. Dismissal comments appear in the event timeline. Users can also add or retrieve a dismissal comment via the REST API. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests#dismissing-an-alert-on-your-pull-request)" and "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)" in the REST API documentation.
+
+ # https://github.com/github/releases/issues/2228
+ - |
+ On instances with a GitHub Advanced Security license, secret scanning prevents the leak of secrets in the web editor. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-web-ui)."
+
+ # https://github.com/github/releases/issues/2318
+ # https://github.com/github/releases/issues/2277
+ - |
+ Enterprise owners and users on an instance with a GitHub Advanced Security license can view secret scanning alerts and bypasses of secret scanning's push protection in the enterprise and organization audit logs, and via the REST API. For more information, see the following documentation.
+
+ - "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)"
+ - "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#secret_scanning_push_protection-category-actions)"
+ - "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#secret_scanning_push_protection-category-actions)"
+ - "[Secret Scanning](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)" in the REST API documentation
+
+ # https://github.com/github/releases/issues/2230
+ # https://github.com/github/releases/issues/2317
+ - |
+ Enterprise owners on an instance with a GitHub Advanced Security license can perform dry runs of custom secret scanning patterns for the enterprise, and all users can perform dry runs when editing a pattern. Dry runs allow you to understand a pattern's impact across the entire instance and hone the pattern before publication and generation of alerts. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+ # https://github.com/github/releases/issues/2236
+ - |
+ Users on an instance with a GitHub Advanced Security license can use `sort` and `direction` parameters in the REST API when retrieving secret scanning alerts, and sort based on the alert’s `created` or `updated` fields. The new parameters are available for the entire instance, or for individual organizations or repositories. For more information, see the following documentation.
+
+ - "[List secret scanning alerts for an enterprise](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)"
+ - "[List secret scanning alerts for an organization](/rest/secret-scanning#list-secret-scanning-alerts-for-an-organization)"
+ - "[List secret scanning alerts for a repository](/rest/secret-scanning#list-secret-scanning-alerts-for-a-repository)"
+ - "[Secret Scanning](/rest/secret-scanning)" in the REST API documentation
+
+ # https://github.com/github/releases/issues/2263
+ - |
+ The contents of the `github/codeql-go` repository have moved to the `github/codeql` repository, to live alongside similar libraries for all other programming languages supported by CodeQL. The open-source CodeQL queries, libraries, and extractor for analyzing codebases written in the Go programming language with GitHub's CodeQL code analysis tools can now be found in the new location. For more information, including guidance on migrating your existing workflows, see [github/codeql-go#741](https://github.com/github/codeql-go/issues/741).
+
+ - heading: Dependabot
+ notes:
+ # https://github.com/github/releases/issues/2256
+ - |
+ Enterprise owners on instances with a GitHub Advanced Security license can see an overview of Dependabot alerts for the entire instance, including a repository-centric view of application security risks, and an alert-centric view of all secret scanning and Dependabot alerts. The views are in beta and subject to change, and alert-centric views for code scanning are planned for a future release of GitHub Enterprise Server. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview#viewing-the-security-overview-for-an-enterprise)."
+
+ # https://github.com/github/releases/issues/2160
+ - |
+ Users can select multiple Dependabot alerts, then dismiss or reopen or dismiss the alerts. For example, from the **Closed alerts** tab, you can select multiple alerts that have been previously dismissed, and then reopen them all at once. For more information, see "[About Dependabot alerts](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
+
+ # https://github.com/github/releases/issues/2232
+ - |
+ Dependabot updates `@types` dependencies alongside corresponding packages in TypeScript projects. Before this change, users would see separate pull requests for a package and the corresponding `@types` package. This feature is automatically enabled for repositories containing `@types` packages in the project's `devDependencies` within the _package.json_ file. You can disable this behavior by setting the [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore) field in your `dependabot.yml` file to `@types/*`. For more information, see "[About Dependabot version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)" and "[Configuration options for the _dependabot.yml_ file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)."
+
+ - heading: Code security
+ notes:
+ # https://github.com/github/releases/issues/2098
+ # https://github.com/github/releases/issues/2282
+ - |
+ GitHub Actions can enforce dependency reviews on users' pull requests by scanning for dependencies, and will warn users about associated security vulnerabilities. The `dependency-review-action` action is supported by a new API endpoint that diffs the dependencies between any two revisions. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."
+
+ # https://github.com/github/releases/issues/2243
+ - |
+ The dependency graph detects _Cargo.toml_ and _Cargo.lock_ files for Rust. These files will be displayed in the **Dependency graph** section of the **Insights** tab. Users will receive Dependabot alerts and updates for vulnerabilities associated with their Rust dependencies. Package metadata, including mapping packages to repositories, will be added at a later date. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+
+ # https://github.com/github/releases/issues/1766
+ - |
+ If GitHub Connect is enabled for your instance, users can contribute an improvement to a security advisory in the [GitHub Advisory Database](https://github.com/advisories). To contribute, click **Suggest improvements for this vulnerability** while viewing an advisory's details. For more information, see the following articles.
+
+ - "[Managing GitHub Connect](/admin/configuration/configuring-github-connect/managing-github-connect)"
+ - "[Browsing security vulnerabilities in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+ - "[About GitHub Security Advisories for repositories](/enterprise-cloud@latest/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)" in the GitHub Enterprise Cloud documentation
+ - "[Editing security advisories in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+
+ - heading: GitHub Actions
+ notes:
+ # https://github.com/github/releases/issues/2159
+ - |
+ Within a workflow that calls a reusable workflow, users can pass the secrets to the reusable workflow with `secrets: inherit`. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow)."
+
+ # https://github.com/github/releases/issues/2102
+ - |
+ When using GitHub Actions, to reduce the risk of merging a change that was not reviewed by another person into a protected branch, enterprise owners and repository administrators can prevent Actions from creating pull requests. Organization owners could previously enable this restriction. For more information, see the following articles.
+
+ - "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)"
+ - "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)"
+ - "[Managing GitHub Actions settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"
+
+ # https://github.com/github/releases/issues/2155
+ - |
+ Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility. For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)."
+
+ # https://github.com/github/releases/issues/2103
+ - |
+ To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)."
+
+ # https://github.com/github/releases/issues/2161
+ - |
+ To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
+
+ # https://github.com/github/releases/issues/2140
+ - |
+ If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)."
+
+ - heading: GitHub Packages
+ notes:
+ # https://github.com/github/releases/issues/2334
+ - |
+ Enterprise owners can migrate container images from the GitHub Docker registry to the GitHub Container registry. The Container registry provides the following benefits.
+
+ - Improves the sharing of containers within an organization
+ - Allows the application of granular access permissions
+ - Permits the anonymous sharing of public container images
+ - Implements OCI standards for hosting Docker images
+
+ The Container registry is in beta and subject to change. For more information, see "[Migrating your enterprise to the Container registry from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)."
+
+ - heading: Community experience
+ notes:
+ # https://github.com/github/releases/issues/2113
+ - |
+ GitHub Discussions is available for GitHub Enterprise Server. GitHub Discussions provides a central gathering space to ask questions, share ideas, and build connections. For more information, see "[GitHub Discussions](/discussions)."
+
+ # https://github.com/github/releases/issues/2259
+ - |
+ Enterprise owners can configure a policy to control whether people's usernames or full names are displayed within internal or public repositories. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-display-of-member-names-in-your-repositories)."
+
+ - heading: Organizations
+ notes:
+ # https://github.com/github/releases/issues/2019
+ - |
+ Users can create member-only READMEs for an organization. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
+
+ # https://github.com/github/releases/issues/2234
+ - |
+ Organization owners can pin a repository to an organization's profile directly from the repository via the new **Pin repository** dropdown. Pinned public repositories appear to all users of your instance, while public, private, and internal repositories are only visible to organization members.
+
+ - heading: Repositories
+ notes:
+ # https://github.com/github/releases/issues/2214
+ - |
+ While creating a fork, users can customize the fork's name. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+
+ # https://github.com/github/releases/issues/1973
+ - |
+ Users can block creation of branches that match a configured name pattern with the **Restrict pushes that create matching branches** branch protection rule. For example, if a repository's default branch changes from `master` to `main`, a repository administrator can prevent any subsequent creation or push of the `master` branch. For more information, see
+ "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#restrict-who-can-push-to-matching-branches)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
+
+ # https://github.com/github/releases/issues/2179
+ - |
+ Users can create a branch directly from a repository's **Branches** page by clicking the **New branch**. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+ # https://github.com/github/releases/issues/2220
+ - |
+ Users can delete a branch that's associated with an open pull request. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+ # https://github.com/github/releases/issues/2118
+ - |
+ Repositories with multiple licenses display all of the licenses in the "About" sidebar on the {% octicon "code" aria-label="The code icon" %} **Code** tab. For more information, see "[Licensing a repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)."
+
+ # https://github.com/github/releases/issues/2233
+ - When a user renames or moves a file to a new directory, if at least half of the file's contents are identical, the commit history indicates that the file was renamed, similar to `git log --follow`. For more information, see the [GitHub Blog](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/).
+
+ # https://github.com/github/releases/issues/2093
+ - |
+ Users can require a successful deployment of a branch before anyone can merge the pull request associated with the branch. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-deployments-to-succeed-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+ # https://github.com/github/releases/issues/2073
+ - |
+ Enterprise owners can prevent organization owners from inviting collaborators to repositories on the instance. For more information, see "[Enforcing a policy for inviting collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)."
+
+ # https://github.com/github/releases/issues/2173
+ - |
+ Users can grant exceptions to GitHub Apps for any branch protection rule that supports exceptions. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+ - heading: Commits
+ notes:
+ # https://github.com/github/releases/issues/2306
+ - |
+ For public GPG signing keys that are expired or revoked, GitHub Enterprise Server verifies Git commit signatures and show commits as verified if the user made the commit while the key was still valid. Users can also upload expired or revoked GPG keys. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
+
+ # https://github.com/github/releases/issues/1977
+ - |
+ To affirm that a commit complies with the rules and licensing governing a repository, organization owners and repository administrators can now require developers to sign off on commits made through the web interface. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)" and "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+ - heading: Pull requests
+ notes:
+ # https://github.com/github/releases/issues/2261
+ - |
+ Using the file tree located in the **Files changed** tab of a pull request, users can navigate modified files, understand the size and scope of changes, and focus reviews. The file tree appears if a pull request modifies at least two files, and the browser window is sufficiently wide. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" and "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+
+ # https://github.com/github/releases/issues/2167
+ - |
+ Users can default to using pull requests titles as the commit message for all squash merges. For more information, see "[Configuring commit squashing for pull requests](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)."
+
+ - heading: Releases
+ notes:
+ # https://github.com/github/releases/issues/2281
+ - |
+ When viewing the details for a particular release, users can see the creation date for each release asset. For more information, see "[Viewing your repository's releases and tags](/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
+
+ # https://github.com/github/releases/issues/2279
+ - While creating a release with automatically generated release notes, users can see the tag identified as the previous release, then choose to select a different tag to specify as the previous release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
+
+ - heading: Markdown
+ notes:
+ # https://github.com/github/releases/issues/2260
+ - |
+ Editing Markdown in the web interface has been improved.
+
+ - After a user selects text and pastes a URL, the selected text will become a Markdown link to the pasted URL.
+ - When a user pastes spreadsheet cells or HTML tables, the resulting text will render as a table.
+ - When a user copies text containing links, the pasted text will include the link as a Markdown link.
+
+ For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links)."
+
+ # https://github.com/github/releases/issues/2258
+ - |
+ When editing a Markdown file in the web interface, clicking the **Preview** tab will automatically scroll to the place in the preview that you were editing. The scroll location is based on the position of your cursor before you clicked the **Preview** tab.
+
+ changes:
+ - Interactive elements in the web interface such as links and buttons show a visible outline when focused with a keyboard, to help users find the current position on a page. In addition, when focused, form fields have a higher contrast outline.
+ - If a user refreshes the page while creating a new issue or pull request, the assignees, reviewers, labels and projects will all be preserved.
+
+ known_issues:
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+ - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+ - In some cases, users cannot convert existing issues to discussions.
+ - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+ - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
\ No newline at end of file
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-6/1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-6/1.yml
new file mode 100644
index 0000000000..f1add29152
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-6/1.yml
@@ -0,0 +1,33 @@
+date: '2022-08-30'
+sections:
+ bugs:
+ - 'Após desbloquear um repositório para acesso temporário, o administrador do site não conseguiu gerenciar as configurações dos produtos de segurança no repositório.'
+ - 'Chaves SSH administrativas duplicadas podem aparecer tanto no Console de Gerenciamento quanto no arquivo `/home/admin/.ssh/authorized_keys`.'
+ - 'A página de administração do site para usuários individuais em http(s)://HOSTNAME/stafftools/users/USERNAME/admin continha funcionalidades não destinadas ao Servidor do GitHub Enterprise.'
+ - 'Em alguns casos, executar `ghe-cluster-config-apply` pode replicar uma configuração vazia para nós existentes em um cluster.'
+ - 'Em alguns casos, as execuções de configuração iniciadas com `ghe-config-apply` não foram concluídas ou retornaram um erro `Incompatibilidade de contagem de contêiner`.'
+ - 'Depois de atualizar um certificado TLS autoassinado em uma instância de4 servidor do GitHub Enterprise, os elementos da interface do usuário em algumas páginas da interface da Web não apareceram.'
+ - 'Em alguns casos, as tarefas em segundo plano podem parar devido a uma biblioteca que foi usada simultaneamente, apesar de não ser thread-safe.'
+ - 'A barra de administração do site na parte superior da interface da Web continha um link quebrado para o SHA para a versão do aplicativo em execução no momento.'
+ - 'Os proprietários da organização não conseguiram definir o nível de acesso necessário para criar discussões.'
+ - 'Os usuários das discussões foram direcionados incorretamente para as diretrizes da comunidade do GitHub.com.'
+ - 'Em alguns casos, os usuários foram instruídos incorretamente a verificar seus emails antes de criar uma discussão.'
+ - 'Alertas da verificação de segredo para clientes do GitHub Advanced Security estavam ausentes na interface do usuário da Web e na API REST se um administrador do site não atualizasse diretamente para o GitHub Enterprise Server 3.4. Os alertas agora estão visíveis.'
+ changes:
+ - 'A geração de pacotes de suporte é mais rápida como resultado da sanitização de log paralelizada. Para ver mais informações sobre pacotes de suporte, confira "[Como fornecer dados ao suporte do GitHub](/support/contacting-github-support/providing-data-to-github-support)."'
+ - 'As APIs que contêm a rota `organization` ou `org` agora aceitam o slug ou a ID da organização. Anteriormente, as APIs aceitavam apenas slugs, o que fazia com que os cabeçalhos `Link` dos pontos de extremidade do GitHub Advanced Security ficassem inacessíveis. Para ver mais informações, confira "[Organizações](https://docs.github.com/rest/orgs/orgs)" na documentação da API REST.'
+ - 'O log de auditoria empresarial agora inclui mais eventos gerados pelo usuário, como `project.create`. A API REST também retorna eventos adicionais gerados pelo usuário, como `repo.create`. Para ver mais informações, confira "[Como acessar o log de auditoria da sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" e "[Como usar a API de log de auditoria da sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."'
+ - 'Em alguns casos, as réplicas de cache podem rejeitar algumas operações do Git em repositórios atualizados recentemente. Para ver mais informações sobre o armazenamento em cache do repositório, confira "[Sobre o armazenamento em cache do repositório](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
+ - 'Agora você pode configurar o banner de anúncio global como dispensável usando a API REST. Para ver mais informações, confira "[Como personalizar mensagens de usuário para sua empresa](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global- anúncio-banner)."'
+ known_issues:
+ - 'Em uma instância de {% data variables.product.prodname_ghe_server %} recém-configurada sem usuários, um invasor pode criar o primeiro usuário administrador.'
+ - 'As regras de firewall personalizadas são removidas durante o processo de atualização.'
+ - 'Arquivos LFS do Git [enviados através da interface da Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.'
+ - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo de blobs é maior que 255 caracteres.'
+ - 'Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.'
+ - 'O registro npm {% data variables.product.prodname_registry %} não retorna mais um valor temporal em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para retornar um valor temporal como parte da resposta de metadados e continuaremos a retornar esse valor no futuro quando tivermos resolvido os problemas de desempenho existentes.'
+ - 'Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive.'
+ - 'Os serviços de ação devem ser reiniciados após a restauração do dispositivo a partir do backup tomado em um host diferente.'
+ - 'Nas configurações de um repositório, habilitar a opção de permitir que usuários com acesso de leitura criem discussões não habilita esta funcionalidade.'
+ - 'Em alguns casos, os usuários não podem converter problemas existentes em discussões.'
+ - 'Padrões personalizados para verificação de segredo têm `.*` como um delimitador final, especificamente no campo "Depois do segredo". Esse delimitador causa inconsistências nas verificações de segredos nos repositórios e você pode notar lacunas no histórico de um repositório em que nenhuma verificação foi concluída. As verificações incrementais também podem ser afetadas. Para evitar problemas com verificações, modifique o final do padrão para remover o delimitador `.*`.'
diff --git a/translations/pt-BR/data/reusables/actions/workflow-basic-example-and-explanation.md b/translations/pt-BR/data/reusables/actions/workflow-basic-example-and-explanation.md
index 5590f6690f..1140778695 100644
--- a/translations/pt-BR/data/reusables/actions/workflow-basic-example-and-explanation.md
+++ b/translations/pt-BR/data/reusables/actions/workflow-basic-example-and-explanation.md
@@ -1,22 +1,17 @@
----
-ms.openlocfilehash: 53dbd22ad351ec7a1abc92107b366ecd8c71a3a9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147064535"
----
-## Criar um exemplo de fluxo de trabalho
+## Create an example workflow
-{% data variables.product.prodname_actions %} usa a sintaxe do YAML para definir o fluxo de trabalho. Cada fluxo de trabalho é armazenado como um arquivo YAML separado no seu repositório de código, em um diretório chamado `.github/workflows`.
+{% data variables.product.prodname_actions %} uses YAML syntax to define the workflow. Each workflow is stored as a separate YAML file in your code repository, in a directory named `.github/workflows`.
-Você pode criar um exemplo de fluxo de trabalho no repositório que aciona automaticamente uma série de comandos sempre que o código for carregado. Nesse fluxo de trabalho, {% data variables.product.prodname_actions %} verifica o código enviado, instala a estrutura de teste [bats](https://www.npmjs.com/package/bats) e executa um comando básico para gerar a versão bats:`bats -v`.
+You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the [bats](https://www.npmjs.com/package/bats) testing framework, and runs a basic command to output the bats version: `bats -v`.
-1. No repositório, crie o diretório `.github/workflows/` para armazenar os arquivos de fluxo de trabalho.
-1. No diretório `.github/workflows/`, crie um arquivo chamado `learn-github-actions.yml` e adicione o código a seguir.
+1. In your repository, create the `.github/workflows/` directory to store your workflow files.
+1. In the `.github/workflows/` directory, create a new file called `learn-github-actions.yml` and add the following code.
- ```yaml
+ ```yaml{:copy}
name: learn-github-actions
+ {%- ifversion actions-run-name %}
+ run-name: {% raw %}${{ github.actor }}{% endraw %} is learning GitHub Actions
+ {%- endif %}
on: [push]
jobs:
check-bats-version:
@@ -29,13 +24,13 @@ Você pode criar um exemplo de fluxo de trabalho no repositório que aciona auto
- run: npm install -g bats
- run: bats -v
```
-1. Faça commit dessas alterações e faça push para o seu repositório do {% data variables.product.prodname_dotcom %}.
+1. Commit these changes and push them to your {% data variables.product.prodname_dotcom %} repository.
-Seu novo arquivo de fluxo de trabalho de {% data variables.product.prodname_actions %} agora está instalado no seu repositório e será executado automaticamente toda vez que alguém fizer push de uma alteração no repositório. Para conferir os detalhes sobre o histórico de execução de um fluxo de trabalho, confira "[Exibir a atividade de uma execução de fluxo de trabalho](#viewing-the-activity-for-a-workflow-run)".
+Your new {% data variables.product.prodname_actions %} workflow file is now installed in your repository and will run automatically each time someone pushes a change to the repository. To see the details about a workflow's execution history, see "[Viewing the activity for a workflow run](#viewing-the-activity-for-a-workflow-run)."
-## Entender o arquivo de fluxo de trabalho
+## Understanding the workflow file
-Para ajudar você a entender como a sintaxe de YAML é usada para criar um arquivo de fluxo de trabalho, esta seção explica cada linha do exemplo Introdução:
+To help you understand how YAML syntax is used to create a workflow file, this section explains each line of the introduction's example:
| - Opcional – O nome do fluxo de trabalho, conforme ele será exibido na guia Ações do repositório do {% data variables.product.prodname_dotcom %}. + Optional - The name of the workflow as it will appear in the "Actions" tab of the {% data variables.product.prodname_dotcom %} repository. | |
| + + ```yaml + run-name: {% raw %}${{ github.actor }}{% endraw %} is learning GitHub Actions + ``` + | ++ + Optional - The name for workflow runs generated from the workflow, which will appear in the list of workflow runs on your repository's "Actions" tab. This example uses an expression with the `github` context to display the username of the actor that triggered the workflow run. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions#run-name)." + | +
| @@ -57,7 +66,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` |
-Especifica o gatilho para este fluxo de trabalho. Este exemplo usa o evento push, para que uma execução de fluxo de trabalho seja disparada sempre que alguém efetuar push de uma alteração para o repositório ou mesclar uma solicitação de pull. Isso é disparado por um push para cada branch. Para ver exemplos de sintaxe que são executados somente em pushes para branches, marcas ou caminhos específicos, confira "Sintaxe de fluxo de trabalho do {% data variables.product.prodname_actions %}".
+Specifies the trigger for this workflow. This example uses the push event, so a workflow run is triggered every time someone pushes a change to the repository or merges a pull request. This is triggered by a push to every branch; for examples of syntax that runs only on pushes to specific branches, paths, or tags, see "Workflow syntax for {% data variables.product.prodname_actions %}."
|
-Agrupa todos os trabalhos executados no fluxo de trabalho learn-github-actions.
+ Groups together all the jobs that run in the learn-github-actions workflow.
|
|
-Define um trabalho chamado check-bats-version. As chaves secundaárias definirão as propriedades do trabalho.
+Defines a job named check-bats-version. The child keys will define properties of the job.
|
|
| -Configura o trabalho a ser executado na versão mais recente de um executor do Linux do Ubuntu. Isto significa que o trabalho será executado em uma nova máquina virtual hospedada pelo GitHub. Para ver exemplos de sintaxe que usam outros executores, confira "Sintaxe de fluxo de trabalho do {% data variables.product.prodname_actions %}". + Configures the job to run on the latest version of an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by GitHub. For syntax examples using other runners, see "Workflow syntax for {% data variables.product.prodname_actions %}." | |
-Agrupa todas as etapas que são executadas no trabalho check-bats-version. Cada item aninhado nesta seção é uma ação separada ou script do shell.
+ Groups together all the steps that run in the check-bats-version job. Each item nested under this section is a separate action or shell script.
|
|
-A palavra-chave uses especifica que esta etapa executará v3 da ação actions/checkout. Esta é uma ação que faz o check-out do seu repositório para o executor, permitindo que você execute scripts ou outras ações com base no seu código (como ferramentas de compilação e teste). Você deve usar a ação de checkout sempre que o fluxo de trabalho for executado no código do repositório.
+The uses keyword specifies that this step will run v3 of the actions/checkout action. This is an action that checks out your repository onto the runner, allowing you to run scripts or other actions against your code (such as build and test tools). You should use the checkout action any time your workflow will run against the repository's code.
|
|
-Esta etapa usa a ação {% data reusables.actions.action-setup-node %} para instalar a versão especificada do Node.js (este exemplo usa a v14). Isso insere os comandos node e npm no PATH.
+ This step uses the {% data reusables.actions.action-setup-node %} action to install the specified version of the Node.js (this example uses v14). This puts both the node and npm commands in your PATH.
|
|
-A palavra-chave run instrui o trabalho a executar um comando no executor. Nesse caso, você está usando npm para instalar o pacote de teste de software bats.
+ The run keyword tells the job to execute a command on the runner. In this case, you are using npm to install the bats software testing package.
|
|
-Por fim, você executará o comando bats com um parâmetro que gera a versão do software.
+ Finally, you'll run the bats command with a parameter that outputs the software version.
|
run-name | github, inputs | |
+{%- endif %}
| concurrency | github, inputs | |
| env | github, secrets, inputs | |
| jobs.<job_id>.concurrency | github, needs, strategy, matrix, inputs | |
diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md
index fc6d84a103..b83df0ebe2 100644
--- a/translations/zh-CN/content/actions/quickstart.md
+++ b/translations/zh-CN/content/actions/quickstart.md
@@ -27,32 +27,34 @@ The following example shows you how {% data variables.product.prodname_actions %
## Creating your first workflow
1. Create a `.github/workflows` directory in your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist.
-2. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
-3. Copy the following YAML contents into the `github-actions-demo.yml` file:
- {% raw %}
- ```yaml{:copy}
- name: GitHub Actions Demo
- on: [push]
- jobs:
- Explore-GitHub-Actions:
- runs-on: ubuntu-latest
- steps:
- - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."{% endraw %}
- - name: Check out repository code
- uses: {% data reusables.actions.action-checkout %}{% raw %}
- - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- - run: echo "🖥️ The workflow is now ready to test your code on the runner."
- - name: List files in the repository
- run: |
- ls ${{ github.workspace }}
- - run: echo "🍏 This job's status is ${{ job.status }}."
+1. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
+1. Copy the following YAML contents into the `github-actions-demo.yml` file:
- ```
- {% endraw %}
-3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
- 
+ ```yaml{:copy}
+ name: GitHub Actions Demo
+ {%- ifversion actions-run-name %}
+ run-name: {% raw %}${{ github.actor }}{% endraw %} is testing out GitHub Actions 🚀
+ {%- endif %}
+ on: [push]
+ jobs:
+ Explore-GitHub-Actions:
+ runs-on: ubuntu-latest
+ steps:
+ - run: echo "🎉 The job was automatically triggered by a {% raw %}${{ github.event_name }}{% endraw %} event."
+ - run: echo "🐧 This job is now running on a {% raw %}${{ runner.os }}{% endraw %} server hosted by GitHub!"
+ - run: echo "🔎 The name of your branch is {% raw %}${{ github.ref }}{% endraw %} and your repository is {% raw %}${{ github.repository }}{% endraw %}."
+ - name: Check out repository code
+ uses: {% data reusables.actions.action-checkout %}
+ - run: echo "💡 The {% raw %}${{ github.repository }}{% endraw %} repository has been cloned to the runner."
+ - run: echo "🖥️ The workflow is now ready to test your code on the runner."
+ - name: List files in the repository
+ run: |
+ ls {% raw %}${{ github.workspace }}{% endraw %}
+ - run: echo "🍏 This job's status is {% raw %}${{ job.status }}{% endraw %}."
+ ```
+1. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
+
+ 
Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow.
diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 5033dda0ed..0db7b2a3d4 100644
--- a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -27,7 +27,23 @@ You must store workflow files in the `.github/workflows` directory of your repos
## `name`
-The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's actions page. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
+The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's "Actions" tab. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
+
+{% ifversion actions-run-name %}
+## `run-name`
+
+The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If you omit `run-name`, the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
+
+This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts.
+
+### Example
+
+{% raw %}
+```yaml
+run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
+```
+{% endraw %}
+{% endif %}
## `on`
diff --git a/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
index c768525303..3944c4fa55 100644
--- a/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
@@ -30,13 +30,15 @@ The {% data variables.product.prodname_serverless %} provides many of the benefi
The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.
+You must be signed in to use the web-based editor.
+
## Opening the {% data variables.product.prodname_serverless %}
You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways:
-- To open the repository in the same browser tab, press `.` while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
+- To open the repository in the same browser tab, press . while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
- To open the repository in a new browser tab, hold down the shift key and press `.`.
+ To open the repository in a new browser tab, press >.
- Change the URL from "github.com" to "github.dev".
- When viewing a file, use the dropdown menu next to {% octicon "pencil" aria-label="The edit icon" %} and select **Open in github.dev**.
diff --git a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
index 4516f39f99..bbd743e04a 100644
--- a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
@@ -50,7 +50,8 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
| Keyboard shortcut | Description
|-----------|------------{% ifversion fpt or ghec %}
-|. | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
+|. | Opens a repository or pull request in the web-based editor in the same browser tab. You must be signed in to use the editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."
+|> | Opens a repository or pull request in the web-based editor in a new browser tab. You must be signed in to use the editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
|Command+B (Mac) or Ctrl+B (Windows/Linux) | Inserts Markdown formatting for bolding text
|Command+I (Mac) or Ctrl+I (Windows/Linux) | Inserts Markdown formatting for italicizing text
|Command+K (Mac) or Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
index 985fd5d0f2..fcb8ff6439 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
@@ -11,6 +11,7 @@ children:
- /managing-access-to-your-projects
- /closing-and-deleting-your-projects
- /adding-your-project-to-a-repository
+ - /adding-your-project-to-a-team
allowTitleToDifferFromFilename: true
ms.openlocfilehash: ca7c42e8dcb3daf477c70248eb79d12ca9670052
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
index d2f7363dd9..e5f823f24e 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
@@ -1,115 +1,117 @@
---
-title: '管理对 {% data variables.projects.projects_v2 %} 的访问权限'
+title: 'Managing access to your {% data variables.projects.projects_v2 %}'
shortTitle: 'Managing {% data variables.projects.project_v2 %} access'
-intro: '了解如何管理团队和个人对 {% data variables.projects.project_v2 %} 的访问权限。'
+intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.'
miniTocMaxHeadingLevel: 3
versions:
- feature: projects-v2
+ feature: "projects-v2"
redirect_from:
- /issues/trying-out-the-new-projects-experience/managing-access-to-projects
type: tutorial
topics:
- Projects
allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 05fa60d5690074c217db87cd52a44b46433c014e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423811'
---
-## 关于项目访问
-组织级项目的管理员可以管理整个组织、团队、单个组织成员和外部协作者的访问权限。
-用户级项目的管理员可以邀请单个协作者并管理其访问权限。
+## About project access
-项目管理员还可以控制其项目在互联网上对每个人的可见性。 有关详细信息，请参阅“[管理项目的可见性](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)”。
+Admins of organization-level projects can manage access for the entire organization, for teams, for individual organization members, and for outside collaborators.
-## 管理组织级项目的访问权限
+Admins of user-level projects can invite individual collaborators and manage their access.
-### 管理组织中每个人的访问权限
+Project admins can also control the visibility of their project for everyone on the internet. For more information, see "[Managing the visibility of your projects](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)."
-默认的基本角色是 `write`，这意味着组织中的每个人都可以查看和编辑项目。 要更改组织中每个人的项目访问权限，您可以更改基本角色。 对基本角色的更改仅影响不是组织所有者且未被授予个人访问权限的组织成员。
+## Managing access for organization-level projects
+
+### Managing access for everyone in your organization
+
+The default base role is `write`, meaning that everyone in the organization can see and edit your project. To change project access for everyone in the organization, you can change the base role. Changes to the base role only affect organization members who are not organization owners and who are not granted individual access.
{% data reusables.projects.project-settings %}
-1. 单击“管理访问”。
- 
-2. 在“基本角色”下，选择默认角色。
- 
- - 无访问权限：只有组织所有者和被授予个人访问权限的用户才能查看该项目。 组织所有者也是项目的管理员。
- - 读取：组织中的每个人都可以查看项目。 组织所有者也是项目的管理员。
- - 写入：组织中的每个人都可以查看并编辑项目。 组织所有者也是项目的管理员。
- - 管理员：组织中的每个人都是项目的管理员。
+1. Click **Manage access**.
+ 
+2. Under **Base role**, select the default role.
+ 
+ - **No access**: Only organization owners and users granted individual access can see the project. Organization owners are also admins for the project.
+ - **Read**: Everyone in the organization can see the project. Organization owners are also admins for the project.
+ - **Write**: Everyone in the organization can see and edit the project. Organization owners are also admins for the project.
+ - **Admin**: Everyone in the organization is an admin for the project.
-### 管理组织中团队和单个成员的访问权限
+### Managing access for teams and individual members of your organization
-您还可以将团队、外部协作者和单个组织成员添加为组织级项目的协作者。 有关详细信息，请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
+You can also add teams, external collaborators, and individual organization members as collaborators for an organization-level project. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
-仅当单个用户已经是组织中的成员或组织中至少一个存储库的外部协作者时，您才能邀请该用户协作处理组织级项目。
+{% ifversion projects-v2-add-to-team %}
+
+If you grant a team read permissions or greater for a project, the project is also displayed on the team's projects page. You can also add projects to a team on the team's projects page. For more information, see "[Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)."
+
+{% endif %}
+
+You can only invite an individual user to collaborate on your organization-level project if they are already a member of the organization or an outside collaborator on at least one repository in the organization.
{% data reusables.projects.project-settings %}
-1. 单击“管理访问”。
- 
-2. 在“邀请协作者”下，搜索要邀请的团队或单个用户。
- 
-3. 为协作者选择角色。
- 
- - 读取：团队或个人可以查看项目。
- - 写入：团队或个人可以查看和编辑项目。
- - 管理员：团队或个人可以查看、编辑项目，还可为项目添加新协作者。
-4. 单击“邀请”。
- 
+1. Click **Manage access**.
+ 
+2. Under **Invite collaborators**, search for the team or individual user that you want to invite.
+ 
+3. Select the role for the collaborator.
+ 
+ - **Read**: The team or individual can view the project.
+ - **Write**: The team or individual can view and edit the project.
+ - **Admin**: The team or individual can view, edit, and add new collaborators to the project.
+4. Click **Invite**.
+ 
-### 管理现有协作者对项目的访问
+### Managing access of an existing collaborator on your project
{% data reusables.projects.project-settings %}
-1. 单击“管理访问”。
- 
-1. 在“管理访问权限”下，找到要修改其权限的协作者。
+1. Click **Manage access**.
+ 
+1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
- 可以使用“类型”和“角色”下拉菜单来筛选访问列表 。
- 
+ You can use the **Type** and **Role** drop-down menus to filter the access list.
+ 
-1. 编辑协作者的角色。
- 
-1. （可选）单击“移除”以移除协作者。
- 
+1. Edit the role for the collaborator(s).
+ 
+1. Optionally, click **Remove** to remove the collaborator(s).
+ 
-## 管理用户级项目的访问权限
+## Managing access for user-level projects
-### 授予协作者对项目的访问权限
+### Granting a collaborator access to your project
{% note %}
-这只会影响项目的协作者，而不会影响项目中的存储库。 要查看项目上的项，必须具有该项所属存储库所需的权限。 如果项目包含私有存储库中的项目，则不是存储库协作者的用户将无法查看该存储库中的项。 有关详细信息，请参阅“[设置存储库可见性](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)”和“[管理有权访问存储库的团队和人员](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)”。
+This only affects collaborators for your project, not for repositories in your project. To view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository. For more information, see "[Setting repository visibility](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
{% endnote %}
{% data reusables.projects.project-settings %}
-1. 单击“管理访问”。
- 
-2. 在“邀请协作者”下，搜索要邀请的用户。
- 
-3. 为协作者选择角色。
- 
- - 读取：个人可以查看项目。
- - 写入：个人可以查看和编辑项目。
- - 管理员：个人可以查看、编辑项目，还可为项目添加新协作者。
-4. 单击“邀请”。
- 
+1. Click **Manage access**.
+ 
+2. Under **Invite collaborators**, search for the user that you want to invite.
+ 
+3. Select the role for the collaborator.
+ 
+ - **Read**: The individual can view the project.
+ - **Write**: The individual can view and edit the project.
+ - **Admin**: The individual can view, edit, and add new collaborators to the project.
+4. Click **Invite**.
+ 
-### 管理现有协作者对项目的访问
+### Managing access of an existing collaborator on your project
{% data reusables.projects.project-settings %}
-1. 单击“管理访问”。
- 
-1. 在“管理访问权限”下，找到要修改其权限的协作者。
+1. Click **Manage access**.
+ 
+1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
- 可以使用“类型”和“角色”下拉菜单来筛选访问列表 。
- 
+ You can use the **Type** and **Role** drop-down menus to filter the access list.
+ 
-1. 编辑协作者的角色。
- 
-1. （可选）单击“移除”以移除协作者。
- 
+1. Edit the role for the collaborator(s).
+ 
+1. Optionally, click **Remove** to remove the collaborator(s).
+ 
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index 58993601d8..522bc91b7a 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -1,6 +1,6 @@
---
-title: '管理团队对组织 {% data variables.product.prodname_project_v1 %} 的访问权限'
-intro: '作为组织所有者或 {% data variables.projects.projects_v1_board %} 管理员，你可以授予单个成员对组织拥有的 {% data variables.projects.projects_v1_board %} 的访问权限。'
+title: Managing team access to an organization {% data variables.product.prodname_project_v1 %}
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
redirect_from:
- /articles/managing-team-access-to-an-organization-project-board
- /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board
@@ -14,46 +14,58 @@ topics:
- Teams
shortTitle: Manage team access
allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 9672dddc31d39349ec99488313e021bca0c12c60
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422864'
---
+
{% data reusables.projects.project_boards_old %}
{% warning %}
-警告：
-- 如果团队可以直接访问 {% data variables.projects.projects_v1_board %}，可以更改团队的权限级别。 如果团队对 {% data variables.projects.projects_v1_board %} 的访问权限是从父团队继承的，则必须更改父团队对 {% data variables.projects.projects_v1_board %} 的访问权限。
-- 如果为父团队添加或移除 {% data variables.projects.projects_v1_board %} 访问权限，每个父级的子团队也将收到或失去对 {% data variables.projects.projects_v1_board %} 的访问权限。 有关详细信息，请参阅“[关于团队](/articles/about-teams)”。
+**Warnings:**
+- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}.
+- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. For more information, see "[About teams](/articles/about-teams)."
{% endwarning %}
-## 授予团队对 {% data variables.projects.projects_v1_board %} 的访问权限
+## Giving a team access to a {% data variables.projects.projects_v1_board %}
-可以授予整个团队对 {% data variables.projects.projects_v1_board %} 的相同权限级别。
+You can give an entire team the same permission level to a {% data variables.projects.projects_v1_board %}.
{% note %}
-注意：{% data reusables.project-management.cascading-permissions %} 例如，如果组织所有者授予团队读取 {% data variables.projects.projects_v1_board %} 的权限，且 {% data variables.projects.projects_v1_board %} 管理员以个人协作者的身份授予其中一个团队成员对该板的管理员权限，则该成员将拥有 {% data variables.projects.projects_v1_board %} 的管理员权限。 有关详细信息，请参阅“[组织的 {% data variables.product.prodname_project_v1_caps %} 权限](/articles/project-board-permissions-for-an-organization)”。
+**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the {% data variables.projects.projects_v1_board %}. For more information see, "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
{% endnote %}
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %}
-8. 在左侧边栏中，单击“团队”。
-9. 要添加团队，请单击“添加团队: 选择团队”。 然后，从下拉菜单中选择一个团队，或者搜索要添加的团队。
- 
-10. 在团队名称旁边，使用下拉菜单选择所需的权限级别：读取、写入或管理员。
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+8. In the left sidebar, click **Teams**.
+9. To add a team, click **Add a team: Select team**. Then, choose a team from the drop-down menu or search for the team you'd like to add.
+ 
+10. Next to the team name, use the drop-down menu to select the desired permission level: **Read**, **Write**, or **Admin**.
+ 
-## 配置团队对 {% data variables.projects.projects_v1_board %} 的访问权限
+## Configuring a team's access to a {% data variables.projects.projects_v1_board %}
-如果团队对 {% data variables.projects.projects_v1_board %} 的访问权限是从父团队继承的，则必须更改父团队对 {% data variables.projects.projects_v1_board %} 的访问权限，以更新子团队的访问权限。
+If a team's access to a {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %} to update access to the child teams.
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %}
-4. 在团队的对话上方，单击 {% octicon "project" aria-label="The Projects icon" %}“项目”。
- 
-5. 若要更改权限级别，请使用要更新的 {% data variables.projects.projects_v1_board %} 的右侧的下拉列表。 若要移除 {% data variables.projects.projects_v1_board %}，请单击 {% octicon "trash" aria-label="The trash icon" %}。
- 
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.specific_team %}
+4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
+ 
+5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**.
+ 
+
+{% ifversion projects-v2-add-to-team %}
+
+## Further reading
+
+- [Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)
+
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md
index b866e36b70..2257eb1ecd 100644
--- a/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md
+++ b/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md
@@ -49,9 +49,20 @@ You can search for archived repositories. For more information, see "[Searching
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", click **Archive this repository** or **Unarchive this repository**.
+3. Under "Danger Zone", click **Archive this repository**
4. Read the warnings.
-5. Type the name of the repository you want to archive or unarchive.
+5. Type the name of the repository you want to archive.
6. Click **I understand the consequences, archive this repository**.
+
+## Unarchiving a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Danger Zone", click **Unarchive this repository**
+ 
+4. Read the warnings.
+5. Type the name of the repository you want to unarchive.
+ 
+6. Click **I understand the consequences, unarchive this repository**.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml
index 8a687f91ff..b5a846e1c3 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml
@@ -27,4 +27,4 @@ sections:
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
- - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+ - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
\ No newline at end of file
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml
index 05d73e8f28..8ec4162b87 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml
@@ -1,41 +1,33 @@
date: '2022-08-30'
sections:
bugs:
- - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
- - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
- - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
- - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
- - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
- - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
- - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
- - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
- - Organization owners were unable to set the level of access required to create discussions.
- - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
- - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
- - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
+ - 解锁存储库以进行临时访问后，站点管理员无法管理存储库中安全产品的设置。
+ - 管理控制台和 `/home/admin/.ssh/authorized_keys` 文件中可能会出现重复的管理 SSH 密钥。
+ - "http(s)://HOSTNAME/stafftools/users/USERNAME/admin 的个人用户的站点管理员页面包含不适用于 GitHub Enterprise Server 的功能。"
+ - 在某些情况下，运行 `ghe-cluster-config-apply` 可以将空配置复制到群集中的现有节点。
+ - 在某些情况下，以 `ghe-config-apply` 开始的配置运行未完成，或返回了 `Container count mismatch` 错误。
+ - 在 GitHub Enterprise Server 实例上更新自签名 TLS 证书后，Web 界面中某些页面上的 UI 元素没有显示。
+ - 在某些情况下，尽管不是线程安全的，但由于同时使用的库，可能会导致后台任务停止。
+ - Web 界面顶部的站点管理员栏包含指向当前正在运行的应用程序版本的 SHA 的断开链接。
+ - 组织所有者无法设置创建讨论所需的访问级别。
+ - 讨论用户被错误地引导至 GitHub.com 的社区指南。
+ - 在某些情况下，系统错误地指示用户在创建讨论之前验证其电子邮件。
+ - 如果站点管理员没有直接升级到 GitHub Enterprise Server 3.4，则 Web UI 和 REST API 中缺少来自 GitHub Advanced Security 客户的机密扫描的警报。警报现在可见。
changes:
- - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
- - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
- - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
- - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
- - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+ - "由于并行日志清理，支持包的生成速度更快。有关支持包的详细信息，请参阅“[将数据提供给 GitHub 支持](/support/contacting-github-support/providing-data-to-github-support)”。"
+ - "包含 `organization` 或 `org` 路由的 API 现在接受组织的 slug 或 ID。以前，API 只接受 slug，这导致 GitHub Advanced Security 终结点的 `Link` 标头无法访问。有关详细信息，请参阅 REST API 文档中的“[组织](https://docs.github.com/rest/orgs/orgs)”。"
+ - "企业审核日志现在包含更多用户生成的事件，例如 `project.create`。REST API 还返回其他用户生成的事件，例如 `repo.create`。有关详细信息，请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for -your-enterprise)”和“[使用企业的审核日志 API](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit- log-api-for-your-enterprise#querying-the-audit-log-rest-api)”。"
+ - "在某些情况下，缓存副本可能会拒绝对最近更新的存储库的某些 Git 操作。有关存储库缓存的详细信息，请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。"
+ - "你现在可以使用 REST API 将全局公告横幅配置为可关闭。有关详细信息，请参阅“[为企业自定义用户消息](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)”。"
known_issues:
- - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
- - Custom firewall rules are removed during the upgrade process.
- - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
- - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
- - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
- - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
- - In some cases, users cannot convert existing issues to discussions.
- - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
- - |
- Running `ghe-repl-status` while upgrading a replica node may indicate `WARNING: git replication is behind the primary`. This warning is due to a change in how GitHub Enterprise Server 3.6.0 and later stores repositories. You can safely ignore this message, and the upgrade will proceed normally. [Updated: 2022-09-26]
- - |
- Hotpatch upgrades to {% data variables.product.prodname_ghe_server %} 3.6.2 may fail. Upgrades with the full `.pkg` are unaffected. If the upgrade fails for your instance, you can work around the issue in one of two ways.
- 1. SSH into the affected node and run `sudo dpkg --configure -a`, then start the upgrade again.
- 2. Alternatively, run the full `.pkg` upgrade.
-
- If you're unable to upgrade, or if you need further assistance, contact GitHub Support. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-09-26]
\ No newline at end of file
+ - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。"
+ - 自定义防火墙规则在升级过程中被删除。
+ - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。"
+ - 如果问题包含指向同一存储库中 Blob 的永久链接，且 Blob 的文件路径长度超过 255 个字符，则无法关闭问题。
+ - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。
+ - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。"
+ - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。
+ - 从不同主机上的备份恢复实例后，需要重新启动操作服务。
+ - 在存储库的设置中，启用允许具有读取访问权限的用户创建讨论的选项不会启用此功能。
+ - 在某些情况下，用户无法将现有问题转换为讨论。
+ - 机密扫描的自定义模式将 `.*` 作为结束分隔符，特别是在“机密之后”字段中。此分隔符会导致跨存储库的机密扫描不一致，并且你可能会注意到存储库历史记录中没有完成扫描的间隙。增量扫描也可能受到影响。为防止出现扫描问题，请修改模式的结尾以删除 `.*` 分隔符。
diff --git a/translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md b/translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md
index da0886005a..1140778695 100644
--- a/translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md
+++ b/translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md
@@ -1,22 +1,17 @@
----
-ms.openlocfilehash: 53dbd22ad351ec7a1abc92107b366ecd8c71a3a9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147064536"
----
-## 创建示例工作流程
+## Create an example workflow
-{% data variables.product.prodname_actions %} 使用 YAML 语法来定义工作流程。 每个工作流都作为单独的 YAML 文件存储在代码存储库中名为 `.github/workflows` 的目录中。
+{% data variables.product.prodname_actions %} uses YAML syntax to define the workflow. Each workflow is stored as a separate YAML file in your code repository, in a directory named `.github/workflows`.
-您可以在仓库中创建示例工作流程，只要推送代码，该工作流程就会自动触发一系列命令。 在此工作流中，{% data variables.product.prodname_actions %} 签出推送的代码，安装 [bats](https://www.npmjs.com/package/bats) 测试框架，并运行基本命令来输出 bats 版本：`bats -v`。
+You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the [bats](https://www.npmjs.com/package/bats) testing framework, and runs a basic command to output the bats version: `bats -v`.
-1. 在存储库中，创建 `.github/workflows/` 目录来存储工作流文件。
-1. 在 `.github/workflows/` 目录中，创建一个名为 `learn-github-actions.yml` 的新文件并添加以下代码。
+1. In your repository, create the `.github/workflows/` directory to store your workflow files.
+1. In the `.github/workflows/` directory, create a new file called `learn-github-actions.yml` and add the following code.
- ```yaml
+ ```yaml{:copy}
name: learn-github-actions
+ {%- ifversion actions-run-name %}
+ run-name: {% raw %}${{ github.actor }}{% endraw %} is learning GitHub Actions
+ {%- endif %}
on: [push]
jobs:
check-bats-version:
@@ -29,13 +24,13 @@ ms.locfileid: "147064536"
- run: npm install -g bats
- run: bats -v
```
-1. 提交这些更改并将其推送到您的 {% data variables.product.prodname_dotcom %} 仓库。
+1. Commit these changes and push them to your {% data variables.product.prodname_dotcom %} repository.
-您的新 {% data variables.product.prodname_actions %} 工作流程文件现在安装在您的仓库中，每次有人推送更改到仓库时都会自动运行。 若要查看关于工作流执行历史记录的详细信息，请参阅“[查看工作流运行的活动](#viewing-the-activity-for-a-workflow-run)”。
+Your new {% data variables.product.prodname_actions %} workflow file is now installed in your repository and will run automatically each time someone pushes a change to the repository. To see the details about a workflow's execution history, see "[Viewing the activity for a workflow run](#viewing-the-activity-for-a-workflow-run)."
-## 了解工作流程文件
+## Understanding the workflow file
-为帮助您了解如何使用 YAML 语法来创建工作流程文件，本节解释介绍示例的每一行：
+To help you understand how YAML syntax is used to create a workflow file, this section explains each line of the introduction's example:
| 可选 - 工作流的名称，它将显示在 {% data variables.product.prodname_dotcom %} 存储库的“操作”选项卡中。 - + | + Optional - The name of the workflow as it will appear in the "Actions" tab of the {% data variables.product.prodname_dotcom %} repository. |
| + + ```yaml + run-name: {% raw %}${{ github.actor }}{% endraw %} is learning GitHub Actions + ``` + | ++ + Optional - The name for workflow runs generated from the workflow, which will appear in the list of workflow runs on your repository's "Actions" tab. This example uses an expression with the `github` context to display the username of the actor that triggered the workflow run. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions#run-name)." + | +
| @@ -57,7 +66,7 @@ ms.locfileid: "147064536" ``` |
-指定此工作流程的触发器。 此示例使用 push 事件，因此每当有人将更改推送到存储库或合并拉取请求时都会触发工作流运行。 这是由到每个分支的推送触发的；有关仅在推送到特定分支、路径或标记时运行的语法示例，请参阅“{% data variables.product.prodname_actions %} 的工作流语法”。
+Specifies the trigger for this workflow. This example uses the push event, so a workflow run is triggered every time someone pushes a change to the repository or merges a pull request. This is triggered by a push to every branch; for examples of syntax that runs only on pushes to specific branches, paths, or tags, see "Workflow syntax for {% data variables.product.prodname_actions %}."
|
-将 learn-github-actions 工作流中运行的所有作业组合在一起。
+ Groups together all the jobs that run in the learn-github-actions workflow.
|
|
-定义一个名为 check-bats-version 作业。 子键将定义作业的属性。
+Defines a job named check-bats-version. The child keys will define properties of the job.
|
|
| -将作业配置为在最新版本的 Ubuntu Linux 运行器上运行。 这意味着该作业将在 GitHub 托管的新虚拟机上执行。 有关使用其他运行器的语法示例，请参阅“{% data variables.product.prodname_actions %} 的工作流语法”。 + Configures the job to run on the latest version of an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by GitHub. For syntax examples using other runners, see "Workflow syntax for {% data variables.product.prodname_actions %}." | |
-将在 check-bats-version 作业中运行的所有步骤组合在一起。 此部分下嵌套的每项都是一个单独的操作或 shell 脚本。
+ Groups together all the steps that run in the check-bats-version job. Each item nested under this section is a separate action or shell script.
|
|
-uses 关键字指定此步骤将运行 actions/checkout 操作的 v3。 这是一个将存储库签出到运行器上的操作，允许您对代码（如生成和测试工具）运行脚本或其他操作。 每当工作流程将针对存储库的代码运行时，都应使用签出操作。
+The uses keyword specifies that this step will run v3 of the actions/checkout action. This is an action that checks out your repository onto the runner, allowing you to run scripts or other actions against your code (such as build and test tools). You should use the checkout action any time your workflow will run against the repository's code.
|
|
-此步骤使用 {% data reusables.actions.action-setup-node %} 操作安装指定的 Node.js 版本（本示例使用 v14）。 这会将 node 和 npm 命令都放在 PATH 中。
+ This step uses the {% data reusables.actions.action-setup-node %} action to install the specified version of the Node.js (this example uses v14). This puts both the node and npm commands in your PATH.
|
|
-run 关键字指示作业在运行器上执行命令。 在这种情况下，你使用 npm 来安装 bats 软件测试包。
+ The run keyword tells the job to execute a command on the runner. In this case, you are using npm to install the bats software testing package.
|
|
-最后，你将使用输出软件版本的参数运行 bats 命令。
+ Finally, you'll run the bats command with a parameter that outputs the software version.
|