diff --git a/translations/log/msft-pt-resets.csv b/translations/log/msft-pt-resets.csv index b548c40b6e..368803d923 100644 --- a/translations/log/msft-pt-resets.csv +++ b/translations/log/msft-pt-resets.csv @@ -219,6 +219,7 @@ translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponso translations/pt-BR/data/glossaries/internal.yml,file deleted because it no longer exists in main translations/pt-BR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main translations/pt-BR/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main +translations/pt-BR/data/reusables/actions/hardware-requirements-3.6.md,file deleted because it no longer exists in main translations/pt-BR/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main translations/pt-BR/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main @@ -615,7 +616,7 @@ translations/pt-BR/content/code-security/dependabot/working-with-dependabot/keep translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md,rendering error translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error -translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,broken liquid tags +translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,rendering error translations/pt-BR/content/code-security/getting-started/github-security-features.md,rendering error translations/pt-BR/content/code-security/getting-started/securing-your-organization.md,rendering error translations/pt-BR/content/code-security/getting-started/securing-your-repository.md,rendering error @@ -900,6 +901,7 @@ translations/pt-BR/content/repositories/releasing-projects-on-github/comparing-r translations/pt-BR/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error translations/pt-BR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags +translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,broken liquid tags translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md,rendering error diff --git a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md index 5a18705739..fed4af9a0b 100644 --- a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md @@ -215,6 +215,12 @@ For more information on how to configure this setting, see {% ifversion allow-ac These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. +{% note %} + +**Note:** {% data variables.product.prodname_dotcom %}-hosted runners do not scan for malicious code downloaded by a user during their job, such as a compromised third party library. + +{% endnote %} + ### Accessing secrets Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token). diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index 5b79fefc07..fd0656617f 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -77,9 +77,15 @@ Maximum concurrency was measured using multiple repositories, job duration of ap {%- endif %} -{%- ifversion ghes = 3.6 %} +{%- ifversion ghes > 3.5 %} -{% data reusables.actions.hardware-requirements-3.6 %} + +| vCPUs | Memory | Maximum Connected Runners | +| :---| :--- | :--- | +| 8 | 64 GB | 740 runners | +| 32 | 160 GB | 2700 runners | +| 96 | 384 GB | 7000 runners | +| 128 | 512 GB | 7000 runners | {% data variables.product.company_short %} measured maximum connected runners using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md index 49ffd87e44..b2d1e3c168 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md @@ -19,11 +19,11 @@ children: - /configuring-dependabot-alerts - /viewing-and-updating-dependabot-alerts - /configuring-notifications-for-dependabot-alerts -ms.openlocfilehash: 04365ffa391c8da15c34f1e0651d9efa4ebb1a42 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf +ms.openlocfilehash: b9abda5288d4f0dfed2175b0e944c0d1bc48f3f7 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146455490' +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113952' --- diff --git a/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md new file mode 100644 index 0000000000..7f477546e0 --- /dev/null +++ b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md @@ -0,0 +1,51 @@ +--- +title: Adicionando um colaborador a uma consultoria de segurança de repositório +intro: É possível adicionar outros usuários ou equipes para colaborar em uma consultoria de segurança com você. +redirect_from: + - /articles/adding-a-collaborator-to-a-maintainer-security-advisory + - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory + - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory + - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory + - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities + - Collaboration +shortTitle: Add collaborators +ms.openlocfilehash: d080fa5d7b66d9ce89b7985f689133e52ec69cc3 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113963' +--- +Todas as pessoas com permissões de administrador para uma consultora de segurança podem adicionar colaboradores à consultora de segurança. + +{% data reusables.security-advisory.repository-level-advisory-note %} + +## Adicionar um colaborador a uma consultora de segurança + +Os colaboradores têm permissões de gravação para a consultoria de segurança. Para obter mais informações, confira "[Níveis de permissão para consultorias de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)". + +{% note %} + +{% data reusables.repositories.security-advisory-collaborators-public-repositories %} Para obter mais informações sobre como remover um colaborador em uma consultoria de segurança, confira "[Como remover um colaborador de uma consultoria de segurança do repositório](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)". + +{% endnote %} + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. Na lista "consultoria de segurança", clique na consultoria de segurança à qual deseja adicionar um colaborador. +5. No lado direito da página, em "Colaboradores", digite o nome do usuário ou da equipe que você gostaria de adicionar à consultora de segurança. + ![Campo usado para digitar o nome de usuário ou a equipe](/assets/images/help/security/add-collaborator-field.png) +6. Clique em **Adicionar**. + ![Botão Adicionar](/assets/images/help/security/security-advisory-add-collaborator-button.png) + +## Leitura adicional + +- "[Níveis de permissão para consultorias de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)" +- "[Como remover um colaborador de uma consultoria de segurança do repositório](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)" diff --git a/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md new file mode 100644 index 0000000000..c72b952d9d --- /dev/null +++ b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md @@ -0,0 +1,91 @@ +--- +title: Colaborando em uma bifurcação privada temporária para resolver uma vulnerabilidade de segurança do repositório +intro: Você pode criar uma bifurcação privada temporária para colaborar de maneira privada na correção de uma vulnerabilidade de segurança em seu repositório. +redirect_from: + - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability + - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability + - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability + - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities + - Collaboration + - Forks +shortTitle: Temporary private forks +ms.openlocfilehash: c5d4f5f8b58498f995a473b4c0c0f3c38ea96083 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113961' +--- +{% data reusables.security-advisory.repository-level-advisory-note %} + +## Pré-requisitos + +Antes de poder colaborar em uma bifurcação privada temporária, você deverá criar um rascunho da consultoria de segurança. Para obter mais informações, confira "[Como criar um aviso de segurança do repositório](/code-security/repository-security-advisories/creating-a-repository-security-advisory)". + +## Criar uma bifurcação privada temporária + +Qualquer pessoa com permissões de administrador em uma consultoria de segurança pode criar uma bifurcação privada temporária. + +Para manter as informações sobre vulnerabilidades em segurança, as integrações, incluindo CI, não podem acessar bifurcações privadas temporárias. + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. Na lista "consultoria de segurança", clique na consultoria de segurança que você gostaria de criar uma bifurcação privada temporária. + ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) +5. Clique em **Novo fork privado temporário**. + ![Botão Novo fork privado temporário](/assets/images/help/security/new-temporary-private-fork-button.png) + +## Adicionar colaboradores a uma bifurcação temporária privada + +Qualquer pessoa com permissão de administrador para uma consultoria de segurança pode adicionar colaboradores ao consultor de segurança, e os colaboradores na consultoria de segurança podem acessar uma bifurcação privada temporária. Para obter mais informações, confira "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)". + +## Adicionar alterações a uma bifurcação privada temporária + +Qualquer pessoa com permissões de gravação em uma consultoria de segurança pode adicionar alterações a uma bifurcação privada temporária. + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. Na lista "consultoria de segurança", clique na consultoria de segurança à qual deseja adicionar alterações. + ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) +5. Adicione as alterações no {% data variables.product.product_name %} ou localmente: + - Para adicionar alterações no {% data variables.product.product_name %}, em "Adicionar alterações a este aviso", clique **no fork privado temporário**. Em seguida, crie um branch e edite os arquivos. Para obter mais informações, confira "[Como criar e excluir branches no seu repositório](/articles/creating-and-deleting-branches-within-your-repository)" e "[Como editar arquivos](/repositories/working-with-files/managing-files/editing-files)". + - Para adicionar as alterações localmente, siga as instruções em "Clonar e criar um novo branch" e "Faça suas alterações e, em seguida, faça o push." + ![Caixa Adicionar alterações a este aviso](/assets/images/help/security/add-changes-to-this-advisory-box.png) + +## Criar uma pull request de uma bifurcação privada temporária + +Qualquer pessoa com permissões de gravação em uma consultoria de segurança pode criar uma pull request de uma bifurcação privada temporária. + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. Na lista "consultoria de segurança" clique na consultoria de segurança na qual deseja criar um pull request. + ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) +5. À direita do nome do branch, clique em **Comparação e solicitação de pull**. + ![Botão Comparação e solicitação de pull](/assets/images/help/security/security-advisory-compare-and-pr.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %} + +{% data reusables.repositories.merge-all-pulls-together %} Para obter mais informações, confira "[Como mesclar alterações em um aviso de segurança](#merging-changes-in-a-security-advisory)". + +## Mesclar alterações em uma consultoria de segurança + +Qualquer pessoa com permissão de administrador para uma consultoria de segurança pode mesclar alterações em uma consultora de segurança. + +{% data reusables.repositories.merge-all-pulls-together %} + +Antes de poder mesclar as alterações em uma consultoria de segurança, todo pull request aberto na bifurcação privada temporária deverá ser mesclada. Pode haver conflitos de merge e os requisitos de proteção do branch devem ser atendidos. Para manter as informações sobre vulnerabilidades seguras, as verificações de status não são executadas em pull requests de bifurcações privadas temporárias. Para obter mais informações, confira "[Sobre os branches protegidos](/articles/about-protected-branches)". + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. Na lista "consultoria de segurança", clique na consultoria de segurança com as alterações que gostaria de mesclar. + ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) +5. Para mesclar todas as solicitações de pull em aberto no fork privado temporário, clique em **Mesclar solicitações de pull**. + ![Botão Mesclar solicitações de pull](/assets/images/help/security/merge-pull-requests-button.png) + +Após mesclar as alterações em uma consultoria de segurança, você poderá publicar a consultoria de segurança para alertar a sua comunidade sobre a vulnerabilidade de segurança em versões anteriores do seu projeto. Para obter mais informações, confira "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)". + +## Leitura adicional + +- "[Níveis de permissão para avisos de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)" diff --git a/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md new file mode 100644 index 0000000000..ff8dd6c6be --- /dev/null +++ b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md @@ -0,0 +1,51 @@ +--- +title: Níveis de permissão para consultorias de segurança do repositório +intro: As ações que você pode tomar em uma consultoria de segurança dependem do fato de você ter permissões de administrador ou de gravação na consultoria de segurança. +redirect_from: + - /articles/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories + - /code-security/security-advisories/permission-levels-for-security-advisories + - /code-security/repository-security-advisories/permission-levels-for-repository-security-advisories +versions: + fpt: '*' + ghec: '*' +type: reference +topics: + - Security advisories + - Vulnerabilities + - Permissions +shortTitle: Permission levels +ms.openlocfilehash: f4195822de121780f1629fda3d646170d4c4e566 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113962' +--- +Este artigo aplica-se apenas às consultorias de segurança a nível de repositório. Qualquer pessoa pode contribuir com avisos de segurança global no {% data variables.product.prodname_advisory_database %} em [github.com/advisories](https://github.com/advisories). As edições nas consultorias globais não mudarão ou afetarão a forma como a consultoria aparece no repositório. Para obter mais informações, confira "[Como editar avisos de segurança no {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)". + +## Visão geral das permissões + +{% data reusables.repositories.security-advisory-admin-permissions %} Para obter mais informações sobre como adicionar um colaborador a um aviso de segurança, confira "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)". + +Ação | Permissões de gravação | Permissões de administrador | +------ | ----------------- | ----------------- | +Veja um rascunho da consultoria de segurança | X | X | +Adicionar colaboradores ao aviso de segurança (confira "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)") | | X | +Editar e excluir quaisquer comentários na consultoria de segurança | X | X | +Criar um fork privado temporário no aviso de segurança (confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | X | +Adicionar alterações a um fork privado temporário no aviso de segurança (confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | X | X | +Criar solicitações de pull em um fork privado temporário (confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | X | X | +Mesclar alterações no aviso de segurança (confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | X | +Adicionar e editar metadados no aviso de segurança (confira "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | X | X | +Adicionar e remover créditos para um aviso de segurança (confira "[Como editar um aviso de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)") | X | X | +Fechar o rascunho da consultoria de segurança | | X | +Publicar o aviso de segurança (confira "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | | X | + +## Leitura adicional + +- "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)" +- "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)" +- "[Como remover um colaborador de um aviso de segurança do repositório](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)" +- "[Como retirar um aviso de segurança do repositório](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" diff --git a/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md new file mode 100644 index 0000000000..96614e89a1 --- /dev/null +++ b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md @@ -0,0 +1,43 @@ +--- +title: Removendo um colaborador de uma consultoria de segurança de repositório +intro: 'Ao remover um colaborador de uma consultoria de segurança do repositório, ele perderá acesso de leitura e gravação às discussões e metadados da consultoria de segurança.' +redirect_from: + - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory + - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory + - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities + - Collaboration +shortTitle: Remove collaborators +ms.openlocfilehash: 77c21bea9c593935ee1b92028fc52859320f5a38 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113959' +--- +As pessoas com permissões de administrador para uma consultoria de segurança podem remover colaboradores da consultoria de segurança. + +{% data reusables.security-advisory.repository-level-advisory-note %} + +## Remover um colaborador de uma consultoria de segurança + +{% data reusables.repositories.security-advisory-collaborators-public-repositories %} + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. Na lista "consultoria de segurança" clique na consultoria de segurança da qual deseja remover um colaborador. + ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) +5. No lado direito da página, em "Colaboradores", encontre o nome do usuário ou da equipe que deseja remover da consultoria de segurança. + ![Colaborador no aviso de segurança](/assets/images/help/security/security-advisory-collaborator.png) +6. Ao lado do colaborador que deseja remover, clique no ícone **X**. + ![Ícone X para remover o colaborador no aviso de segurança](/assets/images/help/security/security-advisory-remove-collaborator-x.png) + +## Leitura adicional + +- "[Níveis de permissão para avisos de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)" diff --git a/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md new file mode 100644 index 0000000000..50886b9c9c --- /dev/null +++ b/translations/pt-BR/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md @@ -0,0 +1,29 @@ +--- +title: Retirando uma consultoria de segurança do repositório +intro: Você pode retirar uma consultoria de segurança do repositório que você publicou. +redirect_from: + - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory + - /code-security/security-advisories/withdrawing-a-security-advisory + - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities +shortTitle: Withdraw repository advisories +ms.openlocfilehash: 71a6560c463384b032546b824e5f4294ced568e5 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113947' +--- +{% data reusables.security-advisory.repository-level-advisory-note %} + +Se você publicar uma consultoria de segurança por engano, poderá retirar a consultoria de segurança entrando em contato com {% data variables.contact.contact_support %}. + +## Leitura adicional + +- "[Editando uma consultoria de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)" diff --git a/translations/pt-BR/content/codespaces/guides.md b/translations/pt-BR/content/codespaces/guides.md index 239552e325..84b442a778 100644 --- a/translations/pt-BR/content/codespaces/guides.md +++ b/translations/pt-BR/content/codespaces/guides.md @@ -55,11 +55,11 @@ includeGuides: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces - /codespaces/codespaces-reference/disaster-recovery-for-codespaces - /codespaces/codespaces-reference/security-in-codespaces -ms.openlocfilehash: 54ba7cc4fbacd536f0438626281d1b59252eb3f1 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 24bf08da053efd9f822b1eb43bacbbe822c1ba8b +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147783108' +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113894' --- diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md index 8bf26a6ec1..f9ce7fd55a 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md @@ -19,11 +19,11 @@ children: - /setting-a-minimum-specification-for-codespace-machines - /automatically-opening-files-in-the-codespaces-for-a-repository - /adding-a-codespaces-badge -ms.openlocfilehash: 1e172243dc351f0a173c8624b66914e1c3795495 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 4649ef4e36dff0b37d4a579ecd56bbb0edd2a184 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147783036' +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113953' --- diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md index b59a5335e2..7a6fcdc772 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md @@ -1,6 +1,6 @@ --- -title: Sobre armazenamento de arquivo grande do Git -intro: '{% data variables.product.product_name %} limita o tamanho dos arquivos permitidos nos repositórios. Para rastrear arquivos além desse limite, você pode usar {% data variables.large_files.product_name_long %}.' +title: About Git Large File Storage +intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' redirect_from: - /articles/about-large-file-storage - /articles/about-git-large-file-storage @@ -12,35 +12,33 @@ versions: ghae: '*' ghec: '*' shortTitle: Git Large File Storage -ms.openlocfilehash: af198fe13f69fc4768178aea74a03f27a82ec20b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126964' --- -## Sobre o {% data variables.large_files.product_name_long %} -O {% data variables.large_files.product_name_short %} manipula arquivos grandes armazenando referências ao arquivo no repositório, mas não no próprio arquivo. Para explorar a arquitetura do Git, o {% data variables.large_files.product_name_short %} cria um arquivo de ponteiro que funciona como uma referência ao arquivo real (que é armazenado em outro lugar). O {% data variables.product.product_name %} gerencia esse arquivo de ponteiro no seu repositório. Quando você clona o repositório, o {% data variables.product.product_name %} usa o arquivo de ponteiro como um mapa para encontrar o arquivo grande para você. +## About {% data variables.large_files.product_name_long %} -{% ifversion fpt or ghec %} Usando o {% data variables.large_files.product_name_short %}, você pode armazenar arquivos até: +{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.product_name %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.product_name %} uses the pointer file as a map to go and find the large file for you. -| Produto | Tamanho máximo do arquivo | +{% ifversion fpt or ghec %} +Using {% data variables.large_files.product_name_short %}, you can store files up to: + +| Product | Maximum file size | |------- | ------- | | {% data variables.product.prodname_free_user %} | 2 GB | | {% data variables.product.prodname_pro %} | 2 GB | | {% data variables.product.prodname_team %} | 4 GB | | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %} -Ao usar {% data variables.large_files.product_name_short %}, você pode armazenar arquivos de até 5 GB no seu repositório. -{% endif %} +Using {% data variables.large_files.product_name_short %}, you can store files up to 5 GB in your repository. +{% endif %} -Também é possível usar o {% data variables.large_files.product_name_short %} com o {% data variables.product.prodname_desktop %}. Para obter mais informações sobre como clonar repositórios do Git LFS no {% data variables.product.prodname_desktop %}, confira "[Como clonar um repositório do GitHub para o GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". +{% data reusables.repositories.git-lfs %} + +You can also use {% data variables.large_files.product_name_short %} with {% data variables.product.prodname_desktop %}. For more information about cloning Git LFS repositories in {% data variables.product.prodname_desktop %}, see "[Cloning a repository from GitHub to GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)." {% data reusables.large_files.can-include-lfs-objects-archives %} -## Formato do arquivo de ponteiro +## Pointer file format -O arquivo de ponteiro do {% data variables.large_files.product_name_short %} tem esta aparência: +{% data variables.large_files.product_name_short %}'s pointer file looks like this: ``` version {% data variables.large_files.version_name %} @@ -48,16 +46,16 @@ oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5 size 84977953 ``` -Ele rastreia a `version` do {% data variables.large_files.product_name_short %} que está sendo usada, seguido de um identificador exclusivo para o arquivo (`oid`). Além disso, armazena o `size` do arquivo final. +It tracks the `version` of {% data variables.large_files.product_name_short %} you're using, followed by a unique identifier for the file (`oid`). It also stores the `size` of the final file. {% note %} -**Observações**: -- {% data variables.large_files.product_name_short %} não pode ser usado com sites de {% data variables.product.prodname_pages %}. -- {% data variables.large_files.product_name_short %} não pode ser usado com repositórios de modelos. +**Notes**: +- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites. +- {% data variables.large_files.product_name_short %} cannot be used with template repositories. {% endnote %} -## Leitura adicional +## Further reading -- "[Colaboração com o {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" +- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" diff --git a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md index ed7f9b1189..f47cd8dbbf 100644 --- a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md +++ b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md @@ -12,6 +12,7 @@ versions: topics: - API shortTitle: Traverse with pagination +miniTocMaxHeadingLevel: 3 --- The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume. @@ -24,10 +25,13 @@ in the [platform-samples][platform samples] repository. {% data reusables.rest-api.dotcom-only-guide-note %} + + ## Basics of Pagination To start with, it's important to know a few facts about receiving paginated items: + 1. Different API calls respond with different defaults. For example, a call to [List public repositories](/rest/reference/repos#list-public-repositories) provides paginated items in sets of 30, whereas a call to the GitHub Search API @@ -37,55 +41,127 @@ provides items in sets of 100 [events](/rest/reference/activity#events) won't let you set a maximum for items to receive. Be sure to read the documentation on how to handle paginated results for specific endpoints. -Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988) -of an API call. For example, let's make a curl request to the search API, to find -out how many times Mozilla projects use the phrase `addClass`: +{% note %} + +**Note**: You should always rely on URLs included in the link header. Don't try to guess or construct your own URLs. + +{% endnote %} + + +### Link header + +The response header includes information about pagination. For more information about headers, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#about-the-response-code-and-headers)." To get the response header, include the `-I` flag in your request. For example: + +```shell +$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/advacado-corp/audit-log -```shell -$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla" ``` -The `-I` parameter indicates that we only care about the headers, not the actual -content. In examining the result, you'll notice some information in the Link header -that looks like this: +The `-I` flag returns only the response header. If the response is paginated, the response header will include a `link` header. The header will look something like this: - Link: ; rel="next", - ; rel="last" +``` +link: ; rel="next" +``` -Let's break that down. `rel="next"` says that the next page is `page=2`. This makes -sense, since by default, all paginated queries start at page `1.` `rel="last"` -provides some more information, stating that the last page of results is on page `34`. -Thus, we have 33 more pages of information about `addClass` that we can consume. -Nice! +or -**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL. +``` +link: ; rel="next", ; rel="last" +``` +### Types of pagination -### Navigating through the pages +{% data variables.product.company_short %}'s API uses two pagination methods: page-based pagination and cursor-based pagination. If the `link` header includes `page`, then the operation uses page-based pagination. If the `link` header includes `before` and `after`, then the operation uses cursor-based pagination. -Now that you know how many pages there are to receive, you can start navigating -through the pages to consume the results. You do this by passing in a `page` -parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14 -and see what happens: + +#### Page based pagination + +The link header for page-based pagination will tell you information about the previous, next, first, and last pages. If you did not request a specific page, then the response will default to the first page and information about the first and previous pages will be omitted. + +For example, for a request that did not specify a page, this header states that the next page is `2` and the last page is `511`. + +``` +link: ; rel="next", ; rel="last" +``` + +For example, for a request that specified page 5, this header states that the previous page is `4`, the next page is `6`, the last page is `511`, and the first page is `1`. + +``` +link: ; rel="prev", ; rel="next", ; rel="last", ; rel="first" +``` + +#### Cursor based pagination + +Cursor pagination uses terms `before` and `after` in order to navigate through pages. `rel="next"` and `rel="prev"` this mark the cursor point in the data set and provides a reference for traveling to the page `before` and `after` the current page. + +``` +link: ; rel="next", +; rel="first", +; rel="prev" +``` + +In this example, `rel=next` says that the next page is located at: + +``` +after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=> +``` + + + + +### Using pagination + +#### Cursor based pagination + +Using cursor based pagination requires you to use the terms `before` and `after`. To navigate using `before` and `after`, copy the link header generated above into your curl request: + +```shell +$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=> +``` + +The above example will generate a page of results and new header information that you can use to make the next request. `rel="next"` provides the next page of results. `rel="prev"` provides the previous page of results. The important part of the output here is the link header needs to be generated rather than manually imputed. Copy the entire link from the following output. + +``` +link: ; rel="next", +; rel="first", +; rel="prev" +``` + +Unlike page-based pagination, the results will not return the last page number in the response. + + link: ; rel="next", + ; rel="first", + ; rel="prev" + +Because cursor based pagination creates a reference point in the data set, it cannot calculate the total number of results. + + +#### Page based pagination + +To navigate using page based pagination pass in a `page` +parameter. By default, `page` always starts at `1`. In the following example, we have made a curl request to the search API Mozilla projects use the phrase `addClass`. Instead of starting at 1, lets jump to page 14. ```shell $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14" ``` -Here's the link header once more: +Here's an except of the link header in the HTTP request: Link: ; rel="next", ; rel="last", ; rel="first", ; rel="prev" -As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've +In this example, `rel="next"` is at 15, and `rel="last"` is 34. But now we've got some more information: `rel="first"` indicates the URL for the _first_ page, and more importantly, `rel="prev"` lets you know the page number of the previous page. Using this information, you could construct some UI that lets users jump between the first, previous, next, or last list of results in an API call. + ### Changing the number of items received +#### Page based pagination + By passing the `per_page` parameter, you can specify how many items you want each page to return, up to 100 items. Let's try asking for 50 items about `addClass`: @@ -102,6 +178,14 @@ As you might have guessed, the `rel="last"` information says that the last page is now 20. This is because we are asking for more information per page about our results. +#### Cursor based pagination + +You can also pass the `per_page` parameter for cursor-based pagination. + +```shell +$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>&per_page=50 +``` + ## Consuming the information You don't want to be making low-level curl calls just to be able to work with diff --git a/translations/pt-BR/data/reusables/actions/hardware-requirements-3.6.md b/translations/pt-BR/data/reusables/actions/hardware-requirements-3.6.md deleted file mode 100644 index e09355b4a4..0000000000 --- a/translations/pt-BR/data/reusables/actions/hardware-requirements-3.6.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -ms.openlocfilehash: 5c7cf10fca8efdcb186487e5de0e9a9d7e88d66b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147580716" ---- -| vCPUs | Memória | Máximo de clientes conectados | -| :---| :--- | :--- | -| 8 | 64 GB | 740 executores | -| 32 | 160 GB | 2700 executores | -| 96 | 384 GB | 7000 executores | -| 128 | 512 GB | 7000 executores | diff --git a/translations/pt-BR/data/reusables/codespaces/edit-devcontainer-json.md b/translations/pt-BR/data/reusables/codespaces/edit-devcontainer-json.md new file mode 100644 index 0000000000..b11e342032 --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/edit-devcontainer-json.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 38208812f73fda89c12d251955a1eee327ceb8db +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 10/27/2022 +ms.locfileid: "148113958" +--- +1. Os {% data variables.product.prodname_github_codespaces %} do repositório são configurados em um arquivo `devcontainer.json`. Se o repositório ainda não contiver um arquivo `devcontainer.json`, adicione-o agora. Confira "[Adicionar uma configuração de contêiner de desenvolvimento ao repositório](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)". \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md b/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md index db1256da20..9bda52c077 100644 --- a/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md +++ b/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md @@ -1,6 +1,6 @@ If your workflow is using a {% data variables.product.pat_generic %} to authenticate to a registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. -{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-pat)."{% endif %} +{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-personal-access-token)."{% endif %} For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)." diff --git a/translations/pt-BR/data/reusables/security-advisory/global-advisories.md b/translations/pt-BR/data/reusables/security-advisory/global-advisories.md new file mode 100644 index 0000000000..5b6013a224 --- /dev/null +++ b/translations/pt-BR/data/reusables/security-advisory/global-advisories.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: cb874d7a6fcaa0deeb828d91f9769df69050d337 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 10/27/2022 +ms.locfileid: "148113942" +--- +As consultorias de segurança do {% data variables.product.prodname_advisory_database %} em [github.com/advisories](https://github.com/advisories) são consideradas consultorias globais. Qualquer pessoa pode sugerir melhorias em qualquer consultoria de segurança global na {% data variables.product.prodname_advisory_database %}. Você pode editar ou adicionar qualquer detalhe, incluindo ecossistemas adicionalmente afetados, nível de gravidade ou descrição de quem é impactado. A equipe de curadoria da {% data variables.product.prodname_security %} irá revisar as melhorias apresentadas e publicá-las em {% data variables.product.prodname_advisory_database %}, se aceitas. \ No newline at end of file