From f22436f61d2cf867b1ff6b95a5cd1696bf8b1944 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Mon, 5 Dec 2022 10:33:15 -0800 Subject: [PATCH] New translation batch for fr (#33243) Co-authored-by: Robert Sese <734194+rsese@users.noreply.github.com> --- ...g-server-statistics-for-your-enterprise.md | 2 +- ...o-your-enterprise-with-an-ip-allow-list.md | 174 +++++++++++------- .../githubs-ssh-key-fingerprints.md | 18 +- .../using-ssh-over-the-https-port.md | 36 ++-- .../quickstart/contributing-to-projects.md | 12 +- .../get-started/quickstart/fork-a-repo.md | 20 +- .../fr-FR/content/rest/overview/libraries.md | 10 +- .../enterprise-accounts/emu-forks.md | 2 +- translations/log/msft-fr-resets.csv | 3 +- 9 files changed, 165 insertions(+), 112 deletions(-) diff --git a/translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md index e42ff2fafe..c4156846ca 100644 --- a/translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md +++ b/translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md @@ -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. diff --git a/translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md b/translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md index 9c6aedbec5..4eb59cf491 100644 --- a/translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md +++ b/translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md @@ -1,7 +1,7 @@ --- -title: Restriction du trafic réseau vers votre entreprise avec une liste d’adresses IP autorisées +title: Restricting network traffic to your enterprise with an IP allow list shortTitle: Restricting network traffic -intro: Vous pouvez restreindre l’accès à votre entreprise et autoriser uniquement l’accès à vos ressources à partir d’adresses IP spécifiées à l’aide d’une liste d’adresses IP autorisées. +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: fr-FR -ms.lasthandoff: 11/29/2022 -ms.locfileid: '148185042' --- -## À propos des restrictions du trafic réseau -Par défaut, les utilisateurs autorisés peuvent accéder à votre entreprise à partir de n’importe quelle adresse IP. Vous pouvez restreindre l’accès aux ressources {% ifversion ghec %}qui sont la propriété d’organisations d’un compte d’entreprise {% endif %}en configurant une liste d’adresses IP spécifiques autorisées. {% 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 %} -Si votre entreprise utilise des {% data variables.product.prodname_emus %} avec OIDC, vous pouvez choisir d’utiliser la fonctionnalité de liste d’adresses IP autorisées de {% data variables.product.company_short %} ou d’utiliser les restrictions de la liste d’autorisations de votre fournisseur d’identité (IdP). Si votre entreprise n’utilise pas de {% data variables.product.prodname_emus %} avec OIDC, vous pouvez utiliser la fonctionnalité de liste d’autorisations de {% 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 %} -Par défaut, les règles du groupe de sécurité réseau (NSG) Azure laissent entrer l’ensemble du trafic sur les ports 22, 80, 443 et 25. Vous pouvez contacter le {% data variables.contact.github_support %} pour configurer des restrictions d’accès pour {% 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 %}. -Pour des restrictions avec des NSG Azure, contactez le {% data variables.contact.github_support %} avec les adresses IP qui doivent être autorisées à accéder à {% data variables.product.product_name %}. Spécifiez des plages d’adresses au format CIDR (Classless Inter-Domain Routing) standard. Le {% data variables.contact.github_support %} configurera les règles de pare-feu adaptées afin de limiter l’accès réseau via HTTP, SSH, HTTPS et SMTP. Pour plus d’informations, consultez « [Obtention d’aide auprès du {% 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 %} -## À propos de la liste d’adresses IP autorisées de {% data variables.product.company_short %} +## About {% data variables.product.company_short %}'s IP allow list -Vous pouvez utiliser la liste d’adresses IP autorisées de {% data variables.product.company_short %} pour contrôler l’accès à votre entreprise et aux ressources appartenant aux organisations de votre entreprise. +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 %} -## À propos de la liste d’autorisations de votre IdP +## About your IdP's allow list -Si vous utilisez des {% data variables.product.prodname_emus %} avec OIDC, vous pouvez utiliser la liste d’autorisations de votre IdP. +If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list. -L’utilisation de la liste d’autorisations de votre IdP désactive les configurations de liste d’adresses IP autorisées de {% data variables.product.company_short %} pour toutes les organisations de votre entreprise et désactive les API GraphQL pour l’activation et la gestion des listes d’adresses IP autorisées. +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. -Par défaut, votre IdP exécute la stratégie d’accès conditionnel sur la connexion SAML ou OIDC interactive initiale à {% data variables.product.company_short %} pour toute configuration de liste d’adresses IP autorisées de votre choix. +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. -La stratégie d’accès conditionnel OIDC s’applique uniquement aux requêtes adressées à l’API à l’aide d’un jeton utilisateur-à-serveur, tel qu’un jeton pour une {% data variables.product.prodname_oauth_app %} ou une {% data variables.product.prodname_github_app %} agissant pour le compte d’un utilisateur. La stratégie d’accès conditionnel OIDC ne s’applique pas lorsqu’une {% data variables.product.prodname_github_app %} utilise un jeton serveur-à-serveur. Pour plus d’informations, consultez « [Authentification avec des {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation) » et « [À propos de la prise en charge de la stratégie d’accès conditionnel de vos IdP](/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)." -Pour garantir une utilisation transparente de la stratégie d’accès conditionnel OIDC tout en appliquant la stratégie aux jetons utilisateur-à-serveur, vous devez copier toutes les plages d’adresses IP de chaque {% data variables.product.prodname_github_app %} que votre entreprise utilise dans la stratégie de votre 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. -## Utilisation de la liste d’adresses IP autorisées de {% data variables.product.company_short %} +## Using {% data variables.product.company_short %}'s IP allow list -### Activation de la liste d’adresses IP autorisées de {% data variables.product.company_short %} -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %} -1. Sous « Liste d’adresses IP autorisées », activez la liste d’adresses IP autorisées. - - Si vous utilisez des {% data variables.product.prodname_emus %} avec OIDC, sélectionnez le menu déroulant et cliquez sur **GitHub**. - ![Capture d’écran du menu déroulant montrant trois options de configuration de liste d’adresses IP autorisées : Désactivé, Fournisseur d’identité et GitHub](/assets/images/help/security/enable-github-ip-allow-list.png) +### 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**. + ![Screenshot of dropdown menu showing three IP allow list configuration options: Disabled, Identity Provider, and GitHub](/assets/images/help/security/enable-github-ip-allow-list.png) - Sélectionnez **Activer la liste d’adresses IP autorisées**. - ![Capture d’écran de la case à cocher pour autoriser les adresses IP](/assets/images/help/security/enable-ip-allow-list-ghec.png) + Select **Enable IP allow list**. + ![Screenshot of checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allow-list-ghec.png) - - Si vous n’utilisez pas de {% data variables.product.prodname_emus %} avec OIDC, sélectionnez **Activer la liste d’adresses IP autorisées**. - ![Capture d’écran de la case à cocher pour autoriser les adresses IP](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png) -1. Cliquez sur **Enregistrer**. + - If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**. + ![Screenshot of checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png) +1. Click **Save**. -### Ajout d’une adresse IP autorisée +### 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 %} -### Autorisation de l’accès par {% 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 %} -### Modification d’une adresse IP autorisée +### 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. Cliquez sur **Update**. +{% 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 %} -### Vérification de l’autorisation d’une adresse IP +### 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 %} -### Suppression d’une adresse IP autorisée +### 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 %} -## Utilisation de la liste d’autorisations de votre fournisseur d’identité +## Using your identity provider's allow list -Vous pouvez utiliser la liste d’autorisations de votre IdP si vous utilisez des {% data variables.product.prodname_emus %} avec OIDC. +{% note %} -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %} -1. Sous « Liste d’adresses IP autorisées », sélectionnez la liste déroulante et cliquez sur **Fournisseur d’identité**. +**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC. - ![Capture d’écran du menu déroulant montrant trois options de configuration de liste d’adresses IP autorisées : Désactivé, Fournisseur d’identité et GitHub](/assets/images/help/security/enable-identity-provider-ip-allow-list.png) -1. Si vous le souhaitez, pour autoriser les {% data variables.product.prodname_oauth_apps %} {% data variables.product.company_short %} installées à accéder à votre entreprise à partir de n’importe quelle adresse IP, sélectionnez **Ignorer la vérification de l’IdP pour les applications**. +{% endnote %} - ![Case à cocher permettant d’autoriser des adresses IP](/assets/images/help/security/ip-allow-list-skip-idp-check.png) -1. Cliquez sur **Enregistrer**. +{% 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**. + + ![Screenshot of dropdown menu showing three IP allow list configuration options: Disabled, Identity Provider, and GitHub](/assets/images/help/security/enable-identity-provider-ip-allow-list.png) +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**. + + ![Checkbox to allow IP addresses](/assets/images/help/security/ip-allow-list-skip-idp-check.png) +1. Click **Save**. {% endif %} {% ifversion ghae %} -## Activation des adresses IP autorisées +## 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. Sous « Liste verte d’adresses IP », sélectionnez **Activer la liste verte d’adresses IP**. - ![Case à cocher permettant d’autoriser des adresses IP](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png) -4. Cliquez sur **Enregistrer**. +{% 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**. + ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png) +4. Click **Save**. -## Ajout d’une adresse IP autorisée +## 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 %} -## Autorisation de l’accès par {% 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 %} -## Modification d’une adresse IP autorisée +## 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. Cliquez sur **Update**. +{% 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 %} -## Vérification de l’autorisation d’une adresse IP +## 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 %} -## Suppression d’une adresse IP autorisée +## 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 %} -## Utilisation de {% data variables.product.prodname_actions %} avec une liste verte d’adresses IP +## Using {% data variables.product.prodname_actions %} with an IP allow list {% data reusables.actions.ip-allow-list-self-hosted-runners %} diff --git a/translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index 1286785f70..fc12ceddd1 100644 --- a/translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -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: Empreintes digitales de clé SSH de GitHub +intro: Les empreintes digitales de clé publique peuvent être utilisées pour valider une connexion à un serveur distant. 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: fr-FR +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190329' --- -These are {% data variables.product.prodname_dotcom %}'s public key fingerprints: +Voici des exemples d’empreintes digitales de clé publique de {% data variables.product.prodname_dotcom %} : - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) -- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated) +- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - déprécié) - `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: +Vous pouvez ajouter les entrées de clé ssh suivantes à votre fichier `~.ssh/known_hosts` pour éviter de vérifier manuellement les hôtes {% 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)." +Pour plus d’informations, consultez « [Obtenir des informations sur Meta {% data variables.product.prodname_dotcom %}](/rest/meta#get-github-meta-information) ». diff --git a/translations/fr-FR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/fr-FR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 7815859b8e..abeaf87e0a 100644 --- a/translations/fr-FR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/fr-FR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -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: Utilisation de SSH sur le port HTTPS +intro: 'Parfois, les pare-feu refusent complètement d’autoriser les connexions SSH. Si vous n’avez pas la possibilité d’utiliser le [clonage HTTPS avec la mise en cache des informations d’identification](/github/getting-started-with-github/caching-your-github-credentials-in-git), vous pouvez tenter un clonage via la une connexion SSH établie sur le port HTTPS. Si la plupart des règles de pare-feu autorisent cela, les serveurs proxy peuvent néanmoins interférer.' 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: fr-FR +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190321' --- {% 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. +**Utilisateurs de {% data variables.product.prodname_ghe_server %}**  : l’accès à {% data variables.product.prodname_ghe_server %} via SSH sur le port HTTPS n’est pas pris en charge. {% endtip %} -To test if SSH over the HTTPS port is possible, run this SSH command: +Pour tester s’il est possible d’utiliser SSH sur le port HTTPS, exécutez cette commande 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 %}`. +**Remarque** : Le nom d’hôte pour le port 443 est `ssh.{% data variables.command_line.backticks %}`, pas `{% 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). +Si cela a fonctionné, parfait ! Sinon, vous devrez peut-être [suivre notre guide de résolution des problèmes](/articles/error-permission-denied-publickey). -Now, to clone the repository, you can run the following command: +À présent, pour cloner le dépôt, vous pouvez exécuter la commande suivante : ``` $ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git ``` -## Enabling SSH connections over HTTPS +## Activation des connexions SSH sur 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. +Si vous êtes en mesure de vous connecter en mode SSH à `git@ssh.{% data variables.command_line.backticks %}` sur le port 443, vous pouvez remplacer vos paramètres SSH afin que toute connexion à {% data variables.location.product_location %} s’exécute via ce serveur et ce port. -To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: +Pour définir cela dans votre fichier de configuration SSH, modifiez le fichier à l’emplacement `~/.ssh/config`, puis ajoutez cette section : ``` 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 %}: +Vous pouvez tester que cela fonctionne en vous reconnectant à {% 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 +## Mise à jour des hôtes connus -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. +La première fois que vous interagissez avec GitHub après avoir basculé sur le port 443, vous pouvez recevoir un message d’avertissement indiquant que l’hôte est introuvable dans `known_hosts`ou qu’il a été trouvé avec un autre nom. ```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)." +Vous pouvez répondre « oui » à cette question sans problème, en supposant que l’empreinte digitale SSH correspond à l’une des empreintes digitales publiées de GitHub. Pour obtenir la liste des empreintes digitales, consultez « [Empreintes digitales des clés SSH de Github](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints) ». diff --git a/translations/fr-FR/content/get-started/quickstart/contributing-to-projects.md b/translations/fr-FR/content/get-started/quickstart/contributing-to-projects.md index a725011596..5cfa395b06 100644 --- a/translations/fr-FR/content/get-started/quickstart/contributing-to-projects.md +++ b/translations/fr-FR/content/get-started/quickstart/contributing-to-projects.md @@ -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 ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %} 3. Select an owner for the forked repository. ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png) -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. ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png) 5. Optionally, add a description of your fork. ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png) @@ -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 diff --git a/translations/fr-FR/content/get-started/quickstart/fork-a-repo.md b/translations/fr-FR/content/get-started/quickstart/fork-a-repo.md index 553a37ad5e..bc2b3175dc 100644 --- a/translations/fr-FR/content/get-started/quickstart/fork-a-repo.md +++ b/translations/fr-FR/content/get-started/quickstart/fork-a-repo.md @@ -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**. ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %} 3. Select an owner for the forked repository. ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png) -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. ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png) 5. Optionally, add a description of your fork. ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png) @@ -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 %} diff --git a/translations/fr-FR/content/rest/overview/libraries.md b/translations/fr-FR/content/rest/overview/libraries.md index fba8416fdd..9be500d2f6 100644 --- a/translations/fr-FR/content/rest/overview/libraries.md +++ b/translations/fr-FR/content/rest/overview/libraries.md @@ -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: fr-FR -ms.lasthandoff: 11/21/2022 -ms.locfileid: '148179735' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148190060' --- ![Gundamcat](/assets/images/gundamcat.png) @@ -24,7 +24,6 @@ ms.locfileid: '148179735' Utilisez la bibliothèque Octokit officielle ou choisissez l’une des bibliothèques tierces disponibles. -- **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 @@ Utilisez la bibliothèque Octokit officielle ou choisissez l’une des biblioth |**github-flask**|[github-flask (site web officiel)](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 diff --git a/translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md b/translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md index f78720f3bc..558a3b591a 100644 --- a/translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md +++ b/translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md @@ -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. diff --git a/translations/log/msft-fr-resets.csv b/translations/log/msft-fr-resets.csv index c8fbdc7a5f..b3b4872d64 100644 --- a/translations/log/msft-fr-resets.csv +++ b/translations/log/msft-fr-resets.csv @@ -532,6 +532,7 @@ translations/fr-FR/content/admin/configuration/configuring-your-enterprise/confi translations/fr-FR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error translations/fr-FR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error translations/fr-FR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error +translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags translations/fr-FR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error translations/fr-FR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error translations/fr-FR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error @@ -637,7 +638,6 @@ translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/a translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error -translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md,rendering error @@ -663,7 +663,6 @@ translations/fr-FR/content/authentication/troubleshooting-ssh/error-agent-admitt translations/fr-FR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error translations/fr-FR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error translations/fr-FR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags -translations/fr-FR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error translations/fr-FR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error translations/fr-FR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags translations/fr-FR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error