Merge pull request #21707 from github/repo-sync

repo sync
2025-12-30 03:01:36 -05:00 · 2022-10-31 11:30:15 -07:00
parent d9c1c585f4 20a96e7072
commit 2e06aeb14e
15 changed files with 97 additions and 108 deletions
--- a/translations/log/msft-pt-resets.csv
+++ b/translations/log/msft-pt-resets.csv
@@ -579,6 +579,7 @@ translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscript
 translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags
 translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
 translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
+translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,broken liquid tags
 translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
 translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
 translations/pt-BR/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
@@ -1055,6 +1056,7 @@ translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md,rende
 translations/pt-BR/data/reusables/audit_log/audit-log-events-workflows.md,rendering error
 translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error
 translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
+translations/pt-BR/data/reusables/billing/license-statuses.md,broken liquid tags
 translations/pt-BR/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
 translations/pt-BR/data/reusables/classroom/about-autograding.md,broken liquid tags
 translations/pt-BR/data/reusables/code-scanning/alerts-found-in-generated-code.md,broken liquid tags
@@ -1108,6 +1110,7 @@ translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md,bro
 translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error
 translations/pt-BR/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
 translations/pt-BR/data/reusables/enterprise-accounts/security-tab.md,broken liquid tags
+translations/pt-BR/data/reusables/enterprise-accounts/vss-ghe-description.md,broken liquid tags
 translations/pt-BR/data/reusables/enterprise/apply-configuration.md,broken liquid tags
 translations/pt-BR/data/reusables/enterprise/rate_limit.md,broken liquid tags
 translations/pt-BR/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
--- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -69,7 +69,7 @@ There are two types of snapshots:
 | Azure | VM | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>
 | Hyper-V | VM | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>
 | Google Compute Engine | Disk | <https://cloud.google.com/compute/docs/disks/create-snapshots>
-| VMware | VM | <https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html>
+| VMware | VM | <https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-64B866EF-7636-401C-A8FF-2B4584D9CA72.html>

 ## Upgrading with a hotpatch

--- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md
+++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md
@@ -85,6 +85,8 @@ When you configure SAML authentication, {% data variables.product.product_name %

 1. Usernames created from email addresses are created from the normalized characters that precede the `@` character.

+1. Usernames created from domain accounts are created from the normalized characters after the `\\` separator. 
+
 1. If multiple accounts are normalized into the same {% data variables.product.product_name %} username, only the first user account is created. Subsequent users with the same username won't be able to sign in. {% ifversion ghec %}For more information, see "[Resolving username problems](#resolving-username-problems)."{% endif %}

 ### Examples of username normalization
@@ -97,6 +99,7 @@ When you configure SAML authentication, {% data variables.product.product_name %
 | The!!Octocat | `the--octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created, because it contains two consecutive dashes. |
 | The!Octocat | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created. Although the normalized username is valid, it already exists. |
 | `The.Octocat@example.com` | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created. Although the normalized username is valid, it already exists. |
+| `internal\\The.Octocat` | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created. Although the normalized username is valid, it already exists. |
 | `mona.lisa.the.octocat.from.github.united.states@example.com` | `mona-lisa-the-octocat-from-github-united-states{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created, because it exceeds the 39-character limit. |

 {% ifversion not ghec %}
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -100,7 +100,7 @@ In the list of pending members, for any individual account, you can cancel all i

 {% endnote %}

-If you use {% data variables.product.prodname_vss_ghe %}, the list of pending invitations includes all {% data variables.product.prodname_vs %} subscribers that haven't joined any of your organizations on {% data variables.product.prodname_dotcom %}, even if the subscriber does not have a pending invitation to join an organization. For more information about how to get {% data variables.product.prodname_vs %} subscribers access to {% data variables.product.prodname_enterprise %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)."
+If you use {% data variables.visual_studio.prodname_vss_ghe %}, the list of pending invitations includes all {% data variables.product.prodname_vs %} subscribers that haven't joined any of your organizations on {% data variables.product.prodname_dotcom %}, even if the subscriber does not have a pending invitation to join an organization. For more information about how to get {% data variables.product.prodname_vs %} subscribers access to {% data variables.product.prodname_enterprise %}, see "[Setting up {% data variables.visual_studio.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)."

 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
--- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
@@ -19,17 +19,17 @@ topics:
 shortTitle: About
 ---

-## About {% data variables.product.prodname_vss_ghe %}
+## About {% data variables.visual_studio.prodname_vss_ghe %}

-{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website.
+{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.visual_studio.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.visual_studio.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website.

 To use the {% data variables.product.prodname_enterprise %} portion of the license, each subscriber's personal account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. To accomplish this, organization owners can invite new members to an organization by email address. The subscriber can accept the invitation with an existing personal account on {% data variables.product.prodname_dotcom_the_website %} or create a new account.

-For more information about the setup of {% data variables.product.prodname_vss_ghe %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)."
+For more information about the setup of {% data variables.visual_studio.prodname_vss_ghe %}, see "[Setting up {% data variables.visual_studio.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)."

-## About licenses for {% data variables.product.prodname_vss_ghe %}
+## About licenses for {% data variables.visual_studio.prodname_vss_ghe %}

-After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise with a personal account on {% data variables.product.prodname_dotcom_the_website %}. If the verified email address for the personal account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}.
+After you assign a license for {% data variables.visual_studio.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise with a personal account on {% data variables.product.prodname_dotcom_the_website %}. If the verified email address for the personal account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.visual_studio.prodname_vss_ghe %}.

 The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the personal account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the personal account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber.

@@ -43,7 +43,7 @@ You can view the number of {% data variables.product.prodname_enterprise %} lice

 {% endtip %}

-You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}.
+You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.visual_studio.prodname_vss_admin_portal_with_url %}.

 ## Further reading

--- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
@@ -10,18 +10,18 @@ topics:
 shortTitle: Set up
 ---

-## About setup of {% data variables.product.prodname_vss_ghe %}
+## About setup of {% data variables.visual_studio.prodname_vss_ghe %}

-{% data reusables.enterprise-accounts.vss-ghe-description %} For more information, see "[About {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."
+{% data reusables.enterprise-accounts.vss-ghe-description %} For more information, see "[About {% data variables.visual_studio.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."

 This guide shows you how your team can get {% data variables.product.prodname_vs %} subscribers licensed and started with {% data variables.product.prodname_enterprise %}.

 If you prefer video, you can watch [Setting up your {% data variables.product.prodname_enterprise %} licenses with {% data variables.product.prodname_vs %} subscriptions](https://www.youtube.com/watch?v=P_zBgp_BE_I) on 
 Microsoft Visual Studio's YouTube channel.

-## Roles for {% data variables.product.prodname_vss_ghe %}
+## Roles for {% data variables.visual_studio.prodname_vss_ghe %}

-Before setting up {% data variables.product.prodname_vss_ghe %}, it's important to understand the roles for this combined offering.
+Before setting up {% data variables.visual_studio.prodname_vss_ghe %}, it's important to understand the roles for this combined offering.

 | Role | Service | Description | More information |
 | :- | :- | :- | :- |
@@ -38,15 +38,15 @@ Before setting up {% data variables.product.prodname_vss_ghe %}, it's important
 
 - Your team must have an enterprise on {% data variables.location.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."

-## Setting up {% data variables.product.prodname_vss_ghe %}
+## Setting up {% data variables.visual_studio.prodname_vss_ghe %}

-To set up {% data variables.product.prodname_vss_ghe %}, members of your team must complete the following tasks.
+To set up {% data variables.visual_studio.prodname_vss_ghe %}, members of your team must complete the following tasks.

-One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see "[Roles for {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)."
+One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see "[Roles for {% data variables.visual_studio.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)."

 1. An enterprise owner must create at least one organization in your enterprise on {% data variables.location.product_location %}. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."

-1. The subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs.
+1. The subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.visual_studio.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs.

 1. Optionally, if the subscription admin assigned licenses to subscribers in {% data variables.product.prodname_vs %} before adding {% data variables.product.prodname_enterprise %} to the subscription, the subscription admin can move the subscribers to the combined offering in the {% data variables.product.prodname_vs %} administration portal. For more information, see [Manage {% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) in Microsoft Docs.

@@ -64,7 +64,7 @@ One person may be able to complete the tasks because the person has all of the r

    {% endtip %}

-After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.location.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
+After {% data variables.visual_studio.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.location.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."

 ## Further reading

--- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Solução de problemas de uso de licenças para GitHub Enterprise
-intro: Você pode solucionar problemas de uso de licença para sua empresa auditando os relatórios de licença.
+title: Troubleshooting license usage for GitHub Enterprise
+intro: You can troubleshoot license usage for your enterprise by auditing license reports.
 permissions: 'Enterprise owners can review license usage for {% data variables.product.prodname_enterprise %}.'
 versions:
  ghec: '*'
@@ -10,30 +10,25 @@ topics:
  - Enterprise
  - Licensing
 shortTitle: Troubleshoot license usage
-ms.openlocfilehash: f23ca2380e71f5b037278c71da57dc8fab94c750
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147572654'
 ---
-## Sobre o uso inesperado de licenças

-Se o número de licenças consumidas da sua empresa for inesperado, você poderá revisar seu relatório de licenças consumidas para auditar seu uso de licenças em todas as suas implantações e assinaturas corporativas. Para obter mais informações, confira "[Como exibir o uso da licença para o GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" e "[Como exibir a assinatura e o uso da sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)".
+## About unexpected license usage

-Se você encontrar erros, tente as etapas de solução de problemas.
+If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. For more information, see "[Viewing license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" and "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."

-Por motivos de privacidade, os proprietários corporativos não podem acessar diretamente os detalhes das contas de usuário, a menos que você use {% data variables.product.prodname_emus %}.
+If you find errors, you can try troubleshooting steps.

-## Sobre o cálculo de licenças consumidas
+For privacy reasons, enterprise owners cannot directly access the details of user accounts unless you use {% data variables.product.prodname_emus %}.

-{% data variables.product.company_short %} fatura para cada pessoa que usa implementações do {% data variables.product.prodname_ghe_server %}, é membro de uma das suas organizações do {% data variables.product.prodname_ghe_cloud %} ou é um {% data variables.product.prodname_vs_subscriber %}. Para obter mais informações sobre as pessoas em sua empresa que consomem uma licença, confira "[Sobre preços por usuário](/billing/managing-billing-for-your-github-account/about-per-user-pricing)".
+## About the calculation of consumed licenses

-Para que cada usuário consuma apenas uma estação, independentemente de quantas implantações eles usam, você precisa sincronizar o uso de licenças entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, confira "[Sincronizando o uso de licenças entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".
+{% data variables.product.company_short %} bills for each person who uses deployments of {% data variables.product.prodname_ghe_server %}, is a member of one of your organizations on {% data variables.product.prodname_ghe_cloud %}, or is a {% data variables.visual_studio.prodname_vs_subscriber %}. For more information about the people in your enterprise who consume a license, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."

-Depois de sincronizar o uso das licenças, {% data variables.product.prodname_dotcom %} corresponde as contas de usuário em {% data variables.product.prodname_ghe_server %} às contas de usuário em {% data variables.product.prodname_ghe_cloud %} por endereço de email.
+For each user to consume a single seat regardless of how many deployments they use, you must synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."

-Primeiro, verificamos o endereço de email primário de cada usuário em {% data variables.product.prodname_ghe_server %}. Em seguida, tentamos corresponder esse endereço com o endereço de email de uma conta de usuário em {% data variables.product.prodname_ghe_cloud %}. Se sua empresa usa o SSO do SAML, primeiro verificamos os atributos de SAML a seguir em busca de endereços de email.
+After you synchronize license usage, {% data variables.product.prodname_dotcom %} matches user accounts on {% data variables.product.prodname_ghe_server %} with user accounts on {% data variables.product.prodname_ghe_cloud %} by email address.
+
+First, we first check the primary email address of each user on {% data variables.product.prodname_ghe_server %}. Then, we attempt to match that address with the email address for a user account on {% data variables.product.prodname_ghe_cloud %}. If your enterprise uses SAML SSO, we first check the following SAML attributes for email addresses.

 - `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`
 - `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`
@@ -41,64 +36,64 @@ Primeiro, verificamos o endereço de email primário de cada usuário em {% data
 - `NameID`
 - `emails`

-Se nenhum endereço de email encontrado nesses atributos corresponder ao endereço de email primário em {% data variables.product.prodname_ghe_server %} ou se sua empresa não usar o SSO do SAML, verificaremos cada um dos endereços de email verificados do usuário em {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações sobre a verificação de endereços de email do {% data variables.product.prodname_dotcom_the_website %}, confira "[Como verificar seu endereço de email](/enterprise-cloud@latest/get-started/signing-up-for-github/verifying-your-email-address){% ifversion not ghec %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
+If no email addresses found in these attributes match the primary email address on {% data variables.product.prodname_ghe_server %}, or if your enterprise doesn't use SAML SSO, we then check each of the user's verified email addresses on {% data variables.product.prodname_ghe_cloud %}. For more information about verification of email addresses on {% data variables.product.prodname_dotcom_the_website %}, see "[Verifying your email address](/enterprise-cloud@latest/get-started/signing-up-for-github/verifying-your-email-address){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}

-## Campos nos arquivos de licença consumidos
+## Fields in the consumed license files

-O relatório de uso da licença do {% data variables.product.prodname_dotcom_the_website %} e o arquivo de uso de licença exportado do {% data variables.product.prodname_ghe_server %} incluem uma variedade de campos para ajudar você a solucionar problemas de uso de licença para sua empresa. 
+The {% data variables.product.prodname_dotcom_the_website %} license usage report and {% data variables.product.prodname_ghe_server %} exported license usage file include a variety of fields to help you troubleshoot license usage for your enterprise. 

-### Relatório de uso de licença do {% data variables.product.prodname_dotcom_the_website %} (arquivo CSV)
+### {% data variables.product.prodname_dotcom_the_website %} license usage report (CSV file)

-O relatório de uso de licença para sua empresa é um arquivo CSV que contém as seguintes informações sobre os membros de sua empresa. Alguns campos são específicos para sua implantação do {% data variables.product.prodname_ghe_cloud %} (GHEC), ambientes conectados do {% data variables.product.prodname_ghe_server %} (GHES), ou suas assinaturas do {% data variables.product.prodname_vs %} (VSS) com o GitHub Enterprise.
+The license usage report for your enterprise is a CSV file that contains the following information about members of your enterprise. Some fields are specific to your {% data variables.product.prodname_ghe_cloud %} (GHEC) deployment, {% data variables.product.prodname_ghe_server %} (GHES) connected environments, or your {% data variables.product.prodname_vs %} subscriptions (VSS) with GitHub Enterprise.

-| Campo | DESCRIÇÃO
+| Field | Description
 | ----- | -----------
-| github_com_login | O nome de usuário da conta do GHEC do usuário
-| github_com_name | O nome de exibição da conta do GHEC do usuário
-| github_com_profile | A URL da página de perfil do usuário no GHEC
-| github_com_user   | Se o usuário tem ou não uma conta no GHEC |
-| github_com_member_roles | Para cada uma das organizações às quais o usuário pertence no GHEC, o nome da organização e a função da pessoa nessa organização (`Owner` ou `Member`) separados por dois pontos<br><br>Organizações delimitadas por vírgulas |
-| github_com_enterprise_role | Pode ser uma entre: `Owner`, `Member` ou `Outside collaborator`
-| github_com_verified_domain_emails | Todos os endereços de email associados à conta GHEC do usuário que correspondem aos domínios verificados da sua empresa |
-| github_com_saml_name_id | O nome de usuário do SAML |
-| github_com_orgs_with_pending_invites | Todos os convites pendentes para a conta do GHEC do usuário ingressar em organizações em sua empresa |
-| license_type | Pode ser `Visual Studio subscription` ou `Enterprise`
-| enterprise_server_user| Se o usuário tem ou não pelo menos uma conta no GHES |
-| enterprise_server_primary_emails | Os endereços de email primários associados a cada uma das contas do GHES do usuário |
-| enterprise_server_user_ids | Para cada uma das contas do GHES do usuário, a ID de usuário da conta
-| total_user_accounts | O número total de contas que a pessoa tem em GHEC e GHES
-| visual_studio_subscription_user | Se o usuário é ou não um {% data variables.product.prodname_vs_subscriber %} |
-| visual_studio_subscription_email | O endereço de email associado ao VSS do usuário |
-| visual_studio_license_status | Se a licença do Visual Studio foi correspondida a um usuário do {% data variables.product.company_short %} |
+| github_com_login | The username for the user's GHEC account
+| github_com_name | The display name for the user's GHEC account
+| github_com_profile | The URL for the user's profile page on GHEC
+| github_com_user	| Whether or not the user has an account on GHEC |
+| github_com_member_roles | For each of the organizations the user belongs to on GHEC, the organization name and the user's role in that organization (`Owner` or `Member`) separated by a colon<br><br>Organizations delimited by commas |
+| github_com_enterprise_role | Can be one of: `Owner`, `Member`, or `Outside collaborator`
+| github_com_verified_domain_emails | All email addresses associated with the user's GHEC account that match your enterprise's verified domains |
+| github_com_saml_name_id | The SAML username |
+| github_com_orgs_with_pending_invites | All pending invitations for the user's GHEC account to join organizations within your enterprise |
+| license_type | Can be one of: `Visual Studio subscription` or `Enterprise`
+| enterprise_server_user| Whether or not the user has at least one account on GHES |
+| enterprise_server_primary_emails | The primary email addresses associated with each of the user's GHES accounts |
+| enterprise_server_user_ids | For each of the user's GHES accounts, the account's user ID
+| total_user_accounts | The total number of accounts the person has across both GHEC and GHES
+| visual_studio_subscription_user | Whether or not the user is a {% data variables.visual_studio.prodname_vs_subscriber %} |
+| visual_studio_subscription_email | The email address associated with the user's VSS |
+| visual_studio_license_status | Whether the Visual Studio license has been matched to a {% data variables.product.company_short %} user |

-{% data variables.product.prodname_vs_subscriber %}s que ainda não são membros de pelo menos uma organização em sua empresa serão incluídos no relatório com um status de convite pendente e não terão valores para o campo "Nome" ou "Link do perfil".
+{% data variables.visual_studio.prodname_vs_subscriber %}s who are not yet members of at least one organization in your enterprise will be included in the report with a pending invitation status, and will be missing values for the "Name" or "Profile link" field.

-### Uso de licença exportada do {% data variables.product.prodname_ghe_server %} (arquivo JSON)
+### {% data variables.product.prodname_ghe_server %} exported license usage (JSON file)

-Seu uso de licença do {% data variables.product.prodname_ghe_server %} é um arquivo JSON que normalmente é usado ao realizar uma sincronização manual de licenças de usuário entre as implantações do {% data variables.product.prodname_ghe_server %} e do {% data variables.product.prodname_ghe_cloud %}. O arquivo contém as seguintes informações específicas para seu ambiente do {% data variables.product.prodname_ghe_server %}.
+Your {% data variables.product.prodname_ghe_server %} license usage is a JSON file that is typically used when performing a manual sync of user licenses between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} deployments. The file contains the following information specific to your {% data variables.product.prodname_ghe_server %} environment.

-| Campo | Descrição
+| Field | Description
 | ----- | -----------
-| Recursos | Os recursos do {% data variables.product.prodname_github_connect %} habilitados em sua instância do {% data variables.product.prodname_ghe_server %} e a data e hora da habilitação.
-| Nome do host | O nome do host de sua instância do {% data variables.product.prodname_ghe_server %}.
-| Somente HTTP | Se o Transport Layer Security (TLS) está ativado e configurado em sua instância do {% data variables.product.prodname_ghe_server %}. Pode ser: `True` ou `False`. 
-| Licença | Um hash de sua licença do {% data variables.product.prodname_ghe_server %}.
-| Chave pública | A parte da chave pública da sua licença do {% data variables.product.prodname_ghe_server %}.
-| ID de servidor | UUID gerado para sua instância do {% data variables.product.prodname_ghe_server %}.
-| Versão | A versão da sua instância do {% data variables.product.prodname_ghe_server %}.
+| Features | The {% data variables.product.prodname_github_connect %} features that are enabled on your {% data variables.product.prodname_ghe_server %} instance, and the date and time of enablement.
+| Host name | The hostname of your {% data variables.product.prodname_ghe_server %} instance.
+| HTTP only | Whether Transport Layer Security (TLS) is enabled and configured on your {% data variables.product.prodname_ghe_server %} instance. Can be one of: `True` or `False`. 
+| License | A hash of your {% data variables.product.prodname_ghe_server %} license.
+| Public key | The public key portion of your {% data variables.product.prodname_ghe_server %} license.
+| Server ID | UUID generated for your {% data variables.product.prodname_ghe_server %} instance.
+| Version | The version of your {% data variables.product.prodname_ghe_server %} instance.

-## Solução de problemas de licenças consumidas
+## Troubleshooting consumed licenses

-Para garantir que cada usuário esteja consumindo apenas uma estação para diferentes implantações e assinaturas, tente as etapas de solução de problemas a seguir.
+To ensure that the each user is only consuming a single seat for different deployments and subscriptions, try the following troubleshooting steps.

-1. Para ajudar a identificar usuários que estão consumindo várias estações, se sua empresa usar domínios verificados para {% data variables.product.prodname_ghe_cloud %}, examine a lista de membros corporativos que não têm um endereço de email de um domínio verificado associado à conta deles em {% data variables.product.prodname_dotcom_the_website %}. Muitas vezes, esses são os usuários que consomem erroneamente mais de uma estação licenciada. Para obter mais informações, confira "[Como exibir os membros que não têm um endereço de email de um domínio verificado](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)".
+1. To help identify users that are consuming multiple seats, if your enterprise uses verified domains for {% data variables.product.prodname_ghe_cloud %}, review the list of enterprise members who do not have an email address from a verified domain associated with their account on {% data variables.product.prodname_dotcom_the_website %}. Often, these are the users who erroneously consume more than one licensed seat. For more information, see "[Viewing members without an email address from a verified domain](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)."

   {% note %}

-  **Observação:** para facilitar a solução de problemas, recomendamos o uso de domínios verificados com sua conta corporativa no {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como verificar ou aprovar um domínio para sua empresa](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".
+  **Note:** To make troubleshooting easier, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."

  {% endnote %}
-1. Depois de identificar usuários que estão consumindo várias estações, verifique se o mesmo endereço de email está associado a todas as contas do usuário. Para obter mais informações sobre quais endereços de email precisam corresponder, confira "[Sobre o cálculo de licenças consumidas](#about-the-calculation-of-consumed-licenses)".
-1. Se um endereço de email foi atualizado ou verificado recentemente para corrigir uma incompatibilidade, exiba o carimbo de data/hora do último trabalho de sincronização de licenças. Se um trabalho não tiver sido executado desde que a correção foi feita, dispare manualmente um novo trabalho. Para obter mais informações, confira "[Como sincronizar o uso da licença entre o GitHub Enterprise Server e o GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
+1. After you identify users who are consuming multiple seats, make sure that the same email address is associated with all of the user's accounts. For more information about which email addresses must match, see "[About the calculation of consumed licenses](#about-the-calculation-of-consumed-licenses)."
+1. If an email address was recently updated or verified to correct a mismatch, view the timestamp of the last license sync job. If a job hasn't run since the correction was made, manually trigger a new 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)."

-Se você ainda tiver dúvidas sobre suas licenças consumidas após analisar as informações de solução de problemas acima, entre em contato com {% data variables.contact.github_support %} por meio do {% data variables.contact.contact_enterprise_portal %}.
+If you still have questions about your consumed licenses after reviewing the troubleshooting information above, you can contact {% data variables.contact.github_support %} through the {% data variables.contact.contact_enterprise_portal %}.
--- a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md
@@ -84,9 +84,9 @@ When you enable {% data variables.product.prodname_secret_scanning %} for a repo

 If {% data variables.product.prodname_secret_scanning %} detects a secret, {% data variables.product.prodname_dotcom %} generates an alert.

- {% data variables.product.prodname_dotcom %} sends an email alert to the repository administrators and organization owners.
+- {% data variables.product.prodname_dotcom %} sends an email alert to the repository administrators and organization owners. You'll receive an alert if you are watching the repository, or if you have enabled notifications for security alerts, or for all the activity on the repository.
 {% ifversion ghes or ghae or ghec %}
- {% data variables.product.prodname_dotcom %} sends an email alert to the contributor who committed the secret to the repository, with a link to the related {% data variables.product.prodname_secret_scanning %} alert. The commit author can then view the alert in the repository, and resolve the alert.
+- If the contributor who committed the secret isn't ignoring the repository, {% data variables.product.prodname_dotcom %} will also send an email alert to the contributor. The emails contains a link to the related {% data variables.product.prodname_secret_scanning %} alert. The commit author can then view the alert in the repository, and resolve the alert.
 {% endif %}
 - {% data variables.product.prodname_dotcom %} displays an alert in the "Security" tab of the repository.

--- a/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
@@ -1,6 +1,7 @@
 ---
 title: Managing alerts from secret scanning
 intro: You can view and close alerts for secrets checked in to your repository.
+permissions: 'People with admin access to a repository can view and dismiss alerts.'
 product: '{% data reusables.gated-features.secret-scanning %}'
 redirect_from:
  - /github/administering-a-repository/managing-alerts-from-secret-scanning
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -56,6 +56,12 @@ After you enable SAML SSO, there are multiple ways you can add new members to yo

 To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization.

+{% note %}
+
+**Note:** Provisioning new users via `https://github.com/orgs/ORGANIZATION/sso/sign_up` is only supported when SAML SSO is configured at the organization level, not when SAML SSO is configured at the enterprise account level. For more information about SAML SSO for enterprise accounts, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
+
+{% endnote %}
+
 If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)."

 {% data reusables.organizations.team-synchronization %}
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
@@ -12,12 +12,12 @@ versions:
  ghec: '*'
 topics:
  - Repositories
-ms.openlocfilehash: e56e8ca634ca1bfec3c587fe8fb606ab73ac72d4
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: d0067d96dce2f2cf9fe8bb2dd519668780d861ff
+ms.sourcegitcommit: bd8b3e152f17d90acf222a0d50ba9595184c1f5f
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145127080'
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111670'
 ---
 Quando você renomear um repositório, todas as informações existentes, com exceção das URLs do site do projeto, serão automaticamente redirecionadas para o novo nome, incluindo:

@@ -31,7 +31,7 @@ Para obter mais informações sobre sites de projeto, confira "[Sobre o {% data
 Além de redirecionar o tráfego da Web, todas as operações `git clone`, `git fetch` ou `git push` direcionadas ao local anterior continuarão funcionando como se fossem feitas no novo local. No entanto, para reduzir a confusão, recomendamos que a atualização de quaisquer clones locais existentes apontem para a nova URL do repositório. Faça isso usando `git remote` na linha de comando:

 ```shell
-$ git remote set-url origin <em>new_url</em>
+$ git remote set-url origin NEW_URL
 ```

 Para obter mais informações, confira "[Como gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
@@ -50,7 +50,7 @@ Se você planeja renomear um repositório que tenha um site do {% data variables

 {% warning %}

-**Aviso**: se você criar um repositório na sua conta no futuro, não reutilize o nome original do repositório renomeado. Se o fizer, o redirecionamento para o repositório renomeado quebrará.
+**Aviso**: se você criar um repositório na sua conta no futuro, não reutilize o nome original do repositório renomeado. Se você reutilizar, redirecionamentos para o repositório renomeado não funcionarão mais.

 {% endwarning %}

--- a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md
+++ b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md
@@ -33,7 +33,6 @@
 {%- ifversion ghes %}
 | `config_entry` |  Contains activities related to configuration settings. These events are only visible in the site admin audit log.
 {%- endif %}
-|
 | `dependabot_alerts`  | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
 | `dependabot_alerts_new_repos`   | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.
 | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access.
--- a/translations/pt-BR/data/reusables/billing/license-statuses.md
+++ b/translations/pt-BR/data/reusables/billing/license-statuses.md
@@ -1,13 +1,6 @@
---
-ms.openlocfilehash: 7604b9a565888d01aee7eac1643ddf4652a54ed9
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145094201"
---
-{% ifversion ghec %} Se sua licença inclui o {% data variables.product.prodname_vss_ghe %}, você poderá identificar se uma conta do usuário no {% data variables.product.prodname_dotcom_the_website %} correspondeu com êxito a um assinante do {% data variables.product.prodname_vs %} baixando o arquivo CSV que contém detalhes adicionais da licença. O status da licença será um dos status a seguir.
- "Correspondente": a conta de usuário no {% data variables.product.prodname_dotcom_the_website %} está vinculada a um assinante do {% data variables.product.prodname_vs %}.
- "Convite Pendente": um convite foi enviado para um assinante do {% data variables.product.prodname_vs %}, mas o assinante não aceitou o convite. 
- Em branco: não há nenhuma associação do {% data variables.product.prodname_vs %} a considerar para a conta de usuário no {% data variables.product.prodname_dotcom_the_website %}.
+{% ifversion ghec %}
+If your license includes {% data variables.visual_studio.prodname_vss_ghe %}, you can identify whether a user account on {% data variables.product.prodname_dotcom_the_website %} has successfully matched with a {% data variables.product.prodname_vs %} subscriber by downloading the CSV file that contains additional license details. The license status will be one of the following.
+- "Matched": The user account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber.
+- "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation. 
+- Blank: There is no {% data variables.product.prodname_vs %} association to consider for the user account on {% data variables.product.prodname_dotcom_the_website %}.
 {% endif %}
--- a/translations/pt-BR/data/reusables/enterprise-accounts/vss-ghe-description.md
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/vss-ghe-description.md
@@ -1,9 +1 @@
---
-ms.openlocfilehash: e8fcb120bbfd58d97607b749e78e3ed6aa94c7fb
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145096799"
---
-O {% data variables.product.prodname_vss_ghe %} é uma oferta combinada da Microsoft que permite que um assinante use o {% data variables.product.prodname_vs %} e o {% data variables.product.prodname_enterprise %}.
+{% data variables.visual_studio.prodname_vss_ghe %} is a combined offering from Microsoft that allows a subscriber to use both {% data variables.product.prodname_vs %} and {% data variables.product.prodname_enterprise %}.
--- a/translations/pt-BR/data/variables/product.yml
+++ b/translations/pt-BR/data/variables/product.yml
@@ -202,9 +202,6 @@ prodname_dependency_review_action: 'dependency review action'
 prodname_vs: 'Visual Studio'
 prodname_vscode_shortname: 'VS Code'
 prodname_vscode: 'Visual Studio Code'
-prodname_vs_subscriber: '{% data variables.product.prodname_vs %} subscriber'
-prodname_vss_ghe: 'Visual Studio subscriptions with GitHub Enterprise'
-prodname_vss_admin_portal_with_url: 'the [administrator portal for Visual Studio subscriptions](https://visualstudio.microsoft.com/subscriptions-administration/)'
 prodname_vscode_command_palette_shortname: 'VS Code Command Palette'
 prodname_vscode_command_palette: 'Visual Studio Code Command Palette'
 prodname_vscode_marketplace: 'Visual Studio Code Marketplace'