diff --git a/translations/fr-FR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/fr-FR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index 213c2d5c9c6a..b01fb08f9895 100644 --- a/translations/fr-FR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/fr-FR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -1,7 +1,7 @@ --- -title: Adding labels to issues +title: Ajout d’étiquettes à des problèmes shortTitle: Add labels to issues -intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.' +intro: 'Vous pouvez utiliser {% data variables.product.prodname_actions %} pour étiqueter automatiquement les problèmes.' redirect_from: - /actions/guides/adding-labels-to-issues versions: @@ -13,24 +13,28 @@ type: tutorial topics: - Workflows - Project management +ms.openlocfilehash: a3523069b9422ecd8107007ca5e00fb0071dd738 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148185560' --- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction -This tutorial demonstrates how to use the [`actions/github-script` action](https://github.com/marketplace/actions/github-script) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label. +Ce tutoriel montre comment utiliser [l’action `actions/github-script`](https://github.com/marketplace/actions/github-script) dans un workflow pour étiqueter les problèmes nouvellement ouverts ou rouverts. Par exemple, vous pouvez ajouter l’étiquette `triage` chaque fois qu’un problème est ouvert ou rouvert. Ensuite, vous pouvez voir tous les problèmes qui doivent être triés en filtrant les problèmes à l’aide de l’étiquette `triage`. -The `actions/github-script` action allows you to easily use the {% data variables.product.prodname_dotcom %} API in a workflow. +L’action `actions/github-script` vous permet d’utiliser facilement l’API {% data variables.product.prodname_dotcom %} dans un workflow. -In the tutorial, you will first make a workflow file that uses the [`actions/github-script` action](https://github.com/marketplace/actions/github-script). Then, you will customize the workflow to suit your needs. +Dans le tutoriel, vous allez d’abord créer un fichier de workflow qui utilise [l’action `actions/github-script`](https://github.com/marketplace/actions/github-script). Ensuite, vous personnaliserez le workflow en fonction de vos besoins. -## Creating the workflow +## Création du workflow 1. {% data reusables.actions.choose-repo %} 2. {% data reusables.actions.make-workflow-file %} -3. Copy the following YAML contents into your workflow file. +3. Copiez le contenu YAML suivant dans votre fichier de workflow. ```yaml{:copy} name: Label issues @@ -56,23 +60,23 @@ In the tutorial, you will first make a workflow file that uses the [`actions/git }) ``` -4. Customize the `script` parameter in your workflow file: - - The `issue_number`, `owner`, and `repo` values are automatically set using the `context` object. You do not need to change these. - - Change the value for `labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `["help wanted", "good first issue"]`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)." +4. Personnalisez le paramètre `script` dans votre fichier de workflow : + - Les valeurs `issue_number`, `owner` et `repo` sont automatiquement définies à l’aide de l’objet `context` . Il est inutile de les modifier. + - Remplacez la valeur de `labels` par la liste des étiquettes que vous souhaitez ajouter au problème. Séparez plusieurs étiquettes par des virgules. Par exemple : `["help wanted", "good first issue"]`. Pour plus d’informations sur les étiquettes, consultez « [Gestion des étiquettes](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests) ». 5. {% data reusables.actions.commit-workflow %} -## Testing the workflow +## Test du workflow -Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue. +Chaque fois qu’un problème dans votre dépôt est ouvert ou rouvert, ce workflow ajoute les étiquettes que vous avez spécifiées au problème. -Test out your workflow by creating an issue in your repository. +Testez votre workflow en créant un problème dans votre dépôt. -1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)." -2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -3. When the workflow completes, the issue that you created should have the specified labels added. +1. Créez un problème dans votre dépôt. Pour plus d’informations, consultez « [Création d’un problème](/github/managing-your-work-on-github/creating-an-issue) ». +2. Pour voir l’exécution du workflow qui a été déclenchée par la création du problème, affichez l’historique des exécutions de votre workflow. Pour plus d’informations, consultez « [Affichage de l’historique des exécutions de workflows](/actions/managing-workflow-runs/viewing-workflow-run-history) ». +3. Une fois le workflow terminé, les étiquettes spécifiées doivent avoir été ajoutées au problème que vous avez créé. -## Next steps +## Étapes suivantes -- To learn more about additional things you can do with the `actions/github-script` action, see the [`actions/github-script` action documentation](https://github.com/marketplace/actions/github-script). -- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)." -- [Search GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) for examples of workflows using this action. +- Pour en savoir plus sur d’autres choses que vous pouvez faire avec l’action `actions/github-script`, consultez la [`actions/github-script`documentation sur l’action](https://github.com/marketplace/actions/github-script). +- Pour en savoir plus sur les différents événements qui peuvent déclencher votre workflow, consultez « [Événements qui déclenchent des workflows](/actions/reference/events-that-trigger-workflows#issues) ». +- [Visitez GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) pour trouver des exemples de workflow utilisant cette action. diff --git a/translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index 1fe2d098997d..542b37b134b9 100644 --- a/translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Configuring SAML single sign-on for your enterprise +title: Configuration d’une authentification unique (SSO) SAML pour votre entreprise shortTitle: Configure SAML SSO -intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghes or ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).' +intro: 'Vous pouvez contrôler et sécuriser l’accès aux {% ifversion ghec %}ressources comme les référentiels, les problèmes et les demandes de tirage au sein des organisations de votre entreprise{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}votre entreprise sur {% data variables.product.prodname_ghe_managed %}{% endif %} en {% ifversion ghec %}appliquant{% elsif ghes or ghae %}la configuration{% endif %} de l’authentification unique (SSO) SAML par le biais de votre fournisseur d’identité (IdP).' permissions: '{% ifversion ghes %}Site administrators{% elsif ghec or ghae %}Enterprise owners{% endif %} can configure SAML SSO for {% ifversion ghec or ghae %}an enterprise on {% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.product_name %} instance{% endif %}.' versions: ghec: '*' @@ -21,11 +21,16 @@ redirect_from: - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise +ms.openlocfilehash: 804ba3b262aae15b862e1a14694b82339c8d34a4 +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/28/2022 +ms.locfileid: '148183955' --- - {% data reusables.enterprise-accounts.emu-saml-note %} -## About SAML SSO +## À propos de SSO SAML {% ifversion ghec %} @@ -33,11 +38,11 @@ redirect_from: {% data reusables.saml.saml-accounts %} -For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." +Pour plus d’informations, consultez « [À propos de la gestion des identités et des accès avec l’authentification unique SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on) ». {% data reusables.saml.about-saml-enterprise-accounts %} -{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." +{% data reusables.saml.about-saml-access-enterprise-account %} Pour plus d’informations, consultez « [Affichage et gestion de l’accès SAML d’un utilisateur à votre compte d’entreprise](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise) ». {% data reusables.saml.saml-disabled-linked-identities-removed %} @@ -45,9 +50,9 @@ For more information, see "[About identity and access management with SAML singl {% elsif ghes or ghae %} -SAML SSO allows you to centrally control and secure access to {% data variables.location.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.location.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.location.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user. +L’authentification unique SAML vous permet de contrôler et de sécuriser de manière centralisée l’accès à {% data variables.location.product_location %} à partir de votre fournisseur d’identité SAML. Quand un utilisateur non authentifié accède à {% data variables.location.product_location %} dans un navigateur, {% data variables.product.product_name %} redirige l’utilisateur vers votre fournisseur d’identité SAML pour l’authentification. Une fois que l’utilisateur s’est authentifié avec un compte sur le fournisseur d’identité, celui-ci redirige l’utilisateur vers {% data variables.location.product_location %}. {% data variables.product.product_name %} valide la réponse de votre IdP, puis accorde l’accès à l’utilisateur. -After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.location.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP. +Une fois qu’un utilisateur s’est authentifié correctement sur votre fournisseur d’identité, la session SAML de l’utilisateur pour {% data variables.location.product_location %} est active dans le navigateur pendant 24 heures. Après 24 heures, l’utilisateur doit s’authentifier à nouveau auprès de votre fournisseur d’identité. {% data reusables.saml.saml-ghes-account-revocation %} @@ -55,171 +60,161 @@ After a user successfully authenticates on your IdP, the user's SAML session for {% data reusables.saml.assert-the-administrator-attribute %} -{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.scim.after-you-configure-saml %} Pour plus d’informations, consultez « [Configuration de l’approvisionnement d’utilisateurs pour votre entreprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise) ». {% endif %} {% endif %} -## Supported identity providers +## Fournisseurs d’identité pris en charge {% data reusables.saml.saml-supported-idps %} {% ifversion ghec %} -## Username considerations with SAML +## Considérations relatives aux noms d’utilisateur avec SAML -{% ifversion ghec %}If you use {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." +{% ifversion ghec %}Si vous utilisez {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} Pour plus d’informations, consultez « [Considérations relatives au nom d’utilisateur pour une authentification externe](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication) ». -## Enforcing SAML single-sign on for organizations in your enterprise account +## Application d’une authentification unique SAML pour les organisations dans votre compte d’entreprise -When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +Lorsque vous appliquez une authentification unique SAML pour votre entreprise, la configuration de l’entreprise remplace toutes les configurations SAML existantes au niveau de l’organisation. {% data reusables.saml.switching-from-org-to-enterprise %} Pour plus d’informations, consultez « [Basculement de votre configuration SAML d’une organisation vers un compte d’entreprise](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account) ». -When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP. +Lorsque vous appliquez une authentification unique SAML pour une organisation, {% data variables.product.company_short %} supprime tous les membres de l’organisation qui ne se sont pas authentifiés avec succès auprès votre fournisseur d’identité SAML. Lorsque vous avez besoin d’une SSO SAML pour votre entreprise, {% data variables.product.company_short %} ne supprime pas les membres de l’entreprise qui ne se sont pas authentifiés avec succès auprès de votre fournisseur d’identité SAML. La prochaine fois qu’un membre accédera aux ressources de l’entreprise, il devra s’authentifier auprès de votre fournisseur d’identité SAML. -For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)." +Pour plus d’informations sur l’activation de SAML à l’aide d’Okta, consultez « [Configuration de l’authentification unique SAML pour votre compte d’entreprise à l’aide d’Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta) ». -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "SAML single sign-on", select **Require SAML authentication**. - ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. -![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. -![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) -8. Under **Public Certificate**, paste a certificate to verify SAML responses. -![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) -9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. -![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) -10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) -11. Click **Save**. +5. Sous « Authentification unique SAML », sélectionnez **Exiger l’authentification SAML**. + ![Case à cocher pour activer l’authentification unique SAML](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. Dans le champ **URL d’authentification**, tapez le point de terminaison HTTP de votre fournisseur d’identité pour les demandes d’authentification unique. Cette valeur est disponible dans votre configuration de fournisseur d’identité. +![Champ de l’URL vers laquelle les membres seront transférés au moment de la connexion](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Si vous le souhaitez, dans le champ **Émetteur**, tapez l’URL de votre émetteur SAML pour vérifier l’authenticité des messages envoyés. +![Champ du nom de l’émetteur SAML](/assets/images/help/saml/saml_issuer.png) +8. Sous **Certificat public**, collez un certificat pour vérifier les réponses SAML. +![Champ du certificat public de votre fournisseur d’identité](/assets/images/help/saml/saml_public_certificate.png) +9. Pour vérifier l’intégrité des demandes de votre émetteur SAML, cliquez sur {% octicon "pencil" aria-label="The edit icon" %}. Ensuite, dans les listes déroulantes « Méthode de signature » et « Méthode Digest », choisissez l’algorithme de hachage utilisé par votre émetteur SAML. +![Listes déroulantes pour les algorithmes de hachage des méthodes de signature et Digest utilisés par votre émetteur SAML](/assets/images/help/saml/saml_hashing_method.png) +10. Avant d’activer une SSO SAML pour votre entreprise, cliquez sur **Tester la configuration SAML** pour vous assurer que les informations que vous avez entrées sont correctes. ![Bouton pour tester la configuration SAML avant de l’appliquer](/assets/images/help/saml/saml_test.png) +11. Cliquez sur **Enregistrer**. {% data reusables.enterprise-accounts.download-recovery-codes %} {% elsif ghes %} -## Configuring SAML SSO +## Configuration d’une SSO SAML -You can enable or disable SAML authentication for {% data variables.location.product_location %}, or you can edit an existing configuration. You can view and edit authentication settings for {% data variables.product.product_name %} in the management console. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." +Vous pouvez activer ou désactiver l’authentification SAML pour {% data variables.location.product_location %} ou modifier une configuration existante. Vous pouvez afficher et modifier les paramètres d’authentification pour {% data variables.product.product_name %} dans la console de gestion. Pour plus d’informations, consultez « [Accès à la console de gestion](/admin/configuration/configuring-your-enterprise/accessing-the-management-console) ». {% note %} -**Note**: {% data reusables.enterprise.test-in-staging %} +**Remarque** : {% data reusables.enterprise.test-in-staging %} {% endnote %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -1. Select **SAML**. +{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} +1. Sélectionnez **SAML**. - ![Screenshot of option to enable SAML authentication in management console](/assets/images/enterprise/management-console/auth-select-saml.png) + ![Capture d’écran de l’option permettant d’activer l’authentification SAML dans la console de gestion](/assets/images/enterprise/management-console/auth-select-saml.png) 1. {% data reusables.enterprise_user_management.built-in-authentication-option %} - ![Screenshot of option to enable built-in authentication outside of SAML IdP](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -1. Optionally, to enable unsolicited response SSO, select **IdP initiated SSO**. By default, {% data variables.product.prodname_ghe_server %} will reply to an unsolicited Identity Provider (IdP) initiated request with an `AuthnRequest` back to the IdP. + ![Capture d’écran de l’option permettant d’activer l’authentification intégrée en dehors de l’IdP SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png) +1. Vous pouvez éventuellement activer l’authentification SSO de réponse non sollicitée en sélectionnant **Authentification unique initiée par le fournisseur d’identité**. Par défaut, {% data variables.product.prodname_ghe_server %} répond à une demande non sollicitée initiée par un fournisseur d’identité par un `AuthnRequest` retourné à ce dernier. - ![Screenshot of option to enable IdP-initiated unsolicited response](/assets/images/enterprise/management-console/saml-idp-sso.png) + ![Capture d’écran de l’option permettant d’activer la réponse non sollicitée initiée par le fournisseur d’identité](/assets/images/enterprise/management-console/saml-idp-sso.png) {% tip %} - **Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}. + **Remarque** : Nous vous recommandons de laisser cette valeur **non sélectionnée**. Cette fonctionnalité doit être activée **uniquement** dans le rare cas où votre implémentation SAML ne prend pas en charge l’authentification unique initiée par le fournisseur de services, et quand cela vous a été conseillé par le {% data variables.contact.enterprise_support %}. {% endtip %} -1. Select **Disable administrator demotion/promotion** if you **do not** want your SAML provider to determine administrator rights for users on {% data variables.location.product_location %}. +1. Sélectionnez **Désactiver la rétrogradation/promotion de l’administrateur** si vous **ne souhaitez pas** que votre fournisseur SAML détermine les droits d’administrateur pour les utilisateurs de {% data variables.location.product_location %}. - ![Screenshot of option to enable option to respect the "administrator" attribute from the IdP to enable or disable administrative rights](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) -{%- ifversion ghes > 3.3 %} -1. Optionally, to allow {% data variables.location.product_location %} to receive encrypted assertions from your SAML IdP, select **Require encrypted assertions**. You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.location.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)." + ![Capture d’écran de l’option pour la prise en compte de l’attribut « administrator » de l’IdP afin d’activer ou de désactiver les droits d’administration](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) {%- ifversion ghes > 3.3 %} +1. Si vous le souhaitez, pour autoriser {% data variables.location.product_location %} à recevoir des assertions chiffrées de votre IdP SAML, sélectionnez **Exiger des assertions chiffrées**. Vous devez vérifier que votre IdP prend en charge les assertions chiffrées et que les méthodes de chiffrement et de transport de clés dans la console de gestion correspondent aux valeurs configurées au niveau de votre IdP. Vous devez également fournir le certificat public de {% data variables.location.product_location %} à votre IdP. Pour plus d’informations, consultez « [Activation des assertions chiffrées](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions) ». - ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) -{%- endif %} -1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.location.product_location %} to use internal nameservers](/enterprise/admin/guides/installation/configuring-dns-nameservers/). + ![Capture d’écran de la case à cocher « Activer les assertions chiffrées » dans la section « Authentification » de la console de gestion](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) {%- endif %} +1. Dans le champ **URL de l’authentification unique**, tapez le point de terminaison HTTP ou HTTPS au niveau de votre IdP pour les demandes d’authentification unique. Cette valeur est fournie par la configuration de votre IdP. Si l’hôte est disponible uniquement à partir de votre réseau interne, vous devez peut-être [configurer {% data variables.location.product_location %} pour utiliser des serveurs de noms internes](/enterprise/admin/guides/installation/configuring-dns-nameservers/). - ![Screenshot of text field for single sign-on URL](/assets/images/enterprise/management-console/saml-single-sign-url.png) -1. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.location.product_location %}. + ![Capture d’écran du champ de texte pour l’URL d’authentification unique](/assets/images/enterprise/management-console/saml-single-sign-url.png) +1. Dans le champ **Émetteur**, tapez éventuellement le nom de votre émetteur SAML. Cette action permet de vérifier l’authenticité des messages envoyés à {% data variables.location.product_location %}. - ![Screenshot of text field for SAML issuer URL](/assets/images/enterprise/management-console/saml-issuer.png) -1. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.location.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu. + ![Capture d’écran du champ de texte pour l’URL de l’émetteur SAML](/assets/images/enterprise/management-console/saml-issuer.png) +1. Dans les menus déroulants **Méthode de signature** et **Méthode de synthèse**, choisissez l’algorithme de hachage utilisé par votre émetteur SAML pour vérifier l’intégrité des requêtes provenant de {% data variables.location.product_location %}. Spécifiez le format via le menu déroulant **Format de l’identificateur de nom**. - ![Screenshot of drop-down menus to select signature and digest method](/assets/images/enterprise/management-console/saml-method.png) -1. Under **Verification certificate**, click **Choose File** and choose a certificate to validate SAML responses from the IdP. + ![Capture d’écran des menus déroulants permettant de sélectionner la méthode de signature et la méthode digest](/assets/images/enterprise/management-console/saml-method.png) +1. Sous **Certificat de vérification**, cliquez sur **Choisir un fichier** et choisissez un certificat pour valider les réponses SAML de l’IdP. - ![Screenshot of button for uploading validation certificate from IdP](/assets/images/enterprise/management-console/saml-verification-cert.png) -1. Modify the SAML attribute names to match your IdP if needed, or accept the default names. + ![Capture d’écran du bouton permettant de charger un certificat de validation de l’IdP](/assets/images/enterprise/management-console/saml-verification-cert.png) +1. Modifiez les noms d’attributs SAML pour les faire correspondre à votre IdP si nécessaire, ou acceptez les noms par défaut. - ![Screenshot of fields for entering additional SAML attributes](/assets/images/enterprise/management-console/saml-attributes.png) + ![Capture d’écran des champs de saisie des attributs SAML supplémentaires](/assets/images/enterprise/management-console/saml-attributes.png) {% elsif ghae %} -## Enabling SAML SSO +## Activation d’une SSO SAML {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. +Les fournisseurs d’identité suivants fournissent de la documentation sur la configuration d’une SSO SAML pour {% data variables.product.product_name %}. Si votre fournisseur d’identité n’est pas répertorié, contactez votre fournisseur d’identité pour demander un support pour {% data variables.product.product_name %}. - | IdP | More information | + | Fournisseur d’identité | Plus d’informations | | :- | :- | - | Azure AD | "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" | -| Okta | "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" | + | Azure AD | « [Configuration de l’authentification et de l’approvisionnement pour votre entreprise à l’aide d’Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) » | +| Okta | « [Configuration de l’authentification et de l’approvisionnement pour votre entreprise à l’aide d’Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) » | -During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML service provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)." +Lors de l’initialisation de {% data variables.product.product_name %}, vous devez configurer {% data variables.product.product_name %} en tant que fournisseur de services SAML sur votre fournisseur d’identité. Vous devez entrer quelques valeurs uniques sur votre fournisseur d’identité pour configurer {% data variables.product.product_name %} comme fournisseur de services valide. Pour plus d’informations, consultez la « [Référence de configuration SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata) ». -## Editing the SAML SSO configuration +## Modification de la configuration de la SSO SAML -If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.location.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate. +Si les détails de votre fournisseur d’identité changent, vous devez modifier la configuration de l’authentification unique SAML pour {% data variables.location.product_location %}. Par exemple, si le certificat de votre fournisseur d’identité expire, vous pouvez modifier la valeur du certificat public. {% ifversion ghae %} {% note %} -**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Remarque** : {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -1. Under "SAML single sign-on", type the new details for your IdP. - ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png) -1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method. - ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) - - - Use the drop-down menus and choose the new signature or digest method. - ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) -1. To ensure that the information you've entered is correct, click **Test SAML configuration**. - !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) -1. Click **Save**. - !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png) -1. Optionally, to automatically provision and deprovision user accounts for {% data variables.location.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +1. Sous « Authentification unique SAML », tapez les nouveaux détails de votre fournisseur d’identité. + ![Champs d’entrée de texte avec les détails du fournisseur d’identité pour la configuration d’une SSO SAML pour une entreprise](/assets/images/help/saml/ae-edit-idp-details.png) +1. Si vous le souhaitez, cliquez sur {% octicon "pencil" aria-label="The edit icon" %} pour configurer une nouvelle signature ou une méthode Digest. + ![Icône Modifier pour modifier la signature et la méthode Digest](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) + + - Utilisez les menus déroulants et choisissez la nouvelle signature ou la méthode Digest. + ![Menus déroulants pour choisir une nouvelle signature ou une méthode Digest](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) +1. Pour vérifier que les informations que vous avez entrées sont correctes, cliquez sur **Tester la configuration SAML**. + ![Bouton « Tester la configuration SAML »](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) +1. Cliquez sur **Enregistrer**. + ![Bouton « Enregistrer » pour la configuration d’une SSO SAML](/assets/images/help/saml/ae-edit-idp-details-save.png) +1. Si vous le souhaitez, pour provisionner et déprovisionner automatiquement des comptes d’utilisateur pour {% data variables.location.product_location %}, reconfigurez l’attribution d’utilisateurs avec SCIM. Pour plus d’informations, consultez « [Configuration de l’approvisionnement d’utilisateurs pour votre entreprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise) ». {% endif %} {% ifversion ghae %} -## Disabling SAML SSO +## Activation d’une SSO SAML {% warning %} -**Warning**: If you disable SAML SSO for {% data variables.location.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.location.product_location %}. SAML SSO sessions on {% data variables.location.product_location %} end after 24 hours. +**Avertissement** : si vous désactivez l’authentification unique SAML pour {% data variables.location.product_location %}, les utilisateurs sans session d’authentification unique SAML existante ne peuvent pas se connecter à {% data variables.location.product_location %}. Les sessions SSO SAML sur {% data variables.location.product_location %} se terminent au bout de 24 heures. {% endwarning %} {% note %} -**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Remarque** : {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -1. Under "SAML single sign-on", unselect **Enable SAML authentication**. - ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png) -1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**. - !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png) +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +1. Sous « Authentification unique SAML », désactivez **Activer l’authentification SAML**. + ![Case à cocher pour « Activer l’authentification SAML »](/assets/images/help/saml/ae-saml-disabled.png) +1. Pour désactiver la SSO SAML et exiger une connexion avec le compte d’utilisateur intégré que vous avez créé lors de l’initialisation, cliquez sur **Enregistrer**. + ![Bouton « Enregistrer » pour la configuration d’une SSO SAML](/assets/images/help/saml/ae-saml-disabled-save.png) {% endif %} @@ -227,13 +222,10 @@ If the details for your IdP change, you'll need to edit the SAML SSO configurati {% ifversion ghec or ghes %} -## Further reading +## Pour aller plus loin {%- ifversion ghec %} -- "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)" -{%- endif %} -{%- ifversion ghes %} -- "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" -{%- endif %} +- « [Gestion de l’authentification unique SAML pour votre organisation](/organizations/managing-saml-single-sign-on-for-your-organization) » {%- endif %} {%- ifversion ghes %} +- « [Promotion ou rétrogradation d’un administrateur de site](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator) » {%- endif %} {% endif %} diff --git a/translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md index a3cb3c1f5bcd..73495c4fcccd 100644 --- a/translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md +++ b/translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md @@ -1,6 +1,6 @@ --- -title: About Server Statistics -intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.' +title: À propos des statistiques du serveur +intro: 'Vous pouvez utiliser {% data variables.product.prodname_server_statistics %} pour analyser vos propres données agrégées à partir de {% data variables.product.prodname_ghe_server %} et nous aider à améliorer les produits {% data variables.product.company_short %}.' versions: feature: server-statistics permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.' @@ -8,97 +8,102 @@ redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics topics: - Enterprise +ms.openlocfilehash: 3d17df54cd5dcf9ad102ab5079794a9bcb3e664b +ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185184' --- +## À propos des avantages des {% data variables.product.prodname_server_statistics %} -## About the benefits of {% data variables.product.prodname_server_statistics %} +{% data variables.product.prodname_server_statistics %} peut vous aider à anticiper les besoins de votre organisation, à comprendre le fonctionnement de votre équipe et à montrer la valeur que vous tirez de {% data variables.product.prodname_ghe_server %}. -{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. +Une fois activé, {% data variables.product.prodname_server_statistics %} collecte des données agrégées sur la quantité de certaines fonctionnalités utilisées sur votre instance au fil du temps. Contrairement à d’autres points de terminaison de l’[API Admin Stats](/rest/reference/enterprise-admin#admin-stats), qui retournent uniquement des données pour le dernier jour, {% data variables.product.prodname_server_statistics %} fournit des données historiques de toutes les métriques {% data variables.product.prodname_server_statistics %} collectées depuis le jour où vous avez activé la fonctionnalité. Pour plus d’informations, consultez « [Activation de {% data variables.product.prodname_server_statistics %} pour votre entreprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise) ». -Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +Lorsque vous activez {% data variables.product.prodname_server_statistics %}, vous contribuez à améliorer {% data variables.product.prodname_dotcom %}. Les données agrégées que vous fournirez nous donnent des insights sur la façon dont {% data variables.product.prodname_dotcom %} apporte de la valeur à nos clients. Ces informations permettent à {% data variables.product.company_short %} de prendre des décisions de produit meilleures et plus éclairées, ce qui vous bénéficie au final. -When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you. +## À propos de la sécurité des données -## About data security +Nous respectons vos données. Nous ne transmettrons jamais les données de {% data variables.location.product_location %} sauf si vous nous avez donné l’autorisation de le faire. -We respect your data. We will never transmit data from {% data variables.location.product_location %} unless you have first given us permission to do so. +Nous ne collectons aucune donnée personnelle. Nous ne collectons pas non plus de contenu {% data variables.product.company_short %}, comme le code, les problèmes, les commentaires ou le contenu de la demande de tirage. -We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content. +Seuls les propriétaires du compte d’entreprise connecté ou de l’organisation sur {% data variables.product.prodname_ghe_cloud %} peuvent accéder aux données. -Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data. +Seules certaines métriques d’agrégation sont collectées sur les référentiels, les problèmes, les demandes d’extraction et d’autres fonctionnalités. Pour afficher la liste des métriques agrégées collectées, consultez « [{% data variables.product.prodname_server_statistics %} collectées](#server-statistics-data-collected) ». -Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." +Toutes les mises à jour des métriques collectées se produisent dans les mises en production de fonctionnalité ultérieures de {% data variables.product.prodname_ghe_server %} et sont décrites dans les [notes de publication de {% data variables.product.prodname_ghe_server %}](/admin/release-notes). En outre, nous mettrons à jour cet article avec toutes les mises à jour de métriques. -Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates. +Pour mieux comprendre comment nous stockons et sécurisons {% data variables.product.prodname_server_statistics %}, consultez « [Sécurité de GitHub](https://github.com/security) ». -For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)." +### À propos de la rétention et de la suppression des données -### About data retention and deletion +{% data variables.product.company_short %} collecte des données {% data variables.product.prodname_server_statistics %} tant que votre licence {% data variables.product.prodname_ghe_server %} est active et que la fonctionnalité {% data variables.product.prodname_server_statistics %} est activée. -{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled. +Si vous souhaitez supprimer vos données, vous pouvez le faire en contactant le support technique GitHub, votre représentant de compte {% data variables.product.prodname_dotcom %} ou votre responsable de réussite client. En règle générale, nous supprimons les données dans la période spécifiée dans notre déclaration de confidentialité. Pour plus d’informations, consultez la [déclaration de confidentialité de {% data variables.product.company_short %}](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data), dans la documentation {% data variables.product.prodname_dotcom_the_website %}. -If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation. +### À propos de la portabilité des données -### About data portability +En tant que propriétaire d’organisation ou propriétaire d’entreprise sur {% data variables.product.prodname_ghe_cloud %}, vous pouvez accéder à {% data variables.product.prodname_server_statistics %} en exportant les données dans un fichier CSV ou JSON ou via l’API REST {% data variables.product.prodname_server_statistics %}. Pour plus d’informations, consultez « [Demande de {% data variables.product.prodname_server_statistics %} à l’aide de l’API REST](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api) » ou « [Exportation de {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics) ». -As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)." +## À propos de la désactivation de la collecte de données -## About disabling data collection - -You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +Vous pouvez désactiver la fonctionnalité {% data variables.product.prodname_server_statistics %} à tout moment. Pour plus d’informations, consultez « [Activation de {% data variables.product.prodname_server_statistics %} pour votre entreprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise) ». ## {% data variables.product.prodname_server_statistics %} data collected -After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.location.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.location.product_location %}. +Une fois que vous avez activé {% data variables.product.prodname_server_statistics %}, les métriques sont collectées via un travail quotidien qui s’exécute sur {% data variables.location.product_location %}. Les métriques d’agrégation sont stockées sur votre compte d’entreprise ou d’organisation sur {% data variables.product.prodname_ghe_cloud %} et ne sont pas stockées sur {% data variables.location.product_location %}. -The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day. +Les métriques d’agrégation suivantes seront collectées et transmises quotidiennement et représentent le total pour la journée. -CSV column | Name | Description | +Colonne CSV | Nom | Description | ---------- | ---- | ----------- | -A | `github_connect.features_enabled` | Array of {% data variables.product.prodname_github_connect %} features that are enabled for your instance (see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#github-connect-features)" ) | -B | `host_name` | The hostname for your instance | -C | `dormant_users.dormancy_threshold` | The length of time a user must be inactive to be considered dormant | -D | `dormant_users.total_dormant_users` | Number of dormant user accounts | -E | `ghes_version` | The version of {% data variables.product.product_name %} that your instance is running | -F | `server_id` | The UUID generated for your instance -G | `collection_date` | The date the metrics were collected | -H | `schema_version` | The version of the database schema used to store this data | -I | `ghe_stats.comments.total_commit_comments` | Number of comments on commits | -J | `ghe_stats.comments.total_gist_comments` | Number of comments on gists | -K | `ghe_stats.comments.total_issue_comments` | Number of comments on issues | -L | `ghe_stats.comments.total_pull_request_comments` | Number of comments on pull requests | -M | `ghe_stats.gists.total_gists` | Number of gists (both secret and public) | -N | `ghe_stats.gists.private_gists` | Number of secret gists | -O | `ghe_stats.gists.public_gists` | Number of public gists | -P | `ghe_stats.hooks.total_hooks` | Number of pre-receive hooks (both active and inactive) | -Q | `ghe_stats.hooks.active_hooks` | Number of active pre-receive hooks | -R | `ghe_stats.hooks.inactive_hooks` | Number of inactive pre-receive hooks | -S | `ghe_stats.issues.total_issues` | Number of issues (both open and closed) | -T | `ghe_stats.issues.open_issues` | Number of open issues | -U | `ghe_stats.issues.closed_issues` | Number of closed issues | -V | `ghe_stats.milestones.total_milestones` | Number of milestones (both open and closed) | -W | `ghe_stats.milestones.open_milestones` | Number of open milestones | -X | `ghe_stats.milestones.closed_milestones` | Number of closed milestones | -Y | `ghe_stats.orgs.total_orgs` | Number of organizations (both enabled and disabled) | -Z | `ghe_stats.orgs.disabled_orgs` | Number of disabled organizations | -AA | `ghe_stats.orgs.total_teams` | Number of teams | -AB | `ghe_stats.orgs.total_team_members` | Number of team members | -AC | `ghe_stats.pages.total_pages` | Number of {% data variables.product.prodname_pages %} sites | -AD | `ghe_stats.pulls.total_pulls` | Number of pull requests | -AE | `ghe_stats.pulls.merged_pulls` | Number of merged pull requests | -AF | `ghe_stats.pulls.mergeable_pulls` | Number of pull requests that are currently mergeable | -AG | `ghe_stats.pulls.unmergeable_pulls` | Number of pull requests that are currently unmergeable | -AH | `ghe_stats.repos.total_repos` | Number of repositories (both upstream repositories and forks) | -AI | `ghe_stats.repos.root_repos` | Number of upstream repositories | -AJ | `ghe_stats.repos.fork_repos` | Number of forks | -AK | `ghe_stats.repos.org_repos` | Number of repositories owned by organizations | -AL | `ghe_stats.repos.total_pushes` | Number of pushes to repositories | -AM | `ghe_stats.repos.total_wikis` | Number of wikis | -AN | `ghe_stats.users.total_users` | Number of user accounts | -AO | `ghe_stats.users.admin_users` | Number of user accounts that are site administrators | -AP | `ghe_stats.users.suspended_users` | Number of user accounts that are suspended | - -## {% data variables.product.prodname_server_statistics %} data examples - -To see an example of the headings included in the CSV export for {% data variables.product.prodname_server_statistics %}, download the [{% data variables.product.prodname_server_statistics %} CSV example](/assets/server-statistics-csv-example.csv). - -To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)." \ No newline at end of file +Un | `github_connect.features_enabled` | Tableau des fonctionnalités {% data variables.product.prodname_github_connect %} activées pour votre instance (consultez « [À propos de {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#github-connect-features) ») | +B | `host_name` | Le nom d’hôte de votre instance | +C | `dormant_users.dormancy_threshold` | La durée pendant laquelle un utilisateur doit être inactif pour être considéré comme étant dormant | +D | `dormant_users.total_dormant_users` | Nombre de comptes d’utilisateurs dormants | +E | `ghes_version` | Version de {% data variables.product.product_name %} que votre instance exécute | +F | `server_id` | UUID généré pour votre instance +G | `collection_date` | Date à laquelle les métriques ont été collectées | +H | `schema_version` | Version du schéma de base de données utilisé pour stocker ces données | +I | `ghe_stats.comments.total_commit_comments` | Nombre de commentaires sur les validations | +J | `ghe_stats.comments.total_gist_comments` | Nombre de commentaires sur les Gists | +K | `ghe_stats.comments.total_issue_comments` | Nombre de commentaires sur les problèmes | +L | `ghe_stats.comments.total_pull_request_comments` | Nombre de commentaires sur les demandes de tirage (pull requests) | +M | `ghe_stats.gists.total_gists` | Nombre de Gists (secrets et publics) | +N | `ghe_stats.gists.private_gists` | Nombre de Gists secrets | +O | `ghe_stats.gists.public_gists` | Nombre de Gists publics | +P | `ghe_stats.hooks.total_hooks` | Nombre de crochets de pré-réception (actifs et inactifs) | +Q | `ghe_stats.hooks.active_hooks` | Nombre de crochets de pré-réception actifs | +R | `ghe_stats.hooks.inactive_hooks` | Nombre de crochets de pré-réception inactifs | +S | `ghe_stats.issues.total_issues` | Nombre de problèmes (ouverts et fermés) | +T | `ghe_stats.issues.open_issues` | Nombre de problèmes ouverts | +U | `ghe_stats.issues.closed_issues` | Nombre de problèmes fermés | +V | `ghe_stats.milestones.total_milestones` | Nombre de jalons (ouverts et fermés) | +W | `ghe_stats.milestones.open_milestones` | Nombre de jalons ouverts | +X | `ghe_stats.milestones.closed_milestones` | Nombre de jalons fermés | +O | `ghe_stats.orgs.total_orgs` | Nombre d’organisations (activées et désactivées) | +Z | `ghe_stats.orgs.disabled_orgs` | Nombre d’organisations désactivées | +AA | `ghe_stats.orgs.total_teams` | Nombre d’équipes | +AB | `ghe_stats.orgs.total_team_members` | Nombre de membres de l’équipe | +Secteur | `ghe_stats.pages.total_pages` | Nombre de sites {% data variables.product.prodname_pages %} | +AD | `ghe_stats.pulls.total_pulls` | Nombre de demandes de tirage | +AE | `ghe_stats.pulls.merged_pulls` | Nombre de demandes de tirage fusionnées | +AF | `ghe_stats.pulls.mergeable_pulls` | Nombre de demandes de tirage actuellement fusionnables | +Groupe de disponibilité | `ghe_stats.pulls.unmergeable_pulls` | Nombre de demandes de tirage actuellement non fusionnables | +AH | `ghe_stats.repos.total_repos` | Nombre de référentiels (référentiels en amont et duplications) | +Intelligence artificielle | `ghe_stats.repos.root_repos` | Nombre de référentiels en amont | +AJ | `ghe_stats.repos.fork_repos` | Nombre de duplications | +AK | `ghe_stats.repos.org_repos` | Nombre de référentiels détenus par des organisations | +AL | `ghe_stats.repos.total_pushes` | Nombre d’envois (push) vers des référentiels | +AM | `ghe_stats.repos.total_wikis` | Nombre de wikis | +AN | `ghe_stats.users.total_users` | Nombre de comptes d’utilisateur | +AO | `ghe_stats.users.admin_users` | Nombre de comptes d’utilisateur administrateurs de site | +AP | `ghe_stats.users.suspended_users` | Nombre de comptes d’utilisateur suspendus | + +## Exemples de données {% data variables.product.prodname_server_statistics %} + +Pour voir un exemple des en-têtes inclus dans l’exportation CSV pour {% data variables.product.prodname_server_statistics %}, téléchargez [l’exemple CSV {% data variables.product.prodname_server_statistics %}](/assets/server-statistics-csv-example.csv). + +Pour voir un exemple de charge utile de réponse pour l’API {% data variables.product.prodname_server_statistics %}, consultez « [Demander {% data variables.product.prodname_server_statistics %} à l’aide de l’API REST](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api) ». diff --git a/translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index a1a74dd1f480..a7060df4d03e 100644 --- a/translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -31,6 +31,9 @@ Before you can enable and configure {% data variables.product.prodname_registry {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} 1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. + + - You must create a storage container prior to setting the container name and connection string. + ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% note %} diff --git a/translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md index 3b8a3b97f625..5f5eb528eed0 100644 --- a/translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md +++ b/translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md @@ -1,6 +1,6 @@ --- -title: Authorizing OAuth Apps -intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing an {% data variables.product.prodname_oauth_app %}, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.' +title: Autorisation des applications OAuth +intro: 'Vous pouvez connecter votre identité {% data variables.product.product_name %} à des applications tierces à l’aide d’OAuth. Quand vous autorisez une {% data variables.product.prodname_oauth_app %}, veillez à ce qu’il s’agisse d’une application de confiance, à vérifier par qui elle a été développée et à passer en revue les types d’informations auxquels elle veut accéder.' redirect_from: - /articles/authorizing-oauth-apps - /github/authenticating-to-github/authorizing-oauth-apps @@ -13,89 +13,95 @@ versions: topics: - Identity - Access management +ms.openlocfilehash: 7d116f8fc5117cdcbdbd5582e007351c47b2d55d +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/28/2022 +ms.locfileid: '148184019' --- -When an {% data variables.product.prodname_oauth_app %} wants to identify you by your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you'll see a page with the app's developer contact information and a list of the specific data that's being requested. +Quand une {% data variables.product.prodname_oauth_app %} souhaite vous identifier par le biais de votre compte sur {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, une page s’affiche avec les coordonnées du développeur de l’application et une liste des données spécifiques nécessaires. {% ifversion fpt or ghec %} {% tip %} -**Tip:** You must [verify your email address](/articles/verifying-your-email-address) before you can authorize an {% data variables.product.prodname_oauth_app %}. +**Conseil :** Vous devez [vérifier votre adresse e-mail](/articles/verifying-your-email-address) pour pouvoir autoriser une {% data variables.product.prodname_oauth_app %}. {% endtip %} {% endif %} -## {% data variables.product.prodname_oauth_app %} access +## Accès d’une {% data variables.product.prodname_oauth_app %} -{% data variables.product.prodname_oauth_apps %} can have *read* or *write* access to your {% data variables.product.product_name %} data. +Les{% data variables.product.prodname_oauth_apps %} peuvent avoir un accès *en lecture* ou *en écriture* à vos données {% data variables.product.product_name %}. -- **Read access** only allows an app to *look at* your data. -- **Write access** allows an app to *change* your data. +- L’**accès en lecture** permet uniquement à une application de *consulter* vos données. +- L’**accès en écriture** permet à une application de *modifier* vos données. {% tip %} -**Tip:** {% data reusables.user-settings.review_oauth_tokens_tip %} +**Conseil :** {% data reusables.user-settings.review_oauth_tokens_tip %} {% endtip %} -### About OAuth scopes +### À propos des étendues OAuth -*Scopes* are named groups of permissions that an {% data variables.product.prodname_oauth_app %} can request to access both public and non-public data. +Les *étendues* sont des groupes d’autorisations nommés qu’une {% data variables.product.prodname_oauth_app %} peut demander pour accéder aux données publiques et non publiques. -When you want to use an {% data variables.product.prodname_oauth_app %} that integrates with {% data variables.product.product_name %}, that app lets you know what type of access to your data will be required. If you grant access to the app, then the app will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)." +Quand vous souhaitez utiliser une {% data variables.product.prodname_oauth_app %} qui s’intègre à {% data variables.product.product_name %}, cette application vous indique le type d’accès à vos données dont elle a besoin. Si vous accordez l’accès à l’application, celle-ci pourra effectuer des actions en votre nom telles que la lecture ou la modification de données. Par exemple, si vous voulez utiliser une application qui demande l’étendue `user:email`, cette application aura accès en lecture seule à vos adresses e-mail privées. Pour plus d’informations, consultez « [À propos des étendues pour les {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps) ». {% tip %} -**Note:** Currently, you can't scope source code access to read-only. +**Remarque :** Actuellement, vous ne pouvez pas limiter l’accès au code source à la lecture seule. {% endtip %} {% data reusables.apps.oauth-token-limit %} -### Types of requested data +### Types de données demandées -{% data variables.product.prodname_oauth_apps %} can request several types of data. +Les {% data variables.product.prodname_oauth_apps %} peuvent demander plusieurs types de données. -| Type of data | Description | +| Type de données | Description | | --- | --- | -| Commit status | You can grant access for an app to report your commit status. Commit status access allows apps to determine if a build is a successful against a specific commit. Apps won't have access to your code, but they can read and write status information against a specific commit. | -| Deployments | Deployment status access allows apps to determine if a deployment is successful against a specific commit for public and private repositories. Apps won't have access to your code. | -| Gists | [Gist](https://gist.github.com) access allows apps to read or write to both your public and secret Gists. | -| Hooks | [Webhooks](/webhooks) access allows apps to read or write hook configurations on repositories you manage. | -| Notifications | Notification access allows apps to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, apps remain unable to access anything in your repositories. | -| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. | -| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. | -| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level. | -| Repository delete | Apps can request to delete repositories that you administer, but they won't have access to your code. |{% ifversion projects-oauth-scope %} -| Projects | Access to user and organization {% data variables.projects.projects_v2 %}. Apps can request either read/write or read only access. |{% endif %} +| État de commit | Vous pouvez accorder à une application l’accès à votre état de commit. L’accès à l’état de commit permet aux applications de déterminer si une génération réussit par rapport à un commit spécifique. Les applications n’ont pas accès à votre code, mais elles peuvent lire et écrire des informations d’état pour un commit spécifique. | +| Déploiements | L’accès à l’état de déploiement permet aux applications de déterminer si un déploiement réussit par rapport à un commit spécifique pour des dépôts publics et privés. Les applications n’ont pas accès à votre code. | +| Gists | L’accès aux [Gists](https://gist.github.com) permet aux applications de lire vos Gist publics et secrets et d’écrire dans ces derniers. | +| Hooks | L’accès aux [webhooks](/webhooks) permet aux applications de lire ou d’écrire des configurations de hook sur les dépôts que vous gérez. | +| Notifications | L’accès aux notifications permet aux applications de lire vos notifications {% data variables.product.product_name %} telles que les commentaires sur les problèmes et les demandes de tirage (pull request). Toutefois, les applications ne peuvent toujours pas accéder à quoi que ce soit dans vos dépôts. | +| Organisations et équipes | L’accès aux organisations et équipes permet aux applications d’accéder à l’appartenance aux organisations et équipes et de la gérer. | +| Données personnelles de l’utilisateur | Les données utilisateur incluent des informations trouvées dans votre profil utilisateur telles que votre nom, votre adresse e-mail et votre emplacement. | +| Référentiels | Les informations de dépôt incluent les noms des contributeurs, les branches que vous avez créées et les fichiers réels dans votre dépôt. Les applications peuvent demander l’accès à des dépôts publics ou privés au niveau de l’utilisateur. | +| Suppression de dépôt | Les applications peuvent demander à supprimer des dépôts que vous administrez, mais elles n’auront pas accès à votre code. |{% ifversion projects-oauth-scope %} +| Projets | Accédez aux {% data variables.projects.projects_v2 %} de l’utilisateur et de l’organisation. Les applications peuvent demander un accès en lecture/écriture ou en lecture seule. |{% endif %} -## Requesting updated permissions +## Demande d’autorisations mises à jour -When {% data variables.product.prodname_oauth_apps %} request new access permissions, they will notify you of the differences between their current permissions and the new permissions. +Quand des {% data variables.product.prodname_oauth_apps %} demandent de nouvelles autorisations d’accès, elles vous informent des différences entre leurs autorisations actuelles et les nouvelles autorisations. {% ifversion fpt or ghec %} -## {% data variables.product.prodname_oauth_apps %} and organizations +## {% data variables.product.prodname_oauth_apps %} et organisations -When you authorize an {% data variables.product.prodname_oauth_app %} for your personal account, you'll also see how the authorization will affect each organization you're a member of. +Quand vous autorisez une {% data variables.product.prodname_oauth_app %} pour votre compte personnel, vous voyez également comment l’autorisation va affecter chaque organisation dont vous êtes membre. -- **For organizations *with* {% data variables.product.prodname_oauth_app %} access restrictions, you can request that organization admins approve the application for use in that organization.** If the organization does not approve the application, then the application will only be able to access the organization's public resources. If you're an organization admin, you can [approve the application](/articles/approving-oauth-apps-for-your-organization) yourself. +- **Pour les organisations *avec* des restrictions d’accès d’{% data variables.product.prodname_oauth_app %}, vous pouvez demander à l’administrateur d’une organisation d’approuver l’application pour une utilisation dans cette organisation.** Si l’organisation n’approuve pas l’application, celle-ci pourra accéder uniquement aux ressources publiques de l’organisation. Si vous êtes administrateur d’une organisation, vous pouvez [approuver l’application](/articles/approving-oauth-apps-for-your-organization) vous-même. -- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources. +- **Pour les organisations *sans* restrictions d’accès d’{% data variables.product.prodname_oauth_app %}, l’application sera automatiquement autorisée à accéder aux ressources de ces organisations.** Ainsi, vous devez être prudent quant aux {% data variables.product.prodname_oauth_apps %} pour lesquelles vous approuvez l’accès aux ressources de votre compte personnel et à toutes les ressources de l’organisation. -If you belong to any organizations with SAML single sign-on (SSO) enabled, and you have created a linked identity for that organization by authenticating via SAML in the past, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}. +Si vous faites partie d’organisations où l’authentification unique (SSO) SAML est activée et que vous avez créé une identité liée pour cette organisation en vous authentifiant via SAML auparavant, vous devez disposer d’une session SAML active pour chaque organisation chaque fois que vous autorisez une {% data variables.product.prodname_oauth_app %}. {% note %} -**Note:** If you're encountering issues with an authorized {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} accessing an organization that is protected by SAML, you may need to revoke the app from your [Authorized {% data variables.product.prodname_github_apps %}](https://github.com/settings/applications) or [Authorized {% data variables.product.prodname_oauth_apps %}](https://github.com/settings/apps/authorizations) page, visit the organization to authenticate and establish an active SAML session, and then attempt to reauthorize the app by accessing it. +**Remarque :** en cas de problèmes avec une {% data variables.product.prodname_oauth_app %} ou {% data variables.product.prodname_github_app %} autorisée qui accède à une organisation protégée par SAML, vous devez peut-être révoquer l’application sur votre page [{% data variables.product.prodname_github_apps %} autorisés](https://github.com/settings/applications) ou [{% data variables.product.prodname_oauth_apps %} autorisés](https://github.com/settings/apps/authorizations), consultez l’organisation pour vous identifier et établir une session SAML active, puis essayez de réautoriser l’application en y accédant. {% endnote %} -## Further reading +## Pour aller plus loin -- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)" -- "[Authorizing GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" -- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)" +- « [À propos des restrictions d’accès d’une {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions) » +- « [Autorisation des applications GitHub](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps) » +- « [Support pour {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support) » {% endif %} 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 a157728eb5cd..1286785f705f 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: 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. +title: GitHub's SSH key fingerprints +intro: Public key fingerprints can be used to validate a connection to a remote server. redirect_from: - /articles/what-are-github-s-ssh-key-fingerprints - /articles/github-s-ssh-key-fingerprints @@ -14,15 +14,20 @@ topics: - Identity - Access management shortTitle: SSH key fingerprints -ms.openlocfilehash: 29f61df463d014e6a72ad7dd21049a2b338b893e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: fr-FR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145086038' --- -Voici des exemples d’empreintes digitales de clé publique de {% data variables.product.prodname_dotcom %} : +These are {% data variables.product.prodname_dotcom %}'s public key fingerprints: - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) +- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated) - `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: + +```text +github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl +github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg= +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)." 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 92f37fba9d43..7815859b8efc 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 @@ -30,7 +30,7 @@ $ ssh -T -p 443 git@ssh.github.com **Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`. -{% endnote %} +{% endnote %} If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey). @@ -71,8 +71,8 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam > ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. > This host key is known by the following other names/addresses: > ~/.ssh/known_hosts:32: github.com -> Are you sure you want to continue connecting (yes/no/[fingerprint])? +> 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 more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." +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)." diff --git a/translations/fr-FR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/fr-FR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 255f1ee23bc3..4753849d884e 100644 --- a/translations/fr-FR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/fr-FR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -1,6 +1,6 @@ --- -title: Deleting a codespace -intro: You can delete a codespace you no longer need. +title: Suppression d’un codespace +intro: Vous pouvez supprimer un espace de code dont vous n’avez plus besoin. redirect_from: - /github/developing-online-with-github-codespaces/deleting-a-codespace - /github/developing-online-with-codespaces/deleting-a-codespace @@ -13,28 +13,33 @@ topics: - Fundamentals - Developer shortTitle: Delete a codespace +ms.openlocfilehash: 24b53cc0cead2b6b15894ada4c799abc8e1c6e7a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188255' --- - -You can delete a codespace in a variety of ways: in the terminal by using {% data variables.product.prodname_cli %}, in {% data variables.product.prodname_vscode %}, or in your web browser. Use the tabs in this article to display instructions for each of these ways of deleting a codespace. +Vous pouvez supprimer un codespace de différentes manières : dans le terminal avec {% data variables.product.prodname_cli %}, dans {% data variables.product.prodname_vscode %} ou dans votre navigateur web. Utilisez les onglets de cet article afin d’afficher les instructions pour chaque méthode de suppression de codespace. {% note %} -**Note**: You can't delete a codespace from within the JetBrains Gateway, or the JetBrains client application, or from within JupyterLab. +**Remarque** : Vous ne pouvez pas supprimer de codespace à partir de JetBrains Gateway, de l’application cliente JetBrains ou de JupyterLab. {% endnote %} -There are costs associated with storing codespaces. You should therefore delete any codespaces you no longer need. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." +Il existe des coûts associés au stockage des codespaces. Vous devez donc supprimer tous les codespaces dont vous n’avez plus besoin. Pour plus d’informations, consultez « [À propos de la facturation de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces) ». {% data reusables.codespaces.max-number-codespaces %} -## Deleting a codespace +## Suppression d’un codespace {% webui %} {% data reusables.codespaces.your-codespaces-procedure-step %} -1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** +1. À droite du codespace à supprimer, cliquez sur {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, puis sur **{% octicon "trash" aria-label="The trash icon" %} Delete** - ![Delete button](/assets/images/help/codespaces/delete-codespace.png) + ![Bouton Supprimer](/assets/images/help/codespaces/delete-codespace.png) {% endwebui %} @@ -49,48 +54,48 @@ There are costs associated with storing codespaces. You should therefore delete {% data reusables.cli.cli-learn-more %} -To delete a codespace use the `gh codespace delete` subcommand and then choose a codespace from the list that's displayed. +Pour supprimer un codespace, utilisez la sous-commande `gh codespace delete`, puis choisissez un codespace dans la liste affichée. ```shell gh codespace delete ``` -If you have unsaved changes, you'll be prompted to confirm deletion. You can use the `--force` flag to force deletion, avoiding this prompt. +Si vous avez des modifications non enregistrées, vous êtes invité à confirmer la suppression. Vous pouvez utiliser l’indicateur `--force` pour forcer la suppression, ce qui évite cette invite. -For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_delete). +Pour plus d’informations sur cette commande, consultez [le manuel {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_delete). {% endcli %} -## Bulk deleting codespaces +## Suppression en bloc de codespaces {% webui %} -You can use {% data variables.product.prodname_cli %} to delete several or all of your codespaces with a single command. For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page. +Vous pouvez utiliser {% data variables.product.prodname_cli %} pour supprimer plusieurs ou tous vos codespaces avec une seule commande. Pour plus d’informations, cliquez sur l’onglet « {% data variables.product.prodname_cli %} » en haut de cette page. {% endwebui %} {% vscode %} -You can use {% data variables.product.prodname_cli %} to delete several or all of your codespaces with a single command. For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page. +Vous pouvez utiliser {% data variables.product.prodname_cli %} pour supprimer plusieurs ou tous vos codespaces avec une seule commande. Pour plus d’informations, cliquez sur l’onglet « {% data variables.product.prodname_cli %} » en haut de cette page. {% endvscode %} {% cli %} -You can delete several or all of your codespaces with a single command, using `gh codespace delete` followed by one of these flags: +Vous pouvez supprimer plusieurs ou tous vos codespaces avec une seule commande en utilisant `gh codespace delete` et l’un de ces indicateurs : -`--all` - Delete all of your codespaces. +`--all` - Supprimer tous vos codespaces. -`--repo REPOSITORY` - Delete all of your codespaces for this repository. Or use together with the `--days` flag to filter by age of the codespace. +`--repo REPOSITORY` - Supprimer tous vos codespaces pour ce référentiel. Vous pouvez également utiliser l’indicateur `--days` pour filtrer les codespaces par ancienneté. -`--days NUMBER` - Delete all of your codespaces that are older than the specified number of days. Can be used together with the `--repo` flag. +`--days NUMBER` - Supprimer tous vos codespaces antérieurs au nombre de jours spécifié. Peut être utilisé avec l’indicateur `--repo`. -By default you are prompted to confirm deletion of any codespaces that contain unsaved changes. You can use the `--force` flag to skip this confirmation. +Par défaut, vous êtes invité à confirmer la suppression de tous les codespaces contenant des modifications non enregistrées. Vous pouvez utiliser l’indicateur `--force` pour ignorer cette confirmation. -### Example +### Exemple -Delete all of the codespaces for the `octo-org/octo-repo` repository that you created more than 7 days ago. +Supprimez tous les codespaces pour le référentiel `octo-org/octo-repo` que vous avez créé il y a plus de 7 jours. ``` gh codespace delete --repo octo-org/octo-repo --days 7 @@ -98,37 +103,37 @@ gh codespace delete --repo octo-org/octo-repo --days 7 {% endcli %} -## Deleting codespaces in your organization +## Suppression des codespaces de votre organisation -As an organization owner, you can use {% data variables.product.prodname_cli %} to delete any codespace in your organization. +En tant que propriétaire de l’organisation, vous pouvez utiliser {% data variables.product.prodname_cli %} pour supprimer tous les codespaces de votre organisation. {% webui %} -For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page. +Pour plus d’informations, cliquez sur l’onglet « {% data variables.product.prodname_cli %} » en haut de cette page. {% endwebui %} {% vscode %} -For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page. +Pour plus d’informations, cliquez sur l’onglet « {% data variables.product.prodname_cli %} » en haut de cette page. {% endvscode %} {% cli %} -1. Enter one of these commands to display a list of codespaces. - * `gh codespace delete --org ORGANIZATION` - Lists the current codespaces in the specified organization. - * `gh codespace delete --org ORGANIZATION --user USER` - Lists only those codespaces created by the specified user. - You must be an owner of the specified organization. -1. In the list of codespaces, navigate to the codespace you want to delete. -1. To delete the selected codespace press Enter. +1. Entrez l’une de ces commandes pour afficher une liste de codespaces. + * `gh codespace delete --org ORGANIZATION` - Répertorie les codespaces actuels dans l’organisation spécifiée. + * `gh codespace delete --org ORGANIZATION --user USER` - Répertorie uniquement les codespaces créés par l’utilisateur spécifié. + Vous devez être propriétaire de l’organisation spécifiée. +1. Dans la liste des codespaces, accédez au codespace que vous souhaitez supprimer. +1. Pour supprimer le codespace sélectionné, appuyez sur Entrer. - If the codespace contains unsaved changes you will be prompted to confirm deletion. + Si le codespace contient des modifications non enregistrées, vous êtes invité à confirmer la suppression. {% endcli %} -You can also use the REST API to delete codespaces for your organization. For more information, see "[Codespaces organizations](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)." +Vous pouvez également utiliser l’API REST pour supprimer des codespaces de votre organisation. Pour plus d’informations, consultez « [Organisations des codespaces](/rest/codespaces/organizations#delete-a-codespace-from-the-organization) ». -## Further reading -- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)" -- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)" +## Pour aller plus loin +- « [Cycle de vie des codespaces](/codespaces/getting-started/the-codespace-lifecycle) » +- « [Configuration de la suppression automatique de vos codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces) » diff --git a/translations/fr-FR/content/codespaces/developing-in-codespaces/index.md b/translations/fr-FR/content/codespaces/developing-in-codespaces/index.md index bd76975c8444..1929d003f56b 100644 --- a/translations/fr-FR/content/codespaces/developing-in-codespaces/index.md +++ b/translations/fr-FR/content/codespaces/developing-in-codespaces/index.md @@ -22,11 +22,11 @@ children: - /using-github-codespaces-in-visual-studio-code - /using-github-codespaces-in-your-jetbrains-ide - /using-github-codespaces-with-github-cli -ms.openlocfilehash: 166283bd0fbc71b8acc180b20ef597dbc0a50781 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 6ace677a68ce7b592ac8ad2a8b83ae4d948b8747 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159012' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188287' --- diff --git a/translations/fr-FR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/fr-FR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md index c9cdeb389160..76a2876d9bcf 100644 --- a/translations/fr-FR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md +++ b/translations/fr-FR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md @@ -1,6 +1,6 @@ --- -title: Opening an existing codespace -intro: 'You can reopen a codespace that you have closed or stopped and return to your work.' +title: Ouverture d’un codespace existant +intro: 'Vous pouvez rouvrir un codespace que vous avez fermé ou arrêté, et revenir à votre travail.' versions: fpt: '*' ghec: '*' @@ -10,46 +10,51 @@ topics: - Fundamentals - Developer shortTitle: Open an existing codespace +ms.openlocfilehash: b139b7f4e8a696416c97b3c400d09a9f26371b9c +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188295' --- - {% jetbrains %} {% data reusables.codespaces.codespaces-jetbrains-beta-note %} {% endjetbrains %} -You can reopen any of your active or stopped codespaces on {% data variables.product.prodname_dotcom_the_website %}, in a JetBrains IDE, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. You can't reopen a codespace that has been deleted. For more information, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)." +Vous pouvez rouvrir vos codespaces actifs ou arrêtés sur {% data variables.product.prodname_dotcom_the_website %}, dans un IDE JetBrains, dans {% data variables.product.prodname_vscode %} ou en utilisant {% data variables.product.prodname_cli %}. Vous ne pouvez pas rouvrir un codespace qui a été supprimé. Pour plus d’informations, consultez « [Cycle de vie d’un codespace](/codespaces/getting-started/the-codespace-lifecycle) ». -You can view all your codespaces on the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). From this page, you can: +Vous pouvez voir tous vos codespaces dans la page « Vos codespaces » sur [github.com/codespaces](https://github.com/codespaces). À partir de cette page, vous pouvez : -- Open, stop, or delete your codespaces. -- See who owns (and may be billed for) your codespaces: your personal account, or organizations you belong to. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." -- Create a new codespace, either by choosing one of {% data variables.product.company_short %}'s templates or by clicking **New codespace**. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)" and "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)." +- Ouvrez, arrêtez ou supprimez vos codespaces. +- Découvrez à qui appartient vos codespaces (et à qui ils peuvent être facturés) : votre compte personnel ou les organisations auxquelles vous appartenez. Pour plus d’informations, consultez « [À propos de la facturation de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces) ». +- Créez un codespace, soit en choisissant l’un des modèles {% data variables.product.company_short %}, soit en cliquant sur **Nouveau codespace**. Pour plus d’informations, consultez « [Création d’un codespace à partir d’un modèle](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template) » et « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository) ». -## Opening an existing codespace +## Ouverture d’un codespace existant {% webui %} {% data reusables.codespaces.your-codespaces-procedure-step %} -1. To open a codespace in your default editor, click the name of the codespace. {% data reusables.codespaces.about-changing-default-editor %} For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)." +1. Pour ouvrir un codespace dans votre éditeur par défaut, cliquez sur le nom du codespace. {% data reusables.codespaces.about-changing-default-editor %} Pour plus d’informations, consultez « [Définition de votre éditeur par défaut pour {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces) ». - To open the codespace in an editor other than your default: + Pour ouvrir le codespace dans un éditeur autre que votre éditeur par défaut : - 1. Click the ellipsis (**...**) to the right of the codespace you want to open. - 1. Click **Open in**. - 1. Click **Open in APPLICATION**. + 1. Cliquez sur les points de suspension ( **...** ) à droite du codespace que vous souhaitez ouvrir. + 1. Cliquez sur **Ouvrir dans**. + 1. Cliquez sur **Ouvrir dans APPLICATION**. - ![Screenshot of the "Open in" dialog box, with "Open in Visual Studio Code" highlighted](/assets/images/help/codespaces/open-codespace-in-another-editor.png) + ![Capture d’écran de la boîte de dialogue « Ouvrir dans », avec « Ouvrir dans Visual Studio Code » mis en évidence](/assets/images/help/codespaces/open-codespace-in-another-editor.png) - You can open the codespace in: - * Your browser + Vous pouvez ouvrir le codespace dans : + * Votre navigateur * {% data variables.product.prodname_vscode %} * JetBrains Gateway * JupyterLab {% data reusables.codespaces.application-installed-locally %} - If you choose **JupyterLab**, the JupyterLab application must be installed in the codespace. {% data reusables.codespaces.jupyterlab-in-default-image %} + Si vous choisissez **JupyterLab**, l’application JupyterLab doit être installée dans le codespace. {% data reusables.codespaces.jupyterlab-in-default-image %} {% endwebui %} @@ -57,29 +62,28 @@ You can view all your codespaces on the "Your codespaces" page at [github.com/co {% note %} -**Note:** {% data reusables.codespaces.using-codespaces-in-vscode %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)." +**Remarque :** {% data reusables.codespaces.using-codespaces-in-vscode %} Pour plus d’informations, consultez « [Utilisation de {% data variables.product.prodname_github_codespaces %} dans {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code) ». {% endnote %} -1. In the {% data variables.product.prodname_vscode_shortname %} desktop application, open the Command Palette with Command+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux). -1. Type "Codespaces" and select one of the following commands. - - To open a codespace in a new window of {% data variables.product.prodname_vscode_shortname %}, select **Codespaces: Open Codespace in New Window** - - To open a codespace in the web editor, select **Codespaces: Open in Browser** -1. Click the codespace that you want to open. +1. Dans l’application de bureau {% data variables.product.prodname_vscode_shortname %}, ouvrez la palette de commandes avec Commande+Maj+P (Mac) ou Ctrl+Maj+P (Windows/Linux). +1. Tapez « Codespaces » et sélectionnez l’une des commandes suivantes. + - Pour ouvrir un codespace dans une nouvelle fenêtre de {% data variables.product.prodname_vscode_shortname %}, sélectionnez **Codespaces : Ouvrir le codespace dans une nouvelle fenêtre** + - Pour ouvrir un codespace dans l’éditeur web, sélectionnez **Codespaces : Ouvrir dans le navigateur** +1. Cliquez sur le codespace à ouvrir. - ![Screenshot of a list of codespaces in Visual Studio Code](/assets/images/help/codespaces/open-codespace-from-vscode.png) + ![Capture d’écran d’une liste de codespaces dans Visual Studio Code](/assets/images/help/codespaces/open-codespace-from-vscode.png) -You can also access the commands listed above by navigating to the Remote Explorer view in {% data variables.product.prodname_vscode_shortname %} and right-clicking the codespace that you want to open. +Vous pouvez également accéder aux commandes listées ci-dessus en accédant à la vue de l’Explorateur distant dans {% data variables.product.prodname_vscode_shortname %} et en cliquant avec le bouton droit sur le codespace à ouvrir. -![Screenshot of a codespace selected in the Remote Explorer, with "Open in Browser" highlighted](/assets/images/help/codespaces/open-codespace-remote-explorer.png) +![Capture d’écran d’un codespace sélectionné dans l’Explorateur distant, avec « Ouvrir dans le navigateur » mis en évidence](/assets/images/help/codespaces/open-codespace-remote-explorer.png) -{% data reusables.codespaces.remote-explorer %} -{% endvscode %} +{% data reusables.codespaces.remote-explorer %} {% endvscode %} {% cli %} -1. In a terminal, enter one of the following {% data variables.product.prodname_cli %} commands. - - To open a codespace in {% data variables.product.prodname_vscode_shortname %}, enter: +1. Dans un terminal, entrez l’une des commandes {% data variables.product.prodname_cli %} suivantes. + - Pour ouvrir un codespace dans {% data variables.product.prodname_vscode_shortname %}, entrez : ```shell{:copy} gh codespace code @@ -87,17 +91,17 @@ You can also access the commands listed above by navigating to the Remote Explor {% note %} - **Note**: You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. + **Remarque** : Vous devez avoir installé {% data variables.product.prodname_vscode_shortname %} sur votre machine locale. Pour plus d’informations, consultez [Configuration de Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview) dans la documentation {% data variables.product.prodname_vscode_shortname %}. {% endnote %} - - To open a codespace in the browser, enter: + - Pour ouvrir un codespace dans le navigateur, entrez : ```shell{:copy} gh codespace code --web ``` - - To open a codespace in JupyterLab, enter: + - Pour ouvrir un codespace dans JupyterLab, entrez : ```shell{:copy} gh codespace code --jupyter @@ -105,14 +109,14 @@ You can also access the commands listed above by navigating to the Remote Explor {% note %} - **Note**: {% data reusables.codespaces.jupyterlab-installed-in-codespace %} + **Remarque** : {% data reusables.codespaces.jupyterlab-installed-in-codespace %} {% endnote %} -1. Using the arrow keys, navigate to the codespace that you want to open. -1. To open the codespace, press Enter. +1. En utilisant les touches de direction, accédez au codespace que vous voulez ouvrir. +1. Pour ouvrir le codespace, appuyez sur Entrée. -For more information, see [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) in the {% data variables.product.prodname_cli %} manual. +Pour plus d’informations, consultez [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) dans le manuel {% data variables.product.prodname_cli %}. {% endcli %} @@ -120,4 +124,4 @@ For more information, see [`gh codespace code`](https://cli.github.com/manual/gh {% data reusables.codespaces.opening-codespace-in-jetbrains %} -{% endjetbrains %} \ No newline at end of file +{% endjetbrains %} diff --git a/translations/fr-FR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md b/translations/fr-FR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md index 6602cce6b44f..4681ea376e09 100644 --- a/translations/fr-FR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md +++ b/translations/fr-FR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md @@ -1,6 +1,6 @@ --- -title: Stopping and starting a codespace -intro: 'You can stop and start your codespace to save resources and to pause work.' +title: Arrêt et démarrage d’un codespace +intro: Vous pouvez arrêter et démarrer votre codespace pour enregistrer des ressources et mettre le travail en pause. versions: fpt: '*' ghec: '*' @@ -10,28 +10,33 @@ topics: - Fundamentals - Developer shortTitle: Stop a codespace +ms.openlocfilehash: 5c34fd5b7d72f52e203cd8f8fdc1871ff6a2f014 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188247' --- - {% jetbrains %} {% data reusables.codespaces.codespaces-jetbrains-beta-note %} {% endjetbrains %} -## About stopping and starting a codespace +## À propos de l’arrêt et du démarrage d’un codespace {% data reusables.codespaces.stopping-a-codespace %} -Regardless of where you created or access your codespaces, you can view and manage them in your browser at https://github.com/codespaces. +Quel que soit l’emplacement à partir duquel vous avez créez vos codespaces ou y accédez, vous pouvez les voir et les gérer dans votre navigateur sur https://github.com/codespaces. -## Stopping a codespace +## Arrêt d’un codespace {% webui %} {% data reusables.codespaces.navigate-to-codespaces-page %} - 1. To the right of the codespace you want to stop, click the elipsis (**...**). - 1. Click **Stop codespace**. - ![Screenshot of option to stop a codespace](/assets/images/help/codespaces/stop-codespace-webui.png) + 1. À droite du codespace que vous voulez arrêter, cliquez sur les points de suspension ( **...** ). + 1. Cliquez sur **Arrêter le codespace**. + ![Capture d’écran de l’option permettant d’arrêter un codespace](/assets/images/help/codespaces/stop-codespace-webui.png) {% endwebui %} @@ -39,7 +44,7 @@ Regardless of where you created or access your codespaces, you can view and mana {% data reusables.cli.cli-learn-more %} - To stop a codespace use the `gh codespace stop` subcommand and then choose the codespace you want to stop from the list that's displayed. + Pour arrêter un codespace, utilisez la sous-commande `gh codespace stop`, puis choisissez le codespace à arrêter dans la liste affichée. ```shell{:copy} gh codespace stop @@ -50,38 +55,38 @@ Regardless of where you created or access your codespaces, you can view and mana {% vscode %} {% data reusables.vs-code.open-command-palette %} -1. Type `stop` and select **Codespaces: Stop Codespace** from the list of options. -1. In the list of codespaces, select the codespace you want to stop. +1. Tapez `stop` et sélectionnez **Codespaces : Arrêter le codespace** dans la liste des options. +1. Dans la liste des codespaces, sélectionnez celui que vous voulez arrêter. {% endvscode %} {% jetbrains %} -You can stop a codespace from the "Your codespaces" page (see [the web browser instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)) or by using {% data variables.product.prodname_cli %} (see [the CLI instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)). +Vous pouvez arrêter un codespace à partir de la page « Vos codespaces » (consultez [les instructions du navigateur web](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)) ou à l’aide de {% data variables.product.prodname_cli %} (consultez [les instructions de l’interface CLI](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)). {% endjetbrains %} -## Restarting a codespace +## Redémarrage d’un codespace {% webui %} {% data reusables.codespaces.navigate-to-codespaces-page %} -1. Click the name of the codespace you want to restart. -![Screenshot of stopped codespaces](/assets/images/help/codespaces/restart-codespace-webui.png) +1. Cliquez sur le nom du codespace que vous voulez redémarrer. +![Capture d’écran des codespaces arrêtés](/assets/images/help/codespaces/restart-codespace-webui.png) {% endwebui %} {% cli %} -When you restart a codespace you can choose to open it in {% data variables.product.prodname_vscode %} or in your browser. +Quand vous redémarrez un codespace, vous pouvez choisir de l’ouvrir dans {% data variables.product.prodname_vscode %} ou dans votre navigateur. - - To restart a codespace and open it in {% data variables.product.prodname_vscode %}, use the `gh codespace code` subcommand and then choose the codespace you want to restart from the list that's displayed. + - Pour redémarrer un codespace et l’ouvrir dans {% data variables.product.prodname_vscode %}, utilisez la sous-commande `gh codespace code`, puis choisissez le codespace à redémarrer dans la liste affichée. ```shell{:copy} gh codespace code ``` - - To restart a codespace and open it in your browser, use the `gh codespace open --web` subcommand and then choose the codespace you want to restart from the list that's displayed. + - Pour redémarrer un codespace et l’ouvrir dans votre navigateur, utilisez la sous-commande `gh codespace open --web`, puis choisissez le codespace à redémarrer dans la liste affichée. ```shell{:copy} gh codespace open --web @@ -92,8 +97,8 @@ When you restart a codespace you can choose to open it in {% data variables.prod {% vscode %} {% data reusables.vs-code.open-command-palette %} -1. Type `connect` and select **Codespaces: Connect to Codespace** from the list of options. -1. In the list of codespaces, select the codespace you want to restart. +1. Tapez `connect` et sélectionnez **Codespaces : Se connecter au codespace** dans la liste des options. +1. Dans la liste des codespaces, sélectionnez celui que vous voulez redémarrer. {% endvscode %} @@ -103,6 +108,6 @@ When you restart a codespace you can choose to open it in {% data variables.prod {% endjetbrains %} -## Further reading +## Pour aller plus loin -- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)" +- « [Cycle de vie des codespaces](/codespaces/getting-started/the-codespace-lifecycle) » diff --git a/translations/fr-FR/content/codespaces/getting-started/deep-dive.md b/translations/fr-FR/content/codespaces/getting-started/deep-dive.md index 2ec53688b2ec..61cfc1159c8d 100644 --- a/translations/fr-FR/content/codespaces/getting-started/deep-dive.md +++ b/translations/fr-FR/content/codespaces/getting-started/deep-dive.md @@ -9,12 +9,12 @@ versions: type: quick_start topics: - Codespaces -ms.openlocfilehash: 5f97a137ec09191d5cbaa9c10aa280e10f11bbc0 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 01e4f3990cc47f61678811f7c4a77b86626fd8a5 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158644' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188263' --- {% data variables.product.prodname_github_codespaces %} est un environnement de développement instantané et basé sur le cloud qui fournit dans un conteneur les langages, les outils et les utilitaires courants dont vous avez besoin pour développer. {% data variables.product.prodname_github_codespaces %} est également configurable, ce qui vous permet de créer un environnement de développement personnalisé pour votre projet. En configurant un environnement de développement personnalisé pour votre projet, vous pouvez disposer d’une configuration de codespace reproductible pour tous les utilisateurs de votre projet. @@ -161,4 +161,4 @@ Si vous travaillez sur vos codespaces dans un IDE JetBrains, vous pouvez ajouter - « [Activation de {% data variables.product.prodname_github_codespaces %} pour votre organisation](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization) » - « [Gestion du coût de {% data variables.product.prodname_github_codespaces %} dans votre organisation](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization) » - « [Ajouter une configuration de conteneur de développement à votre dépôt](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces) ». -- « [Cycle de vie des codespaces](/codespaces/developing-in-codespaces/the-codespace-lifecycle) » +- « [Cycle de vie des codespaces](/codespaces/getting-started/the-codespace-lifecycle) » diff --git a/translations/fr-FR/content/codespaces/getting-started/index.md b/translations/fr-FR/content/codespaces/getting-started/index.md index a0188bbdbafb..5352daa949d9 100644 --- a/translations/fr-FR/content/codespaces/getting-started/index.md +++ b/translations/fr-FR/content/codespaces/getting-started/index.md @@ -9,11 +9,11 @@ children: - /quickstart - /the-codespace-lifecycle - /deep-dive -ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: e89c26ddd6606192f93449fbc99660afe1fb2506 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159767' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188271' --- diff --git a/translations/fr-FR/content/codespaces/getting-started/the-codespace-lifecycle.md b/translations/fr-FR/content/codespaces/getting-started/the-codespace-lifecycle.md new file mode 100644 index 000000000000..6c4aeceeac9c --- /dev/null +++ b/translations/fr-FR/content/codespaces/getting-started/the-codespace-lifecycle.md @@ -0,0 +1,73 @@ +--- +title: Cycle de vie des codespaces +intro: 'Vous pouvez développer dans un environnement {% data variables.product.prodname_github_codespaces %} et conserver vos données tout au long du cycle de vie du codespace.' +versions: + fpt: '*' + ghec: '*' +type: overview +topics: + - Codespaces + - Developer +redirect_from: + - /codespaces/developing-in-codespaces/codespaces-lifecycle + - /codespaces/developing-in-codespaces/the-codespace-lifecycle +ms.openlocfilehash: 8f223bce2acf2f6dc6200271397c0d70f28aefe4 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188359' +--- +## À propos du cycle de vie d’un codespace + +Le cycle de vie d’un codespace commence lorsque vous créez un codespace et se termine lorsque vous le supprimez. Vous pouvez vous déconnecter et vous reconnecter à un codespace actif sans que cela n’affecte ses processus en cours d’exécution. Vous pouvez arrêter et redémarrer un codespace sans perdre les modifications que vous avez apportées à votre projet. + +## Création d’un codespace + +Lorsque vous souhaitez travailler sur un projet, vous pouvez choisir de créer un codespace ou d’ouvrir un codespace existant. Vous pouvez créer un codespace à partir d’une branche de votre dépôt chaque fois que vous développez dans {% data variables.product.prodname_github_codespaces %} ou conserver un codespace à long terme pour une fonctionnalité. {% data reusables.codespaces.starting-new-project-template %} Pour plus d’informations, consultez « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository) » et « [Création d’un codespace à partir d’un modèle](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template) ». + +{% data reusables.codespaces.max-number-codespaces %} De même, si vous atteignez le nombre maximal de codespaces actifs et que vous essayez d’en démarrer un autre, vous êtes invité à arrêter l’un de vos codespaces actifs. + +Si vous choisissez de créer un codespace chaque fois que vous travaillez sur un projet, vous devez régulièrement envoyer (push) vos modifications afin que les nouvelles validations soient sur {% data variables.product.prodname_dotcom %}. Si vous choisissez d’utiliser un codespace à long terme pour votre projet, vous devez extraire la branche par défaut de votre référentiel chaque fois que vous commencez à travailler dans ce codespace afin que votre environnement dispose des dernières validations. Ce workflow est très similaire à celui qui consiste à travailler sur un projet sur votre ordinateur local. + +{% data reusables.codespaces.prebuilds-crossreference %} + +## Enregistrement des modifications dans un codespace + +Lorsque vous vous connectez à un codespace via le web, l’enregistrement automatique est systématiquement activé pour l’éditeur web et configuré de manière à enregistrer les modifications après un certain délai. Lorsque vous vous connectez à un codespace via {% data variables.product.prodname_vscode %} s’exécutant sur votre bureau, vous devez activer l’enregistrement automatique. Pour plus d’informations, consultez [Enregistrer/Enregistrer automatiquement](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) dans la documentation {% data variables.product.prodname_vscode %}. + +Votre travail sera enregistré sur une machine virtuelle dans le cloud. Vous pouvez fermer et arrêter un codespace et revenir ultérieurement au travail enregistré. En présence de modifications non enregistrées, votre éditeur vous invite à les enregistrer avant de quitter. Toutefois, si votre codespace est supprimé, votre travail l’est également. Pour conserver votre travail, vous devez commiter vos modifications et les pousser (push) vers votre dépôt distant, ou publier votre travail dans un nouveau dépôt distant si vous avez créé votre codespace à partir d’un modèle. Pour plus d’informations, consultez « [Utilisation d’un contrôle de code source dans votre codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace) ». + +## Délais d’expiration pour {% data variables.product.prodname_github_codespaces %} + +Si vous laissez votre codespace s’exécuter sans interaction, ou si vous quittez votre codespace sans l'arrêter explicitement, il s’arrête après une période d'inactivité et cesse de fonctionner. Par défaut, un codespace expire après 30 minutes d’inactivité, mais vous pouvez personnaliser le délai d’expiration des codespaces que vous créez. Pour plus d’informations sur la définition du délai d’expiration par défaut de vos espaces de code, consultez « [Définition de votre délai d’expiration pour {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces) ». Pour plus d’informations sur l’arrêt d’un codespace, consultez « [Arrêt d’un codespace](#stopping-a-codespace) ». + +Lorsqu'un codespace expire, vos données sont conservées à partir du dernier enregistrement de vos modifications. Pour plus d’informations, consultez « [Enregistrement des modifications dans un codespace](#saving-changes-in-a-codespace) ». + +## Reconstruction d’un codespace + +Vous pouvez régénérer votre codespace pour implémenter les modifications apportées à la votre configuration du conteneur de développement. Pour la plupart des utilisations, vous pouvez créer un codespace comme alternative à la reconstruction d’un codespace. Par défaut, lorsque vous régénérez votre codespace, {% data variables.product.prodname_github_codespaces %} réutilisera les images de votre cache pour accélérer le processus de régénération. Vous pouvez également effectuer une régénération complète qui efface votre cache et régénère le conteneur avec de nouvelles images. + +Pour plus d'informations, consultez « [Présentation des conteneurs de développement](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace) » et « [Effectuer une régénération complète d'un conteneur](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container) ». + +## Arrêt d’un codespace + +{% data reusables.codespaces.stopping-a-codespace %} Pour plus d’informations, consultez « [Arrêt et démarrage d’un codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace) ». + +## Suppression d’un codespace + +Vous pouvez créer un codespace pour une tâche particulière, puis le supprimer en toute sécurité après avoir envoyé (push) vos modifications vers une branche distante. + +Si vous essayez de supprimer un codespace avec des validations Git non envoyées (push), votre éditeur vous informe de la présence de modifications non envoyées (push) vers une branche distante. Vous pouvez envoyer les modifications souhaitées, puis supprimer votre codespace ou continuer de supprimer votre codespace et toutes les modifications non validées. Vous pouvez également exporter votre code vers une nouvelle branche sans créer de codespace. Pour plus d’informations, consultez « [Exportation des modifications vers une branche](/codespaces/troubleshooting/exporting-changes-to-a-branch) ». + +Les codespaces qui ont été arrêtés et qui restent inactifs pendant une période spécifiée sont supprimés automatiquement. Par défaut, les codespaces inactifs sont supprimés après 30 jours, mais vous pouvez personnaliser votre période de conservation des codespaces. Pour plus d’informations, consultez « [Configuration de la suppression automatique de vos espaces de code](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces) ». + +Si vous créez un codespace, il accumule des frais de stockage jusqu’à ce qu’il soit supprimé, qu’il soit actif ou arrêté. Pour plus d’informations, consultez « [À propos de la facturation de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage) ». La suppression d’un codespace ne réduit pas le montant facturable actuel pour {% data variables.product.prodname_github_codespaces %}, qui s’accumule pendant chaque cycle de facturation mensuel. Pour plus d’informations, consultez « [Consultation de votre utilisation de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage) ». + +Pour plus d’informations sur la suppression d’un codespace, consultez « [Suppression d’un codespace](/codespaces/developing-in-codespaces/deleting-a-codespace) ». + +## Perte de la connexion lors de l’utilisation de {% data variables.product.prodname_github_codespaces %} + +{% data variables.product.prodname_github_codespaces %} est un environnement de développement cloud et nécessite une connexion Internet. Si vous perdez la connexion à Internet lors de l’utilisation d’un codespace, vous ne pouvez pas accéder à celui-ci. Toutes les modifications non validées sont cependant enregistrées. Une fois la connexion à Internet rétablie, vous pouvez vous connecter à votre codespace dans l'état exact où vous l'avez laissé. En cas de connexion à Internet instable, vous devez valider et envoyer (push) vos modifications régulièrement. + +S’il vous arrive souvent de travailler hors connexion, vous pouvez utiliser votre fichier `devcontainer.json` avec l’[extension « Dev Containers »](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) pour {% data variables.product.prodname_vscode_shortname %} afin de créer et d’attacher un conteneur de développement local pour votre dépôt. Pour plus d’informations, consultez [Développement à l’intérieur d’un conteneur](https://code.visualstudio.com/docs/remote/containers) dans la documentation {% data variables.product.prodname_vscode %}. diff --git a/translations/fr-FR/content/codespaces/index.md b/translations/fr-FR/content/codespaces/index.md index c00065a20f87..156550fd4233 100644 --- a/translations/fr-FR/content/codespaces/index.md +++ b/translations/fr-FR/content/codespaces/index.md @@ -53,11 +53,11 @@ children: - /troubleshooting - /the-githubdev-web-based-editor - /guides -ms.openlocfilehash: 62723c1d4bf684e67420149c96586a91e7583031 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 242931386711938cb1eb5e9b84ad66a581ecb1eb +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160433' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188303' --- diff --git a/translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md b/translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md index 27572d4c1377..b26acdc8dab0 100644 --- a/translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md +++ b/translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md @@ -9,12 +9,12 @@ versions: type: how_to topics: - Codespaces -ms.openlocfilehash: 1da438a680dd3e60c1deeec46a98fbcf48f84e5b -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: f17bb20aa919ca94cd13e14a6f770cea23042b2b +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158996' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188279' --- ## Vue d’ensemble @@ -39,7 +39,7 @@ Si l’image spécifiée dans la configuration de conteneur de développement ne {% note %} **Remarques**: -* La stratégie d’image de base est uniquement appliquée quand un codespace est créé. Elle n’est pas actuellement appliquée quand vous regénérez un conteneur. Ceci sera changé dans une future version. Pour plus d’informations, consultez « [Cycle de vie d’un codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle#rebuilding-a-codespace) ». +* La stratégie d’image de base est uniquement appliquée quand un codespace est créé. Elle n’est pas actuellement appliquée quand vous regénérez un conteneur. Ceci sera changé dans une future version. Pour plus d’informations, consultez « [Cycle de vie d’un codespace](/codespaces/getting-started/the-codespace-lifecycle#rebuilding-a-codespace) ». * La stratégie d’image de base ne s’applique ni à l’image par défaut ni à celle utilisée pour récupérer un codespace si une erreur introduite dans une configuration de conteneur de développement empêche la regénération du conteneur. {% endnote %} diff --git a/translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index d755ec57f7ab..0d3529d219f5 100644 --- a/translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -1,6 +1,6 @@ --- -title: Introduction to dev containers -intro: 'When you work in a codespace, the environment you are working in is created using a development container, or dev container, hosted on a virtual machine.' +title: Présentation des conteneurs de développement +intro: 'Lorsque vous travaillez dans un codespace, l’environnement dans lequel vous travaillez est créé à l’aide d’un conteneur de développement hébergé sur une machine virtuelle.' permissions: People with write permissions to a repository can create or edit the codespace configuration. redirect_from: - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project @@ -16,71 +16,76 @@ topics: - Codespaces - Set up - Fundamentals +ms.openlocfilehash: 646f8068e68040f1d12f8155c3ba9e2bdb84c2ca +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185090' --- +## À propos des conteneurs de développement -## About dev containers +Les conteneurs de développement sont des conteneurs Docker spécifiquement configurés pour fournir un environnement de développement complet. Chaque fois que vous travaillez dans un codespace, vous utilisez un conteneur de développement sur une machine virtuelle. -Development containers, or dev containers, are Docker containers that are specifically configured to provide a fully featured development environment. Whenever you work in a codespace, you are using a dev container on a virtual machine. +Vous pouvez configurer le conteneur de développement pour un dépôt de façon à ce que les codespaces créés pour ce dépôt vous offrent un environnement sur mesure et complet avec l’ensemble des outils et runtimes dont vous avez besoin pour travailler sur un projet spécifique. Si vous ne définissez pas de configuration dans le dépôt, {% data variables.product.prodname_github_codespaces %} utilise une configuration par défaut contenant de nombreux outils courants dont votre équipe pourrait avoir besoin pour le développement de votre projet. Pour plus d’informations, consultez « [Utilisation de la configuration de conteneur de développement par défaut](#using-the-default-dev-container-configuration) ». -You can configure the dev container for a repository so that codespaces created for that repository give you a tailored development environment, complete with all the tools and runtimes you need to work on a specific project. If you don't define a configuration in the repository then {% data variables.product.prodname_github_codespaces %} uses a default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +Les fichiers de configuration d’un conteneur de développement sont contenus dans un répertoire `.devcontainer` dans votre dépôt. Vous pouvez utiliser {% data variables.product.prodname_vscode %} pour ajouter des fichiers de configuration à votre place. Vous pouvez opérer un choix dans une sélection de configurations prédéfinies pour différents types de projet. Vous pouvez utiliser celles-ci sans configuration supplémentaire, ou les modifier pour affiner l’environnement de développement qu’elles produisent. Pour plus d’informations, consultez « [Utilisation d’une configuration de conteneur de développement prédéfinie](#using-a-predefined-dev-container-configuration) ». -The configuration files for a dev container are contained in a `.devcontainer` directory in your repository. You can use {% data variables.product.prodname_vscode %} to add configuration files for you. You can choose from a selection of predefined configurations for various project types. You can use these without further configuration, or you can edit the configurations to refine the development environment they produce. For more information, see "[Using a predefined dev container configuration](#using-a-predefined-dev-container-configuration)." +Vous pouvez également ajouter vos propres fichiers de configuration personnalisés. Pour plus d’informations, consultez « [Création d’une configuration de conteneur de développement personnalisée](#creating-a-custom-dev-container-configuration) ». -Alternatively, you can add your own custom configuration files. For more information, see "[Creating a custom dev container configuration](#creating-a-custom-dev-container-configuration)." +Vous pouvez définir une configuration de conteneur de développement unique pour un dépôt, différentes configurations pour différentes branches ou plusieurs configurations. Lorsque plusieurs configurations sont disponibles, les utilisateurs peuvent choisir leur configuration préférée quand ils créent un codespace. Cela est particulièrement utile pour les dépôts volumineux contenant du code source dans différents langages de programmation ou pour différents projets. Vous pouvez créer un choix de configurations qui permettent à différentes équipes de travailler dans un codespace configuré de manière appropriée pour le travail qu’elles accomplissent. -You can define a single dev container configuration for a repository, different configurations for different branches, or multiple configurations. When multiple configurations are available, users can choose their preferred configuration when they create a codespace. This is particularly useful for large repositories that contain source code in different programming languages or for different projects. You can create a choice of configurations that allow different teams to work in a codespace that's set up appropriately for the work they are doing. - -When you create a codespace from a template, you might start with one or more dev container configuration files in your workspace. To configure your environment further, you can add or remove settings from these files and rebuild the container to apply the changes to the codespace you're working in. If you publish your codespace to a repository on {% data variables.product.product_name %}, then any codespaces created from that repository will share the configuration you've defined. For more information, see "[Applying configuration changes to a codespace](#applying-configuration-changes-to-a-codespace)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository)." +Quand vous créez un codespace à partir d’un modèle, vous pouvez commencer avec un ou plusieurs fichiers de configuration de conteneur de développement dans votre espace de travail. Pour configurer davantage votre environnement, vous pouvez ajouter des paramètres à ces fichiers ou en supprimer et regénérer le conteneur pour appliquer les modifications au codespace dans lequel vous travaillez. Si vous publiez votre codespace dans un dépôt sur {% data variables.product.product_name %}, tous les codespaces créés à partir de ce dépôt partagent la configuration que vous avez définie. Pour plus d’informations, consultez « [Application de modifications de configuration à un codespace](#applying-configuration-changes-to-a-codespace) » et « [Création d’un codespace à partir d’un modèle](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository) ». ### devcontainer.json -The primary file in a dev container configuration is the `devcontainer.json` file. You can use this file to determine the environment of codespaces created for your repository. The contents of this file define a dev container that can include frameworks, tools, extensions, and port forwarding. The `devcontainer.json` file usually contains a reference to a Dockerfile, which is typically located alongside the `devcontainer.json` file. +Le fichier principal d’une configuration de conteneur de développement est le fichier `devcontainer.json`. Vous pouvez l’utiliser pour déterminer l’environnement de codespaces créés pour votre dépôt. Le contenu de ce fichier définit un conteneur de développement qui peut inclure des infrastructures, des outils, des extensions et un réacheminement de port. Le fichier `devcontainer.json` contient généralement une référence à un Dockerfile qui est normalement situé à côté du fichier `devcontainer.json`. -If you create a codespace from a repository without a `devcontainer.json` file, or if you start from {% data variables.product.company_short %}'s blank template, the default dev container configuration is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +Si vous créez un codespace à partir d’un dépôt sans fichier `devcontainer.json` ou que vous commencez à partir du modèle vide de {% data variables.product.company_short %}, la configuration de conteneur de développement par défaut est utilisée. Pour plus d’informations, consultez « [Utilisation de la configuration de conteneur de développement par défaut](#using-the-default-dev-container-configuration) ». -The `devcontainer.json` file is usually located in the `.devcontainer` directory of your repository. Alternatively, you can locate it directly in the root of the repository, in which case the file name must begin with a period: `.devcontainer.json`. +Le fichier `devcontainer.json` se trouve généralement dans le répertoire `.devcontainer` de votre dépôt. Vous pouvez également le placer directement à la racine du dépôt, auquel cas le nom de fichier doit commencer par un point : `.devcontainer.json`. -If you want to have a choice of dev container configurations in your repository, any alternatives to the `.devcontainer/devcontainer.json` (or `.devcontainer.json`) file must be located in their own subdirectory at the path `.devcontainer/SUBDIRECTORY/devcontainer.json`. For example, you could have a choice of two configurations: +Si vous souhaitez disposer d’un choix de configurations de conteneur de développement dans votre dépôt, toutes les alternatives au fichier `.devcontainer/devcontainer.json` (ou `.devcontainer.json`) doivent se trouver dans leur propre sous-répertoire dans le chemin d’accès `.devcontainer/SUBDIRECTORY/devcontainer.json`. Par exemple, vous pourriez avoir le choix entre deux configurations : * `.devcontainer/database-dev/devcontainer.json` * `.devcontainer/gui-dev/devcontainer.json` -When you have multiple `devcontainer.json` files in your repository, each codespace is created from only one of the configurations. Settings cannot be imported or inherited between `devcontainer.json` files. If a `devcontainer.json` file in a custom subdirectory has dependent files, such as the Dockerfile or scripts that are run by commands in the `devcontainer.json` file, it's recommended that you co-locate these files in the same subdirectory. +Lorsque vous avez plusieurs fichiers `devcontainer.json` dans votre dépôt, chaque codespace est créé à partir d’une seule des configurations. Des paramètres ne peuvent pas être importés ou hérités entre fichiers `devcontainer.json`. Si un fichier `devcontainer.json` dans un sous-répertoire personnalisé a des fichiers dépendants, tels que le Dockerfile ou des scripts exécutés par des commandes dans le fichier `devcontainer.json`, il est recommandé de colocaliser ces fichiers dans le même sous-répertoire. -For information about how to choose your preferred dev container configuration when you create a codespace, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." +Pour plus d’informations sur la façon de choisir votre configuration de conteneur de développement préférée quand vous créez un codespace, consultez « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository) ». {% data reusables.codespaces.more-info-devcontainer %} -#### How to use the devcontainer.json +#### Comment utiliser le devcontainer.json -It's useful to think of the `devcontainer.json` file as providing "customization" rather than "personalization." You should only include things that everyone working on your codebase needs as standard elements of the development environment, not things that are personal preferences. Things like linters are good to standardize on, and to require everyone to have installed, so they're good to include in your `devcontainer.json` file. Things like user interface decorators or themes are personal choices that should not be put in the `devcontainer.json` file. +Il est utile de considérer que le fichier `devcontainer.json` fournit une « customisation » plutôt qu’une « personnalisation ». Vous ne devriez inclure que des éléments dont toute personne travaillant sur votre codebase a besoin en tant que composants standard de l’environnement de développement, pas des éléments correspondant à des préférences personnelles. Il est bon de normaliser des éléments tels que des linters en exigeant que chacun les installe, et par conséquent de les inclure dans votre fichier `devcontainer.json`. En revanche, des éléments tels que des éléments décoratifs ou des thèmes d’interface utilisateur sont des choix personnels qui n’ont pas leur place dans le fichier `devcontainer.json`. -You can personalize your codespaces by using dotfiles and Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account)." +Vous pouvez personnaliser vos codespaces à l’aide de dotfiles et d’une Synchronisation des paramètres. Pour plus d’informations, consultez « [Personnalisation de {% data variables.product.prodname_github_codespaces %} pour votre compte](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account) ». ### Dockerfile -You can add a Dockerfile as part of your dev container configuration. +Vous pouvez ajouter un Dockerfile à votre configuration de conteneur de développement. -The Dockerfile is a text file that contains the instructions needed to create a Docker container image. This image is used to generate a development container each time someone creates a codespace using the `devcontainer.json` file that references this Dockerfile. The instructions in the Dockerfile typically begin by referencing a parent image on which the new image that will be created is based. This is followed by commands that are run during the image creation process, for example to install software packages. +Le Dockerfile est un fichier texte contenant les instructions nécessaires pour créer une image conteneur Docker. Cette image est utilisée pour générer un conteneur de développement chaque fois que quelqu’un crée un codespace à l’aide du fichier `devcontainer.json` référençant ce Dockerfile. Les instructions figurant dans le Dockerfile commencent généralement par référencer une image parente sur laquelle sera basée la nouvelle image qui sera créée. Viennent ensuite des commandes qui sont exécutées pendant le processus de création de l’image, par exemple, pour installer des packages logiciels. -The Dockerfile for a dev container is typically located in the `.devcontainer` folder, alongside the `devcontainer.json` in which it is referenced. +Le Dockerfile d’un conteneur de développement se trouve généralement dans le dossier `.devcontainer`, à proximité du `devcontainer.json` dans lequel il est référencé. {% note %} -**Note**: As an alternative to using a Dockerfile you can use the `image` property in the `devcontainer.json` file to refer directly to an existing image you want to use. The image you specify here must be allowed by any organization image policy that has been set. For more information, see "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)." If neither a Dockerfile nor an image is found then the default container image is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +**Remarque** : au lieu d’utiliser un Dockerfile, vous pouvez utiliser la propriété `image` dans le fichier `devcontainer.json` pour faire référence directement à une image existante que vous souhaitez utiliser. L’image que vous spécifiez ici doit être autorisée par toute stratégie d’image d’organisation qui a été définie. Pour plus d’informations, consultez « [Restriction de l’image de base pour les codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces) ». En l’absence de Dockerfile ou d’image, l’image conteneur par défaut est utilisée. Pour plus d’informations, consultez « [Utilisation de la configuration de conteneur de développement par défaut](#using-the-default-dev-container-configuration) ». {% endnote %} -#### Simple Dockerfile example +#### Exemple Dockerfile simple -The following example uses four instructions: +L’exemple suivant utilise quatre instructions : -`ARG` defines a build-time variable. +`ARG` définit une variable de temps de génération. -`FROM` specifies the parent image on which the generated Docker image will be based. +`FROM` spécifie l’image parente sur laquelle l’image Docker générée sera basée. -`COPY` copies a file and adds it to the filesystem. +`COPY` copie un fichier et l’ajoute au système de fichiers. -`RUN` updates package lists and runs a script. You can also use a `RUN` instruction to install software, as shown by the commented out instructions. To run multiple commands, use `&&` to combine the commands into a single `RUN` statement. +`RUN` met à jour les listes de packages et exécute un script. Vous pouvez également utiliser une instruction `RUN` pour installer des logiciels, comme l’indiquent les instructions commentées. Pour exécuter plusieurs commandes, utilisez `&&` pour combiner les commandes dans une seule instruction `RUN`. ```Dockerfile{:copy} ARG VARIANT="16-buster" @@ -97,11 +102,11 @@ COPY library-scripts/github-debian.sh /tmp/library-scripts/ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh ``` -For more information about Dockerfile instructions, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder)" in the Docker documentation. +Pour plus d’informations sur les instructions concernant Dockerfile, consultez « [Dockerfile reference](https://docs.docker.com/engine/reference/builder) » dans la documentation Docker. -#### Using a Dockerfile +#### Utilisation d’un Dockerfile -To use a Dockerfile as part of a dev container configuration, reference it in your `devcontainer.json` file by using the `dockerfile` property. +Pour utiliser un Dockerfile dans une configuration de conteneur de développement, référencez-le dans votre fichier `devcontainer.json` à l’aide de la propriété `dockerfile`. ```json{:copy} { @@ -111,134 +116,134 @@ To use a Dockerfile as part of a dev container configuration, reference it in yo } ``` -Various options are available to you if you want to use existing container orchestration in your dev container. For more information, see the "Orchestration options" section of the [Specification](https://containers.dev/implementors/spec/#orchestration-options) on the Development Containers website. +Différentes options s’offrent à vous si vous souhaitez utiliser l’orchestration de conteneur existante dans votre conteneur de développement. Pour plus d’informations, consultez la section « Options d’orchestration » de la [spécification](https://containers.dev/implementors/spec/#orchestration-options) sur le site web Conteneurs de développement. -## Using the default dev container configuration +## Utilisation de la configuration de conteneur de développement par défaut -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace using a default Linux image. This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the URL that the command outputs. +Si vous ne définissez pas de configuration dans votre dépôt, {% data variables.product.prodname_dotcom %} crée un codespace à l’aide d’une image Linux par défaut. Cette image Linux inclut un certain nombre de versions de runtime pour des langages populaires tels que Python, Node, PHP, Java, Go, C++, Ruby et .NET Core/C#. Les dernières versions LTS de ces langages sont utilisées. Il y a également des outils pour prendre en charge la science des données et l’apprentissage automatique, tels que JupyterLab et Conda. L’image inclut également d’autres outils et utilitaires de développement tels que Git, GitHub CLI, yarn, openssh et vim. Pour voir l’ensemble des langages, runtimes et outils inclus, utilisez la commande `devcontainer-info content-url` à l’intérieur de votre terminal codespace, et suivez l’URL que la commande génère. -For information about what's included in the default Linux image, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal) repository. +Pour plus d’informations sur ce qui est inclus dans l’image Linux par défaut, consultez le dépôt [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal). -The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_github_codespaces %} provides. +La configuration par défaut est une bonne option si vous travaillez sur un petit projet utilisant les langages et outils fournis par {% data variables.product.prodname_github_codespaces %}. -## Using a predefined dev container configuration +## Utilisation d’une configuration de conteneur de développement prédéfinie -If you use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, or in a web browser, you can create a dev container configuration for your repository by choosing from a list of predefined configurations. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. +Si vous utilisez {% data variables.product.prodname_codespaces %} dans {% data variables.product.prodname_vscode %} ou dans un navigateur web, vous pouvez créer une configuration de conteneur de développement pour votre dépôt en choisissant parmi une liste de configurations prédéfinies. Ces configurations fournissent des paramétrages courants pour des types de projets particuliers et peuvent vous aider à démarrer rapidement avec une configuration comprenant déjà les options de conteneur, les paramètres {% data variables.product.prodname_vscode %} et les extensions {% data variables.product.prodname_vscode %} appropriés à installer. -Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. For more information about the definitions of predefined dev containers, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) repository. +L’utilisation d’une configuration prédéfinie est une excellente idée si vous avez besoin d’une extensibilité supplémentaire. Vous pouvez également commencer avec une configuration prédéfinie et la modifier en fonction des besoins de votre projet. Pour plus d’informations sur les définitions de conteneurs de développement prédéfinis, consultez le dépôt [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src). -You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Dev Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar. +Vous pouvez ajouter une configuration de conteneur de développement prédéfinie lorsque vous travaillez dans un codespace ou localement sur un dépôt. Pour y parvenir dans {% data variables.product.prodname_vscode_shortname %} quand vous travaillez localement et que vous n’êtes pas connecté à un codespace, l’extension l’extension « Conteneurs de développement » doit être installée et activée. Pour plus d’informations sur cette extension, consultez la [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). La procédure suivante décrit le processus quand vous utilisez un codespace. Les étapes décrites dans {% data variables.product.prodname_vscode_shortname %} quand vous n’êtes pas connecté à un codespace sont très similaires. {% data reusables.codespaces.command-palette-container %} -1. Click the definition you want to use. +1. Cliquez sur la définition que vous souhaitez utiliser. - ![Screenshot of a list of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) + ![Capture d’écran d’une liste de définitions de conteneur prédéfinies](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Follow the prompts to customize your definition. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)." -1. Click **OK**. +1. Suivez les invites pour personnaliser votre définition. Pour plus d’informations sur les options permettant de personnaliser votre définition, consultez « [Ajout de fonctionnalités à votre fichier `devcontainer.json`](#adding-additional-features-to-your-devcontainerjson-file) ». +1. Cliquez sur **OK**. - ![Screenshot of the OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) + ![Capture d’écran du bouton OK](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. If you are working in a codespace, apply your changes, by clicking **Rebuild now** in the message at the bottom right of the window. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." +1. Si vous travaillez dans un codespace, appliquez vos modifications en cliquant sur **Régénérer maintenant** dans le message en bas à droite de la fenêtre. Pour plus d’informations sur la régénération de votre conteneur, consultez « [Application de modifications à votre configuration](#applying-configuration-changes-to-a-codespace) ». - ![Screenshot of a prompt to 'Rebuild now'](/assets/images/help/codespaces/rebuild-prompt.png) + ![Capture d’écran d’une invite à « regénérer maintenant »](/assets/images/help/codespaces/rebuild-prompt.png) -### Adding additional features to your `devcontainer.json` file +### Ajout de fonctionnalités à votre fichier `devcontainer.json` -{% data reusables.codespaces.about-features %} For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode)." +{% data reusables.codespaces.about-features %} Pour plus d’informations, consultez « [Ajout de fonctionnalités à un fichier `devcontainer.json`](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode) ». -## Creating a custom dev container configuration +## Création d’une configuration de conteneur de développement personnalisée -If none of the predefined configurations meets your needs, you can create a custom configuration by writing your own `devcontainer.json` file. +Si aucune des configurations prédéfinies ne répond à vos besoins, vous pouvez créer une configuration personnalisée en écrivant votre propre fichier `devcontainer.json`. -* If you're adding a single `devcontainer.json` file that will be used by everyone who creates a codespace from your repository, create the file within a `.devcontainer` directory at the root of the repository. -* If you want to offer users a choice of configuration, you can create multiple custom `devcontainer.json` files, each located within a separate subdirectory of the `.devcontainer` directory. +* Si vous ajoutez un seul fichier `devcontainer.json` qui sera utilisé par toute personne créant un codespace à partir de votre dépôt, créez le fichier dans un répertoire `.devcontainer` à la racine du dépôt. +* Si vous souhaitez offrir aux utilisateurs un choix de configuration, vous pouvez créer plusieurs fichiers `devcontainer.json` personnalisés, chacun situé dans un sous-répertoire distinct du répertoire `.devcontainer`. {% note %} - **Notes**: - - You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not. - - {% data reusables.codespaces.configuration-choice-templates %} For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)." + **Remarques**: + - Vous ne pouvez pas placer vos fichiers `devcontainer.json` dans des répertoires situés plusieurs niveaux en dessous de `.devcontainer`. Par exemple, un fichier à l’emplacement `.devcontainer/teamA/devcontainer.json` fonctionnera, mais pas `.devcontainer/teamA/testing/devcontainer.json`. + - {% data reusables.codespaces.configuration-choice-templates %} Pour plus d’informations, consultez « [Configuration d’un dépôt modèle pour {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces) ». {% endnote %} - If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." + Si plusieurs fichiers `devcontainer.json` se trouvent dans le dépôt, ils sont répertoriés dans la page des options de création de codespace. Pour plus d’informations, consultez « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository) ». - ![Screenshot of a choice of configuration files](/assets/images/help/codespaces/configuration-file-choice.png) + ![Capture d’écran d’un choix de fichiers de configuration](/assets/images/help/codespaces/configuration-file-choice.png) -### Adding a `devcontainer.json` file +### Ajout d’un fichier `devcontainer.json` -If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.prodname_dotcom_the_website %}. -1. Navigate to your repository and click the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. -1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**. +Si vous n’avez pas encore de fichier `devcontainer.json` dans votre dépôt, vous pouvez rapidement en ajouter un à partir de {% data variables.product.prodname_dotcom_the_website %}. +1. Accédez à votre dépôt et cliquez sur la liste déroulante **{% octicon "code" aria-label="The code icon" %} Code**. +1. Sous l’onglet **Codespaces**, cliquez sur les points de suspension ( **...** ), puis sélectionnez **Configurer le conteneur de développement**. - ![Screenshot of the Code dropdown, with "Configure dev container" highlighted](/assets/images/help/codespaces/configure-dev-container.png) + ![Capture d’écran de la liste déroulante Code avec « Configurer le conteneur de développement » mis en évidence](/assets/images/help/codespaces/configure-dev-container.png) -A new `.devcontainer/devcontainer.json` file will open in the editor. The file will contain some initial properties, including a `features` object to which you can add new tools, libraries, or runtimes. For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui)." +Un nouveau fichier `.devcontainer/devcontainer.json` s’ouvre dans l’éditeur. Le fichier contient certaines propriétés initiales, notamment un objet `features` auquel vous pouvez ajouter de nouveaux outils, bibliothèques ou runtimes. Pour plus d’informations, consultez « [Ajout de fonctionnalités à un fichier `devcontainer.json`](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui) ». -If your repository already contains one or more `devcontainer.json` files, then clicking **Configure dev container** will open the existing `devcontainer.json` file with the highest precedence according to the [specification](https://containers.dev/implementors/spec/#devcontainerjson) on containers.dev. +Si votre dépôt contient déjà un ou plusieurs fichiers `devcontainer.json`, cliquez sur **Configurer le conteneur de développement** pour ouvrir le fichier `devcontainer.json` existant avec la priorité la plus élevée en fonction de la [spécification](https://containers.dev/implementors/spec/#devcontainerjson) sur containers.dev. -### Default configuration selection during codespace creation +### Sélection de configuration par défaut lors de la création d’un codespace -If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be the default selection in the list of available configuration files when you create a codespace. If neither file exists, the default dev container configuration will be selected by default. +Si les fichiers `.devcontainer/devcontainer.json` ou `.devcontainer.json` existent, il s’agit de la sélection par défaut dans la liste des fichiers de configuration disponibles lorsque vous créez un codespace. Si aucun des fichiers n’existe, la configuration du conteneur de développement par défaut est sélectionnée par défaut. -![Screenshot of the default configuration choice selected](/assets/images/help/codespaces/configuration-file-choice-default.png) +![Capture d’écran montrant le choix de la configuration par défaut sélectionné](/assets/images/help/codespaces/configuration-file-choice-default.png) -### Editing the devcontainer.json file +### Édition du fichier devcontainer.json -You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} +Vous pouvez ajouter et modifier les clés de configuration prises en charge dans le fichier `devcontainer.json` pour spécifier des aspects de l’environnement du codespace, comme les extensions {% data variables.product.prodname_vscode_shortname %} qui seront installées. {% data reusables.codespaces.more-info-devcontainer %} -The `devcontainer.json` file is written using the JSONC (JSON with comments) format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. +Le fichier `devcontainer.json` est écrit au format JSONC (JSON avec commentaires). Cela vous permet d’inclure des commentaires dans le fichier de configuration. Pour plus d’informations, consultez « [Édition de JSON avec {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments) » dans la documentation {% data variables.product.prodname_vscode_shortname %}. {% note %} -**Note**: If you use a linter to validate the `devcontainer.json` file, make sure it is set to JSONC and not JSON or comments will be reported as errors. +**Remarque** : si vous utilisez un linter pour valider le fichier `devcontainer.json`, assurez-vous que celui-ci est défini sur JSONC, non JSON, sans quoi les commentaires seront signalés comme des erreurs. {% endnote %} -### Interface settings for {% data variables.product.prodname_vscode_shortname %} +### Paramètres d’interface pour {% data variables.product.prodname_vscode_shortname %} -You can configure the interface settings for {% data variables.product.prodname_vscode_shortname %}, with three scopes: Workspace, Remote [Codespaces], and User. You can view these scopes in the {% data variables.product.prodname_vscode_shortname %} Settings editor. +Vous pouvez configurer les paramètres d’interface pour {% data variables.product.prodname_vscode_shortname %} avec trois étendues : Espace de travail, [Codespaces] distants et Utilisateur. Vous pouvez afficher ces étendues dans l’éditeur Paramètres de {% data variables.product.prodname_vscode_shortname %}. -![Screenshot showing the choice of scopes in the Settings editor](/assets/images/help/codespaces/scopes-for-vscode.png) +![Capture d’écran montrant le choix des étendues dans l’éditeur Paramètres](/assets/images/help/codespaces/scopes-for-vscode.png) -If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User. +Si un paramètre est défini dans plusieurs étendues, les paramètres de l’étendue Espace de travail sont prioritaires, suivis de ceux de l’étendue [Codespaces] distants et de ceux de l’étendue Utilisateur. -You can define default interface settings for {% data variables.product.prodname_vscode_shortname %} in two places. +Vous pouvez définir des paramètres d’interface par défaut pour {% data variables.product.prodname_vscode_shortname %} à deux endroits. -* Interface settings defined in the `.vscode/settings.json` file in your repository are applied as Workspace-scoped settings in the codespace. -* Interface settings defined in the `settings` key in the `devcontainer.json` file are applied as Remote [Codespaces]-scoped settings in the codespace. +* Les paramètres d’interface définis dans le fichier `.vscode/settings.json` dans votre dépôt sont appliqués en tant que paramètres délimités à l’espace de travail dans le codespace. +* Les paramètres d’interface définis dans la clé `settings` dans le fichier `devcontainer.json` sont appliqués en tant que paramètres délimités à [Codespaces] distants dans le codespace. -## Applying configuration changes to a codespace +## Application de modifications de configuration à un codespace -Changes to a configuration will be applied the next time you create a codespace. However, you can apply your changes to an existing codespace by rebuilding the container. You can do this within a codespace in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application, or you can use {% data variables.product.prodname_cli %}. +Les modifications apportées à une configuration seront appliquées la prochaine fois que vous créerez un codespace. Toutefois, vous pouvez appliquer vos modifications à un codespace existant en régénérant le conteneur. Vous pouvez effectuer cette opération dans un codespace dans le client web ou l’application de bureau {% data variables.product.prodname_vscode_shortname %}, ou vous pouvez utiliser {% data variables.product.prodname_cli %}. -### Rebuilding the dev container in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application +### Regénération du conteneur de développement dans le client web ou l’application de bureau {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.rebuild-command %} 1. {% data reusables.codespaces.recovery-mode %} - ![Screenshot of the error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) + ![Capture d’écran du message d’erreur concernant le mode de récupération](/assets/images/help/codespaces/recovery-mode-error-message.png) - - To diagnose the error by reviewing the creation logs, click **View creation log**. - - To fix the errors identified in the logs, update your `devcontainer.json` file. - - To apply the changes, rebuild your container. + - Pour diagnostiquer l’erreur en révisant les journaux de création, cliquez sur **Afficher le journal de création**. + - Pour corriger les erreurs identifiées dans les journaux, mettez à jour votre fichier `devcontainer.json`. + - Pour appliquer les modifications, régénérez votre conteneur. -### Using {% data variables.product.prodname_cli %} to rebuild a dev container +### Utilisation de {% data variables.product.prodname_cli %} pour régénérer un conteneur de développement -If you've changed a dev container configuration outside of VS Code (for example, on {% data variables.product.prodname_dotcom_the_website %} or in a JetBrains IDE), you can use {% data variables.product.prodname_cli %} to rebuild the dev container for an existing codespace. +Si vous avez modifié une configuration de conteneur de développement en dehors de VS Code (par exemple, sur {% data variables.product.prodname_dotcom_the_website %} ou dans un IDE JetBrains), vous pouvez utiliser {% data variables.product.prodname_cli %} pour reconstruire le conteneur de développement d’un codespace existant. -1. In a terminal, enter the following command. +1. Dans le terminal, entrez la commande suivante. ``` gh cs rebuild ``` - Your codespaces are listed. + Vos codespaces sont répertoriés. -1. Use the arrow keys on your keyboard to highlight the required codespace, then press Enter. +1. Utilisez les touches de direction de votre clavier pour mettre en surbrillance l’espace de code requis, puis appuyez sur Entrée. -## Further reading +## Pour aller plus loin -- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)" +- « [Pré-génération de vos codespaces](/codespaces/prebuilding-your-codespaces) » diff --git a/translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md index ff71d2bec892..44aa07505cf3 100644 --- a/translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md +++ b/translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: Création d’un modèle de demande de tirage pour votre dépôt -intro: 'Quand vous ajoutez un modèle de demande de tirage (pull request) à votre dépôt, les contributeurs du projet voient automatiquement le contenu de ce modèle dans le corps de la demande de tirage.' +title: Creating a pull request template for your repository +intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.' redirect_from: - /articles/creating-a-pull-request-template-for-your-repository - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository @@ -12,44 +12,41 @@ versions: topics: - Community shortTitle: Create a PR template -ms.openlocfilehash: 2a85c88944f1d46209429846bba1e7a3c930968e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: fr-FR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145086514' --- -Pour plus d’informations, consultez « [À propos des modèles de problème et de demande de tirage](/articles/about-issue-and-pull-request-templates) ». -Vous pouvez créer un sous-répertoire *PULL_REQUEST_TEMPLATE/* dans l’un des dossiers pris en charge pour y stocker plusieurs modèles de demande de tirage (pull request), puis utiliser le paramètre de requête `template` pour spécifier le modèle qui va remplir le corps de la demande de tirage. Pour plus d’informations, consultez « [Utilisation de paramètres de requête pour créer une demande de tirage](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request) ». +For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." + +You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." {% ifversion fpt or ghes or ghec %} -Vous pouvez créer des modèles de demande de tirage par défaut pour votre organisation{% ifversion fpt or ghes or ghec %} ou votre compte personnel{% endif %}. Pour plus d’informations, consultez « [Création d’un fichier d’intégrité de la communauté par défaut](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file) ». +You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} -## Ajout d’un modèle de demande de tirage - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. Dans le champ du nom de fichier : - - Pour rendre votre modèle de demande de tirage visible dans le répertoire racine du dépôt, nommez le modèle de demande de tirage `pull_request_template.md`. - ![Nom du nouveau modèle de demande de tirage dans le répertoire racine](/assets/images/help/repository/pr-template-file-name.png) - - Pour rendre votre modèle de demande de tirage visible dans le répertoire `docs` du dépôt, nommez le modèle de demande de tirage `docs/pull_request_template.md`. - ![Nouveau modèle de demande de tirage dans le répertoire docs](/assets/images/help/repository/pr-template-file-name-docs.png) - - Pour stocker votre fichier dans un répertoire masqué, nommez le modèle de demande de tirage `.github/pull_request_template.md`. - ![Nouveau modèle de demande de tirage dans un répertoire masqué](/assets/images/help/repository/pr-template-hidden-directory.png) - - Pour créer plusieurs modèles de demande de tirage et utiliser le paramètre de requête `template` afin de spécifier un modèle permettant de remplir le corps de la demande de tirage, tapez *.github/PULL_REQUEST_TEMPLATE/* , puis le nom de votre modèle de demande de tirage. Par exemple : `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. Vous pouvez également stocker plusieurs modèles de demande de tirage (pull request) dans un sous-répertoire `PULL_REQUEST_TEMPLATE` au sein du répertoire racine ou du répertoire `docs/`. Pour plus d’informations, consultez « [À propos de l’automatisation des problèmes et des demandes de tirage avec des paramètres de requête](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters) ». - ![Nouveau modèle de demande de tirage multiple dans un répertoire masqué](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) -4. Dans le corps du nouveau fichier, ajoutez votre modèle de demande de tirage. Vous pouvez inclure ce qui suit : - - [Référence à un problème connexe](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) dans votre dépôt. - - Description des changements proposés dans la demande de tirage. - - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) de la personne ou de l’équipe responsable de la revue les changements proposés. -{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} Les modèles sont accessibles aux collaborateurs quand ils sont fusionnés avec la branche par défaut du dépôt. +## Adding a pull request template + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field: + - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`. + ![New pull request template name in root directory](/assets/images/help/repository/pr-template-file-name.png) + - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`. + ![New pull request template in docs directory](/assets/images/help/repository/pr-template-file-name-docs.png) + - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`. + ![New pull request template in hidden directory](/assets/images/help/repository/pr-template-hidden-directory.png) + - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." + ![New multiple pull request template in hidden directory](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) +4. In the body of the new file, add your pull request template. This could include: + - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository. + - A description of the changes proposed in the pull request. + - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch. {% data reusables.files.propose_new_file %} -## Pour aller plus loin +## Further reading -- « [À propos des modèles de problème et de demande de tirage](/articles/about-issue-and-pull-request-templates) » -- « [À propos de l’automatisation des problèmes et des demandes de tirage avec des paramètres de requête](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters) » -- « [Création d’une demande de tirage](/articles/creating-a-pull-request) » +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating a pull request](/articles/creating-a-pull-request)" diff --git a/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md b/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md index fafd93d4dd63..1b16e3b57663 100644 --- a/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md +++ b/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md @@ -1,123 +1,125 @@ --- -title: Getting started with GitHub Copilot in a JetBrains IDE +title: Bien démarrer avec GitHub Copilot dans un IDE JetBrains shortTitle: JetBrains IDE -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in a JetBrains IDE, and start seeing suggestions as you write comments and code.' +intro: 'Découvrez comment installer {% data variables.product.prodname_copilot %} dans un IDE JetBrains, et commencez à voir des suggestions lorsque vous écrivez des commentaires et du code.' product: '{% data reusables.gated-features.copilot %}' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: ae879b5834007a34ab0e3a7a45dcae4c1e31bc4f +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185058' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and JetBrains IDEs +## À propos de {% data variables.product.prodname_copilot %} et des IDE JetBrains {% data reusables.copilot.procedural-intro %} -If you use a JetBrains IDE, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within a JetBrains IDE for macOS, Windows, or Linux. +Si vous utilisez un IDE JetBrains, vous pouvez visualiser et intégrer les suggestions de {% data variables.product.prodname_copilot %} directement dans l’éditeur. Ce guide montre comment utiliser {% data variables.product.prodname_copilot %} dans un IDE JetBrains pour macOS, Windows ou Linux. -## Prerequisites +## Prérequis {% data reusables.copilot.jetbrains-ides %} -## Installing the {% data variables.product.prodname_copilot %} extension in your JetBrains IDE - -To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} extension. The following procedure will guide you through installation of the {% data variables.product.prodname_copilot %} plugin in IntelliJ IDEA. Steps to install the plugin in another supported IDE may differ. - -1. In your JetBrains IDE, under the **File** menu for Windows or under the name of your IDE for Mac (for example, **PyCharm** or **IntelliJ**), click **Settings** for Windows or **Preferences** for Mac. -2. In the left-side menu of the **Settings/Preferences** dialog box, click **Plugins**. -3. At the top of the **Settings/Preferences** dialog box, click **Marketplace**. In the search bar, search for **{% data variables.product.prodname_copilot %}**, then click **Install**. - ![Screenshot of Marketplace search](/assets/images/help/copilot/jetbrains-marketplace.png) -1. After {% data variables.product.prodname_copilot %} is installed, click **Restart IDE**. -1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**. - ![Screenshot of JetBrains tools menu](/assets/images/help/copilot/jetbrains-tools-menu.png) -1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**. - ![Screenshot of device code copy and open](/assets/images/help/copilot/device-code-copy-and-open.png) -1. A device activation window will open in your browser. Paste the device code, then click **Continue**. - - - To paste the code in Windows or Linux, press Ctrl+v. - - To paste the code in macOS, press command+v. -1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**. -1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**. - ![Screenshot of JetBrains IDE permissions confirmation](/assets/images/help/copilot/jetbrains-ide-confirmation.png) +## Installation de l’extension {% data variables.product.prodname_copilot %} dans votre IDE JetBrains + +Pour utiliser {% data variables.product.prodname_copilot %} dans un IDE JetBrains, vous devez installer l’extension {% data variables.product.prodname_copilot %}. La procédure suivante vous guide tout au long de l’installation du plug-in {% data variables.product.prodname_copilot %} dans IntelliJ IDEA. Les étapes d’installation du plug-in peuvent différer dans les autres IDE pris en charge. + +1. Dans votre IDE JetBrains, sous le menu **Fichier** pour Windows, ou sous le nom de votre IDE pour Mac (par exemple **, PyCharm** ou **IntelliJ**), cliquez sur **Paramètres** pour Windows ou **Préférences** pour Mac. +2. Dans le menu de gauche de la boîte de dialogue **Paramètres/Préférences**, cliquez sur **Plug-ins**. +3. En haut de la boîte de dialogue **Paramètres/Préférences**, cliquez sur **Marketplace**. Dans la barre de recherche, recherchez **{% data variables.product.prodname_copilot %}** , puis cliquez sur **Installer**. + ![Capture d’écran de la recherche Marketplace](/assets/images/help/copilot/jetbrains-marketplace.png) +1. Une fois {% data variables.product.prodname_copilot %} installé, cliquez sur **Redémarrer l’IDE**. +1. Une fois votre IDE JetBrains redémarré, cliquez sur le menu **Outils**. Cliquez sur **{% data variables.product.prodname_copilot %}** , puis cliquez sur **Se connecter à {% data variables.product.prodname_dotcom %}** . + ![Capture d’écran du menu Outils JetBrains](/assets/images/help/copilot/jetbrains-tools-menu.png) +1. Dans la boîte de dialogue « Se connecter à {% data variables.product.prodname_dotcom %} », pour copier le code de l’appareil et ouvrir la fenêtre d’activation de l’appareil, cliquez sur **Copier et ouvrir**. + ![Capture d’écran de la copie et de l’ouverture du code de l’appareil](/assets/images/help/copilot/device-code-copy-and-open.png) +1. Une fenêtre d’activation d’appareil s’ouvrira dans votre navigateur. Collez le code de l’appareil, puis cliquez sur **Continuer**. + + - Pour coller le code sur un système Windows ou Linux, appuyez sur Ctrl+v. + - Pour coller le code sur un système macOS, appuyez sur commande+v. +1. {% data variables.product.prodname_dotcom %} demandera les autorisations nécessaires pour {% data variables.product.prodname_copilot %}. Pour approuver ces autorisations, cliquez sur **Autoriser le plug-in {% data variables.product.prodname_copilot %}** . +1. Une fois les autorisations approuvées, votre IDE JetBrains affichera une confirmation. Pour commencer à utiliser {% data variables.product.prodname_copilot %}, cliquez sur **OK**. + ![Capture d’écran de la confirmation des autorisations IDE JetBrains](/assets/images/help/copilot/jetbrains-ide-confirmation.png) -## Seeing your first suggestion +## Voir votre première suggestion {% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in Java, but other languages will work similarly. +{% data reusables.copilot.supported-languages %} Les exemples suivants sont en Java. Cependant, d’autres langages ont un fonctionnement similaire. {% data reusables.copilot.create-java-file %} -1. In the Java file, create a class by typing `class Test`. - {% data variables.product.prodname_copilot %} will automatically suggest a class body in grayed text, as shown below. The exact suggestion may vary. - ![Screenshot of the Java class body suggestion](/assets/images/help/copilot/java-class-body-suggestion-jetbrains.png) -{% data reusables.copilot.accept-suggestion %} -1. To prompt {% data variables.product.prodname_copilot %} to suggest a function body, type the following line below the bracket of the `main` function. The exact suggestion may vary. +1. Dans le fichier Java, créez une classe en tapant `class Test`. + {% data variables.product.prodname_copilot %} suggère automatiquement un corps de classe en texte grisé, comme indiqué ci-dessous. La suggestion exacte peut varier. + ![Capture d’écran de la suggestion de corps de classe Java](/assets/images/help/copilot/java-class-body-suggestion-jetbrains.png) {% data reusables.copilot.accept-suggestion %} +1. Pour inviter {% data variables.product.prodname_copilot %} à suggérer un corps de fonction, tapez la ligne suivante sous le crochet de la fonction `main`. La suggestion exacte peut varier. {% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} - ![Screenshot of the Java function body suggestion](/assets/images/help/copilot/java-function-body-suggestion-jetbrains.png) -{% data reusables.copilot.accept-suggestion %} + ![Capture d’écran de la suggestion de corps de fonction Java](/assets/images/help/copilot/java-function-body-suggestion-jetbrains.png) {% data reusables.copilot.accept-suggestion %} -{% data variables.product.prodname_copilot %} will attempt to match the context and style of your code. You can always edit the suggested code. +{% data variables.product.prodname_copilot %} tentera de correspondre au contexte et au style de votre code. Vous pouvez toujours modifier le code suggéré. -## Seeing alternative suggestions +## Voir d’autres suggestions {% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file. -{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} -{% data reusables.copilot.see-alternative-suggestions %} +1. Pour inviter {% data variables.product.prodname_copilot %} à afficher une suggestion, tapez la ligne suivante dans le fichier Java. +{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} {% data reusables.copilot.see-alternative-suggestions %} - | OS | See next suggestion | See previous suggestion | + | Système d''exploitation | Voir la suggestion suivante | Voir la suggestion précédente | | :- | :- | :- | | macOS | Option+] | Option+[ | | Windows | Alt+] | Alt+[ | | Linux | Alt+] | Alt+[ | {% data reusables.copilot.accept-or-reject-suggestion %} -## Seeing multiple suggestions in a new tab +## Affichage de plusieurs suggestions sous un nouvel onglet {% data reusables.copilot.suggestions-new-tab %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file. +1. Pour inviter {% data variables.product.prodname_copilot %} à afficher une suggestion, tapez la ligne suivante dans le fichier Java. {% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} -1. Open a new tab with multiple additional suggestions. - - On macOS, press Command+Shift+A, then click **Open GitHub Copilot**, or press Command+Shift+\ to open the new tab immediately. - - On Windows or Linux, press Ctrl+Enter, then click **Open GitHub Copilot**. - ![Screenshot of dialogue to open Copilot](/assets/images/help/copilot/open-copilot-tab-jetbrains.png) -1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab. +1. Ouvrez un nouvel onglet avec plusieurs suggestions supplémentaires. + - Sur macOS, appuyez sur Commande+Maj+A, puis cliquez sur **Ouvrir GitHub Copilot**, ou appuyez sur Commande+Maj+\ pour ouvrir immédiatement le nouvel onglet. + - Sur Windows ou Linux, appuyez sur Ctrl+Entrée, puis cliquez sur **Ouvrir GitHub Copilot**. + ![Capture d’écran de la boîte de dialogue d’ouverture de Copilot](/assets/images/help/copilot/open-copilot-tab-jetbrains.png) +1. Pour accepter une suggestion, au-dessus de celle-ci, cliquez sur **Accepter la solution**. Pour rejeter toutes les suggestions, fermez l’onglet. -## Generating code suggestions from comments +## Génération de suggestions de code à partir de commentaires {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to suggest an implementation of a function in the Java file, type the following lines. +1. Pour inviter {% data variables.product.prodname_copilot %} à suggérer une implémentation d’une fonction dans le fichier Java, tapez les lignes suivantes. ```java{:copy} // find all images without alternate text // and give them a red border void process () { ``` - ![Screenshot of the Java function body suggestion](/assets/images/help/copilot/comment-suggestion-jetbrains.png) + ![Capture d’écran de la suggestion de corps de la fonction Java](/assets/images/help/copilot/comment-suggestion-jetbrains.png) -## Enabling and disabling {% data variables.product.prodname_copilot %} +## Activation et désactivation de {% data variables.product.prodname_copilot %} -You can enable or disable {% data variables.product.prodname_copilot %} for all languages, or for individual languages. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of your JetBrains IDE window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out. +Vous pouvez activer ou désactiver {% data variables.product.prodname_copilot %} pour tous les langages ou seulement certains langages. L’icône d’état {% data variables.product.prodname_copilot %} dans le panneau inférieur de la fenêtre de l’IDE JetBrains indique si {% data variables.product.prodname_copilot %} est activé ou désactivé. Quand cette option est activée, l’icône est mise en évidence. Quand elle est désactivée, l’icône est grisée. -1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window. - ![Screenshot of the status icon in IntelliJ IDEA](/assets/images/help/copilot/status-icon-jetbrains.png) -2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable it globally, or for the language of the file you are currently editing. +1. Pour activer ou désactiver {% data variables.product.prodname_copilot %}, cliquez sur l’icône d’état dans le panneau inférieur de la fenêtre JetBrains. + ![Capture d’écran de l’icône d’état dans IntelliJ IDEA](/assets/images/help/copilot/status-icon-jetbrains.png) +2. Si vous désactivez {% data variables.product.prodname_copilot %}, il vous sera demandé si vous souhaitez le désactiver entièrement ou seulement pour le langage du fichier que vous êtes en train de modifier. - - To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Completions**. - - To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable Completions for _LANGUAGE_**. - ![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png) + - Pour désactiver les suggestions de {% data variables.product.prodname_copilot %} globalement, cliquez sur **Désactiver les saisies semi-automatiques**. + - Pour désactiver les suggestions de {% data variables.product.prodname_copilot %} pour le langage spécifié, cliquez sur **Désactiver les saisies semi-automatiques pour _LANGAGE_**. + ![Capture d’écran de l’option permettant de désactiver {% data variables.product.prodname_copilot %} globalement ou pour le langage actuel](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png) -## Further reading +## Pour aller plus loin -- [The {% data variables.product.prodname_copilot %} website](https://copilot.github.com/) -- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides) +- [Site web de {% data variables.product.prodname_copilot %}](https://copilot.github.com/) +- [À propos de {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides) diff --git a/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md b/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md index bc783d3b490d..5890c5006ff6 100644 --- a/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md +++ b/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md @@ -1,34 +1,39 @@ --- -title: Getting started with GitHub Copilot in Neovim +title: Bien démarrer avec GitHub Copilot dans Neovim shortTitle: Neovim product: '{% data reusables.gated-features.copilot %}' -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in Neovim, and start seeing suggestions as you write comments and code.' +intro: 'Découvrez comment installer {% data variables.product.prodname_copilot %} dans Neovim, et commencez à voir des suggestions lorsque vous écrivez des commentaires et du code.' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 6296ff5b89e86b4b51cbb04bd9ac4ba91863a1ac +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185066' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and Neovim +## À propos de {% data variables.product.prodname_copilot %} et de Neovim {% data reusables.copilot.procedural-intro %} -If you use a Neovim, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. +Si vous utilisez Neovim, vous pouvez visualiser et intégrer les suggestions de {% data variables.product.prodname_copilot %} directement dans l’éditeur. -## Prerequisites +## Prérequis -- To use {% data variables.product.prodname_copilot %} you must have an active {% data variables.product.prodname_copilot %} subscription. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)." +- Pour utiliser {% data variables.product.prodname_copilot %}, vous devez disposer d’un abonnement {% data variables.product.prodname_copilot %} actif. Pour plus d’informations, consultez « [À propos de la facturation pour {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot) ». -- To use {% data variables.product.prodname_copilot %} in Neovim you must have Neovim and Node.js version 17 or below installed. For more information, see the [Neovim documentation](https://neovim.io/doc/) and the [Node.js website](https://nodejs.org/en/). +- Pour utiliser {% data variables.product.prodname_copilot %} dans Neovim, vous devez avoir Neovim et Node.js version 17 ou version inférieure installés. Pour plus d’informations, consultez la [documentation de Neovim](https://neovim.io/doc/) et le [ site web Node.js](https://nodejs.org/en/). -## Installing the Neovim extension +## Installation de l’extension Neovim {% mac %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Terminal. + - Pour installer {% data variables.product.prodname_copilot %} avec le gestionnaire de plug-ins intégré de Neovim, entrez la commande suivante dans Terminal. git clone https://github.com/github/copilot.vim \ ~/.config/nvim/pack/github/start/copilot.vim @@ -41,7 +46,7 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% windows %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Git Bash. + - Pour installer {% data variables.product.prodname_copilot %} avec le gestionnaire de plug-ins intégré de Neovim, entrez la commande suivante dans Git Bash. git clone https://github.com/github/copilot.vim.git ` $HOME/AppData/Local/nvim/pack/github/start/copilot.vim @@ -54,7 +59,7 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% linux %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command: + - Pour installer {% data variables.product.prodname_copilot %} avec le gestionnaire de plug-ins intégré de Neovim, entrez la commande suivante : git clone https://github.com/github/copilot.vim \ ~/.config/nvim/pack/github/start/copilot.vim @@ -63,14 +68,14 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% endlinux %} -## Learning to use {% data variables.product.prodname_copilot %} in Neovim +## En savoir plus sur l’utilisation de {% data variables.product.prodname_copilot %} dans Neovim -For guidance on using {% data variables.product.prodname_copilot %} in Neovim, you can view the plugin documentation. To see the documentation, open Neovim and run the following command. +Pour obtenir de l’aide sur l’utilisation de {% data variables.product.prodname_copilot %} dans Neovim, vous pouvez consulter la documentation du plug-in. Pour consulter la documentation, ouvrez Neovim et exécutez la commande suivante. ``` :help copilot ``` -## Further reading +## Pour aller plus loin - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) diff --git a/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md b/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md index 9894db0413d9..0f46820d2816 100644 --- a/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md +++ b/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md @@ -1,105 +1,109 @@ --- -title: Getting started with GitHub Copilot in Visual Studio Code +title: Bien démarrer avec GitHub Copilot dans Visual Studio Code shortTitle: Visual Studio Code -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, and start seeing suggestions as you write comments and code.' +intro: 'Découvrez comment installer {% data variables.product.prodname_copilot %} dans {% data variables.product.prodname_vscode %}, et commencez à voir des suggestions lorsque vous écrivez des commentaires et du code.' product: '{% data reusables.gated-features.copilot %}' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 63c670a7cd5263057f79b7761a960854ecac2dd6 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185132' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_vscode %} +## À propos de {% data variables.product.prodname_copilot %} et de {% data variables.product.prodname_vscode %} {% data reusables.copilot.procedural-intro %} -If you use {% data variables.product.prodname_vscode %}, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within {% data variables.product.prodname_vscode %} for macOS, Windows, or Linux. +Si vous utilisez {% data variables.product.prodname_vscode %}, vous pouvez visualiser et intégrer les suggestions de {% data variables.product.prodname_copilot %} directement dans l’éditeur. Ce guide montre comment utiliser {% data variables.product.prodname_copilot %} dans {% data variables.product.prodname_vscode %} pour macOS, Windows ou Linux. -## Prerequisites +## Prérequis -To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, you must have {% data variables.product.prodname_vscode %} installed. For more information, see the [{% data variables.product.prodname_vscode %} download page](https://code.visualstudio.com/Download). +Pour utiliser {% data variables.product.prodname_copilot %} dans {% data variables.product.prodname_vscode %}, vous devez avoir installé {% data variables.product.prodname_vscode %}. Pour plus d’informations, consultez la [page de téléchargement {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/Download). -## Installing the {% data variables.product.prodname_vscode %} extension +## Installation de l’extension {% data variables.product.prodname_vscode %} -To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vscode %} extension. +Pour utiliser {% data variables.product.prodname_copilot %}, vous devez d’abord installer l’extension {% data variables.product.prodname_vscode %}. -1. In the {% data variables.product.prodname_vscode %} Marketplace, go to the [{% data variables.product.prodname_copilot %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) page and click **Install**. - ![Install {% data variables.product.prodname_copilot %} extension {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png) -1. A popup will appear, asking to open {% data variables.product.prodname_vscode %}. Click **Open {% data variables.product.prodname_vscode %}**. -1. In the "Extension: {% data variables.product.prodname_copilot %}" tab in {% data variables.product.prodname_vscode %}, click **Install**. - ![Install button in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/in-visual-studio-code-install-button.png) -1. If you have not previously authorized {% data variables.product.prodname_vscode %} in your {% data variables.product.prodname_dotcom %} account, you will be prompted to sign in to {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_vscode %}. - - If you have previously authorized {% data variables.product.prodname_vscode %} for your account on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_copilot %} will be automatically authorized. - ![Screen shot of {% data variables.product.prodname_vscode %} authorization screen](/assets/images/help/copilot/vsc-copilot-authorize.png) -1. In your browser, {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_vscode %}**. -1. In {% data variables.product.prodname_vscode %}, in the "{% data variables.product.prodname_vscode %}" dialog box, to confirm the authentication, click **Open**. +1. Dans {% data variables.product.prodname_vscode %} Marketplace, accédez à la page de l’[extension {% data variables.product.prodname_copilot %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) et cliquez sur **Installer**. + ![Installer l’extension {% data variables.product.prodname_copilot %} {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png) +1. Une fenêtre contextuelle s’affiche, vous demandant d’ouvrir {% data variables.product.prodname_vscode %}. Cliquez sur **Ouvrir {% data variables.product.prodname_vscode %}** . +1. Sous l’onglet « Extension : {% data variables.product.prodname_copilot %} » dans {% data variables.product.prodname_vscode %}, cliquez sur **Installer**. + ![Bouton Installer dans {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/in-visual-studio-code-install-button.png) +1. Si vous n’avez pas déjà autorisé {% data variables.product.prodname_vscode %} dans votre compte {% data variables.product.prodname_dotcom %}, vous serez invité à vous connecter à {% data variables.product.prodname_dotcom %} dans {% data variables.product.prodname_vscode %}. + - Si vous avez déjà autorisé {% data variables.product.prodname_vscode %} pour votre compte {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_copilot %} sera automatiquement autorisé. + ![Capture d’écran de l’écran d’autorisation {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/vsc-copilot-authorize.png) +1. Dans votre navigateur, {% data variables.product.prodname_dotcom %} demandera les autorisations nécessaires pour {% data variables.product.prodname_copilot %}. Pour approuver ces autorisations, cliquez sur **Autoriser {% data variables.product.prodname_vscode %}** . +1. Dans {% data variables.product.prodname_vscode %}, dans la boîte de dialogue « {% data variables.product.prodname_vscode %} », pour confirmer l’authentification, cliquez sur **Ouvrir**. -## Seeing your first suggestion +## Voir votre première suggestion {% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in JavaScript, but other languages will work similarly. +{% data reusables.copilot.supported-languages %} Les exemples suivants sont en JavaScript. Cependant, d’autres langages ont un fonctionnement similaire. {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary. +1. Dans le fichier JavaScript, tapez l’en-tête de fonction suivant. {% data variables.product.prodname_copilot %} suggère automatiquement un corps de fonction entier en texte grisé, comme indiqué ci-dessous. La suggestion exacte peut varier. ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` - ![Screenshot of a first suggestion {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/first-suggestion-visual-studio-code.png) -{% data reusables.copilot.accept-suggestion %} + ![Capture d’écran d’une première suggestion {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/first-suggestion-visual-studio-code.png) {% data reusables.copilot.accept-suggestion %} -## Seeing alternative suggestions +## Voir d’autres suggestions {% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion. +1. Dans le fichier JavaScript, tapez l’en-tête de fonction suivant. {% data variables.product.prodname_copilot %} affichera une suggestion. ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` {% data reusables.copilot.see-alternative-suggestions %} - | OS | See next suggestion | See previous suggestion | + | Système d''exploitation | Voir la suggestion suivante | Voir la suggestion précédente | | :- | :- | :- | - |macOS|Option (⌥) or Alt+]|Option (⌥) or Alt+[| + |macOS|Option (⌥) ou Alt+]|Option (⌥) ou Alt+[| |Windows|Alt+]|Alt+[| |Linux|Alt+]|Alt+[| -1. Alternatively, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions. +1. Si vous le souhaitez, vous pouvez pointer sur la suggestion pour afficher la palette de commandes {% data variables.product.prodname_copilot %} afin de choisir des suggestions. {% data reusables.copilot.accept-or-reject-suggestion %} -## Seeing multiple suggestions in a new tab +## Affichage de plusieurs suggestions sous un nouvel onglet {% data reusables.copilot.suggestions-new-tab %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion. +1. Dans le fichier JavaScript, tapez l’en-tête de fonction suivant. {% data variables.product.prodname_copilot %} affichera une suggestion. ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` -1. To open a new tab with multiple additional options, press Ctrl+Enter. -1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab. +1. Pour ouvrir un nouvel onglet avec plusieurs options supplémentaires, appuyez sur Ctrl+Entrée. +1. Pour accepter une suggestion, au-dessus de celle-ci, cliquez sur **Accepter la solution**. Pour rejeter toutes les suggestions, fermez l’onglet. -## Generating code suggestions from comments +## Génération de suggestions de code à partir de commentaires {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function. +1. Dans le fichier JavaScript, tapez le commentaire suivant. {% data variables.product.prodname_copilot %} suggère une implémentation de la fonction. ```javascript{:copy} // find all images without alternate text // and give them a red border function process() { ``` -## Using a framework +## Utilisation d’un framework -You can also use {% data variables.product.prodname_copilot %} to generate suggestions for APIs and frameworks. The following example uses {% data variables.product.prodname_copilot %} to create a simple Express server that returns the current time. +Vous pouvez également utiliser {% data variables.product.prodname_copilot %} afin de générer des suggestions pour les API et les frameworks. L’exemple suivant utilise {% data variables.product.prodname_copilot %} pour créer un serveur Express simple qui retourne l’heure actuelle. {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following comment and then press Enter. {% data variables.product.prodname_copilot %} will suggest an implementation of the Express app. +1. Dans le fichier JavaScript, tapez le commentaire suivant, puis appuyez sur Entrée. {% data variables.product.prodname_copilot %} suggère une implémentation de l’application Express. ```javascript{:copy} // Express server on port 3000 1. To accept each line, press Tab, then Enter. @@ -107,10 +111,10 @@ You can also use {% data variables.product.prodname_copilot %} to generate sugge ```javascript{:copy} // Return the current time ``` -1. To accept each line, press Tab. +1. Pour accepter chaque ligne, appuyez sur la touche de tabulation. {% data reusables.copilot.enabling-or-disabling-in-vsc %} -## Further reading +## Pour aller plus loin - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) diff --git a/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md b/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md index 618bbdb98aab..40e3d0a4e8fd 100644 --- a/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md +++ b/translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md @@ -1,84 +1,86 @@ --- -title: Getting started with GitHub Copilot in Visual Studio +title: Bien démarrer avec GitHub Copilot dans Visual Studio shortTitle: Visual Studio product: '{% data reusables.gated-features.copilot %}' -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, and start seeing suggestions as you write comments and code.' +intro: 'Découvrez comment installer {% data variables.product.prodname_copilot %} dans {% data variables.product.prodname_vs %}, et commencez à voir des suggestions lorsque vous écrivez des commentaires et du code.' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 353095b0b0490cd12da8d853754b524431605819 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185131' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and Visual Studio +## À propos de {% data variables.product.prodname_copilot %} et de Visual Studio {% data reusables.copilot.procedural-intro %} -If you use {% data variables.product.prodname_vs %}, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within {% data variables.product.prodname_vs %} for Windows. +Si vous utilisez {% data variables.product.prodname_vs %}, vous pouvez visualiser et intégrer les suggestions de {% data variables.product.prodname_copilot %} directement dans l’éditeur. Ce guide montre comment utiliser {% data variables.product.prodname_copilot %} dans {% data variables.product.prodname_vs %} pour Windows. -## Prerequisites +## Prérequis -To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must have {% data variables.product.prodname_vs %} 2022 17.2 or later installed. For more information, see the [Visual Studio IDE](https://visualstudio.microsoft.com/vs/) documentation. +Pour utiliser {% data variables.product.prodname_copilot %} dans {% data variables.product.prodname_vs %}, vous devez avoir installé {% data variables.product.prodname_vs %} 2022 17.2 ou version ultérieure. Pour plus d’informations, consultez la documentation relative à l’[IDE Visual Studio](https://visualstudio.microsoft.com/vs/). {% note %} -**Note**: {% data variables.product.prodname_copilot %} is not currently available for use with Visual Studio for Mac. +**Remarque** : {% data variables.product.prodname_copilot %} ne peut pas être utilisé avec Visual Studio pour Mac. {% endnote %} -## Installing the {% data variables.product.prodname_vs %} extension +## Installation de l’extension {% data variables.product.prodname_vs %} -To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vs %} extension. -1. In the Visual Studio toolbar, click **Extensions**, then click **Manage Extensions**. - ![Screenshot of the Visual Studio toolbar](/assets/images/help/copilot/visual-studio-toolbar.png) -1. In the "Manage Extensions" window, click **Visual Studio Marketplace**, search for the {% data variables.product.prodname_copilot %} extension, then click **Download**. - ![Screenshot of GitHub Copilot extension for Visual Studio with the download button emphasized](/assets/images/help/copilot/install-copilot-extension-visual-studio.png) -1. Close the "Manage Extensions" window, then exit and relaunch {% data variables.product.prodname_vs %}. -1. Optionally, to check that {% data variables.product.prodname_copilot %} is installed and enabled, go back to **Manage Extensions**, click **Installed** to view your currently installed extensions, then click **{% data variables.product.prodname_copilot %}** to see status information. - ![Screenshot of installed extensions in Visual Studio with GitHub Copilot emphasized](/assets/images/help/copilot/installed-copilot-extension-visual-studio.png) -1. Open or create a new project in {% data variables.product.prodname_vs %}. -1. In the "Microsoft {% data variables.product.prodname_vs %}" dialog box, to copy your device activation code, click **OK**. - ![Screenshot of the Microsoft {% data variables.product.prodname_vs %} dialogue box](/assets/images/help/copilot/vs-auth-dialogue.png) -1. A device activation window will open in your browser. Paste the device code, then click **Continue**. +Pour utiliser {% data variables.product.prodname_copilot %}, vous devez d’abord installer l’extension {% data variables.product.prodname_vs %}. +1. Dans la barre d’outils Visual Studio, cliquez sur **Extensions**, puis sur **Gérer les extensions**. + ![Capture d’écran de la barre d’outils Visual Studio](/assets/images/help/copilot/visual-studio-toolbar.png) +1. Dans la fenêtre « Gérer les extensions », cliquez sur **Visual Studio Marketplace**, recherchez l’extension {% data variables.product.prodname_copilot %}, puis cliquez sur **Télécharger**. + ![Capture d’écran de l’extension GitHub Copilot pour Visual Studio avec le bouton de téléchargement mis en évidence](/assets/images/help/copilot/install-copilot-extension-visual-studio.png) +1. Fermez la fenêtre « Gérer les extensions », puis quittez et relancez {% data variables.product.prodname_vs %}. +1. Si vous le souhaitez, pour vérifier que {% data variables.product.prodname_copilot %} est installé et activé, revenez à **Gérer les extensions**, cliquez sur **Installé** pour afficher les extensions actuellement installées, puis cliquez sur **{% data variables.product.prodname_copilot %}** pour afficher les informations d’état. + ![Capture d’écran des extensions installées dans Visual Studio avec GitHub Copilot mis en évidence](/assets/images/help/copilot/installed-copilot-extension-visual-studio.png) +1. Ouvrez ou créez un projet dans {% data variables.product.prodname_vs %}. +1. Dans la boîte de dialogue « Microsoft {% data variables.product.prodname_vs %} », pour copier le code d’activation de votre appareil, cliquez sur **OK**. + ![Capture d’écran de la boîte de dialogue Microsoft {% data variables.product.prodname_vs %}](/assets/images/help/copilot/vs-auth-dialogue.png) +1. Une fenêtre d’activation d’appareil s’ouvrira dans votre navigateur. Collez le code de l’appareil, puis cliquez sur **Continuer**. - - To paste the code in Windows or Linux, press Ctrl+v. - - To paste the code in macOS, press command+v. -1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**. -1. After you approve the permissions, {% data variables.product.prodname_vs %} will show a confirmation. - ![Screenshot of {% data variables.product.prodname_vs %} permissions confirmation](/assets/images/help/copilot/vs-confirmation.png) + - Pour coller le code sur un système Windows ou Linux, appuyez sur Ctrl+v. + - Pour coller le code sur un système macOS, appuyez sur commande+v. +1. {% data variables.product.prodname_dotcom %} demandera les autorisations nécessaires pour {% data variables.product.prodname_copilot %}. Pour approuver ces autorisations, cliquez sur **Autoriser le plug-in {% data variables.product.prodname_copilot %}** . +1. Une fois les autorisations approuvées, {% data variables.product.prodname_vs %} affiche une confirmation. + ![Capture d’écran de la confirmation des autorisations {% data variables.product.prodname_vs %}](/assets/images/help/copilot/vs-confirmation.png) -## Seeing your first suggestion +## Voir votre première suggestion -{% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in C#, but other languages will work similarly. +{% data reusables.copilot.code-examples-limitations %} {% data reusables.copilot.supported-languages %} Les exemples suivants sont en C#. Cependant, d’autres langages ont un fonctionnement similaire. {% data reusables.copilot.create-c-file %} -1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary. +1. Dans le fichier C#, tapez la signature de fonction suivante. {% data variables.product.prodname_copilot %} suggère automatiquement un corps de fonction entier en texte grisé, comme indiqué ci-dessous. La suggestion exacte peut varier. ```csharp{:copy} int CalculateDaysBetweenDates( ``` - ![Screenshot of a first suggestion Visual Studio Code](/assets/images/help/copilot/first-suggestion-visual-studio.png) -{% data reusables.copilot.accept-suggestion %} + ![Capture d’écran d’une première suggestion Visual Studio Code](/assets/images/help/copilot/first-suggestion-visual-studio.png) {% data reusables.copilot.accept-suggestion %} -## Seeing alternative suggestions -{% data reusables.copilot.alternative-suggestions %} -{% data reusables.copilot.create-c-file %} -1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will show you a suggestion. +## Voir d’autres suggestions +{% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-c-file %} +1. Dans le fichier C#, tapez la signature de fonction suivante. {% data variables.product.prodname_copilot %} affichera une suggestion. ```csharp{:copy} int CalculateDaysBetweenDates( ``` -1. If alternative suggestions are available, you can see these alternatives by pressing Alt+] (or Alt+[). -1. Optionally, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions. +1. Si d’autres suggestions sont disponibles, vous pouvez les voir en appuyant sur Alt+] (ou Alt+[). +1. Si vous le souhaitez, vous pouvez pointer sur la suggestion pour afficher la palette de commandes {% data variables.product.prodname_copilot %} afin de choisir des suggestions. {% data reusables.copilot.accept-or-reject-suggestion %} -## Generating code suggestions from comments +## Génération de suggestions de code à partir de commentaires {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-c-file %} -1. In the C# file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function. +1. Dans le fichier C#, tapez le commentaire suivant. {% data variables.product.prodname_copilot %} suggère une implémentation de la fonction. ```csharp{:copy} using System.Xml.Linq; @@ -91,6 +93,6 @@ To use {% data variables.product.prodname_copilot %}, you must first install the {% data reusables.copilot.enabling-or-disabling-vs %} -## Further reading +## Pour aller plus loin - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) diff --git a/translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md b/translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md new file mode 100644 index 000000000000..12c37dfb10ec --- /dev/null +++ b/translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md @@ -0,0 +1,33 @@ +--- +title: Changement de l’URL distante d’un dépôt à partir de GitHub Desktop +intro: 'Vous pouvez changer l’URL distante d’un dépôt avec lequel vous travaillez dans {% data variables.product.prodname_desktop %}. Vous pouvez le faire si le dépôt a été renommé, ou si le nom d’utilisateur ou l’organisation propriétaire du dépôt a changé.' +redirect_from: + - /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop +versions: + fpt: '*' +shortTitle: Change the remote URL for a repository +ms.openlocfilehash: e37c4878c13a9de95520f8e9c1edc9bf6416d46a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188355' +--- +{% mac %} + +{% data reusables.desktop.mac-repository-settings-menu %} +2. Cliquez sur **Dépôt distant** et, sous **Dépôt distant principal**, tapez l’URL souhaitée. +![Champ Dépôt distant principal](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-repository-settings-menu %} +2. Cliquez sur **Dépôt distant** et, sous **Dépôt distant principal**, tapez l’URL souhaitée. +![Champ Dépôt distant principal](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endwindows %} diff --git a/translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index 7893c8b4dd3f..2e9789c9fd6a 100644 --- a/translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -12,11 +12,11 @@ children: - /configuring-notifications-in-github-desktop - /changing-the-remote-url-for-a-repository-from-github-desktop shortTitle: Work with your remote repo -ms.openlocfilehash: 60c2f41546ff085ea8f8d56142da6a3c7a81ebae -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: f7e9f1ab5f73aaad29208db01c62815d7a20ba03 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145105333' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188356' --- diff --git a/translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index 64f440e02d6b..ecc3eaebbca8 100644 --- a/translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -6,12 +6,12 @@ intro: 'Vous pouvez utiliser {% data variables.product.prodname_github_codespace versions: fpt: '*' permissions: 'Organization owners who are admins for a classroom can enable {% data variables.product.prodname_github_codespaces %} for their organization and integrate {% data variables.product.prodname_github_codespaces %} as the supported editor for an assignment. {% data reusables.classroom.classroom-admins-link %}' -ms.openlocfilehash: 6794d20b9ea0153b3baf4bee1a08c68b2ba17456 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 832ab470d13cc741bc4a71e77840c99da5ff3de6 +ms.sourcegitcommit: a35d85531445980b5f04d3fc70180a29dad37f89 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158876' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148189912' --- ## À propos de {% data variables.product.prodname_github_codespaces %} @@ -103,4 +103,4 @@ Les enseignants peuvent voir le codespace de chaque étudiant pour un devoir dan ![Vue d’ensemble des devoirs de l’enseignant avec les codespaces de l’étudiant](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) -Lorsque vous vous connectez à un codespace via un navigateur, l’enregistrement automatique est automatiquement activé. Si vous souhaitez enregistrer les modifications dans le dépôt, vous devez commiter les modifications et les pousser (push) vers une branche distante. Si vous laissez votre codespace s’exécuter sans aucune interaction pendant 30 minutes (durée par défaut), le codespace expire et s’arrête. Vos données sont conservées depuis le dernier enregistrement de vos modifications. Pour plus d’informations sur le cycle de vie d’un codespace, consultez « [Cycle de vie d’un codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle) ». +Lorsque vous vous connectez à un codespace via un navigateur, l’enregistrement automatique est automatiquement activé. Si vous souhaitez enregistrer les modifications dans le dépôt, vous devez commiter les modifications et les pousser (push) vers une branche distante. Si vous laissez votre codespace s’exécuter sans aucune interaction pendant 30 minutes (durée par défaut), le codespace expire et s’arrête. Vos données sont conservées depuis le dernier enregistrement de vos modifications. Pour plus d’informations sur le cycle de vie d’un codespace, consultez « [Cycle de vie d’un codespace](/codespaces/getting-started/the-codespace-lifecycle) ». diff --git a/translations/fr-FR/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/fr-FR/content/graphql/guides/using-the-graphql-api-for-discussions.md index 72a711e0400a..5df0a26725ee 100644 --- a/translations/fr-FR/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/fr-FR/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -4,12 +4,12 @@ intro: 'Découvrez comment utiliser l’API GraphQL {% data variables.product.pr versions: feature: discussions shortTitle: Use GraphQL for Discussions -ms.openlocfilehash: 1512082737df4c92942a40007d2c75897edb1061 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fd296c4e9390cac3500ba7319cb602366a37e262 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147408842' +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148185614' --- L’API GraphQL {% data variables.product.prodname_discussions %} vous permet d’obtenir, de créer, de modifier et de supprimer des posts de discussion. Pour plus d’informations sur les données {% data variables.product.prodname_discussions %}, consultez « [À propos des discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions) ». @@ -72,7 +72,7 @@ enum DiscussionOrderField { ### Repository.discussionCategories -Retourner les catégories de discussion disponibles définies dans ce dépôt. Chaque dépôt peut avoir jusqu’à 10 catégories. Pour plus d’informations sur les catégories de discussion, consultez « [À propos des discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions) ». +Retourner les catégories de discussion disponibles définies dans ce dépôt. Chaque référentiel peut avoir jusqu’à 25 catégories. Pour plus d’informations sur les catégories de discussion, consultez « [À propos des discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions) ». _Signature :_ diff --git a/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md b/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md new file mode 100644 index 000000000000..d67e1e23bbcf --- /dev/null +++ b/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md @@ -0,0 +1,43 @@ +--- +title: Configuration d’un dépôt distant pour une duplication +intro: 'Vous devez configurer un dépôt distant qui pointe vers le dépôt en amont dans Git pour [synchroniser les modifications que vous apportez dans une duplication (fork)](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) avec le dépôt d’origine. Cela vous permet également de synchroniser les modifications apportées dans le dépôt d’origine avec la duplication (fork).' +redirect_from: + - /github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /articles/configuring-a-remote-for-a-fork + - /github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Pull requests +shortTitle: Configure a remote repository +ms.openlocfilehash: 495d3c825356fd69c9130f8a122aa7a8702ff317 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188378' +--- +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Affichez le dépôt distant actuellement configuré pour votre duplication. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + ``` +3. Spécifiez un nouveau dépôt distant *en amont* qui sera synchronisé avec la duplication (fork). + ```shell + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git + ``` +4. Vérifiez le nouveau dépôt en amont que vous avez spécifié pour votre duplication. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + ``` diff --git a/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md index 9b444403baed..544b03233784 100644 --- a/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md +++ b/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md @@ -18,11 +18,11 @@ children: - /syncing-a-fork - /allowing-changes-to-a-pull-request-branch-created-from-a-fork - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility -ms.openlocfilehash: 79d8346fdd63366e5987def43164932503104332 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf +ms.openlocfilehash: 0133f7759cb9040a5acb97a7b08c312a55079bda +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146683660' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188360' --- diff --git a/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index c9b479247ebf..ddaff88d74ee 100644 --- a/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -1,6 +1,6 @@ --- -title: Syncing a fork -intro: Sync a fork of a repository to keep it up-to-date with the upstream repository. +title: Synchronisation d’une duplication +intro: Synchronisez une duplication d’un référentiel pour la maintenir à jour avec le référentiel en amont. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork - /articles/syncing-a-fork @@ -19,44 +19,48 @@ versions: topics: - Pull requests permissions: People with write access for a forked repository can sync the fork to the upstream repository. +ms.openlocfilehash: 85b149e26cb65a428d7e9b66aea99d6b62430ae0 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188327' --- - -## Syncing a fork branch from the web UI +## Synchronisation d’une branche de duplication à partir de l’interface utilisateur web {% ifversion syncing-fork-web-ui %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Sync fork** dropdown. - !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) -3. Review the details about the commits from the upstream repository, then click **Update branch**. - ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) -{% else %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Fetch upstream** dropdown. - !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. - !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} +1. Sur {% data variables.product.product_name %}, accédez à la page principale du dépôt dupliqué que vous souhaitez synchroniser avec le dépôt en amont. +2. Sélectionnez la liste déroulante **Fork de synchronisation**. + ![Liste déroulante « Fork de synchronisation » soulignée](/assets/images/help/repository/sync-fork-dropdown.png) +3. Examinez les détails des validations à partir du référentiel en amont, puis cliquez sur **Mettre à jour la branche**. + ![Modèle Fork de synchronisation avec le bouton « Mettre à jour la branche » souligné](/assets/images/help/repository/update-branch-button.png) {% else %} +1. Sur {% data variables.product.product_name %}, accédez à la page principale du dépôt dupliqué que vous souhaitez synchroniser avec le dépôt en amont. +2. Sélectionnez la liste déroulante **Récupérer en amont**. + ![Liste déroulante « Extraire en amont »](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. Examinez les détails des validations à partir du dépôt en amont, puis cliquez sur **Extraire et fusionner**. + ![Bouton « Extraire et fusionner »](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} -If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. +Si les modifications du dépôt en amont provoquent des conflits,{% data variables.product.company_short %} vous invitera à créer une demande de tirage pour résoudre les conflits. -## Syncing a fork branch with the {% data variables.product.prodname_cli %} +## Synchronisation d’une branche de duplication avec {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %} Pour en savoir plus sur {% data variables.product.prodname_cli %}, consultez « [À propos de {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli) ». -To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments. +Pour mettre à jour la duplication distante à partir de son parent, utilisez la sous-commande `gh repo sync -b BRANCHNAME` et fournissez le nom de votre duplication et de votre branche comme des arguments. ```shell $ gh repo sync owner/cli-fork -b BRANCH_NAME ``` -If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. +Si les modifications du dépôt en amont provoquent un conflit, l’{% data variables.product.prodname_cli %} ne peut pas se synchroniser. Vous pouvez définir l’indicateur `-force` pour remplacer la branche de destination. -## Syncing a fork branch from the command line +## Synchronisation d’une duplication de branche à partir de la ligne de commande -Before you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git. For more information, see "[Configuring a remote repository for a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)." +Avant de pouvoir synchroniser votre duplication avec un référentiel en amont, vous devez configurer un élément distant qui pointe vers le référentiel en amont dans Git. Pour plus d’informations, consultez « [Configuration d’un dépôt distant pour une duplication](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork) ». {% data reusables.command_line.open_the_multi_os_terminal %} -2. Change the current working directory to your local project. -3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. +2. Remplacez le répertoire de travail actuel par votre projet local. +3. Extrayez les branches et leurs validations respectives du dépôt en amont. Les validations dans `BRANCHNAME` seront stockées dans la branche locale `upstream/BRANCHNAME`. ```shell $ git fetch upstream @@ -68,14 +72,14 @@ Before you can sync your fork with an upstream repository, you must configure a > * [new branch] main -> upstream/main ``` -4. Check out your fork's local default branch - in this case, we use `main`. +4. Vérifiez la branche locale par défaut de votre duplication. Dans ce cas, nous utilisons `main`. ```shell $ git checkout main > Switched to branch 'main' ``` -5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. +5. Fusionnez les modifications de la branche par défaut en amont (dans ce cas, `upstream/main`) dans votre branche locale par défaut. Cela synchronise la branche par défaut de votre duplication avec le dépôt en amont, sans perte de vos modifications locales. ```shell $ git merge upstream/main @@ -88,7 +92,7 @@ Before you can sync your fork with an upstream repository, you must configure a > create mode 100644 README.md ``` - If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation. + Si votre branche locale n’a pas de validation unique, Git effectue un transfert rapide. Pour plus d’informations, consultez [Création de branches et fusion](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) dans la documentation Git. ```shell $ git merge upstream/main > Updating 34e91da..16c56ad @@ -96,10 +100,10 @@ Before you can sync your fork with an upstream repository, you must configure a > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) ``` - If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)." + Si votre branche locale avait des validations uniques, vous devrez peut-être résoudre les conflits. Pour plus d’informations, consultez « [Traitement des conflits de fusion](/github/collaborating-with-pull-requests/addressing-merge-conflicts) ». {% tip %} -**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). +**Astuce** : la synchronisation de votre duplication met uniquement à jour votre copie locale du dépôt. Pour mettre à jour votre duplication sur {% data variables.location.product_location %}, vous devez [pousser (push) vos modifications](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). {% endtip %} diff --git a/translations/fr-FR/content/rest/overview/api-versions.md b/translations/fr-FR/content/rest/overview/api-versions.md new file mode 100644 index 000000000000..1d55055773f8 --- /dev/null +++ b/translations/fr-FR/content/rest/overview/api-versions.md @@ -0,0 +1,54 @@ +--- +title: Versions des API +shortTitle: API Versions +intro: Vous devez spécifier la version d’API REST à utiliser chaque fois que vous effectuez une demande à l’API REST. +versions: + feature: api-date-versioning +ms.openlocfilehash: c1209120fab4c4cc26962991ad48b76638627db5 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148184390' +--- +## À propos du contrôle de version de l’API + +{% data reusables.rest-api.about-api-versions %} + +{% ifversion ghes %} + +## À propos du contrôle de version {% data variables.product.prodname_ghe_server %} et du contrôle de version d’API REST + +Les versions {% data variables.product.prodname_ghe_server %} sont dissociées des versions d’API REST. Vous pouvez mettre à niveau votre version {% data variables.product.prodname_ghe_server %}, mais conserver la même version d’API REST, tant que la version de l’API est incluse dans la version {% data variables.product.prodname_ghe_server %}. De même, vous pouvez mettre à niveau votre version d’API REST sans mettre à jour votre version {% data variables.product.prodname_ghe_server %}, tant que la nouvelle version d’API REST que vous choisissez est disponible pour votre version {% data variables.product.prodname_ghe_server %}. + +Les notes de publication {% data variables.product.prodname_ghe_server %} indiquent quand une version d’API REST n’est plus prise en charge. Pour plus d’informations, consultez « [Notes de publication](/admin/release-notes) ». + +{% endif %} + +## Spécification d’une version d’API + +Vous devez utiliser l’en-tête `X-GitHub-Api-Version` pour spécifier une version d’API. Par exemple : + +```shell +$ curl {% data reusables.rest-api.version-header %} https://api.github.com/zen +``` + +Les requêtes sans l’en-tête `X-GitHub-Api-Version` utilisent par défaut la version `{{ initialRestVersioningReleaseDate }}`. + +Si vous spécifiez une version d’API qui n’est plus prise en charge, vous recevrez une erreur `400`. + +## Mise à niveau vers une nouvelle version de l’API + +Avant de procéder à la mise à niveau vers une nouvelle version d’API REST, vous devez lire le journal de modifications des changements cassants qui correspond à la nouvelle version de l’API pour comprendre les changements cassants inclus et pour en savoir plus sur la mise à niveau vers cette version de l’API. Pour plus d'informations, consultez « [Changements cassants](/rest/overview/breaking-changes) ». + +Lorsque vous mettez à jour votre intégration pour spécifier la nouvelle version de l’API dans l’en-tête `X-GitHub-Api-Version` , vous devez également apporter les modifications nécessaires pour que votre intégration fonctionne avec la nouvelle version de l’API. + +Une fois votre intégration mise à jour, testez votre intégration pour vérifier qu’elle fonctionne avec la nouvelle version de l’API. + +## Versions d'API prises en charge + +Les versions d’API REST suivantes sont actuellement prises en charge : + +{% for apiVersion in allVersions[currentVersion].apiVersions %} {{ apiVersion }} {% endfor %} + +Vous pouvez également faire en sorte qu’une demande d’API obtienne toutes les versions d’API prises en charge. Pour plus d’informations, consultez « [Obtenir toutes les versions d’API](/rest/meta#get-all-api-versions) ». diff --git a/translations/fr-FR/content/rest/overview/breaking-changes.md b/translations/fr-FR/content/rest/overview/breaking-changes.md new file mode 100644 index 000000000000..07272e4006c4 --- /dev/null +++ b/translations/fr-FR/content/rest/overview/breaking-changes.md @@ -0,0 +1,30 @@ +--- +title: Changements cassants +shortTitle: Breaking changes +intro: Découvrez les changements cassants introduits dans chaque version d’API REST. +versions: + feature: api-date-versioning +ms.openlocfilehash: 674345b82c5da9b0804fe4a0f62450ff4fbbc3e9 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148184408' +--- +## À propos des changements cassants dans l’API REST + +{% data reusables.rest-api.about-api-versions %} + +Pour plus d’informations sur les versions de l’API, consultez « [Versions de l’API](/rest/overview/api-versions) ». + +## Mise à niveau vers une nouvelle version de l’API + +Avant de procéder à la mise à niveau vers une nouvelle version d’API REST, vous devez lire la section de cette page qui correspond à la nouvelle version de l’API pour comprendre les changements cassants inclus et pour en savoir plus sur la mise à niveau vers cette version de l’API. + +Lorsque vous mettez à jour votre intégration pour spécifier la nouvelle version de l’API dans l’en-tête `X-GitHub-Api-Version` , vous devez également apporter les modifications nécessaires pour que votre intégration fonctionne avec la nouvelle version de l’API. + +Une fois votre intégration mise à jour, testez votre intégration pour vérifier qu’elle fonctionne avec la nouvelle version de l’API. + +## Changements cassants pour {{ initialRestVersioningReleaseDate }} + +Version `{{ initialRestVersioningReleaseDate }}` est la première version d’API REST {% data variables.product.product_name %} après l’introduction du contrôle de version basé sur la date. Cette version n’inclut aucun changement cassant. diff --git a/translations/fr-FR/content/rest/overview/resources-in-the-rest-api.md b/translations/fr-FR/content/rest/overview/resources-in-the-rest-api.md index 9a70c577ae42..11f68a9f7ff0 100644 --- a/translations/fr-FR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/fr-FR/content/rest/overview/resources-in-the-rest-api.md @@ -11,12 +11,12 @@ versions: miniTocMaxHeadingLevel: 3 topics: - API -ms.openlocfilehash: dc16916ada20275d41f23a8bc006cc79ddf51120 -ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.openlocfilehash: 4fd3e2aad72ee0ffc4778a86dc99cd5bb6f9d2c5 +ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/29/2022 -ms.locfileid: '148184268' +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190398' --- {% ifversion api-date-versioning %} ## Version de l'API @@ -262,10 +262,10 @@ Vous pouvez ensuite développer ces modèles à l’aide de la gemme [uri_templa >> tmpl.expand => "/notifications" - >> tmpl.expand :all => 1 + >> tmpl.expand all: 1 => "/notifications?all=1" - >> tmpl.expand :all => 1, :participating => 1 + >> tmpl.expand all: 1, participating: 1 => "/notifications?all=1&participating=1" [rfc]: https://datatracker.ietf.org/doc/html/rfc6570 diff --git a/translations/fr-FR/data/reusables/apps/reauthorize-apps-saml.md b/translations/fr-FR/data/reusables/apps/reauthorize-apps-saml.md new file mode 100644 index 000000000000..9e03e2a021c7 --- /dev/null +++ b/translations/fr-FR/data/reusables/apps/reauthorize-apps-saml.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: a95067136ba91760fb48dae77a42cf9b9377dbeb +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184050" +--- +Après avoir activé l’authentification unique SAML, il peut être nécessaire de révoquer et de réautoriser les autorisations {% data variables.product.prodname_oauth_app %} et {% data variables.product.prodname_github_app %} avant de pouvoir accéder à l’organisation. Pour plus d’informations, consultez « [Autorisation des {% data variables.product.prodname_oauth_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps#oauth-apps-and-organizations) ». diff --git a/translations/fr-FR/data/reusables/audit_log/audit-log-action-categories.md b/translations/fr-FR/data/reusables/audit_log/audit-log-action-categories.md index 0b39c0aba578..08cb4ab95afc 100644 --- a/translations/fr-FR/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/fr-FR/data/reusables/audit_log/audit-log-action-categories.md @@ -1,192 +1,116 @@ -| Category name | Description +--- +ms.openlocfilehash: 1dd9305ca2b7cb3e8d25d697de8ae3a83e0c46bb +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148183979" +--- +| Nom de la catégorie | Description |------------------|------------------- -{%- ifversion fpt or ghec %} -| `account` | Contains activities related to an organization account. -| `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -{%- endif %} -| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts. -{%- ifversion audit-log-streaming %} -| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account. -{%- endif %} -{%- ifversion fpt or ghec %} -| `billing` | Contains activities related to an organization's billing. -{%- endif %} -{%- ifversion ghec or ghes or ghae %} -| `business` | Contains activities related to business settings for an enterprise. -{%- endif %} -{%- ifversion code-security-audit-log-events %} -| `business_advanced_security` | Contains activities related to {% data variables.product.prodname_GH_advanced_security %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." -| `business_secret_scanning` | Contains activities related to {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." -{%- endif %} -{%- ifversion secret-scanning-audit-log-custom-patterns %} -| `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for {% data variables.product.prodname_secret_scanning %} in an enterprise. -{%- endif %} -{%- ifversion code-security-audit-log-events %} -| `business_secret_scanning_push_protection` | Contains activities related to the push protection feature of {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." -| `business_secret_scanning_push_protection_custom_message` | Contains activities related to the custom message displayed when push protection is triggered in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." -{%- endif %} -| `checks` | Contains activities related to check suites and runs. -{%- ifversion fpt or ghec %} -| `codespaces` | Contains activities related to an organization's codespaces. -{%- endif %} -| `commit_comment` | Contains activities related to updating or deleting commit comments. -{%- ifversion ghes %} -| `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log. -{%- endif %} -| `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." -| `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. -| `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. -{%- ifversion fpt or ghec or ghes %} -| `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." -| `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. -{%- endif %} -| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." -| `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. -{%- ifversion fpt or ghec %} -| `discussion` | Contains activities related to team discussions. -| `discussion_comment` | Contains activities related to comments posted in discussions on a team page. -| `discussion_post` | Contains activities related to discussions posted to a team page. -| `discussion_post_reply` | Contains activities related to replies to discussions posted to a team page. -{%- endif %} -{%- ifversion ghec or ghes %} -| `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}. -| `enterprise` | Contains activities related to enterprise settings. -{%- endif %} -{%- ifversion ghec %} -| `enterprise_domain` | Contains activities related to verified enterprise domains. -| `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection. -{%- endif %} -{%- ifversion fpt or ghec %} -| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments. -{%- endif %} -{%- ifversion ghae %} -| `external_group` | Contains activities related to Okta groups. -| `external_identity` | Contains activities related to a user in an Okta group. -{%- endif %} -| `gist` | Contains activities related to Gists. -| `hook` | Contains activities related to webhooks. -| `integration` | Contains activities related to integrations in an account. -| `integration_installation` | Contains activities related to integrations installed in an account. -| `integration_installation_request` | Contains activities related to organization member requests for owners to approve integrations for use in the organization. -{%- ifversion ghec or ghae %} -| `ip_allow_list` | Contains activities related to enabling or disabling the IP allow list for an organization. -| `ip_allow_list_entry` | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. -{%- endif %} -| `issue` | Contains activities related to pinning, transferring, or deleting an issue in a repository. -| `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments. -| `issues` | Contains activities related to enabling or disabling issue creation for an organization. -{%- ifversion fpt or ghec %} -| `marketplace_agreement_signature` | Contains activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. -| `marketplace_listing` | Contains activities related to listing apps in {% data variables.product.prodname_marketplace %}. -{%- endif %} -| `members_can_create_pages` | Contains activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." -| `members_can_create_private_pages` | Contains activities related to managing the publication of private {% data variables.product.prodname_pages %} sites for repositories in the organization. -| `members_can_create_public_pages` | Contains activities related to managing the publication of public {% data variables.product.prodname_pages %} sites for repositories in the organization. -{%- ifversion ghec or ghes or ghae %} -| `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization. -{%- endif %} -{%- ifversion fpt or ghec %} -| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights. -| `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. -{%- endif %} -| `oauth_access` | Contains activities related to OAuth access tokens. -| `oauth_application` | Contains activities related to OAuth Apps. -{%- ifversion fpt or ghec %} -| `oauth_authorization` | Contains activities related to authorizing OAuth Apps. -{%- endif %} -| `org` | Contains activities related to organization membership. -{%- ifversion ghec or ghes or ghae %} -| `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on. -{%- endif %} -{%- ifversion secret-scanning-audit-log-custom-patterns %} -| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." -| `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." -{%- endif %} -| `organization_default_label` | Contains activities related to default labels for repositories in an organization. -{%- ifversion fpt or ghec or ghes %} -| `organization_domain` | Contains activities related to verified organization domains. -| `organization_projects_change` | Contains activities related to organization-wide project boards in an enterprise. -{%- endif %} -{%- ifversion fpt or ghec %} -| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}. -| `payment_method` | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}. -| `prebuild_configuration` | Contains activities related to prebuild configurations for {% data variables.product.prodname_github_codespaces %}. -{%- endif %} -{%- ifversion ghes %} -| `pre_receive_environment` | Contains activities related to pre-receive hook environments. -| `pre_receive_hook` | Contains activities related to pre-receive hooks. -{%- endif %} -{%- ifversion ghes %} -| `private_instance_encryption` | Contains activities related to enabling private mode for an enterprise. -{%- endif %} -| `private_repository_forking` | Contains activities related to allowing forks of private and internal repositories, for a repository, organization or enterprise. -{%- ifversion fpt or ghec %} -| `profile_picture` | Contains activities related to an organization's profile picture. -{%- endif %} -| `project` | Contains activities related to project boards. -| `project_field` | Contains activities related to field creation and deletion in a project board. -| `project_view` | Contains activities related to view creation and deletion in a project board. -| `protected_branch` | Contains activities related to protected branches. -| `public_key` | Contains activities related to SSH keys and deploy keys. -| `pull_request` | Contains activities related to pull requests. -| `pull_request_review` | Contains activities related to pull request reviews. -| `pull_request_review_comment` | Contains activities related to pull request review comments. -| `repo` | Contains activities related to the repositories owned by an organization. -{%- ifversion fpt or ghec %} -| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -| `repository_content_analysis` | Contains activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data). -| `repository_dependency_graph` | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." -{%- endif %} -| `repository_image` | Contains activities related to images for a repository. -| `repository_invitation` | Contains activities related to invitations to join a repository. -| `repository_projects_change` | Contains activities related to enabling projects for a repository or for all repositories in an organization. -{%- ifversion ghec or ghes or ghae %} -| `repository_secret_scanning` | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -{%- endif %} -{%- ifversion secret-scanning-audit-log-custom-patterns %} -| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} -| `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." -{%- endif %} -{%- ifversion fpt or ghec %} -| `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. -{%- endif %} -| `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). -{%- ifversion fpt or ghec %} -| `repository_vulnerability_alerts` | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}. -| `required_status_check` | Contains activities related to required status checks for protected branches. -{%- endif %} -{%- ifversion ghec or ghes %} -| `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise. -{%- endif %} -{%- ifversion custom-repository-roles %} -| `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). -{%- endif %} -{%- ifversion ghec or ghes or ghae %} -| `secret_scanning` | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| `secret_scanning_new_repos` | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. -{%- endif %} -{%- ifversion ghec or ghes or ghae %} -| `security_key` | Contains activities related to security keys registration and removal. -{%- endif %} -{%- ifversion fpt or ghec %} -| `sponsors` | Contains events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"). -{%- endif %} -{%- ifversion ghec or ghes or ghae %} -| `ssh_certificate_authority` | Contains activities related to a SSH certificate authority in an organization or enterprise. -| `ssh_certificate_requirement` | Contains activities related to requiring members use SSH certificates to access organization resources. -{%- endif %}{% ifversion sso-redirect %} -| `sso_redirect` | Contains activities related to automatically redirecting users to sign in (see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)").{% endif %} -| `staff` | Contains activities related to a site admin performing an action. -| `team` | Contains activities related to teams in an organization. -| `team_discussions` | Contains activities related to managing team discussions for an organization. -{%- ifversion ghec %} -| `team_sync_tenant` | Contains activities related to team synchronization with an IdP for an enterprise or organization. -{%- endif %} -{%- ifversion fpt or ghes %} -| `two_factor_authentication` | Contains activities related to two-factor authentication. -{%- endif %} -| `user` | Contains activities related to users in an enterprise or organization. -{%- ifversion ghec or ghes %} -| `user_license` | Contains activities related to a user occupying a licensed seat in, and being a member of, an enterprise. -{%- endif %} -| `workflows` | Contains activities related to {% data variables.product.prodname_actions %} workflows. +{%- ifversion fpt or ghec %} | `account` | Contient des activités liées à un compte d’organisation. +| `advisory_credit` | Contient des activités liées au crédit d’un contributeur pour un avis de sécurité dans les données {% data variables.product.prodname_advisory_database %}. Pour plus d’informations, consultez « [À propos des avis de sécurité {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories) ». +{%- endif %} | `artifact` | Contient des activités liées aux artefacts d’exécution de workflow {% data variables.product.prodname_actions %}. +{%- ifversion audit-log-streaming %} | `audit_log_streaming` | Contient des activités liées aux journaux d’audit de streaming pour les organisations dans un compte d’entreprise. +{%- endif %} {%- ifversion fpt or ghec %} | `billing` |Contient des activités liées à la facturation d’une organisation. +{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | Contient des activités liées aux paramètres métier d’une entreprise. +{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_advanced_security` | Contient les activités liées à {% data variables.product.prodname_GH_advanced_security %} dans une entreprise. Pour plus d’informations, consultez « [Gestion des fonctionnalités {% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise) ». +| `business_secret_scanning` | Contient les activités relatives à l’{% data variables.product.prodname_secret_scanning %} dans une entreprise. Pour plus d’informations, consultez « [Gestion des fonctionnalités {% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise) ». +{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `business_secret_scanning_custom_pattern` | Contient les activités relatives aux modèles personnalisés pour l’{% data variables.product.prodname_secret_scanning %} dans une entreprise. +{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_secret_scanning_push_protection` | Contient les activités relatives à la fonctionnalité de protection des poussées de l’{% data variables.product.prodname_secret_scanning %} dans une entreprise. Pour plus d’informations, consultez « [Gestion des fonctionnalités {% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise) ». +| `business_secret_scanning_push_protection_custom_message` | Contient les activités relatives au message personnalisé affiché quand la protection des poussées est déclenchée dans une entreprise. Pour plus d’informations, consultez « [Gestion des fonctionnalités {% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise) ». +{%- endif %} | `checks` | Contient des activités liées aux suites de vérifications et exécutions. +{%- ifversion fpt or ghec %} | `codespaces` | Contient des activités liées aux codespaces d’une organisation. +{%- endif %} | `commit_comment` | Contient des activités liées à la mise à jour ou à la suppression des commentaires de validation. +{%- ifversion ghes %} | `config_entry` | Contient des activités liées aux paramètres de configuration. Ces événements sont visibles uniquement dans le journal d’audit de l’administrateur de site. +{%- endif %} | `dependabot_alerts` | Contient les activités de configuration au niveau de l’organisation pour les {% data variables.product.prodname_dependabot_alerts %} dans les référentiels existants. Pour plus d’informations, consultez « [À propos des {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts) ». +| `dependabot_alerts_new_repos` | Contient des activités de configuration au niveau de l’organisation pour {% data variables.product.prodname_dependabot_alerts %} dans des nouveaux référentiels créés dans l’organisation. +| `dependabot_repository_access` | Contient des activités liées aux référentiels privés d’une organisation {% data variables.product.prodname_dependabot %} auxquels l’accès est autorisé. +{%- ifversion fpt or ghec or ghes %} | `dependabot_security_updates` | Contient les activités de configuration au niveau de l’organisation pour les {% data variables.product.prodname_dependabot_security_updates %} dans les dépôts existants. Pour plus d’informations, consultez « [Configuration des {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates) ». +| `dependabot_security_updates_new_repos` | Contient des activités de configuration au niveau de l’organisation pour {% data variables.product.prodname_dependabot_security_updates %} pour les nouveaux référentiels créés dans l’organisation. +{%- endif %} | `dependency_graph` | Contient des activités de configuration au niveau de l’organisation pour les graphes des dépendances pour les dépôts. Pour plus d’informations, consultez « [À propos du graphe des dépendances](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) ». +| `dependency_graph_new_repos` | Contient des activités de configuration au niveau de l’organisation pour les nouveaux référentiels créés dans l’organisation. +{%- ifversion fpt or ghec %} | `discussion` | Contient des activités liées aux discussions d’équipe. +| `discussion_comment` | Contient des activités liées aux commentaires publiés dans les discussions sur une page d’équipe. +| `discussion_post` | Contient des activités liées aux discussions publiées sur une page d’équipe. +| `discussion_post_reply` | Contient des activités liées aux réponses aux discussions publiées sur une page d’équipe. +{%- endif %} {%- ifversion ghec or ghes %} | `dotcom_connection` | Contient des activités liées à {% data variables.product.prodname_github_connect %}. +| `enterprise` | Contient des activités liées aux paramètres d’entreprise. +{%- endif %} {%- ifversion ghec %} | `enterprise_domain` | Contient des activités liées aux domaines d’entreprise vérifiés. +| `enterprise_installation` | Contient des activités liées aux {% data variables.product.prodname_github_app %} associés à une connexion d’entreprise {% data variables.product.prodname_github_connect %}. +{%- endif %} {%- ifversion fpt or ghec %} | `environment` | Contient des activités liées aux environnements {% data variables.product.prodname_actions %}. +{%- endif %} {%- ifversion ghae %} | `external_group` | Contient des activités liées aux groupes Okta. +| `external_identity` | Contient des activités liées à un utilisateur dans un groupe Okta. +{%- endif %} | `gist` | Contient des activités liées aux Gists. +| `hook` | Contient toutes les activités liées aux webhooks. +| `integration` | Contient des activités liées aux intégrations dans un compte. +| `integration_installation` | Contient des activités liées aux intégrations installées dans un compte. +| `integration_installation_request` | Contient des activités liées aux demandes des membres de l’organisation pour que les propriétaires approuvent les intégrations à utiliser dans l’organisation. +{%- ifversion ghec or ghae %} | `ip_allow_list` | Contient des activités liées à l’activation ou à la désactivation de la liste d’autorisation des adresses IP pour une organisation. +| `ip_allow_list_entry` | Contient des activités liées à la création, à la suppression et à la modification d’une entrée de la liste d’autorisation des adresses IP pour une organisation. +{%- endif %} | `issue` | Contient des activités liées à l’épinglage, au transfert ou à la suppression d’un problème dans un référentiel. +| `issue_comment` | Contient des activités liées à l’épinglage, au transfert ou à la suppression des commentaires de problème. +| `issues` | Contient des activités liées à l’activation ou à la désactivation de la création de problème pour une organisation. +{%- ifversion fpt or ghec %} | `marketplace_agreement_signature` | Contient des activités liées à la signature du Contrat du développeur {% data variables.product.prodname_marketplace %}. +| `marketplace_listing` | Contient des activités liées à la liste des applications dans {% data variables.product.prodname_marketplace %}. +{%- endif %} | `members_can_create_pages` | Contient des activités liées à la gestion de la publication des sites {% data variables.product.prodname_pages %} pour les référentiels de l’organisation. Pour plus d’informations, consultez « [Gestion de la publication de sites {% data variables.product.prodname_pages %} pour votre organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization). » +| `members_can_create_private_pages` | Contient des activités liées à la gestion de la publication de sites privés {% data variables.product.prodname_pages %} pour les référentiels de l’organisation. +| `members_can_create_public_pages` | Contient des activités liées à la gestion de la publication des sites publiques {% data variables.product.prodname_pages %} pour les référentiels de l’organisation. +{%- ifversion ghec or ghes or ghae %} | `members_can_delete_repos` | Contient des activités liées à l’activation ou à la désactivation de la création de référentiels pour une organisation. +{%- endif %} {%- ifversion fpt or ghec %} | `members_can_view_dependency_insights` | Contient des activités de configuration au niveau de l’organisation permettant aux membres de l’organisation d’afficher les insights sur les dépendances. +| `migration` | Contient des activités liées au transfert de données à partir d’un emplacement *source* (comme une organisation {% data variables.product.prodname_dotcom_the_website %} ou une instance {% data variables.product.prodname_ghe_server %}) vers une instance {% data variables.product.prodname_ghe_server %} *cible*. +{%- endif %} | `oauth_access` | Contient des activités liées aux jetons d’accès OAuth. +| `oauth_application` | Contient toutes les activités liées aux applications OAuth. +{%- ifversion fpt or ghec %} | `oauth_authorization` | Contient des activités liées à l’autorisation des applications OAuth. +{%- endif %} | `org` | Contient des activités liées à l’appartenance à l’organisation. +{%- ifversion ghec or ghes or ghae %} | `org_credential_authorization` | Contient des activités liées à l’autorisation des informations d’identification pour l’authentification unique SAML. +{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org_secret_scanning_custom_pattern` | Contient des activités liées aux modèles personnalisés pour l’analyse des secrets dans une organisation. Pour plus d’informations, consultez « [Définition de modèles personnalisés pour l’analyse des secrets](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning) ». +| `org.secret_scanning_push_protection` | Contient des activités liées aux modèles personnalisés d’analyse des secrets dans une organisation. Pour plus d’informations, consultez « [Protection des poussées avec l’analyse des secrets](/code-security/secret-scanning/protecting-pushes-with-secret-scanning) ». +{%- endif %} | `organization_default_label` | Contient des activités liées aux étiquettes par défaut pour les référentiels d’une organisation. +{%- ifversion fpt or ghec or ghes %} | `organization_domain` | Contient des activités liées aux domaines d’organisation vérifiés. +| `organization_projects_change` | Contient des activités liées aux tableaux de projet à l’échelle de l’organisation dans une entreprise. +{%- endif %} {%- ifversion fpt or ghec %} | `pages_protected_domain` | Contient des activités liées aux domaines personnalisés vérifiés pour {% data variables.product.prodname_pages %}. +| `payment_method` | Contient des activités liées à la façon dont une organisation paie {% data variables.product.prodname_dotcom %}. +| `prebuild_configuration` | Contient des activités liées aux configurations de prébuild pour {% data variables.product.prodname_github_codespaces %}. +{%- endif %} {%- ifversion ghes %} | `pre_receive_environment` |Contient des activités liées aux environnements de hooks de pré-réception. +| `pre_receive_hook` | Contient des activités liées aux hooks de pré-réception. +{%- endif %} {%- ifversion ghes %} | `private_instance_encryption` | Contient des activités liées à l’activation du mode privé pour une entreprise. +{%- endif %} | `private_repository_forking` | Contient des activités liées à l’autorisation des duplications (forks) de référentiels privés et internes, pour un référentiel, une organisation ou une entreprise. +{%- ifversion fpt or ghec %} | `profile_picture` | Contient des activités liées à l’image de profil d’une organisation. +{%- endif %} | `project` | Contient des activités liées aux tableaux de projet. +| `project_field` | Contient des activités liées à la création et à la suppression de champs dans un tableau de projet. +| `project_view` | Contient des activités liées à la création et à la suppression d’affichages dans un tableau de projet. +| `protected_branch` | Contient des activités liées aux branches protégées. +| `public_key` | Contient des activités liées aux clés SSH et aux clés de déploiement. +| `pull_request` | Contient des activités liées aux demandes de tirage. +| `pull_request_review` | Contient des activités liées aux révisions de demande de tirage (pull request). +| `pull_request_review_comment` | Contient des activités liées aux commentaires de révision de demande de tirage (pull request). +| `repo` | Contient des activités liées aux dépôts appartenant à une organisation. +{%- ifversion fpt or ghec %} | `repository_advisory` | Contient des activités au niveau du référentiel liées aux avis de sécurité {% data variables.product.prodname_advisory_database %}. Pour plus d’informations, consultez « [À propos des avis de sécurité {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories) ». +| `repository_content_analysis` | Contient des activités liées à [l’activation ou à la désactivation de l’utilisation des données pour un référentiel privé](/articles/about-github-s-use-of-your-data). +| `repository_dependency_graph` | Contient des activités au niveau du référentiel liées à l’activation ou à la désactivation du graphique de dépendance pour un référentiel privé {% ifversion fpt or ghec %} {% endif %}. Pour plus d’informations, consultez « [À propos du graphe des dépendances](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) ». +{%- endif %} | `repository_image` | Contient des activités liées aux images d’un référentiel. +| `repository_invitation` | Contient des activités liées aux invitations à rejoindre un référentiel. +| `repository_projects_change` | Contient des activités liées à l’activation de projets pour un référentiel ou pour tous les référentiels d’une organisation. +{%- ifversion ghec or ghes or ghae %} | `repository_secret_scanning` | Contient des activités au niveau du référentiel liées à l’analyse des secrets. Pour plus d’informations, consultez « [À propos de l’analyse des secrets](/github/administering-a-repository/about-secret-scanning) ». +{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_custom_pattern` | Contient des activités liées aux modèles personnalisés d’analyse des secrets dans un dépôt. Pour plus d’informations, consultez « [Définition de modèles personnalisés pour l’analyse des secrets](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning) ». {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_push_protection` | Contient des activités liées aux modèles personnalisés d’analyse des secrets dans un dépôt. Pour plus d’informations, consultez « [Protection des poussées avec l’analyse des secrets](/code-security/secret-scanning/protecting-pushes-with-secret-scanning) ». +{%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contient des activités liées au fait d’autoriser des membres de l’organisation à modifier les visibilités des référentiels pour l’organisation. +{%- endif %} | `repository_vulnerability_alert` | Contient des activités liées aux [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). +{%- ifversion fpt or ghec %} | `repository_vulnerability_alerts` | Contient des activités de configuration au niveau du dépôt pour les {% data variables.product.prodname_dependabot_alerts %}. +| `required_status_check` | Contient des activités liées aux vérifications d’état requises pour les branches protégées. +{%- endif %} {%- ifversion ghec or ghes %} | `restrict_notification_delivery` | Contient des activités liées à la restriction des notifications par e-mail aux domaines approuvés ou vérifiés pour une entreprise. +{%- endif %} {%- ifversion custom-repository-roles %} | `role` | Contient des activités liées aux [rôles de dépôt personnalisés](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). +{%- endif %} {%- ifversion ghec or ghes or ghae %} | `secret_scanning` | Contient des activités de configuration au niveau de l’organisation pour l’analyse des secrets dans les référentiels existants. Pour plus d’informations, consultez « [À propos de l’analyse des secrets](/github/administering-a-repository/about-secret-scanning) ». +| `secret_scanning_new_repos` | Contient des activités de configuration au niveau de l’organisation liées à l’analyse des secrets pour les référentiels créés dans l’organisation. +{%- endif %} {%- ifversion ghec or ghes or ghae %} | `security_key` | Contient des activités liées à l’inscription et à la suppression des clés de sécurité. +{%- endif %} {%- ifversion fpt or ghec %} | `sponsors` | Contient des événements liés aux boutons Parrainer (consultez « [Affichage d’un bouton de sponsor dans votre référentiel](/articles/displaying-a-sponsor-button-in-your-repository) »). +{%- endif %} {%- ifversion ghec or ghes or ghae %} | `ssh_certificate_authority` | Contient des activités liées à une autorité de certification SSH dans une organisation ou une entreprise. +| `ssh_certificate_requirement` | Contient des activités liées à l’obligation pour les membres d’utiliser des certificats SSH pour accéder aux ressources de l’organisation. +{%- endif %}{% ifversion sso-redirect %} | `sso_redirect` | Contient des activités liées à la redirection automatique des utilisateurs vers la connexion (consultez « [Application de stratégies pour les paramètres de sécurité dans votre entreprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users) »).{% endif %} | `staff` | Contient des activités liées à un administrateur de site effectuant une action. +| `team` | Contient des activités liées aux équipes d’une organisation. +| `team_discussions` | Contient des activités liées à la gestion des discussions d’équipe d’une organisation. +{%- ifversion ghec %} | `team_sync_tenant` |Contient des activités liées à la synchronisation d’équipe avec un fournisseur d’identité pour une entreprise ou une organisation. +{%- endif %} {%- ifversion fpt or ghes %} | `two_factor_authentication` | Contient des activités liées à l’authentification à 2 facteurs. +{%- endif %} | `user` | Contient des activités liées aux utilisateurs d’une organisation ou entreprise. +{%- ifversion ghec or ghes %} | `user_license` | Contient des activités liées à un utilisateur occupant un siège sous licence et faisant partie d’une entreprise. +{%- endif %} | `workflows` | Contient des activités liées aux workflows {% data variables.product.prodname_actions %}. diff --git a/translations/fr-FR/data/reusables/codespaces/stopping-a-codespace.md b/translations/fr-FR/data/reusables/codespaces/stopping-a-codespace.md index 028cac782aa2..af9a3a30ecbf 100644 --- a/translations/fr-FR/data/reusables/codespaces/stopping-a-codespace.md +++ b/translations/fr-FR/data/reusables/codespaces/stopping-a-codespace.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 4bdcc6ff93e7671d4dc368fc44784c963f549aae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 1eac21c20c1be77fe00ea676714a835fdb2e0de7 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/09/2022 -ms.locfileid: "148159044" +ms.lasthandoff: 12/01/2022 +ms.locfileid: "148189887" --- -Vous pouvez, à tout moment, arrêter un codespace. Lorsque vous arrêtez un codespace, tous les processus en cours d’exécution sont arrêtés et l’historique de terminal est effacé. Ensuite, lorsque vous le redémarrez, toutes les modifications enregistrées dans votre codespace sont disponibles. Si vous n’arrêtez pas explicitement un codespace, il continue de s’exécuter jusqu’à son expiration au terme du délai d’inactivité. Pour plus d’informations, consultez « [Cycle de vie d’un codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle#timeouts-for-github-codespaces) ». +Vous pouvez, à tout moment, arrêter un codespace. Lorsque vous arrêtez un codespace, tous les processus en cours d’exécution sont arrêtés et l’historique de terminal est effacé. Ensuite, lorsque vous le redémarrez, toutes les modifications enregistrées dans votre codespace sont disponibles. Si vous n’arrêtez pas explicitement un codespace, il continue de s’exécuter jusqu’à son expiration au terme du délai d’inactivité. Pour plus d’informations, consultez « [Cycle de vie d’un codespace](/codespaces/getting-started/the-codespace-lifecycle#timeouts-for-github-codespaces) ». Seuls les codespaces exécutés entraînent des frais de processeur. Un codespace arrêté entraîne uniquement des coûts de stockage. diff --git a/translations/fr-FR/data/reusables/copilot/copilot-cta-button.md b/translations/fr-FR/data/reusables/copilot/copilot-cta-button.md new file mode 100644 index 000000000000..c27a4cbcd35a --- /dev/null +++ b/translations/fr-FR/data/reusables/copilot/copilot-cta-button.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 9f7ac09b688bbe2b74a5cba71d2605365b7e7366 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148185126" +--- +Essayez {% data variables.product.prodname_copilot %} {% octicon "link-external" height:16 %} \ No newline at end of file diff --git a/translations/fr-FR/data/reusables/discussions/repository-category-limit.md b/translations/fr-FR/data/reusables/discussions/repository-category-limit.md index 6b19e7165e86..0524b4eeb7e1 100644 --- a/translations/fr-FR/data/reusables/discussions/repository-category-limit.md +++ b/translations/fr-FR/data/reusables/discussions/repository-category-limit.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 7b782aa3d23143a62b07aedf0a07df3734173d44 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: f58fb9410d93c9e50d33de5f1b12b9d6441ea561 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145133076" +ms.lasthandoff: 11/30/2022 +ms.locfileid: "148185613" --- -Chaque dépôt ou organisation peut avoir jusqu’à 10 catégories. +Chaque référentiel ou organisation peut avoir jusqu’à 25 catégories. diff --git a/translations/fr-FR/data/reusables/enterprise-managed/sso-redirect-release-phase.md b/translations/fr-FR/data/reusables/enterprise-managed/sso-redirect-release-phase.md new file mode 100644 index 000000000000..b6dc09bb6f0f --- /dev/null +++ b/translations/fr-FR/data/reusables/enterprise-managed/sso-redirect-release-phase.md @@ -0,0 +1,13 @@ +--- +ms.openlocfilehash: f246dbf76575a4338b8fa28ffbd5439c4121505f +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184054" +--- +{% note %} + +**Remarque :** la redirection automatique des utilisateurs vers la connexion est actuellement en version bêta pour {% data variables.product.prodname_emus %} et est susceptible d’être modifiée. + +{% endnote %} \ No newline at end of file diff --git a/translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md b/translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md index 2ebdbd0ac725..b508bf1893c6 100644 --- a/translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md +++ b/translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md @@ -1,5 +1,13 @@ -When you enable the allow list, the IP addresses you have configured are immediately added to the allow lists of organizations in your enterprise. If you disable the allow list, the addresses are removed from the organization allow lists. +--- +ms.openlocfilehash: f88150299e77eff08e5db75a7ef5bf5bd460328b +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184062" +--- +Lorsque vous activez la liste verte, les adresses IP que vous avez configurées sont immédiatement ajoutées aux listes vertes des organisations de votre entreprise. Si vous désactivez la liste verte, les adresses sont supprimées des listes vertes des organisations. -{% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." +{% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} Pour plus d’informations, consultez « [Gestion des adresses IP autorisées pour votre organisation](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization). » -You can choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} installed in your enterprise. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by GitHub Apps](#allowing-access-by-github-apps)." +Vous pouvez choisir d’ajouter automatiquement à votre liste verte toutes les adresses IP configurées pour {% data variables.product.prodname_github_apps %} installées dans votre entreprise. Le créateur d’une {% data variables.product.prodname_github_app %} peut configurer une liste verte pour son application, en spécifiant les adresses IP autorisées pour l’exécution de l’application. En héritant de sa liste verte dans la vôtre, vous évitez les refus de demandes de connexion de l’application. Pour plus d’informations, consultez « [Autorisation de l’accès par GitHub Apps](#allowing-access-by-github-apps) ». diff --git a/translations/fr-FR/data/reusables/identity-and-permissions/org-enterprise-allow-list-interaction.md b/translations/fr-FR/data/reusables/identity-and-permissions/org-enterprise-allow-list-interaction.md new file mode 100644 index 000000000000..d7bbc6e96e53 --- /dev/null +++ b/translations/fr-FR/data/reusables/identity-and-permissions/org-enterprise-allow-list-interaction.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 5ce9d5cc32dc07a1fe4ead5b16b75a7b10509467 +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184051" +--- +Les propriétaires de l’organisation peuvent ajouter des entrées supplémentaires à la liste verte pour leurs organisations. Toutefois, ils ne peuvent pas gérer les entrées qui ont été héritées de la liste verte du compte d’entreprise, et les propriétaires de l’entreprise ne peuvent pas gérer les entrées qui sont ajoutées à la liste verte de l’organisation. \ No newline at end of file diff --git a/translations/fr-FR/data/reusables/organizations/require-ssh-cert.md b/translations/fr-FR/data/reusables/organizations/require-ssh-cert.md index f4565b4bff01..39f0a64a4d04 100644 --- a/translations/fr-FR/data/reusables/organizations/require-ssh-cert.md +++ b/translations/fr-FR/data/reusables/organizations/require-ssh-cert.md @@ -1,8 +1,16 @@ -1. Optionally, to require members to use SSH certificates, select **Require SSH Certificates**, then click **Save**. - ![Require SSH Certificate checkbox and save button](/assets/images/help/organizations/require-ssh-cert.png) +--- +ms.openlocfilehash: abb4b47406958c1933c5c2bdf7d7e2e2c1091907 +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184047" +--- +1. Pour exiger que les membres utilisent des certificats SSH, vous pouvez sélectionner **Exiger des certificats SSH**, puis cliquer sur **Enregistrer**. + ![Case à cocher Exiger un certificat SSH et bout Enregistrer](/assets/images/help/organizations/require-ssh-cert.png) {% note %} - **Note:** When you require SSH certificates, the requirement does not apply to authorized third-party integrations or to {% data variables.product.prodname_dotcom %} features such as {% data variables.product.prodname_actions %}{% ifversion fpt or ghec %} and {% data variables.product.prodname_codespaces %}{% endif %}, which are trusted environments within the {% data variables.product.prodname_dotcom %} ecosystem. + **Remarque :** quand vous avez besoin de certificats SSH, cette exigence ne s’applique pas aux intégrations tierces autorisées ni aux fonctionnalités {% data variables.product.prodname_dotcom %} comme {% data variables.product.prodname_actions %}{% ifversion fpt or ghec %} et {% data variables.product.prodname_codespaces %}{% endif %} qui sont des environnements de confiance au sein de l’écosystème {% data variables.product.prodname_dotcom %}. {% endnote %} diff --git a/translations/fr-FR/data/reusables/rest-api/about-api-versions.md b/translations/fr-FR/data/reusables/rest-api/about-api-versions.md new file mode 100644 index 000000000000..6e438ea94182 --- /dev/null +++ b/translations/fr-FR/data/reusables/rest-api/about-api-versions.md @@ -0,0 +1,32 @@ +--- +ms.openlocfilehash: dd7c5f37ab5b2d699b47460195e02ae21fca1733 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148184386" +--- +L’API REST {% data variables.product.product_name %} est une version gérée. Le nom de la version de l’API est basé sur la date à laquelle la version de l’API a été publiée. Par exemple, la version de l’API `{{ initialRestVersioningReleaseDate }}` a été publiée sur {{ initialRestVersioningReleaseDateLong }}. + +Tous les changements cassants seront publiés dans une nouvelle version de l’API. Les changements cassants sont des modifications qui peuvent potentiellement arrêter une intégration. Les changements cassants incluent : + +- suppression d’une opération entière +- suppression ou changement de nom d’un paramètre +- suppression ou changement de nom d’un champ de réponse +- ajout d’un nouveau paramètre obligatoire +- rendre obligatoire un paramètre précédemment facultatif +- modification du type d’un paramètre ou d’un champ de réponse +- suppression des valeurs d’énumération +- ajout d’une nouvelle règle de validation à un paramètre existant +- modification des exigences d’authentification ou d’autorisation + +Tous les changements additifs (non cassants) seront disponibles dans toutes les versions d’API prises en charge. Les changements additifs sont des modifications qui ne doivent pas interrompre une intégration. Les changements additifs sont les suivants : + +- ajout d’une opération +- ajout d’un paramètre facultatif +- ajout d’un en-tête de demande facultatif +- ajout d’un champ de réponse +- ajout d’un en-tête de réponse +- ajout de valeurs d’énumération + +Lorsqu’une nouvelle version d’API REST est publiée, la version précédente de l’API est prise en charge pendant au moins 24 mois supplémentaires après la publication de la nouvelle version de l’API. diff --git a/translations/fr-FR/data/reusables/rest-api/version-header.md b/translations/fr-FR/data/reusables/rest-api/version-header.md new file mode 100644 index 000000000000..284e6283ac0c --- /dev/null +++ b/translations/fr-FR/data/reusables/rest-api/version-header.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 28c0a6c9cde70105e42feef89486c5c893ebbe72 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148184385" +--- +{% ifversion api-date-versioning %}--header "X-GitHub-Api-Version:{{ allVersions[currentVersion].latestApiVersion }}"{% endif %} diff --git a/translations/ko-KR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/ko-KR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index a1a74dd1f480..a7060df4d03e 100644 --- a/translations/ko-KR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/ko-KR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -31,6 +31,9 @@ Before you can enable and configure {% data variables.product.prodname_registry {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} 1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. + + - You must create a storage container prior to setting the container name and connection string. + ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% note %} diff --git a/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index be275c21f273..0b8f3a1a75c8 100644 --- a/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -14,17 +14,26 @@ topics: - Identity - Access management shortTitle: SSH key fingerprints -ms.openlocfilehash: b17285e62daf1f71c603e004a5bb00b786e3038a -ms.sourcegitcommit: 605b619588c51336f3ffe9d13c68503ae45cbfc6 +ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed +ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 10/07/2022 -ms.locfileid: '148013842' +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190332' --- 다음은 {% data variables.product.prodname_dotcom %}의 공개 키 지문입니다. - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8`(RSA) +- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - 사용되지 않음) - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM`(ECDSA) - `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU`(Ed25519) -자세한 내용은 [메타 정보 가져오기](/rest/meta#get-github-meta-information)를 참조하세요. +{% data variables.product.prodname_dotcom %} 호스트를 수동으로 확인하지 않도록 파일에 다음 ssh 키 항목을 `~.ssh/known_hosts` 추가할 수 있습니다. + +```text +github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl +github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg= +github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ== +``` + +자세한 내용은 "[{% data variables.product.prodname_dotcom %} 메타 정보 가져오기"를 참조하세요](/rest/meta#get-github-meta-information). diff --git a/translations/ko-KR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/ko-KR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 92f37fba9d43..801f015a7dbb 100644 --- a/translations/ko-KR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/ko-KR/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: HTTPS 포트를 통해 SSH 사용 +intro: '경우에 따라 방화벽은 SSH 연결을 완전히 허용하지 않습니다. [자격 증명 캐싱과 함께 HTTPS 복제](/github/getting-started-with-github/caching-your-github-credentials-in-git)를 사용할 수 없는 경우 HTTPS 포트를 통해 만들어진 SSH 연결을 사용하여 복제를 시도할 수 있습니다. 대부분의 방화벽 규칙은 이를 허용해야 하지만 프록시 서버가 방해할 수 있습니다.' 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: MT +ms.contentlocale: ko-KR +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190324' --- {% 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. +**{% data variables.product.prodname_ghe_server %} 사용자**: 현재 HTTPS 포트를 통해 SSH를 사용하여 {% data variables.product.prodname_ghe_server %}에 액세스할 수는 없습니다. {% endtip %} -To test if SSH over the HTTPS port is possible, run this SSH command: +HTTPS 포트를 통한 SSH가 가능한지 테스트하려면 다음 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 %}`. +**참고**: 포트 443의 호스트 이름은 가 아니라 `{% data variables.command_line.backticks %}`입니다`ssh.{% data variables.command_line.backticks %}`. -{% endnote %} +{% endnote %} -If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey). +성공했다면 다행입니다. 실패한 경우 [문제 해결 가이드에 따라야](/articles/error-permission-denied-publickey) 할 수 있습니다. -Now, to clone the repository, you can run the following command: +이제 리포지토리를 복제하려면 다음 명령을 실행할 수 있습니다. ``` $ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git ``` -## Enabling SSH connections over HTTPS +## HTTPS를 통해 SSH 연결 사용 -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. +포트 443을 통해 SSH할 `git@ssh.{% data variables.command_line.backticks %}` 수 있는 경우 SSH 설정을 재정의하여 {% data variables.location.product_location %}에 대한 모든 연결이 해당 서버 및 포트를 통해 실행되도록 할 수 있습니다. -To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: +SSH 구성 파일에서 이렇게 설정하려면 `~/.ssh/config`에 있는 파일을 편집하여 다음 섹션을 추가합니다. ``` 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 %}: +{% data variables.location.product_location %}에 한 번 더 연결하여 이 작업이 작동하는지 테스트할 수 있습니다. ```shell $ ssh -T git@{% data variables.command_line.codeblock %} @@ -61,18 +67,16 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > provide shell access. ``` -## Updating known hosts +## 알려진 호스트 업데이트 -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. +포트 443으로 전환한 후 GitHub와 처음 상호 작용할 때 호스트가 에서 `known_hosts`발견되지 않았거나 다른 이름으로 발견되었다는 경고 메시지가 나타날 수 있습니다. ```ShellSession > The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established. > ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. > This host key is known by the following other names/addresses: > ~/.ssh/known_hosts:32: github.com -> Are you sure you want to continue connecting (yes/no/[fingerprint])? +> 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 more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." +SSH 지문이 GitHub의 게시된 지문 중 하나와 일치한다고 가정하면 이 질문에 "예"라고 대답하는 것이 안전합니다. 지문 목록은 "[Github의 SSH 키 지문"을 참조하세요.](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints) diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md index c63eacda7551..aeb477c47515 100644 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md +++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md @@ -1,6 +1,6 @@ --- -title: 리포지토리에 대한 codespace 만들기 -intro: 리포지토리의 분기에 대한 Codespace를 만들어 온라인으로 개발할 수 있습니다. +title: Creating a codespace for a repository +intro: You can create a codespace for a branch in a repository to develop online. redirect_from: - /github/developing-online-with-github-codespaces/creating-a-codespace - /github/developing-online-with-codespaces/creating-a-codespace @@ -14,100 +14,95 @@ topics: - Fundamentals - Developer shortTitle: Create a codespace for a repo -ms.openlocfilehash: 7ce85e7d6dc180d08407205188434e3474b9cfd5 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 -ms.translationtype: MT -ms.contentlocale: ko-KR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160078' --- -## 리포지토리에 대한 codespace 만들기 정보 -{% data reusables.codespaces.ways-to-create-a-codespace %} 이 문서의 탭을 사용하여 codespace를 만드는 각 방법에 대한 지침을 표시합니다. +## About creating a codespace for a repository -{% data reusables.codespaces.starting-new-project-template %} 자세한 내용은 "[템플릿에서 codespace 만들기"를 참조하세요](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template). +{% data reusables.codespaces.ways-to-create-a-codespace %} Use the tabs in this article to display instructions for each of these ways of creating a codespace. + +{% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)." {% note %} -**참고**: JetBrains IDE를 사용하는 경우 {% data variables.product.prodname_cli %}를 사용하여 codespace를 만들 수 있습니다. 그런 다음 JetBrains 게이트웨이 애플리케이션을 사용하여 JetBrains IDE에서 codespace를 열 수 있습니다. 자세한 내용은 "[JetBrains IDE에서 Codespaces 사용"을 참조하세요](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide). +**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[Using Codespaces in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)." {% endnote %} -개인 {% data variables.product.prodname_dotcom_the_website %} 계정에서 {% data variables.product.prodname_github_codespaces %}을(를) 사용할 수 있으며, 무료 및 Pro 요금제의 계정에 대해 매월 무료 사용 할당량이 포함됩니다. {% data reusables.codespaces.codespaces-continue-by-paying %} +You can use {% data variables.product.prodname_github_codespaces %} on your personal {% data variables.product.prodname_dotcom_the_website %} account, with the quota of free use included each month for accounts on the Free and Pro plans. {% data reusables.codespaces.codespaces-continue-by-paying %} -조직은 구성원과 외부 협력자가 조직의 비용으로 codespace를 만들고 사용할 수 있도록 할 수 있습니다. 자세한 내용은 “[조직에 {% data variables.product.prodname_github_codespaces %} 사용](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)”을 참조하세요. +Organizations can enable members and outside collaborators to create and use codespaces at the organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)." {% data reusables.codespaces.codespaces-are-personal %} -리포지토리에서 codespace를 만드는 경우 codespace는 비어 있을 수 없는 특정 분기와 연결됩니다. 리포지토리 또는 분기당 둘 이상의 codespace를 만들 수 있습니다. +If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -### codespace 만들기 프로세스 +### The codespace creation process -codespace를 만드는 경우 개발 환경을 만들고 연결하기 위해 여러 단계가 수행됩니다. +When you create a codespace, a number of steps happen to create and connect you to your development environment: -- 1단계: VM 및 스토리지가 codespace에 할당됩니다. -- 2단계: 컨테이너가 생성되고 리포지토리가 복제됩니다. -- 3단계: codespace에 연결할 수 있습니다. -- 4단계: codespace에서 생성 후 설정을 계속합니다. +- Step 1: VM and storage are assigned to your codespace. +- Step 2: Container is created and your repository is cloned. +- Step 3: You can connect to the codespace. +- Step 4: Codespace continues with post-creation setup. -codespace를 만들 때 수행되는 작업에 대한 자세한 내용은 “[심층 분석](/codespaces/getting-started/deep-dive)”을 참조하세요. +For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)." -codespace의 수명 주기에 대한 자세한 내용은 "[codespace 수명 주기](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"를 참조하세요. +For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)." -codespace에 Git 후크를 사용하려면 4단계에서 [`devcontainer.json` 수명 주기 스크립트](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)(예: `postCreateCommand`)를 사용하여 후크를 설정해야 합니다. 리포지토리가 복제된 후 codespace 컨테이너가 생성되므로 컨테이너 이미지에서 구성된 [git 템플릿 디렉터리](https://git-scm.com/docs/git-init#_template_directory)는 codespace에 적용되지 않습니다. 대신, codespace가 생성된 후 후크를 설치해야 합니다. `postCreateCommand` 사용에 대한 자세한 내용은 {% data variables.product.prodname_vscode_shortname %} 설명서에서 [`devcontainer.json` 참조](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties)를 참조하세요. +If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.use-visual-studio-features %} {% data reusables.codespaces.prebuilds-crossreference %} -## 리포지토리에 대한 codespace 만들기 +## Creating a codespace for a repository {% webui %} {% data reusables.repositories.navigate-to-repo %} -1. 리포지토리 이름 아래에서 "분기" 드롭다운 메뉴를 사용하고 codespace를 만들려는 분기를 선택합니다. +1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create a codespace for. - ![분기 드롭다운 메뉴](/assets/images/help/codespaces/branch-drop-down.png) + ![Branch dropdown menu](/assets/images/help/codespaces/branch-drop-down.png) -1. **{% octicon "code" aria-label="The code icon" %} 코드** 단추를 클릭한 다음 **Codespaces** 탭을 클릭합니다. +1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab. - ![새 codespace 단추](/assets/images/help/codespaces/new-codespace-button.png) + ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - 이 리포지토리에 대한 codespace를 조직 또는 해당 부모 엔터프라이즈에 청구할 수 있는 경우 codespace에 대한 비용을 지불할 사람을 알려주는 메시지가 **BRANCH의 codespace 만들기** 단추 아래에 표시됩니다. + If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace. -1. 기본 옵션을 사용하거나 고급 옵션을 구성한 후 codespace를 만듭니다. +1. Create your codespace, either using the default options, or after configuring advanced options: - * **기본 옵션 사용** + * **Use the default options** - 기본 옵션을 사용하여 codespace를 만들려면 더하기 기호({% octicon "plus" aria-label="The plus icon" %})를 클릭합니다. 또는 현재 이 리포지토리에 대한 codespace가 없는 경우 **BRANCH에서 codespace 만들기** 를 클릭할 수 있습니다. + To create a codespace using the default options, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). Alternatively, if you don't currently have any codespaces for this repository, you can click **Create codespace on BRANCH**. - * **옵션 구성** + * **Configure options** - 다른 머신 유형 또는 특정 `devcontainer.json` 파일과 같은 codespace에 대한 고급 옵션을 구성하려면 다음을 수행합니다. + To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file: - 1. **Codespaces** 탭의 오른쪽 위에 있는 줄임표(**...**)를 클릭하고 **옵션을 사용하여 새로 만들기를** 선택합니다. + 1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab and select **New with options**. - ![기본 머신 유형 보기](/assets/images/help/codespaces/default-machine-type.png) + ![View the default machine type](/assets/images/help/codespaces/default-machine-type.png) - 1. codespace에 대한 옵션 페이지의 드롭다운 메뉴에서 원하는 옵션을 선택합니다. + 1. On the options page for your codespace, choose your preferred options from the dropdown menus. - ![codespace 옵션 페이지](/assets/images/help/codespaces/advanced-options.png) + ![The codespace options page](/assets/images/help/codespaces/advanced-options.png) {% note %} - **참고 사항** + **Notes** - * 옵션 페이지에 책갈피를 지정하여 이 리포지토리 및 분기에 대한 codespace를 빠르게 만들 수 있습니다. - * [https://github.com/codespaces/new](https://github.com/codespaces/new) 페이지에서는 모든 리포지토리 및 분기에 대한 codespace를 빠르게 생성할 수 있습니다. 브라우저의 주소 표시줄에 `codespace.new`를 입력하면 이 페이지로 빠르게 이동할 수 있습니다. - * `devcontainer.json` 파일에 대한 자세한 내용은 “[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)”를 참조하세요. - * 머신 유형에 대한 자세한 내용은 “[codespace에 대한 머신 유형 변경](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)”을 참조하세요. + * You can bookmark the options page to give you a quick way to create a codespace for this repository and branch. + * The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar. + * For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)." + * For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)." * {% data reusables.codespaces.codespaces-machine-type-availability %} {% endnote %} - 1. **codespace 만들기** 를 클릭합니다. + 1. Click **Create codespace**. {% endwebui %} @@ -121,30 +116,30 @@ codespace에 Git 후크를 사용하려면 4단계에서 [`devcontainer.json` {% data reusables.cli.cli-learn-more %} -새 codespace를 만들려면 `gh codespace create` 하위 명령을 사용합니다. +To create a new codespace, use the `gh codespace create` subcommand. ```shell gh codespace create ``` -리포지토리를 선택하라는 메시지가 표시됩니다. 이 리포지토리에 대한 codespace가 조직 또는 해당 부모 엔터프라이즈에 청구될 수 있는 경우 codespace에 대한 비용을 누가 지불할 것인지 알려주는 메시지가 표시됩니다. 그런 다음 분기, 개발 컨테이너 구성 파일(둘 이상의 사용 가능한 경우) 및 컴퓨터 유형(둘 이상의 사용 가능한 경우)을 선택하라는 메시지가 표시됩니다. +You are prompted to choose a repository. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available). -또는 플래그를 사용하여 다음 옵션을 일부 또는 모두 지정할 수 있습니다. +Alternatively, you can use flags to specify some or all of the options: ```shell gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE ``` -이 예에서는 `owner/repo`를 리포지토리 식별자로 바꿉니다. `branch`를 codespace에서 초기에 체크 아웃할 분기 이름 또는 커밋의 전체 SHA 해시로 바꿉니다. `b` 플래그 없이 `-r` 플래그를 사용하면 기본 분기에서 codespace가 생성됩니다. +In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch. -`path`을(를) 새 코드스페이스에 사용할 개발 컨테이너 구성 파일의 경로로 바꿉니다. 이 플래그를 생략했으며 둘 이상의 개발 컨테이너 파일을 사용할 수 있는 경우 목록에서 하나를 선택하라는 메시지가 표시됩니다. 개발 컨테이너 구성 파일에 대한 자세한 내용은 “[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”를 참조하세요. +Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." -`machine-type`을 사용 가능한 머신 유형의 유효한 식별자로 바꿉니다. 식별자는 `basicLinux32gb` 및 `standardLinux32gb`와 같은 문자열입니다. 사용 가능한 머신 유형은 리포지토리, 개인 계정, 위치에 따라 다릅니다. 잘못되었거나 사용할 수 없는 머신 유형을 입력하면 오류 메시지에 사용 가능한 유형이 표시됩니다. 이 플래그를 생략했으며 둘 이상의 머신 유형을 사용할 수 있는 경우 목록에서 하나를 선택하라는 메시지가 표시됩니다. +Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list. -이 명령의 옵션에 대한 자세한 내용은 [ {% data variables.product.prodname_cli %} 설명서](https://cli.github.com/manual/gh_codespace_create)를 참조하세요. +For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create). {% endcli %} -## 추가 참고 자료 -- "[기존 codespace 열기](/codespaces/developing-in-codespaces/opening-an-existing-codespace)" -- "[{% data variables.product.prodname_github_codespaces %}에서 열기' 배지 추가"](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge) +## Further reading +- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)" +- "[Adding an 'Open in {% data variables.product.prodname_github_codespaces %}' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)" diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md index a7561aaaf999..842a20e97185 100644 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md +++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md @@ -1,6 +1,6 @@ --- -title: 템플릿에서 codespace 만들기 -intro: 새 프로젝트를 시작하는 경우 빈 템플릿에서 codespace를 만들거나 수행하려는 작업 유형에 맞게 특별히 설계된 템플릿을 선택할 수 있습니다. +title: Creating a codespace from a template +intro: If you're starting a new project, you can create a codespace from a blank template or choose a template specially designed for the type of work you want to do. versions: fpt: '*' ghec: '*' @@ -11,95 +11,92 @@ topics: - Developer shortTitle: Create a codespace from a template miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 7c6ffdb4099b5d5d6f37ec5ffa7d73f838b36c76 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 -ms.translationtype: MT -ms.contentlocale: ko-KR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159862' --- -## {% data variables.product.prodname_github_codespaces %}에 대한 템플릿 정보 -새 프로젝트를 시작하는 경우 템플릿에서 codespace를 만들어 개발 작업을 빠르게 시작할 수 있습니다. 클라우드 기반 개발 환경에서 프로젝트에서 작업하고, 파일을 클라우드에 저장하고, 다른 사용자와 공유하거나 로컬 컴퓨터에 복제할 수 있는 새 원격 리포지토리에 작업을 게시할 수 있습니다. +## About templates for {% data variables.product.prodname_github_codespaces %} + +If you're starting a new project, you can get started with development work quickly by creating a codespace from a template. You'll be able to work on your project in a cloud-based development environment, save your files in the cloud, and publish your work to a new remote repository that you can share with others or clone to your local machine. {% note %} -**참고**: 리포지토리가 아닌 템플릿에서 만든 Codespace는 항상 개인 계정에 청구됩니다. 자세한 내용은 “[{% data variables.product.prodname_github_codespaces %} 청구 정보](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)”를 참조하세요. +**Note**: Codespaces created from a template, rather than from a repository, are always billed to your personal account. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." {% endnote %} -빈 템플릿에서 시작하거나 React 또는 Jupyter Notebook 같은 인기 있는 기술에 대해 {% data variables.product.company_short %}에서 유지 관리하는 템플릿 중에서 선택하거나 {% data variables.product.prodname_dotcom %}의 템플릿 리포지토리에서 codespace를 시작할 수 있습니다. 빈 템플릿을 사용하면 클라우드 기반 컴퓨팅 리소스와 기본 codespace 이미지로 미리 설치된 도구, 언어 및 런타임 환경에 액세스할 수 있는 빈 디렉터리로 시작합니다. 다른 템플릿을 사용하면 작업 중인 기술에 대한 시작 파일과 일반적으로 일부 사용자 지정 환경 구성이 포함된 추가 정보 파일, `.gitignore` 파일 및 개발 컨테이너 구성 파일과 같은 추가 파일을 얻을 수 있습니다. 개발 컨테이너 및 기본 이미지에 대한 자세한 내용은 "[개발 컨테이너 소개"를 참조하세요.](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) +You can start from a blank template, choose from templates maintained by {% data variables.product.company_short %} for popular technologies such as React or Jupyter Notebook, or launch a codespace from any template repository on {% data variables.product.prodname_dotcom %}. With a blank template, you'll start with an empty directory, with access to cloud-based compute resources and the tools, languages, and runtime environments that come preinstalled with the default codespace image. With other templates, you'll get starter files for the technology you're working with, plus typically some extra files such as a README file, a `.gitignore` file, and dev container configuration files containing some custom environment configuration. For more information on dev containers and the default image, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." -예를 들어 {% data variables.product.company_short %}의 React 템플릿에서 codespace를 만드는 경우 , 및 `app.js``package.json`와 같은 `index.js`간단한 애플리케이션에 대한 템플릿 파일이 포함된 작업 영역에 도착합니다. codespace가 열리면 개발 서버가 자동으로 시작되고 {% data variables.product.prodname_vscode_shortname %} 웹 클라이언트 내의 간단한 브라우저 탭에서 실행 중인 애플리케이션을 볼 수 있습니다. +As an example, if you create a codespace from {% data variables.product.company_short %}'s React template, you'll arrive in a workspace containing template files for a simple application, such as `index.js`, `app.js`, and `package.json`. Shortly after the codespace opens, a development server will start up automatically, and you will be able to view the running application in a simple browser tab within the {% data variables.product.prodname_vscode_shortname %} web client. -![codespace에서 실행되는 React 템플릿의 스크린샷](/assets/images/help/codespaces/react-template.png) +![Screenshot of the React template running in a codespace](/assets/images/help/codespaces/react-template.png) -템플릿에 포함된 파일 및 구성은 템플릿 리포지토리에 정의됩니다. codespace를 만들 때 템플릿 리포지토리가 codespace에 복제됩니다. 그런 다음 링크가 끊어지고 codespace는 하나의 리포지토리에 게시할 때까지 원격 리포지토리에 연결되지 않습니다. +The files and configuration included in templates are defined in template repositories. The template repository is cloned into your codespace when you create the codespace. After that, the link is severed, and your codespace won't be linked to a remote repository until you publish to one. {% tip %} -**팁:** 사용자가 프레임워크, 라이브러리 또는 기타 프로젝트를 시작할 수 있도록 {% data variables.product.prodname_github_codespaces %}에 사용할 템플릿 리포지토리를 설정할 수 있습니다. 자세한 내용은 "[{% data variables.product.prodname_github_codespaces %}에 대한 템플릿 리포지토리 설정](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)"을 참조하세요. +**Tip:** To help people get started with your framework, library, or other project, you can set up a template repository for use with {% data variables.product.prodname_github_codespaces %}. For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)." {% endtip %} -## {% data variables.product.company_short %} 템플릿에서 codespace 만들기 +## Creating a codespace from a {% data variables.product.company_short %} template -빈 템플릿을 포함하여 {% data variables.product.company_short %}에서 유지 관리하는 템플릿은 "Codespaces" 페이지에서 사용할 수 있습니다. +Templates maintained by {% data variables.product.company_short %}, including the blank template, are available from the "Your codespaces" page. -{% data reusables.codespaces.your-codespaces-procedure-step %} {% data reusables.codespaces.view-all-templates-step %} -1. 필요에 따라 템플릿의 파일이 포함된 템플릿 리포지토리를 보려면 템플릿의 이름을 클릭합니다. +{% data reusables.codespaces.your-codespaces-procedure-step %} +{% data reusables.codespaces.view-all-templates-step %} +1. Optionally, to view the template repository containing the files for a template, click the name of the template. - !["React"이 강조 표시된 "빠른 시작 템플릿 탐색" 섹션의 스크린샷](/assets/images/help/codespaces/react-template-name.png) + ![Screenshot of the "Explore quick start templates" section, with "React" highlighted](/assets/images/help/codespaces/react-template-name.png) -1. 시작하려는 템플릿 아래에서 **이 템플릿 사용을** 클릭합니다. +1. Under the template you want to launch, click **Use this template**. - ![React 템플릿 아래에 "이 템플릿 사용" 단추가 강조 표시된 빠른 시작 템플릿의 스크린샷](/assets/images/help/codespaces/react-template-button.png) + ![Screenshot of the quick start templates, with the "Use this template" button highlighted under the React template](/assets/images/help/codespaces/react-template-button.png) {% data reusables.codespaces.template-codespaces-default-editor %} -## 템플릿 리포지토리에서 codespace 만들기 +## Creating a codespace from a template repository -템플릿 리포지토리에서 codespace를 만든 다음 준비가 되면 새 리포지토리에 작업을 게시할 수 있습니다. 템플릿 리포지토리에 대한 자세한 내용은 "[템플릿에서 리포지토리 만들기"를](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates) 참조하세요. +You can create a codespace from any template repository, then publish your work to a new repository when you are ready. For more information on template repositories, see "[Creating a repository from a template](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates)." -{% data reusables.repositories.navigate-to-repo %} {% data reusables.codespaces.open-template-in-codespace-step %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.codespaces.open-template-in-codespace-step %} {% note %} - **참고:** 템플릿 리포지토리의 유지 관리자이고 템플릿 리포지토리 자체에 대한 변경 내용을 커밋하려는 경우 **{% octicon "code" aria-label="The code icon" %} 코드** 드롭다운에서 codespace를 만들어야 합니다. 자세한 내용은 "[리포지토리에 대한 codespace 만들기"를 참조하세요](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository). + **Note:** If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." {% endnote %} {% data reusables.codespaces.template-codespaces-default-editor %} -## {% data variables.product.product_name %}의 리포지토리에 게시 +## Publishing to a repository on {% data variables.product.product_name %} {% data reusables.codespaces.about-publishing-templates %} -### {% data variables.product.prodname_vscode_shortname %}에서 게시 +### Publishing from {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.publishing-template-codespaces %} -codespace가 게시되면 {% data variables.product.prodname_github_codespaces %} 환경을 사용자 지정할 수 있는 다양한 옵션에 액세스할 수 있습니다. 예를 들어 다음을 수행할 수 있습니다. +When a codespace is published, you have access to a greater range of options to customize your {% data variables.product.prodname_github_codespaces %} experience. For example, you can: -- codespace의 컴퓨터 유형을 변경하여 수행 중인 작업에 적합한 리소스를 사용하고 있는지 확인합니다("[codespace에 대한 컴퓨터 유형 변경](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)"참조). -- {% data variables.product.prodname_dotcom %}에서 자동으로 GPG를 사용하여 codespace에서 커밋에 서명하도록 허용합니다("[{% data variables.product.prodname_github_codespaces %}에 대한 GPG 확인 관리](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)"참조). -- codespace와 암호화된 비밀을 공유합니다("[codespaces에 대한 암호화된 비밀 관리](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"참조). +- Change the machine type of your codespace to make sure you're using resources appropriate for the work you're doing (see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)"). +- Allow {% data variables.product.prodname_dotcom %} to automatically use GPG to sign commits you make in your codespace (see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)"). +- Share encrypted secrets with your codespace (see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"). -### {% data variables.product.prodname_dotcom_the_website %}에서 게시 +### Publishing from {% data variables.product.prodname_dotcom_the_website %} -{% data variables.product.prodname_dotcom_the_website %}의 "codespaces" 페이지에서 게시되지 않은 codespace를 게시할 수 있습니다. 현재 브라우저에서 열려 있지 않은 codespace를 게시하려는 경우에 유용합니다. 이렇게 하면 작업이 리포지토리에 유지되지만 기존 codespace와 새 리포지토리 사이에는 링크가 없습니다. 그러나 새 리포지토리로 이동하여 여기에서 codespace를 만들 수 있으며 이 codespace는 리포지토리에 연결됩니다. +You can publish an unpublished codespace from the "Your codespaces" page on {% data variables.product.prodname_dotcom_the_website %}. This is useful if you want to publish a codespace that you don't currently have open in your browser. If you do this, your work will be preserved in a repository, but there won't be a link between your existing codespace and the new repository. However, you can navigate to the new repository and create a codespace from there, and this codespace will be connected to the repository. {% data reusables.codespaces.your-codespaces-procedure-step %} -1. 게시되지 않은 codespace 옆에 있는 줄임표(**...**)를 클릭한 다음 **새 리포지토리에 게시를** 선택합니다. +1. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**. - !["새 리포지토리에 게시" 단추의 스크린샷](/assets/images/help/codespaces/publish-to-new-repository.png) -1. 새 리포지토리의 이름을 선택하고 **퍼블릭** 또는 **프라이빗** 으로 설정한 다음 **리포지토리 만들기** 를 클릭합니다. + ![Screenshot of the "Publish to a new repository" button](/assets/images/help/codespaces/publish-to-new-repository.png) +1. Choose a name for your new repository, set it as **Public** or **Private**, and click **Create repository**. - !["새 리포지토리에 게시" 드롭다운 스크린샷](/assets/images/help/codespaces/template-new-repository-settings.png) -1. 필요에 따라 새 리포지토리를 보려면 **리포지토리 보기를** 클릭합니다. + ![Screenshot of the "Publish to a new repository" dropdown](/assets/images/help/codespaces/template-new-repository-settings.png) +1. Optionally, to view the new repository, click **See repository**. -## 추가 정보 +## Further reading -- "[리포지토리에 대한 codespace 만들기](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" -- "[codespace 수명 주기](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" -- "[codespace에서 소스 제어 사용](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" +- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)" +- "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" \ No newline at end of file diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 8d64de2d5db1..2c5021858b65 100644 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -13,18 +13,18 @@ topics: - Fundamentals - Developer shortTitle: Delete a codespace -ms.openlocfilehash: c9f1f6eb407c985d8981504de28e39a4bf742f7a -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 24b53cc0cead2b6b15894ada4c799abc8e1c6e7a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158663' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188258' --- -{% data variables.product.prodname_cli %}, {% data variables.product.prodname_vscode %}을(를) 사용하거나 웹 브라우저에서 터미널에서 다양한 방법으로 codespace를 삭제할 수 있습니다. 이 문서의 탭을 사용하여 codespace를 삭제하는 각 방법에 대한 지침을 표시합니다. +{% data variables.product.prodname_cli %}를 사용하여 터미널에서, {% data variables.product.prodname_vscode %}에서 또는 웹 브라우저에서 다양한 방법으로 codespace를 삭제할 수 있습니다. 이 문서의 탭을 사용하여 codespace를 삭제하는 각 방법에 대한 지침을 표시합니다. {% note %} -**참고**: JetBrains 게이트웨이 내 또는 JetBrains 클라이언트 애플리케이션 또는 JupyterLab 내에서 codespace를 삭제할 수 없습니다. +**참고**: JetBrains 게이트웨이 또는 JetBrains 클라이언트 애플리케이션 내에서 또는 JupyterLab 내에서 codespace를 삭제할 수 없습니다. {% endnote %} @@ -135,5 +135,5 @@ gh codespace delete --repo octo-org/octo-repo --days 7 REST API를 사용하여 조직의 codespace를 삭제할 수도 있습니다. 자세한 내용은 “[Codespaces 조직](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)”을 참조하세요. ## 추가 정보 -- "[codespace 수명 주기](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" -- "[codespaces 자동 삭제 구성](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)" +- "[codespace 수명 주기](/codespaces/getting-started/the-codespace-lifecycle)" +- "[codespace의 자동 삭제 구성](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)" diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md index 878eb6902284..10a18e492429 100644 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md +++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md @@ -22,11 +22,11 @@ children: - /using-github-codespaces-in-visual-studio-code - /using-github-codespaces-in-your-jetbrains-ide - /using-github-codespaces-with-github-cli -ms.openlocfilehash: 166283bd0fbc71b8acc180b20ef597dbc0a50781 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 6ace677a68ce7b592ac8ad2a8b83ae4d948b8747 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159015' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188290' --- diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md index c9cdeb389160..d009d93dc216 100644 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md +++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md @@ -1,6 +1,6 @@ --- -title: Opening an existing codespace -intro: 'You can reopen a codespace that you have closed or stopped and return to your work.' +title: 기존 codespace 열기 +intro: 닫거나 중지한 codespace를 다시 열고 작업으로 돌아갈 수 있습니다. versions: fpt: '*' ghec: '*' @@ -10,46 +10,51 @@ topics: - Fundamentals - Developer shortTitle: Open an existing codespace +ms.openlocfilehash: b139b7f4e8a696416c97b3c400d09a9f26371b9c +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ko-KR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188298' --- - {% jetbrains %} {% data reusables.codespaces.codespaces-jetbrains-beta-note %} {% endjetbrains %} -You can reopen any of your active or stopped codespaces on {% data variables.product.prodname_dotcom_the_website %}, in a JetBrains IDE, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. You can't reopen a codespace that has been deleted. For more information, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)." +{% data variables.product.prodname_dotcom_the_website %}, JetBrains IDE, {% data variables.product.prodname_vscode %}에서 또는 {% data variables.product.prodname_cli %}를 사용하여 활성 또는 중지된 codespace를 다시 열 수 있습니다. 삭제된 codespace는 다시 열 수 없습니다. 자세한 내용은 "[codespace 수명 주기"를 참조하세요](/codespaces/getting-started/the-codespace-lifecycle). -You can view all your codespaces on the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). From this page, you can: +[github.com/codespaces](https://github.com/codespaces) "Codespaces" 페이지에서 모든 codespace를 볼 수 있습니다. 이 페이지에서 다음을 수행할 수 있습니다. -- Open, stop, or delete your codespaces. -- See who owns (and may be billed for) your codespaces: your personal account, or organizations you belong to. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." -- Create a new codespace, either by choosing one of {% data variables.product.company_short %}'s templates or by clicking **New codespace**. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)" and "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)." +- codespace를 열거나 중지하거나 삭제합니다. +- codespace(개인 계정 또는 속한 조직)를 소유(및 청구할 수 있음)를 확인합니다. 자세한 내용은 “[{% data variables.product.prodname_github_codespaces %} 청구 정보](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)”를 참조하세요. +- {% data variables.product.company_short %}의 템플릿 중 하나를 선택하거나 **새 codespace를 클릭하여 새 codespace** 를 만듭니다. 자세한 내용은 "[템플릿에서 codespace 만들기](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)" 및 "[리포지토리에 대한 codespace 만들기"를 참조하세요](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository). -## Opening an existing codespace +## 기존 codespace 열기 {% webui %} {% data reusables.codespaces.your-codespaces-procedure-step %} -1. To open a codespace in your default editor, click the name of the codespace. {% data reusables.codespaces.about-changing-default-editor %} For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)." +1. 기본 편집기에서 codespace를 열려면 codespace의 이름을 클릭합니다. {% data reusables.codespaces.about-changing-default-editor %} 자세한 내용은 "[{% data variables.product.prodname_github_codespaces %}에 대한 기본 편집기 설정](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)"을 참조하세요. - To open the codespace in an editor other than your default: + 기본값이 아닌 편집기에서 codespace를 열려면 다음을 수행합니다. - 1. Click the ellipsis (**...**) to the right of the codespace you want to open. - 1. Click **Open in**. - 1. Click **Open in APPLICATION**. + 1. 열려는 codespace의 오른쪽에 있는 줄임표(**...**)를 클릭합니다. + 1. **열기를** 클릭합니다. + 1. **애플리케이션에서 열기를** 클릭합니다. - ![Screenshot of the "Open in" dialog box, with "Open in Visual Studio Code" highlighted](/assets/images/help/codespaces/open-codespace-in-another-editor.png) + !["Visual Studio Code 열기"가 강조 표시된 "열기" 대화 상자의 스크린샷](/assets/images/help/codespaces/open-codespace-in-another-editor.png) - You can open the codespace in: - * Your browser + 다음에서 codespace를 열 수 있습니다. + * 브라우저 * {% data variables.product.prodname_vscode %} - * JetBrains Gateway + * JetBrains 게이트웨이 * JupyterLab {% data reusables.codespaces.application-installed-locally %} - If you choose **JupyterLab**, the JupyterLab application must be installed in the codespace. {% data reusables.codespaces.jupyterlab-in-default-image %} + **JupyterLab을** 선택하는 경우 Codespace에 JupyterLab 애플리케이션을 설치해야 합니다. {% data reusables.codespaces.jupyterlab-in-default-image %} {% endwebui %} @@ -57,29 +62,28 @@ You can view all your codespaces on the "Your codespaces" page at [github.com/co {% note %} -**Note:** {% data reusables.codespaces.using-codespaces-in-vscode %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)." +**참고:** {% data reusables.codespaces.using-codespaces-in-vscode %} 자세한 내용은 "[{% data variables.product.prodname_vscode %}에서 {% data variables.product.prodname_github_codespaces %} 사용"을 참조하세요](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code). {% endnote %} -1. In the {% data variables.product.prodname_vscode_shortname %} desktop application, open the Command Palette with Command+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux). -1. Type "Codespaces" and select one of the following commands. - - To open a codespace in a new window of {% data variables.product.prodname_vscode_shortname %}, select **Codespaces: Open Codespace in New Window** - - To open a codespace in the web editor, select **Codespaces: Open in Browser** -1. Click the codespace that you want to open. +1. {% data variables.product.prodname_vscode_shortname %} 데스크톱 애플리케이션에서 명령ShiftP(Mac) 또는 Ctrl+Shift++P(Windows/Linux)를 사용하여 명령+ 팔레트를 엽니다. +1. "Codespaces"를 입력하고 다음 명령 중 하나를 선택합니다. + - {% data variables.product.prodname_vscode_shortname %}의 새 창에서 **codespace를 열려면 Codespaces: 새 창에서 Codespace 열기** 를 선택합니다. + - 웹 편집기에서 codespace를 열려면 **Codespaces: 브라우저에서 열기를** 선택합니다. +1. 열려는 codespace를 클릭합니다. - ![Screenshot of a list of codespaces in Visual Studio Code](/assets/images/help/codespaces/open-codespace-from-vscode.png) + ![Visual Studio Code codespace 목록의 스크린샷](/assets/images/help/codespaces/open-codespace-from-vscode.png) -You can also access the commands listed above by navigating to the Remote Explorer view in {% data variables.product.prodname_vscode_shortname %} and right-clicking the codespace that you want to open. +{% data variables.product.prodname_vscode_shortname %}에서 원격 탐색기 보기로 이동하고 열려는 codespace를 마우스 오른쪽 단추로 클릭하여 위에 나열된 명령에 액세스할 수도 있습니다. -![Screenshot of a codespace selected in the Remote Explorer, with "Open in Browser" highlighted](/assets/images/help/codespaces/open-codespace-remote-explorer.png) +!["브라우저에서 열기"가 강조 표시된 원격 탐색기에서 선택한 codespace의 스크린샷](/assets/images/help/codespaces/open-codespace-remote-explorer.png) -{% data reusables.codespaces.remote-explorer %} -{% endvscode %} +{% data reusables.codespaces.remote-explorer %} {% endvscode %} {% cli %} -1. In a terminal, enter one of the following {% data variables.product.prodname_cli %} commands. - - To open a codespace in {% data variables.product.prodname_vscode_shortname %}, enter: +1. 터미널에서 다음 {% data variables.product.prodname_cli %} 명령 중 하나를 입력합니다. + - {% data variables.product.prodname_vscode_shortname %}에서 codespace를 열려면 다음을 입력합니다. ```shell{:copy} gh codespace code @@ -87,17 +91,17 @@ You can also access the commands listed above by navigating to the Remote Explor {% note %} - **Note**: You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. + **참고**: 로컬 컴퓨터에 {% data variables.product.prodname_vscode_shortname %}이(가) 설치되어 있어야 합니다. 자세한 내용은 {% data variables.product.prodname_vscode_shortname %} 설명서의 "Visual Studio Code [설정](https://code.visualstudio.com/docs/setup/setup-overview)"을 참조하세요. {% endnote %} - - To open a codespace in the browser, enter: + - 브라우저에서 codespace를 열려면 다음을 입력합니다. ```shell{:copy} gh codespace code --web ``` - - To open a codespace in JupyterLab, enter: + - JupyterLab에서 codespace를 열려면 다음을 입력합니다. ```shell{:copy} gh codespace code --jupyter @@ -105,14 +109,14 @@ You can also access the commands listed above by navigating to the Remote Explor {% note %} - **Note**: {% data reusables.codespaces.jupyterlab-installed-in-codespace %} + **참고**: {% data reusables.codespaces.jupyterlab-installed-in-codespace %} {% endnote %} -1. Using the arrow keys, navigate to the codespace that you want to open. -1. To open the codespace, press Enter. +1. 화살표 키를 사용하여 열려는 codespace로 이동합니다. +1. codespace를 열려면 Enter 키를 누릅니 다. -For more information, see [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) in the {% data variables.product.prodname_cli %} manual. +자세한 내용은 {% data variables.product.prodname_cli %} 설명서를 참조 [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) 하세요. {% endcli %} @@ -120,4 +124,4 @@ For more information, see [`gh codespace code`](https://cli.github.com/manual/gh {% data reusables.codespaces.opening-codespace-in-jetbrains %} -{% endjetbrains %} \ No newline at end of file +{% endjetbrains %} diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md index e27903b21e95..600a9c98a600 100644 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md +++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md @@ -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: MT ms.contentlocale: ko-KR -ms.lasthandoff: 11/29/2022 -ms.locfileid: '148185085' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188250' --- {% jetbrains %} @@ -27,14 +27,14 @@ ms.locfileid: '148185085' {% data reusables.codespaces.stopping-a-codespace %} -codespace를 만들거나 액세스하는 위치에 관계없이 에서 브라우저 https://github.com/codespaces에서 보고 관리할 수 있습니다. +codespace를 만들거나 액세스하는 위치에 관계없이 브라우저에서 https://github.com/codespaces보고 관리할 수 있습니다. ## Codespace 중지 {% webui %} {% data reusables.codespaces.navigate-to-codespaces-page %} - 1. 중지하려는 codespace 오른쪽에서 elipsis(**...**)를 클릭합니다. + 1. 중지하려는 codespace의 오른쪽에서 elipsis(**...**)를 클릭합니다. 1. **codespace 중지** 를 클릭합니다. ![codespace를 중지하는 옵션의 스크린샷](/assets/images/help/codespaces/stop-codespace-webui.png) @@ -80,13 +80,13 @@ codespace를 만들거나 액세스하는 위치에 관계없이 에서 브라 codespace를 다시 시작하면 {% data variables.product.prodname_vscode %} 또는 브라우저에서 열도록 선택할 수 있습니다. - - codespace를 다시 시작하고 {% data variables.product.prodname_vscode %}에서 열려면 하위 명령을 사용한 `gh codespace code` 다음, 표시된 목록에서 다시 시작할 codespace를 선택합니다. + - codespace를 다시 시작하고 {% data variables.product.prodname_vscode %}에서 열려면 하위 명령을 사용한 `gh codespace code` 다음, 표시된 목록에서 다시 시작하려는 codespace를 선택합니다. ```shell{:copy} gh codespace code ``` - - codespace를 다시 시작하고 브라우저에서 열려면 하위 명령을 사용한 `gh codespace open --web` 다음 표시되는 목록에서 다시 시작할 codespace를 선택합니다. + - codespace를 다시 시작하고 브라우저에서 열려면 하위 명령을 사용한 `gh codespace open --web` 다음, 표시되는 목록에서 다시 시작하려는 codespace를 선택합니다. ```shell{:copy} gh codespace open --web @@ -98,7 +98,7 @@ codespace를 다시 시작하면 {% data variables.product.prodname_vscode %} {% data reusables.vs-code.open-command-palette %} 1. **Codespaces: 옵션 목록에서 Codespace에 연결을** 입력 `connect` 하고 선택합니다. -1. codespace 목록에서 다시 시작할 codespace를 선택합니다. +1. codespace 목록에서 다시 시작하려는 codespace를 선택합니다. {% endvscode %} @@ -110,4 +110,4 @@ codespace를 다시 시작하면 {% data variables.product.prodname_vscode %} ## 추가 정보 -- "[codespace 수명 주기](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" +- "[codespace 수명 주기](/codespaces/getting-started/the-codespace-lifecycle)" diff --git a/translations/ko-KR/content/codespaces/getting-started/index.md b/translations/ko-KR/content/codespaces/getting-started/index.md index acc08e42e678..5748b8789fd4 100644 --- a/translations/ko-KR/content/codespaces/getting-started/index.md +++ b/translations/ko-KR/content/codespaces/getting-started/index.md @@ -9,11 +9,11 @@ children: - /quickstart - /the-codespace-lifecycle - /deep-dive -ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: e89c26ddd6606192f93449fbc99660afe1fb2506 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160253' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188274' --- diff --git a/translations/ko-KR/content/codespaces/getting-started/the-codespace-lifecycle.md b/translations/ko-KR/content/codespaces/getting-started/the-codespace-lifecycle.md new file mode 100644 index 000000000000..55b00c5d84d2 --- /dev/null +++ b/translations/ko-KR/content/codespaces/getting-started/the-codespace-lifecycle.md @@ -0,0 +1,73 @@ +--- +title: codespace 수명 주기 +intro: '{% data variables.product.prodname_github_codespaces %} 환경에서 개발하고 전체 codespace 수명 주기 동안 데이터를 유지 관리할 수 있습니다.' +versions: + fpt: '*' + ghec: '*' +type: overview +topics: + - Codespaces + - Developer +redirect_from: + - /codespaces/developing-in-codespaces/codespaces-lifecycle + - /codespaces/developing-in-codespaces/the-codespace-lifecycle +ms.openlocfilehash: 8f223bce2acf2f6dc6200271397c0d70f28aefe4 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ko-KR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188371' +--- +## Codespace의 수명 주기 정보 + +Codespace의 수명 주기는 Codespace를 만들 때 시작되고 Codespace를 삭제할 때 종료됩니다. 실행 중인 프로세스에 영향을 주지 않고 활성 Codespace의 연결을 끊고 다시 연결할 수 있습니다. 프로젝트에서 변경한 내용에 손실 없이 Codespace를 중지하고 다시 시작할 수 있습니다. + +## codespace 만들기 + +프로젝트에서 작업하려는 경우 새 Codespace를 만들거나 기존 Codespace를 열도록 선택할 수 있습니다. {% data variables.product.prodname_github_codespaces %}에서 개발할 때마다 리포지토리의 분기에서 새 codespace를 만들거나 기능에 대한 장기 실행 codespace를 유지할 수 있습니다. {% data reusables.codespaces.starting-new-project-template %} 자세한 내용은 "[리포지토리에 대한 codespace 만들기](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" 및 "[템플릿에서 codespace 만들기"를](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template) 참조하세요. + +{% data reusables.codespaces.max-number-codespaces %} 마찬가지로 활성 코드스페이스의 최대 수에 도달하고 다른 코드스페이스를 시작하려고 하면 활성 코드스페이스 중 하나를 중지하라는 메시지가 표시됩니다. + +프로젝트에서 작업할 때마다 새 Codespace를 만들도록 선택한 경우 새 커밋이 {% data variables.product.prodname_dotcom %}에 있도록 변경 내용을 정기적으로 푸시해야 합니다. 프로젝트에 대해 장기 실행 Codespace를 사용하도록 선택하는 경우 환경에 최신 커밋이 있도록 Codespace에서 작업을 시작할 때마다 리포지토리의 기본 분기에서 끌어와야 합니다. 이 워크플로는 로컬 컴퓨터에 있는 프로젝트를 작업하는 경우와 매우 유사합니다. + +{% data reusables.codespaces.prebuilds-crossreference %} + +## Codespace의 변경 내용 저장 + +웹을 통해 Codespace에 연결하면 자동 저장이 웹 편집기에서 자동으로 활성화되고 지연 후 변경 내용을 저장하도록 구성됩니다. 데스크톱에서 실행되는 {% data variables.product.prodname_vscode %}를 통해 Codespace에 연결하는 경우 자동 저장을 사용 설정해야 합니다. 자세한 내용은 {% data variables.product.prodname_vscode %} 설명서의 [저장/자동 저장](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save)을 참조하세요. + +작업은 클라우드의 가상 머신에 저장됩니다. codespace를 닫고 중지하고 나중에 저장된 작업으로 돌아갈 수 있습니다. 저장되지 않은 변경 내용이 있는 경우 편집기에 종료하기 전에 저장하라는 메시지가 표시됩니다. 그러나 codespace가 삭제되면 작업도 삭제됩니다. 작업을 유지하려면 변경 내용을 커밋하고 원격 리포지토리에 푸시하거나 템플릿에서 codespace를 만든 경우 새 원격 리포지토리에 작업을 게시해야 합니다. 자세한 내용은 “[codespace에서 소스 제어 사용](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)”을 참조하세요. + +## {% data variables.product.prodname_github_codespaces %}에 대한 시간 제한 + +상호 작용 없이 Codespace를 실행 상태로 두거나 Codespace를 명시적으로 중지하지 않고 종료하는 경우 Codespace는 비활성 기간 후에 시간 초과되고 실행을 중지합니다. 기본적으로 Codespace는 30분 동안 활동이 없으면 시간 제한이 적용되지만 사용자가 만든 새 Codespace의 시간 제한 기간은 사용자 지정할 수 있습니다. Codespace의 기본 시간 제한 기간을 설정하는 방법에 대한 자세한 내용은 “[{% data variables.product.prodname_github_codespaces %}의 시간 제한 기간 설정](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)”을 참조하세요. Codespace를 중지하는 방법에 대한 자세한 내용은 “[Codespace 중지](#stopping-a-codespace)”를 참조하세요. + +Codespace가 시간 초과되면 변경 내용이 마지막으로 저장된 시점부터 데이터가 보존됩니다. 자세한 내용은 “[Codespace의 변경 내용 저장](#saving-changes-in-a-codespace)”을 참조하세요. + +## Codespace 다시 빌드 + +codespace를 다시 빌드하여 개발 컨테이너 구성에 대한 변경 내용을 구현할 수 있습니다. 대부분의 경우 Codespace를 다시 빌드하는 대신 새 Codespace를 만들면 됩니다. 기본적으로 codespace를 다시 빌드할 때 {% data variables.product.prodname_github_codespaces %}은 캐시의 이미지를 다시 사용하여 다시 빌드 프로세스를 가속화합니다. 또는 캐시를 지우고 새 이미지로 컨테이너를 다시 빌드하는 전체 다시 빌드를 수행할 수 있습니다. + +자세한 내용은 "[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)" 및 "컨테이너[의 전체 다시 빌드 수행"을 참조하세요](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container). + +## Codespace 중지 + +{% data reusables.codespaces.stopping-a-codespace %} 자세한 내용은 "[codespace 중지 및 시작"을 참조하세요](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace). + +## Codespace 삭제 + +특정 작업에 대한 Codespace를 만들고 변경 내용을 원격 분기에 푸시한 후 Codespace를 안전하게 삭제할 수 있습니다. + +푸시되지 않은 git 커밋이 있는 Codespace를 삭제하려고 하면 편집기에서 원격 분기에 푸시되지 않은 변경 내용이 있음을 알립니다. 원하는 변경 내용을 푸시한 다음, Codespace를 삭제하거나, Codespace와 커밋되지 않은 변경 내용을 계속 삭제할 수 있습니다. 새 Codespace를 만들지 않고 코드를 새 분기로 내보낼 수도 있습니다. 자세한 내용은 “[분기로 변경 내용 내보내기](/codespaces/troubleshooting/exporting-changes-to-a-branch)”를 참조하세요. + +지정된 기간 동안 중지되고 비활성 상태로 유지된 Codespace는 자동으로 삭제됩니다. 기본적으로 비활성 codespace는 30일 후에 삭제되지만 codespace 보존 기간을 사용자 지정할 수 있습니다. 자세한 내용은 “[내 Codespace의 자동 삭제 구성](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)”을 참조하세요. + +codespace를 만드는 경우 활성 상태인지 중지되었는지에 관계없이 삭제될 때까지 스토리지 요금이 계속 발생합니다. 자세한 내용은 “[{% data variables.product.prodname_github_codespaces %} 청구 정보](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)”를 참조하세요. codespace를 삭제해도 매월 청구 주기마다 누적되는 {% data variables.product.prodname_github_codespaces %}에 대한 현재 청구 가능 금액이 줄어들지 않습니다. 자세한 내용은 “[{% data variables.product.prodname_github_codespaces %} 사용량 보기](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)”를 참조하세요. + +Codespace 삭제에 대한 자세한 내용은 “[Codespace 삭제](/codespaces/developing-in-codespaces/deleting-a-codespace)”를 참조하세요. + +## {% data variables.product.prodname_github_codespaces %}을(를) 사용하는 동안 연결 끊기 + +{% data variables.product.prodname_github_codespaces %}은(는) 클라우드 기반 개발 환경이며 인터넷에 연결해야 합니다. Codespace에서 작업하는 동안 인터넷에 대한 연결이 끊어지면 Codespace에 액세스할 수 없습니다. 그러나 커밋되지 않은 변경 내용은 저장됩니다. 인터넷에 다시 연결하게 되면 Codespace가 남아 있는 상태와 정확히 동일한 상태로 Codespace에 연결할 수 있습니다. 인터넷 연결이 불안정한 경우 변경 내용을 자주 커밋하고 푸시해야 합니다. + +오프라인으로 작업하는 경우가 많다는 것을 알고 있는 경우 {% data variables.product.prodname_vscode_shortname %}에 대한 ["개발 컨테이너" 확장](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)과 함께 파일을 사용하여 `devcontainer.json` 리포지토리에 대한 로컬 개발 컨테이너를 빌드하고 연결할 수 있습니다. 자세한 내용은 {% data variables.product.prodname_vscode %} 설명서의 [컨테이너 내 개발](https://code.visualstudio.com/docs/remote/containers)을 참조하세요. diff --git a/translations/ko-KR/content/codespaces/index.md b/translations/ko-KR/content/codespaces/index.md index 643df17daaab..fd23eda3b9dc 100644 --- a/translations/ko-KR/content/codespaces/index.md +++ b/translations/ko-KR/content/codespaces/index.md @@ -53,11 +53,11 @@ children: - /troubleshooting - /the-githubdev-web-based-editor - /guides -ms.openlocfilehash: 62723c1d4bf684e67420149c96586a91e7583031 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 242931386711938cb1eb5e9b84ad66a581ecb1eb +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160436' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188306' --- diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md index 47995951b271..fa4363ca339b 100644 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md +++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md @@ -1,5 +1,5 @@ --- -title: codespaces에 대한 기본 이미지 제한 +title: codespace에 대한 기본 이미지 제한 shortTitle: Restrict base image intro: 조직 내에서 만든 새 codespace에 사용할 수 있는 기본 이미지를 지정할 수 있습니다. permissions: 'To manage image constraints for an organization''s codespaces, you must be an owner of the organization.' @@ -9,26 +9,26 @@ versions: type: how_to topics: - Codespaces -ms.openlocfilehash: 1da438a680dd3e60c1deeec46a98fbcf48f84e5b -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: f17bb20aa919ca94cd13e14a6f770cea23042b2b +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158999' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188282' --- ## 개요 codespace를 만들면 원격 가상 머신에 Docker 컨테이너가 자동으로 만들어집니다. Docker 컨테이너는 Docker 이미지에서 만들어집니다. 이미지는 사실상 Docker 컨테이너에 대한 템플릿이며 codespace에서 제공하는 결과 환경의 여러 측면을 결정합니다. -리포지토리에 대한 개발 컨테이너 구성에 지정하여 codespaces에 사용할 이미지를 선택할 수 있습니다. 예를 들어 파일의 `image` 속성을 `devcontainer.json` 사용하여 이 작업을 수행할 수 있습니다. +리포지토리에 대한 개발 컨테이너 구성에 지정하여 codespace에 사용할 이미지를 선택할 수 있습니다. 예를 들어 파일의 `image` `devcontainer.json` 속성을 사용하여 이 작업을 수행할 수 있습니다. ```json{:copy} "image": "mcr.microsoft.com/vscode/devcontainers/javascript-node:18", ``` -자세한 내용은 containers.dev [개발 컨테이너 사양](https://containers.dev/implementors/json_reference/) 을 참조하세요. +자세한 내용은 containers.dev [개발 컨테이너 사양을](https://containers.dev/implementors/json_reference/) 참조하세요. -리포지토리에 대한 개발 컨테이너 구성에서 이미지를 지정하지 않으면 기본 이미지가 사용됩니다. 기본 이미지에는 널리 사용되는 언어 및 일반적으로 사용되는 도구에 대한 여러 런타임 버전이 포함되어 있습니다. 자세한 내용은 “[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration)”를 참조하세요. +리포지토리에 대한 개발 컨테이너 구성에서 이미지를 지정하지 않으면 기본 이미지가 사용됩니다. 기본 이미지에는 인기 있는 언어 및 일반적으로 사용되는 도구에 대한 여러 런타임 버전이 포함되어 있습니다. 자세한 내용은 “[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration)”를 참조하세요. 조직 소유자는 조직 내에서 만든 codespace에 사용할 수 있는 이미지를 제한하는 정책을 추가할 수 있습니다. @@ -39,16 +39,16 @@ codespace를 만들면 원격 가상 머신에 Docker 컨테이너가 자동으 {% note %} **참고**: -* 기본 이미지 정책은 codespace를 만들 때만 적용됩니다. 컨테이너를 다시 빌드할 때는 현재 적용되지 않습니다. 이는 향후 릴리스에서 변경될 예정입니다. 자세한 내용은 "[codespace 수명 주기"를 참조하세요](/codespaces/developing-in-codespaces/the-codespace-lifecycle#rebuilding-a-codespace). -* 기본 이미지 정책은 기본 이미지 또는 컨테이너를 다시 빌드할 수 없는 개발 컨테이너 구성에 오류가 발생하는 경우 codespace를 복구하는 데 사용되는 이미지에 적용되지 않습니다. +* 기본 이미지 정책은 codespace를 만들 때만 적용됩니다. 컨테이너를 다시 빌드할 때는 현재 적용되지 않습니다. 이는 향후 릴리스에서 변경될 예정입니다. 자세한 내용은 "[codespace 수명 주기"를 참조하세요](/codespaces/getting-started/the-codespace-lifecycle#rebuilding-a-codespace). +* 기본 이미지 정책은 기본 이미지 또는 컨테이너가 다시 빌드되지 않도록 하는 개발 컨테이너 구성에 오류가 도입된 경우 codespace를 복구하는 데 사용되는 이미지에 적용되지 않습니다. {% endnote %} ### 조직 전체 및 리포지토리별 정책 설정 -정책을 만들 때 조직의 모든 리포지토리에 적용할지 또는 지정된 리포지토리에만 적용할지 선택합니다. 조직 전체 정책을 설정하는 경우 개별 리포지토리에 대해 설정한 정책은 조직 수준에서 설정된 제한에 속해야 합니다. 정책을 추가하면 이미지를 더 많이 선택할 수 있습니다. +정책을 만들 때 조직의 모든 리포지토리에 적용할지 또는 지정된 리포지토리에만 적용할지 선택합니다. 조직 전체 정책을 설정하는 경우 개별 리포지토리에 대해 설정한 정책은 조직 수준에서 설정된 제한에 속해야 합니다. 정책을 추가하면 이미지를 더 많이 선택할 수 있으며, 그다지 제한적이 아닙니다. -예를 들어 기본 이미지를 지정된 10개 이미지로 제한하는 조직 전체 정책을 만들 수 있습니다. 그런 다음, 리포지토리 A에 대한 정책을 설정하여 이미지를 조직 수준에서 지정된 두 이미지의 하위 집합으로 제한할 수 있습니다. 리포지토리 A에 대한 추가 이미지를 지정해도 해당 이미지는 조직 수준 정책에 지정되지 않으므로 영향을 주지 않습니다. 조직 전체 정책을 추가하는 경우 조직의 모든 리포지토리에 사용할 수 있는 가장 큰 이미지 선택으로 설정해야 합니다. 그런 다음, 리포지토리별 정책을 추가하여 선택을 추가로 제한할 수 있습니다. +예를 들어 기본 이미지를 지정된 10개 이미지로 제한하는 조직 전체 정책을 만들 수 있습니다. 그런 다음, 리포지토리 A에 대한 정책을 설정하여 이미지를 조직 수준에서 지정된 두 이미지의 하위 집합으로 제한할 수 있습니다. 리포지토리 A에 대한 추가 이미지를 지정해도 이러한 이미지는 조직 수준 정책에 지정되지 않으므로 아무런 효과가 없습니다. 조직 전체 정책을 추가하는 경우 조직의 모든 리포지토리에 사용할 수 있는 가장 큰 이미지 선택으로 설정해야 합니다. 그런 다음, 리포지토리별 정책을 추가하여 선택을 추가로 제한할 수 있습니다. {% data reusables.codespaces.codespaces-org-policies-note %} @@ -80,7 +80,7 @@ codespace를 만들면 원격 가상 머신에 Docker 컨테이너가 자동으 * “[머신 유형에 대한 액세스 제한](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)” * "[전달된 포트의 표시 유형 제한](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" * "[유휴 시간 제한 기간 제한](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)" - * "[codespaces에 대한 보존 기간 제한](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)" + * "[codespace에 대한 보존 기간 제한](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)" 1. 정책에 제약 조건 추가를 완료한 후 **저장** 을 클릭합니다. 정책은 누구나 조직에 청구할 수 있는 새 codespace를 만들려고 할 때 적용됩니다. 기본 이미지 제약 조건은 활성 또는 중지된 기존 codespace에 영향을 주지 않습니다. @@ -89,7 +89,7 @@ codespace를 만들면 원격 가상 머신에 Docker 컨테이너가 자동으 기존 정책을 편집할 수 있습니다. 예를 들어 정책에서 제약 조건을 추가하거나 제거할 수 있습니다. -1. “Codespace 정책” 페이지를 표시합니다. 자세한 내용은 "[허용되는 이미지를 정의하는 정책 추가](#adding-a-policy-to-define-the-allowed-images)"를 참조하세요. +1. “Codespace 정책” 페이지를 표시합니다. 자세한 내용은 "[허용되는 이미지를 정의하는 정책 추가"를 참조하세요](#adding-a-policy-to-define-the-allowed-images). 1. 편집할 정책의 이름을 클릭합니다. 1. "기본 이미지" 제약 조건 옆에 있는 연필 아이콘({% octicon "pencil" aria-label="The edit icon" %})을 클릭합니다. 1. 이미지 URL을 추가하거나 제거합니다. @@ -97,7 +97,7 @@ codespace를 만들면 원격 가상 머신에 Docker 컨테이너가 자동으 ## 정책 삭제 -1. “Codespace 정책” 페이지를 표시합니다. 자세한 내용은 "[허용되는 이미지를 정의하는 정책 추가](#adding-a-policy-to-define-the-allowed-images)"를 참조하세요. +1. “Codespace 정책” 페이지를 표시합니다. 자세한 내용은 "[허용되는 이미지를 정의하는 정책 추가"를 참조하세요](#adding-a-policy-to-define-the-allowed-images). 1. 삭제하려는 정책 오른쪽에 있는 삭제 단추를 클릭합니다. ![정책에 대한 삭제 단추의 스크린샷](/assets/images/help/codespaces/policy-delete.png) diff --git a/translations/ko-KR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/ko-KR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md index ead0b66aa047..44aa07505cf3 100644 --- a/translations/ko-KR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md +++ b/translations/ko-KR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: 리포지토리에 대한 끌어오기 요청 템플릿 만들기 -intro: 리포지토리에 끌어오기 요청 템플릿을 추가하면 프로젝트 참가자는 끌어오기 요청 본문에 템플릿의 콘텐츠를 자동으로 볼 수 있습니다. +title: Creating a pull request template for your repository +intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.' redirect_from: - /articles/creating-a-pull-request-template-for-your-repository - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository @@ -12,44 +12,41 @@ versions: topics: - Community shortTitle: Create a PR template -ms.openlocfilehash: 2a85c88944f1d46209429846bba1e7a3c930968e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ko-KR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145090185' --- -자세한 내용은 “[문제 및 끌어오기 요청 템플릿 정보](/articles/about-issue-and-pull-request-templates)”를 참조하세요. -여러 끌어오기 요청 템플릿을 포함하도록 지원되는 폴더에 *PULL_REQUEST_TEMPLATE/* 하위 디렉터리를 만들고 쿼리 매개 변수를 사용하여 `template` 끌어오기 요청 본문을 채울 템플릿을 지정할 수 있습니다. 자세한 내용은 “[쿼리 매개 변수를 사용하여 끌어오기 요청 만들기](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)”를 참조하세요. +For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." + +You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." {% ifversion fpt or ghes or ghec %} -조직{% ifversion fpt or ghes or ghec %} 또는 개인 계정{% endif %}에 대한 기본 끌어오기 요청 템플릿을 만들 수 있습니다. 자세한 내용은 “[기본 커뮤니티 상태 파일 만들기](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)”를 참조하세요. +You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} -## 끌어오기 요청 템플릿 추가 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. 파일 이름 필드에서 다음을 수행합니다. - - 끌어오기 요청 템플릿을 리포지토리의 루트 디렉터리에 표시하려면 끌어오기 요청 템플릿의 이름을 `pull_request_template.md`로 지정합니다. - ![루트 디렉터리의 새 끌어오기 요청 템플릿 이름](/assets/images/help/repository/pr-template-file-name.png) - - 끌어오기 요청 템플릿을 리포지토리의 `docs` 디렉터리에 표시하려면 끌어오기 요청 템플릿의 이름을 `docs/pull_request_template.md`로 지정합니다. - ![docs 디렉터리의 새 끌어오기 요청 템플릿](/assets/images/help/repository/pr-template-file-name-docs.png) - - 파일을 숨겨진 디렉터리에 저장하려면 끌어오기 요청 템플릿의 이름을 `.github/pull_request_template.md`로 지정합니다. - ![숨겨진 디렉터리의 새 끌어오기 요청 템플릿](/assets/images/help/repository/pr-template-hidden-directory.png) - - 여러 끌어오기 요청 템플릿을 만들고 쿼리 매개 변수를 사용하여 `template` 끌어오기 요청 본문을 채울 템플릿을 지정하려면 *.github/PULL_REQUEST_TEMPLATE/* 를 입력한 다음 끌어오기 요청 템플릿의 이름을 입력합니다. 예: `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. 루트 또는 `docs/` 디렉터리 내의 `PULL_REQUEST_TEMPLATE` 하위 디렉터리에 여러 끌어오기 요청 템플릿을 저장할 수도 있습니다. 자세한 내용은 “[쿼리 매개 변수를 사용하여 문제 및 끌어오기 요청에 대한 자동화 정보](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)”를 참조하세요. - ![끌어오기](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) -4. 새 파일의 본문에 끌어오기 요청 템플릿을 추가합니다. 여기에는 다음이 포함될 수 있습니다. - - 리포지토리의 [관련 문제에 대한 참조](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)입니다. - - 끌어오기 요청에 제안된 변경 내용에 대한 설명입니다. - - 제안된 변경 사항을 검토할 책임이 있는 사람 또는 팀의 [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)입니다. -{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} 템플릿은 리포지토리의 기본 분기에 병합되면 협력자가 사용할 수 있습니다. +## Adding a pull request template + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field: + - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`. + ![New pull request template name in root directory](/assets/images/help/repository/pr-template-file-name.png) + - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`. + ![New pull request template in docs directory](/assets/images/help/repository/pr-template-file-name-docs.png) + - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`. + ![New pull request template in hidden directory](/assets/images/help/repository/pr-template-hidden-directory.png) + - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." + ![New multiple pull request template in hidden directory](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) +4. In the body of the new file, add your pull request template. This could include: + - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository. + - A description of the changes proposed in the pull request. + - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch. {% data reusables.files.propose_new_file %} -## 추가 참고 자료 +## Further reading -- “[문제 및 끌어오기 요청 템플릿 정보](/articles/about-issue-and-pull-request-templates)” -- “[쿼리 매개 변수를 사용하여 문제 및 끌어오기 요청에 대한 자동화 정보](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)” -- “[끌어오기 요청 만들기](/articles/creating-a-pull-request)” +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating a pull request](/articles/creating-a-pull-request)" diff --git a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md new file mode 100644 index 000000000000..a9404e2acdb8 --- /dev/null +++ b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md @@ -0,0 +1,33 @@ +--- +title: GitHub Desktop에서 리포지토리의 원격 URL 변경 +intro: '{% data variables.product.prodname_desktop %}에서 작업 중인 리포지토리의 원격 URL을 변경할 수 있습니다. 리포지토리의 이름이 변경되었거나 리포지토리를 소유하는 사용자 이름 또는 조직이 변경된 경우 이 작업을 수행할 수 있습니다.' +redirect_from: + - /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop +versions: + fpt: '*' +shortTitle: Change the remote URL for a repository +ms.openlocfilehash: e37c4878c13a9de95520f8e9c1edc9bf6416d46a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ko-KR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188365' +--- +{% mac %} + +{% data reusables.desktop.mac-repository-settings-menu %} +2. **원격** 을 클릭하고 **기본 원격 리포지토리** 아래에 원하는 URL을 입력합니다. +![기본 원격 리포지토리 필드](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-repository-settings-menu %} +2. **원격** 을 클릭하고 **기본 원격 리포지토리** 아래에 원하는 URL을 입력합니다. +![기본 원격 리포지토리 필드](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endwindows %} diff --git a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index 0399346c29d4..c45cc0c3f732 100644 --- a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -12,11 +12,11 @@ children: - /configuring-notifications-in-github-desktop - /changing-the-remote-url-for-a-repository-from-github-desktop shortTitle: Work with your remote repo -ms.openlocfilehash: 60c2f41546ff085ea8f8d56142da6a3c7a81ebae -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT +ms.openlocfilehash: f7e9f1ab5f73aaad29208db01c62815d7a20ba03 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145117476' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188366' --- diff --git a/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md b/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md new file mode 100644 index 000000000000..135ee58a57aa --- /dev/null +++ b/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md @@ -0,0 +1,43 @@ +--- +title: 포크에 대한 원격 리포지토리 구성 +intro: '원본 리포지토리와 [포크에서 변경한 내용을 동기화](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)하려면 Git의 업스트림 리포지토리를 가리키는 원격을 구성해야 합니다. 이렇게 하면 원본 리포지토리의 변경 내용을 포크와 동기화할 수도 있습니다.' +redirect_from: + - /github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /articles/configuring-a-remote-for-a-fork + - /github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Pull requests +shortTitle: Configure a remote repository +ms.openlocfilehash: 495d3c825356fd69c9130f8a122aa7a8702ff317 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ko-KR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188377' +--- +{% data reusables.command_line.open_the_multi_os_terminal %} +2. 포크에 대해 현재 구성된 원격 리포지토리를 나열합니다. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + ``` +3. 포크와 동기화할 새 원격 *업스트림* 리포지토리를 지정합니다. + ```shell + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git + ``` +4. 포크에 대해 지정한 새 업스트림 리포지토리를 확인합니다. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + ``` diff --git a/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md index 8019e4ff59b4..283e84f15639 100644 --- a/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md +++ b/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md @@ -18,11 +18,11 @@ children: - /syncing-a-fork - /allowing-changes-to-a-pull-request-branch-created-from-a-fork - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility -ms.openlocfilehash: 79d8346fdd63366e5987def43164932503104332 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT +ms.openlocfilehash: 0133f7759cb9040a5acb97a7b08c312a55079bda +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146683663' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188372' --- diff --git a/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index c9b479247ebf..1075383a4abf 100644 --- a/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -1,6 +1,6 @@ --- -title: Syncing a fork -intro: Sync a fork of a repository to keep it up-to-date with the upstream repository. +title: 포크 동기화 +intro: 리포지토리의 포크를 동기화하여 업스트림 리포지토리를 최신 상태로 유지합니다. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork - /articles/syncing-a-fork @@ -19,44 +19,48 @@ versions: topics: - Pull requests permissions: People with write access for a forked repository can sync the fork to the upstream repository. +ms.openlocfilehash: 85b149e26cb65a428d7e9b66aea99d6b62430ae0 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ko-KR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188330' --- - -## Syncing a fork branch from the web UI +## 웹 UI에서 포크 분기 동기화 {% ifversion syncing-fork-web-ui %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Sync fork** dropdown. - !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) -3. Review the details about the commits from the upstream repository, then click **Update branch**. - ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) -{% else %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Fetch upstream** dropdown. - !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. - !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} +1. {% data variables.product.product_name %}에서 업스트림 리포지토리와 동기화하려는 포크된 리포지토리의 기본 페이지로 이동합니다. +2. **포크 동기화** 드롭다운을 선택합니다. + ![“포크 동기화” 드롭다운이 강조됨](/assets/images/help/repository/sync-fork-dropdown.png) +3. 업스트림 리포지토리에서의 커밋에 대한 세부 정보를 검토한 다음 **분기 업데이트** 를 클릭합니다. + ![“분기 업데이트” 단추가 강조된 포크 동기화 모달](/assets/images/help/repository/update-branch-button.png) {% else %} +1. {% data variables.product.product_name %}에서 업스트림 리포지토리와 동기화하려는 포크된 리포지토리의 기본 페이지로 이동합니다. +2. **업스트림 가져오기** 드롭다운을 선택합니다. + ![“업스트림 가져오기” 드롭다운](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. 업스트림 리포지토리에서의 커밋에 대한 세부 정보를 검토한 다음 **가져오기 및 병합** 을 클릭합니다. + ![“가져오기 및 병합” 단추](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} -If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. +업스트림 리포지토리의 변경으로 인해 충돌이 발생하는 경우 {% data variables.product.company_short %}는 충돌을 해결하기 위한 끌어오기 요청을 만들라는 메시지를 표시합니다. -## Syncing a fork branch with the {% data variables.product.prodname_cli %} +## 포크 분기를 {% data variables.product.prodname_cli %}와 동기화 -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %} {% data variables.product.prodname_cli %}에 대한 자세한 내용은 “[{% data variables.product.prodname_cli %} 정보](/github-cli/github-cli/about-github-cli)”를 참조하세요. -To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments. +부모에서 원격 포크를 업데이트하려면 `gh repo sync -b BRANCHNAME` 하위 명령을 사용하고 포크 및 분기 이름을 인수로 제공합니다. ```shell $ gh repo sync owner/cli-fork -b BRANCH_NAME ``` -If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. +업스트림 리포지토리의 변경으로 인해 충돌이 발생하는 경우 {% data variables.product.prodname_cli %}는 동기화할 수 없습니다. `-force` 플래그를 설정하여 대상 분기를 덮어쓸 수 있습니다. -## Syncing a fork branch from the command line +## 명령줄에서 포크 분기 동기화 -Before you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git. For more information, see "[Configuring a remote repository for a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)." +포크를 업스트림 리포지토리와 동기화하려면 먼저 Git에서 업스트림 리포지토리를 가리키는 원격을 구성해야 합니다. 자세한 내용은 "[포크에 대한 원격 리포지토리 구성"을 참조하세요](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork). {% data reusables.command_line.open_the_multi_os_terminal %} -2. Change the current working directory to your local project. -3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. +2. 현재 작업 디렉터리를 로컬 프로젝트로 변경합니다. +3. 업스트림 리포지토리에서 분기 및 해당 커밋을 가져옵니다. `BRANCHNAME`에 대한 커밋은 로컬 분기 `upstream/BRANCHNAME`에 저장됩니다. ```shell $ git fetch upstream @@ -68,14 +72,14 @@ Before you can sync your fork with an upstream repository, you must configure a > * [new branch] main -> upstream/main ``` -4. Check out your fork's local default branch - in this case, we use `main`. +4. 포크의 로컬 기본 분기를 확인합니다. 이 경우 `main`을 사용합니다. ```shell $ git checkout main > Switched to branch 'main' ``` -5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. +5. 업스트림 기본 분기(이 경우 `upstream/main`)의 변경 내용을 로컬 기본 분기에 병합합니다. 이렇게 하면 로컬 변경 내용이 손실되지 않고 포크의 기본 분기가 업스트림 리포지토리와 동기화됩니다. ```shell $ git merge upstream/main @@ -88,7 +92,7 @@ Before you can sync your fork with an upstream repository, you must configure a > create mode 100644 README.md ``` - If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation. + 로컬 분기에 고유한 커밋이 없는 경우 Git에서 빠른 전달을 수행합니다. 자세한 내용은 Git 설명서의 [기본 분기 및 병합](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging)을 참조하세요. ```shell $ git merge upstream/main > Updating 34e91da..16c56ad @@ -96,10 +100,10 @@ Before you can sync your fork with an upstream repository, you must configure a > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) ``` - If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)." + 로컬 분기에 고유한 커밋이 있는 경우 충돌을 해결해야 할 수 있습니다. 자세한 내용은 “[병합 충돌 해결](/github/collaborating-with-pull-requests/addressing-merge-conflicts)”을 참조하세요. {% tip %} -**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). +**팁**: 포크를 동기화하면 리포지토리의 로컬 복사본만 업데이트됩니다. {% data variables.location.product_location %}에서 포크를 업데이트하려면 [변경 내용을 푸시](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)해야 합니다. {% endtip %} diff --git a/translations/ko-KR/content/rest/overview/libraries.md b/translations/ko-KR/content/rest/overview/libraries.md index 538939f32d74..5f33126bebfe 100644 --- a/translations/ko-KR/content/rest/overview/libraries.md +++ b/translations/ko-KR/content/rest/overview/libraries.md @@ -11,20 +11,19 @@ versions: ghec: '*' topics: - API -ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c -ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa +ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58 +ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 11/21/2022 -ms.locfileid: '148179738' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148190063' --- -![더 건담캣](/assets/images/gundamcat.png) +![건담캣](/assets/images/gundamcat.png) ## 다양한 버전으로 제공되는 Octokit 공식 Octokit 라이브러리를 사용하거나 사용 가능한 타사 라이브러리 중 하나를 선택합니다. -- **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 @@ ms.locfileid: '148179738' |**github-flask**|[github-flask(공식 웹 사이트)](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/ko-KR/content/rest/overview/resources-in-the-rest-api.md b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md index 26f5282190e5..9a1a2900eae7 100644 --- a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md @@ -292,10 +292,10 @@ gem: >> tmpl.expand => "/notifications" - >> tmpl.expand :all => 1 + >> tmpl.expand all: 1 => "/notifications?all=1" - >> tmpl.expand :all => 1, :participating => 1 + >> tmpl.expand all: 1, participating: 1 => "/notifications?all=1&participating=1" [rfc]: https://datatracker.ietf.org/doc/html/rfc6570 diff --git a/translations/ko-KR/data/reusables/codespaces/stopping-a-codespace.md b/translations/ko-KR/data/reusables/codespaces/stopping-a-codespace.md index 36c5992d7ee0..21ba9b48e35b 100644 --- a/translations/ko-KR/data/reusables/codespaces/stopping-a-codespace.md +++ b/translations/ko-KR/data/reusables/codespaces/stopping-a-codespace.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: 4bdcc6ff93e7671d4dc368fc44784c963f549aae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 1eac21c20c1be77fe00ea676714a835fdb2e0de7 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ko-KR -ms.lasthandoff: 11/09/2022 -ms.locfileid: "148159047" +ms.lasthandoff: 12/01/2022 +ms.locfileid: "148189890" --- -Codespace를 언제든 중지할 수 있습니다. Codespace를 중지하면 실행 중인 모든 프로세스가 중지되고 터미널 기록이 지워집니다. Codespace에서 저장된 변경 내용은 다음에 시작할 때 계속 사용할 수 있습니다. Codespace를 명시적으로 중지하지 않으면 비활성에서 시간이 초과될 때까지 계속 실행됩니다. 자세한 내용은 "[codespace 수명 주기"를 참조하세요](/codespaces/developing-in-codespaces/the-codespace-lifecycle#timeouts-for-github-codespaces). +Codespace를 언제든 중지할 수 있습니다. Codespace를 중지하면 실행 중인 모든 프로세스가 중지되고 터미널 기록이 지워집니다. Codespace에서 저장된 변경 내용은 다음에 시작할 때 계속 사용할 수 있습니다. Codespace를 명시적으로 중지하지 않으면 비활성에서 시간이 초과될 때까지 계속 실행됩니다. 자세한 내용은 "[codespace 수명 주기"를 참조하세요](/codespaces/getting-started/the-codespace-lifecycle#timeouts-for-github-codespaces). -codespace를 실행하는 경우에만 CPU 요금이 발생합니다. 중지된 codespace는 스토리지 비용만 발생합니다. +codespace를 실행하는 경우에만 CPU 요금이 발생합니다. 중지된 codespace에는 스토리지 비용만 발생합니다. Codespace를 중지하고 다시 시작하여 변경 내용을 적용할 수 있습니다. 예를 들어 Codespace에 사용되는 컴퓨터 유형을 변경하는 경우 변경 내용이 적용되려면 이를 중지하고 다시 시작해야 합니다. 또한 Codespace를 중지하고 오류 또는 예기치 않은 오류가 발생하는 경우 다시 시작하거나 삭제하도록 선택할 수 있습니다. diff --git a/translations/log/msft-fr-resets.csv b/translations/log/msft-fr-resets.csv index 169512e6f883..c8fbdc7a5f9d 100644 --- a/translations/log/msft-fr-resets.csv +++ b/translations/log/msft-fr-resets.csv @@ -475,7 +475,6 @@ translations/fr-FR/content/actions/learn-github-actions/expressions.md,rendering translations/fr-FR/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags translations/fr-FR/content/actions/learn-github-actions/understanding-github-actions.md,rendering error translations/fr-FR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error -translations/fr-FR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,broken liquid tags translations/fr-FR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags translations/fr-FR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error translations/fr-FR/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error @@ -577,7 +576,6 @@ translations/fr-FR/content/admin/identity-and-access-management/using-enterprise translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,rendering error translations/fr-FR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,rendering error -translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md,broken liquid tags translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,rendering error translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise.md,rendering error translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags @@ -589,7 +587,6 @@ translations/fr-FR/content/admin/installation/setting-up-a-github-enterprise-ser translations/fr-FR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md,rendering error translations/fr-FR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error translations/fr-FR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error -translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md,rendering error translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error @@ -637,10 +634,10 @@ translations/fr-FR/content/authentication/connecting-to-github-with-ssh/generati translations/fr-FR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,rendering error translations/fr-FR/content/authentication/index.md,rendering error translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error -translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,rendering error 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 @@ -756,27 +753,20 @@ translations/fr-FR/content/codespaces/customizing-your-codespace/changing-the-ma translations/fr-FR/content/codespaces/customizing-your-codespace/renaming-a-codespace.md,broken liquid tags translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error -translations/fr-FR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,broken liquid tags translations/fr-FR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,broken liquid tags -translations/fr-FR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md,broken liquid tags -translations/fr-FR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,broken liquid tags translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,broken liquid tags translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error translations/fr-FR/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md,broken liquid tags translations/fr-FR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error -translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags translations/fr-FR/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md,broken liquid tags translations/fr-FR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error translations/fr-FR/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error translations/fr-FR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error translations/fr-FR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/fr-FR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error -translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags -translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags -translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags -translations/fr-FR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags +translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error translations/fr-FR/content/copilot/quickstart.md,broken liquid tags translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags @@ -973,7 +963,6 @@ translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/propos translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error -translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error @@ -1124,7 +1113,6 @@ translations/fr-FR/data/reusables/advanced-security/secret-scanning-add-custom-p translations/fr-FR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error translations/fr-FR/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags translations/fr-FR/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags -translations/fr-FR/data/reusables/audit_log/audit-log-action-categories.md,broken liquid tags translations/fr-FR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error translations/fr-FR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error translations/fr-FR/data/reusables/audit_log/retention-periods.md,rendering error @@ -1207,7 +1195,6 @@ translations/fr-FR/data/reusables/getting-started/enterprise-advanced-security.m translations/fr-FR/data/reusables/getting-started/managing-enterprise-members.md,rendering error translations/fr-FR/data/reusables/git/git-push.md,rendering error translations/fr-FR/data/reusables/git/provide-credentials.md,rendering error -translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md,broken liquid tags translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md,rendering error translations/fr-FR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,rendering error translations/fr-FR/data/reusables/large_files/storage_assets_location.md,broken liquid tags @@ -1220,7 +1207,6 @@ translations/fr-FR/data/reusables/organizations/github-apps-settings-sidebar.md, translations/fr-FR/data/reusables/organizations/member-privileges.md,rendering error translations/fr-FR/data/reusables/organizations/navigate-to-org.md,rendering error translations/fr-FR/data/reusables/organizations/repository-defaults.md,rendering error -translations/fr-FR/data/reusables/organizations/require-ssh-cert.md,broken liquid tags translations/fr-FR/data/reusables/organizations/security-and-analysis.md,rendering error translations/fr-FR/data/reusables/organizations/security.md,rendering error translations/fr-FR/data/reusables/organizations/settings-sidebar-actions-general.md,rendering error diff --git a/translations/log/msft-ko-resets.csv b/translations/log/msft-ko-resets.csv index ccbc9ad55af8..7f425911e232 100644 --- a/translations/log/msft-ko-resets.csv +++ b/translations/log/msft-ko-resets.csv @@ -673,7 +673,6 @@ translations/ko-KR/content/authentication/troubleshooting-ssh/error-agent-admitt translations/ko-KR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error translations/ko-KR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error translations/ko-KR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,rendering error -translations/ko-KR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error translations/ko-KR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error translations/ko-KR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error @@ -766,8 +765,9 @@ translations/ko-KR/content/code-security/supply-chain-security/understanding-you translations/ko-KR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error translations/ko-KR/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags +translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error +translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error translations/ko-KR/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md,rendering error -translations/ko-KR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md,rendering error translations/ko-KR/content/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide.md,rendering error translations/ko-KR/content/codespaces/getting-started/deep-dive.md,rendering error translations/ko-KR/content/codespaces/getting-started/quickstart.md,rendering error @@ -785,6 +785,7 @@ translations/ko-KR/content/communities/documenting-your-project-with-wikis/about translations/ko-KR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error translations/ko-KR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error +translations/ko-KR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error translations/ko-KR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,rendering error translations/ko-KR/content/copilot/quickstart.md,broken liquid tags translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error @@ -999,7 +1000,6 @@ translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/propos translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error -translations/ko-KR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error translations/ko-KR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error translations/ko-KR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error translations/ko-KR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error diff --git a/translations/log/msft-ru-resets.csv b/translations/log/msft-ru-resets.csv index 4ddc0819a100..3a01fee1110d 100644 --- a/translations/log/msft-ru-resets.csv +++ b/translations/log/msft-ru-resets.csv @@ -733,7 +733,6 @@ translations/ru-RU/content/authentication/troubleshooting-ssh/error-agent-admitt translations/ru-RU/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error translations/ru-RU/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error translations/ru-RU/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,rendering error -translations/ru-RU/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error translations/ru-RU/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error translations/ru-RU/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error @@ -820,6 +819,7 @@ translations/ru-RU/content/code-security/supply-chain-security/understanding-you translations/ru-RU/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,rendering error translations/ru-RU/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error +translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error translations/ru-RU/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,rendering error translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags translations/ru-RU/content/codespaces/overview.md,rendering error @@ -829,6 +829,7 @@ translations/ru-RU/content/communities/documenting-your-project-with-wikis/about translations/ru-RU/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error translations/ru-RU/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error +translations/ru-RU/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error translations/ru-RU/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,rendering error translations/ru-RU/content/copilot/quickstart.md,broken liquid tags translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error @@ -1050,7 +1051,6 @@ translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/propos translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error -translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error translations/ru-RU/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error translations/ru-RU/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error translations/ru-RU/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error diff --git a/translations/ru-RU/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/ru-RU/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index a1a74dd1f480..a7060df4d03e 100644 --- a/translations/ru-RU/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/ru-RU/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -31,6 +31,9 @@ Before you can enable and configure {% data variables.product.prodname_registry {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} 1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. + + - You must create a storage container prior to setting the container name and connection string. + ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% note %} diff --git a/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index 5b18d8be7a7d..aa3e4da0160c 100644 --- a/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -14,17 +14,26 @@ topics: - Identity - Access management shortTitle: SSH key fingerprints -ms.openlocfilehash: b17285e62daf1f71c603e004a5bb00b786e3038a -ms.sourcegitcommit: 605b619588c51336f3ffe9d13c68503ae45cbfc6 +ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed +ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 10/07/2022 -ms.locfileid: '148013841' +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190333' --- Отпечатки открытого ключа {% data variables.product.prodname_dotcom %}: - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) +- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA — не рекомендуется) - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA) - `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519) -Дополнительные сведения см. в разделе ["Получение метаданных](/rest/meta#get-github-meta-information)". +Вы можете добавить в файл следующие записи `~.ssh/known_hosts` ключа SSH, чтобы избежать ручной проверки узлов {% data variables.product.prodname_dotcom %}: + +```text +github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl +github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg= +github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ== +``` + +Дополнительные сведения см. в разделе [Получение метаданных {% data variables.product.prodname_dotcom %}](/rest/meta#get-github-meta-information). diff --git a/translations/ru-RU/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/ru-RU/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 92f37fba9d43..b857e9b5c9e8 100644 --- a/translations/ru-RU/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/ru-RU/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: Использование SSH через порт HTTPS +intro: 'Иногда брандмауэры отказываются в полной мере разрешать подключения по протоколу SSH. Если использование [клонирования HTTPS с кэшированием учетных данных](/github/getting-started-with-github/caching-your-github-credentials-in-git) недоступно, можно попытаться выполнить клонирование с помощью SSH-подключения, выполненного через порт HTTPS. Большинство правил брандмауэра должны разрешать этот вариант, но прокси-серверы могут этому помешать.' 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: MT +ms.contentlocale: ru-RU +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190325' --- {% 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. +**Пользователи {% data variables.product.prodname_ghe_server %}** : доступ к {% data variables.product.prodname_ghe_server %} по SSH через порт HTTPS в настоящее время не поддерживается. {% endtip %} -To test if SSH over the HTTPS port is possible, run this SSH command: +Чтобы проверить, возможно ли подключение по протоколу SSH через порт HTTPS, выполните следующую команду 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 %}`. +**Примечание**. Имя узла для порта 443 — , а `ssh.{% data variables.command_line.backticks %}`не `{% data variables.command_line.backticks %}`. -{% endnote %} +{% endnote %} -If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey). +Если она выполнена успешно, все в порядке. В противном случае вам может потребоваться [выполнить руководство по устранению неполадок](/articles/error-permission-denied-publickey). -Now, to clone the repository, you can run the following command: +Теперь, чтобы клонировать репозиторий, можно выполнить следующую команду: ``` $ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git ``` -## Enabling SSH connections over HTTPS +## Включение SSH-подключений по протоколу 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. +Если вы можете подключиться `git@ssh.{% data variables.command_line.backticks %}` по протоколу SSH через порт 443, можно переопределить параметры SSH, чтобы любое подключение к {% data variables.location.product_location %} выполнялось через этот сервер и порт. -To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: +Чтобы настроить это в файле конфигурации SSH, измените файл по пути `~/.ssh/config` и добавьте следующий раздел: ``` 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 %}: +Вы можете проверить, работает ли это, подключившись еще раз к {% data variables.location.product_location %}: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} @@ -61,18 +67,16 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > provide shell access. ``` -## Updating known hosts +## Обновление известных узлов -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. +При первом взаимодействии с GitHub после переключения на порт 443 может отображаться предупреждающее сообщение о том, что узел не найден в `known_hosts`или что он был найден с другим именем. ```ShellSession > The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established. > ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. > This host key is known by the following other names/addresses: > ~/.ssh/known_hosts:32: github.com -> Are you sure you want to continue connecting (yes/no/[fingerprint])? +> 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 more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." +Можно с уверенностью ответить "да" на этот вопрос, если отпечаток SSH соответствует одному из опубликованных отпечатков пальцев GitHub. Список отпечатков пальцев см. в разделе "[Отпечатки ключей SSH Github](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)". diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md index bb6b66291fce..842a20e97185 100644 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md +++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md @@ -1,6 +1,6 @@ --- -title: Создание codespace на основе шаблона -intro: 'Если вы начинаете новый проект, вы можете создать пространство кода из пустого шаблона или выбрать шаблон, специально разработанный для нужного типа работы.' +title: Creating a codespace from a template +intro: If you're starting a new project, you can create a codespace from a blank template or choose a template specially designed for the type of work you want to do. versions: fpt: '*' ghec: '*' @@ -11,95 +11,92 @@ topics: - Developer shortTitle: Create a codespace from a template miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 7c6ffdb4099b5d5d6f37ec5ffa7d73f838b36c76 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 -ms.translationtype: MT -ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159861' --- -## Сведения о шаблонах для {% data variables.product.prodname_github_codespaces %} -Если вы начинаете новый проект, вы можете быстро приступить к разработке, создав codespace на основе шаблона. Вы сможете работать над проектом в облачной среде разработки, сохранять файлы в облаке и публиковать свои работы в новом удаленном репозитории, которым можно поделиться с другими пользователями или клонировать на локальный компьютер. +## About templates for {% data variables.product.prodname_github_codespaces %} + +If you're starting a new project, you can get started with development work quickly by creating a codespace from a template. You'll be able to work on your project in a cloud-based development environment, save your files in the cloud, and publish your work to a new remote repository that you can share with others or clone to your local machine. {% note %} -**Примечание.** Счета за codespace, созданные на основе шаблона, а не из репозитория, всегда выставляются в вашей личной учетной записи. Дополнительные сведения см. в статье [Сведения о выставлении счетов за {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +**Note**: Codespaces created from a template, rather than from a repository, are always billed to your personal account. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." {% endnote %} -Вы можете начать с пустого шаблона, выбрать шаблоны, поддерживаемые {% data variables.product.company_short %} для популярных технологий, таких как React или Jupyter Notebook, или запустить пространство кода из любого репозитория шаблонов в {% data variables.product.prodname_dotcom %}. С пустым шаблоном вы начнете с пустого каталога с доступом к облачным вычислительным ресурсам и средствам, языкам и средам выполнения, которые предустановлены с изображением codespace по умолчанию. С помощью других шаблонов вы получите начальные файлы для технологии, с которой вы работаете, а также, как правило, некоторые дополнительные файлы, такие как файл сведений `.gitignore` , файл и файлы конфигурации контейнера разработки, содержащие некоторые пользовательские конфигурации среды. Дополнительные сведения о контейнерах разработки и образе по умолчанию см. в разделе [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers). +You can start from a blank template, choose from templates maintained by {% data variables.product.company_short %} for popular technologies such as React or Jupyter Notebook, or launch a codespace from any template repository on {% data variables.product.prodname_dotcom %}. With a blank template, you'll start with an empty directory, with access to cloud-based compute resources and the tools, languages, and runtime environments that come preinstalled with the default codespace image. With other templates, you'll get starter files for the technology you're working with, plus typically some extra files such as a README file, a `.gitignore` file, and dev container configuration files containing some custom environment configuration. For more information on dev containers and the default image, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." -Например, если создать codespace на основе шаблона React {% data variables.product.company_short %}, вы будете поступать в рабочую область, содержащую файлы шаблонов для простого приложения, например `index.js`, `app.js`и `package.json`. Вскоре после открытия codespace сервер разработки запустится автоматически, и вы сможете просматривать запущенное приложение на простой вкладке браузера в веб-клиенте {% data variables.product.prodname_vscode_shortname %}. +As an example, if you create a codespace from {% data variables.product.company_short %}'s React template, you'll arrive in a workspace containing template files for a simple application, such as `index.js`, `app.js`, and `package.json`. Shortly after the codespace opens, a development server will start up automatically, and you will be able to view the running application in a simple browser tab within the {% data variables.product.prodname_vscode_shortname %} web client. -![Снимок экрана: шаблон React, выполняющийся в codespace](/assets/images/help/codespaces/react-template.png) +![Screenshot of the React template running in a codespace](/assets/images/help/codespaces/react-template.png) -Файлы и конфигурация, включенные в шаблоны, определяются в репозиториях шаблонов. Репозиторий шаблонов клонируется в codespace при создании codespace. После этого ссылка будет разорвана, и пространство кода не будет связано с удаленным репозиторием, пока вы не опубликуете его. +The files and configuration included in templates are defined in template repositories. The template repository is cloned into your codespace when you create the codespace. After that, the link is severed, and your codespace won't be linked to a remote repository until you publish to one. {% tip %} -**Совет:** Чтобы помочь пользователям приступить к работе с платформой, библиотекой или другим проектом, можно настроить репозиторий шаблонов для использования с {% data variables.product.prodname_github_codespaces %}. Дополнительные сведения см. в разделе [Настройка репозитория шаблонов для {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces). +**Tip:** To help people get started with your framework, library, or other project, you can set up a template repository for use with {% data variables.product.prodname_github_codespaces %}. For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)." {% endtip %} -## Создание codespace на основе шаблона {% data variables.product.company_short %} +## Creating a codespace from a {% data variables.product.company_short %} template -Шаблоны, поддерживаемые {% data variables.product.company_short %}, включая пустой шаблон, доступны на странице "Ваши пространства кода". +Templates maintained by {% data variables.product.company_short %}, including the blank template, are available from the "Your codespaces" page. -{% data reusables.codespaces.your-codespaces-procedure-step %} {% data reusables.codespaces.view-all-templates-step %} -1. При необходимости, чтобы просмотреть репозиторий шаблонов, содержащий файлы для шаблона, щелкните имя шаблона. +{% data reusables.codespaces.your-codespaces-procedure-step %} +{% data reusables.codespaces.view-all-templates-step %} +1. Optionally, to view the template repository containing the files for a template, click the name of the template. - ![Снимок экрана: раздел "Изучение шаблонов быстрого запуска" с выделенным элементом "React"](/assets/images/help/codespaces/react-template-name.png) + ![Screenshot of the "Explore quick start templates" section, with "React" highlighted](/assets/images/help/codespaces/react-template-name.png) -1. Под шаблоном, который вы хотите запустить, щелкните **Использовать этот шаблон**. +1. Under the template you want to launch, click **Use this template**. - ![Снимок экрана: шаблоны быстрого запуска с выделенной кнопкой "Использовать этот шаблон" в шаблоне React](/assets/images/help/codespaces/react-template-button.png) + ![Screenshot of the quick start templates, with the "Use this template" button highlighted under the React template](/assets/images/help/codespaces/react-template-button.png) {% data reusables.codespaces.template-codespaces-default-editor %} -## Создание codespace из репозитория шаблонов +## Creating a codespace from a template repository -Вы можете создать codespace из любого репозитория шаблонов, а затем опубликовать свою работу в новом репозитории, когда будете готовы. Дополнительные сведения о репозиториях шаблонов см. в разделе [Создание репозитория на основе шаблона](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates). +You can create a codespace from any template repository, then publish your work to a new repository when you are ready. For more information on template repositories, see "[Creating a repository from a template](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates)." -{% data reusables.repositories.navigate-to-repo %} {% data reusables.codespaces.open-template-in-codespace-step %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.codespaces.open-template-in-codespace-step %} {% note %} - **Примечание:** Если вы являетесь хранителем репозитория шаблонов и хотите зафиксировать изменения в самом репозитории шаблонов, создайте пространство кода из раскрывающегося списка **{% octicon "code" aria-label="The code icon" %} Code** . Дополнительные сведения см. в разделе [Создание codespace для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository). + **Note:** If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." {% endnote %} {% data reusables.codespaces.template-codespaces-default-editor %} -## Публикация в репозитории на {% data variables.product.product_name %} +## Publishing to a repository on {% data variables.product.product_name %} {% data reusables.codespaces.about-publishing-templates %} -### Публикация из {% data variables.product.prodname_vscode_shortname %} +### Publishing from {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.publishing-template-codespaces %} -При публикации codespace у вас есть доступ к большему набору параметров для настройки интерфейса {% data variables.product.prodname_github_codespaces %}. Например, вы можете: +When a codespace is published, you have access to a greater range of options to customize your {% data variables.product.prodname_github_codespaces %} experience. For example, you can: -- Измените тип компьютера codespace, чтобы убедиться, что вы используете ресурсы, соответствующие выполняемой работе (см. [раздел Изменение типа компьютера для codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)). -- Разрешить {% data variables.product.prodname_dotcom %} автоматически использовать GPG для подписывания фиксаций, которые вы делаете в codespace (см. раздел [Управление проверкой GPG для {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)). -- Совместное использование зашифрованных секретов с codespace (см. раздел [Управление зашифрованными секретами для codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)). +- Change the machine type of your codespace to make sure you're using resources appropriate for the work you're doing (see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)"). +- Allow {% data variables.product.prodname_dotcom %} to automatically use GPG to sign commits you make in your codespace (see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)"). +- Share encrypted secrets with your codespace (see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"). -### Публикация из {% data variables.product.prodname_dotcom_the_website %} +### Publishing from {% data variables.product.prodname_dotcom_the_website %} -Неопубликованное пространство кода можно опубликовать на странице "Ваши codespaces" на {% data variables.product.prodname_dotcom_the_website %}. Это полезно, если вы хотите опубликовать пространство кода, которое в настоящее время не открыто в браузере. В этом случае работа будет сохранена в репозитории, но не будет связи между существующим пространством кода и новым репозиторием. Однако вы можете перейти к новому репозиторию и создать оттуда codespace, и это пространство кода будет подключено к репозиторию. +You can publish an unpublished codespace from the "Your codespaces" page on {% data variables.product.prodname_dotcom_the_website %}. This is useful if you want to publish a codespace that you don't currently have open in your browser. If you do this, your work will be preserved in a repository, but there won't be a link between your existing codespace and the new repository. However, you can navigate to the new repository and create a codespace from there, and this codespace will be connected to the repository. {% data reusables.codespaces.your-codespaces-procedure-step %} -1. Рядом с неопубликованным пространством кода щелкните многоточие (**...**), а затем выберите **Опубликовать в новом репозитории**. +1. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**. - ![Снимок экрана: кнопка "Опубликовать в новом репозитории"](/assets/images/help/codespaces/publish-to-new-repository.png) -1. Выберите имя для нового репозитория, задайте для него значение **Общедоступный** или **Частный** и нажмите кнопку **Создать репозиторий**. + ![Screenshot of the "Publish to a new repository" button](/assets/images/help/codespaces/publish-to-new-repository.png) +1. Choose a name for your new repository, set it as **Public** or **Private**, and click **Create repository**. - ![Снимок экрана: раскрывающийся список "Опубликовать в новом репозитории"](/assets/images/help/codespaces/template-new-repository-settings.png) -1. При необходимости, чтобы просмотреть новый репозиторий, щелкните **Просмотреть репозиторий**. + ![Screenshot of the "Publish to a new repository" dropdown](/assets/images/help/codespaces/template-new-repository-settings.png) +1. Optionally, to view the new repository, click **See repository**. -## Дополнительные материалы +## Further reading -- [Создание codespace для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository) -- [Жизненный цикл codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle) -- ["Использование системы управления версиями в codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" +- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)" +- "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" \ No newline at end of file diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 9d7f97dd8bbc..f77bf1a0c42f 100644 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -13,18 +13,18 @@ topics: - Fundamentals - Developer shortTitle: Delete a codespace -ms.openlocfilehash: c9f1f6eb407c985d8981504de28e39a4bf742f7a -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 24b53cc0cead2b6b15894ada4c799abc8e1c6e7a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158664' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188259' --- -Пространство кода можно удалить различными способами: в терминале с помощью {% data variables.product.prodname_cli %}, в {% data variables.product.prodname_vscode %} или в веб-браузере. Используйте вкладки в этой статье, чтобы отобразить инструкции по каждому из этих способов удаления codespace. +Кодовое пространство можно удалить различными способами: в терминале с помощью {% data variables.product.prodname_cli %}, в {% data variables.product.prodname_vscode %} или в веб-браузере. Используйте вкладки в этой статье, чтобы отобразить инструкции для каждого из этих способов удаления codespace. {% note %} -**Примечание**. Вы не можете удалить пространство кода из шлюза JetBrains, клиентского приложения JetBrains или из JupyterLab. +**Примечание**. Вы не можете удалить codespace из шлюза JetBrains, клиентского приложения JetBrains или из JupyterLab. {% endnote %} @@ -135,5 +135,5 @@ gh codespace delete --repo octo-org/octo-repo --days 7 Вы также можете удалить среды codespace вашей организации с помощью REST API. Дополнительные сведения см. в статье [Организации Codespaces](/rest/codespaces/organizations#delete-a-codespace-from-the-organization). ## Дополнительные материалы -- [Жизненный цикл codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle) -- Настройка [автоматического удаления codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces) +- [Жизненный цикл codespace](/codespaces/getting-started/the-codespace-lifecycle) +- [Настройка автоматического удаления codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces) diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md index 0a62b50cd7dc..90d2fbd15347 100644 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md +++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md @@ -22,11 +22,11 @@ children: - /using-github-codespaces-in-visual-studio-code - /using-github-codespaces-in-your-jetbrains-ide - /using-github-codespaces-with-github-cli -ms.openlocfilehash: 166283bd0fbc71b8acc180b20ef597dbc0a50781 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 6ace677a68ce7b592ac8ad2a8b83ae4d948b8747 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159016' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188291' --- diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md index 9e2a5e12b12f..337d21e2a77a 100644 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md +++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md @@ -1,5 +1,5 @@ --- -title: Открытие существующего codespace +title: Открытие существующего пространства кода intro: Вы можете повторно открыть закрытое или остановленное пространство кода и вернуться к работе. versions: fpt: '*' @@ -10,12 +10,12 @@ topics: - Fundamentals - Developer shortTitle: Open an existing codespace -ms.openlocfilehash: e7a35c1a7b3a251094bf69fcd401291b69d03eae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: b139b7f4e8a696416c97b3c400d09a9f26371b9c +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159008' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188299' --- {% jetbrains %} @@ -23,30 +23,30 @@ ms.locfileid: '148159008' {% endjetbrains %} -Вы можете повторно открыть любое активное или остановленное codespace в {% data variables.product.prodname_dotcom_the_website %}, в интегрированной среде разработки JetBrains, в {% data variables.product.prodname_vscode %} или с помощью {% data variables.product.prodname_cli %}. Вы не можете повторно открыть пространство codespace, которое было удалено. Дополнительные сведения см. в разделе [Жизненный цикл codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle). +Вы можете повторно открыть любое из активных или остановленных кодовых пространств в {% data variables.product.prodname_dotcom_the_website %}, в интегрированной среде разработки JetBrains, в {% data variables.product.prodname_vscode %} или с помощью {% data variables.product.prodname_cli %}. Вы не можете повторно открыть пространство codespace, которое было удалено. Дополнительные сведения см. в разделе [Жизненный цикл codespace](/codespaces/getting-started/the-codespace-lifecycle). Вы можете просмотреть все свои codespace на странице "Ваши codespaces" в [github.com/codespaces](https://github.com/codespaces). На этой странице можно выполнить следующие действия: - Откройте, остановите или удалите codespace. -- Узнайте, кто владеет (и может оплачиваться) вашими codespace: ваша личная учетная запись или организации, к которым вы принадлежите. Дополнительные сведения см. в статье [Сведения о выставлении счетов за {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). -- Создайте новое пространство кода, выбрав один из шаблонов {% data variables.product.company_short %}, или щелкнув **Создать codespace**. Дополнительные сведения см. в разделах [Создание codespace на основе шаблона](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template) и [Создание пространства кода для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository). +- Узнайте, кто владеет (и может выставляться за) ваши codespace: ваша личная учетная запись или организации, к которым вы принадлежите. Дополнительные сведения см. в статье [Сведения о выставлении счетов за {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +- Создайте новое пространство кода, выбрав один из шаблонов {% data variables.product.company_short %}, или щелкнув **Создать пространство кода**. Дополнительные сведения см. в [разделах Создание codespace из шаблона](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template) и [Создание codespace для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository). -## Открытие существующего codespace +## Открытие существующего пространства кода {% webui %} {% data reusables.codespaces.your-codespaces-procedure-step %} 1. Чтобы открыть codespace в редакторе по умолчанию, щелкните имя codespace. {% data reusables.codespaces.about-changing-default-editor %} Дополнительные сведения см. в разделе [Настройка редактора по умолчанию для {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces). - Чтобы открыть codespace в редакторе, отличном от используемого по умолчанию, выполните следующие действия. + Чтобы открыть пространство кода в редакторе, отличном от используемого по умолчанию, выполните следующие действия. - 1. Щелкните многоточие (**...**) справа от пространства кода, которое нужно открыть. + 1. Щелкните многоточие (**...**) справа от codespace, которое нужно открыть. 1. Нажмите кнопку **Открыть в**. 1. Нажмите кнопку **Открыть в приложении**. ![Снимок экрана: диалоговое окно "Открыть в" с выделенным элементом "Открыть в Visual Studio Code"](/assets/images/help/codespaces/open-codespace-in-another-editor.png) - Codespace можно открыть в: + Пространство кода можно открыть в: * Ваш браузер * {% data variables.product.prodname_vscode %} * Шлюз JetBrains @@ -54,7 +54,7 @@ ms.locfileid: '148159008' {% data reusables.codespaces.application-installed-locally %} - Если вы выберете **JupyterLab**, приложение JupyterLab должно быть установлено в codespace. {% data reusables.codespaces.jupyterlab-in-default-image %} + Если выбрать **JupyterLab**, приложение JupyterLab должно быть установлено в codespace. {% data reusables.codespaces.jupyterlab-in-default-image %} {% endwebui %} @@ -66,24 +66,24 @@ ms.locfileid: '148159008' {% endnote %} -1. В классическом приложении {% data variables.product.prodname_vscode_shortname %} откройте палитру команд спомощью команды Shift++P (Mac) или CTRL+SHIFT+P (Windows/Linux). +1. В классическом приложении {% data variables.product.prodname_vscode_shortname %} откройте палитру команд с помощью команды Shift++P (Mac) или CTRL+SHIFT+P (Windows или Linux). 1. Введите Codespaces и выберите одну из следующих команд. - - Чтобы открыть codespace в новом окне {% data variables.product.prodname_vscode_shortname %}, выберите **Codespaces: Открыть Codespace в новом окне**. + - Чтобы открыть codespace в новом окне {% data variables.product.prodname_vscode_shortname %}, выберите **Codespaces: Открыть codespace в новом окне**. - Чтобы открыть codespace в веб-редакторе, выберите **Codespaces: Открыть в браузере**. 1. Щелкните пространство кода, которое нужно открыть. ![Снимок экрана: список codespace в Visual Studio Code](/assets/images/help/codespaces/open-codespace-from-vscode.png) -Вы также можете получить доступ к приведенным выше командам, перейдя в представление удаленного обозревателя в {% data variables.product.prodname_vscode_shortname %} и щелкнув правой кнопкой мыши пространство кода, которое нужно открыть. +Вы также можете получить доступ к командам, перечисленным выше, перейдя в представление Удаленного обозревателя в {% data variables.product.prodname_vscode_shortname %} и щелкнув правой кнопкой мыши пространство кода, которое нужно открыть. -![Снимок экрана: пространство кода, выбранное в удаленном проводнике, с выделенным элементом "Открыть в браузере"](/assets/images/help/codespaces/open-codespace-remote-explorer.png) +![Снимок экрана: пространство кода, выбранное в удаленном обозревателе, с выделенным элементом "Открыть в браузере"](/assets/images/help/codespaces/open-codespace-remote-explorer.png) {% data reusables.codespaces.remote-explorer %} {% endvscode %} {% cli %} 1. В окне терминала введите одну из следующих команд {% data variables.product.prodname_cli %}. - - Чтобы открыть codespace в {% data variables.product.prodname_vscode_shortname %}, введите: + - Чтобы открыть пространство кода в {% data variables.product.prodname_vscode_shortname %}, введите: ```shell{:copy} gh codespace code @@ -113,7 +113,7 @@ ms.locfileid: '148159008' {% endnote %} -1. С помощью клавиш со стрелками перейдите к пространству кода, которое нужно открыть. +1. С помощью клавиш со стрелками перейдите в пространство кода, которое нужно открыть. 1. Чтобы открыть codespace, нажмите клавишу ВВОД. Дополнительные сведения см [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) . в руководстве по {% data variables.product.prodname_cli %}. diff --git a/translations/ru-RU/content/codespaces/getting-started/deep-dive.md b/translations/ru-RU/content/codespaces/getting-started/deep-dive.md index 09994553d34e..c75d1e8e154d 100644 --- a/translations/ru-RU/content/codespaces/getting-started/deep-dive.md +++ b/translations/ru-RU/content/codespaces/getting-started/deep-dive.md @@ -9,12 +9,12 @@ versions: type: quick_start topics: - Codespaces -ms.openlocfilehash: 5f97a137ec09191d5cbaa9c10aa280e10f11bbc0 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 01e4f3990cc47f61678811f7c4a77b86626fd8a5 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158648' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188267' --- {% data variables.product.prodname_github_codespaces %} — это современная облачная среда разработки, которая использует контейнер для предоставления популярных языков, инструментов и служебных программ для разработки. {% data variables.product.prodname_github_codespaces %} также можно настроить, что позволяет создать настраиваемую среду разработки для проекта. Настроив пользовательскую среду разработки для проекта, вы получите воспроизводимую конфигурацию кодового пространства для всех пользователей проекта. @@ -161,4 +161,4 @@ Git устанавливается по умолчанию в codespace, поэ - [Включение {% data variables.product.prodname_github_codespaces %} для вашей организации](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization) - [Управление затратами на {% data variables.product.prodname_github_codespaces %} в организации](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization) - [Добавление конфигурации контейнера разработки в репозиторий](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces) -- [Жизненный цикл codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle) +- [Жизненный цикл codespace](/codespaces/getting-started/the-codespace-lifecycle) diff --git a/translations/ru-RU/content/codespaces/getting-started/index.md b/translations/ru-RU/content/codespaces/getting-started/index.md index a3b1ae5993d4..4ff4872b7922 100644 --- a/translations/ru-RU/content/codespaces/getting-started/index.md +++ b/translations/ru-RU/content/codespaces/getting-started/index.md @@ -9,11 +9,11 @@ children: - /quickstart - /the-codespace-lifecycle - /deep-dive -ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: e89c26ddd6606192f93449fbc99660afe1fb2506 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160255' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188275' --- diff --git a/translations/ru-RU/content/codespaces/getting-started/the-codespace-lifecycle.md b/translations/ru-RU/content/codespaces/getting-started/the-codespace-lifecycle.md new file mode 100644 index 000000000000..a47f2cad2eb8 --- /dev/null +++ b/translations/ru-RU/content/codespaces/getting-started/the-codespace-lifecycle.md @@ -0,0 +1,73 @@ +--- +title: Жизненный цикл codespace +intro: 'Вы можете разрабатывать в среде {% data variables.product.prodname_github_codespaces %} и поддерживать данные на протяжении всего жизненного цикла codespace.' +versions: + fpt: '*' + ghec: '*' +type: overview +topics: + - Codespaces + - Developer +redirect_from: + - /codespaces/developing-in-codespaces/codespaces-lifecycle + - /codespaces/developing-in-codespaces/the-codespace-lifecycle +ms.openlocfilehash: 8f223bce2acf2f6dc6200271397c0d70f28aefe4 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ru-RU +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188383' +--- +## Сведения о жизненном цикле пространства кода + +Жизненный цикл пространства кода начинается при его создании и заканчивается при его удалении. Вы можете отключиться и переподключиться к активному пространству кода, не затрагивая выполняемые процессы. Вы можете остановить и перезапустить пространство кода без потери изменений, внесенных в проект. + +## Создание codespace + +Когда вы собираетесь работать над проектом, вы можете создать новое пространство кода или открыть существующее. Вам может потребоваться создать новое пространство кода из ветви репозитория при каждой разработке в {% data variables.product.prodname_github_codespaces %} или сохранить длительное пространство кода для функции. {% data reusables.codespaces.starting-new-project-template %} Дополнительные сведения см. в [разделах Создание codespace для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository) и [Создание codespace на основе шаблона](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template). + +{% data reusables.codespaces.max-number-codespaces %} Аналогичным образом, если вы достигнете максимального количества активных сред codespace и попытаетесь запустить еще одну среду, вам будет предложено остановить одну из активных сред codespace. + +Если вы решили создавать новое пространство кода каждый раз при работе над проектом, следует регулярно отправлять изменения, чтобы все новые фиксации были включены в {% data variables.product.prodname_dotcom %}. Если вы решили использовать для своего проекта долгосрочное пространство кода, то должны выполнять вытягивание из ветви по умолчанию репозитория каждый раз, когда начинаете работать в пространстве кода, чтобы в вашей среде присутствовали последние фиксации. Этот рабочий процесс очень похож на работу с проектом на локальном компьютере. + +{% data reusables.codespaces.prebuilds-crossreference %} + +## Сохранение изменений в пространстве кода + +При подключении к пространству кода через Интернет для веб редактора автоматически включается автосохранение и настраивается сохранение изменений после задержки. При подключении к пространству кода через {% data variables.product.prodname_vscode %}, работающий на вашем компьютере, необходимо самостоятельно включить автосохранение. Дополнительные сведения см. в разделе [Сохранение и автосохранение](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) документации по {% data variables.product.prodname_vscode %}. + +Ваша работа будет сохранена на виртуальной машине в облаке. Вы можете закрыть и остановить codespace, а затем вернуться к сохраненной работе. Если у вас есть несохраненные изменения, перед выходом редактор предложит сохранить их. Однако при удалении codespace работа также будет удалена. Чтобы сохранить работу, необходимо зафиксировать изменения и отправить их в удаленный репозиторий или опубликовать работу в новом удаленном репозитории, если вы создали codespace на основе шаблона. Дополнительные сведения см. в статье [Использование системы управления версиями в кодовом пространстве](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace). + +## Время ожидания для {% data variables.product.prodname_github_codespaces %} + +Если вы оставите свое пространство кода работающим без взаимодействия или если выйдете из него, не остановив его явно, после некоторого периода бездействия время ожидания истечет, и пространство кода остановит работу. По умолчанию время ожидания пространства кода истекает через 30 минут бездействия, но вы можете настроить другое время ожидания для вновь создаваемых пространств кода. Дополнительные сведения о настройке времени ожидания по умолчанию для пространств кода см. в разделе [Настройка времени ожидания для {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces). Дополнительные сведения об остановке пространства кода см. в разделе [Остановка пространства кода](#stopping-a-codespace). + +При истечении времени ожидания пространства кода данные сохраняются с момента последнего сохранения изменений. Дополнительные сведения см. в разделе [Сохранение изменений в пространстве кода](#saving-changes-in-a-codespace). + +## Перестроение пространства кода + +Вы можете перестроить codespace, чтобы реализовать изменения в конфигурации контейнера разработки. В большинстве случаев вместо перестроения пространства кода можно просто создать новое пространство кода. По умолчанию при перестроении codespace {% data variables.product.prodname_github_codespaces %} будет повторно использовать образы из кэша, чтобы ускорить процесс перестроения. Кроме того, можно выполнить полную перестройку, которая очищает кэш и перестраивает контейнер со свежими образами. + +Дополнительные сведения см. в разделах [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace) и [Выполнение полной перестройки контейнера](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container). + +## Остановка пространства кода + +{% data reusables.codespaces.stopping-a-codespace %} Дополнительные сведения см. в разделе [Остановка и запуск codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace). + +## Удаление codespace + +Вы можете создать пространство кода для конкретной задачи, а затем безопасно удалить его после отправки изменений в удаленную ветвь. + +Если вы попытаетесь удалить пространство кода с неотправленными фиксациями git, редактор сообщит вам, что имеются изменения, которые не были отправлены в удаленную ветвь. Вы можете отправить все необходимые изменения, а затем удалить пространство кода или продолжить, чтобы удалить пространство кода и все незафиксированные изменения. Вы также можете экспортировать код в новую ветвь, не создавая новое пространство кода. Дополнительные сведения см. в разделе [Экспорт изменений в ветвь](/codespaces/troubleshooting/exporting-changes-to-a-branch). + +Codespace, которые были остановлены и остаются неактивными в течение указанного периода времени, будут удалены автоматически. По умолчанию неактивные codespace удаляются через 30 дней, но вы можете настроить период хранения codespace. Дополнительные сведения см. в статье [Настройка автоматического удаления сред codespace](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces). + +Если вы создадите codespace, оно будет продолжать начислять расходы на хранение, пока оно не будет удалено, независимо от того, является ли оно активным или остановленным. Дополнительные сведения см. в статье [Сведения о выставлении счетов за {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage). Удаление codespace не уменьшает текущую оплачиваемую сумму для {% data variables.product.prodname_github_codespaces %}, которая накапливается в течение каждого ежемесячного цикла выставления счетов. Дополнительные сведения см. в разделе [Просмотр данных об использовании {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage). + +Дополнительные сведения об удалении пространства кода см. в разделе [Удаление пространства кода](/codespaces/developing-in-codespaces/deleting-a-codespace). + +## Потеря подключения при использовании {% data variables.product.prodname_github_codespaces %} + +{% data variables.product.prodname_github_codespaces %} — это облачная среда разработки, для которой требуется подключение к Интернету. Если во время работы в пространстве кода произойдет потеря подключения к Интернету, вы не сможете получить доступ к своему пространству кода. Однако все незафиксированные изменения будут сохранены. Когда подключение к Интернету будет восстановлено, вы сможете подключиться к пространству кода в том же состоянии, в котором оно было оставлено. Если ваше подключение к Интернету нестабильно, следует чаще фиксировать и отправлять изменения. + +Если вы знаете, что часто работаете в автономном режиме, вы можете использовать файл `devcontainer.json` с [расширением "Контейнеры разработки"](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) для {% data variables.product.prodname_vscode_shortname %} для сборки и подключения к локальному контейнеру разработки для репозитория. Дополнительные сведения см. в разделе [Разработка в контейнере](https://code.visualstudio.com/docs/remote/containers) в документации по {% data variables.product.prodname_vscode %}. diff --git a/translations/ru-RU/content/codespaces/index.md b/translations/ru-RU/content/codespaces/index.md index 7a9359093f90..84bd8761f974 100644 --- a/translations/ru-RU/content/codespaces/index.md +++ b/translations/ru-RU/content/codespaces/index.md @@ -53,11 +53,11 @@ children: - /troubleshooting - /the-githubdev-web-based-editor - /guides -ms.openlocfilehash: 62723c1d4bf684e67420149c96586a91e7583031 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 242931386711938cb1eb5e9b84ad66a581ecb1eb +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160437' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188307' --- diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md index cc31f4b689db..f4dc0c338746 100644 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md +++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md @@ -1,7 +1,7 @@ --- title: Ограничение базового образа для codespace shortTitle: Restrict base image -intro: 'Вы можете указать, какие базовые образы можно использовать для новых codespace, созданных в организации.' +intro: 'Вы можете указать, какие базовые образы можно использовать для новых codespace, созданных в вашей организации.' permissions: 'To manage image constraints for an organization''s codespaces, you must be an owner of the organization.' versions: fpt: '*' @@ -9,16 +9,16 @@ versions: type: how_to topics: - Codespaces -ms.openlocfilehash: 1da438a680dd3e60c1deeec46a98fbcf48f84e5b -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: f17bb20aa919ca94cd13e14a6f770cea23042b2b +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159000' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188283' --- -## Общие сведения +## Обзор -При создании codespace контейнер Docker автоматически создается на удаленной виртуальной машине. Контейнер Docker создается из образа Docker. Образ фактически является шаблоном для контейнеров Docker и определяет многие аспекты результирующей среды, предоставляемой пространством кода. +При создании codespace контейнер Docker автоматически создается на удаленной виртуальной машине. Контейнер Docker создается из образа Docker. Образ фактически является шаблоном для контейнеров Docker и определяет многие аспекты результирующей среды, предоставляемой codespace. Вы можете выбрать образ, который вы хотите использовать для codespaces, указав его в конфигурации контейнера разработки для репозитория. Это можно сделать, например, с помощью `image` свойства в `devcontainer.json` файле . @@ -30,17 +30,17 @@ ms.locfileid: '148159000' Если вы не укажете образ в конфигурации контейнера разработки для репозитория, используется образ по умолчанию. Образ по умолчанию содержит несколько версий среды выполнения для популярных языков и часто используемых средств. Дополнительные сведения см. в статье [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration). -Как владелец организации вы можете добавить политику, ограничивающую, какие образы можно использовать для codespace, созданных в вашей организации. +Как владелец организации вы можете добавить политику, чтобы ограничить, какие образы можно использовать для codespace, созданных в вашей организации. Если образ, указанный в конфигурации контейнера разработки, не соответствует одному из разрешенных образов, при попытке создать codespace для репозитория отображается следующее сообщение: -> Не удалось создать Codespace. Базовый образ "DETAILS FROM DEV CONTAINER CONFIGURATION" не допускается на основе политики организации, установленной администратором организации. +> Не удалось создать Codespace. Базовый образ "DETAILS FROM DEV CONTAINER CONFIGURATION" не разрешен на основе политики организации, установленной администратором организации. {% note %} **Примечания** -* Политика базового образа применяется только при создании codespace. В настоящее время он не применяется при перестроении контейнера. Это изменится в будущем выпуске. Дополнительные сведения см. в разделе [Жизненный цикл codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle#rebuilding-a-codespace). -* Политика базового образа не применяется к образу по умолчанию или образу, который используется для восстановления codespace, если в конфигурации контейнера разработки возникает ошибка, которая предотвращает перестроение контейнера. +* Политика базового образа применяется только при создании codespace. В настоящее время он не применяется при перестроении контейнера. Это изменится в будущем выпуске. Дополнительные сведения см. в разделе [Жизненный цикл codespace](/codespaces/getting-started/the-codespace-lifecycle#rebuilding-a-codespace). +* Политика базового образа не применяется к образу по умолчанию или образу, который используется для восстановления пространства кода, если в конфигурации контейнера разработки возникает ошибка, которая препятствует перестроению контейнера. {% endnote %} @@ -48,7 +48,7 @@ ms.locfileid: '148159000' При создании политики вы выбираете, применяется ли она ко всем репозиториям в организации или только к указанным. Если вы задали политику для всей организации, все политики, заданные для отдельных репозиториев, должны относиться к набору ограничений на уровне организации. Добавление политик делает выбор образа более строгим, а не менее строгим. -Например, можно создать политику всей организации, которая ограничивает базовый образ любым из десяти указанных образов. Затем можно задать политику для репозитория A, которая ограничивает образ только двумя образами, указанными на уровне организации. Указание дополнительных образов для репозитория A не будет иметь никакого эффекта, так как эти образы не указаны в политике уровня организации. Если вы добавляете политику для всей организации, следует задать для нее самый большой выбор образов, которые будут доступны для любого репозитория в вашей организации. Затем вы можете добавить политики для конкретного репозитория, чтобы дополнительно ограничить выбор. +Например, можно создать политику для всей организации, которая ограничивает базовый образ любым из десяти указанных образов. Затем можно задать политику для репозитория A, которая ограничивает образ только двумя образами, указанными на уровне организации. Указание дополнительных образов для репозитория A не будет иметь никакого эффекта, так как эти образы не указаны в политике уровня организации. При добавлении политики для всей организации следует задать для нее самый большой выбор образов, которые будут доступны для любого репозитория в вашей организации. Затем вы можете добавить политики для конкретного репозитория, чтобы дополнительно ограничить выбор. {% data reusables.codespaces.codespaces-org-policies-note %} @@ -61,9 +61,9 @@ ms.locfileid: '148159000' 1. Нажмите {% octicon "pencil" aria-label="The edit icon" %}, чтобы изменить ограничение. - ![Снимок экрана: значок карандаша для редактирования ограничения](/assets/images/help/codespaces/edit-image-constraint.png) + ![Снимок экрана: значок карандаша для изменения ограничения](/assets/images/help/codespaces/edit-image-constraint.png) -1. В поле "Разрешенные значения" введите полный URL-адрес изображения, который вы хотите разрешить. +1. В поле "Допустимые значения" введите полный URL-адрес изображения, которое вы хотите разрешить. ![Снимок экрана: запись в поле "Разрешенные значения"](/assets/images/help/codespaces/image-allowed-values.png) @@ -74,16 +74,16 @@ ms.locfileid: '148159000' {% endnote %} 1. Нажмите кнопку "плюс" ({% octicon "plus" aria-label="The plus icon" %}), чтобы добавить значение. -1. При необходимости повторите два предыдущих шага, чтобы добавить дополнительные URL-адреса изображений. +1. При необходимости повторите предыдущие два шага, чтобы добавить ДОПОЛНИТЕЛЬНЫЕ URL-адреса изображений. {% data reusables.codespaces.codespaces-policy-targets %} -1. Если вы хотите добавить другое ограничение в политику, щелкните **Добавить ограничение** и выберите другое ограничение. Сведения о других ограничениях см. в разделе: +1. Если вы хотите добавить другое ограничение в политику, щелкните **Добавить ограничение** и выберите другое ограничение. Дополнительные сведения о других ограничениях см. в разделе: * "[Ограничение доступа к типам компьютеров](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" * ["Ограничение видимости перенаправленных портов](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" - * ["Ограничение времени ожидания простоя](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)" - * ["Ограничение срока хранения для codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)" + * [Ограничение времени ожидания простоя](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period) + * [Ограничение срока хранения для codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces) 1. Завершив добавление ограничений в политику, щелкните **Сохранить**. -Политика применяется, когда кто-либо пытается создать новое пространство кода, которое оплачивается для вашей организации. Ограничение базового образа не влияет на существующие codespace, активные или остановленные. +Политика применяется, когда кто-либо пытается создать новое пространство кода, которое будет оплачиваться для вашей организации. Ограничение базового образа не влияет на существующие codespace, активные или остановленные. ## Изменение политики @@ -92,7 +92,7 @@ ms.locfileid: '148159000' 1. Откройте страницу "Политики codespace". Дополнительные сведения см. в разделе [Добавление политики для определения разрешенных образов](#adding-a-policy-to-define-the-allowed-images). 1. Щелкните имя политики, которую нужно изменить. 1. Щелкните значок карандаша ({% octicon "pencil" aria-label="The edit icon" %}) рядом с ограничением "Базовые изображения". -1. Добавление или удаление URL-адресов изображений. +1. Добавление и удаление URL-адресов изображений. 1. Выберите команду **Сохранить**. ## Удаление политики diff --git a/translations/ru-RU/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/ru-RU/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md index 71e72f15c3d8..44aa07505cf3 100644 --- a/translations/ru-RU/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md +++ b/translations/ru-RU/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: Создание шаблона запроса на вытягивание для репозитория -intro: 'Когда вы добавите шаблон запроса на вытягивание в репозиторий, участники проекта автоматически увидят содержимое шаблона в тексте запроса на вытягивание.' +title: Creating a pull request template for your repository +intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.' redirect_from: - /articles/creating-a-pull-request-template-for-your-repository - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository @@ -12,44 +12,41 @@ versions: topics: - Community shortTitle: Create a PR template -ms.openlocfilehash: 2a85c88944f1d46209429846bba1e7a3c930968e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ru-RU -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145092341' --- -Дополнительные сведения см. в статье "[Сведения о шаблонах проблем и запросов на вытягивание](/articles/about-issue-and-pull-request-templates). -Можно создать подкаталог *PULL_REQUEST_TEMPLATE/* в любой из поддерживаемых папок, чтобы он содержал шаблоны для нескольких запросов на вытягивание, и использовать параметр запроса `template`, чтобы указать шаблон, который будет заполнять текст запроса на вытягивание. Дополнительные сведения см. в разделе [Использование параметров запроса для создания запроса на вытягивание](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request). +For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." + +You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." {% ifversion fpt or ghes or ghec %} -Можно создать шаблоны запроса на вытягивание по умолчанию для организации{% ifversion fpt or ghes or ghec %} или личной учетной записи{% endif %}. Дополнительные сведения см. в статье "[Создание файла работоспособности сообщества по умолчанию](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)". +You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} -## Добавление шаблона запроса на вытягивание - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. В поле имени файла: - - Чтобы сделать шаблон запроса на вытягивание видимым в корневом каталоге репозитория, присвойте шаблону запроса на вытягивание имя `pull_request_template.md`. - ![Имя нового шаблона запроса на вытягивание в корневом каталоге](/assets/images/help/repository/pr-template-file-name.png) - - Чтобы сделать шаблон запроса на вытягивание видимым в каталоге `docs` репозитория, присвойте шаблону запроса на вытягивание имя `docs/pull_request_template.md`. - ![Шаблон нового запроса на вытягивание в каталоге документации](/assets/images/help/repository/pr-template-file-name-docs.png) - - Чтобы сохранить файл в скрытом каталоге, присвойте шаблону запроса на вытягивание имя `.github/pull_request_template.md`. - ![Шаблон нового запроса на вытягивание в скрытом каталоге](/assets/images/help/repository/pr-template-hidden-directory.png) - - Чтобы создать шаблоны для нескольких запросов на вытягивание и использовать параметр запроса `template`, чтобы указать шаблон для заполнения текста проблемы, введите *.github/PULL_REQUEST_TEMPLATE/* , а затем имя шаблона запроса на вытягивание. Например, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. Можно также хранить шаблоны для нескольких запросов на вытягивание в подкаталоге `PULL_REQUEST_TEMPLATE`, в корне или каталогах `docs/`. Дополнительную информацию см. в разделе [Сведения об автоматизации проблем и запросов на вытягивание с параметрами запроса](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters). - ![Шаблон для нескольких новых запросов на вытягивание в скрытом каталоге](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) -4. Добавьте шаблон запроса на вытягивание в текст нового файла. Это может быть: - - [ссылка на связанную проблему](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) в репозитории; - - описание изменений, предлагаемых в запросе на вытягивание; - - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) пользователя или команды, ответственной за проверку предлагаемых изменений. -{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} Шаблоны доступны участникам совместной работы при их слиянии в ветвь репозитория по умолчанию. +## Adding a pull request template + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field: + - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`. + ![New pull request template name in root directory](/assets/images/help/repository/pr-template-file-name.png) + - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`. + ![New pull request template in docs directory](/assets/images/help/repository/pr-template-file-name-docs.png) + - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`. + ![New pull request template in hidden directory](/assets/images/help/repository/pr-template-hidden-directory.png) + - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." + ![New multiple pull request template in hidden directory](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) +4. In the body of the new file, add your pull request template. This could include: + - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository. + - A description of the changes proposed in the pull request. + - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch. {% data reusables.files.propose_new_file %} -## Дополнительные материалы +## Further reading -- [Сведения о шаблонах проблем и запросов на вытягивание](/articles/about-issue-and-pull-request-templates) -- [Сведения об автоматизации проблем и запросов на вытягивание с параметрами запроса](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters) -- [Создание запроса на вытягивание](/articles/creating-a-pull-request) +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating a pull request](/articles/creating-a-pull-request)" diff --git a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md new file mode 100644 index 000000000000..25d523d87829 --- /dev/null +++ b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md @@ -0,0 +1,33 @@ +--- +title: Изменение удаленного URL-адреса репозитория из GitHub Desktop +intro: 'Вы можете изменить удаленный URL-адрес репозитория, с которым вы работаете в {% data variables.product.prodname_desktop %}. Это можно сделать, если репозиторий переименован или имя пользователя или организация, принадлежащие репозиторию, изменились.' +redirect_from: + - /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop +versions: + fpt: '*' +shortTitle: Change the remote URL for a repository +ms.openlocfilehash: e37c4878c13a9de95520f8e9c1edc9bf6416d46a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ru-RU +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188379' +--- +{% mac %} + +{% data reusables.desktop.mac-repository-settings-menu %} +2. Щелкните **Удаленный** и в разделе **Главный удаленный репозиторий** введите нужный URL-адрес. +![Поле "Главный удаленный репозиторий"](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-repository-settings-menu %} +2. Щелкните **Удаленный** и в разделе **Главный удаленный репозиторий** введите нужный URL-адрес. +![Поле "Главный удаленный репозиторий"](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endwindows %} diff --git a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index 3eb0f7b63375..e182e2f4416d 100644 --- a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -12,11 +12,11 @@ children: - /configuring-notifications-in-github-desktop - /changing-the-remote-url-for-a-repository-from-github-desktop shortTitle: Work with your remote repo -ms.openlocfilehash: 60c2f41546ff085ea8f8d56142da6a3c7a81ebae -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT +ms.openlocfilehash: f7e9f1ab5f73aaad29208db01c62815d7a20ba03 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145117475' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188382' --- diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index ec2c7c982017..549f44ba2cdc 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -6,22 +6,22 @@ intro: '{% data variables.product.prodname_github_codespaces %} можно ис versions: fpt: '*' permissions: 'Organization owners who are admins for a classroom can enable {% data variables.product.prodname_github_codespaces %} for their organization and integrate {% data variables.product.prodname_github_codespaces %} as the supported editor for an assignment. {% data reusables.classroom.classroom-admins-link %}' -ms.openlocfilehash: 6794d20b9ea0153b3baf4bee1a08c68b2ba17456 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 832ab470d13cc741bc4a71e77840c99da5ff3de6 +ms.sourcegitcommit: a35d85531445980b5f04d3fc70180a29dad37f89 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158880' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148189916' --- ## О {% data variables.product.prodname_github_codespaces %} -{% data variables.product.prodname_github_codespaces %} — это современная облачная среда разработки, которая использует контейнер для предоставления популярных языков, инструментов и служебных программ для разработки. {% data variables.product.prodname_github_codespaces %} также можно настроить, что позволяет создать настраиваемую среду разработки, которая будет одинаковой для всех пользователей проекта. Дополнительные сведения см. в статье "[Обзор {% data variables.product.prodname_github_codespaces %}](/codespaces/overview)". +{% data variables.product.prodname_github_codespaces %} — это современная облачная среда разработки, которая использует контейнер для предоставления популярных языков, инструментов и служебных программ для разработки. {% data variables.product.prodname_github_codespaces %} также можно настроить, что позволяет создать настраиваемую среду разработки, одинаковую для всех пользователей проекта. Дополнительные сведения см. в статье "[Обзор {% data variables.product.prodname_github_codespaces %}](/codespaces/overview)". После включения {% data variables.product.prodname_github_codespaces %} в организации или на предприятии пользователи могут создать codespace из любой ветви или фиксации в организации или корпоративном репозитории и начать разработку с использованием облачных вычислительных ресурсов. Вы можете подключиться к пространству кода через браузер или в локальной среде Visual Studio Code. {% data reusables.codespaces.links-to-get-started %} -Назначение {% data variables.product.prodname_github_codespaces %} в качестве предпочтительного редактора для задания в GitHub Classroom полезно как для учащихся, так и для преподавателей. {% data variables.product.prodname_github_codespaces %} является хорошим вариантом для учащихся, использующих устройства с кредитом или без доступа к локальной настройке интегрированной среды разработки, так как каждое пространство кода основано на облаке и не требует локальной настройки. Учащиеся могут запустить пространство кода для репозитория заданий в Visual Studio Code, используя любой браузер, и начать разработку без дополнительной настройки. +Назначение {% data variables.product.prodname_github_codespaces %} в качестве предпочтительного редактора для заданий в GitHub Classroom полезно как для учащихся, так и для преподавателей. {% data variables.product.prodname_github_codespaces %} является хорошим вариантом для учащихся, использующих заемные устройства или не имеющих доступа к локальной настройке интегрированной среды разработки, так как каждое пространство кода основано на облаке и не требует локальной настройки. Учащиеся могут запустить пространство кода для репозитория заданий в Visual Studio Code, используя любой браузер, и начать разработку без дополнительной настройки. Для заданий со сложными средами преподаватели могут настроить конфигурацию контейнера разработки для конкретных пространств кода в репозитории. В этом случае при создании пространства кода учащийся автоматически получит среду разработки, настроенную преподавателем. Дополнительные сведения о контейнерах разработки см. в разделе [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers). @@ -41,7 +41,7 @@ ms.locfileid: '148158880' ## Сведения о преимуществах {% data variables.product.prodname_codespaces %} Education для подтвержденных преподавателей -Преимущество для образования {% data variables.product.prodname_codespaces %} предоставляет проверенным преподавателям бесплатное ежемесячное пособие в размере {% data variables.product.prodname_github_codespaces %} часов для использования в {% data variables.product.prodname_classroom %}. Этого пособия, по усредненным оценкам, достаточно для работы класса с 50 учащимися и 5 заданиями в месяц на компьютере с 2 ядрами и хранения 1 пространства кода для каждого учащегося. +Преимущество для образования {% data variables.product.prodname_codespaces %} предоставляет проверенным преподавателям бесплатную ежемесячную надбавку в размере {% data variables.product.prodname_github_codespaces %} часов для использования в {% data variables.product.prodname_classroom %}. Этого пособия, по усредненным оценкам, достаточно для работы класса с 50 учащимися и 5 заданиями в месяц на компьютере с 2 ядрами и хранения 1 пространства кода для каждого учащегося. {% data reusables.classroom.free-limited-codespaces-for-verified-teachers-beta-note %} @@ -49,13 +49,13 @@ ms.locfileid: '148158880' Получив сообщение о том, что вы стали подтвержденным преподавателем, посетите [{% data variables.product.prodname_global_campus %} для преподавателей](https://education.github.com/globalcampus/teacher) и обновите GitHub Team для организации. Дополнительные сведения см. в разделе [Продукты GitHub](/get-started/learning-about-github/githubs-products#github-team). -Если вы имеете право на {% data variables.product.prodname_codespaces %} Для образования, при включении {% data variables.product.prodname_github_codespaces %} в {% data variables.product.prodname_classroom %} для вашей организации GitHub автоматически добавляет политику Codespace, ограничивающую типы компьютеров для всех codespace в организации до 2 основных компьютеров. Это поможет вам максимально эффективно использовать бесплатные {% data variables.product.prodname_github_codespaces %}. Но вы можете свободно изменять или удалять такие политики в параметрах организации. Дополнительные сведения см. в разделе [Ограничение доступа по типам компьютеров](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types). +Если вы имеете право на {% data variables.product.prodname_codespaces %} Для образования, при включении {% data variables.product.prodname_github_codespaces %} в {% data variables.product.prodname_classroom %} для вашей организации GitHub автоматически добавляет политику Codespace, ограничивающую типы компьютеров для всех codespace в организации до 2 основных компьютеров. Это позволяет максимально эффективно использовать бесплатные {% data variables.product.prodname_github_codespaces %}. Но вы можете свободно изменять или удалять такие политики в параметрах организации. Дополнительные сведения см. в разделе [Ограничение доступа по типам компьютеров](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types). -Когда преимущество для образования {% data variables.product.prodname_codespaces %} выходит из бета-версии, если ваша организация превысит свое бесплатное пособие на использование {% data variables.product.prodname_github_codespaces %}, вашей организации будет выставлен счет за дополнительное использование. Дополнительные сведения см. в статье [Сведения о выставлении счетов за {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). +Когда преимущество для образования {% data variables.product.prodname_codespaces %} выходит из бета-версии, если ваша организация превысит бесплатную квоту на использование {% data variables.product.prodname_github_codespaces %}, вашей организации будет выставлен счет за дополнительное использование. Дополнительные сведения см. в статье [Сведения о выставлении счетов за {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). ## Включение {% data variables.product.prodname_codespaces %} для организации -{% data variables.product.prodname_github_codespaces %} доступно для использования с {% data variables.product.prodname_classroom %} для организаций, использующих {% data variables.product.prodname_team %}. Если вы имеете право на {% data variables.product.prodname_codespaces %} Для образования, необходимо включить {% data variables.product.prodname_github_codespaces %} через {% data variables.product.prodname_classroom %}, а не включать его непосредственно в параметрах организации. В противном случае плата за использование {% data variables.product.prodname_github_codespaces %} будет выставляться непосредственно вашей организации. +{% data variables.product.prodname_github_codespaces %} доступен для использования с {% data variables.product.prodname_classroom %} для организаций, использующих {% data variables.product.prodname_team %}. Если вы имеете право на получение преимущества для образования {% data variables.product.prodname_codespaces %}, необходимо включить {% data variables.product.prodname_github_codespaces %} с помощью {% data variables.product.prodname_classroom %}, а не включать его непосредственно в параметрах организации. В противном случае вашей организации будет выставляться счет напрямую за все использование {% data variables.product.prodname_github_codespaces %}. ### Включение Codespaces для организации при создании новой аудитории {% data reusables.classroom.sign-into-github-classroom %} @@ -63,7 +63,7 @@ ms.locfileid: '148158880' ![Кнопка "Создать аудиторию"](/assets/images/help/classroom/click-new-classroom-button.png) -1. В списке организаций выберите организацию, которую хотите использовать для своей аудитории. Организации, имеющие право на {% data variables.product.prodname_github_codespaces %}, получат заметку о том, что они имеют право. При необходимости создайте новую организацию. Дополнительные сведения см. в статье [Создание новой организации с нуля](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch). +1. В списке организаций выберите организацию, которую хотите использовать для своей аудитории. Организации, которые имеют право на {% data variables.product.prodname_github_codespaces %}, будут иметь примечание, показывающее, что они имеют право. При необходимости создайте новую организацию. Дополнительные сведения см. в статье [Создание новой организации с нуля](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch). ![Выбор организации для аудитории с правом на использование Codespaces](/assets/images/help/classroom/org-view-codespaces-eligibility.png) @@ -80,10 +80,10 @@ ms.locfileid: '148158880' ![Настройка Codespaces для организации в параметрах существующей аудитории](/assets/images/help/classroom/classroom-settings-enable-codespaces-button.png) -Вы можете использовать те же методы, что и выше, чтобы отключить {% data variables.product.prodname_github_codespaces %} для вашей организации. Обратите внимание, что {% data variables.product.prodname_github_codespaces %} будет отключен для всех пользователей и репозиториев в организации. +Вы можете использовать те же методы, что и выше, чтобы отключить {% data variables.product.prodname_github_codespaces %} для вашей организации. Обратите внимание, что это приведет к отключению {% data variables.product.prodname_github_codespaces %} для всех пользователей и репозиториев в организации. ## Настройка назначения для использования {% data variables.product.prodname_codespaces %} -Чтобы сделать {% data variables.product.prodname_github_codespaces %} доступным учащимся для задания, можно выбрать {% data variables.product.prodname_github_codespaces %} в качестве поддерживаемого редактора для задания. При создании нового назначения на странице "Добавление начального кода и выбор необязательной интегрированной среды разработки в Интернете" в разделе "Добавление поддерживаемого редактора" выберите **{% data variables.product.prodname_github_codespaces %}** в раскрывающемся меню. +Чтобы сделать {% data variables.product.prodname_github_codespaces %} доступным для задания, можно выбрать {% data variables.product.prodname_github_codespaces %} в качестве поддерживаемого редактора для задания. При создании нового назначения на странице "Добавление начального кода и выбор необязательной интегрированной среды разработки в Интернете" в разделе "Добавление поддерживаемого редактора" выберите **{% data variables.product.prodname_github_codespaces %}** в раскрывающемся меню. ![Выбор Codespaces в качестве поддерживаемого редактора для назначения](/assets/images/help/classroom/select-supported-editor-including-codespaces.png) @@ -95,7 +95,7 @@ ms.locfileid: '148158880' ![Снимок экрана: примечание Codespaces в файле README в репозитории задания для учащихся](/assets/images/help/classroom/student-codespaces-readme-link.png) -Учащиеся могут запустить новое или существующее codespace, нажав кнопку **Открыть в GitHub Codespace** в файле сведений или нажав кнопку **{% octicon "code" aria-label="The code icon" %} Code** на главной странице репозитория заданий, а затем выбрав вкладку **Codespaces** . На вкладке **Codespaces** можно выбрать существующее codespace или создать новое. Дополнительные сведения см. в разделе [Создание пространства кода для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository). +Учащиеся могут запустить новое или существующее codespace, нажав кнопку **Открыть в GitHub Codespace** в файле README или нажав кнопку **{% octicon "code" aria-label="The code icon" %} Code** на главной странице репозитория заданий, а затем выбрав вкладку **Codespaces** . На вкладке **Codespaces** можно выбрать существующее codespace или создать новое. Дополнительные сведения см. в разделе [Создание codespace для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository). ![Запуск нового пространства кода в репозитории назначений](/assets/images/help/classroom/student-launch-new-codespace.png) @@ -103,4 +103,4 @@ ms.locfileid: '148158880' ![Общие сведения о назначении преподавателей для пространств кода учащихся](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) -При подключении к пространству кода в браузере автоматически включается автосохранение. Если вы хотите сохранить внесенные изменения в репозитории, необходимо зафиксировать эти изменения и отправить их в ветвь удаленного репозитория. По умолчанию, если пространство кода не используется в течение 30 минут, истекает время ожидания и работа пространства кода прекращается. Все ваши данные будут сохранены по состоянию на момент последнего изменения. Дополнительные сведения о жизненном цикле codespace см. в разделе [Жизненный цикл codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle). +При подключении к пространству кода в браузере автоматически включается автосохранение. Если вы хотите сохранить внесенные изменения в репозитории, необходимо зафиксировать эти изменения и отправить их в ветвь удаленного репозитория. По умолчанию, если пространство кода не используется в течение 30 минут, истекает время ожидания и работа пространства кода прекращается. Все ваши данные будут сохранены по состоянию на момент последнего изменения. Дополнительные сведения о жизненном цикле codespace см. в разделе [Жизненный цикл codespace](/codespaces/getting-started/the-codespace-lifecycle). diff --git a/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md b/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md new file mode 100644 index 000000000000..38e2da581b3c --- /dev/null +++ b/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md @@ -0,0 +1,43 @@ +--- +title: Настройка удаленного репозитория для вилки +intro: 'Необходимо настроить удаленный репозиторий, указывающий на вышестоящий репозиторий в Git, чтобы [синхронизировать изменения, внесенные в вилку](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) с исходным репозиторием. Это также позволяет синхронизировать изменения, внесенные в исходный репозиторий с созданной вилкой.' +redirect_from: + - /github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /articles/configuring-a-remote-for-a-fork + - /github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Pull requests +shortTitle: Configure a remote repository +ms.openlocfilehash: 495d3c825356fd69c9130f8a122aa7a8702ff317 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ru-RU +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188387' +--- +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Получите текущий настроенный удаленный репозиторий для вилки. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + ``` +3. Укажите новый удаленный *вышестоящий* репозиторий, который будет синхронизирован с вилкой. + ```shell + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git + ``` +4. Проверьте новый вышестоящий репозиторий, указанный для вилки. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + ``` diff --git a/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md index 926ee283dfc4..f5465eb17357 100644 --- a/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md +++ b/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md @@ -18,11 +18,11 @@ children: - /syncing-a-fork - /allowing-changes-to-a-pull-request-branch-created-from-a-fork - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility -ms.openlocfilehash: 79d8346fdd63366e5987def43164932503104332 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT +ms.openlocfilehash: 0133f7759cb9040a5acb97a7b08c312a55079bda +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146683664' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188386' --- diff --git a/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index c9b479247ebf..5b41e411e584 100644 --- a/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/ru-RU/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -1,6 +1,6 @@ --- -title: Syncing a fork -intro: Sync a fork of a repository to keep it up-to-date with the upstream repository. +title: Синхронизация вилки +intro: 'Синхронизируйте вилку репозитория, чтобы гарантировать его актуальность в вышестоящем репозитории.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork - /articles/syncing-a-fork @@ -19,44 +19,48 @@ versions: topics: - Pull requests permissions: People with write access for a forked repository can sync the fork to the upstream repository. +ms.openlocfilehash: 85b149e26cb65a428d7e9b66aea99d6b62430ae0 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: MT +ms.contentlocale: ru-RU +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188331' --- - -## Syncing a fork branch from the web UI +## Синхронизация ветви вилки из пользовательского веб-интерфейса {% ifversion syncing-fork-web-ui %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Sync fork** dropdown. - !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) -3. Review the details about the commits from the upstream repository, then click **Update branch**. - ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) -{% else %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Fetch upstream** dropdown. - !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. - !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} +1. На {% data variables.product.product_name %} перейдите на главную страницу разветвленного репозитория, который требуется синхронизировать с вышестоящим репозиторием. +2. Выберите раскрывающийся список **Синхронизировать вилку**. + ![Выделенный раскрывающийся список "Синхронизировать вилку"](/assets/images/help/repository/sync-fork-dropdown.png) +3. Просмотрите сведения о фиксациях из вышестоящего репозитория, а затем щелкните **Обновить ветвь**. + ![Модальное окно "Синхронизация вилки" с выделенной кнопкой "Обновить ветвь"](/assets/images/help/repository/update-branch-button.png) {% else %} +1. На {% data variables.product.product_name %} перейдите на главную страницу разветвленного репозитория, который требуется синхронизировать с вышестоящим репозиторием. +2. Выберите раскрывающийся список **Получить вышестоящий репозиторий**. + ![Раскрывающийся список "Получить вышестоящий репозиторий"](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. Просмотрите сведения о фиксациях из вышестоящего репозитория, а затем щелкните **Получить и объединить**. + ![Кнопка "Получить и объединить"](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} -If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. +Если изменения из вышестоящего репозитория вызывают конфликты, {% data variables.product.company_short %} предложит создать запрос на вытягивание для разрешения конфликтов. -## Syncing a fork branch with the {% data variables.product.prodname_cli %} +## Синхронизация ветви вилки с помощью {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %} Дополнительные сведения о {% data variables.product.prodname_cli %} см. в статье ["Общие сведения о {% data variables.product.prodname_cli %}"](/github-cli/github-cli/about-github-cli). -To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments. +Чтобы обновить удаленную вилку из родительского элемента, используйте подкоманду `gh repo sync -b BRANCHNAME` и укажите имена вилки и ветви в качестве аргументов. ```shell $ gh repo sync owner/cli-fork -b BRANCH_NAME ``` -If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. +Если изменения из вышестоящего репозитория вызывают конфликт, то {% data variables.product.prodname_cli %} не сможет синхронизироваться. Вы можете задать флаг `-force` для перезаписи целевой ветви. -## Syncing a fork branch from the command line +## Синхронизация ветви вилки из командной строки -Before you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git. For more information, see "[Configuring a remote repository for a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)." +Прежде чем синхронизировать вилку с вышестоящим репозиторием, необходимо настроить удаленный репозиторий, указывающий на вышестоящий репозиторий в Git. Дополнительные сведения см. в разделе [Настройка удаленного репозитория для вилки](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork). {% data reusables.command_line.open_the_multi_os_terminal %} -2. Change the current working directory to your local project. -3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. +2. Измените текущий рабочий каталог на локальный проект. +3. Получение ветвей и их соответствующих фиксаций из вышестоящего репозитория. Фиксации в `BRANCHNAME` будут храниться в локальной ветви `upstream/BRANCHNAME`. ```shell $ git fetch upstream @@ -68,14 +72,14 @@ Before you can sync your fork with an upstream repository, you must configure a > * [new branch] main -> upstream/main ``` -4. Check out your fork's local default branch - in this case, we use `main`. +4. Извлеките локальную ветвь вилки по умолчанию — в этом примере мы используем `main`. ```shell $ git checkout main > Switched to branch 'main' ``` -5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. +5. Объедините изменения из вышестоящей ветви по умолчанию ( в данном случае `upstream/main`) с локальной ветвью по умолчанию. Это приведет к синхронизации ветви вилки по умолчанию с вышестоящим репозиторием без потери локальных изменений. ```shell $ git merge upstream/main @@ -88,7 +92,7 @@ Before you can sync your fork with an upstream repository, you must configure a > create mode 100644 README.md ``` - If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation. + Если локальная ветвь не имеет уникальных фиксаций, Git выполнит быстрое перемещение вперед. Дополнительные сведения см. в статье [Базовое ветвление и слияние](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) в документации по Git. ```shell $ git merge upstream/main > Updating 34e91da..16c56ad @@ -96,10 +100,10 @@ Before you can sync your fork with an upstream repository, you must configure a > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) ``` - If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)." + Если локальная ветвь имела уникальные фиксации, возможно, потребуется устранить конфликты. Дополнительные сведения см. в разделе [Устранение конфликтов слияния](/github/collaborating-with-pull-requests/addressing-merge-conflicts). {% tip %} -**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). +**Совет.** При синхронизации вилки обновляется только локальная копия репозитория. Чтобы обновить вилку на {% data variables.location.product_location %}, необходимо [отправить изменения](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). {% endtip %} diff --git a/translations/ru-RU/content/rest/overview/libraries.md b/translations/ru-RU/content/rest/overview/libraries.md index ebabc4a96239..cd3bdb7fb6ad 100644 --- a/translations/ru-RU/content/rest/overview/libraries.md +++ b/translations/ru-RU/content/rest/overview/libraries.md @@ -11,22 +11,21 @@ versions: ghec: '*' topics: - API -ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c -ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa +ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58 +ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/21/2022 -ms.locfileid: '148179739' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148190064' --- -![The Gundamcat](/assets/images/gundamcat.png) +![Гандамкат](/assets/images/gundamcat.png) ## Octokit имеет множество вариантов Воспользуйтесь официальной библиотекой Octokit или выберите любую доступную стороннюю библиотеку. -- [Octokit.py](https://github.com/khornberg/octokit.py) → **Python** - **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb) -- **octokit.net → .NET** [](https://github.com/octokit/octokit.net) +- [octokit.net](https://github.com/octokit/octokit.net) → **.NET** - **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js) ## Сторонние библиотеки @@ -131,6 +130,7 @@ ms.locfileid: '148179739' |**github-flask**|[github-flask (официальный веб-сайт)](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/ru-RU/content/rest/overview/resources-in-the-rest-api.md b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md index 26f5282190e5..9a1a2900eae7 100644 --- a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md @@ -292,10 +292,10 @@ gem: >> tmpl.expand => "/notifications" - >> tmpl.expand :all => 1 + >> tmpl.expand all: 1 => "/notifications?all=1" - >> tmpl.expand :all => 1, :participating => 1 + >> tmpl.expand all: 1, participating: 1 => "/notifications?all=1&participating=1" [rfc]: https://datatracker.ietf.org/doc/html/rfc6570 diff --git a/translations/ru-RU/data/reusables/codespaces/stopping-a-codespace.md b/translations/ru-RU/data/reusables/codespaces/stopping-a-codespace.md index 007c23c74913..25b4c4806655 100644 --- a/translations/ru-RU/data/reusables/codespaces/stopping-a-codespace.md +++ b/translations/ru-RU/data/reusables/codespaces/stopping-a-codespace.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: 4bdcc6ff93e7671d4dc368fc44784c963f549aae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 1eac21c20c1be77fe00ea676714a835fdb2e0de7 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: MT ms.contentlocale: ru-RU -ms.lasthandoff: 11/09/2022 -ms.locfileid: "148159048" +ms.lasthandoff: 12/01/2022 +ms.locfileid: "148189891" --- -Вы можете остановить пространство кода в любой момент. При остановке пространства кода все выполняемые процессы останавливаются, и журнал терминала очищается. Все сохраненные изменения в пространстве кода по-прежнему будут доступны при следующем запуске. Если не остановить пространство кода явным образом, оно будет продолжать работать до истечения времени ожидания в результате бездействия. Дополнительные сведения см. в разделе [Жизненный цикл codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle#timeouts-for-github-codespaces). +Вы можете остановить пространство кода в любой момент. При остановке пространства кода все выполняемые процессы останавливаются, и журнал терминала очищается. Все сохраненные изменения в пространстве кода по-прежнему будут доступны при следующем запуске. Если не остановить пространство кода явным образом, оно будет продолжать работать до истечения времени ожидания в результате бездействия. Дополнительные сведения см. в разделе [Жизненный цикл codespace](/codespaces/getting-started/the-codespace-lifecycle#timeouts-for-github-codespaces). -Плата за ЦП взимается только с запуска codespace. Остановленное пространство кода влечет за собой только затраты на хранение. +Плата за использование ЦП взимается только при выполнении codespace. Остановленное codespace влечет за собой только затраты на хранение. Может потребоваться остановить и перезапустить пространство кода, чтобы применить к нему изменения. Например, при изменении типа виртуальной машины, используемой для пространства кода, необходимо остановить и перезапустить его, чтобы изменения вступили в силу. Вы также можете остановить пространство кода и перезапустить или удалить его, если возникла ошибка или произошло что-то непредвиденное.