diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md new file mode 100644 index 000000000000..1f90ae0e98f6 --- /dev/null +++ b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md @@ -0,0 +1,102 @@ +--- +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: '*' +type: how_to +topics: + - Codespaces + - Fundamentals + - Developer +shortTitle: Create a codespace from a template +miniTocMaxHeadingLevel: 3 +--- + +## 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 %} + +**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 %} + +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)." + +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. + +![Screenshot of the React template running in a codespace](/assets/images/help/codespaces/react-template.png) + +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 %} + +**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 %} + +## Creating a codespace from a {% data variables.product.company_short %} template + +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. Optionally, to view the template repository containing the files for a template, click the name of the template. + + ![Screenshot of the "Explore quick start templates" section, with "React" highlighted](/assets/images/help/codespaces/react-template-name.png) + +1. Under the template you want to launch, click **Use this template**. + + ![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 %} + +## Creating a codespace from a template repository + +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 %} + + {% note %} + + **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 %} + +## Publishing to a repository on {% data variables.product.product_name %} + +{% data reusables.codespaces.about-publishing-templates %} + +### Publishing from {% data variables.product.prodname_vscode_shortname %} + +{% data reusables.codespaces.publishing-template-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: + +- 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)"). + +### Publishing from {% data variables.product.prodname_dotcom_the_website %} + +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. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**. + + ![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**. + + ![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 + +- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" +- "[The codespace lifecycle](/codespaces/developing-in-codespaces/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/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md index 914857fdefed..746e40937570 100644 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md +++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md @@ -1,8 +1,8 @@ --- -title: Enabling GitHub Codespaces for your organization +title: Aktivieren von GitHub Codespaces für deine Organisation shortTitle: 'Enable {% data variables.product.prodname_codespaces %}' -intro: "You can control which users in your organization can use {% data variables.product.prodname_github_codespaces %} at the organization's expense." -permissions: "To alter an organization's billing settings, you must be an organization owner." +intro: 'Du kannst steuern, welche Benutzer in deiner Organisation {% data variables.product.prodname_github_codespaces %} auf Kosten der Organisation nutzen können.' +permissions: 'To alter an organization''s billing settings, you must be an organization owner.' redirect_from: - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization @@ -14,70 +14,69 @@ topics: - Codespaces - Billing - Administrator +ms.openlocfilehash: 992d744e04ae00db4d760b59a9d08d1700846998 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.translationtype: HT +ms.contentlocale: de-DE +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148158901' --- +## Informationen zum Aktivieren von {% data variables.product.prodname_github_codespaces %} für deine Organisation -## About enabling {% data variables.product.prodname_github_codespaces %} for your organization +Organisationsbesitzer können steuern, welche Benutzer in der Organisation Codespaces auf Kosten der Organisation erstellen und verwenden können. Informationen zu den Kosten findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces). -Organization owners can control which users in your organization can create and use codespaces at the organization's expense. For information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." +Nur Personen, die Änderungen an ein Repository pushen oder das Repository forken können, können einen Codespace für dieses Repository erstellen. Um Personen das Erstellen von Codespaces für Repositorys im Besitz deiner Organisation zu ermöglichen, musst du Folgendes ausführen: -Only people who can either push changes to a repository, or fork the repository, can create a codespace for that repository. To allow people to create codespaces for repositories owned by your organization, you must: +- Stelle sicher, dass Benutzer*innen mindestens Schreibzugriff auf die Repositorys haben, in denen sie einen Codespace verwenden möchten. Weitere Informationen findest du [Teams und Personen mit Zugriff auf dein Repository verwalten](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository). +- Stelle sicher, dass für deine Organisation keine Zulassungsliste für IP-Adressen aktiviert ist. Weitere Informationen findest du unter [Verwalten zulässiger IP-Adressen für deine Organisation](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization){% ifversion fpt %} in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation.{% else %}.{% endif %} -- Ensure that users have at least write access to the repositories where they want to use a codespace. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." -- Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +Damit Personen Codespaces erstellen können, die deiner Organisation in Rechnung gestellt werden, musst du Folgendes ausführen: -To allow people to create codespaces for which your organization will be billed, you must: +- [Festlegen eines Ausgabenlimits](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) +- [Auswählen der Personen, die Codespaces auf Kosten deiner Organisation erstellen können](#choose-who-can-create-codespaces-that-are-billed-to-your-organization) -- [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) -- [Choose who can create codespaces that are billed to your organization](#choose-who-can-create-codespaces-that-are-billed-to-your-organization) +{% ifversion fpt %} {% note %} -{% ifversion fpt %} -{% note %} +**Hinweis:** Wenn du verifizierte*r Kursleiter*in oder Lehrkraft bist, musst du {% data variables.product.prodname_github_codespaces %} von einem {% data variables.product.prodname_classroom %} aus aktivieren, um deinen {% data variables.product.prodname_codespaces %} Education-Vorteil zu nutzen. Weitere Informationen findest Du unter „[Verwenden von {% data variables.product.prodname_github_codespaces %} mit {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)“. -**Note:** If you are a verified educator or a teacher, you must enable {% data variables.product.prodname_github_codespaces %} from a {% data variables.product.prodname_classroom %} to use your {% data variables.product.prodname_codespaces %} Education benefit. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)." +{% endnote %} {% endif %} -{% endnote %} -{% endif %} +Standardmäßig kann ein Codespace nur auf das Repository zugreifen, aus dem er erstellt wurde. Wenn Codespaces in deiner Organisation auf andere Organisationsrepositorys zugreifen können sollen, auf die der Ersteller des Codespace Zugriff hat, findest du weitere Informationen unter [Verwalten des Repositoryzugriffs für die Codespaces deiner Organisation](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces). -By default, a codespace can only access the repository from which it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)." +## Auswählen der Personen, die Codespaces auf Kosten deiner Organisation erstellen können -## Choose who can create codespaces that are billed to your organization +{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.click-codespaces %} +1. Wähle unter „Abrechnung“ eine der folgenden Optionen aus: -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "Billing," select one of the following options: + * **Deaktiviert**: Deiner Organisation wird die Codespacenutzung nicht in Rechnung gestellt. Für die Repositorys deiner Organisation erstellte {% data variables.product.prodname_codespaces %} werden mit den einzelnen Benutzern abgerechnet, von denen sie erstellt werden. + * **Ausgewählte Mitglieder**: Von ausgewählten Mitgliedern für Repositorys deiner Organisation erstellte {% data variables.product.prodname_codespaces %} werden der Organisation in Rechnung gestellt. + * **Alle Mitglieder**: Von Mitgliedern deiner Organisation für Organisationsrepositorys erstellte {% data variables.product.prodname_codespaces %} werden der Organisation in Rechnung gestellt. + * **Alle Mitglieder und externe Mitarbeiter**: Von Organisationsmitgliedern und externen Mitarbeitern für Organisationsrepositorys erstellte {% data variables.product.prodname_codespaces %} werden der Organisation in Rechnung gestellt. - * **Disabled** - Your organization will not be charged for codespace usage. {% data variables.product.prodname_codespaces %} created for your organization's repositories will be billed to the individual users who create them. - * **Selected members** - {% data variables.product.prodname_codespaces %} created for your organization's repositories by selected members will be billed to the organization. - * **All members** - {% data variables.product.prodname_codespaces %} created for your organization's repositories by members of your organization will be billed to the organization. - * **All members and outside collaborators** - {% data variables.product.prodname_codespaces %} created for your organization's repositories by organization members and outside collaborators will be billed to the organization. - - ![Radio buttons for "Billing"](/assets/images/help/codespaces/codespaces-org-billing-settings.png) + ![Optionsfelder für „Abrechnung“](/assets/images/help/codespaces/codespaces-org-billing-settings.png) {% note %} - **Note:** When you select **All members and outside collaborators**, all outside collaborators who have been added to specific repositories can create and use {% data variables.product.prodname_codespaces %} for those repositories, and your organization will be billed for this usage. For more information on managing outside collaborators, see "[About outside collaborators](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization#about-outside-collaborators)." + **Hinweis**: Wenn du **Alle Mitglieder und externe Mitarbeiter** auswählst, können alle externen Mitarbeiter, die bestimmten Repositorys hinzugefügt wurden, {% data variables.product.prodname_codespaces %} für diese Repositorys auf Kosten deiner Organisation erstellen und verwenden. Weitere Informationen zum Verwalten externer Mitarbeiter*innen findest du unter [Informationen zu externen Mitarbeiter*innen](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization#about-outside-collaborators). {% endnote %} -1. Click **Save**. -1. If you chose **Selected members**, an input box is displayed for you to enter the names of users you want to select. +1. Klicke auf **Speichern**. +1. Wenn du **Ausgewählte Mitglieder** ausgewählt hast, wird ein Eingabefeld angezeigt, in dem du die Namen der gewünschten Benutzer eingeben kannst. - ![Input box for selecting users](/assets/images/help/codespaces/codespaces-org-billing-add-users.png) + ![Eingabefeld zum Auswählen von Benutzern](/assets/images/help/codespaces/codespaces-org-billing-add-users.png) -## Disabling {% data variables.product.prodname_codespaces %} for your organization +## Deaktivieren von {% data variables.product.prodname_codespaces %} für deine Organisation -You can prevent the creation and use of codespaces billable to your organization. +Du kannst die Erstellung und Verwendung von Codespaces, die deiner Organisation in Rechnung gestellt werden können, verhindern. {% data reusables.codespaces.codespaces-disabling-org-billing %} -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "Billing," select **Disabled**. +{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.click-codespaces %} +1. Wähle unter „Abrechnung“ die Option **Deaktiviert** aus. -## Setting a spending limit +## Festlegen eines Ausgabenlimits {% data reusables.codespaces.codespaces-spending-limit-requirement %} -For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +Informationen zum Verwalten und Ändern des Ausgabenlimits deines Kontos findest du unter [Verwalten deines Ausgabenlimits für {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces). diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md index 93a197c3eb55..4be3a6c6c448 100644 --- a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md +++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md @@ -1,27 +1,32 @@ --- -title: Syntax for GitHub's form schema -intro: 'You can use {% data variables.product.company_short %}''s form schema to configure forms for supported features.' +title: Syntax für das GitHub-Formularschema +intro: 'Du kannst mit dem Formularschema von {% data variables.product.company_short %} Formulare für unterstützte Features konfigurieren.' versions: fpt: '*' ghec: '*' miniTocMaxHeadingLevel: 3 topics: - Community +ms.openlocfilehash: 3a8a21f04582b87741ef80755e92fbc859921bb5 +ms.sourcegitcommit: 06d16bf9a5c7f3e7107f4dcd4d06edae5971638b +ms.translationtype: HT +ms.contentlocale: de-DE +ms.lasthandoff: 11/21/2022 +ms.locfileid: '148179669' --- - {% note %} -**Note:** {% data variables.product.company_short %}'s form schema is currently in beta and subject to change. +**Hinweis:** Das Formularschema von {% data variables.product.company_short %} befindet sich derzeit in der Betaphase und kann noch geändert werden. {% endnote %} -## About {% data variables.product.company_short %}'s form schema +## Informationen zum Formularschema von {% data variables.product.company_short %} -You can use {% data variables.product.company_short %}'s form schema to configure forms for supported features. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)." +Du kannst mit dem Formularschema von {% data variables.product.company_short %} Formulare für unterstützte Features konfigurieren. Weitere Informationen findest du unter [Konfigurieren von Issuevorlagen für dein Repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms). -A form is a set of elements for requesting user input. You can configure a form by creating a YAML form definition, which is an array of form elements. Each form element is a set of key-value pairs that determine the type of the element, the properties of the element, and the constraints you want to apply to the element. For some keys, the value is another set of key-value pairs. +Ein Formular ist ein Satz von Elementen zum Anfordern von Benutzereingaben. Du kannst ein Formular konfigurieren, indem du eine YAML-Formulardefinition erstellst, die ein Array von Formularelementen ist. Jedes Formularelement ist ein Satz von Schlüssel-Wert-Paaren, die den Typ des Elements, die Eigenschaften des Elements und die Einschränkungen bestimmen, die du auf das Element anwenden möchtest. Bei einigen Schlüsseln ist der Wert ein weiterer Satz von Schlüssel-Wert-Paaren. -For example, the following form definition includes four form elements: a text area for providing the user's operating system, a dropdown menu for choosing the software version the user is running, a checkbox to acknowledge the Code of Conduct, and Markdown that thanks the user for completing the form. +Die folgende Formulardefinition enthält beispielsweise vier Formularelemente: einen Textbereich für die Bereitstellung des Betriebssystems des Benutzers, ein Dropdownmenü zum Auswählen der Softwareversion, die der Benutzer ausführt, ein Kontrollkästchen, um die Verhaltensregeln zu bestätigen, und Markdown, um dem Benutzer zum Ausfüllen des Formulars zu danken. ```yaml{:copy} - type: textarea @@ -55,48 +60,48 @@ For example, the following form definition includes four form elements: a text a value: "Thanks for completing our form!" ``` -## Keys +## Tasten -For each form element, you can set the following keys. +Für jedes Formularelement kannst du die folgenden Schlüssel festlegen. -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | -| `type` | The type of element that you want to define. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | | -| `id` | The identifier for the element, except when `type` is set to `markdown`. {% data reusables.form-schema.id-must-be-unique %} If provided, the `id` is the canonical identifier for the field in URL query parameter prefills. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `attributes` | A set of key-value pairs that define the properties of the element. | Required | Map | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `validations` | A set of key-value pairs that set constraints on the element. | Optional | Map | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `type` | Der Typ des Elements, das du definieren möchtest. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | | +| `id` | Der Bezeichner für das Element, außer wenn `type` auf `markdown` gesetzt ist. {% data reusables.form-schema.id-must-be-unique %} Wenn angegeben, ist `id` der kanonische Bezeichner für das Feld im URL-Abfrageparameter. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `attributes` | Ein Satz von Schlüssel-Wert-Paaren, die die Eigenschaften des Elements definieren. | Erforderlich | Zuordnung | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `validations` | Ein Satz von Schlüssel-Wert-Paaren, die Einschränkungen für das Element festlegen. | Optional | Zuordnung | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -You can choose from the following types of form elements. Each type has unique attributes and validations. +Du hast die Wahl zwischen den folgenden Typen von Formularelementen. Jeder Typ hat eindeutige Attribute und Validierungen. -| Type | Description | +| type | BESCHREIBUNG | | ---- | ----------- | -| [`markdown`](#markdown) | Markdown text that is displayed in the form to provide extra context to the user, but is **not submitted**. | -| [`textarea`](#textarea) | A multi-line text field. | -| [`input`](#input) | A single-line text field. | -| [`dropdown`](#dropdown) | A dropdown menu. | -| [`checkboxes`](#checkboxes) | A set of checkboxes. | +| [`markdown`](#markdown) | Markdown-Text, der im Formular angezeigt wird, um dem Benutzer zusätzlichen Kontext zu bieten, jedoch **nicht übermittelt** wird. | +| [`textarea`](#textarea) | Ein mehrzeiliges Textfeld. | +| [`input`](#input) | Ein einzeiliges Textfeld. | +| [`dropdown`](#dropdown) | Ein Dropdownmenü. | +| [`checkboxes`](#checkboxes) | Ein Satz von Kontrollkästchen. | ### `markdown` -You can use a `markdown` element to display Markdown in your form that provides extra context to the user, but is not submitted. +Mit einem `markdown`-Element kannst du Markdown in deinem Formular anzuzeigen, um dem Benutzer zusätzlichen Kontext zu bieten, Markdown wird aber nicht übermittelt. -#### Attributes +#### Attribute {% data reusables.form-schema.attributes-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | -| `value` | The text that is rendered. Markdown formatting is supported. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `value` | Der Text, der gerendert wird. Markdown-Formatierung wird unterstützt. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | {% tip %} -**Tips:** YAML processing will treat the hash symbol as a comment. To insert Markdown headers, wrap your text in quotes. +**Tipp:** Die YAML-Verarbeitung behandelt das Hashsymbol als Kommentar. Um Markdown-Kopfzeilen einzufügen, schließe den Text in Anführungszeichen ein. -For multi-line text, you can use the pipe operator. +Für mehrzeiligen Text kannst du den Pipe-Operator verwenden. {% endtip %} -#### Example +#### Beispiel ```YAML{:copy} body: @@ -111,29 +116,29 @@ body: ### `textarea` -You can use a `textarea` element to add a multi-line text field to your form. Contributors can also attach files in `textarea` fields. +Du kannst mit einem `textarea`-Element deinem Formular ein mehrzeiliges Textfeld hinzufügen. Mitwirkende können auch Dateien in `textarea`-Feldern anfügen. -#### Attributes +#### Attribute {% data reusables.form-schema.attributes-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | -| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `description` | A description of the text area to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | -| `placeholder` | A semi-opaque placeholder that renders in the text area when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | -| `value` | Text that is pre-filled in the text area. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `render` | If a value is provided, submitted text will be formatted into a codeblock. When this key is provided, the text area will not expand for file attachments or Markdown editing. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | Languages known to {% data variables.product.prodname_dotcom %}. For more information, see [the languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). | +| `label` | Eine auch im Formular angezeigte kurze Beschreibung der erwarteten Benutzereingabe. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | Eine im Formular angezeigte Beschreibung des Textbereichs, die Kontext oder Anleitungen bereitstellt. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} | +| `placeholder` | Ein halbdurchsichtiger Platzhalter, der im Textbereich gerendert wird, wenn er leer ist. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} | +| `value` | Im Textbereich als Vorgabe angezeigter Text. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `render` | Wenn ein Wert angegeben wird, wird übermittelter Text in einen Codeblock formatiert. Wenn dieser Schlüssel bereitgestellt wird, wird der Textbereich nicht für Dateianlagen oder Markdown-Bearbeitung erweitert. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | Sprachen, die {% data variables.product.prodname_dotcom %} bekannt sind. Weitere Informationen findest du in der [YAML-Datei der Sprachen](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). | -#### Validations +#### Überprüfungen {% data reusables.form-schema.validations-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Example +#### Beispiel ```YAML{:copy} body: @@ -154,28 +159,28 @@ body: ### `input` -You can use an `input` element to add a single-line text field to your form. +Du kannst mit einem `input`-Element deinem Formular ein einzeiliges Textfeld hinzufügen. -#### Attributes +#### Attribute {% data reusables.form-schema.attributes-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | -| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `description` | A description of the field to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | -| `placeholder` | A semi-transparent placeholder that renders in the field when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | -| `value` | Text that is pre-filled in the field. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `label` | Eine auch im Formular angezeigte kurze Beschreibung der erwarteten Benutzereingabe. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | Eine im Formular angezeigte Beschreibung des Felds, die Kontext oder Anleitungen bereitstellt. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} | +| `placeholder` | Ein halbdurchsichtiger Platzhalter, der im Feld gerendert wird, wenn es leer ist. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} | +| `value` | Im Feld als Vorgabe angezeigter Text. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -#### Validations +#### Überprüfungen {% data reusables.form-schema.validations-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Example +#### Beispiel ```YAML{:copy} body: @@ -191,28 +196,28 @@ body: ### `dropdown` -You can use a `dropdown` element to add a dropdown menu in your form. +Mit einem `dropdown`-Element kannst du deinem Formular ein Dropdownmenü hinzufügen. -#### Attributes +#### Attribute {% data reusables.form-schema.attributes-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | -| `label` | A brief description of the expected user input, which is displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `description` | A description of the dropdown to provide extra context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | -| `multiple` | Determines if the user can select more than one option. | Optional | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} | -| `options` | An array of options the user can choose from. Cannot be empty and all choices must be distinct. | Required | String array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `label` | Eine im Formular angezeigte kurze Beschreibung der erwarteten Benutzereingabe. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | Eine im Formular angezeigte Beschreibung des Dropdownmenüs, die zusätzlichen Kontext oder Anleitungen bereitstellt. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} | +| `multiple` | Bestimmt, ob der Benutzer mehrere Optionen auswählen kann. | Optional | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} | +| `options` | Ein Array von Optionen, aus dem der Benutzer auswählen kann. Kann nicht leer sein, und alle Auswahlmöglichkeiten müssen eindeutig sein. | Erforderlich | Zeichenfolgenarray | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -#### Validations +#### Überprüfungen {% data reusables.form-schema.validations-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Example +#### Beispiel ```YAML{:copy} body: @@ -231,29 +236,29 @@ body: ### `checkboxes` -You can use the `checkboxes` element to add a set of checkboxes to your form. +Du kannst mit dem `checkboxes`-Element deinem Formular einen Satz von Kontrollkästchen hinzufügen. -#### Attributes +#### Attribute {% data reusables.form-schema.attributes-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | -| `label` | A brief description of the expected user input, which is displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -| `description` | A description of the set of checkboxes, which is displayed in the form. Supports Markdown formatting. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | -| `options` | An array of checkboxes that the user can select. For syntax, see below. | Required | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `label` | Eine im Formular angezeigte kurze Beschreibung der erwarteten Benutzereingabe. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | Eine im Formular angezeigte Beschreibung des Satzes von Kontrollkästchen. Unterstützt Markdown-Formatierung. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} | +| `options` | Ein Array von Kontrollkästchen, die der Benutzer auswählen kann. Syntax siehe unten. | Erforderlich | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | {% data reusables.form-schema.options-syntax %} -#### Validations +#### Überprüfungen {% data reusables.form-schema.validations-intro %} -| Key | Description | Required | Type | Default | Valid values | +| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte | | --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Example +#### Beispiel ```YAML{:copy} body: @@ -268,6 +273,6 @@ body: - label: Linux ``` -## Further reading +## Weiterführende Themen - [YAML](https://yaml.org) diff --git a/translations/de-DE/content/get-started/quickstart/github-glossary.md b/translations/de-DE/content/get-started/quickstart/github-glossary.md index 18a85238e5a7..daaa681b7108 100644 --- a/translations/de-DE/content/get-started/quickstart/github-glossary.md +++ b/translations/de-DE/content/get-started/quickstart/github-glossary.md @@ -1,6 +1,6 @@ --- -title: GitHub glossary -intro: 'This glossary introduces common Git and {% data variables.product.prodname_dotcom %} terminology.' +title: GitHub-Glossar +intro: 'Dieses Glossar führt in die gängige Git- und {% data variables.product.prodname_dotcom %}-Terminologie ein.' redirect_from: - /articles/github-glossary - /github/getting-started-with-github/github-glossary @@ -10,6 +10,12 @@ versions: ghes: '*' ghae: '*' ghec: '*' +ms.openlocfilehash: b8a436ed4e20133f1a2c4def572a60b73c48cf4d +ms.sourcegitcommit: c95a5c9bdf3ae54ad77b074739b262e7d0e8a077 +ms.translationtype: HT +ms.contentlocale: de-DE +ms.lasthandoff: 11/17/2022 +ms.locfileid: '148169582' --- {% for glossary in glossaries %} ### {{ glossary.term }} @@ -19,8 +25,8 @@ versions: --- -## Further reading +## Weiterführende Themen -- [The Official Git Glossary](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) -- [Git documentation](https://git-scm.com/doc) -- [Git command list](https://git-scm.com/docs) +- [Das offizielle Git-Glossar](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) +- [Git-Dokumentation](https://git-scm.com/doc) +- [Git-Befehlsliste](https://git-scm.com/docs) diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/about-tasklists.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/about-tasklists.md new file mode 100644 index 000000000000..be33064f0ba7 --- /dev/null +++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/about-tasklists.md @@ -0,0 +1,146 @@ +--- +title: Informationen zu Aufgabenlisten +intro: Mithilfe von Aufgabenlisten kannst du deine Issues in kleinere Unteraufgaben unterteilen. +versions: + feature: projects-v2-tasklists +miniTocMaxHeadingLevel: 3 +redirect_from: + - /early-access/issues/about-tasklists +ms.openlocfilehash: e35065ae4de634bb7a2da815e0a860c7c0b92234 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.translationtype: HT +ms.contentlocale: de-DE +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159709' +--- +{% data reusables.projects.tasklists-release-stage %} + +## Informationen zu Aufgabenlisten + +Aufgabenlisten ermöglichen die Unterstützung von Hierarchien für Issues auf {% data variables.product.product_name %}, damit du den Überblick über deine Issues behalten, deine Issues in kleinere Unteraufgaben unterteilen und neue Beziehungen zwischen deinen Issues erstellen kannst. + +Aufgabenlisten bauen auf der vorherigen Iteration von [Betaaufgabenlisten](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists) auf und bieten weiterhin die Möglichkeit, Elemente in Issues zu konvertieren, den Status einer Aufgabenliste anzuzeigen und eine Nachverfolgungsbeziehung zwischen Issues zu erstellen. + +Die Issues, die du deinen Aufgabenlisten hinzufügst, werden automatisch mit den zugewiesenen Personen und allen ggf. angewendeten Bezeichnungen aufgefüllt. + +![Abbildung: Aufgabenlisten in Aktion](/assets/images/help/issues/tasklist-hero.png) + +### Informationen zur Integration in {% data variables.projects.projects_v2 %} + + Im Seitenbereich deines Projekts wird die Position eines Issues in der Hierarchie innerhalb eines Breadcrumb-Menüs angezeigt, sodass du durch die Issues in deinen Aufgabenlisten navigieren kannst. Du kannst auch die Felder „Nachverfolgungen“ und „Nachverfolgt von“ hinzufügen, um die Beziehungen zwischen deinen Issues schnell zu erkennen. Weitere Informationen zu den Feldern „Nachverfolgungen“ und „Nachverfolgt von“ findest du [hier](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields). + +## Erstellen von Aufgabenlisten + +Eine Aufgabenliste kann durch Klicken auf die Schaltfläche „Aufgabenliste hinzufügen“ oder durch Bearbeiten des Markdown-Codes des Issues erstellt werden. + +### Erstellen einer Aufgabenliste mithilfe der Schaltfläche „Aufgabenliste hinzufügen“ + +Klicke unten in einer Issuebeschreibung, die du bearbeiten kannst, auf die Schaltfläche **{% octicon "checklist" aria-label="The checklist icon" %} Aufgabenliste hinzufügen**, um eine Aufgabenliste hinzuzufügen. + +![Screenshot: Schaltfläche zum Hinzufügen einer Aufgabenliste](/assets/images/help/issues/tasklist-add-tasklist-button.png) + +### Erstellen einer Aufgabenliste mithilfe von Markdown + +Du kannst Markdown in einer Issuebeschreibung verwenden, um eine Aufgabenliste zu erstellen. Erstelle einen Fenced-Code-Block, und schließe `[tasklist]` neben den öffnenden Graviszeichen ein. Stelle jedem Element `- [ ]` voran, und füge Links zu anderen Issues oder Text ein. Am Anfang deiner Liste kannst du optional einen Titel als Markdownheader einfügen. + +```` +```[tasklist] +### Tasks +- [ ] https://github.com/octo-org/octo-repo/issues/45 +- [ ] Draft issue title +``` +```` + +Dein Markdown-Code wird von {% data variables.product.product_name %} als Aufgabenliste gerendert. Anschließend kannst du über die Benutzeroberfläche Änderungen vornehmen sowie Issues hinzufügen und entwerfen. Wenn du die Issuebeschreibung bearbeitest, kannst du den Markdown-Code direkt ändern oder ihn kopieren, um die Aufgabenliste in anderen Issues zu duplizieren. + + + +## Hinzufügen von Issues zu einer Aufgabenliste + +1. Klicke unten in der Aufgabenliste auf **Element zu Aufgaben hinzufügen**. + + ![Screenshot: Schaltfläche „Element zu Aufgaben hinzufügen“](/assets/images/help/issues/add-new-tasklist-button.png) + +1. Wähle das Issue aus, das du deiner Aufgabenliste hinzufügen möchtest. + + * Wenn du ein kürzlich aktualisiertes Issue aus dem Repository hinzufügen möchtest, kannst du in der Dropdownliste auf das Issue klicken oder es mithilfe der Pfeiltasten auswählen und anschließend die EINGABETASTE drücken. + + ![Screenshot: Aktuelle Issues](/assets/images/help/issues/select-recent-issue.png) + + * Um nach einem Issue im Repository zu suchen, beginne mit der Eingabe des Titels oder der Nummer des Issues, und klicke auf das Ergebnis, oder wähle es mithilfe der Pfeiltasten aus, und drücke anschließend die EINGABETASTE. + + ![Screenshot: Suchen nach einem Issue](/assets/images/help/issues/search-for-issue.png) + + * Wenn du ein Issue direkt unter Verwendung seiner URL hinzufügen möchtest, füge die URL eines Issues ein, und drücke anschließend die EINGABETASTE. + + ![Screenshot: Eingefügte Issue-URL](/assets/images/help/issues/paste-issue-url.png) + + +## Erstellen von Issueentwürfen in einer Aufgabenliste + +Mit Issueentwürfen kannst du schnell Ideen erfassen und sie später in Issues konvertieren. Im Gegensatz zu Issues und Pull Requests, auf die von deinen Repositorys aus verwiesen wird, sind Issueentwürfe nur in deiner Aufgabenliste vorhanden. + +1. Klicke unten in der Aufgabenliste auf **Element zu Aufgaben hinzufügen**. + + ![Screenshot: Schaltfläche „Element zu Aufgaben hinzufügen“](/assets/images/help/issues/add-new-tasklist-button.png) + +1. Gibt den Titel deines Issueentwurfs ein, und drücke die EINGABETASTE. + + ![Screenshot: Titel eines Issueentwurfs](/assets/images/help/issues/add-draft-issue-to-tasklist.png) + + +## Konvertieren von Issueentwürfen in Issues in einer Aufgabenliste + +Du kannst Issueentwürfe in Issues konvertieren. Issues werden im gleichen Repository erstellt wie das übergeordnete Issue der Aufgabenliste. + +1. Klicke neben dem Issueentwurf, den du konvertieren möchtest, auf {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}. + + ![Screenshot des Menüsymbols](/assets/images/help/issues/tasklist-item-kebab.png) + +1. Klicke auf **In Issue konvertieren**. + + ![Screenshot: Option „In Issue konvertieren“](/assets/images/help/issues/tasklist-convert-to-issue.png) + + +## Entfernen eines Issues oder Issueentwurfs aus einer Aufgabenliste + +Du kannst Issues und Issueentwürfe aus deiner Aufgabenliste entfernen. Issues, die aus einer Aufgabenliste entfernt werden, werden nicht aus dem Repository entfernt. + +1. Klicke neben dem Issueentwurf, den du entfernen möchtest, auf {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}. + + ![Screenshot des Menüsymbols](/assets/images/help/issues/tasklist-item-kebab.png) + +1. Klicke im Menü auf **Entfernen**. + + ![Screenshot: Option „Entfernen“](/assets/images/help/issues/tasklist-remove.png) + +## Ändern des Titels einer Aufgabenliste + +Wenn du eine neue Aufgabenliste erstellst, lautet der Titel standardmäßig „Aufgaben“. Du kannst den Titel ändern, indem du den Markdown-Code des Issues bearbeitest. + +1. Klicke rechts oben im Issuetext auf {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}. + + ![Screenshot: Position des Menüsymbols](/assets/images/help/issues/comment-menu.png) + +1. Klicke im Menü auf **Bearbeiten**. + + ![Screenshot: Bearbeitungsoption](/assets/images/help/issues/comment-menu-edit.png) + +1. Ändere den Header im Fenced-Code-Block in deinen neuen Titel. Ändere beispielsweise `### Tasks` in `### My new title`. + + ![Screenshot: Bearbeitungsoption](/assets/images/help/issues/edit-tasklist-title.png) + +1. Klicke auf **Kommentar aktualisieren**. + +## Kopieren einer Aufgabenliste + +Wenn du deine Aufgabenliste mithilfe der Option „Markdown kopieren“ kopierst, kopiert {% data variables.product.product_name %} Markdown in die Zwischenablage und schließt den Namen des Issues ein, sodass du die Aufgabenliste außerhalb von GitHub ohne Kontextverlust einfügen kannst. + +1. Klicke rechts oben in deiner Aufgabenliste auf {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}. + + ![Screenshot des Menüsymbols](/assets/images/help/issues/tasklist-kebab.png) + +1. Klicke im Menü auf **Markdown kopieren**. + + ![Screenshot: Option „Markdown kopieren“](/assets/images/help/issues/tasklist-copy-markdown.png) + diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index f52573bdd68d..44a3b5732019 100644 --- a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -15,12 +15,12 @@ topics: - Organizations - Teams shortTitle: Roles in an organization -ms.openlocfilehash: 960f6f701ad524220e9e79ada04fa9e4d30b8e9f -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: c6c345e3d1f0fb2c49aa55e79346bc4ac6567885 +ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 ms.translationtype: HT ms.contentlocale: de-DE -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148108286' +ms.lasthandoff: 11/09/2022 +ms.locfileid: '148159173' --- ## Informationen zu Rollen {% data reusables.organizations.about-roles %} @@ -65,7 +65,7 @@ Wenn deine Organisation über ein Sicherheitsteam verfügt, kannst du mit der Ro ### {% data variables.product.prodname_github_app %}-Managers Standardmäßig können nur Organisationsbesitzer die Einstellungen von {% data variables.product.prodname_github_apps %} im Besitz einer Organisation verwalten. Wenn du weiteren Benutzern die Berechtigung zur Verwaltung von {% data variables.product.prodname_github_apps %} im Besitz einer Organisation erteilen möchtest, kann ihnen ein Besitzer Managerberechtigungen für {% data variables.product.prodname_github_app %} zuweisen. -Wenn du einen Benutzer/eine Benutzerin zum {% data variables.product.prodname_github_app %}-Manager in deiner Organisation ernennst, kannst du ihnen Zugriff auf die Verwaltung der Einstellungen einzelner oder aller {% data variables.product.prodname_github_apps %} im Besitz der Organisation gewähren. Weitere Informationen finden Sie unter +Wenn du einen Benutzer/eine Benutzerin zum {% data variables.product.prodname_github_app %}-Manager in deiner Organisation ernennst, kannst du ihnen Zugriff auf die Verwaltung der Einstellungen einzelner oder aller {% data variables.product.prodname_github_apps %} im Besitz der Organisation gewähren. Weitere Informationen findest du unter - [Hinzufügen von GitHub-App-Manager*innen zu deiner Organisation](/articles/adding-github-app-managers-in-your-organization) - [Entfernen von GitHub-App-Manager*innen aus deiner Organisation](/articles/removing-github-app-managers-from-your-organization) @@ -80,7 +80,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da {% ifversion fpt or ghec %} -| Organisationsberechtigung | Besitzer | Member | Moderatoren | Abrechnungsmanager | Sicherheitsmanager | +| Organisationsberechtigung | Besitzer | Members | Moderatoren | Abrechnungsmanager | Sicherheitsmanager | |:------------------------|:------:|:-------:|:----------:|:----------------:|:-----------------:| | Erstellen von Repositorys (weitere Informationen findest du unter [Einschränken der Erstellung von Repositorys in deiner Organisation](/articles/restricting-repository-creation-in-your-organization)) | **X** | **X** | **X** | | **X** | | Abrechnungsinformationen anzeigen und bearbeiten | **X** | | | **X** | | @@ -121,7 +121,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da | Zuordnen deines Sponsorings zu einer anderen Organisation (weitere Informationen findest du unter [Zuordnen von Sponsorings zu deiner Organisation](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)) | **X** | | | | | | Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites aus Repositorys in der Organisation (weitere Informationen findest du unter [Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für deine Organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)) | **X** | | | | | | Verwalten von Sicherheits- und Analyseeinstellungen (weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)) | **X** | | | | **X** | -| Anzeigen der Sicherheitsübersicht für die Organisation (Informationen unter [Informationen zur Sicherheitsübersicht](/code-security/security-overview/about-the-security-overview)) | **X** | | | | **X** |{% ifversion ghec %} +| Anzeigen der Sicherheitsübersicht für die Organisation (siehe [Informationen zu Sicherheitsübersichten](/code-security/security-overview/about-the-security-overview)) | **X** | | | | **X** |{% ifversion ghec %} | Aktivieren und Erzwingen der [einmaligen SAML-Anmeldung](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | | | [Verwalten des SAML-Benutzerzugriffs auf deine Organisation](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | | | Verwalten der SSH-Zertifizierungsstellen einer Organisation (weitere Informationen findest du unter [Verwalten der SSH-Zertifizierungsstellen deiner Organisation](/articles/managing-your-organizations-ssh-certificate-authorities)) | **X** | | | | |{% endif %} @@ -145,7 +145,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da {% elsif ghes or ghae %} -| Aktion in der Organisation | Besitzer | Member | Sicherheitsmanager | +| Aktion in der Organisation | Besitzer | Members | Sicherheitsmanager | |:--------------------|:------:|:-------:|:-------:| | Personen zum Beitritt zur Organisation einladen | **X** | | | | Einladungen zum Beitritt zu der Organisation bearbeiten und zurückziehen | **X** | | | @@ -167,7 +167,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da | Kann die Rolle des *Maintainers für ein Team* zugewiesen werden | **X** | **X** | **X** | | Repositorys übertragen | **X** | | | | Verwalten von Sicherheits- und Analyseeinstellungen (weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)) | **X** | | **X** |{% ifversion ghes %} -| Anzeigen der Sicherheitsübersicht für die Organisation (Informationen unter [Informationen zur Sicherheitsübersicht](/code-security/security-overview/about-the-security-overview)) | **X** | | **X** |{% endif %}{% ifversion ghes %} +| Anzeigen der Sicherheitsübersicht für die Organisation (siehe [Informationen zu Sicherheitsübersichten](/code-security/security-overview/about-the-security-overview)) | **X** | | **X** |{% endif %}{% ifversion ghes %} | Verwalten von {% data variables.product.prodname_dependabot_security_updates %} (Informationen unter [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)) | **X** | | **X** |{% endif %} | Verwalten der SSH-Zertifizierungsstellen einer Organisation (weitere Informationen findest du unter [Verwalten der SSH-Zertifizierungsstellen deiner Organisation](/articles/managing-your-organizations-ssh-certificate-authorities)) | **X** | | | | Erstellen von Projektboards (Informationen unter [Berechtigungen für Projektboards einer Organisation](/articles/project-board-permissions-for-an-organization)) | **X** | **X** | **X** | @@ -191,7 +191,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da {% else %} -| Aktion in der Organisation | Besitzer | Member | +| Aktion in der Organisation | Besitzer | Members | |:--------------------|:------:|:-------:| | Personen zum Beitritt zur Organisation einladen | **X** | | | Einladungen zum Beitritt zu der Organisation bearbeiten und zurückziehen | **X** | | @@ -231,7 +231,7 @@ Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Da {% endif %} -## Weitere Informationsquellen +## Weiterführende Themen - [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization) - [Projektboardberechtigungen für eine Organisation](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization) diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md index 5450d81b0aab..3496f599c7b0 100644 --- a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md +++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md @@ -1,6 +1,6 @@ --- -title: About READMEs -intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.' +title: Informationen zu README-Dateien +intro: 'Du kannst eine README-Datei zu Deinem Repository hinzufügen, um anderen Personen mitzuteilen, warum Dein Projekt nützlich ist, was sie mit Deinem Projekt machen können und wie sie es nutzen können.' redirect_from: - /articles/section-links-on-readmes-and-blob-pages - /articles/relative-links-in-readmes @@ -14,25 +14,31 @@ versions: ghec: '*' topics: - Repositories +ms.openlocfilehash: 146f1a33eb4de224625b9603b27d2f383e55c54d +ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e +ms.translationtype: HT +ms.contentlocale: de-DE +ms.lasthandoff: 11/14/2022 +ms.locfileid: '148163336' --- -## About READMEs +## Informationen zu README-Dateien {% data reusables.repositories.about-READMEs %} -For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." +Weitere Informationen zur Bereitstellung von Richtlinien für Dein Projekt findest Du unter {% ifversion fpt or ghec %}"[Hinzufügen von Verhaltensregeln zu Deinem Projekt](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" und {% endif %}"[Einrichten Deines Projekts für hilfreiche Beiträge](/communities/setting-up-your-project-for-healthy-contributions)". -A README is often the first item a visitor will see when visiting your repository. README files typically include information on: -- What the project does -- Why the project is useful -- How users can get started with the project -- Where users can get help with your project -- Who maintains and contributes to the project +Die README-Datei ist oft das erste Element, das ein Benutzer beim Besuch Deines Repositorys sieht. README-Dateien enthalten in der Regel folgende Informationen: +- Was ist die Aufgabe des Projekts? +- Warum ist das Projekt sinnvoll? +- Wie können Benutzer am Projekt mitwirken? +- Wo erhalten Benutzer Hilfe zu Ihrem Projekt? +- Wer verwaltet das Projekt und trägt dazu bei? -If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors. +Wenn Du Deine README-Datei im ausgeblendeten `.github`, im Stamm oder im `docs`-Verzeichnis Deines Repositorys ablegst, erkennt {% data variables.product.product_name %} Deine README-Datei und stellt sie automatisch den Besuchern des Repositorys zur Verfügung. -If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory. +Enthält ein Repository mehrere README-Dateien, wird die angezeigte Datei aus Speicherorten in der folgenden Reihenfolge ausgewählt: das `.github`-Verzeichnis, dann das Stammverzeichnis des Repositorys und schließlich das `docs`-Verzeichnis. -![Main page of the github/scientist repository and its README file](/assets/images/help/repository/repo-with-readme.png) +![Hauptseite des github/scientist-Repositorys und seiner README-Datei](/assets/images/help/repository/repo-with-readme.png) {% ifversion fpt or ghes or ghec %} @@ -40,30 +46,28 @@ If a repository contains more than one README file, then the file shown is chose {% endif %} -![README file on your username/username repository](/assets/images/help/repository/username-repo-with-readme.png) +![README-Datei zu Deinem Benutzernamen/Benutzernamen-Repository](/assets/images/help/repository/username-repo-with-readme.png) -## Auto-generated table of contents for README files +## Automatisch generiertes Inhaltsverzeichnis für README-Dateien -For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %} menu icon at the top left of the rendered page. +Für die gerenderte Ansicht einer Markdown-Datei in einem Repository einschließlich README-Dateien generiert {% data variables.product.product_name %} automatisch ein Inhaltsverzeichnis basierend auf Abschnittsüberschriften. Du kannst das Inhaltsverzeichnis für eine README-Datei anzeigen, indem Du oben links neben der gerenderten Seite auf das Menüsymbol {% octicon "list-unordered" aria-label="The unordered list icon" %} klickst. -![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png) +![README-Datei mit automatisch generiertem Inhaltsverzeichnis](/assets/images/help/repository/readme-automatic-toc.png) -## Section links in README files and blob pages +## Links zu Abschnitten in README-Dateien und auf Blob-Seiten {% data reusables.repositories.section-links %} -## Relative links and image paths in README files +## Relative Links und Bildpfade in README-Dateien {% data reusables.repositories.relative-links %} ## Wikis -A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)." +Eine README-Datei sollte nur die Informationen enthalten, die Entwickler für ihre ersten Schritte benötigen und die für ihr Projekt relevant sind. Längere Dokumentationen eignen sich am besten für Wikis. Weitere Informationen findest Di unter [Informationen zu Wikis](/communities/documenting-your-project-with-wikis/about-wikis). -## Further reading +## Weiterführende Themen -- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)" -- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" -{%- ifversion fpt or ghec %} -- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)" -{%- endif %} +- [Hinzufügen einer Datei zu einem Repository](/articles/adding-a-file-to-a-repository) +- [Lesbarmachen von Infodateien](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md) von 18F {%- ifversion fpt or ghec %} +- [Hinzufügen eines Badges „In GitHub Codespaces öffnen“](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge) {%- endif %} diff --git a/translations/de-DE/data/reusables/actions/ref-description.md b/translations/de-DE/data/reusables/actions/ref-description.md index 50c03dfc790e..9aab148fbc1d 100644 --- a/translations/de-DE/data/reusables/actions/ref-description.md +++ b/translations/de-DE/data/reusables/actions/ref-description.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: b4949218acc89828772bf2bea3998dfde3a10e95 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 298bcacbb02a443ae929ddcd48d9d9cd4bebd41a +ms.sourcegitcommit: 99eb4456062aea31ca381977396417cf92e5798d ms.translationtype: HT ms.contentlocale: de-DE -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147079962" +ms.lasthandoff: 11/21/2022 +ms.locfileid: "148179612" --- -Das Branch- oder Tag-Ref, das den Workflow-Lauf ausgelöst hat. Bei Workflows, die durch `push` ausgelöst wurden, ist dies das Branch- oder Tag-Ref, das gepusht wurde. Bei Workflows, die von `pull_request` ausgelöst werden, ist dies der Branch für das Mergen des Pull Requests. Bei Workflows, die von `release` ausgelöst werden, ist dies das erstellte Releasetag. Bei anderen Triggern handelt es sich um das Branch- oder Tag-Ref, das die Workflowausführung ausgelöst hat. Es wird nur festgelegt, wenn für den Ereignistyp ein Branch oder ein Tag verfügbar ist. Das Ref ist vollständig gebildet, d.h. für Branches ist das Format `refs/heads/`, für Pull Requests `refs/pull//merge` und für Tags `refs/tags/`. Beispiel: `refs/heads/feature-branch-1`. +Das vollständig geformte Ref des Branch- oder Tagnamens, der die Workflowausführung ausgelöst hat. Bei Workflows, die durch `push` ausgelöst wurden, ist dies das Branch- oder Tag-Ref, das gepusht wurde. Bei Workflows, die von `pull_request` ausgelöst werden, ist dies der Branch für das Mergen des Pull Requests. Bei Workflows, die von `release` ausgelöst werden, ist dies das erstellte Releasetag. Bei anderen Triggern handelt es sich um das Branch- oder Tag-Ref, das die Workflowausführung ausgelöst hat. Es wird nur festgelegt, wenn für den Ereignistyp ein Branch oder ein Tag verfügbar ist. Das Ref ist vollständig gebildet, d.h. für Branches ist das Format `refs/heads/`, für Pull Requests `refs/pull//merge` und für Tags `refs/tags/`. Beispiel: `refs/heads/feature-branch-1`. \ No newline at end of file diff --git a/translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index 8ddb21e79d7e..9d5bb2b672c3 100644 --- a/translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -1,7 +1,7 @@ --- -title: About SAML for enterprise IAM +title: À propos de SAML pour la gestion des identités et des accès d’entreprise shortTitle: About SAML for IAM -intro: 'You can use SAML single sign-on (SSO) {% ifversion ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.location.product_location %}{% elsif ghae %}to {% data variables.location.product_location %}{% endif %}.' +intro: 'Vous pouvez utiliser l’authentification unique SAML {% ifversion ghae %}et SCIM (System for Cross-domain Identity Management) {% endif %}pour gérer de façon centralisée l’accès aux organisations {% ifversion ghec %}appartenant à votre entreprise {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}à {% data variables.location.product_location %}{% elsif ghae %}à {% data variables.location.product_location %}{% endif %}.' versions: ghec: '*' ghes: '*' @@ -22,41 +22,46 @@ redirect_from: - /admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise - /admin/identity-and-access-management/using-saml-for-enterprise-iam/about-identity-and-access-management-for-your-enterprise +ms.openlocfilehash: d719ef81948cef75018b0976fc97ef45c267469f +ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/22/2022 +ms.locfileid: '148180028' --- - -## About SAML SSO for {% ifversion ghec or ghae %}your enterprise on {% endif %}{% ifversion ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} +## À propos de l’authentification unique SAML pour {% ifversion ghec or ghae %}votre entreprise sur {% endif %}{% ifversion ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} {% ifversion ghec %} -If your enterprise members manage their own user accounts on {% data variables.location.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} +Si les membres de votre entreprise gèrent leurs propres comptes d’utilisateur sur {% data variables.location.product_location %}, vous pouvez configurer l’authentification SAML comme restriction d’accès supplémentaire pour votre entreprise ou votre organisation. {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.saml-accounts %} -{% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." +{% data reusables.saml.about-saml-enterprise-accounts %} Pour plus d’informations, consultez « [Configuration d’une authentification unique (SSO) SAML pour votre entreprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise). » -Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." +Vous pouvez également provisionner et gérer les comptes des membres de votre entreprise avec {% data variables.product.prodname_emus %}. Pour vous aider à déterminer si l’authentification unique SAML ou {% data variables.product.prodname_emus %} constitue la meilleure solution pour votre entreprise, consultez « [À propos de l’authentification pour votre entreprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise) ». -{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)." +{% data reusables.enterprise-accounts.about-recovery-codes %} Pour plus d’informations, consultez « [Gestion des codes de récupération pour votre entreprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise) ». -After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. +Après avoir activé l’authentification unique SAML, selon le fournisseur d’identité que vous utilisez, vous pouvez activer des fonctionnalités de gestion des identités et des accès supplémentaires. -If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." +Si vous utilisez Azure AD comme fournisseur d’identité, vous pouvez utiliser la synchronisation d’équipe pour gérer l’appartenance à l’équipe au sein de chaque organisation. {% data reusables.identity-and-permissions.about-team-sync %} Pour plus d’informations, consultez « [Gestion de la synchronisation d’équipe pour les organisations dans votre compte d’entreprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise) ». {% note %} -**Note:** You cannot use SCIM at the enterprise level unless your enterprise is enabled for {% data variables.product.prodname_emus %}. +**Remarque :** Vous ne pouvez pas utiliser SCIM au niveau de l’entreprise, sauf si votre entreprise est activée pour {% data variables.product.prodname_emus %}. {% endnote %} -{% 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)." +{% 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) ». {% elsif ghes %} -SAML SSO allows people to authenticate and access {% data variables.location.product_location %} through an external system for identity management. +L’authentification unique SAML permet aux utilisateurs de s’authentifier et d’accéder à {% data variables.location.product_location %} via un système externe de gestion des identités. -SAML is an XML-based standard for authentication and authorization. When you configure SAML for {% data variables.location.product_location %}, the external system for authentication is called an identity provider (IdP). Your instance acts as a SAML service provider (SP). For more information about the SAML standard, see [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) on Wikipedia. +SAML est un standard basé sur XML pour l’authentification et l’autorisation. Quand vous configurez SAML pour {% data variables.location.product_location %}, le système externe d’authentification s’appelle un fournisseur d’identité (IdP). Votre instance fait office de fournisseur de service SAML. Pour plus d’informations sur la norme SAML, consultez [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) sur Wikipédia. -For more information about the configuration of SAML SSO on {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)." +Pour plus d’informations sur la configuration de l’authentification unique SAML sur {% data variables.product.product_name %}, consultez « [Configuration de l’authentification unique SAML pour votre entreprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise) ». {% data reusables.saml.saml-ghes-account-revocation %} @@ -68,23 +73,23 @@ For more information about the configuration of SAML SSO on {% data variables.pr {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.location.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." +Après avoir configuré l’application pour {% data variables.product.product_name %} sur votre IdP, vous pouvez provisionner l’accès à {% data variables.location.product_location %} en affectant l’application aux utilisateurs et groupes sur votre IdP. Pour plus d’informations sur l’authentification unique SAML pour {% data variables.product.product_name %}, consultez « [Configuration de l’authentification unique SAML pour votre entreprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise) ». -{% 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) ». -To learn how to configure both authentication and user provisioning for {% data variables.location.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." +Pour savoir comment configurer l’authentification et le provisionnement d’utilisateurs pour {% data variables.location.product_location %} avec votre IdP spécifique, consultez « [Configuration de l’authentification et du provisionnement avec votre fournisseur d’identité](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider) ». {% endif %} -## Supported IdPs +## Fournisseurs d’identité pris en charge {% ifversion ghec %} -We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. +Nous testons et prenons officiellement en charge les fournisseurs d’identité suivants. Pour l’authentification unique SAML, nous offrons une prise en charge limitée pour tous les fournisseurs d’identité qui implémentent la norme SAML 2.0. Pour plus d’informations, consultez le [Wiki SAML](https://wiki.oasis-open.org/security) sur le site web OASIS. -IdP | SAML | Team synchronization | +Fournisseur d’identité | SAML | Synchronisation d’équipe | --- | :--: | :-------: | -Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} | Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | @@ -97,7 +102,7 @@ Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% ifversion ghes > 3.3 %} -If your IdP supports encrypted assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process. +Si votre IdP prend en charge les assertions chiffrées, vous pouvez configurer des assertions chiffrées sur {% data variables.product.product_name %} pour renforcer la sécurité durant le processus d’authentification. {% endif %} @@ -105,7 +110,7 @@ If your IdP supports encrypted assertions, you can configure encrypted assertion {% elsif ghae %} -The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}. +Les fournisseurs d’identité suivants sont officiellement pris en charge pour l’intégration à {% data variables.product.prodname_ghe_managed %}. {% data reusables.saml.okta-ae-sso-beta %} @@ -115,16 +120,14 @@ The following IdPs are officially supported for integration with {% data variabl {% ifversion ghae %} -## Mapping {% data variables.product.prodname_ghe_managed %} teams to Okta groups +## Mappage des équipes {% data variables.product.prodname_ghe_managed %} aux groupes Okta -If you use Okta as your IdP, you can map your Okta groups to teams on {% data variables.product.product_name %}. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." +Si vous utilisez Okta en tant que fournisseur d’identité, vous pouvez mapper vos groupes Okta aux équipes sur {% data variables.product.product_name %}. Pour plus d’informations, consultez « [Mappage de groupes Okta à des équipes](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) ». {% endif %} -## Further reading +## Pour aller plus loin -- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website -- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website -{%- ifversion ghae %} -- "[Restricting network traffic to your enterprise with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" -{%- endif %} +- [Wiki SAML](https://wiki.oasis-open.org/security) sur le site web OASIS +- [Système de gestion des identités inter-domaines : protocole (RFC 7644)](https://tools.ietf.org/html/rfc7644) sur le site web IETF {%- ifversion ghae %} +- « [Restriction du trafic réseau vers votre entreprise avec une liste d’adresses IP autorisées](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list) » {%- endif %} diff --git a/translations/fr-FR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/fr-FR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md index 15837294e8f6..1973b5d01161 100644 --- a/translations/fr-FR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md +++ b/translations/fr-FR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md @@ -1,6 +1,6 @@ --- -title: Telling Git about your signing key -intro: 'To sign commits locally, you need to inform Git that there''s a GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or X.509 key you''d like to use.' +title: Informer Git de l’utilisation de votre clé de signature +intro: 'Pour signer les commits localement, vous devez informer Git qu’il y a une clé GPG{% ifversion ssh-commit-verification %}, SSH{% endif %} ou X.509 que vous voulez utiliser.' redirect_from: - /articles/telling-git-about-your-gpg-key - /articles/telling-git-about-your-signing-key @@ -15,38 +15,39 @@ topics: - Identity - Access management shortTitle: Tell Git your signing key +ms.openlocfilehash: d70911bdf3ff5de93537f7c9acb1374a4f2c90e3 +ms.sourcegitcommit: aded2711e14a0c2473049d3d7e05c82a74e4c634 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/21/2022 +ms.locfileid: '148179948' --- {% mac %} -## Telling Git about your GPG key +## Informer Git de l’utilisation de votre clé GPG -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +Si vous utilisez une clé GPG qui correspond à votre identité de commiteur et à votre adresse e-mail vérifiée associées à votre compte sur {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, vous pouvez commencer à signer des commits et des étiquettes. {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +Si vous n’avez pas de clé GPG qui correspond à votre identité de commiteur, vous devez associer un e-mail à une clé existante. Pour plus d’informations, consultez « [Association d’un e-mail à votre clé GPG](/articles/associating-an-email-with-your-gpg-key) ». {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +Si vous avez plusieurs clés GPG, vous devez indiquer à Git laquelle utiliser. -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} -1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file: +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} +1. Si vous n’utilisez pas la suite GPG, exécutez la commande suivante dans l’interpréteur de commandes `zsh` pour ajouter la clé GPG à votre fichier `.zshrc`, s’il existe, ou votre fichier `.zprofile` : ```shell $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \ else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi ``` - Alternatively, if you use the `bash` shell, run this command: + Vous utilisez l’interpréteur de commandes `bash`, vous pouvez également exécuter cette commande : ```shell $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \ else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi ``` -1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/): +1. Si vous le souhaitez, pour être invité à entrer un code PIN ou une phrase secrète quand c’est nécessaire, installez `pinentry-mac`. Par exemple, avec [Homebrew](https://brew.sh/) : ```shell $ brew install pinentry-mac $ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf @@ -57,69 +58,56 @@ If you have multiple GPG keys, you need to tell Git which one to use. {% windows %} -## Telling Git about your GPG key +## Informer Git de l’utilisation de votre clé GPG -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +Si vous utilisez une clé GPG qui correspond à votre identité de commiteur et à votre adresse e-mail vérifiée associées à votre compte sur {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, vous pouvez commencer à signer des commits et des étiquettes. {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +Si vous n’avez pas de clé GPG qui correspond à votre identité de commiteur, vous devez associer un e-mail à une clé existante. Pour plus d’informations, consultez « [Association d’un e-mail à votre clé GPG](/articles/associating-an-email-with-your-gpg-key) ». {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +Si vous avez plusieurs clés GPG, vous devez indiquer à Git laquelle utiliser. -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} {% endwindows %} {% linux %} -## Telling Git about your GPG key +## Informer Git de l’utilisation de votre clé GPG -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +Si vous utilisez une clé GPG qui correspond à votre identité de commiteur et à votre adresse e-mail vérifiée associées à votre compte sur {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, vous pouvez commencer à signer des commits et des étiquettes. {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +Si vous n’avez pas de clé GPG qui correspond à votre identité de commiteur, vous devez associer un e-mail à une clé existante. Pour plus d’informations, consultez « [Association d’un e-mail à votre clé GPG](/articles/associating-an-email-with-your-gpg-key) ». {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +Si vous avez plusieurs clés GPG, vous devez indiquer à Git laquelle utiliser. -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} -1. To add your GPG key to your `.bashrc` startup file, run the following command: +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} +1. Pour ajouter votre clé GPG à votre fichier de démarrage `.bashrc`, exécutez la commande suivante : ```bash $ [ -f ~/.bashrc ] && echo 'export GPG_TTY=$(tty)' >> ~/.bashrc ``` -{% endlinux %} -{% ifversion ssh-commit-verification %} +{% endlinux %} {% ifversion ssh-commit-verification %} -## Telling Git about your SSH key +## Informer Git concernant votre clé SSH -You can use an existing SSH key to sign commits and tags, or generate a new one specifically for signing. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." +Vous pouvez utiliser une clé SSH existante pour signer des commits et des étiquettes, ou en générer une nouvelle spécifiquement pour la signature. Pour plus d’informations, consultez « [Génération d’une nouvelle clé SSH et ajout de celle-ci à ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) ». {% data reusables.gpg.ssh-git-version %} -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-ssh-signing %} -{% data reusables.gpg.paste-ssh-public-key %} +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-ssh-signing %} {% data reusables.gpg.paste-ssh-public-key %} {% endif %} {% data reusables.gpg.x-509-key %} -## Further reading +## Lectures supplémentaires -- "[Adding a new SSH key to your GitHub account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)." -- "[Signing commits](/articles/signing-commits)" -- "[Signing tags](/articles/signing-tags)" +- « [Ajout d’une nouvelle clé SSH à votre compte GitHub](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) ». +- « [Signature de commits](/articles/signing-commits) » +- « [Signature d’étiquettes](/articles/signing-tags) » diff --git a/translations/fr-FR/content/issues/tracking-your-work-with-issues/about-tasklists.md b/translations/fr-FR/content/issues/tracking-your-work-with-issues/about-tasklists.md index b69a9c3a2f9a..b0247b758978 100644 --- a/translations/fr-FR/content/issues/tracking-your-work-with-issues/about-tasklists.md +++ b/translations/fr-FR/content/issues/tracking-your-work-with-issues/about-tasklists.md @@ -6,12 +6,12 @@ versions: miniTocMaxHeadingLevel: 3 redirect_from: - /early-access/issues/about-tasklists -ms.openlocfilehash: e35065ae4de634bb7a2da815e0a860c7c0b92234 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 69cdde1bb071f963b1a2f58ef1227bc96ab9d869 +ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19 ms.translationtype: HT ms.contentlocale: fr-FR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159708' +ms.lasthandoff: 11/22/2022 +ms.locfileid: '148180784' --- {% data reusables.projects.tasklists-release-stage %} @@ -31,17 +31,7 @@ Les problèmes que vous ajoutez à vos listes de tâches sont automatiquement re ## Création de listes de tâches -Pour créer une liste de tâches, vous pouvez utiliser le bouton « Ajouter une liste de tâches » ou modifier le Markdown du problème. - -### Création d’une liste de tâches à l’aide du bouton « Ajouter une liste de tâches » - -Cliquez sur le bouton **{% octicon "checklist" aria-label="The checklist icon" %} Ajouter une liste de tâches** dans la partie inférieure d’une description de problème que vous pouvez modifier pour créer une liste de tâches. - -![Capture d’écran montrant le bouton « Ajouter une liste de tâches »](/assets/images/help/issues/tasklist-add-tasklist-button.png) - -### Création d’une liste de tâches à l’aide de Markdown - -Vous pouvez utiliser Markdown dans une description de problème pour créer une liste de tâches. Créez un bloc de code délimité et incluez `[tasklist]` en regard des accents graves d’ouverture. Préfacez chaque élément avec `- [ ]` et incluez des liens vers d’autres problèmes ou du texte. Vous pouvez éventuellement inclure un titre en tant qu’en-tête Markdown en haut de votre liste. +Vous pouvez créer une liste d tâches dans une description de problème. Créez un bloc de code délimité et incluez `[tasklist]` en regard des accents graves d’ouverture. Vous pouvez ensuite préfacer chaque élément avec `- [ ]` et inclure des liens vers d’autres problèmes ou du texte. Vous pouvez éventuellement inclure un titre en tant qu’en-tête Markdown en haut de votre liste. ```` ```[tasklist] @@ -50,10 +40,11 @@ Vous pouvez utiliser Markdown dans une description de problème pour créer une - [ ] Draft issue title ``` ```` - Votre Markdown sera rendu par {% data variables.product.product_name %} sous la forme d’une liste de tâches. Vous pouvez ensuite apporter des modifications et ajouter des problèmes et des brouillons de problèmes à l’aide de l’interface utilisateur. Si vous modifiez la description du problème, vous pouvez modifier le Markdown directement ou le copier pour dupliquer la liste de tâches dans d’autres problèmes. +Vous pouvez également cliquer sur {% octicon "checklist" aria-label="The checklist icon" %} dans la barre d’outils de mise en forme pour insérer une liste de tâches lors de la création d’un problème ou de la modification d’une description de problème. +![Capture d’écran montrant le bouton « Ajouter une liste de tâches »](/assets/images/help/issues/tasklist-formatting-toolbar.png) ## Ajout de problèmes à une liste de tâches diff --git a/translations/fr-FR/data/reusables/actions/supported-github-runners.md b/translations/fr-FR/data/reusables/actions/supported-github-runners.md index 2599a33141ea..59c754e4ebc5 100644 --- a/translations/fr-FR/data/reusables/actions/supported-github-runners.md +++ b/translations/fr-FR/data/reusables/actions/supported-github-runners.md @@ -1,26 +1,34 @@ +--- +ms.openlocfilehash: b40c432907d00f7bf7cf33a1f379ea3318ae8aa2 +ms.sourcegitcommit: cb39c15ab6ccfacf49f4b114b77e3b920fdddf70 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/22/2022 +ms.locfileid: "148180668" +--- - - - + + + @@ -95,12 +103,12 @@ Migrate to macOS-11 or macOS-12. For more information, {% note %} -**Note:** The `-latest` runner images are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor. +**Remarque :** Les images d’exécuteur `-latest` sont les dernières images stables que fournit {% data variables.product.prodname_dotcom %} et peuvent ne pas correspondre à la version la plus récente du système d’exploitation disponible auprès du fournisseur du système d’exploitation. {% endnote %} {% warning %} -**Warning:** Beta and Deprecated Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support. +**Avertissement :** Les images bêta et dépréciées sont fournies « en l’état », « avec toutes les imperfections » et « selon la disponibilité », et sont exclues du contrat de niveau de service et de la garantie. Les images bêta peuvent ne pas être couvertes par le service client. {% endwarning %} diff --git a/translations/fr-FR/data/reusables/enterprise_installation/image-urls-viewable-warning.md b/translations/fr-FR/data/reusables/enterprise_installation/image-urls-viewable-warning.md index d4ad4ce93726..e8dd790c6311 100644 --- a/translations/fr-FR/data/reusables/enterprise_installation/image-urls-viewable-warning.md +++ b/translations/fr-FR/data/reusables/enterprise_installation/image-urls-viewable-warning.md @@ -1,5 +1,13 @@ +--- +ms.openlocfilehash: 699a28a2443778018ea25e0060e621da9427b4ef +ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/22/2022 +ms.locfileid: "148179972" +--- {% warning %} -**Warning:** If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication{% ifversion ghes %}, even if the pull request is in a private repository, or if private mode is enabled. To prevent unauthorized access to the images, ensure that you restrict network access to the systems that serve the images, including {% data variables.location.product_location %}{% endif %}.{% ifversion ghae %} To prevent unauthorized access to image URLs on {% data variables.product.product_name %}, consider restricting network traffic to your enterprise. For more information, see "[Restricting network traffic to your enterprise with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)."{% endif %} +**Avertissement :** si vous joignez une image à une demande de tirage ou à un commentaire sur un problème, n’importe qui peut afficher l’URL anonymisée sans authentification{% ifversion ghes %}, même si la demande de tirage se trouve dans un référentiel privé ou si le mode privé est activé. Pour empêcher tout accès non autorisé aux images, veillez à restreindre l’accès réseau aux systèmes qui servent les images, notamment {% data variables.location.product_location %}{% endif %}.{% ifversion ghae %} Pour empêcher tout accès non autorisé aux URL des images sur {% data variables.product.product_name %}, n’hésitez pas à restreindre le trafic réseau vers votre entreprise. Pour plus d’informations, consultez « [Restriction du trafic réseau vers votre entreprise avec une liste d’adresses IP autorisées](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list) ».{% endif %} {% endwarning %} diff --git a/translations/fr-FR/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md b/translations/fr-FR/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md index f8c5490631da..6c7ba059cd92 100644 --- a/translations/fr-FR/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md +++ b/translations/fr-FR/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md @@ -1,3 +1,11 @@ -You can edit an entry in your IP allow list. If you edit an enabled entry, changes are enforced immediately. +--- +ms.openlocfilehash: a6a2388e469c6283bbe0f9f7855044f45829584e +ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/22/2022 +ms.locfileid: "148180068" +--- +Vous pouvez modifier une entrée dans votre liste d’autorisation IP. Si vous modifiez une entrée activée, les modifications s’appliquent immédiatement. -After you finish editing entries, you can check whether your allow list will permit a connection from a particular IP address after you enable the list. \ No newline at end of file +Une fois que vous avez terminé de modifier les entrées, vous pouvez vérifier si votre liste autorise une connexion à partir d’une adresse IP particulière une fois que vous avez activé la liste. \ No newline at end of file diff --git a/translations/fr-FR/data/reusables/two_fa/backup_options_during_2fa_enrollment.md b/translations/fr-FR/data/reusables/two_fa/backup_options_during_2fa_enrollment.md new file mode 100644 index 000000000000..c810dddd8f4e --- /dev/null +++ b/translations/fr-FR/data/reusables/two_fa/backup_options_during_2fa_enrollment.md @@ -0,0 +1,10 @@ +--- +ms.openlocfilehash: 251049400fe7254dd3be991c1612faaa05efeb96 +ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1 +ms.translationtype: HT +ms.contentlocale: fr-FR +ms.lasthandoff: 11/22/2022 +ms.locfileid: "148180141" +--- +1. Si vous le souhaitez, vous pouvez configurer des méthodes 2FA supplémentaires pour réduire le risque de verrouillage de compte. Pour plus d’informations sur la configuration de chaque méthode supplémentaire, consultez « [Configuration de l’authentification à deux facteurs avec GitHub Mobile](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) » et « [Configuration de l’authentification à deux facteurs avec une clé de sécurité](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key) ». +![Section supplémentaire sur les méthodes à deux facteurs](/assets/images/help/2fa/2fa-enrollment-additional-methods.png) diff --git a/translations/ko-KR/content/packages/quickstart.md b/translations/ko-KR/content/packages/quickstart.md index 2f18379ec8e8..7ff2db3442c4 100644 --- a/translations/ko-KR/content/packages/quickstart.md +++ b/translations/ko-KR/content/packages/quickstart.md @@ -1,6 +1,6 @@ --- -title: GitHub Packages 빠른 시작 -intro: '{% data variables.product.prodname_actions %}를 사용해 {% data variables.product.prodname_registry %}에 게시합니다.' +title: Quickstart for GitHub Packages +intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.' allowTitleToDifferFromFilename: true versions: fpt: '*' @@ -8,34 +8,29 @@ versions: ghae: '*' ghec: '*' shortTitle: Quickstart -ms.openlocfilehash: a3e4869253e91766eaf44a06dcc71f92d59433fd -ms.sourcegitcommit: 5f40f9341dd1e953f4be8d1642f219e628e00cc8 -ms.translationtype: MT -ms.contentlocale: ko-KR -ms.lasthandoff: 10/04/2022 -ms.locfileid: '148009317' --- + {% data reusables.actions.enterprise-github-hosted-runners %} -## 소개 +## Introduction -이 가이드에서는 {% data variables.product.prodname_actions %} 워크플로를 만들어 코드를 테스트한 다음 {% data variables.product.prodname_registry %}에 게시합니다. +In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}. -## 패키지 게시 +## Publishing your package -1. {% data variables.product.prodname_dotcom %}에 새 리포지토리를 만들고 Node에 `.gitignore`를 추가합니다. 자세한 내용은 “[새 리포지토리 만들기](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)”를 참조하세요. -2. 로컬 컴퓨터에 리포지토리를 복제합니다. +1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clone the repository to your local machine. ```shell $ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git $ cd YOUR-REPOSITORY ``` -3. `index.js` 파일을 만들고 “Hello world!”라는 기본 알림을 추가합니다. +3. Create an `index.js` file and add a basic alert to say "Hello world!" {% raw %} ```javascript{:copy} console.log("Hello, World!"); ``` {% endraw %} -4. `npm init`을 사용하여 npm 패키지를 초기화합니다. 패키지 초기화 마법사에서 _`@YOUR-USERNAME/YOUR-REPOSITORY`_ 와 같은 이름의 패키지를 입력하고 테스트 스크립트를 `exit 0`으로 설정합니다. 그러면 패키지에 대한 정보가 포함된 `package.json` 파일이 생성됩니다. +4. Initialize an npm package with `npm init`. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0`. This will generate a `package.json` file with information about your package. {% raw %} ```shell $ npm init @@ -46,15 +41,15 @@ ms.locfileid: '148009317' ... ``` {% endraw %} -5. `npm install`을 실행하여 `package-lock.json` 파일을 생성한 다음 변경 내용을 {% data variables.product.prodname_dotcom %}에 푸시합니다. +5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}. ```shell $ npm install $ git add index.js package.json package-lock.json $ git commit -m "initialize npm package" $ git push ``` -6. `.github/workflows` 디렉터리를 만듭니다. 디렉터리에서 `release-package.yml`이라는 파일을 만듭니다. -7. 다음 YAML 콘텐츠를 `release-package.yml` 파일{% ifversion ghes or ghae %}로 복사하여 `YOUR-HOSTNAME`을(를) 엔터프라이즈{% endif %}의 이름으로 바꿉니다. +6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`. +7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghes or ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}. ```yaml{:copy} name: Node.js Package @@ -69,7 +64,7 @@ ms.locfileid: '148009317' - uses: {% data reusables.actions.action-checkout %} - uses: {% data reusables.actions.action-setup-node %} with: - node-version: 12 + node-version: 16 - run: npm ci - run: npm test @@ -83,27 +78,29 @@ ms.locfileid: '148009317' - uses: {% data reusables.actions.action-checkout %} - uses: {% data reusables.actions.action-setup-node %} with: - node-version: 12 + node-version: 16 registry-url: {% ifversion ghes or ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} - run: npm ci - run: npm publish env: NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %} ``` -8. 다음 방법 중 하나를 사용하여 패키지를 게시할 범위 및 레지스트리를 NPM에 알릴 수 있습니다. - - 다음과 같은 콘텐츠의 루트 디렉터리에 `.npmrc` 파일을 만들어 리포지토리에 대한 NPM 구성 파일을 추가합니다. {% raw %} +8. Tell NPM which scope and registry to publish packages to using one of the following methods: + - Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents: + {% raw %} ```shell @YOUR-USERNAME:registry=https://npm.pkg.github.com ``` {% endraw %} - - `package.json` 파일을 편집하고 `publishConfig` 키를 지정합니다.{% raw %} + - Edit the `package.json` file and specify the `publishConfig` key: + {% raw %} ```shell "publishConfig": { "@YOUR-USERNAME:registry": "https://npm.pkg.github.com" } ``` {% endraw %} -9. 변경 내용을 커밋하고 {% data variables.product.prodname_dotcom %}에 푸시합니다. +9. Commit and push your changes to {% data variables.product.prodname_dotcom %}. ```shell $ git add .github/workflows/release-package.yml # Also add the file you created or edited in the previous step. @@ -111,26 +108,28 @@ ms.locfileid: '148009317' $ git commit -m "workflow to publish package" $ git push ``` -10. 만든 워크플로는 리포지토리에 새 릴리스가 만들어질 때마다 실행됩니다. 테스트가 통과하면 패키지가 {% data variables.product.prodname_registry %}에 게시됩니다. +10. The workflow that you created will run whenever a new release is created in your repository. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. - 이를 테스트하려면 리포지토리의 **코드** 탭으로 이동하여 새 릴리스를 만듭니다. 자세한 내용은 “[리포지토리에서 릴리스 관리](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)”를 참조하세요. + To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." -## 게시된 패키지 보기 +## Viewing your published package -게시한 모든 패키지를 볼 수 있습니다. +You can view all of the packages you have published. -{% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.navigate-to-packages %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} -## 게시된 패키지 설치 +## Installing a published package -이제 패키지를 게시했으므로 전체 프로젝트에서 종속성으로 사용할 수 있습니다. 자세한 내용은 “[npm 레지스트리 작업](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)”을 참조하세요. +Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)." -## 다음 단계 +## Next steps -방금 추가한 기본 워크플로는 리포지토리에 새 릴리스가 만들어질 때마다 실행됩니다. 그러나 이것은 {% data variables.product.prodname_registry %}로 수행할 수 있는 작업의 시작에 불과합니다. 단일 워크플로를 사용하여 여러 레지스트리에 패키지를 게시하고, 병합된 끌어오기 요청과 같은 다른 이벤트에서 실행되도록 워크플로를 트리거하고, 컨테이너를 관리하는 등 여러 작업을 할 수 있습니다. +The basic workflow you just added runs any time a new release is created in your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more. -{% data variables.product.prodname_registry %}와 {% data variables.product.prodname_actions %}를 결합하면 애플리케이션 개발 프로세스의 거의 모든 측면을 자동화할 수 있습니다. 시작할 준비가 되셨나요? {% data variables.product.prodname_registry %}와 {% data variables.product.prodname_actions %}를 사용하여 다음 단계를 수행하는 데 유용한 리소스는 다음과 같습니다. +Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}: -- GitHub Packages에 대한 심층적인 자습서인 “[{% data variables.product.prodname_registry %} 알아보기](/packages/learn-github-packages)” -- GitHub Actions에 대한 심층적인 자습서인 “[{% data variables.product.prodname_actions %} 알아보기](/actions/learn-github-actions)” -- 특정 사용 사례 및 예제가 담긴 “[{% data variables.product.prodname_registry %} 레지스트리 작업](/packages/working-with-a-github-packages-registry)” +- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions +- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples diff --git a/translations/log/msft-de-resets.csv b/translations/log/msft-de-resets.csv index dd0ad9326671..176446851e72 100644 --- a/translations/log/msft-de-resets.csv +++ b/translations/log/msft-de-resets.csv @@ -760,11 +760,11 @@ translations/de-DE/content/codespaces/codespaces-reference/security-in-github-co translations/de-DE/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md,broken liquid tags translations/de-DE/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags translations/de-DE/content/codespaces/customizing-your-codespace/renaming-a-codespace.md,broken liquid tags +translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error translations/de-DE/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md,broken liquid tags translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md,broken liquid tags translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,broken liquid tags translations/de-DE/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md,broken liquid tags -translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,broken liquid tags translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags @@ -778,7 +778,6 @@ translations/de-DE/content/communities/documenting-your-project-with-wikis/about translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error translations/de-DE/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error -translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,broken liquid tags translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags @@ -866,7 +865,6 @@ translations/de-DE/content/get-started/quickstart/contributing-to-projects.md,re translations/de-DE/content/get-started/quickstart/create-a-repo.md,rendering error translations/de-DE/content/get-started/quickstart/fork-a-repo.md,rendering error translations/de-DE/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags -translations/de-DE/content/get-started/quickstart/github-glossary.md,broken liquid tags translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error translations/de-DE/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error translations/de-DE/content/get-started/using-git/about-git-rebase.md,rendering error @@ -1011,7 +1009,6 @@ translations/de-DE/content/repositories/creating-and-managing-repositories/delet translations/de-DE/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error translations/de-DE/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error translations/de-DE/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,rendering error -translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,broken liquid tags translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,rendering error translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md,rendering error translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error @@ -1056,7 +1053,7 @@ translations/de-DE/content/rest/guides/traversing-with-pagination.md,rendering e translations/de-DE/content/rest/guides/working-with-comments.md,broken liquid tags translations/de-DE/content/rest/migrations/source-imports.md,broken liquid tags translations/de-DE/content/rest/overview/api-previews.md,rendering error -translations/de-DE/content/rest/overview/other-authentication-methods.md,broken liquid tags +translations/de-DE/content/rest/overview/other-authentication-methods.md,rendering error translations/de-DE/content/rest/overview/permissions-required-for-github-apps.md,rendering error translations/de-DE/content/rest/overview/resources-in-the-rest-api.md,rendering error translations/de-DE/content/rest/overview/troubleshooting.md,broken liquid tags diff --git a/translations/log/msft-fr-resets.csv b/translations/log/msft-fr-resets.csv index 3f055b112c1b..99f76230a9b9 100644 --- a/translations/log/msft-fr-resets.csv +++ b/translations/log/msft-fr-resets.csv @@ -573,7 +573,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/about-saml-for-enterprise-iam.md,broken liquid tags 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 @@ -651,7 +650,6 @@ translations/fr-FR/content/authentication/managing-commit-signature-verification translations/fr-FR/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,rendering error translations/fr-FR/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,rendering error translations/fr-FR/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error -translations/fr-FR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,broken liquid tags translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error @@ -1115,7 +1113,6 @@ translations/fr-FR/data/reusables/actions/settings-ui/settings-actions-pages-cus translations/fr-FR/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error translations/fr-FR/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error translations/fr-FR/data/reusables/actions/sidebar-secret.md,rendering error -translations/fr-FR/data/reusables/actions/supported-github-runners.md,broken liquid tags translations/fr-FR/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,rendering error translations/fr-FR/data/reusables/actions/workflow-basic-example-and-explanation.md,rendering error translations/fr-FR/data/reusables/actions/workflow-dispatch-inputs.md,rendering error @@ -1186,7 +1183,6 @@ translations/fr-FR/data/reusables/enterprise/test-in-staging.md,rendering error translations/fr-FR/data/reusables/enterprise_installation/download-package.md,rendering error translations/fr-FR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,rendering error translations/fr-FR/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags -translations/fr-FR/data/reusables/enterprise_installation/image-urls-viewable-warning.md,broken liquid tags translations/fr-FR/data/reusables/enterprise_installation/ssh-into-instance.md,rendering error translations/fr-FR/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,rendering error translations/fr-FR/data/reusables/enterprise_site_admin_settings/sign-in.md,rendering error @@ -1214,7 +1210,6 @@ translations/fr-FR/data/reusables/getting-started/managing-enterprise-members.md 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/about-adding-ip-allow-list-entries.md,broken liquid tags -translations/fr-FR/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md,broken liquid tags translations/fr-FR/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md,broken liquid tags translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-enable.md,broken liquid tags translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md,rendering error diff --git a/translations/log/msft-ko-resets.csv b/translations/log/msft-ko-resets.csv index ab8d34aa551e..8c6bac703f5b 100644 --- a/translations/log/msft-ko-resets.csv +++ b/translations/log/msft-ko-resets.csv @@ -971,6 +971,7 @@ translations/ko-KR/content/packages/learn-github-packages/introduction-to-github translations/ko-KR/content/packages/learn-github-packages/publishing-a-package.md,rendering error translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md,rendering error translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error +translations/ko-KR/content/packages/quickstart.md,rendering error translations/ko-KR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,rendering error translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
Runner imageYAML workflow labelNotesImage de l’exécuteurÉtiquette de workflow YAMLRemarques
-Windows Server 2022 +Windows Server 2022 -windows-latest or windows-2022 +windows-latest ou windows-2022 -The windows-latest label currently uses the Windows Server 2022 runner image. +L’étiquette windows-latest utilise actuellement l’image de l’exécuteur Windows Server 2022.
-Windows Server 2019 +Windows Server 2019 windows-2019 @@ -30,7 +38,7 @@ Windows Server 2019
-Ubuntu 22.04 +Ubuntu 22.04 ubuntu-22.04 @@ -43,26 +51,26 @@ Ubuntu 22.04 Ubuntu 20.04 -ubuntu-latest or ubuntu-20.04 +ubuntu-latest ou ubuntu-20.04 -The ubuntu-latest label is currently transitioning to the Ubuntu 22.04 runner image. During the transition, the label might refer to the runner image for either Ubuntu 20.04 or 22.04. For more information, see this {% data variables.product.prodname_dotcom %} blog post. +L’étiquette ubuntu-latest est en cours de transition vers l’image d’exécuteur Ubuntu 22.04. Pendant la transition, l’étiquette peut faire référence à l’image d’exécuteur pour Ubuntu 20.04 ou 22.04. Pour plus d’informations, consultez ce billet de blog {% data variables.product.prodname_dotcom %}.
-Ubuntu 18.04 [deprecated] +Ubuntu 18.04 [déconseillé] ubuntu-18.04 -Migrate to ubuntu-20.04 or ubuntu-22.04. For more information, see this GitHub blog post. +Migrer vers ubuntu-20.04 ou ubuntu-22.04. Pour plus d’informations, consultez ce billet de blog GitHub.
-macOS Monterey 12 +macOS Monterey 12 macos-12 @@ -70,24 +78,24 @@ macOS Monterey 12
-macOS Big Sur 11 +macOS Big Sur 11 -macos-latest or macos-11 +macos-latest ou macos-11 -The macos-latest label is currently transitioning to the macOS Monterey 12 runner image. During the transition, the label might refer to the runner image for either macOS 11 or 12. For more information, see this {% data variables.product.prodname_dotcom %} blog post. +L’étiquette macos-latest est en cours de transition vers l’image d’exécuteur macOS Monterey 12. Pendant la transition, l’étiquette peut faire référence à l’image d’exécuteur pour macOS 11 ou 12. Pour plus d’informations, consultez ce billet de blog {% data variables.product.prodname_dotcom %}.
-macOS Catalina 10.15 [deprecated] +macOS Catalina 10.15 [déprécié] macos-10.15 -Migrate to macOS-11 or macOS-12. For more information, see this GitHub blog post. +Migrer vers macOS-11 ou macOS-12. Pour plus d’informations, consultez ce billet de blog GitHub.