diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv index 8b06772f0073..1df66ee60a54 100644 --- a/translations/log/pt-resets.csv +++ b/translations/log/pt-resets.csv @@ -162,6 +162,7 @@ translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-s translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,rendering error translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,rendering error translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,rendering error +translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,rendering error translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,rendering error translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md,rendering error translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md,rendering error @@ -231,7 +232,15 @@ translations/pt-BR/content/admin/user-management/managing-users-in-your-enterpri translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,rendering error translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md,rendering error translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md,rendering error +translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,rendering error +translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error +translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error +translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md,rendering error +translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md,rendering error +translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md,rendering error translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error +translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md,rendering error +translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md,rendering error translations/pt-BR/content/authentication/index.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error @@ -246,18 +255,28 @@ translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/r translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error +translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error +translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md,rendering error translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error +translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md,rendering error +translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,rendering error translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error +translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,rendering error +translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md,rendering error +translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error translations/pt-BR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,Listed in localization-support#489 translations/pt-BR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error translations/pt-BR/content/authentication/troubleshooting-ssh/error-unknown-key-type.md,rendering error +translations/pt-BR/content/authentication/troubleshooting-ssh/index.md,rendering error +translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,rendering error translations/pt-BR/content/billing/index.md,rendering error translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error +translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,rendering error translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md,rendering error translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,rendering error @@ -307,6 +326,7 @@ translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-de translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,rendering error translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,rendering error translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,rendering error +translations/pt-BR/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md,rendering error translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md,rendering error translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,rendering error translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,rendering error @@ -346,6 +366,10 @@ translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps. translations/pt-BR/content/developers/apps/guides/index.md,rendering error translations/pt-BR/content/developers/apps/guides/using-content-attachments.md,rendering error translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error +translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error +translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,rendering error +translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error +translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error translations/pt-BR/content/developers/overview/managing-deploy-keys.md,rendering error translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md,rendering error translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md,rendering error @@ -424,6 +448,7 @@ translations/pt-BR/content/github/site-policy/github-terms-for-additional-produc translations/pt-BR/content/github/site-policy/github-terms-of-service.md,rendering error translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md,rendering error translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error +translations/pt-BR/content/github/writing-on-github/index.md,rendering error translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md,rendering error translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md,rendering error translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md,rendering error @@ -435,21 +460,41 @@ translations/pt-BR/content/issues/guides.md,rendering error translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md,rendering error translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md,rendering error +translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error +translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md,rendering error +translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md,rendering error +translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md,rendering error translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489 translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,parsing error +translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,rendering error +translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md,rendering error +translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,rendering error +translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,rendering error +translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md,rendering error translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,rendering error translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md,rendering error +translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md,rendering error translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md,rendering error +translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md,rendering error translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error @@ -480,24 +525,49 @@ translations/pt-BR/content/pull-requests/committing-changes-to-your-project/crea translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error +translations/pt-BR/content/repositories/archiving-a-github-repository/index.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error +translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error +translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md,rendering error +translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md,rendering error +translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md,rendering error translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md,rendering error +translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md,rendering error translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error +translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,rendering error +translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,parsing error +translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error +translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md,rendering error +translations/pt-BR/content/repositories/releasing-projects-on-github/index.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/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md,rendering error +translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md,rendering error +translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error +translations/pt-BR/content/repositories/working-with-files/index.md,rendering error +translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md,rendering error +translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,rendering error +translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error +translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md,rendering error +translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md,rendering error +translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md,rendering error +translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md,rendering error +translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md,rendering error +translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md,rendering error translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md,rendering error translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md,rendering error translations/pt-BR/content/rest/guides/traversing-with-pagination.md,rendering error diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 4b23257b33b2..4e9757aec376 100644 --- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -260,9 +260,9 @@ For more information, see "[`github context`](/actions/reference/context-and-exp #### `runs.steps[*].shell` {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} -**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell). Required if `run` is set. +**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set. {% else %} -**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell). Required if `run` is set. +**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set. {% endif %} #### `runs.steps[*].name` diff --git a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md index 61b4d9168686..6e69efdfbc11 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md @@ -30,7 +30,7 @@ topics: ## The components of {% data variables.product.prodname_actions %} -You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created. Your workflow contains one or more _jobs_ which can run in sequential order or in parallel. Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify in your workflow. +You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created. Your workflow contains one or more _jobs_ which can run in sequential order or in parallel. Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify your workflow. ![Workflow overview](/assets/images/help/images/overview-actions-simple.png) diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 2967c84c73d5..21fc4b65db22 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -1,9 +1,8 @@ --- -title: Configurar a autenticação e provisionamento para sua empresa usando o Azure AD -shortTitle: Configurar com Azure AD -intro: 'Você pode usar um inquilino no Azure Active Directory (Azure AD) como um provedor de identidade (IdP) para gerenciar centralizadamente autenticação e provisionamento de usuário para {% data variables.product.product_location %}.' +title: Configuring authentication and provisioning for your enterprise using Azure AD +shortTitle: Configuring with Azure AD +intro: 'You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.product_location %}.' permissions: 'Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.saml-sso %}' versions: ghae: '*' type: how_to @@ -16,42 +15,41 @@ topics: redirect_from: - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad --- +## About authentication and user provisioning with Azure AD -## Sobre autenticação e provisionamento de usuário com Azure AD +Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs. -O Azure Active Directory (Azure AD) é um serviço da Microsoft que permite gerenciar centralmente as contas de usuários e acessar aplicativos da web. Para obter mais informações, consulte [O que é Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) na documentação da Microsoft. +To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access membership with SCIM, which allows you to create {% data variables.product.prodname_ghe_managed %} users and manage team and organization membership from your Azure AD tenant. -Para gerenciar identidade e acesso para {% data variables.product.product_name %}, você pode usar um inquilino no Azure AD como um IdP de SAML para autenticação. Você também pode configurar o Azure AD para fornecer contas automaticamente e acessar a associação com o SCIM, que permite criar usuários de {% data variables.product.prodname_ghe_managed %} e gerenciar os membros da equipe e da organização do seu inquilino do Azure AD. +After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_managed %} using Azure AD, you can accomplish the following from your Azure AD tenant. -Após habilitar o SAML SSO e SCIM durante {% data variables.product.prodname_ghe_managed %} usando Azure AD, você pode realizar o seguinte no seu inquilino do Azure AD. +* Assign the {% data variables.product.prodname_ghe_managed %} application on Azure AD to a user account to automatically create and grant access to a corresponding user account on {% data variables.product.product_name %}. +* Unassign the {% data variables.product.prodname_ghe_managed %} application to a user account on Azure AD to deactivate the corresponding user account on {% data variables.product.product_name %}. +* Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization. +* Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}. -* Atribua o aplicativo de {% data variables.product.prodname_ghe_managed %} no Azure AD a uma conta de usuário para criar e conceder acesso automaticamente a uma conta de usuário correspondente em {% data variables.product.product_name %}. -* Desatribua o aplicativo de {% data variables.product.prodname_ghe_managed %} para uma conta de usuário no Azure AD para desabilitar a conta de usuário correspondente em {% data variables.product.product_name %}. -* Atribua o aplicativo {% data variables.product.prodname_ghe_managed %} a um grupo IdP no Azure AD para criar automaticamente e conceder acesso a contas de usuário em {% data variables.product.product_name %} para todos os integrantes do grupo IdP. Além disso, o grupo IdP está disponível em {% data variables.product.prodname_ghe_managed %} para conexão com uma equipe e sua organização principal. -* Desatribua o aplicativo de {% data variables.product.prodname_ghe_managed %} de um grupo de IdP para desativar as contas de usuário de {% data variables.product.product_name %} de todos os usuários de IdP que tiveram acesso somente através desse grupo de IdP e remova os usuários da organização principal. O grupo IdP será desconectado de qualquer equipe em {% data variables.product.product_name %}. +For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." -Para obter mais informações sobre gerenciamento de identidade e acesso para a sua empresa em {% data variables.product.product_location %}, consulte "[Gerenciar identidade e acesso da sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". Para obter mais informações sobre como sincronizar equipes com grupos de IdP, consulte "[Sincronizar uma equipe com um grupo de provedores de identidade](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". +## Prerequisites -## Pré-requisitos +To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs. -Para configurar o provisionamento de autenticação e usuário para {% data variables.product.product_name %} usando o Azure AD, você deve ter uma conta do Azure AD e um inquilino. Para obter mais informações, consulte o [site do Azure AD](https://azure.microsoft.com/free/active-directory) e o [Início rápido: Crie um inquilino do Azure Active Directory](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) na documentação da Microsoft. - -{% data reusables.saml.assert-the-administrator-attribute %} Para mais informações sobre a inclusão do atributo do `administrador` na solicitação do SAML do Azure AD, consulte [Como personalizar solicitações emitidas no token SAML para aplicativos corporativos](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) na documentação da Microsoft. +{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs. {% data reusables.saml.create-a-machine-user %} -## Configurar autenticação e provisionamento de usuário com Azure AD +## Configuring authentication and user provisioning with Azure AD {% ifversion ghae %} -1. No Azure AD, adicione {% data variables.product.ae_azure_ad_app_link %} ao seu inquilino e configure logon único. Para obter mais informações, consulte o [Tutorial: integração do logon único (SSO) do Azure Active Directory com {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) na documentação da Microsoft. +1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. -1. Em {% data variables.product.prodname_ghe_managed %}, insira os detalhes para o seu inquilino do Azure AD. +1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} - - Se você já configurou SSO de SAML para {% data variables.product.product_location %} usando outro IdP e você deseja usar o Azure AD, você pode editar a sua configuração. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)". + - If you've already configured SAML SSO for {% data variables.product.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)." -1. Habilitar provisionamento do usuário em {% data variables.product.product_name %} e configurar provisionamento do usuário no Azure AD. Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)". +1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md index 6d26e290e4d6..fbe74e7c9499 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md +++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md @@ -3,9 +3,8 @@ title: Configuring authentication and provisioning for your enterprise using Okt shortTitle: Configuring with Okta intro: 'You can use Okta as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.prodname_ghe_managed %}.' permissions: 'Enterprise owners can configure authentication and provisioning for {% data variables.product.prodname_ghe_managed %}.' -product: '{% data reusables.gated-features.saml-sso %}' versions: - github-ae: '*' + ghae: '*' type: how_to topics: - Accounts diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md index 8dafb03fa5f0..bf03a67c9166 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md +++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md @@ -2,9 +2,8 @@ title: Mapping Okta groups to teams intro: 'You can map your Okta groups to teams on {% data variables.product.prodname_ghe_managed %} to automatically add and remove team members.' permissions: 'Enterprise owners can configure authentication and provisioning for {% data variables.product.prodname_ghe_managed %}.' -product: '{% data reusables.gated-features.saml-sso %}' versions: - github-ae: '*' + ghae: '*' type: how_to topics: - Accounts diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md index 0d5ef218e805..3da45be1af3e 100644 --- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md @@ -2,7 +2,6 @@ title: About identity and access management for your enterprise shortTitle: About identity and access management intro: 'You can use SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% ifversion ghae %}to {% data variables.product.product_location %}{% endif %}.' -product: '{% data reusables.gated-features.saml-sso %}' versions: ghec: '*' ghae: '*' diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md index 3a5178de5673..e3b193572bbc 100644 --- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md @@ -2,7 +2,6 @@ title: Configuring SAML single sign-on for your enterprise shortTitle: Configure SAML SSO intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).' -product: '{% data reusables.gated-features.saml-sso %}' permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.' versions: ghec: '*' diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md index a1c6d63a4cc6..2f2984bc97d3 100644 --- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md @@ -3,7 +3,6 @@ title: Configuring user provisioning for your enterprise shortTitle: Configuring user provisioning intro: 'You can configure System for Cross-domain Identity Management (SCIM) for your enterprise, which automatically provisions user accounts on {% data variables.product.product_location %} when you assign the application for {% data variables.product.product_location %} to a user on your identity provider (IdP).' permissions: 'Enterprise owners can configure user provisioning for an enterprise on {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.saml-sso %}' versions: ghae: '*' type: how_to 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 9af860441777..5f067794ac52 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 @@ -61,38 +61,23 @@ The peak quantity of concurrent jobs running without performance loss depends on {%- ifversion ghes < 3.2 %} -| vCPUs | Memory | Maximum job throughput | -| :--- | :--- | :--- | -| 4 | 32 GB | Demo or light testing | -| 8 | 64 GB | 25 jobs | -| 16 | 160 GB | 35 jobs | -| 32 | 256 GB | 100 jobs | +{% data reusables.actions.hardware-requirements-before %} {%- endif %} {%- ifversion ghes = 3.2 %} -| vCPUs | Memory | Maximum Concurrency*| -| :--- | :--- | :--- | -| 32 | 128 GB | 1000 jobs | -| 64 | 256 GB | 1300 jobs | -| 96 | 384 GB | 2200 jobs | +{% data reusables.actions.hardware-requirements-3.2 %} -*Maximum concurrency was measured 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. +Maximum concurrency was measured 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. {%- endif %} {%- ifversion ghes > 3.2 %} -| vCPUs | Memory | Maximum Concurrency*| -| :--- | :--- | :--- | -| 8 | 64 GB | 300 jobs | -| 16 | 160 GB | 700 jobs | -| 32 | 128 GB | 1300 jobs | -| 64 | 256 GB | 2000 jobs | -| 96 | 384 GB | 4000 jobs | +{% data reusables.actions.hardware-requirements-after %} -*Maximum concurrency was measured 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. +Maximum concurrency was measured 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. {%- endif %} diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 165dcf3649ab..94f907907560 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,62 +1,59 @@ --- -title: Sobre a autenticação com SAML SSO -intro: 'Você pode acessar {% ifversion ghae %}{% data variables.product.product_location %}{% elsif fpt %}uma organização que usa o logon único SAML (SSO){% endif %} efetuando a autenticação {% ifversion ghae %}com o logon único SAML (SSO) {% endif %}por meio de um provedor de identidade (IdP).{% ifversion fpt or ghec %} Depois de efetuar a autenticação com o IdP com sucesso a partir de {% data variables.product.product_name %}, você deverá autorizar qualquer token de acesso pessoal, chave SSH ou {% data variables.product.prodname_oauth_app %} que você gostaria de acessar os recursos da organização.{% endif %}' -product: '{% data reusables.gated-features.saml-sso %}' +title: About authentication with SAML single sign-on +intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% ifversion ghec %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on versions: - fpt: '*' ghae: '*' ghec: '*' topics: - SSO -shortTitle: logon único SAML +shortTitle: SAML single sign-on --- - -## Sobre autenticação com SSO do SAML +## About authentication with SAML SSO {% ifversion ghae %} -O SAML SSO permite que um proprietário corporativo realize o controle central e proteja o acesso para {% data variables.product.product_name %} a partir de um IdP do SAML. Ao acessar {% data variables.product.product_location %} em um navegador, {% data variables.product.product_name %} irá redirecioná-lo para seu IdP para efetuar a autenticação. Depois de concluir a autenticação com sucesso com uma conta no IdP, este irá redirecionar você de volta para {% data variables.product.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IpD e, em seguida, concede acesso. +SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. {% data reusables.saml.you-must-periodically-authenticate %} -Se você não puder acessar {% data variables.product.product_name %}, entre em contato com o proprietário da empresa local ou administrador para {% data variables.product.product_name %}. Você pode conseguir localizar informações de contato para sua empresa clicando em **Suporte** na parte inferior de qualquer página em {% data variables.product.product_name %}. {% data variables.product.company_short %} e {% data variables.contact.github_support %} não têm acesso ao seu IdP e não podem solucionar problemas de autenticação. +If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. {% endif %} {% ifversion fpt or ghec %} -{% data reusables.saml.dotcom-saml-explanation %} Os proprietários da organização podem convidar sua conta de usuário em {% data variables.product.prodname_dotcom %} para participar da organização que usa o SSO SAML, o que permite que você contribua com a organização e mantenha sua identidade e contribuições existentes em {% data variables.product.prodname_dotcom %}. +{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your user account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. -Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você usará uma nova conta que lhe será fornecida. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} -Ao acessar os recursos dentro de uma organização que usa o SSO SAML, o {% data variables.product.prodname_dotcom %} irá redirecionar você para o SAML IdP da organização para que você efetue a autenticação. Depois de efetuar a autenticação com sucesso com sua conta no IdP, este irá redirecionar você de volta para {% data variables.product.prodname_dotcom %}, onde você poderá acessar os recursos da organização. +When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. {% data reusables.saml.outside-collaborators-exemption %} -Se você efetuou a autenticação recentemente com o IdP SAML da sua organização no navegador, você estará automaticamente autorizado ao acessar uma organização do {% data variables.product.prodname_dotcom %} que usa SAML SSO. Se não tiver efetuado a autenticação recentemente com o IdP SAML da sua organização no navegador, você deverá efetuar a autenticação no SAML IdP antes de acessar a organização. +If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. {% data reusables.saml.you-must-periodically-authenticate %} -Para usar a API ou o Git na linha de comando de modo a acessar conteúdo protegido em uma organização que usa SAML SSO, você precisará usar um token de acesso pessoal autorizado por HTTPS ou uma chave SSH autorizada. +To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. -Na falta de um token de acesso pessoal ou uma chave SSH, você poderá criar um token de acesso pessoal para a linha de comando ou gerar uma nova chave SSH. Para obter mais informações consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)ou "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent-](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". +If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -Para usar um token novo ou existente de acesso pessoal ou chave SSH com uma organização que usa ou impõe o SSO do SAML, você precisará autorizar o token ou autorizar a chave SSH para uso com uma organização de SSO do SAML. Para obter mais informações consulte "[Autorizar um token de acesso pessoal para usar com logon único SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Autorizando uma chave SSH para uso com o logon único SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on). +To use a new or existing personal access token or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -## Sobre {% data variables.product.prodname_oauth_apps %} e SSO do SAML +## About {% data variables.product.prodname_oauth_apps %} and SAML SSO -Você deve ter uma sessão do SAML ativa toda vez que autorizar um {% data variables.product.prodname_oauth_app %} para acessar uma organização que usa ou aplica o SSO do SAML. +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} to access an organization that uses or enforces SAML SSO. -Após o proprietário de uma empresa ou organização habilitar ou aplicar o SSO do SAML para uma organização, você deverá autorizar novamente qualquer {% data variables.product.prodname_oauth_app %} que você autorizou anteriormente a acessar a organização. Para visualizar {% data variables.product.prodname_oauth_apps %} que você autorizou ou ou autorizar novamente um {% data variables.product.prodname_oauth_app %}, acesse a sua página de [{% data variables.product.prodname_oauth_apps %}](https://github.com/settings/applications). +After an enterprise or organization owner enables or enforces SAML SSO for an organization, you must reauthorize any {% data variables.product.prodname_oauth_app %} that you previously authorized to access the organization. To see the {% data variables.product.prodname_oauth_apps %} you've authorized or reauthorize an {% data variables.product.prodname_oauth_app %}, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). {% endif %} -## Leia mais +## Further reading -{% ifversion fpt or ghec %}- "[Sobre identidade e gerenciamento de acesso com logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} -{% ifversion ghae %}- "[Sobre identidade e gerenciamento de acesso para a sua empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} +{% ifversion ghec %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% ifversion ghae %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md index 465810bdd9a2..cd89fcbb59b4 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md @@ -1,31 +1,31 @@ --- -title: Autorizar o uso de um token de acesso pessoal para uso com logon único SAML -intro: 'Para usar um token de acesso pessoal com uma organização que utiliza logon único SAML (SSO), primeiramente, você deve autorizar o token.' +title: Authorizing a personal access token for use with SAML single sign-on +intro: 'To use a personal access token with an organization that uses SAML single sign-on (SSO), you must first authorize the token.' redirect_from: - - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization/ + - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on - /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on versions: - fpt: '*' ghec: '*' topics: - SSO -shortTitle: PAT com SAML +shortTitle: PAT with SAML --- - -Você pode autorizar um token de acesso pessoal existente ou [criar um](/github/authenticating-to-github/creating-a-personal-access-token) e autorizá-lo. +You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it. {% data reusables.saml.authorized-creds-info %} {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -3. Ao lado do token que deseja autorizar, clique em **Enable SSO** (Habilitar SSO) ou **Disable SSO** (Desabilitar SSO). ![Botão de autorização do token SSO](/assets/images/help/settings/sso-allowlist-button.png) -4. Encontre a organização para a qual deseja autorizar o token de acesso. -4. Clique em **Autorizar**. ![Botão de autorização do token](/assets/images/help/settings/token-authorize-button.png) +3. Next to the token you'd like to authorize, click **Enable SSO** or **Disable SSO**. + ![SSO token authorize button](/assets/images/help/settings/sso-allowlist-button.png) +4. Find the organization you'd like to authorize the access token for. +4. Click **Authorize**. + ![Token authorize button](/assets/images/help/settings/token-authorize-button.png) -## Leia mais +## Further reading -- "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" -- "[Sobre a autenticação com logon único SAML](/articles/about-authentication-with-saml-single-sign-on)" +- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" +- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md index 4f0064e8da9d..2bd5cef6ba25 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md @@ -1,36 +1,36 @@ --- -title: Autorizar o uso de uma chave SSH para uso com logon único SAML -intro: 'Para usar uma chave SSH com uma organização que usa logon único SAML (SSO), primeiramente, você deve autorizar a chave.' +title: Authorizing an SSH key for use with SAML single sign-on +intro: 'To use an SSH key with an organization that uses SAML single sign-on (SSO), you must first authorize the key.' redirect_from: - - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization/ + - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on - /github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on versions: - fpt: '*' ghec: '*' topics: - SSO -shortTitle: Chave SSH com SAML +shortTitle: SSH Key with SAML --- - -Você pode autorizar uma chave SSH existente ou criar uma e autorizá-la. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." +You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." {% data reusables.saml.authorized-creds-info %} {% note %} -**Observação:** se a autorização da sua chave SSH foi revogada por uma organização, você não poderá reautorizar a mesma chave. Será preciso criar outra chave SSH e autorizá-la. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." +**Note:** If your SSH key authorization is revoked by an organization, you will not be able to reauthorize the same key. You will need to create a new SSH key and authorize it. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." {% endnote %} {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -3. Ao lado da chave SSH que deseja autorizar, clique em **Enable SSO** (Habilitar SSO) ou **Disable SSO** (Desabilitar SSO). ![Botão de autorização do token SSO](/assets/images/help/settings/ssh-sso-button.png) -4. Encontre a organização para a qual deseja autorizar a chave SSH. -5. Clique em **Autorizar**. ![Botão de autorização do token](/assets/images/help/settings/ssh-sso-authorize.png) +3. Next to the SSH key you'd like to authorize, click **Enable SSO** or **Disable SSO**. +![SSO token authorize button](/assets/images/help/settings/ssh-sso-button.png) +4. Find the organization you'd like to authorize the SSH key for. +5. Click **Authorize**. +![Token authorize button](/assets/images/help/settings/ssh-sso-authorize.png) -## Leia mais +## Further reading -- "[Verificar se há chaves SSH existentes](/articles/checking-for-existing-ssh-keys)" -- "[Sobre a autenticação com logon único SAML](/articles/about-authentication-with-saml-single-sign-on)" +- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)" +- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md index b8ecca2e5530..c609a547c96b 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md @@ -1,13 +1,11 @@ --- -title: Sobre a autenticação com logon único SAML -intro: 'Você pode efetuar a autenticação em {% ifversion fpt %}a organização {% data variables.product.product_name %} {% elsif ghae %}{% data variables.product.product_location %} {% endif %}com o logon único SAML (SSO){% ifversion fpt %} e visualizar as suas sessões ativas{% endif %}.' -product: '{% data reusables.gated-features.saml-sso %}' +title: Authenticating with SAML single sign-on +intro: 'You can authenticate to {% data variables.product.product_name %} with SAML single sign-on (SSO){% ifversion ghec %} and view your active sessions{% endif %}.' redirect_from: - - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on/ + - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on - /articles/authenticating-with-saml-single-sign-on - - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/ + - /github/authenticating-to-github/authenticating-with-saml-single-sign-on versions: - fpt: '*' ghae: '*' ghec: '*' topics: @@ -17,6 +15,6 @@ children: - /authorizing-an-ssh-key-for-use-with-saml-single-sign-on - /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on - /viewing-and-managing-your-active-saml-sessions -shortTitle: Efetuar a autenticação com SAML +shortTitle: Authenticate with SAML --- diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md index ee9d94de74db..466649aa42bd 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md @@ -1,30 +1,31 @@ --- -title: Exibir e gerenciar sessões SAML ativas -intro: É possível exibir e revogar sessões SAML ativas nas configurações de segurança. +title: Viewing and managing your active SAML sessions +intro: You can view and revoke your active SAML sessions in your security settings. redirect_from: - /articles/viewing-and-managing-your-active-saml-sessions - /github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions versions: - fpt: '*' ghec: '*' topics: - SSO -shortTitle: Sessões de SAML ativas +shortTitle: Active SAML sessions --- - {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security %} -3. Em "Sessões", você pode ver suas sessões ativas do SAML. ![Lista de sessões SAML ativas](/assets/images/help/settings/saml-active-sessions.png) -4. Para ver as informações da sessão, clique em **Ver mais**. ![Botão para abrir as informações da sessão do SAML](/assets/images/help/settings/saml-expand-session-details.png) -5. Para revogar uma sessão, clique em **Revogar SAML**. ![Botão para revogar uma sessão SAML](/assets/images/help/settings/saml-revoke-session.png) +3. Under "Sessions," you can see your active SAML sessions. + ![List of active SAML sessions](/assets/images/help/settings/saml-active-sessions.png) +4. To see the session details, click **See more**. + ![Button to open SAML session details](/assets/images/help/settings/saml-expand-session-details.png) +5. To revoke a session, click **Revoke SAML**. + ![Button to revoke a SAML session](/assets/images/help/settings/saml-revoke-session.png) {% note %} - **Observação:** quando você revoga uma sessão, remove a autenticação SAML para essa organização. Para acessar a organização novamente, você precisa fazer logon único por meio do provedor de identidade. Para obter mais informações, consulte "[Sobre a autenticação com SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". + **Note:** When you revoke a session, you remove your SAML authentication to that organization. To access the organization again, you will need to single sign-on through your identity provider. For more information, see "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." {% endnote %} -## Leia mais +## Further reading -- "[Sobre a autenticação com SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" +- "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 0b2fd99c74f7..a649ffb62839 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -1,6 +1,6 @@ --- -title: Sobre o SSH -intro: 'Usando o protocolo SSH, você pode se conectar a servidores e serviços remotos e se autenticar neles. Com chaves SSH, você pode conectar-se a {% data variables.product.product_name %} sem inserir seu nome de usuário e token de acesso pessoal em cada visita.' +title: About SSH +intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.' redirect_from: - /articles/about-ssh - /github/authenticating-to-github/about-ssh @@ -13,23 +13,22 @@ versions: topics: - SSH --- +When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." -Ao configurar o SSH, você precisará gerar uma nova chave SSH e adicioná-la ao agente ssh. Você deve adicionar a chave SSH à sua conta {% data variables.product.product_name %} antes de usar a chave para efetuar a autenticação. Para mais informações consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" e "[Adicionar uma nova chave SSH à sua conta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)". +You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)." -Você pode proteger ainda mais sua chave SSH usando uma chave de segurança de hardware, o que exige que a chave de segurança física do hardware seja conectada ao seu computador quando o par de chaves é usado para efetuar a autenticação com SSH. Você também pode proteger sua chave SSH, adicionando sua chave ao agente do ssh-agent e usando uma frase secreta. Para obter mais informações, consulte "[Trabalhar com frases secretas da chave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)". +{% ifversion fpt or ghec %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} -{% ifversion fpt or ghec %}Para usar a chave SSH com um repositório pertencente a uma organização que usa o logon único SAML, você deverá autorizar a chave. Para obter mais informações, consulte "[Autorizar uma chave SSH para uso com logon único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %} - -Para manter a segurança da conta, você pode revisar regularmente sua lista de chaves SSH e revogar quaisquer chaves que sejam inválidas ou que tenham sido comprometidas. Para obter mais informações, consulte "[Revisar as chaves SSH](/github/authenticating-to-github/reviewing-your-ssh-keys)". +To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. For more information, see "[Reviewing your SSH keys](/github/authenticating-to-github/reviewing-your-ssh-keys)." {% ifversion fpt or ghec %} -Se você ficou sem usar a chave SSH por um ano, o {% data variables.product.prodname_dotcom %} excluirá automaticamente essa chave SSH inativa como uma medida de segurança. Para obter mais informações, consulte "[Chaves SSH excluídas ou ausentes](/articles/deleted-or-missing-ssh-keys)". +If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)." {% endif %} -Se você for integrante de uma organização que fornece certificados SSH, você poderá usar seu certificado para acessar os repositórios da organização sem adicionar o certificado à sua conta em {% data variables.product.product_name %}. Você não pode usar seu certificado para acessar bifurcações dos repositórios da organização pertencentes à sua conta de usuário. Para obter mais informações, consulte "[Sobre autoridades certificadas SSH](/articles/about-ssh-certificate-authorities)". +If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)." -## Leia mais +## Further reading -- "[Verificar se há chaves SSH existentes](/articles/checking-for-existing-ssh-keys)" -- "[Testar a conexão SSH](/articles/testing-your-ssh-connection)" -- "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)" +- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)" +- "[Testing your SSH connection](/articles/testing-your-ssh-connection)" +- "[Troubleshooting SSH](/articles/troubleshooting-ssh)" diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 17b3890a4525..98e191c19ba9 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -2,8 +2,8 @@ title: Generating a new SSH key and adding it to the ssh-agent intro: 'After you''ve checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.' redirect_from: - - /articles/adding-a-new-ssh-key-to-the-ssh-agent/ - - /articles/generating-a-new-ssh-key/ + - /articles/adding-a-new-ssh-key-to-the-ssh-agent + - /articles/generating-a-new-ssh-key - /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent - /github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent - /github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent @@ -252,6 +252,6 @@ If you are using macOS or Linux, you may need to update your SSH client or insta - "[About SSH](/articles/about-ssh)" - "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)" -{%- ifversion fpt %} -- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" +{%- ifversion fpt or ghec %} +- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %} {%- endif %} diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md index 95389c5e9937..f052a1f3f46f 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md @@ -1,16 +1,16 @@ --- -title: Conectar-se ao GitHub com SSH -intro: 'Você pode conectar-se a {% data variables.product.product_name %} usando o protocolo Secure Shell (SSH), que fornece um canal seguro por meio de uma rede insegura.' +title: Connecting to GitHub with SSH +intro: 'You can connect to {% data variables.product.product_name %} using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.' redirect_from: - - /key-setup-redirect/ - - /linux-key-setup/ - - /mac-key-setup/ - - /msysgit-key-setup/ - - /articles/ssh-key-setup/ - - /articles/generating-ssh-keys/ - - /articles/generating-an-ssh-key/ + - /key-setup-redirect + - /linux-key-setup + - /mac-key-setup + - /msysgit-key-setup + - /articles/ssh-key-setup + - /articles/generating-ssh-keys + - /articles/generating-an-ssh-key - /articles/connecting-to-github-with-ssh - - /github/authenticating-to-github/connecting-to-github-with-ssh/ + - /github/authenticating-to-github/connecting-to-github-with-ssh versions: fpt: '*' ghes: '*' @@ -25,6 +25,6 @@ children: - /adding-a-new-ssh-key-to-your-github-account - /testing-your-ssh-connection - /working-with-ssh-key-passphrases -shortTitle: Conectar com SSH +shortTitle: Connect with SSH --- diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md index 1b86ad5d409a..f9dfd3f00c52 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md @@ -1,9 +1,9 @@ --- -title: Trabalhar com frase secreta da chave SSH -intro: Você pode proteger suas chaves SSH e configurar um agente de autenticação para que não precise redigitar a senha toda vez que usar as chaves SSH. +title: Working with SSH key passphrases +intro: You can secure your SSH keys and configure an authentication agent so that you won't have to reenter your passphrase every time you use your SSH keys. redirect_from: - - /ssh-key-passphrases/ - - /working-with-key-passphrases/ + - /ssh-key-passphrases + - /working-with-key-passphrases - /articles/working-with-ssh-key-passphrases - /github/authenticating-to-github/working-with-ssh-key-passphrases - /github/authenticating-to-github/connecting-to-github-with-ssh/working-with-ssh-key-passphrases @@ -14,14 +14,13 @@ versions: ghec: '*' topics: - SSH -shortTitle: Frases secretas da chave SSH +shortTitle: SSH key passphrases --- +With SSH keys, if someone gains access to your computer, they also gain access to every system that uses that key. To add an extra layer of security, you can add a passphrase to your SSH key. You can use `ssh-agent` to securely save your passphrase so you don't have to reenter it. -Com as chaves SSH, se alguém conseguir acessar seu computador, terá acesso a todos os sistemas que usam essas chaves. Para incluir uma camada extra de segurança, adicione uma frase secreta à sua chave SSH. Você pode usar `ssh-agent` para salvar sua frase secreta de forma segura e não precisar digitá-la novamente. +## Adding or changing a passphrase -## Adicionar ou alterar frase secreta - -É possível alterar a frase secreta de uma chave privada sem gerar novamente o par de chaves. Basta digitar o seguinte comando: +You can change the passphrase for an existing private key without regenerating the keypair by typing the following command: ```shell $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} @@ -32,13 +31,13 @@ $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} > Your identification has been saved with the new passphrase. ``` -Caso a sua chave já tenha uma frase secreta, você precisará digitá-la antes de poder alterar para uma nova frase secreta. +If your key already has a passphrase, you will be prompted to enter it before you can change to a new passphrase. {% windows %} -## Abrir automaticamente o `ssh-agent` no Git para Windows +## Auto-launching `ssh-agent` on Git for Windows -Você pode executar `ssh-agent` automaticamente ao abrir o bash ou o Git shell. Copie as linhas a seguir e cole-as no arquivo `~/.profile` ou `~/.bashrc` no Git Shell: +You can run `ssh-agent` automatically when you open bash or Git shell. Copy the following lines and paste them into your `~/.profile` or `~/.bashrc` file in Git shell: ``` bash env=~/.ssh/agent.env @@ -64,15 +63,15 @@ fi unset env ``` -Se sua chave privada não estiver armazenada em um dos locais-padrão (como `~/. sh/id_rsa`), você precisará dizer ao seu agente de autenticação SSH onde encontrá-la. Para adicionar a chave ao ssh-agent, digite `ssh-add ~/path/to/my_key`. Para obter mais informações, consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)". +If your private key is not stored in one of the default locations (like `~/.ssh/id_rsa`), you'll need to tell your SSH authentication agent where to find it. To add your key to ssh-agent, type `ssh-add ~/path/to/my_key`. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)" {% tip %} -**Dica:** se você quiser que o `ssh-agent` esqueça sua chave depois de algum tempo, configure-o para isso executando `ssh-add -t `. +**Tip:** If you want `ssh-agent` to forget your key after some time, you can configure it to do so by running `ssh-add -t `. {% endtip %} -Agora, quando você executar o Git Bash pela primeira vez, sua frase secreta será solicitada: +Now, when you first run Git Bash, you are prompted for your passphrase: ```shell > Initializing new SSH agent... @@ -85,25 +84,25 @@ Agora, quando você executar o Git Bash pela primeira vez, sua frase secreta ser > Run 'git help ' to display help for specific commands. ``` -O processo do `ssh-agent` continuará sendo executado até você fazer logoff, desligar o computador ou interromper o processo. +The `ssh-agent` process will continue to run until you log out, shut down your computer, or kill the process. {% endwindows %} {% mac %} -## Salvar a frase secreta na keychain +## Saving your passphrase in the keychain -No Mac OS X Leopard até o OS X El Capitan, estes arquivos de chave privada padrão são tratados automaticamente: +On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically: - *.ssh/id_rsa* - *.ssh/identity* -Na primeira vez que você usar a chave, precisará digitar sua frase secreta. Se você optar por salvar a frase secreta com a keychain, não precisará digitá-la novamente. +The first time you use your key, you will be prompted to enter your passphrase. If you choose to save the passphrase with your keychain, you won't have to enter it again. -Caso contrário, armazene a frase secreta na keychain quando adicionar a chave ao ssh-agent. Para obter mais informações, consulte "[Adicionar sua chave SSH ao ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)". +Otherwise, you can store your passphrase in the keychain when you add your key to the ssh-agent. For more information, see "[Adding your SSH key to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)." {% endmac %} -## Leia mais +## Further reading -- "[Sobre SSH](/articles/about-ssh)" +- "[About SSH](/articles/about-ssh)" diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index 1d89343fd851..91249e7e4e7b 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -76,7 +76,7 @@ If you authenticate without {% data variables.product.prodname_cli %}, you will ### Authorizing for SAML single sign-on -{% ifversion fpt or ghec %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %} +{% ifversion fpt or ghec %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index ccb0b169ea60..da6560320359 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -27,7 +27,7 @@ shortTitle: Create a PAT Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). -{% ifversion fpt or ghec %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %} +{% ifversion fpt or ghec %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %} @@ -65,7 +65,7 @@ A token with no assigned scopes can only access public information. To use your {% endwarning %} -{% ifversion fpt or ghec %}9. To use your token to authenticate to an organization that uses SAML SSO, [authorize the token for use with a SAML single-sign-on organization](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %} +{% ifversion fpt or ghec %}9. To use your token to authenticate to an organization that uses SAML single sign-on, authorize the token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} ## Using a token on the command line diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index 7620a03432e9..e36953072663 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -1,9 +1,9 @@ --- -title: Sobre a verificação de assinatura de commit -intro: 'Ao usar GPG ou S/MIME, você pode assinar tags e commits localmente. Essas tags ou commits estão marcadas como verificadas em {% data variables.product.product_name %} para que outras pessoas possam estar confiantes de que as alterações vêm de uma fonte de confiança.' +title: About commit signature verification +intro: 'Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can be confident that the changes come from a trusted source.' redirect_from: - - /articles/about-gpg-commit-and-tag-signatures/ - - /articles/about-gpg/ + - /articles/about-gpg-commit-and-tag-signatures + - /articles/about-gpg - /articles/about-commit-signature-verification - /github/authenticating-to-github/about-commit-signature-verification - /github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification @@ -15,85 +15,84 @@ versions: topics: - Identity - Access management -shortTitle: Fazer commit da verificação de assinatura +shortTitle: Commit signature verification --- +## About commit signature verification -## Sobre a verificação de assinatura de commit +You can sign commits and tags locally, to give other people confidence about the origin of a change you have made. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, GitHub marks the commit or tag {% ifversion fpt or ghec %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %} -Você pode assinar commits e tags localmente para dar a outras pessoas confiança sobre a origem de uma alteração que você fez. Se um commit ou tag tiver uma assinatura GPG ou S/MIME que seja verificável criptograficamente, o GitHub marcará o commit ou a tag {% ifversion fpt or ghec %}"Verificado" ou "Verificado parcialmente."{% else %}"Verificado."{% endif %} - -![Commit verificado](/assets/images/help/commits/verified-commit.png) +![Verified commit](/assets/images/help/commits/verified-commit.png) {% ifversion fpt or ghec %} -Os commits e tags têm o seguinte status de verificação, dependendo se você habilitou o modo vigilante. Por padrão, o modo vigilante não está habilitado. Para obter informações sobre como habilitar o modo vigilante, consulte "[Exibir status de verificação para todos os seus commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)". +Commits and tags have the following verification statuses, depending on whether you have enabled vigilant mode. By default vigilant mode is not enabled. For information on how to enable vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)." {% data reusables.identity-and-permissions.vigilant-mode-beta-note %} -### Status padrão +### Default statuses -| Status | Descrição | -| ------------------------- | ------------------------------------------------------------------- | -| **Verificado** | O commit foi assinado e a assinatura foi verificada com sucesso. | -| **Não verificado** | O commit foi assinado, mas não foi possível verificar a assinatura. | -| Sem status de verificação | O commit não foi assinado. | +| Status | Description | +| -------------- | ----------- | +| **Verified** | The commit is signed and the signature was successfully verified. +| **Unverified** | The commit is signed but the signature could not be verified. +| No verification status | The commit is not signed. -### Status com modo vigilante habilitado +### Statuses with vigilant mode enabled {% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %} {% else %} -Se um commit ou tag tiver uma assinatura que não pode ser verificada, {% data variables.product.product_name %} marca o commit ou a tag "não verificada". +If a commit or tag has a signature that can't be verified, {% data variables.product.product_name %} marks the commit or tag "Unverified." {% endif %} -Os administradores do repositório podem impor a assinatura de commit obrigatória em um branch para bloquear todos os commits que não estejam assinados e verificados. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-signed-commits)." +Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)." {% data reusables.identity-and-permissions.verification-status-check %} {% ifversion fpt or ghec %} -{% data variables.product.product_name %} usará automaticamente o GPG para assinar os commits que você criar usando a interface web de {% data variables.product.product_name %}. Commits assinados por {% data variables.product.product_name %} terão um status de verificado em {% data variables.product.product_name %}. É possível verificar a assinatura localmente usando a chave pública disponível em https://github.com/web-flow.gpg. A impressão digital completa da chave é `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. Opcionalmente, você pode escolher que {% data variables.product.product_name %} assine os commits que você fizer em {% data variables.product.prodname_codespaces %}. Para obter mais informações sobre como habilitar a verificação de GPG para os seus códigos, consulte "[Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". +{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. The full fingerprint of the key is `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." {% endif %} -## Verificação da assinatura de commit GPG +## GPG commit signature verification -É possível usar GPG para assinar commits com uma chave GPG que você mesmo gera. +You can use GPG to sign commits with a GPG key that you generate yourself. -{% data variables.product.product_name %} usa bibliotecas OpenPGP para confirmar que seus commits e tags assinados localmente são verificáveis criptograficamente com base em uma chave pública que você adicionou à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +{% data variables.product.product_name %} uses OpenPGP libraries to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. -Para assinar commits usando GPG e para que esses commits sejam verificados no {% data variables.product.product_name %}, siga estas etapas: +To sign commits using GPG and have those commits verified on {% data variables.product.product_name %}, follow these steps: -1. [Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys) -2. [Gerar uma nova chave GPG](/articles/generating-a-new-gpg-key) -3. [Adicionar uma nova chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account) -4. [Informar o Git sobre a chave de assinatura](/articles/telling-git-about-your-signing-key) -5. [Assinar commits](/articles/signing-commits) -6. [Assinar tags](/articles/signing-tags) +1. [Check for existing GPG keys](/articles/checking-for-existing-gpg-keys) +2. [Generate a new GPG key](/articles/generating-a-new-gpg-key) +3. [Add a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account) +4. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key) +5. [Sign commits](/articles/signing-commits) +6. [Sign tags](/articles/signing-tags) -## Verificação da assinatura de commit S/MIME +## S/MIME commit signature verification -Você pode usar S/MIME para assinar commits com uma chave X.509 emitida pela organização. +You can use S/MIME to sign commits with an X.509 key issued by your organization. -O {% data variables.product.product_name %} usa [o pacote Debian ca-certificates](https://packages.debian.org/hu/jessie/ca-certificates), a mesma loja confiável usada pelos navegadores Mozilla, para confirmar se seus commits e tags localmente assinados são criptograficamente verificáveis em uma chave pública em um certificado raiz confiável. +{% data variables.product.product_name %} uses [the Debian ca-certificates package](https://packages.debian.org/hu/jessie/ca-certificates), the same trust store used by Mozilla browsers, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key in a trusted root certificate. {% data reusables.gpg.smime-git-version %} -Para assinar commits usando S/MIME e para que esses commits sejam verificados no {% data variables.product.product_name %}, siga estas etapas: +To sign commits using S/MIME and have those commits verified on {% data variables.product.product_name %}, follow these steps: -1. [Informar o Git sobre a chave de assinatura](/articles/telling-git-about-your-signing-key) -2. [Assinar commits](/articles/signing-commits) -3. [Assinar tags](/articles/signing-tags) +1. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key) +2. [Sign commits](/articles/signing-commits) +3. [Sign tags](/articles/signing-tags) -Não é preciso fazer upload da chave pública no {% data variables.product.product_name %}. +You don't need to upload your public key to {% data variables.product.product_name %}. {% ifversion fpt or ghec %} -## Verificação de assinatura para bots +## Signature verification for bots -As organizações e {% data variables.product.prodname_github_apps %} que exigem a assinatura de commit podem usar bots para assinar commits. Se um commit ou uma tag tiver uma assinatura de bot que possa ser verificada de maneira criptográfica, o {% data variables.product.product_name %} marcará o commit ou tag como verificado. +Organizations and {% data variables.product.prodname_github_apps %} that require commit signing can use bots to sign commits. If a commit or tag has a bot signature that is cryptographically verifiable, {% data variables.product.product_name %} marks the commit or tag as verified. -A verificação de assinatura para bots somente funcionará se a solicitação for verificada e autenticada como o {% data variables.product.prodname_github_app %} ou bot e se não tiver informações de autor personalizadas, informações de committer personalizadas e nenhuma informação de assinatura personalizada, como API de commits. +Signature verification for bots will only work if the request is verified and authenticated as the {% data variables.product.prodname_github_app %} or bot and contains no custom author information, custom committer information, and no custom signature information, such as Commits API. {% endif %} -## Leia mais +## Further reading -- "[Assinar commits](/articles/signing-commits)" -- "[Assinar tags](/articles/signing-tags)" -- "[Solucionar verificação da assinatura de commit](/articles/troubleshooting-commit-signature-verification)" +- "[Signing commits](/articles/signing-commits)" +- "[Signing tags](/articles/signing-tags)" +- "[Troubleshooting commit signature verification](/articles/troubleshooting-commit-signature-verification)" diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md index 53b8a2e34de4..8a3ba49810e3 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md @@ -1,11 +1,11 @@ --- -title: Gerenciar a verificação de assinatura de commit -intro: 'Você pode assinar seu trabalho localmente usando GPG ou S/MIME. O {% data variables.product.product_name %} verificará essas assinaturas, assim as pessoas saberão que seus commits tem origem em uma fonte confiável.{% ifversion fpt %} O {% data variables.product.product_name %} assinará automaticamente os commits que você fez com a interface web do {% data variables.product.product_name %}.{% endif %}' +title: Managing commit signature verification +intro: 'You can sign your work locally using GPG or S/MIME. {% data variables.product.product_name %} will verify these signatures so other people will know that your commits come from a trusted source.{% ifversion fpt %} {% data variables.product.product_name %} will automatically sign commits you make using the {% data variables.product.product_name %} web interface.{% endif %}' redirect_from: - - /articles/generating-a-gpg-key/ - - /articles/signing-commits-with-gpg/ + - /articles/generating-a-gpg-key + - /articles/signing-commits-with-gpg - /articles/managing-commit-signature-verification - - /github/authenticating-to-github/managing-commit-signature-verification/ + - /github/authenticating-to-github/managing-commit-signature-verification versions: fpt: '*' ghes: '*' @@ -24,6 +24,6 @@ children: - /associating-an-email-with-your-gpg-key - /signing-commits - /signing-tags -shortTitle: Verificar assinaturas de commit +shortTitle: Verify commit signatures --- diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md index ad03fae2b291..a158f5199a66 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md @@ -2,8 +2,8 @@ title: Signing commits intro: You can sign commits locally using GPG or S/MIME. redirect_from: - - /articles/signing-commits-and-tags-using-gpg/ - - /articles/signing-commits-using-gpg/ + - /articles/signing-commits-and-tags-using-gpg + - /articles/signing-commits-using-gpg - /articles/signing-commits - /github/authenticating-to-github/signing-commits - /github/authenticating-to-github/managing-commit-signature-verification/signing-commits diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md index 06079bdc1af5..7d9a38a398a1 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md @@ -1,8 +1,8 @@ --- -title: Assinar tags -intro: Você pode assinar as tags localmente usando GPG ou S/MIME. +title: Signing tags +intro: You can sign tags locally using GPG or S/MIME. redirect_from: - - /articles/signing-tags-using-gpg/ + - /articles/signing-tags-using-gpg - /articles/signing-tags - /github/authenticating-to-github/signing-tags - /github/authenticating-to-github/managing-commit-signature-verification/signing-tags @@ -15,26 +15,25 @@ topics: - Identity - Access management --- - {% data reusables.gpg.desktop-support-for-commit-signing %} -1. Para assinar uma tag, adicione `-s` ao comando `git tag`. +1. To sign a tag, add `-s` to your `git tag` command. ```shell $ git tag -s mytag # Creates a signed tag ``` -2. Verifique a tag assinada executando `git tag -v [tag-name]`. +2. Verify your signed tag it by running `git tag -v [tag-name]`. ```shell $ git tag -v mytag # Verifies the signed tag ``` -## Leia mais +## Further reading -- "[Exibir tags do seu repositório](/articles/viewing-your-repositorys-tags)" -- "[Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -- "[Gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)" -- "[Adicionar uma nova chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -- "[Avisar o Git sobre sua chave de assinatura](/articles/telling-git-about-your-signing-key)" -- "[Associar um e-mail à sua chave GPG](/articles/associating-an-email-with-your-gpg-key)" -- "[Assinar commits](/articles/signing-commits)" +- "[Viewing your repository's tags](/articles/viewing-your-repositorys-tags)" +- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" +- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)" +- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)" +- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)" +- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)" +- "[Signing commits](/articles/signing-commits)" diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md index 498aee25beea..25275ba5df21 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md @@ -1,8 +1,8 @@ --- -title: Informar ao Git sobre a chave de assinatura -intro: 'Para assinar commits localmente, você precisa informar ao Git que há uma chave GPG ou X.509 que você gostaria de usar.' +title: Telling Git about your signing key +intro: 'To sign commits locally, you need to inform Git that there''s a GPG or X.509 key you''d like to use.' redirect_from: - - /articles/telling-git-about-your-gpg-key/ + - /articles/telling-git-about-your-gpg-key - /articles/telling-git-about-your-signing-key - /github/authenticating-to-github/telling-git-about-your-signing-key - /github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key @@ -14,33 +14,32 @@ versions: topics: - Identity - Access management -shortTitle: Informe ao Git sua chave de assinatura +shortTitle: Tell Git your signing key --- - {% mac %} -## Informar ao Git sobre a chave GPG +## Telling Git about your GPG key -Se você estiver usando uma chave GPG que corresponde à sua identidade do autor do submissão e ao endereço de e-mail verificado associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá começar a assinar commits e tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} -Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "[Associar e-mail à chave GPG](/articles/associating-an-email-with-your-gpg-key)". +If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". {% endnote %} -Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada. +If you have multiple GPG keys, you need to tell Git which one to use. {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} -1. Se você não estiver usando o pacote GPG, execute o comando a seguir no shell do `zsh` para adicionar a chave GPG ao seu arquivo `.zshrc`, se ele existir, ou seu arquivo `.zprofile`: +1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file: ```shell $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \ else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi ``` - Como alternativa, se você usar o shall de `bash`, execute este comando: + Alternatively, if you use the `bash` shell, run this command: ```shell $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \ else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi @@ -52,17 +51,17 @@ Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usad {% windows %} -## Informar ao Git sobre a chave GPG +## Telling Git about your GPG key -Se você estiver usando uma chave GPG que corresponde à sua identidade do autor do submissão e ao endereço de e-mail verificado associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá começar a assinar commits e tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} -Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "[Associar e-mail à chave GPG](/articles/associating-an-email-with-your-gpg-key)". +If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". {% endnote %} -Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada. +If you have multiple GPG keys, you need to tell Git which one to use. {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %} @@ -75,41 +74,41 @@ Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usad {% linux %} -## Informar ao Git sobre a chave GPG +## Telling Git about your GPG key -Se você estiver usando uma chave GPG que corresponde à sua identidade do autor do submissão e ao endereço de e-mail verificado associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá começar a assinar commits e tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} -Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "[Associar e-mail à chave GPG](/articles/associating-an-email-with-your-gpg-key)". +If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". {% endnote %} -Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada. +If you have multiple GPG keys, you need to tell Git which one to use. {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} -1. Para adicionar a sua chave GPG ao seu perfil bash, execute o seguinte comando: +1. To add your GPG key to your bash profile, run the following command: ```shell $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \ else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi ``` {% note %} - **Observação:** se você não tiver `.bash_profile`, este comando adicionará sua chave GPG a `.profile`. + **Note:** If you don't have `.bash_profile`, this command adds your GPG key to `.profile`. {% endnote %} {% endlinux %} -## Leia mais +## Further reading -- "[Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -- "[Gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)" -- "[Usar um endereço de e-mail verificado na chave GPG](/articles/using-a-verified-email-address-in-your-gpg-key)" -- "[Adicionar uma nova chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -- "[Associar um e-mail à sua chave GPG](/articles/associating-an-email-with-your-gpg-key)" -- "[Assinar commits](/articles/signing-commits)" -- "[Assinar tags](/articles/signing-tags)" +- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" +- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)" +- "[Using a verified email address in your GPG key](/articles/using-a-verified-email-address-in-your-gpg-key)" +- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)" +- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)" +- "[Signing commits](/articles/signing-commits)" +- "[Signing tags](/articles/signing-tags)" diff --git a/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md b/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md index cf2b81b35c73..38e0b8786510 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md +++ b/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md @@ -1,8 +1,8 @@ --- -title: Confirmar o status de verificação da assinatura do commit e da tag -intro: 'Você pode conferir o status da verificação da assinatura do commit e da tag no {% data variables.product.product_name %}.' +title: Checking your commit and tag signature verification status +intro: 'You can check the verification status of your commit and tag signatures on {% data variables.product.product_name %}.' redirect_from: - - /articles/checking-your-gpg-commit-and-tag-signature-verification-status/ + - /articles/checking-your-gpg-commit-and-tag-signature-verification-status - /articles/checking-your-commit-and-tag-signature-verification-status - /github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status - /github/authenticating-to-github/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status @@ -14,26 +14,30 @@ versions: topics: - Identity - Access management -shortTitle: Verificar status da verificação +shortTitle: Check verification status --- +## Checking your commit signature verification status -## Confirmar o status de verificação da assinatura do commit - -1. No {% data variables.product.product_name %}, navegue até sua pull request. +1. On {% data variables.product.product_name %}, navigate to your pull request. {% data reusables.repositories.review-pr-commits %} -3. Ao lado do hash do commit abreviado do seu commit, há uma caixa que mostra se a assinatura do seu commit foi verificada{% ifversion fpt or ghec %}, parcialmente verificada{% endif %} ou não verificada. ![Commit assinado](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) -4. Para ver informações mais detalhadas sobre a assinatura de commit, clique em **Verificado**{% ifversion fpt or ghec %}, **Parcialmente verificado**,{% endif %} ou **Não verificado**. ![Commit assinado verificado](/assets/images/help/commits/gpg-signed-commit_verified_details.png) +3. Next to your commit's abbreviated commit hash, there is a box that shows whether your commit signature is verified{% ifversion fpt or ghec %}, partially verified,{% endif %} or unverified. +![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) +4. To view more detailed information about the commit signature, click **Verified**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**. +![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png) -## Confirmar o status de verificação da assinatura da tag +## Checking your tag signature verification status {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} -2. Na parte superior da página Versões, clique em **Tags**. ![Página de tags](/assets/images/help/releases/tags-list.png) -3. Ao lado da descrição da sua tag, há uma caixa que mostra se a assinatura da tag é verificada{% ifversion fpt or ghec %}, parcialmente verificado,{% endif %} ou não verificada. ![assinatura de tag verificada](/assets/images/help/commits/gpg-signed-tag-verified.png) -4. Para ver informações mais detalhadas sobre a assinatura do marcador, clique em **Verificado**{% ifversion fpt or ghec %}, **Parcialmente verificado**,{% endif %} ou **Não verificado**. ![Tag assinada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png) +2. At the top of the Releases page, click **Tags**. +![Tags page](/assets/images/help/releases/tags-list.png) +3. Next to your tag description, there is a box that shows whether your tag signature is verified{% ifversion fpt or ghec %}, partially verified,{% endif %} or unverified. +![verified tag signature](/assets/images/help/commits/gpg-signed-tag-verified.png) +4. To view more detailed information about the tag signature, click **Verified**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**. +![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png) -## Leia mais +## Further reading -- "[Sobre a verificação de assinatura de commit](/articles/about-commit-signature-verification)" -- "[Assinar commits](/articles/signing-commits)" -- "[Assinar tags](/articles/signing-tags)" +- "[About commit signature verification](/articles/about-commit-signature-verification)" +- "[Signing commits](/articles/signing-commits)" +- "[Signing tags](/articles/signing-tags)" diff --git a/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md b/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md index a99acc3ca049..46abaa90dfdb 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md +++ b/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md @@ -1,10 +1,10 @@ --- -title: Solucionar problemas de verificação de assinatura de commit -intro: 'Talvez você precise solucionar problemas inesperados ao assinar commits localmente para verificação no {% data variables.product.product_name %}.' +title: Troubleshooting commit signature verification +intro: 'You may need to troubleshoot unexpected issues that arise when signing commits locally for verification on {% data variables.product.product_name %}.' redirect_from: - - /articles/troubleshooting-gpg/ + - /articles/troubleshooting-gpg - /articles/troubleshooting-commit-signature-verification - - /github/authenticating-to-github/troubleshooting-commit-signature-verification/ + - /github/authenticating-to-github/troubleshooting-commit-signature-verification versions: fpt: '*' ghes: '*' @@ -17,6 +17,6 @@ children: - /checking-your-commit-and-tag-signature-verification-status - /updating-an-expired-gpg-key - /using-a-verified-email-address-in-your-gpg-key -shortTitle: Verificação da solução de problemas +shortTitle: Troubleshoot verification --- diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md index 3d1c664293a1..1f852e1bcf7a 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md @@ -1,8 +1,8 @@ --- -title: 'Erro: agente com falha ao entrar' -intro: 'Em raras circunstâncias, a conexão com o {% data variables.product.product_name %} via SSH no Linux produz o erro "Agente com falha ao entrar usando a chave". Siga estas etapas para resolver o problema.' +title: 'Error: Agent admitted failure to sign' +intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.' redirect_from: - - /articles/error-agent-admitted-failure-to-sign-using-the-key/ + - /articles/error-agent-admitted-failure-to-sign-using-the-key - /articles/error-agent-admitted-failure-to-sign - /github/authenticating-to-github/error-agent-admitted-failure-to-sign - /github/authenticating-to-github/troubleshooting-ssh/error-agent-admitted-failure-to-sign @@ -13,41 +13,40 @@ versions: ghec: '*' topics: - SSH -shortTitle: Falha do agente ao assinar +shortTitle: Agent failure to sign --- - -Ao tentar se conectar via SSH ao {% data variables.product.product_location %} em um computador Linux, você poderá receber a seguinte mensagem: +When trying to SSH into {% data variables.product.product_location %} on a Linux computer, you may see the following message in your terminal: ```shell $ ssh -vT git@{% data variables.command_line.codeblock %} > ... -> Agente com falha ao entrar usando a chave. -> debug1: Não há mais métodos de autenticação para tentar. -> Permissão negada (publickey). +> Agent admitted failure to sign using the key. +> debug1: No more authentication methods to try. +> Permission denied (publickey). ``` -Para ver mais detalhes, consulte este relatório de problemas. +For more details, see this issue report. -## Resolução +## Resolution -Para corrigir esse erro, carregue suas chaves no agente SSH com `ssh-add`: +You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`: ```shell -# Inicie o ssh-agent em segundo plano +# start the ssh-agent in the background $ eval "$(ssh-agent -s)" > Agent pid 59566 $ ssh-add -> Insira a frase secreta para /home/you/.ssh/id_rsa: [tippy tap] -> Identidade adicionadafrase secreta: /home/you/.ssh/id_rsa (/home/you/.ssh/id_rsa) +> Enter passphrase for /home/you/.ssh/id_rsa: [tippy tap] +> Identity added: /home/you/.ssh/id_rsa (/home/you/.ssh/id_rsa) ``` -Se a chave não tiver o nome de arquivo padrão (`/.ssh/id_rsa`), você precisará passar esse caminho para `ssh-add`: +If your key does not have the default filename (`/.ssh/id_rsa`), you'll have to pass that path to `ssh-add`: ```shell -# Inicie o ssh-agent em segundo plano +# start the ssh-agent in the background $ eval "$(ssh-agent -s)" > Agent pid 59566 $ ssh-add ~/.ssh/my_other_key -> Insira a frase secreta para /home/you/.ssh/my_other_key: [tappity tap tap] -> Identidade adicionada: /home/you/.ssh/my_other_key (/home/you/.ssh/my_other_key) +> Enter passphrase for /home/you/.ssh/my_other_key: [tappity tap tap] +> Identity added: /home/you/.ssh/my_other_key (/home/you/.ssh/my_other_key) ``` diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/index.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/index.md index 0f6da8b1c09e..b7b79529d9a2 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/index.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/index.md @@ -1,9 +1,9 @@ --- -title: Solucionar problemas de SSH -intro: 'Ao usar o SSH para se conectar e autenticar no {% data variables.product.product_name %}, talvez você precise solucionar problemas inesperados que podem surgir.' +title: Troubleshooting SSH +intro: 'When using SSH to connect and authenticate to {% data variables.product.product_name %}, you may need to troubleshoot unexpected issues that may arise.' redirect_from: - /articles/troubleshooting-ssh - - /github/authenticating-to-github/troubleshooting-ssh/ + - /github/authenticating-to-github/troubleshooting-ssh versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md index 94f9d3bb9ecc..e8e60da73069 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md @@ -1,9 +1,9 @@ --- -title: Recuperar frase secreta da chave SSH -intro: 'Se você perder a frase secreta da chave SSH, poderá recuperá-la ou gerar uma nova, dependendo do sistema operacional usado.' +title: Recovering your SSH key passphrase +intro: 'If you''ve lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.' redirect_from: - - /articles/how-do-i-recover-my-passphrase/ - - /articles/how-do-i-recover-my-ssh-key-passphrase/ + - /articles/how-do-i-recover-my-passphrase + - /articles/how-do-i-recover-my-ssh-key-passphrase - /articles/recovering-your-ssh-key-passphrase - /github/authenticating-to-github/recovering-your-ssh-key-passphrase - /github/authenticating-to-github/troubleshooting-ssh/recovering-your-ssh-key-passphrase @@ -14,30 +14,31 @@ versions: ghec: '*' topics: - SSH -shortTitle: Recuperar a frase secreta da chave SSH +shortTitle: Recover SSH key passphrase --- - {% mac %} -Se você [configurou sua frase secreta de SSH com a keychain do macOS](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), você poderá recuperá-la. +If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it. -1. Procure o app **Keychain Access** (Acesso a keychain) no Finder (Localizador). ![Barra de pesquisa do Spotlight](/assets/images/help/setup/keychain-access.png) -2. No Acesso às Chaves, pesquise **SSH**. -3. Clique duas vezes na entrada da chave SSH para abrir uma nova caixa de diálogo. -4. No canto inferior esquerdo, selecione **Mostrar senha**. ![Caixa de diálogo Acesso às Chaves](/assets/images/help/setup/keychain_show_password_dialog.png) -5. A senha de administrador será solicitada. Insira a senha na caixa de diálogo "Acesso às Chaves". -6. A senha será exibida. +1. In Finder, search for the **Keychain Access** app. + ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png) +2. In Keychain Access, search for **SSH**. +3. Double click on the entry for your SSH key to open a new dialog box. +4. In the lower-left corner, select **Show password**. + ![Keychain access dialog](/assets/images/help/setup/keychain_show_password_dialog.png) +5. You'll be prompted for your administrative password. Type it into the "Keychain Access" dialog box. +6. Your password will be revealed. {% endmac %} {% windows %} -Se você perder a frase secreta da chave SSH, não haverá como recuperá-la. Você precisará [gerar uma nova chave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) ou [mudar para o clone HTTPS](/github/getting-started-with-github/managing-remote-repositories) para poder usar a senha do GitHub. +If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/managing-remote-repositories) so you can use your GitHub password instead. {% endwindows %} {% linux %} -Se você perder a frase secreta da chave SSH, não haverá como recuperá-la. Você precisará [gerar uma nova chave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) ou [mudar para o clone HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls) para poder usar a senha do GitHub. +If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls) so you can use your GitHub password instead. {% endlinux %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md index bab3719f2c4d..82e5a8e8b3dc 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md @@ -1,6 +1,6 @@ --- -title: Atualizar sua assinatura do GitHub -intro: 'Você pode atualizar a assinatura para qualquer tipo de conta em {% data variables.product.product_location %} a qualquer momento.' +title: Upgrading your GitHub subscription +intro: 'You can upgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription - /articles/upgrading-your-personal-account-s-billing-plan/ @@ -28,26 +28,26 @@ topics: - Troubleshooting - Upgrades - User account -shortTitle: Atualizar a sua assinatura +shortTitle: Upgrade your subscription --- +## Upgrading your personal account's subscription -## Atualizar a assinatura da sua conta pessoal - -Você pode atualizar sua conta pessoal do {% data variables.product.prodname_free_user %} para o {% data variables.product.prodname_pro %} para obter ferramentas de revisão de código avançadas em repositórios privados. {% data reusables.gated-features.more-info %} +You can upgrade your personal account from {% data variables.product.prodname_free_user %} to {% data variables.product.prodname_pro %} to get advanced code review tools on private repositories. {% data reusables.gated-features.more-info %} {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.billing_plans %} -1. Ao lado de "Plano atual", clique em **Atualizar**. ![Botão Upgrade (Atualizar)](/assets/images/help/billing/settings_billing_user_upgrade.png) -2. Em "Pro" na página "Comparar planos", clique em **Fazer atualização para Pro**. +1. Next to "Current plan", click **Upgrade**. + ![Upgrade button](/assets/images/help/billing/settings_billing_user_upgrade.png) +2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**. {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.show-plan-details %} {% data reusables.dotcom_billing.enter-billing-info %} {% data reusables.dotcom_billing.enter-payment-info %} {% data reusables.dotcom_billing.finish_upgrade %} -## Atualizar a assinatura da organização +## Upgrading your organization's subscription -Você pode atualizar sua organização de {% data variables.product.prodname_free_team %} para uma organização para {% data variables.product.prodname_team %} para acessar ferramentas avançadas de gerenciamento e colaboração para equipes ou atualizar sua organização para o {% data variables.product.prodname_ghe_cloud %} para obter controles adicionais de segurança, conformidade e implantação. {% data reusables.gated-features.more-info-org-products %} +You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls. {% data reusables.gated-features.more-info-org-products %} {% data reusables.dotcom_billing.org-billing-perms %} @@ -60,39 +60,41 @@ Você pode atualizar sua organização de {% data variables.product.prodname_fre {% data reusables.dotcom_billing.owned_by_business %} {% data reusables.dotcom_billing.finish_upgrade %} -### Próximas etapas para organizações que usam o {% data variables.product.prodname_ghe_cloud %} +### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %} -Se você tiver atualizado sua organização para o {% data variables.product.prodname_ghe_cloud %}, você poderá configurar a identidade e a gestão de acesso para a sua organização. For more information, see "[Gerenciar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization)". +If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -Caso queira usar uma conta corporativa com o {% data variables.product.prodname_ghe_cloud %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %} +If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -## Adicionar estações à organização +## Adding seats to your organization -Se você quiser que outros usuários tenham acesso aos repositórios privados da organização {% data variables.product.prodname_team %}, você poderá comprar mais estações a qualquer momento. +If you'd like additional users to have access to your {% data variables.product.prodname_team %} organization's private repositories, you can purchase more seats anytime. {% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.add-seats %} {% data reusables.dotcom_billing.number-of-seats %} {% data reusables.dotcom_billing.confirm-add-seats %} -## Trocar o plano de cobrança da organização de preços por repositório para por usuário +## Switching your organization from per-repository to per-user pricing -{% data reusables.dotcom_billing.switch-legacy-billing %} Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)". +{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.billing-settings %} -5. À direita do nome do seu plano, use o menu suspenso **Editar** e selecione **Editar plano**. ![Menu suspenso de editar](/assets/images/help/billing/per-user-upgrade-button.png) -6. À direita das "Ferramentas avançadas para equipes", clique em **Atualizar agora**. ![Botão Atualizar agora](/assets/images/help/billing/per-user-upgrade-now-button.png) +5. To the right of your plan name, use the **Edit** drop-down menu, and select **Edit plan**. + ![Edit drop-down menu](/assets/images/help/billing/per-user-upgrade-button.png) +6. To the right of "Advanced tools for teams", click **Upgrade now**. + ![Upgrade now button](/assets/images/help/billing/per-user-upgrade-now-button.png) {% data reusables.dotcom_billing.choose_org_plan %} {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.owned_by_business %} {% data reusables.dotcom_billing.finish_upgrade %} -## Solucionar problemas de erro 500 ao atualizar +## Troubleshooting a 500 error when upgrading {% data reusables.dotcom_billing.500-error %} -## Leia mais +## Further reading -- "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)" -- "[Como a atualização ou o downgrade afetam o processo de cobrança?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" -- "[Sobre a cobrança no {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)" +- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)" +- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" +- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)." diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md index b1dda999a173..ea47b4b45a93 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- -title: Requisitos para listar um aplicativo -intro: 'Os aplicativos em {% data variables.product.prodname_marketplace %} devem atender aos requisitos definidos nessa página antes que o anúncio possa ser publicado.' +title: Requirements for listing an app +intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ @@ -14,68 +14,67 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Requisitos de anúncio +shortTitle: Listing requirements --- - -Os requisitos para a anunciar um aplicativo em {% data variables.product.prodname_marketplace %} variam de acordo com o fato de você desejar oferecer um aplicativo grátis ou pago. +The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app. -## Requisitos para todos os anúncios de {% data variables.product.prodname_marketplace %} +## Requirements for all {% data variables.product.prodname_marketplace %} listings -Todos os anúncios em {% data variables.product.prodname_marketplace %} devem ser para ferramentas que fornecem valor à comunidade de {% data variables.product.product_name %}. Ao enviar seu anúncio para publicação, você deverá ler e aceitar os termos do "[ Acordo de Desenvolvedor de {% data variables.product.prodname_marketplace %}](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)". +All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)." -### Requisitos de experiência do usuário para todos os aplicativos +### User experience requirements for all apps -Todos os anúncios devem atender aos requisitos a seguir, independentemente de serem para um aplicativo grátis ou pago. +All listings should meet the following requirements, regardless of whether they are for a free or paid app. -- Os anúncios não devem persuadir ativamente os usuários para fora de {% data variables.product.product_name %}. -- Os anúncios devem incluir informações de contato válidas para o editor. -- Os anúncios devem ter uma descrição relevante do aplicativo. -- Os anúncios devem especificar um plano de preços. -- Os aplicativos devem fornecer valor aos clientes e integrar-se à plataforma de alguma forma além da autenticação. -- Os aplicativos devem estar disponíveis publicamente em {% data variables.product.prodname_marketplace %} e não podem estar na versão beta ou disponíveis apenas por convite. -- Os aplicativos devem ter eventos webhook configurados para notificar o editor de qualquer alteração do plano ou cancelamentos usando a API de {% data variables.product.prodname_marketplace %} Para obter mais informações, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +- Listings must not actively persuade users away from {% data variables.product.product_name %}. +- Listings must include valid contact information for the publisher. +- Listings must have a relevant description of the application. +- Listings must specify a pricing plan. +- Apps must provide value to customers and integrate with the platform in some way beyond authentication. +- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only. +- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Para obter mais informações sobre como fornecer uma boa experiência com o cliente, consulte "[As práticas recomendadas com o cliente para aplicativos](/developers/github-marketplace/customer-experience-best-practices-for-apps)". +For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)." -### Requisitos da marca e anúncios para todos os aplicativos +### Brand and listing requirements for all apps -- Os aplicativos que usam logotipos do GitHub precisam seguir as diretrizes de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Logos e uso de {% data variables.product.company_short %}](https://github.com/logos)". -- Os aplicativos devem ter um logotipo, cartões de recurso, e imagens de captura de tela que atendam às recomendações fornecidas em "[Escrevendo descrições da listagem de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". -- As listagens devem incluir descrições bem escritas e sem erros gramaticais. Para obter orientação par escrever a sua listagem, consulte "[Escrevendo descrições de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". +- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)." +- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." +- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." -Para proteger seus clientes, recomendamos que siga as práticas recomendadas em matéria de segurança. Para obter mais informações, consulte "[as práticas recomendadas de segurança para os aplicativos](/developers/github-marketplace/security-best-practices-for-apps)". +To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)." -## Considerações para aplicativos gratuitos +## Considerations for free apps -{% data reusables.marketplace.free-apps-encouraged %} +{% data reusables.marketplace.free-apps-encouraged %} -## Requisitos para aplicativos pagos +## Requirements for paid apps -Para publicar um plano pago para o seu aplicativo em {% data variables.product.prodname_marketplace %}, seu aplicativo deverá pertencer a uma organização que seja um publicador verificado. Para obter mais informações sobre o processo de verificação ou transferir a propriedade do seu aplicativo, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". +To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transferring ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." -Se seu aplicativo já está publicado e você é um editor verificado, você poderá publicar um novo plano pago no editor do plano de preços. Para obter mais informações, consulte "[Configurar planos de preços para sua listagem](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". +If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -Para publicar um aplicativo pago (ou um aplicativo que ofereça um plano pago), você também deve atender aos seguintes requisitos: +To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements: -- {% data variables.product.prodname_github_apps %} deve ter no mínimo 100 instalações. -- {% data variables.product.prodname_oauth_apps %} deve ter no mínimo 200 usuários. -- Todos os aplicativos pagos devem lidar com eventos de compra de {% data variables.product.prodname_marketplace %} para novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter mais informações, consulte "[Requisitos de cobrança para aplicativos pagos](#billing-requirements-for-paid-apps)" abaixo. +- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations. +- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users. +- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. -Quando estiver pronto para publicar o aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar a verificação para o anúncio do aplicativo. +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing. {% note %} -**Observação:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como transferir um aplicativo para uma organização, consulte: "[Enviar o seu anúncio para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". +**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." {% endnote %} -## Requisitos de cobrança para aplicativos pagos +## Billing requirements for paid apps -Seu aplicativo não precisa gerenciar pagamentos, mas precisa usar eventos de compra de {% data variables.product.prodname_marketplace %} para gerenciar novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter informações sobre como integrar esses eventos no seu aplicativo, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their account on {% data variables.product.product_location %}. -- Os aplicativos devem ser compatíveis tanto com a cobrança anual quanto mensal para as compras de suas assinaturas pagas. -- As listagens podem oferecer qualquer combinação de planos grátis e pagos. Os planos grátis são opcionais, porém incentivados. Para obter mais informações, consulte "[Definir um plano de preços da listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". +- Apps must support both monthly and annual billing for paid subscriptions purchases. +- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." diff --git a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md index f39af809d3e5..9b9bc6f64635 100644 --- a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md +++ b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md @@ -1,6 +1,6 @@ --- -title: Sobre o GitHub Marketplace -intro: 'Aprenda sobre {% data variables.product.prodname_marketplace %} em que você pode compartilhar seus aplicativos e ações publicamente com todos os usuários do {% data variables.product.product_name %}.' +title: About GitHub Marketplace +intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.' redirect_from: - /apps/marketplace/getting-started/ - /marketplace/getting-started @@ -11,56 +11,55 @@ versions: topics: - Marketplace --- - -[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) conecta você a desenvolvedores que querem estender e melhorar seus fluxos de trabalho do {% data variables.product.prodname_dotcom %}. Você pode listar ferramentas gratuitas e pagas para os desenvolvedores usarem no {% data variables.product.prodname_marketplace %}. O {% data variables.product.prodname_marketplace %} oferece aos desenvolvedores dois tipos de ferramenta: {% data variables.product.prodname_actions %} e aplicativos, e cada ferramenta exige etapas diferentes para adicioná-lo ao {% data variables.product.prodname_marketplace %}. +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) connects you to developers who want to extend and improve their {% data variables.product.prodname_dotcom %} workflows. You can list free and paid tools for developers to use in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_marketplace %} offers developers two types of tools: {% data variables.product.prodname_actions %} and Apps, and each tool requires different steps for adding it to {% data variables.product.prodname_marketplace %}. ## GitHub Actions {% data reusables.actions.actions-not-verified %} -Para saber mais sobre publicação de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_marketplace %}, consulte "[Publicar ações no GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)". +To learn about publishing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." -## Aplicativos +## Apps -Qualquer pessoa pode compartilhar seus aplicativos com outros usuários gratuitamente em {% data variables.product.prodname_marketplace %}, mas somente os aplicativos pertencentes a organizações podem vender seu aplicativo. +Anyone can share their apps with other users for free on {% data variables.product.prodname_marketplace %} but only apps owned by organizations can sell their app. -Para publicar planos pagos para o seu aplicativo e exibir um selo do Marketplace, você deve concluir o processo de verificação do publicador. Para obter mais informações, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" ou "[Requisitos para anunciar um aplicativo](/developers/github-marketplace/requirements-for-listing-an-app)". +To publish paid plans for your app and display a marketplace badge, you must complete the publisher verification process. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" or "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." -Uma vez que a organização atenda aos requisitos, alguém com permissões de proprietário na organização pode publicar planos pagos para qualquer um dos aplicativos. Cada aplicativo com um plano pago também passa por um processo de integração financeira para habilitar pagamentos. +Once the organization meets the requirements, someone with owner permissions in the organization can publish paid plans for any of their apps. Each app with a paid plan also goes through a financial onboarding process to enable payments. -Para publicar aplicativos com planos grátis, você só precisa atender aos requisitos gerais para anunciar qualquer aplicativo. Para obter mais informações, consulte "[Requisitos para todos os anúncios do GitHub Marketplace](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)". +To publish apps with free plans, you only need to meet the general requirements for listing any app. For more information, see "[Requirements for all GitHub Marketplace listings](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)." -### Novo nos aplicativos? +### New to apps? -Se você estiver interessado em criar um aplicativo para {% data variables.product.prodname_marketplace %}, mas você é novo em {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_apps %}, consulte "[Criando {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" ou "[Criando {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)." +If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)." ### {% data variables.product.prodname_github_apps %} vs. {% data variables.product.prodname_oauth_apps %} -{% data reusables.marketplace.github_apps_preferred %}, embora você possa anunciar OAuth e {% data variables.product.prodname_github_apps %} em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" e "[Fazendo a migração de {% data variables.product.prodname_oauth_apps %} para {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)". +{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_apps %} in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_apps %} to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." -## Publicar um aplicativo na visão geral de {% data variables.product.prodname_marketplace %} +## Publishing an app to {% data variables.product.prodname_marketplace %} overview -Ao terminar de criar seu aplicativo, você poderá compartilhá-lo com outros usuários publicando-o em {% data variables.product.prodname_marketplace %}. Em resumo, o processo é: +When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: -1. Revise cuidadosamente o seu app para garantir que se comportará como esperado em outros repositórios e que segue as diretrizes das práticas recomendadas. Para obter mais informações, consulte "[as práticas de segurança recomendadas para os aplicativos](/developers/github-marketplace/security-best-practices-for-apps)" e "[requisitos para listar um app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)". +1. Review your app carefully to ensure that it will behave as expected in other repositories and that it follows best practice guidelines. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)." -1. Adicionar eventos webhook ao aplicativo para rastrear solicitações de cobrança do usuário. Para obter mais informações sobre a API de {% data variables.product.prodname_marketplace %}, eventos de webhook e solicitações de cobrança, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +1. Add webhook events to the app to track user billing requests. For more information about the {% data variables.product.prodname_marketplace %} API, webhook events, and billing requests, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -1. Crie um rascunho de listagem de {% data variables.product.prodname_marketplace %} Para obter mais informações, consulte "[Criar uma listagem para o seu aplicativo](/developers/github-marketplace/drafting-a-listing-for-your-app)". +1. Create a draft {% data variables.product.prodname_marketplace %} listing. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -1. Adicionar um plano de preços. Para obter mais informações, consulte "[Configurar planos de preços para sua listagem](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". +1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -1. Read and accept the terms of the "\[{% data variables.product.prodname_marketplace %} Developer Agreement\](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement." +1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement." -1. Envie seu anúncio para publicação em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Enviar sua listagem para publicação](/developers/github-marketplace/submitting-your-listing-for-publication)". +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." -## Ver como seu aplicativo está sendo executado +## Seeing how your app is performing -Você pode acessar métricas e transações para a sua listagem. Para obter mais informações, consulte: +You can access metrics and transactions for your listing. For more information, see: -- "[Visualizar métricas para a sua listagem](/developers/github-marketplace/viewing-metrics-for-your-listing)" -- "[Visualizar transações para a sua listagem](/developers/github-marketplace/viewing-transactions-for-your-listing)" +- "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" +- "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" -## Entrar em contato com o suporte +## Contacting Support -Em caso de dúvidas dúvidas sobre {% data variables.product.prodname_marketplace %}, entre em contato diretamente com {% data variables.contact.contact_support %}. +If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md index 00e8a977b12d..1905ce84460e 100644 --- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md @@ -1,6 +1,6 @@ --- -title: Escrever uma descrição da listagem para o seu aplicativo -intro: 'Para [listar seu aplicativo](/marketplace/listing-on-github-marketplace/) no {% data variables.product.prodname_marketplace %}, você precisará escrever as descrições do seu aplicativo e fornecer imagens que seguem as diretrizes do GitHub.' +title: Writing a listing description for your app +intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.' redirect_from: - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions/ - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions/ @@ -16,183 +16,181 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Escrever descrições de anúncio +shortTitle: Write listing descriptions --- +Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing. -Aqui estão as diretrizes sobre os campos que você precisará preencher na seção de **Descrição da listagem** do seu rascunho da listagem. +## Naming and links -## Nomenclatura e links +### Listing name -### Nome da listagem +Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing account on {% data variables.product.product_location %}, unless the name is your own user or organization name. -O nome do seu anúncio irá aparecer na [página inicial de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). O nome é limitado a 255 caracteres e pode ser diferente do nome do seu aplicativo. Your listing cannot have the same name as an existing account on {% data variables.product.product_location %}, unless the name is your own user or organization name. +### Very short description -### Descrição muito curta +The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). -A comunidade verá a descrição "muito curta" sob o nome de seu aplicativo [na página inicial do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). +![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png) -![Descrição curta do aplicativo em {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_short_description.png) +#### Length -#### Comprimento +We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly. -Recomendamos manter descrições curtas para com 40 a 80 caracteres. Embora você possa usar mais caracteres, as descrições concisas são mais fáceis para os clientes ler e entender rapidamente. +#### Content -#### Conteúdo +- Describe the app’s functionality. Don't use this space for a call to action. For example: -- Descreva as funcionalidades do aplicativo. Não use este espaço para uma chamada para ação. Por exemplo: + **DO:** Lightweight project management for GitHub issues - **RECOMENDADO:** Gerenciamento de projeto leve para problemas do GitHub + **DON'T:** Manage your projects and issues on GitHub - **NÃO RECOMENDADO:** Gerencie seus projetos e problemas no GitHub + **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_ - **Dica:** Adicione um "s" ao final do verbo em uma chamada para ação para transformá-lo em uma descrição aceitável: _Gerencia seus projetos e problemas no GitHub_ +- Don’t repeat the app’s name in the description. -- Não repita o nome do aplicativo na descrição. + **DO:** A container-native continuous integration tool - **RECOMENDADO:** Uma ferramenta de integração contínua nativa para o contêiner + **DON'T:** Skycap is a container-native continuous integration tool - **NÃO RECOMENDADO:** O Skycap é uma ferramenta de integração contínua nativa do contêiner +#### Formatting -#### Formatação +- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns. -- Use sempre letras maiúsculas na frase. Use maiúscula somente para a primeira letra e para substantivos próprios. +- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence. -- Não use pontuação no final da sua descrição curta. As descrições curtas não devem incluir frases completas e definitivamente não devem incluir mais de uma frase. +- Only capitalize proper nouns. For example: -- Use maiúscula apenas para os substantivos próprios. Por exemplo: + **DO:** One-click delivery automation for web developers - **RECOMENDADO:** Automação de entrega com um clique para desenvolvedores web + **DON'T:** One-click delivery automation for Web Developers - **NÃO RECOMENDADO:** Automação de entrega com um clique para desenvolvedores web +- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. -- Sempre use uma [vírgula de série](https://en.wikipedia.org/wiki/Serial_comma) nas listas. +- Avoid referring to the GitHub community as "users." -- Evite referir-se à comunidade do GitHub como "usuários". + **DO:** Create issues automatically for people in your organization - **RECOMENDADO:** Crie problemas automaticamente para pessoas da sua organização + **DON'T:** Create issues automatically for an organization's users - **NÃO RECOMENDADO:** Crie problemas automaticamente para usuários de uma organização +- Avoid acronyms unless they’re well established (such as API). For example: -- Evite acrônimos, a menos que estejam conhecidos (como, por exemplo, API). Por exemplo: + **DO:** Agile task boards, estimates, and reports without leaving GitHub - **RECOMENDADO:** Quadros de tarefas ágeis, estimativas e relatórios sem sair do GitHub + **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI - **NÃO RECOMENDADO:** Quadros de tarefas ágeis, estimativas e relatórios sem sair da interface de usuário do GitHub +### Categories -### Categorias +Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app. -Os aplicativos em {% data variables.product.prodname_marketplace %} podem ser exibidos por categoria. Selecione a categoria que melhor descreve a principal funcionalidade do seu aplicativo no menu suspenso **categoria primária**, e opcionalmente, selecione uma **categoria secundária** que se encaixa no seu aplicativo. +### Supported languages -### Linguagens compatíveis +If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional. -Se o seu aplicativo só funciona com idiomas específicos, selecione até 10 linguagens de programação com as quais o seu aplicativo é compatível. Esses idiomas são exibidos na página de listagem do {% data variables.product.prodname_marketplace %} do seu aplicativo. Este campo é opcional. +### Listing URLs -### Listar URLs +**Required URLs** +* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries. +* **Privacy policy URL:** The web page that displays your app's privacy policy. +* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App. -**URLs obrigatórias** -* **URL de suporte ao cliente:** A URL de uma página da web para a qual seus clientes acessarão quando tiverem dúvidas referente ao suporte técnico, produtos ou conta. -* **URL da política de privacidade:** A página da web que exibe a política de privacidade do seu aplicativo. -* **URL de instalação:** Este campo é exibido somente para os aplicativos OAuth. (Os aplicativos GitHub não usam esta URL porque usam a URL de configuração opcional em sua página de configurações.) Quando um cliente compra seu aplicativo OAuth, o GitHub irá redirecionar os clientes para a URL de instalação após instalarem o aplicativo. Você deverá redirecionar os clientes para `https://github.com/login/oauth/authorize` para iniciar o fluxo de autorização do OAuth. Consulte "[Novas compras para os aplicativos OAuth](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para obter mais informações. Ignore este campo se você estiver listando um aplicativo GitHub. +**Optional URLs** +* **Company URL:** A link to your company's website. +* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance. +* **Documentation URL:** A link to documentation that teaches customers how to use your app. -**URLs opcionais** -* **URL da empresa:** Um link para o site da sua empresa. -* **URL de status:** Um link para uma página da web que exibe o status do seu aplicativo. As páginas de status podem incluir relatórios de incidente atuais e em forma de histórico, status do tempo de atividade do aplicativo, bem como manutenção programada. -* **URL da documentação:** Um link para a documentação que ensina os clientes a usar seu aplicativo. +## Logo and feature card -## Logotipo e cartão de recurso +{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps. -{% data variables.product.prodname_marketplace %} exibe todas as listagens com um logotipo quadrado dentro de um selo circular para distinguir visualmente os aplicativos. +![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png) -![Imagens e logotipo do GitHub Marketplace](/assets/images/marketplace/marketplace-logo-and-badge.png) +A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card. -Um cartão de recursos consiste do logotipo, nome e uma imagem de fundo personalizada do seu aplicativo que capta a personalidade da sua marca. {% data variables.product.prodname_marketplace %} exibe este cartão se seu aplicativo for um dos quatro aplicativos destacado aleatoriamente na parte superior da [página inicial](https://github.com/marketplace). A descrição muito curta de cada aplicativo é exibida abaixo de seu cartão de recursos. +![Feature card](/assets/images/marketplace/marketplace_feature_card.png) -![Cartão de recurso](/assets/images/marketplace/marketplace_feature_card.png) +As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card. -À medida que você faz o upload das imagens e seleciona as cores, sua listagem de rascunho do {% data variables.product.prodname_marketplace %} exibirá uma prévia do seu logotipo e do seu cartão de recurso. +#### Guidelines for logos -#### Diretrizes para logotipos +You must upload a custom image for the logo. For the badge, choose a background color. -Você deve enviar uma imagem personalizada para o logotipo. Escolha uma cor de fundo para o selo. +- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published. +- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center. +- For best results, upload a logo image with a transparent background. +- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image. +- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens. -- Faça upload de uma imagem do logotipo com, pelo menos, 200 pixels x 200 pixels para que seu logotipo não tenha que ser dimensionado quando a sua listagem for publicada. -- Os logotipos serão cortados em um quadrado. Recomendamos fazer o upload de um arquivo de imagem quadrada com seu logotipo no centro. -- Para obter o melhor resultado, faça o upload de uma imagem de logotipo com um fundo transparente. -- Para dar a aparência de um selo perfeito, escolha uma cor de fundo para o selo que corresponda à cor de fundo (ou transparência) da imagem do seu logotipo. -- Evite usar imagens do logotipo com palavras ou texto. Os logotipos com texto não são bem dimensionados em telas pequenas. +#### Guidelines for feature cards -#### Diretrizes para cartões de recurso +You must upload a custom background image for the feature card. For the app's name, choose a text color. -Você deve enviar uma imagem de fundo personalizada para o cartão de recurso. Para o nome do aplicativo, escolha uma cor do texto. +- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality. +- Background image measures 965 pixels x 482 pixels (width x height). +- Choose a text color for your app's name that shows up clearly over the background image. -- Use um padrão ou textura na sua imagem de fundo para dar ao seu cartão uma identidade visual e ajudá-lo a destacar-se com relação ao fundo escuro da página inicial do {% data variables.product.prodname_marketplace %}. Os cartões de recursos devem capturar a personalidade da sua marca. -- A iImagem de fundo mede 965 pixels x 482 pixels (largura x altura). -- Escolha uma cor de texto para o nome do aplicativo que aparece claramente sobre a imagem de fundo. +## Listing details -## Detalhes da listagem +To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description." -Para acessar a página inicial do seu aplicativo, clique no nome do aplicativo na página inicial ou na página de categoria do {% data variables.product.prodname_marketplace %}. A página de destino exibe uma descrição mais longa do aplicativo, que inclui duas partes: uma "Descrição introdutória" e uma "Descrição detalhada". +Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page. -A sua "Descrição introdutória" é exibida no topo da página inicial {% data variables.product.prodname_marketplace %} do seu aplicativo. +![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png) -![Descrição introdutória do {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_intro_description.png) +Clicking **Read more...**, displays the "Detailed description." -Clicar em **Ler mais...**, exibirá a "Descrição detalhada". +![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png) -![Descrição detalhada do {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_detailed_description.png) +Follow these guidelines for writing these descriptions. -Siga estas instruções para escrever estas descrições. +### Length -### Comprimento +We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly. -Recomendamos escrever um resumo de alto nível de 1 a 2 frases com 150 a 250 caracteres no campo obrigatório de "Descrição introdutória" ao [listar o seu aplicativo](/marketplace/listing-on-github-marketplace/). Embora seja permitido o uso de mais caracteres, os resumos concisos são mais fáceis de ler e entender pelos clientes rapidamente. +You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description. -Você pode adicionar mais informações ao campo opcional "Descrição detalhada". Você verá esta descrição ao clicar em **Leia mais...**, abaixo da descrição introdutória na página inicial do seu aplicativo. Uma descrição detalhada consiste de 3 a 5 [propostas de valor](https://en.wikipedia.org/wiki/Value_proposition), com 1 a 2 frases que descrevem cada uma. Você pode usar até 1.000 caracteres para essa descrição. +### Content -### Conteúdo +- Always begin introductory descriptions with your app's name. -- Sempre comece descrições introdutórias com o nome do seu aplicativo. +- Always write descriptions and value propositions using the active voice. -- Sempre escreva as descrições e as propostas de valores usando a voz ativa. +### Formatting -### Formatação +- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns. -- Sempre use as letras maiúsculas adequadamente nas frases dos títulos para as propostas de valor. Use maiúscula somente para a primeira letra e para substantivos próprios. +- Use periods in your descriptions. Avoid exclamation marks. -- Use pontos nas suas descrições. Evite pontos de exclamação. +- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence. -- Não use pontuação no final dos títulos da sua proposição de valor. Títulos de proposição de valor não devem incluir frases completas,e não devem incluir mais de uma frase. +- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example: -- Para cada proposta de valor, inclua um título seguido de um parágrafo de descrição. Forme o título como um [cabeçalho de nível 3](/articles/basic-writing-and-formatting-syntax/#headings) usando Markdown. Por exemplo: + ### Learn the skills you need + GitHub Learning Lab can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more. - ### Aprenda as habilidades de que você precisa +- Only capitalize proper nouns. - O GitHub Learning Lab pode ajudá-lo a aprender como usar o GitHub, comunicar-se de modo mais efetivo com o Markdown, gerenciar conflitos de merge, entre outros. +- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. -- Use maiúscula apenas para os substantivos próprios. +- Avoid referring to the GitHub community as "users." -- Use sempre a [vírgula em série](https://en.wikipedia.org/wiki/Serial_comma) nas listas. + **DO:** Create issues automatically for people in your organization -- Evite referir-se à comunidade do GitHub como "usuários". + **DON'T:** Create issues automatically for an organization's users - **RECOMENDADO:** Crie problemas automaticamente para pessoas da sua organização +- Avoid acronyms unless they’re well established (such as API). - **NÃO RECOMENDADO:** Crie problemas automaticamente para usuários de uma organização +## Product screenshots -- Evite acrônimos, a menos que estejam conhecidos (como, por exemplo, API). +You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page. -## Capturas de tela dos produtos +### Guidelines for screenshots -Você pode enviar até cinco imagens de captura de tela do seu aplicativo para ser exibidas na página inicial do seu aplicativo. Adicione uma legenda opcional para cada captura de tela para fornecer contexto. Após enviar suas capturas de tela, você pode arrastá-las para a ordem que você deseja que sejam exibidas na página inicial. +- Images must be of high resolution (at least 1200px wide). +- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next. +- Show as much of the user interface as possible so people can see what your app does. +- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes. +- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots. +- Captions are most effective when they are short and snappy. -### Diretrizes para capturas de tela - -- As imagens devem ser de alta resolução (pelo menos 1200 px de largura). -- Todas as imagens devem ter a mesma altura e largura (proporção de aspecto) para evitar pular páginas quando as pessoas clicam de uma imagem para a seguinte. -- Mostre a maior quantidade possível de interface de usuário para que as pessoas possam ver o que seu aplicativo faz. -- Ao capturar telas do seu app em um navegador, inclua apenas o conteúdo na janela de exibição. Evite incluir a barra de endereço, barra de título ou ícones da barra de ferramentas, que não são bem dimensionados para tamanhos de tela menores. -- O GitHub exibe as capturas de tela das quais você fizer o upload em uma caixa na página inicial do seu aplicativo. Portanto, você não precisa adicionar caixas ou bordas ao redor de suas capturas de tela. -- As legendas são mais eficazes quando são curtas e ágeis. - -![Imagem de captura de tela do GitHub Marketplace](/assets/images/marketplace/marketplace-screenshots.png) +![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png) diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md index 232e58e0e77d..999f345c3d0e 100644 --- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -1,6 +1,6 @@ --- -title: Planos de preços para aplicativos do GitHub Marketplace -intro: 'Os planos de preços permitem que você forneça ao seu aplicativo diferentes níveis de serviço ou recursos. Você pode oferecer até 10 planos de preços na sua listagem do {% data variables.product.prodname_marketplace %}.' +title: Pricing plans for GitHub Marketplace apps +intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.' redirect_from: - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans/ - /marketplace/selling-your-app/github-marketplace-pricing-plans @@ -10,51 +10,50 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Preços de planos para os aplicativos +shortTitle: Pricing plans for apps --- +{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to apps published by verified publishers. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." -Os planos de preços de {% data variables.product.prodname_marketplace %} podem ser grátis, fixos ou por unidade. Os preços são definidos, exibidos e processados em dólares. Os planos pagos são restritos a aplicativos publicados por editores verificados. Para obter mais informações sobre como se tornar um editor verificado, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". +Customers purchase your app using a payment method attached to their account on {% data variables.product.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Customers purchase your app using a payment method attached to their account on {% data variables.product.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. Você não precisa escrever um código para realizar transações de cobrança, mas deverá gerenciar eventos da API de {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed. -Se o aplicativo que você está listando no {% data variables.product.prodname_marketplace %} tiver várias opções de plano, você poderá definir os planos de preços correspondentes. Por exemplo, se o app tiver duas opções de plano, um plano de código aberto e um plano profissional, você poderá criar um plano de preços grátis para o seu plano de código aberto e um plano de preço fixo para o seu plano profissional. Cada listagem do {% data variables.product.prodname_marketplace %} deve ter um preço anual e um preço mensal para todos os planos listados. - -Para obter mais informações sobre como criar um plano de preços, consulte "[Configurar um plano de preços da listagem de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". +For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." {% data reusables.marketplace.free-plan-note %} -## Tipos de planos de preços +## Types of pricing plans -### Planos de preços grátis +### Free pricing plans {% data reusables.marketplace.free-apps-encouraged %} -Planos grátis são completamente grátis para os usuários. Se você configurar um plano de preços grátis, você não poderá cobrar os usuários que escolherem o plano de preços grátis para o uso do seu aplicativo. Você pode criar planos grátis e pagos para a sua listagem. +Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. -Todos os aplicativos precisam gerenciar eventos para novas compras e cancelamentos. Os aplicativos que só têm planos grátis não precisam gerenciar eventos para testes, atualizações e downgrades grátis. Para mais informações, consulte: "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Se você adicionar um plano pago a um aplicativo que já esteja listado em {% data variables.product.prodname_marketplace %} como um serviço grátis, você precisará solicitar verificação para o aplicativo e passar pela integração financeira. +If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding. -### Planos de preços pagos +### Paid pricing plans -Existem dois tipos de planos de preços pagos: +There are two types of paid pricing plan: -- Os planos de preços fixos cobram uma taxa definida mensalmente e anualmente. +- Flat rate pricing plans charge a set fee on a monthly and yearly basis. -- Os planos de preços por unidade cobram uma taxa definida mensalmente ou anualmente para uma unidade que você especificar. Uma "unidade" pode ser qualquer coisa que você deseje (por exemplo, um usuário, estação ou pessoa). +- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). -Você também pode oferecer testes grátis. Eles fornecem gratuitamente testes de 14 dias referentes aos aplicativos OAuth ou GitHub para os clientes. Ao configurar um plano de preços do Marketplace você poderá selecionar a opção de fornecer um teste gratuito para planos de taxa fixa ou por unidade de preços +You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans. -## Testes grátis +## Free trials -Os clientes podem iniciar uma avaliação gratuita para qualquer plano pago de um anúncio do Marketplace que inclui testes grátis. No entanto, os clientes não podem criar mais de um teste grátis por produto no marketplace. +Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product. -Os testes gratuitos têm uma duração fixa de 14 dias. Os clientes são notificados 4 dias antes do final do período de teste (no 11o dia do teste grátis) de que seu plano será atualizado. No final do teste grátis, os clientes serão inscritos automaticamente no plano que estão testando, caso não efetuem o cancelamento. +Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel. -Para mais informações, consulte: "[Como gerenciar novas compras e testes grátis](/developers/github-marketplace/handling-new-purchases-and-free-trials/)". +For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)." {% note %} -**Observação:** O GitHub espera que você exclua quaisquer dados privados do cliente no prazo de 30 dias após o cancelamento do teste, a contar do recebimento do evento de cancelamento. +**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event. {% endnote %} diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md index 6448f9759d4e..78b6642b52ae 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -73,7 +73,7 @@ SSH URLs provide access to a Git repository via SSH, a secure protocol. To use t When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)." -{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %} +{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} {% tip %} diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md index 895f30fd9d70..2f1cf8bcf2aa 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md @@ -13,7 +13,7 @@ shortTitle: GitHub AE trial You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region. - **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance. -- **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at https://portal.azure.com. This is used to deploy the {% data variables.product.prodname_ghe_managed %} account. +- **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account. ## Setting up your trial of {% data variables.product.prodname_ghe_managed %} diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md index 8c44c1a59ad6..cfe1727e1233 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md @@ -23,7 +23,7 @@ shortTitle: Enterprise Cloud trial You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page. -{% data reusables.saml.saml-accounts %} For more information, see "About identity and access management with SAML single sign-on." +{% data reusables.saml.saml-accounts %} For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% data reusables.products.which-product-to-use %} diff --git a/translations/pt-BR/content/github/index.md b/translations/pt-BR/content/github/index.md index b8c5e0a1660b..25aee3d9465c 100644 --- a/translations/pt-BR/content/github/index.md +++ b/translations/pt-BR/content/github/index.md @@ -1,9 +1,9 @@ --- title: GitHub redirect_from: - - /articles/ - - /common-issues-and-questions/ - - /troubleshooting-common-issues/ + - /articles + - /common-issues-and-questions + - /troubleshooting-common-issues intro: 'Documentation, guides, and help topics for software developers, designers, and project managers. Covers using Git, pull requests, issues, wikis, gists, and everything you need to make the most of GitHub for development.' versions: fpt: '*' diff --git a/translations/pt-BR/content/github/writing-on-github/index.md b/translations/pt-BR/content/github/writing-on-github/index.md index cb27c2c0c864..e53ef2f32bda 100644 --- a/translations/pt-BR/content/github/writing-on-github/index.md +++ b/translations/pt-BR/content/github/writing-on-github/index.md @@ -1,11 +1,11 @@ --- -title: Gravar no GitHub +title: Writing on GitHub redirect_from: - - /categories/88/articles/ - - /articles/github-flavored-markdown/ - - /articles/writing-on-github/ + - /categories/88/articles + - /articles/github-flavored-markdown + - /articles/writing-on-github - /categories/writing-on-github -intro: 'Você pode estruturar as informações compartilhadas em {% data variables.product.product_name %} com várias opções de formatação.' +intro: 'You can structure the information shared on {% data variables.product.product_name %} with various formatting options.' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md index ac48d85531e0..84fdefa98d04 100644 --- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -1,28 +1,26 @@ --- -title: Sobre a autenticação de dois fatores e o SAML de logon único -intro: Os administradores da organização podem habilitar o SAML de logon único e a autenticação de dois fatores para adicionar medidas extras de autenticação para os integrantes da organização. -product: '{% data reusables.gated-features.saml-sso %}' +title: About two-factor authentication and SAML single sign-on +intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members. redirect_from: - /articles/about-two-factor-authentication-and-saml-single-sign-on - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: 2FA & Logon único SAML +shortTitle: 2FA & SAML single sign-on --- -A autenticação de dois fatores (2FA, Two-Factor Authentication) fornece autenticação básica para integrantes da organização. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.product.product_location %} could be compromised. Para obter mais informações sobre a 2FA, consulte "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)". +Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.product.product_location %} could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)." -Para adicionar medidas extras de autenticação, os administradores da organização também podem [habilitar o SAML de logon único (SSO, Single Sign-On)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para que os integrantes da organização usem o logon único para acessar uma organização. Para obter mais informações sobre o SAML SSO, consulte "[Sobre o gerenciamento de identidade e acesso com SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)". +To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)." -Se a 2FA e o SAML SSO forem habilitados, os integrantes da organização deverão fazer o seguinte: +If both 2FA and SAML SSO are enabled, organization members must do the following: - Use 2FA to log in to their account on {% data variables.product.product_location %} -- Usar o logon único para acessar a organização -- Usar um token autorizado para acesso por API ou Git e usar logon único para autorizar o token +- Use single sign-on to access the organization +- Use an authorized token for API or Git access and use single sign-on to authorize the token -## Leia mais +## Further reading -- "[Aplicar SAML de logon único para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)" +- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md index a6588022b2f2..3b715c25defa 100644 --- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md @@ -1,11 +1,10 @@ --- -title: Conceder acesso à sua organização com logon único SAML -intro: 'Administradores de organizações podem conceder acesso à organização com logon único SAML. O acesso pode ser concedido a integrantes de organizações, bots e contas de serviço.' +title: Granting access to your organization with SAML single sign-on +intro: 'Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.' redirect_from: - /articles/granting-access-to-your-organization-with-saml-single-sign-on - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on versions: - fpt: '*' ghec: '*' topics: - Organizations @@ -14,6 +13,6 @@ children: - /managing-bots-and-service-accounts-with-saml-single-sign-on - /viewing-and-managing-a-members-saml-access-to-your-organization - /about-two-factor-authentication-and-saml-single-sign-on -shortTitle: Conceder acesso com SAML +shortTitle: Grant access with SAML --- diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md index 6f5aaa33be8a..0b6a23458841 100644 --- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -1,27 +1,25 @@ --- -title: Gerenciar bots e contas de serviço com logon único SAML -intro: Organizações que habilitaram logon único SAML podem manter o acesso para bots e contas de serviço. -product: '{% data reusables.gated-features.saml-sso %}' +title: Managing bots and service accounts with SAML single sign-on +intro: Organizations that have enabled SAML single sign-on can retain access for bots and service accounts. redirect_from: - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Gerenciar bots & contas de serviço +shortTitle: Manage bots & service accounts --- -Para manter o acesso para bots e contas de serviço, os administradores da organização podem [habilitar](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), mas **não** [executar](/articles/enforcing-saml-single-sign-on-for-your-organization) o logon único SAML na organização. Se você precisa executar logon único SAML na organização, é possível criar uma identidade externa para o bot ou conta de serviço com seu provedor de identidade (IdP). +To retain access for bots and service accounts, organization administrators can [enable](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), but **not** [enforce](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP). {% warning %} -**Observação:** se você aplicar logon único SAML na sua organização e **não** tiver configurado identidades externas para bots e contas de serviço com o IdP, eles serão removidos da organização. +**Note:** If you enforce SAML single sign-on for your organization and **do not** have external identities set up for bots and service accounts with your IdP, they will be removed from your organization. {% endwarning %} -## Leia mais +## Further reading -- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index 7a548cf40862..8845f4c7cb1d 100644 --- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -1,39 +1,37 @@ --- -title: Visualizar e gerenciar o acesso SAML de um integrante à sua organização -intro: 'Você pode visualizar e revogar a identidade vinculada de um integrante da organização, as sessões ativas e as credenciais autorizadas.' +title: Viewing and managing a member's SAML access to your organization +intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.' permissions: Organization owners can view and manage a member's SAML access to an organization. -product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/viewing-and-revoking-organization-members-authorized-access-tokens - /github/setting-up-and-managing-organizations-and-teams/viewing-and-revoking-organization-members-authorized-access-tokens - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Gerenciar acesso SAML +shortTitle: Manage SAML access --- -## Sobre o acesso SAML à sua organização +## About SAML access to your organization -When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.product_location %}. Para acessar os recursos da sua organização no {% data variables.product.product_name %}, o integrante deverá ter uma sessão SAML ativa em seu navegador. Para acessar os recursos da sua organização usando a API ou o Git, o integrante deve usar um token de acesso pessoal ou chave SSH que o integrante autorizou a usar com a sua organização. +When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.product_location %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a personal access token or SSH key that the member has authorized for use with your organization. -Você pode visualizar e revogar a identidade vinculada de cada integrante, as sessões ativas e as credenciais autorizadas na mesma página. +You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page. -## Visualizar e revogar uma identidade vinculada +## Viewing and revoking a linked identity -{% data reusables.saml.about-linked-identities %} +{% data reusables.saml.about-linked-identities %} -Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". +When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% warning %} -**Aviso:** Para organizações que usam SCIM: -- A revogação de uma identidade de usuário vinculada em {% data variables.product.product_name %} também removerá os metadados SAML e SCIM. Como resultado, o provedor de identidade não poderá sincronizar ou desprovisionar a identidade do usuário vinculada. -- Um administrador deverá revogar uma identidade vinculada por meio do provedor de identidade. -- Para revogar uma identidade vinculada e vincular uma conta diferente por meio do provedor de identidade, um administrador pode remover e reatribuir o usuário ao aplicativo de {% data variables.product.product_name %}. Para obter mais informações, consulte a documentação do seu provedor de identidade. +**Warning:** For organizations using SCIM: +- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. +- An admin must revoke a linked identity through the identity provider. +- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation. {% endwarning %} @@ -49,7 +47,7 @@ Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informaç {% data reusables.saml.revoke-sso-identity %} {% data reusables.saml.confirm-revoke-identity %} -## Visualizar e revogar uma sessão ativa de SAML +## Viewing and revoking an active SAML session {% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} @@ -59,7 +57,7 @@ Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informaç {% data reusables.saml.view-saml-sessions %} {% data reusables.saml.revoke-saml-session %} -## Visualizar e revogar credenciais autorizadas +## Viewing and revoking authorized credentials {% data reusables.saml.about-authorized-credentials %} @@ -72,7 +70,7 @@ Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informaç {% data reusables.saml.revoke-authorized-credentials %} {% data reusables.saml.confirm-revoke-credentials %} -## Leia mais +## Further reading - "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %} - "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %} diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md index f222e7b6c47f..08a2b3eb702e 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -56,7 +56,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. | [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} | [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} -| [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion fpt or ghec %} +| [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion fpt or ghes or ghae or ghec %} | [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} | [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% ifversion fpt or ghes > 3.0 or ghec %} @@ -423,12 +423,12 @@ For more information, see "[Managing the publication of {% data variables.produc | `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization). | `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% ifversion fpt or ghes or ghec %} | `create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."{% endif %} {% ifversion fpt or ghec %} -| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization. -| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %} +| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %} +| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %}{% endif %} | `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} | `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} -| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization. -| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %} +| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %} +| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %}{% endif %} | `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} | `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} | `invite_member` | Triggered when [a new user was invited to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). @@ -440,7 +440,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. |{% endif %} | `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization.| | `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. | -| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." {% ifversion fpt or ghec %} +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." {% ifversion ghec %} | `revoke_external_identity` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." | `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." {% endif %} | `runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." @@ -464,7 +464,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated. | `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %} -{% ifversion fpt or ghec %} +{% ifversion ghec %} ### `org_credential_authorization` category actions | Action | Description diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md index 6907db3ad919..c08a2a1e4e42 100644 --- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -1,6 +1,6 @@ --- -title: Posso criar contas para as pessoas na minha organização? -intro: 'Embora você possa adicionar usuários a uma organização que criou, não é possível criar contas de usuário pessoais em nome de outra pessoa.' +title: Can I create accounts for people in my organization? +intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.' redirect_from: - /articles/can-i-create-accounts-for-those-in-my-organization/ - /articles/can-i-create-accounts-for-people-in-my-organization @@ -11,7 +11,7 @@ versions: topics: - Organizations - Teams -shortTitle: Criar contas para pessoas +shortTitle: Create accounts for people --- ## About user accounts @@ -19,11 +19,13 @@ shortTitle: Criar contas para pessoas Because you access an organization by logging in to a user account, each of your team members needs to create their own user account. After you have usernames for each person you'd like to add to your organization, you can add the users to teams. {% ifversion fpt or ghec %} -If you need greater control over the user accounts of your organization members, consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} +{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can use SAML single sign-on to centrally manage the access that user accounts have to the organization's resources through an identity provider (IdP). For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} + +You can also consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} {% endif %} -## Adicionar usuários à organização +## Adding users to your organization 1. Provide each person instructions to [create a user account](/articles/signing-up-for-a-new-github-account). -2. Peça o nome de usuário de cada pessoa a quem deseja conceder associação à organização. -3. [Convide as novas contas pessoais para ingressar](/articles/inviting-users-to-join-your-organization) na sua organização. Use as [funções da organização](/articles/permission-levels-for-an-organization) e [permissões de repositório](/articles/repository-permission-levels-for-an-organization) para limitar o acesso de cada conta. +2. Ask for the username of each person you want to give organization membership to. +3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account. diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md index bb722710d329..fac88da5efe1 100644 --- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -1,6 +1,6 @@ --- -title: Convidar usuários para sua organização -intro: 'É possível convidar qualquer pessoa para integrar sua organização usando o nome de usuário {% data variables.product.product_name %} ou endereço de e-mail dela.' +title: Inviting users to join your organization +intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.product.product_location %}.' permissions: Organization owners can invite users to join an organization. redirect_from: - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ @@ -12,16 +12,18 @@ versions: topics: - Organizations - Teams -shortTitle: Convidar usuários para participar +shortTitle: Invite users to join --- ## About organization invitations -Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)". +If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-scim %} -Se a sua organização exige que os integrantes usem a autenticação de dois fatores, os usuários que você convidar deverão ativar a autenticação de dois fatores antes de aceitar o convite. Para mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" e[Proteger a sua conta com a autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". +If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)." + +{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.prodname_dotcom_the_website %} through an identity provider (IdP). For more information, see "[About SCIM](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} ## Inviting a user to join your organization @@ -36,5 +38,5 @@ Se a sua organização exige que os integrantes usem a autenticação de dois fa {% data reusables.organizations.send-invitation %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} -## Leia mais -- "[Adicionar integrantes da organização a uma equipe](/articles/adding-organization-members-to-a-team)" +## Further reading +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md index e216fcf9c809..9fd78a873542 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -1,6 +1,6 @@ --- -title: Renomear uma organização -intro: 'Se seu projeto ou sua empresa mudarem de nome, atualize o nome da organização.' +title: Renaming an organization +intro: 'If your project or company has changed names, you can update the name of your organization to match.' redirect_from: - /articles/what-happens-when-i-change-my-organization-s-name/ - /articles/renaming-an-organization @@ -17,34 +17,35 @@ topics: {% tip %} -**Dica:** somente proprietários da organização podem renomear a organização. {% data reusables.organizations.new-org-permissions-more-info %} +**Tip:** Only organization owners can rename an organization. {% data reusables.organizations.new-org-permissions-more-info %} {% endtip %} -## O que acontece quando eu altero o nome da organização? +## What happens when I change my organization's name? -Depois que você altera o nome da organização, o nome antigo da organização fica disponível para ser usado por outra pessoa. Quando você altera o nome da organização, a maioria das referências ao repositórios no nome antigo da organização é alterada automaticamente para o novo nome. No entanto, alguns links para seu perfil não são redirecionados automaticamente. +After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect. -### Alterações que ocorrem automaticamente +### Changes that occur automatically -- O {% data variables.product.prodname_dotcom %} redireciona automaticamente as referências aos seus repositórios. Os links da web para os **repositórios** da organização continuarão a funcionar. Esse processo pode demorar alguns minutos após a alteração. -- Você pode continuar a fazer push dos repositórios locais para a URL de controle do remote antigo sem atualizá-lo. No entanto, recomendamos que você atualize todas as URLs do repositório remoto depois de alterar o nome da organização. Como o nome antigo da organização ficou disponível para uso por qualquer pessoa após a alteração, o proprietário da nova organização pode criar repositórios que sobrescrevem as entradas de redirecionamento para o seu repositório. Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". -- Os Git commits anteriores também serão atribuídos corretamente ao usuários na sua organização. +- {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories. Web links to your organization's existing **repositories** will continue to work. This can take a few minutes to complete after you initiate the change. +- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +- Previous Git commits will also be correctly attributed to users within your organization. -### Alterações que não são automáticas +### Changes that aren't automatic -Depois de alterar o nome da organização: -- Os links para a página de perfil da organização anterior, como `https://{% data variables.command_line.backticks %}/previousorgname`, retornarão um erro 404. Recomendamos que você atualize os links para a organização de outros sites{% ifversion fpt or ghec %}, como os perfis do LinkedIn ou do Twitter{% endif %}. -- As solicitações de API que usam o nome antigo da organização retornarão um erro 404. Recomendamos que você atualize o nome da organização nas solicitações de API. -- Não há redirecionamentos de [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) automática para equipes que usam o nome da organização antiga.{% ifversion fpt or ghec %} -- Se o SAML logon único (SSO) estiver habilitado para a organização, você deverá atualizar o nome da organização no aplicativo para {% data variables.product.prodname_ghe_cloud %} no seu provedor de identidade (IdP). Se você não atualizar o nome da organização no seu IdP, os integrantes da organização não poderão mais efetuar a autenticação com seu IdP para acessar os recursos da organização. Para obter mais informações, consulte "[Conectando o seu provedor de identidade à sua organização](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} +After changing your organization's name: +- Links to your previous organization profile page, such as `https://{% data variables.command_line.backticks %}/previousorgname`, will return a 404 error. We recommend you update links to your organization from other sites{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profiles{% endif %}. +- API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests. +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% ifversion ghec %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} -## Alterar o nome da organização +## Changing your organization's name {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -4. Perto da parte inferior da página de configuração, em "Rename organization" (Renomear organização), clique em **Rename Organization** (Renomear organização). ![Botão Rename organization (Renomear organização)](/assets/images/help/settings/settings-rename-organization.png) +4. Near the bottom of the settings page, under "Rename organization", click **Rename Organization**. + ![Rename organization button](/assets/images/help/settings/settings-rename-organization.png) -## Leia mais +## Further reading -* "[Por que meus commits estão vinculados ao usuário errado?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)" +* "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)" diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index fcabee5b9e6e..58b849aac46a 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -16,7 +16,6 @@ topics: - Teams shortTitle: Roles in an organization --- - ## About roles {% data reusables.organizations.about-roles %} @@ -31,14 +30,14 @@ Organization-level roles are sets of permissions that can be assigned to individ You can assign individuals or teams to a variety of organization-level roles to control your members' access to your organization and its resources. For more details about the individual permissions included in each role, see "[Permissions for organization roles](#permissions-for-organization-roles)." ### Organization owners -Organization owners have complete administrative access to your organization. Essa função deve ser limitada a não menos que duas pessoas na sua organização. Para obter mais informações, consulte "[Manter a continuidade da propriedade para a sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)". +Organization owners have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." -### Integrantes da organização +### Organization members The default, non-administrative role for people in an organization is the organization member. By default, organization members have a number of permissions, including the ability to create repositories and project boards. {% ifversion fpt or ghec %} -### Gerentes de cobrança -Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. Para obter mais informações, consulte "[Adicionar um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." +### Billing managers +Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." {% endif %} @@ -51,179 +50,174 @@ Billing managers are users who can manage the billing settings for your organiza If your organization has a security team, you can use the security manager role to give members of the team the least access they need to the organization. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." {% endif %} -### Gerentes de {% data variables.product.prodname_github_app %} -Por padrão, somente proprietários da organização podem gerenciar as configurações de {% data variables.product.prodname_github_apps %} pertencentes a uma organização. Para permitir que usuários adicionais gerenciem {% data variables.product.prodname_github_apps %} pertencente a uma organização, um proprietário pode conceder a eles permissões de gerentes de {% data variables.product.prodname_github_app %}. +### {% data variables.product.prodname_github_app %} managers +By default, only organization owners can manage the settings of {% data variables.product.prodname_github_apps %} owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_apps %} owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions. -Ao nomear um usuário como um gerente de {% data variables.product.prodname_github_app %} na sua organização, você pode conceder a eles acesso para gerenciar as configurações de alguns ou todos os {% data variables.product.prodname_github_apps %} pertencentes à organização. Para obter mais informações, consulte: +When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_apps %} owned by the organization. For more information, see: -- "[Adicionar gerentes de aplicativos GitHub na organização](/articles/adding-github-app-managers-in-your-organization)" -- "[Remover gerentes de aplicativos GitHub de sua organização](/articles/removing-github-app-managers-from-your-organization)" +- "[Adding GitHub App managers in your organization](/articles/adding-github-app-managers-in-your-organization)" +- "[Removing GitHub App managers from your organization](/articles/removing-github-app-managers-from-your-organization)" -### Colaboradores externos -Para manter os dados da sua organização seguros, permitindo o acesso aos repositórios, é possível adicionar *colaboradores externos*. {% data reusables.organizations.outside_collaborators_description %} +### Outside collaborators +To keep your organization's data secure while allowing access to repositories, you can add *outside collaborators*. {% data reusables.organizations.outside_collaborators_description %} ## Permissions for organization roles {% ifversion fpt %} -Algumas das funcionalidades listadas abaixo estão limitadas a organizações que usam {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} {% ifversion fpt or ghec %} -| Organization permission | Proprietários | Integrantes | Gerentes de cobrança | Security managers | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------------:|:-----------:|:--------------------:|:-----------------:| -| Criar repositórios (consulte "[Restringir a criação de repositórios na organização](/articles/restricting-repository-creation-in-your-organization)" para detalhes) | **X** | **X** | | **X** | -| Visualizar e editar informações de cobrança | **X** | | **X** | | -| Convidar pessoas para integrar a organização | **X** | | | | -| Editar e cancelar convites para integrar a organização | **X** | | | | -| Remover integrantes da organização | **X** | | | | -| Restabelecer ex-integrantes da organização | **X** | | | | -| Adicionar e remover pessoas de **todas as equipes** | **X** | | | | -| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | | -| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | | -| Definir lembretes agendados (consulte "[Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | | -| Adicionar colaboradores em **todos os repositórios** | **X** | | | | -| Acessar o log de auditoria da organização | **X** | | | | -| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" para detalhes) | **X** | | | | -| Verificar os domínios da organização (consulte "[Verificar o domínio da sua organização](/articles/verifying-your-organization-s-domain)" para detalhes) | **X** | | | | -| Restringir as notificações de e-mail a domínios verificados ou aprovados (consulte "[Restringir notificações de e-mail para a sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para obter informações) | **X** | | | | -| Excluir **todas as equipes** | **X** | | | | -| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | | -| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | | **X** | -| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | | -| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | | **X** | -| Ver todos os integrantes e equipes da organização | **X** | **X** | | **X** | -| @mencionar qualquer equipe visível | **X** | **X** | | **X** | -| Poder se tornar um *mantenedor de equipe* | **X** | **X** | | **X** | -| Visualizar as informações da organização (consulte "[Visualizar informações da organização](/articles/viewing-insights-for-your-organization)" para detalhes) | **X** | **X** | | **X** | -| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | **X** | | **X** | -| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | | | | -| Editar e excluir discussões de equipe em **todas as equipes** (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" para detalhes) | **X** | | | | -| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | | **X** | -| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | | | -| Gerenciar a visualização de informações de dependência da organização (consulte "[Alterar a visibilidade das informações de dependência da organização](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para detalhes) | **X** | | | | -| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | | | -| Patrocinar contas e gerenciar os patrocínios da organização (Consulte "[Patrocinar contribuidoresde código aberto](/sponsors/sponsoring-open-source-contributors)" para mais detalhes) | **X** | | **X** | **X** | -| Gerenciar atualizações de e-mail de contas patrocinadas (consulte "[Gerenciar atualizações de contas que a sua organização patrocina](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" para obter detalhes) | **X** | | | | -| Atribuir seus patrocínios a outra organização (consulte "[Atribuir de patrocínios à sua organização](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" para obter mais detalhes) | **X** | | | | -| Gerencie a publicação dos sites de {% data variables.product.prodname_pages %} a partir dos repositórios na organização (consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)para obter mais informações) | **X** | | | | -| Gerenciar as configurações de segurança e análise (consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" para obter mais informações) | **X** | | | **X** | -| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | | **X** | -| Habilitar e executar [logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | -| [Gerenciar o acesso de SAML de um usuário à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | -| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | | | -| Transferir repósitórios | **X** | | | | -| Comprar, instalar, gerenciar cobranças e cancelar aplicativos do {% data variables.product.prodname_marketplace %} | **X** | | | | -| Listar aplicativos no {% data variables.product.prodname_marketplace %} | **X** | | | | -| Recebe [{% data variables.product.prodname_dependabot_alerts %} sobre dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos os repositórios de uma organização | **X** | | | **X** | -| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | **X** | -| [Gerenciar a política de bifurcação](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | | -| [Limitar a atividade em repositórios públicos na organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | | -| Pull (read) *all repositories* in the organization | **X** | | | **X** | -| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | | -| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | | -| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | -| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | | -| Gerenciar o nome do branch-padrão (consulte "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | | -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | | -| Habilitar sincronização de equipes (consulte "[Gerenciar sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" para obter informações) | **X** | | | | +| Organization permission | Owners | Members | Billing managers | Security managers | +|:--------------------|:------:|:-------:|:----------------:|:----------------:| +| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **X** | **X** | | **X** | +| View and edit billing information | **X** | | **X** | | +| Invite people to join the organization | **X** | | | | +| Edit and cancel invitations to join the organization | **X** | | | | +| Remove members from the organization | **X** | | | | +| Reinstate former members to the organization | **X** | | | | +| Add and remove people from **all teams** | **X** | | | | +| Promote organization members to *team maintainer* | **X** | | | | +| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | | +| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | | +| Add collaborators to **all repositories** | **X** | | | | +| Access the organization audit log | **X** | | | | +| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | | | +| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | | | +| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | | | | +| Delete **all teams** | **X** | | | | +| Delete the organization account, including all repositories | **X** | | | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | | **X** | +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | **X** | +| See all organization members and teams | **X** | **X** | | **X** | +| @mention any visible team | **X** | **X** | | **X** | +| Can be made a *team maintainer* | **X** | **X** | | **X** | +| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | **X** | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | **X** | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | | +| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" for details) | **X** | | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | | **X** | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | | +| Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" for details) | **X** | | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | | | +| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/sponsors/sponsoring-open-source-contributors)" for details) | **X** | | **X** | **X** | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | | +| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | | **X** | +| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | | **X** |{% ifversion ghec %} +| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | +| [Manage a user's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | | |{% endif %} +| Transfer repositories | **X** | | | | +| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | | | +| List apps in {% data variables.product.prodname_marketplace %} | **X** | | | | +| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **X** | | | **X** | +| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | **X** | +| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | | +| Pull (read) *all repositories* in the organization | **X** | | | **X** | +| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | +| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | | +| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | | +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | |{% ifversion ghec %} +| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** | | | |{% endif %} {% elsif ghes > 3.2 or ghae-issue-4999 %} -| Ação da organização | Proprietários | Integrantes | Security managers | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------------:|:-----------:|:--------------------------------------------:| -| Convidar pessoas para integrar a organização | **X** | | | -| Editar e cancelar convites para integrar a organização | **X** | | | -| Remover integrantes da organização | **X** | | | | -| Restabelecer ex-integrantes da organização | **X** | | | | -| Adicionar e remover pessoas de **todas as equipes** | **X** | | | -| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | -| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | -| Adicionar colaboradores em **todos os repositórios** | **X** | | | -| Acessar o log de auditoria da organização | **X** | | | -| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" para detalhes) | **X** | | |{% ifversion ghes > 3.1 %} -| Verificar os domínios da organização (consulte "[Verificar o domínio da sua organização](/articles/verifying-your-organization-s-domain)" para detalhes) | **X** | | | -| Restringir as notificações de e-mail a domínios verificados ou aprovados (consulte "[Restringir notificações de e-mail para a sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para obter informações) | **X** | | -{% endif %} -| Excluir **todas as equipes** | **X** | | | -| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | -| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | **X** | -| Ver todos os integrantes e equipes da organização | **X** | **X** | **X** | -| @mencionar qualquer equipe visível | **X** | **X** | **X** | -| Poder se tornar um *mantenedor de equipe* | **X** | **X** | **X** | -| Transferir repósitórios | **X** | | | -| Gerenciar as configurações de segurança e análise (consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" para obter mais informações) | **X** | | **X** |{% ifversion ghes > 3.1 %} -| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %} -| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** -{% endif %} -| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | | -| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | **X** | -| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | **X** | **X** | -| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | | | -| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | | -| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | **X** | -| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | | -| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | |{% ifversion ghes > 3.0 %} -| Gerencie a publicação dos sites de {% data variables.product.prodname_pages %} a partir dos repositórios na organização (consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)para obter mais informações) | **X** | | -{% endif %} -| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Pull (read) *all repositories* in the organization | **X** | | **X** | -| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | -| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | -| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | -| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | +| Organization action | Owners | Members | Security managers | +|:--------------------|:------:|:-------:|:-------:| +| Invite people to join the organization | **X** | | | +| Edit and cancel invitations to join the organization | **X** | | | +| Remove members from the organization | **X** | | | | +| Reinstate former members to the organization | **X** | | | | +| Add and remove people from **all teams** | **X** | | | +| Promote organization members to *team maintainer* | **X** | | | +| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Add collaborators to **all repositories** | **X** | | | +| Access the organization audit log | **X** | | | +| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | |{% ifversion ghes > 3.1 %} +| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | | +| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | | |{% endif %} +| Delete **all teams** | **X** | | | +| Delete the organization account, including all repositories | **X** | | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | **X** | +| See all organization members and teams | **X** | **X** | **X** | +| @mention any visible team | **X** | **X** | **X** | +| Can be made a *team maintainer* | **X** | **X** | **X** | +| Transfer repositories | **X** | | | +| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | **X** |{% ifversion ghes > 3.1 %} +| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %} +| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** |{% endif %} +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | **X** | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | **X** | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | |{% ifversion ghes > 3.0 %} +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | |{% endif %} +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Pull (read) *all repositories* in the organization | **X** | | **X** | +| Push (write) and clone (copy) *all repositories* in the organization | **X** | | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | {% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | | |{% endif %} {% else %} -| Ação da organização | Proprietários | Integrantes | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------------:|:------------------------------:| -| Convidar pessoas para integrar a organização | **X** | | -| Editar e cancelar convites para integrar a organização | **X** | | -| Remover integrantes da organização | **X** | | | -| Restabelecer ex-integrantes da organização | **X** | | | -| Adicionar e remover pessoas de **todas as equipes** | **X** | | -| Promover integrantes da organização a *mantenedor de equipe* | **X** | | -| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** | | -| Adicionar colaboradores em **todos os repositórios** | **X** | | -| Acessar o log de auditoria da organização | **X** | | -| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" para detalhes) | **X** | | |{% ifversion ghes > 3.1 %} -| Verificar os domínios da organização (consulte "[Verificar o domínio da sua organização](/articles/verifying-your-organization-s-domain)" para detalhes) | **X** | | -| Restringir as notificações de e-mail a domínios verificados ou aprovados (consulte "[Restringir notificações de e-mail para a sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para obter informações) | **X** | -{% endif %} -| Excluir **todas as equipes** | **X** | | -| Excluir a conta da organização, inclusive todos os repositórios | **X** | | -| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | -| Ver todos os integrantes e equipes da organização | **X** | **X** | -| @mencionar qualquer equipe visível | **X** | **X** | -| Poder se tornar um *mantenedor de equipe* | **X** | **X** | -| Transferir repósitórios | **X** | | -| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | -| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | | -| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | **X** | | -| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | | | -| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | -| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | **X** | -| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | | -| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | |{% ifversion ghes > 3.0 %} -| Gerencie a publicação dos sites de {% data variables.product.prodname_pages %} a partir dos repositórios na organização (consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)para obter mais informações) | **X** | -{% endif %} -| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | -| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | -| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | -| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | -{% ifversion ghae %}| Gerenciar listas de permissão de IP (consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} +| Organization action | Owners | Members | +|:--------------------|:------:|:-------:| +| Invite people to join the organization | **X** | | +| Edit and cancel invitations to join the organization | **X** | | +| Remove members from the organization | **X** | | | +| Reinstate former members to the organization | **X** | | | +| Add and remove people from **all teams** | **X** | | +| Promote organization members to *team maintainer* | **X** | | +| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** | | +| Add collaborators to **all repositories** | **X** | | +| Access the organization audit log | **X** | | +| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** | | |{% ifversion ghes > 3.1 %} +| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | +| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** | |{% endif %} +| Delete **all teams** | **X** | | +| Delete the organization account, including all repositories | **X** | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | +| See all organization members and teams | **X** | **X** | +| @mention any visible team | **X** | **X** | +| Can be made a *team maintainer* | **X** | **X** | +| Transfer repositories | **X** | | +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | |{% ifversion ghes > 3.0 %} +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | |{% endif %} +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | +{% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} {% endif %} -## Leia mais +## Further reading - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" -- "[Permissões de quadro de projeto para uma organização](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)" +- "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)" diff --git 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 index e95cb9e97218..5839c6e3336c 100644 --- 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 @@ -1,68 +1,64 @@ --- -title: Sobre o gerenciamento de identidade e acesso com o SAML de logon único -intro: 'Se você gerencia centralmente as identidades e aplicativos dos seus usuários com um provedor de identidade (IdP), você pode configurar o Logon Único (SSO) da Linguagem de Markup de Declaração de Segurança (SAML) para proteger os recursos da sua organização em {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.saml-sso %}' +title: About identity and access management with SAML single sign-on +intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% data variables.product.prodname_dotcom %}.' redirect_from: - /articles/about-identity-and-access-management-with-saml-single-sign-on - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: IAM com SSO do SAML +shortTitle: IAM with SAML SSO --- {% data reusables.enterprise-accounts.emu-saml-note %} -## Sobre o SAML SSO +## About SAML SSO {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.saml-accounts %} -Os proprietários da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". - -{% data reusables.saml.saml-requires-ghec %}{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." {% data reusables.saml.outside-collaborators-exemption %} -Antes de ativar o SAML SSO para sua organização, é necessário conectar seu IdP à sua organização. Para obter mais informações, consulte "[Conectar o provedor de identidade à sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)". +Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." -Para uma organização, o SAML SSO pode ser desabilitado, habilitado, mas não aplicado, ou habilitado e aplicado. Depois de ativar o SSO SAML para a sua organização e os integrantes da sua organização efetuarem a autenticação com sucesso com o seu IdP, você poderá aplicar a configuração SAML SSO. Para obter mais informações sobre a aplicação de SAML SSO para a sua organização do {% data variables.product.prodname_dotcom %}, consulte "[Aplicando logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". +For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." -Os integrantes devem efetuar a autenticação periodicamente com seu IdP para efetuar a autenticação e obter acesso aos recursos da sua organização. A duração desse período de login é especificado pelo seu IdP e geralmente é de 24 horas. Esse requisito de login periódico limita a duração do acesso e exige que os usuários identifiquem-se novamente para continuar. +Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue. -Para acessar os recursos protegidos da organização que usam a API e o Git na linha de comando, os integrantes devem autorizar e efetuar a autenticação com um token de acesso pessoal ou chave SSH. Para mais informações consulte "[Autorizar um token de acesso pessoal para usar com o logon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" e "[Autorizar uma chave SSH para uso com o logon único SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. Você pode visualizar e revogar a identidade de SAML vinculada, as sessões ativas e credenciais autorizadas para integrantes da sua empresa ou conta corporativa. Para obter mais informações consulte "[Visualizar e gerenciar o acesso de SAML de um integrante da sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" e "[Visualizar e gerenciar o acesso de SAML de um usuário à conta corporativa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)". +The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise account](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." -Se os integrantes estiverem conectados com uma sessão SAML SSO, ao criarem um novo repositório, a visibilidade-padrão desse repositório será privada. Caso contrário, a visibilidade-padrão será pública. Para obter mais informações sobre a visibilidade do repositório, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". +If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." -Os integrantes da organização também devem ter uma sessão de SAML ativa para autorizar um {% data variables.product.prodname_oauth_app %}. Você pode optar por não participar deste requisito entrando em contato com {% data variables.contact.contact_support %}. {% data variables.product.product_name %} não recomenda a exclusão deste requisito, o que irá expor sua organização a um maior risco de aquisições de conta e perda potencial de dados. +Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss. {% data reusables.saml.saml-single-logout-not-supported %} -## Serviços SAML compatíveis +## Supported SAML services {% data reusables.saml.saml-supported-idps %} -Alguns IdPs são compatíveis com o o provisionamento de acesso a uma organização {% data variables.product.prodname_dotcom %} via SCIM. {% data reusables.scim.enterprise-account-scim %} Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." +Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. {% data reusables.scim.enterprise-account-scim %} For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." -## Adicionar integrantes a uma organização usando SAML SSO +## Adding members to an organization using SAML SSO -Depois que o SAML SSO é habilitado, há várias maneiras possíveis de adicionar novos integrantes à organização. Os proprietários da organização podem convidar novos integrantes manualmente no {% data variables.product.product_name %} ou usando a API. Para obter mais informações, consulte "[Convidar usuários para juntar-se à sua organização](/articles/inviting-users-to-join-your-organization)" e "[Integrantes](/rest/reference/orgs#add-or-update-organization-membership)". +After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." -Para provisionar novos usuários sem o convite de um proprietário da organização, você pode usar a URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, substituindo _ORGANIZATION_ pelo nome da sua organização. Por exemplo, é possível configurar o IdP para que qualquer pessoa que tenha acesso possa clicar em um link no painel do IdP para ingressar na sua organização do {% data variables.product.prodname_dotcom %}. +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. -Se o seu IdP é compatível com o SCIM, o {% data variables.product.prodname_dotcom %} poderá convidar automaticamente integrantes para participarem da sua organização ao conceder acesso no seu IdP. Se você remover o acesso de um integrante à organização do seu {% data variables.product.prodname_dotcom %} no seu IdP de SAML, o integrante será removido automaticamente da organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". +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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% data reusables.organizations.team-synchronization %} {% data reusables.saml.saml-single-logout-not-supported %} -## Leia mais +## Further reading -- "[Sobre a autenticação de dois fatores e o SAML de logon único](/articles/about-two-factor-authentication-and-saml-single-sign-on)" -- "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" +- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)" +- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index c2d88a5dc74a..b4df5f9aec32 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -1,12 +1,10 @@ --- -title: Sobre o SCIM -intro: 'Com o Sistema para gerenciamento de identidades entre domínios (SCIM, System for Cross-domain Identity Management), os administradores podem automatizar a troca de informações de identidade do usuário entre sistemas.' -product: '{% data reusables.gated-features.saml-sso %}' +title: About SCIM +intro: 'With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.' redirect_from: - /articles/about-scim - /github/setting-up-and-managing-organizations-and-teams/about-scim versions: - fpt: '*' ghec: '*' topics: - Organizations @@ -15,20 +13,20 @@ topics: {% data reusables.enterprise-accounts.emu-scim-note %} -Se você usa [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) em sua organização, é possível implementar o SCIM pra adicionar, gerenciar e remover o acesso dos integrantes da organização ao {% data variables.product.product_name %}. Por exemplo, um administrador pode desprovisionar um integrante da organização usando SCIM e remover automaticamente o integrante da organização. +If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization. -Se o SAML SSO for usado sem implementação do SCIM, você não terá desprovisionamento automático. Quando as sessões dos integrantes da organização expiram depois que o acesso deles é removido do IdP, eles não podem ser removidos automaticamente da organização. Os tokens autorizados concedem acesso à organização mesmo depois que as respectivas sessões expiram. Para remover o acesso, os administradores da organização podem remover o token autorizado manualmente da organização ou automatizar a remoção com o SCIM. +If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM. -Estes provedores de identidade são compatíveis com a API de SCIM de {% data variables.product.product_name %} para organizações. For more information, see [SCIM](/rest/reference/scim) in the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation. +These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation. - Azure AD - Okta - OneLogin {% data reusables.scim.enterprise-account-scim %} -## Leia mais +## Further reading -- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" -- "[Conectar o provedor de identidade à sua organização](/articles/connecting-your-identity-provider-to-your-organization)" -- "[Habilitar e testar SAML de logon único para sua organização](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" -- "[Visualizar e gerenciar acesso de SAML de um integrante à sua organização](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)" +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)" +- "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" +- "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md index 2d9f0b7b517b..61ab67a115a2 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -1,33 +1,34 @@ --- -title: Acessar sua organização se o provedor de identidade não estiver disponível -intro: 'Os administradores da organização podem entrar no {% data variables.product.product_name %} mesmo se o provedor de identidade deles estiver indisponível, ignorando o logon único e usando os respectivos códigos de recuperação.' -product: '{% data reusables.gated-features.saml-sso %}' +title: Accessing your organization if your identity provider is unavailable +intro: 'Organization administrators can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on and using their recovery codes.' redirect_from: - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Provedor de identidade indisponível +shortTitle: Unavailable identity provider --- -Os administradores da organização podem usar [um de seus códigos de recuperação baixados ou salvos](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) para ignorar o logon único. Você pode ter salvado em um gerenciador de senhas, como [LastPass](https://lastpass.com/) ou [1Password](https://1password.com/). +Organization administrators can use [one of their downloaded or saved recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) to bypass single sign-on. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/). {% note %} -**Observação:** você pode usar os códigos de recuperação apenas uma vez e deve usá-los em ordem consecutiva. Os códigos de recuperação concedem acesso por 24 horas. +**Note:** You can only use recovery codes once and you must use them in consecutive order. Recovery codes grant access for 24 hours. {% endnote %} -1. Na parte inferior da caixa de diálogo de logon único, clique em **Use a recovery code** (Usar um código de recuperação) para ignorar o logon único. ![Link para inserir código de recuperação](/assets/images/help/saml/saml_use_recovery_code.png) -2. No campo "Recovery Code" (Código de Recuperação), digite seu código de recuperação. ![Campo para inserir código de recuperação](/assets/images/help/saml/saml_recovery_code_entry.png) -3. Clique em **Verificar**. ![Botão para verificar código de recuperação](/assets/images/help/saml/saml_verify_recovery_codes.png) +1. At the bottom of the single sign-on dialog, click **Use a recovery code** to bypass single sign-on. +![Link to enter your recovery code](/assets/images/help/saml/saml_use_recovery_code.png) +2. In the "Recovery Code" field, type your recovery code. +![Field to enter your recovery code](/assets/images/help/saml/saml_recovery_code_entry.png) +3. Click **Verify**. +![Button to verify your recovery code](/assets/images/help/saml/saml_verify_recovery_codes.png) -Depois de ter usado um código de recuperação, certifique-se de anotar que ele não é mais válido. Você não poderá reutilizar o código de recuperação. +After you've used a recovery code, make sure to note that it's no longer valid. You will not be able to reuse the recovery code. -## Leia mais +## Further reading -- "[Sobre gerenciamento de identidade e acesso com o SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[About identity and access management with SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md index 242442993042..0c2dba8ac39e 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -1,59 +1,59 @@ --- -title: Configurar SCIM e o logon único SAML usando o Okta -intro: 'Você pode usar o logon único (SSO) da Linguagem de Markup da Declaração de Segurança (SAML) e o Sistema de Gerenciamento de Identidades de Domínio Cruzado (SCIM) com o Okta para gerenciar automaticamente o acesso à sua organização em {% data variables.product.prodname_dotcom %}.' +title: Configuring SAML single sign-on and SCIM using Okta +intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.product.product_location %}.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta -product: '{% data reusables.gated-features.saml-sso %}' permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization. versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Configurar SAML & SCIM com Okta +shortTitle: Configure SAML & SCIM with Okta --- -## Sobre SAML e SCIM com Okta +## About SAML and SCIM with Okta -Você pode controlar o acesso à organização do {% data variables.product.prodname_dotcom %} e outros aplicativos da web a partir de uma interface central, configurando a organização para usar SAML SSO e SCIM com Okta, um provedor de identidade (IdP). +You can control access to your organization on {% data variables.product.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP). -O SAML SSO controla e protege o acesso a recursos da organização, como repositórios, problemas e pull requests. O SCIM adiciona, gerencia e remove automaticamente o acesso dos integrantes à sua organização do {% data variables.product.prodname_dotcom %} quando você fizer alterações no Okta. Para obter mais informações, consulte "[Sobre a identidade e gerenciamento de acesso com logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" e "[Sobre SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". +SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." -Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponíveis para qualquer usuário ao qual você atribuir seu aplicativo do {% data variables.product.prodname_ghe_cloud %} no Okta. +After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta. -| Funcionalidade | Descrição | -| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fazer push de novos usuários | Ao criar um novo usuário no Okta, ele receberá um e-mail para juntar-se à sua organização do {% data variables.product.prodname_dotcom %}. | -| Fazer push de desativações de usuário | Ao desativar um usuário no Okta, este removerá o usuário da sua organização de {% data variables.product.prodname_dotcom %}. | -| Fazer push das atualização de perfil | Ao atualizar o perfil de um usuário no Okta, este atualizará os metadados para a associação do usuário na sua organização de {% data variables.product.prodname_dotcom %}. | -| Reativar usuários | Ao reativar um usuário no Okta, este enviará um convite por e-mail para o usuário juntar-se novamente à sua organização de {% data variables.product.prodname_dotcom %}. | +| Feature | Description | +| --- | --- | +| Push New Users | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.product.product_location %}. | +| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.product.product_location %}. | +| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. | +| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}. | -## Pré-requisitos +## Prerequisites {% data reusables.saml.use-classic-ui %} -## Adicionar o aplicativo {% data variables.product.prodname_ghe_cloud %} no Okta +## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta {% data reusables.saml.okta-dashboard-click-applications %} {% data reusables.saml.add-okta-application %} {% data reusables.saml.search-ghec-okta %} -4. À direita do "Github Enterprise Cloud - Organização", clique em **Adicionar**. ![Clicar em "Adicionar" para o aplicativo {% data variables.product.prodname_ghe_cloud %}](/assets/images/help/saml/okta-add-ghec-application.png) +4. To the right of "Github Enterprise Cloud - Organization", click **Add**. + ![Clicking "Add" for the {% data variables.product.prodname_ghe_cloud %} application](/assets/images/help/saml/okta-add-ghec-application.png) -5. No campo **Organização do GitHub**, digite o nome da sua organização de {% data variables.product.prodname_dotcom %}. Por exemplo, se a URL da sua organização for https://github.com/octo-org, o nome da organização será `octo-org`. ![Digite o nome da organização do GitHub](/assets/images/help/saml/okta-github-organization-name.png) +5. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`. + ![Type GitHub organization name](/assets/images/help/saml/okta-github-organization-name.png) -6. Clique em **Cpncluído**. +6. Click **Done**. -## Habilitar e e testar o SAML SSO +## Enabling and testing SAML SSO {% data reusables.saml.okta-dashboard-click-applications %} {% data reusables.saml.okta-applications-click-ghec-application-label %} {% data reusables.saml.assign-yourself-to-okta %} {% data reusables.saml.okta-sign-on-tab %} {% data reusables.saml.okta-view-setup-instructions %} -6. Habilitar e testar o SAML SSO no {% data variables.product.prodname_dotcom %} usando a URL de logon, a URL do emissor e os certificados públicos da aba "Como configurar o SAML 2.0". Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)". +6. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)." -## Configurar provisionamento de acesso com SCIM em Okta +## Configuring access provisioning with SCIM in Okta {% data reusables.saml.okta-dashboard-click-applications %} {% data reusables.saml.okta-applications-click-ghec-application-label %} @@ -62,22 +62,25 @@ Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponív {% data reusables.saml.okta-enable-api-integration %} -6. Clique em **Efetuar a autenticação com Github Enterprise Cloud - Organização**. ![Botão "Efetuar a autenticação com Github Enterprise Cloud - Organização" para o aplicativo Okta](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) +6. Click **Authenticate with Github Enterprise Cloud - Organization**. + !["Authenticate with Github Enterprise Cloud - Organization" button for Okta application](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) -7. À direita do nome da sua organização, clique em **Conceder**. ![Botão "Conceder" para autorizar a integração do SCIM do Okta para acessar a organização](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) +7. To the right of your organization's name, click **Grant**. + !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) {% note %} - **Observação**: Se você não vir a sua organização na lista, acesse `https://github.com/orgs/ORGANIZATION-NAME/sso` no seu navegador e efetue a autenticação com sua organização por meio do SAML SSO usando sua conta de administrador no IdP. Por exemplo, se o nome da sua organização for `octo-org`, a URL seria `https://github.com/orgs/octo-org/sso`. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". + **Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." {% endnote %} -1. Clique em **Autorizar o OktaOAN**. ![Botão "Autorizar o OktaOAN" para autorizar a integração do SCIM do Okta para acessar a organização](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) +1. Click **Authorize OktaOAN**. + !["Authorize OktaOAN" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) {% data reusables.saml.okta-save-provisioning %} {% data reusables.saml.okta-edit-provisioning %} -## Leia mais +## Further reading -- "[Configurar o logon único SAML para a sua conta corporativa usando o Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" -- "[Gerenciar a sincronização de equipe para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" -- [Compreender o SAML](https://developer.okta.com/docs/concepts/saml/) na documentação do Okta -- [Entender o SCIM](https://developer.okta.com/docs/concepts/scim/) na documentação do Okta +- "[Configuring SAML single sign-on for your enterprise account using Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" +- "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" +- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation +- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md index 83c4d554e383..6917f58951cd 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -1,31 +1,29 @@ --- -title: Conectar o provedor de identidade à organização -intro: 'Para usar o logon único SAML e o SCIM, é preciso conectar o provedor de identidade à organização do {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.saml-sso %}' +title: Connecting your identity provider to your organization +intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider to your {% data variables.product.product_name %} organization.' redirect_from: - /articles/connecting-your-identity-provider-to-your-organization - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Conectar um IdP +shortTitle: Connect an IdP --- -Ao habilitar o SAML SSO para sua organização de {% data variables.product.product_name %}, você conecta seu provedor de identidade (IdP) à sua organização. Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)". +When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)." -Você pode encontrar as informações de implementação do SAML e SCIM para seu IdP na documentação do IdP. -- [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) do Active Directory Federation Services (AD FS) -- [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) e [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) do Azure Active Directory (Azure AD) -- [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) e [SCIM](http://developer.okta.com/standards/SCIM/) do Okta -- [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) e [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e) do OneLogin -- [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector) do PingOne -- [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home) do Shibboleth +You can find the SAML and SCIM implementation details for your IdP in the IdP's documentation. +- Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) +- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) and [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) +- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) and [SCIM](http://developer.okta.com/standards/SCIM/) +- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) and [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e) +- PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector) +- Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home) {% note %} -**Observação:** os provedores de identidade aceitos pelo {% data variables.product.product_name %} para SCIM são Azure AD, Okta e OneLogin. {% data reusables.scim.enterprise-account-scim %} Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". +**Note:** {% data variables.product.product_name %} supported identity providers for SCIM are Azure AD, Okta, and OneLogin. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% endnote %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md index 6691d7de20af..01040de16fb0 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -1,37 +1,37 @@ --- -title: Baixar os códigos de recuperação de logon único de SAML da organização -intro: 'Os administradores da organização devem baixar os códigos de recuperação de logon único de SAML dela para garantir que possam acessar o {% data variables.product.product_name %} mesmo se o provedor de identidade da organização não estiver disponível.' +title: Downloading your organization's SAML single sign-on recovery codes +intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.' redirect_from: - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes -product: '{% data reusables.gated-features.saml-sso %}' versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Fazer o download de códigos de recuperação SAML +shortTitle: Download SAML recovery codes --- -Os códigos de recuperação não devem ser compartilhados ou distribuídos. Recomendamos salvá-los com um gerenciador de senhas como [LastPass](https://lastpass.com/) ou [1Password](https://1password.com/). +Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/). {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %} -5. Em "SAML single sign-on" (Logon único de SAML), na observação sobre código de recuperação, clique em **Save your recovery codes** (Salvar os códigos de recuperação). ![Link para exibir e salvar os códigos de recuperação](/assets/images/help/saml/saml_recovery_codes.png) -6. Salve seus códigos de recuperação clicando em **Download** (Baixar), **Print** (Imprimir) ou **Copy** (Copiar). ![Botões para baixar, imprimir ou copiar os códigos de recuperação](/assets/images/help/saml/saml_recovery_code_options.png) +5. Under "SAML single sign-on", in the note about recovery codes, click **Save your recovery codes**. +![Link to view and save your recovery codes](/assets/images/help/saml/saml_recovery_codes.png) +6. Save your recovery codes by clicking **Download**, **Print**, or **Copy**. +![Buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png) {% note %} - **Observação:** os códigos de recuperação ajudam você a retornar para o {% data variables.product.product_name %} caso seu IdP fique indisponível. Se você gerar novos códigos de recuperação, os exibidos na página "Códigos de recuperação de logon único" serão atualizados automaticamente. + **Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated. {% endnote %} -7. Cada código de recuperação só pode ser usado uma vez para recuperar o acesso ao {% data variables.product.product_name %}. O acesso ao {% data variables.product.product_name %} só ficará disponível 24 horas antes de você fazer login usando o login único. +7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on. -## Leia mais +## Further reading -- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" -- "[Acessar a organização se o provedor de identidade estiver indisponível](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)" +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md index 0b2813c766d3..00cc0a8af62c 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -1,60 +1,63 @@ --- -title: Habilitar e testar logon único de SAML para sua organização -intro: 'Os administradores e proprietários da organização podem habilitar o logon único (SSO, Single Sign-On) de SAML para adicionar uma camada extra de segurança à organização.' -product: '{% data reusables.gated-features.saml-sso %}' +title: Enabling and testing SAML single sign-on for your organization +intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization. redirect_from: - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Habilitar & testar o SSO do SAML +shortTitle: Enable & test SAML SSO --- -## Sobre o logon único SAML +## About SAML single sign-on -Você pode habilitar o SAML SSO na sua organização sem exigir que todos os integrantes o utilizem. A habilitação (em vez da aplicação) do SAML SSO facilitará a adoção dele pela organização. Depois que a maioria dos integrantes da sua organização já estiver usando o SAML SSO, você poderá aplicá-lo a toda a organização. +You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization. -Se você habilitar em vez de aplicar o SAML SSO, os integrantes da organização que preferem não usá-lo poderão continuar sendo integrantes da organização. Para obter mais informações sobre a aplicação do SAML SSO, consulte "[Aplicar logon único de SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". +If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." {% data reusables.saml.outside-collaborators-exemption %} -## Habilitar e testar logon único de SAML para sua organização +## Enabling and testing SAML single sign-on for your organization -{% data reusables.saml.saml-requires-ghec %}{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} +Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)." -Antes de aplicar o SAML SSO na sua organização, certifique-se de preparar a organização. Para obter mais informações, consulte "[Preparar para aplicar logon único de SAML na organização](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)". - -Para obter mais informações sobre os provedores de identidade (IdPs) que {% data variables.product.company_short %} tem compabilidade com o SAML SSO, consulte "[Conectando seu provedor de identidade à sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)". +For more information about the identity providers (IdPs) that {% data variables.product.company_short %} supports for SAML SSO, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %} -5. Em "SAML single sign-on" (Logon único de SAML), selecione **Enable SAML authentication** (Habilitar autenticação SAML). ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/saml/saml_enable.png) +5. Under "SAML single sign-on", select **Enable SAML authentication**. +![Checkbox for enabling SAML SSO](/assets/images/help/saml/saml_enable.png) {% note %} - **Observação:** depois de habilitar o SAML SSO, baixe os seus códigos de recuperação de logon único para poder acessar sua organização mesmo que o IdP esteja indisponível. Para obter mais informações, consulte "[Baixar códigos de recuperação de logon único de SAML da organização](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)". + **Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)." {% endnote %} -6. No campo "Sign on URL" (URL de logon), digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url.png) -7. Como alternativa, no campo "Issuer" (Emissor), digite o nome do emissor do SAML. Isso confirma a autenticidade das mensagens enviadas. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png) -8. Em "Public Certificate" (Certificado público), cole um certificado para verificar as respostas de SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) -9. Clique em {% octicon "pencil" aria-label="The edit icon" %} e, nos menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação), escolha o algoritmo de hash usado pelo emissor de SAML para verificar a integridade das solicitações. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png) -10. Antes de habilitar o SAML SSO para sua organização, clique em **Test SAML configuration** (Testar configuração de SAML) para garantir que as informações que você digitou estão corretas. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_test.png) +6. In the "Sign on URL" field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. +![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url.png) +7. Optionally, in the "Issuer" field, type your SAML issuer's name. This verifies the authenticity of sent messages. +![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) +8. Under "Public Certificate," paste a certificate to verify SAML responses. +![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) +9. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests. +![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) +10. Before enabling SAML SSO for your organization, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) {% tip %} - **Dica:** {% data reusables.saml.testing-saml-sso %} + **Tip:** {% data reusables.saml.testing-saml-sso %} {% endtip %} -11. Para aplicar o SAML SSO e remover todos os integrantes da organização que não foram autenticados via IdP, selecione **Require SAML SSO authentication for all members of the _organization name_ organization** (Requer autenticação do SAML SSO para todos os integrantes da organização *nome da organização*). Para obter mais informações sobre a aplicação do SAML SSO, consulte "[Aplicar logon único de SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". ![Caixa de seleção para exigir SAML SSO para sua organização ](/assets/images/help/saml/saml_require_saml_sso.png) -12. Clique em **Salvar**. ![Botão para salvar as configurações do SAML SSO](/assets/images/help/saml/saml_save.png) +11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." +![Checkbox to require SAML SSO for your organization ](/assets/images/help/saml/saml_require_saml_sso.png) +12. Click **Save**. +![Button to save SAML SSO settings](/assets/images/help/saml/saml_save.png) -## Leia mais +## Further reading -- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md index a42fb0082de3..667d5251a902 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -1,50 +1,50 @@ --- -title: Aplicar logon único de SAML para sua organização -intro: Administradores e proprietários da organização podem aplicar SAML SSO para que todos os integrantes da organização possam efetuar a autenticação por meio de um provedor de identidade (IdP). -product: '{% data reusables.gated-features.saml-sso %}' +title: Enforcing SAML single sign-on for your organization +intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider (IdP). redirect_from: - /articles/enforcing-saml-single-sign-on-for-your-organization - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Aplicar logon único SAML +shortTitle: Enforce SAML single sign-on --- -## Sobre a aplicação do SAML SSO para sua organização +## About enforcement of SAML SSO for your organization -Ao habilitar o SAML SSO, {% data variables.product.prodname_dotcom %} solicitará que os integrantes que visitam os recursos da organização em {% data variables.product.prodname_dotcom_the_website %} efetuem a autenticação no seu IdP, que vincula a conta de usuário do integrante a uma identidade no IdP. Os integrantes ainda podem acessar os recursos da organização antes da autenticação com seu IdP. +When you enable SAML SSO, {% data variables.product.prodname_dotcom %} will prompt members who visit the organization's resources on {% data variables.product.prodname_dotcom_the_website %} to authenticate on your IdP, which links the member's user account to an identity on the IdP. Members can still access the organization's resources before authentication with your IdP. -![Banner com solicitação para efetuar a autenticação por meio do SAML SSO para acessar a organização](/assets/images/help/saml/sso-has-been-enabled.png) +![Banner with prompt to authenticate via SAML SSO to access organization](/assets/images/help/saml/sso-has-been-enabled.png) -Você também pode aplicar SAML SSO para a sua organização. {% data reusables.saml.when-you-enforce %} Aplicação remove todos os integrantes e administradores que não tenham efetuado a autenticação por meio do seu IdP da organização. {% data variables.product.company_short %} envia uma notificação de email para cada usuário removido. +You can also enforce SAML SSO for your organization. {% data reusables.saml.when-you-enforce %} Enforcement removes any members and administrators who have not authenticated via your IdP from the organization. {% data variables.product.company_short %} sends an email notification to each removed user. -Você poderá restaurar integrantes da organização depois que eles tiverem concluído o logon único com êxito. Os privilégios e configurações de acesso dos usuários removidos são salvos por três meses e podem ser restaurados durante este período. Para obter mais informações, consulte "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)". +You can restore organization members once they successfully complete single sign-on. Removed users' access privileges and settings are saved for three months and can be restored during this time frame. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)." -As contas de bots e serviços que não têm identidades externas configuradas no IdP da sua organização também serão removidas quando você aplicar o SAML SSO. Para obter mais informações sobre bots e contas de serviço, consulte "[Gerenciar bots e contas de serviço com logon único SAML](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)". +Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed when you enforce SAML SSO. For more information about bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)." -Se a sua organização pertencer a uma conta corporativa que exigir o SAML para a conta corporativa substituirá a configuração SAML da organização e aplicará SAML SSO para todas as organizações da empresa. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". +If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." {% tip %} -**Dica:** {% data reusables.saml.testing-saml-sso %} +**Tip:** {% data reusables.saml.testing-saml-sso %} {% endtip %} -## Impondo o SAML SSO para a sua organização +## Enforcing SAML SSO for your organization -1. Habilitar e testar o SAML SSO para a sua organização e, em seguida, efetuar a autenticação com seu IdP pelo menos uma vez. Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)". -1. Prepare-se para aplicar o SAML SSO na sua organização. Para obter mais informações, consulte "[Preparar para aplicar logon único de SAML na organização](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)". +1. Enable and test SAML SSO for your organization, then authenticate with your IdP at least once. For more information, see "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)." +1. Prepare to enforce SAML SSO for your organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)." {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %} -1. Em "logon único SAML", selecione **Exige augenticação SAML SSO para todos os integrantes da _ORGANIZAÇÃO_ organização**. ![Caixa de seleção "Exigir autenticação SAML SSO"](/assets/images/help/saml/require-saml-sso-authentication.png) -1. Se algum integrante da organização não tiver efetuado a autenticação por eio do seu IdP, {% data variables.product.company_short %} irá exibir os integrantes. Se você aplicar o SAML SSO, {% data variables.product.company_short %} removerá os integrantes da organização. Revise o aviso e clique em **Remover os integrantes e exigir o logon único SAML**. ![Diálogo "Confirmar a aplicação do SAML SSO" com a lista de integrantes a serem removidos da organização](/assets/images/help/saml/confirm-saml-sso-enforcement.png) -1. Em "Códigos de recuperação do logon único", revise seus códigos de recuperação. Armazene os códigos de recuperação em um local seguro, como um gerenciador de senhas. +1. Under "SAML single sign-on", select **Require SAML SSO authentication for all members of the _ORGANIZATION_ organization**. + !["Require SAML SSO authentication" checkbox](/assets/images/help/saml/require-saml-sso-authentication.png) +1. If any organization members have not authenticated via your IdP, {% data variables.product.company_short %} displays the members. If you enforce SAML SSO, {% data variables.product.company_short %} will remove the members from the organization. Review the warning and click **Remove members and require SAML single sign-on**. + !["Confirm SAML SSO enforcement" dialog with list of members to remove from organization](/assets/images/help/saml/confirm-saml-sso-enforcement.png) +1. Under "Single sign-on recovery codes", review your recovery codes. Store the recovery codes in a safe location like a password manager. -## Leia mais +## Further reading -- "[Visualizar e gerenciar acesso de SAML de um integrante à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" +- "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md index 420131782ea7..4a825c577035 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -1,12 +1,11 @@ --- title: Managing SAML single sign-on for your organization -intro: Organization administrators can manage organization members' identities and access to the organization with SAML single sign-on (SSO). +intro: Organization owners can manage organization members' identities and access to the organization with SAML single sign-on (SSO). redirect_from: - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on/ - /articles/managing-saml-single-sign-on-for-your-organization - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization versions: - fpt: '*' ghec: '*' topics: - Organizations diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index c963c89bb722..353f17c351fb 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -1,7 +1,6 @@ --- title: Managing team synchronization for your organization intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.team-synchronization %}' redirect_from: - /articles/synchronizing-teams-between-your-identity-provider-and-github - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github @@ -10,7 +9,6 @@ redirect_from: permissions: Organization owners can manage team synchronization for an organization. miniTocMaxHeadingLevel: 3 versions: - fpt: '*' ghec: '*' topics: - Organizations diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md index e44f6aa588ba..8af5f304512a 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -1,27 +1,25 @@ --- -title: Preparar para exigir o logon único SAML na organização -intro: 'Antes de exigir o logon único SAML na organização, você deve verificar a associação da organização e configurar as definições de conexão para seu provedor de identidade.' -product: '{% data reusables.gated-features.saml-sso %}' +title: Preparing to enforce SAML single sign-on in your organization +intro: 'Before you enforce SAML single sign-on in your organization, you should verify your organization''s membership and configure the connection settings to your identity provider.' redirect_from: - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization versions: - fpt: '*' ghec: '*' topics: - Organizations - Teams -shortTitle: Prepare-se para aplicar o SSO do SAML +shortTitle: Prepare to enforce SAML SSO --- -{% data reusables.saml.when-you-enforce %} antes de aplicar o SAML SSO na sua organização, você deverá revisar a associação da organização, habilitar o SAML SSO e revisar o acesso SAML dos integrantes da organização. Para obter mais informações, consulte o seguinte. +{% data reusables.saml.when-you-enforce %} Before enforcing SAML SSO in your organization, you should review organization membership, enable SAML SSO, and review organization members' SAML access. For more information, see the following. -| Tarefa | Mais informações | -|:---------------------------------------------------------------------------------------------- |:------------------------- | -| Adicionar ou remover integrantes da sua organização |
  • "[Convidar usuários para participar da sua organização](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"
  • "[Remover um integrante da sua organização](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"
| -| Conecte seu IdP à sua organização habilitando o SAML SSO |
  • "[Conectando seu provedor de identidade à sua organização](/organizations/managing-saml-one-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"
  • "[Habilitando e testando o logon único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"
| -| Certifique-se de que os integrantes da organização registraram e vincularam suas contas ao IdP |
  • "[Visualizando e gerenciando o acesso SAML de um integrante para a sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"
| +| Task | More information | +| :- | :- | +| Add or remove members from your organization |
  • "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"
  • "[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"
| +| Connect your IdP to your organization by enabling SAML SSO |
  • "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"
  • "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"
| +| Ensure that your organization members have signed in and linked their accounts with the IdP |
  • "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"
| -Após concluir estas tarefas, você pode aplicar o SAML SSO SAML para a sua organização. Para obter mais informações, consulte "[Aplicando o logon único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)". +After you finish these tasks, you can enforce SAML SSO for your organization. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md index dffddfadae82..5e33eb9458b8 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md @@ -1,9 +1,7 @@ --- title: Troubleshooting identity and access management intro: 'Review and resolve common troubleshooting errors for managing your organization''s SAML SSO, team synchronization, or identity provider (IdP) connection.' -product: '{% data reusables.gated-features.saml-sso %}' versions: - fpt: '*' ghec: '*' topics: - Organizations diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md index afb6c6e98797..9224f9ceecd7 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -1,6 +1,6 @@ --- -title: Criar equipes -intro: Você pode criar equipes independentes ou aninhadas para gerenciar permissões de repositório e menções para grupos de pessoas. +title: Creating a team +intro: You can create independent or nested teams to manage repository permissions and mentions for groups of people. redirect_from: - /articles/creating-a-team-early-access-program/ - /articles/creating-a-team @@ -15,7 +15,7 @@ topics: - Teams --- -Apenas os proprietários e mantenedores de uma equipe principal podem criar uma nova equipe secundária sob a principal. Os proprietários também podem restringir as permissões de criação para todas as equipes em uma organização. Para obter mais informações, consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)". +Only organization owners and maintainers of a parent team can create a new child team under a parent. Owners can also restrict creation permissions for all teams in an organization. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." {% data reusables.organizations.team-synchronization %} @@ -25,17 +25,18 @@ Apenas os proprietários e mantenedores de uma equipe principal podem criar uma {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} -{% ifversion fpt or ghec %} -1. Opcionalmente, se sua conta da organização ou empresa usa a sincronização de equipes ou sua empresa usa {% data variables.product.prodname_emus %}, conecte um grupo do provedor de identidade à sua equipe. - * Se a sua empresa usar o {% data variables.product.prodname_emus %}, use o menu suspenso "Grupos de provedor de identidade" e selecione um único grupo de provedores de identidade para conectar-se à nova equipe. Para mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". - * Se a conta da sua organização ou empresa usar a sincronização de equipe, use o menu suspenso "Grupos de provedor de identidade e selecione até cinco grupos de provedores de identidade para conectar-se à nova equipe. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Menu suspenso para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png) +{% ifversion ghec %} +1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team. + * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." + ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -1. Se desejar, [forneça à equipe acesso aos repositórios da organização](/articles/managing-team-access-to-an-organization-repository). +1. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository). -## Leia mais +## Further reading -- "[Sobre equipes](/articles/about-teams)" -- "[Alterar a visibilidade da equipe](/articles/changing-team-visibility)" -- "[Mover uma equipe na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[About teams](/articles/about-teams)" +- "[Changing team visibility](/articles/changing-team-visibility)" +- "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 1c53bcbdc812..1e2fc70a8f0f 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -3,10 +3,8 @@ title: Synchronizing a team with an identity provider group intro: 'You can synchronize a {% data variables.product.product_name %} team with an identity provider (IdP) group to automatically add and remove team members.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group -product: '{% data reusables.gated-features.team-synchronization %} ' permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.' versions: - fpt: '*' ghae: '*' ghec: '*' topics: @@ -21,15 +19,15 @@ shortTitle: Synchronize with an IdP {% data reusables.identity-and-permissions.about-team-sync %} -{% ifversion fpt or ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. +{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. -{% ifversion fpt or ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} +{% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} -Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion fpt or ghec %} or using the API{% endif %}. +Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}. -{% ifversion fpt or ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} +{% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} -{% ifversion fpt or ghec %} +{% ifversion ghec %} All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour. Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)." {% endif %} @@ -42,9 +40,9 @@ Parent teams cannot synchronize with IdP groups. If the team you want to connect To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." -{% ifversion fpt or ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %} +{% ifversion ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %} -{% ifversion fpt or ghec %} +{% ifversion ghec %} ## Requirements for members of synchronized teams After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if: @@ -62,7 +60,7 @@ To avoid unintentionally removing team members, we recommend enforcing SAML SSO ## Prerequisites -{% ifversion fpt or ghec %} +{% ifversion ghec %} Before you can connect a {% data variables.product.product_name %} team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator. @@ -83,7 +81,7 @@ When you connect an IdP group to a {% data variables.product.product_name %} tea {% data reusables.user_settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} -{% ifversion fpt or ghec %} +{% ifversion ghec %} 6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %} 6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list. @@ -98,7 +96,7 @@ If you disconnect an IdP group from a {% data variables.product.prodname_dotcom {% data reusables.user_settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} -{% ifversion fpt or ghec %} +{% ifversion ghec %} 6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %} 6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. diff --git a/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md index 7656a128c8e9..293248895a08 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md +++ b/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md @@ -1,6 +1,6 @@ --- -title: Configurando o controle de acesso e visibilidade de um pacote -intro: 'Escolha quem tem acesso de leitura, gravação ou administrador à sua imagem de contêiner e a visibilidade das suas imagens de contêiner em {% data variables.product.prodname_dotcom %}.' +title: Configuring a package's access control and visibility +intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images @@ -8,83 +8,94 @@ redirect_from: versions: fpt: '*' ghec: '*' -shortTitle: Controle de acesso & visibilidade +shortTitle: Access control & visibility --- -Pacotes com permissões granulares são escopos para uma conta de usuário pessoal ou de organização. Você pode alterar o controle de acesso e a visibilidade de um pacote separadamente do repositório ao qual ele está conectado (ou vinculado). +Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to. -Atualmente, você só pode usar permissões granulares com o {% data variables.product.prodname_container_registry %}. Permissões granulares não são compatíveis nos nossos outros registros de pacotes, como o registro npm. +Currently, you can only use granular permissions with the {% data variables.product.prodname_container_registry %}. Granular permissions are not supported in our other package registries, such as the npm registry. -Para obter mais informações sobre permissões para pacotes com escopo de repositório, escopos relacionados aos pacotes para PATs, ou gerenciar permissões para seus fluxos de trabalho de ações, consulte "[Sobre permissões para os Pacotes GitHub](/packages/learn-github-packages/about-permissions-for-github-packages)". +For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)." -## Visibilidade e permissões de acesso para imagens de contêiner +## Visibility and access permissions for container images {% data reusables.package_registry.visibility-and-access-permissions %} -## Configurar acesso a imagens de contêiner para sua conta pessoal +## Configuring access to container images for your personal account -Se você tiver permissões de administrador para uma imagem de contêiner que pertence a uma conta de usuário, você pode atribuir funções de leitura, gravação ou administração a outros usuários. Para obter mais informações sobre essas funções de permissão, consulte "[Visibilidade e permissões de acesso para imagens de contêiner](#visibility-and-access-permissions-for-container-images)". +If you have admin permissions to a container image that's owned by a user account, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)." -Se o seu pacote for privado ou interno e pertencer a uma organização, você somente poderá dar acesso a outros integrantes ou equipes da organização. +If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams. {% data reusables.package_registry.package-settings-from-user-level %} -1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. As equipes não podem ter acesso a uma imagem de contêiner de uma conta de usuário. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png) -1. Ao lado do nome de usuário ou nome de equipe, use o menu suspenso "Função" para selecionar um nível de permissão desejado. ![Opções de acesso ao contêiner](/assets/images/help/package-registry/container-access-control-options.png) +1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a user account. + ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) +1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. + ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) -Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro. +The selected users will automatically be given access and don't need to accept an invitation first. -## Configurar o acesso a imagens de contêiner para uma organização +## Configuring access to container images for an organization -Se você tiver permissões de administrador para uma imagem de contêiner pertencente à organização, pode atribuir funções de leitura, gravação ou administrador para outros usuários e equipes. Para obter mais informações sobre essas funções de permissão, consulte "[Visibilidade e permissões de acesso para imagens de contêiner](#visibility-and-access-permissions-for-container-images)". +If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)." -Se o seu pacote for privado ou interno e pertencer a uma organização, você somente poderá dar acesso a outros integrantes ou equipes da organização. +If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams. {% data reusables.package_registry.package-settings-from-org-level %} -1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. Você também pode inserir um nome de equipe da organização para dar acesso a todos os integrantes da equipe. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png) -1. Ao lado do nome de usuário ou nome de equipe, use o menu suspenso "Função" para selecionar um nível de permissão desejado. ![Opções de acesso ao contêiner](/assets/images/help/package-registry/container-access-control-options.png) +1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. + ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) +1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. + ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) -Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro. +The selected users or teams will automatically be given access and don't need to accept an invitation first. -## Herdar acesso a uma imagem de contêiner de um repositório +## Inheriting access for a container image from a repository -Para simplificar o gerenciamento de pacotes por meio dos fluxos de trabalho de {% data variables.product.prodname_actions %}, você pode habilitar uma imagem contêiner para herdar as permissões de acesso de um repositório por padrão. +To simplify package management through {% data variables.product.prodname_actions %} workflows, you can enable a container image to inherit the access permissions of a repository by default. -Se você herdar as permissões de acesso do repositório onde os fluxos de trabalho do seu pacote são armazenados, posteriormente, você poderá ajustar o acesso ao seu pacote pelas permissões do repositório. +If you inherit the access permissions of the repository where your package's workflows are stored, then you can adjust access to your package through the repository's permissions. -Uma vez que um repositório é sincronizado, você não poderá acessar as configurações de acesso granular do pacote. Para personalizar as permissões do pacote através das configurações de acesso ao pacote granular, você deverá remover a sincronização do repositório primeiro. +Once a repository is synced, you can't access the package's granular access settings. To customize the package's permissions through the granular package access settings, you must remove the synced repository first. {% data reusables.package_registry.package-settings-from-org-level %} -2. Em "Fonte do repositório", selecione **Herdar acesso do repositório (recomendado)**. ![Caixa de seleção herdar acesso do repositório](/assets/images/help/package-registry/inherit-repo-access-for-package.png) +2. Under "Repository source", select **Inherit access from repository (recommended)**. + ![Inherit repo access checkbox](/assets/images/help/package-registry/inherit-repo-access-for-package.png) -## Garantir o acesso ao fluxo de trabalho para o seu pacote +## Ensuring workflow access to your package -Para garantir que um fluxo de trabalho do {% data variables.product.prodname_actions %} tenha acesso ao seu pacote, você deverá conceder acesso explícito ao repositório onde o fluxo de trabalho é armazenado. +To ensure that a {% data variables.product.prodname_actions %} workflow has access to your package, you must give explicit access to the repository where the workflow is stored. -O repositório especificado não precisa ser o repositório onde o código-fonte do pacote é mantido. Você pode conceder acesso ao fluxo de trabalho de vários repositórios para um pacote. +The specified repository does not need to be the repository where the source code for the package is kept. You can give multiple repositories workflow access to a package. {% note %} -**Observação:** Sincronizar sua imagem de contêiner com um repositório por meio da opção de menu **Acesso de ações** é diferente de conectar seu contêiner a um repositório. Para obter mais informações sobre como vincular um repositório ao seu contêiner, consulte "[Conectar um repositório a um pacote](/packages/learn-github-packages/connecting-a-repository-to-a-package)". +**Note:** Syncing your container image with a repository through the **Actions access** menu option is different than connecting your container to a repository. For more information about linking a repository to your container, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)." {% endnote %} -### {% data variables.product.prodname_actions %} acesso para imagens de contêiner pertencentes ao usuário +### {% data variables.product.prodname_actions %} access for user-account-owned container images {% data reusables.package_registry.package-settings-from-user-level %} -1. Na barra lateral esquerda, clique em **Acesso às ações**. ![Opção "Ações de acesso" no menu à esquerda](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) -2. Para garantir que seu fluxo de trabalho tenha acesso ao seu pacote de container, você deve adicionar o repositório em que o fluxo de trabalho é armazenado. Clique **Adicionar repositório** e pesquise o repositório que deseja adicionar. ![Botão "Adicionar repositório"](/assets/images/help/package-registry/add-repository-button.png) -3. Ao usar o menu suspenso "função", selecione o nível de acesso padrão que você gostaria que o repositório tivesse na imagem do seu contêiner. ![Níveis de acesso permitidos para repositórios](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) +1. In the left sidebar, click **Actions access**. + !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) +2. To ensure your workflow has access to your container package, you must add the repository where the workflow is stored. Click **Add repository** and search for the repository you want to add. + !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png) +3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. + ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) -Para personalizar ainda mais o acesso à imagem do seu contêiner, consulte "[Configurando acesso a imagens de contêiner para sua conta pessoal](#configuring-access-to-container-images-for-your-personal-account)". +To further customize access to your container image, see "[Configuring access to container images for your personal account](#configuring-access-to-container-images-for-your-personal-account)." -### acesso de {% data variables.product.prodname_actions %} para imagens de contêiner pertencentes à organização +### {% data variables.product.prodname_actions %} access for organization-owned container images {% data reusables.package_registry.package-settings-from-org-level %} -1. Na barra lateral esquerda, clique em **Acesso às ações**. ![Opção "Ações de acesso" no menu à esquerda](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) -2. Clique **Adicionar repositório** e pesquise o repositório que deseja adicionar. ![Botão "Adicionar repositório"](/assets/images/help/package-registry/add-repository-button.png) -3. Usando o menu suspenso "função", selecione o nível de acesso padrão que você gostaria que os integrantes do repositório tivessem na sua imagem contêiner. Os colaboradores externos não serão incluídos. ![Níveis de acesso permitidos para repositórios](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) +1. In the left sidebar, click **Actions access**. + !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) +2. Click **Add repository** and search for the repository you want to add. + !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png) +3. Using the "role" drop-down menu, select the default access level that you'd like repository members to have to your container image. Outside collaborators will not be included. + ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) -Para personalizar ainda mais o acesso à sua imagem de contêiner, consulte "[Configurar acesso a imagens de contêiner para uma organização](#configuring-access-to-container-images-for-an-organization)". +To further customize access to your container image, see "[Configuring access to container images for an organization](#configuring-access-to-container-images-for-an-organization)." ## Ensuring {% data variables.product.prodname_codespaces %} access to your package @@ -92,68 +103,71 @@ By default, a codespace can seamlessly access certain packages in the {% data va Otherwise, to ensure that a codespace has access to your package, you must grant access to the repository where the codespace is being launched. -O repositório especificado não precisa ser o repositório onde o código-fonte do pacote é mantido. You can give codespaces in multiple repositories access to a package. +The specified repository does not need to be the repository where the source code for the package is kept. You can give codespaces in multiple repositories access to a package. Once you've selected the package you're interested in sharing with codespaces in a repository, you can grant that repo access. 1. In the right sidebar, click **Package settings**. !["Package settings" option in right menu](/assets/images/help/package-registry/package-settings.png) - + 2. Under "Manage Codespaces access", click **Add repository**. - ![Botão "Adicionar repositório"](/assets/images/help/package-registry/manage-codespaces-access-blank.png) + !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-blank.png) 3. Search for the repository you want to add. - ![Botão "Adicionar repositório"](/assets/images/help/package-registry/manage-codespaces-access-search.png) - + !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-search.png) + 4. Repeat for any additional repositories you would like to allow access. 5. If the codespaces for a repository no longer need access to an image, you can remove access. !["Remove repository" button](/assets/images/help/package-registry/manage-codespaces-access-item.png) -## Configurar a visibilidade de imagens de contêiner para sua conta pessoal +## Configuring visibility of container images for your personal account -Ao publicar um pacote, a visibilidade-padrão é privada e só você poderá ver o pacote. Você pode modificar o acesso de uma imagem do contêiner privada ou pública, alterando as configurações de acesso. +When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings. -Um pacote público pode ser acessado anonimamente sem autenticação. Uma vez que você torna público o seu pacote, mas você não poderá tornar o seu pacote privado novamente. +A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. {% data reusables.package_registry.package-settings-from-user-level %} -5. Em "Zona de Perigo", escolha uma configuração de visibilidade: - - Para tornar a imagem do contêiner visível para qualquer pessoa, clique em **Tornar pública**. +5. Under "Danger Zone", choose a visibility setting: + - To make the container image visible to anyone, click **Make public**. {% warning %} - **Aviso:** Depois de tornar um pacote público, você não poderá torná-lo privado novamente. + **Warning:** Once you make a package public, you cannot make it private again. {% endwarning %} - - Para tornar a imagem do contêiner visível para uma seleção personalizada de pessoas, clique em **Tornar privada**. ![Opções de visibilidade do contêiner](/assets/images/help/package-registry/container-visibility-option.png) + - To make the container image visible to a custom selection of people, click **Make private**. + ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) -## Visibilidade da criação de contêiner para os integrantes da organização +## Container creation visibility for organization members -Você pode escolher a visibilidade de contêineres que os integrantes da organização podem publicar por padrão. +You can choose the visibility of containers that organization members can publish by default. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -4. À esquerda, clique em **Pacotes**. -6. Em "Criação de contêiner", escolha se deseja permitir a criação de imagens públicas, privadas ou internas de contêineres. - - Para permitir que os integrantes da organização criem imagens de contêiner público, clique em **Público**. - - Para permitir que os integrantes da organização criem imagens privadas de contêiner visíveis apenas para outros integrantes da organização, clique em **Privado**. Você pode personalizar ainda mais a visibilidade de imagens de contêiner privado. - - **Para {% data variables.product.prodname_ghe_cloud %} apenas:** Para permitir que os integrantes da organização criem imagens internas de contêiner visíveis apenas para outros integrantes da organização, clique em **Interno**. ![Opções de visibilidade para imagens de contêiner publicadas por integrantes da organização](/assets/images/help/package-registry/container-creation-org-settings.png) +4. On the left, click **Packages**. +6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. + - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise members. + ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png) -## Configurar a visibilidade de imagens de contêiner para uma organização +## Configuring visibility of container images for an organization -Ao publicar um pacote, a visibilidade-padrão é privada e só você poderá ver o pacote. Você pode conceder a usuários ou equipes diferentes funções de acesso para sua imagem de contêiner por meio das configurações de acesso. +When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings. -Um pacote público pode ser acessado anonimamente sem autenticação. Uma vez que você torna público o seu pacote, mas você não poderá tornar o seu pacote privado novamente. +A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. {% data reusables.package_registry.package-settings-from-org-level %} -5. Em "Zona de Perigo", escolha uma configuração de visibilidade: - - Para tornar a imagem do contêiner visível para qualquer pessoa, clique em **Tornar pública**. +5. Under "Danger Zone", choose a visibility setting: + - To make the container image visible to anyone, click **Make public**. {% warning %} - **Aviso:** Depois de tornar um pacote público, você não poderá torná-lo privado novamente. + **Warning:** Once you make a package public, you cannot make it private again. {% endwarning %} - - Para tornar a imagem do contêiner visível para uma seleção personalizada de pessoas, clique em **Tornar privada**. ![Opções de visibilidade do contêiner](/assets/images/help/package-registry/container-visibility-option.png) + - To make the container image visible to a custom selection of people, click **Make private**. + ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/index.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/index.md index f9a45b6c167c..753b40a4bfed 100644 --- a/translations/pt-BR/content/repositories/archiving-a-github-repository/index.md +++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/index.md @@ -1,8 +1,8 @@ --- -title: Arquivar um repositório do GitHub -intro: 'Você pode arquivar, fazer backup e citar seu trabalho usando o {% data variables.product.product_name %}, a API ou ferramentas e serviços de terceiros.' +title: Archiving a GitHub repository +intro: 'You can archive, back up, and cite your work using {% data variables.product.product_name %}, the API, or third-party tools and services.' redirect_from: - - /articles/can-i-archive-a-repository/ + - /articles/can-i-archive-a-repository - /articles/archiving-a-github-repository - /enterprise/admin/user-management/archiving-and-unarchiving-repositories - /github/creating-cloning-and-archiving-repositories/archiving-a-github-repository @@ -18,6 +18,6 @@ children: - /about-archiving-content-and-data-on-github - /referencing-and-citing-content - /backing-up-a-repository -shortTitle: Arquivar um repositório +shortTitle: Archive a repository --- diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md index 9f763420be49..fbef6893f48e 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md @@ -1,8 +1,8 @@ --- -title: Definir a capacidade de merge de pull requests -intro: 'É possível exigir que as pull requests passem por uma série de verificações antes do merge. Por exemplo, você pode bloquear pull requests que não são aprovadas nas verificações de status ou exigir que essas pull requests tenham um número específico de revisões de aprovação antes de passarem por merge.' +title: Defining the mergeability of pull requests +intro: 'You can require pull requests to pass a set of checks before they can be merged. For example, you can block pull requests that don''t pass status checks or require that pull requests have a specific number of approving reviews before they can be merged.' redirect_from: - - /articles/defining-the-mergeability-of-a-pull-request/ + - /articles/defining-the-mergeability-of-a-pull-request - /articles/defining-the-mergeability-of-pull-requests - /enterprise/admin/developer-workflow/establishing-pull-request-merge-conditions - /github/administering-a-repository/defining-the-mergeability-of-pull-requests @@ -18,6 +18,6 @@ children: - /about-protected-branches - /managing-a-branch-protection-rule - /troubleshooting-required-status-checks -shortTitle: Mesclabilidade de PRs +shortTitle: Mergeability of PRs --- diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md index 00cda67d6c20..807c0c5aa50e 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md @@ -1,10 +1,10 @@ --- -title: Excluir e restaurar branches em uma pull request -intro: 'Se você tem acesso de gravação em um repositório, pode excluir os branches que estão associados a pull requests fechadas ou mescladas. Não é possível excluir branches associados a pull requests abertas.' +title: Deleting and restoring branches in a pull request +intro: 'If you have write access in a repository, you can delete branches that are associated with closed or merged pull requests. You cannot delete branches that are associated with open pull requests.' redirect_from: - - /articles/tidying-up-pull-requests/ - - /articles/restoring-branches-in-a-pull-request/ - - /articles/deleting-unused-branches/ + - /articles/tidying-up-pull-requests + - /articles/restoring-branches-in-a-pull-request + - /articles/deleting-unused-branches - /articles/deleting-and-restoring-branches-in-a-pull-request - /github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request - /github/administering-a-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request @@ -15,32 +15,33 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Excluir & restaurar branches +shortTitle: Delete & restore branches --- +## Deleting a branch used for a pull request -## Excluindo um branch usado para uma pull request - -Você pode excluir um branch que esteja associado a uma pull request se a pull request tiver sofrido merge ou estiver encerrada e não houver outras pull requests abertas que referenciem o branch. Para obter informações sobre branches de fechamento que não estão associados a pull requests, consulte "[Criar e excluir branches dentro do seu repositório.](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)". +You can delete a branch that is associated with a pull request if the pull request has been merged or closed and there are no other open pull requests referencing the branch. For information on closing branches that are not associated with pull requests, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.list-closed-pull-requests %} -4. Na lista de pull requests, clique naquela associada ao branch que você deseja excluir. -5. Próximo à parte inferior da pull request, clique em **Delete branch** (Excluir branch). ![Botão Delete branch (Excluir branch)](/assets/images/help/pull_requests/delete_branch_button.png) +4. In the list of pull requests, click the pull request that's associated with the branch that you want to delete. +5. Near the bottom of the pull request, click **Delete branch**. + ![Delete branch button](/assets/images/help/pull_requests/delete_branch_button.png) - Este botão não é exibido se houver atualmente uma pull request aberta para este branch. + This button isn't displayed if there's currently an open pull request for this branch. -## Restaurar um branch excluído +## Restoring a deleted branch -É possível restaurar um head branch de uma pull request fechada. +You can restore the head branch of a closed pull request. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.list-closed-pull-requests %} -4. Na lista de pull requests, clique naquela associada ao branch que você deseja restaurar. -5. Próximo à parte inferior da pull request, clique em **Restore branch** (Restaurar branch). ![Botão Restore deleted branch (Restaurar branch excluído)](/assets/images/help/branches/branches-restore-deleted.png) +4. In the list of pull requests, click the pull request that's associated with the branch that you want to restore. +5. Near the bottom of the pull request, click **Restore branch**. + ![Restore deleted branch button](/assets/images/help/branches/branches-restore-deleted.png) -## Leia mais +## Further reading -- "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)" -- "[Gerenciando a exclusão automática de branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)" +- "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)" +- "[Managing the automatic deletion of branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)" diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md index 6a27e9ea41ef..46012a30d41a 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -48,7 +48,7 @@ You can restrict who has access to a repository by choosing a repository's visib {% ifversion fpt or ghec or ghes %} -When you create a repository, you can choose to make the repository public or private.{% ifversion ghec or ghes %} If you're creating the repository in an organization{% ifversion ghec %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %}{% endif %}{% ifversion fpt %} Repositories in organizations that use {% data variables.product.prodname_ghe_cloud %} can also be created with internal visibility. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" in the {% data variables.product.prodname_ghe_cloud %} documentation. +When you create a repository, you can choose to make the repository public or private.{% ifversion ghec or ghes %} If you're creating the repository in an organization{% ifversion ghec %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %}{% endif %}{% ifversion fpt %} Repositories in organizations that use {% data variables.product.prodname_ghe_cloud %} and are owned by an enterprise account can also be created with internal visibility. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories). {% elsif ghae %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index 78e9a37e7814..a8a463dce35a 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -1,10 +1,10 @@ --- -title: Criar um repositório -intro: Você pode criar um repositório na sua conta pessoal ou em qualquer organização onde tenha permissões suficientes. +title: Creating a new repository +intro: You can create a new repository on your personal account or any organization where you have sufficient permissions. redirect_from: - - /creating-a-repo/ - - /articles/creating-a-repository-in-an-organization/ - - /articles/creating-a-new-organization-repository/ + - /creating-a-repo + - /articles/creating-a-repository-in-an-organization + - /articles/creating-a-new-organization-repository - /articles/creating-a-new-repository - /articles/creating-an-internal-repository - /github/setting-up-and-managing-your-enterprise-account/creating-an-internal-repository @@ -19,39 +19,41 @@ versions: topics: - Repositories --- - {% tip %} -**Dica:** os proprietários podem restringir as permissões de criação de repositório em uma organização. Para obter mais informações, consulte "[Restringir a criação de repositórios na organização](/articles/restricting-repository-creation-in-your-organization)". +**Tip:** Owners can restrict repository creation permissions in an organization. For more information, see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)." {% endtip %} {% ifversion fpt or ghae or ghes or ghec %} {% tip %} -**Dica**: Você também pode criar um repositório usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`criar repositório gh`](https://cli.github.com/manual/gh_repo_create)" na documentação do {% data variables.product.prodname_cli %}. +**Tip**: You can also create a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} {% endif %} {% data reusables.repositories.create_new %} -2. Se desejar, para criar um repositório com a estrutura de diretório e arquivos de um repositório existente, use o menu suspenso **Choose a template** (Escolher um modelo) e selecione um repositório de modelo. Você verá repositórios de modelo que pertencem a você e às organizações das quais você é integrante ou que usou antes. Para obter mais informações, consulte "[Criar um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %} -3. Opcionalmente, se você escolheu usar um modelo para incluir a estrutura do diretório e arquivos de todos os branches no modelo, e não apenas o branch-padrão, selecione **Incluir todos os branches**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} -3. No menu suspenso Proprietário, selecione a conta na qual deseja criar o repositório.![Menu suspenso Owner (Proprietário)](/assets/images/help/repository/create-repository-owner.png) +2. Optionally, to create a repository with the directory structure and files of an existing repository, use the **Choose a template** drop-down and select a template repository. You'll see template repositories that are owned by you and organizations you're a member of or that you've used before. For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." + ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %} +3. Optionally, if you chose to use a template, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**. + ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +3. In the Owner drop-down, select the account you wish to create the repository on. + ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} -6. Se você não estiver usando um modelo, haverá um número de itens opcionais com os quais você pode preencher previamente o seu repositório. Se for importar um repositório existente para o {% data variables.product.product_name %}, não escolha qualquer uma destas opções, pois isso poderá criar um conflito de merge. É possível adicionar ou criar arquivos usando a interface de usuário ou optar por adicionar novos arquivos posteriormente usando a linha de comando. Para obter mais informações, consulte "[Importando um repositório do Git usando a linha de comando](/articles/importing-a-git-repository-using-the-command-line/), , "[Adicionando um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" e "[Resolvendo conflitos de merge](/articles/addressing-merge-conflicts/)". - - Você pode criar um README, que é um documento que descreve seu projeto. Para obter mais informações, consulte "[Sobre arquivos README](/articles/about-readmes/)". - - Você pode criar um arquivo *.gitignore*, que é um conjunto de regras com instruções para ignorar. Para obter mais informações, consulte "[Ignorar arquivos](/github/getting-started-with-github/ignoring-files)".{% ifversion fpt or ghec %} - - Você pode optar por adicionar uma licença de software para seu projeto. Para obter mais informações, consulte "[Licenciar um repositório](/articles/licensing-a-repository)".{% endif %} +6. If you're not using a template, there are a number of optional items you can pre-populate your repository with. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see "[Importing a Git repository using the command line](/articles/importing-a-git-repository-using-the-command-line/)," "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[Addressing merge conflicts](/articles/addressing-merge-conflicts/)." + - You can create a README, which is a document describing your project. For more information, see "[About READMEs](/articles/about-readmes/)." + - You can create a *.gitignore* file, which is a set of ignore rules. For more information, see "[Ignoring files](/github/getting-started-with-github/ignoring-files)."{% ifversion fpt or ghec %} + - You can choose to add a software license for your project. For more information, see "[Licensing a repository](/articles/licensing-a-repository)."{% endif %} {% data reusables.repositories.select-marketplace-apps %} {% data reusables.repositories.create-repo %} {% ifversion fpt or ghec %} -9. Na parte inferior da página Configuração rápida resultante, em "Import code from an old repository" (Importar código de um repositório antigo), você pode optar por importar um projeto para o novo repositório. Para isso, clique em **Import code** (Importar código). +9. At the bottom of the resulting Quick Setup page, under "Import code from an old repository", you can choose to import a project to your new repository. To do so, click **Import code**. {% endif %} -## Leia mais +## Further reading -- "[Gerenciar acessos aos repositórios da organização](/articles/managing-access-to-your-organization-s-repositories)" -- [Guias de código aberto](https://opensource.guide/){% ifversion fpt or ghec %} +- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)" +- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md index 33cc01b27f49..e5428dc4c829 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md @@ -1,9 +1,9 @@ --- -title: Criar um repositório somente com problemas -intro: 'O {% data variables.product.product_name %} não fornece permissões de acesso somente a problemas, mas você pode fazer isso usando um segundo repositório que contenha apenas os problemas.' +title: Creating an issues-only repository +intro: '{% data variables.product.product_name %} does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.' redirect_from: - - /articles/issues-only-access-permissions/ - - /articles/is-there-issues-only-access-to-organization-repositories/ + - /articles/issues-only-access-permissions + - /articles/is-there-issues-only-access-to-organization-repositories - /articles/creating-an-issues-only-repository - /github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository @@ -14,14 +14,13 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Repositório exclusivo para problemas +shortTitle: Issues-only repository --- +1. Create a **private** repository to host the source code from your project. +2. Create a second repository with the permissions you desire to host the issue tracker. +3. Add a README file to the issues repository explaining the purpose of this repository and linking to the issues section. +4. Set your collaborators or teams to give access to the repositories as you desire. -1. Crie um repositório **privado** para hospedar o código-fonte do seu projeto. -2. Crie um segundo repositório com as permissões que deseja para hospedar o rastreador de problema. -3. Adicione um arquivo README ao repositório de problemas explicando a finalidade desse repositório e vinculando-o à seção de problemas. -4. Defina colaboradores ou equipes para fornecer acesso aos repositórios conforme desejado. +Users with write access to both can reference and close issues back and forth across the repositories, but those without the required permissions will see references that contain a minimum of information. -Os usuários com acesso de gravação a ambos podem fazer referência e fechar problemas nos repositórios, mas aqueles sem as permissões necessárias verão referências que contêm informações mínimas. - -Por exemplo, se você fizesse push de um commit no branch padrão do repositório privado com a mensagem `Fixes organization/public-repo#12`, o problema seria fechado, mas apenas os usuários com as permissões adequadas veriam a referência entre repositórios indicando o commit que fechou o problema. Sem as permissões, uma referência continua aparecendo, mas os detalhes são omitidos. +For example, if you pushed a commit to the private repository's default branch with a message that read `Fixes organization/public-repo#12`, the issue would be closed, but only users with the proper permissions would see the cross-repository reference indicating the commit that closed the issue. Without the permissions, a reference still appears, but the details are omitted. diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md index 5fb2fd7aeae8..f9f2013c0c68 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md @@ -2,8 +2,8 @@ title: Deleting a repository intro: You can delete any repository or fork if you're either an organization owner or have admin permissions for the repository or fork. Deleting a forked repository does not delete the upstream repository. redirect_from: - - /delete-a-repo/ - - /deleting-a-repo/ + - /delete-a-repo + - /deleting-a-repo - /articles/deleting-a-repository - /github/administering-a-repository/deleting-a-repository - /github/administering-a-repository/managing-repository-settings/deleting-a-repository diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md index ce80f6e4c471..0cbb49c85b6e 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md @@ -1,8 +1,8 @@ --- -title: Duplicar um repositório -intro: 'Para manter um espelho de um repositório sem a bifurcação, é possível executar um comando especial de clone e, em seguida, fazer push do espelho para o novo repositório.' +title: Duplicating a repository +intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.' redirect_from: - - /articles/duplicating-a-repo/ + - /articles/duplicating-a-repo - /articles/duplicating-a-repository - /github/creating-cloning-and-archiving-repositories/duplicating-a-repository - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/duplicating-a-repository @@ -14,92 +14,91 @@ versions: topics: - Repositories --- - -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec %} {% note %} -**Observação:** Se você tem um projeto hospedado em outro sistema de controle de versão, você poderá importar automaticamente seu projeto para {% data variables.product.prodname_dotcom %} usando a ferramenta Importador de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre o importador de {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)." +**Note:** If you have a project hosted on another version control system, you can automatically import your project to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_dotcom %} Importer tool. For more information, see "[About {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)." {% endnote %} {% endif %} -Antes de fazer push do repositório original para sua nova cópia ou _espelho_ do repositório, você deverá [criar o novo repositório](/articles/creating-a-new-repository) em {% data variables.product.product_location %}. Nesses exemplos, `exampleuser/new-repository` ou `exampleuser/mirrored` são os espelhos. +Before you can push the original repository to your new copy, or _mirror_, of the repository, you must [create the new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. In these examples, `exampleuser/new-repository` or `exampleuser/mirrored` are the mirrors. -## Espelhar um repositório +## Mirroring a repository {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crie um clone bare do repositório. +2. Create a bare clone of the repository. ```shell $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git ``` -3. Faça espelhamento/push no novo repositório. +3. Mirror-push to the new repository. ```shell $ cd old-repository $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` -4. Remova o repositório local temporário que você criou anteriormente. +4. Remove the temporary local repository you created earlier. ```shell $ cd .. $ rm -rf old-repository ``` -## Espelhar um repositório que contém objetos do {% data variables.large_files.product_name_long %} +## Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crie um clone bare do repositório. Substitua o exemplo de nome de usuário pelo nome da pessoa ou da organização a quem pertence o repositório e substitua o exemplo de nome de repositório pelo nome do repositório que você deseja duplicar. +2. Create a bare clone of the repository. Replace the example username with the name of the person or organization who owns the repository, and replace the example repository name with the name of the repository you'd like to duplicate. ```shell $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git ``` -3. Navegue até o repositório que você acabou de clonar. +3. Navigate to the repository you just cloned. ```shell $ cd old-repository ``` -4. Extraia os objetos do {% data variables.large_files.product_name_long %} do repositório. +4. Pull in the repository's {% data variables.large_files.product_name_long %} objects. ```shell $ git lfs fetch --all ``` -5. Faça espelhamento/push no novo repositório. +5. Mirror-push to the new repository. ```shell $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` -6. Faça push nos objetos do {% data variables.large_files.product_name_long %} do repositório no seu espelho. +6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror. ```shell $ git lfs push --all https://github.com/exampleuser/new-repository.git ``` -7. Remova o repositório local temporário que você criou anteriormente. +7. Remove the temporary local repository you created earlier. ```shell $ cd .. $ rm -rf old-repository ``` -## Espelhar um repositório em outro local +## Mirroring a repository in another location -Se você deseja espelhar um repositório em outro local e ainda obter atualizações do original, é possível clonar um espelho e fazer push das alterações periodicamente. +If you want to mirror a repository in another location, including getting updates from the original, you can clone a mirror and periodically push the changes. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crie um clone bare espelhado do repositório. +2. Create a bare mirrored clone of the repository. ```shell $ git clone --mirror https://{% data variables.command_line.codeblock %}/exampleuser/repository-to-mirror.git ``` -3. Defina o local de push no espelho. +3. Set the push location to your mirror. ```shell $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` -Assim como um clone bare, um clone espelhado inclui todos os branches remotes e tags, mas todas as referências locais serão substituídas todas as vezes que você fizer fetch, assim ele sempre será o mesmo do repositório original. O push no espelho é simplificado pela configuração da URL para pushes. +As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror. -4. Para atualizar o espelho, obtenha atualizações e faça push. +4. To update your mirror, fetch updates and push. ```shell $ git fetch -p origin $ git push --mirror ``` -{% ifversion fpt or ghec %} -## Leia mais +{% ifversion fpt or ghec %} +## Further reading -* "[Enviando por push as alterações para o GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" -* "[Sobre o armazenamento de arquivos grandes do Git e do GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" -* "[Sobre o Importador do GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)" +* "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" +* "[About Git Large File Storage and GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" +* "[About GitHub Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)" {% endif %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index 651ec1b4dddc..82edf7150d69 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -2,15 +2,15 @@ title: Transferring a repository intro: You can transfer repositories to other users or organization accounts. redirect_from: - - /articles/about-repository-transfers/ - - /move-a-repo/ - - /moving-a-repo/ - - /articles/what-is-transferred-with-a-repository/ - - /articles/what-is-transferred-with-a-repo/ - - /articles/how-to-transfer-a-repo/ - - /articles/how-to-transfer-a-repository/ - - /articles/transferring-a-repository-owned-by-your-personal-account/ - - /articles/transferring-a-repository-owned-by-your-organization/ + - /articles/about-repository-transfers + - /move-a-repo + - /moving-a-repo + - /articles/what-is-transferred-with-a-repository + - /articles/what-is-transferred-with-a-repo + - /articles/how-to-transfer-a-repo + - /articles/how-to-transfer-a-repository + - /articles/transferring-a-repository-owned-by-your-personal-account + - /articles/transferring-a-repository-owned-by-your-organization - /articles/transferring-a-repository - /github/administering-a-repository/transferring-a-repository - /github/administering-a-repository/managing-repository-settings/transferring-a-repository diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 0371d81e6233..d5d45325ef68 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -2,7 +2,7 @@ title: About code owners intro: You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository. redirect_from: - - /articles/about-codeowners/ + - /articles/about-codeowners - /articles/about-code-owners - /github/creating-cloning-and-archiving-repositories/about-code-owners - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md index a6ad2effcdc7..bd1c73488fae 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md @@ -2,8 +2,8 @@ title: About READMEs intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.' redirect_from: - - /articles/section-links-on-readmes-and-blob-pages/ - - /articles/relative-links-in-readmes/ + - /articles/section-links-on-readmes-and-blob-pages + - /articles/relative-links-in-readmes - /articles/about-readmes - /github/creating-cloning-and-archiving-repositories/about-readmes - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md index db6e6b8c3c0e..be5c459c904f 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md @@ -1,12 +1,12 @@ --- -title: Sobre linguagens do repositório -intro: Os arquivos e diretórios em um repositório determinam as linguagens que compõem o repositório. É possível exibir linguagens de um repositório para obter uma visão geral rápida do repositório. +title: About repository languages +intro: The files and directories within a repository determine the languages that make up the repository. You can view a repository's languages to get a quick overview of the repository. redirect_from: - - /articles/my-repository-is-marked-as-the-wrong-language/ - - /articles/why-isn-t-my-favorite-language-recognized/ - - /articles/my-repo-is-marked-as-the-wrong-language/ - - /articles/why-isn-t-sql-recognized-as-a-language/ - - /articles/why-isn-t-my-favorite-language-recognized-by-github/ + - /articles/my-repository-is-marked-as-the-wrong-language + - /articles/why-isn-t-my-favorite-language-recognized + - /articles/my-repo-is-marked-as-the-wrong-language + - /articles/why-isn-t-sql-recognized-as-a-language + - /articles/why-isn-t-my-favorite-language-recognized-by-github - /articles/about-repository-languages - /github/creating-cloning-and-archiving-repositories/about-repository-languages - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-languages @@ -17,14 +17,13 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Linguagens do repositório +shortTitle: Repository languages --- +{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to +determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch. -{% data variables.product.product_name %} usa [Biblioteca Linguist](https://github.com/github/linguist) a de código aberto para -determinar as linguagens de arquivo para destacar a sintaxe e estatísticas do repositório. As estatísticas da linguagem serão atualizadas após você fazer push de alterações no seu branch-padrão. +Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) for help. -Alguns arquivos são difíceis de identificar e, às vezes, os projetos contêm mais arquivos de fornecedor e biblioteca do que código primário. Se estiver recebendo resultados incorretos, consulte o [guia de solução de problemas](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) do Linguist para obter ajuda. +## Markup languages -## Linguagens markup - -As linguagens markup são renderizadas para HTML e exibidas em linha usando nossa [Biblioteca de markup](https://github.com/github/markup) de código aberto. Neste momento, não estamos aceitando novas linguagens markup a serem mostradas no {% data variables.product.product_name %}. No entanto, mantemos de maneira ativa nossas linguagens markup atuais. Em caso de dificuldades, [crie um problema](https://github.com/github/markup/issues/new). +Markup languages are rendered to HTML and displayed inline using our open-source [Markup library](https://github.com/github/markup). At this time, we are not accepting new markup languages to show within {% data variables.product.product_name %}. However, we do actively maintain our current markup languages. If you see a problem, [please create an issue](https://github.com/github/markup/issues/new). diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index 2aa2f07f4f11..48c0c4d4bf27 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -2,7 +2,7 @@ title: Classifying your repository with topics intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.' redirect_from: - - /articles/about-topics/ + - /articles/about-topics - /articles/classifying-your-repository-with-topics - /github/administering-a-repository/classifying-your-repository-with-topics - /github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 91a7485326f5..3ac3c54bdd02 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -1,8 +1,8 @@ --- -title: Licenciar um repositório -intro: 'Os repositórios públicos no GitHub são usados frequentemente para compartilhar softwares de código aberto. Para que seu repositório seja realmente de código aberto, você precisará licenciá-lo para que outros tenham a liberdade de usar, alterar e distribuir o software.' +title: Licensing a repository +intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.' redirect_from: - - /articles/open-source-licensing/ + - /articles/open-source-licensing - /articles/licensing-a-repository - /github/creating-cloning-and-archiving-repositories/licensing-a-repository - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository @@ -13,86 +13,86 @@ versions: topics: - Repositories --- - ## Escolher a licença ideal +## Choosing the right license -Nós criamos o [choosealicense.com](https://choosealicense.com), para ajudá-lo a compreender como licenciar seu código. Uma licença de software descreve o que pode e não pode ser feito com seu código-fonte, assim é importante tomar uma decisão fundamentada. +We created [choosealicense.com](https://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision. -Você não tem qualquer obrigação de escolher uma licença. Entretanto, sem uma licença, são aplicadas as leis padrão de copyright, o que significa que você detém todos os direitos de seu código-fonte e ninguém poderá reproduzir, distribuir ou criar derivativos de seu trabalho. Se você está criando um projeto de código aberto, incentivamos fortemente que você contemple uma licença de código aberto. O [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) (Guia de código aberto) apresenta orientações adicionais para a escolha da licença correta para seu projeto. +You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) provides additional guidance on choosing the correct license for your project. {% note %} -**Observação:** Se você publicar seu código-fonte em um repositório público em {% data variables.product.product_name %}, {% ifversion fpt or ghec %}de acordo com os [Termos de Serviço](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}outros usuários de {% data variables.product.product_location %} terão o direito de visualizar e bifurcar o seu repositório. Se você já criou um repositório e não quer mais que os usuários tenham acesso a ele, você pode torná-lo privado. Ao alterar a visibilidade de um repositório para privado, as bifurcações existentes ou cópias locais criadas por outros usuários continuarão existindo. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)". +**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.product.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." {% endnote %} -## Identificar a localização da sua licença +## Determining the location of your license -A maioria das pessoas coloca seu texto de licença em um arquivo denominado `LICENSE.txt` (ou `LICENSE.rst` ou `LICENSE.rst`) na raiz do repositório; [aqui está um exemplo do Hubot](https://github.com/github/hubot/blob/master/LICENSE.md). +Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md` or `LICENSE.rst`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md). -Alguns projetos incluem as informações sobre a licença no README. Por exemplo, um README de um projeto pode incluir uma observação declarando "Este projeto está licenciado nos termos da licença MIT." +Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license." -Como uma prática recomendada, incentivamos que você inclua o arquivo da licença no seu projeto. +As a best practice, we encourage you to include the license file with your project. -## Pesquisar no GitHub por tipo de licença +## Searching GitHub by license type -É possível filtrar repositórios com base nas licenças ou família de licenças deles usando o qualificador `license` (licença) e a palavra-chave exata da licença: +You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword: -| Licença | Palavra-chave da licença | -| ------- | ---------------------------------------------------------------- | -| | Licença Academic Free v3.0 | `afl-3.0` | -| | Licença Apache 2.0 | `apache-2.0` | -| | Licença Artistic 2.0 | `artistic-2.0` | -| | Licença Boost Software 1.0 | `bsl-1.0` | -| | Licença "simplificada" BSD 2-clause | `bsd-2-clause` | -| | Licença "nova" ou "revisada" BSD 3-clause | `bsd-3-clause` | -| | Licença BSD 3-clause Clear | `bsd-3-clause-clear` | -| | Família de licenças Creative Commons | `cc` | -| | Creative Commons Zero v1.0 Universal | `cc0-1.0` | -| | Creative Commons Attribution 4.0 | `cc-by-4.0` | -| | Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` | -| | Licença Do What The F*ck You Want To Public | `wtfpl` | -| | Licença Educational Community v2.0 | `ecl-2.0` | -| | Licença Pública Eclipse 1.0 | `epl-1.0` | -| | Licença Pública Eclipse 2.0 | `epl-2.0` | -| | Licença Pública da União Europeia 1.1 | `eupl-1.1` | -| | Licença Pública Geral Affero GNU v3.0 | `agpl-3.0` | -| | Família de Licença Pública Geral GNU | `gpl` | -| | Licença Pública Geral GNU v2.0 | `gpl-2.0` | -| | Licença Pública Geral GNU v3.0 | `gpl-3.0` | -| | Família de Licença Pública Geral Menor GNU | `lgpl` | -| | Licença Pública Geral Menor GNU v2.1 | `lgpl-2.1` | -| | Licença Pública Geral Menor GNU v3.0 | `lgpl-3.0` | -| | ISC | `isc` | -| | Licença Pública do Projeto LaTeX v1.3c | `lppl-1.3c` | -| | Licença Pública Microsoft | `ms-pl` | -| | MIT | `mit` | -| | Licença Pública Mozilla 2.0 | `mpl-2.0` | -| | Licença Open Software 3.0 | `osl-3.0` | -| | Licença PostgreSQL | `postgresql` | -| | Licença de fonte Aberta do SIL 1.1 | `ofl-1.1` | -| | Licença de Código Aberto da University of Illinois/NCSA | `ncsa` | -| | The Unlicense | `unlicense` | -| | Licença zLib | `zlib` | +License | License keyword +--- | --- +| Academic Free License v3.0 | `afl-3.0` | +| Apache license 2.0 | `apache-2.0` | +| Artistic license 2.0 | `artistic-2.0` | +| Boost Software License 1.0 | `bsl-1.0` | +| BSD 2-clause "Simplified" license | `bsd-2-clause` | +| BSD 3-clause "New" or "Revised" license | `bsd-3-clause` | +| BSD 3-clause Clear license | `bsd-3-clause-clear` | +| Creative Commons license family | `cc` | +| Creative Commons Zero v1.0 Universal | `cc0-1.0` | +| Creative Commons Attribution 4.0 | `cc-by-4.0` | +| Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` | +| Do What The F*ck You Want To Public License | `wtfpl` | +| Educational Community License v2.0 | `ecl-2.0` | +| Eclipse Public License 1.0 | `epl-1.0` | +| Eclipse Public License 2.0 | `epl-2.0` | +| European Union Public License 1.1 | `eupl-1.1` | +| GNU Affero General Public License v3.0 | `agpl-3.0` | +| GNU General Public License family | `gpl` | +| GNU General Public License v2.0 | `gpl-2.0` | +| GNU General Public License v3.0 | `gpl-3.0` | +| GNU Lesser General Public License family | `lgpl` | +| GNU Lesser General Public License v2.1 | `lgpl-2.1` | +| GNU Lesser General Public License v3.0 | `lgpl-3.0` | +| ISC | `isc` | +| LaTeX Project Public License v1.3c | `lppl-1.3c` | +| Microsoft Public License | `ms-pl` | +| MIT | `mit` | +| Mozilla Public License 2.0 | `mpl-2.0` | +| Open Software License 3.0 | `osl-3.0` | +| PostgreSQL License | `postgresql` | +| SIL Open Font License 1.1 | `ofl-1.1` | +| University of Illinois/NCSA Open Source License | `ncsa` | +| The Unlicense | `unlicense` | +| zLib License | `zlib` | -Quando você pesquisar uma família de licenças, os resultados incluirão todas as licenças daquela família. Por exemplo, quando você usa a consulta `license:gpl`, seus resultados incluirão repositórios licenciados sob a Licença Pública Geral GNU v2.0 e Licença Pública Geral GNU v3.0. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories/#search-by-license)". +When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)." -## Identificar uma licença +## Detecting a license -[A licenciada de código aberto Ruby gem ](https://github.com/licensee/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/rest/reference/licenses) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](https://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). -Caso o seu repositório use uma licença listada no site Choose a License que não aparece na parte superior da página do repositório, ele pode conter licenças múltiplas ou outras complexidades. Para que sua licença seja detectada, simplifique o arquivo *LICENSE* e anote a complexidade em algum outro local, como no arquivo *README* do repositório. +If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file. -## Aplicar uma licença em um repositório com uma licença existente +## Applying a license to a repository with an existing license -O selecionador de licenças somente está disponível quando você cria um novo projeto no GitHub. Você pode adicionar uma licença manualmente usando o navegador. Para obter mais informações sobre adicionar uma licença em um repositório, consulte "[Adicionar uma licença em um repositório](/articles/adding-a-license-to-a-repository)". +The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)." -![Captura de tela do selecionador de licenças no GitHub.com](/assets/images/help/repository/repository-license-picker.png) +![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png) -## Isenção de responsabilidade +## Disclaimer -O objetivo das iniciativas de licenciamento de código aberto do GitHub é oferecer um ponto de partida para ajudar você a tomar uma decisão fundamentada. O GitHub apresenta informações sobre licenças para ajudar os usuários a conseguir informações sobre licenças de código aberto e sobre os projetos que as usam. Esperamos que seja útil, mas esteja ciente de que não somos advogados e que cometemos erros como qualquer pessoa. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. Se você tiver quaisquer dúvidas com relação à licença ideal para seu código ou quaisquer outras questões legais relacionadas a ele, sempre é melhor consultar um profissional. +The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional. -## Leia mais +## Further reading -- Seção do Open Source Guide (Guia de código aberto) "[O aspecto legal do código aberto](https://opensource.guide/legal/)"{% ifversion fpt or ghec %} +- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% ifversion fpt or ghec %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md index e65c79b35991..0181b7ae84e7 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -1,10 +1,10 @@ --- -title: Gerenciando as configurações de segurança e análise do seu repositório -intro: 'Você pode controlar recursos que protegem e analisam o código em seu projeto no {% data variables.product.prodname_dotcom %}.' +title: Managing security and analysis settings for your repository +intro: 'You can control features that secure and analyze the code in your project on {% data variables.product.prodname_dotcom %}.' permissions: People with admin permissions to a repository can manage security and analysis settings for the repository. redirect_from: - - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories/ - - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories/ + - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories + - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization - /github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository @@ -22,23 +22,23 @@ topics: - Dependency graph - Secret scanning - Repositories -shortTitle: Segurança & análise +shortTitle: Security & analysis --- - {% ifversion fpt or ghec %} -## Habilitar ou desabilitar funcionalidades de segurança e análise para repositórios públicos +## Enabling or disabling security and analysis features for public repositories -É possível gerenciar um subconjunto de recursos de segurança e análise para repositórios públicos. Outros recursos são habilitados permanentemente, incluindo gráfico de dependências e varredura de segredo. +You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" em um repositório público](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. + !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) {% endif %} -## Habilitar ou desabilitar os recursos de segurança e análise{% ifversion fpt or ghec %} para repositórios privados{% endif %} +## Enabling or disabling security and analysis features{% ifversion fpt or ghec %} for private repositories{% endif %} -´Você pode administrar as funcionalidades de segurança e análise para o seu repositório{% ifversion fpt or ghec %}privado ou interno {% endif %}.{% ifversion fpt or ghes or ghec %} Se a sua organização pertencer a uma empresa que tem uma licença para {% data variables.product.prodname_GH_advanced_security %}, haverá opções adicionais disponíveis. {% data reusables.advanced-security.more-info-ghas %}{% endif %} +You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion fpt or ghes or ghec %} If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %}{% endif %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -46,74 +46,77 @@ shortTitle: Segurança & análise {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} {% ifversion fpt or ghes > 3.0 or ghec %} -4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion fpt or ghec %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% elsif ghes > 3.2 %} -!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% else %} -!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %} +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion fpt or ghec %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% elsif ghes > 3.2 %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% else %} + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %} {% note %} - **Observação:** Se você desabilitar {% data variables.product.prodname_GH_advanced_security %}, {% ifversion fpt or ghec %}revisão de dependência, {% endif %}{% data variables.product.prodname_secret_scanning %} e {% data variables.product.prodname_code_scanning %} ficarão desabilitados. Todos os fluxos de trabalho, uploads de SARIF, ou chamadas de API para {% data variables.product.prodname_code_scanning %} falharão. + **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion fpt or ghec %}dependency review, {% endif %}{% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. {% endnote %} {% endif %} {% ifversion ghes = 3.0 %} -4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. + !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) {% endif %} {% ifversion ghae %} -4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. Antes de poder habilitar "{% data variables.product.prodname_secret_scanning %}" no seu repositório, talvez seja necessário habilitar {% data variables.product.prodname_GH_advanced_security %}. ![Habilite ou desabilite {% data variables.product.prodname_GH_advanced_security %} ou {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png) +4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. Before you can enable "{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}. + ![Enable or disable {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png) {% endif %} -## Conceder acesso aos alertas de segurança +## Granting access to security alerts -Depois de habilitar alertas de {% ifversion not ghae %}{% data variables.product.prodname_dependabot %} ou {% endif %}{% data variables.product.prodname_secret_scanning %} de um repositório na organização, os proprietários da organização e administradores de repositórios poderão visualizar os alertas por padrão. Você pode dar acesso a outras equipes e pessoas aos alertas de um repositório. +After you enable {% ifversion not ghae %}{% data variables.product.prodname_dependabot %} or {% endif %}{% data variables.product.prodname_secret_scanning %} alerts for a repository in an organization, organization owners and repository administrators can view the alerts by default. You can give additional teams and people access to the alerts for a repository. {% note %} -Os proprietários da organização e os administradores do repositório só podem conceder acesso para ver os alertas de segurança como, por exemplo, alertas de {% data variables.product.prodname_secret_scanning %} para pessoas ou equipes que têm acesso de gravação no repositório. +Organization owners and repository administrators can only grant access to view security alerts, such as {% data variables.product.prodname_secret_scanning %} alerts, to people or teams who have write access to the repo. {% endnote %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Acesso aos alertas", no campo de pesquisa, comece a digitar o nome da pessoa ou equipe que você gostaria de encontrar e, em seguida, clique em um nome na lista de correspondências. +4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. {% ifversion fpt or ghec or ghes > 3.2 %} - ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) {% endif %} {% ifversion ghes < 3.3 %} - ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png) + ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png) {% endif %} {% ifversion ghae %} - ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png) + ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png) {% endif %} - -5. Clique em **Save changes** (Salvar alterações). + +5. Click **Save changes**. {% ifversion fpt or ghes > 3.2 or ghec %} - ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) + !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) {% endif %} {% ifversion ghes < 3.3 %} - ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png) + !["Save changes" button for changes to security alert settings](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png) {% endif %} {% ifversion ghae %} - ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png) + !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png) {% endif %} -## Remover o acesso aos alertas de segurança +## Removing access to security alerts {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Acesso aos alertas", à direita da pessoa ou da equipe cujo acesso você deseja remover, clique em {% octicon "x" aria-label="X symbol" %}. - {% ifversion fpt or ghec or ghes > 3.2 %} - ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}. + {% ifversion fpt or ghec or ghes > 3.2 %} + !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) {% endif %} {% ifversion ghes < 3.3 %} - ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png) + !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png) {% endif %} {% ifversion ghae %} - ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png) + !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png) {% endif %} - 5. Clique em **Save changes** (Salvar alterações). + 5. Click **Save changes**. -## Leia mais +## Further reading -- "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)" -- "[Gerenciando configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" +- "[Securing your repository](/code-security/getting-started/securing-your-repository)" +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 9a40def4b8db..67c8fece2013 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -3,9 +3,9 @@ title: About email notifications for pushes to your repository intro: You can choose to automatically send email notifications to a specific email address when anyone pushes to the repository. permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository. redirect_from: - - /articles/managing-notifications-for-pushes-to-a-repository/ - - /articles/receiving-email-notifications-for-pushes-to-a-repository/ - - /articles/about-email-notifications-for-pushes-to-your-repository/ + - /articles/managing-notifications-for-pushes-to-a-repository + - /articles/receiving-email-notifications-for-pushes-to-a-repository + - /articles/about-email-notifications-for-pushes-to-your-repository - /github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository - /github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository - /github/administering-a-repository/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index 1841cf3ab957..60c27fc3591c 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -2,9 +2,9 @@ title: Setting repository visibility intro: You can choose who can view your repository. redirect_from: - - /articles/making-a-private-repository-public/ - - /articles/making-a-public-repository-private/ - - /articles/converting-a-public-repo-to-a-private-repo/ + - /articles/making-a-private-repository-public + - /articles/making-a-public-repository-private + - /articles/converting-a-public-repo-to-a-private-repo - /articles/setting-repository-visibility - /github/administering-a-repository/setting-repository-visibility - /github/administering-a-repository/managing-repository-settings/setting-repository-visibility diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md index d5493c5582b5..b4e5fce59be8 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md @@ -1,9 +1,9 @@ --- -title: Sobre as versões -intro: 'Você pode criar uma versão de modo a empacotar software, com notas de versão e links para arquivos binários, para uso de outras pessoas.' +title: About releases +intro: 'You can create a release to package software, along with release notes and links to binary files, for other people to use.' redirect_from: - - /articles/downloading-files-from-the-command-line/ - - /articles/downloading-files-with-curl/ + - /articles/downloading-files-from-the-command-line + - /articles/downloading-files-with-curl - /articles/about-releases - /articles/getting-the-download-count-for-your-releases - /github/administering-a-repository/getting-the-download-count-for-your-releases @@ -17,50 +17,42 @@ versions: topics: - Repositories --- - -## Sobre as versões +## About releases {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %} -![Uma visão geral de versões](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) +![An overview of releases](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) {% elsif ghes > 3.3 or ghae-issue-4972 %} -![Uma visão geral de versões](/assets/images/help/releases/releases-overview-with-contributors.png) +![An overview of releases](/assets/images/help/releases/releases-overview-with-contributors.png) {% else %} -![Uma visão geral de versões](/assets/images/help/releases/releases-overview.png) +![An overview of releases](/assets/images/help/releases/releases-overview.png) {% endif %} -Versões são iterações de software implementáveis que você pode empacotar e disponibilizar para um público mais amplo para baixar e usar. +Releases are deployable software iterations you can package and make available for a wider audience to download and use. -As versões se baseiam em [tags Git](https://git-scm.com/book/en/Git-Basics-Tagging), que marcam um ponto específico no histórico do seu repositório. Uma data de tag pode ser diferente de uma data de versão, já que elas podem ser criadas em momentos diferentes. Para obter mais informações sobre como visualizar as tags existentes, consulte "[Visualizar tags e versões do seu repositório](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)". +Releases are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging), which mark a specific point in your repository's history. A tag date may be different than a release date since they can be created at different times. For more information about viewing your existing tags, see "[Viewing your repository's releases and tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)." -Você pode receber notificações quando novas versões são publicadas em um repositório sem receber notificações sobre outras atualizações para o repositório. Para obter mais informações, consulte {% ifversion fpt or ghae or ghes or ghec %}"[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Inspecionando e desinspecionando versões para um repositório](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}." +You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching releases for a repository](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}." -Qualquer pessoa com acesso de leitura a um repositório pode ver e comparar versões, mas somente pessoas com permissões de gravação a um repositório podem gerenciar versões. Para obter mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)." +Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)." {% ifversion fpt or ghec %} -Você pode criar notas de versão manualmente enquanto gerencia uma versão. Como alternativa, você pode gerar automaticamente notas de versão a partir de um modelo padrão, ou personalizar seu próprio modelo de notas de versão. Para obter mais informações, consulte "[Notas de versão geradas automaticamente](/repositories/releasing-projects-on-github/automatically-generated-release-notes)". - -Pessoas com permissões de administrador para um repositório podem escolher se objetos {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte " - -[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

+You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)." +People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} {% ifversion fpt or ghec %} +If a release fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -Se uma versão consertar uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório. {% data variables.product.prodname_dotcom %} revisa a cada consultoria de segurança publicado e pode usá-lo para enviar {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)." - -Você pode visualizar a aba **Dependentes** do gráfico de dependências para ver quais repositórios e pacotes dependem do código no repositório e pode, portanto, ser afetado por uma nova versão. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". - +You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} -Você também pode usar a API de Releases para reunir informações, tais como o número de vezes que as pessoas baixam um ativo de versão. Para obter mais informações, consulte "[Versões](/rest/reference/repos#releases)". +You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)." {% ifversion fpt or ghec %} +## Storage and bandwidth quotas - -## Cotas de armazenamento e banda - -Cada arquivo incluído em uma versão deve ser inferior a {% data variables.large_files.max_file_size %}. Não há limite para o tamanho total de uma versão, nem uso de largura de banda. + Each file included in a release must be under {% data variables.large_files.max_file_size %}. There is no limit on the total size of a release, nor bandwidth usage. {% endif %} diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md index cc1fc75a3ec2..feb05945b223 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md @@ -1,9 +1,9 @@ --- -title: Lançando projetos no GitHub -intro: 'Você pode criar uma versão de modo a empacotar software, notas de versão e arquivos binários para outras pessoas baixarem.' +title: Releasing projects on GitHub +intro: 'You can create a release to package software, release notes, and binary files for other people to download.' redirect_from: - - /categories/85/articles/ - - /categories/releases/ + - /categories/85/articles + - /categories/releases - /github/administering-a-repository/releasing-projects-on-github versions: fpt: '*' @@ -21,6 +21,6 @@ children: - /comparing-releases - /automatically-generated-release-notes - /automation-for-release-forms-with-query-parameters -shortTitle: Projetos de versão +shortTitle: Release projects --- diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index d7ecf752a3c7..eff47a5b08ca 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -1,9 +1,9 @@ --- -title: Gerenciar versões em repositórios -intro: Você pode criar versões para empacotar e entregar iterações de um projeto para os usuários. +title: Managing releases in a repository +intro: You can create releases to bundle and deliver iterations of a project to users. redirect_from: - /articles/creating-releases - - /articles/listing-and-editing-releases/ + - /articles/listing-and-editing-releases - /articles/editing-and-deleting-releases - /articles/managing-releases-in-a-repository - /github/administering-a-repository/creating-releases @@ -18,113 +18,71 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Gerenciar versões +shortTitle: Manage releases --- - {% ifversion fpt or ghes > 3.0 or ghae or ghec %} -## Sobre o gerenciamento da versão +## About release management -Você pode criar novas versões com observações de versões, @menções de contribuidores e links para arquivos binários, bem como editar ou excluir versões existentes. +You can create new releases with release notes, @mentions of contributors, and links to binary files, as well as edit or delete existing releases. {% ifversion fpt or ghec %} -Você também pode publicar uma ação a partir de uma versão específica em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "Publicar uma ação no {% data variables.product.prodname_marketplace %}" - -Você pode escolher se objetos {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte " - -[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

+You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see "Publishing an action in the {% data variables.product.prodname_marketplace %}." +You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} - - - {% endif %} - - -## Criando uma versão +## Creating a release {% include tool-switcher %} {% webui %} {% data reusables.repositories.navigate-to-repo %} - - - {% data reusables.repositories.releases %} +3. Click **Draft a new release**. -3. Clique em **Draft a new release** (Rascunhar uma nova versão). - {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %} +4. {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}, and press **Enter**{% endif %}. Alternatively, select an existing tag. -4. {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}, and press **Enter**{% endif %}. Como alternativa, selecione um tag existente. - - {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Insira uma tag](/assets/images/help/releases/releases-tag-create.png) + {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Enter a tag](/assets/images/help/releases/releases-tag-create.png) +5. If you are creating a new tag, click **Create new tag**. -5. Se você estiver criando uma nova tag, clique em **Criar nova tag**. - - ![Confirme que você deseja criar uma nova tag](/assets/images/help/releases/releases-tag-create-confirm.png) - + ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} - - ![Versão com tag das versões](/assets/images/enterprise/releases/releases-tag-version.png) - - {% endif %} + ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png) +{% endif %} +5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. -5. Se você criou uma nova tag, use o menu suspenso para selecionar o branch que contém o projeto que você deseja liberar. - - {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Escolha um branch](/assets/images/help/releases/releases-choose-branch.png) - + {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %} - -6. Digite um título e uma descrição para a sua versão. - +6. Type a title and description for your release. {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} - - - Se você @mencionar qualquer usuário de {% data variables.product.product_name %} na descrição, a versão publicada incluirá uma seção de **Colaboradores** com uma lista de avatar de todos os usuários mencionados. - + If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users. {%- endif %} - - - - {% ifversion fpt or ghec %} Como alternativa, você pode gerar automaticamente as suas observações de versão, clicando em **Gerar observações de versão automaticamente**. - + {% ifversion fpt or ghec %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**. {% endif %} - - ![Descrição das versões](/assets/images/help/releases/releases_description_auto.png) - -7. Opcionalmente, para incluir arquivos binários, como programas compilados em sua versão, arraste e solte ou selecione arquivos manualmente na caixa de binários. ![Fornecer um DMG com a versão](/assets/images/help/releases/releases_adding_binary.gif) + ![Releases description](/assets/images/help/releases/releases_description_auto.png) +7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box. + ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif) +8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**. + ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png) +{%- ifversion fpt or ghec %} +1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. + ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**. + ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png) -8. Para notificar os usuários que a versão não está pronta para produção e pode ser instável, selecione **This is a pre-release** (Esta é uma versão prévia). ![Caixa de seleção para marcar uma versão como pré-versão](/assets/images/help/releases/prerelease_checkbox.png) - - {%- ifversion fpt or ghec %} - -1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Caixa de seleção para criar uma discussão de versão e menu suspenso para escolher uma categoria](/assets/images/help/releases/create-release-discussion.png) - - {%- endif %} - -9. Se estiver pronto para tornar pública a sua versão, clique em **Publish release** (Publicar versão). Para trabalhar na versão posteriormente, clique em **Save draft** (Salvar rascunho). ![Botões Publish release (Publicar versão) e Draft release (Rascunhar versão)](/assets/images/help/releases/release_buttons.png) - {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 or ghae-issue-4974 %} + You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Viewing your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)." - - Você pode visualizar as suas versões publicadas ou rascunhos no feed de versões do seu repositório. Para obter mais informações, consulte "[Visualizando versões e tags do seu repositório](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags). - {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %} - - - ![Versão publicada com contribuidores @mencionados](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) - + ![Published release with @mentioned contributors](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) {% else %} - - ![Versão publicada com contribuidores @mencionados](/assets/images/help/releases/releases-overview-with-contributors.png) - + ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png) {% endif %} - - - {%- endif %} {% endwebui %} @@ -133,109 +91,77 @@ Você pode escolher se objetos {% data variables.large_files.product_name_long % {% data reusables.cli.cli-learn-more %} -1. Para criar uma versão, use o subcomando `gh release create`. Substitua `tag` pela tag desejada para a versão. - - +1. To create a release, use the `gh release create` subcommand. Replace `tag` with the desired tag for the release. ```shell gh release create tag ``` - -2. Siga as instruções interativas. Como alternativa, você pode especificar argumentos para pular essas instruções. Para obter mais informações sobre possíveis argumentos, consulte [o manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_release_create). Por exemplo, este comando cria uma pré-versão com o título e observações especificadas. - - +2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes. ```shell gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a beta release" --prerelease ``` - - {% ifversion fpt or ghes > 3.3 or ghae-issue-4972 or ghec %} - - -Se você @mencionar qualquer usuário de {% data variables.product.product_name %} nas observações, a versão publicada em {% data variables.product.prodname_dotcom_the_website %} incluirá uma seção **Colaboradores** com uma lista de avatar de todos os usuários mencionados. - +If you @mention any {% data variables.product.product_name %} users in the notes, the published release on {% data variables.product.prodname_dotcom_the_website %} will include a **Contributors** section with an avatar list of all the mentioned users. {% endif %} {% endcli %} - - -## Editar uma versão +## Editing a release {% include tool-switcher %} {% webui %} {% data reusables.repositories.navigate-to-repo %} - - - {% data reusables.repositories.releases %} - - - {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %} - -3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. ![Editar uma versão](/assets/images/help/releases/edit-release-pencil.png) - - {% else %} - -3. No lado direito da página, ao lado da versão que você deseja editar, clique em **Editar versão**. ![Editar uma versão](/assets/images/help/releases/edit-release.png) - - {% endif %} - -4. Edite as informações da versão no formulário e, em seguida, clique em **Atualizar versão**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} Se você adicionar ou remover quaisquer @menções de usuários do GitHub na descrição, esses usuários serão adicionados ou removidos da lista de avatares na seção **Colaboradores** da versão.{% endif %} ![Atualizar uma versão](/assets/images/help/releases/update-release.png) +3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. + ![Edit a release](/assets/images/help/releases/edit-release-pencil.png) +{% else %} +3. On the right side of the page, next to the release you want to edit, click **Edit release**. + ![Edit a release](/assets/images/help/releases/edit-release.png) +{% endif %} +4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %} + ![Update a release](/assets/images/help/releases/update-release.png) {% endwebui %} {% cli %} -As versões não podem ser editadas com {% data variables.product.prodname_cli %}. +Releases cannot currently be edited with {% data variables.product.prodname_cli %}. {% endcli %} - - -## Excluir uma versão +## Deleting a release {% include tool-switcher %} {% webui %} {% data reusables.repositories.navigate-to-repo %} - - - {% data reusables.repositories.releases %} - - - {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %} - -3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. ![Excluir uma versão](/assets/images/help/releases/delete-release-trash.png) - - {% else %} - -3. Clique no nome da versão que você deseja excluir.![Link para visualizar versão](/assets/images/help/releases/release-name-link.png) - -4. No canto superior direito da página, clique em **Delete** (Excluir). ![Botão de exclusão de versão](/assets/images/help/releases/delete-release.png) - - {% endif %} - -5. Clique em **Excluir esta versão**. ![Confirmar exclusão da versão](/assets/images/help/releases/confirm-delete-release.png) +3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. + ![Delete a release](/assets/images/help/releases/delete-release-trash.png) +{% else %} +3. Click the name of the release you wish to delete. + ![Link to view release](/assets/images/help/releases/release-name-link.png) +4. In the upper-right corner of the page, click **Delete**. + ![Delete release button](/assets/images/help/releases/delete-release.png) +{% endif %} +5. Click **Delete this release**. + ![Confirm delete release](/assets/images/help/releases/confirm-delete-release.png) {% endwebui %} {% cli %} -1. Para excluir uma versão, use o subcomando `gh release delete`. Substitua `tag` pela tag da versão a ser excluída. Use o sinalizador `-y` para ignorar a confirmação. - +1. To delete a release, use the `gh release delete` subcommand. Replace `tag` with the tag of the release to delete. Use the `-y` flag to skip confirmation. ```shell gh release delete tag -y ``` - {% endcli %} diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md index 6b323b670cf8..393e6eb56cf4 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md @@ -1,8 +1,8 @@ --- -title: Visualizando versões e tags do seu repositório -intro: Você pode visualizar o histórico cronológico do seu repositório pelo número da versão da versão ou da tag. +title: Viewing your repository's releases and tags +intro: You can view the chronological history of your repository by release name or tag version number. redirect_from: - - /articles/working-with-tags/ + - /articles/working-with-tags - /articles/viewing-your-repositorys-tags - /github/administering-a-repository/viewing-your-repositorys-tags - /github/administering-a-repository/viewing-your-repositorys-releases-and-tags @@ -14,29 +14,29 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Visualizar versões & tags +shortTitle: View releases & tags --- - {% ifversion fpt or ghae or ghes or ghec %} {% tip %} -**Dica**: Você também pode ver uma versão usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`vista da versão `](https://cli.github.com/manual/gh_release_view)" na documentação do {% data variables.product.prodname_cli %}. +**Tip**: You can also view a release using the {% data variables.product.prodname_cli %}. For more information, see "[`gh release view`](https://cli.github.com/manual/gh_release_view)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} {% endif %} -## Visualizar versões +## Viewing releases {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} -2. Na parte superior da página Versões, clique em **Releases** (Versões). +2. At the top of the Releases page, click **Releases**. -## Visualizar tags +## Viewing tags {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} -2. Na parte superior da página Versões, clique em **Tags**. ![Página de tags](/assets/images/help/releases/tags-list.png) +2. At the top of the Releases page, click **Tags**. +![Tags page](/assets/images/help/releases/tags-list.png) -## Leia mais +## Further reading -- "[Assinar tags](/articles/signing-tags)" +- "[Signing tags](/articles/signing-tags)" diff --git a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md index 4743f1cafdc0..2a5f05924539 100644 --- a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md +++ b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md @@ -1,8 +1,8 @@ --- -title: Sobre gráficos do repositório -intro: Os gráficos do repositório ajudam a exibir e analisar dados do repositório. +title: About repository graphs +intro: Repository graphs help you view and analyze data for your repository. redirect_from: - - /articles/using-graphs/ + - /articles/using-graphs - /articles/about-repository-graphs - /github/visualizing-repository-data-with-graphs/about-repository-graphs - /github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/about-repository-graphs @@ -14,19 +14,18 @@ versions: topics: - Repositories --- - -Os gráficos de um repositório fornecem informações sobre o tráfego do {% ifversion fpt or ghec %}, projetos que dependem do repositório,{% endif %} contribuidores e commits do repositório, além de bifurcações e rede de um repositório. Se você mantém um repositório, é possível usar esses dados para entender melhor quem está usando o repositório e por que está usando. +A repository's graphs give you information on {% ifversion fpt or ghec %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. If you maintain a repository, you can use this data to get a better understanding of who's using your repository and why they're using it. {% ifversion fpt or ghec %} -Alguns gráficos do repositório estão disponíveis somente em repositórios públicos com o {% data variables.product.prodname_free_user %}: -- Pulso -- Contribuidores -- Tráfego +Some repository graphs are available only in public repositories with {% data variables.product.prodname_free_user %}: +- Pulse +- Contributors +- Traffic - Commits -- Frequência de código -- Rede +- Code frequency +- Network -Todos os outros gráficos do repositório estão disponíveis em todos os repositórios. Cada gráfico do repositório está disponível em repositórios públicos e privados com o {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} e {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} +All other repository graphs are available in all repositories. Every repository graph is available in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} {% endif %} diff --git a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md index 0b1ae71daf18..02ea78541a83 100644 --- a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md +++ b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md @@ -1,9 +1,9 @@ --- -title: Exibir contribuidores do projeto -intro: 'Você pode ver quem contribuiu com commits para um repositório{% ifversion fpt or ghec %} e as dependências dele{% endif %}.' +title: Viewing a project's contributors +intro: 'You can see who contributed commits to a repository{% ifversion fpt or ghec %} and its dependencies{% endif %}.' redirect_from: - - /articles/i-don-t-see-myself-in-the-contributions-graph/ - - /articles/viewing-contribution-activity-in-a-repository/ + - /articles/i-don-t-see-myself-in-the-contributions-graph + - /articles/viewing-contribution-activity-in-a-repository - /articles/viewing-a-projects-contributors - /github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors - /github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-projects-contributors @@ -15,37 +15,38 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Visualizar contribuidores do projeto +shortTitle: View project contributors --- +## About contributors -## Sobre contribuidores - -No gráfico de contribuidores, você pode visualizar os 100 principais contribuidores de um repositório{% ifversion ghes or ghae %}, incluindo coautores de commits{% endif %}. Commits de merge e commits vazios não são contabilizados como contribuições para este gráfico. +You can view the top 100 contributors to a repository{% ifversion ghes or ghae %}, including commit co-authors,{% endif %} in the contributors graph. Merge commits and empty commits aren't counted as contributions for this graph. {% ifversion fpt or ghec %} -Você também pode ver uma lista de pessoas que contribuíram para as dependências Python do projeto. Para acessar essa lista de contribuidores da comunidade, visite `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. +You can also see a list of people who have contributed to the project's Python dependencies. To access this list of community contributors, visit `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. {% endif %} -## Acessar o gráfico de contribuidores +## Accessing the contributors graph {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} -3. Na barra lateral esquerda, clique em **Contributors** (Contribuiddores). ![Aba de colaboradores](/assets/images/help/graphs/contributors_tab.png) -4. Como alternativa, para exibir os contribuidores durante um determinado período, clique no período desejado e arraste-o até que seja selecionado. Os gráficos de contribuidores somam o número de commit semanalmente para cada domingo, de modo que seu período de tempo deve incluir um domingo. ![Intervalo de tempo selecionado no gráfico de contribuidores](/assets/images/help/graphs/repo_contributors_click_drag_graph.png) +3. In the left sidebar, click **Contributors**. + ![Contributors tab](/assets/images/help/graphs/contributors_tab.png) +4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday. + ![Selected time range in the contributors graph](/assets/images/help/graphs/repo_contributors_click_drag_graph.png) -## Solucionar problemas com contribuidores +## Troubleshooting contributors -Se você não aparecer no gráfico de contribuidores de um repositório, pode ser que: -- Você não seja um dos 100 principais contribuidores. -- Não tenha sido feito merge dos seus commits no branch padrão. -- O endereço de e-mail que você usou para criar os commits não está conectado à sua conta em {% data variables.product.product_name %}. +If you don't appear in a repository's contributors graph, it may be because: +- You aren't one of the top 100 contributors. +- Your commits haven't been merged into the default branch. +- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}. {% tip %} -**Dica:** para listar todos os contribuidores de commit em um repositório, consulte "[Repositórios](/rest/reference/repos#list-contributors)". +**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)." {% endtip %} -Se todos os seus commits no repositório estiverem em branches não padrão, você não estará no gráfico de contribuidores. Por exemplo, os commits no branch `gh-pages` só serão incluídos no gráfico se `gh-pages` for o branch padrão do repositório. Para que seja feito merge dos seus commits no branch padrão, você precisa criar uma pull request. Para obter mais informações, consulte "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)". +If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." -Se o endereço de e-mail que você usou para criar os commits não estiver conectado à sua conta em {% data variables.product.product_name %}, seus commits não serão vinculados à sua conta e você não aparecerá no gráfico de contribuidores. Para obter mais informações, consulte "[Definir o seu endereço de e-mail de commit](/articles/setting-your-commit-email-address){% ifversion not ghae %}" e "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.prodname_dotcom %} ](/articles/adding-an-email-address-to-your-github-account){% endif %}." +If the email address you used to author the commits is not connected to your account on {% data variables.product.product_name %}, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address){% ifversion not ghae %}" and "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}." diff --git a/translations/pt-BR/content/repositories/working-with-files/index.md b/translations/pt-BR/content/repositories/working-with-files/index.md index a17c07affc41..1e874875f794 100644 --- a/translations/pt-BR/content/repositories/working-with-files/index.md +++ b/translations/pt-BR/content/repositories/working-with-files/index.md @@ -1,9 +1,9 @@ --- -title: Trabalhando com arquivos -intro: Aprenda como gerenciar e usar arquivos em repositórios. +title: Working with files +intro: Learn how to manage and use files in repositories. redirect_from: - - /categories/81/articles/ - - /categories/manipulating-files/ + - /categories/81/articles + - /categories/manipulating-files - /categories/managing-files-in-a-repository - /github/managing-files-in-a-repository versions: @@ -17,6 +17,6 @@ children: - /managing-files - /using-files - /managing-large-files -shortTitle: Trabalhar com arquivos +shortTitle: Work with files --- diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md b/translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md index e64256c3028b..b52562a21b40 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md @@ -1,8 +1,8 @@ --- -title: Editando arquivos -intro: 'Com o editor de arquivos, você pode editar arquivos diretamente no {% data variables.product.product_name %} em qualquer dos seus repositórios.' +title: Editing files +intro: 'You can edit files directly on {% data variables.product.product_name %} in any of your repositories using the file editor.' redirect_from: - - /articles/editing-files/ + - /articles/editing-files - /articles/editing-files-in-your-repository - /github/managing-files-in-a-repository/editing-files-in-your-repository - /articles/editing-files-in-another-user-s-repository @@ -16,42 +16,47 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Editar arquivos +shortTitle: Edit files --- -## Editar arquivos no repositório +## Editing files in your repository {% tip %} -**Dica**: {% data reusables.repositories.protected-branches-block-web-edits-uploads %} +**Tip**: {% data reusables.repositories.protected-branches-block-web-edits-uploads %} {% endtip %} {% note %} -**Observação:** o editor de arquivos do {% data variables.product.product_name %} usa o [CodeMirror](https://codemirror.net/). +**Note:** {% data variables.product.product_name %}'s file editor uses [CodeMirror](https://codemirror.net/). {% endnote %} -1. No repositório, navegue até o arquivo que deseja editar. +1. In your repository, browse to the file you want to edit. {% data reusables.repositories.edit-file %} -3. Na guia **Edit file** (Editar arquivo), faça as alterações necessárias no arquivo. ![Novo conteúdo no arquivo](/assets/images/help/repository/edit-readme-light.png) +3. On the **Edit file** tab, make any changes you need to the file. +![New content in file](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} -## Editar arquivos no repositório de outro usuário +## Editing files in another user's repository -Ao editar um arquivo em um repositório de outro usuário, iremos [bifurcar o repositório](/articles/fork-a-repo) automaticamente e [abrir um pull request](/articles/creating-a-pull-request) para você. +When you edit a file in another user's repository, we'll automatically [fork the repository](/articles/fork-a-repo) and [open a pull request](/articles/creating-a-pull-request) for you. -1. No repositório de outro usuário, navegue até a pasta que contém o arquivo que deseja editar. Clique no nome do arquivo a ser editado. -2. Acima do conteúdo do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %}. Neste ponto, o GitHub bifurca o repositório para você. -3. Faça as alterações necessárias no arquivo. ![Novo conteúdo no arquivo](/assets/images/help/repository/edit-readme-light.png) +1. In another user's repository, browse to the folder that contains the file you want to edit. Click the name of the file you want to edit. +2. Above the file content, click {% octicon "pencil" aria-label="The edit icon" %}. At this point, GitHub forks the repository for you. +3. Make any changes you need to the file. +![New content in file](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} -6. Clique em **Propose file change** (Propor alteração no arquivo). ![Botão Commit Changes (Fazer commit de alterações)](/assets/images/help/repository/propose_file_change_button.png) -7. Digite um título e uma descrição para a pull request. ![Página Pull Request description (Descrição da pull request)](/assets/images/help/pull_requests/pullrequest-description.png) -8. Clique em **Create pull request** (Criar pull request). ![Botão Pull Request (Pull request)](/assets/images/help/pull_requests/pullrequest-send.png) +6. Click **Propose file change**. +![Commit Changes button](/assets/images/help/repository/propose_file_change_button.png) +7. Type a title and description for your pull request. +![Pull Request description page](/assets/images/help/pull_requests/pullrequest-description.png) +8. Click **Create pull request**. +![Pull Request button](/assets/images/help/pull_requests/pullrequest-send.png) 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 606bad1418db..284c0fc933b5 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,8 +1,8 @@ --- -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-large-file-storage - /articles/about-git-large-file-storage - /github/managing-large-files/about-git-large-file-storage - /github/managing-large-files/versioning-large-files/about-git-large-file-storage @@ -14,29 +14,29 @@ versions: shortTitle: Git Large File Storage --- -## Sobre o {% data variables.large_files.product_name_long %} +## About {% 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 trabalhar em torno da arquitetura do Git, o {% data variables.large_files.product_name_short %} cria um arquivo de ponteiro que atua como uma referência ao arquivo real (que é armazenado em algum 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ê. +{% 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. {% ifversion fpt or ghec %} -Ao usar {% data variables.large_files.product_name_short %}, você pode armazenar arquivos até: +Using {% data variables.large_files.product_name_short %}, you can store files up to: -| Produto | Tamanho máximo do arquivo | -| ------------------------------------------------- | ------------------------- | -| {% data variables.product.prodname_free_user %} | 2 GB | -| {% data variables.product.prodname_pro %} | 2 GB | -| {% data variables.product.prodname_team %} | 4 GB | +| 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 LFS do Git no {% data variables.product.prodname_desktop %}, consulte "[Clonar um repositório do GitHub no GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". +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 %} @@ -44,16 +44,16 @@ oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5 size 84977953 ``` -Ele rastreia a `version` (versão) do {% data variables.large_files.product_name_short %} que você está usando, seguida por um identificador exclusivo para o arquivo (`oid`). Ele também armazena o `size` (tamanho) 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 %} -**Atenção**: -- {% 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 %} -## Leia mais +## 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/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md index 1a20c597c1ba..575108e57ec0 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md @@ -1,6 +1,6 @@ --- -title: Sobre arquivos grandes no GitHub -intro: '{% data variables.product.product_name %} limita o tamanho dos arquivos que você pode rastrear em repositórios do Git regulares. Aprenda a rastrear ou remover arquivos que estão além do limite.' +title: About large files on GitHub +intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.' redirect_from: - /articles/distributing-large-binaries - /github/managing-large-files/distributing-large-binaries @@ -12,7 +12,7 @@ redirect_from: - /articles/conditions-for-large-files - /github/managing-large-files/conditions-for-large-files - /github/managing-large-files/working-with-large-files/conditions-for-large-files - - /articles/what-is-the-size-limit-for-a-repository/ + - /articles/what-is-the-size-limit-for-a-repository - /articles/what-is-my-disk-quota - /github/managing-large-files/what-is-my-disk-quota - /github/managing-large-files/working-with-large-files/what-is-my-disk-quota @@ -21,86 +21,86 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Arquivos grandes +shortTitle: Large files --- -## Sobre limites de tamanho em {% data variables.product.product_name %} +## About size limits on {% data variables.product.product_name %} {% ifversion fpt or ghec %} -O {% data variables.product.product_name %} tenta fornecer armazenamento abundante para todos os repositórios do Git, embora existam limites rígidos para tamanhos de arquivo e repositório. Para garantir o desempenho e confiabilidade aos nossos usuários, monitoramos ativamente os sinais da saúde geral do repositório. A saúde do repositório é uma função de vários fatores de interação, incluindo tamanho, frequência de commit, conteúdo e estrutura. +{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes. To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure. -### Limites de tamanho do arquivo +### File size limits {% endif %} -{% data variables.product.product_name %} limita o tamanho dos arquivos permitidos nos repositórios. Se você tentar adicionar ou atualizar um arquivo maior do que {% data variables.large_files.warning_size %}, você receberá um aviso do Git. As alterações ainda serão carregadas no seu repositório com sucesso, mas você pode considerar remover o commit para minimizar o impacto no desempenho. Para obter mais informações, consulte "[Remover arquivos do histórico de um repositório](#removing-files-from-a-repositorys-history)". +{% data variables.product.product_name %} limits the size of files allowed in repositories. If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see "[Removing files from a repository's history](#removing-files-from-a-repositorys-history)." {% note %} -**Observação:** se você adicionar um arquivo a um repositório por meio de um navegador, o arquivo não poderá ser maior que {% data variables.large_files.max_github_browser_size %}. Para obter mais informações, consulte "[Adicionar um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." +**Note:** If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." {% endnote %} -{% ifversion ghes %}Por padrão, {% endif %}{% data variables.product.product_name %} bloqueia pushes que excedem {% data variables.large_files.max_github_size %}. {% ifversion ghes %}No entanto, um administrador do site pode configurar um limite diferente para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurando limites de push do Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)."{% endif %} +{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)."{% endif %} -Para rastrear arquivos além desse limite, você deverá usar {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obter mais informações, consulte "[Sobre {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)". +To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)." -Se precisar distribuir arquivos grandes dentro do seu repositório, você poderá criar versões no {% data variables.product.product_location %} em vez de rastrear os arquivos. Para obter mais informações, consulte "[Distribuir grandes arquivos binários](#distributing-large-binaries)". +If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)." -O Git não é projetado para lidar com arquivos SQL grandes. Para compartilhar bancos de dados grandes com outros desenvolvedores, recomendamos usar o [Dropbox](https://www.dropbox.com/). +Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/). {% ifversion fpt or ghec %} -### Limites de tamanho do repositório +### Repository size limits -Recomendamos que repositórios permaneçam pequenos, idealmente inferior a 1 GB, e o tamanho inferior a 1 GB é altamente recomendado. Os repositórios menores são mais rápidos de clonar e são mais fáceis de trabalhar com e manter. Se o seu repositório impactar excessivamente a nossa infraestrutura, você pode receber um e-mail do {% data variables.contact.github_support %} pedindo para tomar medidas corretivas. Tentamos ser flexíveis, especialmente com grandes projetos que têm muitos colaboradores e trabalharemos com você para encontrar uma resolução sempre que possível. Você pode impedir que seu repositório afete nossa infraestrutura gerenciando efetivamente o tamanho e a saúde geral do seu repositório. É possível encontrar aconselhamento e uma ferramenta para análise de repositórios no repositório [`github/git-sizer`](https://github.com/github/git-sizer). +We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository. -As dependências externas podem fazer com que os repositórios do Git se tornem muito grandes. Para evitar o preenchimento de um repositório com dependências externas, recomendamos o uso de um gerenciador de pacotes. Os gerenciados de pacote populares para linguagens comuns incluem [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/) e [Maven](http://maven.apache.org/). Estes gerenciadores de pacotes são compatíveis com o uso direto dos repositórios do Git. Portanto, você não precisa de fontes pré-empacotadas. +External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](http://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources. -O Git não foi projetado para servir como ferramenta de backup. No entanto, existem muitas soluções especificamente projetadas para executar backups, como [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/) e [CrashPlan](https://www.crashplan.com/en-us/). +Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), and [CrashPlan](https://www.crashplan.com/en-us/). {% endif %} -## Remover arquivos do histórico do repositório +## Removing files from a repository's history {% warning %} -**Aviso**: estes procedimentos removem definitivamente os arquivos do repositório no computador e no {% data variables.product.product_location %}. Se o arquivo for importante, faça uma cópia de backup local em um diretório fora do repositório. +**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository. {% endwarning %} -### Remover um arquivo adicionado ao commit não processado mais recente +### Removing a file added in the most recent unpushed commit -Se o arquivo foi adicionado ao commit mais recente e ainda não foi processado no {% data variables.product.product_location %}, você poderá excluir o arquivo e corrigir o commit: +If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit: {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} -3. Para remover o arquivo, insira `git rm --cached`: +3. To remove the file, enter `git rm --cached`: ```shell $ git rm --cached giant_file # Stage our giant file for removal, but leave it on disk ``` -4. Faça o commit da alteração usando `--amend -CHEAD`: +4. Commit this change using `--amend -CHEAD`: ```shell $ git commit --amend -CHEAD # Amend the previous commit with your change # Simply making a new commit won't work, as you need # to remove the file from the unpushed history as well ``` -5. Faça push dos commits para {% data variables.product.product_location %}: +5. Push your commits to {% data variables.product.product_location %}: ```shell $ git push # Push our rewritten, smaller commit ``` -### Remover um arquivo adicionado em um commit anterior +### Removing a file that was added in an earlier commit -Se você adicionou um arquivo em um commit anterior, você deverá removê-lo do histórico do repositório. Para remover arquivos do histórico do repositório, você pode usar o comando BFG Repo-Cleaner ou o `git filter-branch`. Para obter mais informações, consulte "[Remover dados confidenciais de um repositório](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". +If you added a file in an earlier commit, you need to remove it from the repository's history. To remove files from the repository's history, you can use the BFG Repo-Cleaner or the `git filter-branch` command. For more information see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)." -## Distribuir binários grandes +## Distributing large binaries -Se você precisar distribuir arquivos grandes dentro do seu repositório, você poderá criar versões no {% data variables.product.product_location %}. As versões permitem que você empacote software, notas de versão e links para arquivos binários para que outras pessoas possam usar. Para mais informações, acesse "[Sobre as versões](/github/administering-a-repository/about-releases)". +If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)." {% ifversion fpt or ghec %} -Não limitamos o tamanho total dos arquivos binários na versão ou a banda larga usada para entregá-los. No entanto, cada arquivo deve ser menor que {% data variables.large_files.max_lfs_size %}. +We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}. {% endif %} diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md index 7e607186d34b..d8b8b08de9d9 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md @@ -1,59 +1,49 @@ --- -title: Sobre o uso de armazenamento e largura de banda +title: About storage and bandwidth usage intro: '{% data reusables.large_files.free-storage-bandwidth-amount %}' redirect_from: - - /articles/billing-plans-for-large-file-storage/ - - /articles/billing-plans-for-git-large-file-storage/ + - /articles/billing-plans-for-large-file-storage + - /articles/billing-plans-for-git-large-file-storage - /articles/about-storage-and-bandwidth-usage - /github/managing-large-files/about-storage-and-bandwidth-usage - /github/managing-large-files/versioning-large-files/about-storage-and-bandwidth-usage versions: fpt: '*' ghec: '*' -shortTitle: Armazenamento & banda +shortTitle: Storage & bandwidth --- +{% data variables.large_files.product_name_short %} is available for every repository on {% data variables.product.product_name %}, whether or not your account or organization has a paid subscription. -O {% data variables.large_files.product_name_short %} está disponível para cada repositório do {% data variables.product.product_name %}, sua conta ou organização tendo ou não uma assinatura paga. +## Tracking storage and bandwidth use -## Rastrear o uso de armazenamento e largura de banda +When you commit and push a change to a file tracked with {% data variables.large_files.product_name_short %}, a new version of the entire file is pushed and the total file size is counted against the repository owner's storage limit. When you download a file tracked with {% data variables.large_files.product_name_short %}, the total file size is counted against the repository owner's bandwidth limit. {% data variables.large_files.product_name_short %} uploads do not count against the bandwidth limit. -Quando você faz commit e push de uma alteração em um arquivo rastreado com o {% data variables.large_files.product_name_short %}, é feito push de uma nova versão de todo o arquivo e o tamanho total do arquivo é contado no limite de armazenamento do proprietário do repositório. Quando você baixa um arquivo rastreado com o {% data variables.large_files.product_name_short %}, o tamanho total do arquivo é contado no limite da largura de banda do proprietário do repositório. Os uploads do {% data variables.large_files.product_name_short %} não contam no limite de largura de banda. - -Por exemplo: -- Se você fizer push de um arquivo de 500 MB no {% data variables.large_files.product_name_short %}, serão usados 500 MB do armazenamento alocado e nada da largura de banda. Se você fizer uma alteração de 1 byte e fizer push do arquivo novamente, serão usados outros 500 MB do armazenamento e nada a largura de banda, totalizando 1 GB de uso total do armazenamento e zero de largura de banda para esses dois pushes. -- Se você baixar um arquivo de 500 MB que é rastreado com o LFS, serão usados 500 MB da largura de banda alocada do proprietário do repositório. Se um colaborador fizer push de uma alteração no arquivo e você fizer pull da nova versão no repositório local, serão usados outros 500 MB de largura de banda, totalizando 1 GB de uso total da largura de banda para esses dois downloads. -- Se {% data variables.product.prodname_actions %} fizer o download de um arquivo de 500 MB rastreado com LFS, ele usará 500 MB da largura de banda atribuída pelo proprietário do repositório. +For example: +- If you push a 500 MB file to {% data variables.large_files.product_name_short %}, you'll use 500 MB of your allotted storage and none of your bandwidth. If you make a 1 byte change and push the file again, you'll use another 500 MB of storage and no bandwidth, bringing your total usage for these two pushes to 1 GB of storage and zero bandwidth. +- If you download a 500 MB file that's tracked with LFS, you'll use 500 MB of the repository owner's allotted bandwidth. If a collaborator pushes a change to the file and you pull the new version to your local repository, you'll use another 500 MB of bandwidth, bringing the total usage for these two downloads to 1 GB of bandwidth. +- If {% data variables.product.prodname_actions %} downloads a 500 MB file that is tracked with LFS, it will use 500 MB of the repository owner's allotted bandwidth. {% ifversion fpt or ghec %} -Se {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) os objetos forem incluídos nos arquivos de código-fonte para o seu repositório, os downloads desses arquivos contarão para o uso de largura de banda para o repositório. Para obter mais informações, consulte " -[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

- +If {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} {% tip %} -**Dicas**: - +**Tips**: - {% data reusables.large_files.owner_quota_only %} - {% data reusables.large_files.does_not_carry %} {% endtip %} +## Storage quota +If you use more than {% data variables.large_files.initial_storage_quota %} of storage without purchasing a data pack, you can still clone repositories with large assets, but you will only retrieve the pointer files, and you will not be able to push new files back up. For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)." -## Cota de armazenamento - -Se você usar mais de {% data variables.large_files.initial_storage_quota %} de armazenamento sem comprar um pacote de dados, ainda será possível clonar repositórios com ativos grandes, mas será possível recuperar apenas os arquivos de ponteiro, não sendo possível fazer push do backup de novos arquivos. Para obter mais informações sobre arquivos de ponteiro, consulte "[Sobre o {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)". - - - -## Cota de largura de banda - -Se você usar mais de {% data variables.large_files.initial_bandwidth_quota %} de largura de banda por mês sem comprar um pacote de dados, o suporte do {% data variables.large_files.product_name_short %} será desabilitado na sua conta até o próximo mês. - +## Bandwidth quota +If you use more than {% data variables.large_files.initial_bandwidth_quota %} of bandwidth per month without purchasing a data pack, {% data variables.large_files.product_name_short %} support is disabled on your account until the next month. -## Leia mais +## Further reading -- "[Exibir o uso do {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)" -- "[Gerenciar cobrança do {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" +- "[Viewing your {% data variables.large_files.product_name_long %} usage](/articles/viewing-your-git-large-file-storage-usage)" +- "[Managing billing for {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md index 524b7ee9c36f..f1cd37622a81 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md @@ -1,8 +1,8 @@ --- -title: Colaboração com o Git Large File Storage -intro: 'Com o {% data variables.large_files.product_name_short %} habilitado, você poderá fazer fetch, modificar e fazer push de arquivos grandes, assim como em qualquer arquivo gerenciado pelo Git. No entanto, um usuário que não tem o {% data variables.large_files.product_name_short %} verá um fluxo de trabalho diferente.' +title: Collaboration with Git Large File Storage +intro: 'With {% data variables.large_files.product_name_short %} enabled, you''ll be able to fetch, modify, and push large files just as you would expect with any file that Git manages. However, a user that doesn''t have {% data variables.large_files.product_name_short %} will experience a different workflow.' redirect_from: - - /articles/collaboration-with-large-file-storage/ + - /articles/collaboration-with-large-file-storage - /articles/collaboration-with-git-large-file-storage - /github/managing-large-files/collaboration-with-git-large-file-storage - /github/managing-large-files/versioning-large-files/collaboration-with-git-large-file-storage @@ -11,37 +11,36 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Colaboração +shortTitle: Collaboration --- - -Se os colaboradores no seu repositório não tiverem o {% data variables.large_files.product_name_short %} instalado, eles não terão acesso ao arquivo grande original. Se tentarem clonar o repositório, eles farão fetch apenas dos arquivos de ponteiro e não terão acesso aos dados reais. +If collaborators on your repository don't have {% data variables.large_files.product_name_short %} installed, they won't have access to the original large file. If they attempt to clone your repository, they will only fetch the pointer files, and won't have access to any of the actual data. {% tip %} -**Dica:** para ajudar os usuários sem o {% data variables.large_files.product_name_short %} habilitado, é recomendável definir diretrizes para contribuidores do repositório que descrevam como trabalhar com arquivos grandes. Por exemplo, você pode pedir que os contribuidores não modifiquem arquivos grandes nem façam upload das alterações em um serviço de compartilhamento de arquivos, como [Dropbox](http://www.dropbox.com/) ou Google Drive. Para obter mais informações, consulte "[Configurar diretrizes para contribuidores de repositório](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)". +**Tip:** To help users without {% data variables.large_files.product_name_short %} enabled, we recommend you set guidelines for repository contributors that describe how to work with large files. For example, you may ask contributors not to modify large files, or to upload changes to a file sharing service like [Dropbox](http://www.dropbox.com/) or Google Drive. For more information, see "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." {% endtip %} -## Exibir arquivos grandes em pull requests +## Viewing large files in pull requests -O {% data variables.product.product_name %} não renderiza objetos do {% data variables.large_files.product_name_short %} em pull requests. Apenas o arquivo de ponteiro é mostrado: +{% data variables.product.product_name %} does not render {% data variables.large_files.product_name_short %} objects in pull requests. Only the pointer file is shown: -![Amostra de PR para arquivos grandes](/assets/images/help/large_files/large_files_pr.png) +![Sample PR for large files](/assets/images/help/large_files/large_files_pr.png) -Para obter mais informações sobre arquivos de ponteiro, consulte "[Sobre o {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)". +For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)." -Para ver as alterações feitas em arquivos grandes, confira o pull request localmente para revisar a diferença. Para obter mais informações, consulte "[Fazer checkout de pull requests localmente](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)". +To view changes made to large files, check out the pull request locally to review the diff. For more information, see "[Checking out pull requests locally](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)." {% ifversion fpt or ghec %} -## Fazer push de arquivos grandes em bifurcações +## Pushing large files to forks -Fazer push de arquivos grandes em bifurcações de um repositório conta nas cotas de armazenamento e na largura de banda do repositório principal, e não nas cotas do proprietário da bifurcação. +Pushing large files to forks of a repository count against the parent repository's bandwidth and storage quotas, rather than the quotas of the fork owner. -É possível fazer push de objetos do {% data variables.large_files.product_name_short %} em bifurcações públicas se a rede do repositório já tiver objetos do {% data variables.large_files.product_name_short %} ou se você tiver acesso de gravação à raiz da rede do repositório. +You can push {% data variables.large_files.product_name_short %} objects to public forks if the repository network already has {% data variables.large_files.product_name_short %} objects or you have write access to the root of the repository network. {% endif %} -## Leia mais +## Further reading -- "[Duplicar um repositório com objetos do Git Large File Storage](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)" +- "[Duplicating a repository with Git Large File Storage objects](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)" diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md index 77d91a2a40ca..6569c30f30ea 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md @@ -1,8 +1,8 @@ --- -title: Configurar o GitLarge File Storage -intro: 'Assim que o [{% data variables.large_files.product_name_short %} estiver instalado](/articles/installing-git-large-file-storage/), você precisará associá-lo a um arquivo grande no seu repositório.' +title: Configuring Git Large File Storage +intro: 'Once [{% data variables.large_files.product_name_short %} is installed](/articles/installing-git-large-file-storage/), you need to associate it with a large file in your repository.' redirect_from: - - /articles/configuring-large-file-storage/ + - /articles/configuring-large-file-storage - /articles/configuring-git-large-file-storage - /github/managing-large-files/configuring-git-large-file-storage - /github/managing-large-files/versioning-large-files/configuring-git-large-file-storage @@ -11,10 +11,9 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Configurar o LFS do Git +shortTitle: Configure Git LFS --- - -Se houver arquivos no seu repositório com os quais deseja usar o {% data variables.product.product_name %}, você precisará primeiramente removê-los do repositório e, em seguida, adicioná-los ao {% data variables.large_files.product_name_short %} no local. Para obter mais informações, consulte "[Mover um arquivo do repositório para o {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)". +If there are existing files in your repository that you'd like to use {% data variables.product.product_name %} with, you need to first remove them from the repository and then add them to {% data variables.large_files.product_name_short %} locally. For more information, see "[Moving a file in your repository to {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)." {% data reusables.large_files.resolving-upload-failures %} @@ -22,46 +21,46 @@ Se houver arquivos no seu repositório com os quais deseja usar o {% data variab {% tip %} -**Observação:** antes de tentar fazer push de um arquivo grande no {% data variables.product.product_name %}, certifique-se de que habilitou o {% data variables.large_files.product_name_short %} no seu aplicativo. Para obter mais informações, consulte "[Configurar o Git Large File Storage no GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)". +**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see "[Configuring Git Large File Storage on GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)." {% endtip %} {% endif %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual para um repositório existente que deseja usar com o {% data variables.large_files.product_name_short %}. -3. Para associar um tipo de arquivo no repositório ao {% data variables.large_files.product_name_short %}, digite `git {% data variables.large_files.command_name %} track` seguido pelo nome da extensão do arquivo do qual deseja fazer upload automaticamente no {% data variables.large_files.product_name_short %}. +2. Change your current working directory to an existing repository you'd like to use with {% data variables.large_files.product_name_short %}. +3. To associate a file type in your repository with {% data variables.large_files.product_name_short %}, enter `git {% data variables.large_files.command_name %} track` followed by the name of the file extension you want to automatically upload to {% data variables.large_files.product_name_short %}. - Por exemplo, para associar um arquivo _.psd_, digite o seguinte comando: + For example, to associate a _.psd_ file, enter the following command: ```shell $ git {% data variables.large_files.command_name %} track "*.psd" > Adding path *.psd ``` - Cada tipo de arquivo que desejar associar ao {% data variables.large_files.product_name_short %} precisará ser adicionado com `git {% data variables.large_files.command_name %} track`. Esse comando corrige o arquivo *.gitattributes* do repositório e associa arquivos grandes ao {% data variables.large_files.product_name_short %}. + Every file type you want to associate with {% data variables.large_files.product_name_short %} will need to be added with `git {% data variables.large_files.command_name %} track`. This command amends your repository's *.gitattributes* file and associates large files with {% data variables.large_files.product_name_short %}. {% tip %} - **Dica:** sugerimos enfaticamente que você faça commit do arquivo *.gitattributes* local no repositório. Depender de um arquivo *.gitattributes* global associado ao {% data variables.large_files.product_name_short %} pode causar conflitos durante a contribuição com outros projetos do Git. + **Tip:** We strongly suggest that you commit your local *.gitattributes* file into your repository. Relying on a global *.gitattributes* file associated with {% data variables.large_files.product_name_short %} may cause conflicts when contributing to other Git projects. {% endtip %} -4. Adicione um arquivo ao repositório correspondente à extensão associada: +4. Add a file to the repository matching the extension you've associated: ```shell $ git add path/to/file.psd ``` -5. Faça commit do arquivo e faça push dele no {% data variables.product.product_name %}: +5. Commit the file and push it to {% data variables.product.product_name %}: ```shell $ git commit -m "add file.psd" - $ git push origin master + $ git push ``` - Você deve ver algumas informações de diagnóstico sobre o upload do arquivo: + You should see some diagnostic information about your file upload: ```shell > Sending file.psd > 44.74 MB / 81.04 MB 55.21 % 14s > 64.74 MB / 81.04 MB 79.21 % 3s ``` -## Leia mais +## Further reading -- "[Colaboração com {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %} -- "[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} +- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %} +- "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md index fefbfadd0ada..744ea932b551 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md @@ -1,8 +1,8 @@ --- -title: Instalar o Git Large File Storage -intro: 'Para usar o {% data variables.large_files.product_name_short %}, você precisará baixar e instalar um novo programa separado do Git.' +title: Installing Git Large File Storage +intro: 'In order to use {% data variables.large_files.product_name_short %}, you''ll need to download and install a new program that''s separate from Git.' redirect_from: - - /articles/installing-large-file-storage/ + - /articles/installing-large-file-storage - /articles/installing-git-large-file-storage - /github/managing-large-files/installing-git-large-file-storage - /github/managing-large-files/versioning-large-files/installing-git-large-file-storage @@ -11,107 +11,106 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Install o LFS do Git +shortTitle: Install Git LFS --- - {% mac %} -1. Navegue para [git-lfs.github.com](https://git-lfs.github.com) e clique em **Download** (Baixar). Como alternativa, é possível instalar o {% data variables.large_files.product_name_short %} usando um gerenciador de pacotes: - - Para usar o [Homebrew](http://brew.sh/), execute `brew install git-lfs`. - - Para usar o [MacPorts](https://www.macports.org/), execute `port install git-lfs`. +1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**. Alternatively, you can install {% data variables.large_files.product_name_short %} using a package manager: + - To use [Homebrew](http://brew.sh/), run `brew install git-lfs`. + - To use [MacPorts](https://www.macports.org/), run `port install git-lfs`. - Se você instalar o {% data variables.large_files.product_name_short %} com Homebrew ou MacPorts, passe para a etapa 6. + If you install {% data variables.large_files.product_name_short %} with Homebrew or MacPorts, skip to step six. -2. Em seu computador, localize e descompacte o arquivo que foi baixado. +2. On your computer, locate and unzip the downloaded file. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Mude o diretório de trabalho atual para o folder que você baixou e descompactou. +3. Change the current working directory into the folder you downloaded and unzipped. ```shell $ cd ~/Downloads/git-lfs-1.X.X ``` {% note %} - **Observação:** o caminho do arquivo que você usa depois de `cd` depende de seu sistema operacional, da versão do Git que você baixou e de onde você salvou o download do {% data variables.large_files.product_name_short %}. + **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download. {% endnote %} -4. Para instalar o arquivo, execute este comando: +4. To install the file, run this command: ```shell $ ./install.sh > {% data variables.large_files.product_name_short %} initialized. ``` {% note %} - **Observação:** é possível que você tenha que usar `sudo ./install.sh` para instalar o arquivo. + **Note:** You may have to use `sudo ./install.sh` to install the file. {% endnote %} -5. Verifique se a instalação foi bem-sucedida: +5. Verify that the installation was successful: ```shell $ git {% data variables.large_files.command_name %} install > {% data variables.large_files.product_name_short %} initialized. ``` -6. Caso não veja a mensagem indicando que o `git {% data variables.large_files.command_name %} install` teve êxito, entre em contato com {% data variables.contact.contact_support %}. Certifique-se de incluir o nome de seu sistema operacional. +6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system. {% endmac %} {% windows %} -1. Navegue para [git-lfs.github.com](https://git-lfs.github.com) e clique em **Download** (Baixar). +1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**. {% tip %} - **Dica:** para obter mais informações sobre alternativas para instalar o {% data variables.large_files.product_name_short %} para Windows, consulte este [Guia de introdução](https://github.com/github/git-lfs#getting-started). + **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Windows, see this [Getting started guide](https://github.com/github/git-lfs#getting-started). {% endtip %} -2. Em seu computador, localize o arquivo que foi baixado. -3. Clique duas vezes sobre o arquivo denominado *git-lfs-windows-1.X.X.exe*, onde 1.X.X é substituído pela versão Git LFS que você baixou. Quando você abrir esse arquivo, o Windows executará um assistente de configuração para instalar o {% data variables.large_files.product_name_short %}. +2. On your computer, locate the downloaded file. +3. Double click on the file called *git-lfs-windows-1.X.X.exe*, where 1.X.X is replaced with the Git LFS version you downloaded. When you open this file Windows will run a setup wizard to install {% data variables.large_files.product_name_short %}. {% data reusables.command_line.open_the_multi_os_terminal %} -5. Verifique se a instalação foi bem-sucedida: +5. Verify that the installation was successful: ```shell $ git {% data variables.large_files.command_name %} install > {% data variables.large_files.product_name_short %} initialized. ``` -6. Caso não veja a mensagem indicando que o `git {% data variables.large_files.command_name %} install` teve êxito, entre em contato com {% data variables.contact.contact_support %}. Certifique-se de incluir o nome de seu sistema operacional. +6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system. {% endwindows %} {% linux %} -1. Navegue para [git-lfs.github.com](https://git-lfs.github.com) e clique em **Download** (Baixar). +1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**. {% tip %} - **Dica:** para obter mais informações sobre alternativas para instalar o {% data variables.large_files.product_name_short %} para Linux, consulte este [Guia de introdução](https://github.com/github/git-lfs#getting-started). + **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Linux, see this [Getting started guide](https://github.com/github/git-lfs#getting-started). {% endtip %} -2. Em seu computador, localize e descompacte o arquivo que foi baixado. +2. On your computer, locate and unzip the downloaded file. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Mude o diretório de trabalho atual para o folder que você baixou e descompactou. +3. Change the current working directory into the folder you downloaded and unzipped. ```shell $ cd ~/Downloads/git-lfs-1.X.X ``` {% note %} - **Observação:** o caminho do arquivo que você usa depois de `cd` depende de seu sistema operacional, da versão do Git que você baixou e de onde você salvou o download do {% data variables.large_files.product_name_short %}. + **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download. {% endnote %} -4. Para instalar o arquivo, execute este comando: +4. To install the file, run this command: ```shell $ ./install.sh > {% data variables.large_files.product_name_short %} initialized. ``` {% note %} - **Observação:** é possível que você tenha que usar `sudo ./install.sh` para instalar o arquivo. + **Note:** You may have to use `sudo ./install.sh` to install the file. {% endnote %} -5. Verifique se a instalação foi bem-sucedida: +5. Verify that the installation was successful: ```shell $ git {% data variables.large_files.command_name %} install > {% data variables.large_files.product_name_short %} initialized. ``` -6. Caso não veja a mensagem indicando que o `git {% data variables.large_files.command_name %} install` teve êxito, entre em contato com {% data variables.contact.contact_support %}. Certifique-se de incluir o nome de seu sistema operacional. +6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system. {% endlinux %} -## Leia mais +## Further reading -- "[Configurar o {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)" +- "[Configuring {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)" diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md index b5796b9c5971..e634289eb4fe 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md @@ -1,9 +1,9 @@ --- -title: Links permanentes em arquivos -intro: 'Ao visualizar um arquivo em {% data variables.product.product_location %}, é possível pressionar a tecla "y" para atualizar a URL para um permalink com a versão exata do arquivo visualizado.' +title: Getting permanent links to files +intro: 'When viewing a file on {% data variables.product.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.' redirect_from: - - /articles/getting-a-permanent-link-to-a-file/ - - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url/ + - /articles/getting-a-permanent-link-to-a-file + - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url - /articles/getting-permanent-links-to-files - /github/managing-files-in-a-repository/getting-permanent-links-to-files - /github/managing-files-in-a-repository/managing-files-on-github/getting-permanent-links-to-files @@ -14,45 +14,44 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Links permanentes para arquivos +shortTitle: Permanent links to files --- - {% tip %} -**Dica**: Pressione "?" em qualquer página de {% data variables.product.product_name %} para visualizar todos os atalhos de teclado disponíveis. +**Tip**: Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts. {% endtip %} -## As visualizações de arquivos mostram a versão mais recente de um branch +## File views show the latest version on a branch -Ao visualizar um arquivo em {% data variables.product.product_location %}, normalmente você vê a versão do head atual de um branch. Por exemplo: +When viewing a file on {% data variables.product.product_location %}, you usually see the version at the current head of a branch. For example: -* [https://github.com/github/hubot/blob/**master**/README.md](https://github.com/github/codeql/blob/main/README.md) +* [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md) -refere-se ao repositório `hubot` do GitHub e apresenta a versão atual do branch `master` do arquivo `README.md`. +refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file. -A versão de um arquivo no head de um branch pode ser modificada assim que novos commits são feitos. Desta forma, caso você copie a URL normal, os conteúdos dos arquivos podem não ser os mesmos quando outra pessoa olhá-los posteriormente. +The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later. -## Pressione y para gerar um permalink para um arquivo em um commit específico +## Press y to permalink to a file in a specific commit -Para um link permanente em uma versão específica de um arquivo que você vê, em vez de usar o nome do branch na URL (por exemplo: a parte `master` no exemplo acima), coloque o ID do commit. Isso vinculará permanentemente a versão exata do arquivo naquele commit. Por exemplo: +For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id. This will permanently link to the exact version of the file in that commit. For example: -* [https://github.com/github/hubot/blob/**ed25584f5ac2520a6c28547ffd0961c7abd7ea49**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) +* [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) -substitui `master` com um ID específico do commit e o conteúdo do arquivo não será modificado. +replaces `main` with a specific commit id and the file content will not change. -É incoveniente procurar o commit SHA manualmente, mas é possível digitar o atalho y para atualizar automaticamente a URL à versão do permalink. Em seguida, você pode copiar a URL sabendo que qualquer pessoa com quem você compartilhá-la verá exatamente o que você vê. +Looking up the commit SHA by hand is inconvenient, however, so as a shortcut you can type y to automatically update the URL to the permalink version. Then you can copy the URL knowing that anyone you share it with will see exactly what you saw. {% tip %} -**Dica**: é possível colocar qualquer identificador em um commit da URL, inclusive nomes de branches, commits SHAS específicos ou mesmo tags! +**Tip**: You can put any identifier that can be resolved to a commit in the URL, including branch names, specific commit SHAs, or tags! {% endtip %} -## Criar um link permanente em um trecho de código +## Creating a permanent link to a code snippet -É possível criar um link permanente em uma linha específica ou conjunto de linhas de código de uma determinada versão de arquivo ou pull request. Para obter mais informações, consulte "[Criar um link permanente em um trecho de código](/articles/creating-a-permanent-link-to-a-code-snippet/)". +You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request. For more information, see "[Creating a permanent link to a code snippet](/articles/creating-a-permanent-link-to-a-code-snippet/)." -## Leia mais +## Further reading -- "[Arquivar um repositório GitHub ](/articles/archiving-a-github-repository)" +- "[Archiving a GitHub repository](/articles/archiving-a-github-repository)" diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md b/translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md index 2bd2d0ed6787..2aa33de78af6 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md @@ -1,9 +1,9 @@ --- -title: Controlar as alterações em um arquivo -intro: É possível controlar as alterações em linhas de um arquivo e descobrir como as partes do arquivo evoluíram ao longo do tempo. +title: Tracking changes in a file +intro: You can trace changes to lines in a file and discover how parts of the file evolved over time. redirect_from: - - /articles/using-git-blame-to-trace-changes-in-a-file/ - - /articles/tracing-changes-in-a-file/ + - /articles/using-git-blame-to-trace-changes-in-a-file + - /articles/tracing-changes-in-a-file - /articles/tracking-changes-in-a-file - /github/managing-files-in-a-repository/tracking-changes-in-a-file - /github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file @@ -14,24 +14,25 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Rastrear alterações do arquivo +shortTitle: Track file changes --- +With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when. -Com a exibição blame, você pode ver o histórico de revisão linha por linha de um arquivo inteiro ou exibir o histórico de revisão de uma única linha dentro de um arquivo clicando em {% octicon "versions" aria-label="The prior blame icon" %}. Toda vez que você clicar em {% octicon "versions" aria-label="The prior blame icon" %}, verá as informações anteriores de revisão relativas a essa linha, inclusive quem realizou a alteração e quando. +![Git blame view](/assets/images/help/repository/git_blame.png) -![Exibição blame do Git](/assets/images/help/repository/git_blame.png) +In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines. -Em um arquivo ou uma pull request, também é possível usar o menu {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} para exibir o recurso blame do Git relacionado a uma determinada linha ou um intervalo de linhas. - -![Menu kebab com opção para exibir o recurso blame do Git relacionado a uma determinada linha](/assets/images/help/repository/view-git-blame-specific-line.png) +![Kebab menu with option to view Git blame for a selected line](/assets/images/help/repository/view-git-blame-specific-line.png) {% tip %} -**Dica:** na linha de comando, você também pode usar `git blame` para exibir o histórico de revisão das linhas dentro de um arquivo. Para obter mais informações, consulte [Documentação sobre `git blame` no Git](https://git-scm.com/docs/git-blame). +**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame). {% endtip %} {% data reusables.repositories.navigate-to-repo %} -2. Clique para abrir o arquivo cujo histórico de linhas você deseja exibir. -3. No canto superior direito da exibição do arquivo, clique em **Blame** para abrir a exibição blame. ![Botão Blame (Blame)](/assets/images/help/repository/blame-button.png) -4. Para ver revisões anteriores de uma linha específica ou tornar a usar o recurso blame, clique em {% octicon "versions" aria-label="The prior blame icon" %} até encontrar as alterações que você deseja exibir. ![Botão Prior blame (Blame anterior)](/assets/images/help/repository/prior-blame-button.png) +2. Click to open the file whose line history you want to view. +3. In the upper-right corner of the file view, click **Blame** to open the blame view. +![Blame button](/assets/images/help/repository/blame-button.png) +4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing. +![Prior blame button](/assets/images/help/repository/prior-blame-button.png) diff --git a/translations/pt-BR/content/rest/reference/packages.md b/translations/pt-BR/content/rest/reference/packages.md index 72b91cab3b7d..8af15e78f917 100644 --- a/translations/pt-BR/content/rest/reference/packages.md +++ b/translations/pt-BR/content/rest/reference/packages.md @@ -19,7 +19,7 @@ To use this API, you must authenticate using a personal access token. If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)." -If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your personal access token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." +If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your personal access token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml index 52edf172f329..6b929ef70fc8 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml @@ -69,7 +69,7 @@ sections: - | [{% data variables.product.prodname_mobile %}](https://github.com/mobile) filtering allows you to search for and find issues, pull requests, and discussions from your device. New metadata for issues and pull request list items allow you to filter by assignees, checks status, review states, and comment counts. - {% data variables.product.prodname_mobile %} beta is available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. For more information, see "[GitHub Mobile](/github/getting-started-with-github/using-github/github-mobile)." + {% data variables.product.prodname_mobile %} beta is available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. For more information, see "[GitHub Mobile](/get-started/using-github/github-mobile)." changes: - heading: Alterações na administração diff --git a/translations/pt-BR/data/reusables/actions/hardware-requirements-3.2.md b/translations/pt-BR/data/reusables/actions/hardware-requirements-3.2.md new file mode 100644 index 000000000000..561ef67d96f6 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/hardware-requirements-3.2.md @@ -0,0 +1,5 @@ +| vCPUs | Memória | Simultaneidade máxima | +|:----- |:------- |:--------------------- | +| 32 | 128 GB | 1000 trabalhos | +| 64 | 256 GB | 1300 trabalhos | +| 96 | 384 GB | 2200 trabalhos | \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/hardware-requirements-after.md b/translations/pt-BR/data/reusables/actions/hardware-requirements-after.md new file mode 100644 index 000000000000..04a9407fceaf --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/hardware-requirements-after.md @@ -0,0 +1,7 @@ +| vCPUs | Memória | Simultaneidade máxima | +|:----- |:------- |:--------------------- | +| 8 | 64 GB | 300 trabalhos | +| 16 | 160 GB | 700 trabalhos | +| 32 | 128 GB | 1300 trabalhos | +| 64 | 256 GB | 2000 trabalhos | +| 96 | 384 GB | 4000 trabalhos | \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/hardware-requirements-before.md b/translations/pt-BR/data/reusables/actions/hardware-requirements-before.md new file mode 100644 index 000000000000..dcdd5ac87708 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/hardware-requirements-before.md @@ -0,0 +1,6 @@ +| vCPUs | Memória | Rendimento máximo do trabalho | +|:----- |:------- |:------------------------------ | +| 4 | 32 GB | Demonstração ou testes rápidos | +| 8 | 64 GB | 25 trabalhos | +| 16 | 160 GB | 35 trabalhos | +| 32 | 256 GB | 100 trabalhos | \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md index d1f8a8a5700c..d763c677adf8 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md @@ -22,7 +22,27 @@ {% ifversion ghes %} -Se você planeja habilitar {% data variables.product.prodname_actions %} para os usuários da sua instância, verifique os requisitos para hardware, armazenamento externo e executores em "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". +If you plan to enable {% data variables.product.prodname_actions %} for the users of your instance, more resources are required. + +{%- ifversion ghes < 3.2 %} + +{% data reusables.actions.hardware-requirements-before %} + +{%- endif %} + +{%- ifversion ghes = 3.2 %} + +{% data reusables.actions.hardware-requirements-3.2 %} + +{%- endif %} + +{%- ifversion ghes > 3.2 %} + +{% data reusables.actions.hardware-requirements-after %} + +{%- endif %} + +For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)." {% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/internal-repos.md b/translations/pt-BR/data/reusables/gated-features/internal-repos.md deleted file mode 100644 index 0f522b719f1a..000000000000 --- a/translations/pt-BR/data/reusables/gated-features/internal-repos.md +++ /dev/null @@ -1,7 +0,0 @@ -{% ifversion fpt %} -Internal repositories are available on -{% data variables.product.prodname_ghe_cloud %} for organizations that are owned by an enterprise account and {% data variables.product.prodname_ghe_server %} 2.20+. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" in the {% data variables.product.prodname_ghe_cloud %} documentation. -{% else %} -Internal repositories are available on -{% data variables.product.prodname_ghe_cloud %} for organizations that are owned by an enterprise account{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 2.20+. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." -{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/saml-sso.md b/translations/pt-BR/data/reusables/gated-features/saml-sso.md deleted file mode 100644 index 1e0b5c168947..000000000000 --- a/translations/pt-BR/data/reusables/gated-features/saml-sso.md +++ /dev/null @@ -1 +0,0 @@ -O logon único do SAML está disponível com {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %} e {% data variables.product.prodname_ghe_managed %}{% endif %}. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". diff --git a/translations/pt-BR/data/reusables/gated-features/team-synchronization.md b/translations/pt-BR/data/reusables/gated-features/team-synchronization.md deleted file mode 100644 index fad3dc007c21..000000000000 --- a/translations/pt-BR/data/reusables/gated-features/team-synchronization.md +++ /dev/null @@ -1 +0,0 @@ -{% ifversion fpt or ghec %}A sincronização de equipes está disponível para organizações e contas corporativas que usam {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info-org-products %}{% elsif ghae %}sincronização de equipes com grupos SCIM está disponível para organizações que usam {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[produtos do GitHub](/github/getting-started-with-github/githubs-products)."{% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/organizations_include.md b/translations/pt-BR/data/reusables/organizations/organizations_include.md index 5ee4268d3f15..11db39320ef6 100644 --- a/translations/pt-BR/data/reusables/organizations/organizations_include.md +++ b/translations/pt-BR/data/reusables/organizations/organizations_include.md @@ -10,7 +10,7 @@ As organizações incluem: You can use organizations for free, with {% data variables.product.prodname_free_team %}, which includes unlimited collaborators on unlimited public repositories with full features, and unlimited private repositories with limited features. -For additional features, including sophisticated user authentication and management, and improved support coverage, you can upgrade to {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} +For additional features, including SAML single sign-on and improved support coverage, you can upgrade to {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} If you use {% data variables.product.prodname_ghe_cloud %}, you have the option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/pt-BR/data/reusables/organizations/team-synchronization.md b/translations/pt-BR/data/reusables/organizations/team-synchronization.md index 2e46be47b282..520d1c96b404 100644 --- a/translations/pt-BR/data/reusables/organizations/team-synchronization.md +++ b/translations/pt-BR/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% ifversion fpt or ghae or ghec %} -Você pode usar a sincronização de equipe para adicionar e remover automaticamente integrantes da organização às equipes por meio de um provedor de identidade. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." +{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud%}{% else %}You{% endif %} can use team synchronization to automatically add and remove organization members to teams through an identity provider. For more information, see "[Synchronizing a team with an identity provider group]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/about-internal-repos.md b/translations/pt-BR/data/reusables/repositories/about-internal-repos.md index d0649590dd1f..355807ba96cb 100644 --- a/translations/pt-BR/data/reusables/repositories/about-internal-repos.md +++ b/translations/pt-BR/data/reusables/repositories/about-internal-repos.md @@ -1 +1 @@ -Você pode usar repositórios internos para praticar "innersource" dentro da sua empresa. Os integrantes da sua empresa podem colaborar usando metodologias de código aberto sem compartilhar informações proprietárias publicamente{% ifversion ghes %}, mesmo com o modo privado desabilitado{% endif %}. +{% ifversion ghec %}If your organization is owned by an enterprise account, you{% else %}You{% endif %} can use internal repositories to practice "innersource" within your enterprise. Os integrantes da sua empresa podem colaborar usando metodologias de código aberto sem compartilhar informações proprietárias publicamente{% ifversion ghes %}, mesmo com o modo privado desabilitado{% endif %}. diff --git a/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md b/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md index 3e672a301df6..1193514f500a 100644 --- a/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -O logon único SAML (SSO) de SAML concede aos proprietários corporativos da organização em {% data variables.product.prodname_dotcom %} uma forma de controlar e proteger o acesso aos recursos da organização, como repositórios, problemas e pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/pt-BR/data/reusables/saml/saml-accounts.md b/translations/pt-BR/data/reusables/saml/saml-accounts.md index fe65e529406a..1933de50a4f0 100644 --- a/translations/pt-BR/data/reusables/saml/saml-accounts.md +++ b/translations/pt-BR/data/reusables/saml/saml-accounts.md @@ -1 +1 @@ -If you configure SAML SSO, members of your {% data variables.product.prodname_dotcom %} organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom %}. Quando um membro acessa recursos dentro de sua organização que usa o SAML SSO, o {% data variables.product.prodname_dotcom %} redireciona o integrante para o seu IdP para efetuar a autenticação. Após a autenticação bem-sucedida, seu IdP redireciona o integrante para {% data variables.product.prodname_dotcom %}, onde poderá acessar os recursos da sua organização. +If you configure SAML SSO, members of your organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom_the_website %}. Quando um membro acessa recursos dentro de sua organização que usa o SAML SSO, o {% data variables.product.prodname_dotcom %} redireciona o integrante para o seu IdP para efetuar a autenticação. Após a autenticação bem-sucedida, seu IdP redireciona o integrante para {% data variables.product.prodname_dotcom %}, onde poderá acessar os recursos da sua organização. diff --git a/translations/pt-BR/data/reusables/saml/saml-session-oauth.md b/translations/pt-BR/data/reusables/saml/saml-session-oauth.md index 4f00428cfa9a..1d144e16d3e8 100644 --- a/translations/pt-BR/data/reusables/saml/saml-session-oauth.md +++ b/translations/pt-BR/data/reusables/saml/saml-session-oauth.md @@ -1 +1 @@ -Se você pertence a alguma organização que force o logon único SAML, pode ser que seja solicitado que você efetue a autenticação por meio do seu provedor de identidade antes de você poder autorizar um {% data variables.product.prodname_oauth_app %}. Para obter mais informações sobre o SAML, consulte "[Sobre autenticação com o logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". +Se você pertence a alguma organização que force o logon único SAML, pode ser que seja solicitado que você efetue a autenticação por meio do seu provedor de identidade antes de você poder autorizar um {% data variables.product.prodname_oauth_app %}. For more information about SAML, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md index c97e775a502f..562da1763a0e 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -16,7 +16,9 @@ Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_a {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} -Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token Azure | Azure SAS Token | azure_sas_token Azure | Azure Service Management Certificate | azure_management_certificate +Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} +{%- ifversion fpt or ghec or ghes > 3.3 %} +Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token Azure | Azure SAS Token | azure_sas_token Azure | Azure Service Management Certificate | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} Azure | Azure Storage Account Key | azure_storage_account_key {%- ifversion fpt or ghec or ghes > 3.2 %}