New translation batch for pt (#33239)
Co-authored-by: Robert Sese <734194+rsese@users.noreply.github.com>
This commit is contained in:
docubot
@@ -548,6 +548,7 @@ translations/pt-BR/content/admin/configuration/configuring-your-enterprise/confi
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
|
||||
translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
|
||||
translations/pt-BR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
|
||||
@@ -642,7 +643,6 @@ translations/pt-BR/content/authentication/connecting-to-github-with-ssh/testing-
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
@@ -664,7 +664,6 @@ translations/pt-BR/content/authentication/troubleshooting-commit-signature-verif
|
||||
translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
|
||||
translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
|
||||
translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
|
||||
translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error
|
||||
translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
|
||||
translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
|
||||
translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
|
||||
|
||||
|
@@ -14,7 +14,7 @@ shortTitle: Server Statistics
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Como restringir o tráfego de rede para sua empresa com uma lista de permissões de IP
|
||||
title: Restricting network traffic to your enterprise with an IP allow list
|
||||
shortTitle: Restricting network traffic
|
||||
intro: Você pode restringir o acesso à sua empresa e permitir o acesso aos seus recursos apenas de endereços IP especificados usando uma lista de permissões de IP.
|
||||
intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -17,150 +17,192 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: b62ab2a143ed0e7ec57f7e7225a09c0ca713295c
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185040'
|
||||
---
|
||||
## Sobre as restrições de tráfego de rede
|
||||
|
||||
Por padrão, os usuários autorizados podem acessar sua empresa a partir de qualquer endereço IP. Você pode restringir o acesso a recursos {% ifversion ghec %}pertencentes a organizações em uma conta corporativa {% endif %}configurando uma lista de permissões para endereços IP específicos. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
## About network traffic restrictions
|
||||
|
||||
By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
Se a sua empresa usa {% data variables.product.prodname_emus %} com o OIDC, você pode escolher se deseja adotar o recurso de lista de permissões de IP do {% data variables.product.company_short %} ou as restrições da lista de permissões do seu IdP (provedor de identidade). Se sua empresa não usa {% data variables.product.prodname_emus %} com o OIDC, você pode adotar o recurso de lista de permissões do {% data variables.product.company_short %}.
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
Por padrão, as regras do grupo de segurança de rede do Azure (NSG) deixam todo o tráfego de entrada aberto nas portas 22, 80, 443 e 25. Você pode entrar em contato com o {% data variables.contact.github_support %} para configurar restrições de acesso ao {% data variables.product.product_name %}.
|
||||
By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
|
||||
|
||||
Para restrições no uso do Azure NSGs, entre em contato com o {% data variables.contact.github_support %} com os endereços IP que têm permissão para acessar o {% data variables.product.product_name %}. Especifica os intervalos de endereços usando o formato CIDR padrão (Encaminhamento sem Classe entre Domínios). O {% data variables.contact.github_support %} vai configurar as regras de firewall apropriadas para restringir o acesso à rede por meio de HTTP, SSH, HTTPS e SMTP. Para obter mais informações, confira "[Como receber ajuda do {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)".
|
||||
For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## Sobre a lista de permissões de IP do {% data variables.product.company_short %}
|
||||
## About {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
Você pode usar a lista de permissões de IP do {% data variables.product.company_short %} para controlar o acesso à sua empresa e a ativos pertencentes a organizações da sua empresa.
|
||||
You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
|
||||
|
||||
## Sobre a lista de permissões do seu IdP
|
||||
## About your IdP's allow list
|
||||
|
||||
Se estiver usando o {% data variables.product.prodname_emus %} com o OIDC, você poderá usar a lista de permissões do seu IdP.
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
|
||||
O uso da lista de permissões do seu IdP desativa as configurações da lista de permissões de IP do {% data variables.product.company_short %} para todas as organizações da sua empresa e desativa as APIs do GraphQL para habilitar e gerenciar as listas de permissões de IP.
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
|
||||
Por padrão, o IdP executa a CAP na entrada inicial interativa do SAML ou do OIDC no {% data variables.product.company_short %} para qualquer configuração de lista de permissões de IP escolhida.
|
||||
By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
|
||||
|
||||
A CAP do OIDC só se aplica a solicitações à API usando um token de usuário para servidor, como um token para um {% data variables.product.prodname_oauth_app %} ou um {% data variables.product.prodname_github_app %} atuando em nome de um usuário. A CAP do OIDC não se aplica quando um {% data variables.product.prodname_github_app %} usa um token de servidor para servidor. Para obter mais informações, confira "[Como se autenticar com {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" e "[Sobre o suporte para a Política de Acesso Condicional de IdPs](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps)".
|
||||
The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps)."
|
||||
|
||||
Para garantir o uso contínuo da CAP do OIDC enquanto ainda aplica a política a tokens de usuário para servidor, você deve copiar todos os intervalos de IP de cada {% data variables.product.prodname_github_app %} que sua empresa usa na política do IdP.
|
||||
To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
|
||||
|
||||
## Como usar a lista de permissões de IP do {% data variables.product.company_short %}
|
||||
## Using {% data variables.product.company_short %}'s IP allow list
|
||||
|
||||
### Como habilitar a lista de permissões de IP do {% data variables.product.company_short %}
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. Em "Lista de permissões de IP", habilite a lista de permissões de IP.
|
||||
- Se você estiver usando o {% data variables.product.prodname_emus %} com o OIDC, selecione o menu suspenso e clique em **GitHub**.
|
||||
|
||||
### Enabling {% data variables.product.company_short %}'s IP allow list
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", enable the IP allow list.
|
||||
- If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
|
||||
|
||||
|
||||
Selecione **Habilitar lista de permissões de IP**.
|
||||
|
||||
Select **Enable IP allow list**.
|
||||
|
||||
|
||||
- Se você não estiver usando o {% data variables.product.prodname_emus %} com o OIDC, selecione **Habilitar lista de permissões de IP**.
|
||||
|
||||
1. Clique em **Salvar**.
|
||||
- If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### Adicionar endereços IP permitidos
|
||||
### Adding an allowed IP address
|
||||
|
||||
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ipv6-allow-lists %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Permitindo acesso de {% data variables.product.prodname_github_apps %}
|
||||
### Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### Editar endereços IP permitidos
|
||||
### Editing an allowed IP address
|
||||
|
||||
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Clique em **Atualizar**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Verificando se um endereço IP é permitido
|
||||
### Checking if an IP address is permitted
|
||||
|
||||
{% data reusables.identity-and-permissions.about-checking-ip-address %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
|
||||
### Excluir endereços IP permitidos
|
||||
### Deleting an allowed IP address
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
|
||||
## Como usar a lista de permissões do seu provedor de identidade
|
||||
## Using your identity provider's allow list
|
||||
|
||||
Você pode adotar a lista de permissões do seu IdP se usar o {% data variables.product.prodname_emus %} com o OIDC.
|
||||
{% note %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. Em "Lista de permissões de IP", selecione o menu suspenso e clique em **Provedor de Identidade**.
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
|
||||
|
||||
1. Como alternativa, para permitir que os {% data variables.product.company_short %} e {% data variables.product.prodname_oauth_apps %} acessem sua empresa de qualquer endereço IP, selecione **Ignorar a verificação do IdP nos aplicativos**.
|
||||
{% endnote %}
|
||||
|
||||
|
||||
1. Clique em **Salvar**.
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
|
||||
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Habilitar endereços IP permitidos
|
||||
## Enabling allowed IP addresses
|
||||
|
||||
{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Em "Lista de IPs permitidos", selecione **Habilitar a lista de IPs permitidos**.
|
||||
|
||||
4. Clique em **Salvar**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
## Adicionar endereços IP permitidos
|
||||
## Adding an allowed IP address
|
||||
|
||||
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
|
||||
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Permitindo acesso de {% data variables.product.prodname_github_apps %}
|
||||
## Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## Editar endereços IP permitidos
|
||||
## Editing an allowed IP address
|
||||
|
||||
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Clique em **Atualizar**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Click **Update**.
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Verificando se um endereço IP é permitido
|
||||
## Checking if an IP address is permitted
|
||||
|
||||
{% data reusables.identity-and-permissions.about-checking-ip-address %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
|
||||
## Excluir endereços IP permitidos
|
||||
## Deleting an allowed IP address
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
|
||||
## Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub's SSH key fingerprints
|
||||
intro: Public key fingerprints can be used to validate a connection to a remote server.
|
||||
title: Impressões digitais da chave SSH do GitHub
|
||||
intro: Impressões digitais da chave pública podem ser usadas para validar uma conexão com um servidor remote.
|
||||
redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
@@ -14,15 +14,21 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: SSH key fingerprints
|
||||
ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190327'
|
||||
---
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
Estas são as impressões digitais de chave pública de {% data variables.product.prodname_dotcom %}:
|
||||
|
||||
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
|
||||
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA – preterida)
|
||||
- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
|
||||
- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
|
||||
|
||||
You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
|
||||
Você pode adicionar as seguintes entradas de chave ssh ao arquivo `~.ssh/known_hosts` para evitar verificar manualmente os hosts do {% data variables.product.prodname_dotcom %}:
|
||||
|
||||
```text
|
||||
github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
|
||||
@@ -30,4 +36,4 @@ github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
|
||||
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|
||||
```
|
||||
|
||||
For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."
|
||||
Para obter mais informações, confira "[Obter metainformações do {% data variables.product.prodname_dotcom %}](/rest/meta#get-github-meta-information)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using SSH over the HTTPS port
|
||||
intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.'
|
||||
title: Usar SSH na porta HTTPS
|
||||
intro: 'Às vezes, os firewalls se recusam a permitir conexões SSH completamente. Se usar [clonagem de HTTPS com armazenamento de credenciais em cache](/github/getting-started-with-github/caching-your-github-credentials-in-git) não for uma opção, experimente clonar usando uma conexão SSH na porta HTTPS. A maioria das regras de firewall deve permitir isso, mas o servidores proxy podem interferir.'
|
||||
redirect_from:
|
||||
- /articles/using-ssh-over-the-https-port
|
||||
- /github/authenticating-to-github/using-ssh-over-the-https-port
|
||||
@@ -11,14 +11,20 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
shortTitle: Use SSH over HTTPS port
|
||||
ms.openlocfilehash: 24a56147129e68c674eaf8dc733a203e2b03348a
|
||||
ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190319'
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
|
||||
**Usuários {% data variables.product.prodname_ghe_server %}** : acessar {% data variables.product.prodname_ghe_server %} via SSH por porta HTTPS atualmente não tem suporte.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
To test if SSH over the HTTPS port is possible, run this SSH command:
|
||||
Para testar se o SSH na porta HTTPS é possível, execute este comando SSH:
|
||||
|
||||
```shell
|
||||
$ ssh -T -p 443 git@ssh.github.com
|
||||
@@ -28,23 +34,23 @@ $ ssh -T -p 443 git@ssh.github.com
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
|
||||
**Observação**: o nome do host da porta 443 é `ssh.{% data variables.command_line.backticks %}`, não `{% data variables.command_line.backticks %}`.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
|
||||
Se deu certo, ótimo! Caso contrário, talvez seja necessário [seguir nosso guia de solução de problemas](/articles/error-permission-denied-publickey).
|
||||
|
||||
Now, to clone the repository, you can run the following command:
|
||||
Agora, para clonar o repositório, você pode executar o seguinte comando:
|
||||
|
||||
```
|
||||
$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
|
||||
```
|
||||
|
||||
## Enabling SSH connections over HTTPS
|
||||
## Habilitar conexões SSH por HTTPS
|
||||
|
||||
If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
|
||||
Se você conseguir usar SSH no `git@ssh.{% data variables.command_line.backticks %}` na porta 443, você poderá substituir as configurações de SSH para forçar qualquer conexão ao {% data variables.location.product_location %} a ser executada nesse servidor e nessa porta.
|
||||
|
||||
To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
|
||||
Para definir isso em seu arquivo de configuração SSH, edite o arquivo em `~/.ssh/config` e adicione esta seção:
|
||||
|
||||
```
|
||||
Host {% data variables.command_line.codeblock %}
|
||||
@@ -53,7 +59,7 @@ Port 443
|
||||
User git
|
||||
```
|
||||
|
||||
You can test that this works by connecting once more to {% data variables.location.product_location %}:
|
||||
Para testar se funciona, conecte-se mais uma vez ao {% data variables.location.product_location %}:
|
||||
|
||||
```shell
|
||||
$ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
@@ -61,10 +67,9 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
> provide shell access.
|
||||
```
|
||||
|
||||
## Updating known hosts
|
||||
## Atualizando hosts conhecidos
|
||||
|
||||
The first time you interact with GitHub after switching to port 443, you may get a warning message
|
||||
that the host wasn't found in `known_hosts`, or that it was found by another name.
|
||||
Na primeira vez que você interagir com o GitHub depois de alternar para a porta 443, talvez receba uma mensagem de aviso informando que o host não foi encontrado no `known_hosts` ou que ele foi encontrado por outro nome.
|
||||
|
||||
```ShellSession
|
||||
> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
|
||||
@@ -74,5 +79,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
|
||||
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
|
||||
```
|
||||
|
||||
It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
|
||||
one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
|
||||
Você pode responder "sim" a essa pergunta, supondo que a impressão digital do SSH corresponde a uma das impressões digitais publicadas do GitHub. Para obter a lista de impressões digitais, confira "[Impressões digitais de chave SSH do Github](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)".
|
||||
|
||||
@@ -10,12 +10,12 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Stop a codespace
|
||||
ms.openlocfilehash: c09cd757ac2667c32c26f9b5e7d7a36b8e5431f9
|
||||
ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67
|
||||
ms.openlocfilehash: 5c34fd5b7d72f52e203cd8f8fdc1871ff6a2f014
|
||||
ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185080'
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148188245'
|
||||
---
|
||||
{% jetbrains %}
|
||||
|
||||
@@ -110,4 +110,4 @@ Ao reiniciar um codespace, você pode optar por abri-lo no {% data variables.pro
|
||||
|
||||
## Leitura adicional
|
||||
|
||||
- "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
|
||||
- "[O ciclo de vida do codespace](/codespaces/getting-started/the-codespace-lifecycle)"
|
||||
|
||||
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
|
||||
ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179733'
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148190058'
|
||||
---
|
||||
|
||||
|
||||
@@ -24,7 +24,6 @@ ms.locfileid: '148179733'
|
||||
|
||||
Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.
|
||||
|
||||
- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
|
||||
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
@@ -131,6 +130,7 @@ Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das biblioteca
|
||||
|**github-flask**|[github-flask (site oficial)](http://github-flask.readthedocs.org)|
|
||||
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|
||||
|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
|
||||
|**octokit.py**|[khornberg/octokit.py](https://github.com/khornberg/octokit.py)|
|
||||
|
||||
### Ruby
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
|
||||
|
||||
Reference in New Issue
Block a user