.if` conditional to prevent a job from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
diff --git a/data/reusables/copilot/about-copilot.md b/data/reusables/copilot/about-copilot.md
new file mode 100644
index 0000000000..faa89196e7
--- /dev/null
+++ b/data/reusables/copilot/about-copilot.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_copilot %} is a new AI-powered code completion tool that helps you write code faster. {% data variables.product.prodname_copilot %} is available through {% data variables.product.prodname_dotcom %} personal accounts with {% data variables.product.prodname_copilot_for_individuals %} and through {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_copilot_for_business %}. For more information, see "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
\ No newline at end of file
diff --git a/data/reusables/copilot/copilot-prerequisites.md b/data/reusables/copilot/copilot-prerequisites.md
index b6ecb4ad66..474fc8b7fa 100644
--- a/data/reusables/copilot/copilot-prerequisites.md
+++ b/data/reusables/copilot/copilot-prerequisites.md
@@ -1,2 +1,2 @@
- {% data variables.product.prodname_copilot %} is free to use for verified students, teachers, and open source maintainers.
-- If you are not a student, teacher, or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. You must provide billing information in order to start a free trial. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
+- If you are not a student, teacher, or open source maintainer, you will need an active trial or subscription. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
diff --git a/data/reusables/copilot/dotcom-settings.md b/data/reusables/copilot/dotcom-settings.md
index 32ce3b3753..6f4ce42556 100644
--- a/data/reusables/copilot/dotcom-settings.md
+++ b/data/reusables/copilot/dotcom-settings.md
@@ -2,7 +2,9 @@
Once you have an active {% data variables.product.prodname_copilot %} trial or subscription, you can adjust {% data variables.product.prodname_copilot %} settings for your personal account on {% data variables.product.prodname_dotcom %} in the [{% data variables.product.prodname_copilot %} settings](https://github.com/settings/copilot). The settings apply anywhere that you use {% data variables.product.prodname_copilot %}. You can configure the suggestions that {% data variables.product.prodname_copilot %} offers and how {% data variables.product.company_short %} uses your telemetry data.
-## Enabling or disabling duplication detection
+### Enabling or disabling duplication detection
+
+{% data reusables.copilot.duplication-setting-org %}
{% data variables.product.prodname_copilot %} includes a filter which detects code suggestions matching public code on {% data variables.product.prodname_dotcom %}. You can choose to enable or disable the filter. When the filter is enabled, {% data variables.product.prodname_copilot %} checks code suggestions with their surrounding code of about 150 characters against public code on {% data variables.product.prodname_dotcom %}. If there is a match or near match, the suggestion will not be shown to you.
@@ -12,7 +14,9 @@ Once you have an active {% data variables.product.prodname_copilot %} trial or s
{% data reusables.copilot.save-settings %}
-## Enabling or disabling telemetry
+### Enabling or disabling telemetry
+
+{% data reusables.copilot.telemetry-setting-org %}
You can choose whether your code snippets are collected and retained by GitHub and further processed and shared with Microsoft and OpenAI by adjusting your user settings. For more information about data that {% data variables.product.prodname_copilot %} may collect depending on your telemetry settings, see "[{% data variables.product.company_short %} Terms for Additional Products and Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)" and the [{% data variables.product.prodname_copilot %} privacy FAQ](https://github.com/features/copilot/#faq-privacy).
diff --git a/data/reusables/copilot/duplication-setting-org.md b/data/reusables/copilot/duplication-setting-org.md
new file mode 100644
index 0000000000..b23f70436c
--- /dev/null
+++ b/data/reusables/copilot/duplication-setting-org.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** If you are a member of an organization on {% data variables.product.prodname_ghe_cloud %} who has been assigned a {% data variables.product.prodname_copilot %} seat through your organization, you will not be able to configure duplication detection in your personal account settings. Your duplication detection setting will be inherited from your organization or enterprise.
+
+{% endnote %}
\ No newline at end of file
diff --git a/data/reusables/copilot/signup-procedure.md b/data/reusables/copilot/signup-procedure.md
index 2e13ed4e79..2a65feb841 100644
--- a/data/reusables/copilot/signup-procedure.md
+++ b/data/reusables/copilot/signup-procedure.md
@@ -1,7 +1,5 @@
-Before you can start using {% data variables.product.prodname_copilot %}, you will need to set up a free trial or subscription.
-
{% data reusables.user-settings.access_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} GitHub Copilot**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} {% data variables.product.prodname_copilot %}**.
1. On the {% data variables.product.prodname_copilot %} settings page, click **Enable {% data variables.product.prodname_copilot %}**.
diff --git a/data/reusables/copilot/subscription-prerequisite.md b/data/reusables/copilot/subscription-prerequisite.md
new file mode 100644
index 0000000000..f3e04dfe32
--- /dev/null
+++ b/data/reusables/copilot/subscription-prerequisite.md
@@ -0,0 +1 @@
+- To use {% data variables.product.prodname_copilot %} you must have an active {% data variables.product.prodname_copilot %} subscription. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
\ No newline at end of file
diff --git a/data/reusables/copilot/telemetry-setting-org.md b/data/reusables/copilot/telemetry-setting-org.md
new file mode 100644
index 0000000000..ef2e99e05d
--- /dev/null
+++ b/data/reusables/copilot/telemetry-setting-org.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** If you are a member of an organization on {% data variables.product.prodname_ghe_cloud %} who has been assigned a {% data variables.product.prodname_copilot %} seat through your organization, you will not be able to configure telemetry in your personal account settings. Telemetry will be automatically disabled.
+
+{% endnote %}
\ No newline at end of file
diff --git a/data/reusables/copilot/vscode-settings.md b/data/reusables/copilot/vscode-settings.md
new file mode 100644
index 0000000000..e4e6114ae8
--- /dev/null
+++ b/data/reusables/copilot/vscode-settings.md
@@ -0,0 +1,2 @@
+1. In the **File** menu, navigate to **Preferences** and click **Settings**.
+
\ No newline at end of file
diff --git a/data/reusables/discussions/discussion-category-forms-beta.md b/data/reusables/discussions/discussion-category-forms-beta.md
new file mode 100644
index 0000000000..1798a8f48a
--- /dev/null
+++ b/data/reusables/discussions/discussion-category-forms-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Discussion category forms are currently in limited public beta and subject to change.
+
+{% endnote %}
diff --git a/data/reusables/discussions/discussion-category-forms-name.md b/data/reusables/discussions/discussion-category-forms-name.md
new file mode 100644
index 0000000000..4199c3023a
--- /dev/null
+++ b/data/reusables/discussions/discussion-category-forms-name.md
@@ -0,0 +1 @@
+ The name must correspond with the slug for one of your discussion categories. For example, the template for the "Announcements" category should be `.github/DISCUSSION_TEMPLATE/announcements.yml`.
\ No newline at end of file
diff --git a/data/reusables/discussions/discussion-category-forms-sample.md b/data/reusables/discussions/discussion-category-forms-sample.md
new file mode 100644
index 0000000000..f84a0494a5
--- /dev/null
+++ b/data/reusables/discussions/discussion-category-forms-sample.md
@@ -0,0 +1,58 @@
+```YAML{:copy}
+title: "[General] "
+labels: ["General Introduction"]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ This is text that will show up in the template!
+ - type: textarea
+ id: improvements
+ attributes:
+ label: Top 3 improvements
+ description: "What are the top 3 improvements we could make to this project?"
+ value: |
+ 1.
+ 2.
+ 3.
+ ...
+ render: bash
+ validations:
+ required: true
+ - type: markdown
+ attributes:
+ value: |
+ ## Markdown header
+ And some more markdown
+ - type: input
+ id: has-id
+ attributes:
+ label: Suggestions
+ description: A description about suggestions to help you
+ validations:
+ required: true
+ - type: dropdown
+ id: download
+ attributes:
+ label: Which area of this project could be most improved?
+ options:
+ - Documentation
+ - Pull request review time
+ - Bug fix time
+ - Release cadence
+ validations:
+ required: true
+ - type: checkboxes
+ attributes:
+ label: Check that box!
+ options:
+ - label: This one!
+ required: true
+ - label: I won't stop you if you check this one, too
+ - type: markdown
+ attributes:
+ value: |
+ ### The thrilling conclusion
+ _to our template_
+
+```
diff --git a/data/reusables/enterprise-accounts/copilot-tab.md b/data/reusables/enterprise-accounts/copilot-tab.md
new file mode 100644
index 0000000000..7b3d2b7644
--- /dev/null
+++ b/data/reusables/enterprise-accounts/copilot-tab.md
@@ -0,0 +1 @@
+1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **{% data variables.product.prodname_copilot_short %}**.
\ No newline at end of file
diff --git a/data/reusables/enterprise-accounts/dormant-user-activity.md b/data/reusables/enterprise-accounts/dormant-user-activity.md
index 80878d1726..24b839f410 100644
--- a/data/reusables/enterprise-accounts/dormant-user-activity.md
+++ b/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
- Starring a repository
- Deleting a repository
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
+- Joining an organization
+
+{% ifversion ghes %}
+A user will also be considered active if their account has been updated by LDAP.
+{% endif %}
diff --git a/data/reusables/enterprise_site_admin_settings/3-7-new-subdomains.md b/data/reusables/enterprise_site_admin_settings/3-7-new-subdomains.md
new file mode 100644
index 0000000000..ba602ec304
--- /dev/null
+++ b/data/reusables/enterprise_site_admin_settings/3-7-new-subdomains.md
@@ -0,0 +1,17 @@
+{% ifversion ghes = 3.5 or ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
+
+{% note %}
+
+{%- ifversion ghes = 3.5 or ghes = 3.6 %}
+
+**Note**: The `http(s)://render.HOSTNAME` subdomain is deprecated in {% data variables.product.product_name %} 3.7 and later. After you upgrade to 3.7 or later, ensure that your TLS certificate covers the subdomains for the replacement services, `http(s)://notebook.HOSTNAME` and `http(s)://viewscreen.HOSTNAME`.
+
+{%- elsif ghes = 3.7 or ghes = 3.8 %}
+
+**Note**: The `http(s)://notebook.HOSTNAME` or `http(s)://viewscreen.HOSTNAME` subdomains are new in {% data variables.product.product_name %} 3.7 and later, and replace `http(s)://render.HOSTNAME`. After you upgrade to 3.7 or later, your TLS certificate must cover the subdomain for the replacement services, `http(s)://notebook.HOSTNAME` and `http(s)://viewscreen.HOSTNAME`.
+
+{%- endif %}
+
+{% endnote %}
+
+{% endif %}
diff --git a/data/reusables/gated-features/copilot-billing.md b/data/reusables/gated-features/copilot-billing.md
index 3e5f15281c..3c08554221 100644
--- a/data/reusables/gated-features/copilot-billing.md
+++ b/data/reusables/gated-features/copilot-billing.md
@@ -1 +1,3 @@
-Billing for {% data variables.product.prodname_copilot %} can currently only be managed through personal accounts. Organizations cannot manage {% data variables.product.prodname_copilot %} billing for organization members at this time. If you are interested in managing billing for {% data variables.product.prodname_copilot %} through your organization, you can join the [waitlist](https://github.com/features/copilot/org_signup).
+{% data variables.product.prodname_copilot %} can be managed through personal accounts with {% data variables.product.prodname_copilot_for_individuals %} or through invoiced {% data variables.product.prodname_ghe_cloud %} accounts with {% data variables.product.prodname_copilot_for_business %}.
+
+{% data variables.product.prodname_ghe_cloud %} accounts paying through credit card or PayPal, and organizations on the {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %} plans cannot manage {% data variables.product.prodname_copilot %} for their members at this time. If you are interested in managing {% data variables.product.prodname_copilot %} through your {% data variables.product.prodname_ghe_cloud %} account paying through credit card or PayPal, or your organization on the {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %} plan, you can contact sales and request to join the [waitlist](https://github.com/enterprise/contact?ref_page=/pricing?_features=site_copilot_biz_ga&ref_cta=Contact%20Sales&ref_loc=cards).
diff --git a/data/reusables/gated-features/copilot.md b/data/reusables/gated-features/copilot.md
index 4c8d486ca8..6181711a83 100644
--- a/data/reusables/gated-features/copilot.md
+++ b/data/reusables/gated-features/copilot.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.copilot.emus-cannot-use-copilot %}
+{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_ghe_cloud %} organizations owned by an enterprise account.
-{% data variables.product.prodname_copilot %} is free to use for verified students, teachers, and maintainers of popular open source projects. If you are not a student, teacher, or maintainer of a popular open source project, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
+{% data variables.product.prodname_copilot %} is free to use for verified students, teachers, and maintainers of popular open source projects. If you are not a student, teacher, or maintainer of a popular open source project, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60-day trial. After the free trial, you will need a paid subscription for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
diff --git a/data/reusables/package_registry/about-graphql-support.md b/data/reusables/package_registry/about-graphql-support.md
new file mode 100644
index 0000000000..ae5408d695
--- /dev/null
+++ b/data/reusables/package_registry/about-graphql-support.md
@@ -0,0 +1,3 @@
+{% ifversion packages-registries-v2 %}For certain registries, you{% else %}You{% endif %} can use GraphQL to delete a version of a private package.
+
+{% data reusables.package_registry.no-graphql-to-delete-packages %}
\ No newline at end of file
diff --git a/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md b/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
index 9bda52c077..74c99daf27 100644
--- a/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
+++ b/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
@@ -1,6 +1,8 @@
-If your workflow is using a {% data variables.product.pat_generic %} to authenticate to a registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`.
+Some {% data variables.product.prodname_registry %} registries support granular permissions. This means you can choose to allow packages to be owned by a user or an organization, or linked to a repository. For the list of registries that support granular permissions, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)."
-{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-personal-access-token)."{% endif %}
+For registries that support granular permissions, if your workflow is using a {% data variables.product.pat_generic %} to authenticate to a registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`.
+
+For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-personal-access-token)."
For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
diff --git a/data/reusables/package_registry/no-graphql-to-delete-packages.md b/data/reusables/package_registry/no-graphql-to-delete-packages.md
index bd9799cf5d..cb0fceb232 100644
--- a/data/reusables/package_registry/no-graphql-to-delete-packages.md
+++ b/data/reusables/package_registry/no-graphql-to-delete-packages.md
@@ -1 +1,3 @@
-{% ifversion fpt or ghec %} The {% data variables.product.prodname_registry %} GraphQL API does not support containers or Docker images that use the package namespace `https://ghcr.io/OWNER/PACKAGE-NAME`, or npm images that use the package namespace `https://npm.pkg.github.com/OWNER/PACKAGE-NAME`.{% endif %}
+{% ifversion packages-registries-v2 %}
+You cannot use the {% data variables.product.prodname_registry %} GraphQL API with registries that support granular permissions. For the registries that **only** support repository-scoped permissions, and can be used with the GraphQL API, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#permissions-for-repository-scoped-packages)."
+{% endif %}
\ No newline at end of file
diff --git a/data/reusables/package_registry/publishing-user-scoped-packages.md b/data/reusables/package_registry/publishing-user-scoped-packages.md
new file mode 100644
index 0000000000..0f756f289e
--- /dev/null
+++ b/data/reusables/package_registry/publishing-user-scoped-packages.md
@@ -0,0 +1 @@
+When you first publish a package, the default visibility is private. When a package is linked to repository, the package visibility is dependent on the repository's visibility. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
\ No newline at end of file
diff --git a/data/reusables/release-notes/babeld-max-threads-performance-issue.md b/data/reusables/release-notes/babeld-max-threads-performance-issue.md
new file mode 100644
index 0000000000..dc06ac2d9e
--- /dev/null
+++ b/data/reusables/release-notes/babeld-max-threads-performance-issue.md
@@ -0,0 +1 @@
+Instances experiencing a high sustained number of concurrent Git requests may experience performance issues. If you suspect that this issue is affecting your instance, contact {% data variables.contact.github_support %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-12-07]
diff --git a/data/reusables/support/support-ticket-translation-option.md b/data/reusables/support/support-ticket-translation-option.md
new file mode 100644
index 0000000000..43a6427ecb
--- /dev/null
+++ b/data/reusables/support/support-ticket-translation-option.md
@@ -0,0 +1 @@
+You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish. For more information, see "[Viewing and updating support tickets](/support/contacting-github-support/viewing-and-updating-support-tickets)."
\ No newline at end of file
diff --git a/data/ui.yml b/data/ui.yml
index 1e8377dd72..29dec0fbef 100644
--- a/data/ui.yml
+++ b/data/ui.yml
@@ -127,7 +127,7 @@ products:
rest:
banner:
api_versioned: The REST API is now versioned.
- api_version_info: For more information, see "About API versioning".
+ api_version_info: For more information, see "About API versioning."
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "About versions of GitHub Docs".
versioning:
about_versions: About REST API versions
diff --git a/data/variables/packages.yml b/data/variables/packages.yml
deleted file mode 100644
index edb27e50e2..0000000000
--- a/data/variables/packages.yml
+++ /dev/null
@@ -1,3 +0,0 @@
-prodname_ghcr_and_npm_registry: '{% data variables.product.prodname_container_registry %}{% ifversion packages-npm-v2 %} and {% data variables.product.prodname_npm_registry %}{% endif %}'
-prodname_ghcr_or_npm_registry: '{% data variables.product.prodname_container_registry %}{% ifversion packages-npm-v2 %} or {% data variables.product.prodname_npm_registry %}{% endif %}'
-prodname_ghcr_and_npm_registry_full: '{% data variables.product.prodname_container_registry %} (`ghcr.io`){% ifversion packages-npm-v2 %} and {% data variables.product.prodname_npm_registry %} (`npm.pkg.github.com`){% endif %}'
diff --git a/data/variables/product.yml b/data/variables/product.yml
index 4b90a74a9d..28190383b2 100644
--- a/data/variables/product.yml
+++ b/data/variables/product.yml
@@ -223,6 +223,10 @@ prodname_arctic_vault: 'Arctic Code Vault'
# GitHub Copilot
prodname_copilot: 'GitHub Copilot'
prodname_copilot_short: 'Copilot'
+prodname_copilot_for_business: 'GitHub Copilot for Business'
+prodname_copilot_for_individuals: 'GitHub Copilot for Individuals'
+prodname_copilot_business_short: 'Copilot for Business'
+prodname_copilot_individuals_short: 'Copilot for Individuals'
# Command Palette
prodname_command_palette: 'GitHub Command Palette'
diff --git a/lib/graphql/static/changelog.json b/lib/graphql/static/changelog.json
index 2363f2737e..8c2f9fc4bf 100644
--- a/lib/graphql/static/changelog.json
+++ b/lib/graphql/static/changelog.json
@@ -1,4 +1,26 @@
[
+ {
+ "schemaChanges": [
+ {
+ "title": "The GraphQL schema includes these changes:",
+ "changes": [
+ "Field fiscalHost was added to object type SponsorsListing
",
+ "WorkflowRun object implements UniformResourceLocatable interface
"
+ ]
+ }
+ ],
+ "previewChanges": [],
+ "upcomingChanges": [
+ {
+ "title": "The following changes will be made to the schema:",
+ "changes": [
+ "On member PackageType.NPM:NPM will be removed. Effective 2022-11-21.
",
+ "On member PackageType.NUGET:NUGET will be removed. Effective 2022-11-21.
"
+ ]
+ }
+ ],
+ "date": "2022-12-07"
+ },
{
"schemaChanges": [
{
diff --git a/lib/graphql/static/schema-dotcom.json b/lib/graphql/static/schema-dotcom.json
index 0960d737e5..be57dc3606 100644
--- a/lib/graphql/static/schema-dotcom.json
+++ b/lib/graphql/static/schema-dotcom.json
@@ -61866,6 +61866,14 @@
}
]
},
+ {
+ "name": "fiscalHost",
+ "description": "The fiscal host used for payments, if any. Will only return a value when\nqueried by the maintainer themselves, or by an admin of the sponsorable organization.
",
+ "type": "Organization",
+ "id": "organization",
+ "kind": "objects",
+ "href": "/graphql/reference/objects#organization"
+ },
{
"name": "fullDescription",
"description": "The full description of the listing.
",
@@ -71563,6 +71571,11 @@
"name": "Node",
"id": "node",
"href": "/graphql/reference/interfaces#node"
+ },
+ {
+ "name": "UniformResourceLocatable",
+ "id": "uniformresourcelocatable",
+ "href": "/graphql/reference/interfaces#uniformresourcelocatable"
}
],
"fields": [
diff --git a/lib/graphql/static/schema-ghae.json b/lib/graphql/static/schema-ghae.json
index 3e850e4792..b0c8e137ba 100644
--- a/lib/graphql/static/schema-ghae.json
+++ b/lib/graphql/static/schema-ghae.json
@@ -58255,6 +58255,11 @@
"name": "Node",
"id": "node",
"href": "/graphql/reference/interfaces#node"
+ },
+ {
+ "name": "UniformResourceLocatable",
+ "id": "uniformresourcelocatable",
+ "href": "/graphql/reference/interfaces#uniformresourcelocatable"
}
],
"fields": [
diff --git a/lib/graphql/static/schema-ghec.json b/lib/graphql/static/schema-ghec.json
index 0960d737e5..be57dc3606 100644
--- a/lib/graphql/static/schema-ghec.json
+++ b/lib/graphql/static/schema-ghec.json
@@ -61866,6 +61866,14 @@
}
]
},
+ {
+ "name": "fiscalHost",
+ "description": "The fiscal host used for payments, if any. Will only return a value when\nqueried by the maintainer themselves, or by an admin of the sponsorable organization.
",
+ "type": "Organization",
+ "id": "organization",
+ "kind": "objects",
+ "href": "/graphql/reference/objects#organization"
+ },
{
"name": "fullDescription",
"description": "The full description of the listing.
",
@@ -71563,6 +71571,11 @@
"name": "Node",
"id": "node",
"href": "/graphql/reference/interfaces#node"
+ },
+ {
+ "name": "UniformResourceLocatable",
+ "id": "uniformresourcelocatable",
+ "href": "/graphql/reference/interfaces#uniformresourcelocatable"
}
],
"fields": [
diff --git a/lib/graphql/static/upcoming-changes.json b/lib/graphql/static/upcoming-changes.json
index 52053ffae4..4b67f8d342 100644
--- a/lib/graphql/static/upcoming-changes.json
+++ b/lib/graphql/static/upcoming-changes.json
@@ -1316,6 +1316,24 @@
"owner": "lukewar"
}
],
+ "2022-11-21": [
+ {
+ "location": "PackageType.NUGET",
+ "description": "NUGET will be removed.
",
+ "reason": "NUGET will be removed from this enum as this type will be migrated to only be used by the Packages REST API.
",
+ "date": "2022-11-21",
+ "criticality": "breaking",
+ "owner": "s-anupam"
+ },
+ {
+ "location": "PackageType.NPM",
+ "description": "NPM will be removed.
",
+ "reason": "NPM will be removed from this enum as this type will be migrated to only be used by the Packages REST API.
",
+ "date": "2022-11-21",
+ "criticality": "breaking",
+ "owner": "s-anupam"
+ }
+ ],
"2022-10-01": [
{
"location": "UpdateProjectNextItemFieldInput.fieldWithSettingId",
@@ -2790,6 +2808,24 @@
"owner": "lukewar"
}
],
+ "2022-11-21": [
+ {
+ "location": "PackageType.NUGET",
+ "description": "NUGET will be removed.
",
+ "reason": "NUGET will be removed from this enum as this type will be migrated to only be used by the Packages REST API.
",
+ "date": "2022-11-21",
+ "criticality": "breaking",
+ "owner": "s-anupam"
+ },
+ {
+ "location": "PackageType.NPM",
+ "description": "NPM will be removed.
",
+ "reason": "NPM will be removed from this enum as this type will be migrated to only be used by the Packages REST API.
",
+ "date": "2022-11-21",
+ "criticality": "breaking",
+ "owner": "s-anupam"
+ }
+ ],
"2022-10-01": [
{
"location": "UpdateProjectNextItemFieldInput.fieldWithSettingId",
@@ -3908,6 +3944,24 @@
"owner": "adamshwert"
}
],
+ "2022-11-21": [
+ {
+ "location": "PackageType.NUGET",
+ "description": "NUGET will be removed.
",
+ "reason": "NUGET will be removed from this enum as this type will be migrated to only be used by the Packages REST API.
",
+ "date": "2022-11-21",
+ "criticality": "breaking",
+ "owner": "s-anupam"
+ },
+ {
+ "location": "PackageType.NPM",
+ "description": "NPM will be removed.
",
+ "reason": "NPM will be removed from this enum as this type will be migrated to only be used by the Packages REST API.
",
+ "date": "2022-11-21",
+ "criticality": "breaking",
+ "owner": "s-anupam"
+ }
+ ],
"2022-10-01": [
{
"location": "RepositoryVulnerabilityAlert.fixReason",
diff --git a/lib/liquid-tags/data.js b/lib/liquid-tags/data.js
index 7955730005..94ca4b9578 100644
--- a/lib/liquid-tags/data.js
+++ b/lib/liquid-tags/data.js
@@ -18,11 +18,13 @@ export default {
async render(scope) {
const text = getDataByLanguage(this.path, scope.environments.currentLanguage)
if (text === undefined) {
- const message = `Can't find the key 'site.data.${this.path}' in the scope.`
- if (THROW_ON_EMPTY) {
- throw new DataReferenceError(message)
+ if (scope.environments.currentLanguage === 'en') {
+ const message = `Can't find the key 'site.data.${this.path}' in the scope.`
+ if (THROW_ON_EMPTY) {
+ throw new DataReferenceError(message)
+ }
+ console.warn(message)
}
- console.warn(message)
return
}
diff --git a/lib/liquid-tags/indented-data-reference.js b/lib/liquid-tags/indented-data-reference.js
index cb38db3ffe..dfc082df16 100644
--- a/lib/liquid-tags/indented-data-reference.js
+++ b/lib/liquid-tags/indented-data-reference.js
@@ -36,11 +36,13 @@ export default {
// Get the referenced value from the context
const text = getDataByLanguage(dataReference, scope.environments.currentLanguage)
if (text === undefined) {
- const message = `Can't find the key 'site.data.${dataReference}' in the scope.`
- if (THROW_ON_EMPTY) {
- throw new IndentedDataReferenceError(message)
+ if (scope.environments.currentLanguage === 'en') {
+ const message = `Can't find the key 'site.data.${dataReference}' in the scope.`
+ if (THROW_ON_EMPTY) {
+ throw new IndentedDataReferenceError(message)
+ }
+ console.warn(message)
}
- console.warn(message)
return
}
diff --git a/lib/page.js b/lib/page.js
index fe076f2f9e..75cac9b6d4 100644
--- a/lib/page.js
+++ b/lib/page.js
@@ -18,6 +18,7 @@ import getLinkData from './get-link-data.js'
import getDocumentType from './get-document-type.js'
import { union } from 'lodash-es'
import { allTools } from './all-tools.js'
+import { renderContentWithFallback } from './render-with-fallback.js'
// We're going to check a lot of pages' "ID" (the first part of
// the relativePath) against `productMap` to make sure it's valid.
@@ -171,24 +172,22 @@ class Page {
context.englishHeadings = englishHeadings
}
- this.intro = await renderContent(this.rawIntro, context)
- this.introPlainText = await renderContent(this.rawIntro, context, {
+ this.intro = await renderContentWithFallback(this, 'rawIntro', context)
+ this.introPlainText = await renderContentWithFallback(this, 'rawIntro', context, {
textOnly: true,
})
- this.title = await renderContent(this.rawTitle, context, {
+ this.title = await renderContentWithFallback(this, 'rawTitle', context, {
textOnly: true,
encodeEntities: true,
})
- this.titlePlainText = await renderContent(this.rawTitle, context, {
+ this.titlePlainText = await renderContentWithFallback(this, 'rawTitle', context, {
textOnly: true,
})
- this.shortTitle = await renderContent(this.shortTitle, context, {
+ this.shortTitle = await renderContentWithFallback(this, 'shortTitle', context, {
textOnly: true,
- encodeEntities: true,
})
- context.relativePath = this.relativePath
- const html = await renderContent(this.markdown, context)
+ const html = await renderContentWithFallback(this, 'markdown', context)
// Adding communityRedirect for Discussions, Sponsors, and Codespaces - request from Product
if (
@@ -205,12 +204,12 @@ class Page {
// product frontmatter may contain liquid
if (this.rawProduct) {
- this.product = await renderContent(this.rawProduct, context)
+ this.product = await renderContentWithFallback(this, 'rawProduct', context)
}
// permissions frontmatter may contain liquid
if (this.rawPermissions) {
- this.permissions = await renderContent(this.rawPermissions, context)
+ this.permissions = await renderContentWithFallback(this, 'rawPermissions', context)
}
// Learning tracks may contain Liquid and need to have versioning processed.
@@ -277,16 +276,16 @@ class Page {
async renderProp(propName, context, opts = { unwrap: false }) {
let prop
if (propName === 'title') {
- prop = this.rawTitle
+ prop = 'rawTitle'
} else if (propName === 'shortTitle') {
- prop = this.rawShortTitle || this.rawTitle // fall back to title
+ prop = this.rawShortTitle ? 'rawShortTitle' : 'rawTitle'
} else if (propName === 'intro') {
- prop = this.rawIntro
+ prop = 'rawIntro'
} else {
- prop = this[propName]
+ prop = propName
}
- const html = await renderContent(prop, context, opts)
+ const html = await renderContentWithFallback(this, prop, context, opts)
if (!opts.unwrap) return html
diff --git a/lib/process-learning-tracks.js b/lib/process-learning-tracks.js
index 0770528263..62e8aa4cda 100644
--- a/lib/process-learning-tracks.js
+++ b/lib/process-learning-tracks.js
@@ -2,6 +2,7 @@ import renderContent from './render-content/index.js'
import getLinkData from './get-link-data.js'
import getApplicableVersions from './get-applicable-versions.js'
import { getDataByLanguage } from './get-data.js'
+import { executeWithFallback } from './render-with-fallback.js'
const renderOpts = { textOnly: true, encodeEntities: true }
@@ -42,8 +43,23 @@ export default async function processLearningTracks(rawLearningTracks, context)
throw new Error(`No learning track called '${renderedTrackName}'.`)
}
+ // If the current language isn't 'en' we need to prepare and have the
+ // English quivalent ready.
+ // We do this for two reasons:
+ //
+ // 1. For each learning-track .yml file (in data) always want the
+ // English values for `guides`, `versions`, `featured_track`.
+ // Meaning, for the translated learning tracks we only keep the
+ // `title` and `description`.
+ //
+ // 2. When we attempt to render the translated learning tracks'
+ // `title` and `description`, if they are failing to render,
+ // we need to have the English `title` and `description` to
+ // fall back to.
+ //
+ let enTrack
if (context.currentLanguage !== 'en') {
- const enTrack = getDataByLanguage(
+ enTrack = getDataByLanguage(
`learning-tracks.${context.currentProduct}.${renderedTrackName}`,
'en'
)
@@ -53,6 +69,7 @@ export default async function processLearningTracks(rawLearningTracks, context)
// from the English equivalent.
track.guides = enTrack.guides
track.versions = enTrack.versions
+ track.featured_track = enTrack.featured_track
}
// If there is no `versions` prop in the learning track frontmatter, assume the track should display in all versions.
@@ -65,11 +82,22 @@ export default async function processLearningTracks(rawLearningTracks, context)
}
}
+ const title = await executeWithFallback(
+ context,
+ () => renderContent(track.title, context, renderOpts),
+ (enContext) => renderContent(enTrack.title, enContext, renderOpts)
+ )
+ const description = await executeWithFallback(
+ context,
+ () => renderContent(track.description, context, renderOpts),
+ (enContext) => renderContent(enTrack.description, enContext, renderOpts)
+ )
+
const learningTrack = {
trackName: renderedTrackName,
trackProduct: context.currentProduct || null,
- title: await renderContent(track.title, context, renderOpts),
- description: await renderContent(track.description, context, renderOpts),
+ title,
+ description,
// getLinkData respects versioning and only returns guides available in the current version;
// if no guides are available, the learningTrack.guides property will be an empty array.
guides: await getLinkData(track.guides, context),
diff --git a/lib/render-with-fallback.js b/lib/render-with-fallback.js
new file mode 100644
index 0000000000..75d52a0ace
--- /dev/null
+++ b/lib/render-with-fallback.js
@@ -0,0 +1,69 @@
+import renderContent from './render-content/index.js'
+import Page from './page.js'
+
+const LIQUID_ERROR_NAMES = new Set(['RenderError', 'ParseError', 'TokenizationError'])
+const isLiquidError = (error) =>
+ error instanceof Error && error.name && LIQUID_ERROR_NAMES.has(error.name)
+
+// Returns a string by wrapping `renderContent()`. The input string to
+// `renderContent` is one that contains Liquid and Markdown. The output
+// is HTML.
+// But what the wrapper does is that it watches out for possible Liquid
+// related rendering errors AND if the context has been prepared with a
+// sync callable that can yield the English equivalent.
+// So it's up to how the `context` is prepared if it has a `getEnglishPage`
+// function. This means, we can know, in the middleware (which is a
+// highter level than `lib/`) how to use the URL to figure out the
+// equivalent English page instance.
+export async function renderContentWithFallback(page, property, context, options) {
+ if (!(page instanceof Page)) {
+ throw new Error(`The first argument has to be Page instance (not ${typeof page})`)
+ }
+ if (typeof property !== 'string') {
+ throw new Error(`The second argument has to be a string (not ${typeof property})`)
+ }
+ const template = page[property]
+ try {
+ return await renderContent(template, context, options)
+ } catch (error) {
+ // Only bother trying to fallback if it was an error we *can* fall back
+ // on English for.
+ if (isLiquidError(error) && context.getEnglishPage) {
+ const enPage = context.getEnglishPage(context)
+ const englishTemplate = enPage[property]
+ // If you don't change the context, it'll confuse the liquid plugins
+ // like `data.js` that uses `environment.scope.currentLanguage`
+ const enContext = Object.assign({}, context, { currentLanguage: 'en' })
+ // Try again!
+ return await renderContent(englishTemplate, enContext, options)
+ }
+ throw error
+ }
+}
+
+// Returns the result of executing the first function, but if it fails
+// return the result of executing the second function.
+// In particular, "fails" means if it's deemed an error thrown that we
+// can fall back for.
+// When it executes the fallback function, it creates a shallow copy of
+// the original `context` but with the `currentLanguage:'en'` set on it.
+//
+// You can use this function to do things like this:
+//
+// const title = await executeWithFallback(
+// context,
+// () => renderContent(track.title, context, renderOpts),
+// (enContext) => renderContent(enTrack.title, enContext, renderOpts)
+// )
+//
+export async function executeWithFallback(context, callable, fallback) {
+ try {
+ return await callable(context)
+ } catch (error) {
+ if (isLiquidError(error)) {
+ const enContext = Object.assign({}, context, { currentLanguage: 'en' })
+ return await fallback(enContext)
+ }
+ throw error
+ }
+}
diff --git a/lib/rest/static/decorated/api.github.com.2022-11-28.json b/lib/rest/static/decorated/api.github.com.2022-11-28.json
index 72357733a1..f57ae7582f 100644
--- a/lib/rest/static/decorated/api.github.com.2022-11-28.json
+++ b/lib/rest/static/decorated/api.github.com.2022-11-28.json
@@ -473448,9 +473448,15 @@
}
},
{
- "type": "issue",
+ "type": "issue_title",
"details": {
- "issue_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ "issue_title_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ }
+ },
+ {
+ "type": "issue_body",
+ "details": {
+ "issue_body_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
}
},
{
@@ -473470,7 +473476,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -473543,10 +473550,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -473556,7 +473563,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
diff --git a/lib/rest/static/decorated/ghec.2022-11-28.json b/lib/rest/static/decorated/ghec.2022-11-28.json
index dac34e8834..94ff85146b 100644
--- a/lib/rest/static/decorated/ghec.2022-11-28.json
+++ b/lib/rest/static/decorated/ghec.2022-11-28.json
@@ -477591,9 +477591,15 @@
}
},
{
- "type": "issue",
+ "type": "issue_title",
"details": {
- "issue_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ "issue_title_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ }
+ },
+ {
+ "type": "issue_body",
+ "details": {
+ "issue_body_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
}
},
{
@@ -477613,7 +477619,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -477686,10 +477693,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -477699,7 +477706,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json
index ae0cd93461..cd93be43ff 100644
--- a/lib/rest/static/decorated/github.ae.json
+++ b/lib/rest/static/decorated/github.ae.json
@@ -365216,9 +365216,15 @@
}
},
{
- "type": "issue",
+ "type": "issue_title",
"details": {
- "issue_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ "issue_title_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ }
+ },
+ {
+ "type": "issue_body",
+ "details": {
+ "issue_body_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
}
},
{
@@ -365238,7 +365244,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -365311,10 +365318,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -365324,7 +365331,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
diff --git a/lib/rest/static/dereferenced/api.github.com.2022-11-28.deref.json b/lib/rest/static/dereferenced/api.github.com.2022-11-28.deref.json
index 62c1e95699..4575b759fd 100644
--- a/lib/rest/static/dereferenced/api.github.com.2022-11-28.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.2022-11-28.deref.json
@@ -415356,7 +415356,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -415429,10 +415430,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -415442,7 +415443,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
@@ -415489,9 +415507,15 @@
}
},
{
- "type": "issue",
+ "type": "issue_title",
"details": {
- "issue_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ "issue_title_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ }
+ },
+ {
+ "type": "issue_body",
+ "details": {
+ "issue_body_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
}
},
{
@@ -1069221,7 +1069245,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -1069294,10 +1069319,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -1069307,7 +1069332,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index 62c1e95699..4575b759fd 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -415356,7 +415356,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -415429,10 +415430,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -415442,7 +415443,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
@@ -415489,9 +415507,15 @@
}
},
{
- "type": "issue",
+ "type": "issue_title",
"details": {
- "issue_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ "issue_title_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ }
+ },
+ {
+ "type": "issue_body",
+ "details": {
+ "issue_body_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
}
},
{
@@ -1069221,7 +1069245,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -1069294,10 +1069319,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -1069307,7 +1069332,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
diff --git a/lib/rest/static/dereferenced/ghec.2022-11-28.deref.json b/lib/rest/static/dereferenced/ghec.2022-11-28.deref.json
index 7dd0a32a1e..092b4679e9 100644
--- a/lib/rest/static/dereferenced/ghec.2022-11-28.deref.json
+++ b/lib/rest/static/dereferenced/ghec.2022-11-28.deref.json
@@ -418271,7 +418271,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -418344,10 +418345,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -418357,7 +418358,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
@@ -418404,9 +418422,15 @@
}
},
{
- "type": "issue",
+ "type": "issue_title",
"details": {
- "issue_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ "issue_title_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ }
+ },
+ {
+ "type": "issue_body",
+ "details": {
+ "issue_body_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
}
},
{
@@ -1076435,7 +1076459,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -1076508,10 +1076533,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -1076521,7 +1076546,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
diff --git a/lib/rest/static/dereferenced/ghec.deref.json b/lib/rest/static/dereferenced/ghec.deref.json
index 7dd0a32a1e..092b4679e9 100644
--- a/lib/rest/static/dereferenced/ghec.deref.json
+++ b/lib/rest/static/dereferenced/ghec.deref.json
@@ -418271,7 +418271,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -418344,10 +418345,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -418357,7 +418358,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
@@ -418404,9 +418422,15 @@
}
},
{
- "type": "issue",
+ "type": "issue_title",
"details": {
- "issue_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ "issue_title_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ }
+ },
+ {
+ "type": "issue_body",
+ "details": {
+ "issue_body_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
}
},
{
@@ -1076435,7 +1076459,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -1076508,10 +1076533,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -1076521,7 +1076546,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json
index f18d3843bc..cf4974de6a 100644
--- a/lib/rest/static/dereferenced/github.ae.deref.json
+++ b/lib/rest/static/dereferenced/github.ae.deref.json
@@ -343685,7 +343685,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -343758,10 +343759,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -343771,7 +343772,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
@@ -343818,9 +343836,15 @@
}
},
{
- "type": "issue",
+ "type": "issue_title",
"details": {
- "issue_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ "issue_title_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ }
+ },
+ {
+ "type": "issue_body",
+ "details": {
+ "issue_body_url": "https://api.github.com/repos/octocat/Hello-World/issues/1347"
}
},
{
@@ -904341,7 +904365,8 @@
"type": "string",
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
],
"description": "The location type. Because secrets may be found in different types of resources (ie. code, comments, issues), this field identifies the type of resource where the secret was found.",
@@ -904414,10 +904439,10 @@
]
},
{
- "description": "Represents an 'issue' secret scanning location type. This location type shows that a secret was detected in the title or description of an issue.",
+ "description": "Represents an 'issue_title' secret scanning location type. This location type shows that a secret was detected in the title of an issue.",
"type": "object",
"properties": {
- "issue_url": {
+ "issue_title_url": {
"type": "string",
"format": "uri",
"description": "The API URL to get the issue where the secret was detected.",
@@ -904427,7 +904452,24 @@
}
},
"required": [
- "issue_url"
+ "issue_title_url"
+ ]
+ },
+ {
+ "description": "Represents an 'issue_body' secret scanning location type. This location type shows that a secret was detected in the body of an issue.",
+ "type": "object",
+ "properties": {
+ "issue_body_url": {
+ "type": "string",
+ "format": "uri",
+ "description": "The API URL to get the issue where the secret was detected.",
+ "examples": [
+ "https://api.github.com/repos/octocat/Hello-World/issues/1347"
+ ]
+ }
+ },
+ "required": [
+ "issue_body_url"
]
},
{
diff --git a/lib/webhooks/static/decorated/api.github.com.json b/lib/webhooks/static/decorated/api.github.com.json
index cc647f02c8..791a779ddd 100644
--- a/lib/webhooks/static/decorated/api.github.com.json
+++ b/lib/webhooks/static/decorated/api.github.com.json
@@ -150907,12 +150907,13 @@
"isRequired": true,
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
]
},
{
- "type": "object or object or object",
+ "type": "object or object or object or object",
"name": "details",
"description": "Represents a 'commit' secret scanning location type. This location type shows that a secret was detected inside a commit to a repository.
",
"isRequired": true
diff --git a/lib/webhooks/static/decorated/ghec.json b/lib/webhooks/static/decorated/ghec.json
index 772ffba7f6..82d3eb0bc4 100644
--- a/lib/webhooks/static/decorated/ghec.json
+++ b/lib/webhooks/static/decorated/ghec.json
@@ -150907,12 +150907,13 @@
"isRequired": true,
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
]
},
{
- "type": "object or object or object",
+ "type": "object or object or object or object",
"name": "details",
"description": "Represents a 'commit' secret scanning location type. This location type shows that a secret was detected inside a commit to a repository.
",
"isRequired": true
diff --git a/lib/webhooks/static/decorated/github.ae.json b/lib/webhooks/static/decorated/github.ae.json
index d82430e352..fe8db755eb 100644
--- a/lib/webhooks/static/decorated/github.ae.json
+++ b/lib/webhooks/static/decorated/github.ae.json
@@ -150447,12 +150447,13 @@
"isRequired": true,
"enum": [
"commit",
- "issue",
+ "issue_title",
+ "issue_body",
"issue_comment"
]
},
{
- "type": "object or object or object",
+ "type": "object or object or object or object",
"name": "details",
"description": "Represents a 'commit' secret scanning location type. This location type shows that a secret was detected inside a commit to a repository.
",
"isRequired": true
diff --git a/middleware/api/search.js b/middleware/api/search.js
index 3ea0014335..9f5bfa96ad 100644
--- a/middleware/api/search.js
+++ b/middleware/api/search.js
@@ -5,7 +5,7 @@ import FailBot from '../../lib/failbot.js'
import languages from '../../lib/languages.js'
import { allVersions } from '../../lib/all-versions.js'
import statsd from '../../lib/statsd.js'
-import { cacheControlFactory } from '../cache-control.js'
+import { searchCacheControl } from '../cache-control.js'
import catchMiddlewareError from '../catch-middleware-error.js'
import { setFastlySurrogateKey } from '../set-fastly-surrogate-key.js'
import {
@@ -14,13 +14,6 @@ import {
DEFAULT_HIGHLIGHT_FIELDS,
} from './es-search.js'
-// This means we tell the browser to cache the XHR request for 1h
-const browserCacheControl = cacheControlFactory(60 * 60)
-// This tells the CDN to cache the response for 4 hours
-const cdnCacheControl = cacheControlFactory(60 * 60 * 4, {
- key: 'surrogate-control',
-})
-
// Used by the legacy search
const versions = new Set(Object.values(searchVersions))
const languagesSet = new Set(Object.keys(languages))
@@ -157,8 +150,7 @@ router.get(
}
})
if (process.env.NODE_ENV !== 'development') {
- browserCacheControl(res)
- cdnCacheControl(res)
+ searchCacheControl(res)
setFastlySurrogateKey(res, `api-search:${language}`, true)
}
@@ -287,8 +279,7 @@ router.get(
statsd.timing('api.search.query', meta.took.query_msec, tags)
if (process.env.NODE_ENV !== 'development') {
- browserCacheControl(res)
- cdnCacheControl(res)
+ searchCacheControl(res)
setFastlySurrogateKey(res, `api-search:${language}`, true)
}
diff --git a/middleware/cache-control.js b/middleware/cache-control.js
index 8cd603e117..5bbc78d5f8 100644
--- a/middleware/cache-control.js
+++ b/middleware/cache-control.js
@@ -9,7 +9,7 @@
// res.send(body)
//
// Max age is in seconds
-export function cacheControlFactory(
+function cacheControlFactory(
maxAge = 60 * 60,
{ key = 'cache-control', public_ = true, immutable = false, maxAgeZero = false } = {}
) {
@@ -19,6 +19,8 @@ export function cacheControlFactory(
maxAge && immutable && 'immutable',
!maxAge && 'private',
!maxAge && 'no-store',
+ maxAge >= 60 * 60 && `stale-while-revalidate=${60 * 60}`,
+ // maxAge >= 60 * 60 && `stale-if-error=${60 * 60}`,
maxAgeZero && 'max-age=0',
]
.filter(Boolean)
@@ -33,16 +35,33 @@ export function cacheControlFactory(
}
}
+// These are roughly in order from shortest to longest
+
+// If you do not want caching
+export const noCacheControl = cacheControlFactory(0)
+
+// Short cache for 4xx errors
+export const errorCacheControl = cacheControlFactory(60) // 1 minute
+
+// This means we tell the browser to cache the XHR request for 1h
+const searchBrowserCacheControl = cacheControlFactory(60 * 60)
+// This tells the CDN to cache the response for 4 hours
+const searchCdnCacheControl = cacheControlFactory(60 * 60 * 4, {
+ key: 'surrogate-control',
+})
+export function searchCacheControl(res) {
+ searchBrowserCacheControl(res)
+ searchCdnCacheControl(res)
+}
+
// 24 hours for CDN, we soft-purge this with each deploy
const defaultCDNCacheControl = cacheControlFactory(60 * 60 * 24, {
key: 'surrogate-control',
})
-
// Shorter because between deployments and their (sort) purges,
// we don't want the browser to overly cache because with them we
// can't control purging.
const defaultBrowserCacheControl = cacheControlFactory(60)
-
// A general default configuration that is useful to almost all responses
// that can be cached.
export function defaultCacheControl(res) {
@@ -50,12 +69,6 @@ export function defaultCacheControl(res) {
defaultBrowserCacheControl(res)
}
-// If you do not want caching
-export const noCacheControl = cacheControlFactory(0)
-
-// Long caching for archived pages and assets
-export const archivedCacheControl = cacheControlFactory(60 * 60 * 24 * 365)
-
// Vary on language when needed
// x-user-language is a custom request header derived from req.cookie:user_language
// accept-language is truncated to one of our available languages
@@ -64,3 +77,9 @@ export function languageCacheControl(res) {
defaultCacheControl(res)
res.set('vary', 'accept-language, x-user-language')
}
+
+// Long cache control for versioned assets: images, CSS, JS...
+export const assetCacheControl = cacheControlFactory(60 * 60 * 24 * 7, { immutable: true })
+
+// Long caching for archived pages and assets
+export const archivedCacheControl = cacheControlFactory(60 * 60 * 24 * 365)
diff --git a/middleware/context.js b/middleware/context.js
index 47e8d45fef..5f1fd2151f 100644
--- a/middleware/context.js
+++ b/middleware/context.js
@@ -65,5 +65,30 @@ export default async function contextualize(req, res, next) {
const restDate = new Date(req.context.initialRestVersioningReleaseDate)
req.context.initialRestVersioningReleaseDateLong = restDate.toUTCString().split(' 00:')[0]
+
+ // Conditionally add this for non-English pages so what inside the
+ // `Page.render` method, when it calls out to `renderContentWithFallback`
+ // it can be able to fall back get original content from English if there's
+ // some runtime rendering error from the translation.
+ if (req.language !== 'en') {
+ // The reason this is a function is because most of the time, we don't
+ // need to know the English equivalent. It only comes into play if a
+ // translated
+ req.context.getEnglishPage = (context) => {
+ if (!context.enPage) {
+ const { page } = context
+ if (!page) {
+ throw new Error("The 'page' has not been put into the context yet.")
+ }
+ const enPath = context.currentPath.replace(`/${page.languageCode}`, '/en')
+ const enPage = context.pages[enPath]
+ if (!enPage) {
+ throw new Error(`Unable to find equivalent English page by the path '${enPath}'`)
+ }
+ context.enPage = enPage
+ }
+ return context.enPage
+ }
+ }
return next()
}
diff --git a/middleware/contextualizers/generic-toc.js b/middleware/contextualizers/generic-toc.js
index 8f149d133c..d7bf9d1b71 100644
--- a/middleware/contextualizers/generic-toc.js
+++ b/middleware/contextualizers/generic-toc.js
@@ -1,5 +1,4 @@
import findPageInSiteTree from '../../lib/find-page-in-site-tree.js'
-import { liquid } from '../../lib/render-content/index.js'
// This module adds either flatTocItems or nestedTocItems to the context object for
// product, categorie, and map topic TOCs that don't have other layouts specified.
@@ -92,10 +91,7 @@ async function getTocItems(node, context, opts) {
return await Promise.all(
node.childPages.filter(filterHidden).map(async (child) => {
const { page } = child
- // The rawTitle never contains Markdown but it might contain Liquid
- const title = page.rawTitle.includes('{')
- ? await liquid.parseAndRender(page.rawTitle, context)
- : page.rawTitle
+ const title = await page.renderProp('rawTitle', context, { textOnly: true })
let intro = null
if (opts.renderIntros) {
intro = ''
diff --git a/middleware/favicons.js b/middleware/favicons.js
index 4a88584e5d..9e5f426945 100644
--- a/middleware/favicons.js
+++ b/middleware/favicons.js
@@ -6,9 +6,7 @@
import fs from 'fs'
import { SURROGATE_ENUMS, setFastlySurrogateKey } from './set-fastly-surrogate-key.js'
-import { cacheControlFactory } from './cache-control.js'
-
-const cacheControl = cacheControlFactory(60 * 60 * 24 * 7, { immutable: true })
+import { assetCacheControl } from './cache-control.js'
const MAP = {
'/favicon.ico': {
@@ -45,7 +43,7 @@ export default function favicons(req, res, next) {
// Manually settings a Cache-Control because no other middleware
// will get a chance to do this later since we terminate here.
- cacheControl(res)
+ assetCacheControl(res)
const { contentType, buffer } = MAP[req.path]
res.set('content-type', contentType)
diff --git a/middleware/handle-errors.js b/middleware/handle-errors.js
index 62b6522058..5f160ad807 100644
--- a/middleware/handle-errors.js
+++ b/middleware/handle-errors.js
@@ -1,9 +1,7 @@
import FailBot from '../lib/failbot.js'
import { nextApp } from './next.js'
import { setFastlySurrogateKey, SURROGATE_ENUMS } from './set-fastly-surrogate-key.js'
-import { cacheControlFactory } from './cache-control.js'
-
-const cacheControl = cacheControlFactory(60) // 1 minute
+import { errorCacheControl } from './cache-control.js'
function shouldLogException(error) {
const IGNORED_ERRORS = [
@@ -39,7 +37,7 @@ export default async function handleError(error, req, res, next) {
// Let's cache our 404'ing assets conservatively.
// The Cache-Control is short, and let's use the default surrogate
// key just in case it was a mistake.
- cacheControl(res)
+ errorCacheControl(res)
// Makes sure the surrogate key is NOT the manual one if it failed.
// This basically unsets what was assumed in the beginning of
// loading all the middlewares.
diff --git a/middleware/index.js b/middleware/index.js
index 982b4c6125..90b84298ea 100644
--- a/middleware/index.js
+++ b/middleware/index.js
@@ -11,7 +11,10 @@ import morgan from 'morgan'
import datadog from './connect-datadog.js'
import helmet from './helmet.js'
import cookieParser from './cookie-parser.js'
-import { setDefaultFastlySurrogateKey } from './set-fastly-surrogate-key.js'
+import {
+ setDefaultFastlySurrogateKey,
+ setLanguageFastlySurrogateKey,
+} from './set-fastly-surrogate-key.js'
import reqUtils from './req-utils.js'
import recordRedirect from './record-redirect.js'
import handleErrors from './handle-errors.js'
@@ -234,6 +237,10 @@ export default function (app) {
app.get('/_ip', instrument(remoteIP, './remoteIP'))
app.get('/_build', instrument(buildInfo, './buildInfo'))
+ // Things like `/api` sets their own Fastly surrogate keys.
+ // Now that the `req.language` is known, set it for the remaining endpoints
+ app.use(setLanguageFastlySurrogateKey)
+
// Check for a dropped connection before proceeding (again)
app.use(haltOnDroppedConnection)
diff --git a/middleware/render-page.js b/middleware/render-page.js
index c55360a5d0..6a65e9ba99 100644
--- a/middleware/render-page.js
+++ b/middleware/render-page.js
@@ -17,9 +17,7 @@ async function buildRenderedPage(req) {
const pageRenderTimed = statsd.asyncTimer(page.render, 'middleware.render_page', [`path:${path}`])
- const renderedPage = await pageRenderTimed(context)
-
- return renderedPage
+ return await pageRenderTimed(context)
}
async function buildMiniTocItems(req) {
diff --git a/middleware/set-fastly-surrogate-key.js b/middleware/set-fastly-surrogate-key.js
index 63f1f8d5b9..82b0accd80 100644
--- a/middleware/set-fastly-surrogate-key.js
+++ b/middleware/set-fastly-surrogate-key.js
@@ -26,6 +26,18 @@ export function setFastlySurrogateKey(res, enumKey, isCustomKey = false) {
}
export function setDefaultFastlySurrogateKey(req, res, next) {
- res.set(KEY, SURROGATE_ENUMS.DEFAULT)
+ res.set(KEY, `${SURROGATE_ENUMS.DEFAULT} ${makeLanguageSurrogateKey()}`)
return next()
}
+
+export function setLanguageFastlySurrogateKey(req, res, next) {
+ res.set(KEY, `${SURROGATE_ENUMS.DEFAULT} ${makeLanguageSurrogateKey(req.language)}`)
+ return next()
+}
+
+export function makeLanguageSurrogateKey(langCode = null) {
+ if (!langCode) {
+ return 'no-language'
+ }
+ return `language:${langCode}`
+}
diff --git a/package-lock.json b/package-lock.json
index ed05bc9df9..7253e3536d 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -9,6 +9,7 @@
"dependencies": {
"@elastic/elasticsearch": "7.11.0",
"@github/failbot": "0.8.0",
+ "@primer/behaviors": "^1.3.1",
"@primer/css": "^20.2.4",
"@primer/octicons": "17.7.0",
"@primer/octicons-react": "17.7.0",
@@ -4051,9 +4052,9 @@
}
},
"node_modules/@primer/behaviors": {
- "version": "1.1.3",
- "resolved": "https://registry.npmjs.org/@primer/behaviors/-/behaviors-1.1.3.tgz",
- "integrity": "sha512-WpCcjAkXG7Lv3ZbaCUgASWKHnCi/pmuSEiyTmHHb6f5xhwk1mliixNL5ZZHtDN6RCcT3VnXUsyek4GopG2lbZQ=="
+ "version": "1.3.1",
+ "resolved": "https://registry.npmjs.org/@primer/behaviors/-/behaviors-1.3.1.tgz",
+ "integrity": "sha512-aMRDUQ350lk0FxtL5gJWPFHHOSSzDbJ6uNJVIt8XSqiGe1pxuW5mVVfrEp1uvzZ0pCHkCdm9fycjnfOeMeIrOQ=="
},
"node_modules/@primer/css": {
"version": "20.2.4",
@@ -23127,9 +23128,9 @@
}
},
"@primer/behaviors": {
- "version": "1.1.3",
- "resolved": "https://registry.npmjs.org/@primer/behaviors/-/behaviors-1.1.3.tgz",
- "integrity": "sha512-WpCcjAkXG7Lv3ZbaCUgASWKHnCi/pmuSEiyTmHHb6f5xhwk1mliixNL5ZZHtDN6RCcT3VnXUsyek4GopG2lbZQ=="
+ "version": "1.3.1",
+ "resolved": "https://registry.npmjs.org/@primer/behaviors/-/behaviors-1.3.1.tgz",
+ "integrity": "sha512-aMRDUQ350lk0FxtL5gJWPFHHOSSzDbJ6uNJVIt8XSqiGe1pxuW5mVVfrEp1uvzZ0pCHkCdm9fycjnfOeMeIrOQ=="
},
"@primer/css": {
"version": "20.2.4",
diff --git a/package.json b/package.json
index d2453d83f7..02ac6d5a98 100644
--- a/package.json
+++ b/package.json
@@ -11,6 +11,7 @@
"dependencies": {
"@elastic/elasticsearch": "7.11.0",
"@github/failbot": "0.8.0",
+ "@primer/behaviors": "^1.3.1",
"@primer/css": "^20.2.4",
"@primer/octicons": "17.7.0",
"@primer/octicons-react": "17.7.0",
@@ -196,7 +197,7 @@
"sync-search": "cross-env NODE_OPTIONS='--max_old_space_size=8192' start-server-and-test sync-search-server 4002 sync-search-indices",
"sync-search-ghes-release": "cross-env GHES_RELEASE=1 start-server-and-test sync-search-server 4002 sync-search-indices",
"sync-search-indices": "script/search/sync-search-indices.js",
- "sync-search-server": "cross-env NODE_ENV=production PORT=4002 CHANGELOG_DISABLED=true node server.js",
+ "sync-search-server": "cross-env NODE_ENV=production PORT=4002 MINIMAL_RENDER=true CHANGELOG_DISABLED=true node server.js",
"translation-check": "start-server-and-test translation-check-server 4002 translation-check-test",
"translation-check-server": "cross-env NODE_ENV=test PORT=4002 node server.js",
"translation-check-test": "script/i18n/test-html-pages.js",
diff --git a/pages/[versionId]/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.tsx b/pages/[versionId]/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.tsx
index ec4230cf78..a005c4b74c 100644
--- a/pages/[versionId]/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.tsx
+++ b/pages/[versionId]/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.tsx
@@ -1,4 +1,7 @@
import { GetServerSideProps } from 'next'
+import { useRouter } from 'next/router'
+import { useEffect } from 'react'
+
import { getInitialPageWebhooks } from 'lib/webhooks'
import { getMainContext, MainContext, MainContextT } from 'components/context/MainContext'
import {
@@ -22,6 +25,8 @@ export default function WebhooksEventsAndPayloads({
automatedPageContext,
webhooks,
}: Props) {
+ const router = useRouter()
+ const { locale } = router
const content = webhooks.map((webhook: WebhookAction, index) => {
return (
@@ -29,6 +34,47 @@ export default function WebhooksEventsAndPayloads({
)
})
+
+ // When someone clicks on a minitoc hash anchor link on this page, we want to
+ // remove the type query parameter from the URL because the type won't make
+ // sense anymore (e.g. ?actionTtype=closed#issues and you click on the fork minitoc
+ // we don't want the URL to be ?actionType=closed#fork).
+ useEffect(() => {
+ const hashChangeHandler = () => {
+ const { asPath } = router
+ let [pathRoot, pathQuery = ''] = asPath.split('?')
+
+ if (pathRoot.includes('#')) {
+ pathRoot = pathRoot.split('#')[0]
+ }
+
+ // carry over any other query parameters besides `actionType` for the webhook
+ // action type
+ if (pathQuery.includes('#')) {
+ pathQuery = pathQuery.split('#')[0]
+ }
+ const params = new URLSearchParams(pathQuery)
+ params.delete('actionType')
+
+ if (location.hash) {
+ router.replace(
+ { pathname: pathRoot, query: params.toString(), hash: location.hash },
+ undefined,
+ {
+ shallow: true,
+ locale,
+ }
+ )
+ }
+ }
+
+ window.addEventListener('hashchange', hashChangeHandler)
+
+ return () => {
+ window.removeEventListener('hashchange', hashChangeHandler)
+ }
+ }, [locale])
+
return (
diff --git a/script/deployment/purge-edge-cache.js b/script/deployment/purge-edge-cache.js
index 8b6c5feb97..47d073230a 100644
--- a/script/deployment/purge-edge-cache.js
+++ b/script/deployment/purge-edge-cache.js
@@ -1,11 +1,21 @@
import got from 'got'
+// Because we use Origin Shielding, it's recommended that you purge twice
+// so it purges the edge nodes *and* the origin.
+// The documentation says:
+//
+// One solution to this race condition problem is simply to purge
+// twice. For purge-all operations, the two purges should be
+// around 30 seconds apart and, for single object and surrogate
+// key purges, around 2 seconds apart.
+//
+// See https://developer.fastly.com/learning/concepts/purging/#shielding
+const DELAY_BEFORE_FIRST_PURGE = 5 * 1000
+const DELAY_BEFORE_SECOND_PURGE = 30 * 1000
+
const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms))
-const ONE_SECOND = 1000
-
async function purgeFastlyBySurrogateKey({ apiToken, serviceId, surrogateKey }) {
- const key = surrogateKey
const safeServiceId = encodeURIComponent(serviceId)
const headers = {
@@ -13,44 +23,53 @@ async function purgeFastlyBySurrogateKey({ apiToken, serviceId, surrogateKey })
accept: 'application/json',
'fastly-soft-purge': '1',
}
- const requestPath = `https://api.fastly.com/service/${safeServiceId}/purge/${key}`
+ const requestPath = `https://api.fastly.com/service/${safeServiceId}/purge/${surrogateKey}`
return got.post(requestPath, { headers, json: true })
}
-export default async function purgeEdgeCache() {
- // Give the app some extra time to wake up before the thundering herd of
- // Fastly requests.
- const delayBeforeFirstPurge = 30 * ONE_SECOND
+export default async function purgeEdgeCache(
+ surrogateKey,
+ {
+ purgeTwice = true,
+ delayBeforeFirstPurge = DELAY_BEFORE_FIRST_PURGE,
+ delayBeforeSecondPurge = DELAY_BEFORE_SECOND_PURGE,
+ } = {}
+) {
+ if (!surrogateKey) {
+ throw new Error('No key set and/or no FASTLY_SURROGATE_KEY env var set')
+ }
+ console.log(`Fastly purgeEdgeCache initialized for: '${surrogateKey}'`)
- // Evidence has shown that it's necessary to purge twice to ensure all
- // customers see fresh content.
- const delayBeforeSecondPurge = 5 * ONE_SECOND
-
- console.log('Fastly purgeEdgeCache initialized...')
-
- const { FASTLY_TOKEN, FASTLY_SERVICE_ID, FASTLY_SURROGATE_KEY } = process.env
- if (!FASTLY_TOKEN || !FASTLY_SERVICE_ID || !FASTLY_SURROGATE_KEY) {
- console.log('Fastly env vars not detected; skipping purgeEdgeCache step')
- return
+ const { FASTLY_TOKEN, FASTLY_SERVICE_ID } = process.env
+ if (!FASTLY_TOKEN || !FASTLY_SERVICE_ID) {
+ throw new Error('Fastly env vars not detected; skipping purgeEdgeCache step')
}
const purgingParams = {
apiToken: FASTLY_TOKEN,
serviceId: FASTLY_SERVICE_ID,
- surrogateKey: FASTLY_SURROGATE_KEY,
+ surrogateKey,
}
- console.log('Waiting extra time to prevent a Thundering Herd problem...')
- await sleep(delayBeforeFirstPurge)
+ // Give the app some extra time to wake up before the thundering herd of
+ // Fastly requests.
+ if (delayBeforeFirstPurge) {
+ console.log('Waiting extra time to prevent a Thundering Herd problem...')
+ await sleep(delayBeforeFirstPurge)
+ }
console.log('Attempting first Fastly purge...')
const firstPurge = await purgeFastlyBySurrogateKey(purgingParams)
console.log('First Fastly purge result:', firstPurge.body || firstPurge)
- console.log('Waiting to purge a second time...')
- await sleep(delayBeforeSecondPurge)
+ // Evidence has shown that it's necessary to purge twice to ensure all
+ // customers see fresh content.
+ if (purgeTwice) {
+ console.log('Waiting to purge a second time...')
+ await sleep(delayBeforeSecondPurge)
- console.log('Attempting second Fastly purge...')
- const secondPurge = await purgeFastlyBySurrogateKey(purgingParams)
- console.log('Second Fastly purge result:', secondPurge.body || secondPurge)
+ console.log('Attempting second Fastly purge...')
+ const secondPurge = await purgeFastlyBySurrogateKey(purgingParams)
+ console.log('Second Fastly purge result:', secondPurge.body || secondPurge)
+ }
}
diff --git a/script/enterprise-server-deprecations/remove-static-files.js b/script/enterprise-server-deprecations/remove-static-files.js
index febc194e81..9a2dcaef3a 100755
--- a/script/enterprise-server-deprecations/remove-static-files.js
+++ b/script/enterprise-server-deprecations/remove-static-files.js
@@ -9,25 +9,30 @@
import fs from 'fs'
import path from 'path'
import rimraf from 'rimraf'
+import walk from 'walk-sync'
import { allVersions } from '../../lib/all-versions.js'
+import { deprecated } from '../../lib/enterprise-server-releases.js'
const graphqlDataDir = path.join(process.cwd(), 'data/graphql')
const webhooksStaticDir = path.join(process.cwd(), 'lib/webhooks/static')
const graphqlStaticDir = path.join(process.cwd(), 'lib/graphql/static')
const restDecoratedDir = path.join(process.cwd(), 'lib/rest/static/decorated')
const restDereferencedDir = path.join(process.cwd(), 'lib/rest/static/dereferenced')
+const ghesReleaseNotesDir = 'data/release-notes/enterprise-server'
const supportedEnterpriseVersions = Object.values(allVersions).filter(
(v) => v.plan === 'enterprise-server'
)
-// RELEASE NOTES
-// We currently do not remove the Enterprise release note content in
-// data/release-notes/enterprise-server/*. One reason to keep this
-// content in the `main` branch is that the GHES team can add
-// new release notes for a deprecated version in some cases.
-// Having that content still in the main branch makes it easier for us to
-// re-scrape the release note pages and upload the changes to Azure.
+// GHES release notes
+const deprecatedVersionsHyphenated = deprecated.map((v) => v.replace(/\./g, '-'))
+walk(ghesReleaseNotesDir)
+ // Only directories end with a /
+ .filter((file) => file.endsWith('/'))
+ // Check if the directory name contains a deprecated GHES version
+ .filter((dir) => deprecatedVersionsHyphenated.some((version) => dir.includes(version)))
+ // Remove the directory
+ .map((dir) => rimraf.sync(path.join(ghesReleaseNotesDir, dir)))
// webhooks and GraphQL
const supportedMiscVersions = supportedEnterpriseVersions.map((v) => v.miscVersionName)
diff --git a/script/rest/update-files.js b/script/rest/update-files.js
index 718d5545ff..9a64c50c73 100755
--- a/script/rest/update-files.js
+++ b/script/rest/update-files.js
@@ -84,9 +84,12 @@ async function getBundledFiles(schemas) {
const bundlerOptions = await getBundlerOptions()
try {
- console.log(`bundle -w -o ${TEMP_DOCS_DIR} ${bundlerOptions}`)
+ console.log(`bundle -v -w -o ${TEMP_DOCS_DIR} ${bundlerOptions}`)
execSync(
- `${path.join(GITHUB_REP_DIR, 'bin/openapi')} bundle -w -o ${TEMP_DOCS_DIR} ${bundlerOptions}`,
+ `${path.join(
+ GITHUB_REP_DIR,
+ 'bin/openapi'
+ )} bundle -v -w -o ${TEMP_DOCS_DIR} ${bundlerOptions}`,
{ stdio: 'inherit' }
)
} catch (error) {
diff --git a/tests/content/webhooks.js b/tests/content/webhooks.js
index 975ce42ad4..d3e4215186 100644
--- a/tests/content/webhooks.js
+++ b/tests/content/webhooks.js
@@ -1,5 +1,8 @@
import { get } from '../helpers/e2etest.js'
-import { SURROGATE_ENUMS } from '../../middleware/set-fastly-surrogate-key.js'
+import {
+ SURROGATE_ENUMS,
+ makeLanguageSurrogateKey,
+} from '../../middleware/set-fastly-surrogate-key.js'
import { describe, expect } from '@jest/globals'
describe('webhooks v1 middleware', () => {
@@ -23,7 +26,9 @@ describe('webhooks v1 middleware', () => {
expect(res.headers['cache-control']).toMatch(/max-age=[1-9]/)
expect(res.headers['surrogate-control']).toContain('public')
expect(res.headers['surrogate-control']).toMatch(/max-age=[1-9]/)
- expect(res.headers['surrogate-key']).toBe(SURROGATE_ENUMS.DEFAULT)
+ const surrogateKeySplit = res.headers['surrogate-key'].split(/\s/g)
+ expect(surrogateKeySplit.includes(SURROGATE_ENUMS.DEFAULT)).toBeTruthy()
+ expect(surrogateKeySplit.includes(makeLanguageSurrogateKey())).toBeTruthy()
})
test('get non-fpt version webhook', async () => {
diff --git a/tests/helpers/caching-headers.js b/tests/helpers/caching-headers.js
index 6386227b93..02d6060d8f 100644
--- a/tests/helpers/caching-headers.js
+++ b/tests/helpers/caching-headers.js
@@ -8,7 +8,7 @@ export function checkCachingHeaders(res, defaultSurrogateKey = false, minMaxAge
// that it's a reasonably large number of seconds.
expect(maxAgeSeconds).toBeGreaterThanOrEqual(minMaxAge)
// Because it doesn't have have a unique URL
- expect(res.headers['surrogate-key']).toBe(
+ expect(res.headers['surrogate-key'].split(/\s/g)[0]).toBe(
defaultSurrogateKey ? SURROGATE_ENUMS.DEFAULT : SURROGATE_ENUMS.MANUAL
)
}
diff --git a/tests/linting/lint-files.js b/tests/linting/lint-files.js
index c2507ba2ff..179f394067 100644
--- a/tests/linting/lint-files.js
+++ b/tests/linting/lint-files.js
@@ -42,7 +42,7 @@ const languageCodes = Object.keys(languages)
// This is a string that contributors can use in markdown and yaml files as a placeholder.
// If any placeholders slip through, this test will flag them.
const placeholder = 'TODOCS'
-const placeholderRegex = new RegExp(`\\b${placeholder}\\b`, 'g')
+const placeholderRegex = new RegExp(`\\b${placeholder}\\b`, 'gi')
// WARNING: Complicated RegExp below!
//
@@ -480,8 +480,11 @@ describe('lint markdown content', () => {
test('placeholder string is not present in any markdown files', async () => {
const matches = rawContent.match(placeholderRegex) || []
+ const placeholderStr = matches.length === 1 ? 'placeholder' : 'placeholders'
const errorMessage = `
- Found ${matches.length} placeholder string '${placeholder}' in this file! Please update all placeholders.
+ Found ${matches.length} ${placeholderStr} '${matches.join(
+ ', '
+ )}' in this file! Please update all placeholders.
`
expect(matches.length, errorMessage).toBe(0)
})
diff --git a/tests/rendering/header.js b/tests/rendering/header.js
index 0351a999fc..0546ca0a15 100644
--- a/tests/rendering/header.js
+++ b/tests/rendering/header.js
@@ -11,7 +11,7 @@ describe('header', () => {
const $ = await getDOM(
'/en/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer'
)
- const getStarted = $('div ul ul li a[href="/en/get-started"]')
+ const getStarted = $('details div li a[href="/en/get-started"]')
expect(getStarted.length).toBe(1)
expect(getStarted.text().trim()).toBe('Get started')
diff --git a/tests/rendering/release-notes.js b/tests/rendering/release-notes.js
index 31bcebf4ec..492194acf9 100644
--- a/tests/rendering/release-notes.js
+++ b/tests/rendering/release-notes.js
@@ -47,9 +47,9 @@ describe('server', () => {
)
})
)
- expect.assertions(page.applicableVersions.length * testLanguages.length)
for (const [url, status] of statusCodes.flat()) {
expect(status, url).toBe(200)
}
+ expect.assertions(page.applicableVersions.length * testLanguages.length)
})
})
diff --git a/tests/rendering/server.js b/tests/rendering/server.js
index 37058f64db..748433a305 100644
--- a/tests/rendering/server.js
+++ b/tests/rendering/server.js
@@ -5,7 +5,10 @@ import { describeViaActionsOnly } from '../helpers/conditional-runs.js'
import { loadPages } from '../../lib/page-data.js'
import CspParse from 'csp-parse'
import { productMap } from '../../lib/all-products.js'
-import { SURROGATE_ENUMS } from '../../middleware/set-fastly-surrogate-key.js'
+import {
+ SURROGATE_ENUMS,
+ makeLanguageSurrogateKey,
+} from '../../middleware/set-fastly-surrogate-key.js'
import { getPathWithoutVersion } from '../../lib/path-utils.js'
import { describe, jest } from '@jest/globals'
@@ -138,7 +141,10 @@ describe('server', () => {
const res = await get('/en')
expect(res.statusCode).toBe(200)
expect(res.headers['cache-control']).toMatch(/public, max-age=/)
- expect(res.headers['surrogate-key']).toBe(SURROGATE_ENUMS.DEFAULT)
+
+ const surrogateKeySplit = res.headers['surrogate-key'].split(/\s/g)
+ expect(surrogateKeySplit.includes(SURROGATE_ENUMS.DEFAULT)).toBeTruthy()
+ expect(surrogateKeySplit.includes(makeLanguageSurrogateKey('en'))).toBeTruthy()
})
test('does not render duplicate or tags', async () => {
@@ -950,7 +956,10 @@ describe('static routes', () => {
expect(res.headers['set-cookie']).toBeUndefined()
expect(res.headers['cache-control']).toContain('public')
expect(res.headers['cache-control']).toMatch(/max-age=\d+/)
- expect(res.headers['surrogate-key']).toBe(SURROGATE_ENUMS.DEFAULT)
+
+ const surrogateKeySplit = res.headers['surrogate-key'].split(/\s/g)
+ expect(surrogateKeySplit.includes(SURROGATE_ENUMS.DEFAULT)).toBeTruthy()
+ expect(surrogateKeySplit.includes(makeLanguageSurrogateKey())).toBeTruthy()
})
it('serves schema files from the /data/graphql directory at /public', async () => {
diff --git a/tests/unit/anchor-redirect.js b/tests/unit/anchor-redirect.js
index cc77ed0e65..2b9a2b1a31 100644
--- a/tests/unit/anchor-redirect.js
+++ b/tests/unit/anchor-redirect.js
@@ -1,7 +1,10 @@
import { describe, expect } from '@jest/globals'
import { get } from '../helpers/e2etest.js'
-import { SURROGATE_ENUMS } from '../../middleware/set-fastly-surrogate-key.js'
+import {
+ SURROGATE_ENUMS,
+ makeLanguageSurrogateKey,
+} from '../../middleware/set-fastly-surrogate-key.js'
import clientSideRedirects from '../../lib/redirects/static/client-side-rest-api-redirects.json'
describe('anchor-redirect middleware', () => {
@@ -52,6 +55,8 @@ describe('anchor-redirect middleware', () => {
expect(res.headers['cache-control']).toMatch(/max-age=[1-9]/)
expect(res.headers['surrogate-control']).toContain('public')
expect(res.headers['surrogate-control']).toMatch(/max-age=[1-9]/)
- expect(res.headers['surrogate-key']).toBe(SURROGATE_ENUMS.DEFAULT)
+ const surrogateKeySplit = res.headers['surrogate-key'].split(/\s/g)
+ expect(surrogateKeySplit.includes(SURROGATE_ENUMS.DEFAULT)).toBeTruthy()
+ expect(surrogateKeySplit.includes(makeLanguageSurrogateKey())).toBeTruthy()
})
})
diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md
index 382e81006b..f54adf093a 100644
--- a/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md
@@ -94,7 +94,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
shell: bash
```
{% endraw %}
- This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+ This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, adds the action's path to the runner system path (to locate the `goodbye.sh` script during execution), and runs the `goodbye.sh` script.
For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
index 5a1ea071a9..8dcb762313 100644
--- a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
@@ -271,3 +271,10 @@ jobs:
From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+
+## Template repositories for creating JavaScript actions
+
+{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
+
+* [`javascript-action` template repository](https://github.com/actions/javascript-action)
+* [`typescript-action` template repository](https://github.com/actions/typescript-action)
diff --git a/translations/de-DE/content/actions/learn-github-actions/contexts.md b/translations/de-DE/content/actions/learn-github-actions/contexts.md
index bdf5bb0bfb..9217298a2a 100644
--- a/translations/de-DE/content/actions/learn-github-actions/contexts.md
+++ b/translations/de-DE/content/actions/learn-github-actions/contexts.md
@@ -811,7 +811,7 @@ The `inputs` context contains input properties passed to an action{% ifversion a
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
| Property name | Type | Description |
|---------------|------|-------------|
diff --git a/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0d316eca1f..397d51b308 100644
--- a/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -88,7 +88,7 @@ In addition to the usage limits, you must ensure that you use {% data variables.
{% ifversion fpt or ghes > 3.3 or ghec %}
## Billing for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
diff --git a/translations/de-DE/content/actions/using-workflows/reusing-workflows.md b/translations/de-DE/content/actions/using-workflows/reusing-workflows.md
index 2adee6a3f4..1cc0d2d002 100644
--- a/translations/de-DE/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/de-DE/content/actions/using-workflows/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
---
{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
## Overview
diff --git a/translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md b/translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md
index 8e4adb430f..837875fe9e 100644
--- a/translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md
@@ -123,7 +123,7 @@ You can use activity types and filters to further control when your workflow wil
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
diff --git a/translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 4969f6b53e..e6e11c2ff5 100644
--- a/translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -72,7 +72,7 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `on.workflow_call`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
@@ -320,7 +320,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+You can use the `if` conditional to prevent a step from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
@@ -945,7 +945,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `jobs..uses`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 98a84270fb..1e67bc7da9 100644
--- a/translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
+
| Path without subdomain isolation | Path with subdomain isolation |
| --- | --- |
-| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
-| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
-| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
-| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
-| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
-| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
-| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
+| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
+| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
+| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
+| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
+| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
{%- ifversion viewscreen-and-notebooks %}
-| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
-| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
-{%- else %}
-| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
+| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+{%- ifversion ghes < 3.7 %}
+| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
+| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
+{%- ifversion viewscreen-and-notebooks %}
+| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
+{%- endif %}
+{%- ifversion ghes > 3.4 %}
+| Not supported | `https://containers.HOSTNAME/` |
{%- endif %}
-| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
-| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %}
-| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported | `https://containers.HOSTNAME/` |{% endif %}
## Prerequisites
diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
index 6336814ef8..e723efe2ae 100644
--- a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
+++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Actions with MinIO storage
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO storage to store data generated by workflow runs.'
+title: Aktivieren von GitHub Actions mit dem MinIO-Speicher
+intro: 'Du kannst {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_ghe_server %} aktivieren und MinIO zum Speichern von Daten verwenden, die durch Workflowausführungen generiert wurden.'
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
versions:
ghes: '*'
@@ -14,36 +14,35 @@ redirect_from:
- /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
- /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage
shortTitle: MinIO storage
+ms.openlocfilehash: 3d9c6cfca6b81a66185515c8757cef22290ead30
+ms.sourcegitcommit: 8f1801040a84ca9353899a2d1e6782c702aaed0d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148166569'
---
+## Voraussetzungen
-## Prerequisites
+Stelle vor dem Aktivieren von {% data variables.product.prodname_actions %} sicher, dass du die folgenden Schritte ausgeführt hast:
-Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
+* Erstelle deinen MinIO-Bucket zum Speichern von Daten, die von Workflowausführungen generiert werden. Weitere Informationen zum Installieren und Konfigurieren von MinIO findest du unter [MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html) (Hochleistungsobjektspeicher von MinIO) und [mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html) in der MinIO-Dokumentation.
-* Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
+ Um Ressourcenkonflikte in der Appliance zu vermeiden, empfehlen wir, MinIO separat von {% data variables.location.product_location %} zu hosten.
- To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.
+ {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %}
- {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
-{% data reusables.actions.enterprise-common-prereqs %}
+## Aktivieren von {% data variables.product.prodname_actions %} mit dem MinIO-Speicher
-## Enabling {% data variables.product.prodname_actions %} with MinIO storage
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
+1. Wähle unter "Artefakt- und Protokollspeicher" die Option **Amazon S3** aus, und gib die Details des Speicherbuckets ein:
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.actions %}
-{% data reusables.actions.enterprise-enable-checkbox %}
-1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
+ * **AWS-Service-URL**: Die URL für deinen MinIO-Service. Beispiel: `https://my-minio.example:9000`.
+ * **AWS S3 Bucket**: Der Name deines S3-Buckets.
+ * **AWS S3-Zugriffsschlüssel und Geheimer AWS S3****-Schlüssel**: `MINIO_ACCESS_KEY` und `MINIO_SECRET_KEY`, verwendet für deine MinIO-Instanz.
- * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`.
- * **AWS S3 Bucket**: The name of your S3 bucket.
- * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance.
+ 
+1. Wähle unter "Artifact & Log Storage" (Artefakte & Protokoll Storage) die Option **Pfadformat erzwingen** aus.
- 
-1. Under "Artifact & Log Storage", select **Force path style**.
-
- 
-{% data reusables.enterprise_management_console.test-storage-button %}
-{% data reusables.enterprise_management_console.save-settings %}
+  {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
{% data reusables.actions.enterprise-postinstall-nextsteps %}
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 625a34aa98..c01ecca7a2 100644
--- a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
index 59f87dab08..222b054e59 100644
--- a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
@@ -1,7 +1,7 @@
---
-title: About {% data variables.product.prodname_emus %}
+title: 'Informationen zu {% data variables.product.prodname_emus %}'
shortTitle: About managed users
-intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
+intro: 'Du kannst Identität und Zugriff für deine Unternehmensmitglieder auf {% data variables.product.prodname_dotcom %} über deinen Identitätsanbieter zentral verwalten.'
redirect_from:
- /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
- /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
@@ -17,48 +17,53 @@ topics:
- Enterprise
- SSO
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 72d8263029317783e60d8f81f45edc3dbb8b1c8b
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180013'
---
+## Informationen zu {% data variables.product.prodname_emus %}
-## About {% data variables.product.prodname_emus %}
+Mit {% data variables.product.prodname_emus %} kannst du die Benutzerkonten der Unternehmensmitglieder über deinen Identitätsanbieter (Identity Provider, IdP) steuern. Benutzer, die der Anwendung {% data variables.product.prodname_emu_idp_application %} auf dem IdP zugewiesen sind, werden als neue Benutzerkonten auf {% data variables.product.prodname_dotcom %} bereitgestellt und deinem Unternehmen hinzugefügt. Du steuerst Benutzernamen, Profildaten, Teammitgliedschaft und Repositoryzugriff für die Benutzerkonten über den IdP.
-With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.
-
-In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+Auf deinem IdP kannst du jedem {% data variables.enterprise.prodname_managed_user %} die Rolle des Benutzers, des Unternehmensbesitzers oder des Abrechnungs-Managers zuweisen. {% data variables.enterprise.prodname_managed_users_caps %} können Organisationen innerhalb deines Unternehmens besitzen und andere {% data variables.enterprise.prodname_managed_users %} den Organisationen und Teams innerhalb des Unternehmens hinzufügen. Weitere Informationen findest du unter [Rollen in einem Unternehmen](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise) und [Informationen zu Organisationen](/organizations/collaborating-with-groups-in-organizations/about-organizations).
{% ifversion oidc-for-emu %}
-{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
+{% data reusables.enterprise-accounts.emu-cap-validates %} Weitere Informationen findest du unter [Informationen zur Unterstützung der Richtlinie für bedingten Zugriff deines IdP](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy).
{% endif %}
-You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)."
+Du kannst für {% data variables.enterprise.prodname_managed_users %} Zugriff gewähren und die Möglichkeit bieten, Beiträge zu Repositorys innerhalb deines Unternehmens zu leisten, doch {% data variables.enterprise.prodname_managed_users %} sind nicht dazu in der Lage, öffentliche Inhalte zu erstellen oder mit anderen Benutzer*innen, Organisationen und Unternehmen im übrigen Bereich von {% data variables.product.prodname_dotcom %} zusammenzuarbeiten. Weitere Informationen findest du unter [Möglichkeiten und Einschränkungen von {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users).
-The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+Die Benutzernamen der {% data variables.enterprise.prodname_managed_users %} deines Unternehmens und ihre Profilinformationen, z. B. Anzeigenamen und E-Mail-Adressen, werden durch deinen IdP festgelegt und können von den Benutzer*innen selbst nicht geändert werden. Weitere Informationen findest du unter [Benutzernamen und Profilinformationen](#usernames-and-profile-information).
-Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)."
+Unternehmensbesitzer*innen können alle Aktionen der {% data variables.enterprise.prodname_managed_users %} auf {% data variables.product.prodname_dotcom %} überprüfen. Weitere Informationen findest du unter [Überwachungsprotokollereignisse für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise).
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
+Zum Verwenden von {% data variables.product.prodname_emus %} benötigst du einen separaten Unternehmenskontotyp mit Aktivierung von {% data variables.product.prodname_emus %}. Weitere Informationen zum Erstellen dieses Kontos findest du unter [Informationen zu Unternehmen mit verwalteten Benutzern](#about-enterprises-with-managed-users).
{% note %}
-**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right 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)."
+**Hinweis:** Es gibt mehrere Optionen für die Identitäts- und Zugriffsverwaltung mit {% data variables.product.prodname_ghe_cloud %}, wobei {% data variables.product.prodname_emus %} nicht die beste Lösung für jeden Kunden ist. Weitere Informationen darüber, ob {% data variables.product.prodname_emus %} für dein Unternehmen geeignet ist, findest du unter [Informationen zur Authentifizierung für dein Unternehmen](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise).
{% endnote %}
-## About organization membership management
+## Informationen zum Verwalten der Organisationsmitgliedschaft
-Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+Organisationsmitgliedschaften können manuell verwaltet oder automatisch mithilfe von IdP-Gruppen aktualisiert werden. Um Organisationsmitgliedschaften über deinen IdP zu verwalten, müssen die Mitglieder einer IdP-Gruppe hinzugefügt werden, und die Gruppe muss mit einem Team innerhalb der Organisation verbunden sein. Weitere Informationen zum automatischen Verwalten von Organisation und Teammitgliedschaft findest du unter [Verwalten von Teammitgliedschaften mit Identitätsanbietergruppen](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups).
-The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization.
+Die Art, wie Mitglieder zu einer Organisation hinzugefügt werden, die deinem Unternehmen gehört – entweder über IdP-Gruppen oder manuell – bestimmt, wie sie aus einer Organisation entfernt werden müssen.
-- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
-- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
+- Wenn ein Mitglied einer Organisation manuell hinzugefügt wurde, musst du es manuell entfernen. Wenn du seine Zuweisung zur {% data variables.product.prodname_emu_idp_application %}-Anwendung auf deinem IdP aufhebst, wird das Mitglied gesperrt, jedoch nicht aus der Organisation entfernt.
+- Wenn Benutzer*innen Mitglieder einer Organisation wurden, da sie zu IdP-Gruppen hinzugefügt wurden, die einem oder mehreren Teams in der Organisation zugeordnet sind, werden sie, wenn sie aus _allen_ zugeordneten IDP-Gruppen entfernt werden, die der Organisation zugeordnet sind, auch aus der Organisation entfernt.
-To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
+Um zu ermitteln, wie ein Mitglied einer Organisation hinzugefügt wurde, kannst du die Mitgliederliste nach Typ filtern. Weitere Informationen findest du unter [Anzeigen von Personen in deinem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users).
-## Identity provider support
+## Unterstützung für Identitätsanbieter
-{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
+{% data variables.product.prodname_emus %} unterstützt die folgenden IdPs{% ifversion oidc-for-emu %} und Authentifizierungsmethoden:
| | SAML | OIDC |
|----------------------------------|-----------------------------------------------|-----------------------------------------------|
@@ -70,36 +75,36 @@ To discover how a member was added to an organization, you can filter the member
{% endif %}
-## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
+## Möglichkeiten und Einschränkungen von {% data variables.enterprise.prodname_managed_users %}
-{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests.
+{% data variables.enterprise.prodname_managed_users_caps %} können nur zu privaten und internen Repositorys innerhalb ihres Unternehmens und privaten Repositorys im Besitz ihres Benutzerkontos beitragen. {% data variables.enterprise.prodname_managed_users_caps %} haben schreibgeschützten Zugriff auf die breitere {% data variables.product.prodname_dotcom %}-Community. Diese Sichtbarkeits- und Zugriffsbeschränkungen für Benutzer und Inhalte gelten für alle Anforderungen, einschließlich API-Anforderungen.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises.
-* Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
-* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate.
-* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
-* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories.
+* {% data variables.enterprise.prodname_managed_users_caps %} können weder zu Organisationen oder Repositorys außerhalb des Unternehmens eingeladen werden noch können die {% data variables.enterprise.prodname_managed_users %} zu anderen Unternehmen eingeladen werden.
+* Externe Projektmitarbeiter werden von {% data variables.product.prodname_emus %} nicht unterstützt.
+* {% data variables.enterprise.prodname_managed_users_caps %} können keine Issues oder Pull Requests in Repositorys außerhalb des Unternehmens erstellen, Kommentare oder Reaktionen zu ihnen hinzufügen sowie diese nicht mit Sternen versehen, überwachen oder forken.
+* {% data variables.enterprise.prodname_managed_users_caps %} können alle öffentlichen Repositorys auf {% data variables.product.prodname_dotcom_the_website %} anzeigen, jedoch keinen Code an Repositorys außerhalb des Unternehmens pushen.
+* {% data variables.enterprise.prodname_managed_users_caps %} und die Inhalte, die sie erstellen, sind nur für andere Mitglieder des Unternehmens sichtbar.
+* {% data variables.enterprise.prodname_managed_users_caps %} können Benutzer*innen außerhalb des Unternehmens nicht folgen.
+* {% data variables.enterprise.prodname_managed_users_caps %} können keine Gists erstellen und kommentieren.
+* {% data variables.enterprise.prodname_managed_users_caps %} können keine Starterworkflows für {% data variables.product.prodname_actions %} erstellen.
+* {% data variables.enterprise.prodname_managed_users_caps %} können {% data variables.product.prodname_github_apps %} nicht auf ihren Benutzerkonten installieren.
+* Andere {% data variables.product.prodname_dotcom %}-Benutzer*innen können keine {% data variables.enterprise.prodname_managed_user %} sehen, erwähnen oder zur Zusammenarbeit einladen.
+* Du kannst auswählen, ob {% data variables.enterprise.prodname_managed_users %} Repositorys im Besitz ihrer Benutzerkonten erstellen können. Weitere Informationen findest du unter [Erzwingen von Repositoryverwaltungsrichtlinien in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation).
+* Wenn du {% data variables.enterprise.prodname_managed_users %} erlaubst, Repositorys im Besitz ihrer Benutzerkonten zu erstellen, können sie nur private Repositorys besitzen und nur andere Unternehmensmitglieder einladen, an ihren Benutzerrepositorys mitzuarbeiten.
* {% data reusables.enterprise-accounts.emu-forks %}
-* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings.
-* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
+* Je nach Sichtbarkeitseinstellungen für Organisations- und Unternehmensrepositorys können nur private und interne Repositorys in Organisationen im Besitz eines {% data variables.enterprise.prodname_emu_enterprise %} erstellt werden.
+* {% data variables.enterprise.prodname_managed_users_caps %} können {% data variables.product.prodname_pages %} nur eingeschränkt verwenden. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users).
* {% data reusables.copilot.emus-cannot-use-copilot %}
-## Getting started with {% data variables.product.prodname_emus %}
+## Erste Schritte mit {% data variables.product.prodname_emus %}
-Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps.
+Ehe deine Entwickler {% data variables.product.prodname_ghe_cloud %} mit {% data variables.product.prodname_emus %} verwenden können, musst du eine Reihe von Konfigurationsschritten durchführen.
-1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+1. Zum Verwenden von {% data variables.product.prodname_emus %} benötigst du einen separaten Unternehmenskontotyp mit Aktivierung von {% data variables.product.prodname_emus %}. Zum Ausprobieren von {% data variables.product.prodname_emus %} oder zum Besprechen von Optionen zum Migrieren deines vorhandenen Unternehmens kannst du dich an das [{% data variables.product.prodname_dotcom %}-Vertriebsteam wenden](https://enterprise.github.com/contact).
- Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+ Dein Ansprechpartner im GitHub-Vertriebsteam arbeitet mit dir zusammen, um dein neues {% data variables.enterprise.prodname_emu_enterprise %} zu erstellen. Du musst die E-Mail-Adresse für den Benutzer bereitstellen, der dein Unternehmen einrichtet, und einen kurzen Code, der als Suffix für die Benutzernamen deiner Unternehmensmitglieder verwendet wird. {% data reusables.enterprise-accounts.emu-shortcode %} Weitere Informationen findest du unter [Benutzernamen und Profilinformationen](#usernames-and-profile-information).
-2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`.
+2. Nachdem das Unternehmen erstellt ist, erhältst du eine E-Mail von {% data variables.product.prodname_dotcom %}, in der du gebeten wirst, ein Kennwort für den Setupbenutzer deines Unternehmens auszuwählen, der als erster Besitzer des Unternehmens geführt wird. Verwende den Inkognito-Modus oder ein privates Browserfenster beim Festlegen des Kennworts. Der Setupbenutzer wird nur zum Konfigurieren der SSO- und SCIM-Bereitstellungsintegration für das Unternehmen verwendet. Der Setupbenutzer hat keinen Zugriff mehr auf die Verwaltung des Unternehmenskontos, nachdem SSO erfolgreich aktiviert wurde. Der Benutzername des Setupbenutzers ist der kurze Code deines Unternehmens mit dem Suffix `_admin`.
{% note %}
@@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w
{% endnote %}
-3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+3. Nachdem du dich als Setupbenutzer angemeldet hast, empfehlen wir die Aktivierung der zweistufigen Authentifizierung. Weitere Informationen findest du unter [Konfigurieren der zweistufigen Authentifizierung](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication).
-1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). We recommend OIDC, which includes support for Conditional Access Policies (CAP). If you require multiple enterprises with {% data variables.enterprise.prodname_managed_users %} provisioned from one tenant, you must use SAML for each enterprise after the first. If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
+1. Konfiguriere zunächst {% ifversion oidc-for-emu %}, wie sich deine Mitglieder authentifizieren sollen. Wenn du Azure Active Directory als Identitätsanbieter verwendest, kannst du zwischen OpenID Connect (OIDC) und Security Assertion Markup Language (SAML) wählen. OIDC wird empfohlen, da es auch Unterstützung für Richtlinien für bedingten Zugriff (Conditional Access Policies, CAP) umfasst. Wenn du mehrere Unternehmen mit {% data variables.enterprise.prodname_managed_users %} benötigst, die über einen Mandanten bereitgestellt werden, musst du SAML für jedes Unternehmen nach dem ersten verwenden. Wenn du Okta als Identitätsanbieter verwendest, kannst du SAML für die Authentifizierung deiner Mitglieder nutzen.{% else %}SAML SSO für dein Unternehmen. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users).{% endif %}
{% ifversion oidc-for-emu %}
- To get started, read the guide for your chosen authentication method.
+ Lies zunächst den Leitfaden für deine gewählte Authentifizierungsmethode.
- - "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
- - "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+ - [Konfigurieren von OIDC für Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)
+ - [Konfigurieren von SAML Single Sign-On für Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)
{% endif %}
-4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+4. Sobald du SSO konfiguriert hast, kannst du die SCIM-Bereitstellung konfigurieren. SCIM ist dafür zuständig, wie dein Identitätsanbieter {% data variables.enterprise.prodname_managed_users %} auf {% data variables.product.prodname_dotcom_the_website %} zu erstellen. Weitere Informationen findest du unter [Konfigurieren der SCIM-Bereitstellung für Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users).
-5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
+5. Sobald die Authentifizierung und Bereitstellung konfiguriert sind, kannst du mit der Verwaltung der Organisationsmitgliedschaft für deine {% data variables.enterprise.prodname_managed_users %} beginnen, indem du IdP-Gruppen mit Teams synchronisierst. Weitere Informationen findest du unter [Verwalten von Teammitgliedschaften mit Identitätsanbietergruppen](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups).
-If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)."
+Wenn Mitglieder deines Unternehmens eine einzige Arbeitsstation verwenden müssen, um an Repositorys auf {% data variables.location.product_location %} sowohl über ein {% data variables.enterprise.prodname_managed_user %} als auch über ein persönliches Konto mitzuwirken, kannst du Support bereitstellen. Weitere Informationen findest du unter [Unterstützen von Entwicklern mit mehreren Benutzerkonten auf {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom).
-## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
+## Authentifizieren als {% data variables.enterprise.prodname_managed_user %}
-{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}.
+{% data variables.enterprise.prodname_managed_users_caps %} müssen sich über ihren Identitätsanbieter authentifizieren. Zum Authentifizieren kann ein {% data variables.enterprise.prodname_managed_user %} sein IdP-Anwendungsportal besuchen oder die Anmeldeseite auf {% data variables.product.prodname_dotcom_the_website %} verwenden.
-By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
+Wenn nicht authentifizierte Benutzer*innen versuchen, auf ein Unternehmen mit {% data variables.product.prodname_emus %} zuzugreifen, zeigt {% data variables.product.company_short %} standardmäßig den Fehler 404 an. Unternehmensbesitzer*innen können optional automatische Umleitungen zum einmaligen Anmelden (SSO) anstelle des Fehlers 404 aktivieren. Weitere Informationen findest du unter [Erzwingen von Richtlinien für Sicherheitseinstellungen in deinem Unternehmen](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users).
-{% 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 %} Weitere Informationen findest du unter [Verwalten von Wiederherstellungscodes für dein Unternehmen](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise).
-### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
+### Authentifizieren als {% data variables.enterprise.prodname_managed_user %} über {% data variables.product.prodname_dotcom_the_website %}
-1. Navigate to [https://github.com/login](https://github.com/login).
-1. In the "Username or email address" text box, enter your username including the underscore and short code.
- 
- When the form recognizes your username, the form will update. You do not need to enter your password on this form.
-1. To continue to your identity provider, click **Sign in with your identity provider**.
- 
+1. Navigiere zu [https://github.com/login](https://github.com/login).
+1. Gib im Textfeld „Username or email address“ (Benutzername oder E-Mail-Adresse) deinen Benutzernamen ein, einschließlich des Unterstrichs und des kurzen Codes.
+  Wenn dein Benutzername vom Formular erkannt wird, wird das Formular aktualisiert. Du musst dein Kennwort in diesem Formular nicht eingeben.
+1. Klicke auf **Sign in with your identity provider** (Anmelden mit Identitätsanbieter), um den Vorgang über deinen Identitätsanbieter fortzusetzen.
+ 
-## Usernames and profile information
+## Benutzernamen und Profilinformationen
-{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+{% data variables.product.product_name %} erstellt automatisch einen Benutzernamen für jede Person, indem ein von deinem IdP bereitgestellter Bezeichner normalisiert wird. Weitere Informationen findest du unter [Überlegungen zu Benutzernamen zur externen Authentifizierung](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication).
-A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
+Bei der Bereitstellung von Benutzern kann ein Konflikt auftreten, wenn die eindeutigen Teile des von deinem IdP bereitgestellten Bezeichners während der Normalisierung entfernt werden. Wenn du einen Benutzer aufgrund eines Benutzernamenskonflikts nicht bereitstellen kannst, solltest du den vom IdP bereitgestellten Benutzernamen ändern. Weitere Informationen findest du unter [Beheben von Problemen mit Benutzernamen](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems).
{% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %}
-The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
+Der Profilname und die E-Mail-Adresse von einem {% data variables.enterprise.prodname_managed_user %} wird auch vom IdP bereitgestellt. {% data variables.enterprise.prodname_managed_users_caps %} können ihren Profilnamen oder ihre E-Mail-Adresse auf {% data variables.product.prodname_dotcom %} nicht ändern, und der IdP kann nur eine einzelne E-Mail-Adresse bereitstellen.
-## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
+## Unterstützen von Entwickler*innen mit mehreren Benutzerkonten auf {% data variables.location.product_location %}
-People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work.
+Personen in deinem Team müssen möglicherweise an Ressourcen auf {% data variables.location.product_location %} mitwirken, die sich außerhalb deines {% data variables.enterprise.prodname_emu_enterprise %} befinden. Beispielsweise möchtest du ein separates Unternehmen für die Open-Source Projekte deines Unternehmens verwalten. Da ein {% data variables.enterprise.prodname_managed_user %} nicht an öffentlichen Ressourcen mitwirken kann, müssen Benutzer*innen für diese Arbeit über ein separates, persönliches Konto verfügen.
-People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
+Personen, die von zwei Benutzerkonten auf {% data variables.location.product_location %} und mithilfe einer einzigen Arbeitsstation mitwirken müssen, können Git für einen vereinfachten Prozess konfigurieren. Weitere Informationen findest du unter [Verwalten mehrerer Konten](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts).
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
index 33c6b16923..c67b54174b 100644
--- a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
@@ -1,7 +1,7 @@
---
-title: About support for your IdP's Conditional Access Policy
+title: Informationen zur Unterstützung der IdP-Richtlinie für bedingten Zugriff
shortTitle: Conditional access policy
-intro: 'When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} can validate access to your enterprise and its resources using your IdP''s Conditional Access Policy (CAP).'
+intro: 'Wenn dein Unternehmen OIDC-SSO verwendet, kann {% data variables.product.prodname_dotcom %} den Zugriff auf dein Unternehmen und seine Ressourcen mithilfe der Richtlinie für bedingten Zugriff (Conditional Access Policy, CAP) deines Identitätsanbieters überprüfen.'
product: '{% data reusables.gated-features.emus %}'
versions:
feature: oidc-for-emu
@@ -10,35 +10,40 @@ topics:
- Authentication
- Enterprise
- SSO
+ms.openlocfilehash: aed7008bd008ccfd6303ccbb36f4d6f3bd7002ca
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148179997'
---
-
{% data reusables.enterprise-accounts.azure-emu-support-oidc %}
-## About support for Conditional Access Policies
+## Informationen zur Unterstützung der Richtlinien für bedingten Zugriff
{% data reusables.enterprise-accounts.emu-cap-validates %}
-{% data variables.product.product_name %} supports CAP for any {% data variables.enterprise.prodname_emu_enterprise %} where OIDC SSO is enabled. {% data variables.product.product_name %} enforces your IdP's IP conditions but cannot enforce your device compliance conditions. Enterprise owners can choose to use this IP allow list configuration instead of {% data variables.product.product_name %}'s IP allow list, and can do so once OIDC SSO is configured. For more information about IP allow lists, see "[Restricting network traffic with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."
+{% data variables.product.product_name %} unterstützt CAP für alle {% data variables.enterprise.prodname_emu_enterprise %} mit aktiviertem OIDC-SSO. {% data variables.product.product_name %} erzwingt die IP-Bedingungen deines Identitätsanbieters, kann aber nicht die Gerätekompatibilitätsbedingungen erzwingen. Unternehmensbesitzer*innen können diese Konfiguration für eine Liste zugelassener IP-Adressen anstelle der Liste zugelassener IP-Adressen von {% data variables.product.product_name %} verwenden. Dies ist nach der Konfiguration von OIDC-SSO möglich. Weitere Informationen zu Listen zugelassener IP-Adressen findest du unter [Einschränken des Netzwerkdatenverkehrs mit einer Liste zugelassener IP-Adressen](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list) und [Verwalten zulässiger IP-Adressen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization).
-For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."
+Weitere Informationen zur Verwendung von OIDC mit {% data variables.product.prodname_emus %} findest du unter [Konfigurieren von OIDC für verwaltete Benutzer im Unternehmen](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users) und [Migrieren von SAML zu OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc).
-## Considerations for integrations and automations
+## Überlegungen zu Integrationen und Automatisierungen
-{% data variables.product.prodname_dotcom %} sends the originating IP address to your IdP for validation against your CAP. To make sure actions and apps are not blocked by your IdP's CAP, you will need to make changes to your configuration.
+{% data variables.product.prodname_dotcom %} sendet die IP-Quelladresse zur Überprüfung anhand deiner CAP an deinen IdP. Um sicherzustellen, dass Aktionen und Apps nicht von der CAP deines IdP blockiert werden, musst du Änderungen an deiner Konfiguration vornehmen.
{% data reusables.enterprise-accounts.oidc-gei-warning %}
### {% data variables.product.prodname_actions %}
-Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP.
+Aktionen, die ein {% data variables.product.pat_generic %} verwenden, werden wahrscheinlich von der CAP deines Identitätsanbieters blockiert. {% data variables.product.pat_generic %} sollten von einem Dienstkonto erstellt werden, das dann von IP-Steuerungen in der CAP deines Identitätsanbieters ausgenommen ist.
-If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)."
+Wenn du kein Dienstkonto verwenden kannst, ist die Zulassung der von {% data variables.product.prodname_actions %} verwendeten IP-Bereiche eine weitere Option, Aktionen freizugeben, die {% data variables.product.pat_generic %} verwenden. Weitere Informationen findest du unter [Informationen zu den IP-Adressen von GitHub](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses).
-### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+### {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %}
-When {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} make requests on a member's behalf, {% data variables.product.prodname_dotcom %} will send the IP address of the app's server to your IdP for validation. If the IP address of the app's server is not validated by your IdP's CAP, the request will fail.
+Wenn {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %} Anforderungen im Auftrag eines Mitglieds vornehmen, sendet {% data variables.product.prodname_dotcom %} die IP-Adresse des Servers der App zur Überprüfung an deinen IdP. Wenn die IP-Adresse des Servers der App von der CAP deines IdP nicht überprüft wird, tritt bei der Anforderung ein Fehler auf.
-You can contact the owners of the apps you want to use, ask for their IP ranges, and configure your IdP's CAP to allow access from those IP ranges. If you're unable to contact the owners, you can review your IdP sign-in logs to review the IP addresses seen in the requests, then allow-list those addresses.
+Du kannst die Besitzer der Apps, die du verwenden möchtest, nach ihren IP-Bereichen fragen und die CAP deines IDP konfigurieren, um den Zugriff von diesen IP-Bereichen aus zu ermöglichen. Wenn du dich nicht an die Besitzer wenden kannst, kannst du deinen IdP-Anmeldeprotokollen die in den Anforderungen angezeigten IP-Adressen entnehmen und dann diese Adressen auf die Zulassungsliste setzen.
-If you do not wish to allow all of the IP ranges for all of your enterprise's apps, you can also exempt installed {% data variables.product.prodname_github_apps %} and authorized {% data variables.product.prodname_oauth_apps %} from the IdP allow list. If you do so, these apps will continue working regardless of the originating IP address. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)."
+Wenn du nicht alle IP-Adressbereiche für alle Apps deines Unternehmens zulassen möchtest, kannst du auch installierte {% data variables.product.prodname_github_apps %} und autorisierte {% data variables.product.prodname_oauth_apps %} aus der Liste zugelassener IP-Adressen des Identitätsanbieters ausschließen. In diesem Fall funktionieren diese Apps weiterhin, unabhängig von der ursprünglichen IP-Adresse. Weitere Informationen findest du unter [Erzwingen von Richtlinien für Sicherheitseinstellungen in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps).
diff --git a/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
index a7060df4d0..382b65613d 100644
--- a/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
+++ b/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Packages with Azure Blob Storage
-intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.'
+title: Aktivieren von GitHub Packages mit Azure Blob Storage
+intro: 'Richte die {% data variables.product.prodname_registry %} mit Azure Blob Storage als deinem externen Speicher ein.'
versions:
ghes: '*'
type: tutorial
@@ -9,42 +9,44 @@ topics:
- Packages
- Storage
shortTitle: Enable Packages with Azure
+ms.openlocfilehash: b851f698baba60323cbaaa69122cacdc92ec83c2
+ms.sourcegitcommit: 3ece72cf2d90987575d369c44101d19d3bb06f76
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190387'
---
-
{% warning %}
-**Warnings:**
-- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
-- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
-- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
+**Warnungen:**
+- Es ist wichtig, dass du für deinen Speicherbucket die benötigten Zugriffsbeschränkungsrichtlinien konfigurierst, da {% data variables.product.company_short %} keine spezifischen Objektberechtigungen oder zusätzlichen Zugriffssteuerungslisten (Access Control Lists, ACLs) auf deine Speicherbucketkonfiguration anwendet. Wenn du z. B. deinen Bucket als öffentlich festlegst, kann auf die Daten in diesem Bucket über das öffentliche Internet zugegriffen werden.
+- Wir empfehlen die Nutzung eines dedizierten Buckets für {% data variables.product.prodname_registry %}, der vom Bucket für die Speicherung von {% data variables.product.prodname_actions %} getrennt ist.
+- Konfiguriere den Bucket, den du in Zukunft verwenden möchtest. Es wird nicht empfohlen, den Speicher nach der Verwendung von {% data variables.product.prodname_registry %} noch einmal zu ändern.
{% endwarning %}
-## Prerequisites
+## Voraussetzungen
-Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/).
+Bevor du {% data variables.product.prodname_registry %} in {% data variables.location.product_location_enterprise %} aktivieren und konfigurieren kannst, musst du deinen Azure Blob Storage-Bucket vorbereiten. Zur Vorbereitung deines Azure Blob-Speicherbuckets empfehlen wir dir, die Azure Blob Storage-Dokumente auf der offiziellen [Azure Blob Storage-Dokumentationswebsite](https://docs.microsoft.com/en-us/azure/storage/blobs/) zu lesen.
-## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage
+## Aktivieren von {% data variables.product.prodname_registry %} mit Azure Blob Storage
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_site_admin_settings.packages-tab %}
-{% data reusables.package_registry.enable-enterprise-github-packages %}
-1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %}
+1. Wähle unter „Paketspeicher“ die Option **Azure Blob Storage** aus, und gib den Namen deines Azure-Containers für deinen Paketspeicherbucket sowie die Verbindungszeichenfolge ein.
- - You must create a storage container prior to setting the container name and connection string.
+ - Du musst einen Speichercontainer erstellen, bevor du den Containernamen und die Verbindungszeichenfolge festlegst.
- 
+ 
{% note %}
- **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
- Usage of a SAS Token or SAS URL as connection string is not currently supported.
+ **Hinweis:** Du findest deine Azure-Verbindungszeichenfolge, indem du in deinem Azure-Speicherkonto zum Menü „Zugriffsschlüssel“ navigierst.
+ Die Verwendung eines SAS-Tokens oder einer SAS-URL als Verbindungszeichenfolge wird derzeit nicht unterstützt.
{% endnote %}
{% data reusables.enterprise_management_console.save-settings %}
-## Next steps
+## Nächste Schritte
{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 991873cdca..041431c2e8 100644
--- a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -56,7 +56,7 @@ You can enforce policies to control how members of your enterprise on {% data va
Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% ifversion ghes or ghae %}
@@ -166,7 +166,7 @@ Across all organizations owned by your enterprise, you can set the default branc
Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
index 1286785f70..54a2d63e6c 100644
--- a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
@@ -1,6 +1,6 @@
---
-title: GitHub's SSH key fingerprints
-intro: Public key fingerprints can be used to validate a connection to a remote server.
+title: SSH-Schlüssel-Fingerprints von GitHub
+intro: Öffentliche Schlüssel-Fingerprints können für die Validierung einer Verbindung zu einem Remote-Server benutzt werden.
redirect_from:
- /articles/what-are-github-s-ssh-key-fingerprints
- /articles/github-s-ssh-key-fingerprints
@@ -14,15 +14,21 @@ topics:
- Identity
- Access management
shortTitle: SSH key fingerprints
+ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed
+ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190330'
---
-These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
+Dies sind die öffentlichen Schlüssel-Fingerprints von {% data variables.product.prodname_dotcom %}:
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
-- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
+- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA – veraltet)
- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
-You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
+Du kannst deiner `~.ssh/known_hosts`-Datei die folgenden SSH-Schlüsseleinträge hinzufügen, damit {% data variables.product.prodname_dotcom %}-Hosts nicht manuell überprüft werden müssen:
```text
github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
@@ -30,4 +36,4 @@ github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
```
-For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."
+Weitere Informationen findest du unter [Abrufen von {% data variables.product.prodname_dotcom %}-Metadaten](/rest/meta#get-github-meta-information).
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
index 7815859b8e..8c7a3415ed 100644
--- a/translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
@@ -1,6 +1,6 @@
---
-title: Using SSH over the HTTPS port
-intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.'
+title: SSH über den HTTPS-Port verwenden
+intro: 'Mitunter verweigert die Firewall das Zulassen von SSH-Verbindungen vollständig. Wenn das [HTTPS-Klonen mittels Zwischenspeicherung von Anmeldeinformationen](/github/getting-started-with-github/caching-your-github-credentials-in-git) keine Option ist, kannst Du versuchen, mithilfe einer über den HTTPS-Port hergestellten SSH-Verbindung einen Klonvorgang durchzuführen. Die meisten Firewallregeln sollten dies erlauben, aber Proxyserver beeinträchtigen dies möglicherweise.'
redirect_from:
- /articles/using-ssh-over-the-https-port
- /github/authenticating-to-github/using-ssh-over-the-https-port
@@ -11,14 +11,20 @@ versions:
topics:
- SSH
shortTitle: Use SSH over HTTPS port
+ms.openlocfilehash: 24a56147129e68c674eaf8dc733a203e2b03348a
+ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190322'
---
{% tip %}
-**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
+**{% data variables.product.prodname_ghe_server %}-Benutzer**: Der Zugriff auf {% data variables.product.prodname_ghe_server %} über SSH über den HTTPS-Port wird derzeit nicht unterstützt.
{% endtip %}
-To test if SSH over the HTTPS port is possible, run this SSH command:
+Führe den folgenden Befehl aus, um zu testen, ob SSH über den HTTPS-Port möglich ist:
```shell
$ ssh -T -p 443 git@ssh.github.com
@@ -28,23 +34,23 @@ $ ssh -T -p 443 git@ssh.github.com
{% note %}
-**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
+**Hinweis**: Der Hostname für Port 443 ist `ssh.{% data variables.command_line.backticks %}`, nicht `{% data variables.command_line.backticks %}`.
{% endnote %}
-If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
+Falls das funktioniert hat, prima! Wenn nicht, musst du [möglicherweise die Schritte in unserem Leitfaden zur Problembehandlung ausführen](/articles/error-permission-denied-publickey).
-Now, to clone the repository, you can run the following command:
+Um das Repository zu klonen, kannst du nun den folgenden Befehl ausführen:
```
$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
```
-## Enabling SSH connections over HTTPS
+## SSH-Verbindungen über HTTPS aktivieren
-If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
+Wenn du über Port 443 eine SSH-Verbindung mit `git@ssh.{% data variables.command_line.backticks %}` herstellen kannst, kannst du deine SSH-Einstellungen überschreiben, um zu erzwingen, dass Verbindungen mit {% data variables.location.product_location %} diesen Server und Port durchlaufen.
-To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
+Um dies in deiner SSH-Konfigurationsdatei festzulegen, bearbeite die Datei unter `~/.ssh/config`, und füge den folgenden Abschnitt hinzu:
```
Host {% data variables.command_line.codeblock %}
@@ -53,7 +59,7 @@ Port 443
User git
```
-You can test that this works by connecting once more to {% data variables.location.product_location %}:
+Du kannst testen, ob es funktioniert, indem du erneut eine Verbindung mit {% data variables.location.product_location %} herstellst:
```shell
$ ssh -T git@{% data variables.command_line.codeblock %}
@@ -61,10 +67,9 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
> provide shell access.
```
-## Updating known hosts
+## Aktualisieren bekannter Hosts
-The first time you interact with GitHub after switching to port 443, you may get a warning message
-that the host wasn't found in `known_hosts`, or that it was found by another name.
+Wenn du nach dem Wechsel zu Port 443 zum ersten Mal mit GitHub interagierst, wird möglicherweise eine Warnmeldung angezeigt, dass der Host in `known_hosts` nicht oder unter einem anderen Namen gefunden wurde.
```ShellSession
> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
@@ -74,5 +79,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
```
-It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
-one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
+Du kannst diese Frage bedenkenlos mit „Ja“ beantworten, sofern der SSH-Fingerabdruck mit einem der von GitHub veröffentlichten Fingerabdrücke übereinstimmt. Die Liste der Fingerabdrücke findest du unter [GitHub-Fingerabdrücke für SSH-Schlüssel](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints).
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 571de5c750..f278c9a072 100644
--- a/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -1,6 +1,6 @@
---
-title: About billing for GitHub Actions
-intro: 'If you want to use {% data variables.product.prodname_actions %} beyond the storage or minutes included in your account, you will be billed for additional usage.'
+title: Informationen zur Abrechnung für GitHub Actions
+intro: 'Wenn du {% data variables.product.prodname_actions %} über den in deinem Konto definierten Kontingenten für Speicher oder Minuten verwenden möchtest, wird dir die zusätzliche Nutzung in Rechnung gestellt.'
miniTocMaxHeadingLevel: 3
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
@@ -13,103 +13,104 @@ topics:
- Actions
- Spending limits
shortTitle: Billing for GitHub Actions
+ms.openlocfilehash: f08d06a34d5e7e7f0e2ed49d07a4297c4c6be930
+ms.sourcegitcommit: 06d16bf9a5c7f3e7107f4dcd4d06edae5971638b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179661'
---
-## About billing for {% data variables.product.prodname_actions %}
+## Informationen zur Abrechnung für {% data variables.product.prodname_actions %}
{% data reusables.actions.actions-billing %}
-{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
+{% data reusables.actions.actions-spending-limit-brief %} Weitere Informationen findest du unter [Informationen zu Ausgabenlimits](#about-spending-limits).
-{% ifversion ghec %}
-If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% ifversion ghec %} Wenn du {% data variables.product.prodname_enterprise %} über ein Microsoft Enterprise Agreement erworben hast, kannst du deine Azure-Abonnement-ID mit deinem Unternehmenskonto verbinden, um die Nutzung von {% data variables.product.prodname_actions %} über die im Konto enthaltenen Beträge hinaus zu aktivieren und zu bezahlen. Weitere Informationen findest du unter [Verbinden eines Azure-Abonnements mit deinem Unternehmen](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise).
{% endif %}
-Minutes reset every month, while storage usage does not.
+Die Minuten werden jeden Monat zurückgesetzt, die Speichernutzung wird hingegen nicht zurückgesetzt.
-### Included storage and minutes
+### Enthaltener Speicher und enthaltene Minuten
-{% ifversion actions-hosted-runners %}
-{% note %}
+{% ifversion actions-hosted-runners %} {% note %}
-**Note**: Entitlement minutes cannot be used for Windows and Ubuntu runners over 2-cores. These runners will always be charged for, including in public repos. For more information, see "[Per-minute rates for runners](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)."
+**Hinweis**: Berechtigungsminuten können nicht für Windows- und Ubuntu-Runner mit mehr als 2 Kernen verwendet werden. Diese Runner werden immer in Rechnung gestellt, auch in öffentlichen Repositorys. Weitere Informationen findest du unter [Minutentarife für Runner](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates).
-{% endnote %}
-{% endif %}
+{% endnote %} {% endif %}
-|Product | Storage | Minutes (per month)|
+|Produkt | Storage | Minuten (pro Monat)|
|------- | ------- | ---------|
-| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
+| {% data variables.product.prodname_free_user %} | 500 MB | 2\.000 |
| {% data variables.product.prodname_pro %} | 1 GB | 3,000 |
-| {% data variables.product.prodname_free_team %} for organizations | 500 MB | 2,000 |
+| {% data variables.product.prodname_free_team %} für Organsationen | 500 MB | 2\.000 |
| {% data variables.product.prodname_team %} | 2 GB | 3,000 |
-| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 |
+| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50.000 |
-Jobs that run on Windows and macOS runners that {% data variables.product.prodname_dotcom %} hosts consume minutes at 2 and 10 times the rate that jobs on Linux runners consume. For example, using 1,000 Windows minutes would consume 2,000 of the minutes included in your account. Using 1,000 macOS minutes, would consume 10,000 minutes included in your account.
+Aufträge, die auf Windows- oder MacOS-Läufern auf {% data variables.product.prodname_dotcom %} laufen, verbrauchen doppelt respektive 10-mal mehr Minuten gegenüber Aufträgen auf Linux-Läufern. 1.000 Windows-Minuten würden beispielsweise 2.000 der Minuten verbrauchen, die in deinem Konto enthalten sind. 1.000 macOS-Minuten würden hingegen 10.000 der in deinem Konto enthaltenen Minuten verbrauchen.
-### Minute multipliers
+### Minutenmultiplikatoren
-| Operating system | Minute multiplier |
+| Betriebssystem | Minutenmultiplikator |
|------- | ---------|
| Linux | 1 |
| macOS| 10 |
| Windows | 2 |
-The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+Der Speicher, der von einem Repository verbraucht wird, ist der gesamte Speicher, der von {% data variables.product.prodname_actions %}-Artefakten und {% data variables.product.prodname_registry %} verwendet wird. Deine Speicherkosten setzen sich aus den Nutzungskosten aller Repositorys zusammen, die sich im Besitz deines Kontos befinden. Weitere Informationen zu den Preisen für {% data variables.product.prodname_registry %} findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages).
- If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
+ Wenn die Nutzung deines Kontos diese Limits übersteigt und du ein Ausgabenlimit über 0 USD festgelegt hast, zahlst du 0,008 USD pro GB Speicherplatz pro Tag und pro Minute, je nach dem vom {% data variables.product.prodname_dotcom %}-gehosteten Runner verwendeten Betriebssystem. {% data variables.product.prodname_dotcom %} rundet die von jedem Auftrag verwendeten Minuten und Teilminuten auf die nächste ganze Minute auf.
{% note %}
-**Note:** Minute multipliers do not apply to the per-minute rates shown below.
+**Hinweis:** Die Minutenmultiplikatoren gelten nicht für die unten aufgeführten Minutentarife.
{% endnote %}
-### Per-minute rates
+### Minutentarife
-{% data reusables.billing.billing-standard-runners %}
-{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
+{% data reusables.billing.billing-standard-runners %} {%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
-- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
-- {% data reusables.user-settings.context_switcher %}
-{% ifversion actions-hosted-runners %}
-- For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
-- Entitlement minutes cannot be used for {% data variables.actions.hosted_runner %}s.
-- The {% data variables.actions.hosted_runner %}s are not free for public repositories.
+- Die Anzahl der Aufträge, die du gleichzeitig über alle Repositories in deinem Benutzer- oder Organisationskonto ausführen kannst, hängt von deinem GitHub-Plan ab. Weitere Informationen findest du unter [Nutzungslimits und Abrechnung](/actions/reference/usage-limits-billing-and-administration) für auf {% data variables.product.prodname_dotcom %} gehostete Runner und unter [Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits) (Nutzungslimits für selbstgehostete Runner).
+- {% data reusables.user-settings.context_switcher %} {% ifversion actions-hosted-runners %}
+- Für {% data variables.actions.hosted_runner %} fallen keine zusätzlichen Kosten für Konfigurationen an, die einem {% data variables.actions.hosted_runner %} öffentliche statische IP-Adressen zuweisen. Weitere Informationen zu {% data variables.actions.hosted_runner %}n findest du unter [Verwenden von {% data variables.actions.hosted_runner %}n](/actions/using-github-hosted-runners/using-larger-runners).
+- Berechtigungsminuten können nicht für {% data variables.actions.hosted_runner %} verwendet werden.
+- {% data variables.actions.hosted_runner %} sind für öffentliche Repositorys nicht kostenfrei.
{% endif %}
-## Calculating minute and storage spending
+## Minuten- und Speicherausgaben berechnen
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_actions %}
-At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account.
+Am Ende des Monats berechnet {% data variables.product.prodname_dotcom %} die Minuten- und Speicherkosten, die über den in deinem Konto enthaltenen Kontingent liegen.
-### Sample minutes cost calculation
+### Beispiel für die Kostenberechnung von Minuten
-For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
+Wenn deine Organisation beispielsweise {% data variables.product.prodname_team %} verwendet und unbegrenzte Ausgaben zulässt, würde der Verbrauch von 5.000 Minuten abhängig von den für die Ausführung von Aufträgen verwendeten Betriebssystemen die gesamten Speicher- und Minutenkosten um 56 USD überschreiten.
-- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
- - 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
- - 2,000 Windows minutes at $0.016 USD per minute = $32 USD.
+- 5\.000 Minuten (3.000 Linux und 2.000 Windows) = 56 USD (24 USD + 32 USD).
+ - 3\.000 Linux-Minuten zu 0,008 USD pro Minute = 24 USD.
+ - 2\.000 Windows-Minuten zu 0,016 USD pro Minute = 32 USD.
-{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month.
+{% data variables.product.prodname_dotcom %} berechnet deinen Speicherverbrauch für jeden Monat auf Stundenbasis während dieses Monats.
-### Sample storage cost calculation
+### Beispiel für die Berechnung der Speicherkosten
-For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be:
+Wenn du z. B. im März 10 Tage lang 3 GB Speicher und 21 Tage lang 12 GB verwendet hast, berechnet sich die Speichernutzung wie folgt:
-- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours
-- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours
-- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours
-- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months
+- 3 GB x 10 Tage x (24 Stunden pro Tag) = 720 GB-Stunden
+- 12 GB x 21 Tage x (24 Stunden pro Tag) = 6,048 GB-Stunden
+- 720 GB-Stunden + 6,048 GB-Stunden = 6,768 GB-Stunden
+- 6,768 GB-Stunden / (744 Stunden pro Monat) = 9.0967 GB-Monate
-At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
+Am Ende des Monats rundet {% data variables.product.prodname_dotcom %} deine Speichernutzung auf das nächste MB. Daher würde deine Speichernutzung im März 9,097 GB betragen.
-Your {% data variables.product.prodname_actions %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
+Deine {% data variables.product.prodname_actions %}-Nutzung teilt das bestehende Rechnungsdatum, die Zahlungsmethode und die Quittung. {% data reusables.dotcom_billing.view-all-subscriptions %}
-## About spending limits
+## Über Ausgabenlimits
{% data reusables.actions.actions-spending-limit-detailed %}
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+Informationen zum Verwalten und Ändern des Ausgabenlimits deines Kontos findest du unter [Verwalten deines Ausgabenlimits für {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions).
{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
diff --git a/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md b/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
index d6daeb7614..55508dc822 100644
--- a/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
+++ b/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
@@ -1,6 +1,6 @@
---
-title: Managing privately reported security vulnerabilities
-intro: Repository maintainers can manage security vulnerabilities that have been privately reported to them by security reseachers for repositories where private vulnerability reporting is enabled.
+title: Verwalten privat gemeldeter Sicherheitsrisiken
+intro: 'Repository-Maintainer können Sicherheitsrisiken verwalten, die privat von Sicherheitsforschern für Repositorys gemeldet wurden, in denen private Sicherheitsrisikomeldungen aktiviert sind.'
permissions: 'Anyone with admin permissions to a repository can see, review, and manage privately-reported vulnerabilities for the repository.'
versions:
fpt: '*'
@@ -11,35 +11,38 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Manage vulnerability reports
+ms.openlocfilehash: 942533788dc6ad9280ddc023f583462c7a0ff7f8
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160294'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## Informationen zum privaten Melden eines Sicherheitsrisikos
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to you using a simple form.
+Dank der Möglichkeit zum privaten Melden von Sicherheitsrisiken können Sicherheitsforscher Sicherheitsrisiken mühelos über ein einfaches Formular direkt an dich melden.
-When a security researcher reports a vulnerability privately, you are notified and can choose to either accept it, ask more questions, or reject it. If you accept the report, you're ready to collaborate on a fix for the vulnerability in private with the security researcher.
+Wenn ein Sicherheitsforscher privat eine Sicherheitslücke meldet, wirst du benachrichtigt und kannst die Meldung entweder akzeptieren, weitere Fragen stellen oder die Meldung ablehnen. Wenn du die Meldung akzeptierst, bist du bereit, gemeinsam mit dem Sicherheitsforscher privat an einer Lösung für das Sicherheitsrisiko zu arbeiten.
-## Managing security vulnerabilities that are privately reported
+## Verwalten privat gemeldeter Sicherheitsrisiken
-{% data variables.product.prodname_dotcom %} notifies repository maintainers when security researchers privately report vulnerabilities in their repository, and sends notifications if maintainers watch the repository or if they have notifications enabled for the repository. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
+{% data variables.product.prodname_dotcom %} benachrichtigt Repository-Maintainer, wenn Sicherheitsforscher privat Sicherheitsrisiken in ihrem Repository melden, und sendet Benachrichtigungen, wenn Maintainer das Repository überwachen oder Benachrichtigungen für das Repository aktiviert haben. Weitere Informationen findest du unter [Konfigurieren von Benachrichtigungen](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications).
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click the advisory you want to review. An advisory that is privately reported will have a status of `Needs triage`.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Klicke auf die Empfehlung, die du überprüfen möchtest. Eine privat gemeldete Empfehlung hat den Status `Needs triage`.
- 
+ 
-2. Carefully review the report. You can:
- - Collaborate with the security researcher on a patch in private, by clicking **Start a temporary private fork**. This gives you a place for further discussions with the contributor without changing the status of the proposed advisory from `Needs triage`.
- - Accept the vulnerability report as a draft advisory on {% data variables.product.prodname_dotcom %}, by clicking **Accept and open as draft**. If you choose this option:
- - This doesn't make the report public.
- - The report becomes a draft repository security advisory and you can work on it in the same way as any draft advisory that you create.
- For more information on security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."
- - Reject the report by clicking **Close security advisory**. Where possible, you should add a comment explaining why you don't consider the report a security risk before you close the advisory.
+2. Überprüfe die Meldung sorgfältig. Du hast folgende Möglichkeiten:
+ - Klicke auf **Mit temporärem privatem Fork beginnen**, um zusammen mit dem Sicherheitsforscher privat an einem Patch zu arbeiten. Dadurch erhältst du eine Umgebung für weitere Diskussionen mit dem Mitwirkenden, ohne den Status `Needs triage` der vorgeschlagenen Empfehlung zu ändern.
+ - Klicke auf **Akzeptieren und als Entwurf öffnen**, um die Sicherheitsrisikomeldung als Empfehlungsentwurf für {% data variables.product.prodname_dotcom %} zu akzeptieren. Bei dieser Option gilt Folgendes:
+ - Die Meldung wird dadurch nicht öffentlich.
+ - Die Meldung wird zu einem Entwurf für eine Repositorysicherheitsempfehlung, und du kannst sie auf die gleiche Weise bearbeiten wie alle von dir erstellten Empfehlungsentwürfe.
+ Weitere Informationen zu Sicherheitsempfehlungen findest du unter [Informationen zu Sicherheitsempfehlungen für Repositorys](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories).
+ - Klicke auf **Sicherheitsempfehlung schließen**, um die Meldung abzulehnen. Füge vor dem Schließen der Empfehlung nach Möglichkeit einen Kommentar hinzu, um zu erläutern, warum du die Meldung nicht als Sicherheitsrisiko betrachtest.
- 
\ No newline at end of file
+ 
diff --git a/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md b/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
index 521fa86d92..2d3063f228 100644
--- a/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
+++ b/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
@@ -1,6 +1,6 @@
---
-title: Privately reporting a security vulnerability
-intro: Some public repositories configure security advisories so that anyone can report security vulnerabilities directly and privately to the maintainers.
+title: Privates Melden eines Sicherheitsrisikos
+intro: 'Bei einigen öffentlichen Repositorys sind die Sicherheitsempfehlungen so konfiguriert, dass jede Person Sicherheitsrisiken direkt und privat an die Maintainer*innen melden kann.'
versions:
fpt: '*'
ghec: '*'
@@ -10,61 +10,64 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Privately reporting
+ms.openlocfilehash: 7f4f208bd2724608cf9955efd82a256c3479e884
+ms.sourcegitcommit: 2ff4a43f0b14939da79d56c54402cfee8d90ae23
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/17/2022
+ms.locfileid: '148169557'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## Informationen zum privaten Melden eines Sicherheitsrisikos
-Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
+Sicherheitsforscher fühlen sich häufig dafür verantwortlich, Benutzer vor einer Sicherheitslücke zu warnen, die ausgenutzt werden könnte. Wenn es keine eindeutigen Anweisungen dazu gibt, die Verwalter des Repositorys zu kontaktieren, das das Sicherheitsrisiko beinhaltet, haben Sicherheitsforscher möglicherweise keine andere Wahl, als in sozialen Medien über das Sicherheitsrisiko zu informieren, direkte Nachrichten an den Verwalter zu senden oder sogar öffentliche Issues zu erstellen. Diese Situation kann möglicherweise zu einer Veröffentlichung der Details des Sicherheitsrisikos führen.
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to repository maintainer using a simple form.
+Ein privates Melden von Sicherheitsrisiken ermöglicht es Sicherheitsforscher*innen, Sicherheitsrisiken leicht über ein einfaches Formular direkt an die Maintainer*innen von Repositorys zu melden.
-For security researchers, the benefits of using private vulnerability reporting are:
-- Less frustration, and less time spent trying to figure out how to contact the maintainer.
-- A smoother process for disclosing and discussing vulnerability details.
-- The opportunity to discuss vulnerability details privately with repository maintainer.
+Für Sicherheitsforscher*innen bietet ein privates Melden von Sicherheitsrisiken die folgenden Vorteile:
+- Weniger Frust und weniger Zeit, die aufgewendet werden muss, um herauszufinden, wie man den bzw. die Maintainer*in kontaktieren kann
+- Ein reibungsloserer Prozess für das Offenlegen und Besprechen von Details zu Sicherheitsrisiken
+- Die Möglichkeit, Details zu Sicherheitsrisiken privat mit dem bzw. der Maintainer*in des Repositorys zu besprechen
{% note %}
-**Note:** If the repository doesn't have private vulnerabiliy reporting enabled, you need to initiate the reporting process by following the instructions in the security policy for the repository, or create an issue asking the maintainers for a preferred security contact. For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
+**Hinweis:** Wenn das private Melden von Sicherheitsrisiken für das Repository nicht aktiviert ist, musst du den Meldeprozess initiieren, indem du die Anweisungen in der Sicherheitsrichtlinie für das Repository befolgst oder ein Issue erstellst, in dem du den bzw. die Maintainer*in nach einem bevorzugten Sicherheitskontakt fragst. Weitere Informationen findest du unter [Informationen zur koordinierten Offenlegung von Sicherheitsrisiken](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github).
{% endnote %}
-## Privately reporting a security vulnerability
+## Privates Melden eines Sicherheitsrisikos
-Security researchers can privately report a security vulnerability to repository maintainers.
+Sicherheitsforscher*innen können Sicherheitsrisiken privat an Repository-Maintainer*innen melden.
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **Report a vulnerability** to open the advisory form.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Klicke auf **Sicherheitsrisiko melden**, um das Empfehlungsformular zu öffnen.
- 
+ 
-2. Fill in the advisory details form.
+2. Fülle das Formular für die Empfehlungsdetails aus.
{% tip %}
- **Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
+ **Tipp:** In diesem Formular sind nur der Titel und die Beschreibung obligatorisch. (Im allgemeinen Entwurf für das Formular für Sicherheitsempfehlungen, das der bzw. die Repository-Maintainer*in initiiert, ist die Angabe eines Ökosystems ebenfalls erforderlich.) Es wird jedoch empfohlen, dass Sicherheitsforscher*innen so viele Informationen wie möglich im Formular angeben, damit die Maintainer*innen eine fundierte Entscheidung in Bezug auf die übermittelte Meldung treffen können. Du kannst die von unseren Sicherheitsexperten verwendete Vorlage aus {% data variables.product.prodname_security %} übernehmen, was im [`github/securitylab`-Repository](https://github.com/github/securitylab/blob/main/docs/report-template.md) verfügbar ist.
{% endtip %}
- For more information about the fields available and guidance on filling in the form, see "[Creating a repository security advisory](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[Best practices for writing repository security advisories](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
+ Weitere Informationen zu den verfügbaren Feldern sowie einen Leitfaden zum Ausfüllen des Formulars findest du unter [Erstellen einer Sicherheitsempfehlung für ein Repository](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory) und [Bewährte Methoden für das Schreiben von Sicherheitsempfehlungen für Repositorys](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories).
-1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
+1. Klicke unten im Formular auf **Meldung übermitteln**. {% data variables.product.prodname_dotcom %} zeigt dann eine Meldung an, dass die Maintainer*innen benachrichtigt wurden und eine ausstehende Erwähnung für dich in Bezug auf diese Sicherheitsempfehlung vorliegt.
- 
+ 
{% tip %}
- **Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
+ **Tipp:** Wenn die Meldung übermittelt wird, fügt {% data variables.product.prodname_dotcom %} die Person, die das Sicherheitsrisiko gemeldet hat, automatisch als Projektmitarbeiter*in und erwähnte*n Benutzer*in in der vorgeschlagenen Empfehlung hinzu.
{% endtip %}
-1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge that private fork.
+1. Klicke optional auf **Mit temporärem privatem Fork beginnen**, wenn du beginnen möchtest, das Problem zu beheben. Beachte, dass nur der bzw. die Repository-Maintainer*in einen Merge für diesen privaten Fork durchführen kann.
- 
+ 
-The next steps depend on the action taken by the repository maintainer. For more information, see "[Managing privately reported security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)."
+Die nächsten Schritte hängen davon ab, welche Maßnahmen der bzw. die Repository-Maintainer*in ergreift. Weitere Informationen findest du unter [Verwalten von privat gemeldeten Sicherheitsrisiken](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities).
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
index 8f8ea3d298..4b3b9e552c 100644
--- a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository security advisory
-intro: You can create a draft security advisory to privately discuss and fix a security vulnerability in your open source project.
+title: Erstellen einer Sicherheitsempfehlung für ein Repository
+intro: 'Du kannst einen Entwurf eines Sicherheitshinweises erstellen, um privat über die Sicherheitslücke in Deinem Open-Source-Projekt zu diskutieren und sie zu beheben.'
redirect_from:
- /articles/creating-a-maintainer-security-advisory
- /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
@@ -15,31 +15,31 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Create repository advisories
+ms.openlocfilehash: 5c78a8b0c0a2d5085a876de2b0788ef093c4c6b1
+ms.sourcegitcommit: 74c60a4564bcc17e47b5a67941ac6d9fe13b6a5c
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/30/2022
+ms.locfileid: '148186155'
---
-
-Anyone with admin permissions to a repository can create a security advisory.
+Jeder, der über Administratorberechtigungen für ein Repository verfügt, kann einen Sicherheitshinweis erstellen.
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-## Creating a security advisory
+## Erstellen einer Sicherheitsempfehlung
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **New draft security advisory** to open the draft advisory form. The fields marked with an asterisk are required.
- 
-1. Type a title for your security advisory.
-{% data reusables.repositories.security-advisory-edit-details %}
-{% data reusables.repositories.security-advisory-edit-severity %}
-{% data reusables.repositories.security-advisory-edit-cwe-cve %}
-{% data reusables.repositories.security-advisory-edit-description %}
-1. Click **Create draft security advisory**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Klicke auf **Neue Sicherheitsempfehlung entwerfen**, um das Entwurfsformular für Empfehlungen zu öffnen. Mit einem Sternchen gekennzeichnete Felder müssen ausgefüllt werden.
+ 
+1. Gib einen Titel für den Sicherheitshinweis ein.
+{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
+1. Klicke auf **Entwurf für Sicherheitsempfehlung erstellen**.
+ 
-## Next steps
+## Nächste Schritte
-- Comment on the draft security advisory to discuss the vulnerability with your team.
-- Add collaborators to the security advisory. For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)."
-- Privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)."
-- Add individuals who should receive credit for contributing to the security advisory. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)."
-- Publish the security advisory to notify your community of the security vulnerability. For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
+- Du kannst Den Entwurf des Sicherheitshinweises kommentieren, um die Schwachstelle mit Deinem Team zu diskutieren.
+- Füge Mitarbeiter zum Sicherheitshinweis hinzu. Weitere Informationen findest du unter [Hinzufügen eines Mitarbeiters zu einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory).
+- Privat mit anderen zusammenarbeiten, um die Schwachstelle in einem temporären privaten Fork zu beheben. Weitere Informationen findest du unter [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability).
+- Füge Personen hinzu, die eine Anerkennung für einen Beitrag zur Sicherheitsempfehlung erhalten sollen. Weitere Informationen findest du unter [Bearbeiten einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories).
+- Veröffentliche den Sicherheitshinweis, um Deine Community über die Sicherheitslücke zu informieren. Weitere Informationen findest du unter [Veröffentlichen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/publishing-a-repository-security-advisory).
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
index aeb477c475..f0a929ae47 100644
--- a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a codespace for a repository
-intro: You can create a codespace for a branch in a repository to develop online.
+title: Erstellen eines Codespaces für ein Repository
+intro: 'Du kannst einen Codespace für einen Branch in einem Repository erstellen, um online entwickeln zu können.'
redirect_from:
- /github/developing-online-with-github-codespaces/creating-a-codespace
- /github/developing-online-with-codespaces/creating-a-codespace
@@ -14,95 +14,100 @@ topics:
- Fundamentals
- Developer
shortTitle: Create a codespace for a repo
+ms.openlocfilehash: 409c946feda4ffbd3d9ab615b6ea07fabee3f530
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188320'
---
+## Informationen zum Erstellen eines Codespaces für ein Repository
-## About creating a codespace for a repository
+{% data reusables.codespaces.ways-to-create-a-codespace %} Verwende die Registerkarten in diesem Artikel, um Anweisungen für jede dieser Möglichkeiten zum Erstellen eines Codespaces anzuzeigen.
-{% data reusables.codespaces.ways-to-create-a-codespace %} Use the tabs in this article to display instructions for each of these ways of creating a codespace.
-
-{% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+{% data reusables.codespaces.starting-new-project-template %} Weitere Informationen findest du unter „[Erstellen eines Codespaces aus einer Vorlage](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)“.
{% note %}
-**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[Using Codespaces in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
+**Hinweis**: Wenn du eine JetBrains-IDE verwendest, kannst du {% data variables.product.prodname_cli %} verwenden, um einen Codespace zu erstellen. Anschließend kannst du die JetBrains Gateway-Anwendung verwenden, um den Codespace in einer JetBrains-IDE zu öffnen. Weitere Informationen findest du unter [Verwenden von Codespaces in der JetBrains-IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide).
{% endnote %}
-You can use {% data variables.product.prodname_github_codespaces %} on your personal {% data variables.product.prodname_dotcom_the_website %} account, with the quota of free use included each month for accounts on the Free and Pro plans. {% data reusables.codespaces.codespaces-continue-by-paying %}
+Du kannst {% data variables.product.prodname_github_codespaces %} für dein persönliches {% data variables.product.prodname_dotcom_the_website %}-Konto verwenden, wobei das Kontingent der kostenlosen Nutzung jeden Monat für Konten im Free- und Pro-Tarif enthalten ist. {% data reusables.codespaces.codespaces-continue-by-paying %}
-Organizations can enable members and outside collaborators to create and use codespaces at the organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
+Organisationen können Mitgliedern und externen Mitarbeitern das Erstellen und Verwenden von Codespaces auf Kosten der Organisation ermöglichen. Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_github_codespaces %} für deine Organisation](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization).
{% data reusables.codespaces.codespaces-are-personal %}
-If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch.
+Wenn du einen Codespace aus einem Repository erstellst, wird der Codespace einem bestimmten Branch zugeordnet, der nicht leer sein kann. Du kannst pro Repository oder sogar pro Branch mehr als einen Codespace erstellen.
{% data reusables.codespaces.you-can-see-all-your-codespaces %}
-### The codespace creation process
+### Der Codespace-Erstellungsprozess
-When you create a codespace, a number of steps happen to create and connect you to your development environment:
+Wenn du einen Codespace erstellst, erfolgt eine Reihe von Schritten zum Erstellen und Herstellen einer Verbindung mit deiner Entwicklungsumgebung:
-- Step 1: VM and storage are assigned to your codespace.
-- Step 2: Container is created and your repository is cloned.
-- Step 3: You can connect to the codespace.
-- Step 4: Codespace continues with post-creation setup.
+- Schritt 1: VM und Speicher werden deinem Codespace zugewiesen.
+- Schritt 2: Der Container wird erstellt, und dein Repository wird geklont.
+- Schritt 3: Du kannst eine Verbindung mit dem Codespace herstellen.
+- Schritt 4: Der Codespace wird mit dem Setup nach der Erstellung fortgesetzt.
-For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
+Weitere Informationen dazu, was passiert, wenn du einen Codespace erstellst, findest du unter [Vertiefung](/codespaces/getting-started/deep-dive).
-For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)."
+Weitere Informationen zum Lebenszyklus eines Codespaces findest du unter [Der Codespace-Lebenszyklus](/codespaces/getting-started/the-codespace-lifecycle).
-If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+Wenn du Git-Hooks für deinen Codespace verwenden möchtest, solltest du die Hooks mithilfe der [`devcontainer.json`-Lebenszyklusskripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts) einrichten, z. B. `postCreateCommand` während Schritt 4. Da dein Codespace-Container erstellt wird, nachdem das Repository geklont wurde, gelten alle im Containerimage konfigurierten [Git-Vorlagenverzeichnisse](https://git-scm.com/docs/git-init#_template_directory) nicht für deinen Codespace. Hooks müssen stattdessen installiert werden, nachdem der Codespace erstellt wurde. Weitere Informationen zur Verwendung von `postCreateCommand` findest du in der [`devcontainer.json` Referenz](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in der {% data variables.product.prodname_vscode_shortname %}-Dokumentation.
{% data reusables.codespaces.use-visual-studio-features %}
{% data reusables.codespaces.prebuilds-crossreference %}
-## Creating a codespace for a repository
+## Erstellen eines Codespaces für ein Repository
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create a codespace for.
+1. Wähle im Dropdownmenü „Branch“ unterhalb des Repositorynamens den Branch aus, für den du einen Codespace erstellen möchtest.
- 
+ 
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. Klicke auf die Schaltfläche **{% octicon "code" aria-label="The code icon" %} Code** und dann auf die Registerkarte **Codespaces**.
- 
+ 
- If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
+ Wenn Codespaces für dieses Repository einer Organisation oder dem übergeordneten Unternehmen in Rechnung gestellt werden können, wird unterhalb der Schaltfläche **Codespace auf BRANCH erstellen** eine Mitteilung angezeigt, wer für den Codespace bezahlt.
-1. Create your codespace, either using the default options, or after configuring advanced options:
+1. Erstelle deinen Codespace entweder mithilfe der Standardoptionen oder nach dem Konfigurieren erweiterter Optionen:
- * **Use the default options**
+ * Verwenden der **Standardoptionen**
- To create a codespace using the default options, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). Alternatively, if you don't currently have any codespaces for this repository, you can click **Create codespace on BRANCH**.
+ Um einen Codespace mit den Standardoptionen zu erstellen, klicke auf das Pluszeichen ({% octicon "plus" aria-label="The plus icon" %}). Wenn du derzeit keine Codespaces für dieses Repository hast, kannst du alternativ auf **Codespace in BRANCH erstellen** klicken.
- * **Configure options**
+ * **Konfigurieren von Optionen**
- To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file:
+ So konfigurierst du erweiterte Optionen für deinen Codespace, z. B. einen anderen Computertyp oder eine bestimmte Datei `devcontainer.json`:
- 1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab and select **New with options**.
+ 1. Klicke oben rechts auf der Registerkarte **Codespaces** auf die Auslassungspunkte ( **...** ), und wähle dann **Neu mit Optionen** aus.
- 
+ 
- 1. On the options page for your codespace, choose your preferred options from the dropdown menus.
+ 1. Wähle auf der Seite „Optionen“ für deinen Codespace deine bevorzugten Optionen aus den Dropdownmenüs aus.
- 
+ 
{% note %}
- **Notes**
+ **Hinweise**
- * You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
- * The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
- * For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
- * For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+ * Du kannst die Optionsseite mit einer Textmarke versehen, damit du schnell einen Codespace für dieses Repository und diesen Branch erstellen kannst.
+ * Die Seite [https://github.com/codespaces/new](https://github.com/codespaces/new) bietet eine schnelle Möglichkeit, einen Codespace für jedes Repository und jeden Branch zu erstellen. Du kannst schnell zu dieser Seite gelangen, indem du `codespace.new` in die Adressleiste deines Browsers eingibst.
+ * Weitere Informationen zur Datei `devcontainer.json` findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson).
+ * Weitere Informationen zu Computertypen findest du unter [Ändern des Computertyps für deinen Codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types).
* {% data reusables.codespaces.codespaces-machine-type-availability %}
{% endnote %}
- 1. Click **Create codespace**.
+ 1. Klicke auf **Codespace erstellen**.
{% endwebui %}
@@ -116,30 +121,30 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
{% data reusables.cli.cli-learn-more %}
-To create a new codespace, use the `gh codespace create` subcommand.
+Verwende zum Erstellen eines neuen Codespaces den Unterbefehl `gh codespace create`.
```shell
gh codespace create
```
-You are prompted to choose a repository. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
+Du wirst aufgefordert, ein Repository auszuwählen. Wenn Codespaces für dieses Repository einer Organisation oder dem übergeordneten Unternehmen in Rechnung gestellt werden können, wird eine Mitteilung angezeigt, wer für den Codespace bezahlt. Du wirst dann aufgefordert, einen Branch, eine Entwicklungscontainer-Konfigurationsdatei (sofern mehrere vorhanden sind) und einen Computertyp (sofern mehrere vorhanden sind) auszuwählen.
-Alternatively, you can use flags to specify some or all of the options:
+Alternativ kannst du Flags verwenden, um einige oder alle Optionen anzugeben:
```shell
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
```
-In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
+In diesem Beispiel ersetze `owner/repo` durch den Repositorybezeichner. Ersetze `branch` durch den Namen des Branch oder den vollständigen SHA-Hash des Commits, den du zunächst im Codespace auschecken möchtest. Wenn du das `-r`-Flag ohne das `b`-Flag verwendest, wird der Codespace aus dem Standardbranch erstellt.
-Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+Ersetze `path` durch den Pfad zur Dev-Containerkonfigurationsdatei, die du für den neuen Codespace verwenden möchtest. Wenn du dieses Flag auslässt und mehrere Dev-Containerdateien verfügbar sind, wirst du aufgefordert, eine davon in einer Liste auszuwählen. Weitere Informationen zur Dev-Containerkonfigurationsdatei findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers).
-Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
+Ersetze `machine-type` durch einen gültigen Bezeichner für einen verfügbaren Computertyp. Bezeichner sind Zeichenfolgen wie `basicLinux32gb` und `standardLinux32gb`. Der Typ der verfügbaren Computer hängt vom Repository, deinem persönlichen Konto und deinem Standort ab. Wenn du einen ungültigen oder nicht verfügbaren Computertyp eingibst, werden die verfügbaren Typen in der Fehlermeldung angezeigt. Wenn du dieses Flag auslässt und mehrere Computertypen verfügbar sind, wirst du aufgefordert, einen Typ aus einer Liste auszuwählen.
-For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
+Ausführliche Informationen zu den Optionen für diesen Befehl findest du im [{% data variables.product.prodname_cli %}-Handbuch](https://cli.github.com/manual/gh_codespace_create).
{% endcli %}
-## Further reading
-- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
-- "[Adding an 'Open in {% data variables.product.prodname_github_codespaces %}' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
+## Weiterführende Themen
+- [Öffnen eines vorhandenen Codespaces](/codespaces/developing-in-codespaces/opening-an-existing-codespace)
+- [Hinzufügen eines „In {% data variables.product.prodname_github_codespaces %} öffnen“-Badges](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)
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
index 842a20e971..e87d857fc9 100644
--- 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
@@ -1,6 +1,6 @@
---
-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.
+title: Erstellen eines Codespaces aus einer Vorlage
+intro: 'Wenn du mit einem neuen Projekt beginnst, kannst du einen Codespace aus einer leeren Vorlage erstellen oder eine Vorlage auswählen, die speziell für die geplante Tätigkeit entwickelt wurde.'
versions:
fpt: '*'
ghec: '*'
@@ -11,92 +11,95 @@ topics:
- Developer
shortTitle: Create a codespace from a template
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 9e7ee0d110e962fa755f5f57cc70bc3cab341808
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188312'
---
+## Informationen zu Vorlagen für {% data variables.product.prodname_github_codespaces %}
-## 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.
+Wenn du mit einem neuen Projekt beginnst, kannst du schnell mit der Entwicklung beginnen, indem du einen Codespace aus einer Vorlage erstellst. Du kannst in einer cloudbasierten Entwicklungsumgebung an deinem Projekt arbeiten, deine Dateien in der Cloud speichern und deine Arbeit in einem neuen Remoterepository veröffentlichen, das du für andere freigeben oder auf deinen lokalen Computer klonen kannst.
{% 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)."
+**Hinweis**: Codespaces, die aus einer Vorlage und nicht aus einem Repository erstellt wurden, werden immer deinem persönlichen Konto in Rechnung gestellt. Weitere Informationen 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).
{% 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)."
+Du kannst mit einer leeren Vorlage beginnen, aus Vorlagen wählen, die von {% data variables.product.company_short %} für gängige Technologien wie React oder Jupyter Notebook bereitgestellt werden, oder einen Codespace aus einem beliebigen Vorlagenrepository auf {% data variables.product.prodname_dotcom %} starten. Wenn du eine leere Vorlage verwendest, beginnst du mit einem leeren Verzeichnis, Zugriff auf cloudbasierte Computeressourcen und den Tools, Sprachen und Laufzeitumgebungen, die mit dem Standardcodespaceimage vorinstalliert wurden. Wenn du andere Vorlagen verwendest, erhältst du Startdateien für die Technologie, mit der du arbeitest, sowie in der Regel einige zusätzliche Dateien wie eine README-Datei, eine `.gitignore`-Datei und Konfigurationsdateien für Entwicklungscontainer, die eine benutzerdefinierte Umgebungskonfiguration enthalten. Weitere Informationen zu Entwicklungscontainern und dem Standardimage findest du unter [Einführung in Entwicklungscontainer](/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.
+Wenn du beispielsweise einen Codespace aus der React-Vorlage von {% data variables.product.company_short %} erstellst, gelangst du in einen Arbeitsbereich, der Vorlagendateien (wie `index.js`, `app.js` und `package.json`) für eine einfache Anwendung enthält. Kurz nachdem der Codespace geöffnet wurde, wird automatisch ein Entwicklungsserver gestartet, und du kannst die ausgeführte Anwendung auf einer einfachen Browserregisterkarte im {% data variables.product.prodname_vscode_shortname %}-Webclient anzeigen.
-
+
-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.
+Die in Vorlagen enthaltenen Dateien und Konfigurationen werden in Vorlagenrepositorys definiert. Das Vorlagenrepository wird beim Erstellen des Codespaces in deinen Codespace geklont. Danach wird die Verbindung unterbrochen, und dein Codespace wird erst dann mit einem Remoterepository verknüpft, wenn du es in einem veröffentlichst.
{% 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)."
+**Tipp:** Um Personen bei den ersten Schritten mit deinem Framework, deiner Bibliothek oder einem anderen Projekt zu helfen, kannst du ein Vorlagenrepository zur Verwendung mit {% data variables.product.prodname_github_codespaces %} einrichten. Weitere Informationen findest du unter [Einrichten eines Vorlagenrepositorys für {% 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
+## Erstellen eines Codespaces aus einer {% data variables.product.company_short %}-Vorlage
-Templates maintained by {% data variables.product.company_short %}, including the blank template, are available from the "Your codespaces" page.
+Vorlagen, die von {% data variables.product.company_short %} verwaltet werden (einschließlich der leeren Vorlage), sind auf der Seite „Deine Codespaces“ verfügbar.
-{% 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.
+{% data reusables.codespaces.your-codespaces-procedure-step %} {% data reusables.codespaces.view-all-templates-step %}
+1. Klicke optional auf den Namen der Vorlage, um das Vorlagenrepository anzuzeigen, das die Dateien für eine Vorlage enthält.
- 
+ 
-1. Under the template you want to launch, click **Use this template**.
+1. Klicke unter der Vorlage, die du starten möchtest, auf **Diese Vorlage verwenden**.
- 
+ 
{% data reusables.codespaces.template-codespaces-default-editor %}
-## Creating a codespace from a template repository
+## Erstellen eines Codespaces aus einem Vorlagenrepository
-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)."
+Du kannst einen Codespace aus einem beliebigen Vorlagenrepository erstellen und dann deine Arbeit in einem neuen Repository veröffentlichen, wenn du bereit bist. Weitere Informationen zu Vorlagenrepositorys findest du unter [Erstellen eines Repositorys aus einer Vorlage](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates).
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.codespaces.open-template-in-codespace-step %}
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.codespaces.open-template-in-codespace-step %}
{% note %}
- **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)."
+ **Hinweis:** Wenn du ein*e Maintainer des Vorlagenrepositorys bist und Änderungen an das Vorlagenrepository selbst committen möchtest, solltest du einen Codespace aus dem Dropdownmenü **{% octicon "code" aria-label="The code icon" %}-Code** erstellen. Weitere Informationen findest du unter [Erstellen eines Codespaces für ein 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 %}
+## Veröffentlichen in einem Repository auf {% data variables.product.product_name %}
{% data reusables.codespaces.about-publishing-templates %}
-### Publishing from {% data variables.product.prodname_vscode_shortname %}
+### Veröffentlichen aus {% 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:
+Wenn ein Codespace veröffentlicht wird, hast du Zugriff auf eine größere Auswahl an Optionen, mit denen du deine {% data variables.product.prodname_github_codespaces %}-Benutzeroberfläche anpassen kannst. Du hast beispielsweise folgende Möglichkeiten:
-- 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)").
+- Ändere den Computertyp deines Codespaces, um sicherzustellen, dass du Ressourcen verwendest, die für die von dir ausgeführte Arbeit geeignet sind (siehe [Ändern des Computertyps für deinen Codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)).
+- Erlaube {% data variables.product.prodname_dotcom %}, GPG automatisch zu verwenden, um Commits zu signieren, die du in deinem Codespace vornimmst (weitere Informationen findest du unter [Verwalten der GPG-Überprüfung für {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)).
+- Teile verschlüsselte Geheimnisse mit deinem Codespace (weitere Informationen findest du unter [Verwalten verschlüsselter Geheimnisse für deine Codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)).
-### Publishing from {% data variables.product.prodname_dotcom_the_website %}
+### Veröffentlichen aus {% 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.
+Du kannst einen unveröffentlichten Codespace über die Seite „Deine Codespaces“ auf {% data variables.product.prodname_dotcom_the_website %} veröffentlichen. Dies ist nützlich, wenn du einen Codespace veröffentlichen möchtest, den du derzeit nicht in deinem Browser geöffnet hast. Wenn du dies tust, bleibt deine Arbeit in einem Repository erhalten, es gibt jedoch keine Verknüpfung zwischen deinem vorhandenen Codespace und dem neuen Repository. Du kannst jedoch zum neuen Repository navigieren und dort einen Codespace erstellen, und dieser Codespace wird mit dem Repository verbunden.
{% data reusables.codespaces.your-codespaces-procedure-step %}
-1. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**.
+1. Klicke neben dem nicht veröffentlichten Codespace auf die Auslassungspunkte ( **...** ), und wähle dann **In einem neuen Repository veröffentlichen** aus.
- 
-1. Choose a name for your new repository, set it as **Public** or **Private**, and click **Create repository**.
+ 
+1. Wähle einen Namen für dein neues Repository aus, lege es auf **Öffentlich** oder **Privat** fest, und klicke auf **Repository erstellen**.
- 
-1. Optionally, to view the new repository, click **See repository**.
+ 
+1. Klicke optional auf **Repository anzeigen**, um das neue Repository anzuzeigen.
-## Further reading
+## Weitere nützliche Informationen
-- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)"
-- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)"
-- "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
\ No newline at end of file
+- [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)
+- [Der Codespace-Lebenszyklus](/codespaces/getting-started/the-codespace-lifecycle)
+- [Verwenden der Quellcodeverwaltung in deinem Codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md
index c9cdeb3891..67f19e4def 100644
--- a/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md
@@ -1,6 +1,6 @@
---
-title: Opening an existing codespace
-intro: 'You can reopen a codespace that you have closed or stopped and return to your work.'
+title: Öffnen eines vorhandenen Codespaces
+intro: 'Du kannst einen Codespace, den du geschlossen oder angehalten hast, erneut öffnen und zu deiner Arbeit zurückkehren.'
versions:
fpt: '*'
ghec: '*'
@@ -10,46 +10,51 @@ topics:
- Fundamentals
- Developer
shortTitle: Open an existing codespace
+ms.openlocfilehash: b139b7f4e8a696416c97b3c400d09a9f26371b9c
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188296'
---
-
{% jetbrains %}
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
{% endjetbrains %}
-You can reopen any of your active or stopped codespaces on {% data variables.product.prodname_dotcom_the_website %}, in a JetBrains IDE, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. You can't reopen a codespace that has been deleted. For more information, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)."
+Du kannst jeden deiner aktiven oder angehaltenen Codespaces auf {% data variables.product.prodname_dotcom_the_website %}, in einer JetBrains-IDE, in {% data variables.product.prodname_vscode %} oder mit {% data variables.product.prodname_cli %} erneut öffnen. Ein gelöschter Codespace kann nicht erneut geöffnet werden. Weitere Informationen findest du unter [Der Codespace-Lebenszyklus](/codespaces/getting-started/the-codespace-lifecycle).
-You can view all your codespaces on the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). From this page, you can:
+Du kannst alle deine Codespaces auf der Seite „Deine Codespaces“ unter [github.com/codespaces](https://github.com/codespaces) anzeigen. Auf dieser Seite hast du folgende Möglichkeiten:
-- Open, stop, or delete your codespaces.
-- See who owns (and may be billed for) your codespaces: your personal account, or organizations you belong to. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
-- Create a new codespace, either by choosing one of {% data variables.product.company_short %}'s templates or by clicking **New codespace**. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)" and "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."
+- Du kannst deine Codespaces öffnen, beenden oder löschen.
+- Du kannst feststellen, wer der Besitzer deiner Codespaces ist (und worüber ggf. die Abrechnung anfallender Kosten erfolgt): dein persönliches Konto oder die Organisationen, denen du angehörst. Weitere Informationen 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).
+- Erstelle einen neuen Codespace, indem du entweder eine der Vorlagen von {% data variables.product.company_short %} auswählst oder auf **Neuer Codespace** klickst. Weitere Informationen findest du unter [Erstellen eines Codespaces mithilfe einer Vorlage](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template) und [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository).
-## Opening an existing codespace
+## Öffnen eines vorhandenen Codespaces
{% webui %}
{% data reusables.codespaces.your-codespaces-procedure-step %}
-1. To open a codespace in your default editor, click the name of the codespace. {% data reusables.codespaces.about-changing-default-editor %} For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
+1. Wenn du einen Codespace in deinem Standard-Editor öffnen möchtest, klicke auf den Namen des Codespaces. {% data reusables.codespaces.about-changing-default-editor %} Weitere Informationen findest du unter [Festlegen deines Standard-Editors für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces).
- To open the codespace in an editor other than your default:
+ So öffnest du den Codespace in einem anderen Editor als deinem Standard-Editor
- 1. Click the ellipsis (**...**) to the right of the codespace you want to open.
- 1. Click **Open in**.
- 1. Click **Open in APPLICATION**.
+ 1. Klicke auf die Auslassungspunkte ( **...** ) rechts neben dem Codespace, den du öffnen möchtest.
+ 1. Klicke auf **Öffnen in**.
+ 1. Klicken auf **Öffnen in ANWENDUNG**.
- 
+ 
- You can open the codespace in:
- * Your browser
+ Du kannst den Codespace über folgende Optionen öffnen:
+ * In deinem Browser
* {% data variables.product.prodname_vscode %}
* JetBrains Gateway
* JupyterLab
{% data reusables.codespaces.application-installed-locally %}
- If you choose **JupyterLab**, the JupyterLab application must be installed in the codespace. {% data reusables.codespaces.jupyterlab-in-default-image %}
+ Wenn du **JupyterLab** auswählst, muss die JupyterLab-Anwendung im Codespace installiert sein. {% data reusables.codespaces.jupyterlab-in-default-image %}
{% endwebui %}
@@ -57,29 +62,28 @@ You can view all your codespaces on the "Your codespaces" page at [github.com/co
{% note %}
-**Note:** {% data reusables.codespaces.using-codespaces-in-vscode %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)."
+**Hinweis:** {% data reusables.codespaces.using-codespaces-in-vscode %} Weitere Informationen findest du unter [Verwenden von {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code).
{% endnote %}
-1. In the {% data variables.product.prodname_vscode_shortname %} desktop application, open the Command Palette with Command+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux).
-1. Type "Codespaces" and select one of the following commands.
- - To open a codespace in a new window of {% data variables.product.prodname_vscode_shortname %}, select **Codespaces: Open Codespace in New Window**
- - To open a codespace in the web editor, select **Codespaces: Open in Browser**
-1. Click the codespace that you want to open.
+1. Öffne in der {% data variables.product.prodname_vscode_shortname %}-Desktopanwendung über BEFEHL+UMSCHALT+P (Mac) oder STRG+UMSCHALT+P (Windows/Linux) die Befehlspalette.
+1. Gib „Codespaces“ ein, und wähle einen der folgenden Befehle aus.
+ - Um einen Codespace in einem neuen Fenster von {% data variables.product.prodname_vscode_shortname %} zu öffnen, wähle **Codespaces: Codespace in neuem Fenster öffnen** aus.
+ - Wenn du einen Codespace im Web-Editor öffnen möchtest, wähle **Codespaces: Im Browser öffnen** aus.
+1. Klicke auf den Codespace, den du öffnen möchtest.
- 
+ 
-You can also access the commands listed above by navigating to the Remote Explorer view in {% data variables.product.prodname_vscode_shortname %} and right-clicking the codespace that you want to open.
+Du kannst auch auf die oben aufgeführten Befehle zugreifen, indem du in {% data variables.product.prodname_vscode_shortname %} zur Remote-Explorer-Ansicht navigierst und mit der rechten Maustaste auf den Codespace klickst, den du öffnen möchtest.
-
+
-{% data reusables.codespaces.remote-explorer %}
-{% endvscode %}
+{% data reusables.codespaces.remote-explorer %} {% endvscode %}
{% cli %}
-1. In a terminal, enter one of the following {% data variables.product.prodname_cli %} commands.
- - To open a codespace in {% data variables.product.prodname_vscode_shortname %}, enter:
+1. Gib in einem Terminal einen der folgenden {% data variables.product.prodname_cli %}-Befehle ein.
+ - Um einen Codespace in {% data variables.product.prodname_vscode_shortname %} zu öffnen, gibst du Folgendes ein:
```shell{:copy}
gh codespace code
@@ -87,17 +91,17 @@ You can also access the commands listed above by navigating to the Remote Explor
{% note %}
- **Note**: You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+ **Hinweis**: {% data variables.product.prodname_vscode_shortname %} muss auf deinem lokalen Computer installiert sein. Weitere Informationen findest du unter [Einrichten von Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview) in der {% data variables.product.prodname_vscode_shortname %}-Dokumentation.
{% endnote %}
- - To open a codespace in the browser, enter:
+ - Zum Öffnen eines Codespaces im Browser gibst du Folgendes ein:
```shell{:copy}
gh codespace code --web
```
- - To open a codespace in JupyterLab, enter:
+ - Um einen Codespace in JupyterLab zu öffnen, gibst du Folgendes ein:
```shell{:copy}
gh codespace code --jupyter
@@ -105,14 +109,14 @@ You can also access the commands listed above by navigating to the Remote Explor
{% note %}
- **Note**: {% data reusables.codespaces.jupyterlab-installed-in-codespace %}
+ **Hinweis**: {% data reusables.codespaces.jupyterlab-installed-in-codespace %}
{% endnote %}
-1. Using the arrow keys, navigate to the codespace that you want to open.
-1. To open the codespace, press Enter.
+1. Navigiere mithilfe der Pfeiltasten zu dem Codespace, den du öffnen möchtest.
+1. Drücke die EINGABETASTE, um den Codespace zu öffnen.
-For more information, see [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) in the {% data variables.product.prodname_cli %} manual.
+Weitere Informationen findest du unter [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) im Handbuch {% data variables.product.prodname_cli %}.
{% endcli %}
@@ -120,4 +124,4 @@ For more information, see [`gh codespace code`](https://cli.github.com/manual/gh
{% data reusables.codespaces.opening-codespace-in-jetbrains %}
-{% endjetbrains %}
\ No newline at end of file
+{% endjetbrains %}
diff --git a/translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
index c7605e66fc..87183c50e3 100644
--- a/translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
+++ b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Configuring prebuilds
+title: Konfigurieren von Prebuilds
shortTitle: Configure prebuilds
-intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
+intro: 'Du kannst dein Projekt so konfigurieren, dass ein Codespace automatisch erstellt wird, wenn du eine Änderung an dein Repository sendest.'
versions:
fpt: '*'
ghec: '*'
@@ -10,106 +10,111 @@ topics:
- Codespaces
- Set up
permissions: People with admin access to a repository can configure prebuilds for the repository.
+ms.openlocfilehash: dbb355e150695f27d1d6a7fa51eccc33a0ebde4f
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159117'
---
+Du kannst eine Prebuildkonfiguration für die Kombination eines bestimmten Branchs deines Repositorys mit einer bestimmten Dev-Containerkonfigurationsdatei einrichten.
-You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file.
+Alle Branches, die aus einem übergeordneten Branch mit Prebuildunterstützung erstellt werden, erhalten in der Regel auch Prebuilds für die gleiche Dev-Containerkonfiguration. Das liegt daran, dass Prebuilds für untergeordnete Branches, die die gleiche Entwicklungscontainerkonfiguration wie der übergeordnete Branch verwenden, größtenteils identisch sind, sodass Entwickler*innen auch von den schnelleren Codespace-Erstellungszeiten für diese Branches profitieren können. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers).
-Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because prebuilds for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+Bei der Konfiguration von Prebuilds für einen Branch stehen Prebuilds für mehrere Computertypen zur Verfügung. Wenn dein Repository jedoch größer als 32 GB ist, sind Prebuilds für 2-Kern- und 4-Kern-Computer nicht verfügbar, da der von diesen bereitgestellte Speicher auf 32 GB begrenzt ist.
-Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB.
+## Voraussetzungen
-## Prerequisites
+Prebuilds werden mit {% data variables.product.prodname_actions %} erstellt. Daher muss {% data variables.product.prodname_actions %} für das Repository aktiviert werden, für das du Prebuilds konfigurierst. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_actions %}-Einstellungen für ein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository).
-Prebuilds are created using {% data variables.product.prodname_actions %}. As a result, {% data variables.product.prodname_actions %} must be enabled for the repository for which you are configuring prebuilds. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)."
-
-## Configuring prebuilds
+## Konfigurieren von Prebuilds
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
+1. Klicke im Abschnitt „Prebuildkonfiguration“ der Seite auf **Prebuild einrichten**.
- 
+ 
-1. Choose the branch for which you want to set up prebuilds.
+1. Wähle den Branch aus, für den du Prebuilds einrichten möchtest.
- 
+ 
{% note %}
- **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
+ **Hinweis**: Alle Branches, die aus einem Basisbranch mit Prebuildunterstützung erstellt werden, erhalten in der Regel auch Prebuilds für die gleiche Dev-Containerkonfiguration. Wenn du beispielsweise Prebuilds für eine Dev-Containerkonfigurationsdatei im Standardbranch des Repositorys aktivierst, erhalten Branches, die auf dem Standardbranch basieren, in den meisten Fällen ebenfalls Prebuilds für die gleiche Dev-Containerkonfiguration.
{% endnote %}
-1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
+1. Wähle optional im angezeigten Dropdownmenü **Konfigurationsdatei** die `devcontainer.json`-Konfigurationsdatei aus, die du für deine Prebuilds verwenden möchtest. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson).
- 
+ 
-1. Choose how you want to automatically trigger prebuild updates.
+1. Wähle aus, wie du die Updates von Prebuilds automatisch auslösen möchtest.
- * **Every push** (the default setting) - With this setting, prebuilds will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies.
- * **On configuration change** - With this setting, prebuilds will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The {% data variables.product.prodname_actions %} workflow that updates the prebuilds will run less often, so this option will use fewer {% data variables.product.prodname_actions %} minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created.
- * **Scheduled** - With this setting, you can have your prebuilds updated on a custom schedule that's defined by you. This can reduce consumption of {% data variables.product.prodname_actions %} minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes.
+ * **Bei jedem Push** (Standardeinstellung): Mit dieser Einstellung werden Prebuilds bei jedem Push aktualisiert, der in den angegebenen Branch erfolgt. So wird sichergestellt, dass die aus einem Prebuild generierten Codespaces stets die neueste Codespacekonfiguration enthalten, einschließlich aller zuletzt hinzugefügten oder aktualisierten Abhängigkeiten.
+ * **Bei Konfigurationsänderung**: Mit dieser Einstellung werden die Prebuilds jedes Mal aktualisiert, wenn die zugeordneten Konfigurationsdateien für ein bestimmtes Repository und einen bestimmten Branch aktualisiert werden. Damit wird sichergestellt, dass Änderungen an den Konfigurationsdateien des Entwicklungscontainers für das Repository verwendet werden, wenn ein Codespace anhand eines Prebuilds generiert wird. Der {% data variables.product.prodname_actions %}-Workflow, der die Prebuilds aktualisiert, wird seltener ausgeführt, sodass diese Option weniger {% data variables.product.prodname_actions %}-Minuten benötigt. Diese Option garantiert jedoch nicht, dass Codespaces immer zuletzt hinzugefügte oder aktualisierte Abhängigkeiten enthalten, sodass diese möglicherweise manuell hinzugefügt oder aktualisiert werden müssen, nachdem ein Codespace erstellt wurde.
+ * **Geplant**: Mit dieser Einstellung kannst du festlegen, dass deine Prebuilds nach einem benutzerdefinierten Zeitplan aktualisiert werden. Dies kann den Verbrauch von {% data variables.product.prodname_actions %}-Minuten verringern. Mit dieser Option werden jedoch möglicherweise Codespaces erstellt, bei denen die neuesten Konfigurationsänderungen des Entwicklungscontainers nicht übernommen werden.
- 
+ 
-1. Optionally, select **Reduce prebuild available to only specific regions** to create prebuilds only in specified regions. Select the regions in which you want prebuilds to be available.
+1. Wähle optional **Prebuild auf bestimmte Regionen beschränken** aus, um Prebuilds nur in bestimmten Regionen zu erstellen. Wähle die Regionen aus, in denen Prebuilds verfügbar sein sollen.
- By default, prebuilds are created in all of the available regions, incurring storage charges per prebuild.
+ Standardmäßig werden Prebuilds in allen verfügbaren Regionen erstellt, wobei Speichergebühren pro Prebuild anfallen.
- 
+ 
{% note %}
- **Notes**:
- * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
- * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
+ **Hinweise**:
+ * Für den Prebuild in jeder Region fallen individuelle Speichergebühren an. Du solltest daher nur Prebuilds für Regionen aktivieren, von denen du weißt, dass sie verwendet werden. Weitere Informationen 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#billing-for-codespaces-prebuilds).
+ * Entwickler*innen können deine Standardregion für {% data variables.product.prodname_github_codespaces %} festlegen, wodurch du Prebuilds für weniger Regionen aktivieren kannst. Weitere Informationen findest du unter [Festlegen deiner Standardregion für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces).
{% endnote %}
-1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved.
+1. Lege unter **Vorlagenverlauf** wahlweise die Anzahl der Prebuildversionen fest, die aufbewahrt werden sollen. Du kannst eine beliebige Zahl zwischen 1 und 5 eingeben. Standardmäßig werden zwei Versionen gespeichert. Das bedeutet, dass nur der neueste Prebuild und die Vorgängerversion gespeichert werden.
- 
+ 
- Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. This setting allows you to set the number of retained versions to a level that is appropriate for your needs.
+ Abhängig von den Triggereinstellungen könnte der Prebuild mit jedem Push oder jeder Konfigurationsänderung im Entwicklungscontainer geändert werden. Wenn du ältere Versionen von Prebuilds aufbewahrst, kannst du einen Prebuild aus einem älteren Commit mit einer anderen Konfiguration für den Entwicklungscontainer erstellen als der aktuelle Prebuild. Mit dieser Einstellung kannst du die Anzahl der aufbewahrten Versionen auf ein für deine Anforderungen geeignetes Maß festlegen.
- If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration.
+ Wenn du festlegst, dass nur eine Version deines Prebuilds gespeichert wird, bewahrt {% data variables.product.prodname_github_codespaces %} nur die neueste Version des Prebuilds auf. Ältere Versionen werden bei jedem Update der Vorlage gelöscht. Das bedeutet, dass kein vordefinierter Codespace vorhanden ist, wenn du zurück zu einer älteren Konfiguration des Entwicklungscontainers wechselst.
- There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+ Für jede Prebuildversion, die aufbewahrt wird, fallen Speicherkosten an. Wenn du beispielsweise Prebuilds in vier Regionen generieren und zwei Versionen aufbewahren möchtest, werden dir bis zu acht Prebuilds in Rechnung gestellt. Weitere Informationen zur Abrechnung 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#codespaces-pricing).
-1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation.
+1. Füge wahlweise Benutzer*innen oder Teams hinzu, die benachrichtigt werden sollen, wenn bei der Ausführung des Prebuildworkflows für diese Konfiguration ein Fehler auftritt. Beginne mit der Eingabe eines Benutzernamens, eines Teamnamens oder eines vollständigen Namens, und klicke dann auf den gewünschten Namen, sobald dieser angezeigt wird, um ihn der Liste hinzuzufügen. Die Benutzer*innen oder Teams, die du hinzufügst, erhalten eine E-Mail, wenn Prebuildfehler auftreten. Diese enthält einen Link zu den Ausführungsprotokollen des Workflows, um weitere Untersuchungen zu erleichtern.
- 
+ 
-1. Optionally, at the bottom of the page, click **Show advanced options**.
+1. Wähle am unteren Rand der Seite die Option **Erweiterte Optionen anzeigen** aus.
- 
+ 
- In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
+ Wenn du im Abschnitt „Erweiterte Optionen“ die Option **Prebuildoptimierung deaktivieren** auswählst, werden Codespaces ohne Prebuild erstellt, wenn der neueste Prebuildworkflow fehlgeschlagen ist oder gerade ausgeführt wird. Weitere Informationen findest du unter [Problembehandlung bei Prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used).
-1. Click **Create**.
+1. Klicke auf **Erstellen**.
{% data reusables.codespaces.prebuilds-permission-authorization %}
-After you create a prebuild configuration it is listed on the {% data variables.product.prodname_github_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuilds in the regions you specified, based on the branch and dev container configuration file you selected.
+Nachdem du eine Prebuildkonfiguration erstellt hast, wird diese auf der Seite {% data variables.product.prodname_github_codespaces %} in deinen Repositoryeinstellungen aufgeführt. Ein {% data variables.product.prodname_actions %}-Workflow wird in die Warteschlange gestellt und anschließend ausgeführt, um Prebuilds in den angegebenen Regionen basierend auf deiner Auswahl für den Branch und die Dev-Containerkonfigurationsdatei zu erstellen.
-
+
-For information about editing and deleting prebuild configurations, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)."
+Informationen zum Bearbeiten und Löschen von Prebuildkonfigurationen findest du unter [Verwalten von Prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds).
-## Configuring environment variables
+## Konfigurieren von Umgebungsvariablen
-To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)."
+Damit der Prebuildprozess auf Umgebungsvariablen zugreifen kann, die zum Erstellen deiner Entwicklungsumgebung erforderlich sind, kannst du diese entweder als {% data variables.product.prodname_codespaces %}-Repositorygeheimnisse oder als {% data variables.product.prodname_codespaces %}-Organisationsgeheimnisse festlegen. Weitere Informationen findest du unter [Hinzufügen von Geheimnissen für ein Repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository) und [Hinzufügen von Geheimnissen für eine Organisation](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization).
-Secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces.
+Geheimnisse, die du auf diese Weise erstellst, sind für alle Personen zugänglich, die einen Codespace aus diesem Repository erstellen. Wenn du dies nicht möchtest, kannst du alternativ das `CODESPACES_PREBUILD_TOKEN`-Geheimnis festlegen. Das `CODESPACES_PREBUILD_TOKEN`-Geheimnis wird nur zum Prebuilding verwendet, und sein Wert ist in den Codespaces der Benutzer*innen nicht zugänglich.
-Prebuilds cannot use any user-level secrets while building your environment, because these are not available until after the codespace has been created.
+Prebuilds können bei der Erstellung deiner Umgebung keine Geheimnisse auf Benutzerebene verwenden, da diese erst nach der Erstellung des Codespaces verfügbar sind.
-## Configuring time-consuming tasks to be included in the prebuild
+## Konfigurieren von zeitaufwendigen Aufgaben, die im Prebuild enthalten sind
-You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)."
+Du kannst die Befehle `onCreateCommand` und `updateContentCommand` in deine `devcontainer.json`-Datei einschließen, um zeitaufwändige Prozesse bei der Erstellung des Prebuilds zu verwenden. Weitere Informationen findest du in der {% data variables.product.prodname_vscode %}-Dokumentation unter [ Referenz zu „devcontainer.json“](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts).
-`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at creation of the prebuild and at subsequent updates to it. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update.
+`onCreateCommand` wird nur einmal ausgeführt, wenn der Prebuild erstellt wird, wobei `updateContentCommand` zum Zeitpunkt der Erstellung des Prebuilds und bei nachfolgenden Updates ausgeführt wird. Inkrementelle Builds sollten in `updateContentCommand` enthalten sein, da sie die Quelle deines Projekts darstellen und in jedem Prebuildupdate enthalten sein müssen.
-## Further reading
+## Weitere Informationsquellen
-- "[Allowing a prebuild to access other repositories](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)"
-- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
+- [Gewähren von Zugriff auf andere Repositorys durch einen Pebuild](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)
+- [Problembehandlung bei Prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
index 36e4e0ae51..46b1edf776 100644
--- a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
@@ -1,7 +1,7 @@
---
-title: Adding an "Open in GitHub Codespaces" badge
+title: Hinzufügen eines Badges „In GitHub Codespaces öffnen“
shortTitle: Add a Codespaces badge
-intro: You can add a badge to a Markdown file in your repository which people can click to create a codespace.
+intro: 'Du kannst einer Markdown-Datei in deinem Repository einen Badge hinzufügen, auf den Benutzer klicken können, um einen Codespace zu erstellen.'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -10,50 +10,55 @@ type: how_to
topics:
- Codespaces
- Set up
+ms.openlocfilehash: c69a815501f5943a56d32af3e58cd7850a69588b
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158781'
---
+## Übersicht
-## Overview
+Das Hinzufügen eines Badges „In {% data variables.product.prodname_github_codespaces %} öffnen“ zu einer Markdown-Datei bietet Benutzern eine einfache Möglichkeit, einen Codespace für dein Repository zu erstellen.
-Adding an "Open in {% data variables.product.prodname_github_codespaces %}" badge to a Markdown file gives people an easy way to create a codespace for your repository.
+
-
+Wenn du einen Badge erstellst, kannst du bestimmte Konfigurationsoptionen für den Codespace auswählen, den der Badge erstellt.
-When you create a badge you can choose specific configuration options for the codespace that the badge will create.
+Wenn Benutzer auf den Badge klicken, werden sie für die Erstellung von Codespaces zur Seite mit erweiterten Optionen weitergeleitet, wobei die Optionen deiner Wahl vordefiniert sind. Weitere Informationen zur Seite mit erweiterten Optionen findest du unter [Erstellen eines Codespace für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
-When people click the badge they'll be taken to the advanced options page for codespace creation, with the options you chose preselected. For more information about the advanced options page, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+Auf der Seite mit erweiterten Optionen können Benutzer die vordefinierten Einstellungen bei Bedarf ändern und dann auf **Codespace erstellen** klicken.
-From the advanced options page, users can change the preselected settings if required, then click **Create codespace**.
-
-## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge
+## Erstellen eines „In {% data variables.product.prodname_github_codespaces %} öffnen“-Badges
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create the badge for.
+1. Wähle im Dropdownmenü „Branch“ unterhalb des Repositorynamens den Branch aus, für den du den Badge erstellen möchtest.
- 
+ 
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. Klicke auf die Schaltfläche **{% octicon "code" aria-label="The code icon" %} Code** und dann auf die Registerkarte **Codespaces**.
- 
+ 
-1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab, then click **New with options**.
+1. Klicke oben rechts auf der Registerkarte **Codespaces** auf die Auslassungspunkte ( **...** ), und klicke dann auf **Neu mit Optionen**.
- 
+ 
-1. On the advanced options page for codespace creation, select the values you want to be preselected in each field.
+1. Wähle auf der Seite mit erweiterten Optionen für die Erstellung von Codespaces die Werte aus, die in jedem Feld vordefiniert sein sollen.
- 
+ 
-1. Copy the URL from the browser's address bar.
-1. Add the following Markdown to, for example, the `README.md` file of your repository:
+1. Kopiere die URL aus der Adressleiste des Browsers.
+1. Füge das folgende Markdown hinzu, z. B. die Datei „`README.md`“ deines Repositorys:
```Markdown{:copy}
[](COPIED-URL)
```
- For example:
+ Beispiel:
```Markdown
[](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2)
```
- In the above example, `0000000` will be the reference number of your repository. The other details in the URL are determined by the values you selected in the fields on the advanced options page.
+ Im obigen Beispiel wird `0000000` die Referenznummer deines Repositorys sein. Die anderen Details in der URL werden durch die Werte bestimmt, die du in den Feldern auf der Seite mit erweiterten Optionen ausgewählt hast.
diff --git a/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index 25a547449e..bdccaa8e31 100644
--- a/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Troubleshooting prebuilds
+title: Problembehandlung bei Prebuilds
shortTitle: Codespaces prebuilds
-intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds.
+intro: Mit Prebuilds kannst du die Erstellung von Codespaces beschleunigen. Dieser Artikel enthält Schritte zur Behandlung von häufig auftretenden Problemen mit Prebuilds.
versions:
fpt: '*'
ghec: '*'
@@ -9,86 +9,91 @@ type: reference
topics:
- Codespaces
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: b8c45f9eae6094b78026d055ebea27c3748a8681
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158885'
---
+Weitere Informationen zu {% data variables.product.prodname_github_codespaces %}-Prebuilds findest du unter [Vordefinieren von Codespaces](/codespaces/prebuilding-your-codespaces).
-For more information about {% data variables.product.prodname_github_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)."
+## Prüfst du, ob ein Codespace aus einem Prebuild erstellt wurde?
-## Checking whether a codespace was created from a prebuild?
+Wenn du einen Codespace erstellst, kannst du den Typ des virtuellen Computers auswählen, den du verwenden möchtest. Wenn ein Prebuild für den Typ der VM verfügbar ist, wird „{% octicon "zap" aria-label="The zap icon" %} Prebuild bereit“ daneben angezeigt.
-When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it.
+
-
+Wenn du die Voreinstellungen für den {% data variables.product.prodname_github_codespaces %}-Editor auf „{% data variables.product.prodname_vscode %} für Web“ festgelegt hast, wird auf der Seite „Einrichten deines Codespace“ die Meldung „Vordefinierter Codespace gefunden“ angezeigt, wenn ein Prebuild verwendet wird.
-If you have your {% data variables.product.prodname_github_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used.
+
-
+Ähnlich verhält es sich, wenn deine Editor-Voreinstellung „{% data variables.product.prodname_vscode_shortname %}“ lautet. Dann wird im integrierten Terminal die Meldung „Du befindest dich in einem vordefinierten Codespace, der durch die Prebuildkonfiguration für dein Repository definiert ist“ angezeigt, wenn du einen neuen Codespace erstellst. Weitere Informationen findest du unter [Festlegen deines Standard-Editors für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces).
-Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
-
-After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal:
+Nachdem du einen Codespace erstellt hast, kannst du überprüfen, ob er aus einem Prebuild erstellt wurde, indem du den folgenden {% data variables.product.prodname_cli %}-Befehl im Terminal ausführst:
```shell{:copy}
gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild
```
-This returns `true` if the codespace was created using a prebuild.
+Dieser gibt `true` zurück, wenn der Codespace mithilfe eines Prebuilds erstellt wurde.
-Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild:
+Wenn {% data variables.product.prodname_cli %} (`gh`) nicht installiert ist, kannst du den folgenden Befehl verwenden, der `createFromPrebuild` zurückgibt, wenn der Codespace aus einem Prebuild erstellt wurde:
```shell{:copy}
cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME'
```
-## The "Prebuild Ready" label is sometimes missing
+## Die Bezeichnung „Prebuild bereit“ fehlt manchmal.
-You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
+Wenn du einen neuen Codespace aus einem Branch mit Prebuildunterstützung erstellst, stellst du vielleicht fest, dass die Bezeichnung „{% octicon "zap" aria-label="The zap icon" %} Prebuild bereit“ nicht im Dialogfeld für die Auswahl eines Computertyps angezeigt wird. Dies bedeutet, dass Prebuilds derzeit nicht verfügbar sind.
-By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+Der Prebuild wird standardmäßig jedes Mal aktualisiert, wenn du einen Push in einen Branch mit Prebuildunterstützung ausführst. Wenn der Push eine Änderung der Konfiguration des Entwicklungscontainers beinhaltet, wird während der Aktualisierung die Bezeichnung „{% octicon "zap" aria-label="The zap icon" %} Prebuild bereit“ aus der Liste der Computertypen entfernt. Während dieser Zeit kannst du weiterhin Codespaces ohne Prebuild erstellen. Bei Bedarf kannst du die Anzahl der Fälle reduzieren, in denen Prebuilds für ein Repository nicht verfügbar sind, indem du das Prebuild so einstellst, dass es nur aktualisiert wird, wenn du eine Änderung an deinen Dev-Container-Konfigurationsdateien vornimmst, oder nur nach einem benutzerdefinierten Zeitplan. Weitere Informationen findest du unter [Konfigurieren von Prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds).
-If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
+Wenn dein Branch nicht speziell für Prebuilds aktiviert ist, kann er trotzdem von Prebuilds profitieren, wenn er von einem Branch mit Prebuildunterstützung abzweigt. Wenn die Dev-Containerkonfiguration jedoch in deinem Branch geändert wird, sodass sie nicht mit der Konfiguration im Basisbranch identisch ist, stehen Prebuilds nicht mehr in deinem Branch zur Verfügung.
-Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch:
+Die folgenden Punkte müssen überprüft werden, wenn die Bezeichnung „{% octicon "zap" aria-label="The zap icon" %} Prebuild bereit“ für einen bestimmten Branch nicht angezeigt wird:
-* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this.
-* Confirm that the prebuild configuration includes your region.
-* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
-* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
+* Vergewissere dich, dass für diesen Branch eine Prebuildkonfiguration vorhanden ist. Wenn du kein Repositoryadministrator bist, musst du einen solchen bitten, dies zu bestätigen.
+* Vergewissere dich, dass die Vorbuildkonfiguration deine Region enthält.
+* Überprüfe, ob kürzlich eine Änderung der Dev-Containerkonfiguration zu dem Branch mit Prebuildunterstützung verschoben wurde. Wenn dies der Fall ist, musst du in der Regel warten, bis der Prebuildworkflow für diesen Push abgeschlossen ist, bevor Prebuilds erneut verfügbar sind.
+* Wenn in letzter Zeit keine Konfigurationsänderungen vorgenommen wurden, navigiere zur Registerkarte **Aktionen** deines Repositorys, klicke in der Liste der Workflows auf **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}-Prebuilds**, und überprüfe, ob Ausführungen von Prebuildworkflows für den Branch erfolgreich sind. Wenn die letzten Ausführungen eines Workflows erfolglos waren und eine oder mehrere dieser erfolglosen Ausführungen Änderungen an der Dev-Container-Konfiguration enthielten, sind keine Prebuilds für den zugehörigen Branch verfügbar.
-## Some resources cannot be accessed in codespaces created using a prebuild
+## In Codespaces, die mithilfe eines Prebuilds erstellt wurden, kann auf einige Ressourcen nicht zugegriffen werden.
-If the `devcontainer.json` configuration file for a prebuild configuration specifies that permissions for access to other repositories are required, then the repository administrator is prompted to authorize these permissions when they create or update the prebuild configuration. If the administrator does not grant all of the requested permissions there's a chance that problems may occur in the prebuild, and in codespaces created from this prebuild. This is true even if the user who creates a codespace based on this prebuild _does_ grant all of the permissions when they are prompted to do so.
+Wenn die `devcontainer.json`-Konfigurationsdatei für eine Prebuildkonfiguration angibt, dass Berechtigungen für den Zugriff auf andere Repositorys erforderlich sind, werden Repositoryadministrator*innen beim Erstellen oder Aktualisieren der Prebuildkonfiguration aufgefordert, diese Berechtigungen zu autorisieren. Wenn der bzw. die Administrator*in nicht alle angeforderten Berechtigungen gewährt, können im Prebuild und in Codespaces, die aus diesem Prebuild erstellt wurden, unter Umständen Probleme auftreten. Dies gilt auch dann, wenn die Benutzer*innen, die einen Codespace basierend auf diesem Prebuild erstellen, alle Berechtigungen _gewähren_, wenn sie dazu aufgefordert werden.
-## Troubleshooting failed workflow runs for prebuilds
+## Problembehandlung bei erfolglosen Workflowausführungen für Prebuilds
-### Increasing the {% data variables.product.prodname_actions %} spending limit
+### Erhöhen des Ausgabenlimits für {% data variables.product.prodname_actions %}
-Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+Prebuilds werden mit {% data variables.product.prodname_actions %} erstellt und aktualisiert. Prebuildworkflows sind nicht erfolgreich, wenn du alle deine {% data variables.product.prodname_actions %}-Minuten aufgebraucht und dein Ausgabenlimit erreicht hast. Sollte das der Fall sein, kannst du dein Ausgabenlimit für {% data variables.product.prodname_actions %} erhöhen, damit die Workflows ausgeführt werden können. Weitere Informationen findest du unter [Verwalten deines Ausgabenlimits für {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions).
-### Authorizing access permissions
+### Autorisieren von Zugriffsberechtigungen
-If the `devcontainer.json` configuration file for a prebuild configuration is updated to specify that permissions for access to other repositories are required, and a repository administrator has not been prompted to authorize these permissions for the prebuild configuration, then the prebuild workflow may fail. Try updating the prebuild configuration, without making any changes. If, when you click **Update**, the authorization page is displayed, check that the requested permissions are appropriate and, if so, authorize the request. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" and "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)."
+Wenn die `devcontainer.json`-Konfigurationsdatei für eine Prebuildkonfiguration aktualisiert wird, um anzugeben, dass Berechtigungen für den Zugriff auf andere Repositorys erforderlich sind, und Repositoryadministrator*innen nicht zur Autorisierung dieser Berechtigungen für die Prebuildkonfiguration aufgefordert werden, kann der Prebuild fehlschlagen. Versuche, die Prebuildkonfiguration zu aktualisieren, ohne Änderungen vorzunehmen. Wenn du auf **Aktualisieren** klickst, wird die Autorisierungsseite angezeigt. Überprüfe, ob die angeforderten Berechtigungen geeignet sind, und autorisiere die Anforderung gegebenenfalls. Weitere Informationen findest du unter [Verwalten von Prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration) und [Verwalten des Zugriffs auf andere Repositorys innerhalb deines Codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions).
-If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
+Wenn die Workflowausführungen für eine Prebuildkonfiguration erfolglos sind, kannst du die Prebuildkonfiguration vorübergehend deaktivieren, während du Untersuchungen anstellst. Weitere Informationen findest du unter [Verwalten von Prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration).
-### Preventing out-of-date prebuilds being used
+### Verhindern der Verwendung veralteter Prebuilds
-By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
+Wenn beim neuesten Prebuildworkflow ein Fehler aufgetreten ist, wird standardmäßig ein vorheriger Prebuild für die gleiche Kombination aus Repository, Branch und Konfigurationsdatei (`devcontainer.json`) verwendet, um neue Codespaces zu erstellen. Dieses Verhalten wird als Prebuildoptimierung bezeichnet.
-We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
+Es empfiehlt sich, die Prebuildoptimierung aktiviert zu lassen, da dadurch sichergestellt werden kann, dass weiterhin schnell Codespaces erstellt werden können, auch wenn kein aktueller Prebuild verfügbar ist. Als Repositoryadministrator kannst du die Prebuildoptimierung jedoch deaktivieren, wenn bei dir Probleme mit vordefinierten Codespaces auftreten, die nicht dem aktuellen Zustand des Branchs entsprechen. Falls du die Prebuildoptimierung deaktivierst, werden Codespaces für die relevante Kombination aus Repository, Branch und der Datei `devcontainer.json` ohne Prebuild erstellt, wenn beim neuesten Prebuildworkflow ein Fehler aufgetreten ist oder wenn der neueste Prebuildworkflow gerade ausgeführt wird.
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
+1. Wähle rechts neben der betroffenen Prebuildkonfiguration die Auslassungspunkte ( **...** ) aus, und klicke anschließend auf **Bearbeiten**.
- 
-1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
+ 
+1. Scrolle zum unteren Rand der Seite „Konfiguration bearbeiten“, und klicke auf **Erweiterte Optionen anzeigen**.
- 
-1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
+ 
+1. Falls du die Standardeinstellung wirklich deaktivieren möchtest, wähle **Prebuildoptimierung deaktivieren** aus.
- 
-1. To save your change, click **Update**.
+ 
+1. Klicke zum Speichern deiner Änderung auf **Aktualisieren**.
-## Further reading
+## Weiterführende Themen
-- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
-- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
+- [Konfigurieren von Prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)
+- [Verwalten von Prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index af188745d7..8f7905ac45 100644
--- a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -1,6 +1,6 @@
---
-title: Erstellen einer Standard-Community-Health-File
-intro: "Du kannst standardmäßige Community-Unterstützungsdateien wie z.\_B. CONTRIBUTING oder CODE_OF_CONDUCT erstellen. Standarddateien werden für alle Repositorys eines Kontos verwendet, das keine eigene Datei dieser Art enthält."
+title: Creating a default community health file
+intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
redirect_from:
- /articles/creating-a-default-community-health-file-for-your-organization
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
@@ -12,41 +12,46 @@ versions:
topics:
- Community
shortTitle: Community health file
-ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: de-DE
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145105412'
---
-## Informationen zu Standard-Community-Unterstützungsdateien
-Du kannst standardmäßige Communityintegritätsdateien einem öffentlichen Repository namens `.github` im Stammverzeichnis des Repositorys oder in den Ordnern `docs` oder `.github` hinzufügen.
+## About default community health files
-Standarddateien werden von {% data variables.product.product_name %} für beliebige im Besitz des Kontos befindliche Repositorys verwendet und angezeigt, die an keiner der folgenden Stellen über eigene Dateien dieses Typs verfügen:
-- im Root des Repositorys
-- im Ordner `.github`
-- im Ordner `docs`
+You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders.
-Wenn z. B. jemand einen Issue oder Pull Request in einem Repository erstellt, das keine eigene CONTRIBUTING-Datei enthält, wird ein Link zur standardmäßigen CONTRIBUTING-Datei angezeigt. Wenn ein Repository Dateien in seinem eigenen `.github/ISSUE_TEMPLATE`-Ordner{% ifversion fpt or ghes or ghec %} enthält, einschließlich Issuevorlagen oder einer *config.yml*-Datei,{% endif %} wird keiner der Inhalte des standardmäßigen `.github/ISSUE_TEMPLATE`-Ordners verwendet.
+{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
+- the root of the repository
+- the `.github` folder
+- the `docs` folder
-Standarddateien sind nicht in Klonen, Paketen oder Downloads von einzelnen Repositorys enthalten, da sie nur im `.github`-Repository gespeichert sind.
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
-## Unterstützte Dateitypen
+Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
-Du kannst in deiner Organisation{% ifversion fpt or ghes or ghec %} oder deinem persönlichen Konto{% endif %} Standardeinstellungen für die folgenden Communityintegritätsdateien erstellen:
+## Supported file types
-Communityintegritätsdatei | Beschreibung --- | ---{% ifversion fpt or ghec %} *CODE_OF_CONDUCT.md* | Eine A CODE_OF_CONDUCT-Datei definiert Standards für die Interaktion in einer Community. Weitere Informationen findest du unter „[Hinzufügen eines Verhaltenskodexes zum Projekt](/articles/adding-a-code-of-conduct-to-your-project/)“.{% endif %} *CONTRIBUTING.md* | Eine CONTRIBUTING-Datei vermittelt, wie Personen zu deinem Projekt beitragen sollten. Weitere Informationen findest du unter „[Festlegen von Richtlinien für Repositorymitwirkende](/articles/setting-guidelines-for-repository-contributors/)“.{% ifversion fpt or ghec %} *FUNDING.yml* | Eine FUNDING-Datei zeigt eine Sponsorenschaltfläche in deinem Repository an, um die Transparenz von Finanzierungsoptionen für dein Open Source Projekt zu erhöhen. Weitere Informationen findest du unter „[Anzeigen einer Sponsorenschaltfläche im Repository](/articles/displaying-a-sponsor-button-in-your-repository)“.{% endif %} Issue- und Pull Request-Vorlagen{% ifversion fpt or ghes or ghec %} und *config.yml*{% endif %} | Mit Issue- und Pull Request-Vorlagen kannst du die Informationen, die Mitarbeiter beim Erstellen von Issues und Pull Requests in deinem Repository verwenden sollen, anpassen und standardisieren. Weitere Informationen findest du unter „[Informationen zu Issue- und Pull Request-Vorlagen](/articles/about-issue-and-pull-request-templates/)“.{% ifversion fpt or ghes or ghec %} *SECURITY.md |* Eine SECURITY-Datei enthält Anweisungen zum Melden eines Sicherheitsrisikos in deinem Projekt. Weitere Informationen findest du unter „[Hinzufügen einer Sicherheitsrichtlinie zum Repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)“.{% endif %} *SUPPORT.md |* Eine SUPPORT-Datei informiert Personen über Möglichkeiten, Hilfe zu deinem Projekt zu erhalten. Weitere Informationen findest du unter „[Hinzufügen von Supportressourcen zum Projekt](/articles/adding-support-resources-to-your-project/)“.
+You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
-Du kannst keine Standard-Lizenzdatei erstellen. Lizenzdateien müssen zu individuellen Repositorys hinzugefügt werden, damit die Datei bei Klonen, Paketieren und Herunterladen des Projekts enthalten ist.
+Community health file | Description
+--- | ---{% ifversion fpt or ghec %}
+*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
+*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion discussion-category-forms %}
+Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[Creating discussion category forms](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
+*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
+Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes or ghec %}
+*SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
-## Ein Repository für Standarddateien erstellen
+You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
+
+## Creating a repository for default files
{% data reusables.repositories.create_new %}
-2. Verwende das Dropdownmenü **Besitzer**, und wähle die Organisation{% ifversion fpt or ghes or ghec %} oder das persönliche Konto{% endif %} aus, für die bzw. das du Standarddateien erstellen möchtest.
- 
-3. Gib **.github** als Namen für dein Repository und eine optionale Beschreibung ein.
- 
-4. Stelle sicher, dass der Repositorystatus auf **Öffentlich** festgelegt ist (ein Repository für Standarddateien darf nicht privat sein).
-  {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
-7. Erstelle im Repository eine der möglichen Community-Unterstützungsdateien. Issuevorlagen{% ifversion fpt or ghes or ghec %} und die zugehörige Konfigurationsdatei{% endif %} müssen sich in einem Ordner namens `.github/ISSUE_TEMPLATE` befinden. Alle anderen unterstützten Dateien können sich im Stammverzeichnis des Repositorys, im `.github`-Ordner oder im `docs`-Ordner befinden. Weitere Informationen findest du unter [Erstellen neuer Dateien](/articles/creating-new-files/).
+2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
+ 
+3. Type **.github** as the name for your repository, and an optional description.
+ 
+4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+ 
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
index 44aa07505c..920ec13be1 100644
--- a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a pull request template for your repository
-intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.'
+title: Eine Pull-Request-Vorlage für dein Repository erstellen
+intro: 'Wenn du eine Pull-Request-Vorlage zu deinem Repository hinzufügst, sehen Projektmitarbeiter automatisch den Inhalt der Vorlage im Text des Pull Requests.'
redirect_from:
- /articles/creating-a-pull-request-template-for-your-repository
- /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
@@ -12,41 +12,44 @@ versions:
topics:
- Community
shortTitle: Create a PR template
+ms.openlocfilehash: fa4d3cf78b63af147c85b8f6d77d7cca74e3853a
+ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190408'
---
+Weitere Informationen findest du unter [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates).
-For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
-
-You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
+Du kannst in jedem beliebigen unterstützten Ordner ein Unterverzeichnis namens *PULL_REQUEST_TEMPLATE* erstellen, um mehrere Pull Request-Vorlagen zu speichern. Mit dem Abfrageparameter `template` kannst du die Vorlage angeben, mit der der Pull Request-Text ausgefüllt werden soll. Weitere Informationen findest du unter [Verwenden von Abfrageparametern zum Erstellen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request).
{% ifversion fpt or ghes or ghec %}
-You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+Du kannst Standardvorlagen für Pull Requests für dein Organisationskonto{% ifversion fpt or ghes or ghec %} oder dein persönliches Konto{% endif %} festlegen. Weitere Informationen findest du unter [Erstellen einer Standard-Communityintegritätsdatei](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
{% endif %}
-## Adding a pull request template
+## Eine Pull-Request-Vorlage hinzufügen
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field:
- - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`.
- 
- - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`.
- 
- - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`.
- 
- - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
- 
-4. In the body of the new file, add your pull request template. This could include:
- - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository.
- - A description of the changes proposed in the pull request.
- - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes.
-{% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib Folgendes im Feld für den Dateinamen ein:
+ - Wenn die Pull Request-Vorlage im Stammverzeichnis des Repositorys sichtbar sein soll, benenne diese Vorlage `pull_request_template.md`.
+ 
+ - Wenn die Pull Request-Vorlage im `docs/pull_request_template.md`-Verzeichnis des Repositorys sichtbar sein soll, benenne diese Vorlage `docs`.
+ 
+ - Um deine Datei in einem ausgeblendeten Verzeichnis zu speichern, benenne die Pull Request-Vorlage `.github/pull_request_template.md`.
+ 
+ - Um mehrere Pull Request-Vorlagen zu erstellen und mithilfe des Abfrageparameters `template` eine Vorlage zum Ausfüllen des Pull Request-Texts anzugeben, gib *.github/PULL_REQUEST_TEMPLATE/* gefolgt vom Namen der Pull Request-Vorlage ein. Beispiel: `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. Du kannst auch mehrere Pull Request-Vorlagen in einem `PULL_REQUEST_TEMPLATE`-Unterverzeichnis innerhalb des Stammverzeichnisses oder des `docs/`-Verzeichnisses speichern. Weitere Informationen findest du unter [Verwenden von Abfrageparametern zum Erstellen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request).
+ 
+4. Füge im Text der neuen Datei deine Pull-Request-Vorlage hinzu. Sie könnte beispielsweise Folgendes enthalten:
+ - Ein [Verweis auf ein verwandtes Issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in deinem Repository.
+ - Eine Beschreibung der Änderungen, die im Pull Request vorgeschlagen werden.
+ - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) der Person oder des Teams, die bzw. das für die Überprüfung vorgeschlagener Änderungen verantwortlich ist.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} Vorlagen sind für Mitarbeiter verfügbar, wenn sie in den Standardbranch des Repositorys gemergt wurden.
{% data reusables.files.propose_new_file %}
-## Further reading
+## Weiterführende Themen
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating a pull request](/articles/creating-a-pull-request)"
+- [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates)
+- [Informationen zur Automatisierung für Issues und Pull Requests mit Abfrageparametern](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)
+- [Erstellen eines Pull Requests](/articles/creating-a-pull-request)
diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md
index 8d77643658..20c6afa9f1 100644
--- a/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,6 +9,8 @@ children:
- /managing-categories-for-discussions
- /moderating-discussions
- /viewing-insights-for-your-discussions
+ - /creating-discussion-category-forms
+ - /syntax-for-discussion-category-forms
ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
ms.translationtype: HT
diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index 302f14adae..cf7fe99651 100644
--- a/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -1,215 +1,201 @@
---
-title: Managing discussions
-intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
+title: Verwalten von Diskussionen
+intro: 'Du kannst die Diskussionen kategorisieren, hervorheben, übertragen oder löschen.'
permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
versions:
feature: discussions
shortTitle: Manage discussions
redirect_from:
- /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
+ms.openlocfilehash: e5e1474648973c90d16e8998db18518331233aa3
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164339'
---
+## Informationen zum Verwalten von Diskussionen
+{% data reusables.discussions.about-discussions %} Weitere Informationen zu Diskussionen findest du unter [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions).
-## About management of discussions
+Organisationsbesitzer*innen können die erforderlichen Berechtigungen zum Erstellen einer Diskussion in Repositorys auswählen, die sich im Besitz der Organisation befinden. Ebenso können sie die im Quellrepository erforderlichen Berechtigungen ändern, um auszuwählen, welche Berechtigungen zum Erstellen einer Organisationsdiskussion erforderlich sind. Weitere Informationen findest du unter [Verwalten der Diskussionserstellung für Repositorys in deiner Organisation](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization).
-{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+Als Diskussionsbetreuer kannst du Communityressourcen erstellen, um Diskussionen zu fördern, die auf das Gesamtprojektziel ausgerichtet sind, und ein freundliches offenes Forum für Projektmitarbeiter verfügbar machen. Das Erstellen von zu befolgenden {% ifversion fpt or ghec %}Verhaltensregeln oder{% endif %} Richtlinien für Mitwirkende für Projektmitarbeiter, trägt dazu bei, ein kooperatives und produktives Forum zu etablieren. Weitere Informationen zum Erstellen von Communityressourcen 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 %} [Festlegen von Richtlinien für Repositorymitwirkende](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors).
-Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."
+Wenn im Rahmen einer Diskussion Ideen oder Fehler herausgearbeitet werden, an denen gearbeitet werden kann, kannst du aus der Diskussion heraus ein neues Issue erstellen. Weitere Informationen findest du unter [Erstellen eines Issues](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion).
-As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, 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 guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+Du kannst eine Diskussion an den Anfang der Diskussionsliste für das Repository oder die Organisation anheften. {% ifversion discussions-category-specific-pins %}Du kannst eine Diskussion auch an eine bestimmte Kategorie anheften.{% endif %} Weitere Informationen findest du unter [Anheften einer Diskussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion).
-When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
-
-You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
-
-For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
+Weitere Informationen zum Fördern einer produktiven Diskussion findest du unter [Moderieren von Kommentaren und Konversationen](/communities/moderating-comments-and-conversations).
{% data reusables.discussions.you-can-label-discussions %}
-## Prerequisites
+## Voraussetzungen
-To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)."
+Zum Verwalten von Diskussionen in einem Repository muss {% data variables.product.prodname_discussions %} für das Repository aktiviert sein. Weitere Informationen findest du unter [Aktivieren oder Deaktivieren von {% data variables.product.prodname_discussions %} für ein Repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository).
-To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+{% data variables.product.prodname_discussions %} muss für die Organisation aktiviert sein, um Diskussionen in einer Organisation zu verwalten. Weitere Informationen findest du unter [Aktivieren oder Deaktivieren von {% data variables.product.prodname_discussions %} für eine Organisation](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization).
-## Changing the category for a discussion
+## Ändern der Kategorie für eine Diskussion
-You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+Du kannst Diskussionen kategorisieren, um Communitymitgliedern bei der Suche nach verwandten Diskussionen zu helfen. Weitere Informationen findest du unter [Verwalten von Kategorien für Diskussionen](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions).
-You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category.
+Du kannst auch eine Diskussion in eine andere Kategorie verschieben. Es ist nicht möglich, eine Diskussion in die Umfragekategorie zu verschieben oder aus dieser zu entfernen.
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Randleiste rechts neben „Category“ (Kategorie) auf {% octicon "gear" aria-label="The gear icon" %}.
- 
+ 
-1. Click a category.
+1. Klicke auf eine Kategorie.
- 
+ 
-## Pinning a discussion
+## Anheften einer Diskussion
-{% ifversion discussions-category-specific-pins %}
-You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
+{% ifversion discussions-category-specific-pins %} Du kannst eine Diskussion oberhalb der Diskussionsliste für das Repository oder die Organisation anheften. Du kannst eine Diskussion auch an eine bestimmte Kategorie anheften. Die global angehefteten Diskussionen werden zusätzlich zu den Diskussionen angezeigt, die an eine bestimmte Kategorie angeheftet wurden.
-This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
+So sieht es aus, wenn du eine global angeheftete Diskussion und eine Diskussion an die Kategorie „Ideen“ anheftest.
-
+
-### Pinning a discussion globally
+### Globales Anheften einer Diskussion
{% endif %}
-You can pin up to four important discussions above the list of discussions for the repository or organization.
+Du kannst bis zu vier wichtige Diskussionen über der Liste der Diskussionen für das Repository oder die Organisation anheften.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Randleiste auf {% octicon "pin" aria-label="The pin icon" %} **Pin discussion** (Diskussion anheften).
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ {% else %}
- {% endif %}
+ {% endif %}
-1. Optionally, customize the look of the pinned discussion.
+1. Passe optional das Aussehen der angehefteten Diskussion an.
- 
+ 
-1. Click **Pin discussion**.
+1. Klicke auf **Pin discussion** (Diskussion anheften).
- 
+ 
{% ifversion discussions-category-specific-pins %}
-### Pinning a discussion to a category
+### Anheften einer Diskussion an eine Kategorie
-You can pin up to four important discussions above the list of discussions in a specific category.
+Du kannst bis zu vier wichtige Diskussionen über der Diskussionsliste in einer bestimmten Kategorie anheften.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Seitenleiste auf {% octicon "pin" aria-label="The pin icon" %} **Diskussion an KATEGORIE anheften**.
- 
+ 
-2. To confirm, click **Pin to CATEGORY**.
+2. Klicke zur Bestätigung auf **An KATEGORIE anheften**.
- 
+ 
{% endif %}
-## Editing a pinned discussion
+## Bearbeiten einer angehefteten Diskussion
-Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+Durch das Bearbeiten einer angehefteten Diskussion wird die Kategorie der Diskussion nicht geändert. Weitere Informationen findest du unter [Verwalten von Kategorien für Diskussionen](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions).
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Randleiste auf {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion** (Angeheftete Diskussion bearbeiten).
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+  {% else %}
- {% endif %}
+ {% endif %}
-1. Customize the look of the pinned discussion.
+1. Passe das Aussehen der angehefteten Diskussion an.
- 
+ 
-1. Click **Pin discussion**.
+1. Klicke auf **Pin discussion** (Diskussion anheften).
- 
+ 
-## Unpinning a discussion
+## Lösen einer Diskussion
{% ifversion discussions-category-specific-pins %}
-You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
+Du kannst eine Diskussion von der Diskussionsliste für das Repository oder die Organisation oder von der Diskussionsliste einer bestimmten Kategorie lösen.
-### Unpinning a globally pinned discussion
+### Lösen einer global angehefteten Diskussion
-You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
+Du kannst eine global angeheftete Diskussion wieder lösen. Dadurch wird die Diskussion nicht gelöscht, aber die Diskussion wird nicht mehr oberhalb der Diskussionsliste angezeigt.
{% endif %}
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Randleiste auf {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion** (Diskussion lösen).
- 
+ 
-1. Read the warning, then click **Unpin discussion**.
+1. Lies die Warnung, und klicke dann auf **Unpin discussion** (Diskussion lösen).
- 
+ 
{% ifversion discussions-category-specific-pins %}
-### Unpinning a discussion from a category
+### Lösen einer Diskussion von einer Kategorie
-You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
+Du kannst eine Diskussion, die an eine bestimmte Kategorie angeheftet wurde, wieder lösen. Dadurch wird die Diskussion nicht gelöscht, aber sie wird nicht mehr oben in der Kategorie angezeigt.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Seitenleiste auf {% octicon "pin" aria-label="The pin icon" %} **Diskussion von dieser Kategorie lösen**.
- 
+ 
-1. Read the warning, then click **Unpin from this category**.
+1. Lies die Warnung, und klicke dann auf **Von dieser Kategorie lösen**.
- 
+ 
{% endif %}
-## Transferring a discussion
+## Übertragen einer Diskussion
-To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
+Zum Übertragen einer Diskussion musst du über Berechtigungen zum Erstellen von Diskussionen im Repository verfügen, in das du die Diskussion übertragen möchtest. Wenn du eine Diskussion in eine Organisation übertragen möchtest, musst du über die Berechtigungen zum Erstellen von Diskussionen im Quellrepository für die Diskussionen der Organisation verfügen. Du kannst Diskussionen nur zwischen Repositorys übertragen, die demselben Benutzer- oder Organisationskonto angehören. Du kannst eine Diskussion nicht von einem privaten{% ifversion ghec or ghes %} oder internen{% endif %} Repository in ein öffentliches Repository übertragen.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Seitenleiste auf {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Diese Diskussion übertragen**{% else %}**Diskussion übertragen**{% endif %}.
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+  {% else %}
- {% endif %}
+ {% endif %}
-1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
+1. Wähle im Dropdownmenü **Choose a Repository** (Repository auswählen) das Repository aus, in das du die Diskussion übertragen möchtest. Wenn du eine Diskussion in eine Organisation übertragen möchtest, wähle das Quellrepository für die Diskussionen der Organisation aus.
- 
+ 
-1. Click **Transfer discussion**.
+1. Klicke auf **Transfer discussion** (Diskussion übertragen).
- 
+ 
-## Deleting a discussion
+## Löschen einer Diskussion
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Randleiste auf {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion** (Diskussion löschen).
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ {% else %}
- {% endif %}
+ {% endif %}
-1. Read the warning, then click **Delete this discussion**.
+1. Lies die Warnung, und klicke dann auf **Delete this discussion** (Diese Diskussion löschen).
- 
+ 
-## Converting issues based on labels
+## Konvertieren von Issues basierend auf Bezeichnungen
-You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.
+Du kannst alle Issues mit derselben Bezeichnung in Diskussionen massenkonvertieren. Zukünftige Issues mit dieser Bezeichnung werden auch automatisch in die von Ihnen konfigurierte Diskussion und Kategorie konvertiert.
-1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository.
-{% data reusables.repositories.sidebar-issues %}
-{% data reusables.project-management.labels %}
-1. Next to the label you want to convert to issues, click **Convert issues**.
-1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
-1. Click **I understand, convert this issue to a discussion**.
+1. Navigiere auf {% data variables.location.product_location %} zur Hauptseite des Repositorys oder (für Organisationsdiskussionen) zum Quellrepository.
+{% data reusables.repositories.sidebar-issues %} {% data reusables.project-management.labels %}
+1. Klicke neben der Bezeichnung der Issues, die du in Diskussionen konvertieren möchtest, auf **Convert issues** (Issues konvertieren).
+1. Wähle das Dropdownmenü **Choose a category** (Kategorie auswählen) aus, und klicke auf eine Kategorie für deine Diskussion.
+1. Klicke auf **Verstanden, dieses Issue in eine Diskussion konvertieren**.
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index ffef0a4aba..ac1d1e64a4 100644
--- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -1,78 +1,84 @@
---
-title: Create a group assignment
-intro: You can create a collaborative assignment for teams of students who participate in your course.
+title: Erstellen einer Gruppenaufgabe
+intro: 'Du kannst eine gemeinsame Aufgabe für Teams von Kursteilnehmern erstellen, die an deinem Kurs teilnehmen.'
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
redirect_from:
- /education/manage-coursework-with-github-classroom/create-group-assignments
- /education/manage-coursework-with-github-classroom/create-a-group-assignment
+ms.openlocfilehash: 71c5f5eaf97ba58e25921c1e2be6fc638550dfa8
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179760'
---
-## About group assignments
+## Informationen zu Gruppenaufgaben
-{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+{% data reusables.classroom.assignments-group-definition %} Kursteilnehmer*innen können wie ein Team professioneller Entwickler*innen zusammen an einer Gruppenaufgabe in einem geteilten Repository arbeiten.
-When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+Wenn Kursteilnehmer*innen eine Gruppenaufgabe annehmen, können sie ein neues Team erstellen oder einem vorhandenen Team beitreten. {% data variables.product.prodname_classroom %} speichert die Teams für eine Aufgabe als Gruppe. Du kannst die Gruppe von Teams für eine bestimmte Aufgabe benennen, wenn du die Aufgabe erstellst. Darüber hinaus kannst du die Gruppe von Teams für eine spätere Aufgabe wiederverwenden.
{% data reusables.classroom.classroom-creates-group-repositories %}
{% data reusables.classroom.about-assignments %}
-You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+Du kannst entscheiden, wie viele Teams einer Aufgabe zugeordnet werden können und wie viele Mitglieder jedes Team haben darf. Jedes Team, das ein*e Kursteilnehmer*in für eine Aufgabe erstellt, ist ein Team in deiner Organisation auf {% data variables.product.product_name %}. Der Sichtbarkeitsstatus des Teams ist geheim. Teams, die du auf {% data variables.product.product_name %} erstellst, werden nicht in {% data variables.product.prodname_classroom %} angezeigt. Weitere Informationen findest du unter [Informationen zu Teams](/organizations/organizing-members-into-teams/about-teams).
-For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+Ein Video zum Erstellen einer Gruppenaufgabe findest du unter [Grundlagen der Einrichtung von {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom).
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## Voraussetzungen
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## Erstellen einer Aufgabe
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## Festlegen der Grundeinstellungen für eine Aufgabe
-Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+Benenne die Aufgabe, entscheide, ob du einen Abgabetermin festlegen möchtest, definiere Teams, und wähle die Sichtbarkeit von Aufgabenrepositorys aus.
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Defining teams for an assignment](#defining-teams-for-an-assignment)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Benennen einer Aufgabe](#naming-an-assignment)
+- [Festlegen eines Abgabetermins für eine Aufgabe](#assigning-a-deadline-for-an-assignment)
+- [Auswählen eines Aufgabentyps](#choosing-an-assignment-type)
+- [Definieren von Teams für eine Aufgabe](#defining-teams-for-an-assignment)
+- [Auswählen der Sichtbarkeit von Aufgabenrepositorys](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### Benennen einer Aufgabe
-For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+Für eine Gruppenaufgabe benennt {% data variables.product.prodname_classroom %} Repositorys nach Repositorypräfix und dem Namen des Teams. Standardmäßig ist das Repositorypräfix der Aufgabentitel. Wenn du eine Aufgabe „Aufgabe-1“ nennst und der Name des Teams auf {% data variables.product.product_name %} „student-team“ ist, lautet der Name des Aufgabenrepositorys für Teammitglieder `assignment-1-student-team`.
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### Festlegen eines Abgabetermins für eine Aufgabe
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### Auswählen eines Aufgabentyps
-Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create an individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+Klicke unter „Einzel- oder Gruppenaufgabe“ auf das Dropdownmenü, und wähle dann **Gruppenaufgabe** aus. Du kannst den Aufgabentyp nach Erstellen der Aufgabe nicht mehr ändern. Wenn du lieber eine Einzelaufgabe erstellen möchtest, findest du weitere Informationen unter [Erstellen einer Einzelaufgabe](/education/manage-coursework-with-github-classroom/create-an-individual-assignment).
-### Defining teams for an assignment
+### Definieren von Teams für eine Aufgabe
-If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+Wenn du bereits eine Gruppenaufgabe für den Kurs erstellt hast, kannst du eine Gruppe von Teams für die neue Aufgabe wiederverwenden. Gib den Namen für eine Gruppe ein, um eine neue Gruppe mit den Teams zu erstellen, die deine Kursteilnehmer*innen für die Aufgabe erstellen. Optional kannst du die maximale Anzahl von Teammitgliedern und Teams insgesamt eingeben.
{% tip %}
-**Tips**:
+**Tipps**:
-- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+- Es wird empfohlen, Details zur Gruppe von Teams in den Namen für die Gruppe einzuschließen. Wenn du beispielsweise die Gruppe von Teams für eine Aufgabe verwenden möchtest, benenne die Gruppe nach der Aufgabe. Wenn du die Gruppe für ein ganzes Semester oder einen ganzen Kurs verwenden willst, benenne die Gruppe nachdem Semester oder Kurs.
-- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+- Wenn du Kursteilnehmer*innen einem bestimmten Team zuweisen möchtest, gib den Kursteilnehmer*innen einen Namen für das Team, und stelle eine Liste aller Mitglieder bereit.
{% endtip %}
-
+
-### Choosing a visibility for assignment repositories
+### Auswählen der Sichtbarkeit von Aufgabenrepositorys
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -80,22 +86,22 @@ If you've already created a group assignment for the classroom, you can reuse a
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## Hinzufügen von Startcode und Konfigurieren einer Entwicklungsumgebung
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [Auswählen eines Vorlagenrepositorys](#choosing-a-template-repository)
+- [Auswählen einer integrierten Entwicklungsumgebung (IDE)](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### Auswählen eines Vorlagenrepositorys
-By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %}
+Standardmäßig erstellt eine neue Aufgabe ein leeres Repository für jedes Team, das ein*e Kursteilnehmer*in erstellt. {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
-### Choosing an integrated development environment (IDE)
+### Auswählen einer integrierten Entwicklungsumgebung (IDE)
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} Weitere Informationen findest du unter [Integrieren von {% data variables.product.prodname_classroom %} mit einer IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide).
{% data reusables.classroom.classroom-codespaces-link %}
@@ -103,18 +109,18 @@ By default, a new assignment will create an empty repository for each team that
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-## Providing feedback
+## Abgeben von Feedback
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+Optional kannst du Aufgaben automatisch benoten und Raum für Diskussionen über die einzelnen Übermittlungen mit dem Team schaffen.
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [Automatisches Testen von Aufgaben](#testing-assignments-automatically)
+- [Erstellen eines Pull Requests für Feedback](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### Automatisches Testen von Aufgaben
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### Erstellen eines Pull Requests für Feedback
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -122,36 +128,36 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## Einladen von Kursteilnehmer*innen zu einer Aufgabe
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+Auf der Registerkarte **Teams** für die Aufgabe kannst du die Teams anzeigen, die an einer Aufgabe arbeiten oder diese übermittelt haben. {% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
+## Überwachen des Fortschritts von Kursteilnehmer*innen
+Auf der Übersichtsseite für Aufgaben werden Informationen zum Aufgabenannahmestatus und Teamfortschritt angezeigt. Möglicherweise werden basierend auf den Konfigurationen deiner Aufgaben verschiedene Zusammenfassungsinformationen angezeigt.
-- **Total teams**: The number of teams that have been created.
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
-- **Accepted teams**: The number of teams who have accepted this assignment.
-- **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
+- **Teams insgesamt:** Anzahl der erstellten Teams
+- **Kursteilnehmerliste:** Anzahl der Kursteilnehmer*innen auf der Kursliste
+- **Kursteilnehmer*innen, die nicht in einem Teams sind:** Anzahl der Kursteilnehmer*innen in der Kursliste, die noch keinem Team angehören
+- **Akzeptierte Teams:** Anzahl der Teams, die die Aufgabe angenommen haben
+- **Übermittelte Aufgaben:** Anzahl der Teams, die die Aufgabe übermittelt haben. Die Übermittlung wird zum Abgabezeitpunkt für die Aufgabe ausgelöst.
+- **Teams, die bestanden haben:** Anzahl der Teams, die derzeit den automatisch benoteten Test für diese Aufgabe bestehen
-## Next steps
+## Nächste Schritte
-- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}.
+- Nachdem du die Aufgabe erstellt hast und die Kursteilnehmer*innen Teams gebildet haben, können Teammitglieder mithilfe von Git und {% data variables.product.product_name %}-Features mit der Arbeit an der Aufgabe beginnen. Kursteilnehmer*innen können das Repository klonen, Commits pushen, Branches verwalten, Pull Requests erstellen und überprüfen, Mergekonflikte adressieren und Änderungen mit Issues diskutieren. Sowohl du als auch das Team kann den Commitverlauf für das Repository überprüfen. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github), [Repositorys](/repositories), [Verwenden von Git](/github/getting-started-with-github/using-git) und [Zusammenarbeiten mit Issues und Pull Requests](/github/collaborating-with-issues-and-pull-requests). Im kostenlosen Kurs zum [Auflösen von Mergekonflikten](https://github.com/skills/resolve-merge-conflicts) in {% data variables.product.prodname_learning %} erhältst du ebenfalls Informationen.
-- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- Wenn ein Team eine Aufgabe abgeschlossen hat, kannst du die Dateien im Repository oder den Verlauf und Visualisierungen für das Repository überprüfen, um besser zu verstehen, wie das Team zusammengearbeitet hat. Weitere Informationen findest du unter [Visualisieren von Repositorydaten mit Graphen](/github/visualizing-repository-data-with-graphs).
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- Du kannst Feedback zu einer Aufgabe bereitstellen, indem du einzelne Commits oder Zeilen in einem Pull Request kommentierst. Weitere Informationen findest du unter [Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request) und [Öffnen eines Issues zu Code](/github/managing-your-work-on-github/opening-an-issue-from-code). Weitere Informationen zum Erstellen gespeicherter Antworten für Feedback zu häufigen Fehlern findest du unter [Informationen zu gespeicherten Antworten](/github/writing-on-github/about-saved-replies).
-## Further reading
+## Weiterführende Themen
-- [{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
-- "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
-- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
+- [{% data variables.product.prodname_global_campus %} für Lehrkräfte](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- [Verknüpfen eines Learning Management System-Kurses mit einem Kursraum](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)
+- [Verwenden vorhandener Teams in Gruppenaufgaben](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in der {% data variables.product.prodname_education %}-Community
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 8161608b81..2b1261cb94 100644
--- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -1,6 +1,6 @@
---
-title: Create an individual assignment
-intro: You can create an assignment for students in your course to complete individually.
+title: Erstellen einer Einzelaufgabe
+intro: 'Du kannst eine Aufgabe für Studierende im Kurs erstellen, die individuell abgeschlossen werden soll.'
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
@@ -8,8 +8,14 @@ redirect_from:
- /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
- /education/manage-coursework-with-github-classroom/create-an-individual-assignment
shortTitle: Individual assignment
+ms.openlocfilehash: 1ffa725be4e42695b297545f65c998b14ed8e000
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179747'
---
-## About individual assignments
+## Informationen zu Einzelaufgaben
{% data reusables.classroom.assignments-individual-definition %}
@@ -17,42 +23,42 @@ shortTitle: Individual assignment
{% data reusables.classroom.about-assignments %}
-For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+Ein Video zum Erstellen einer Einzelaufgabe findest du unter [Grundlagen der Einrichtung von {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom).
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## Voraussetzungen
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## Erstellen einer Aufgabe
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## Festlegen der Grundeinstellungen für eine Aufgabe
-Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+Benenne die Aufgabe, entscheide, ob du einen Abgabetermin festlegen möchtest, und wähle die Sichtbarkeit von Aufgabenrepositorys aus.
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Benennen einer Aufgabe](#naming-an-assignment)
+- [Festlegen eines Abgabetermins für eine Aufgabe](#assigning-a-deadline-for-an-assignment)
+- [Auswählen eines Aufgabentyps](#choosing-an-assignment-type)
+- [Auswählen der Sichtbarkeit von Aufgabenrepositorys](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### Benennen einer Aufgabe
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+Bei einer einzelnen Aufgabe werden Repositorys von {% data variables.product.prodname_classroom %} durch das Repositorypräfix und den {% data variables.product.product_name %}-Benutzernamen des Kursteilnehmers benannt. Standardmäßig ist das Repositorypräfix der Aufgabentitel. Wenn du eine Aufgabe beispielsweise „assignment-1“ nennst und der Name des Kursteilnehmers auf {% data variables.product.product_name %} @octocat lautet, wird der Name des Aufgabenrepositorys für @octocat auf `assignment-1-octocat` festgelegt.
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### Festlegen eines Abgabetermins für eine Aufgabe
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### Auswählen eines Aufgabentyps
-Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+Klicke unter „Einzel- oder Gruppenaufgabe“ im Dropdownmenü auf **Einzelaufgabe**. Du kannst den Aufgabentyp nach Erstellen der Aufgabe nicht mehr ändern. Wenn du lieber eine Gruppenaufgabe erstellen möchtest, findest du unter [Erstellen einer Gruppenaufgabe](/education/manage-coursework-with-github-classroom/create-a-group-assignment) weitere Informationen.
-### Choosing a visibility for assignment repositories
+### Auswählen der Sichtbarkeit von Aufgabenrepositorys
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -60,41 +66,41 @@ Under "Individual or group assignment", select the drop-down menu, and click **I
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## Hinzufügen von Startcode und Konfigurieren einer Entwicklungsumgebung
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [Auswählen eines Vorlagenrepositorys](#choosing-a-template-repository)
+- [Auswählen einer integrierten Entwicklungsumgebung (IDE)](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### Auswählen eines Vorlagenrepositorys
-By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+Standardmäßig erstellt eine neue Aufgabe ein leeres Repository für sämtliche Kursteilnehmenden im Listenfeld für den Classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-### Choosing an integrated development environment (IDE)
+### Auswählen einer integrierten Entwicklungsumgebung (IDE)
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} Weitere Informationen findest du unter [Integrieren von {% data variables.product.prodname_classroom %} mit einer IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide).
{% data reusables.classroom.classroom-codespaces-link %}
{% data reusables.classroom.assignments-guide-choose-an-online-ide %}
-## Providing feedback for an assignment
+## Bereitstellen von Feedback für eine Aufgabe
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
+Optional kannst du Aufgaben automatisch benoten und Raum für Diskussionen über die einzelnen Übermittlungen mit den Kursteilnehmenden schaffen.
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [Automatisches Testen von Aufgaben](#testing-assignments-automatically)
+- [Erstellen eines Pull Requests für Feedback](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### Automatisches Testen von Aufgaben
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### Erstellen eines Pull Requests für Feedback
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -102,34 +108,34 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## Einladen von Kursteilnehmer*innen zu einer Aufgabe
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
+Auf der Registerkarte **Kursliste** für die Aufgabe kannst du anzeigen, ob ein Kursteilnehmer dem Kursraum beigetreten ist und eine Aufgabe angenommen oder eingereicht hat. Du kannst auf dieser Registerkarte auch die {% data variables.product.prodname_dotcom %}-Aliase von Kursteilnehmenden mit ihrem zugeordneten Listenbezeichner verknüpfen und umgekehrt. {% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
+## Überwachen des Fortschritts von Kursteilnehmer*innen
+Auf der Seite mit der Aufgabenübersicht findest du eine Übersicht über deine angenommenen Aufgaben und den Fortschritt der Kursteilnehmenden. Möglicherweise werden basierend auf den Konfigurationen deiner Aufgaben verschiedene Zusammenfassungsinformationen angezeigt.
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
-- **Accepted students**: The number of accounts have accepted this assignment.
-- **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing students**: The number of students currently passing the autograding tests for this assignment.
+- **Kursteilnehmerliste:** Anzahl der Kursteilnehmer*innen auf der Kursliste
+- **Hinzugefügte Kursteilnehmende:** Anzahl der {% data variables.product.prodname_dotcom %}-Konten, die die Aufgabe akzeptiert haben und keinem Listenbezeichner zugeordnet sind
+- **Akzeptierte Kursteilnehmende:** Anzahl der Konten, die diese Aufgabe akzeptiert haben
+- **Übermittelte Aufgaben:** Anzahl der Kursteilnehmenden, die die Aufgabe übermittelt haben. Die Übermittlung wird zum Abgabezeitpunkt für die Aufgabe ausgelöst.
+- **Bestandene Kursteilnehmende:** Anzahl der Kursteilnehmenden, die derzeit die automatisch benoteten Tests für diese Aufgabe bestehen
-## Next steps
+## Nächste Schritte
-- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- Nachdem du die Aufgabe erstellt hast, können die Kursteilnehmenden mithilfe von Git und {% data variables.product.product_name %}-Features mit der Arbeit an der Aufgabe beginnen. Kursteilnehmer*innen können das Repository klonen, Commits pushen, Branches verwalten, Pull Requests erstellen und überprüfen, Mergekonflikte adressieren und Änderungen mit Issues diskutieren. Sowohl du als auch die Kursteilnehmenden können den Commitverlauf für das Repository überprüfen. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github), [Repositorys](/repositories) und [Zusammenarbeiten an Issues und Pull Requests](/github/collaborating-with-issues-and-pull-requests).
-- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- Wenn ein Kursteilnehmer eine Aufgabe abgeschlossen hat, kannst du die Dateien im Repository oder den Verlauf und die Visualisierungen für das Repository überprüfen, um seine Arbeit besser zu verstehen. Weitere Informationen findest du unter [Visualisieren von Repositorydaten mit Graphen](/github/visualizing-repository-data-with-graphs).
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- Du kannst Feedback zu einer Aufgabe bereitstellen, indem du einzelne Commits oder Zeilen in einem Pull Request kommentierst. Weitere Informationen findest du unter [Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request) und [Öffnen eines Issues zu Code](/github/managing-your-work-on-github/opening-an-issue-from-code). Weitere Informationen zum Erstellen gespeicherter Antworten für Feedback zu häufigen Fehlern findest du unter [Informationen zu gespeicherten Antworten](/github/writing-on-github/about-saved-replies).
-## Further reading
+## Weiterführende Themen
-- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
+- [{% data variables.product.prodname_global_campus %} für Lehrkräfte](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- [Verbinden eines Lernverwaltungssystems mit {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)
diff --git a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md
index 7a247d6c1c..20c3b54274 100644
--- a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -1,83 +1,88 @@
---
-title: Getting started with GitHub AE
-intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.'
+title: Erste Schritte mit GitHub AE
+intro: 'Erste Schritte beim Einrichten und Konfigurieren von {% data variables.product.product_name %} für {% data variables.location.product_location %}.'
versions:
ghae: '*'
+ms.openlocfilehash: 957a922a2493abd8f625cdb9e9d6650283820222
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180061'
---
+In diesem Leitfaden erfährst du, wie du Einstellungen für {% data variables.location.product_location %} in {% data variables.product.product_name %} als Unternehmensadministrator*in einrichtest, konfigurierst und verwaltest. Weitere Informationen zu {% data variables.product.product_name %} findest du unter [Informationen zu {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae).
-This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)."
+## Teil 1: Einrichten von {% data variables.product.product_name %}
+Um mit {% data variables.product.product_name %} zu beginnen, kannst du dein Unternehmenskonto erstellen, {% data variables.product.product_name %} initialisieren, eine Liste zugelassener IP-Adressen sowie die Benutzerauthentifizierung und Bereitstellung konfigurieren und die Abrechnung für {% data variables.location.product_location %} verwalten.
-## Part 1: Setting up {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}.
-
-### 1. Creating your {% data variables.product.product_name %} enterprise account
-You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+### 1. Erstellen deines {% data variables.product.product_name %}-Unternehmenskontos
+Zuerst musst du {% data variables.product.product_name %} erwerben. Weitere Informationen erhältst du vom [Vertriebsteam für {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
{% data reusables.github-ae.initialize-enterprise %}
-### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+### 2. Initialisieren von {% data variables.product.product_name %}
+Nachdem {% data variables.product.company_short %} das Besitzerkonto für {% data variables.location.product_location %} in {% data variables.product.product_name %} erstellt hat, erhältst du eine E-Mail, um dich anzumelden und die Initialisierung abzuschließen. Während der Initialisierung benennst du als Unternehmensbesitzer*in {% data variables.location.product_location %}, konfigurierst SAML-SSO, erstellst Richtlinien für alle Organisationen in {% data variables.location.product_location %} und konfigurierst einen Supportkontakt für deine Enterprise-Mitglieder. Weitere Informationen findest du unter [Initialisieren von {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae).
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 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)."
+### 3. Einschränken des Netzwerkzugriffs
+Du kannst eine Liste bestimmter, zugelassener IP-Adressen konfigurieren, um den Zugriff auf Ressourcen im Besitz von Organisationen in deinem Unternehmenskonto einzuschränken. Weitere Informationen findest du unter [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen mit einer Liste zugelassener IP-Adressen](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list).
-### 4. Managing identity and access for {% data variables.location.product_location %}
-You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[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)."
+### 4. Verwalten der Identität und des Zugriffs für {% data variables.location.product_location %}
+Du kannst den Zugriff auf {% data variables.location.product_location %} in {% data variables.product.product_name %} über einen Identitätsanbieter (IdP) mithilfe von SAML-SSO (Single Sign-On, einmaliges Anmelden) für die Benutzerauthentifizierung und SCIM (System for Cross-Domain Identity Management) für die Benutzerbereitstellung zentral verwalten. Nachdem du die Bereitstellung konfiguriert hast, kannst du der Anwendung Benutzer über den IdP zuweisen bzw. deren Zuweisung aufheben und Benutzerkonten im Unternehmen erstellen oder deaktivieren. Weitere Informationen findest du unter [Informationen zur Identitäts- und Zugriffsverwaltung für dein Unternehmen](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise).
-### 5. Managing billing for {% data variables.location.product_location %}
-Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+### 5. Verwalten der Abrechnung für {% data variables.location.product_location %}
+Besitzer*innen des Abonnements für {% data variables.location.product_location %} in {% data variables.product.product_name %} können Abrechnungsdetails für {% data variables.product.product_name %} im Azure-Portal einsehen. Weitere Informationen findest du unter [Verwalten der Abrechnung für ein Unternehmen](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise).
-## Part 2: Organizing and managing enterprise members
-As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
+## Teil 2: Organisieren und Verwalten von Enterprise-Mitgliedern
+Als Unternehmensbesitzer*in für {% data variables.product.product_name %} kannst du Einstellungen auf Benutzer-, Repository-, Team- und Organisationsebene verwalten. Du kannst Mitglieder von {% data variables.location.product_location %} verwalten, Organisationen erstellen und verwalten, Richtlinien für die Repositoryverwaltung festlegen und Teams erstellen und verwalten.
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. Verwalten von Mitgliedern von {% data variables.location.product_location %}
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. Erstellen von Organisationen
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. Hinzufügen von Mitgliedern zu Organisationen
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. Erstellen von Teams
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. Festlegen von Berechtigungsstufen für Organisationen und Repositorys
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. Erzwingen von Repositoryverwaltungsrichtlinien
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations.
+## Teil 3: Sicheres Erstellen
+Um die Sicherheit von {% data variables.location.product_location %} zu erhöhen, kannst du {% data variables.location.product_location %} überwachen und Sicherheits- und Analysefeatures für deine Organisationen konfigurieren.
-### 1. Monitoring {% data variables.location.product_location %}
-You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)."
+### 1. Überwachen von {% data variables.location.product_location %}
+Du kannst {% data variables.location.product_location %} mit deinem Aktivitätsdashboard und dem Überwachungsprotokoll überwachen. Weitere Informationen findest du unter [Überwachung von Aktivitäten in deinem Unternehmen](/admin/monitoring-activity-in-your-enterprise).
-### 2. Configuring security features for your organizations
+### 2. Konfigurieren von Sicherheitsfeatures für deine Organisationen
{% data reusables.getting-started.configuring-security-features %}
-## Part 4: Customizing and automating work on {% data variables.location.product_location %}
-You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
+## Teil 4: Anpassen und Automatisieren der Arbeit in {% data variables.location.product_location %}
+Du kannst die Arbeit in Organisationen in {% data variables.location.product_location %} mit der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API sowie mit {% data variables.product.prodname_actions %} und {% data variables.product.prodname_pages %} anpassen und automatisieren.
-### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Verwenden der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API
{% data reusables.getting-started.api %}
-### 2. Building {% data variables.product.prodname_actions %}
+### 2. Erstellen von {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."
+Weitere Informationen zum Aktivieren und Konfigurieren von {% data variables.product.prodname_actions %} für {% data variables.product.product_name %} findest du unter [Erste Schritte mit {% data variables.product.prodname_actions %} für {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae).
-### 3. Using {% data variables.product.prodname_pages %}
+### 3. Verwenden von {% data variables.product.prodname_pages %}
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Teil 5: Verwenden der Lern- und Supportressourcen von {% data variables.product.prodname_dotcom %}
+Die Mitglieder deines Unternehmens können mit unseren Lernressourcen mehr über Git und {% data variables.product.prodname_dotcom %} erfahren, und du kannst mit {% data variables.product.prodname_dotcom %} Enterprise Support genau den Support erhalten, den du benötigst.
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+### 1. Informationen zu {% data variables.product.product_name %} in {% data variables.product.prodname_docs %}
+Du kannst die Dokumentation zu den mit {% data variables.product.prodname_ghe_managed %} verfügbaren Features lesen. Weitere Informationen findest du unter [Informationen zu Versionen von {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs).
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. Lernen mit {% data variables.product.prodname_learning %}
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Arbeiten mit {% data variables.product.prodname_dotcom %} Enterprise Support
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index f3368b385c..dda45438c0 100644
--- a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,128 +1,132 @@
---
-title: Getting started with GitHub Enterprise Server
-intro: 'Get started with setting up and managing {% data variables.location.product_location %}.'
+title: Erste Schritte mit GitHub Enterprise Server
+intro: 'Erste Schritte beim Einrichten und Verwalten von {% data variables.location.product_location %}.'
versions:
ghes: '*'
+ms.openlocfilehash: 68cd462c42ef63863750d9edc5e122dc3c325115
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163416'
---
+In diesem Leitfaden erfährst du, wie du als Unternehmensadministrator {% data variables.location.product_location %} einrichtest, konfigurierst und verwaltest.
-This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator.
-
-{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
+{% data variables.product.company_short %} bietet zwei Möglichkeiten zum Bereitstellen von {% data variables.product.prodname_enterprise %}.
- **{% data variables.product.prodname_ghe_cloud %}**
- **{% data variables.product.prodname_ghe_server %}**
-{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
+{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. Du kannst {% data variables.product.prodname_ghe_server %} im eigenen Rechenzentrum oder bei einem unterstützten Cloudanbieter bereitstellen und hosten.
-For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)."
+Weitere Informationen über {% data variables.product.product_name %} findest du unter [Informationen über {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server).
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing.
-### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## Teil 1: Installieren von {% data variables.product.product_name %}
+Für den Einstieg in {% data variables.product.product_name %} musst du ein Unternehmenskonto erstellen, die Instanz installieren, die Verwaltungskonsole für die Ersteinrichtung verwenden, die Instanz konfigurieren und sich um die Abrechnung kümmern.
+### 1. Erstellen eines Unternehmenskontos
+Vor der Installation von {% data variables.product.product_name %} kannst du auf {% data variables.product.prodname_dotcom_the_website %} ein Unternehmenskonto erstellen. Wende dich dazu an das [Vertriebsteam von {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). Ein Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} ist nützlich für die Abrechnung sowie für Features, die über {% data variables.product.prodname_github_connect %} auf {% data variables.product.prodname_dotcom_the_website %} freigegeben werden. Weitere Informationen findest du unter [Informationen zu Unternehmenskonten](/admin/overview/about-enterprise-accounts).
+### 2. Installieren von {% data variables.product.product_name %}
+Für den Einstieg in {% data variables.product.product_name %} musst du die Appliance auf einer Virtualisierungsplattform deiner Wahl installieren. Weitere Informationen findest du unter [Einrichten einer {% data variables.product.prodname_ghe_server %}-Instanz](/admin/installation/setting-up-a-github-enterprise-server-instance).
-### 3. Using the Management Console
-You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+### 3. Öffnen der Verwaltungskonsole
+Beim ersten Aufruf von {% data variables.location.product_location %} verwendest du die Verwaltungskonsole für die Ersteinrichtung. Du kannst die Verwaltungskonsole auch verwenden, um Instanzeinstellungen wie Lizenzen, Domänen, Authentifizierung und TLS zu verwalten. Weitere Informationen findest du unter [Zugreifen auf die Verwaltungskonsole](/admin/configuration/configuring-your-enterprise/accessing-the-management-console).
-### 4. Configuring {% data variables.location.product_location %}
-In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
+### 4. Konfigurieren {% data variables.location.product_location %}
+Neben der Verwaltungskonsole kannst du auch das Dashboard für die Websiteverwaltung und die Verwaltungsshell (SSH) verwenden, um {% data variables.location.product_location %} zu verwalten. So kannst du beispielsweise Anwendungen und Ratenbegrenzungen konfigurieren, Berichte anzeigen und Befehlszeilenprogramme verwenden. Weitere Informationen findest du unter [Konfigurieren deines Unternehmens](/admin/configuration/configuring-your-enterprise).
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+Du kannst die von {% data variables.product.product_name %} standardmäßig über DHCP (Dynamic Host Configuration Protocol) verwendeten Netzwerkeinstellungen verwenden oder die Netzwerkeinstellungen mithilfe der VM-Konsole konfigurieren. Zudem kannst du einen Proxyserver oder Firewallregeln konfigurieren. Weitere Informationen findest du unter [Konfigurieren von Netzwerkeinstellungen](/admin/configuration/configuring-network-settings).
-### 5. Configuring high availability
-You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
+### 5. Konfigurieren von Hochverfügbarkeit
+Du kannst {% data variables.location.product_location %} für Hochverfügbarkeit konfigurieren, um die Auswirkungen von Hardwarefehlern und Netzwerkausfällen zu minimieren. Weitere Informationen findest du unter [Konfigurieren von Hochverfügbarkeit](/admin/enterprise-management/configuring-high-availability).
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 6. Einrichten einer Staginginstanz
+Du kannst eine Staginginstanz einrichten, um Änderungen zu testen, eine Notfallwiederherstellung zu planen und Updates auszuprobieren, bevor du sie auf {% data variables.location.product_location %} anwendest. Weitere Informationen findest du unter [Einrichten einer Staginginstanz](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance).
-### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+### 7. Festlegen von Sicherungen und Notfallwiederherstellungen
+Zum Schutz deiner Produktionsdaten kannst du automatisierte Sicherungen für {% data variables.location.product_location %} mit {% data variables.product.prodname_enterprise_backup_utilities %} konfigurieren. Weitere Informationen findest du unter [Konfigurieren von Sicherungen auf deiner Appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).
-### 8. Managing billing for your enterprise
-Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+### 8. Verwalten der Abrechnung für ein Unternehmen
+Die Abrechnung für alle Organisationen und {% data variables.product.product_name %}-Instanzen, die mit deinem Unternehmenskonto verbunden sind, werden in einer einzigen Rechnung für alle kostenpflichtigen {% data variables.product.prodname_dotcom %}.com-Services aggregiert. Unternehmensbesitzer*innen als auch Abrechnungsmanager*innen können auf Abrechnungseinstellungen für Unternehmenskonten zugreifen und diese verwalten. Weitere Informationen findest du unter [Verwalten der Abrechnung für ein Unternehmen](/admin/overview/managing-billing-for-your-enterprise).
-## Part 2: Organizing and managing your team
-As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
+## Teil 2: Organisieren und Verwalten von Teams
+Als Unternehmensbesitzer oder Administrator kannst du Einstellungen auf Benutzer-, Repository-, Team- und Organisationsebenen verwalten. Du kannst Mitglieder deines Unternehmens verwalten, Organisationen erstellen und verwalten, Richtlinien für die Repositoryverwaltung festlegen und Teams erstellen und verwalten.
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. Verwalten von Mitgliedern von {% data variables.location.product_location %}
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. Erstellen von Organisationen
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. Hinzufügen von Mitgliedern zu Organisationen
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. Erstellen von Teams
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. Festlegen von Berechtigungsstufen für Organisationen und Repositorys
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. Erzwingen von Repositoryverwaltungsrichtlinien
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
-### 1. Authenticating enterprise members
-You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+## Teil 3: Sicheres Erstellen
+Zur Verbesserung der Sicherheit von {% data variables.location.product_location %} kannst du die Authentifizierung für Unternehmensmitglieder konfigurieren, Tools und die Überwachungsprotokollierung zur Gewährleistung der Konformität nutzen, Sicherheits- und Analysefeatures für deine Organisationen konfigurieren und optional {% data variables.product.prodname_GH_advanced_security %} aktivieren.
+### 1. Authentifizieren von Unternehmensmitgliedern
+Du kannst die integrierte Authentifizierungsmethode von {% data variables.product.product_name %} verwenden oder einen externen Authentifizierungsanbieter wie CAS, LDAP oder SAML auswählen, um deine vorhandenen Konten zu integrieren und den Benutzerzugriff auf {% data variables.location.product_location %} zentral zu verwalten. Weitere Informationen findest du unter [Informationen zur Authentifizierung für dein Unternehmen](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).
-You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
+Du kannst auch festlegen, dass für all deine Organisationen eine zweistufige Authentifizierung erforderlich ist. Weitere Informationen findest du unter [Festlegen, dass für eine Organisation die zweistufige Authentifizierung erforderlich ist](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization).
-### 2. Staying in compliance
-You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+### 2. Wahrung der Compliance
+Zur Automatisierung von Complianceworkflows sowie zur Einhaltung von Compliancestandards in deiner Organisation kannst du obligatorische Status- und Commitüberprüfungen implementieren. Du kannst auch das Überwachungsprotokoll für deine Organisation verwenden, um Aktionen zu überprüfen, die von deinem Team ausgeführt werden. Weitere Informationen findest du unter [Erzwingen einer Richtlinie mit Pre-Receive-Hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks) und [Informationen zum Überwachungsprotokoll für ein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise).
{% ifversion ghes %}
-### 3. Configuring security features for your organizations
-{% data reusables.getting-started.configuring-security-features %}
-{% endif %}
+### 3. Konfigurieren von Sicherheitsfeatures für eine Organisation
+{% data reusables.getting-started.configuring-security-features %} {% endif %}
{% ifversion ghes %}
-### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
-You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+### 4. Aktivieren von {% data variables.product.prodname_GH_advanced_security %}-Features
+Du kannst deine {% data variables.product.product_name %}-Lizenz upgraden, sodass {% data variables.product.prodname_GH_advanced_security %} enthalten ist. Dadurch hast du Zugriff auf zusätzliche Features, die Benutzer*innen helfen, Sicherheitsprobleme in ihren Codes zu erkennen und zu beheben, z. B. Code- und Geheimnisprüfungen. Weitere Informationen findest du unter [{% data variables.product.prodname_GH_advanced_security %} für dein Unternehmen](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise).
{% endif %}
-## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
-You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
+## Teil 4: Anpassen und Automatisieren von Unternehmensarbeit auf {% data variables.product.prodname_dotcom %}
+Mit {% data variables.product.prodname_dotcom %}- und {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} und {% data variables.product.prodname_pages %} kannst du Arbeit in Organisationen in einem Unternehmen anpassen und automatisieren.
-### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Erstellen von {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %}
+Mit der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API kannst du Integrationen wie {% data variables.product.prodname_github_apps %} oder {% data variables.product.prodname_oauth_apps %} zur Verwendung in Organisationen in deinem Unternehmen erstellen, um Workflows zu ergänzen und zu erweitern. Weitere Informationen findest du unter [Informationen zu Apps](/developers/apps/getting-started-with-apps/about-apps).
+### 2. Verwenden der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API
{% data reusables.getting-started.api %}
{% ifversion ghes %}
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. Erstellen von {% data variables.product.prodname_actions %}-Aktionen
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+Weitere Informationen zum Aktivieren und Konfigurieren von {% data variables.product.prodname_actions %} auf {% data variables.product.product_name %} findest du unter [Erste Schritte mit {% data variables.product.prodname_actions %} für {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server).
-### 4. Publishing and managing {% data variables.product.prodname_registry %}
+### 4. Veröffentlichen und Verwalten von {% data variables.product.prodname_registry %}
{% data reusables.getting-started.packages %}
-For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+Weitere Informationen zum Aktivieren und Konfigurieren von {% data variables.product.prodname_registry %} für {% data variables.location.product_location %} findest du unter [Erste Schritte mit {% data variables.product.prodname_registry %} für dein Unternehmen](/admin/packages/getting-started-with-github-packages-for-your-enterprise).
{% endif %}
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. Verwenden von {% data variables.product.prodname_pages %}
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
-You can use {% data variables.product.prodname_github_connect %} to share resources.
+## Teil 5: Herstellen einer Verbindung mit anderen {% data variables.product.prodname_dotcom %}-Ressourcen
+Zum Freigeben von Ressourcen kannst du {% data variables.product.prodname_github_connect %} verwenden.
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Wenn du der Besitzer einer {% data variables.product.product_name %}-Instanz und einer {% data variables.product.prodname_ghe_cloud %}-Organisation oder eines Unternehmenskontos bist, kannst du {% data variables.product.prodname_github_connect %} aktivieren. Mit {% data variables.product.prodname_github_connect %} kannst du bestimmte Workflows und Features zwischen {% data variables.location.product_location %} und {% data variables.product.prodname_ghe_cloud %} gemeinsam nutzen, z. B. die gemeinsame Suche und einheitliche Beiträge. Weitere Informationen findest du unter [Herstellen einer Verbindung zwischen {% data variables.product.prodname_ghe_server %} und {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud).
-## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Teil 6: Verwenden der Lern- und Supportressourcen von {% data variables.product.prodname_dotcom %}
+Deine Unternehmensmitglieder können mit unseren Lernressourcen mehr über Git und {% data variables.product.prodname_dotcom %} erfahren, und du erhältst mit {% data variables.product.prodname_dotcom %} Enterprise Support den Support, den du zum Einrichten und Verwalten von {% data variables.location.product_location %} benötigst.
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+### 1. Informationen zu {% data variables.product.product_name %} in {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+Du kannst die Dokumentation zu den im Zusammenhang mit {% data variables.product.prodname_ghe_server %} verfügbaren Features lesen. Weitere Informationen findest du unter [Informationen zu Versionen von {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs).
{% data reusables.enterprise.best-practices %}
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. Lernen mit {% data variables.product.prodname_learning %}
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Arbeiten mit {% data variables.product.prodname_dotcom %} Enterprise Support
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 02ab297dbb..3ed5b9a95c 100644
--- a/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,6 +1,6 @@
---
-title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
-intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
+title: 'Migrieren von {% data variables.product.prodname_projects_v1 %}'
+intro: 'Du kannst deine {% data variables.projects.projects_v1_board %}s in die neue Umgebung von {% data variables.product.prodname_projects_v2 %} migrieren.'
miniTocMaxHeadingLevel: 3
versions:
feature: projects-v2
@@ -10,57 +10,53 @@ type: tutorial
topics:
- Projects
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e6db4fd8c6587f413ee0e6832dbae93bbf281573
+ms.sourcegitcommit: 9bf175b190674416ad4e11b5c567409f74c00ad2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/23/2022
+ms.locfileid: '148181221'
---
-
-
{% note %}
-**Notes:**
+**Hinweise:**
-- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
-- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
-- Automation will not be migrated.
-- Triage, archive, and activity will not be migrated.
-- After migration, the new migrated project and old project will not be kept in sync.
+- Wenn das Projekt, das du migrierst, mehr als {% data variables.projects.item_limit %} Elemente enthält, werden offene Issues priorisiert, gefolgt von offenen Pull Requests und Anmerkungen. Der verbleibende Platz wird für geschlossene Issues sowie gemergte und geschlossene Pull Requests genutzt. Elemente, die aufgrund dieses Grenzwerts nicht migriert werden können, werden ins Archiv verschoben. Wenn der Archivgrenzwert von {% data variables.projects.archived_item_limit %} Elementen erreicht ist, werden keine weiteren Elemente migriert.
+- Hinweiskarten werden in Issueentwürfe konvertiert, der Inhalt wird im Textkörper des Issueentwurfs gespeichert. Wenn Informationen fehlen sollten, mache alle verborgenen Felder sichtbar. Weitere Informationen findest du unter [Anzeigen und Ausblenden von Feldern](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields).
+- Automatisierungen werden nicht migriert.
+- Selektierung, Archiv und Aktivität werden nicht migriert.
+- Nach der Migration bleiben das neue migrierte Projekt und das alte Projekt nicht mehr synchronisiert.
{% endnote %}
-## About project migration
+## Informationen zur Projektmigration
-You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
+Du kannst deine Projektboards zur neuen Umgebung von {% data variables.product.prodname_projects_v2 %} migrieren und Tabellen, mehrere Ansichten, neue Automatisierungsoptionen und leistungsstarke Feldtypen ausprobieren. Weitere Informationen findest du unter [Informationen zu Projekten](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
-## Migrating an organization project board
+## Migrieren des Projektboards einer Organisation
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
-1. On the left, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
+1. Klicke auf der linken Seite auf **Projekte (klassisch)** .
+  {% data reusables.projects.migrate-project-steps %}
-## Migrating a user project board
+## Migrieren eines Benutzerprojektboards
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_profile %}
-1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
- 
-1. Above the list of projects, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
+1. Klicke oben auf deiner Profilseite in der Hauptnavigation auf {% octicon "table" aria-label="The project board icon" %} **Projekte**.
+ 
+1. Klicke über der Liste der Projekte auf **Projekte (klassisch)** .
+  {% data reusables.projects.migrate-project-steps %}
-## Migrating a repository project board
+## Migrieren eines Repositoryprojektboards
{% note %}
-**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
+**Hinweis:** Projekte auf Repositoryebene werden von {% data variables.projects.projects_v2_caps %} nicht unterstützt. Wenn du ein Repositoryprojektboard migrierst, wird es entweder in die Organisation oder in das persönliche Konto migriert, zu dem das Repositoryprojekt gehört, und das migrierte Projekt wird an das ursprüngliche Repository angeheftet.
{% endnote %}
-{% data reusables.projects.enable-migration %}
-{% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
-
-1. Click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
+1. Klicke unter dem Namen des Repositorys auf {% octicon "table" aria-label="The project board icon" %} **Projekte**.
+
+1. Klicke auf **Projekte (klassisch)** .
+  {% data reusables.projects.migrate-project-steps %}
diff --git a/translations/de-DE/content/packages/quickstart.md b/translations/de-DE/content/packages/quickstart.md
index 7ff2db3442..81dc7ccb6a 100644
--- a/translations/de-DE/content/packages/quickstart.md
+++ b/translations/de-DE/content/packages/quickstart.md
@@ -1,6 +1,6 @@
---
-title: Quickstart for GitHub Packages
-intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
+title: Schnellstartanleitung für GitHub Packages
+intro: 'Veröffentlichen auf {% data variables.product.prodname_registry %} mit {% data variables.product.prodname_actions %}.'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -8,29 +8,34 @@ versions:
ghae: '*'
ghec: '*'
shortTitle: Quickstart
+ms.openlocfilehash: 887c4ee6c5e6b3e2c391c2d5754cfcb2787e4b86
+ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/24/2022
+ms.locfileid: '148181255'
---
-
{% data reusables.actions.enterprise-github-hosted-runners %}
-## Introduction
+## Einführung
-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 %}.
+In diesem Leitfaden erstellst du einen {% data variables.product.prodname_actions %}-Workflow, um deinen Code zu testen und dann in {% data variables.product.prodname_registry %} zu veröffentlichen.
-## Publishing your package
+## Veröffentlichen deines Pakets
-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.
+1. Erstelle ein neues Repository für {% data variables.product.prodname_dotcom %}, indem du `.gitignore` für Node hinzufügst. Weitere Informationen findest du unter [Erstellen eines neuen Repositorys](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository).
+2. Klonen Sie das Repository auf Ihren lokalen Computer.
```shell
$ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
$ cd YOUR-REPOSITORY
```
-3. Create an `index.js` file and add a basic alert to say "Hello world!"
+3. Erstelle eine `index.js` Datei, und füge eine einfache Benachrichtigung hinzu, um „Hallo Welt!“ zu sagen.
{% raw %}
```javascript{:copy}
console.log("Hello, World!");
```
{% endraw %}
-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.
+4. Initialisiere ein npm-Paket mit `npm init`. Gib dein Paket im Paketinitialisierungs-Assistenten mit dem Namen _`@YOUR-USERNAME/YOUR-REPOSITORY`_ ein, und lege das Testskript auf `exit 0` fest. Dadurch wird eine `package.json`-Datei mit Informationen zu deinem Paket generiert.
{% raw %}
```shell
$ npm init
@@ -41,15 +46,15 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
...
```
{% endraw %}
-5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
+5. Führe `npm install` aus, um die `package-lock.json`-Datei zu generieren. Committe deine Änderungen und pushe sie dann in {% 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. 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 %}.
+6. Erstelle das Verzeichnis `.github/workflows`. Erstelle in diesem Verzeichnis eine Datei namens `release-package.yml`.
+7. Kopiere den folgenden YAML-Inhalt in die `release-package.yml`-Datei{% ifversion ghes or ghae %}, wobei du `YOUR-HOSTNAME` durch den Namen deines Unternehmens{% endif %} ersetzt.
```yaml{:copy}
name: Node.js Package
@@ -85,22 +90,20 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
env:
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
```
-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 %}
+8. Teile NPM mit, in welchem Bereich und welcher Registrierung Pakete mit einer der folgenden Methoden veröffentlicht werden sollen:
+ - Füge eine NPM-Konfigurationsdatei für das Repository hinzu, indem du eine `.npmrc`-Datei im Stammverzeichnis mit folgendem Inhalt erstellst: {% raw %}
```shell
@YOUR-USERNAME:registry=https://npm.pkg.github.com
```
{% endraw %}
- - Edit the `package.json` file and specify the `publishConfig` key:
- {% raw %}
+ - Bearbeite die `package.json`-Datei, und gib den `publishConfig`-Schlüssel an: {% raw %}
```shell
"publishConfig": {
"@YOUR-USERNAME:registry": "https://npm.pkg.github.com"
}
```
{% endraw %}
-9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
+9. Committe deine Änderungen und pushe sie in {% 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.
@@ -108,28 +111,26 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
$ git commit -m "workflow to publish package"
$ git push
```
-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 %}.
+10. Der von dir erstellte Workflow wird ausgeführt, wenn ein neues Release im Repository erstellt wird. Wenn die Tests bestanden werden, wird das Paket in {% data variables.product.prodname_registry %}veröffentlicht.
- 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)."
+ Um dies zu testen, navigiere zur Registerkarte **Code** in deinem Repository, und erstelle ein neues Release. Weitere Informationen findest du unter „[Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)“.
-## Viewing your published package
+## Anzeigen eines veröffentlichten Pakets
-You can view all of the packages you have published.
+Du kannst alle Pakete anzeigen, die du veröffentlicht hast.
-{% 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
+## Installieren eines veröffentlichten Pakets
-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)."
+Nachdem du das Paket veröffentlicht hast, solltest du es als projektübergreifende Abhängigkeit verwenden. Weitere Informationen findest du unter „[Arbeiten mit der npm-Registrierung](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)“.
-## Next steps
+## Nächste Schritte
-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.
+Der Basisworkflow, den du gerade hinzugefügt hast, wird jedes Mal ausgeführt, wenn ein neues Release in deinem Repository erstellt wird. Dies ist jedoch längst nicht alles, was du mit {% data variables.product.prodname_registry %} tun kannst. Du kannst dein Paket mit einem einzelnen Workflow in mehreren Registrierungen veröffentlichen, den Workflow auslösen, um ihn bei verschiedenen Ereignissen wie einer zusammengeführten Pullanforderung auszuführen, Container verwalten usw.
-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 %}:
+Durch Kombination von {% data variables.product.prodname_registry %} und {% data variables.product.prodname_actions %} kannst du nahezu jeden Aspekt deiner Anwendungsentwicklungsprozesse automatisieren. Wollen Sie loslegen? Hier sind einige hilfreiche Ressourcen zum Ausführen der nächsten Schritte mit {% data variables.product.prodname_registry %} und {% data variables.product.prodname_actions %}:
-- "[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
+- „[Informationen zu {% data variables.product.prodname_registry %}](/packages/learn-github-packages)“ – ausführliches Tutorial zu GitHub Packages
+- „[Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)“ – ausführliches Tutorial zu GitHub Actions
+- „[Arbeiten mit einer {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)“ – spezifische Anwendungsfälle und Beispiele
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index e1c586dd1f..38dd9f350f 100644
--- a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -15,12 +15,12 @@ versions:
topics:
- Pull requests
shortTitle: Deleted or changes visibility
-ms.openlocfilehash: d52215a7406edc84bc71022517f848faa9e48600
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 95296f33d9163cd1171481386efd0a2351095c39
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
ms.translationtype: HT
ms.contentlocale: de-DE
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '147886798'
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191361'
---
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
@@ -32,7 +32,7 @@ Wenn du ein privates Repository löschst, werden alle zugehörigen privaten Fork
## Öffentliches Repository löschen
-Wenn du ein öffentliches Repository löschst, wird einer der vorhandenen öffentlichen Forks als das neue übergeordnete Repository ausgewählt. Alle anderen Repositorys werden von diesem neuen übergeordneten Element abgezweigt, und nachfolgende Pull Requests werden an dieses neue übergeordnete Element gesendet.
+Wenn du ein öffentliches Repository löschst, wird einer der vorhandenen öffentlichen Forks als neues Upstream-Repository ausgewählt. Alle anderen Repositorys werden von diesem neuen Upstream-Repository geforkt und nachfolgende Pull Requests gehen an dieses neue Upstream-Repository.
{% endif %}
@@ -44,9 +44,9 @@ Wenn du ein öffentliches Repository löschst, wird einer der vorhandenen öffen
## Öffentliches Repository in ein privates Repository ändern
-Wenn ein öffentliches Repository auf privat festgelegt wird, werden die zugehörigen öffentlichen Forks in ein neues Netzwerk abgespalten. Wie beim Löschen eines öffentlichen Repositorys wird einer der vorhandenen öffentliches Forks als das neue übergeordnete Repository ausgewählt, und alle anderen Repositorys werden von diesem neuen übergeordneten Element abgezweigt. Nachfolgende Pull Requests werden an dieses neue übergeordnete Element gesendet.
+Wenn ein öffentliches Repository auf privat festgelegt wird, werden die zugehörigen öffentlichen Forks in ein neues Netzwerk abgespalten. Wie beim Löschen eines öffentlichen Repositorys wird einer der vorhandenen öffentlichen Forks als neues Upstream-Repository ausgewählt und alle anderen Repositorys werden von diesem neuen Upstream-Repository geforkt. Nachfolgende Pull Requests werden an dieses neue Upstream-Repository übermittelt.
-Die Forks eines öffentlichen Repositorys bleiben demnach in ihrem eigenen separaten Repository-Netzwerk öffentlich, selbst nachdem das übergeordnete Repository auf privat eingestellt wurde. Dadurch können Fork-Inhaber ohne Unterbrechung weiterhin arbeiten und zusammenarbeiten. Wenn öffentliche Forks nicht auf diese Weise in ein separates Netzwerk verschoben wurden, benötigen die Inhaber dieser Forks die entsprechenden [Zugriffsberechtigungen](/articles/access-permissions-on-github), um Änderungen vom (inzwischen privaten) übergeordneten Repository abzurufen - auch wenn sie zuvor diese Berechtigungen nicht benötigt haben.
+Anders ausgedrückt: Die Forks eines öffentlichen Repositorys bleiben in ihrem eigenen separaten Repositorynetzwerk öffentlich, auch wenn das Upstream-Repository als privat festgelegt wird. Dadurch können Fork-Inhaber ohne Unterbrechung weiterhin arbeiten und zusammenarbeiten. Wenn öffentliche Forks nicht auf diese Weise in ein separates Netzwerk verschoben wurden, benötigen die Inhaber dieser Forks die entsprechenden [Zugriffsberechtigungen](/articles/access-permissions-on-github), um Änderungen vom (inzwischen privaten) Upstream-Repository abzurufen – auch wenn sie diese Berechtigungen zuvor nicht benötigt wurden.
{% ifversion ghes or ghae %} Wenn für ein öffentliches Repository der anonyme Git-Lesezugriff aktiviert ist und das Repository auf privat festgelegt wird, verlieren alle Forks des Repositorys den anonymen Git-Lesezugriff und verwenden wieder die standardmäßig deaktivierte Einstellung. Wenn ein geforktes Repository als öffentlich festgelegt wird, kann der anonyme Git-Lesezugriff durch die Repository-Administratoren wieder aktiviert werden. Weitere Informationen findest du unter [Aktivieren des anonymen Git-Lesezugriffs für ein Repository](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository).
{% endif %}
@@ -57,7 +57,7 @@ Wenn ein öffentliches Repository auf privat festgelegt und anschließend gelös
## Privates Repository in ein öffentliches Repository ändern
-Wenn ein privates Repository auf öffentlich festgelegt wird, werden alle privaten Forks in eigenständige private Repositorys umgewandelt und werden zum übergeordneten Element ihres eigenen neuen Repository-Netzwerks. Private Forks werden niemals automatisch auf öffentlich festgelegt, da sie sensible Commits enthalten können, die nicht veröffentlicht werden sollten.
+Wenn ein privates Repository als öffentlich festgelegt wird, werden alle privaten Forks in eigenständige private Repositorys umgewandelt und werden zum Upstream-Repository ihres eigenen neuen Repository-Netzwerks. Private Forks werden niemals automatisch auf öffentlich festgelegt, da sie sensible Commits enthalten können, die nicht veröffentlicht werden sollten.
### Öffentliches Repository löschen
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
index a66e99ee9a..25fe51f8d6 100644
--- a/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository from a template
-intro: You can generate a new repository with the same directory structure and files as an existing repository.
+title: Ein Repository anhand einer Vorlage erstellen
+intro: 'Du kannst ein neues Repository mit derselben Verzeichnisstruktur und denselben Dateien erstellen, die ein vorhandenes Repository aufweist.'
redirect_from:
- /articles/creating-a-repository-from-a-template
- /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template
@@ -13,45 +13,46 @@ versions:
topics:
- Repositories
shortTitle: Create from a template
+ms.openlocfilehash: 16d124431426e19cf95c768e8a4cdaa5f4da2e17
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160246'
---
-## About repository templates
+## Informationen zu Repositoryvorlagen
-Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)."
+Jeder, der über Leseberechtigung auf eine Repository-Vorlage verfügt, kann ein Repository anhand dieser Vorlage erstellen. Weitere Informationen findest du unter [Erstellen eines Vorlagenrepositorys](/articles/creating-a-template-repository).
{% tip %}
-**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+**Tipp:** Du kannst auch ein Repository aus einer Vorlage mithilfe der {% data variables.product.prodname_cli %} erstellen. Weitere Informationen findest du unter „[`gh repo create`](https://cli.github.com/manual/gh_repo_create)“ in der Dokumentation zur {% data variables.product.prodname_cli %}.
{% endtip %}
-You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
+Du kannst die Verzeichnisstruktur und die Dateien nur aus dem Standard-Branch des Vorlagen-Repositorys einbinden oder alle Branches einbinden. Aus einer Vorlage erstellte Branches weisen abweichende Verläufe auf. Das bedeutet, dass du keine Pull Requests erstellen oder Branches zusammenführen kannst.
-Creating a repository from a template is similar to forking a repository, but there are important differences:
-- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit.
-- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph.
-- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly.
+Das Erstellen eines Repositorys anhand einer Vorlage ähnelt dem Vorgang zum Forken eines Repositorys, aber es gibt entscheidende Unterschiede:
+- Ein neuer Fork enthält den gesamten Commit-Verlauf des übergeordneten Repositorys, wohingegen ein Repository, das anhand einer Vorlage erstellt wurde, mit einem einzigen Commit beginnt.
+- Commits für einen Fork erscheinen nicht im Beteiligungsdiagramm, während Commits für ein Repository, das anhand einer Vorlage erstellt wurde, im Beteiligungsdiagramm angezeigt werden.
+- Ein Fork kann eine temporäre Möglichkeit sein, um Code zu einem vorhandenen Projekt beizutragen. Beim Erstellen eines Repositorys anhand einer Vorlage wird dagegen schnell ein neues Projekt gestartet.
-For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
+Weitere Informationen zu Forks findest du unter [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks).
-## Creating a repository from a template
+## Ein Repository anhand einer Vorlage erstellen
{% data reusables.repositories.navigate-to-repo %}
-1. Above the file list, click **Use this template**.
+1. Klicke über der Dateiliste auf **Diese Vorlage verwenden**.
{% ifversion fpt or ghec %}
-1. Select **Create a new repository**.
+1. Wähle **Neues Repository erstellen** aus.
- 
+ 
{% note %}
- **Note:** Alternatively, you can open the template in a codespace and publish your work to a new repository later. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+ **Hinweis:** Alternativ kannst du die Vorlage in einem Codespace öffnen und deine Arbeit später in einem neuen Repository veröffentlichen. Weitere Informationen findest du unter [Erstellen eines Codespace mithilfe einer Vorlage](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template).
- {% endnote %}
-{% endif %}
-{% data reusables.repositories.owner-drop-down %}
-{% data reusables.repositories.repo-name %}
-{% data reusables.repositories.choose-repo-visibility %}
-1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
- 
-{% data reusables.repositories.select-marketplace-apps %}
-8. Click **Create repository from template**.
+ {% endnote %} {% endif %} {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %}
+1. Um optional die Verzeichnisstruktur und die Dateien aller Branches aus dieser Vorlage und nicht nur aus dem Standardbranch einzuschließen, wählst du **Alle Branches einschließen** aus.
+  {% data reusables.repositories.select-marketplace-apps %}
+8. Klicke auf **Create repository from template** (Repository aus Vorlage erstellen).
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
index 151756761d..dd92510dd2 100644
--- a/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
@@ -1,6 +1,6 @@
---
-title: Automatically generated release notes
-intro: You can automatically generate release notes for your GitHub releases
+title: Automatisch generierte Versionshinweise
+intro: Du kannst Versionshinweise für deine GitHub-Versionen automatisch generieren.
permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release.
versions:
fpt: '*'
@@ -13,71 +13,63 @@ shortTitle: Automated release notes
communityRedirect:
name: Provide GitHub Feedback
href: 'https://github.com/orgs/community/discussions/categories/general'
+ms.openlocfilehash: aee951e6f57492240b5baf8870578409945aefdc
+ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/29/2022
+ms.locfileid: '148185194'
---
+## Informationen zu automatisch generierten Versionshinweisen
-## About automatically generated release notes
+Automatisch generierte Versionshinweise bieten eine automatisierte Alternative zum manuellen Schreiben von Versionshinweisen für deine {% data variables.product.prodname_dotcom %}-Releases. Mit automatisch generierten Versionshinweisen kannst du schnell einen Überblick über den Inhalt einer Version erstellen. Automatisch generierte Versionshinweise umfassen eine Liste der zusammengeführten Pull Requests, eine Liste der Mitwirkenden an der Version und einen Link zu einem vollständigen Änderungsprotokoll.
-Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. Automatically generated release notes include a list of merged pull requests, a list of contributors to the release, and a link to a full changelog.
+Du kannst auch deine automatisierten Versionshinweise anpassen, indem du Beschriftungen verwendest, um benutzerdefinierte Kategorien zu erstellen, um Pull Requests zu strukturieren, die du einschließen möchtest, und um bestimmte Bezeichnungen und Benutzer*innen aus der Ausgabe auszuschließen.
-You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
+## Erstellen von automatisch generierten Versionshinweisen für ein neues Release
-## Creating automatically generated release notes for a new release
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
- 
-4. {% ifversion fpt or ghec %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag.
- {% ifversion fpt or ghec %}
- 
-5. If you are creating a new tag, click **Create new tag**.
-
- {% else %}
- 
-{% endif %}
-6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
- {% ifversion fpt or ghec %}
- {% else %}
- {% endif %}
-{%- data reusables.releases.previous-release-tag %}
-7. To the top right of the description text box, click {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% ifversion previous-release-tag %}
- {% else %}
- {% endif %}
-8. Check the generated notes to ensure they include all (and only) the information you want to include.
-9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
- 
-10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
- 
-{%- ifversion fpt or ghec %}
-11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
- 
-{%- endif %}
-12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+3. Klicke auf **Neues Release entwerfen**.
+ 
+4. {% ifversion fpt or ghec %}Klicke auf **Tag auswählen** und gib{% else %}Geben{% endif %} eine Versionsnummer für dein Release ein. Alternativ kannst du ein vorhandenes Tag auswählen.
+ {% ifversion fpt or ghec %} 
+5. Wenn du ein neues Tag erstellst, klicke auf **Neues Tag erstellen**.
+ {% else %}  {% endif %}
+6. Wenn du ein neues Tag erstellt hast, verwende das Dropdownmenü, um den Branch auszuwählen, der das zu veröffentlichende Projekt enthält.
+ {% ifversion fpt or ghec %} {% else %} {% endif %} {%- data reusables.releases.previous-release-tag %}
+7. Klicke rechts neben dem Beschreibungstextfeld auf {% ifversion previous-release-tag %}**Versionshinweise generieren**{% else %}**Versionshinweise automatisch generieren**{% endif %}.{% ifversion previous-release-tag %} {% else %} {% endif %}
+8. Überprüfe die generierten Notizen, um sicherzustellen, dass sie alle (und nur) die Informationen enthalten, die du einschließen möchtest.
+9. Um optional binäre Dateien wie kompilierte Programme in deinen Release einzubinden, ziehe die Dateien mit Drag-and-Drop herüber oder wähle die Dateien manuell im Feld für Binärdateien.
+ 
+10. Um Benutzer*innen darüber zu informieren, dass das Release nicht produktionsbereit und möglicherweise instabil ist, wähle **Dies ist eine Vorabversion** aus.
+  {%- ifversion fpt or ghec %}
+11. Wähle optional **Diskussion für diesen Release erstellen** aus, und wähle dann das Dropdownmenü **Kategorie** aus. Dann klicke auf eine Kategorie für die Releasediskussion.
+  {%- endif %}
+12. Wenn du dein Release veröffentlichen möchtest, klicke auf **Release veröffentlichen**. Wenn du später an dem Release arbeiten möchtest, klicke auf **Entwurf speichern**.
+ 
-## Configuring automatically generated release notes
+## Konfigurieren von automatisch generierten Versionshinweisen
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory.
- 
-4. In the file, using the configuration options below, specify in YAML the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib `.github/release.yml` im Dateinamenfeld ein, um die Datei `release.yml` im Verzeichnis `.github` zu erstellen.
+ 
+4. Gib in der Datei mithilfe der nachstehenden Konfigurationsoptionen in YAML die Pull-Request-Bezeichnungen und Autoren an, die du aus diesem Release ausschließen möchtest. Du kannst auch neue Kategorien erstellen und die Pull-Request-Bezeichnungen auflisten, die in jede dieser Kategorien einbezogen werden sollen.
-### Configuration options
+### Konfigurationsoptionen
-| Parameter | Description |
+| Parameter | BESCHREIBUNG |
| :- | :- |
-| `changelog.exclude.labels` | A list of labels that exclude a pull request from appearing in release notes. |
-| `changelog.exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from release notes. |
-| `changelog.categories[*].title` | **Required.** The title of a category of changes in release notes. |
-| `changelog.categories[*].labels`| **Required.** Labels that qualify a pull request for this category. Use `*` as a catch-all for pull requests that didn't match any of the previous categories. |
-| `changelog.categories[*].exclude.labels` | A list of labels that exclude a pull request from appearing in this category. |
-| `changelog.categories[*].exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from this category. |
+| `changelog.exclude.labels` | Eine Liste von Bezeichnungen, die ausschließen, dass ein Pull Request in den Versionshinweisen angezeigt wird. |
+| `changelog.exclude.authors` | Eine Liste der Benutzer*innen- oder Bot-Anmeldehhandles, deren Pull Requests aus Versionshinweisen ausgeschlossen werden sollen. |
+| `changelog.categories[*].title` | **Erforderlich.** Der Titel einer Kategorie von Änderungen in Versionshinweisen. |
+| `changelog.categories[*].labels`| **Erforderlich.** Bezeichnungen, die einen Pull Request für diese Kategorie qualifizieren. Verwende `*` als Catch-All für Pull Requests, die keinen der vorherigen Kategorien entsprechen. |
+| `changelog.categories[*].exclude.labels` | Eine Liste der Bezeichnungen, die eine Pull Request ausschließen, die in dieser Kategorie angezeigt wird. |
+| `changelog.categories[*].exclude.authors` | Eine Liste der Benutzer*innen- oder Bot-Anmeldehhandles, deren Pull Requests aus dieser Kategorie ausgeschlossen werden sollen. |
-### Example configurations
+### Beispielkonfigurationen
-A configuration for a repository that labels semver releases
+Eine Konfiguration für ein Repository, das SemVer-Releases kennzeichnet
{% raw %}
```yaml{:copy}
@@ -104,7 +96,7 @@ changelog:
```
{% endraw %}
-A configuration for a repository that doesn't tag pull requests but where we want to separate out {% data variables.product.prodname_dependabot %} automated pull requests in release notes (`labels: '*'` is required to display a catchall category)
+Eine Konfiguration für ein Repository, das keine Pull Requests taggt, aber in der automatisierte {% data variables.product.prodname_dependabot %}-Pull Requests in Versionshinweisen getrennt werden sollen (`labels: '*'` ist erforderlich, um eine Catchall-Kategorie anzuzeigen)
{% raw %}
```yaml{:copy}
@@ -124,6 +116,6 @@ changelog:
```
{% endraw %}
-## Further reading
+## Weiterführende Themen
-- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)"
+- [Verwalten von Bezeichnungen](/issues/using-labels-and-milestones-to-track-work/managing-labels)
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
index 00cff5d2b7..b315e45a17 100644
--- a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
@@ -1,6 +1,6 @@
---
title: Zusammenhänge zwischen Repositorys verstehen
-intro: 'Die Verbindungen zwischen Repositorys kannst du besser verstehen, wenn du dir das Netzwerk und die vom Repository abhängigen Projekte und die Forks des Repositorys ansiehst.'
+intro: 'Verwende das Netzwerkdiagramm und die Liste der Forks, um ein Verständnis für Forknetzwerke zu erhalten.'
product: '{% data reusables.gated-features.repository-insights %}'
redirect_from:
- /articles/viewing-a-repository-s-network
@@ -22,16 +22,17 @@ versions:
topics:
- Repositories
shortTitle: Connections between repositories
-ms.openlocfilehash: f1b92a62d0acf9f31a16ce1b7c57850b87c1bf9c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 46cc440093c3ca8dc0952933847a6f04b0446661
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
ms.translationtype: HT
ms.contentlocale: de-DE
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147060066'
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191358'
---
## Netzwerk eines Repositorys anzeigen
-Das Netzwerkdiagramm zeigt den Branch-Verlauf des gesamten Repository-Netzwerks an, einschließlich der Branches des Root-Repositorys und der Branches der Forks, die netzwerkspezifische Commits enthalten.
+Das Netzwerkdiagramm zeigt den Branchverlauf für das gesamte Repositorynetzwerk an, einschließlich der Forkbranches. Dieses Diagramm umfasst eine Zeitleiste der letzten Commits und zeigt bis zu 100 der zuletzt gepushten Branches an. Die erste Zeile zeigt das Datum, die erste Spalte den Branchbesitzer. Verwende die Pfeiltasten oder andere Tastenkombinationen, um einfacher im Diagramm zu navigieren. Sie werden im Popupfenster „Verfügbare Tastenkombinationen“ unter dem Diagramm angegeben.
+
@@ -51,7 +52,7 @@ Das Netzwerkdiagramm zeigt den Branch-Verlauf des gesamten Repository-Netzwerks
Das Mitgliederdiagramm zeigt alle Forks eines Repositorys.
-Die Forks sind alphabetisch nach dem Benutzernamen der Person geordnet, die das Repository geforkt hat. Du kannst auf den Benutzernamen klicken, um zur {% data variables.product.product_name %}-Profilseite des Benutzers weitergeleitet zu werden, oder auf den Forknamen, um zum entsprechenden Fork des Repositorys weitergeleitet zu werden.
+Die Forks sind alphabetisch nach der Organisation oder dem Benutzernamen der Person angeordnet, die das Repository geforkt hat. Du kannst auf die Organisation oder den Benutzernamen klicken, um zur {% data variables.product.product_name %}-Profilseite der Organisation oder des Benutzers weitergeleitet zu werden, oder du kannst auf den Namen des Forks klicken, um zum spezifischen Fork des Repositorys weitergeleitet zu werden.
{% ifversion fpt or ghec %}
diff --git a/translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md
index ea88316e23..a2f8359387 100644
--- a/translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md
+++ b/translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -1,6 +1,6 @@
---
-title: Viewing a file
-intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
+title: Anzeigen einer Datei
+intro: 'Du kannst Rohdatendateiinhalte anzeigen oder die Änderungen an den einzelnen Zeilen einer Datei verfolgen und so feststellen, wie sich die Datei im Lauf der Zeit entwickelt hat.'
redirect_from:
- /articles/using-git-blame-to-trace-changes-in-a-file
- /articles/tracing-changes-in-a-file
@@ -16,48 +16,54 @@ versions:
topics:
- Repositories
shortTitle: View files and track file changes
+ms.openlocfilehash: 7d34e776cb1747ee749531e49abf6f0e3d052b3b
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179861'
---
-## Viewing or copying the raw file content
+## Anzeigen oder Kopieren des Rohdateiinhalts
-With the raw view, you can view or copy the raw content of a file without any styling.
+Mit der unformatierten Ansicht kannst du den rohen Inhalt einer Datei ohne Formatierung anzeigen oder kopieren.
{% data reusables.repositories.navigate-to-repo %}
-1. Click the file that you want to view.
-2. In the upper-right corner of the file view, click **Raw**.
-
-3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
+1. Klicke auf die Datei, die du anzeigen möchtest.
+2. Klicke in der oberen rechten Ecke der Dateiansicht auf **Rohformat**.
+
+3. Wenn du optional den Rohdateiinhalt kopieren möchtest, klicke in der oberen rechten Ecke der Dateiansicht auf **{% octicon "copy" aria-label="The copy icon" %}**.
-## Viewing the line-by-line revision history for a file
+## Anzeigen des zeilenweisen Revisionsverlaufs für eine Datei
-With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
+In der Blame-Ansicht kannst du den Revisionsverlauf einer vollständigen Datei Zeile für Zeile sehen oder durch klicken auf {% octicon "versions" aria-label="The prior blame icon" %} auch nur den Revisionsverlauf einer einzelnen Zeile anzeigen. Mit jedem Klick auf {% octicon "versions" aria-label="The prior blame icon" %} siehst du die vorangegangene Revisionsinformation zur betreffenden Zeile, einschließlich des Committers und des Commit-Zeitpunkts der Änderung.
-
+
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+In einer Datei oder einem Pull Request kannst du auch das {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}-Menü verwenden, um Git Blame für eine ausgewählte Zeile oder einen ausgewählten Zeilenbereich anzuzeigen.
-
+
{% tip %}
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+**Tipp:** In der Befehlszeile kannst du auch `git blame` verwenden, um den Revisionsverlauf von Zeilen innerhalb einer Datei anzuzeigen. Weitere Informationen findest du in der [`git blame`-Dokumentation von Git](https://git-scm.com/docs/git-blame).
{% endtip %}
{% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-
+2. Zum Öffnen klicke auf die Datei, deren Zeilenverlauf du anzeigen möchtest.
+3. Klicke in der oberen rechten Ecke der Dateiansicht auf **Blame**, um die Blame-Ansicht zu öffnen.
+
+4. Wenn du frühere Überarbeitungen einer bestimmten Zeile oder erneut die Blame-Ansicht anzeigen möchtest, klicke auf {% octicon "versions" aria-label="The prior blame icon" %}, bis du die gewünschten Änderungen gefunden hast.
+
{% ifversion blame-ignore-revs %}
-## Ignore commits in the blame view
+## Ignorieren von Commits in der Blame-Ansicht
-All revisions specified in the `.git-blame-ignore-revs` file, which must be in the root directory of your repository, are hidden from the blame view using Git's `git blame --ignore-revs-file` configuration setting. For more information, see [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) in the Git documentation.
+Alle Überarbeitungen, die in der `.git-blame-ignore-revs`-Datei angegeben sind, die sich im Stammverzeichnis deines Repositorys befinden muss, sind in der Blame-Ansicht mithilfe der Git-Konfigurationseinstellung `git blame --ignore-revs-file` ausgeblendet. Weitere Informationen findest du in der Git-Dokumentation unter [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt).
-1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`.
-2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:
+1. Erstelle im Stammverzeichnis deines Repositorys eine Datei mit dem Namen `.git-blame-ignore-revs`.
+2. Füge die Commithashes hinzu, die du aus der Blame-Ansicht dieser Datei ausschließen möchtest. Es wird empfohlen, die Datei wie folgt zu strukturieren, einschließlich der Kommentare:
```ini
# .git-blame-ignore-revs
@@ -67,19 +73,19 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t
69d029cec8337c616552756310748c4a507bd75a
```
-3. Commit and push the changes.
+3. Committe und pushe die Änderungen.
-Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden:
+Wenn du nun die Blame-Ansicht öffnest, werden die aufgelisteten Überarbeitungen darin nicht angezeigt. Es wird ein Banner **Überarbeitungen in .git-blame-ignore-revs werden ignoriert** angezeigt, das darauf hinweist, dass einige Commits möglicherweise ausgeblendet sind:
-
+
-This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well:
+Dies kann hilfreich sein, wenn einige Commits umfangreiche Änderungen an deinem Code vornehmen. Du kannst die Datei auch bei der lokalen Ausführung von `git blame` verwenden:
```shell
git blame --ignore-revs-file .git-blame-ignore-revs
```
-You can also configure your local git so it always ignores the revs in that file:
+Du kannst Git auch lokal so konfigurieren, dass Überarbeitungen in dieser Datei immer ignoriert werden:
```shell
git config blame.ignoreRevsFile .git-blame-ignore-revs
@@ -87,6 +93,6 @@ git config blame.ignoreRevsFile .git-blame-ignore-revs
{% endif %}
-## Bypassing `.git-blame-ignore-revs` in the blame view
+## Umgehen von `.git-blame-ignore-revs` in der Blame-Ansicht
-If the blame view for a file shows **Ignoring revisions in .git-blame-ignore-revs**, you can still bypass `.git-blame-ignore-revs` and see the normal blame view. In the URL, append a `~` to the SHA and the **Ignoring revisions in .git-blame-ignore-revs** will disappear.
+Wenn in der Blame-Ansicht für eine Datei **Überarbeitungen in .git-blame-ignore-revs werden ignoriert** angezeigt wird, kannst du `.git-blame-ignore-revs` umgehen und dennoch die normale Blame-Ansicht anzeigen. Füge in der URL `~` an den SHA an, und **Überarbeitungen in .git-blame-ignore-revs werden ignoriert** wird nicht mehr angezeigt.
diff --git a/translations/de-DE/content/rest/overview/libraries.md b/translations/de-DE/content/rest/overview/libraries.md
index ebaebda728..d59f0ceeec 100644
--- a/translations/de-DE/content/rest/overview/libraries.md
+++ b/translations/de-DE/content/rest/overview/libraries.md
@@ -11,12 +11,12 @@ versions:
ghec: '*'
topics:
- API
-ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c
-ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
+ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
ms.translationtype: HT
ms.contentlocale: de-DE
-ms.lasthandoff: 11/21/2022
-ms.locfileid: '148179736'
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148190061'
---
@@ -24,7 +24,6 @@ ms.locfileid: '148179736'
Verwende die offizielle Octokit-Bibliothek oder wähle eine der verfügbaren Drittanbieterbibliotheken aus.
-- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
@@ -131,6 +130,7 @@ Verwende die offizielle Octokit-Bibliothek oder wähle eine der verfügbaren Dri
|**github-flask**|[github-flask (offizielle Website)](http://github-flask.readthedocs.org)|
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
+|**octokit.py**|[khornberg/octokit.py](https://github.com/khornberg/octokit.py)|
### Ruby
diff --git a/translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
index 383bb81294..e53a389ec6 100644
--- a/translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
+++ b/translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -1,6 +1,6 @@
---
-title: Anzeigen und Aktualisieren von Supporttickets
-intro: 'Du kannst deine Supporttickets{% ifversion ghes or ghec %} anzeigen, mit Kollegen an Tickets zusammenarbeiten{% endif %} und dem {% data variables.contact.github_support %} über das {% data variables.contact.support_portal %} antworten.'
+title: Viewing and updating support tickets
+intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.'
shortTitle: Managing your tickets
versions:
fpt: '*'
@@ -8,62 +8,64 @@ versions:
ghes: '*'
topics:
- Support
-ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: de-DE
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147051980'
---
-## Informationen zur Ticketverwaltung
+
+## About ticket management
{% data reusables.support.zendesk-old-tickets %}
-Du kannst das [GitHub-Supportportal](https://support.github.com/) verwenden, um aktuelle und frühere Supporttickets anzuzeigen und dem {% data variables.contact.github_support %} zu antworten. Nach 120 Tagen werden aufgelöste Tickets archiviert{% ifversion ghec or ghes or ghae %}, und archivierte Tickets können nur für Unternehmenskonten angezeigt werden{% endif %}.
+You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}. After 120 days, resolved tickets are archived{% ifversion ghec or ghes or ghae %}, and archived tickets can only be viewed for enterprise accounts{% endif %}.
-{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+{% ifversion ghes or ghec %}
+{% data reusables.enterprise-accounts.support-entitlements %}
+{% endif %}
-## Anzeigen deiner letzten Supporttickets
+## Viewing your recent support tickets
{% data reusables.support.view-open-tickets %}
-1. Unter dem Textfeld kannst du den Kommentarverlauf lesen. Die letzte Antwort wird an oberster Stelle angezeigt.
-
+1. Under the text box, you can read the comment history. The most recent response is at the top.
+
+ 
+
+1. Optionally, to translate the ticket comment, click {% octicon "globe" aria-label="The globe icon" %} and choose your preferred language from the dropdown menu. You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish.
+
+ 
{% ifversion ghec or ghes or ghae %}
-## Anzeigen deiner archivierten Supporttickets
+## Viewing your archived support tickets
-Du kannst nur archivierte Tickets für ein Unternehmenskonto anzeigen.
+You can only view archived tickets for an enterprise account.
{% data reusables.support.navigate-to-my-tickets %}
-1. Wähle das Dropdownmenü **Meine Tickets** aus, und klicke auf den Namen des Unternehmenskontos.
+1. Select the **My Tickets** drop-down menu and click the name of the enterprise account.
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
- 
-1. Klicke in der Tabelle „Meine Tickets“ auf **Archivierte Tickets anzeigen**.
+ 
+1. Under the "My tickets" table, click **View archived tickets**.
{% endif %}
-## Aktualisieren von Supporttickets
+## Updating support tickets
{% data reusables.support.view-open-tickets %}
-1. Wenn das Problem behoben ist, kannst du optional unter dem Textfeld auf **Ticket schließen** klicken.
-
-1. Um dem GitHub-Support zu antworten und dem Ticket einen neuen Kommentar hinzuzufügen, gib deine Antwort in das Textfeld ein.
-
-1. Um dem Ticket deinen Kommentar hinzuzufügen, klicke auf **Kommentar**.
-
+1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
+
+1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
+
+1. To add your comment to the ticket, click **Comment**.
+
{% ifversion ghec or ghes %}
-## Zusammenarbeit an Supporttickets
+## Collaborating on support tickets
-Du kannst mit deinen Kollegen über das Supportportal an Supporttickets zusammenarbeiten. Besitzer, Abrechnungsmanager und andere Unternehmensmitglieder mit Supportberechtigungen können Tickets anzeigen, die sich auf ein Unternehmenskonto oder eine von einem Unternehmenskonto verwaltete Organisation beziehen. Weitere Informationen findest du unter [Verwalten von Supportberechtigungen für dein Unternehmen](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise).
+You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-Neben dem Anzeigen von Tickets kannst du auch Kommentare zu Supporttickets hinzufügen, wenn deine E-Mail-Adresse in das Ticket kopiert wurde oder wenn die Person, die das Ticket geöffnet hat, eine E-Mail-Adresse mit einer Domäne verwendet hat, die für das Unternehmenskonto oder die von einem Unternehmenskonto verwaltete Organisation verifiziert wurde. Weitere Informationen zum Überprüfen einer Domäne findest du unter [Überprüfen oder Genehmigen einer Domäne für dein Unternehmen](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise) und [Überprüfen oder Genehmigen einer Domäne für deine Organisation](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization).
+In addition to viewing tickets, you can also add comments to support tickets if your email address is copied on the ticket or if the person who opened the ticket used an email address with a domain that is verified for the enterprise account or organization managed by an enterprise account. For more information about verifying a domain, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Verifying or approving a domain for your organization](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
{% endif %}
-## Weiterführende Themen
+## Further reading
-- [Informationen zum GitHub-Support](/support/learning-about-github-support/about-github-support)
+- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
diff --git a/translations/de-DE/content/support/learning-about-github-support/about-github-support.md b/translations/de-DE/content/support/learning-about-github-support/about-github-support.md
index f5d6525f05..be735ece17 100644
--- a/translations/de-DE/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/de-DE/content/support/learning-about-github-support/about-github-support.md
@@ -83,6 +83,10 @@ If you have any paid product or are a member of an organization with a paid prod
With {% data variables.product.product_name %}, you have access to support in English and Japanese.
{% endif %}
+{% ifversion fpt or ghec or ghes %}
+{% data reusables.support.support-ticket-translation-option %}
+{% endif %}
+
{% ifversion ghes or ghec %}
To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml b/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml
index 028b8750b6..2d4ef88879 100644
--- a/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml
@@ -29,4 +29,5 @@ sections:
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
- |
- GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
\ No newline at end of file
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml b/translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml
index fdb9b3ea7e..05de05ac2b 100644
--- a/translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml
@@ -1,27 +1,30 @@
date: '2022-08-30'
sections:
bugs:
- - Nach dem Freigeben eines Repositorys für den temporären Zugriff konnte ein Siteadministrator die Einstellungen für Sicherheitsprodukte im Repository nicht mehr verwalten.
- - Doppelte administrative SSH-Schlüssel konnten sowohl in der Verwaltungskonsole als auch in der Datei `/home/admin/.ssh/authorized_keys` vorkommen.
- - "Die Siteadministratorseite für einzelne Benutzer unter http(s)://HOSTNAME/stafftools/users/USERNAME/admin enthielt Funktionen, die nicht für GitHub Enterprise Server vorgesehen waren."
- - In einigen Fällen konnte die Ausführung von `ghe-cluster-config-apply` eine leere Konfiguration zu bestehenden Knoten in einem Cluster replizieren.
- - "In einigen Fällen wurden Konfigurationsläufe, die mit `ghe-config-apply` gestartet wurden, nicht abgeschlossen oder gaben den Fehler `Nicht übereinstimmende Containerzahl` zurück."
- - Nach dem Aktualisieren eines selbstsignierten TLS-Zertifikats auf einer GitHub Enterprise Server-Instanz wurden Benutzeroberflächenelemente auf einigen Seiten der Weboberfläche nicht angezeigt.
- - Die Siteadministratorleiste oben auf der Weboberfläche enthielt einen defekten Link zu SHA für die aktuell ausgeführte Version der Anwendung.
- - "In einigen Fällen konnten Hintergrundaufgaben aufgrund einer Bibliothek, die gleichzeitig verwendet wurde, obwohl sie nicht threadsicher war, zum Stillstand kommen."
- - "Warnungen aus der Geheimnisüberprüfung für GitHub Advanced Security-Kunden fehlten in der Webbenutzeroberfläche und der REST-API, wenn ein Siteadministrator nicht direkt auf GitHub Enterprise Server 3.4 upgradete. Die Warnungen sind nun sichtbar."
- - "Wenn ein Benutzer ein Repository in eine Organisation forkte, wurde eine lange Liste von Organisationen nicht korrekt gerendert."
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
+ - When a user forked a repository into an organization, a long list of organizations would not render properly.
changes:
- - "Die Generierung von Supportbundles wird durch die parallelisierte Protokollbereinigung beschleunigt. Weitere Informationen zu Supportbundles findest du unter [Daten für den GitHub-Support bereitstellen](/support/contacting-github-support/providing-data-to-github-support)."
- - "APIs, die die Route `organization` oder `org` enthalten, akzeptieren jetzt entweder das Platzhalterfeld oder die ID der Organisation. Zuvor akzeptierten die APIs nur Platzhalterfelder, was dazu führte, dass kein Zugriff auf `Link`-Kopfzeilen für GitHub Advanced Security-Endpunkte möglich war. Weitere Informationen findest du unter [Organisationen](https://docs.github.com/rest/orgs/orgs) in der REST-API-Dokumentation."
- - "Das Unternehmensüberwachungsprotokoll enthält jetzt mehr benutzergenerierte Ereignisse, wie z. B. `project.create`. Die REST-API liefert auch zusätzliche benutzergenerierte Ereignisse, wie z. B. `repo.create`. Weitere Informationen findest du unter [Zugreifen auf das Überwachungsprotokoll für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise) und [Verwenden der Überwachungsprotokoll-API für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
- - "In einigen Fällen konnten Cachereplikate einige Git-Operationen für kürzlich aktualisierte Repositorys ablehnen. Weitere Informationen zum Zwischenspeichern von Repositorys findest du unter [Informationen zum Zwischenspeichern von Repositorys](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
known_issues:
- - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
- - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
- - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
- - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
- - "Wenn die Option zum Durchsuchen von GitHub.com mit GitHub Connect aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
- - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
- - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
- - "Actions-Dienste müssen nach der Wiederherstellung einer Appliance aus einer Sicherung, die auf einem anderen Host erstellt wurde, neu gestartet werden."
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml
index 3ae7af2fe6..6e638df146 100644
--- a/translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml
@@ -1,33 +1,38 @@
date: '2022-08-30'
sections:
bugs:
- - Nach dem Freigeben eines Repositorys für den temporären Zugriff konnte ein Siteadministrator die Einstellungen für Sicherheitsprodukte im Repository nicht mehr verwalten.
- - Doppelte administrative SSH-Schlüssel konnten sowohl in der Verwaltungskonsole als auch in der Datei `/home/admin/.ssh/authorized_keys` vorkommen.
- - "Die Siteadministratorseite für einzelne Benutzer unter http(s)://HOSTNAME/stafftools/users/USERNAME/admin enthielt Funktionen, die nicht für GitHub Enterprise Server vorgesehen waren."
- - In einigen Fällen konnte die Ausführung von `ghe-cluster-config-apply` eine leere Konfiguration zu bestehenden Knoten in einem Cluster replizieren.
- - "In einigen Fällen wurden Konfigurationsläufe, die mit `ghe-config-apply` gestartet wurden, nicht abgeschlossen oder gaben den Fehler `Nicht übereinstimmende Containerzahl` zurück."
- - Nach dem Aktualisieren eines selbstsignierten TLS-Zertifikats auf einer GitHub Enterprise Server-Instanz wurden Benutzeroberflächenelemente auf einigen Seiten der Weboberfläche nicht angezeigt.
- - "In einigen Fällen konnten Hintergrundaufgaben aufgrund einer Bibliothek, die gleichzeitig verwendet wurde, obwohl sie nicht threadsicher war, zum Stillstand kommen."
- - Die Siteadministratorleiste oben auf der Weboberfläche enthielt einen defekten Link zu SHA für die aktuell ausgeführte Version der Anwendung.
- - "Die Besitzer der Organisation konnten nicht festlegen, welche Zugriffsrechte für die Erstellung von Diskussionen erforderlich sind."
- - Benutzer von Diskussionen wurden fälschlicherweise auf die Communityrichtlinien für GitHub.com verwiesen.
- - "In einigen Fällen wurden die Benutzer fälschlicherweise angewiesen, vor dem Erstellen einer Diskussion ihre E-Mail-Adresse zu bestätigen."
- - "Warnungen aus der Geheimnisüberprüfung für GitHub Advanced Security-Kunden fehlten in der Webbenutzeroberfläche und der REST-API, wenn ein Siteadministrator nicht direkt auf GitHub Enterprise Server 3.4 upgradete. Die Warnungen sind nun sichtbar."
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - Organization owners were unable to set the level of access required to create discussions.
+ - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
+ - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
changes:
- - "Die Generierung von Supportbundles wird durch die parallelisierte Protokollbereinigung beschleunigt. Weitere Informationen zu Supportbundles findest du unter [Daten für den GitHub-Support bereitstellen](/support/contacting-github-support/providing-data-to-github-support)."
- - "APIs, die die Route `organization` oder `org` enthalten, akzeptieren jetzt entweder das Platzhalterfeld oder die ID der Organisation. Zuvor akzeptierten die APIs nur Platzhalterfelder, was dazu führte, dass kein Zugriff auf `Link`-Kopfzeilen für GitHub Advanced Security-Endpunkte möglich war. Weitere Informationen findest du unter [Organisationen](https://docs.github.com/rest/orgs/orgs) in der REST-API-Dokumentation."
- - "Das Unternehmensüberwachungsprotokoll enthält jetzt mehr benutzergenerierte Ereignisse, wie z. B. `project.create`. Die REST-API liefert auch zusätzliche benutzergenerierte Ereignisse, wie z. B. `repo.create`. Weitere Informationen findest du unter [Zugreifen auf das Überwachungsprotokoll für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise) und [Verwenden der Überwachungsprotokoll-API für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
- - "In einigen Fällen konnten Cachereplikate einige Git-Operationen für kürzlich aktualisierte Repositorys ablehnen. Weitere Informationen zum Zwischenspeichern von Repositorys findest du unter [Informationen zum Zwischenspeichern von Repositorys](/admin/enterprise-management/caching-repositories/about-repository-caching)."
- - "Du kannst jetzt konfigurieren, dass das globale Ankündigungsbanner über die REST-API geschlossen werden kann. Weitere Informationen findest du unter [Anpassen von Benutzernachrichten für dein Unternehmen](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+ - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
known_issues:
- - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
- - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
- - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
- - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
- - "Wenn die Option zum Durchsuchen von GitHub.com mit GitHub Connect aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
- - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
- - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
- - "Actions-Dienste müssen nach der Wiederherstellung einer Instanz aus einer Sicherung, die auf einem anderen Host erstellt wurde, neu gestartet werden."
- - "Wenn du in den Einstellungen eines Repositorys die Option aktivierst, die Benutzern mit Lesezugriff das Erstellen von Diskussionen gestattet, wird diese Funktionalität nicht aktiviert."
- - In einigen Fällen können Benutzer vorhandene Issues nicht in Diskussionen umwandeln.
- - "Benutzerdefinierte Muster für die Geheimnisüberprüfung verwenden `.*` als Endtrennzeichen, insbesondere im Feld „Nach Geheimnis“. Dieses Trennzeichen verursacht Inkonsistenzen in repositoryübergreifenden Überprüfungen auf Geheimnisse, und du stellst möglicherweise Lücken im Repositoryverlauf fest, in denen keine Überprüfungen abgeschlossen wurden. Auch inkrementelle Überprüfungen werden möglicherweise beeinträchtigt. Um Probleme mit Überprüfungen zu verhindern, ändere das Ende des Musters, indem du das Trennzeichen `.*` entfernst."
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+ - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+ - In some cases, users cannot convert existing issues to discussions.
+ - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+ - |
+ After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 8d29f30fc5..1193172cdd 100644
--- a/translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,18 +1,10 @@
----
-ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: de-DE
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145103711"
----
-Mit der Bedingung `jobs..if` kannst du dafür sorgen, dass ein Schritt nur ausgeführt wird, wenn eine Bedingung erfüllt ist. Du kannst eine Bedingung mit jedem unterstützten Kontext und Ausdruck erstellen.
+You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
-{% data reusables.actions.expression-syntax-if %} Weitere Informationen findest du unter [Ausdrücke](/actions/learn-github-actions/expressions).
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
-### Beispiel: Ausführen eines Auftrags nur für bestimmte Repositorys
+### Example: Only run job for specific repository
-In diesem Beispiel wird `if` verwendet, um zu steuern, wann der Auftrag `production-deploy` ausgeführt werden kann. Er wird nur ausgeführt, wenn das Repository `octo-repo-prod` heißt und sich innerhalb der Organisation `octo-org` befindet. Andernfalls wird der Auftrag als _übersprungen_ markiert.
+This example uses `if` to control when the `production-deploy` job can run. It will only run if the repository is named `octo-repo-prod` and is within the `octo-org` organization. Otherwise, the job will be marked as _skipped_.
```yaml{:copy}
name: example-workflow
diff --git a/translations/de-DE/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/de-DE/data/reusables/actions/reusable-workflows-ghes-beta.md
deleted file mode 100644
index 6fb3ef2e4f..0000000000
--- a/translations/de-DE/data/reusables/actions/reusable-workflows-ghes-beta.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% ifversion ghes = 3.4 %}
-
-{% note %}
-
-**Note**: Reusable workflows are currently in beta and subject to change.
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md
index 80878d1726..24b839f410 100644
--- a/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md
+++ b/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
- Starring a repository
- Deleting a repository
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
+- Joining an organization
+
+{% ifversion ghes %}
+A user will also be considered active if their account has been updated by LDAP.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md
index 558a3b591a..4276f63cf0 100644
--- a/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md
@@ -1 +1,9 @@
-{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
+---
+ms.openlocfilehash: 484a4230527deebe6f4aeb24ceabdf95eb75b492
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/03/2022
+ms.locfileid: "148191330"
+---
+{% data variables.enterprise.prodname_managed_users_caps %} können keine Repositorys von außerhalb des Unternehmens forken. Gemäß der Unternehmensrichtlinie können {% data variables.enterprise.prodname_managed_users_caps %} private oder interne Repositorys, die sich im Besitz von Organisationen im Unternehmen befinden, in ihren Benutzerkonto-Namespace oder in andere Organisationen im Besitz des Unternehmens forken.
diff --git a/translations/de-DE/data/reusables/repositories/fork-definition-long.md b/translations/de-DE/data/reusables/repositories/fork-definition-long.md
new file mode 100644
index 0000000000..91f9e6dbad
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/fork-definition-long.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eb538c8746bf9d5ec4cd0e422e50ccc032309812
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 12/03/2022
+ms.locfileid: "148191364"
+---
+Ein Fork ist ein neues Repository, das denselben Code und dieselben Sichtbarkeitseinstellungen verwendet wie das ursprüngliche „Upstream-Repository“. Forks werden oft verwendet, um Ideen oder Änderungen zu überprüfen, bevor sie für das Upstream-Repository vorgeschlagen werden, z. B. in Open-Source-Projekten oder wenn ein Benutzer keinen Schreibzugriff auf das Upstream-Repository hat.
diff --git a/translations/de-DE/data/ui.yml b/translations/de-DE/data/ui.yml
index 1e8377dd72..29dec0fbef 100644
--- a/translations/de-DE/data/ui.yml
+++ b/translations/de-DE/data/ui.yml
@@ -127,7 +127,7 @@ products:
rest:
banner:
api_versioned: The REST API is now versioned.
- api_version_info: For more information, see "About API versioning".
+ api_version_info: For more information, see "About API versioning."
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "About versions of GitHub Docs".
versioning:
about_versions: About REST API versions
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
index 382e81006b..f54adf093a 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
@@ -94,7 +94,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
shell: bash
```
{% endraw %}
- This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+ This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, adds the action's path to the runner system path (to locate the `goodbye.sh` script during execution), and runs the `goodbye.sh` script.
For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
index 5a1ea071a9..8dcb762313 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
@@ -271,3 +271,10 @@ jobs:
From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+
+## Template repositories for creating JavaScript actions
+
+{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
+
+* [`javascript-action` template repository](https://github.com/actions/javascript-action)
+* [`typescript-action` template repository](https://github.com/actions/typescript-action)
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index 30c0ee6762..0d240ae768 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -283,6 +283,12 @@ After this setting is applied, the JWT will contain the updated `iss` value. In
To help improve security, compliance, and standardization, you can customize the standard claims to suit your required access conditions. If your cloud provider supports conditions on subject claims, you can create a condition that checks whether the `sub` value matches the path of the reusable workflow, such as `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`. The exact format will vary depending on your cloud provider's OIDC configuration. To configure the matching condition on {% data variables.product.prodname_dotcom %}, you can can use the REST API to require that the `sub` claim must always include a specific custom claim, such as `job_workflow_ref`. You can use the [OIDC REST API](/rest/actions/oidc) to apply a customization template for the OIDC subject claim; for example, you can require that the `sub` claim within the OIDC token must always include a specific custom claim, such as `job_workflow_ref`.
+{% note %}
+
+**Note**: When the organization template is applied, it will not affect any workflows in existing repositories that already use OIDC. For existing repositories, as well as any new repositories that are created after the template has been applied, the repository owner will need to opt-in to receive this configuration, or alternatively could apply a different configuration specific to the repo. For more information, see "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)."
+
+{% endnote %}
+
Customizing the claims results in a new format for the entire `sub` claim, which replaces the default predefined `sub` format in the token described in "[Example subject claims](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims)."
The following example templates demonstrate various ways to customize the subject claim. To configure these settings on {% data variables.product.prodname_dotcom %}, admins use the REST API to specify a list of claims that must be included in the subject (`sub`) claim.
@@ -291,12 +297,6 @@ The following example templates demonstrate various ways to customize the subjec
To customize your subject claims, you should first create a matching condition in your cloud provider's OIDC configuration, before customizing the configuration using the REST API. Once the configuration is completed, each time a new job runs, the OIDC token generated during that job will follow the new customization template. If the matching condition doesn't exist in the cloud provider's OIDC configuration before the job runs, the generated token might not be accepted by the cloud provider, since the cloud conditions may not be synchronized.
-{% note %}
-
-**Note**: When the organization template is applied, it will not affect any action workflows in existing repositories that already use OIDC. For existing repositories, as well as any new repositories that are created after the template has been applied, the repository owner will need to opt-in to receive this configuration, or alternatively could apply a different configuration specific to the repo. For more information, see "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)."
-
-{% endnote %}
-
#### Example: Allowing repository based on visibility and owner
This example template allows the `sub` claim to have a new format, using `repository_owner` and `repository_visibility`:
@@ -431,7 +431,9 @@ In your cloud provider's OIDC configuration, configure the `sub` condition to re
#### Using the default subject claims
-For repositories that can receive a subject claim policy from their organization, the repository owner can later choose to opt-out and instead use the default `sub` claim format. To configure this, the repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
+For repositories that can receive a subject claim policy from their organization, the repository owner can later choose to opt-out and instead use the default `sub` claim format. This means that the repository will not use the organization's customized template.
+
+To configure the repository to use the default `sub` claim format, a repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
```json
{
@@ -439,6 +441,18 @@ For repositories that can receive a subject claim policy from their organization
}
```
+#### Example: Configuring a repository to use an organization template
+
+A repository administrator can configure their repository to use the template created by the administrator of their organisation.
+
+To configure the repository to use the organization's template, a repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
+
+```json
+{
+ "use_default": false
+}
+```
+
{% endif %}
## Updating your workflows for OIDC
diff --git a/translations/es-ES/content/actions/learn-github-actions/contexts.md b/translations/es-ES/content/actions/learn-github-actions/contexts.md
index bdf5bb0bfb..9217298a2a 100644
--- a/translations/es-ES/content/actions/learn-github-actions/contexts.md
+++ b/translations/es-ES/content/actions/learn-github-actions/contexts.md
@@ -811,7 +811,7 @@ The `inputs` context contains input properties passed to an action{% ifversion a
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
| Property name | Type | Description |
|---------------|------|-------------|
diff --git a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0d316eca1f..397d51b308 100644
--- a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -88,7 +88,7 @@ In addition to the usage limits, you must ensure that you use {% data variables.
{% ifversion fpt or ghes > 3.3 or ghec %}
## Billing for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
diff --git a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
index 2adee6a3f4..1cc0d2d002 100644
--- a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
---
{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
## Overview
diff --git a/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md b/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
index 8e4adb430f..837875fe9e 100644
--- a/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
@@ -123,7 +123,7 @@ You can use activity types and filters to further control when your workflow wil
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
diff --git a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 4969f6b53e..e6e11c2ff5 100644
--- a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -72,7 +72,7 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `on.workflow_call`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
@@ -320,7 +320,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+You can use the `if` conditional to prevent a step from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
@@ -945,7 +945,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `jobs..uses`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 98a84270fb..1e67bc7da9 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
+
| Path without subdomain isolation | Path with subdomain isolation |
| --- | --- |
-| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
-| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
-| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
-| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
-| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
-| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
-| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
+| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
+| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
+| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
+| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
+| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
{%- ifversion viewscreen-and-notebooks %}
-| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
-| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
-{%- else %}
-| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
+| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+{%- ifversion ghes < 3.7 %}
+| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
+| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
+{%- ifversion viewscreen-and-notebooks %}
+| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
+{%- endif %}
+{%- ifversion ghes > 3.4 %}
+| Not supported | `https://containers.HOSTNAME/` |
{%- endif %}
-| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
-| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %}
-| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported | `https://containers.HOSTNAME/` |{% endif %}
## Prerequisites
diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
index 6336814ef8..bcb87587cc 100644
--- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
+++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Actions with MinIO storage
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO storage to store data generated by workflow runs.'
+title: Habilitación de Acciones de GitHub con almacenamiento de MinIO
+intro: 'Puedes habilitar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar el almacenamiento de MinIO para almacenar datos generados por las ejecuciones de flujos de trabajo.'
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
versions:
ghes: '*'
@@ -14,36 +14,35 @@ redirect_from:
- /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
- /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage
shortTitle: MinIO storage
+ms.openlocfilehash: 3d9c6cfca6b81a66185515c8757cef22290ead30
+ms.sourcegitcommit: 8f1801040a84ca9353899a2d1e6782c702aaed0d
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148166573'
---
+## Requisitos previos
-## Prerequisites
+Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos:
-Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
+* Crea tu cubo de MinIO para almacenar los datos que generan las ejecuciones de flujo de trabajo. Para obtener más información sobre cómo instalar y configurar MinIO, consulta: "[Almacenamiento de objetos de alto rendimiento de MinIO ](https://min.io/docs/minio/container/index.html)" y "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" en la documentación de MinIO.
-* Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
+ Para evitar la contención de recursos en el dispositivo, te recomendamos que hospedes MinIO separado de {% data variables.location.product_location %}.
- To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.
+ {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %}
- {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
-{% data reusables.actions.enterprise-common-prereqs %}
+## Habilitar {% data variables.product.prodname_actions %} mediante el almacenamiento de MinIO
-## Enabling {% data variables.product.prodname_actions %} with MinIO storage
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
+1. En "Artifact & Log Storage" (Almacenamiento de artefactos y registros), seleccione **Amazon S3** y escriba los detalles del cubo de almacenamiento:
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.actions %}
-{% data reusables.actions.enterprise-enable-checkbox %}
-1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
+ * **AWS Service URL** (URL del servicio AWS): dirección URL del servicio MinIO. Por ejemplo, `https://my-minio.example:9000`.
+ * **AWS S3 Bucket** (Cubo de AWS S3): nombre del cubo de S3.
+ * **AWS S3 Access Key** (Clave de acceso de AWS S3) y **AWS S3 Secret Key** (Clave de secreto de AWS S3): se usan `MINIO_ACCESS_KEY` y `MINIO_SECRET_KEY` para la instancia de MinIO.
- * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`.
- * **AWS S3 Bucket**: The name of your S3 bucket.
- * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance.
+ 
+1. En "Artifact & Log Storage" (Almacenamiento de artefactos y registros), seleccione **Force path style** (Forzar estilo de ruta de acceso).
- 
-1. Under "Artifact & Log Storage", select **Force path style**.
-
- 
-{% data reusables.enterprise_management_console.test-storage-button %}
-{% data reusables.enterprise_management_console.save-settings %}
+  {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
{% data reusables.actions.enterprise-postinstall-nextsteps %}
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 625a34aa98..c01ecca7a2 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}
diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
index 59f87dab08..af1cdb397c 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
@@ -1,7 +1,7 @@
---
-title: About {% data variables.product.prodname_emus %}
+title: 'Acerca de {% data variables.product.prodname_emus %}'
shortTitle: About managed users
-intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
+intro: 'Puedes administrar centralmente la identidad y el acceso para los miembros de tu empresa en {% data variables.product.prodname_dotcom %} desde tu proveedor de identidad.'
redirect_from:
- /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
- /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
@@ -17,48 +17,53 @@ topics:
- Enterprise
- SSO
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 72d8263029317783e60d8f81f45edc3dbb8b1c8b
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180017'
---
+## Acerca de {% data variables.product.prodname_emus %}
-## About {% data variables.product.prodname_emus %}
+Con {% data variables.product.prodname_emus %}, puedes controlar las cuentas de usuario de los miembros de tu empresa a través de tu proveedor de identidad (IdP). Los usuarios que se asignen a la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu IdP se aprovisionarán como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} y se agregarán a tu empresa. Tú controlas los nombres de usuario, los datos de perfil, la pertenencia del equipo y el acceso de las cuentas de usuario al repositorio desde tu IdP.
-With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.
-
-In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+En tu IdP, puedes dar a cada {% data variables.enterprise.prodname_managed_user %} el rol de usuario, propietario de la empresa o gerente de facturación. {% data variables.enterprise.prodname_managed_users_caps %} puede ser propietario de organizaciones dentro de tu empresa y puede agregar a otros {% data variables.enterprise.prodname_managed_users %} a las organizaciones y equipos dentro de ella. Para obtener más información, vea "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" y "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
{% ifversion oidc-for-emu %}
-{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
+{% data reusables.enterprise-accounts.emu-cap-validates %} Para obtener más información, consulta "[Acerca de la compatibilidad con la directiva de acceso condicional del IdP](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)".
{% endif %}
-You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)."
+Puedes conceder acceso a los {% data variables.enterprise.prodname_managed_users %} a repositorios de la empresa, así como la capacidad de contribuir en ellos, pero los {% data variables.enterprise.prodname_managed_users %} no pueden crear contenido público ni colaborar con otros usuarios, organizaciones y empresas del resto de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Habilidades y restricciones de los {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)".
-The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+El nombre de usuario de los {% data variables.enterprise.prodname_managed_users %} de tu empresa y su información de perfil, como los nombres y direcciones de correo electrónico que se muestran, se configuran mediante tu IdP y no pueden cambiarlos los propios usuarios. Para más información, vea "[Nombres de usuario e información de perfil](#usernames-and-profile-information)".
-Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)."
+Los propietarios de las empresas pueden auditar todas las acciones de los {% data variables.enterprise.prodname_managed_users %} en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Eventos del registro de auditoría para la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)".
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
+Para utilizar los {% data variables.product.prodname_emus %}, necesitas un tipo separado de cuenta empresarial con {% data variables.product.prodname_emus %} habilitados. Para obtener más información sobre cómo crear esta cuenta, consulte "[Acerca de las empresas con usuarios administrados](#about-enterprises-with-managed-users)".
{% note %}
-**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right 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)."
+**Nota**: Hay varias opciones para la administración de identidades y acceso con {% data variables.product.prodname_ghe_cloud %}, y la solución de {% data variables.product.prodname_emus %} no es la mejor para todos los clientes. Para obtener más información que te ayude a decidir si la opción de {% data variables.product.prodname_emus %} es adecuada para tu empresa, consulta "[Acerca de la autenticación de la empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)".
{% endnote %}
-## About organization membership management
+## Acerca de la administración de la pertenencia a una organización
-Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+Las pertenencias a una organización se pueden administrar manualmente o bien las puedes actualizar automáticamente mediante grupos de IdP. Para administrar las pertenencias a la organización mediante el IdP, los miembros deben agregarse a un grupo de IdP y este grupo debe estar conectado a un equipo en la organización. Para obtener más información sobre la administración automática de la organización y las pertenencias a equipos, consulta "[Administración de las pertenencias a equipos con grupos de proveedores de identidades](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)".
-The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization.
+La forma en que se agrega un miembro a una organización propiedad de tu empresa (mediante grupos de IdP o manualmente) determina cómo se deben quitar de una organización.
-- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
-- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
+- Si un miembro se agregó a una organización manualmente, debes quitarlo manualmente. La anulación de la asignación de la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu IdP suspenderá al usuario pero no lo eliminará de la organización.
+- Si un usuario se convirtió en miembro de una organización porque se agregó a grupos de IdP asignados a uno o varios equipos de la organización, quitarlo de _todos_ los grupos de IdP asignados asociados a la organización hará que se quite de la organización.
-To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
+Para descubrir cómo se agregó un miembro a una organización, puedes filtrar la lista de miembros por tipo. Para más información, vea "[Visualización de personas en la empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)".
-## Identity provider support
+## Soporte del proveedor de identidad
-{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
+{% data variables.product.prodname_emus %} admite los siguientes IdP{% ifversion oidc-for-emu %} y métodos de autenticación:
| | SAML | OIDC |
|----------------------------------|-----------------------------------------------|-----------------------------------------------|
@@ -70,36 +75,36 @@ To discover how a member was added to an organization, you can filter the member
{% endif %}
-## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
+## Habilidades y restricciones de los {% data variables.enterprise.prodname_managed_users %}
-{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests.
+Los {% data variables.enterprise.prodname_managed_users_caps %} solo pueden colaborar en los repositorios privados e internos en su empresa y con los repositorios que pertenecen a su cuenta de usuario. Los {% data variables.enterprise.prodname_managed_users_caps %} tienen acceso de solo lectura al resto de la comunidad de {% data variables.product.prodname_dotcom %}. Estas restricciones de visibilidad y acceso para los usuarios, así como el contenido, aplican a todas las solicitudes, incluyendo a las de la API.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises.
-* Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
-* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate.
-* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
-* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories.
+* No se puede invitar a {% data variables.enterprise.prodname_managed_users_caps %} para que se unan a organizaciones o repositorios de fuera de la empresa, ni se puede invitar a {% data variables.enterprise.prodname_managed_users %} a otras empresas.
+* Los colaboradores externos no son compatibles con los {% data variables.product.prodname_emus %}.
+* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden crear incidencias ni solicitudes de incorporación de cambios, comentar o agregar reacciones, ni marcar como favoritos u observar o bifurcar repositorios fuera de la empresa.
+* Los {% data variables.enterprise.prodname_managed_users_caps %} pueden ver todos los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %} pero no pueden insertar código a los repositorios fuera de la empresa.
+* Solo otros miembros de la empresa pueden ver a los {% data variables.enterprise.prodname_managed_users_caps %} y el contenido que estos crean.
+* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden seguir a usuarios que estén fuera de la empresa.
+* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden crear gists o comentar en ellos.
+* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden crear flujos de trabajo de inicio para {% data variables.product.prodname_actions %}.
+* Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden instalar {% data variables.product.prodname_github_apps %} en sus cuentas de usuario.
+* Otros usuarios de {% data variables.product.prodname_dotcom %} no pueden ver, mencionar o invitar a {% data variables.enterprise.prodname_managed_user %} para colaborar.
+* Puedes elegir si los {% data variables.enterprise.prodname_managed_users %} pueden crear repositorios propiedad de sus cuentas de usuario. Para más información, vea "[Aplicación de directivas de administración de repositorios en la empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)".
+* Si permites que {% data variables.enterprise.prodname_managed_users %} creen repositorios propiedad de sus cuentas de usuario, solo pueden poseer repositorios privados y únicamente pueden invitar a otros miembros de la empresa a colaborar en los repositorios propiedad del usuario.
* {% data reusables.enterprise-accounts.emu-forks %}
-* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings.
-* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
+* Solo se pueden crear repositorios internos y privados en las organizaciones que pertenezcan a una {% data variables.enterprise.prodname_emu_enterprise %}, en función de la configuración de visibilidad del repositorio o la empresa.
+* Los {% data variables.enterprise.prodname_managed_users_caps %} están limitados en su uso de {% data variables.product.prodname_pages %}. Para obtener más información, consulta [Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users).
* {% data reusables.copilot.emus-cannot-use-copilot %}
-## Getting started with {% data variables.product.prodname_emus %}
+## Introducción a {% data variables.product.prodname_emus %}
-Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps.
+Para que los desarrolladores puedan usar la {% data variables.product.prodname_ghe_cloud %} con {% data variables.product.prodname_emus %}, debes llevar a cabo una serie de pasos de configuración.
-1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+1. Para utilizar los {% data variables.product.prodname_emus %}, necesitas un tipo separado de cuenta empresarial con {% data variables.product.prodname_emus %} habilitados. Para probar {% data variables.product.prodname_emus %} o para analizar las opciones para migrar desde su empresa existente, póngase en contacto con el [equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
- Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+ La persona de contacto en el equipo de ventas de GitHub trabajará contigo para crear tu {% data variables.enterprise.prodname_emu_enterprise %} nueva. Necesitarás proporcionar la dirección de correo electrónico del usuario que configurará tu empresa y un código corto que se utilizará como el sufijo de los nombres de usuario de los miembros. {% data reusables.enterprise-accounts.emu-shortcode %} Para más información, vea "[Nombres de usuario e información de perfil](#usernames-and-profile-information)".
-2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`.
+2. Después de crear tu empresa, recibirás un mensaje de correo electrónico de {% data variables.product.prodname_dotcom %}, el cual te invitará a elegir una contraseña para tu usuario de configuración de la empresa, quien será el primer propietario de esta. Utiliza una ventana de búsqueda privada o en modo incógnito al configurar la contraseña. El usuario de configuración solo se usa para configurar el inicio de sesión único y la integración de aprovisionamiento de SCIM para la empresa. Ya no tendrá acceso para administrar la cuenta empresarial una vez que se habilite correctamente el inicio de sesión único. El nombre de usuario del usuario de configuración es el código corto de la empresa con el sufijo `_admin`.
{% note %}
@@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w
{% endnote %}
-3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+3. Después de iniciar sesión como usuario de configuración, se recomienda habilitar la autenticación en dos fases. Para obtener más información, vea "[Configuración de autenticación en dos fases](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)".
-1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). We recommend OIDC, which includes support for Conditional Access Policies (CAP). If you require multiple enterprises with {% data variables.enterprise.prodname_managed_users %} provisioned from one tenant, you must use SAML for each enterprise after the first. If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
+1. Para empezar, configura {% ifversion oidc-for-emu %}cómo se autenticarán los miembros. Si usas Azure Active Directory como proveedor de identidades, puedes elegir entre OpenID Connect (OIDC) y el Lenguaje de marcado de aserción de seguridad (SAML). Se recomienda OIDC, que incluye compatibilidad con directivas de acceso condicional (CAP). Si necesitas varias empresas con {% data variables.enterprise.prodname_managed_users %} aprovisionados desde un inquilino, debes usar SAML para cada empresa después de la primera. Si usas Okta como proveedor de identidades, puedes usar SAML para autenticar a los miembros. {% else %}SSO de SAML para tu empresa. Para obtener más información, consulta "[Configuración del inicio de sesión único de SAML para Usuarios Administrados de Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)".{% endif %}
{% ifversion oidc-for-emu %}
- To get started, read the guide for your chosen authentication method.
+ Para empezar, lea la guía del método de autenticación elegido.
- - "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
- - "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+ - "[Configuración de OIDC para Usuarios Administrados de Enterprise](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)".
+ - "[Configuración del inicio de sesión único de SAML para Usuarios Administrados de Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)".
{% endif %}
-4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+4. Una vez que hayas configurado el inicio de sesión único, puedes configurar el aprovisionamiento de SCIM. SCIM es cómo creará el proveedor de identidades {% data variables.enterprise.prodname_managed_users %} en los datos {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre cómo configurar el aprovisionamiento de SCIM, consulta "[Configuración del aprovisionamiento de SCIM para Usuarios Administrados de Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)".
-5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
+5. Una vez configurada la autenticación y el aprovisionamiento, puede empezar a administrar la pertenencia a la organización para los datos {% data variables.enterprise.prodname_managed_users %} mediante la sincronización de grupos de IdP con equipos. Para más información sobre cómo administrar equipos, vea "[Administración de pertenencias a equipos con grupos de proveedores de identidades](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)".
-If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)."
+Si los miembros de tu empresa deben usar una estación de trabajo para contribuir a los repositorios en {% data variables.location.product_location %} tanto de un {% data variables.enterprise.prodname_managed_user %} como de una cuenta personal, puedes proporcionar compatibilidad. Para obtener más información, consulta "[Compatibilidad con desarrolladores con varias cuentas de usuario en {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)".
-## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
+## Autenticación como {% data variables.enterprise.prodname_managed_user %}
-{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}.
+Los {% data variables.enterprise.prodname_managed_users_caps %} se deben autenticar mediante su proveedor de identidad. Para autenticarse, un {% data variables.enterprise.prodname_managed_user %} puede visitar su portal de aplicación IdP o utilizar una página de inicio de sesión en el {% data variables.product.prodname_dotcom_the_website %}.
-By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
+De manera predeterminada, cuando un usuario no autenticado intenta acceder a una empresa que usa {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} muestra un error 404. Opcionalmente, un propietario de la empresa puede habilitar redirecciones automáticas al inicio de sesión único (SSO) en lugar de al error 404. Para más información, vea "[Aplicación de directivas de configuración de seguridad en la empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)".
-{% 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 %} Para más información, vea "[Administración de códigos de recuperación para la empresa](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)".
-### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
+### Autenticarse como un {% data variables.enterprise.prodname_managed_user %} mediante el {% data variables.product.prodname_dotcom_the_website %}
-1. Navigate to [https://github.com/login](https://github.com/login).
-1. In the "Username or email address" text box, enter your username including the underscore and short code.
- 
- When the form recognizes your username, the form will update. You do not need to enter your password on this form.
-1. To continue to your identity provider, click **Sign in with your identity provider**.
- 
+1. Vaya a [https://github.com/login](https://github.com/login).
+1. En la caja de texto de "Nombre de usuario o dirección de correo electrónico", ingresa tu nombre de usuario incluyendo el guion bajo y código corto.
+ . Si el formulario reconoce el nombre de usuario, se actualizará. No necesitas ingresar tu contraseña en este formato.
+1. Para continuar con el proveedor de identidades, haga clic en **Sign in with your identity provider** (Iniciar sesión con el proveedor de identidades).
+ 
-## Usernames and profile information
+## Nombres de usuario e información de perfil
-{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+{% data variables.product.product_name %} crea automáticamente un nombre de usuario para cada persona mediante la normalización de un identificador proporcionado por el IdP. Para más información, consulta "[Consideraciones sobre el nombre de usuario para la autenticación externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)".
-A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
+Puede producirse un conflicto al aprovisionar usuarios si las partes únicas del identificador proporcionado por el IdP se quitan durante la normalización. Si no puedes aprovisionar un usuario debido a un conflicto con el nombre de usuario, debes modificar el nombre de usuario proporcionado por el IdP. Para obtener más información, consulta "[Resolución de problemas de nombre de usuario](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)".
{% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %}
-The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
+El nombre de perfil y dirección de correo electrónico de un {% data variables.enterprise.prodname_managed_user %} también lo proporciona el IdP. Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden cambiar su nombre de perfil ni la dirección de correo electrónico en {% data variables.product.prodname_dotcom %}, y el IdP solo puede proporcionar una dirección de correo electrónico.
-## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
+## Compatibilidad con desarrolladores con varias cuentas de usuario en {% data variables.location.product_location %}
-People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work.
+Es posible que personas del equipo necesiten contribuir a los recursos de {% data variables.location.product_location %} que están fuera de {% data variables.enterprise.prodname_emu_enterprise %}. Por ejemplo, puede que quieras mantener una empresa independiente para los proyectos de código abierto de la empresa. Dado que un {% data variables.enterprise.prodname_managed_user %} no puede contribuir a los recursos públicos, los usuarios deberán mantener una cuenta personal independiente para este trabajo.
-People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
+Las personas que deben contribuir desde dos cuentas de usuario en {% data variables.location.product_location %} con una estación de trabajo pueden configurar Git para simplificar el proceso. Para obtener más información, consulta "[Administración de varias cuentas](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)".
diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
index 33c6b16923..bddf1ff344 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
@@ -1,7 +1,7 @@
---
-title: About support for your IdP's Conditional Access Policy
+title: Sobre la compatibilidad con la Directiva de acceso condicional de IdP
shortTitle: Conditional access policy
-intro: 'When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} can validate access to your enterprise and its resources using your IdP''s Conditional Access Policy (CAP).'
+intro: 'Cuando la empresa usa el inicio de sesión único de OIDC, {% data variables.product.prodname_dotcom %} puede validar el acceso a la empresa y sus recursos mediante la Directiva de acceso condicional (CAP) del IdP.'
product: '{% data reusables.gated-features.emus %}'
versions:
feature: oidc-for-emu
@@ -10,35 +10,40 @@ topics:
- Authentication
- Enterprise
- SSO
+ms.openlocfilehash: aed7008bd008ccfd6303ccbb36f4d6f3bd7002ca
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180001'
---
-
{% data reusables.enterprise-accounts.azure-emu-support-oidc %}
-## About support for Conditional Access Policies
+## Sobre la compatibilidad con las Directivas de acceso condicional
{% data reusables.enterprise-accounts.emu-cap-validates %}
-{% data variables.product.product_name %} supports CAP for any {% data variables.enterprise.prodname_emu_enterprise %} where OIDC SSO is enabled. {% data variables.product.product_name %} enforces your IdP's IP conditions but cannot enforce your device compliance conditions. Enterprise owners can choose to use this IP allow list configuration instead of {% data variables.product.product_name %}'s IP allow list, and can do so once OIDC SSO is configured. For more information about IP allow lists, see "[Restricting network traffic with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."
+{% data variables.product.product_name %} admite CAP para cualquier {% data variables.enterprise.prodname_emu_enterprise %} donde está habilitado el inicio de sesión único de OIDC. {% data variables.product.product_name %} aplica las condiciones de la IP del IdP, pero no las condiciones de cumplimiento del dispositivo. Los propietarios de la empresa pueden optar por usar esta configuración de lista de direcciones IP permitidas en lugar de la lista de direcciones permitidas de {% data variables.product.product_name %}, y pueden hacerlo una vez configurado el inicio de sesión único de OIDC. Para obtener más información sobre las listas de direcciones IP permitidas, consulta "[Restricción del tráfico de red con una lista de direcciones IP permitidas](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" y "[Administración de las direcciones IP permitidas para tu organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)".
-For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."
+Para más información sobre el uso de OIDC con {% data variables.product.prodname_emus %}, consulta "[Configuración de OIDC para usuarios administrados por empresas](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" y "[Migración de SAML a OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)".
-## Considerations for integrations and automations
+## Consideraciones sobre integraciones y automatizaciones
-{% data variables.product.prodname_dotcom %} sends the originating IP address to your IdP for validation against your CAP. To make sure actions and apps are not blocked by your IdP's CAP, you will need to make changes to your configuration.
+{% data variables.product.prodname_dotcom %} envía la dirección IP de origen al IdP para su validación en el CAP. Para asegurar que las acciones y las aplicaciones no están bloqueadas por el CAP del IdP, habrá que realizar cambios en la configuración.
{% data reusables.enterprise-accounts.oidc-gei-warning %}
### {% data variables.product.prodname_actions %}
-Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP.
+Es probable que las acciones que usen un {% data variables.product.pat_generic %} estén bloqueadas por el CAP del proveedor de identidades. Se recomienda que los {% data variables.product.pat_generic %} se creen mediante una cuenta de servicio que, después, esté exenta de los controles IP en el CAP del proveedor de identidades.
-If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)."
+Si no puedes usar una cuenta de servicio, otra opción para desbloquear acciones que usan {% data variables.product.pat_generic %} es permitir los intervalos IP usados por {% data variables.product.prodname_actions %}. Para más información, consulta "[Sobre las direcciones IP de GitHub](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)".
-### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+### {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %}
-When {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} make requests on a member's behalf, {% data variables.product.prodname_dotcom %} will send the IP address of the app's server to your IdP for validation. If the IP address of the app's server is not validated by your IdP's CAP, the request will fail.
+Cuando {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %} realizan solicitudes en nombre de un miembro, {% data variables.product.prodname_dotcom %} enviará la dirección IP del servidor de la aplicación al IdP para su validación. Si el CAP del IDP no valida la dirección IP del servidor de la aplicación, se producirá un error en la solicitud.
-You can contact the owners of the apps you want to use, ask for their IP ranges, and configure your IdP's CAP to allow access from those IP ranges. If you're unable to contact the owners, you can review your IdP sign-in logs to review the IP addresses seen in the requests, then allow-list those addresses.
+Puedes contactar con los propietarios de las aplicaciones que quiere usar, pedir sus intervalos IP y configurar el CAP del IdP para permitir el acceso desde esos intervalos IP. Si no puedes contactar con los propietarios, puedes revisar los registros de inicio de sesión de IdP para revisar las direcciones IP que se ven en las solicitudes y, después, permitir enumerar esas direcciones.
-If you do not wish to allow all of the IP ranges for all of your enterprise's apps, you can also exempt installed {% data variables.product.prodname_github_apps %} and authorized {% data variables.product.prodname_oauth_apps %} from the IdP allow list. If you do so, these apps will continue working regardless of the originating IP address. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)."
+Si no quieres permitir todos los intervalos IP para todas las aplicaciones de la empresa, también puedes excluir los {% data variables.product.prodname_github_apps %} y los {% data variables.product.prodname_oauth_apps %} autorizados de la lista de permitidos del proveedor de identidades. Si lo haces, estas aplicaciones seguirán funcionando independientemente de la dirección IP de origen. Para obtener más información, consulta "[Aplicación de directivas de configuración de seguridad en la empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)".
diff --git a/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
index a7060df4d0..8d863f5f52 100644
--- a/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
+++ b/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Packages with Azure Blob Storage
-intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.'
+title: Habilitar GitHub Packages con Azure Blob Storage
+intro: 'Configura el {% data variables.product.prodname_registry %} con Azure Blob Storage como tu almacenamiento externo.'
versions:
ghes: '*'
type: tutorial
@@ -9,42 +9,44 @@ topics:
- Packages
- Storage
shortTitle: Enable Packages with Azure
+ms.openlocfilehash: b851f698baba60323cbaaa69122cacdc92ec83c2
+ms.sourcegitcommit: 3ece72cf2d90987575d369c44101d19d3bb06f76
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190391'
---
-
{% warning %}
-**Warnings:**
-- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
-- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
-- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
+**Advertencias:**
+- Es crítico que configures las políticas de acceso restrictivo que necesites para tu bucket de almacenamiento, ya que {% data variables.product.company_short %} no aplica permisos de objeto específicos o listas de control de acceso adicionales (ACLs) a tu configuración de bucket de almacenamiento. Por ejemplo, si haces a tu bucket público, el público general en la internet podrá acceder a ellos.
+- Te recomendamos utilizar un bucket dedicado para {% data variables.product.prodname_registry %}, separado de aquél que utilices para almacenar {% data variables.product.prodname_actions %}.
+- Asegúrate de configurar el bucket que quieres utilizar en el futuro. No te recomendamos cambiar tu almacenamiento después de que comienzas a utilizar {% data variables.product.prodname_registry %}.
{% endwarning %}
-## Prerequisites
+## Requisitos previos
-Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/).
+Antes de que puedas habilitar y configurar el {% data variables.product.prodname_registry %} en {% data variables.location.product_location_enterprise %}, necesitas preparar tu cubo de almacenamiento de Azure Blob Storage. Para preparar el cubo de Azure Blob Storage, se recomienda consultar los documentos oficiales de Azure Blob Storage en el [sitio oficial de documentación de Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/).
-## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage
+## Habilitar el {% data variables.product.prodname_registry %} con Azure Blob Storage
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_site_admin_settings.packages-tab %}
-{% data reusables.package_registry.enable-enterprise-github-packages %}
-1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %}
+1. Debajo de "Almacenamiento de paquetes", selecciona **Azure Blob Storage** y escribe el nombre de tu contenedor de Azure para el cubo de almacenamiento de paquetes y la cadena de conexión.
- - You must create a storage container prior to setting the container name and connection string.
+ - Debes crear un contenedor de almacenamiento antes de establecer el nombre del contenedor y la cadena de conexión.
- 
+ 
{% note %}
- **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
- Usage of a SAS Token or SAS URL as connection string is not currently supported.
+ **Nota:** Para encontrar la cadena de conexión de Azure, ve al menú Clave de acceso de la cuenta de Azure Storage.
+ Actualmente, no se admite el uso de un token de SAS o una dirección URL de SAS como cadena de conexión.
{% endnote %}
{% data reusables.enterprise_management_console.save-settings %}
-## Next steps
+## Pasos siguientes
{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 991873cdca..041431c2e8 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -56,7 +56,7 @@ You can enforce policies to control how members of your enterprise on {% data va
Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% ifversion ghes or ghae %}
@@ -166,7 +166,7 @@ Across all organizations owned by your enterprise, you can set the default branc
Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 571de5c750..1c4f17c010 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -1,6 +1,6 @@
---
-title: About billing for GitHub Actions
-intro: 'If you want to use {% data variables.product.prodname_actions %} beyond the storage or minutes included in your account, you will be billed for additional usage.'
+title: Acerca de la facturación para las Acciones de GitHub
+intro: 'Si quieres utilizar {% data variables.product.prodname_actions %} con más almacenamiento o minutos de los que se incluyen en tu cuenta, se te cobrará por estos recursos adicionales.'
miniTocMaxHeadingLevel: 3
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
@@ -13,103 +13,104 @@ topics:
- Actions
- Spending limits
shortTitle: Billing for GitHub Actions
+ms.openlocfilehash: f08d06a34d5e7e7f0e2ed49d07a4297c4c6be930
+ms.sourcegitcommit: 06d16bf9a5c7f3e7107f4dcd4d06edae5971638b
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179665'
---
-## About billing for {% data variables.product.prodname_actions %}
+## Acerca de la facturación para {% data variables.product.prodname_actions %}
{% data reusables.actions.actions-billing %}
-{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
+{% data reusables.actions.actions-spending-limit-brief %} Para más información, vea "[Acerca de los límites de gasto](#about-spending-limits)".
-{% ifversion ghec %}
-If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% ifversion ghec %} Si ha comprado {% data variables.product.prodname_enterprise %} mediante un Acuerdo de Microsoft Enterprise, puede conectar el id. de la suscripción de Azure a la cuenta empresarial para habilitar y pagar por el uso de {% data variables.product.prodname_actions %} más allá de las cantidades que se incluyen en la cuenta. Para más información, vea "[Conexión de una suscripción de Azure a la empresa](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)".
{% endif %}
-Minutes reset every month, while storage usage does not.
+Los minutos se restablecen cada mes, mientras que el uso del almacenamiento no.
-### Included storage and minutes
+### Minutos y almacenamiento incluídos
-{% ifversion actions-hosted-runners %}
-{% note %}
+{% ifversion actions-hosted-runners %} {% note %}
-**Note**: Entitlement minutes cannot be used for Windows and Ubuntu runners over 2-cores. These runners will always be charged for, including in public repos. For more information, see "[Per-minute rates for runners](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)."
+**Nota**: Los minutos de derechos no se pueden usar para los ejecutores de Windows y Ubuntu de más de 2 núcleos. Estos ejecutores siempre se cobrarán, incluidos en repositorios públicos. Para obtener más información, consulta "[Tarifas por minuto para los ejecutores](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)".
-{% endnote %}
-{% endif %}
+{% endnote %} {% endif %}
-|Product | Storage | Minutes (per month)|
+|Producto | Storage | Minutos (por mes)|
|------- | ------- | ---------|
-| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
+| {% data variables.product.prodname_free_user %} | 500 MB | 2\.000 |
| {% data variables.product.prodname_pro %} | 1 GB | 3,000 |
-| {% data variables.product.prodname_free_team %} for organizations | 500 MB | 2,000 |
+| {% data variables.product.prodname_free_team %} para organizaciones | 500 MB | 2\.000 |
| {% data variables.product.prodname_team %} | 2 GB | 3,000 |
-| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 |
+| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50.000 |
-Jobs that run on Windows and macOS runners that {% data variables.product.prodname_dotcom %} hosts consume minutes at 2 and 10 times the rate that jobs on Linux runners consume. For example, using 1,000 Windows minutes would consume 2,000 of the minutes included in your account. Using 1,000 macOS minutes, would consume 10,000 minutes included in your account.
+Los jobs que se ejecutan en Windows y macOS y que se hospedan en {% data variables.product.prodname_dotcom %} consumen minutos en una proporción de 2 a 10 veces mayor que aquellos que se ejecutan en Linux. Por ejemplo, el uso de 1000 minutos de Windows consumirá 2000 de los minutos incluidos en su cuenta. El uso de 1000 minutos de macOS, consumirá 10 000 minutos incluidos en su cuenta.
-### Minute multipliers
+### Multiplicadores de minutos
-| Operating system | Minute multiplier |
+| Sistema operativo | Multiplicador de minutos |
|------- | ---------|
| Linux | 1 |
| macOS| 10 |
| Windows | 2 |
-The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+El almacenamiento que utilza un repositorio es el total del almacenamiento utilizado por los artefactos de {% data variables.product.prodname_actions %} y por {% data variables.product.prodname_registry %}. El costo de almacenamiento es el uso total de todos los repositorios que pertenecen a su cuenta. Para más información sobre los precios de {% data variables.product.prodname_registry %}, vea "[Acerca de la facturación de {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)".
- If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
+ Si tu uso de la cuenta sobrepasa estos límites y has establecido un límite de gasto superior a 0 USD, pagarás 0,008 USD por GB de almacenamiento por día y por minuto de uso, en función del sistema operativo que utilice el ejecutor hospedado en {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} redondea al alza los minutos y minutos parciales que cada trabajo utiliza al siguiente minuto completo.
{% note %}
-**Note:** Minute multipliers do not apply to the per-minute rates shown below.
+**Nota:** Los multiplicadores de minutos no se aplican a las tasas por minuto que se muestran a continuación.
{% endnote %}
-### Per-minute rates
+### Tasas por minuto
-{% data reusables.billing.billing-standard-runners %}
-{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
+{% data reusables.billing.billing-standard-runners %} {%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
-- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
-- {% data reusables.user-settings.context_switcher %}
-{% ifversion actions-hosted-runners %}
-- For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
-- Entitlement minutes cannot be used for {% data variables.actions.hosted_runner %}s.
-- The {% data variables.actions.hosted_runner %}s are not free for public repositories.
+- La cantidad de jobs que puedes ejecutar simultáneamente a través de todos los repositorios que pertenezcan a tu cuenta de usuario u organización dependerá de tu plan de GitHub. Para más información, vea "[Límites de uso y facturación](/actions/reference/usage-limits-billing-and-administration)" para ejecutores hospedados en {% data variables.product.prodname_dotcom %} y "[Acerca de los ejecutores autohospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para los límites de uso de los ejecutores autohospedados.
+- {% data reusables.user-settings.context_switcher %} {% ifversion actions-hosted-runners %}
+- Para {% data variables.actions.hosted_runner %}, no hay ningún costo adicional para las configuraciones que asignan direcciones IP estáticas públicas a un {% data variables.actions.hosted_runner %}. Para obtener más información sobre {% data variables.actions.hosted_runner %}, consulta "[Usar {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-larger-runners)".
+- No se pueden usar minutos de derechos para {% data variables.actions.hosted_runner %}.
+- Un {% data variables.actions.hosted_runner %} no es gratis para los repositorios públicos.
{% endif %}
-## Calculating minute and storage spending
+## Calcular los gastos por minuto y por almacenamiento
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_actions %}
-At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account.
+Al final de cada mes, {% data variables.product.prodname_dotcom %} calcula el costo de los minutos y almacenamiento utilizados en comparación con lo que se incluye en tu cuenta.
-### Sample minutes cost calculation
+### Ejemplo de cálculos de costo por minuto
-For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
+Por ejemplo, si en la organización se usa {% data variables.product.prodname_team %} y permite gastos ilimitados, el uso de 5000 minutos podría tener un costo de uso por encima del límite de almacenamiento y minutos total de 56 USD, en función de los sistemas operativos que se usen para ejecutar los trabajos.
-- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
- - 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
- - 2,000 Windows minutes at $0.016 USD per minute = $32 USD.
+- 5,000 minutos (3,000 de Linux y 2,000 de Windows) = $56 USD ($24 USD + $32 USD).
+ - 3,000 minutos de Linux a $0.008 USD por minuto = $24 USD.
+ - 2,000 minutos de Windows a $0.016 USD por minuto = $32 USD.
-{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month.
+{% data variables.product.prodname_dotcom %} calcula tu uso de almacenamiento para cada mes basándose en el uso por hora durante el mismo mes.
-### Sample storage cost calculation
+### Muestra de cálculo de costos de almacenamiento
-For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be:
+Por ejemplo, si usa 3 GB de almacenamiento durante 10 días de marzo y 12 GB durante 21 días de marzo, el uso del almacenamiento sería:
-- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours
-- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours
-- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours
-- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months
+- 3 GB x 10 días x (24 horas por día) = 720 GB-Horas
+- 12 GB x 21 días x (24 horas por día) = 6,048 GB-Horas
+- 720 GB-Horas + 6,048 GB-Horas = 6,768 GB-Horas
+- 6,768 GB-Horas/ (744 horas por mes) = 9.0967 GB-Meses
-At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
+Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. Por lo tanto, el uso del almacenamiento para marzo sería de 9097 GB.
-Your {% data variables.product.prodname_actions %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
+Tu uso de {% data variables.product.prodname_actions %} comparte la fecha de facturación, método de pago y recibo existente en tu cuenta. {% data reusables.dotcom_billing.view-all-subscriptions %}
-## About spending limits
+## Acerca de los límites de gasto
{% data reusables.actions.actions-spending-limit-detailed %}
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+Para obtener información sobre cómo administrar y cambiar el límite de gasto de la cuenta, vea "[Administración del límite de gasto para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)".
{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
diff --git a/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md b/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
index d6daeb7614..68fec17bdb 100644
--- a/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
+++ b/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
@@ -1,6 +1,6 @@
---
-title: Managing privately reported security vulnerabilities
-intro: Repository maintainers can manage security vulnerabilities that have been privately reported to them by security reseachers for repositories where private vulnerability reporting is enabled.
+title: Administración de vulnerabilidades de seguridad notificadas de forma privada
+intro: Los mantenedores de repositorios pueden administrar las vulnerabilidades de seguridad que les hayan notificado de forma privada los investigadores de seguridad para los repositorios en los que esté habilitado el informe privado de vulnerabilidades.
permissions: 'Anyone with admin permissions to a repository can see, review, and manage privately-reported vulnerabilities for the repository.'
versions:
fpt: '*'
@@ -11,35 +11,38 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Manage vulnerability reports
+ms.openlocfilehash: 942533788dc6ad9280ddc023f583462c7a0ff7f8
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160359'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## Acerca de la creación de informes privados de una vulnerabilidad de seguridad
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to you using a simple form.
+Los informes de vulnerabilidades privados facilitan a los investigadores de seguridad notificar las vulnerabilidades directamente mediante un formulario sencillo.
-When a security researcher reports a vulnerability privately, you are notified and can choose to either accept it, ask more questions, or reject it. If you accept the report, you're ready to collaborate on a fix for the vulnerability in private with the security researcher.
+Cuando un investigador de seguridad notifica una vulnerabilidad de forma privada, se te notifica y puedes optar por aceptarla, formular más preguntas o rechazarla. Si aceptas el informe, estarás a punto para colaborar en una corrección de la vulnerabilidad en privado con el investigador de seguridad.
-## Managing security vulnerabilities that are privately reported
+## Administración de vulnerabilidades de seguridad que se notifican de forma privada
-{% data variables.product.prodname_dotcom %} notifies repository maintainers when security researchers privately report vulnerabilities in their repository, and sends notifications if maintainers watch the repository or if they have notifications enabled for the repository. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
+{% data variables.product.prodname_dotcom %} envía una notificación a los mantenedores del repositorio cuando los investigadores de seguridad informan de forma privada sobre vulnerabilidades en su repositorio y envía notificaciones si los mantenedores observan el repositorio o si tienen notificaciones habilitadas para el repositorio. Para más información, vea "[Configuración de notificaciones](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)".
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click the advisory you want to review. An advisory that is privately reported will have a status of `Needs triage`.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Haz clic en el aviso que quieras revisar. Un aviso que se notifique de forma privada tendrá el estado `Needs triage`.
- 
+ 
-2. Carefully review the report. You can:
- - Collaborate with the security researcher on a patch in private, by clicking **Start a temporary private fork**. This gives you a place for further discussions with the contributor without changing the status of the proposed advisory from `Needs triage`.
- - Accept the vulnerability report as a draft advisory on {% data variables.product.prodname_dotcom %}, by clicking **Accept and open as draft**. If you choose this option:
- - This doesn't make the report public.
- - The report becomes a draft repository security advisory and you can work on it in the same way as any draft advisory that you create.
- For more information on security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."
- - Reject the report by clicking **Close security advisory**. Where possible, you should add a comment explaining why you don't consider the report a security risk before you close the advisory.
+2. Revisa detenidamente el informe. Puede:
+ - Colabora con el investigador de seguridad para realizar una revisión en privado; para ello, haz clic en **Iniciar una bifurcación privada temporal**. Esta opción te ofrece un lugar para seguir conversando con el colaborador sin cambiar el estado `Needs triage` del aviso propuesto.
+ - Acepta el informe de vulnerabilidades como borrador de aviso sobre {% data variables.product.prodname_dotcom %} haciendo clic en **Aceptar y abrir como borrador**. Si eliges esta opción:
+ - El informe no se hará público.
+ - El informe se convertirá en un borrador de aviso de seguridad de repositorio y podrás trabajar en él de la misma manera que en cualquier otro borrador de aviso que crees.
+ Para obtener más información acerca de los avisos de seguridad de repositorio, consulta "[Acerca de los avisos de seguridad de repositorio](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)".
+ - Rechaza el informe haciendo clic en **Cerrar aviso de seguridad**. Siempre que sea posible, debes agregar un comentario que explique por qué no consideras el informe un riesgo de seguridad antes de cerrar el aviso.
- 
\ No newline at end of file
+ 
diff --git a/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md b/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
index 521fa86d92..17d2d4e198 100644
--- a/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
+++ b/translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
@@ -1,6 +1,6 @@
---
-title: Privately reporting a security vulnerability
-intro: Some public repositories configure security advisories so that anyone can report security vulnerabilities directly and privately to the maintainers.
+title: Creación de informes privados de una vulnerabilidad de seguridad
+intro: Algunos repositorios públicos configuran avisos de seguridad para que cualquier usuario pueda notificar vulnerabilidades de seguridad directamente y de forma privada a los mantenedores.
versions:
fpt: '*'
ghec: '*'
@@ -10,61 +10,64 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Privately reporting
+ms.openlocfilehash: 7f4f208bd2724608cf9955efd82a256c3479e884
+ms.sourcegitcommit: 2ff4a43f0b14939da79d56c54402cfee8d90ae23
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/17/2022
+ms.locfileid: '148169561'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## Acerca de la creación de informes privados de una vulnerabilidad de seguridad
-Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
+A menudo, los investigadores de seguridad se sienten responsables de alertar a los usuarios de una vulnerabilidad que podría aprovecharse. Si no hay instrucciones claras sobre cómo ponerse en contacto con los mantenedores del repositorio que contienen la vulnerabilidad, es posible que los investigadores de seguridad no tengan otra opción, sino publicar sobre la vulnerabilidad en las redes sociales, enviar mensajes directos al mantenedor o incluso crear problemas públicos. Esta situación puede dar lugar a una divulgación pública de los detalles de la vulnerabilidad.
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to repository maintainer using a simple form.
+Los informes de vulnerabilidades privadas facilitan a los investigadores de seguridad notificar las vulnerabilidades directamente al mantenedor de repositorios mediante un formulario sencillo.
-For security researchers, the benefits of using private vulnerability reporting are:
-- Less frustration, and less time spent trying to figure out how to contact the maintainer.
-- A smoother process for disclosing and discussing vulnerability details.
-- The opportunity to discuss vulnerability details privately with repository maintainer.
+Para los investigadores de seguridad, las ventajas de usar informes de vulnerabilidades privados son:
+- Menos frustración y menos tiempo dedicado a tratar de averiguar cómo ponerse en contacto con el mantenedor.
+- Un proceso más sencillo para revelar y analizar los detalles de la vulnerabilidad.
+- La oportunidad de analizar los detalles de vulnerabilidades de forma privada con el mantenedor de repositorios.
{% note %}
-**Note:** If the repository doesn't have private vulnerabiliy reporting enabled, you need to initiate the reporting process by following the instructions in the security policy for the repository, or create an issue asking the maintainers for a preferred security contact. For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
+**Nota:** Si el repositorio no tiene habilitados los informes privados de vulnerabilidades, debes iniciar el proceso de informes siguiendo las instrucciones de la directiva de seguridad del repositorio o crear una incidencia que solicite a los mantenedores un contacto de seguridad preferido. Para obtener más información, consulta "[Acerca de la divulgación coordinada de las vulnerabilidades de seguridad](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
{% endnote %}
-## Privately reporting a security vulnerability
+## Creación de informes privados de una vulnerabilidad de seguridad
-Security researchers can privately report a security vulnerability to repository maintainers.
+Los investigadores de seguridad pueden notificar de forma privada una vulnerabilidad de seguridad a los mantenedores de repositorios.
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **Report a vulnerability** to open the advisory form.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Haz clic en **Notificar una vulnerabilidad** para abrir el formulario de asesoramiento.
- 
+ 
-2. Fill in the advisory details form.
+2. Rellena el formulario de detalles de asesoramiento.
{% tip %}
- **Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
+ **Consejo:** En este formato, solo el título y la descripción son obligatorios. (En el formulario de aviso de seguridad general, que inicia el mantenedor del repositorio, también se requiere especificar el ecosistema). Sin embargo, recomendamos que los investigadores de seguridad proporcionen toda la información posible en el formulario para que los mantenedores puedan tomar una decisión informada sobre el informe enviado. Puedes adoptar la plantilla que usan nuestros investigadores de seguridad de {% data variables.product.prodname_security %}, que está disponible en el [repositorio `github/securitylab`](https://github.com/github/securitylab/blob/main/docs/report-template.md)".
{% endtip %}
- For more information about the fields available and guidance on filling in the form, see "[Creating a repository security advisory](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[Best practices for writing repository security advisories](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
+ Para obtener más información sobre los campos disponibles y las instrucciones para rellenar el formulario, consulta "[Creación de un aviso de seguridad de repositorio](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" y "[Procedimientos recomendados para escribir avisos de seguridad de repositorios](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)".
-1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
+1. En la parte inferior del formulario, haz clic en **Enviar informe**. {% data variables.product.prodname_dotcom %} mostrará un mensaje que te indicará que se ha notificado a los mantenedores y que tienes un crédito pendiente para este aviso de seguridad.
- 
+ 
{% tip %}
- **Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
+ **Consejo:** Cuando se envía el informe, {% data variables.product.prodname_dotcom %} agrega automáticamente al informador de la vulnerabilidad como colaborador y como usuario acreditado en el aviso propuesto.
{% endtip %}
-1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge that private fork.
+1. Opcionalmente, haz clic en **Iniciar una bifurcación privada temporal** si quieres empezar a corregir el problema. Ten en cuenta que solo el mantenedor del repositorio puede combinar esa bifurcación privada.
- 
+ 
-The next steps depend on the action taken by the repository maintainer. For more information, see "[Managing privately reported security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)."
+Los pasos siguientes dependen de la acción realizada por el mantenedor del repositorio. Para obtener más información, consulta "[Administración de vulnerabilidades de seguridad notificadas de forma privada](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)".
diff --git a/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
index 8f8ea3d298..6505dbcdd9 100644
--- a/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
+++ b/translations/es-ES/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository security advisory
-intro: You can create a draft security advisory to privately discuss and fix a security vulnerability in your open source project.
+title: Creación de un aviso de seguridad de repositorio
+intro: Puedes crear un borrador de asesoría de seguridad para debatir en privado y arreglar una vulnerabilidad de seguridad en tu proyecto de código abierto.
redirect_from:
- /articles/creating-a-maintainer-security-advisory
- /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
@@ -15,31 +15,31 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Create repository advisories
+ms.openlocfilehash: 5c78a8b0c0a2d5085a876de2b0788ef093c4c6b1
+ms.sourcegitcommit: 74c60a4564bcc17e47b5a67941ac6d9fe13b6a5c
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/30/2022
+ms.locfileid: '148186159'
---
-
-Anyone with admin permissions to a repository can create a security advisory.
+Cualquier usuario con permisos de administrador puede crear un aviso de seguridad.
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-## Creating a security advisory
+## Creación de un aviso de seguridad
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **New draft security advisory** to open the draft advisory form. The fields marked with an asterisk are required.
- 
-1. Type a title for your security advisory.
-{% data reusables.repositories.security-advisory-edit-details %}
-{% data reusables.repositories.security-advisory-edit-severity %}
-{% data reusables.repositories.security-advisory-edit-cwe-cve %}
-{% data reusables.repositories.security-advisory-edit-description %}
-1. Click **Create draft security advisory**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Haz clic en **Nuevo borrador de asesoría de seguridad** para abrir el borrador del formulario de asesoría. Los campos marcados con un asterisco son obligatorios.
+ 
+1. Escribe un título para tu aviso de seguridad.
+{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
+1. Haga clic en **Create draft security advisory**.
+ 
-## Next steps
+## Pasos siguientes
-- Comment on the draft security advisory to discuss the vulnerability with your team.
-- Add collaborators to the security advisory. For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)."
-- Privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)."
-- Add individuals who should receive credit for contributing to the security advisory. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)."
-- Publish the security advisory to notify your community of the security vulnerability. For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
+- Comentar en el borrador de asesoría de seguridad para debatir sobre la vulnerabilidad con tu equipo.
+- Añadir colaboradores a la asesoría de seguridad. Para obtener más información, consulte "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
+- Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria. Para más información, vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)".
+- Agregar individuos que deberían recibir crédito por contribuir con la asesoría de seguridad. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)".
+- Publicar la asesoría de seguridad para notificar a tu comunidad sobre la vulnerabilidad de seguridad en cuestión. Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
index aeb477c475..b9ecb748a8 100644
--- a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a codespace for a repository
-intro: You can create a codespace for a branch in a repository to develop online.
+title: Creación de un codespace para un repositorio
+intro: Puedes crear un codespace para una rama en un repositorio para desarrollar en línea.
redirect_from:
- /github/developing-online-with-github-codespaces/creating-a-codespace
- /github/developing-online-with-codespaces/creating-a-codespace
@@ -14,95 +14,100 @@ topics:
- Fundamentals
- Developer
shortTitle: Create a codespace for a repo
+ms.openlocfilehash: 409c946feda4ffbd3d9ab615b6ea07fabee3f530
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188324'
---
+## Acerca de la creación de un codespace para un repositorio
-## About creating a codespace for a repository
+{% data reusables.codespaces.ways-to-create-a-codespace %} Usa las pestañas de este artículo a fin de mostrar instrucciones para cada una de estas formas de crear un codespace.
-{% data reusables.codespaces.ways-to-create-a-codespace %} Use the tabs in this article to display instructions for each of these ways of creating a codespace.
-
-{% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+{% data reusables.codespaces.starting-new-project-template %} Para obtener más información, consulta "[Creación de un codespace a partir de una plantilla](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)".
{% note %}
-**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[Using Codespaces in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
+**Nota**: Si usas un IDE de JetBrains, puedes usar la {% data variables.product.prodname_cli %} para crear un codespace. Después, puedes usar la aplicación de Puerta de enlace de JetBrains para abrir el codespace en un IDE de JetBrains. Para obtener más información, consulta "[Uso de codespaces en el IDE de JetBrains](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)".
{% endnote %}
-You can use {% data variables.product.prodname_github_codespaces %} on your personal {% data variables.product.prodname_dotcom_the_website %} account, with the quota of free use included each month for accounts on the Free and Pro plans. {% data reusables.codespaces.codespaces-continue-by-paying %}
+Puedes usar {% data variables.product.prodname_github_codespaces %} en tu cuenta personal del {% data variables.product.prodname_dotcom_the_website %}, con la cuota de uso gratuito incluido cada mes para las cuentas de los planes Gratis y Pro. {% data reusables.codespaces.codespaces-continue-by-paying %}
-Organizations can enable members and outside collaborators to create and use codespaces at the organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
+Las organizaciones pueden permitir que los miembros y colaboradores externos creen y usen codespaces a costa de la organización. Para más información, consulta ["Habilitación de {% data variables.product.prodname_github_codespaces %} para la organización](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)".
{% data reusables.codespaces.codespaces-are-personal %}
-If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch.
+Si creas un codespace desde un repositorio, este se asociará a una rama específica, que no puede estar vacía. Puedes crear más de un codespace por repositorio o incluso por rama.
{% data reusables.codespaces.you-can-see-all-your-codespaces %}
-### The codespace creation process
+### Proceso de creación de codespace
-When you create a codespace, a number of steps happen to create and connect you to your development environment:
+Cuando creas un codespace, se suscitan varios pasos para crear y conectarte a tu ambiente de desarrollo:
-- Step 1: VM and storage are assigned to your codespace.
-- Step 2: Container is created and your repository is cloned.
-- Step 3: You can connect to the codespace.
-- Step 4: Codespace continues with post-creation setup.
+- Paso 1: se le asignan una MV y almacenamiento a tu codespace.
+- Paso 2: Se crea el contenedor y se clona tu repositorio.
+- Paso 3: Puedes conectarte al codespace.
+- Paso 4: El codespace sigue con la configuración post-creación.
-For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
+Para más información sobre lo que sucede al crear un codespace, vea "[Análisis en profundidad](/codespaces/getting-started/deep-dive)".
-For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)."
+Para obtener más información sobre el ciclo de vida de un codespace, consulta "[Ciclo de vida del codespaces](/codespaces/getting-started/the-codespace-lifecycle)".
-If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+Si quiere usar enlaces de Git para el codespace, debe configurarlos mediante los [scripts de ciclo de vida `devcontainer.json`](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), como `postCreateCommand`, durante el paso 4. Como el contenedor de codespace se crea después de clonar el repositorio, cualquier [directorio de plantilla de Git](https://git-scm.com/docs/git-init#_template_directory) configurado en la imagen de contenedor no se aplicará al codespace. En su lugar, deben instalarse los ganchos después de que se crea el codespace. Para obtener más información sobre cómo usar `postCreateCommand`, consulta la referencia [`devcontainer.json`](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) en la documentación de {% data variables.product.prodname_vscode_shortname %}.
{% data reusables.codespaces.use-visual-studio-features %}
{% data reusables.codespaces.prebuilds-crossreference %}
-## Creating a codespace for a repository
+## Creación de un codespace para un repositorio
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create a codespace for.
+1. Debajo del nombre de repositorio, utiliza el menú desplegable "Rama" y selecciona aquella en la que quieras crear un codespace.
- 
+ 
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. Haz clic en el botón **{% octicon "code" aria-label="The code icon" %} Código** y , a continuación, haz clic en la pestaña **Codespaces**.
- 
+ 
- If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
+ Si los codespaces de este repositorio son facturables a una organización o a su empresa matriz, debajo del botón **Crear codespace en RAMA** verás un mensaje que indica quién pagará el codespace.
-1. Create your codespace, either using the default options, or after configuring advanced options:
+1. Crea el codespace, ya sea con las opciones predeterminadas o después de configurar las opciones avanzadas:
- * **Use the default options**
+ * **Uso de las opciones predeterminadas**
- To create a codespace using the default options, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). Alternatively, if you don't currently have any codespaces for this repository, you can click **Create codespace on BRANCH**.
+ Para crear un codespace con las opciones predeterminadas, haz clic en el signo más ({% octicon "plus" aria-label="The plus icon" %}). Como alternativa, si actualmente no tienes ningún codespace para este repositorio, puedes hacer clic en **Crear codespace en RAMA**.
- * **Configure options**
+ * **Configurar opciones**
- To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file:
+ Para configurar opciones avanzadas para el codespace, como un tipo de máquina diferente o un archivo determinado `devcontainer.json`:
- 1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab and select **New with options**.
+ 1. Haz clic en los puntos suspensivos ( **...** ) de la parte superior derecha de la pestaña **Codespaces** y selecciona **Nuevo con opciones**.
- 
+ 
- 1. On the options page for your codespace, choose your preferred options from the dropdown menus.
+ 1. En la página de opciones del codespace, elige tus opciones preferidas en los menús desplegables.
- 
+ 
{% note %}
- **Notes**
+ **Notas**
- * You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
- * The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
- * For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
- * For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+ * Puedes marcar la página de opciones para poder crear rápidamente un codespace para este repositorio y esta rama.
+ * La página [https://github.com/codespaces/new](https://github.com/codespaces/new) proporciona una manera rápida de crear un codespace para cualquier repositorio y rama. Puedes acceder a esta página rápidamente escribiendo `codespace.new` en la barra de direcciones del explorador.
+ * Para obtener más información sobre el archivo `devcontainer.json`, consulta "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)".
+ * Para obtener más información, consulta "[Cambio del tipo de máquina para el codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)".
* {% data reusables.codespaces.codespaces-machine-type-availability %}
{% endnote %}
- 1. Click **Create codespace**.
+ 1. Haga clic en **Crear codespace**.
{% endwebui %}
@@ -116,30 +121,30 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
{% data reusables.cli.cli-learn-more %}
-To create a new codespace, use the `gh codespace create` subcommand.
+Para crear un codespace, use el subcomando `gh codespace create`.
```shell
gh codespace create
```
-You are prompted to choose a repository. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
+Se te pedirá que elijas un repositorio. Si los codespaces de este repositorio son facturables a una organización o a su empresa matriz, se muestra un mensaje que indica quién pagará el codespace. Luego, se te pedirá que elijas una rama, un archivo de configuración de contenedor de desarrollo (si hay más de uno disponible) y un tipo de máquina (si hay más de uno disponible).
-Alternatively, you can use flags to specify some or all of the options:
+Como alternativa, puedes utilizar marcadores para especificar algunas o todas las opciones:
```shell
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
```
-In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
+En este ejemplo, reemplaza `owner/repo` por el identificador del repositorio. Reemplace a `branch` por el nombre de la rama o el hash SHA completo de la confirmación que quiera que se extraiga inicialmente en el codespace. Si usa la marca `-r` sin la marca `b`, el codespace se crea a partir de la rama predeterminada.
-Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+Reemplaza `path` por la ruta de acceso al archivo de configuración de contenedor de desarrollo que desees usar para el nuevo codespace. Si omites este marcador y hay más de un tipo de archivo de contenedor de desarrollo disponible, se te pedirá que lo elijas en una lista. Para obtener más información sobre el archivo de configuración de contenedor de desarrollo, consulta "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)".
-Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
+Reemplace `machine-type` por un identificador válido para un tipo de máquina disponible. Los identificadores son cadenas como: `basicLinux32gb` y `standardLinux32gb`. El tipo de máquinas que están disponibles depende del repositorio, la cuenta personal y la ubicación. Si ingresas un tipo de máquina no disponible o inválido, los tipos disponibles se mostrarán en el mensaje de error. Si omites este marcador y hay más de un tipo de máquina disponible, se te pedirá elegirlo de una lista.
-For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
+Para obtener los detalles completos de las opciones de este comando, consulta [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_create).
{% endcli %}
-## Further reading
-- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
-- "[Adding an 'Open in {% data variables.product.prodname_github_codespaces %}' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
+## Información adicional
+- "[Apertura de un codespace existente](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
+- "[Incorporación de un distintivo 'Abrir en {% data variables.product.prodname_github_codespaces %}'](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
index 842a20e971..3d7f0e6dfd 100644
--- a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
@@ -1,6 +1,6 @@
---
-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.
+title: Creación de un codespace a partir de una plantilla
+intro: 'Si vas a iniciar un nuevo proyecto, puedes crear un codespace a partir de una plantilla en blanco o elegir una plantilla especialmente diseñada para el tipo de trabajo que deseas realizar.'
versions:
fpt: '*'
ghec: '*'
@@ -11,92 +11,95 @@ topics:
- Developer
shortTitle: Create a codespace from a template
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 9e7ee0d110e962fa755f5f57cc70bc3cab341808
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188316'
---
+## Acerca de las plantillas para {% data variables.product.prodname_github_codespaces %}
-## 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.
+Si vas a iniciar un nuevo proyecto, puedes crear un codespace a partir de una plantilla para empezar con el trabajo de desarrollo rápidamente. Podrás trabajar en el proyecto en un entorno de desarrollo basado en la nube, guardar los archivos en la nube y publicar el trabajo en un nuevo repositorio remoto que puedes compartir con otros usuarios o clonar en la máquina local.
{% 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)."
+**Nota**: Los codespaces creados a partir de una plantilla, no a partir de un repositorio, siempre se facturan a tu cuenta personal. Para más información, consulta "[Acerca de la facturación de {% 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)."
+Puedes empezar con una plantilla en blanco, elegir entre las plantillas que mantiene {% data variables.product.company_short %} para tecnologías populares como React o Jupyter Notebook, o iniciar un codespace desde cualquier repositorio de plantilla en {% data variables.product.prodname_dotcom %}. Con una plantilla en blanco, empezarás con un directorio vacío, con acceso a los recursos de proceso basados en la nube y a las herramientas, lenguajes y entornos en tiempo de ejecución que vienen preinstalados con la imagen de codespace predeterminada. Con otras plantillas, obtendrás archivos de inicio para la tecnología con la que estás trabajando y, normalmente, algunos archivos adicionales, como un archivo Léame, un archivo `.gitignore` y archivos de configuración de contenedor de desarrollo que contienen algunas opciones de configuración de entorno personalizadas. Para obtener más información sobre los contenedores de desarrollo y la imagen predeterminada, consulta "[Introducción a los contenedores de desarrollo](/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.
+Por ejemplo, si creas un codespace a partir de la plantilla de React de {% data variables.product.company_short %}, llegarás a un área de trabajo que contiene archivos de plantilla para una aplicación sencilla, como `index.js`, `app.js` y `package.json`. Poco después de que se abra el codespace, se iniciará automáticamente un servidor de desarrollo y podrás ver la aplicación en ejecución en una pestaña sencilla del explorador en el cliente web de {% data variables.product.prodname_vscode_shortname %}.
-
+
-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.
+Los archivos y la configuración incluidos en las plantillas se definen en repositorios de plantilla. El repositorio de plantilla se clona en el codespace al crear el codespace. Después, se corta el vínculo y el codespace no se vincula a un repositorio remoto hasta que publicas en uno.
{% 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)."
+**Sugerencia:** Para ayudar a los usuarios a empezar a trabajar con el marco, la biblioteca u otro proyecto, puedes configurar un repositorio de plantilla para utilizarlo con {% data variables.product.prodname_github_codespaces %}. Para obtener más información, consulta "[Configuración de un repositorio de plantilla para {% 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
+## Creación de un codespace a partir de una plantilla de {% data variables.product.company_short %}
-Templates maintained by {% data variables.product.company_short %}, including the blank template, are available from the "Your codespaces" page.
+Las plantillas que mantiene {% data variables.product.company_short %}, incluida la plantilla en blanco, están disponibles en la página "Tus codespaces".
-{% 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.
+{% data reusables.codespaces.your-codespaces-procedure-step %} {% data reusables.codespaces.view-all-templates-step %}
+1. Opcionalmente, para ver el repositorio de plantilla que contiene los archivos de una plantilla, haz clic en el nombre de la plantilla.
- 
+ 
-1. Under the template you want to launch, click **Use this template**.
+1. En la plantilla que deseas iniciar, haz clic en **Usar esta plantilla**.
- 
+ 
{% data reusables.codespaces.template-codespaces-default-editor %}
-## Creating a codespace from a template repository
+## Creación de un codespace a partir de un repositorio de plantilla
-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)."
+Puedes crear un codespace a partir de cualquier repositorio de plantilla y, a continuación, publicar tu trabajo en un nuevo repositorio cuando estés a punto. Para obtener más información sobre los repositorios de plantilla, consulta "[Crear un repositorio desde una plantilla](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates)".
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.codespaces.open-template-in-codespace-step %}
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.codespaces.open-template-in-codespace-step %}
{% note %}
- **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)."
+ **Nota:** Si eres el responsable del mantenimiento del repositorio de plantilla y deseas confirmar los cambios en el propio repositorio de plantilla, debes crear un codespace a partir de la lista desplegable **{% octicon "code" aria-label="The code icon" %} Código**. Para obtener más información, consulta "[Creación de un codespace para un repositorio](/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 %}
+## Publicación en un repositorio en {% data variables.product.product_name %}
{% data reusables.codespaces.about-publishing-templates %}
-### Publishing from {% data variables.product.prodname_vscode_shortname %}
+### Publicación desde {% 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:
+Cuando se publica un codespace, tienes acceso a una mayor variedad de opciones para personalizar tu experiencia de {% data variables.product.prodname_github_codespaces %}. Por ejemplo, se puede:
-- 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)").
+- Cambiar el tipo de máquina del codespace para asegurarse de que se usan los recursos adecuados para el trabajo que se está realizando (consulta "[Cambiar el tipo de máquina de tu codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)").
+- Permitir que {% data variables.product.prodname_dotcom %} use automáticamente GPG para firmar las confirmaciones que se realizan en el codespace (consulta "[Administración de la comprobación de GPG para {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)").
+- Compartir secretos cifrados con el codespace (consulta "[Administrar secretos cifrados para tus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)").
-### Publishing from {% data variables.product.prodname_dotcom_the_website %}
+### Publicación desde {% 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.
+Puedes publicar un codespace no publicado desde la página "Tus codespaces" en {% data variables.product.prodname_dotcom_the_website %}. Esto resulta útil si deseas publicar un codespace que no tienes abierto actualmente en el explorador. Si lo haces, el trabajo se conservará en un repositorio, pero no habrá un vínculo entre el codespace existente y el nuevo repositorio. Sin embargo, puedes ir al nuevo repositorio y crear un codespace desde allí, y este codespace estará conectado al repositorio.
{% data reusables.codespaces.your-codespaces-procedure-step %}
-1. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**.
+1. Junto al codespace no publicado, haz clic en los puntos suspensivos ( **...** ) y selecciona **Publicar en un nuevo repositorio**.
- 
-1. Choose a name for your new repository, set it as **Public** or **Private**, and click **Create repository**.
+ 
+1. Elige un nombre para el nuevo repositorio, establécelo como **Público** o **Privado** y haz clic en **Crear repositorio**.
- 
-1. Optionally, to view the new repository, click **See repository**.
+ 
+1. Opcionalmente, para ver el nuevo repositorio, haz clic en **Ver repositorio**.
-## Further reading
+## Información adicional
-- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)"
-- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)"
-- "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
\ No newline at end of file
+- "[Creación de un codespace para un repositorio](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)"
+- "[Ciclo de vida de un codespace](/codespaces/getting-started/the-codespace-lifecycle)"
+- "[Utilizar el control de código fuente en tu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
index c7605e66fc..438bf40045 100644
--- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
+++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Configuring prebuilds
+title: Configuración de precompilaciones
shortTitle: Configure prebuilds
-intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
+intro: Puedes configurar tu proyecto para precompilar un codespace automáticamente cada vez que insertas un cambio en el repositorio.
versions:
fpt: '*'
ghec: '*'
@@ -10,106 +10,111 @@ topics:
- Codespaces
- Set up
permissions: People with admin access to a repository can configure prebuilds for the repository.
+ms.openlocfilehash: dbb355e150695f27d1d6a7fa51eccc33a0ebde4f
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159121'
---
+Puedes configurar una configuración de precompilación para la combinación de una rama específica del repositorio con un archivo de configuración de contenedor de desarrollo específico.
-You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file.
+Las ramas creadas a partir de una rama primaria habilitada previamente para la compilación normalmente también obtendrán precompilaciones para la misma configuración de contenedor de desarrollo. El motivo es que las precompilaciones para ramas secundarias que usan la misma configuración de contenedor de desarrollo que la rama primaria es, en su mayor parte, idéntica, por lo que los desarrolladores también se pueden beneficiar de tiempos de creación de codespaces más rápidos en esas ramas. Para más información, vea "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)".
-Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because prebuilds for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+Normalmente, al configurar precompilaciones para una rama, estarán disponibles para varios tipos de equipo. Pero si el repositorio es mayor de 32 GB, las precompilaciones no estarán disponibles para los tipos de máquina de 2 y 4 núcleos, ya que el almacenamiento que proporcionan está limitado a 32 GB.
-Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB.
+## Requisitos previos
-## Prerequisites
+Los precompilaciones se crean con {% data variables.product.prodname_actions %}. Como resultado, {% data variables.product.prodname_actions %} debe estar habilitado para el repositorio para el que vas a configurar las precompilaciones. Para más información, vea "[Administración de la configuración de {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)".
-Prebuilds are created using {% data variables.product.prodname_actions %}. As a result, {% data variables.product.prodname_actions %} must be enabled for the repository for which you are configuring prebuilds. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)."
-
-## Configuring prebuilds
+## Configuración de precompilaciones
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
+1. En la sección "Configuración de la precompilación" de la página, haz clic en **Configurar precompilación**.
- 
+ 
-1. Choose the branch for which you want to set up prebuilds.
+1. Elige la rama para la que quieras configurar las precompilaciones.
- 
+ 
{% note %}
- **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
+ **Nota**: Las ramas creadas a partir de una rama base habilitada previamente para la compilación normalmente también obtendrán precompilaciones para la misma configuración de contenedor de desarrollo. Por ejemplo, si habilita las precompilaciones para un archivo de configuración de contenedor de desarrollo en la rama predeterminada del repositorio, las ramas basadas en la predeterminada también obtendrán precompilaciones en la mayoría de los casos para la misma configuración de contenedor de desarrollo.
{% endnote %}
-1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
+1. Opcionalmente, en el menú desplegable **Archivo de configuración** que se muestra, elige el archivo de configuración de `devcontainer.json` que quieres usar para esta plantilla de precompilaciones. Para obtener más información, consulte "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)".
- 
+ 
-1. Choose how you want to automatically trigger prebuild updates.
+1. Elige cómo quieres desencadenar automáticamente las actualizaciones de la precompilación.
- * **Every push** (the default setting) - With this setting, prebuilds will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies.
- * **On configuration change** - With this setting, prebuilds will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The {% data variables.product.prodname_actions %} workflow that updates the prebuilds will run less often, so this option will use fewer {% data variables.product.prodname_actions %} minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created.
- * **Scheduled** - With this setting, you can have your prebuilds updated on a custom schedule that's defined by you. This can reduce consumption of {% data variables.product.prodname_actions %} minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes.
+ * **Todas las inserciones** (configuración predeterminada): con esta configuración, las precompilaciones se actualizarán en cada inserción realizada en la rama especificada. Esto garantizará que los codespaces generados a partir de una precompilación siempre contengan la configuración de codespace más reciente, incluidas las dependencias agregadas o actualizadas recientemente.
+ * **Al cambiar la configuración**: con esta opción, las precompilaciones se actualizarán cada vez que se actualicen los archivos de configuración asociados para un repositorio y una rama determinados. Esto garantiza que los cambios en los archivos de configuración del contenedor de desarrollo para el repositorio se usan cuando se genera un codespace a partir de una precompilación. El flujo de trabajo de {% data variables.product.prodname_actions %} que actualiza los precompilaciones se ejecutará con menos frecuencia, por lo que esta opción usará menos minutos de {% data variables.product.prodname_actions %}. Pero esta opción no garantizará que los codespaces siempre incluyan dependencias agregadas o actualizadas recientemente, por lo que es posible que tengan que agregarse o actualizarse manualmente después de crear un codespace.
+ * **Programado:** con esta configuración, podrás actualizar la precompilación en una programación personalizada que definas. Esto puede reducir el consumo de minutos de {% data variables.product.prodname_actions %}; sin embargo, con esta opción, se pueden crear codespaces que no usen los cambios más recientes en la configuración del contenedor de desarrollo.
- 
+ 
-1. Optionally, select **Reduce prebuild available to only specific regions** to create prebuilds only in specified regions. Select the regions in which you want prebuilds to be available.
+1. Opcionalmente, selecciona **Reducir precompilación disponible para solo regiones específicas** para crear precompilaciones solo en regiones especificadas. Selecciona las regiones en las que quieres que estén disponibles las precompilaciones.
- By default, prebuilds are created in all of the available regions, incurring storage charges per prebuild.
+ De forma predeterminada, las precompilaciones se crean en todas las regiones disponibles, lo que conlleva cargos de almacenamiento por precompilación.
- 
+ 
{% note %}
- **Notes**:
- * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
- * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
+ **Notas**:
+ * La compilación previa en cada región incurre en cargos de almacenamiento individuales. Por tanto, solo debe habilitar las precompilaciones para las regiones en las que sabe que se van a usar. Para más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)".
+ * Los desarrolladores pueden establecer su región predeterminada para {% data variables.product.prodname_github_codespaces %}, lo que te permite habilitar precompilaciones para menos regiones. Para más información, consulta "[Configuración de la región predeterminada para {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)".
{% endnote %}
-1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved.
+1. Opcionalmente, en **plantilla de precompilación**, se establece el número de versiones que se conservarán. Puedes especificar cualquier número entre 1 y 5. El número predeterminado de versiones guardadas es 2, lo que significa que solo se guardan la más reciente y la versión anterior.
- 
+ 
- Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. This setting allows you to set the number of retained versions to a level that is appropriate for your needs.
+ En función de la configuración del desencadenador de precompilaciones, la precompilación podría cambiar con cada inserción o en cada cambio de configuración del contenedor de desarrollo. Conservar las versiones anteriores de las precompilaciones permite crear una precompilación a partir de una confirmación anterior con una configuración de contenedor de desarrollo diferente a la de la precompilación actual. Esta configuración permite establecer el número de versiones retenidas en un nivel adecuado para tus necesidades.
- If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration.
+ Si estableces el número de versiones de precompilaciones para guardar en 1, {% data variables.product.prodname_github_codespaces %} solo guardará la más reciente y se eliminará la versión anterior cada vez que se actualice la plantilla. Esto significa que no obtendrás un codespace precompilado si vuelves a una configuración de contenedor de desarrollo anterior.
- There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+ Hay un costo de almacenamiento asociado a cada versión de precompilación que se conserva. Por ejemplo, si vas a generar precompilaciones en 4 regiones y conservas 2 versiones, se te cobrará por el almacenamiento de hasta 8 precompilaciones. Para más información sobre la facturación, consulta "[Acerca de la facturación de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)".
-1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation.
+1. Opcionalmente, agrega usuarios o equipos a quienes notificar cuando se produzca un error en la ejecución del flujo de trabajo de precompilación de esta configuración. Para empezar, puedes escribir un nombre de usuario, un nombre de equipo o un nombre completo y, luego, hacer clic en ellos cuando aparezcan para agregarlos a la lista. Los usuarios o equipos que agregues recibirán un correo electrónico cuando se produzcan errores de precompilación, con un vínculo a los registros de ejecución del flujo de trabajo para que puedan investigarlo más a fondo.
- 
+ 
-1. Optionally, at the bottom of the page, click **Show advanced options**.
+1. Opcionalmente, en la parte inferior de la página, haz clic en **Mostrar opciones avanzadas**.
- 
+ 
- In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
+ En la sección "Opciones avanzadas", si seleccionas **Deshabilitar optimización de precompilación**, los codespaces se crearán sin un precompilado si se ha producido un error en el flujo de trabajo de precompilación más reciente o si se está ejecutando actualmente. Para obtener más información, consulta "[Solución de problemas anterior a la compilación](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)".
-1. Click **Create**.
+1. Haga clic en **Crear**.
{% data reusables.codespaces.prebuilds-permission-authorization %}
-After you create a prebuild configuration it is listed on the {% data variables.product.prodname_github_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuilds in the regions you specified, based on the branch and dev container configuration file you selected.
+Después de crear una configuración de precompilación, esta aparece en la página {% data variables.product.prodname_github_codespaces %} de la configuración del repositorio. Se pone en cola un flujo de trabajo de {% data variables.product.prodname_actions %} y, después, se ejecuta para crear precompilaciones en las regiones especificadas, en función de la rama y el archivo de configuración de contenedor de desarrollo seleccionados.
-
+
-For information about editing and deleting prebuild configurations, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)."
+Para obtener información sobre cómo editar y eliminar configuraciones de precompilación, consulta "[Administración de precompilaciones](/codespaces/prebuilding-your-codespaces/managing-prebuilds)".
-## Configuring environment variables
+## Configurar variables de ambiente
-To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)."
+Para permitir que el proceso de precompilación acceda a las variables de entorno necesarias para crear el entorno de desarrollo, puede establecerlas como secretos de repositorio de {% data variables.product.prodname_codespaces %}, o bien como secretos de organización de {% data variables.product.prodname_codespaces %}. Para más información, vea "[Adición de secretos para un repositorio](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)" y "[Adición de secretos para una organización](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)".
-Secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces.
+Los secretos que crees de esta manera serán accesibles para cualquiera que cree un codespace desde este repositorio. Si no quiere este comportamiento, también puede establecer el secreto `CODESPACES_PREBUILD_TOKEN`. El secreto `CODESPACES_PREBUILD_TOKEN` solo se usa para la precompilación y su valor no es accesible en los codespaces de los usuarios.
-Prebuilds cannot use any user-level secrets while building your environment, because these are not available until after the codespace has been created.
+Las precompilaciones no pueden usar ningún secreto de nivel de usuario al compilar el entorno, ya que no están disponibles hasta después de crear el codespace.
-## Configuring time-consuming tasks to be included in the prebuild
+## Configuración de tareas que requieren mucho tiempo para incluirse en la precompilación
-You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)."
+Puede usar los comandos `onCreateCommand` y `updateContentCommand` en `devcontainer.json` para incluir procesos lentos como parte de la creación de la precompilación. Para más información, consulta la documentación de {% data variables.product.prodname_vscode %} "[referencia de devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)".
-`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at creation of the prebuild and at subsequent updates to it. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update.
+`onCreateCommand` solo se ejecuta una vez, cuando se crea la precompilación, mientras que `updateContentCommand` se ejecuta en la creación de la precompilación y en las actualizaciones de plantilla posteriores a esta. Las compilaciones incrementales se deben incluir en `updateContentCommand`, ya que representan el origen del proyecto y deben incluirse para cada actualización de precompilación.
-## Further reading
+## Información adicional
-- "[Allowing a prebuild to access other repositories](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)"
-- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
+- "[Permiso para que una precompilación acceda a otros repositorios](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)"
+- "[Solución de problemas de precompilaciones](/codespaces/troubleshooting/troubleshooting-prebuilds)"
diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
index 36e4e0ae51..75186abfdc 100644
--- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
+++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
@@ -1,7 +1,7 @@
---
-title: Adding an "Open in GitHub Codespaces" badge
+title: Adición de un distintivo "Abrir en GitHub Codespaces"
shortTitle: Add a Codespaces badge
-intro: You can add a badge to a Markdown file in your repository which people can click to create a codespace.
+intro: Puedes agregar un distintivo a un archivo Markdown en el repositorio en el que la gente puede hacer clic para crear un codespace.
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -10,50 +10,55 @@ type: how_to
topics:
- Codespaces
- Set up
+ms.openlocfilehash: c69a815501f5943a56d32af3e58cd7850a69588b
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158785'
---
+## Información general
-## Overview
+Agregar un distintivo "Abrir en {% data variables.product.prodname_github_codespaces %}" a un archivo de Markdown proporciona a la gente una manera fácil de crear un codespace para el repositorio.
-Adding an "Open in {% data variables.product.prodname_github_codespaces %}" badge to a Markdown file gives people an easy way to create a codespace for your repository.
+
-
+Al crear un distintivo, puedes elegir opciones de configuración específicas para el codespace que creará el distintivo.
-When you create a badge you can choose specific configuration options for the codespace that the badge will create.
+Cuando la gente haga clic en el distintivo, se les dirigirá a la página de opciones avanzadas para la creación del codespace, con las opciones que elegiste preseleccionadas. Para obtener más información sobre la página de opciones avanzadas, consulta "[Creación de un codespace para un repositorio](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)".
-When people click the badge they'll be taken to the advanced options page for codespace creation, with the options you chose preselected. For more information about the advanced options page, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+En la página opciones avanzadas, los usuarios pueden cambiar la configuración preseleccionada si es necesario y, a continuación, hacer clic en **Crear codespace**.
-From the advanced options page, users can change the preselected settings if required, then click **Create codespace**.
-
-## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge
+## Creación de un distintivo "Abrir en {% data variables.product.prodname_github_codespaces %}"
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create the badge for.
+1. Debajo del nombre del repositorio, usa el menú desplegable "Rama" y selecciona aquella en la que quieras crear el distintivo.
- 
+ 
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. Haz clic en el botón **{% octicon "code" aria-label="The code icon" %} Código** y , a continuación, haz clic en la pestaña **Codespaces**.
- 
+ 
-1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab, then click **New with options**.
+1. Haz clic en los puntos suspensivos ( **…** ) en la parte superior derecha de la pestaña **Codespaces** y, luego, haz clic en **Nuevo con opciones**.
- 
+ 
-1. On the advanced options page for codespace creation, select the values you want to be preselected in each field.
+1. En la página opciones avanzadas para la creación del codespace, selecciona los valores que deseas que se preseleccionen en cada campo.
- 
+ 
-1. Copy the URL from the browser's address bar.
-1. Add the following Markdown to, for example, the `README.md` file of your repository:
+1. Copie la dirección URL de la barra de direcciones del explorador.
+1. Agrega el siguiente markdown a, por ejemplo, el `README.md` archivo del repositorio:
```Markdown{:copy}
[](COPIED-URL)
```
- For example:
+ Por ejemplo:
```Markdown
[](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2)
```
- In the above example, `0000000` will be the reference number of your repository. The other details in the URL are determined by the values you selected in the fields on the advanced options page.
+ En el ejemplo anterior, `0000000` será el número de referencia del repositorio. Los demás detalles de la dirección URL vienen determinados por los valores seleccionados en los campos de la página de opciones avanzadas.
diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index 25a547449e..c7a648fbf3 100644
--- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Troubleshooting prebuilds
+title: Solución de problemas de precompilaciones
shortTitle: Codespaces prebuilds
-intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds.
+intro: Puedes usar precompilaciones para acelerar la creación de codespaces. En este artículo se proporcionan los pasos para la solución de problemas comunes con las precompilaciones.
versions:
fpt: '*'
ghec: '*'
@@ -9,86 +9,91 @@ type: reference
topics:
- Codespaces
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: b8c45f9eae6094b78026d055ebea27c3748a8681
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158889'
---
+Para obtener más información sobre las precompilaciones de {% data variables.product.prodname_github_codespaces %}, consulta "[Precompilación de codespaces](/codespaces/prebuilding-your-codespaces)".
-For more information about {% data variables.product.prodname_github_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)."
+## ¿Quiere comprobar si un codespace se ha creado a partir de una precompilación?
-## Checking whether a codespace was created from a prebuild?
+Al crear un codespace, puedes elegir el tipo de la máquina virtual que quieres usar. Si hay disponible un precompilado para el tipo de máquina virtual, "{% octicon "zap" aria-label="The zap icon" %} Precompilación lista" se muestra junto a él.
-When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it.
+
-
+Si tienes la preferencia del editor de {% data variables.product.prodname_github_codespaces %} establecida en "{% data variables.product.prodname_vscode %} para la web", en la página "Configuración del codespace" se mostrará el mensaje "Se ha encontrado un codespace precompilado" si se usa una precompilación.
-If you have your {% data variables.product.prodname_github_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used.
+
-
+Del mismo modo, si la preferencia del editor es "{% data variables.product.prodname_vscode_shortname %}", el terminal integrado contendrá el mensaje "Estás en un codespace precompilado definido por la configuración de precompilación para el repositorio" al crear un codespace. Para más información, consulta "[Configuración del editor predeterminado para {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)".
-Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
-
-After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal:
+Después de crear un codespace, puede comprobar si se ha creado a partir de una precompilación si ejecuta el comando {% data variables.product.prodname_cli %} siguiente en el terminal:
```shell{:copy}
gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild
```
-This returns `true` if the codespace was created using a prebuild.
+Esto devuelve `true` si el codespace se ha creado mediante una precompilación.
-Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild:
+Como alternativa, si {% data variables.product.prodname_cli %} (`gh`) no está instalado, puede usar el comando siguiente, que devuelve `createFromPrebuild` si el codespace se ha creado a partir de una precompilación:
```shell{:copy}
cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME'
```
-## The "Prebuild Ready" label is sometimes missing
+## En ocasiones falta la etiqueta "Prebuild Ready" (Listo para precompilación)
-You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
+Es posible que observe que, en ocasiones, al crear un codespace desde una rama habilitada para la precompilación, la etiqueta "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" (Listo para precompilación) no se muestra en el cuadro de diálogo para elegir un tipo de máquina. Esto significa que las precompilaciones no están disponibles actualmente.
-By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+De forma predeterminada, cada vez que se inserta en una rama habilitada para precompilación, se actualiza la precompilación. Si la inserción implica un cambio en el contenedor de desarrollo, mientras la actualización está en curso, la etiqueta "{% octicon "zap" aria-label="The zap icon" %} Precompilación lista" se quita de la lista de tipos de máquina. Durante este tiempo, todavía puede crear codespace sin una precompilación. Si es necesario, puede reducir las ocasiones en las que las precompilaciones no están disponibles para un repositorio estableciendo que la precompilación se actualice solo cuando realice un cambio en los archivos de configuración del contenedor de desarrollo o solo en una programación personalizada. Para obtener más información, consulta "[Configuración de precompilaciones](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)".
-If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
+Si la rama no está habilitada específicamente para las precompilaciones, todavía se puede beneficiar de ellas si se bifurca desde una rama habilitada para la precompilación. Pero si la configuración del contenedor de desarrollo se cambia en la rama, de modo que no sea la mismo que la de la rama base, las precompilaciones ya no estarán disponibles en la rama.
-Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch:
+Estos son los aspectos para comprobar si la etiqueta "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" (Listo para precompilación) no se muestra para una rama determinada:
-* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this.
-* Confirm that the prebuild configuration includes your region.
-* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
-* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
+* Confirme que existe una configuración de precompilación para esta rama. Si no es administrador del repositorio, tendrá que ponerse en contacto con uno para confirmarlo.
+* Confirme que la configuración de precompilación incluye la región.
+* Compruebe si se ha insertado recientemente un cambio de la configuración del contenedor de desarrollo en la rama habilitada para la precompilación. En caso afirmativo, normalmente tendrás que esperar hasta que se complete el flujo de trabajo de precompilación para esta inserción antes de que los precompilaciones vuelvan a estar disponibles.
+* Si no se han realizado cambios de configuración recientemente, vaya a la pestaña **Actions** (Acciones) del repositorio, haga clic en **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** (Precompilaciones) en la lista de flujos de trabajo y compruebe que las ejecuciones de flujo de trabajo de precomplilación para la rama sean correctas. Si se ha producido un error en las ejecuciones más recientes de un flujo de trabajo y una o varias de estas ejecuciones con errores contenían cambios en la configuración del contenedor de desarrollo, no habrá precompilaciones disponibles para la rama asociada.
-## Some resources cannot be accessed in codespaces created using a prebuild
+## No se puede acceder a algunos recursos en codespaces creados mediante una precompilación
-If the `devcontainer.json` configuration file for a prebuild configuration specifies that permissions for access to other repositories are required, then the repository administrator is prompted to authorize these permissions when they create or update the prebuild configuration. If the administrator does not grant all of the requested permissions there's a chance that problems may occur in the prebuild, and in codespaces created from this prebuild. This is true even if the user who creates a codespace based on this prebuild _does_ grant all of the permissions when they are prompted to do so.
+Si el archivo de configuración de `devcontainer.json` de una configuración de precompilación especifica que se requieren permisos para el acceso a otros repositorios, se pedirá al administrador del repositorio que autorice estos permisos cuando cree o actualice la configuración de precompilación. Si el administrador no concede todos los permisos solicitados, existe la posibilidad de que se produzcan problemas en la precompilación y en los codespaces creados a partir de la misma. Esto es cierto incluso si el usuario que crea un codespace basado en esta precompilación _concede_ todos los permisos cuando se le pide que lo haga.
-## Troubleshooting failed workflow runs for prebuilds
+## Solución de problemas de ejecuciones de flujo de trabajo con errores para precompilaciones
-### Increasing the {% data variables.product.prodname_actions %} spending limit
+### Aumento del límite de gasto de {% data variables.product.prodname_actions %}
-Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+Las precompilaciones se crean y actualizan con {% data variables.product.prodname_actions %}. Se producirá un error en los flujos de trabajo de precompilación si has usado todos los minutos de {% data variables.product.prodname_actions %} y has alcanzado el límite de gasto. Si esto ocurre, puedes aumentar el límite de gasto de {% data variables.product.prodname_actions %} para permitir que se ejecuten los flujos de trabajo. Para obtener más información, consulta "[Administración del límite de gasto para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)".
-### Authorizing access permissions
+### Autorización de permisos de acceso
-If the `devcontainer.json` configuration file for a prebuild configuration is updated to specify that permissions for access to other repositories are required, and a repository administrator has not been prompted to authorize these permissions for the prebuild configuration, then the prebuild workflow may fail. Try updating the prebuild configuration, without making any changes. If, when you click **Update**, the authorization page is displayed, check that the requested permissions are appropriate and, if so, authorize the request. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" and "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)."
+Si se actualiza el archivo de configuración de `devcontainer.json` de una configuración de precompilación para especificar que se requieren permisos para el acceso a otros repositorios y no se ha solicitado a un administrador de repositorio que autorice estos permisos para la configuración de precompilación, es posible que se produzca un error en el flujo de trabajo de precompilación. Prueba a actualizar la configuración de precompilación sin realizar ningún cambio. Si, al hacer clic en **Actualizar**, se muestra la página de autorización, comprueba que los permisos solicitados son adecuados y, si es así, autoriza la solicitud. Para obtener más información, consulta "[Administración de precompilaciones](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" y "[Administración del acceso a otros repositorios dentro del codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)".
-If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
+Si se produce un error en la ejecución del flujo de trabajo para una configuración de precompilación, puedes deshabilitar temporalmente la configuración de precompilación mientras investigas. Consulta "[Administración del estado](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)" para obtener más información.
-### Preventing out-of-date prebuilds being used
+### Prevención del uso de precompilaciones obsoletas
-By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
+De forma predeterminada, si se ha producido un error en el flujo de trabajo de precompilación más reciente, se usará una precompilación anterior para la misma combinación de repositorio, rama y archivo de configuración `devcontainer.json` para crear espacios de código. Este comportamiento se denomina "optimización de precompilación".
-We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
+Se recomienda mantener habilitada la optimización de precompilación, ya que ayuda a garantizar que los codespaces sigan pudiéndose crear rápidamente si no hay disponible una precompilación actualizada. Aun así, como administrador del repositorio, puedes deshabilitar la optimización de precompilación si tienes problemas porque los codespaces precompilados están detrás del estado actual de la rama. En caso de que deshabilites la optimización de precompilación, los codespaces para la combinación pertinente de repositorio, rama y archivo `devcontainer.json` se crearán sin una precompilación si el flujo de trabajo de precompilación más reciente ha generado un error o se está ejecutando actualmente.
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
+1. A la derecha de la configuración de precompilación afectada, selecciona los puntos suspensivos ( **…** ) y haz clic en **Editar**.
- 
-1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
+ 
+1. Desplázate hasta la parte inferior de la página "Editar configuración" y haz clic en **Mostrar opciones avanzadas**.
- 
-1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
+ 
+1. Si sabes con seguridad que quieres deshabilitar la configuración predeterminada, selecciona **Deshabilitar la optimización de precompilación**.
- 
-1. To save your change, click **Update**.
+ 
+1. Para guardar el cambio, haz clic en **Actualizar**.
-## Further reading
+## Información adicional
-- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
-- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
+- "[Configuración de precompilaciones](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
+- "[Administración de precompilaciones](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
diff --git a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 32f4cbe7b5..8f7905ac45 100644
--- a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -1,6 +1,6 @@
---
-title: Creación de un archivo predeterminado de mantenimiento de la comunidad
-intro: 'Puedes crear archivos predeterminados para la salud de la comunidad, como CONTRIBUTING (Contribuciones) y CODE_OF_CONDUCT (Código de conducta). Los archivos predeterminados se utilizarán para cualquier repositorio que pertenezca a la cuenta que no contiene su propio archivo de este tipo.'
+title: Creating a default community health file
+intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
redirect_from:
- /articles/creating-a-default-community-health-file-for-your-organization
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
@@ -12,41 +12,46 @@ versions:
topics:
- Community
shortTitle: Community health file
-ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145117634'
---
-## Acerca de los archivos predeterminados del estado de la comunidad
-Puede agregar archivos de mantenimiento de la comunidad predeterminados a un repositorio público denominado `.github`, en la raíz del repositorio o en las carpetas `docs` o `.github`.
+## About default community health files
-{% data variables.product.product_name %} utilizará y mostrará los archivos predeterminados para cualquier repositorio que pertenezca a la cuenta que no tenga su propio archivo de ese tipo en cualquiera de los siguientes lugares:
-- la raíz del repositorio
-- La carpeta `.github`
-- La carpeta `docs`
+You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders.
-Por ejemplo, cualquiera que crea una propuesta o solicitud de cambios en un repositorio que no tenga su propio archivo de "CONTRIBUTING" verá un enlace en el archivo "CONTRIBUTING" predeterminado. Si un repositorio tiene archivos en una carpeta `.github/ISSUE_TEMPLATE` propia{% ifversion fpt or ghes or ghec %}, incluidas las plantillas de incidencia o un archivo *config.yml*,{% endif %} no se usará el contenido de la carpeta `.github/ISSUE_TEMPLATE` predeterminada.
+{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
+- the root of the repository
+- the `.github` folder
+- the `docs` folder
-Los archivos predeterminados no están incluidos en los clones, paquetes ni descargas de repositorios individuales porque solo se almacenan en el repositorio `.github`.
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
-## Tipos de archivo admitidos
+Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
-Puedes crear valores predeterminados en tu cuenta de la organización{% ifversion fpt or ghes or ghec %} o personal{% endif %} para los siguientes archivos de estado de la comunidad:
+## Supported file types
-Archivo de estado de la comunidad | Descripción --- | ---{% ifversion fpt or ghec %} *CODE_OF_CONDUCT.md* | Un archivo CODE_OF_CONDUCT define los estándares de participación en una comunidad. Para más información, vea "[Adición de un código de conducta al proyecto](/articles/adding-a-code-of-conduct-to-your-project/)".{% endif %} *CONTRIBUTING.md* | Un archivo CONTRIBUTING comunica cómo deben contribuir al proyecto los usuarios. Para más información, vea "[Establecimiento de instrucciones para colaboradores del repositorio](/articles/setting-guidelines-for-repository-contributors/)".{% ifversion fpt or ghec %} *FUNDING.yml* | Un archivo FUNDING muestra un botón de patrocinador en el repositorio para aumentar la visibilidad de las opciones de financiación para el proyecto de código abierto. Para más información, vea "[Representación de un botón de patrocinador en el repositorio](/articles/displaying-a-sponsor-button-in-your-repository)".{% endif %} Plantillas de incidencia y solicitud de incorporación de cambios{% ifversion fpt or ghes or ghec %} y *config.yml*{% endif %} | Las plantillas de incidencia y solicitud de incorporación de cambios personalizan y estandarizan la información que quiere que los colaboradores incluyan cuando abren incidencias y solicitudes de incorporación de cambios en el repositorio. Para más información, vea "[Acerca de las plantillas de incidencia y solicitud de incorporación de cambios](/articles/about-issue-and-pull-request-templates/)".{% ifversion fpt or ghes or ghec %} *SECURITY.md* | Un archivo SECURITY proporciona instrucciones sobre cómo notificar una vulnerabilidad de seguridad en el proyecto. Para más información, vea "[Adición de una directiva de seguridad al repositorio](/code-security/getting-started/adding-a-security-policy-to-your-repository)".{% endif %} *SUPPORT.md* | Un archivo SUPPORT permite a los usuarios conocer las formas de obtener ayuda con el proyecto. Para más información, vea "[Adición de recursos de soporte técnico al proyecto](/articles/adding-support-resources-to-your-project/)".
+You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
-No puedes crear un archivo de licencia predeterminado. Los archivos de licencia se deben agregar a repositorios individuales, de manera que el archivo se incluirá cuando el proyecto se clone, se coloque dentro de un paquete o se descargue.
+Community health file | Description
+--- | ---{% ifversion fpt or ghec %}
+*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
+*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion discussion-category-forms %}
+Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[Creating discussion category forms](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
+*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
+Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes or ghec %}
+*SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
-## Crear un repositorio para archivos predeterminados
+You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
+
+## Creating a repository for default files
{% data reusables.repositories.create_new %}
-2. Usa el menú desplegable **Propietario** y selecciona la cuenta de la organización{% ifversion fpt or ghes or ghec %} o personal{% endif %} para la que quieras crear archivos predeterminados.
- 
-3. Escriba **.github** como nombre del repositorio y una descripción opcional.
- 
-4. Asegúrese de que el estado del repositorio se establece en **Público** (los repositorios para los archivos predeterminados no pueden ser privados).
-  {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
-7. En el repositorio, crea uno de los archivos admitidos de estado de la comunidad. Las plantillas de incidencia{% ifversion fpt or ghes or ghec %} y su archivo de configuración{% endif %} deben estar en una carpeta denominada `.github/ISSUE_TEMPLATE`. Todos los demás archivos admitidos pueden estar en la raíz del repositorio, la carpeta `.github` o la carpeta `docs`. Para más información, vea "[Creación de archivos](/articles/creating-new-files/)".
+2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
+ 
+3. Type **.github** as the name for your repository, and an optional description.
+ 
+4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+ 
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
index 44aa07505c..73bbf6e8b5 100644
--- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
+++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a pull request template for your repository
-intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.'
+title: Crear una plantilla de solicitud de extracción para tu repositorio
+intro: 'Cuando agregas una plantilla de solicitud de extracción a tu repositorio, los colaboradores del proyecto verán automáticamente los contenidos de la plantilla en el cuerpo de la solicitud de extracción.'
redirect_from:
- /articles/creating-a-pull-request-template-for-your-repository
- /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
@@ -12,41 +12,44 @@ versions:
topics:
- Community
shortTitle: Create a PR template
+ms.openlocfilehash: fa4d3cf78b63af147c85b8f6d77d7cca74e3853a
+ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190412'
---
+Para más información, vea "[Acerca de las plantillas de incidencias y solicitudes de incorporación de cambios](/articles/about-issue-and-pull-request-templates)".
-For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
-
-You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
+Puedes crear un subdirectorio *PULL_REQUEST_TEMPLATE/* en cualquiera de las carpetas admitidas para incluir múltiples plantillas de solicitudes de incorporación de cambios y usar el parámetro de consulta `template` para especificar la plantilla que completará el cuerpo de dicha solicitud. Para obtener más información, consulta "[Utilizar parámetros de consulta para crear una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)".
{% ifversion fpt or ghes or ghec %}
-You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+Puedes crear plantillas de solicitudes de incorporación de cambios predeterminadas para tu organización{% ifversion fpt or ghes or ghec %} o cuenta personal{% endif %}. Para más información, vea "[Creación de un archivo de estado de la comunidad predeterminado](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)".
{% endif %}
-## Adding a pull request template
+## Agregar una plantilla de solicitud de extracción
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field:
- - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`.
- 
- - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`.
- 
- - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`.
- 
- - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
- 
-4. In the body of the new file, add your pull request template. This could include:
- - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository.
- - A description of the changes proposed in the pull request.
- - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes.
-{% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. En el campo para el nombre del archivo:
+ - Para que la plantilla de solicitud de incorporación de cambios esté visible en el directorio raíz del repositorio, asigna el nombre `pull_request_template.md` a dicha plantilla.
+ 
+ - Para que la plantilla de solicitud de incorporación de cambios esté visible en el directorio `docs` del repositorio, asigna el nombre `docs/pull_request_template.md` a dicha plantilla.
+ 
+ - Para almacenar el archivo en un directorio oculto, asigna el nombre `.github/pull_request_template.md` a la plantilla de solicitud de incorporación de cambios.
+ 
+ - Para crear varias plantillas de solicitud de incorporación de cambios y usar el parámetro de consulta `template` para especificar una plantilla para rellenar el cuerpo de la solicitud de este tipo, escribe *.github/PULL_REQUEST_TEMPLATE/* y, después, el nombre de la plantilla de solicitud de incorporación de cambios. Por ejemplo, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. También puedes almacenar varias plantillas de solicitud de incorporación de cambios en un subdirectorio `PULL_REQUEST_TEMPLATE` dentro del directorio raíz o `docs/`. Para obtener más información, consulta "[Utilizar parámetros de consulta para crear una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)".
+ 
+4. En el cuerpo del nuevo archivo, agrega tu plantilla de solicitud de extracción. Puede incluir:
+ - Una [referencia a un problema relacionado](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) en el repositorio.
+ - Una descripción de los cambios propuestos en la solicitud de extracción.
+ - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) de la persona o equipo responsable de revisar los cambios propuestos.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} Las plantillas están disponibles para los colaboradores cuando están fusionadas mediante combinación dentro de la rama predeterminada del repositorio.
{% data reusables.files.propose_new_file %}
-## Further reading
+## Información adicional
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating a pull request](/articles/creating-a-pull-request)"
+- "[Acerca de las plantillas de incidencias y las solicitudes de incorporación de cambios](/articles/about-issue-and-pull-request-templates)"
+- "[Acerca de la automatización para incidencias y solicitudes de incorporación de cambios con parámetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
+- "[Creación de una solicitud de incorporación de cambios](/articles/creating-a-pull-request)"
diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
index db0162551d..47a8883d85 100644
--- a/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
+++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -1,6 +1,6 @@
---
-title: About apps
-intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}'
+title: Acerca de las apps
+intro: 'Puedes crear integraciones con las API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} para agregar flexibilidad y reducir la fricción en tu propio flujo de trabajo.{% ifversion fpt or ghec %} También puedes compartir las integraciones con otros en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}.'
redirect_from:
- /apps/building-integrationssetting-up-a-new-integration
- /apps/building-integrations
@@ -14,93 +14,99 @@ versions:
ghec: '*'
topics:
- GitHub Apps
+ms.openlocfilehash: a66af14f6047b2aff435ac4ac8dc83d7a1181e92
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107361'
---
-Apps on {% data variables.product.prodname_dotcom %} allow you to automate and improve your workflow. You can build apps to improve your workflow.{% ifversion fpt or ghec %} You can also share or sell apps in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). To learn how to list an app on {% data variables.product.prodname_marketplace %}, see "[Getting started with GitHub Marketplace](/marketplace/getting-started/)."{% endif %}
+Las apps en {% data variables.product.prodname_dotcom %} te permiten automatizar y mejorar tu flujo de trabajo. Puedes compilar aplicaciones para mejorar tu flujo de trabajo. {% ifversion fpt or ghec %} También puedes compartir o vender aplicaciones en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Para aprender a mostrar una aplicación en {% data variables.product.prodname_marketplace %}, consulta "[Comenzar con GitHub Marketplace](/marketplace/getting-started/)".{% endif %}
-{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)."
+{% data reusables.marketplace.github_apps_preferred %}, Pero GitHub es compatible tanto con las {% data variables.product.prodname_oauth_apps %} y con las {% data variables.product.prodname_github_apps %}. Para obtener información sobre cómo elegir un tipo de aplicación, consulta "[Diferencias entre las aplicaciones de GitHub y las aplicaciones de OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)".
{% data reusables.apps.general-apps-restrictions %}
-For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+Para obtener una guía detallada del proceso de creación de una {% data variables.product.prodname_github_app %}, consulta la sección "[Crear tu primera {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)".
-## About {% data variables.product.prodname_github_apps %}
+## Acerca de las {% data variables.product.prodname_github_apps %}
-{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user.
+Las {% data variables.product.prodname_github_apps %} son actores de primera clase dentro de GitHub. Una {% data variables.product.prodname_github_app %} actúa por si misma, tomando las acciones a través de la API y utilizando directamente su propia identidad, lo que significa que no necesitas mantener un bot o cuenta de servicio como un usuario separado.
-{% data variables.product.prodname_github_apps %} can be installed directly on organizations and personal accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository.
+Las {% data variables.product.prodname_github_apps %} se pueden instalar directamente en las cuentas de organización y personales, y se les puede dar acceso a repositorios específicos. Vienen con webhooks integrados y con permisos específicos y delimitados. Cuando configuras tu {% data variables.product.prodname_github_app %}, puedes seleccionar los repositorios a los cuales quieres acceder. Por ejemplo, puedes configurar una aplicación denominada `MyGitHub` que escriba incidencias en el repositorio `octocat` y _solo_ en el repositorio `octocat`. Para instalar una {% data variables.product.prodname_github_app %}, necesitas ser propietario de la organización o tener permisos administrativos en el repositorio.
{% data reusables.apps.app_manager_role %}
-{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+Las {% data variables.product.prodname_github_apps %} son aplicaciones que necesitan hospedarse en algún lugar. Para obtener instrucciones paso a paso que cubran los temas de servidores y hospedaje, consulta la sección "[Crear tu primera {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)".
-To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs.
+Para mejorar tu flujo de trabajo, puedes crear una {% data variables.product.prodname_github_app %} que contenga varios scripts, o bien, una aplicación completa, y después conectarla a muchas otras herramientas. Por ejemplo, puedes conectar las {% data variables.product.prodname_github_apps %} a GitHub, Slack, a otras apps locales que tuvieras, programas de correo electrónico, o incluso a otras API.
-Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}:
+Toma estas ideas en consideración cuando crees {% data variables.product.prodname_github_apps %}:
{% ifversion fpt or ghec %}
* {% data reusables.apps.maximum-github-apps-allowed %} {% endif %}
-* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %}
+* Una {% data variables.product.prodname_github_app %} debe realizar acciones independientemente de un usuario (a menos que la aplicación use un token de [usuario a servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) ). {% data reusables.apps.expiring_user_authorization_tokens %}
-* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories.
-* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization.
-* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can.
-* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things.
-* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %}
+* Asegúrate de que la {% data variables.product.prodname_github_app %} se integre con repositorios específicos.
+* La {% data variables.product.prodname_github_app %} deberá conectarse a una cuenta personal o a una organización.
+* No esperes que la {% data variables.product.prodname_github_app %} sepa y haga todo lo que puede hacer un usuario.
+* No utilices a la {% data variables.product.prodname_github_app %} si solo necesitas el servicio de "Iniciar sesión en GitHub". Pero una {% data variables.product.prodname_github_app %} puede usar un [flujo de identificación de usuario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) para registrar usuarios _y_ hacer otras cosas.
+* No crees una {% data variables.product.prodname_github_app %} si _únicamente_ quieres actuar como usuario de GitHub y hacer todo lo que puede hacer un usuario.{% ifversion fpt or ghec %}
* {% data reusables.apps.general-apps-restrictions %}{% endif %}
-To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %}
+Para empezar a desarrollar {% data variables.product.prodname_github_apps %}, comienza con "[Crear una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)".{% ifversion fpt or ghec %} Para aprender a usar los manifiestos de las {% data variables.product.prodname_github_app %}, que permitan a otras personas crear {% data variables.product.prodname_github_apps %} preconfiguradas, consulta "[Crear {% data variables.product.prodname_github_apps %} a partir de un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)".{% endif %}
-## About {% data variables.product.prodname_oauth_apps %}
+## Acerca de las {% data variables.product.prodname_oauth_apps %}
-OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time.
+OAuth2 es un protocolo que permite a las aplicaciones externas el solicitar autorización para usar detalles privados en una cuenta de {% data variables.product.prodname_dotcom %} del usuario sin acceder a su contraseña. Estas son preferentes sobre la Autenticación Básica, ya que los tokens pueden limitarse a ciertos tipos de datos y los usuarios pueden revocarlos en cualquier momento.
{% data reusables.apps.deletes_ssh_keys %}
-An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access.
+Una {% data variables.product.prodname_oauth_app %} utiliza a {% data variables.product.prodname_dotcom %} como proveedor de identidad para autenticarse como el usuario que otorga el acceso a la app. Esto significa que, cuando un usuario otorga acceso a una {% data variables.product.prodname_oauth_app %}, también otorga permisos a _todos_ los repositorios a los cuales tiene acceso en su cuenta, y también a cualquier organización a la que pertenezca que no haya bloqueado el acceso de terceros.
-Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere.
+Crear una {% data variables.product.prodname_oauth_app %} es una buena opción si estás creando procesos más complejos de lo que puede manejar un script sencillo. Nota que las {% data variables.product.prodname_oauth_apps %} son aplicaciones que necesitan hospedarse en algún lugar.
-Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}:
+Toma estas ideas en consideración cuando crees {% data variables.product.prodname_oauth_apps %}:
{% ifversion fpt or ghec %}
* {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %}
-* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications).
-* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user.
-* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories.
-* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %}
+* Una {% data variables.product.prodname_oauth_app %} siempre debe actuar como el usuario autenticado de {% data variables.product.prodname_dotcom %} a través de todo {% data variables.product.prodname_dotcom %} (por ejemplo, cuando proporciona notificaciones de usuario).
+* Una {% data variables.product.prodname_oauth_app %} puede utilizarse como un proveedor de identidad si el usuario autenticado habilita la opción de "Ingresar con {% data variables.product.prodname_dotcom %}".
+* No crees una {% data variables.product.prodname_oauth_app %} si quieres que tu aplicación actúe en un solo repositorio. Con el alcance de OAuth de `repo`, las {% data variables.product.prodname_oauth_apps %} podrán actuar en _todos_ los repositorios del usuario autenticado.
+* No crees una {% data variables.product.prodname_oauth_app %} para que actúe como una aplicación para tu equipo o compañía. Las {% data variables.product.prodname_oauth_apps %} se autentican como un solo usuario, así que, si una persona crea una {% data variables.product.prodname_oauth_app %} para el uso de una compañía, y luego salen de dicha compañía, nadie más tendrá acceso a ella.{% ifversion fpt or ghec %}
* {% data reusables.apps.oauth-apps-restrictions %}{% endif %}
-For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)."
+Para obtener más información sobre {% data variables.product.prodname_oauth_apps %}, consulta "[Crear una {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" y "[Registro de la aplicación](/rest/guides/basics-of-authentication#registering-your-app)".
-## {% data variables.product.pat_generic_caps %}s
+## {% data variables.product.pat_generic_caps %}
-A [{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A {% data variables.product.pat_generic %} is also similar to a password, but you can have many of them and you can revoke access to each one at any time.
+Un [{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) es una cadena de caracteres que funciona de forma similar a un [token de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/) en el sentido de que puedes especificar sus permisos mediante [ámbitos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Un {% data variables.product.pat_generic %} también es similar a una contraseña, pero puedes tener varios de ellos y revocar el acceso de cada uno en cualquier momento.
-As an example, you can enable a {% data variables.product.pat_generic %} to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the {% data variables.product.pat_generic %} to authenticate. You can store the {% data variables.product.pat_generic %} as an environment variable to avoid typing it every time you use it.
+Por ejemplo, puedes permitir que un {% data variables.product.pat_generic %} escriba en tus repositorios. Si después ejecutas un comando cURL o escribes un script que [genera una incidencia](/rest/reference/issues#create-an-issue) en tu repositorio, pasarías e {% data variables.product.pat_generic %} para la autenticación. Puedes almacenar el {% data variables.product.pat_generic %} como una variable de entorno para evitar tener que escribirlo cada vez que lo uses.
-Keep these ideas in mind when using {% data variables.product.pat_generic %}s:
+Ten en cuenta lo siguiente cuando uses un {% data variables.product.pat_generic %}:
-* Remember to use this token to represent yourself only.
-* You can perform one-off cURL requests.
-* You can run personal scripts.
-* Don't set up a script for your whole team or company to use.
-* Don't set up a shared personal account to act as a bot user.
-* Grant your token the minimal privileges it needs.
-* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.
+* Recuerda utilizar este token para que te represente únicamente a ti.
+* Puedes realizar solicitudes cURL de una sola ocasión.
+* Puedes ejecutar scripts personales.
+* No configures un script para que lo utilice todo tu equipo o compañía.
+* No configures una cuenta personal compartida para que actúe como un usuario de bot.
+* Concede al token los privilegios mínimos que necesite.
+* Establece una expiración para el {% data variables.product.pat_generic %}, con el fin de ayudar a mantener la información segura.
-## Determining which integration to build
+## Determinar qué integración debes crear
-Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use {% data variables.product.pat_generic %}s, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration.
+Antes de que comiences a crear integraciones, necesitas determinar la mejor forma de acceder, autenticar, e interactuar con las API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. En la imagen siguiente encontrarás algunas preguntas que deberías plantearte cuando decidas si vas a usar un {% data variables.product.pat_generic %}, {% data variables.product.prodname_github_apps %} o {% data variables.product.prodname_oauth_apps %} para la integración.
-
+
-Consider these questions about how your integration needs to behave and what it needs to access:
+Considera estas preguntas acerca de cómo necesita comportarse tu integración y a qué necesita acceder:
-* Will my integration act only as me, or will it act more like an application?
-* Do I want it to act independently of me as its own entity?
-* Will it access everything that I can access, or do I want to limit its access?
-* Is it simple or complex? For example, {% data variables.product.pat_generic %}s are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting.
+* ¿Mi integración actuará únicamente como yo, o actuará más como una aplicación?
+* ¿Quiero que actúe independientemente de mí como su propia entidad?
+* ¿Accederá a todo lo que yo puedo acceder, o quiero limitar su acceso?
+* ¿Es simple o compleja? Por ejemplo, un {% data variables.product.pat_generic %} es una buena opción para scripts simples y cURL, mientras que una {% data variables.product.prodname_oauth_app %} puede controlar scripts más complejos.
-## Requesting support
+## Solicitar soporte
{% data reusables.support.help_resources %}
diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md
index c2e9f85746..f684df6166 100644
--- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,6 +9,8 @@ children:
- /managing-categories-for-discussions
- /moderating-discussions
- /viewing-insights-for-your-discussions
+ - /creating-discussion-category-forms
+ - /syntax-for-discussion-category-forms
ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
ms.translationtype: HT
diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index 302f14adae..b5047084d2 100644
--- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -1,215 +1,201 @@
---
-title: Managing discussions
-intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
+title: Administrar los debates
+intro: 'Puedes categorizar, resaltar, transferir o borrar los debates.'
permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
versions:
feature: discussions
shortTitle: Manage discussions
redirect_from:
- /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
+ms.openlocfilehash: e5e1474648973c90d16e8998db18518331233aa3
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164343'
---
+## Acerca de la administración de los debates
+{% data reusables.discussions.about-discussions %} Para obtener más información, consulte "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
-## About management of discussions
+Los propietarios de la organización pueden elegir los permisos que se requieren para crear un debate en los repositorios que pertenezcan a la organización. Del mismo modo, para elegir los permisos necesarios para crear un debate de la organización, los propietarios de la organización pueden cambiar los permisos necesarios en el repositorio de origen. Para más información, vea "[Administración de la creación de debates para repositorios de la organización](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)".
-{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+Como mantenedor de debates, puedes crear recursos comunitarios para impulsar los debates que se alinien con la meta general del proyecto y mantener así un foro abierto y amistoso para los colaboradores. La creación de{% ifversion fpt or ghec %} un código de conducta o{% endif %} directrices de colaboración para que los colaboradores los sigan te ayudará a proporcionar un foro colaborativo y productivo. Para obtener más información sobre la creación de recursos de la comunidad, consulta{% ifversion fpt or ghec %} "[Adición de un código de conducta al proyecto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" y{% endif %} "[Establecimiento de instrucciones para los colaboradores del repositorio](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)".
-Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."
+Cuando un debate produce una idea o error que está listo para solucionarse, puedes crear una propuesta nueva desde un debate. Para más información, vea "[Creación de una incidencia](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)".
-As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, 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 guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+Puedes anclar un debate a la parte superior de la lista de debates para el repositorio o la organización. {% ifversion discussions-category-specific-pins %}También puedes anclar un debate a una categoría específica.{% endif %} Para obtener más información, consulta "[Anclaje de un debate](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)".
-When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
-
-You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
-
-For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
+Para obtener más información sobre cómo facilitar un debate correcto, vea "[Moderación de comentarios y conversaciones](/communities/moderating-comments-and-conversations)".
{% data reusables.discussions.you-can-label-discussions %}
-## Prerequisites
+## Prerrequisitos
-To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)."
+Para administrar los debates en un repositorio, debes habilitar los {% data variables.product.prodname_discussions %} en este. Para más información, vea "[Habilitación o deshabilitación de {% data variables.product.prodname_discussions %} en un repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)".
-To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+Para administrar debates en una organización, los datos {% data variables.product.prodname_discussions %} debe estar habilitados para la organización. Para más información, consulta "[Habilitación o deshabilitación de {% data variables.product.prodname_discussions %} para una organización](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)".
-## Changing the category for a discussion
+## Cambiar la categoría de un debate
-You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+Puedes categorizar los debates para ayudar a que los miembros de la comunidad encuentren aquellos que tengan alguna relación. Para más información, consulta "[Administración de categorías para debates](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)".
-You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category.
+También puedes migrar un debate a una categoría diferente. No es posible mover un debate a o desde la categoría de sondeos.
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. En la barra lateral derecha, a la derecha de "Categoría", haz clic en {% octicon "gear" aria-label="The gear icon" %}.
- 
+ 
-1. Click a category.
+1. Haz clic en una categoría.
- 
+ 
-## Pinning a discussion
+## Fijar un debate
-{% ifversion discussions-category-specific-pins %}
-You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
+{% ifversion discussions-category-specific-pins %} Puedes anclar un debate encima de la lista de debates para el repositorio o la organización. También puedes anclar un debate a una categoría específica. Los debates anclados globalmente se mostrarán además de los debates anclados a una categoría específica.
-This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
+Así es como se ve cuando tienes un debate anclado globalmente y un debate anclado a la categoría Ideas.
-
+
-### Pinning a discussion globally
+### Anclaje de un debate globalmente
{% endif %}
-You can pin up to four important discussions above the list of discussions for the repository or organization.
+Puedes fijar hasta cuatro debates importantes sobre la lista de debates del repositorio u organización.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. En la barra lateral derecha, haga clic en {% octicon "pin" aria-label="The pin icon" %} **Pin discussion** (Anclar debate).
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ {% else %}
- {% endif %}
+ {% endif %}
-1. Optionally, customize the look of the pinned discussion.
+1. Opcionalmente, personaliza la apariencia del debate que fijaste.
- 
+ 
-1. Click **Pin discussion**.
+1. Haga clic en **Pin discussion** (Anclar debate).
- 
+ 
{% ifversion discussions-category-specific-pins %}
-### Pinning a discussion to a category
+### Anclaje de un debate a una categoría
-You can pin up to four important discussions above the list of discussions in a specific category.
+Puedes anclar hasta cuatro debates importantes sobre la lista de debates en una categoría específica.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. En la barra lateral derecha, haz clic en {% octicon "pin" aria-label="The pin icon" %} **Anclar debate a CATEGORÍA**.
- 
+ 
-2. To confirm, click **Pin to CATEGORY**.
+2. Para confirmarlo, haz clic en **Anclar a CATEGORÍA**.
- 
+ 
{% endif %}
-## Editing a pinned discussion
+## Editar un debate que se fijó
-Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+Editar un debate que se ha fijado no cambiará la categoría del mismo. Para más información, consulta "[Administración de categorías para debates](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)".
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. En la barra lateral derecha, haga clic en {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion** (Editar debate anclado).
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+  {% else %}
- {% endif %}
+ {% endif %}
-1. Customize the look of the pinned discussion.
+1. Personaliza la apariencia del debate que fijaste.
- 
+ 
-1. Click **Pin discussion**.
+1. Haga clic en **Pin discussion** (Anclar debate).
- 
+ 
-## Unpinning a discussion
+## Dejar de fijar un debate
{% ifversion discussions-category-specific-pins %}
-You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
+Puedes desanclar un debate de la lista de debates para el repositorio o la organización, o bien de la lista de debates de una categoría específica.
-### Unpinning a globally pinned discussion
+### Desanclaje de un debate anclado globalmente
-You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
+Puedes desanclar un debate anclado globalmente. Esto no eliminará el debate, pero este ya no se mostrará encima de la lista de debates.
{% endif %}
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. En la barra lateral derecha, haga clic en {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion** (Desanclar debate).
- 
+ 
-1. Read the warning, then click **Unpin discussion**.
+1. Lea la advertencia y haga clic en **Unpin discussion** (Desanclar debate).
- 
+ 
{% ifversion discussions-category-specific-pins %}
-### Unpinning a discussion from a category
+### Desanclaje de un debate de una categoría
-You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
+Puedes desanclar un debate anclado a una categoría específica. Esto no eliminará el debate, pero este ya no se mostrará encima de la categoría.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. En la barra lateral derecha, haz clic en {% octicon "pin" aria-label="The pin icon" %} **Desanclar debate de esta categoría**.
- 
+ 
-1. Read the warning, then click **Unpin from this category**.
+1. Lee la advertencia y, a continuación, haz clic en **Desanclar de esta categoría**.
- 
+ 
{% endif %}
-## Transferring a discussion
+## Transferir un debate
-To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
+Para transferir un debate, debes tener permisos para crear debates en el repositorio a donde quieras trasnferirlo. Si quieres transferir un debate a una organización, debes tener permisos para crear debates en el repositorio de origen para los debates de la organización. Solo puedes transferir debates entre los repositorios que pertenezcan a la misma cuenta de organización o de usuario. No se puede transferir un debate de un repositorio privado{% ifversion ghec or ghes %} o interno{% endif %} a un repositorio público.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. En la barra lateral derecha, haz clic en {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transferir este debate**{% else %}**Transferir debate**{% endif %}.
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+  {% else %}
- {% endif %}
+ {% endif %}
-1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
+1. Seleccione el menú desplegable **Choose a repository** (Elegir un repositorio) y haga clic en el repositorio al que quiera transferir el debate. Si deseas transferir un debate a una organización, elige el repositorio de origen para los debates de la organización.
- 
+ 
-1. Click **Transfer discussion**.
+1. Haga clic en **Transfer discussion** (Transferir debate).
- 
+ 
-## Deleting a discussion
+## Borrar un debate
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. En la barra lateral derecha, haga clic en {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion** (Eliminar debate).
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ {% else %}
- {% endif %}
+ {% endif %}
-1. Read the warning, then click **Delete this discussion**.
+1. Lea la advertencia y haga clic en **Delete this discussion** (Eliminar este debate).
- 
+ 
-## Converting issues based on labels
+## Convertir propuestas con base en las etiquetas
-You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.
+Puedes convertir todas las propuestas con la misma etiqueta en debates, por lote. Las propuestas subsecuentes que tengan esta etiqueta también se convertirán automáticamente en el debate y categoría que configures.
-1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository.
-{% data reusables.repositories.sidebar-issues %}
-{% data reusables.project-management.labels %}
-1. Next to the label you want to convert to issues, click **Convert issues**.
-1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
-1. Click **I understand, convert this issue to a discussion**.
+1. En {% data variables.location.product_location %}, ve hasta la página principal del repositorio o, para los debates de organizaciones, el repositorio de origen.
+{% data reusables.repositories.sidebar-issues %} {% data reusables.project-management.labels %}
+1. Junto a la etiqueta que quiere convertir en incidencias, haga clic en **Convert issues** (Convertir incidencias).
+1. Seleccione el menú desplegable **Choose a category** (Seleccionar una categoría) y haga clic en una categoría para el debate.
+1. Haga clic en **I understand, convert this issue to a discussion** (Lo entiendo, convertir esta incidencia en un debate).
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index ffef0a4aba..3af423111e 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -1,78 +1,84 @@
---
-title: Create a group assignment
-intro: You can create a collaborative assignment for teams of students who participate in your course.
+title: Crear una tarea de grupo
+intro: Puedes crear una tarea colaborativa para que los equipos de alumnos participen en tu curso.
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
redirect_from:
- /education/manage-coursework-with-github-classroom/create-group-assignments
- /education/manage-coursework-with-github-classroom/create-a-group-assignment
+ms.openlocfilehash: 71c5f5eaf97ba58e25921c1e2be6fc638550dfa8
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179764'
---
-## About group assignments
+## Acerca de las tareas de grupo
-{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+{% data reusables.classroom.assignments-group-definition %} Los alumnos pueden trabajar en conjunto en las tareas de grupo dentro de un repositorio compartido, como un equipo de desarrolladores profesionales.
-When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+Cuando un alumno acepta una tarea grupal, los alumnos pueden crear un equipo nuevo o unirse a uno existente. {% data variables.product.prodname_classroom %} guarda los equipos para una tarea como un conjunto. Puedes nombrar el conjunto de equipos para una tarea específica cuando creas dicha tarea y puedes reutilizar ese conjunto de equipos para una tarea más grande.
{% data reusables.classroom.classroom-creates-group-repositories %}
{% data reusables.classroom.about-assignments %}
-You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+Puedes decidir cuántos equipos puede tener una tarea y cuántos miembros puede tener cada equipo. Cada equipo que crea un alumno para una tarea constituye un equipo dentro de tu organización en {% data variables.product.product_name %}. La visibilidad del equipo es secreta. Los equipos que crees en {% data variables.product.product_name %} no aparecerán en {% data variables.product.prodname_classroom %}. Para más información, vea "[Acerca de los equipos](/organizations/organizing-members-into-teams/about-teams)".
-For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+Para obtener una demostración en vídeo de la creación de una asignación de grupo, vea "[Conceptos básicos de la configuración de {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)".
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## Requisitos previos
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## Crear una tarea
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## Configurar lo básico para una tarea
-Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+Nombra tu tarea, decide si quires asignarle una fecha límite, definir equipos o elegir la visibilidad de los repositorios de la misma.
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Defining teams for an assignment](#defining-teams-for-an-assignment)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Denominación de una asignación](#naming-an-assignment)
+- [Asignación de una fecha límite para una asignación](#assigning-a-deadline-for-an-assignment)
+- [Elección de un tipo de asignación](#choosing-an-assignment-type)
+- [Definición de equipos para una asignación](#defining-teams-for-an-assignment)
+- [Elección de un tipo de visibilidad para los repositorios de asignación](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### Nombrar una tarea
-For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+En las tareas grupales, {% data variables.product.prodname_classroom %} nombra a los repositorios de acuerdo con el prefijo de los mismos y el nombre del equipo. Predeterminadamente, el prefijo del repositorio es el título de la tarea. Por ejemplo, si asigna el nombre "assingment-1" a una asignación y el nombre del equipo en {% data variables.product.product_name %} es "student-team", el nombre del repositorio de la asignación para los miembros del equipo será `assignment-1-student-team`.
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### Asignar una fecha límita para una tarea
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### Elegir un tipo de tarea
-Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create an individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+En "Individual or group assignment" (Asignación individual o de grupo), seleccione el menú desplegable y haga clic en **Group assignment** (Asignación de grupo). No puedes cambiar el tipo de tarea después de crearla. Si prefieres crear una asignación individual, consulta "[Crear una asignación individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)".
-### Defining teams for an assignment
+### Definir los equipos para una tarea
-If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+Si ya creaste una tarea grupal para el aula, puedes reutilizar un conjunto de equipos para la tarea nueva. Para crear un conjunto nuevo con los equipos que crean tus alumnos para la tarea, teclea el nombre de dicho conjunto. Opcionalmente, teclea la cantidad máxima de miembros de los equipos y el total de los equipos.
{% tip %}
-**Tips**:
+**Sugerencias**:
-- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+- Te recomendamos incluir detalles sobre el conjunto de equipos en el nombre de dicho conjunto. Por ejemplo, si quieres utilizar un conjunto de equipos en un segmente, nómbralo como la tarea. Si quieres reutilizar el conjunto a lo largo de un semesre o curso, nombra el conjunto como el semestre o curso.
-- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+- Si te gustaría asignar alumnos a un equipo específico, proporciónales un nombre de equipo y una lista de mimebros.
{% endtip %}
-
+
-### Choosing a visibility for assignment repositories
+### Elegir un tipo de visibilidad para los repositorios de la tarea
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -80,22 +86,22 @@ If you've already created a group assignment for the classroom, you can reuse a
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## Agergar un código de inicio y configurar un ambiente de desarrollo
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [Elección de un repositorio de plantilla](#choosing-a-template-repository)
+- [Elección de un entorno de desarrollo integrado (IDE)](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### Elegir un repositorio de plantilla
-By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %}
+Predeterminadamente, una tarea nueva creará un repositorio en blanco para cada equipo que cree el alumno. {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
-### Choosing an integrated development environment (IDE)
+### Elegir un ambiente de desarrollo integrado (IDE)
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} Para más información, vea "[Integración de {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)".
{% data reusables.classroom.classroom-codespaces-link %}
@@ -103,18 +109,18 @@ By default, a new assignment will create an empty repository for each team that
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-## Providing feedback
+## Comentarios
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+Opcionalmente, puedes calificar tareas automáticamente y crear un espacio para debatir cada entrega con el equipo.
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [Prueba automática de las tareas](#testing-assignments-automatically)
+- [Creación de una solicitud de incorporación de cambios para comentarios](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### Probar las tareas automáticamente
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### Crear una solicitud de cambios para retroalimentación
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -122,36 +128,36 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## Invitar a los alumnos a una tarea
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+Puede ver los equipos que han enviado una asignación o que están trabajando en ella en la pestaña **Teams** (Equipos) de dicha asignación. {% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
+## Monitorear el progreso de los alumnos
+La página de resumen de la tarea muestra la información de las aceptaciones de la misma y del progreso del equipo. Podrías tener información de resumen diferente con base en las configuraciones de tus tareas.
-- **Total teams**: The number of teams that have been created.
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
-- **Accepted teams**: The number of teams who have accepted this assignment.
-- **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
+- **Total teams** (Total de equipos): el número de equipos que se han creado.
+- **Alumnos en la lista**: cantidad de alumnos en la lista del aula.
+- **Students not on a team** (Alumnos que no están en un equipo): el número de alumnos en la lista del aula que aún no se han unido a un equipo.
+- **Accepted teams** (Equipos que han aceptado): el número de equipos que han aceptado esta asignación.
+- **Assignment submissions** (Entregas de asignaciones): el número de equipos que han enviado la asignación. Las emisiones se activan en la fecha límite de la tarea.
+- **Passing teams** (Equipos que han aprobado): el número de equipos que actualmente han superado las pruebas de autoevaluación de esta asignación.
-## Next steps
+## Pasos siguientes
-- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}.
+- Después de que creas una tarea y de que tus alumnos forme equipos, los miembros de dichos equipos pueden comenzar a trabajar en la tarea utilizando las características de Git y de {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el equipo pueden revisar el historial de confirmaciones del repositorio. Para obtener más información, consulta "[Introducción a {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)", "[Repositorios](/repositories)", "[Uso de Git](/github/getting-started-with-github/using-git)" y "[Colaboración con incidencias y solicitudes de incorporación de cambios](/github/collaborating-with-issues-and-pull-requests)", así como el curso gratuito sobre la [resolución de conflictos de combinación](https://github.com/skills/resolve-merge-conflicts) de {% data variables.product.prodname_learning %}.
-- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- Cuando un equipo termina una tarea, puedes revisar los archivos en el repositorio, o puedes revisar el historial y visualizaciones del mismo para entender mejor cómo colaboró el equipo. Para más información, vea "[Visualización de datos del repositorio con gráficos](/github/visualizing-repository-data-with-graphs)".
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- Puedes proporcionar retroalimentación para una tarea si comentas en confirmaciones o líneas individuales dentro de una solicitud de cambios. Para más información, vea "[Comentarios sobre una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" y "[Apertura de una incidencia desde el código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Para más información sobre cómo crear respuestas guardadas para proporcionar comentarios sobre errores comunes, vea "[Acerca de las respuestas guardadas](/github/writing-on-github/about-saved-replies)".
-## Further reading
+## Información adicional
-- [{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
-- "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
-- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
+- [{% data variables.product.prodname_global_campus %} para profesores](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- "[Conexión de un curso de un sistema de administración del aprendizaje a una clase](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
+- [Uso de equipos existentes en asignaciones de grupo](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) en la comunidad de {% data variables.product.prodname_education %}
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 8161608b81..52b7cb67ec 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -1,6 +1,6 @@
---
-title: Create an individual assignment
-intro: You can create an assignment for students in your course to complete individually.
+title: Crear una tarea individual
+intro: Puedes crear una tarea individual para que los alumnos de tu curso la completen individualmente.
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
@@ -8,8 +8,14 @@ redirect_from:
- /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
- /education/manage-coursework-with-github-classroom/create-an-individual-assignment
shortTitle: Individual assignment
+ms.openlocfilehash: 1ffa725be4e42695b297545f65c998b14ed8e000
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179756'
---
-## About individual assignments
+## Acerca de las tareas individuales
{% data reusables.classroom.assignments-individual-definition %}
@@ -17,42 +23,42 @@ shortTitle: Individual assignment
{% data reusables.classroom.about-assignments %}
-For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+Para obtener una demostración en vídeo de la creación de una asignación individual, vea "[Conceptos básicos de la configuración de {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)".
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## Requisitos previos
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## Crear una tarea
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## Configurar lo básico para una tarea
-Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+Nombra tu tarea, decide si quieres asignar una fecha límite y elige la visibilidad de los repositorios de la misma.
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Denominación de una asignación](#naming-an-assignment)
+- [Asignación de una fecha límite para una asignación](#assigning-a-deadline-for-an-assignment)
+- [Elección de un tipo de asignación](#choosing-an-assignment-type)
+- [Elección de un tipo de visibilidad para los repositorios de asignación](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### Nombrar una tarea
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+Para una tarea individual, {% data variables.product.prodname_classroom %} nombra los repositorios de acuerdo con su prefijo y con el nombre de usuario de {% data variables.product.product_name %} del alumno. Predeterminadamente, el prefijo del repositorio es el título de la tarea. Por ejemplo, si asigna el nombre "assingment-1" a una asignación y el nombre de usuario del alumno en {% data variables.product.product_name %} es @octocat, el nombre del repositorio de la asignación para @octocat será `assignment-1-octocat`.
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### Asignar una fecha límita para una tarea
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### Elegir un tipo de tarea
-Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+En "Individual or group assignment", seleccione el menú desplegable y haga clic en **Individual assignment**. No puedes cambiar el tipo de tarea después de crearla. Si prefiere crear una asignación de grupo, vea "[Creación de una asignación de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)".
-### Choosing a visibility for assignment repositories
+### Elegir un tipo de visibilidad para los repositorios de la tarea
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -60,41 +66,41 @@ Under "Individual or group assignment", select the drop-down menu, and click **I
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## Agergar un código de inicio y configurar un ambiente de desarrollo
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [Elección de un repositorio de plantilla](#choosing-a-template-repository)
+- [Elección de un entorno de desarrollo integrado (IDE)](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### Elegir un repositorio de plantilla
-By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+Predeterminadamente, una tarea nueva creará un repositorio en blanco para cada alumno del registro de alumnos del aula. {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-### Choosing an integrated development environment (IDE)
+### Elegir un ambiente de desarrollo integrado (IDE)
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} Para más información, vea "[Integración de {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)".
{% data reusables.classroom.classroom-codespaces-link %}
{% data reusables.classroom.assignments-guide-choose-an-online-ide %}
-## Providing feedback for an assignment
+## Proporcionar retroalimentación para una tarea
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
+Opcionalmente, puedes calificar tareas automáticamente y crear un espacio para debatir cada entrega con el alumno.
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [Prueba automática de las tareas](#testing-assignments-automatically)
+- [Creación de una solicitud de incorporación de cambios para comentarios](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### Probar las tareas automáticamente
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### Crear una solicitud de cambios para retroalimentación
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -102,34 +108,34 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## Invitar a los alumnos a una tarea
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
+Puede ver si un alumno se ha unido a la clase y ha aceptado o enviado una asignación en la pestaña **Classroom roster** para la asignación. También puede vincular los alias de {% data variables.product.prodname_dotcom %} de los alumnos a sus listas de identificadores asociadas y viceversa en esta pestaña. {% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
+## Monitorear el progreso de los alumnos
+La página de vista general de la tarea te proporciona una vista general de las aceptaciones de tu tarea y del progreso de los alumnos. Podrías tener información de resumen diferente con base en las configuraciones de tus tareas.
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
-- **Accepted students**: The number of accounts have accepted this assignment.
-- **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing students**: The number of students currently passing the autograding tests for this assignment.
+- **Alumnos en la lista**: cantidad de alumnos en la lista del aula.
+- **Alumnos agregados**: cantidad de cuentas de {% data variables.product.prodname_dotcom %} que han aceptado la asignación y no están asociadas con un identificador de lista.
+- **Alumnos aceptados**: cantidad de cuentas que han aceptado esta asignación.
+- **Envíos de asignación**: cantidad de alumnos que han enviado la asignación. Las emisiones se activan en la fecha límite de la tarea.
+- **Alumnos aprobados**: cantidad de alumnos que actualmente han superado las pruebas de autoevaluación de esta asignación.
-## Next steps
+## Pasos siguientes
-- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- Después de que creas la tarea, los alumnos pueden comenzar a trabajar en ella utilizando las características de Git y {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el alumno pueden revisar el historial de confirmaciones del repositorio. Para más información, vea "[Introducción a {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)", "[Repositorios](/repositories)" y "[Colaboración con incidencias y solicitudes de incorporación de cambios](/github/collaborating-with-issues-and-pull-requests)".
-- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- Cuando un alumno termina una tarea, puedes revisar los archivos en el repositorio, o puedes revisar el historial y las visualizaciones del repositorio para entender mejor su trabajo. Para más información, vea "[Visualización de datos del repositorio con gráficos](/github/visualizing-repository-data-with-graphs)".
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- Puedes proporcionar retroalimentación para una tarea si comentas en confirmaciones o líneas individuales dentro de una solicitud de cambios. Para más información, vea "[Comentarios sobre una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" y "[Apertura de una incidencia desde el código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Para más información sobre cómo crear respuestas guardadas para proporcionar comentarios sobre errores comunes, vea "[Acerca de las respuestas guardadas](/github/writing-on-github/about-saved-replies)".
-## Further reading
+## Información adicional
-- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
+- «[{% data variables.product.prodname_global_campus %} para profesores](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)»
+- "[Conexión de un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md
index 7a247d6c1c..16ba6e2b51 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -1,83 +1,88 @@
---
-title: Getting started with GitHub AE
-intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.'
+title: Iniciar con GitHub AE
+intro: 'Empieza con la configuración y ajustes de {% data variables.product.product_name %} para {% data variables.location.product_location %}.'
versions:
ghae: '*'
+ms.openlocfilehash: 957a922a2493abd8f625cdb9e9d6650283820222
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180065'
---
+Esta guía te mostrará cómo configurar, ajustar y administrar la configuración de {% data variables.location.product_location %} en {% data variables.product.product_name %} como propietario de la empresa. Para obtener más información acerca de {% data variables.product.product_name %}, consulta "[Acerca de {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)".
-This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)."
+## Parte 1: Configurar {% data variables.product.product_name %}
+Para comenzar con {% data variables.product.product_name %}, puedes crear tu propia cuenta empresarial, inicializar {% data variables.product.product_name %}, configurar una lista de IP permitidas, configurar la autenticación y aprovisionamiento de usuarios y administrar la facturación de {% data variables.location.product_location %}.
-## Part 1: Setting up {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}.
-
-### 1. Creating your {% data variables.product.product_name %} enterprise account
-You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+### 1. Crear una cuenta empresarial de {% data variables.product.product_name %}
+Primero necesitarás comprar {% data variables.product.product_name %}. Para obtener más información, póngase en contacto con el [equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
{% data reusables.github-ae.initialize-enterprise %}
-### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+### 2. Inicializar {% data variables.product.product_name %}
+Después de que {% data variables.product.company_short %} crea la cuenta de propietario para {% data variables.location.product_location %} en {% data variables.product.product_name %}, recibirás un correo electrónico para iniciar sesión y completar la inicialización. Durante la inicialización, tú, como propietario de la empresa, nombrarás la {% data variables.location.product_location %}, configurarás el SSO de SAML y crearás políticas para todas las organizaciones en {% data variables.location.product_location %} y configurarás un contacto de soporte para los miembros de tu empresa. Para obtener más información, consulte "[Inicialización de {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 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)."
+### 3. Restringir el tráfico de red
+Puedes configurar una lista de direcciones IP permitidas específicas para restringir el acceso a los activos que pertenecen a las organizaciones en tu cuenta empresarial. Para obtener más información, consulta "[Restricción del tráfico de red a la empresa con una lista de direcciones IP permitidas](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)".
-### 4. Managing identity and access for {% data variables.location.product_location %}
-You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[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)."
+### 4. Administrar la identidad y el acceso de {% data variables.location.product_location %}
+Puedes administrar el acceso centralmente a {% data variables.location.product_location %} en {% data variables.product.product_name %} desde un proveedor de identidad (IdP) utilizando el inicio de sesión único (SSO) de SAML para la autenticación de usuarios y un Sistema de Administración de Identidad de Dominio Cruzado (SCIM) para el aprovisionamiento de usuarios. Una vez que configures el aprovisionamiento, podrás asignar o desasignar usuarios a la aplicación desde el IdP, creando o inhabilitando cuentas de usuario en la empresa. Para obtener más información, consulte "[Acerca de la administración de identidades y acceso para la empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)".
-### 5. Managing billing for {% data variables.location.product_location %}
-Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+### 5. Administrar la facturación de {% data variables.location.product_location %}
+Los propietarios de la suscripción a {% data variables.location.product_location %} en {% data variables.product.product_name %} pueden ver los detalles de facturación para {% data variables.product.product_name %} en Azure Portal. Para obtener más información, consulte "[Administración de la facturación de la empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)".
-## Part 2: Organizing and managing enterprise members
-As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
+## Parte 2: Organizar y administrar a los miembros de la empresa
+Como propietario de la empresa para {% data variables.product.product_name %}, puedes administrar los ajustes a nivel de los usuarios, repositorios, equipos y de la organización. Puedes administrar a los miembros de {% data variables.location.product_location %}, crear y administrar organizaciones, configurar políticas para la administración de repositorios y crear y administrar equipos.
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. Administración de los miembros de {% data variables.location.product_location %}
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. Creación de organizaciones
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. Adición de miembros a las organizaciones
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. Creación de equipos
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. Configuración de niveles de permiso de organización y repositorio
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. Aplicación de directivas de administración de repositorios
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations.
+## Parte 3: Compilar de forma segura
+Para incrementar la seguridad de {% data variables.location.product_location %}, puedes monitorear a {% data variables.location.product_location %} y configurar las características de seguridad y análisis para tus organizaciones.
-### 1. Monitoring {% data variables.location.product_location %}
-You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)."
+### 1. Supervisión de {% data variables.location.product_location %}
+Puedes monitorear a {% data variables.location.product_location %} con tu tablero de actividad y registro de bitácoras de auditoría. Para obtener más información, consulte "[Supervisión de la actividad de usuario en la empresa](/admin/monitoring-activity-in-your-enterprise)".
-### 2. Configuring security features for your organizations
+### 2. Configuración de las características de seguridad de las organizaciones
{% data reusables.getting-started.configuring-security-features %}
-## Part 4: Customizing and automating work on {% data variables.location.product_location %}
-You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
+## Parte 4: Personalizar y automatizar el trabajo en {% data variables.location.product_location %}
+Puedes personalizar y automatizar el trabajo en las organizaciones de {% data variables.location.product_location %} con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, {% data variables.product.prodname_actions %} y {% data variables.product.prodname_pages %}.
-### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Uso de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
{% data reusables.getting-started.api %}
-### 2. Building {% data variables.product.prodname_actions %}
+### 2. Creación de {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."
+Para obtener más información sobre cómo habilitar y configurar {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}, consulte "[Introducción a {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)".
-### 3. Using {% data variables.product.prodname_pages %}
+### 3. Uso de {% data variables.product.prodname_pages %}
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Parte 5: Utilizar los recursos de apoyo y aprendizaje de {% data variables.product.prodname_dotcom %}
+Los miembros de tu empresa pueden aprender más sobre Git y sobre {% data variables.product.prodname_dotcom %} con nuestros recursos para aprender y puedes obtener el apoyo que necesitas con {% data variables.product.prodname_dotcom %} Enterprise Support.
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+### 1. Información sobre {% data variables.product.product_name %} en {% data variables.product.prodname_docs %}
+Puedes leer la documentación que refleje las características disponibles en {% data variables.product.prodname_ghe_managed %}. Para más información, vea "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)".
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. Aprendizaje con {% data variables.product.prodname_learning %}
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Ayuda del soporte técnico de {% data variables.product.prodname_dotcom %} Enterprise
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index f3368b385c..7ba422dd6f 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,128 +1,132 @@
---
-title: Getting started with GitHub Enterprise Server
-intro: 'Get started with setting up and managing {% data variables.location.product_location %}.'
+title: Guía de inicio para GitHub Enterprise Server
+intro: 'Comienzo con la configuración y administración de {% data variables.location.product_location %}.'
versions:
ghes: '*'
+ms.openlocfilehash: 68cd462c42ef63863750d9edc5e122dc3c325115
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163420'
---
+Esta guía te mostrará cómo configurar, ajustar y administrar {% data variables.location.product_location %} como un administrador de empresas.
-This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator.
-
-{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
+{% data variables.product.company_short %} proporciona dos formas para desplegar {% data variables.product.prodname_enterprise %}.
- **{% data variables.product.prodname_ghe_cloud %}**
- **{% data variables.product.prodname_ghe_server %}**
-{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
+{% data variables.product.company_short %} hospeda a {% data variables.product.prodname_ghe_cloud %}. Puedes desplegar y hospedar a {% data variables.product.prodname_ghe_server %} en tu propio centro de datos o en un proveedor de servicios en la nube que sea compatible.
-For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)."
+Para obtener más información acerca de {% data variables.product.product_name %}, consulta "[Acerca de {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)".
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing.
-### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## Parte 1: Instalación de {% data variables.product.product_name %}
+Para iniciar con {% data variables.product.product_name %}, necesitarás crear tu cuenta empresarial, instalar la instancia, utilizar la Consola de Administración para la configuración inicial, configurar tu instancia y administrar la facturación.
+### 1. Creación de una cuenta empresarial
+Antes de instalar {% data variables.product.product_name %}, puede crear una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}; para ello, póngase en contacto con el [equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). Una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} es útil para facturar y compartir características con {% data variables.product.prodname_dotcom_the_website %} a través de {% data variables.product.prodname_github_connect %}. Para más información, vea "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)".
+### 2. Instalación de {% data variables.product.product_name %}
+Para iniciar con {% data variables.product.product_name %}, necesitarás instalar el aplicativo en una plataforma de virtualización que tú elijas. Para más información, vea "[Configuración de una instancia de {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)".
-### 3. Using the Management Console
-You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+### 3. Uso de la consola de administración
+Utilizarás la consola de administración para recorrer el proceso de configuración inicial cuando lances {% data variables.location.product_location %} por primera vez. También puedes utilizar la consola de administración para administrar los ajustes de instancia tales como la licencia, dominio, autenticación y TLS. Para más información, vea "[Acceso a la consola de administración](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)".
-### 4. Configuring {% data variables.location.product_location %}
-In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
+### 4. Configuración de {% data variables.location.product_location %}
+Adicionalmente a la Consola de Administración, puedes utilizar el tablero de administrador de sitio y el shell administrativo (SSH) para administrar {% data variables.location.product_location %}. Por ejemplo, puedes configurar las aplicaciones y límites de tasa, ver reportes y utilizar utilidades de línea de comandos. Para más información, vea "[Configuración de la empresa](/admin/configuration/configuring-your-enterprise)".
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+Puedes utilizar los ajustes de red predeterminados que utiliza {% data variables.product.product_name %} a través del protocolo de configuración de host dinámico (DHCP), o también puedes configurar los ajustes de red utilizando la consola de la máquina virtual. También puedes configurar un servidor proxy o reglas de firewall. Para más información, vea "[Definición de la configuración de red](/admin/configuration/configuring-network-settings)".
-### 5. Configuring high availability
-You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
+### 5. Configuración de la alta disponibilidad
+Puedes configurar {% data variables.location.product_location %} para tener disponibilidad alta para minimizar el impacto de los errores de hardware y de las interrupciones de red. Para más información, vea "[Configuración de la alta disponibilidad](/admin/enterprise-management/configuring-high-availability)".
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 6. Configuración de una instancia de ensayo
+También puedes configurar una instancia de almacenamiento provisional para probar modificaciones, planear la recuperación de desastres y probar las actualizaciones antes de aplicarlas a {% data variables.location.product_location %}. Para más información, vea "[Configuración de una instancia de ensayo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)".
-### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+### 7. Configuración de copias de seguridad y de la recuperación ante desastres
+Para proteger tus datos de producción, puedes configurar las copias de seguridad automatizadas de {% data variables.location.product_location %} con {% data variables.product.prodname_enterprise_backup_utilities %}. Para más información, vea "[Configuración de copias de seguridad en el dispositivo](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)".
-### 8. Managing billing for your enterprise
-Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+### 8. Administración de la facturación de la empresa
+La facturación para todas las organizaciones e instancias de {% data variables.product.product_name %} conectadas a tu cuenta empresarial se agregará en un cargo de facturación único para todos tus servicios de pago de {% data variables.product.prodname_dotcom %}.com. Los propietarios y gerentes de facturación de las empresas pueden acceder y administrar los ajustes de facturación de las cuentas empresariales. Para más información, vea "[Administración de la facturación de la empresa](/admin/overview/managing-billing-for-your-enterprise)".
-## Part 2: Organizing and managing your team
-As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
+## Parte 2: Organizar y administrar tu equipo
+Como propietario empresarial o administrador, puedes administrar los ajustes a nivel de usuario, repositorio, equipo y organización. Puedes administrar a los miembros de tu empresa, crear y administrar organizaciones, configurar políticas para la administración de repositorios y crear y administrar equipos.
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. Administración de los miembros de {% data variables.location.product_location %}
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. Creación de organizaciones
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. Adición de miembros a las organizaciones
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. Creación de equipos
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. Configuración de niveles de permiso de organización y repositorio
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. Aplicación de directivas de administración de repositorios
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
-### 1. Authenticating enterprise members
-You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+## Parte 3: Compilar de forma segura
+Para aumentar la seguridad de {% data variables.location.product_location %}, puedes configurar la autenticación para los miembros empresariales, utilizar herramientas y registro en bitácoras de auditoría para permanecer en cumplimiento, configurar las características de seguridad y análisis para tus organizaciones y, opcionalmente, habilitar la {% data variables.product.prodname_GH_advanced_security %}.
+### 1. Autenticación de los miembros de la empresa
+Puedes utilizar el método de autenticación integrado de {% data variables.product.product_name %} o puedes elegir entre un proveedor de autenticación externo, tal como CAS, LDAP o SAML, para integrar tus cuentas existentes y administrar centralmente el acceso de los usuarios a {% data variables.location.product_location %}. Para obtener más información, consulta "[Acerca de la autenticación para tu empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)".
-You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
+También puedes requerir la autenticación bifactorial para cada una de tus organizaciones. Para más información, vea "[Exigencia de la autenticación en dos fases en una organización](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)".
-### 2. Staying in compliance
-You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+### 2. Mantenimiento del cumplimiento
+Puedes implementar las verificaciones de estado requeridas y confirmar las verificaciones para hacer cumplir los estándares de cumplimiento de tu organización y automatizar los flujos de trabajo de cumplimiento. También puedes utilizar la bitácora de auditoría de tu organización para revisar las acciones que realiza tu equipo. Para obtener más información, consulte "[Aplicación de directivas con enlaces de recepción previa](/admin/policies/enforcing-policy-with-pre-receive-hooks)" y "[Acerca del registro de auditoría de la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)".
{% ifversion ghes %}
-### 3. Configuring security features for your organizations
-{% data reusables.getting-started.configuring-security-features %}
-{% endif %}
+### 3. Configuración de las características de seguridad de las organizaciones
+{% data reusables.getting-started.configuring-security-features %} {% endif %}
{% ifversion ghes %}
-### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
-You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+### 4. Habilitación de las características de {% data variables.product.prodname_GH_advanced_security %}
+Puedes mejorar tu licencia de {% data variables.product.product_name %} para que incluya la {% data variables.product.prodname_GH_advanced_security %}. Esto proporciona características adicionales que ayudan a los usuarios a encontrar y arreglar problemas de seguridad en su código, tales como el escaneo de secretos y de código. Para más información, vea "[{% data variables.product.prodname_GH_advanced_security %} para la empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)".
{% endif %}
-## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
-You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
+## Parte 4: Personalizar y automatizar el trabajo de tu empresa en {% data variables.product.prodname_dotcom %}
+Puedes personalizar y automatizar el trabajo en las organizaciones de tu empresa con {% data variables.product.prodname_dotcom %} y con la API de {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} y {% data variables.product.prodname_pages %}.
-### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Creación de {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %}
+Puedes compilar integraciones con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, tales como {% data variables.product.prodname_github_apps %} o {% data variables.product.prodname_oauth_apps %}, para utilizarlas en las organizaciones de tu empresa para complementar y extender tus flujos de trabajo. Para más información, consulte "[Acerca de las actualizaciones](/developers/apps/getting-started-with-apps/about-apps)".
+### 2. Uso de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
{% data reusables.getting-started.api %}
{% ifversion ghes %}
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. Creación de {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+Para más información sobre cómo habilitar y configurar {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}, vea "[Introducción a {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)".
-### 4. Publishing and managing {% data variables.product.prodname_registry %}
+### 4. Publicación y administración de {% data variables.product.prodname_registry %}
{% data reusables.getting-started.packages %}
-For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+Para obtener más información sobre cómo habilitar y configurar {% data variables.product.prodname_registry %} para {% data variables.location.product_location %}, consulta "[Introducción a {% data variables.product.prodname_registry %} para la empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)".
{% endif %}
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. Uso de {% data variables.product.prodname_pages %}
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
-You can use {% data variables.product.prodname_github_connect %} to share resources.
+## Parte 5: Conectarse con otros recursos de {% data variables.product.prodname_dotcom %}
+Puedes utilizar {% data variables.product.prodname_github_connect %} para compartir recursos.
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Si eres el propietario tanto de una instancia de {% data variables.product.product_name %} como de cuenta de organización o de empresa de {% data variables.product.prodname_ghe_cloud %}, puedes habilitar {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} te permite compartir flujos de trabajo y características específicos entre {% data variables.location.product_location %} y {% data variables.product.prodname_ghe_cloud %}, tales como la búsqueda unificada y las contribuciones. Para más información, vea "[Conexión de {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)".
-## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Parte 6: Utilizar los recursos de apoyo y aprendizaje de {% data variables.product.prodname_dotcom %}
+Los miembros de tu empresa pueden aprender más sobre Git y sobre {% data variables.product.prodname_dotcom %} con nuestros recursos para aprender y puedes obtener el apoyo que necesitas cuando configures y administres {% data variables.location.product_location %} con {% data variables.product.prodname_dotcom %} Enterprise Support.
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+### 1. Información sobre {% data variables.product.product_name %} en {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+Puedes leer la documentación que refleje las características disponibles en {% data variables.product.prodname_ghe_server %}. Para más información, vea "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)".
{% data reusables.enterprise.best-practices %}
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. Aprendizaje con {% data variables.product.prodname_learning %}
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Ayuda del soporte técnico de {% data variables.product.prodname_dotcom %} Enterprise
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/es-ES/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/es-ES/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 02ab297dbb..8231ef334b 100644
--- a/translations/es-ES/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
+++ b/translations/es-ES/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,6 +1,6 @@
---
-title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
-intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
+title: 'Migración desde {% data variables.product.prodname_projects_v1 %}'
+intro: 'Puedes migrar las instancias de {% data variables.projects.projects_v1_board %} a la nueva experiencia de {% data variables.product.prodname_projects_v2 %}.'
miniTocMaxHeadingLevel: 3
versions:
feature: projects-v2
@@ -10,57 +10,53 @@ type: tutorial
topics:
- Projects
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e6db4fd8c6587f413ee0e6832dbae93bbf281573
+ms.sourcegitcommit: 9bf175b190674416ad4e11b5c567409f74c00ad2
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/23/2022
+ms.locfileid: '148181225'
---
-
-
{% note %}
-**Notes:**
+**Notas:**
-- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
-- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
-- Automation will not be migrated.
-- Triage, archive, and activity will not be migrated.
-- After migration, the new migrated project and old project will not be kept in sync.
+- Si el proyecto que vas a migrar contiene más de {% data variables.projects.item_limit %} elementos, se dará prioridad a las incidencias abiertas seguidas de las solicitudes de incorporación de cambios abiertas y, luego, las notas. El espacio restante se usará para las incidencias cerradas, las solicitudes de incorporación de cambios combinadas y las solicitudes de incorporación de cambios cerradas. Los elementos que no se pueden migrar debido a este límite se moverán al archivo. Si se alcanza el límite de archivo de {% data variables.projects.archived_item_limit %} elementos, no se migrarán más elementos.
+- Las tarjetas de notas se convierten en borradores de incidencias y el contenido se guarda en el cuerpo del borrador. Si parece que falta información, haz que los campos ocultos sean visibles. Para más información, consulta "[Mostrar y ocultar](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)".
+- No se migrará la automatización.
+- No se migrarán la evaluación de prioridades, el archivo ni la actividad.
+- Después de la migración, el proyecto migrado nuevo y el proyecto anterior no seguirán sincronizados.
{% endnote %}
-## About project migration
+## Acerca de la migración de proyectos
-You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
+Puedes migrar los paneles de proyecto a la nueva experiencia de {% data variables.product.prodname_projects_v2 %} y probar tablas, varias vistas, opciones de automatización nuevas y tipos de campo eficaces. Para más información, consulta "[Acerca de los proyectos](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)".
-## Migrating an organization project board
+## Migración de un panel de proyecto de organización
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
-1. On the left, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
+1. A la izquierda, haz clic en **Proyectos (clásico)** .
+  {% data reusables.projects.migrate-project-steps %}
-## Migrating a user project board
+## Migración de un panel de proyecto de usuario
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_profile %}
-1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
- 
-1. Above the list of projects, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
+1. En la parte superior de la página de perfil, en la navegación principal, haz clic en {% octicon "table" aria-label="The project board icon" %} **Proyectos**.
+ 
+1. Encima de la lista de proyectos, haz clic en **Proyectos (clásico)** .
+  {% data reusables.projects.migrate-project-steps %}
-## Migrating a repository project board
+## Migración de un panel de proyecto de repositorio
{% note %}
-**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
+**Nota:** {% data variables.projects.projects_v2_caps %} no admite proyectos de nivel de repositorio. Cuando migras un panel de proyecto de repositorio, se migrará a la cuenta de organización o a la cuenta personal propietaria del proyecto de repositorio y el proyecto migrado se anclará al repositorio original.
{% endnote %}
-{% data reusables.projects.enable-migration %}
-{% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
-
-1. Click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
+1. En el nombre del repositorio, haz clic en {% octicon "table" aria-label="The project board icon" %} **Proyectos**.
+
+1. Haz clic en **Proyectos (clásico)** .
+  {% data reusables.projects.migrate-project-steps %}
diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md
index 7ff2db3442..7301d794c6 100644
--- a/translations/es-ES/content/packages/quickstart.md
+++ b/translations/es-ES/content/packages/quickstart.md
@@ -1,6 +1,6 @@
---
-title: Quickstart for GitHub Packages
-intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
+title: Guía de inciio rápido para GitHub Packages
+intro: 'Publica en el {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %}.'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -8,29 +8,34 @@ versions:
ghae: '*'
ghec: '*'
shortTitle: Quickstart
+ms.openlocfilehash: 887c4ee6c5e6b3e2c391c2d5754cfcb2787e4b86
+ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/24/2022
+ms.locfileid: '148181263'
---
-
{% data reusables.actions.enterprise-github-hosted-runners %}
-## Introduction
+## Introducción
-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 %}.
+En esta guía, crearás un flujo de trabajo de {% data variables.product.prodname_actions %} para probar tu código y luego lo publicarás en el {% data variables.product.prodname_registry %}.
-## Publishing your package
+## Publicar tu paquete
-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.
+1. Cree un nuevo repositorio en {% data variables.product.prodname_dotcom %} y agregue el archivo `.gitignore` para Node. Para más información, vea "[Creación de un repositorio](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)".
+2. Clone el repositorio en la máquina local.
```shell
$ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
$ cd YOUR-REPOSITORY
```
-3. Create an `index.js` file and add a basic alert to say "Hello world!"
+3. Cree un archivo `index.js` y agregue una alerta básica que diga "Hello, world!".
{% raw %}
```javascript{:copy}
console.log("Hello, World!");
```
{% endraw %}
-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.
+4. Inicialice un paquete de npm con `npm init`. En el asistente para la inicialización de paquetes, escriba el paquete con el nombre : _`@YOUR-USERNAME/YOUR-REPOSITORY`_ y establezca el script de prueba en `exit 0`. Esto generará un archivo `package.json` con información sobre el paquete.
{% raw %}
```shell
$ npm init
@@ -41,15 +46,15 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
...
```
{% endraw %}
-5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
+5. Ejecute `npm install` para generar el archivo `package-lock.json` y, después, confirme e inserte los cambios en {% 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. 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 %}.
+6. Cree un directorio `.github/workflows`. En este directorio, cree un archivo denominado `release-package.yml`.
+7. Copia el siguiente contenido YAML en el archivo `release-package.yml`{% ifversion ghes or ghae %}, reemplazando `YOUR-HOSTNAME` por el nombre de tu empresa{% endif %}.
```yaml{:copy}
name: Node.js Package
@@ -85,22 +90,20 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
env:
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
```
-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 %}
+8. Dile a NPM en qué alcance y registro publicar paquetes para utilizar uno de los siguientes métodos:
+ - Agregue un archivo de configuración de NPM para el repositorio mediante la creación de un archivo `.npmrc` en el directorio raíz con el contenido: {% raw %}
```shell
@YOUR-USERNAME:registry=https://npm.pkg.github.com
```
{% endraw %}
- - Edit the `package.json` file and specify the `publishConfig` key:
- {% raw %}
+ - Edite el archivo `package.json` y especifique la clave `publishConfig`: {% raw %}
```shell
"publishConfig": {
"@YOUR-USERNAME:registry": "https://npm.pkg.github.com"
}
```
{% endraw %}
-9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
+9. Confirma y sube tus cambios a {% 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.
@@ -108,28 +111,26 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
$ git commit -m "workflow to publish package"
$ git push
```
-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 %}.
+10. El flujo de trabajo que creaste se ejecutará cuando sea que se cree un lanzamiento nuevo en tu repositorio. Si las pruebas pasan, entonces el paquete se publicará en {% data variables.product.prodname_registry %}.
- 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)."
+ Para probar esto, vaya a la pestaña **Code** (Código) del repositorio y cree una nueva versión. Para más información, vea "[Administración de las versiones en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)".
-## Viewing your published package
+## Visualizar tu paquete publicado
-You can view all of the packages you have published.
+Puedes ver todos los paquetes que has publicado.
-{% 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
+## Instalar un paquete publicado
-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)."
+Ahora que publicaste el paquete, querrás utilizarlo como una dependencia en tus proyectos. Para obtener más información, vea "[Trabajo con el registro npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)".
-## Next steps
+## Pasos siguientes
-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.
+El flujo básico que acabas de agregar se ejecuta en cualquier momento que se cree un lanzamiento nuevo en tu repositorio. Pero esto es solo el inicio de lo que puedes hacer con el {% data variables.product.prodname_registry %}. Puedes publicar tu paquete en varios registros con un solo flujo de trabajo, activar el flujo de trabajo para que se ejecute en eventos diferentes tales como una solicitud de cambios fusionada, administrar contenedores, y más.
-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 %}:
+El combinar el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %} puede ayudarte a automatizar casi cualquier aspecto de tu proceso de desarrollo de aplicaciones. ¿Ya está listo para comenzar? Aquí hay algunos recursos útiles para llevar a cabo los siguientes pasos con el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %}:
-- "[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
+- Consulte "[Más información sobre {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" para obtener un tutorial detallado sobre los paquetes de GitHub.
+- Consulte "[Más información sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para obtener un tutorial en profundidad sobre Acciones de GitHub.
+- Consulte "[Trabajo con un registro de {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)" para obtener casos de uso y ejemplos específicos.
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 7704d91fc2..a7091bd706 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -15,12 +15,12 @@ versions:
topics:
- Pull requests
shortTitle: Deleted or changes visibility
-ms.openlocfilehash: d52215a7406edc84bc71022517f848faa9e48600
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 95296f33d9163cd1171481386efd0a2351095c39
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
ms.translationtype: HT
ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146332739'
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191368'
---
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
@@ -32,7 +32,7 @@ Cuando eliminas un repositorio privado, todas sus bifurcaciones privadas tambié
## Eliminar un repositorio público
-Cuando eliminas un repositorio público, se elige una de sus bifurcaciones públicas para ser el nuevo repositorio padre. Todos los otros repositorios se bifurcan fuera de este nuevo repositorio y las solicitudes de extracción siguientes van a este nuevo padre.
+Cuando eliminas un repositorio público, se elige una de sus bifurcaciones públicas para ser el nuevo repositorio ascendente. Todos los otros repositorios se bifurcan fuera de este nuevo repositorio y las solicitudes de incorporación de cambios siguientes van a este nuevo repositorio ascendente.
{% endif %}
@@ -44,9 +44,9 @@ Cuando eliminas un repositorio público, se elige una de sus bifurcaciones públ
## Convertir un repositorio público en un repositorio privado
-Si un repositorio público se convierte en privado, sus bifurcaciones públicas se separan a una nueva red. Como con la eliminación de un repositorio público, se elige una de las bifurcaciones públicas existentes para ser el nuevo repositorio padre y todos los otros repositorios se bifurcan fuera de este nuevo padre. Las solicitudes de extracción siguientes van a este nuevo padre.
+Si un repositorio público se convierte en privado, sus bifurcaciones públicas se separan a una nueva red. Como con la eliminación de un repositorio público, se elige una de las bifurcaciones públicas existentes para ser el nuevo repositorio ascendente y todos los otros repositorios se bifurcan fuera de este nuevo ascendente. Las solicitudes de incorporación de cambios siguientes van a este nuevo repositorio ascendente.
-En otras palabras, las bifurcaciones de un repositorio público permanecerán en su propia red separada del repositorio incluso después de que un repositorio padre se convierte en privado. Esto permite que los propietarios de las bifurcaciones continúen trabajando y colaboren sin interrupción. Si las bifurcaciones públicas no se mueven a una red separada de esta manera, los propietarios de esas bifurcaciones podrían necesitar obtener los [permisos de acceso](/articles/access-permissions-on-github) adecuados a fin de extraer cambios y enviar solicitudes de extracción desde el repositorio principal (ahora privado) y hacia él, incluso si antes no han necesitado esos permisos.
+En otras palabras, las bifurcaciones de un repositorio público permanecerán en su propia red separada del repositorio incluso después de que el repositorio ascendente se convierta en privado. Esto permite que los propietarios de las bifurcaciones continúen trabajando y colaboren sin interrupción. Si las bifurcaciones públicas no se mueven a una red separada de esta manera, los propietarios de esas bifurcaciones podrían necesitar obtener los [permisos de acceso](/articles/access-permissions-on-github) adecuados a fin de extraer cambios y enviar solicitudes de incorporación de cambios desde el repositorio ascendente (ahora privado) y hacia él, incluso si antes no han necesitado esos permisos.
{% ifversion ghes or ghae %} Si un repositorio público tiene habilitado el acceso de lectura anónimo de Git y el repositorio se convierte en privado, todas las bifurcaciones del repositorio perderán el acceso de lectura anónimo de Git y regresarán al valor deshabilitado predeterminado. Si un repositorio bifurcado se convierte en público, los administradores del repositorio pueden volver a habilitar el acceso de lectura anónimo de Git. Para más información, vea "[Habilitación del acceso de lectura anónimo de Git para un repositorio](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)".
{% endif %}
@@ -57,7 +57,7 @@ Si un repositorio público se convierte en privado, y después se elimina, sus b
## Convertir un repositorio privado en un repositorio público
-Si un repositorio privado se convierte en público, cada una de sus bifurcaciones se convierte en un repositorio privado independiente y se vuelve el padre de su propia red de repositorio nueva. Las bifurcaciones privadas nunca se convierten en públicas automáticamente ya que podrían contener confirmaciones confidenciales que no deberían divulgarse públicamente.
+Si un repositorio privado se convierte en público, cada una de sus bifurcaciones se convierte en un repositorio privado independiente y se vuelve el ascendente de su propia red de repositorio nueva. Las bifurcaciones privadas nunca se convierten en públicas automáticamente ya que podrían contener confirmaciones confidenciales que no deberían divulgarse públicamente.
### Eliminar el repositorio público
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
index a66e99ee9a..de0727594d 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository from a template
-intro: You can generate a new repository with the same directory structure and files as an existing repository.
+title: Crear un repositorio desde una plantilla
+intro: Puedes generar un nuevo repositorio con la misma estructura de directorio y los mismos archivos que un repositorio existente.
redirect_from:
- /articles/creating-a-repository-from-a-template
- /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template
@@ -13,45 +13,46 @@ versions:
topics:
- Repositories
shortTitle: Create from a template
+ms.openlocfilehash: 16d124431426e19cf95c768e8a4cdaa5f4da2e17
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160347'
---
-## About repository templates
+## Acerca de las plantillas de repositorio
-Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)."
+Cualquier usuario con permisos de lectura para un repositorio de plantillas puede crear un repositorio a partir de esa plantilla. Para obtener más información, consulte "[Creación de un repositorio de plantillas](/articles/creating-a-template-repository)".
{% tip %}
-**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+**Sugerencia**: También puede crear un repositorio a partir de una plantilla con {% data variables.product.prodname_cli %}. Para obtener más información, consulte "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" en la documentación de {% data variables.product.prodname_cli %}.
{% endtip %}
-You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
+Puedes elegir incluir la estructura de directorio y archivos únicamente desde la rama predeterminada del repositorio plantilla o incluir todas las ramas. Las ramas que se creen a partir de una plantilla tienen historiales sin relación, lo cual significa que no puedes crear solicitudes de cambio ni hacer fusiones entre las ramas.
-Creating a repository from a template is similar to forking a repository, but there are important differences:
-- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit.
-- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph.
-- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly.
+Crear un repositorio a partir de una plantilla es similar a bifurcar un repositorio, pero existen algunas diferencias importantes:
+- Una nueva bifurcación incluye todo el historial de confirmaciones del repositorio padre, mientras que un repositorio creado a partir de una plantilla comienza con una única confirmación.
+- Las confirmaciones en una bifurcación no aparecen en tu gráfico de contribuciones, mientras que las confirmaciones en un repositorio creado a partir de una plantilla sí se muestran en tu gráfico de contribuciones.
+- Una bifurcación puede ser una forma temporaria de contribuir código a un proyecto existente, mientras que crear un repositorio a partir de una plantilla permite iniciar rápidamente un proyecto nuevo.
-For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
+Para obtener más información sobre las bifurcaciones, vea "[Acerca de las bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)".
-## Creating a repository from a template
+## Crear un repositorio desde una plantilla
{% data reusables.repositories.navigate-to-repo %}
-1. Above the file list, click **Use this template**.
+1. Encima de la lista de archivos, haga clic en **Use this template** (Usar esta plantilla).
{% ifversion fpt or ghec %}
-1. Select **Create a new repository**.
+1. Selecciona **Crear un repositorio nuevo**.
- 
+ 
{% note %}
- **Note:** Alternatively, you can open the template in a codespace and publish your work to a new repository later. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+ **Nota:** Como alternativa, puedes abrir la plantilla en un codespace y publicar el trabajo en un nuevo repositorio más adelante. Para obtener más información, consulta "[Creación de un codespace a partir de una plantilla](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)".
- {% endnote %}
-{% endif %}
-{% data reusables.repositories.owner-drop-down %}
-{% data reusables.repositories.repo-name %}
-{% data reusables.repositories.choose-repo-visibility %}
-1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
- 
-{% data reusables.repositories.select-marketplace-apps %}
-8. Click **Create repository from template**.
+ {% endnote %} {% endif %} {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %}
+1. De manera opcional, para incluir la estructura de directorios y los archivos de todas las ramas en la plantilla, y no únicamente aquellos de la rama predeterminada, seleccione **Include all branches** (Incluir todas las ramas).
+  {% data reusables.repositories.select-marketplace-apps %}
+8. Haga clic en **Create repository from template** (Crear repositorio a partir de plantilla).
diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
index 151756761d..e86468b3b5 100644
--- a/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
+++ b/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
@@ -1,6 +1,6 @@
---
-title: Automatically generated release notes
-intro: You can automatically generate release notes for your GitHub releases
+title: Notas de lanzamiento generadas automáticamente
+intro: Puedes generar notas de lanzamiento automáticamente para tus lanzamientos de GitHub
permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release.
versions:
fpt: '*'
@@ -13,71 +13,63 @@ shortTitle: Automated release notes
communityRedirect:
name: Provide GitHub Feedback
href: 'https://github.com/orgs/community/discussions/categories/general'
+ms.openlocfilehash: aee951e6f57492240b5baf8870578409945aefdc
+ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/29/2022
+ms.locfileid: '148185198'
---
+## Acerca de las notas de lanzamiento generadas automáticamente
-## About automatically generated release notes
+Las notas de lanzamiento generadas automáticamente proporcionan una alternativa de automatización para escribir notas de lanzamiento manualmente para tus lanzamientos de {% data variables.product.prodname_dotcom %}. Con las notas de lanzamiento generadas automáticamente, puedes generar rápidamente un resumen del contenido de un lanzamiento. Las notas de la versión generadas automáticamente incluyen una lista de solicitudes de incorporación de cambios combinadas, una lista de colaboradores para la versión y un vínculo a un registro de cambios completo.
-Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. Automatically generated release notes include a list of merged pull requests, a list of contributors to the release, and a link to a full changelog.
+También puedes personalizar tus notas de lanzamiento automatizadas, utilizando etiquetas para crear categorías personalizadas para organizar las solicitudes de cambio que quieras incluir y excluyendo ciertas etiquetas y usuarios para que no aparezcan en la salida.
-You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
+## Crear notas de lanzamiento generadas automáticamente para un lanzamiento nuevo
-## Creating automatically generated release notes for a new release
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
- 
-4. {% ifversion fpt or ghec %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag.
- {% ifversion fpt or ghec %}
- 
-5. If you are creating a new tag, click **Create new tag**.
-
- {% else %}
- 
-{% endif %}
-6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
- {% ifversion fpt or ghec %}
- {% else %}
- {% endif %}
-{%- data reusables.releases.previous-release-tag %}
-7. To the top right of the description text box, click {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% ifversion previous-release-tag %}
- {% else %}
- {% endif %}
-8. Check the generated notes to ensure they include all (and only) the information you want to include.
-9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
- 
-10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
- 
-{%- ifversion fpt or ghec %}
-11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
- 
-{%- endif %}
-12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+3. Haga clic en **Draft a new release** (Borrador de una nueva versión).
+ 
+4. {% ifversion fpt or ghec %}Haga clic en **Choose a tag** (Elegir una etiqueta) y escriba {% else %}Escriba{% endif %} un número para la versión. Como alternativa, selecciona una etiqueta existente.
+ {% ifversion fpt or ghec %} 
+5. Si va a crear una etiqueta, haga clic en **Create new tag** (Crear etiqueta).
+ {% else %}  {% endif %}
+6. Si creaste una etiqueta nueva, utiliza el menú desplegable para seleccionar la rama que contiene el proyecto que quieres lanzar.
+ {% ifversion fpt or ghec %} {% else %} {% endif %} {%- data reusables.releases.previous-release-tag %}
+7. En la parte superior derecha del cuadro de texto de descripción, haz clic en {% ifversion previous-release-tag %}**Generar notas de la versión**{% else %}**Generar automáticamente notas de la versión**{% endif %}. {% ifversion previous-release-tag %} {% else %} {% endif %}
+8. Verifica las notas generadas para garantizar que incluyan toda (y únicamente) la información que quieras incluir.
+9. Opcionalmente, para incluir los archivos binarios tales como programas compilados en tu lanzamiento, arrastra y suelta o selecciona manualmente los archivos en la caja de binarios.
+ 
+10. Para notificar a los usuarios que la versión no está lista para producción y puede ser inestable, seleccione **Es una versión preliminar**.
+  {%- ifversion fpt or ghec %}
+11. Opcionalmente, seleccione **Create a discussion for this release** (Crear un debate para esta versión), después, seleccione el menú desplegable **Category** (Categoría) y haga clic en una categoría para el debate de la versión.
+  {%- endif %}
+12. Si está listo para publicar la versión, haga clic en **Publish release** (Publicar versión). Para trabajar después en la versión, haga clic en **Save draft** (Guardar borrador).
+ 
-## Configuring automatically generated release notes
+## Configurar las notas de lanzamiento generadas automáticamente
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory.
- 
-4. In the file, using the configuration options below, specify in YAML the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. En el campo nombre de archivo, escriba `.github/release.yml` para crear el archivo `release.yml` en el directorio `.github`.
+ 
+4. En el archivo, el utilizar las opciones de configuración siguientes, especificarán en YAML las etiquetas de solicitudes de cambio y los autores que quieras excluir de este lanzamiento. También puedes crear categorías nuevas y listar las etiquetas de la solicitud de cambios que se deben incluir en cada una de ellas.
-### Configuration options
+### Opciones de configuración
-| Parameter | Description |
+| Parámetro | Descripción |
| :- | :- |
-| `changelog.exclude.labels` | A list of labels that exclude a pull request from appearing in release notes. |
-| `changelog.exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from release notes. |
-| `changelog.categories[*].title` | **Required.** The title of a category of changes in release notes. |
-| `changelog.categories[*].labels`| **Required.** Labels that qualify a pull request for this category. Use `*` as a catch-all for pull requests that didn't match any of the previous categories. |
-| `changelog.categories[*].exclude.labels` | A list of labels that exclude a pull request from appearing in this category. |
-| `changelog.categories[*].exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from this category. |
+| `changelog.exclude.labels` | Una lista de etiquetas que excluyen una solicitud de cambios para que no aparezca en las notas de lanzamiento. |
+| `changelog.exclude.authors` | Una lista de manejos de inicio de sesión de usuarios o bots cuyas solicitudes de cambio deben excluirse de las notas de lanzamiento. |
+| `changelog.categories[*].title` | **Obligatorio.** El título de una categoría de cambios en las notas de la versión. |
+| `changelog.categories[*].labels`| **Obligatorio.** Las etiquetas que califican una solicitud de incorporación de cambios para esta categoría. Use `*` como comodín para las solicitudes de incorporación de cambios que no encajen en ninguna de las categorías anteriores. |
+| `changelog.categories[*].exclude.labels` | Una lista de etiquetas que excluye una solicitud de cambio para que no aparezca en esta categoría. |
+| `changelog.categories[*].exclude.authors` | Una lista de manejos de inicio de sesión de usuarios o bots cuyas solicitudes de cambio deben excluirse de esta categoría. |
-### Example configurations
+### Configuraciones de ejemplo
-A configuration for a repository that labels semver releases
+Configuración de un repositorio que etiqueta las versiones de semver
{% raw %}
```yaml{:copy}
@@ -104,7 +96,7 @@ changelog:
```
{% endraw %}
-A configuration for a repository that doesn't tag pull requests but where we want to separate out {% data variables.product.prodname_dependabot %} automated pull requests in release notes (`labels: '*'` is required to display a catchall category)
+Configuración de un repositorio que no etiqueta las solicitudes de incorporación de cambios, pero donde queremos separar solicitudes de incorporación de cambios automatizadas de {% data variables.product.prodname_dependabot %} en las notas la versión (`labels: '*'` es necesario para mostrar una categoría catchall)
{% raw %}
```yaml{:copy}
@@ -124,6 +116,6 @@ changelog:
```
{% endraw %}
-## Further reading
+## Información adicional
-- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)"
+- "[Administración de etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)"
diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
index b08335496a..b1053a7b61 100644
--- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
+++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
@@ -1,6 +1,6 @@
---
title: Entender las conexiones entre repositorios
-intro: Puedes entender mejor las conexiones que existen entre los repositorios si ves la red y las bifurcaciones de este y los proyectos que dependen de él.
+intro: Usa el gráfico de red y la lista de bifurcaciones para comprender las redes de bifurcación.
product: '{% data reusables.gated-features.repository-insights %}'
redirect_from:
- /articles/viewing-a-repository-s-network
@@ -22,16 +22,17 @@ versions:
topics:
- Repositories
shortTitle: Connections between repositories
-ms.openlocfilehash: f1b92a62d0acf9f31a16ce1b7c57850b87c1bf9c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 46cc440093c3ca8dc0952933847a6f04b0446661
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
ms.translationtype: HT
ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147060070'
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191367'
---
## Ver la red de un repositorio
-El gráfico de red muestra el historial de la rama de la red del repositorio completa, incluidas las ramas del repositorio raíz y las ramas de las bifurcaciones que contienen confirmaciones únicas de la red.
+El gráfico de red muestra el historial de ramas de toda la red del repositorio, incluidas las bifurcaciones de rama. Este gráfico es una escala de tiempo de las confirmaciones más recientes y muestra hasta 100 de las ramas insertadas más recientemente. La primera fila hace referencia a la fecha y la primera columna hace referencia al propietario de la rama. Usa teclas de dirección u otros métodos abreviados de teclado para navegar más fácilmente por el gráfico. Se proporcionan en la ventana emergente "Métodos abreviados de teclado disponibles" del gráfico.
+
@@ -51,7 +52,7 @@ El gráfico de red muestra el historial de la rama de la red del repositorio com
El Gráfico de miembros muestra todas las bifurcaciones de un repositorio.
-Las bifurcaciones se detallan alfabéticamente por el nombre de usuario de la persona que bifurcó el repositorio. Puedes hacer clic en el nombre de usuario para ser redirigido a la página de perfil del usuario {% data variables.product.product_name %} o hacer clic en el nombre de la bifurcación para ser redirigido a la bifurcación específica del repositorio.
+Las bifurcaciones se detallan alfabéticamente por la organización o el nombre de usuario de la persona que bifurcó el repositorio. Puedes hacer clic en la organización o el nombre de usuario para que se te redirija a la página de perfil del usuario {% data variables.product.product_name %} o hacer clic en el nombre de la bifurcación para que se te redirija a la bifurcación específica del repositorio.
{% ifversion fpt or ghec %}
diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md
index ea88316e23..3b449e1914 100644
--- a/translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md
+++ b/translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -1,6 +1,6 @@
---
-title: Viewing a file
-intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
+title: Visualización de un archivo
+intro: Puedes ver el contenido del archivo sin procesar o realizar un seguimiento de los cambios en las líneas de un archivo y descubrir cómo evolucionaron las partes del archivo a lo largo del tiempo.
redirect_from:
- /articles/using-git-blame-to-trace-changes-in-a-file
- /articles/tracing-changes-in-a-file
@@ -16,48 +16,54 @@ versions:
topics:
- Repositories
shortTitle: View files and track file changes
+ms.openlocfilehash: 7d34e776cb1747ee749531e49abf6f0e3d052b3b
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179866'
---
-## Viewing or copying the raw file content
+## Visualización o copia del contenido del archivo sin formato
-With the raw view, you can view or copy the raw content of a file without any styling.
+Con la vista sin formato, puede ver o copiar el contenido sin formato de un archivo sin ningún estilo.
{% data reusables.repositories.navigate-to-repo %}
-1. Click the file that you want to view.
-2. In the upper-right corner of the file view, click **Raw**.
-
-3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
+1. Haga clic en el archivo que quiera ver.
+2. En la esquina superior derecha de la vista de archivo, haga clic en **Raw**.
+
+3. Opcionalmente, para copiar el contenido del archivo sin procesar, en la esquina superior derecha de la vista de archivos, haga clic en **{% octicon "copy" aria-label="The copy icon" %}** .
-## Viewing the line-by-line revision history for a file
+## Visualización del historial de revisiones línea a línea de un archivo
-With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
+Con la vista de último responsable, puede ver el historial de revisión línea por línea para todo un archivo, o bien el historial de revisión de una única línea dentro de un archivo si hace clic en {% octicon "versions" aria-label="The prior blame icon" %}. Cada vez que haga clic en {% octicon "versions" aria-label="The prior blame icon" %}, verá la información de revisión anterior para esa línea, incluido quién ha confirmado el cambio y cuándo.
-
+
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+En un archivo o una solicitud de incorporación de cambios, también puede usar el menú {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} para ver el último responsable de Git para una línea o rango de líneas seleccionado.
-
+
{% tip %}
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+**Sugerencia:** En la línea de comandos, también puede usar `git blame` para ver el historial de revisiones de líneas dentro de un archivo. Para más información, vea la [documentación de `git blame` de Git](https://git-scm.com/docs/git-blame).
{% endtip %}
{% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-
+2. Haz clic para abrir el archivo cuyo historial de líneas quieres ver.
+3. En la esquina superior derecha de la vista del archivo, haga clic en **Blame** para abrir la vista del último responsable.
+
+4. Para ver versiones anteriores de una línea concreta, o bien el último responsable siguiente, haga clic en {% octicon "versions" aria-label="The prior blame icon" %} hasta que encuentre los cambios que quiera ver.
+
{% ifversion blame-ignore-revs %}
-## Ignore commits in the blame view
+## Omisión de las confirmaciones en la vista de último responsable
-All revisions specified in the `.git-blame-ignore-revs` file, which must be in the root directory of your repository, are hidden from the blame view using Git's `git blame --ignore-revs-file` configuration setting. For more information, see [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) in the Git documentation.
+Todas las revisiones especificadas en el archivo `.git-blame-ignore-revs`, que debe estar en el directorio raíz del repositorio, se ocultan de la vista de último responsable mediante el valor de configuración `git blame --ignore-revs-file` de Git. Para más información, vea [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) en la documentación de Git.
-1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`.
-2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:
+1. En el directorio raíz del repositorio, cree un archivo con el nombre `.git-blame-ignore-revs`.
+2. Agregue a ese archivo los hash de confirmación que quiera excluir de la vista de último responsable. Se recomienda estructurar el archivo de la siguiente manera, incluidos los comentarios:
```ini
# .git-blame-ignore-revs
@@ -67,19 +73,19 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t
69d029cec8337c616552756310748c4a507bd75a
```
-3. Commit and push the changes.
+3. Confirme e inserte los cambios.
-Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden:
+Ahora, cuando visite la vista de último responsable, las revisiones enumeradas no se incluirán. Verá un banner **Ignoring revisions in .git-blame-ignore-revs** (Omitir revisiones en .git-blame-ignore-revs) que indica que algunas confirmaciones pueden estar ocultas:
-
+
-This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well:
+Este archivo puede ser útil cuando algunas confirmaciones realizan cambios exhaustivos en el código. También puede usar el archivo al ejecutar `git blame` localmente:
```shell
git blame --ignore-revs-file .git-blame-ignore-revs
```
-You can also configure your local git so it always ignores the revs in that file:
+También puedes configurar el repositorio Git local para que siempre omita las revisiones de ese archivo:
```shell
git config blame.ignoreRevsFile .git-blame-ignore-revs
@@ -87,6 +93,6 @@ git config blame.ignoreRevsFile .git-blame-ignore-revs
{% endif %}
-## Bypassing `.git-blame-ignore-revs` in the blame view
+## Omisión de `.git-blame-ignore-revs` en la vista de último responsable
-If the blame view for a file shows **Ignoring revisions in .git-blame-ignore-revs**, you can still bypass `.git-blame-ignore-revs` and see the normal blame view. In the URL, append a `~` to the SHA and the **Ignoring revisions in .git-blame-ignore-revs** will disappear.
+Si la vista de último responsable de un archivo muestra **Ignorando revisiones de .git-blame-ignore-revs**, todavía puedes omitir `.git-blame-ignore-revs` y ver la vista de último responsable normal. En la dirección URL, anexa `~` al SHA para que desaparezca el mensaje **Ignorando revisiones de .git-blame-ignore-revs**.
diff --git a/translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
index b884caa78b..e53a389ec6 100644
--- a/translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
+++ b/translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -1,6 +1,6 @@
---
-title: Ver y actualizar los tickets de soporte
-intro: 'Puedes ver los tickets de soporte{% ifversion ghes or ghec %}, colaborar con colegas en ellos,{% endif %} y responder a {% data variables.contact.github_support %} utilizando el {% data variables.contact.support_portal %}.'
+title: Viewing and updating support tickets
+intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.'
shortTitle: Managing your tickets
versions:
fpt: '*'
@@ -8,62 +8,64 @@ versions:
ghes: '*'
topics:
- Support
-ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147051984'
---
-## Acerca de la administración de tickets
+
+## About ticket management
{% data reusables.support.zendesk-old-tickets %}
-Puede usar el [Portal de soporte técnico de GitHub ](https://support.github.com/) para ver las incidencias de soporte técnico actuales y anteriores, y responder a {% data variables.contact.github_support %}. Después de 120 días, los vales resueltos se archivan{% ifversion ghec or ghes or ghae %}, y solo se pueden ver los vales archivados de las cuentas empresariales{% endif %}.
+You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}. After 120 days, resolved tickets are archived{% ifversion ghec or ghes or ghae %}, and archived tickets can only be viewed for enterprise accounts{% endif %}.
-{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+{% ifversion ghes or ghec %}
+{% data reusables.enterprise-accounts.support-entitlements %}
+{% endif %}
-## Visualización de las incidencias de soporte técnico recientes
+## Viewing your recent support tickets
{% data reusables.support.view-open-tickets %}
-1. En el cuadro de texto, puede leer el historial de comentarios. La respuesta más reciente está en la parte superior.
-
+1. Under the text box, you can read the comment history. The most recent response is at the top.
+
+ 
+
+1. Optionally, to translate the ticket comment, click {% octicon "globe" aria-label="The globe icon" %} and choose your preferred language from the dropdown menu. You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish.
+
+ 
{% ifversion ghec or ghes or ghae %}
-## Visualización de las incidencias de soporte técnico archivadas
+## Viewing your archived support tickets
-Solo puede ver los vales archivados de una cuenta empresarial.
+You can only view archived tickets for an enterprise account.
{% data reusables.support.navigate-to-my-tickets %}
-1. Selecciona el menú desplegable **Mis vales** y haz clic en el nombre de la cuenta de empresa.
+1. Select the **My Tickets** drop-down menu and click the name of the enterprise account.
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
- 
-1. En la tabla "Mis vales", haz clic en **Ver vales archivados**.
+ 
+1. Under the "My tickets" table, click **View archived tickets**.
{% endif %}
-## Actualización de incidencias de soporte técnico
+## Updating support tickets
{% data reusables.support.view-open-tickets %}
-1. Opcionalmente, si se resuelve la incidencia, haga clic en **Cerrar incidencia** en el cuadro de texto.
-
-1. Para responder a al Soporte técnico de GitHub y agregar un nuevo comentario a la incidencia, escriba la respuesta en el cuadro de texto.
-
-1. Para agregar el comentario a la incidencia, haga clic en **Comentario**.
-
+1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
+
+1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
+
+1. To add your comment to the ticket, click **Comment**.
+
{% ifversion ghec or ghes %}
-## Colaboración en incidencias de soporte técnico
+## Collaborating on support tickets
-Puede colaborar con los compañeros en incidencias de soporte técnico mediante el portal de soporte técnico. Los propietarios, los administradores de facturación y otros miembros de la empresa con derechos de soporte técnico pueden ver las incidencias asociadas a una cuenta de empresa o a una organización administrada por una cuenta de empresa. Para más información, vea "[Administración de derechos de soporte técnico para su empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)".
+You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-Adicionalmente a poder ver los tickets, también puedes agregar comentarios para apoyarlos si tu dirección de correo electrónico se copia en el ticket o si la persona que lo abrió utilizó una dirección de correo electrónico con un dominio que esté verificado en la cuenta u organización empresarial que administra una cuenta empresarial. Para más información sobre la comprobación de un dominio, vea "[Comprobación o aprobación de un dominio para la empresa](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" y "[Comprobación o aprobación de un dominio para la organización](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".
+In addition to viewing tickets, you can also add comments to support tickets if your email address is copied on the ticket or if the person who opened the ticket used an email address with a domain that is verified for the enterprise account or organization managed by an enterprise account. For more information about verifying a domain, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Verifying or approving a domain for your organization](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
{% endif %}
-## Información adicional
+## Further reading
-- "[Acerca del soporte técnico de GitHub](/support/learning-about-github-support/about-github-support)"
+- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
diff --git a/translations/es-ES/content/support/learning-about-github-support/about-github-support.md b/translations/es-ES/content/support/learning-about-github-support/about-github-support.md
index f5d6525f05..be735ece17 100644
--- a/translations/es-ES/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/es-ES/content/support/learning-about-github-support/about-github-support.md
@@ -83,6 +83,10 @@ If you have any paid product or are a member of an organization with a paid prod
With {% data variables.product.product_name %}, you have access to support in English and Japanese.
{% endif %}
+{% ifversion fpt or ghec or ghes %}
+{% data reusables.support.support-ticket-translation-option %}
+{% endif %}
+
{% ifversion ghes or ghec %}
To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/4.yml
index 028b8750b6..2d4ef88879 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-5/4.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/4.yml
@@ -29,4 +29,5 @@ sections:
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
- |
- GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
\ No newline at end of file
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/5.yml
index 6fcebfa19b..05de05ac2b 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-5/5.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/5.yml
@@ -1,27 +1,30 @@
date: '2022-08-30'
sections:
bugs:
- - 'Tras desbloquear un repositorio para su acceso temporal, un administrador de sitio no podía administrar los ajustes de los productos de seguridad en el repositorio.'
- - 'Podían aparecer claves SSH administrativas duplicadas en la Consola de administración y en el archivo `/home/admin/.ssh/authorized_keys`.'
- - 'La página de administración del sitio de usuarios individuales en http(s)://HOSTNAME/stafftools/users/USERNAME/admin contenía funciones no dirigidas a GitHub Enterprise Server.'
- - 'En algunos casos, la ejecución de `ghe-cluster-config-apply` podía replicar una configuración vacía en nodos existentes de un clúster.'
- - 'En algunos casos, las ejecuciones de configuración que se iniciaban con `ghe-config-apply` no se completaban, o devolvían un error de tipo `Container count mismatch`.'
- - 'Después de actualizar un certificado TLS autofirmado en una instancia de GitHub Enterprise Server, los elementos de la interfaz de usuario de algunas páginas de la interfaz web no aparecían.'
- - 'La barra de administrador del sitio de la parte superior de la interfaz web contenía un enlace roto al SHA de la versión en ejecución de la aplicación.'
- - 'En algunos casos, las tareas en segundo plano se bloqueaban porque se utiliza una biblioteca simultáneamente a pesar de no ser segura para los subprocesos.'
- - 'Las alertas de los clientes de escaneo de secretos de GitHub Advanced Security no aparecían en la interfaz de usuario web ni en la API REST si el administrador de un sitio no actualizaba directamente a GitHub Enterprise Server 3.4. Las alertas ya son visibles.'
- - 'Cuando un usuario bifurcaba un repositorio en una organización, no se representaba la lista de organizaciones correctamente.'
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
+ - When a user forked a repository into an organization, a long list of organizations would not render properly.
changes:
- - 'Se ha acelerado la generación de conjuntos de soporte gracias a un saneamiento de bitácoras en paralelo. Si deseas más información sobre los conjuntos de soporte, consulta "[Facilitar información al equipo de soporte de GitHub](/support/contacting-github-support/providing-data-to-github-support)."'
- - 'Las API que contienen la ruta `organization` o `org` ahora aceptan el slug o el ID de la organización. Anteriormente, las API solo aceptaban slugs, lo que provocaba que los encabezados de enlaces de puntos de conexión de GitHub Advanced Security no fueran accesibles. Para más información, consulta "[Organizaciones](https://docs.github.com/rest/orgs/orgs)" en la documento de la API REST.'
- - 'El registro de auditoría empresarial incluye ahora más eventos generados por el usuario, como `project.create`. La API REST también devuelve eventos adicionales generados por el usuario, como `repo.create`. Para más información, consulta "[Acceso al registro de auditoría de tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" y "[Uso de la API de registro de auditoría para la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."'
- - 'En algunos casos, las réplicas en caché rechazaban algunas operaciones de Git en repositorios recientemente actualizados. Para obtener más información sobre el almacenamiento en caché de repositorios, consulta la sección "[Acerca del almacenamiento en caché de repositorios](/admin/enterprise-management/caching-repositories/about-repository-caching)".'
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
known_issues:
- - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.'
- - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
- - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.'
- - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres."
- - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.'
- - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.'
- - 'Los límites de recursos que son específicos para procesar ganchos pre-recepción podían ocasionar errores en algunos de ellos.'
- - 'Los servicios de Acciones se deben reiniciar después de restaurar el dispositivo a partir de una copia de seguridad realizada en otro host.'
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-6/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-6/1.yml
index 081045ecd0..6e638df146 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-6/1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-6/1.yml
@@ -1,33 +1,38 @@
date: '2022-08-30'
sections:
bugs:
- - 'Tras desbloquear un repositorio para su acceso temporal, un administrador de sitio no podía administrar los ajustes de los productos de seguridad en el repositorio.'
- - 'Podían aparecer claves SSH administrativas duplicadas en la Consola de administración y en el archivo `/home/admin/.ssh/authorized_keys`.'
- - 'La página de administración del sitio de usuarios individuales en http(s)://HOSTNAME/stafftools/users/USERNAME/admin contenía funciones no dirigidas a GitHub Enterprise Server.'
- - 'En algunos casos, la ejecución de `ghe-cluster-config-apply` podía replicar una configuración vacía en nodos existentes de un clúster.'
- - 'En algunos casos, las ejecuciones de configuración que se iniciaban con `ghe-config-apply` no se completaban, o devolvían un error de tipo `Container count mismatch`.'
- - 'Después de actualizar un certificado TLS autofirmado en una instancia de GitHub Enterprise Server, los elementos de la interfaz de usuario de algunas páginas de la interfaz web no aparecían.'
- - 'En algunos casos, las tareas en segundo plano se bloqueaban porque se utilizaba una biblioteca simultáneamente a pesar de no ser segura para subprocesos.'
- - 'La barra de administrador del sitio de la parte superior de la interfaz web contenía un enlace roto al SHA de la versión en ejecución de la aplicación.'
- - 'Los propietarios de la organización no pudieron establecer el nivel de acceso requerido para crear discusiones.'
- - 'Los usuarios de las discusiones fueron dirigidos incorrectamente a las guías de la comunidad de GitHub.com.'
- - 'En algunos casos, se solicitó incorrectamente a los usuarios que verificasen su correo electrónico antes de crear una discusión.'
- - 'Las alertas de los clientes de escaneo de secretos de GitHub Advanced Security no aparecían en la interfaz de usuario web ni en la API REST si el administrador de un sitio no actualizaba directamente a GitHub Enterprise Server 3.4. Las alertas ya son visibles.'
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - Organization owners were unable to set the level of access required to create discussions.
+ - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
+ - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
changes:
- - 'Se ha acelerado la generación de conjuntos de soporte gracias a un saneamiento de registros en paralelo. Si desea más información sobre los conjuntos de soporte, consulte "[Facilitar información al equipo de soporte de GitHub](/support/contacting-github-support/providing-data-to-github-support)".'
- - 'Las API que contienen la ruta `organization` o `org` ahora aceptan el slug o el ID de la organización. Anteriormente, las API solo aceptaban slugs, lo que provocaba que los encabezados de enlaces de puntos de conexión de GitHub Advanced Security no fueran accesibles. Para más información, consulte "[Organizaciones](https://docs.github.com/rest/orgs/orgs)" en la documento de la API REST.'
- - 'El registro de auditoría empresarial incluye ahora más eventos generados por el usuario, como `project.create`. La API REST también devuelve eventos adicionales generados por el usuario, como `repo.create`. Para más información, consulte "[Acceso al registro de auditoría de tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" y "[Uso de la API de registro de auditoría para la empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)".'
- - 'En algunos casos, las réplicas en caché rechazaban algunas operaciones de Git en repositorios recientemente actualizados. Para obtener más información sobre el almacenamiento en caché de repositorios, consulte la sección "[Acerca del almacenamiento en caché de repositorios](/admin/enterprise-management/caching-repositories/about-repository-caching)".'
- - 'Ahora puede configurar el banner de anuncio global para que se pueda descartar mediante la API de REST. Para obtener más información, consulte "[Personalizar los mensajes de usuario para su empresa](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)".'
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+ - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
known_issues:
- - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.'
- - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
- - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.'
- - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres."
- - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.'
- - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.'
- - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.'
- - 'Los servicios de Acciones se deben reiniciar después de restaurar una instancia a partir de una copia de seguridad realizada en otro host.'
- - 'En la configuración de un repositorio, habilitar la opción de permitir a los usuario acceso de lectura para crear discusiones no habilita esta funcionalidad.'
- - 'En algunos casos, los usuarios no pueden convertir incidencias existentes en discusiones.'
- - 'Los patrones personalizados de examen de secretos tienen `.*`como delimitador de final, específicamente en el campo "Después del secreto". Este delimitador causa inconsistencias en los exámenes de secretos entre repositorios y es posible que note brechas en el historial de un repositorio en el que no se han completado exámenes. Los exámenes incrementales también pueden verse afectados. Para evitar incidencias con los exámenes, modifique el final del patrón para quitar el delimitador `.*`.'
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+ - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+ - In some cases, users cannot convert existing issues to discussions.
+ - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+ - |
+ After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 0da9fed769..1193172cdd 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,18 +1,10 @@
----
-ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
-ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145114233"
----
-Puede usar el condicional `jobs..if` para impedir que se ejecute una tarea si no se cumple una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional.
+You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
-{% data reusables.actions.expression-syntax-if %} Para más información, vea "[Expresiones](/actions/learn-github-actions/expressions)".
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
-### Ejemplo: Solo ejecutar un job para un repositorio específico
+### Example: Only run job for specific repository
-En este ejemplo se usa `if` para controlar cuándo se puede ejecutar el trabajo `production-deploy`. Solo se ejecutará si el repositorio se denomina `octo-repo-prod` y está dentro de la organización `octo-org`. De lo contrario, el trabajo se marcará como _omitido_.
+This example uses `if` to control when the `production-deploy` job can run. It will only run if the repository is named `octo-repo-prod` and is within the `octo-org` organization. Otherwise, the job will be marked as _skipped_.
```yaml{:copy}
name: example-workflow
diff --git a/translations/es-ES/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/es-ES/data/reusables/actions/reusable-workflows-ghes-beta.md
deleted file mode 100644
index 49c849d403..0000000000
--- a/translations/es-ES/data/reusables/actions/reusable-workflows-ghes-beta.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-ms.openlocfilehash: 933805023c32c3e956b510000cdaff7326b880e3
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145069494"
----
-{% ifversion ghes = 3.4 %}
-
-{% note %}
-
-**Nota**: Los flujos de trabajo reutilizables se encuentran actualmente en versión beta y están sujetos a cambios.
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity.md
index 80878d1726..24b839f410 100644
--- a/translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity.md
+++ b/translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
- Starring a repository
- Deleting a repository
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
+- Joining an organization
+
+{% ifversion ghes %}
+A user will also be considered active if their account has been updated by LDAP.
+{% endif %}
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-forks.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-forks.md
index 558a3b591a..a90834faad 100644
--- a/translations/es-ES/data/reusables/enterprise-accounts/emu-forks.md
+++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-forks.md
@@ -1 +1,9 @@
-{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
+---
+ms.openlocfilehash: 484a4230527deebe6f4aeb24ceabdf95eb75b492
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 12/03/2022
+ms.locfileid: "148191334"
+---
+Los {% data variables.enterprise.prodname_managed_users_caps %} no pueden bifurcar repositorios desde fuera de la empresa. {% data variables.enterprise.prodname_managed_users_caps %} pueden bifurcar repositorios privados o internos que pertenezcan a organizaciones en la empresa hacia su espacio de nombres de la cuenta de usuario u otras organizaciones que pertenezcan a la empresa, tal como especifica en la directiva de empresa.
diff --git a/translations/es-ES/data/reusables/repositories/fork-definition-long.md b/translations/es-ES/data/reusables/repositories/fork-definition-long.md
new file mode 100644
index 0000000000..387764634e
--- /dev/null
+++ b/translations/es-ES/data/reusables/repositories/fork-definition-long.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eb538c8746bf9d5ec4cd0e422e50ccc032309812
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 12/03/2022
+ms.locfileid: "148191373"
+---
+Una bifurcación es un nuevo repositorio que comparte la configuración de visibilidad y código con el repositorio “ascendente” original. Las bifurcaciones se suelen usar para iterar ideas o cambios antes de que se vuelvan a proponer al repositorio ascendente, como en proyectos de código abierto o cuando un usuario no tiene acceso de escritura al repositorio ascendente.
diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml
index 1e8377dd72..29dec0fbef 100644
--- a/translations/es-ES/data/ui.yml
+++ b/translations/es-ES/data/ui.yml
@@ -127,7 +127,7 @@ products:
rest:
banner:
api_versioned: The REST API is now versioned.
- api_version_info: For more information, see "About API versioning".
+ api_version_info: For more information, see "About API versioning."
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "About versions of GitHub Docs".
versioning:
about_versions: About REST API versions
diff --git a/translations/fr-FR/content/actions/creating-actions/about-custom-actions.md b/translations/fr-FR/content/actions/creating-actions/about-custom-actions.md
index 4ad1618840..ffb39cfb49 100644
--- a/translations/fr-FR/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/fr-FR/content/actions/creating-actions/about-custom-actions.md
@@ -16,12 +16,12 @@ type: overview
topics:
- Action development
- Fundamentals
-ms.openlocfilehash: ac933a5014750f75373fafa7f8dd52333b79a469
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 1e81bea551ceff1980b0bbe96202f60db0d0e7f2
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: fr-FR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147154572'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191943'
---
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
@@ -35,7 +35,7 @@ Les actions peuvent s’exécuter directement sur un ordinateur ou dans un conte
## Types d’actions
-Vous pouvez créer des actions de conteneur Docker et JavaScript. Les actions nécessitent un fichier de métadonnées pour définir les entrées, les sorties et le point d’entrée principal de votre action. Le nom de fichier des métadonnées doit être soit `action.yml`, soit `action.yaml`. Pour plus d’informations, consultez « [Syntaxe des métadonnées pour {% data variables.product.prodname_actions %} »](/articles/metadata-syntax-for-github-actions).
+Vous pouvez créer des actions composites, de conteneur Docker et JavaScript. Les actions nécessitent un fichier de métadonnées pour définir les entrées, les sorties et le point d’entrée principal de votre action. Le nom de fichier des métadonnées doit être soit `action.yml`, soit `action.yaml`. Pour plus d’informations, consultez « [Syntaxe des métadonnées pour {% data variables.product.prodname_actions %} »](/articles/metadata-syntax-for-github-actions).
| Type | Système d’exploitation |
| ---- | ------------------- |
diff --git a/translations/fr-FR/content/actions/creating-actions/creating-a-composite-action.md b/translations/fr-FR/content/actions/creating-actions/creating-a-composite-action.md
index 382e81006b..f54adf093a 100644
--- a/translations/fr-FR/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/fr-FR/content/actions/creating-actions/creating-a-composite-action.md
@@ -94,7 +94,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
shell: bash
```
{% endraw %}
- This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+ This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, adds the action's path to the runner system path (to locate the `goodbye.sh` script during execution), and runs the `goodbye.sh` script.
For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
diff --git a/translations/fr-FR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/fr-FR/content/actions/creating-actions/creating-a-javascript-action.md
index 5a1ea071a9..8dcb762313 100644
--- a/translations/fr-FR/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/fr-FR/content/actions/creating-actions/creating-a-javascript-action.md
@@ -271,3 +271,10 @@ jobs:
From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+
+## Template repositories for creating JavaScript actions
+
+{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
+
+* [`javascript-action` template repository](https://github.com/actions/javascript-action)
+* [`typescript-action` template repository](https://github.com/actions/typescript-action)
diff --git a/translations/fr-FR/content/actions/learn-github-actions/contexts.md b/translations/fr-FR/content/actions/learn-github-actions/contexts.md
index bdf5bb0bfb..9217298a2a 100644
--- a/translations/fr-FR/content/actions/learn-github-actions/contexts.md
+++ b/translations/fr-FR/content/actions/learn-github-actions/contexts.md
@@ -811,7 +811,7 @@ The `inputs` context contains input properties passed to an action{% ifversion a
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
| Property name | Type | Description |
|---------------|------|-------------|
diff --git a/translations/fr-FR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/fr-FR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0d316eca1f..397d51b308 100644
--- a/translations/fr-FR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/fr-FR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -88,7 +88,7 @@ In addition to the usage limits, you must ensure that you use {% data variables.
{% ifversion fpt or ghes > 3.3 or ghec %}
## Billing for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
diff --git a/translations/fr-FR/content/actions/using-workflows/reusing-workflows.md b/translations/fr-FR/content/actions/using-workflows/reusing-workflows.md
index 2adee6a3f4..1cc0d2d002 100644
--- a/translations/fr-FR/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/fr-FR/content/actions/using-workflows/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
---
{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
## Overview
diff --git a/translations/fr-FR/content/actions/using-workflows/triggering-a-workflow.md b/translations/fr-FR/content/actions/using-workflows/triggering-a-workflow.md
index 8e4adb430f..837875fe9e 100644
--- a/translations/fr-FR/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/fr-FR/content/actions/using-workflows/triggering-a-workflow.md
@@ -123,7 +123,7 @@ You can use activity types and filters to further control when your workflow wil
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
diff --git a/translations/fr-FR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/fr-FR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 4969f6b53e..e6e11c2ff5 100644
--- a/translations/fr-FR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/fr-FR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -72,7 +72,7 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `on.workflow_call`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
@@ -320,7 +320,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+You can use the `if` conditional to prevent a step from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
@@ -945,7 +945,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `jobs..uses`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
diff --git a/translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
index c4156846ca..b15aabcd45 100644
--- a/translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
+++ b/translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
@@ -1,6 +1,6 @@
---
-title: Enabling Server Statistics for your enterprise
-intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.'
+title: Activation des statistiques de serveur pour votre entreprise
+intro: 'Vous pouvez analyser vos propres données agrégées de {% data variables.product.prodname_ghe_server %} et nous aider à améliorer les produits {% data variables.product.company_short %} en activant {% data variables.product.prodname_server_statistics %}.'
versions:
feature: server-statistics
redirect_from:
@@ -8,23 +8,27 @@ redirect_from:
topics:
- Enterprise
shortTitle: Server Statistics
+ms.openlocfilehash: 125651de793a45240008de34845762e6de637040
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191869'
---
+## À propos de {% data variables.product.prodname_server_statistics %}
-## About {% data variables.product.prodname_server_statistics %}
+{% data variables.product.prodname_server_statistics %} collecte les données d’utilisation agrégées à partir de {% data variables.location.product_location %}, que vous pouvez utiliser pour mieux anticiper les besoins de votre organisation, comprendre comment votre équipe travaille et montrer la valeur que vous tirez de {% data variables.product.prodname_ghe_server %}.
-{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
+{% data variables.product.prodname_server_statistics %} collecte uniquement certaines métriques d’agrégation sur les référentiels, les problèmes, les demandes de tirage et d’autres fonctionnalités. Le contenu {% data variables.product.prodname_dotcom %} comme le code, les problèmes, les commentaires ou le contenu de la demande de tirage, n’est pas collecté. Pour plus d’informations, consultez « [À propos de {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics) ».
-{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
-
-By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
+En activant {% data variables.product.prodname_server_statistics %}, vous contribuez également à améliorer {% data variables.product.company_short %}. Les données agrégées que vous fournirez nous aident à comprendre comment nos clients utilisent {% data variables.product.prodname_dotcom %}, et à prendre des décisions plus éclairées pour nos produits, et en fin de compte vous bénéficier.
## Enabling {% data variables.product.prodname_server_statistics %}
-Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Avant de pouvoir activer {% data variables.product.prodname_server_statistics %}, vous devez d’abord connecter votre instance {% data variables.product.prodname_ghe_server %} à {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. Pour plus d’informations, consultez « [Connexion de {% data variables.product.prodname_ghe_server %} à {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud) ».
-You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time.
+Vous pouvez désactiver {% data variables.product.prodname_server_statistics %} à partir de {% data variables.product.prodname_ghe_server %} à tout moment.
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**.
- 
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
+4. Sous « Partager les statistiques du serveur avec GitHub.com », sélectionnez le menu déroulant, puis cliquez sur **Activé** ou **Désactivé**.
+ 
diff --git a/translations/fr-FR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/fr-FR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 98a84270fb..1e67bc7da9 100644
--- a/translations/fr-FR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/fr-FR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
+
| Path without subdomain isolation | Path with subdomain isolation |
| --- | --- |
-| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
-| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
-| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
-| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
-| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
-| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
-| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
+| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
+| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
+| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
+| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
+| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
{%- ifversion viewscreen-and-notebooks %}
-| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
-| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
-{%- else %}
-| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
+| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+{%- ifversion ghes < 3.7 %}
+| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
+| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
+{%- ifversion viewscreen-and-notebooks %}
+| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
+{%- endif %}
+{%- ifversion ghes > 3.4 %}
+| Not supported | `https://containers.HOSTNAME/` |
{%- endif %}
-| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
-| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %}
-| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported | `https://containers.HOSTNAME/` |{% endif %}
## Prerequisites
diff --git a/translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md b/translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
index 4eb59cf491..8bb9f91a34 100644
--- a/translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
+++ b/translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
@@ -1,7 +1,7 @@
---
-title: Restricting network traffic to your enterprise with an IP allow list
+title: Restriction du trafic réseau vers votre entreprise avec une liste d’adresses IP autorisées
shortTitle: Restricting network traffic
-intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
+intro: Vous pouvez restreindre l’accès à votre entreprise et autoriser uniquement l’accès à vos ressources à partir d’adresses IP spécifiées à l’aide d’une liste d’adresses IP autorisées.
permissions: Enterprise owners can configure IP allow lists.
miniTocMaxHeadingLevel: 3
versions:
@@ -17,192 +17,154 @@ topics:
redirect_from:
- /admin/configuration/restricting-network-traffic-to-your-enterprise
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
+ms.openlocfilehash: 8511499e723fdeb4a2d24c2fce627bce56ad9777
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191893'
---
+## À propos des restrictions du trafic réseau
-## About network traffic restrictions
-
-By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+Par défaut, les utilisateurs autorisés peuvent accéder à votre entreprise à partir de n’importe quelle adresse IP. Vous pouvez restreindre l’accès aux ressources {% ifversion ghec %}qui sont la propriété d’organisations d’un compte d’entreprise {% endif %}en configurant une liste d’adresses IP spécifiques autorisées. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
{% ifversion ghec %}
-If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
+Si votre entreprise utilise des {% data variables.product.prodname_emus %} avec Azure AD et OIDC, vous pouvez choisir d’utiliser la fonctionnalité de liste d’adresses IP autorisées de {% data variables.product.company_short %} ou d’utiliser les restrictions de la liste d’autorisations de votre fournisseur d’identité (IdP). Si votre entreprise n’utilise pas de {% data variables.product.prodname_emus %} avec Azure et OIDC, vous pouvez utiliser la fonctionnalité de liste d’autorisations de {% data variables.product.company_short %}.
{% elsif ghae %}
-By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
+Par défaut, les règles du groupe de sécurité réseau (NSG) Azure laissent entrer l’ensemble du trafic sur les ports 22, 80, 443 et 25. Vous pouvez contacter le {% data variables.contact.github_support %} pour configurer des restrictions d’accès pour {% data variables.product.product_name %}.
-For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+Pour des restrictions avec des NSG Azure, contactez le {% data variables.contact.github_support %} avec les adresses IP qui doivent être autorisées à accéder à {% data variables.product.product_name %}. Spécifiez des plages d’adresses au format CIDR (Classless Inter-Domain Routing) standard. Le {% data variables.contact.github_support %} configurera les règles de pare-feu adaptées afin de limiter l’accès réseau via HTTP, SSH, HTTPS et SMTP. Pour plus d’informations, consultez « [Obtention d’aide auprès du {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support) ».
{% endif %}
{% ifversion ghec %}
-## About {% data variables.product.company_short %}'s IP allow list
+## À propos de la liste d’adresses IP autorisées de {% data variables.product.company_short %}
-You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
+Vous pouvez utiliser la liste d’adresses IP autorisées de {% data variables.product.company_short %} pour contrôler l’accès à votre entreprise et aux ressources appartenant aux organisations de votre entreprise.
{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
-## About your IdP's allow list
+## À propos de la liste d’autorisations de votre IdP
-If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
+Si vous utilisez des {% data variables.product.prodname_emus %} avec Azure AD et OIDC, vous pouvez utiliser la liste d’autorisations de votre IdP.
-Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
+L’utilisation de la liste d’autorisations de votre IdP désactive les configurations de liste d’adresses IP autorisées de {% data variables.product.company_short %} pour toutes les organisations de votre entreprise et désactive les API GraphQL pour l’activation et la gestion des listes d’adresses IP autorisées.
-By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
+Par défaut, votre IdP exécute la stratégie d’accès conditionnel sur la connexion SAML ou OIDC interactive initiale à {% data variables.product.company_short %} pour toute configuration de liste d’adresses IP autorisées de votre choix.
-The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps)."
+La stratégie d’accès conditionnel OIDC s’applique uniquement aux requêtes adressées à l’API à l’aide d’un jeton utilisateur-à-serveur, tel qu’un jeton pour une {% data variables.product.prodname_oauth_app %} ou une {% data variables.product.prodname_github_app %} agissant pour le compte d’un utilisateur. La stratégie d’accès conditionnel OIDC ne s’applique pas lorsqu’une {% data variables.product.prodname_github_app %} utilise un jeton serveur-à-serveur. Pour plus d’informations, consultez « [Authentification avec des {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation) » et « [À propos de la prise en charge de la stratégie d’accès conditionnel de vos IdP](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps) ».
-To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
+Pour garantir une utilisation transparente de la stratégie d’accès conditionnel OIDC tout en appliquant la stratégie aux jetons utilisateur-à-serveur, vous devez copier toutes les plages d’adresses IP de chaque {% data variables.product.prodname_github_app %} que votre entreprise utilise dans la stratégie de votre IdP.
-## Using {% data variables.product.company_short %}'s IP allow list
+## Utilisation de la liste d’adresses IP autorisées de {% data variables.product.company_short %}
-### Enabling {% data variables.product.company_short %}'s IP allow list
-{% data reusables.profile.access_org %}
-{% data reusables.profile.org_settings %}
-{% data reusables.organizations.security %}
-1. Under "IP allow list", enable the IP allow list.
- - If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
- 
+### Activation de la liste d’adresses IP autorisées de {% data variables.product.company_short %}
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
+1. Sous « Liste d’adresses IP autorisées », activez la liste d’adresses IP autorisées.
+ - Si vous utilisez des {% data variables.product.prodname_emus %} avec OIDC, sélectionnez le menu déroulant et cliquez sur **GitHub**.
+ 
- Select **Enable IP allow list**.
- 
+ Sélectionnez **Activer la liste d’adresses IP autorisées**.
+ 
- - If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
- 
-1. Click **Save**.
+ - Si vous n’utilisez pas de {% data variables.product.prodname_emus %} avec OIDC, sélectionnez **Activer la liste d’adresses IP autorisées**.
+ 
+1. Cliquez sur **Enregistrer**.
-### Adding an allowed IP address
+### Ajout d’une adresse IP autorisée
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
{% data reusables.identity-and-permissions.ipv6-allow-lists %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
-{% data reusables.identity-and-permissions.check-ip-address %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
-### Allowing access by {% data variables.product.prodname_github_apps %}
+### Autorisation de l’accès par {% data variables.product.prodname_github_apps %}
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
-### Editing an allowed IP address
+### Modification d’une adresse IP autorisée
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+8. Cliquez sur **Update**.
{% data reusables.identity-and-permissions.check-ip-address %}
-### Checking if an IP address is permitted
+### Vérification de l’autorisation d’une adresse IP
{% data reusables.identity-and-permissions.about-checking-ip-address %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
-### Deleting an allowed IP address
+### Suppression d’une adresse IP autorisée
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
-## Using your identity provider's allow list
+## Utilisation de la liste d’autorisations de votre fournisseur d’identité
{% note %}
-**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
+**Remarque :** l’utilisation de la liste verte de votre fournisseur d’identité est uniquement prise en charge pour {% data variables.product.prodname_emus %} avec Azure AD et OIDC.
{% endnote %}
-{% data reusables.profile.access_org %}
-{% data reusables.profile.org_settings %}
-{% data reusables.organizations.security %}
-1. Under "IP allow list", select the dropdown and click **Identity Provider**.
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
+1. Sous « Liste d’adresses IP autorisées », sélectionnez la liste déroulante et cliquez sur **Fournisseur d’identité**.
- 
-1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
+ 
+1. Si vous le souhaitez, pour autoriser les {% data variables.product.prodname_oauth_apps %} {% data variables.product.company_short %} installées à accéder à votre entreprise à partir de n’importe quelle adresse IP, sélectionnez **Ignorer la vérification de l’IdP pour les applications**.
- 
-1. Click **Save**.
+ 
+1. Cliquez sur **Enregistrer**.
{% endif %}
{% ifversion ghae %}
-## Enabling allowed IP addresses
+## Activation des adresses IP autorisées
{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-1. Under "IP allow list", select **Enable IP allow list**.
- 
-4. Click **Save**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
+1. Sous « Liste verte d’adresses IP », sélectionnez **Activer la liste verte d’adresses IP**.
+ 
+4. Cliquez sur **Enregistrer**.
-## Adding an allowed IP address
+## Ajout d’une adresse IP autorisée
-{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
-{% data reusables.identity-and-permissions.check-ip-address %}
+{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## Autorisation de l’accès par {% data variables.product.prodname_github_apps %}
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
-## Editing an allowed IP address
+## Modification d’une adresse IP autorisée
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+8. Cliquez sur **Update**.
{% data reusables.identity-and-permissions.check-ip-address %}
-## Checking if an IP address is permitted
+## Vérification de l’autorisation d’une adresse IP
{% data reusables.identity-and-permissions.about-checking-ip-address %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
-## Deleting an allowed IP address
+## Suppression d’une adresse IP autorisée
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
{% endif %}
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## Utilisation de {% data variables.product.prodname_actions %} avec une liste verte d’adresses IP
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/fr-FR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md b/translations/fr-FR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
index 6336814ef8..1983dfe9c3 100644
--- a/translations/fr-FR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
+++ b/translations/fr-FR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Actions with MinIO storage
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO storage to store data generated by workflow runs.'
+title: Activation de GitHub Actions avec le stockage MinIO
+intro: 'Vous pouvez activer {% data variables.product.prodname_actions %} sur {% data variables.product.prodname_ghe_server %}, et utiliser le stockage MinIO pour stocker les données générées par les exécutions de workflow.'
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
versions:
ghes: '*'
@@ -14,36 +14,35 @@ redirect_from:
- /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
- /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage
shortTitle: MinIO storage
+ms.openlocfilehash: 3d9c6cfca6b81a66185515c8757cef22290ead30
+ms.sourcegitcommit: 8f1801040a84ca9353899a2d1e6782c702aaed0d
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148166568'
---
+## Prérequis
-## Prerequisites
+Avant d’activer {% data variables.product.prodname_actions %}, vérifiez que vous avez effectué les étapes suivantes :
-Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
+* Créez votre compartiment MinIO pour stocker les données générées par les exécutions de workflow. Pour plus d’informations sur l’installation et la configuration de MinIO, consultez « [MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html) » et « [mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html) » dans la documentation MinIO.
-* Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
+ Pour éviter une contention des ressources sur l’appliance, nous vous recommandons d’héberger MinIO séparément de {% data variables.location.product_location %}.
- To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.
+ {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %}
- {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
-{% data reusables.actions.enterprise-common-prereqs %}
+## Activation de {% data variables.product.prodname_actions %} avec un stockage MinIO
-## Enabling {% data variables.product.prodname_actions %} with MinIO storage
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
+1. Sous « Stockage d’artefacts et de journaux », sélectionnez **Amazon S3** et entrez les détails de votre compartiment de stockage :
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.actions %}
-{% data reusables.actions.enterprise-enable-checkbox %}
-1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
+ * **URL du service AWS** : URL de votre service MinIO. Par exemple : `https://my-minio.example:9000`.
+ * **Compartiment AWS S3** : Nom de votre compartiment S3.
+ * **Clé d’accès AWS S3** et **Clé secrète AWS S3** : `MINIO_ACCESS_KEY` et `MINIO_SECRET_KEY` utilisés pour votre instance MinIO.
- * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`.
- * **AWS S3 Bucket**: The name of your S3 bucket.
- * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance.
+ 
+1. Sous « Stockage d’artefacts et de journaux », sélectionnez **Forcer le style de chemin**.
- 
-1. Under "Artifact & Log Storage", select **Force path style**.
-
- 
-{% data reusables.enterprise_management_console.test-storage-button %}
-{% data reusables.enterprise_management_console.save-settings %}
+  {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
{% data reusables.actions.enterprise-postinstall-nextsteps %}
diff --git a/translations/fr-FR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/fr-FR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 625a34aa98..c01ecca7a2 100644
--- a/translations/fr-FR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/fr-FR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}
diff --git a/translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
index 59f87dab08..d22ed3931c 100644
--- a/translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
+++ b/translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
@@ -1,7 +1,7 @@
---
-title: About {% data variables.product.prodname_emus %}
+title: 'À propos d’{% data variables.product.prodname_emus %}'
shortTitle: About managed users
-intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
+intro: 'Vous pouvez gérer de manière centralisée l’identité et l’accès des membres de votre entreprise sur {% data variables.product.prodname_dotcom %} à partir de votre fournisseur d’identité.'
redirect_from:
- /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
- /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
@@ -17,89 +17,94 @@ topics:
- Enterprise
- SSO
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 72d8263029317783e60d8f81f45edc3dbb8b1c8b
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180012'
---
+## À propos d’{% data variables.product.prodname_emus %}
-## About {% data variables.product.prodname_emus %}
+Avec {% data variables.product.prodname_emus %}, vous pouvez contrôler les comptes d’utilisateur de vos membres d’entreprise par le biais de votre fournisseur d’identité (IdP). Les utilisateurs attribués à l’application {% data variables.product.prodname_emu_idp_application %} dans votre IdP sont provisionnés comme nouveaux comptes d’utilisateur dans {% data variables.product.prodname_dotcom %} et ajoutés à votre entreprise. Vous contrôlez les noms d’utilisateur, les données de profil, l’appartenance aux équipes et l’accès aux référentiels à partir de votre IdP.
-With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.
-
-In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+Dans votre IdP, vous pouvez donner à chaque {% data variables.enterprise.prodname_managed_user %} le rôle utilisateur, propriétaire d’entreprise ou gestionnaire de facturation. Les {% data variables.enterprise.prodname_managed_users_caps %} peuvent posséder des organisations au sein de votre entreprise et ajouter d’autres {% data variables.enterprise.prodname_managed_users %} aux organisations et aux équipes qui y sont incluses. Pour plus d’informations, consultez « [Rôles dans une entreprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise) » et « [À propos des organisations](/organizations/collaborating-with-groups-in-organizations/about-organizations) ».
{% ifversion oidc-for-emu %}
-{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
+{% data reusables.enterprise-accounts.emu-cap-validates %} Pour plus d’informations, consultez « [À propos du support de la stratégie d’accès conditionnel de votre fournisseur d’identité](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy) ».
{% endif %}
-You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)."
+Vous pouvez accorder l’accès aux {% data variables.enterprise.prodname_managed_users %} et la capacité à contribuer aux dépôts de votre entreprise, mais les {% data variables.enterprise.prodname_managed_users %} ne peuvent pas créer de contenu public ni collaborer avec d’autres utilisateurs, organisations et entreprises sur le reste de {% data variables.product.prodname_dotcom %}. Pour plus d’informations, consultez « [Capacités et restrictions des {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users) ».
-The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+Les noms d’utilisateur des {% data variables.enterprise.prodname_managed_users %} de votre entreprise et leurs informations de profil telles que les noms d’affichage et les adresses e-mail sont définis par le biais de votre IdP et ne peuvent pas être modifiés par les utilisateurs eux-mêmes. Pour plus d’informations, consultez « [Noms d’utilisateur et informations de profil](#usernames-and-profile-information) ».
-Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)."
+Les propriétaires d’entreprise peuvent auditer toutes les actions des {% data variables.enterprise.prodname_managed_users %} sur {% data variables.product.prodname_dotcom %}. Pour plus d’informations, consultez « [Événements du journal d’audit pour votre entreprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise) ».
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
+Pour utiliser {% data variables.product.prodname_emus %}, vous avez besoin d’un type distinct de compte d’entreprise avec {% data variables.product.prodname_emus %} activé. Pour plus d’informations sur la création de ce compte, consultez « [À propos des entreprises avec des utilisateurs managés](#about-enterprises-with-managed-users) ».
{% note %}
-**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right 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)."
+**Remarque :** il existe plusieurs options pour la gestion des identités et des accès avec {% data variables.product.prodname_ghe_cloud %}, et {% data variables.product.prodname_emus %} n’est pas la meilleure solution pour chaque client. Pour plus d’informations sur la question de savoir si {% data variables.product.prodname_emus %} convient à 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) ».
{% endnote %}
-## About organization membership management
+## À propos de la gestion des appartenances à l’organisation
-Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+Vous pouvez gérer manuellement les appartenances à l’organisation ou vous pouvez mettre à jour les appartenances automatiquement à l’aide de groupes d’IdP. Pour gérer les appartenances à l’organisation par le biais de votre IdP, les membres doivent être ajoutés à un groupe d’IdP et le groupe d’IdP doit être connecté à une équipe de l’organisation. Pour plus d’informations sur la gestion automatique des appartenances aux organisations et aux équipes, consultez « [Gestion des appartenances aux équipes avec des groupes de fournisseurs d’identité](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups) ».
-The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization.
+La façon dont un membre est ajouté à une organisation appartenant à votre entreprise (via des groupes d’IdP ou manuellement) détermine comment il doit être supprimé d’une organisation.
-- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
-- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
+- Si un membre a été ajouté à une organisation manuellement, vous devez le supprimer manuellement. S’il est désattribué de l’application {% data variables.product.prodname_emu_idp_application %} sur votre IdP, il sera suspendu mais pas supprimé de l’organisation.
+- Si un utilisateur est devenu membre d’une organisation parce qu’il a été ajouté à des groupes d’IdP mappés à une ou plusieurs équipes de l’organisation, sa suppression de _tous_ les groupes d’IdP mappés associés à l’organisation le supprimera de l’organisation.
-To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
+Pour découvrir comment un membre a été ajouté à une organisation, vous pouvez filtrer sur la liste des membres par type. Pour plus d’informations, consultez « [Visualisation des personnes dans votre entreprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users) ».
-## Identity provider support
+## Prise en charge des fournisseurs d’identité
-{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
+{% data variables.product.prodname_emus %} prend en charge les fournisseurs d’identité {% ifversion oidc-for-emu %} et les méthodes d’authentification suivants :
| | SAML | OIDC |
|----------------------------------|-----------------------------------------------|-----------------------------------------------|
| Azure Active Directory | {% octicon "check" aria-label="Check icon" %} | {% octicon "check" aria-label="Check icon" %} |
| Okta | {% octicon "check" aria-label="Check icon" %} | |
-{% else %}:
+{% else %} :
{% data reusables.enterprise-accounts.emu-supported-idps %}
{% endif %}
-## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
+## Capacités et restrictions des {% data variables.enterprise.prodname_managed_users %}
-{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests.
+Les {% data variables.enterprise.prodname_managed_users_caps %} peuvent contribuer uniquement aux dépôts privés et internes à leurs entreprises et aux dépôts privés appartenant à leur compte d’utilisateur. Les {% data variables.enterprise.prodname_managed_users_caps %} ont un accès en lecture seule à la large communauté {% data variables.product.prodname_dotcom %}. Ces restrictions de visibilité et d’accès pour les utilisateurs et le contenu s’appliquent à toutes les requêtes, y compris les requêtes d’API.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises.
-* Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
-* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate.
-* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
-* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories.
+* Les {% data variables.enterprise.prodname_managed_users_caps %} ne peuvent pas être invités dans les organisations ou les dépôts extérieurs à l’entreprise. Les {% data variables.enterprise.prodname_managed_users %} ne peuvent pas non plus être invités dans d’autres entreprises.
+* Les collaborateurs externes ne sont pas pris en charge par {% data variables.product.prodname_emus %}.
+* Les {% data variables.enterprise.prodname_managed_users_caps %} ne peuvent pas créer de problèmes ou de demandes de tirage dans des dépôts hors de l’entreprise, ni les commenter ou y ajouter des réactions, ni les surveiller, les dupliquer ou leur ajouter une étoile.
+* Les {% data variables.enterprise.prodname_managed_users_caps %} peuvent voir tous les dépôts publics sur {% data variables.product.prodname_dotcom_the_website %}, mais ne peuvent pas pousser (push) de code sur des dépôts hors de l’entreprise.
+* Seuls les autres membres de l’entreprise peuvent voir les {% data variables.enterprise.prodname_managed_users_caps %} et le contenu qu’ils créent.
+* Les {% data variables.enterprise.prodname_managed_users_caps %} ne peuvent pas suivre les utilisateurs externes à l’entreprise.
+* Les {% data variables.enterprise.prodname_managed_users_caps %} ne peuvent pas créer de Gist ni en commenter.
+* Les {% data variables.enterprise.prodname_managed_users_caps %} ne peuvent pas créer de workflows de démarrage pour {% data variables.product.prodname_actions %}.
+* Les {% data variables.enterprise.prodname_managed_users_caps %} ne peuvent pas installer {% data variables.product.prodname_github_apps %} sur leurs comptes d’utilisateur.
+* Les autres utilisateurs de {% data variables.product.prodname_dotcom %} ne peuvent pas voir, mentionner ou inviter à collaborer un {% data variables.enterprise.prodname_managed_user %}.
+* Vous pouvez choisir si les {% data variables.enterprise.prodname_managed_users %} peuvent créer des dépôts appartenant à leurs comptes d’utilisateur. Pour plus d’informations, consultez « [Application de stratégies de gestion des dépôts dans votre entreprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation) ».
+* Si vous autorisez les {% data variables.enterprise.prodname_managed_users %} à créer des dépôts appartenant à leurs comptes d’utilisateur, ils ne peuvent avoir que des dépôts privés et peuvent uniquement inviter d’autres membres de l’entreprise à collaborer sur leurs dépôts appartenant aux utilisateurs.
* {% data reusables.enterprise-accounts.emu-forks %}
-* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings.
-* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
+* Seuls des dépôts privés et internes peuvent être créés dans les organisations appartenant à une {% data variables.enterprise.prodname_emu_enterprise %}, en fonction des paramètres de visibilité des dépôts de l’entreprise et des organisations.
+* Les {% data variables.enterprise.prodname_managed_users_caps %} sont limités dans leur utilisation de {% data variables.product.prodname_pages %}. Pour plus d’informations, consultez « [À propos de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users) ».
* {% data reusables.copilot.emus-cannot-use-copilot %}
-## Getting started with {% data variables.product.prodname_emus %}
+## Bien démarrer avec {% data variables.product.prodname_emus %}
-Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps.
+Pour que vos développeurs puissent utiliser {% data variables.product.prodname_ghe_cloud %} avec {% data variables.product.prodname_emus %}, vous devez suivre une série d’étapes de configuration.
-1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+1. Pour utiliser {% data variables.product.prodname_emus %}, vous avez besoin d’un type distinct de compte d’entreprise avec {% data variables.product.prodname_emus %} activé. Pour essayer {% data variables.product.prodname_emus %} ou pour discuter des options de migration à partir de votre entreprise existante, contactez l’[équipe commerciale {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
- Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+ Votre contact de l’équipe commerciale GitHub vous aidera à créer votre {% data variables.enterprise.prodname_emu_enterprise %}. Vous devrez fournir l’adresse e-mail de l’utilisateur qui configurera votre entreprise et un code court qui sera utilisé comme suffixe pour les noms d’utilisateur de vos membres d’entreprise. {% data reusables.enterprise-accounts.emu-shortcode %} Pour plus d’informations, consultez « [Noms d’utilisateur et informations de profil](#usernames-and-profile-information) ».
-2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`.
+2. Après avoir créé votre entreprise, vous recevrez un e-mail de {% data variables.product.prodname_dotcom %} vous invitant à choisir un mot de passe pour l’utilisateur de configuration de votre entreprise, qui sera le premier propriétaire de l’entreprise. Utilisez une fenêtre de navigation privée pour la définition du mot de passe. L’utilisateur de configuration est utilisé uniquement pour la configuration de l’authentification unique et l’intégration de l’approvisionnement SCIM pour l’entreprise. Après l’authentification unique réussie, il n’aura plus accès à l’administration du compte d’entreprise. Le nom d’utilisateur de l’utilisateur de configuration est le code court de votre entreprise avec le suffixe `_admin`.
{% note %}
@@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w
{% endnote %}
-3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+3. Une fois que vous vous êtes connecté en tant qu’utilisateur de configuration, nous vous recommandons d’activer l’authentification à 2 facteurs. Pour plus d’informations, consultez « [Configuration de l’authentification à 2 facteurs](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication) ».
-1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). We recommend OIDC, which includes support for Conditional Access Policies (CAP). If you require multiple enterprises with {% data variables.enterprise.prodname_managed_users %} provisioned from one tenant, you must use SAML for each enterprise after the first. If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
+1. Pour démarrer, configurez {% ifversion oidc-for-emu %}comment vos membres s’authentifieront. Si vous utilisez Azure Active Directory comme fournisseur d’identité, vous pouvez choisir entre OpenID Connect (OIDC) et Security Assertion Markup Language (SAML). Nous recommandons OIDC, qui inclut la prise en charge des stratégies d’accès conditionnel (CAP). Si vous avez besoin de plusieurs entreprises avec des {% data variables.enterprise.prodname_managed_users %} provisionnées à partir d’un locataire, vous devez utiliser SAML pour chaque entreprise après la première. Si vous utilisez Okta comme fournisseur d’identité, vous pouvez utiliser SAML pour authentifier vos membres.{% else %} Authentification unique SAML pour votre entreprise. Pour plus d’informations, consultez « [Configuration de l’authentification unique SAML pour les utilisateurs managés Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users) ».{% endif %}
{% ifversion oidc-for-emu %}
- To get started, read the guide for your chosen authentication method.
+ Pour démarrer, lisez le guide relatif à la méthode d’authentification choisie.
- - "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
- - "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+ - « [Configuration d’OIDC pour les utilisateurs managés Enterprise](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users) ».
+ - « [Configuration de l’authentification unique SAML pour les utilisateurs managés Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users) ».
{% endif %}
-4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+4. Une fois que vous avez configuré l’authentification unique, vous pouvez configurer l’approvisionnement SCIM. SCIM est le moyen qu’utilise votre fournisseur d’identité pour créer {% data variables.enterprise.prodname_managed_users %} sur {% data variables.product.prodname_dotcom_the_website %}. Pour plus d’informations sur la configuration de l’approvisionnement SCIM, consultez « [Configuration de l’approvisionnement SCIM pour les utilisateurs managés Enterprise](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users) ».
-5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
+5. Une fois l’authentification et le provisionnement configurés, vous pouvez commencer à gérer l’appartenance à l’organisation pour vos {% data variables.enterprise.prodname_managed_users %} en synchronisant les groupes d’IdP avec les équipes. Pour plus d’informations, consultez « [Gestion des appartenances aux équipes avec les groupes d’un fournisseur d’identité](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups) ».
-If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)."
+Si les membres de votre entreprise doivent utiliser une station de travail pour contribuer aux dépôts sur {% data variables.location.product_location %} à la fois à partir d’un {% data variables.enterprise.prodname_managed_user %} et d’un compte personnel, vous pouvez fournir un support. Pour plus d’informations, consultez « [Support des développeurs avec plusieurs comptes d’utilisateur sur {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom) ».
-## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
+## Authentification comme {% data variables.enterprise.prodname_managed_user %}
-{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}.
+Les {% data variables.enterprise.prodname_managed_users_caps %} doivent s’authentifier par le biais de leur fournisseur d’identité. Pour s’authentifier, un {% data variables.enterprise.prodname_managed_user %} peut accéder au portail d’application de son IdP ou utiliser la page de connexion sur {% data variables.product.prodname_dotcom_the_website %}.
-By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
+Par défaut, lorsqu’un utilisateur non authentifié tente d’accéder à une entreprise qui utilise {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} affiche une erreur 404. Un propriétaire d’entreprise peut éventuellement activer les redirections automatiques vers l’authentification unique (SSO) au lieu de l’erreur 404. Pour plus d’informations, consultez « [Application de stratégies pour les paramètres de sécurité dans votre entreprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users) ».
-{% 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) ».
-### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
+### Authentification comme {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
-1. Navigate to [https://github.com/login](https://github.com/login).
-1. In the "Username or email address" text box, enter your username including the underscore and short code.
- 
- When the form recognizes your username, the form will update. You do not need to enter your password on this form.
-1. To continue to your identity provider, click **Sign in with your identity provider**.
- 
+1. Accédez à [https://github.com/login](https://github.com/login).
+1. Dans la zone de texte « Nom d’utilisateur ou adresse e-mail », entrez votre nom d’utilisateur avec le trait de soulignement et le code court.
+  Quand le formulaire reconnaît votre nom d’utilisateur, il est mis à jour. Vous n’avez pas besoin d’entrer votre mot de passe dans ce formulaire.
+1. Pour continuer et utiliser votre fournisseur d’identité, cliquez sur **Se connecter avec un fournisseur d’identité**.
+ 
-## Usernames and profile information
+## Noms d’utilisateur et informations de profil
-{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+{% data variables.product.product_name %} crée automatiquement un nom d’utilisateur pour chaque personne en normalisant un identificateur fourni par votre fournisseur d’identité. Pour plus d’informations, consultez « [Considérations relatives au nom d’utilisateur pour l’authentification externe](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication) ».
-A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
+Un conflit peut se produire lors de l’approvisionnement des utilisateurs si les parties uniques de l’identificateur fournies par votre fournisseur d’identité sont supprimées lors de la normalisation. Si vous ne parvenez pas à provisionner un utilisateur en raison d’un conflit de nom d’utilisateur, vous devez modifier le nom d’utilisateur fourni par votre IdP. Pour plus d’informations, consultez « [Résolution des problèmes de nom d’utilisateur](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems) ».
{% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %}
-The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
+Le nom de profil et l’adresse e-mail d’un {% data variables.enterprise.prodname_managed_user %} sont également fournis par l’IdP. Les {% data variables.enterprise.prodname_managed_users_caps %} ne peuvent pas changer leur nom de profil ou leur adresse e-mail sur {% data variables.product.prodname_dotcom %} et l’IdP peut uniquement fournir une seule adresse e-mail.
-## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
+## Support des développeurs avec plusieurs comptes d’utilisateur sur {% data variables.location.product_location %}
-People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work.
+Les personnes de votre équipe peuvent avoir besoin de contribuer aux ressources sur {% data variables.location.product_location %} qui se trouvent en dehors de votre {% data variables.enterprise.prodname_emu_enterprise %}. Par exemple, vous pouvez envisager de gérer une entreprise distincte pour les projets open source de votre entreprise. Étant donné qu’un {% data variables.enterprise.prodname_managed_user %} ne peut pas contribuer à des ressources publiques, les utilisateurs doivent gérer un compte personnel distinct pour ce travail.
-People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
+Les personnes qui doivent contribuer à partir de deux comptes d’utilisateur sur {% data variables.location.product_location %} à l’aide d’une seule station de travail peuvent configurer Git pour simplifier le processus. Pour plus d’informations, consultez « [Gestion de plusieurs comptes](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts) ».
diff --git a/translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md b/translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
index 33c6b16923..c6ad8fdac8 100644
--- a/translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
+++ b/translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
@@ -1,7 +1,7 @@
---
-title: About support for your IdP's Conditional Access Policy
+title: À propos de la prise en charge de la stratégie d’accès conditionnel de votre fournisseur d’identité
shortTitle: Conditional access policy
-intro: 'When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} can validate access to your enterprise and its resources using your IdP''s Conditional Access Policy (CAP).'
+intro: 'Lorsque votre entreprise utilise l’authentification unique OIDC, {% data variables.product.prodname_dotcom %} peut valider l’accès à votre entreprise et à ses ressources en utilisant la stratégie d’accès conditionnel de votre fournisseur d’identité.'
product: '{% data reusables.gated-features.emus %}'
versions:
feature: oidc-for-emu
@@ -10,35 +10,40 @@ topics:
- Authentication
- Enterprise
- SSO
+ms.openlocfilehash: aed7008bd008ccfd6303ccbb36f4d6f3bd7002ca
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148179996'
---
-
{% data reusables.enterprise-accounts.azure-emu-support-oidc %}
-## About support for Conditional Access Policies
+## À propos de la prise en charge des stratégies d’accès conditionnel
{% data reusables.enterprise-accounts.emu-cap-validates %}
-{% data variables.product.product_name %} supports CAP for any {% data variables.enterprise.prodname_emu_enterprise %} where OIDC SSO is enabled. {% data variables.product.product_name %} enforces your IdP's IP conditions but cannot enforce your device compliance conditions. Enterprise owners can choose to use this IP allow list configuration instead of {% data variables.product.product_name %}'s IP allow list, and can do so once OIDC SSO is configured. For more information about IP allow lists, see "[Restricting network traffic with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."
+{% data variables.product.product_name %} prend en charge la stratégie d’accès conditionnel pour toutes les {% data variables.enterprise.prodname_emu_enterprise %} où l’authentification unique OIDC est activée. {% data variables.product.product_name %} applique les conditions IP de votre fournisseur d’identité, mais ne peut pas appliquer les conditions de conformité de l’appareil. Les propriétaires d’entreprise peuvent choisir d’utiliser cette configuration de liste d’adresses IP autorisées au lieu de la liste d’adresses IP autorisées de {% data variables.product.product_name %}, et peuvent le faire une fois l’authentification unique OIDC configurée. Pour plus d’informations sur les listes d’adresses IP autorisées, consultez « [Restriction du trafic réseau avec une liste d’adresses IP autorisées](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list) » et « [Gestion des adresses IP autorisées pour votre organisation](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization) ».
-For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."
+Pour plus d’informations sur l’utilisation d’OIDC avec {% data variables.product.prodname_emus %}, consultez [Configurer OIDC pour les utilisateurs d’entreprise managés](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users) et [Migration de SAML à OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc).
-## Considerations for integrations and automations
+## Considérations relatives aux intégrations et aux automatisations
-{% data variables.product.prodname_dotcom %} sends the originating IP address to your IdP for validation against your CAP. To make sure actions and apps are not blocked by your IdP's CAP, you will need to make changes to your configuration.
+{% data variables.product.prodname_dotcom %} envoie l’adresse IP d’origine à votre fournisseur d’identité pour validation par rapport à votre stratégie d’autorisation de connexion. Pour vous assurer que les actions et les applications ne sont pas bloquées par la stratégie d’autorisation de connexion de votre fournisseur d’identité, vous devrez apporter des modifications à votre configuration.
{% data reusables.enterprise-accounts.oidc-gei-warning %}
### {% data variables.product.prodname_actions %}
-Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP.
+Les actions qui utilisent un {% data variables.product.pat_generic %} seront probablement bloquées par la stratégie d’accès conditionnel de votre fournisseur d’identité. Nous recommandons que les {% data variables.product.pat_generic %} soient créés par un compte de service qui est ensuite exempté des contrôles d’IP dans la stratégie d’accès conditionnel de votre fournisseur d’identité.
-If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)."
+Si vous ne pouvez pas utiliser un compte de service, une autre option pour débloquer les actions qui utilisent des {% data variables.product.pat_generic %} consiste à autoriser les plages d’IP utilisées par {% data variables.product.prodname_actions %}. Pour plus d’informations, consultez [À propos des adresses IP de GitHub](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses).
-### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+### {% data variables.product.prodname_github_apps %} et {% data variables.product.prodname_oauth_apps %}
-When {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} make requests on a member's behalf, {% data variables.product.prodname_dotcom %} will send the IP address of the app's server to your IdP for validation. If the IP address of the app's server is not validated by your IdP's CAP, the request will fail.
+Lorsque {% data variables.product.prodname_github_apps %} et {% data variables.product.prodname_oauth_apps %} font des demandes au nom d’un membre, {% data variables.product.prodname_dotcom %} enverra l’adresse IP du serveur de l’application à votre fournisseur d’identité pour validation. Si l’adresse IP du serveur de l’application n’est pas validée par la stratégie d’autorisation de connexion de votre fournisseur d’identité, la demande échouera.
-You can contact the owners of the apps you want to use, ask for their IP ranges, and configure your IdP's CAP to allow access from those IP ranges. If you're unable to contact the owners, you can review your IdP sign-in logs to review the IP addresses seen in the requests, then allow-list those addresses.
+Vous pouvez contacter les propriétaires des applications que vous souhaitez utiliser, demander leurs plages d’adresses IP et configurer la stratégie d’autorisation de connexion de votre fournisseur d’identité pour autoriser l’accès à partir de ces plages d’adresses IP. Si vous ne parvenez pas à contacter les propriétaires, vous pouvez consulter les journaux d’ouverture de session de votre fournisseur d’identité pour voir les adresses IP qui ont fait l’objet des demandes, puis les inscrire sur une liste d’autorisation.
-If you do not wish to allow all of the IP ranges for all of your enterprise's apps, you can also exempt installed {% data variables.product.prodname_github_apps %} and authorized {% data variables.product.prodname_oauth_apps %} from the IdP allow list. If you do so, these apps will continue working regardless of the originating IP address. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)."
+Si vous ne souhaitez pas autoriser toutes les plages d’adresses IP pour toutes les applications de votre entreprise, vous pouvez également exempter les {% data variables.product.prodname_github_apps %} installées et les {% data variables.product.prodname_oauth_apps %} autorisées de la liste d’autorisations du fournisseur d’identité. Si vous le faites, ces applications continueront de fonctionner quelle que soit l’adresse IP d’origine. Pour plus d’informations, consultez « [Application de stratégies pour les paramètres de sécurité dans votre entreprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps) ».
diff --git a/translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
index a7060df4d0..3197e8f6f9 100644
--- a/translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
+++ b/translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Packages with Azure Blob Storage
-intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.'
+title: "Activation de GitHub\_Packages avec Stockage\_Blob Azure"
+intro: 'Configurez {% data variables.product.prodname_registry %} en faisant de Stockage Blob Azure votre stockage externe.'
versions:
ghes: '*'
type: tutorial
@@ -9,42 +9,44 @@ topics:
- Packages
- Storage
shortTitle: Enable Packages with Azure
+ms.openlocfilehash: b851f698baba60323cbaaa69122cacdc92ec83c2
+ms.sourcegitcommit: 3ece72cf2d90987575d369c44101d19d3bb06f76
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190386'
---
-
{% warning %}
-**Warnings:**
-- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
-- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
-- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
+**Avertissements :**
+- Il est essentiel de définir les stratégies d’accès restrictives dont vous avez besoin pour votre compartiment de stockage, car {% data variables.product.company_short %} n’applique pas d’autorisations d’objet spécifiques ou de listes de contrôle d’accès (ACL) supplémentaires à la configuration de votre compartiment de stockage. Par exemple, si vous rendez votre compartiment public, les données du compartiment sont accessibles sur l’Internet public.
+- Nous vous recommandons d’utiliser un compartiment dédié pour {% data variables.product.prodname_registry %}, séparé du compartiment que vous utilisez pour le stockage {% data variables.product.prodname_actions %}.
+- Veillez à configurer le compartiment à utiliser à l’avenir. Nous vous déconseillons de modifier votre stockage après avoir commencé à utiliser {% data variables.product.prodname_registry %}.
{% endwarning %}
-## Prerequisites
+## Prérequis
-Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/).
+Pour pouvoir activer et configurer {% data variables.product.prodname_registry %} sur {% data variables.location.product_location_enterprise %}, vous devez préparer votre compartiment Stockage Blob Azure. Pour préparer votre compartiment Stockage Blob Azure, nous vous recommandons de consulter les documents officiels correspondants sur le [site officiel de la documentation Stockage Blob Azure](https://docs.microsoft.com/en-us/azure/storage/blobs/).
-## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage
+## Activation de {% data variables.product.prodname_registry %} avec Stockage Blob Azure
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_site_admin_settings.packages-tab %}
-{% data reusables.package_registry.enable-enterprise-github-packages %}
-1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %}
+1. Sous « Stockage de packages », sélectionnez **Stockage Blob Azure** et entrez le nom de votre conteneur Azure pour votre compartiment de stockage de packages ainsi que la chaîne de connexion Azure.
- - You must create a storage container prior to setting the container name and connection string.
+ - Vous devez créer un conteneur de stockage avant de définir le nom du conteneur et la chaîne de connexion.
- 
+ 
{% note %}
- **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
- Usage of a SAS Token or SAS URL as connection string is not currently supported.
+ **Remarque :** Vous pouvez trouver votre chaîne de connexion Azure en accédant au menu Clé d’accès dans votre compte de stockage Azure.
+ L’utilisation d’un jeton SAP ou d’une URL SAS en tant que chaîne de connexion n’est pas prise en charge actuellement.
{% endnote %}
{% data reusables.enterprise_management_console.save-settings %}
-## Next steps
+## Étapes suivantes
{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
diff --git a/translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 991873cdca..041431c2e8 100644
--- a/translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -56,7 +56,7 @@ You can enforce policies to control how members of your enterprise on {% data va
Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% ifversion ghes or ghae %}
@@ -166,7 +166,7 @@ Across all organizations owned by your enterprise, you can set the default branc
Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/fr-FR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/fr-FR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 571de5c750..9d4bff714a 100644
--- a/translations/fr-FR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/fr-FR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -1,6 +1,6 @@
---
-title: About billing for GitHub Actions
-intro: 'If you want to use {% data variables.product.prodname_actions %} beyond the storage or minutes included in your account, you will be billed for additional usage.'
+title: À propos de la facturation de GitHub Actions
+intro: 'Si vous souhaitez utiliser {% data variables.product.prodname_actions %} au-delà du stockage ou des minutes inclus dans votre compte, vous êtes facturé pour l’utilisation supplémentaire.'
miniTocMaxHeadingLevel: 3
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
@@ -13,103 +13,104 @@ topics:
- Actions
- Spending limits
shortTitle: Billing for GitHub Actions
+ms.openlocfilehash: fcc8f84b8a11b214ca66e8a3851a1afc9df6213a
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191885'
---
-## About billing for {% data variables.product.prodname_actions %}
+## À propos de la facturation de {% data variables.product.prodname_actions %}
{% data reusables.actions.actions-billing %}
-{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
+{% data reusables.actions.actions-spending-limit-brief %} Pour plus d’informations, consultez « [À propos des limites de dépense](#about-spending-limits) ».
-{% ifversion ghec %}
-If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% ifversion ghec %} Si vous avez acheté {% data variables.product.prodname_enterprise %} par le biais d’un Contrat Entreprise Microsoft, vous pouvez connecter votre ID d’abonnement Azure à votre compte d’entreprise pour activer l’utilisation de {% data variables.product.prodname_actions %} et la payer au-delà des montants inclus avec votre compte. Pour plus d’informations, consultez « [Connexion d’un abonnement Azure à votre entreprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise) ».
{% endif %}
-Minutes reset every month, while storage usage does not.
+Les minutes sont réinitialisées chaque mois, contrairement à l’utilisation du stockage.
-### Included storage and minutes
+### Minutes et stockage inclus
-{% ifversion actions-hosted-runners %}
-{% note %}
+{% ifversion actions-hosted-runners %} {% note %}
-**Note**: Entitlement minutes cannot be used for Windows and Ubuntu runners over 2-cores. These runners will always be charged for, including in public repos. For more information, see "[Per-minute rates for runners](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)."
+**Remarque** : Les minutes de droit d’utilisation ne peuvent pas être utilisées pour les exécuteurs Windows et Ubuntu via 2 cœurs. Ces exécuteurs seront toujours facturés, y compris dans les dépôts publics. Pour plus d’informations, consultez « [Tarifs à la minute pour les exécuteurs](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates) ».
-{% endnote %}
-{% endif %}
+{% endnote %} {% endif %}
-|Product | Storage | Minutes (per month)|
+|Produit | Stockage | Minutes (par mois)|
|------- | ------- | ---------|
-| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
-| {% data variables.product.prodname_pro %} | 1 GB | 3,000 |
-| {% data variables.product.prodname_free_team %} for organizations | 500 MB | 2,000 |
-| {% data variables.product.prodname_team %} | 2 GB | 3,000 |
-| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 |
+| {% data variables.product.prodname_free_user %} | 500 Mo | 2 000 |
+| {% data variables.product.prodname_pro %} | 1 Go | 3 000 |
+| {% data variables.product.prodname_free_team %} pour les organisations | 500 Mo | 2 000 |
+| {% data variables.product.prodname_team %} | 2 Go | 3 000 |
+| {% data variables.product.prodname_ghe_cloud %} | 50 Go | 50 000 |
-Jobs that run on Windows and macOS runners that {% data variables.product.prodname_dotcom %} hosts consume minutes at 2 and 10 times the rate that jobs on Linux runners consume. For example, using 1,000 Windows minutes would consume 2,000 of the minutes included in your account. Using 1,000 macOS minutes, would consume 10,000 minutes included in your account.
+Les travaux qui s’exécutent sur les exécuteurs Windows et macOS hébergés par {% data variables.product.prodname_dotcom %} consomment des minutes à 2 et 10 fois le taux de consommation des travaux sur les exécuteurs Linux. Par exemple, l’utilisation de 1 000 minutes Windows consomme 2 000 des minutes incluses dans votre compte. L’utilisation de 1 000 minutes macOS consomme 10 000 des minutes incluses dans votre compte.
-### Minute multipliers
+### Multiplicateurs de minutes
-| Operating system | Minute multiplier |
+| Système d’exploitation | Multiplicateur de minutes |
|------- | ---------|
| Linux | 1 |
| macOS| 10 |
| Windows | 2 |
-The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+Le stockage utilisé par un dépôt est le stockage total utilisé par les artefacts {% data variables.product.prodname_actions %} et {% data variables.product.prodname_registry %}. Le coût de stockage correspond à l’utilisation totale de tous les référentiels détenus par votre compte. Pour plus d’informations sur les tarifs de {% data variables.product.prodname_registry %}, consultez « [À propos de la facturation pour {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages) ».
- If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
+ Si l’utilisation de votre compte dépasse ces limites et que vous avez défini une limite de dépense supérieure à 0 USD, vous paierez 0,008 USD par Go de stockage, par jour et par minute d’utilisation, selon le système d’exploitation qu’utilise l’exécuteur hébergé par {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} arrondit les minutes et minutes partielles utilisées par chaque travail à la minute entière la plus proche.
{% note %}
-**Note:** Minute multipliers do not apply to the per-minute rates shown below.
+**Remarque :** Les multiplicateurs de minute ne s’appliquent pas aux taux par minute indiqués ci-dessous.
{% endnote %}
-### Per-minute rates
+### Taux par minute
-{% data reusables.billing.billing-standard-runners %}
-{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
+{% data reusables.billing.billing-standard-runners %} {%- ifversion actions-hosted-runners %} {% data reusables.billing.billing-hosted-runners %} {%- endif %}
-- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
-- {% data reusables.user-settings.context_switcher %}
-{% ifversion actions-hosted-runners %}
-- For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
-- Entitlement minutes cannot be used for {% data variables.actions.hosted_runner %}s.
-- The {% data variables.actions.hosted_runner %}s are not free for public repositories.
+- Le nombre de travaux que vous pouvez exécuter simultanément sur tous les dépôts de votre compte d’utilisateur ou d’organisation dépend de votre plan GitHub. Pour plus d’informations, consultez « [Limites d’utilisation et facturation](/actions/reference/usage-limits-billing-and-administration) » pour les exécuteurs hébergés par {% data variables.product.prodname_dotcom %} et [« À propos des exécuteurs auto-hébergés](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits) » pour les limites d’utilisation des exécuteurs auto-hébergés.
+- {% data reusables.user-settings.context_switcher %} {% ifversion actions-hosted-runners %}
+- Pour les {% data variables.actions.hosted_runner %}s, aucun coût supplémentaire n’est facturé pour les configurations qui attribuent des adresses IP statiques publiques à un {% data variables.actions.hosted_runner %}. Pour plus d’informations sur les {% data variables.actions.hosted_runner %}s, consultez « [Utilisation des {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners) ».
+- Les minutes de droit d’utilisation ne peuvent pas être utilisées pour les {% data variables.actions.hosted_runner %}s.
+- Les {% data variables.actions.hosted_runner %} ne sont pas gratuits pour les référentiels publics.
{% endif %}
-## Calculating minute and storage spending
+## Calcul des dépenses de minute et de stockage
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_actions %}
-At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account.
+À la fin du mois, {% data variables.product.prodname_dotcom %} calcule le coût des minutes et du stockage utilisés par rapport au montant inclus dans votre compte.
-### Sample minutes cost calculation
+### Exemple de calcul du coût des minutes
-For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
+Par exemple, si votre organisation utilise {% data variables.product.prodname_team %} et autorise des dépenses illimitées, l’utilisation de 5 000 minutes peut entraîner un coût supplémentaire total des minutes et du stockage de 56 USD, selon les systèmes d’exploitation utilisés pour exécuter les travaux.
-- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
- - 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
- - 2,000 Windows minutes at $0.016 USD per minute = $32 USD.
+- 5 000 minutes (3 000 Linux et 2 000 Windows) = 56 USD (24 USD + 32 USD).
+ - 3 000 minutes Linux à 0,008 USD par minute = 24 USD.
+ - 2 000 minutes Windows à 0,016 USD par minute = 32 USD.
-{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month.
+{% data variables.product.prodname_dotcom %} calcule l’utilisation du stockage pour chaque mois en fonction de l’utilisation horaire pendant le mois concerné.
-### Sample storage cost calculation
+### Exemple de calcul du coût de stockage
-For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be:
+Par exemple, si vous utilisez 3 Go de stockage pendant 10 jours en mars et 12 Go pendant 21 jours en mars, votre utilisation du stockage serait la suivante :
-- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours
-- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours
-- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours
-- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months
+- 3 Go x 10 jours x (24 heures par jour) = 720 Go-heures
+- 12 Go x 21 jours x (24 heures par jour) = 6 048 Go-heures
+- 720 Go-heures + 6 048 Go-heures= 6 768 Go-heures
+- 6 768 Go-heures / (744 heures par mois) = 9,0967 Go-mois
-At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
+À la fin du mois, {% data variables.product.prodname_dotcom %} arrondit votre stockage au Mo le plus proche. Par conséquent, l’utilisation de votre stockage pour mars sera de 9,097 Go.
-Your {% data variables.product.prodname_actions %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
+Votre utilisation de {% data variables.product.prodname_actions %} partage la date de facturation, le mode de paiement et le reçu existants de votre compte. {% data reusables.dotcom_billing.view-all-subscriptions %}
-## About spending limits
+## À propos des limites de dépense
{% data reusables.actions.actions-spending-limit-detailed %}
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+Pour plus d’informations sur la gestion et la modification de la limite de dépense de votre compte, consultez « [Gestion de votre limite de dépense pour {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions) ».
{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
diff --git a/translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md b/translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
index d6daeb7614..976f4d8d93 100644
--- a/translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
+++ b/translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
@@ -1,6 +1,6 @@
---
-title: Managing privately reported security vulnerabilities
-intro: Repository maintainers can manage security vulnerabilities that have been privately reported to them by security reseachers for repositories where private vulnerability reporting is enabled.
+title: Gestion des vulnérabilités de sécurité signalées en privé
+intro: Les chargés de maintenance de dépôt peuvent gérer les vulnérabilités de sécurité qui leur ont été signalées en privé par des chercheurs en sécurité pour les dépôts où la création de rapports de vulnérabilités privés est activée.
permissions: 'Anyone with admin permissions to a repository can see, review, and manage privately-reported vulnerabilities for the repository.'
versions:
fpt: '*'
@@ -11,35 +11,38 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Manage vulnerability reports
+ms.openlocfilehash: 942533788dc6ad9280ddc023f583462c7a0ff7f8
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159787'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## À propos du signalement privé d’une vulnérabilité de sécurité
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to you using a simple form.
+Les rapports de vulnérabilités privés permettent aux chercheurs en sécurité de vous signaler les vulnérabilités directement au moyen d’un simple formulaire.
-When a security researcher reports a vulnerability privately, you are notified and can choose to either accept it, ask more questions, or reject it. If you accept the report, you're ready to collaborate on a fix for the vulnerability in private with the security researcher.
+Quand un chercheur en sécurité signale une vulnérabilité en privé, vous en êtes averti et vous pouvez choisir d’accepter le rapport, de poser d’autres questions ou de le rejeter. Si vous acceptez le rapport, vous êtes prêt à collaborer sur un correctif de la vulnérabilité en privé avec le chercheur en sécurité.
-## Managing security vulnerabilities that are privately reported
+## Gestion des vulnérabilités de sécurité signalées en privé
-{% data variables.product.prodname_dotcom %} notifies repository maintainers when security researchers privately report vulnerabilities in their repository, and sends notifications if maintainers watch the repository or if they have notifications enabled for the repository. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
+{% data variables.product.prodname_dotcom %} avertit les chargés de maintenance de dépôt quand les chercheurs en sécurité signalent en privé des vulnérabilités dans leur dépôt, et envoie des notifications si les chargés de maintenance surveillent le dépôt ou s’ils ont des notifications activées pour le dépôt. Pour plus d’informations, consultez « [Configuration des notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications) ».
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click the advisory you want to review. An advisory that is privately reported will have a status of `Needs triage`.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Cliquez sur l’avis que vous souhaitez consulter. Un avis qui est signalé en privé a l’état `Needs triage`.
- 
+ 
-2. Carefully review the report. You can:
- - Collaborate with the security researcher on a patch in private, by clicking **Start a temporary private fork**. This gives you a place for further discussions with the contributor without changing the status of the proposed advisory from `Needs triage`.
- - Accept the vulnerability report as a draft advisory on {% data variables.product.prodname_dotcom %}, by clicking **Accept and open as draft**. If you choose this option:
- - This doesn't make the report public.
- - The report becomes a draft repository security advisory and you can work on it in the same way as any draft advisory that you create.
- For more information on security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."
- - Reject the report by clicking **Close security advisory**. Where possible, you should add a comment explaining why you don't consider the report a security risk before you close the advisory.
+2. Examinez attentivement le rapport. Vous pouvez :
+ - Collaborez avec le chercheur en sécurité sur un correctif en privé, en cliquant sur **Démarrer une duplication (fork) privée temporaire**. Cette action vous octroie un espace pour d’autres discussions avec le contributeur sans changer le statut de l’avis proposé (`Needs triage`).
+ - Acceptez le rapport de vulnérabilité en tant que brouillon d’avis sur {% data variables.product.prodname_dotcom %}, en cliquant sur **Accepter et ouvrir en tant que brouillon**. Si vous choisissez cette option :
+ - Cela ne rend pas le rapport public.
+ - Le rapport devient un brouillon d’avis de sécurité de dépôt et vous pouvez travailler dessus de la même façon que sur tout brouillon d’avis que vous créez.
+ Pour plus d’informations sur les avis de sécurité, consultez « [À propos des avis de sécurité des dépôts](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories) ».
+ - Rejetez le rapport en cliquant sur **Fermer l’avis de sécurité**. Si possible, avant de fermer l’avis, vous devez ajouter un commentaire expliquant pourquoi vous ne considérez pas le rapport comme un risque pour la sécurité.
- 
\ No newline at end of file
+ 
diff --git a/translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md b/translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
index 521fa86d92..1dda217aaa 100644
--- a/translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
+++ b/translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
@@ -1,6 +1,6 @@
---
-title: Privately reporting a security vulnerability
-intro: Some public repositories configure security advisories so that anyone can report security vulnerabilities directly and privately to the maintainers.
+title: Signalement privé d’une vulnérabilité de sécurité
+intro: Certains dépôts publics configurent des avis de sécurité afin que tout le monde puisse signaler les failles de sécurité directement et en privé aux chargés de maintenance.
versions:
fpt: '*'
ghec: '*'
@@ -10,61 +10,64 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Privately reporting
+ms.openlocfilehash: 7f4f208bd2724608cf9955efd82a256c3479e884
+ms.sourcegitcommit: 2ff4a43f0b14939da79d56c54402cfee8d90ae23
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/17/2022
+ms.locfileid: '148169556'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## À propos du signalement privé d’une vulnérabilité de sécurité
-Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
+Les chercheurs en sécurité se sentent souvent responsables d’alerter les utilisateurs sur une vulnérabilité qui pourrait être exploitée. S’il n’y a pas d’instructions claires sur la façon de contacter les chargés de maintenance du dépôt contenant la vulnérabilité, les chercheurs en sécurité risquent de ne pas avoir d’autre choix que de publier le rapport sur la vulnérabilité sur les réseaux sociaux, d’envoyer des messages directement au chargé de maintenance ou même de créer des problèmes publics. Cette situation peut potentiellement conduire à une divulgation publique des détails de la vulnérabilité.
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to repository maintainer using a simple form.
+Les rapports de vulnérabilités privés permettent aux chercheurs en sécurité de signaler les vulnérabilités au chargé de maintenance de dépôt directement au moyen d’un simple formulaire.
-For security researchers, the benefits of using private vulnerability reporting are:
-- Less frustration, and less time spent trying to figure out how to contact the maintainer.
-- A smoother process for disclosing and discussing vulnerability details.
-- The opportunity to discuss vulnerability details privately with repository maintainer.
+Pour les chercheurs en sécurité, les avantages de l’utilisation des rapports de vulnérabilité privés sont les suivants :
+- Moins de frustration et moins de temps passé à essayer de trouver comment contacter le chargé de maintenance.
+- Un processus plus fluide pour la divulgation et la discussion des détails de la vulnérabilité.
+- La possibilité de discuter des détails des vulnérabilités en privé avec le chargé de maintenance de dépôt.
{% note %}
-**Note:** If the repository doesn't have private vulnerabiliy reporting enabled, you need to initiate the reporting process by following the instructions in the security policy for the repository, or create an issue asking the maintainers for a preferred security contact. For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
+**Remarque :** Si le signalement de vulnérabilité privé n’est pas activé pour le dépôt, vous devez lancer le processus de signalement en suivant les instructions de la stratégie de sécurité pour le dépôt ou créer un problème demandant aux chargés de maintenance un contact de sécurité préféré. Pour plus d’informations, consultez « [À propos de la divulgation coordonnée des vulnérabilités de sécurité](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github) ».
{% endnote %}
-## Privately reporting a security vulnerability
+## Signalement privé d’une vulnérabilité de sécurité
-Security researchers can privately report a security vulnerability to repository maintainers.
+Les chercheurs en sécurité peuvent signaler en privé une vulnérabilité de sécurité aux chargés de maintenance de dépôt.
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **Report a vulnerability** to open the advisory form.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Cliquez sur **Signaler une vulnérabilité** pour ouvrir le formulaire d’avis.
- 
+ 
-2. Fill in the advisory details form.
+2. Remplissez le formulaire de détails de l’avis.
{% tip %}
- **Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
+ **Conseil :** Dans ce formulaire, seuls le titre et la description sont obligatoires. (Dans le formulaire général de brouillon d’avis de sécurité, qui est lancé par le chargé de maintenance de dépôt, la spécification de l’écosystème est également requise.) Toutefois, nous recommandons que les chercheurs en sécurité fournissent autant d’informations que possible dans le formulaire afin que les chargés de maintenance puissent prendre une décision éclairée au sujet du rapport soumis. Vous pouvez adopter le modèle utilisé par nos chercheurs en sécurité à partir du {% data variables.product.prodname_security %}, qui est disponible sur le référentiel [`github/securitylab` ](https://github.com/github/securitylab/blob/main/docs/report-template.md). »
{% endtip %}
- For more information about the fields available and guidance on filling in the form, see "[Creating a repository security advisory](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[Best practices for writing repository security advisories](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
+ Pour plus d’informations sur les champs disponibles et des conseils sur le remplissage du formulaire, consultez « [Création d’un avis de sécurité de dépôt](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory) » et « [Bonnes pratiques pour écrire des avis de sécurité de dépôt](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories) ».
-1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
+1. En bas du formulaire, cliquez sur **Envoyer le rapport**. {% data variables.product.prodname_dotcom %} affiche un message vous informant que les chargés de maintenance ont été avertis et que vous avez un crédit en attente pour cet avis de sécurité.
- 
+ 
{% tip %}
- **Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
+ **Conseil :** Quand le rapport est soumis, {% data variables.product.prodname_dotcom %} ajoute automatiquement le rapporteur de la vulnérabilité en tant que collaborateur et utilisateur crédité sur l’avis proposé.
{% endtip %}
-1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge that private fork.
+1. Si vous souhaitez commencer à résoudre le problème, cliquez sur **Démarrer une duplication privée temporaire**. Notez que seul le chargé de maintenance de dépôt peut fusionner cette duplication (fork) privée.
- 
+ 
-The next steps depend on the action taken by the repository maintainer. For more information, see "[Managing privately reported security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)."
+Les étapes suivantes dépendent de l’action effectuée par le chargé de maintenance de dépôt. Pour plus d’informations, consultez « [Gestion des vulnérabilités de sécurité signalées en privé](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities) ».
diff --git a/translations/fr-FR/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/fr-FR/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
index 8f8ea3d298..1fe90ac8a5 100644
--- a/translations/fr-FR/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
+++ b/translations/fr-FR/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository security advisory
-intro: You can create a draft security advisory to privately discuss and fix a security vulnerability in your open source project.
+title: Création d’un avis de sécurité de dépôt
+intro: Vous pouvez créer un brouillon d’avis de sécurité pour discuter en privé et corriger une vulnérabilité de sécurité dans votre projet open source.
redirect_from:
- /articles/creating-a-maintainer-security-advisory
- /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
@@ -15,31 +15,31 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Create repository advisories
+ms.openlocfilehash: 5c78a8b0c0a2d5085a876de2b0788ef093c4c6b1
+ms.sourcegitcommit: 74c60a4564bcc17e47b5a67941ac6d9fe13b6a5c
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/30/2022
+ms.locfileid: '148186154'
---
-
-Anyone with admin permissions to a repository can create a security advisory.
+Toute personne disposant d’autorisations d’administrateur sur un dépôt peut créer un avis de sécurité.
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-## Creating a security advisory
+## Création d’un avis de sécurité
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **New draft security advisory** to open the draft advisory form. The fields marked with an asterisk are required.
- 
-1. Type a title for your security advisory.
-{% data reusables.repositories.security-advisory-edit-details %}
-{% data reusables.repositories.security-advisory-edit-severity %}
-{% data reusables.repositories.security-advisory-edit-cwe-cve %}
-{% data reusables.repositories.security-advisory-edit-description %}
-1. Click **Create draft security advisory**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. Cliquez sur **Nouveau brouillon d’avis de sécurité** pour ouvrir le formulaire de brouillon d’avis. Les champs marqués d’un astérisque sont obligatoires.
+ 
+1. Tapez un titre pour votre avis de sécurité.
+{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
+1. Cliquez sur **Créer un brouillon d’avis de sécurité**.
+ 
-## Next steps
+## Étapes suivantes
-- Comment on the draft security advisory to discuss the vulnerability with your team.
-- Add collaborators to the security advisory. For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)."
-- Privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)."
-- Add individuals who should receive credit for contributing to the security advisory. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)."
-- Publish the security advisory to notify your community of the security vulnerability. For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
+- Commentez le brouillon d’avis de sécurité pour discuter de la vulnérabilité avec votre équipe.
+- Ajoutez des collaborateurs à l’avis de sécurité. Pour plus d’informations, consultez « [Ajout d’un collaborateur à un avis de sécurité de dépôt](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory) ».
+- Collaborez en privé pour corriger la vulnérabilité dans une duplication (fork) privée temporaire. Pour plus d’informations, consultez « [Collaboration dans une duplication privée temporaire pour résoudre une vulnérabilité de sécurité de dépôt](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability) »
+- Ajoutez des personnes à créditer pour leur contribution à l’avis de sécurité. Pour plus d’informations, consultez « [Modification d’un avis de sécurité de dépôt](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories) ».
+- Publiez l’avis de sécurité pour informer votre communauté de la vulnérabilité de sécurité. Pour plus d’informations, consultez « [Publication d’un avis de sécurité de dépôt](/code-security/repository-security-advisories/publishing-a-repository-security-advisory) ».
diff --git a/translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md b/translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
index aeb477c475..0436757da7 100644
--- a/translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
+++ b/translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a codespace for a repository
-intro: You can create a codespace for a branch in a repository to develop online.
+title: Création d’un codespace pour un dépôt
+intro: Vous pouvez créer un espace de code pour une branche dans un dépôt à développer en ligne.
redirect_from:
- /github/developing-online-with-github-codespaces/creating-a-codespace
- /github/developing-online-with-codespaces/creating-a-codespace
@@ -14,95 +14,100 @@ topics:
- Fundamentals
- Developer
shortTitle: Create a codespace for a repo
+ms.openlocfilehash: 409c946feda4ffbd3d9ab615b6ea07fabee3f530
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188319'
---
+## À propos de la création d’un codespace pour un dépôt
-## About creating a codespace for a repository
+{% data reusables.codespaces.ways-to-create-a-codespace %} Utilisez les onglets de cet article afin d’afficher des instructions pour chacune de ces méthodes de création d’un codespace.
-{% data reusables.codespaces.ways-to-create-a-codespace %} Use the tabs in this article to display instructions for each of these ways of creating a codespace.
-
-{% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+{% data reusables.codespaces.starting-new-project-template %} Pour plus d’informations, consultez « [Création d’un codespace à partir d’un modèle](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template) ».
{% note %}
-**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[Using Codespaces in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
+**Remarque** : Si vous utilisez un IDE JetBrains, vous pouvez utiliser {% data variables.product.prodname_cli %} pour créer un codespace. Vous pouvez ensuite utiliser l’application JetBrains Gateway pour ouvrir le codespace dans un IDE JetBrains. Pour plus d’informations, consultez « [Utilisation de Codespaces dans votre IDE JetBrains](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide) ».
{% endnote %}
-You can use {% data variables.product.prodname_github_codespaces %} on your personal {% data variables.product.prodname_dotcom_the_website %} account, with the quota of free use included each month for accounts on the Free and Pro plans. {% data reusables.codespaces.codespaces-continue-by-paying %}
+Vous pouvez utiliser {% data variables.product.prodname_github_codespaces %} sur votre compte personnel {% data variables.product.prodname_dotcom_the_website %}, avec le quota d’utilisation gratuite inclus chaque mois pour les comptes associés aux plans Gratuit et Pro. {% data reusables.codespaces.codespaces-continue-by-paying %}
-Organizations can enable members and outside collaborators to create and use codespaces at the organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
+Les organisations peuvent, à leurs frais, permettre aux membres et aux collaborateurs externes de créer et d’utiliser des codespaces. Pour plus d'informations, consultez « [Activation de {% data variables.product.prodname_github_codespaces %} pour votre organisation](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization) ».
{% data reusables.codespaces.codespaces-are-personal %}
-If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch.
+Si vous créez un codespace à partir d’un dépôt, le codespace est associé à une branche spécifique, qui ne peut pas être vide. Vous pouvez créer plusieurs codespaces par référentiel, voire par branche.
{% data reusables.codespaces.you-can-see-all-your-codespaces %}
-### The codespace creation process
+### Processus de création d’un codespace
-When you create a codespace, a number of steps happen to create and connect you to your development environment:
+Lorsque vous créez un codespace, un certain nombre d’étapes sont nécessaires pour créer votre environnement de développement et vous y connecter :
-- Step 1: VM and storage are assigned to your codespace.
-- Step 2: Container is created and your repository is cloned.
-- Step 3: You can connect to the codespace.
-- Step 4: Codespace continues with post-creation setup.
+- Étape 1 : la machine virtuelle et le stockage sont affectés à votre codespace.
+- Étape 2 : le conteneur est créé et votre dépôt est cloné.
+- Étape 3 : vous pouvez vous connecter au codespace.
+- Étape 4 : le codespace continue avec la configuration après création.
-For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
+Pour plus d’informations sur ce qui se passe lorsque vous créez un codespace, consultez « [Présentation approfondie](/codespaces/getting-started/deep-dive) ».
-For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)."
+Pour plus d’informations sur le cycle de vie d’un codespace, consultez « [Cycle de vie des codespaces](/codespaces/getting-started/the-codespace-lifecycle) ».
-If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+Si vous souhaitez utiliser des crochets Git pour votre codespace, vous devriez configurer des crochets à l’aide de [scripts de cycle de vie `devcontainer.json`](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), tels que `postCreateCommand`, à l’étape 4. Étant donné que votre conteneur de codespace est créé une fois le dépôt cloné, aucun [répertoire de modèles Git](https://git-scm.com/docs/git-init#_template_directory) configuré dans l’image conteneur ne s’applique pas à votre codespace. Les crochets doivent plutôt être installés après la création du codespace. Pour plus d’informations sur l’utilisation de `postCreateCommand`, consultez la [référence `devcontainer.json`](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) dans la documentation de {% data variables.product.prodname_vscode_shortname %}.
{% data reusables.codespaces.use-visual-studio-features %}
{% data reusables.codespaces.prebuilds-crossreference %}
-## Creating a codespace for a repository
+## Création d’un codespace pour un dépôt
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create a codespace for.
+1. Sous le nom du dépôt, utilisez le menu déroulant « Branche », puis sélectionnez la branche pour laquelle vous souhaitez créer un codespace.
- 
+ 
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. Cliquez sur le bouton **{% octicon "code" aria-label="The code icon" %} Code**, puis sur l’onglet **Codespaces**.
- 
+ 
- If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
+ Si les codespaces de ce dépôt sont facturables à une organisation ou à son entreprise parente, un message s’affiche sous le bouton **Créer un codespace sur BRANCH** vous indiquant qui doit payer pour le codespace.
-1. Create your codespace, either using the default options, or after configuring advanced options:
+1. Créez votre codespace en utilisant les options par défaut, ou après configuration d’options avancées :
- * **Use the default options**
+ * **Utiliser les options par défaut**
- To create a codespace using the default options, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). Alternatively, if you don't currently have any codespaces for this repository, you can click **Create codespace on BRANCH**.
+ Pour créer un codespace en utilisant les options par défaut, cliquez sur le signe plus ({% octicon "plus" aria-label="The plus icon" %}). Sinon, si vous n’avez aucun codespace pour ce dépôt, vous pouvez cliquer sur **Créer un codespace sur BRANCH**.
- * **Configure options**
+ * **Configurer les options**
- To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file:
+ Pour configurer des options avancées pour votre codespace, telles qu’un autre type de machine ou un fichier `devcontainer.json` particulier :
- 1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab and select **New with options**.
+ 1. Cliquez sur les points de suspension ( **...** ) en haut à droite de l’onglet **Codespaces** et sélectionnez **Nouveau avec des options**.
- 
+ 
- 1. On the options page for your codespace, choose your preferred options from the dropdown menus.
+ 1. Dans la page d’options pour votre codespace, choisissez vos options préférées dans les menus déroulants.
- 
+ 
{% note %}
- **Notes**
+ **Remarques**
- * You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
- * The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
- * For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
- * For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+ * Vous pouvez marquer d’un signet la page d’options afin de disposer d’un moyen rapide de créer un codespace pour ce dépôt et cette branche.
+ * La page [https://github.com/codespaces/new](https://github.com/codespaces/new) offre un moyen rapide de créer un codespace pour tout dépôt et toute branche. Vous pouvez accéder rapidement à cette page en tapant `codespace.new` dans la barre d’adresse de votre navigateur.
+ * Pour plus d’informations sur le fichier `devcontainer.json`, consultez « [Présentation des conteneurs de développement](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson) ».
+ * Pour plus d’informations sur les types de machines, consultez « [Modification du type de machine pour votre codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types) ».
* {% data reusables.codespaces.codespaces-machine-type-availability %}
{% endnote %}
- 1. Click **Create codespace**.
+ 1. Cliquez sur **Créer codespace**.
{% endwebui %}
@@ -116,30 +121,30 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
{% data reusables.cli.cli-learn-more %}
-To create a new codespace, use the `gh codespace create` subcommand.
+Pour créer un codespace, utilisez la sous-commande `gh codespace create`.
```shell
gh codespace create
```
-You are prompted to choose a repository. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
+Vous êtes invité à choisir un dépôt. Si les codespaces de ce dépôt sont facturables à une organisation ou à son entreprise parente, un message s’affiche vous indiquant qui doit payer pour le codespace. Vous êtes invité à choisir une branche, un fichier de configuration de conteneur de développement (si plusieurs sont disponibles) et un type de machine (si plusieurs sont disponibles).
-Alternatively, you can use flags to specify some or all of the options:
+Vous pouvez également utiliser des indicateurs pour spécifier tout ou partie des options :
```shell
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
```
-In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
+Dans cet exemple, remplacez `owner/repo` par l’identificateur du dépôt. Remplacez `branch` par le nom de la branche, ou le hachage SHA complet de la validation, dont vous souhaitez l’extraction initiale dans le codespace. Si vous utilisez l’indicateur `-r` sans l’indicateur `b`, le codespace est créé à partir de la branche par défaut.
-Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+Remplacez `path` par le chemin du fichier de configuration de conteneur de développement que vous souhaitez utiliser pour le nouveau codespace. Si vous omettez cet indicateur et que plusieurs fichiers de conteneur de développement sont disponibles, vous êtes invité à en choisir un dans une liste. Pour plus d’informations sur le fichier de configuration de conteneur de développement, consultez « [Présentation des conteneurs de développement](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) ».
-Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
+Remplacez `machine-type` par un identificateur valide pour un type de machine disponible. Les identificateurs sont des chaînes telles que : `basicLinux32gb` et `standardLinux32gb`. Les types de machines disponibles dépendent du dépôt, de votre compte personnel et de votre emplacement. Si vous entrez un type de machine non valide ou indisponible, les types disponibles sont affichés dans le message d’erreur. Si vous omettez cet indicateur et que plusieurs types de machines sont disponibles, vous êtes invité à en choisir un dans une liste.
-For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
+Pour obtenir des détails complets sur les options de cette commande, consultez [le manuel de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_create).
{% endcli %}
-## Further reading
-- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
-- "[Adding an 'Open in {% data variables.product.prodname_github_codespaces %}' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
+## Pour aller plus loin
+- « [Ouverture d’un codespace existant](/codespaces/developing-in-codespaces/opening-an-existing-codespace) »
+- « [Ajout d’un badge « Ouvrir dans {% data variables.product.prodname_github_codespaces %} »](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge) »
diff --git a/translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
index 842a20e971..d89d43b971 100644
--- a/translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
+++ b/translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
@@ -1,6 +1,6 @@
---
-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.
+title: Création d’un codespace à partir d’un modèle
+intro: 'Si vous démarrez un nouveau projet, vous pouvez créer un codespace à partir d’un modèle vide ou choisir un modèle spécialement conçu pour le type de travail que vous souhaitez effectuer.'
versions:
fpt: '*'
ghec: '*'
@@ -11,92 +11,95 @@ topics:
- Developer
shortTitle: Create a codespace from a template
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 9e7ee0d110e962fa755f5f57cc70bc3cab341808
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188311'
---
+## À propos des modèles pour {% data variables.product.prodname_github_codespaces %}
-## 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.
+Si vous démarrez un nouveau projet, vous pouvez commencer rapidement à travailler sur le développement en créant un codespace à partir d’un modèle. Vous pourrez travailler sur votre projet dans un environnement de développement cloud, enregistrer vos fichiers dans le cloud et publier votre travail dans un nouveau dépôt distant que vous pouvez partager avec d’autres personnes ou cloner sur votre ordinateur local.
{% 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)."
+**Remarque** : Les codespaces créés à partir d’un modèle, plutôt que d’un dépôt, sont toujours facturés à votre compte personnel. Pour plus d’informations, consultez « [À propos de la facturation de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces) ».
{% 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)."
+Vous pouvez commencer à partir d’un modèle vide, choisir parmi les modèles gérés par {% data variables.product.company_short %} pour les technologies populaires telles que React ou Jupyter Notebook ou lancer un codespace à partir d’un dépôt de modèles sur {% data variables.product.prodname_dotcom %}. Si vous utilisez un modèle vide, vous commencez avec un répertoire vide, avec accès à des ressources de calcul cloud et aux outils, langages et environnements d’exécution qui sont préinstallés avec l’image codespace par défaut. Avec d’autres modèles, vous obtenez des fichiers de démarrage pour la technologie que vous utilisez ainsi que des fichiers supplémentaires tels qu’un fichier README, un fichier `.gitignore` et des fichiers de configuration de conteneur de développement comportant une configuration d’environnement personnalisée. Pour plus d’informations sur les conteneurs de développement et l’image par défaut, consultez « [Présentation des conteneurs de développement](/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.
+Par exemple, si vous créez un codespace à partir du modèle React de {% data variables.product.company_short %}, vous arrivez dans un espace de travail contenant des fichiers de modèle pour une application simple, tels que `index.js`, `app.js` et `package.json`. Peu après l’ouverture du codespace, un serveur de développement démarre automatiquement et vous pouvez afficher l’application en cours d’exécution sous un simple onglet de navigateur dans le client web {% data variables.product.prodname_vscode_shortname %}.
-
+
-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.
+Les fichiers et la configuration inclus dans les modèles sont définis dans des dépôts de modèles. Le dépôt de modèles est cloné dans votre codespace quand vous créez celui-ci. Ensuite, le lien est rompu et votre codespace n’est pas lié à un dépôt distant tant que vous n’y publiez pas.
{% 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)."
+**Conseil :** Pour aider les utilisateurs à démarrer avec votre framework, bibliothèque ou autre projet, vous pouvez configurer un dépôt de modèles à utiliser avec {% data variables.product.prodname_github_codespaces %}. Pour plus d’informations, consultez « [Configuration d’un dépôt de modèles pour {% 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
+## Création d’un codespace à partir d’un modèle {% data variables.product.company_short %}
-Templates maintained by {% data variables.product.company_short %}, including the blank template, are available from the "Your codespaces" page.
+Les modèles gérés par {% data variables.product.company_short %}, y compris le modèle vide, sont disponibles à partir de la page « Vos codespaces ».
-{% 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.
+{% data reusables.codespaces.your-codespaces-procedure-step %} {% data reusables.codespaces.view-all-templates-step %}
+1. Si vous le souhaitez, pour afficher le dépôt de modèles contenant les fichiers d’un modèle, cliquez sur le nom du modèle.
- 
+ 
-1. Under the template you want to launch, click **Use this template**.
+1. Sous le modèle que vous souhaitez lancer, cliquez sur **Utiliser ce modèle**.
- 
+ 
{% data reusables.codespaces.template-codespaces-default-editor %}
-## Creating a codespace from a template repository
+## Création d’un codespace à partir d’un dépôt de modèles
-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)."
+Vous pouvez créer un codespace à partir de n’importe quel dépôt de modèles, puis publier votre travail dans un nouveau dépôt quand vous êtes prêt. Pour plus d’informations sur les dépôts de modèles, consultez « [Création d’un dépôt à partir d’un modèle](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates) ».
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.codespaces.open-template-in-codespace-step %}
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.codespaces.open-template-in-codespace-step %}
{% note %}
- **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)."
+ **Remarque :** Si vous êtes chargé de maintenance du dépôt de modèles et que vous souhaitez commiter les modifications apportées au dépôt de modèles lui-même, vous devez créer un codespace à partir de la liste déroulante **{% octicon "code" aria-label="The code icon" %} Code**. Pour plus d’informations, consultez « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository) ».
{% endnote %}
{% data reusables.codespaces.template-codespaces-default-editor %}
-## Publishing to a repository on {% data variables.product.product_name %}
+## Publication dans un dépôt sur {% data variables.product.product_name %}
{% data reusables.codespaces.about-publishing-templates %}
-### Publishing from {% data variables.product.prodname_vscode_shortname %}
+### Publication à partir de {% 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:
+Quand un codespace est publié, vous avez accès à un plus grand nombre d’options pour personnaliser votre expérience {% data variables.product.prodname_github_codespaces %}. Par exemple, vous pouvez :
-- 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)").
+- Changez le type de machine de votre codespace pour vous assurer que vous utilisez les ressources appropriées pour le travail que vous effectuez (consultez « [Changement du type d’ordinateur pour votre codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace) »).
+- Autorisez {% data variables.product.prodname_dotcom %} à utiliser automatiquement GPG pour signer les commits que vous effectuez dans votre codespace (consultez « [Gestion de la vérification GPG pour {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces) »).
+- Partagez des secrets chiffrés avec votre codespace (consultez « [Gestion des secrets chiffrés pour vos codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) »).
-### Publishing from {% data variables.product.prodname_dotcom_the_website %}
+### Publication à partir de {% 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.
+Vous pouvez publier un codespace non publié à partir de la page « Vos codespaces » sur {% data variables.product.prodname_dotcom_the_website %}. Cela est utile si vous souhaitez publier un codespace que vous n’avez pas ouvert dans votre navigateur. Dans ce cas, votre travail est conservé dans un dépôt, mais il n’y a pas de lien entre votre codespace existant et le nouveau dépôt. Toutefois, vous pouvez accéder au nouveau dépôt et créer un codespace à partir de là ; ce codespace sera alors connecté au dépôt.
{% data reusables.codespaces.your-codespaces-procedure-step %}
-1. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**.
+1. En regard du codespace non publié, cliquez sur les points de suspension ( **...** ), puis sélectionnez **Publier dans un nouveau dépôt**.
- 
-1. Choose a name for your new repository, set it as **Public** or **Private**, and click **Create repository**.
+ 
+1. Choisissez un nom pour votre nouveau dépôt, définissez-le comme **Public** ou **Privé**, puis cliquez sur **Créer le dépôt**.
- 
-1. Optionally, to view the new repository, click **See repository**.
+ 
+1. Si vous le souhaitez, pour afficher le nouveau dépôt, cliquez sur **Voir le dépôt**.
-## Further reading
+## Pour aller plus loin
-- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)"
-- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)"
-- "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
\ No newline at end of file
+- « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository) »
+- « [Cycle de vie des codespaces](/codespaces/getting-started/the-codespace-lifecycle) »
+- « [Utilisation du contrôle de code source dans votre codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace) »
diff --git a/translations/fr-FR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/translations/fr-FR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
index b9f817a834..bb0fc7af48 100644
--- a/translations/fr-FR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
+++ b/translations/fr-FR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
@@ -9,12 +9,12 @@ topics:
- Codespaces
redirect_from:
- /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds
-ms.openlocfilehash: e0962e410f2227a23ff98c8a3e7995ea8ec8a914
-ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.openlocfilehash: eecb77b541cc735fcf788fbc5da6960cabad899d
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: fr-FR
-ms.lasthandoff: 11/09/2022
-ms.locfileid: '148158796'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191917'
---
## Vue d’ensemble
diff --git a/translations/fr-FR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/fr-FR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
index c7605e66fc..3657599525 100644
--- a/translations/fr-FR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
+++ b/translations/fr-FR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Configuring prebuilds
+title: Configuration des prébuilds
shortTitle: Configure prebuilds
-intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
+intro: Vous pouvez configurer votre projet pour prédéfinir automatiquement un espace de code chaque fois que vous envoyez une modification à votre référentiel.
versions:
fpt: '*'
ghec: '*'
@@ -10,106 +10,111 @@ topics:
- Codespaces
- Set up
permissions: People with admin access to a repository can configure prebuilds for the repository.
+ms.openlocfilehash: dbb355e150695f27d1d6a7fa51eccc33a0ebde4f
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159116'
---
+Vous pouvez configurer une configuration de prébuild pour combiner une branche spécifique de votre dépôt avec un fichier de configuration de conteneur de développement spécifique.
-You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file.
+Toutes les branches créées à partir d’une branche parente activée par prébuild obtiennent généralement des prébuilds pour la même configuration de conteneur de développement. En effet, la prébuild pour les branches enfants qui utilisent la même configuration de conteneur de développement que la branche parente est, pour une grande partie, identique, afin que les développeurs puissent bénéficier d’un temps de création de codespace plus rapide sur ces branches également. Pour plus d’informations, consultez « [Présentation des conteneurs de développement](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) ».
-Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because prebuilds for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+En règle générale, lorsque vous configurez des prébuilds pour une branche, celles-ci sont disponibles pour plusieurs types de machines. Toutefois, si votre référentiel fait plus de 32 Go, les prébuilds ne seront pas disponibles pour les types de machines 2 cœurs et 4 cœurs, car le stockage qu’elles fournissent est limité à 32 Go.
-Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB.
+## Prérequis
-## Prerequisites
+Les prébuilds sont créées avec {% data variables.product.prodname_actions %}. {% data variables.product.prodname_actions %} doit donc être activé pour le dépôt pour lequel vous configurez des prébuilds. Pour plus d’informations, consultez « [Gestion des paramètres {% data variables.product.prodname_actions %} pour un dépôt](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository) ».
-Prebuilds are created using {% data variables.product.prodname_actions %}. As a result, {% data variables.product.prodname_actions %} must be enabled for the repository for which you are configuring prebuilds. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)."
-
-## Configuring prebuilds
+## Configuration des prébuilds
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
+1. Dans la section « Configuration de prébuild » de la page, cliquez sur **Configurer la prébuild**.
- 
+ 
-1. Choose the branch for which you want to set up prebuilds.
+1. Choisissez la branche pour laquelle vous souhaitez configurer des prébuilds.
- 
+ 
{% note %}
- **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
+ **Remarque** :Toutes les branches créées à partir d’une branche de base activée par prébuild obtiennent généralement des prébuilds pour la même configuration de conteneur de développement. Par exemple, si vous activez les prébuilds pour un fichier de configuration de conteneur de développement sur la branche par défaut du dépôt, dans la plupart des cas, vous obtenez aussi les prébuilds pour la même configuration de conteneur de développement.
{% endnote %}
-1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
+1. Si vous le souhaitez, dans le menu déroulant **Fichier de configuration** qui s’affiche, choisissez le fichier de configuration `devcontainer.json` que vous souhaitez utiliser pour vos prébuilds. Pour plus d’informations, consultez « [Présentation des conteneurs de développement](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson) ».
- 
+ 
-1. Choose how you want to automatically trigger prebuild updates.
+1. Choisissez la façon dont vous souhaitez déclencher automatiquement les mises à jour des prébuilds.
- * **Every push** (the default setting) - With this setting, prebuilds will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies.
- * **On configuration change** - With this setting, prebuilds will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The {% data variables.product.prodname_actions %} workflow that updates the prebuilds will run less often, so this option will use fewer {% data variables.product.prodname_actions %} minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created.
- * **Scheduled** - With this setting, you can have your prebuilds updated on a custom schedule that's defined by you. This can reduce consumption of {% data variables.product.prodname_actions %} minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes.
+ * **À chaque envoi** (paramètre par défaut) : avec ce paramètre, les prébuilds sont mises à jour à chaque envoi (push) vers la branche donnée. Vous avez ainsi la certitude que les codespaces générés à partir d’une prébuild contiennent toujours la dernière configuration de codespace, ainsi que les dépendances récemment ajoutées ou mises à jour.
+ * **Lors d’une modification de la configuration** : avec ce paramètre, les prébuilds sont mises à jour chaque fois que les fichiers de configuration associés d’un dépôt et d’une branche donnés sont mis à jour. Vous avez ainsi la certitude que les modifications apportées aux fichiers de configuration du conteneur de développement pour le référentiel sont utilisées lorsqu’un codespace est généré à partir d’une prébuild. Le workflow {% data variables.product.prodname_actions %} qui met à jour les prébuilds s’exécute moins souvent. Cette option utilise donc moins de minutes {% data variables.product.prodname_actions %}. Toutefois, cette option ne garantit pas que les codespaces incluront toujours des dépendances récemment ajoutées ou mises à jour. Celles-ci peuvent donc être ajoutées ou mises à jour manuellement après la création d’un codespace.
+ * **Mise à jour planifiée** : avec ce paramètre, vous pouvez mettre à jour vos prébuilds selon une planification personnalisée définie par vous. Cela peut réduire la consommation des minutes {% data variables.product.prodname_actions %}. Toutefois, avec cette option, des codespaces n’utilisant pas les dernières modifications de la configuration de conteneur de développement peuvent être créés.
- 
+ 
-1. Optionally, select **Reduce prebuild available to only specific regions** to create prebuilds only in specified regions. Select the regions in which you want prebuilds to be available.
+1. Si vous le souhaitez, sélectionnez **Réduire la disponibilité des prébuilds à des régions spécifiques** pour créer des prébuilds uniquement dans les régions spécifiées. Sélectionnez les régions dans lesquelles vous souhaitez que les prébuilds soient disponibles.
- By default, prebuilds are created in all of the available regions, incurring storage charges per prebuild.
+ Par défaut, les prébuilds sont créées dans toutes les régions disponibles, ce qui entraîne des frais de stockage par prébuild.
- 
+ 
{% note %}
- **Notes**:
- * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
- * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
+ **Remarques**:
+ * La prébuild dans chaque région entraîne des frais de stockage individuels. Vous ne devez donc activer les prébuilds que pour les régions dans lesquelles vous savez qu’elles seront utilisées. Pour plus d’informations, consultez « [À propos de la facturation de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds) ».
+ * Les développeurs peuvent définir leur région par défaut pour {% data variables.product.prodname_github_codespaces %}, ce qui permet d’activer les prébuilds pour un plus petit nombre de régions. Pour plus d’informations, consultez « [Définition de votre région par défaut pour {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces) ».
{% endnote %}
-1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved.
+1. Si vous le souhaitez, sous **Historique des modèles**, définissez le nombre de versions de prébuild à conserver. Vous pouvez entrer n’importe quel nombre compris entre 1 et 5. Le nombre par défaut de versions enregistrées est de 2, ce qui signifie que seules la dernière prébuild et la version précédente sont enregistrées.
- 
+ 
- Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. This setting allows you to set the number of retained versions to a level that is appropriate for your needs.
+ En fonction de vos paramètres de déclencheur de prébuild, votre prébuild peut changer avec chaque modification push ou sur chaque modification de configuration de conteneur de développement. La conservation des versions antérieures des prébuilds vous permet de créer une prébuild à partir d’une validation antérieure avec une configuration de conteneur de développement différente de celle de la prébuild actuelle. Ce paramètre vous permet de définir le nombre de versions conservées à un niveau adapté à vos besoins.
- If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration.
+ Si vous définissez le nombre de versions de prébuilds à enregistrer sur 1, {% data variables.product.prodname_github_codespaces %} enregistre uniquement la dernière version de la prébuild et supprime l’ancienne version chaque fois que le modèle est mis à jour. Cela signifie que vous n’obtiendrez pas d’espace de code prédéfini si vous revenez à une configuration de conteneur de développement plus ancienne.
- There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+ Un coût de stockage est associé à chaque version de prébuild conservée. Par exemple, si vous générez des prébuilds dans 4 régions et conservez 2 versions, vous serez facturé pour le stockage de 8 prébuilds au maximum. Pour plus d’informations sur la facturation, consultez « [À propos de la facturation de {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing) ».
-1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation.
+1. Ajoutez éventuellement des utilisateurs ou des équipes à avertir quand l’exécution du workflow de prébuild échoue pour cette configuration. Vous pouvez commencer à taper un nom d’utilisateur, un nom d’équipe ou un nom complet, puis cliquer sur le nom une fois qu’il apparaît pour les ajouter à la liste. Les utilisateurs ou les équipes que vous ajoutez recevront un e-mail lorsque des échecs de prébuild se produisent, avec un lien vers les journaux d’exécution du workflow pour faciliter l’examen approfondi.
- 
+ 
-1. Optionally, at the bottom of the page, click **Show advanced options**.
+1. Si vous le souhaitez, en bas de la page, cliquez sur **Afficher les options avancées**.
- 
+ 
- In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
+ Dans la section « Options avancées », si vous sélectionnez **Désactiver l’optimisation de la prébuild**, les codespaces sont créés sans prébuild si le dernier workflow de prébuild a échoué ou est en cours d’exécution. Pour plus d’informations, consultez « [Résolution des problèmes liés aux prébuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used) ».
-1. Click **Create**.
+1. Cliquez sur **Créer**.
{% data reusables.codespaces.prebuilds-permission-authorization %}
-After you create a prebuild configuration it is listed on the {% data variables.product.prodname_github_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuilds in the regions you specified, based on the branch and dev container configuration file you selected.
+Après la création d’une configuration de prébuild, celle-ci est listée dans la page {% data variables.product.prodname_github_codespaces %} des paramètres de votre dépôt. Un workflow {% data variables.product.prodname_actions %} est mis en file d’attente, puis exécuté pour créer des prébuilds dans les régions que vous avez spécifiées, en fonction de la branche et du fichier de configuration de conteneur de développement que vous avez sélectionnés.
-
+
-For information about editing and deleting prebuild configurations, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)."
+Pour plus d’informations sur la modification et la suppression des configurations de prébuild, consultez « [Gestion des prébuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds) ».
-## Configuring environment variables
+## Configuration des variables d’environnement
-To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)."
+Pour permettre au processus de prébuild d’accéder aux variables d’environnement nécessaires à la création de votre environnement de développement, vous pouvez les définir sous la forme de secrets de référentiel {% data variables.product.prodname_codespaces %} ou de secrets d’organisation {% data variables.product.prodname_codespaces %}. Pour plus d’informations, consultez « [Ajout de secrets pour un référentiel](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository) » et « [Ajout de secrets pour une organisation](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization) ».
-Secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces.
+Les secrets que vous créez de cette façon seront accessibles par toute personne qui crée un codespace à partir de ce dépôt. Si ce n’est pas ce que vous souhaitez, vous pouvez définir le secret `CODESPACES_PREBUILD_TOKEN`. Le secret `CODESPACES_PREBUILD_TOKEN` est utilisé uniquement pour les prébuilds et sa valeur n’est pas accessible dans les codespaces des utilisateurs.
-Prebuilds cannot use any user-level secrets while building your environment, because these are not available until after the codespace has been created.
+Les prébuilds ne peuvent pas utiliser de secrets au niveau utilisateur lors de la création de votre environnement, car ceux-ci ne sont disponibles qu’après la création du codespace.
-## Configuring time-consuming tasks to be included in the prebuild
+## Configuration des tâches chronophages à inclure dans la prébuild
-You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)."
+Vous pouvez utiliser les commandes `onCreateCommand` et `updateContentCommand` de votre `devcontainer.json` pour inclure les processus chronophages dans le cadre de la création de la prébuild. Pour plus d’informations, consultez la documentation {% data variables.product.prodname_vscode %}, « [Informations de référence sur devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts) ».
-`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at creation of the prebuild and at subsequent updates to it. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update.
+`onCreateCommand` ne s’exécute qu’une seule fois, lors de la création de la prébuild, tandis que `updateContentCommand` s’exécute lors de la création de la prébuild et de ses mises à jour ultérieures. Les builds incrémentielles doivent être incluses dans `updateContentCommand`, car elles représentent la source de votre projet et doivent être incluses pour chaque mise à jour de la prébuild.
-## Further reading
+## Pour aller plus loin
-- "[Allowing a prebuild to access other repositories](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)"
-- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
+- « [Autorisation d’une prébuild à accéder à d’autres dépôts](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories) »
+- « [Résolution des problèmes liés aux prébuilds](/codespaces/troubleshooting/troubleshooting-prebuilds) »
diff --git a/translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
index 36e4e0ae51..199968e4d5 100644
--- a/translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
+++ b/translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
@@ -1,7 +1,7 @@
---
-title: Adding an "Open in GitHub Codespaces" badge
+title: "Ajout d’un badge «\_Ouvrir dans GitHub Codespaces\_»"
shortTitle: Add a Codespaces badge
-intro: You can add a badge to a Markdown file in your repository which people can click to create a codespace.
+intro: 'Vous pouvez ajouter un badge à un fichier Markdown dans votre dépôt, sur lequel les utilisateurs peuvent cliquer pour créer un codespace.'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -10,50 +10,55 @@ type: how_to
topics:
- Codespaces
- Set up
+ms.openlocfilehash: c69a815501f5943a56d32af3e58cd7850a69588b
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158780'
---
+## Vue d'ensemble
-## Overview
+L’ajout d’un badge « Ouvrir dans {% data variables.product.prodname_github_codespaces %} » à un fichier Markdown permet aux utilisateurs de créer facilement un codespace pour votre dépôt.
-Adding an "Open in {% data variables.product.prodname_github_codespaces %}" badge to a Markdown file gives people an easy way to create a codespace for your repository.
+
-
+Quand vous créez un badge, vous pouvez choisir des options de configuration spécifiques pour le codespace que le badge va créer.
-When you create a badge you can choose specific configuration options for the codespace that the badge will create.
+Quand les utilisateurs cliquent sur le badge, ils accèdent à la page des options avancées de création d’un codespace, avec les options que vous avez choisies présélectionnées. Pour plus d’informations sur la page des options avancées, consultez « [Création d’un codespace pour un dépôt](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository) ».
-When people click the badge they'll be taken to the advanced options page for codespace creation, with the options you chose preselected. For more information about the advanced options page, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+Dans la page des options avancées, les utilisateurs peuvent modifier les paramètres présélectionnés si nécessaire, puis cliquer sur **Créer un codespace**.
-From the advanced options page, users can change the preselected settings if required, then click **Create codespace**.
-
-## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge
+## Création d’un badge « Ouvrir dans {% data variables.product.prodname_github_codespaces %} »
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create the badge for.
+1. Sous le nom du dépôt, utilisez le menu déroulant « Branche », puis sélectionnez la branche pour laquelle vous voulez créer le badge.
- 
+ 
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. Cliquez sur le bouton **{% octicon "code" aria-label="The code icon" %} Code**, puis sur l’onglet **Codespaces**.
- 
+ 
-1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab, then click **New with options**.
+1. Cliquez sur les points de suspension ( **...** ) en haut à droite de l’onglet **Codespaces**, puis cliquez sur **Nouveau avec des options**.
- 
+ 
-1. On the advanced options page for codespace creation, select the values you want to be preselected in each field.
+1. Dans la page des options avancées de création d’un codespace, sélectionnez les valeurs que vous voulez présélectionner dans chaque champ.
- 
+ 
-1. Copy the URL from the browser's address bar.
-1. Add the following Markdown to, for example, the `README.md` file of your repository:
+1. Copiez l’URL de la barre d’adresses du navigateur.
+1. Ajoutez, par exemple, le Markdown suivant au fichier `README.md` de votre dépôt :
```Markdown{:copy}
[](COPIED-URL)
```
- For example:
+ Par exemple :
```Markdown
[](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2)
```
- In the above example, `0000000` will be the reference number of your repository. The other details in the URL are determined by the values you selected in the fields on the advanced options page.
+ Dans l’exemple ci-dessus, `0000000` correspond au numéro de référence de votre dépôt. Les autres détails inclus dans l’URL sont déterminés par les valeurs que vous avez sélectionnées dans les champs de la page des options avancées.
diff --git a/translations/fr-FR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/fr-FR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index 25a547449e..430609edba 100644
--- a/translations/fr-FR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/translations/fr-FR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Troubleshooting prebuilds
+title: Résolution des problèmes liés aux prébuilds
shortTitle: Codespaces prebuilds
-intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds.
+intro: Vous pouvez utiliser des prébuilds pour accélérer la création des codespaces. Cet article indique les étapes à suivre pour résoudre les problèmes courants relatifs aux prébuilds.
versions:
fpt: '*'
ghec: '*'
@@ -9,86 +9,91 @@ type: reference
topics:
- Codespaces
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: b8c45f9eae6094b78026d055ebea27c3748a8681
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158884'
---
+Pour plus d’informations sur les prébuilds {% data variables.product.prodname_github_codespaces %}, consultez « [Prégénération de vos codespaces](/codespaces/prebuilding-your-codespaces) ».
-For more information about {% data variables.product.prodname_github_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)."
+## Vérifier si un codespace a été créé à partir d’une prébuild
-## Checking whether a codespace was created from a prebuild?
+Lorsque vous créez un codespace, vous pouvez choisir le type de machine virtuelle que vous souhaitez utiliser. Si une prébuild est disponible pour le type de machine virtuelle, « {% octicon "zap" aria-label="The zap icon" %} Prébuild prête » s’affiche.
-When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it.
+
-
+Si vous avez défini votre éditeur {% data variables.product.prodname_github_codespaces %} favori sur « {% data variables.product.prodname_vscode %} pour le Web », la page « Configuration de votre codespace » affiche le message « Codespace prédéfini trouvé » si une prébuild est utilisée.
-If you have your {% data variables.product.prodname_github_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used.
+
-
+De même, si votre éditeur favori est « {% data variables.product.prodname_vscode_shortname %} », le terminal intégré affiche le message « Vous êtes sur un codespace prédéfini par la configuration de prébuild de votre référentiel » lorsque vous créez un codespace. Pour plus d’informations, consultez « [Définition de votre éditeur par défaut pour {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces) ».
-Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
-
-After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal:
+Après avoir créé un codespace, vous pouvez vérifier s’il a été créé à partir d’une prébuild en exécutant la commande {% data variables.product.prodname_cli %} suivante dans le terminal :
```shell{:copy}
gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild
```
-This returns `true` if the codespace was created using a prebuild.
+Cette commande renvoie `true` si le codespace a été créé à l’aide d’une prébuild.
-Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild:
+Si {% data variables.product.prodname_cli %} (`gh`) n’est pas installé, vous pouvez utiliser la commande suivante, qui renvoie `createFromPrebuild` si le codespace a été créé à partir d’une prébuild :
```shell{:copy}
cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME'
```
-## The "Prebuild Ready" label is sometimes missing
+## L’étiquette « Prébuild prête » est parfois manquante
-You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
+Vous pouvez remarquer que parfois, lorsque vous créez un codespace à partir d’une branche de prébuild, l’étiquette « {% octicon "zap" aria-label="The zap icon" %} Prébuild prête » ne s’affiche pas dans la boîte de dialogue pour choisir un type de machine. Cela signifie que les prébuilds ne sont pas encore disponibles.
-By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+Par défaut, chaque fois que vous effectuez un envoi (push) vers une branche de prébuild, la prébuild est mise à jour. Si l’envoi (push) push implique une modification de la configuration du conteneur de développement alors que la mise à jour est en cours, l’étiquette « {% octicon "zap" aria-label="The zap icon" %} Prébuild prête » est supprimée de la liste des types de machine. Pendant ce temps, vous pouvez toujours créer des codespaces sans prébuild. Si nécessaire, vous pouvez réduire le nombre d'occasions où les prébuilds ne sont pas disponibles pour un référentiel en configurant la prébuild pour qu’elle soit uniquement mise à jour lorsque vous apportez une modification aux fichiers de configuration de votre conteneur de développement, ou uniquement selon une planification personnalisée. Pour plus d’informations, consultez « [Configuration des prébuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds) ».
-If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
+Si votre branche n’est pas spécifiquement activée pour les prébuilds, elle peut bénéficier de prébuilds si elle a été créée à partir d’une branche de prébuild. Toutefois, si la configuration du conteneur de développement est modifiée sur votre branche et que sa configuration est différente sur la branche de base, les prébuilds ne sont plus disponibles sur votre branche.
-Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch:
+Voici quelques éléments à vérifier si l’étiquette « {% octicon "zap" aria-label="The zap icon" %} Prébuild prête » ne s’affiche pas pour une branche particulière :
-* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this.
-* Confirm that the prebuild configuration includes your region.
-* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
-* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
+* Vérifiez qu’une configuration de prébuild existe pour cette branche. Si vous n’êtes pas administrateur de référentiel, vous devez faire en contacter un pour le vérifier.
+* Vérifiez que la configuration de prébuild inclut votre région.
+* Vérifiez si une modification de la configuration du conteneur de développement a récemment été envoyée (push) à la branche de prébuild. Si tel est le cas, vous devrez probablement attendre que le workflow de prébuild s’exécute pour que cet envoi (push) se termine avant que les prébuilds ne soient à nouveau disponibles.
+* Si aucune modification de configuration n’a été récemment apportée, accédez à l’onglet **Actions** de votre référentiel, cliquez sur **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prébuilds** dans la liste des workflows, puis vérifiez que les exécutions de worflow de prébuild ont abouti. Si les dernières exécutions d’un workflow ont échoué et qu’une ou plusieurs de ces exécutions ayant échoué contiennent des modifications apportées à la configuration du conteneur de développement, aucune prébuild ne sera disponible pour la branche associée.
-## Some resources cannot be accessed in codespaces created using a prebuild
+## Certaines ressources ne peuvent pas être accessibles dans les codespaces créés avec une prébuild.
-If the `devcontainer.json` configuration file for a prebuild configuration specifies that permissions for access to other repositories are required, then the repository administrator is prompted to authorize these permissions when they create or update the prebuild configuration. If the administrator does not grant all of the requested permissions there's a chance that problems may occur in the prebuild, and in codespaces created from this prebuild. This is true even if the user who creates a codespace based on this prebuild _does_ grant all of the permissions when they are prompted to do so.
+Si le fichier de configuration `devcontainer.json` d’une configuration de prébuild spécifie que des autorisations d’accès à d’autres dépôts sont nécessaires, l’administrateur du dépôt est invité à accorder ces autorisations quand il crée ou met à jour la configuration de prébuild. Si l’administrateur n’accorde pas toutes les autorisations demandées, il est possible que des problèmes se produisent dans la prébuild et dans les codespaces créés à partir de cette prébuild. C’est vrai même si l’utilisateur qui crée un codespace basé sur cette prébuild _accorde_ toutes les autorisations lorsqu’il est invité à le faire.
-## Troubleshooting failed workflow runs for prebuilds
+## Résolution des problèmes liés aux exécutions de workflow ayant échoué pour les prébuilds
-### Increasing the {% data variables.product.prodname_actions %} spending limit
+### Augmentation de la limite de dépense pour {% data variables.product.prodname_actions %}
-Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+Les prébuilds sont créées et mises à jour en utilisant {% data variables.product.prodname_actions %}. Vos workflows de prébuild échouent si vous avez utilisé toutes vos minutes {% data variables.product.prodname_actions %} et atteint votre limite de dépense. Dans ce cas, vous pouvez augmenter votre limite de dépense pour {% data variables.product.prodname_actions %} afin d’autoriser l’exécution des workflows. Pour plus d’informations, consultez « [Gestion de votre limite de dépense pour {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions) ».
-### Authorizing access permissions
+### Octroi d’autorisations d’accès
-If the `devcontainer.json` configuration file for a prebuild configuration is updated to specify that permissions for access to other repositories are required, and a repository administrator has not been prompted to authorize these permissions for the prebuild configuration, then the prebuild workflow may fail. Try updating the prebuild configuration, without making any changes. If, when you click **Update**, the authorization page is displayed, check that the requested permissions are appropriate and, if so, authorize the request. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" and "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)."
+Si le fichier de configuration `devcontainer.json` d’une configuration de prébuild est mis à jour pour spécifier que les autorisations d’accès à d’autres dépôts sont nécessaires et qu’un administrateur de dépôt n’a pas été invité à accorder ces autorisations pour la configuration de la prébuild, le workflow de prébuild peut échouer. Essayez de mettre à jour la configuration de prébuild, sans apporter de modifications. Si, lorsque vous cliquez sur **Mettre à jour**, la page d’autorisations s’affiche, vérifiez que les autorisations demandées sont appropriées et, le cas échéant, autorisez la demande. Pour plus d’informations, consultez « [Gestion des prébuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration) » et « [Gestion des accès à d’autres dépôts dans votre codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions) ».
-If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
+Si les exécutions de workflow pour une configuration de prébuild échouent, vous pouvez temporairement désactiver la configuration de prébuild en attendant que le problème soit résolu. Pour plus d’informations, consultez « [Gestion des prébuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration) ».
-### Preventing out-of-date prebuilds being used
+### Empêcher l’utilisation de prébuilds obsolètes
-By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
+Par défaut, si le dernier workflow de prébuild a échoué, une prébuild précédente pour la même combinaison de dépôt, de branche et de fichier de configuration `devcontainer.json` est utilisée pour créer des codespaces. Ce comportement est appelé « optimisation de la prébuild ».
-We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
+Nous vous recommandons de laisser l’optimisation de la prébuild activée pour garantir la création rapide de codespaces si aucune prébuild à jour n’est disponible. Toutefois, en tant qu’administrateur de dépôt, vous pouvez désactiver l’optimisation de la prébuild si vous rencontrez des problèmes liés à des codespaces prédéfinis en retrait par rapport à l’état actuel de la branche. Si vous désactivez l’optimisation de la prébuild, des codespaces pour la combinaison appropriée de dépôt, de branche et de fichier `devcontainer.json` sont créés sans prébuild si le dernier workflow de prébuild a échoué ou est en cours d’exécution.
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
+1. À droite de la configuration de prébuild affectée, sélectionnez les points de suspension ( **...** ), puis cliquez sur **Modifier**.
- 
-1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
+ 
+1. Faites défiler la page « Modifier la configuration » jusqu’en bas et cliquez sur **Afficher les options avancées**.
- 
-1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
+ 
+1. Si vous êtes sûr de vouloir désactiver le paramètre par défaut, sélectionnez **Désactiver l’optimisation de la prébuild**.
- 
-1. To save your change, click **Update**.
+ 
+1. Pour enregistrer votre modification, cliquez sur **Mettre à jour**.
-## Further reading
+## Pour aller plus loin
-- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
-- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
+- « [Configuration des prébuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds) »
+- « [Gestion des prébuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds) »
diff --git a/translations/fr-FR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/fr-FR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 09e1af14db..8f7905ac45 100644
--- a/translations/fr-FR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/fr-FR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -1,6 +1,6 @@
---
-title: Création d’un fichier d’intégrité de la communauté par défaut
-intro: 'Vous pouvez créer des fichiers d’intégrité par défaut pour la communauté, comme CONTRIBUTING et CODE_OF_CONDUCT. Les fichiers par défaut seront utilisés pour tout dépôt appartenant à votre organisation qui ne contient pas son propre fichier d’intégrité.'
+title: Creating a default community health file
+intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
redirect_from:
- /articles/creating-a-default-community-health-file-for-your-organization
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
@@ -12,41 +12,46 @@ versions:
topics:
- Community
shortTitle: Community health file
-ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: fr-FR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145105413'
---
-## À propos des fichiers d’intégrité de la communauté par défaut
-Vous pouvez ajouter des fichiers d’intégrité de la communauté par défaut à un dépôt public appelé `.github`, à la racine du dépôt ou dans les dossiers `docs` ou `.github`.
+## About default community health files
-{% data variables.product.product_name %} utilise et affiche les fichiers par défaut pour tout dépôt appartenant au compte qui n’a pas son propre fichier de ce type à l’un des emplacements suivants :
-- racine du dépôt
-- dossier `.github`
-- dossier `docs`
+You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders.
-Par exemple, toute personne qui crée un problème ou une demande de tirage dans un dépôt qui n’a pas son propre fichier CONTRIBUTING voit un lien vers le fichier CONTRIBUTING par défaut. Si un dépôt a des fichiers dans son propre dossier `.github/ISSUE_TEMPLATE`{% ifversion fpt or ghes or ghec %}, notamment des modèles de problème ou un fichier *config.yml*,{% endif %} aucun des contenus du dossier `.github/ISSUE_TEMPLATE` par défaut n’est utilisé.
+{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
+- the root of the repository
+- the `.github` folder
+- the `docs` folder
-Les fichiers par défaut ne sont pas inclus dans les clones, les packages ou les téléchargements de dépôts individuels, car ils sont stockés uniquement dans le dépôt `.github`.
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
-## Types de fichiers pris en charge
+Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
-Vous pouvez créer des valeurs par défaut dans votre organisation{% ifversion fpt or ghes or ghec %} ou votre compte personnel{% endif %} pour les fichiers d’intégrité de la communauté suivants :
+## Supported file types
-Fichier d’intégrité de la communauté | Description --- | ---{% ifversion fpt or ghec %} *CODE_OF_CONDUCT.md* | Un fichier CODE_OF_CONDUCT définit les standards d’engagement dans une communauté. Pour plus d’informations, consultez « [Ajout d’un code de conduite à votre projet](/articles/adding-a-code-of-conduct-to-your-project/) ».{% endif %} *CONTRIBUTING.md* | Un fichier CONTRIBUTING indique la façon dont les gens doivent contribuer à votre projet. Pour plus d’informations, consultez « [Définition de recommandations pour les contributeurs de dépôt](/articles/setting-guidelines-for-repository-contributors/) ».{% ifversion fpt or ghec %} *FUNDING.yml* | Un fichier FUNDING affiche un bouton de sponsor dans votre dépôt pour augmenter la visibilité des options de financement de votre projet open source. Pour plus d’informations, consultez « [Affichage d’un bouton de sponsor dans votre dépôt](/articles/displaying-a-sponsor-button-in-your-repository) ».{% endif %} Modèles de problème et de demande de tirage{% ifversion fpt or ghes or ghec %} et *config.yml*{% endif %} | Les modèles de problème et de demande de tirage personnalisent et standardisent les informations que vous souhaitez que les contributeurs incluent quand ils ouvrent des problèmes et des demandes de tirage dans votre dépôt. Pour plus d’informations, consultez « [À propos des modèles de problème et de demande de tirage](/articles/about-issue-and-pull-request-templates/) ».{% ifversion fpt or ghes or ghec %} *SECURITY.md* | Un fichier SECURITY fournit des instructions sur la façon de signaler une faille de sécurité dans votre projet. Pour plus d’informations, consultez « [Ajout d’une stratégie de sécurité à votre dépôt](/code-security/getting-started/adding-a-security-policy-to-your-repository) ».{% endif %} *SUPPORT.md* | Un fichier SUPPORT permet aux utilisateurs de connaître les moyens d’obtenir de l’aide pour votre projet. Pour plus d’informations, consultez « [Ajout de ressources de support à votre projet](/articles/adding-support-resources-to-your-project/) ».
+You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
-Vous ne pouvez pas créer de fichier de licence par défaut. Vous devez ajouter les fichiers de licence à des dépôts individuels pour qu’ils soient inclus quand un projet est cloné, packagé ou téléchargé.
+Community health file | Description
+--- | ---{% ifversion fpt or ghec %}
+*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
+*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion discussion-category-forms %}
+Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[Creating discussion category forms](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
+*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
+Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes or ghec %}
+*SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
-## Création d’un dépôt pour les fichiers par défaut
+You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
+
+## Creating a repository for default files
{% data reusables.repositories.create_new %}
-2. Utilisez le menu déroulant **Propriétaire**, puis sélectionnez l’organisation{% ifversion fpt or ghes or ghec %} ou le compte personnel{% endif %} pour lequel vous souhaitez créer les fichiers par défaut.
- 
-3. Tapez **.github** en tant que nom de votre dépôt ainsi qu’une description facultative.
- 
-4. Vérifiez que l’état du dépôt est **Public** (un dépôt de fichiers par défaut ne peut pas être privé).
-  {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
-7. Dans le dépôt, créez l’un des fichiers d’intégrité de la communauté pris en charge. Les modèles de problème{% ifversion fpt or ghes or ghec %} et leur fichier config{% endif %} doivent se trouver dans un dossier appelé `.github/ISSUE_TEMPLATE`. Tous les autres fichiers pris en charge peuvent se trouver à la racine du dépôt, dans le dossier `.github` ou dans le dossier `docs`. Pour plus d’informations, consultez « [Création de fichiers](/articles/creating-new-files/) ».
+2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
+ 
+3. Type **.github** as the name for your repository, and an optional description.
+ 
+4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+ 
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
diff --git a/translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
index 44aa07505c..d8ecb5b2c4 100644
--- a/translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
+++ b/translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a pull request template for your repository
-intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.'
+title: Création d’un modèle de demande de tirage pour votre dépôt
+intro: 'Quand vous ajoutez un modèle de demande de tirage (pull request) à votre dépôt, les contributeurs du projet voient automatiquement le contenu de ce modèle dans le corps de la demande de tirage.'
redirect_from:
- /articles/creating-a-pull-request-template-for-your-repository
- /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
@@ -12,41 +12,44 @@ versions:
topics:
- Community
shortTitle: Create a PR template
+ms.openlocfilehash: fa4d3cf78b63af147c85b8f6d77d7cca74e3853a
+ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190407'
---
+Pour plus d’informations, consultez « [À propos des modèles de problème et de demande de tirage](/articles/about-issue-and-pull-request-templates) ».
-For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
-
-You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
+Vous pouvez créer un sous-répertoire *PULL_REQUEST_TEMPLATE/* dans l’un des dossiers pris en charge pour y stocker plusieurs modèles de demande de tirage (pull request), puis utiliser le paramètre de requête `template` pour spécifier le modèle qui va remplir le corps de la demande de tirage. Pour plus d’informations, consultez « [Utilisation de paramètres de requête pour créer une demande de tirage](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request) ».
{% ifversion fpt or ghes or ghec %}
-You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+Vous pouvez créer des modèles de demande de tirage par défaut pour votre organisation{% ifversion fpt or ghes or ghec %} ou votre compte personnel{% endif %}. Pour plus d’informations, consultez « [Création d’un fichier d’intégrité de la communauté par défaut](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file) ».
{% endif %}
-## Adding a pull request template
+## Ajout d’un modèle de demande de tirage
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field:
- - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`.
- 
- - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`.
- 
- - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`.
- 
- - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
- 
-4. In the body of the new file, add your pull request template. This could include:
- - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository.
- - A description of the changes proposed in the pull request.
- - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes.
-{% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Dans le champ du nom de fichier :
+ - Pour rendre votre modèle de demande de tirage visible dans le répertoire racine du dépôt, nommez le modèle de demande de tirage `pull_request_template.md`.
+ 
+ - Pour rendre votre modèle de demande de tirage visible dans le répertoire `docs` du dépôt, nommez le modèle de demande de tirage `docs/pull_request_template.md`.
+ 
+ - Pour stocker votre fichier dans un répertoire masqué, nommez le modèle de demande de tirage `.github/pull_request_template.md`.
+ 
+ - Pour créer plusieurs modèles de demande de tirage et utiliser le paramètre de requête `template` afin de spécifier un modèle permettant de remplir le corps de la demande de tirage, tapez *.github/PULL_REQUEST_TEMPLATE/* , puis le nom de votre modèle de demande de tirage. Par exemple : `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. Vous pouvez également stocker plusieurs modèles de demande de tirage (pull request) dans un sous-répertoire `PULL_REQUEST_TEMPLATE` au sein du répertoire racine ou du répertoire `docs/`. Pour plus d’informations, consultez « [Utilisation de paramètres de requête pour créer une demande de tirage](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request) ».
+ 
+4. Dans le corps du nouveau fichier, ajoutez votre modèle de demande de tirage. Vous pouvez inclure ce qui suit :
+ - [Référence à un problème connexe](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) dans votre dépôt.
+ - Description des changements proposés dans la demande de tirage.
+ - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) de la personne ou de l’équipe responsable de la revue les changements proposés.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} Les modèles sont accessibles aux collaborateurs quand ils sont fusionnés avec la branche par défaut du dépôt.
{% data reusables.files.propose_new_file %}
-## Further reading
+## Pour aller plus loin
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating a pull request](/articles/creating-a-pull-request)"
+- « [À propos des modèles de problème et de demande de tirage](/articles/about-issue-and-pull-request-templates) »
+- « [À propos de l’automatisation des problèmes et des demandes de tirage avec des paramètres de requête](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters) »
+- « [Création d’une demande de tirage](/articles/creating-a-pull-request) »
diff --git a/translations/fr-FR/content/discussions/managing-discussions-for-your-community/index.md b/translations/fr-FR/content/discussions/managing-discussions-for-your-community/index.md
index 379df32197..605c7ad172 100644
--- a/translations/fr-FR/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/fr-FR/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,6 +9,8 @@ children:
- /managing-categories-for-discussions
- /moderating-discussions
- /viewing-insights-for-your-discussions
+ - /creating-discussion-category-forms
+ - /syntax-for-discussion-category-forms
ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
ms.translationtype: HT
diff --git a/translations/fr-FR/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/fr-FR/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index 302f14adae..4e9a6d79fd 100644
--- a/translations/fr-FR/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/fr-FR/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -1,215 +1,201 @@
---
-title: Managing discussions
-intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
+title: Gestion des discussions
+intro: 'Vous pouvez catégoriser, mettre en lumière, transférer ou supprimer les discussions.'
permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
versions:
feature: discussions
shortTitle: Manage discussions
redirect_from:
- /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
+ms.openlocfilehash: e5e1474648973c90d16e8998db18518331233aa3
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164338'
---
+## À propos de la gestion des discussions
+{% data reusables.discussions.about-discussions %} Pour plus d’informations sur les discussions, consultez « [À propos des discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions) ».
-## About management of discussions
+Les propriétaires d’organisation peuvent choisir les autorisations nécessaires à la création d’une discussion dans les référentiels appartenant à l’organisation. De même, pour choisir les autorisations requises pour créer une discussion d’organisation, les propriétaires d’organisation peuvent modifier les autorisations requises dans le référentiel source. Pour plus d’informations, consultez « [Gestion de la création de discussion pour les dépôts dans votre organisation](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization) ».
-{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+En tant que chargé de maintenance des discussions, vous pouvez créer des ressources de la communauté pour encourager des discussions alignées sur l’objectif global du projet et gérer un forum ouvert convivial pour les collaborateurs. La création{% ifversion fpt or ghec %} d’un code de conduite ou{% endif %} de directives de contribution pour les collaborateurs favorise un forum collaboratif et productif. Pour plus d’informations sur la création de ressources de la communauté, consultez{% ifversion fpt or ghec %} « [Ajout d’un code de conduite à votre projet](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project) » et{% endif %} « [Définition de directives pour les contributeurs de dépôt](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors) ».
-Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."
+Quand une discussion génère une idée ou un bogue prêt à étudier, vous pouvez créer un problème à partir d’une discussion. Pour plus d’informations, consultez « [Création d’un problème](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion) ».
-As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, 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 guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+Vous pouvez épingler une discussion en haut de la liste des discussions pour le référentiel ou l’organisation. {% ifversion discussions-category-specific-pins %}Vous pouvez également épingler une discussion à une catégorie spécifique.{% endif %} Pour plus d’informations, consultez « [Épinglage d’une discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion) ».
-When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
-
-You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
-
-For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
+Pour plus d’informations sur l’animation d’une discussion saine, consultez « [Modération de commentaires et de conversations](/communities/moderating-comments-and-conversations) ».
{% data reusables.discussions.you-can-label-discussions %}
-## Prerequisites
+## Prérequis
-To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)."
+Pour gérer les discussions dans un dépôt, {% data variables.product.prodname_discussions %} doit être activé pour le dépôt. Pour plus d’informations, consultez « [Activation ou désactivation de {% data variables.product.prodname_discussions %} pour un dépôt](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) ».
-To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+Pour gérer les discussions dans une organisation, {% data variables.product.prodname_discussions %} doit être activé pour l’organisation. Pour plus d’informations, consultez « [Activation ou désactivation de {% data variables.product.prodname_discussions %} pour une organisation](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization) ».
-## Changing the category for a discussion
+## Changement de la catégorie d’une discussion
-You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+Vous pouvez catégoriser les discussions pour aider les membres de la communauté à trouver les discussions connexes. Pour plus d’informations, consultez « [Gestion des catégories de discussion](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) ».
-You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category.
+Vous pouvez également déplacer une discussion vers une autre catégorie. Il n’est pas possible de déplacer une discussion vers ou depuis la catégorie des sondages.
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Dans la barre latérale droite, à droite de « Catégorie », cliquez sur {% octicon "gear" aria-label="The gear icon" %}.
- 
+ 
-1. Click a category.
+1. Cliquez sur une catégorie.
- 
+ 
-## Pinning a discussion
+## Épinglage d’une discussion
-{% ifversion discussions-category-specific-pins %}
-You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
+{% ifversion discussions-category-specific-pins %} Vous pouvez épingler une discussion au-dessus de la liste des discussions pour le référentiel ou l’organisation. Vous pouvez également épingler une discussion à une catégorie spécifique. Les discussions épinglées globalement s’affichent en plus des discussions épinglées à une catégorie spécifique.
-This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
+Voici à quoi cela ressemble lorsque vous avez une discussion épinglée globalement et une discussion épinglée dans la catégorie Idées.
-
+
-### Pinning a discussion globally
+### Épinglage d’une discussion globalement
{% endif %}
-You can pin up to four important discussions above the list of discussions for the repository or organization.
+Vous pouvez épingler jusqu’à quatre discussions importantes au-dessus de la liste des discussions du référentiel ou de l’organisation.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Dans la barre latérale droite, cliquez sur {% octicon "pin" aria-label="The pin icon" %} **Épingler la discussion**.
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ {% else %}
- {% endif %}
+ {% endif %}
-1. Optionally, customize the look of the pinned discussion.
+1. Vous pouvez aussi personnaliser l’apparence de la discussion épinglée.
- 
+ 
-1. Click **Pin discussion**.
+1. Cliquez sur **Épingler la discussion**.
- 
+ 
{% ifversion discussions-category-specific-pins %}
-### Pinning a discussion to a category
+### Épinglage d’une discussion à une catégorie
-You can pin up to four important discussions above the list of discussions in a specific category.
+Vous pouvez épingler jusqu’à quatre discussions importantes au-dessus de la liste des discussions d’une catégorie spécifique.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Dans la barre latérale droite, cliquez sur {% octicon "pin" aria-label="The pin icon" %} **Épingler la discussion à CATEGORY**.
- 
+ 
-2. To confirm, click **Pin to CATEGORY**.
+2. Pour confirmer, cliquez sur **Épingler à CATEGORY**.
- 
+ 
{% endif %}
-## Editing a pinned discussion
+## Modification d’une discussion épinglée
-Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+La modification d’une discussion épinglée ne change pas la catégorie de la discussion. Pour plus d’informations, consultez « [Gestion des catégories de discussion](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) ».
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Dans la barre latérale droite, cliquez sur {% octicon "pencil" aria-label="The pencil icon" %} **Modifier la discussion épinglée**.
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+  {% else %}
- {% endif %}
+ {% endif %}
-1. Customize the look of the pinned discussion.
+1. Personnalisez l’apparence de la discussion épinglée.
- 
+ 
-1. Click **Pin discussion**.
+1. Cliquez sur **Épingler la discussion**.
- 
+ 
-## Unpinning a discussion
+## Désépinglage d’une discussion
{% ifversion discussions-category-specific-pins %}
-You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
+Vous pouvez désépingler une discussion de la liste des discussions pour le référentiel ou l’organisation, ou de la liste des discussions d’une catégorie spécifique.
-### Unpinning a globally pinned discussion
+### Désépinglage d’une discussion épinglée globalement
-You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
+Vous pouvez désépingler une discussion épinglée globalement. Cela ne supprimera pas la discussion, mais la discussion ne sera plus affichée au-dessus de la liste des discussions.
{% endif %}
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Dans la barre latérale droite, cliquez sur {% octicon "pin" aria-label="The pin icon" %} **Désépingler la discussion**.
- 
+ 
-1. Read the warning, then click **Unpin discussion**.
+1. Lisez l’avertissement, puis cliquez sur **Désépingler la discussion**.
- 
+ 
{% ifversion discussions-category-specific-pins %}
-### Unpinning a discussion from a category
+### Désépinglage d’une discussion d’une catégorie
-You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
+Vous pouvez désépingler une discussion épinglée à une catégorie spécifique. Cela ne supprime pas la discussion, mais la discussion ne s’affiche plus en haut de la catégorie.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Dans la barre latérale droite, cliquez sur {% octicon "pin" aria-label="The pin icon" %} **Désépingler la discussion de cette catégorie**.
- 
+ 
-1. Read the warning, then click **Unpin from this category**.
+1. Lisez l’avertissement, puis cliquez sur **Désépingler de cette catégorie**.
- 
+ 
{% endif %}
-## Transferring a discussion
+## Transfert d’une discussion
-To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
+Pour transférer une discussion, vous devez avoir l’autorisation de créer des discussions dans le dépôt où vous transférez la discussion. Si vous souhaitez transférer une discussion à une organisation, vous devez disposer des autorisations nécessaires pour créer des discussions dans le référentiel source des discussions de l’organisation. Vous pouvez uniquement transférer des discussions entre les dépôts appartenant au même compte d’utilisateur ou d’organisation. Vous ne pouvez pas transférer une discussion d’un dépôt privé{% ifversion ghec or ghes %} ou interne{% endif %} vers un dépôt public.
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Dans la barre latérale droite, cliquez sur {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transférer cette discussion**{% else %}**Transférer cette discussion**{% endif %}.
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+  {% else %}
- {% endif %}
+ {% endif %}
-1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
+1. Sélectionnez la liste déroulante **Choisir un dépôt** et cliquez sur le dépôt vers lequel vous voulez transférer la discussion. Si vous souhaitez transférer une discussion à une organisation, choisissez le référentiel source pour les discussions de l’organisation.
- 
+ 
-1. Click **Transfer discussion**.
+1. Cliquez sur **Transférer la discussion**.
- 
+ 
-## Deleting a discussion
+## Suppression d’une discussion
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Dans la barre latérale droite, cliquez sur {% octicon "trash" aria-label="The trash arrow icon" %} **Supprimer la discussion**.
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ {% else %}
- {% endif %}
+ {% endif %}
-1. Read the warning, then click **Delete this discussion**.
+1. Lisez l’avertissement, puis cliquez sur **Supprimer cette discussion**.
- 
+ 
-## Converting issues based on labels
+## Conversion de problèmes en fonction d’étiquettes
-You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.
+Vous pouvez convertir en bloc en discussions tous les problèmes qui ont la même étiquette. Les futurs problèmes qui ont cette étiquette sont également convertis automatiquement en discussion dans la catégorie que vous configurez.
-1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository.
-{% data reusables.repositories.sidebar-issues %}
-{% data reusables.project-management.labels %}
-1. Next to the label you want to convert to issues, click **Convert issues**.
-1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
-1. Click **I understand, convert this issue to a discussion**.
+1. Sur {% data variables.location.product_location %}, accédez à la page principale du référentiel ou, pour les discussions de l’organisation, au référentiel source.
+{% data reusables.repositories.sidebar-issues %} {% data reusables.project-management.labels %}
+1. À côté de l’étiquette que vous voulez convertir en problème, cliquez sur **Convertir les problèmes**.
+1. Sélectionnez le menu déroulant **Choisir une catégorie** et cliquez sur une catégorie pour votre discussion.
+1. Cliquez sur **Je comprends, convertir ce problème en discussion**.
diff --git a/translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index ffef0a4aba..42e2d17471 100644
--- a/translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -1,78 +1,84 @@
---
-title: Create a group assignment
-intro: You can create a collaborative assignment for teams of students who participate in your course.
+title: Créer un devoir de groupe
+intro: Vous pouvez créer une affectation collaborative pour des équipes d’étudiants qui participent à votre cours.
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
redirect_from:
- /education/manage-coursework-with-github-classroom/create-group-assignments
- /education/manage-coursework-with-github-classroom/create-a-group-assignment
+ms.openlocfilehash: 71c5f5eaf97ba58e25921c1e2be6fc638550dfa8
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179759'
---
-## About group assignments
+## À propos des devoirs de groupe
-{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+{% data reusables.classroom.assignments-group-definition %} Les étudiants peuvent travailler à plusieurs sur un devoir de groupe dans un dépôt partagé, comme une équipe de développeurs professionnels.
-When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+Quand un étudiant accepte un devoir de groupe, il peut créer une équipe ou rejoindre une équipe existante. {% data variables.product.prodname_classroom %} enregistre les équipes d’un devoir sous forme d’ensemble. Vous pouvez nommer l’ensemble des équipes pour un devoir spécifique quand vous créez le devoir, et vous pouvez réutiliser cet ensemble d’équipes pour un devoir ultérieur.
{% data reusables.classroom.classroom-creates-group-repositories %}
{% data reusables.classroom.about-assignments %}
-You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+Vous pouvez choisir le nombre d’équipes d’un devoir et le nombre de membres de chaque équipe. Chaque équipe créée par un étudiant pour un devoir est une équipe au sein de votre organisation sur {% data variables.product.product_name %}. La visibilité de l’équipe est secrète. Les équipes que vous créez sur {% data variables.product.product_name %} n’apparaissent pas dans {% data variables.product.prodname_classroom %}. Pour plus d’informations, consultez « [À propos des équipes](/organizations/organizing-members-into-teams/about-teams) ».
-For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+Pour une démonstration vidéo de la création d’un devoir de groupe, consultez « [Concepts de base de la configuration de {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom) ».
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## Prérequis
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## Création d’un devoir
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## Configuration des éléments de base d’un devoir
-Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+Nommez votre devoir, choisissez une échéance éventuelle, définissez des équipes et choisissez la visibilité des dépôts de devoir.
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Defining teams for an assignment](#defining-teams-for-an-assignment)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Nommage d’un devoir](#naming-an-assignment)
+- [Attribution d’une échéance pour un devoir](#assigning-a-deadline-for-an-assignment)
+- [Choix d’un type de devoir](#choosing-an-assignment-type)
+- [Définition d’équipes pour un devoir](#defining-teams-for-an-assignment)
+- [Choix d’une visibilité pour les dépôts de devoir](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### Nommage d’un devoir
-For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+Pour un devoir de groupe, {% data variables.product.prodname_classroom %} nomme les dépôts avec le préfixe du dépôt et le nom de l’équipe. Par défaut, le préfixe du dépôt est le titre du devoir. Par exemple, si vous nommez un devoir « assignment-1 » et que le nom de l’équipe sur {% data variables.product.product_name %} est « student-name », le nom du dépôt de devoir pour les membres de l’équipe est `assignment-1-student-team`.
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### Attribution d’une échéance pour un devoir
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### Choix d’un type de devoir
-Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create an individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+Sous « Devoir individuel ou de groupe », sélectionnez le menu déroulant, puis cliquez sur **Devoir de groupe**. Vous ne pouvez pas changer le type de devoir après l’avoir créé. Si vous préférez créer un devoir individuel, consultez « [Créer un devoir individuel](/education/manage-coursework-with-github-classroom/create-an-individual-assignment) ».
-### Defining teams for an assignment
+### Définition d’équipes pour un devoir
-If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+Si vous avez déjà créé un devoir de groupe pour la classe, vous pouvez réutiliser un ensemble d’équipes pour le nouveau devoir. Pour créer un ensemble avec les équipes que vos étudiants ont créées pour le devoir, tapez le nom de l’ensemble. Vous pouvez aussi taper le nombre maximal de membres de l’équipe et le nombre total d’équipes.
{% tip %}
-**Tips**:
+**Conseils** :
-- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+- Nous vous recommandons d’ajouter des détails sur l’ensemble d’équipes dans le nom de l’ensemble. Par exemple, si vous voulez utiliser l’ensemble d’équipes pour un devoir, donnez-lui le nom du devoir. Si vous voulez réutiliser l’ensemble tout au long d’un semestre ou d’un cours, donnez-lui le nom du semestre ou du cours.
-- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+- Si vous voulez attribuer des étudiants à une équipe spécifique, donnez-leur un nom pour l’équipe et fournissez une liste de membres.
{% endtip %}
-
+
-### Choosing a visibility for assignment repositories
+### Choix d’une visibilité pour les dépôts de devoir
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -80,22 +86,22 @@ If you've already created a group assignment for the classroom, you can reuse a
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## Ajout de code de démarrage et configuration d’un environnement de développement
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [Choix d’un modèle de dépôt](#choosing-a-template-repository)
+- [Choix d’un environnement de développement intégré (IDE)](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### Choix d’un modèle de dépôt
-By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %}
+Par défaut, un nouveau devoir crée un dépôt vide pour chaque équipe créée par un étudiant. {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
-### Choosing an integrated development environment (IDE)
+### Choix d’un environnement de développement intégré (IDE)
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} Pour plus d’informations, consultez « [Intégrer {% data variables.product.prodname_classroom %} à un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide) ».
{% data reusables.classroom.classroom-codespaces-link %}
@@ -103,18 +109,18 @@ By default, a new assignment will create an empty repository for each team that
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-## Providing feedback
+## Formulation de commentaires
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+Vous pouvez aussi évaluer automatiquement les devoirs et créer un espace pour discuter de chaque envoi avec l’équipe.
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [Test automatique des devoirs](#testing-assignments-automatically)
+- [Création d’une demande de tirage pour les commentaires](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### Test automatique des devoirs
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### Création d’une demande de tirage pour les commentaires
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -122,36 +128,36 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## Invitation d’étudiants à un devoir
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+Vous pouvez voir les équipes qui travaillent sur un devoir ou qui ont envoyé un devoir sous l’onglet **Équipes** du devoir. {% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
+## Monitoring de la progression des étudiants
+La page de présentation des devoirs montre des informations sur les devoirs que vous avez acceptés et la progression de l’équipe. Vous pouvez avoir des informations récapitulatives différentes en fonction des configurations de vos devoirs.
-- **Total teams**: The number of teams that have been created.
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
-- **Accepted teams**: The number of teams who have accepted this assignment.
-- **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
+- **Nombre total d’équipes** : nombre d’équipes créées.
+- **Étudiants inscrits** : nombre d’étudiants sur la liste de classe.
+- **Étudiants sans équipe** : nombre d’étudiants de la liste de classe Classroom qui n’ont pas encore rejoint une équipe.
+- **Équipes ayant accepté** : nombre d’équipes qui ont accepté ce devoir.
+- **Envois de devoir** : nombre d’équipes qui ont envoyé le devoir. L’envoi est déclenché à l’échéance du devoir.
+- **Équipes ayant réussi** : nombre d’équipes qui réussissent actuellement les tests d’évaluation automatique pour ce devoir.
-## Next steps
+## Étapes suivantes
-- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}.
+- Une fois que vous avez créé le devoir et que vos étudiants ont formé des équipes, les membres d’équipe peuvent commencer à travailler sur le devoir en utilisant les fonctionnalités Git et {% data variables.product.product_name %}. Les étudiants peuvent cloner le dépôt, pousser des commits, gérer des branches, créer et réviser des demandes de tirage, résoudre les conflits de fusion et discuter sur les changements en utilisant les problèmes. L’équipe et vous-même pouvez passer en revue l’historique des commits du dépôt. Pour plus d’informations, consultez « [Bien démarrer avec {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github) », « [Dépôts](/repositories) », « [Utilisation de Git](/github/getting-started-with-github/using-git) » et « [Collaboration en utilisant les problèmes et les demandes de tirage](/github/collaborating-with-issues-and-pull-requests) », ainsi que le cours gratuit sur la [résolution des conflits de fusion](https://github.com/skills/resolve-merge-conflicts) sur {% data variables.product.prodname_learning %}.
-- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- Dès qu’une équipe a terminé un devoir, vous pouvez passer en revue les fichiers du dépôt ou l’historique et les visualisations du dépôt pour mieux comprendre comment l’équipe a collaboré. Pour plus d’informations, consultez « [Visualisation des données de dépôt avec des graphes](/github/visualizing-repository-data-with-graphs) ».
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- Vous pouvez fournir des commentaires sur un devoir en commentant des lignes ou des commits individuels dans une demande de tirage. Pour plus d’informations, consultez « [Commentaires dans une demande de tirage](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request) » et « [Ouverture d’un problème à partir du code](/github/managing-your-work-on-github/opening-an-issue-from-code) ». Pour plus d’informations sur la création de réponses enregistrées afin de fournir des commentaires sur les erreurs courantes, consultez « [À propos des réponses enregistrées](/github/writing-on-github/about-saved-replies) ».
-## Further reading
+## Pour aller plus loin
-- [{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
-- "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
-- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
+- [{% data variables.product.prodname_global_campus %} pour les enseignants](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- « [Connecter un système de gestion de l’apprentissage à une classe](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom) »
+- [Utilisation des équipes existantes dans les devoirs de groupe ?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) dans la communauté {% data variables.product.prodname_education %}
diff --git a/translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 8161608b81..974e152aa6 100644
--- a/translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -1,6 +1,6 @@
---
-title: Create an individual assignment
-intro: You can create an assignment for students in your course to complete individually.
+title: Créer un devoir individuel
+intro: Vous pouvez créer un devoir pour les étudiants de votre cours à faire individuellement.
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
@@ -8,8 +8,14 @@ redirect_from:
- /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
- /education/manage-coursework-with-github-classroom/create-an-individual-assignment
shortTitle: Individual assignment
+ms.openlocfilehash: 1ffa725be4e42695b297545f65c998b14ed8e000
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179745'
---
-## About individual assignments
+## À propos des devoirs individuels
{% data reusables.classroom.assignments-individual-definition %}
@@ -17,42 +23,42 @@ shortTitle: Individual assignment
{% data reusables.classroom.about-assignments %}
-For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+Pour une démonstration vidéo de la création d’un devoir individuel, consultez « [Concepts de base de la configuration de {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom) ».
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## Prérequis
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## Création d’un devoir
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## Configuration des éléments de base d’un devoir
-Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+Nommez votre devoir, choisissez une échéance éventuelle et la visibilité des dépôts de devoir.
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Nommage d’un devoir](#naming-an-assignment)
+- [Attribution d’une échéance pour un devoir](#assigning-a-deadline-for-an-assignment)
+- [Choix d’un type de devoir](#choosing-an-assignment-type)
+- [Choix d’une visibilité pour les dépôts de devoir](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### Nommage d’un devoir
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+Pour un devoir individuel, {% data variables.product.prodname_classroom %} nomme les dépôts avec le préfixe du dépôt et le nom d’utilisateur {% data variables.product.product_name %} de l’étudiant. Par défaut, le préfixe du dépôt est le titre du devoir. Par exemple, si vous nommez un devoir « assignment-1 » et que le nom d’utilisateur de l’étudiant sur {% data variables.product.product_name %} est @octocat, le nom du dépôt de devoir pour @octocat est `assignment-1-octocat`.
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### Attribution d’une échéance pour un devoir
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### Choix d’un type de devoir
-Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+Sous « Devoir individuel ou de groupe », sélectionnez le menu déroulant et cliquez sur **Devoir individuel**. Vous ne pouvez pas changer le type de devoir après l’avoir créé. Si vous préférez créer un devoir de groupe, consultez « [Créer un devoir de groupe](/education/manage-coursework-with-github-classroom/create-a-group-assignment) ».
-### Choosing a visibility for assignment repositories
+### Choix d’une visibilité pour les dépôts de devoir
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -60,41 +66,41 @@ Under "Individual or group assignment", select the drop-down menu, and click **I
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## Ajout de code de démarrage et configuration d’un environnement de développement
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [Choix d’un modèle de dépôt](#choosing-a-template-repository)
+- [Choix d’un environnement de développement intégré (IDE)](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### Choix d’un modèle de dépôt
-By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+Par défaut, un nouveau devoir crée un dépôt vide pour chaque étudiant de la liste de classe. {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-### Choosing an integrated development environment (IDE)
+### Choix d’un environnement de développement intégré (IDE)
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} Pour plus d’informations, consultez « [Intégrer {% data variables.product.prodname_classroom %} à un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide) ».
{% data reusables.classroom.classroom-codespaces-link %}
{% data reusables.classroom.assignments-guide-choose-an-online-ide %}
-## Providing feedback for an assignment
+## Envoi de commentaires pour un devoir
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
+Vous pouvez aussi évaluer automatiquement les devoirs et créer un espace pour discuter de chaque envoi avec l’étudiant.
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [Test automatique des devoirs](#testing-assignments-automatically)
+- [Création d’une demande de tirage pour les commentaires](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### Test automatique des devoirs
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### Création d’une demande de tirage pour les commentaires
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -102,34 +108,34 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## Invitation d’étudiants à un devoir
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
+Vous pouvez voir si un étudiant a rejoint la classe, et a accepté ou envoyé un devoir sous l’onglet **Liste de classe** du devoir. Vous pouvez également lier les alias {% data variables.product.prodname_dotcom %} des étudiants à leur identificateur de liste de classe et vice versa sous cet onglet. {% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
+## Monitoring de la progression des étudiants
+La page de présentation des devoirs fournit une vue d’ensemble des acceptations de vos devoirs et de la progression des étudiants. Vous pouvez avoir des informations récapitulatives différentes en fonction des configurations de vos devoirs.
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
-- **Accepted students**: The number of accounts have accepted this assignment.
-- **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing students**: The number of students currently passing the autograding tests for this assignment.
+- **Étudiants inscrits** : nombre d’étudiants sur la liste de classe.
+- **Étudiants ajoutés** : nombre de comptes {% data variables.product.prodname_dotcom %} qui ont accepté le devoir et ne sont pas associés à un identificateur de liste de classe.
+- **Étudiants acceptés** : nombre de comptes qui ont accepté ce devoir.
+- **Envois de devoir** : nombre d’étudiants qui ont envoyé le devoir. L’envoi est déclenché à l’échéance du devoir.
+- **Étudiants ayant réussi** : nombre d’étudiants qui réussissent actuellement les tests d’évaluation automatique pour ce devoir.
-## Next steps
+## Étapes suivantes
-- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- Dès que vous avez créé le devoir, les étudiants peuvent commencer à travailler sur le devoir en utilisant les fonctionnalités Git et {% data variables.product.product_name %}. Les étudiants peuvent cloner le dépôt, pousser des commits, gérer des branches, créer et réviser des demandes de tirage, résoudre les conflits de fusion et discuter sur les changements en utilisant les problèmes. L’étudiant et vous-même pouvez passer en revue l’historique des commits du dépôt. Pour plus d’informations, consultez « [Bien démarrer avec {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github) », « [Dépôts](/repositories) » et « [Collaboration avec les problèmes et les demandes de tirage](/github/collaborating-with-issues-and-pull-requests) ».
-- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- Dès qu’un étudiant a terminé un devoir, vous pouvez passer en revue les fichiers du dépôt, ou l’historique et les visualisations du dépôt pour mieux comprendre le travail de l’étudiant. Pour plus d’informations, consultez « [Visualisation des données de dépôt avec des graphes](/github/visualizing-repository-data-with-graphs) ».
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- Vous pouvez fournir des commentaires sur un devoir en commentant des lignes ou des commits individuels dans une demande de tirage. Pour plus d’informations, consultez « [Commentaires dans une demande de tirage](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request) » et « [Ouverture d’un problème à partir du code](/github/managing-your-work-on-github/opening-an-issue-from-code) ». Pour plus d’informations sur la création de réponses enregistrées afin de fournir des commentaires sur les erreurs courantes, consultez « [À propos des réponses enregistrées](/github/writing-on-github/about-saved-replies) ».
-## Further reading
+## Pour aller plus loin
-- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
+- « [{% data variables.product.prodname_global_campus %} pour les enseignants](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers) »
+- « [Connecter un système de gestion des formations à {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom) »
diff --git a/translations/fr-FR/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/fr-FR/content/get-started/onboarding/getting-started-with-github-ae.md
index 7a247d6c1c..b9ea126a4c 100644
--- a/translations/fr-FR/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/fr-FR/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -1,83 +1,88 @@
---
-title: Getting started with GitHub AE
-intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.'
+title: Bien démarrer avec GitHub AE
+intro: 'Démarrage de la définition et de la configuration de {% data variables.product.product_name %} pour {% data variables.location.product_location %}.'
versions:
ghae: '*'
+ms.openlocfilehash: 957a922a2493abd8f625cdb9e9d6650283820222
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180060'
---
+Ce guide vous accompagne tout au long de l’installation, de la configuration et de la gestion des paramètres pour {% data variables.location.product_location %} sur {% data variables.product.product_name %} en tant que propriétaire d’entreprise. Pour plus d’informations sur {% data variables.product.product_name %}, consultez « [À propos de {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae) ».
-This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)."
+## Partie 1 : Configuration de {% data variables.product.product_name %}
+Pour commencer à utiliser {% data variables.product.product_name %}, vous pouvez créer votre compte d’entreprise, initialiser {% data variables.product.product_name %}, configurer une liste d’adresses IP autorisées, configurer l’authentification et le provisionnement des utilisateurs, et gérer la facturation pour {% data variables.location.product_location %}.
-## Part 1: Setting up {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}.
-
-### 1. Creating your {% data variables.product.product_name %} enterprise account
-You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+### 1. Création de votre compte d’entreprise {% data variables.product.product_name %}
+Vous devez commencer par acheter {% data variables.product.product_name %}. Pour plus [d’informations, contactez l’équipe de vente de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
{% data reusables.github-ae.initialize-enterprise %}
-### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+### 2. Initialisation de {% data variables.product.product_name %}
+Une fois que {% data variables.product.company_short %} a créé le compte de propriétaire pour {% data variables.location.product_location %} sur {% data variables.product.product_name %}, vous recevez un e-mail pour vous connecter et effectuer l’initialisation. Lors de l’initialisation, en tant que propriétaire de l’entreprise, vous nommez {% data variables.location.product_location %}, configurez une authentification unique (SSO) SAML, créez des stratégies pour toutes les organisations dans {% data variables.location.product_location %}, puis configurez un contact de support pour les membres de votre entreprise. Pour plus d’informations, consultez « [Initialisation de {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae) ».
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 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)."
+### 3. Restriction du trafic réseau
+Vous pouvez configurer une liste verte d’adresses IP spécifiques afin de restreindre l’accès aux ressources détenues par des organisations au sein de votre compte d’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) ».
-### 4. Managing identity and access for {% data variables.location.product_location %}
-You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[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)."
+### 4. Gestion des identités et des accès pour {% data variables.location.product_location %}
+Vous pouvez gérer de manière centralisée l’accès à {% data variables.location.product_location %} sur {% data variables.product.product_name %} à partir d’un fournisseur d’identité en utilisant une authentification unique (SSO) SAML pour l’authentification utilisateur et SCIM pour le provisionnement d’utilisateurs. Une fois que vous avez configuré l’approvisionnement, vous pouvez affecter des utilisateurs à l’application, ou les désaffecter, à partir du fournisseur d’identité, en créant ou désactivant des comptes d’utilisateur dans l’entreprise. Pour plus d’informations, consultez « [À propos de la gestion des identités et des accès pour votre entreprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise) ».
-### 5. Managing billing for {% data variables.location.product_location %}
-Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+### 5. Gestion de la facturation pour {% data variables.location.product_location %}
+Les propriétaires de l’abonnement pour {% data variables.location.product_location %} sur {% data variables.product.product_name %} peuvent voir les détails de facturation pour {% data variables.product.product_name %} dans le portail Azure. Pour plus d’informations, consultez « [Gestion de la facturation pour votre entreprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise) ».
-## Part 2: Organizing and managing enterprise members
-As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
+## Partie 2 : Organisation et gestion des membres de l’entreprise
+En tant que propriétaire de l’entreprise, pour {% data variables.product.product_name %}, vous pouvez gérer des paramètres aux niveaux utilisateur, dépôt, équipe et organisation. Vous pouvez gérer les membres de {% data variables.location.product_location %}, créer et gérer des organisations, définir des stratégies pour la gestion du dépôt, ainsi que créer et gérer des équipes.
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. Gérer les membres de {% data variables.location.product_location %}
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. Créer des organisations
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. Ajouter des membres à des organisations
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. Créer des équipes
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. Définir des niveaux d’autorisation pour les organisations et les dépôts
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. Appliquer des stratégies de gestion des dépôts
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations.
+## Partie 3 : Génération en toute sécurité
+Pour augmenter la sécurité de {% data variables.location.product_location %}, vous pouvez surveiller {% data variables.location.product_location %} et configurer des fonctionnalités de sécurité et d’analyse pour vos organisations.
-### 1. Monitoring {% data variables.location.product_location %}
-You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)."
+### 1. Surveillance de {% data variables.location.product_location %}
+Vous pouvez surveiller {% data variables.location.product_location %} avec votre tableau de bord d’activité et une journalisation d’audit. Pour plus d’informations, consultez « [Supervision de l’activité dans votre entreprise](/admin/monitoring-activity-in-your-enterprise) ».
-### 2. Configuring security features for your organizations
+### 2. Configuration de fonctionnalités de sécurité pour vos organisations
{% data reusables.getting-started.configuring-security-features %}
-## Part 4: Customizing and automating work on {% data variables.location.product_location %}
-You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
+## Partie 4 : Personnalisation et automatisation du travail sur {% data variables.location.product_location %}
+Vous pouvez personnaliser et automatiser le travail au sein d’organisations dans {% data variables.location.product_location %} avec l’API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, {% data variables.product.prodname_actions %} et {% data variables.product.prodname_pages %}.
-### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Utilisation de l’API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
{% data reusables.getting-started.api %}
-### 2. Building {% data variables.product.prodname_actions %}
+### 2. Génération de {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."
+Pour plus d’informations sur l’activation et la configuration de {% data variables.product.prodname_actions %} pour {% data variables.product.product_name %}, consultez « [Bien démarrer avec {% data variables.product.prodname_actions %} pour {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae) ».
-### 3. Using {% data variables.product.prodname_pages %}
+### 3. Utilisation de {% data variables.product.prodname_pages %}
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Partie 5 : Utilisation des ressources d’apprentissage et de support de {% data variables.product.prodname_dotcom %}
+Les membres de votre entreprise peuvent en apprendre davantage sur Git et {% data variables.product.prodname_dotcom %} avec nos ressources d’apprentissage, et vous pouvez obtenir l’aide dont vous avez besoin auprès du Support entreprise {% data variables.product.prodname_dotcom %}.
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+### 1. Lecture à propose de {% data variables.product.product_name %} sur {% data variables.product.prodname_docs %}
+Vous pouvez lire une documentation qui reflète les fonctionnalités disponibles avec {% data variables.product.prodname_ghe_managed %}. Pour plus d’informations, consultez « [À propos des versions de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs) ».
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. Apprendre avec {% data variables.product.prodname_learning %}
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Faire appel au Support {% data variables.product.prodname_dotcom %} Enterprise
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/fr-FR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/fr-FR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index f3368b385c..f6216ff242 100644
--- a/translations/fr-FR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/fr-FR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,128 +1,132 @@
---
-title: Getting started with GitHub Enterprise Server
-intro: 'Get started with setting up and managing {% data variables.location.product_location %}.'
+title: Bien démarrer avec GitHub Enterprise Server
+intro: 'Commencez à configurer et à gérer {% data variables.location.product_location %}.'
versions:
ghes: '*'
+ms.openlocfilehash: 68cd462c42ef63863750d9edc5e122dc3c325115
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163415'
---
+Ce guide vous accompagne tout au long de l’installation, de la configuration et de la gestion de {% data variables.location.product_location %} en tant qu’administrateur d’entreprise.
-This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator.
-
-{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
+{% data variables.product.company_short %} offre deux façons de déployer {% data variables.product.prodname_enterprise %}.
- **{% data variables.product.prodname_ghe_cloud %}**
- **{% data variables.product.prodname_ghe_server %}**
-{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
+{% data variables.product.company_short %} héberge {% data variables.product.prodname_ghe_cloud %}. Vous pouvez déployer et héberger {% data variables.product.prodname_ghe_server %} dans votre propre centre de données ou chez un fournisseur de cloud pris en charge.
-For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)."
+Pour plus d’informations sur {% data variables.product.product_name %}, consultez « [À propos de {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server). »
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing.
-### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## Partie 1 : Installation de {% data variables.product.product_name %}
+Pour bien démarrer avec {% data variables.product.product_name %}, vous devez créer votre compte d’entreprise, installer l’instance, utiliser la console de gestion pour la configuration initiale, configurer votre instance et gérer la facturation.
+### 1. Créer votre compte d’entreprise
+Avant d’installer {% data variables.product.product_name %}, vous pouvez créer un compte d’entreprise sur {% data variables.product.prodname_dotcom_the_website %} en contactant l’[équipe des ventes de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). Un compte d’entreprise sur {% data variables.product.prodname_dotcom_the_website %} est utile pour la facturation et pour les fonctionnalités partagées avec {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. Pour plus d’informations, consultez « [À propos des comptes d’entreprise](/admin/overview/about-enterprise-accounts) ».
+### 2. Installer {% data variables.product.product_name %}
+Pour bien démarrer avec {% data variables.product.product_name %}, vous devez installer l’appliance sur une plateforme de virtualisation de votre choix. Pour plus d’informations, consultez « [Configuration d’une instance {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance) ».
-### 3. Using the Management Console
-You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+### 3. Utiliser la console de gestion
+Vous utilisez la console de gestion pour effectuer le processus de configuration initiale au premier lancement de {% data variables.location.product_location %}. Vous pouvez également utiliser la console de gestion pour gérer les paramètres de l’instance comme la licence, le domaine, l’authentification et TLS. Pour plus d’informations, consultez « [Accès à la console de gestion](/admin/configuration/configuring-your-enterprise/accessing-the-management-console) ».
-### 4. Configuring {% data variables.location.product_location %}
-In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
+### 4. Configuration de {% data variables.location.product_location %}
+En plus de la console de gestion, vous pouvez utiliser le tableau de bord d’administration du site et le shell d’administration (SSH) pour gérer {% data variables.location.product_location %}. Par exemple, vous pouvez configurer des applications et des limites de débit, afficher des rapports et utiliser des utilitaires en ligne de commande. Pour plus d’informations, consultez « [Configuration de votre entreprise](/admin/configuration/configuring-your-enterprise) ».
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+Vous pouvez conserver les paramètres réseau par défaut utilisés par {% data variables.product.product_name %} via le protocole DHCP (Dynamic Host Configuration Protocol) ou bien configurer les paramètres réseau dans la console de machine virtuelle. Vous pouvez aussi configurer un serveur proxy ou des règles de pare-feu. Pour plus d’informations, consultez « [Configuration des paramètres réseau](/admin/configuration/configuring-network-settings) ».
-### 5. Configuring high availability
-You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
+### 5. Configurer la haute disponibilité
+Vous pouvez configurer la haute disponibilité pour {% data variables.location.product_location %} afin de réduire l’impact des défaillances matérielles et des pannes réseau. Pour plus d’informations, consultez « [Configuration de la haute disponibilité](/admin/enterprise-management/configuring-high-availability) ».
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 6. Configurer une instance de préproduction
+Vous pouvez configurer une instance de préproduction pour valider les modifications, planifier la reprise d’activité après sinistre et tester les mises à jour avant de les appliquer à {% data variables.location.product_location %}. Pour plus d’informations, consultez « [Configuration d’une instance intermédiaire](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance) ».
-### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+### 7. Définir les sauvegardes et la reprise d’activité après sinistre
+Pour protéger vos données de production, vous pouvez configurer des sauvegardes automatiques de {% data variables.location.product_location %} avec {% data variables.product.prodname_enterprise_backup_utilities %}. Pour plus d’informations, consultez « [Configuration des sauvegardes sur votre appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance) ».
-### 8. Managing billing for your enterprise
-Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+### 8. Gérer la facturation pour votre entreprise
+La facturation de toutes les organisations et instances de {% data variables.product.product_name %} connectées à votre compte d’entreprise est agrégée en une seule facture pour tous vos services {% data variables.product.prodname_dotcom %}.com payants. Les propriétaires d’entreprise et les gestionnaires de facturation peuvent voir et gérer les paramètres de facturation définis pour les comptes d’entreprise. Pour plus d’informations, consultez « [Gestion de la facturation pour votre entreprise](/admin/overview/managing-billing-for-your-enterprise) ».
-## Part 2: Organizing and managing your team
-As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
+## Partie 2 : Organisation et gestion de votre équipe
+En tant que propriétaire ou administrateur d’entreprise, vous pouvez gérer les paramètres aux niveaux utilisateur, dépôt, équipe et organisation. Vous pouvez gérer les membres de votre entreprise, créer et gérer des organisations, définir des stratégies pour la gestion des dépôts ainsi que créer et gérer des équipes.
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. Gérer les membres de {% data variables.location.product_location %}
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. Créer des organisations
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. Ajouter des membres à des organisations
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. Créer des équipes
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. Définir des niveaux d’autorisation pour les organisations et les dépôts
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. Appliquer des stratégies de gestion des dépôts
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
-### 1. Authenticating enterprise members
-You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+## Partie 3 : Génération en toute sécurité
+Pour renforcer la sécurité de {% data variables.location.product_location %}, vous pouvez configurer l’authentification des membres de l’entreprise, utiliser des outils et les journaux d’audit pour maintenir la conformité, configurer des fonctionnalités de sécurité et d’analyse pour vos organisations et éventuellement activer {% data variables.product.prodname_GH_advanced_security %}.
+### 1. Authentifier les membres de l’entreprise
+Vous pouvez utiliser la méthode d’authentification intégrée de {% data variables.product.product_name %}, ou choisir un fournisseur d’authentification externe, par exemple CAS, LDAP ou SAML, pour intégrer vos comptes existants et gérer de manière centralisée les accès utilisateur à {% data variables.location.product_location %}. Pour plus d’informations, consultez « [À propos de l’authentification pour votre entreprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise) ».
-You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
+Vous pouvez également exiger une authentification à 2 facteurs pour chacune de vos organisations. Pour plus d’informations, consultez « [Exiger l’authentification à 2 facteurs pour une organisation](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization) ».
-### 2. Staying in compliance
-You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+### 2. Maintenir la conformité
+Vous pouvez implémenter les vérifications d’état requises et commiter ces vérifications afin de respecter les normes de conformité de votre organisation et d’automatiser les workflows de conformité. Vous pouvez également utiliser le journal d’audit de votre organisation pour examiner les actions effectuées par votre équipe. Pour plus d’informations, consultez « [Application d’une stratégie avec des hooks de préréception](/admin/policies/enforcing-policy-with-pre-receive-hooks) » et « [À propos du journal d’audit de votre entreprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise) ».
{% ifversion ghes %}
-### 3. Configuring security features for your organizations
-{% data reusables.getting-started.configuring-security-features %}
-{% endif %}
+### 3. Configurer les fonctionnalités de sécurité pour vos organisations
+{% data reusables.getting-started.configuring-security-features %} {% endif %}
{% ifversion ghes %}
-### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
-You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+### 4. Activer les fonctionnalités de {% data variables.product.prodname_GH_advanced_security %}
+Vous pouvez mettre à niveau votre licence {% data variables.product.product_name %} pour inclure {% data variables.product.prodname_GH_advanced_security %}. Cette licence donne accès à des fonctionnalités supplémentaires qui aident les utilisateurs à détecter et résoudre les problèmes de sécurité dans leur code, tels que l’analyse du code et des secrets. Pour plus d’informations, consultez « [{% data variables.product.prodname_GH_advanced_security %} pour votre entreprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise) ».
{% endif %}
-## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
-You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
+## Partie 4 : Personnalisation et automatisation du travail dans votre entreprise dans {% data variables.product.prodname_dotcom %}
+Vous pouvez personnaliser et automatiser le travail dans les organisations de votre entreprise avec {% data variables.product.prodname_dotcom %} et {% data variables.product.prodname_oauth_apps %}, l’API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} et {% data variables.product.prodname_pages %}.
-### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Créer avec {% data variables.product.prodname_github_apps %} et {% data variables.product.prodname_oauth_apps %}
+Vous pouvez créer des intégrations avec l’API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, comme {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_apps %}, en vue de les utiliser ensuite dans les organisations pour compléter et étendre vos workflows. Pour plus d’informations, consultez « [À propos des applications](/developers/apps/getting-started-with-apps/about-apps) ».
+### 2. Utiliser l’API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
{% data reusables.getting-started.api %}
{% ifversion ghes %}
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. Créer avec {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+Pour plus d’informations sur l’activation et la configuration de {% data variables.product.prodname_actions %} sur {% data variables.product.product_name %}, consultez « [Bien démarrer avec {% data variables.product.prodname_actions %} pour {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server) ».
-### 4. Publishing and managing {% data variables.product.prodname_registry %}
+### 4. Publier et gérer des packages avec {% data variables.product.prodname_registry %}
{% data reusables.getting-started.packages %}
-For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+Pour plus d’informations sur l’activation et la configuration de {% data variables.product.prodname_registry %} pour {% data variables.location.product_location %}, consultez « [Bien démarrer avec {% data variables.product.prodname_registry %} pour votre entreprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise) ».
{% endif %}
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. Utiliser {% data variables.product.prodname_pages %}
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
-You can use {% data variables.product.prodname_github_connect %} to share resources.
+## Partie 5 : Connexion à d’autres ressources {% data variables.product.prodname_dotcom %}
+Vous pouvez utiliser {% data variables.product.prodname_github_connect %} pour partager des ressources.
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Si vous êtes propriétaire d’une instance de {% data variables.product.product_name %} et d’un compte d’entreprise ou d’organisation {% data variables.product.prodname_ghe_cloud %}, vous pouvez activer {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} vous permet de partager des workflows et fonctionnalités spécifiques entre {% data variables.location.product_location %} et {% data variables.product.prodname_ghe_cloud %}, par exemple une recherche unifiée et des contributions. Pour plus d’informations, consultez « [Connexion de {% data variables.product.prodname_ghe_server %} à {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud) ».
-## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Partie 6 : Utilisation des ressources d’apprentissage et de support de {% data variables.product.prodname_dotcom %}
+Les membres de votre entreprise peuvent utiliser nos ressources d’apprentissage pour en apprendre davantage sur Git et {% data variables.product.prodname_dotcom %}. Vous pouvez aussi contacter le Support {% data variables.product.prodname_dotcom %} Enterprise si vous avez besoin d’aide pour configurer et gérer {% data variables.location.product_location %}.
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+### 1. Consulter la documentation relative à {% data variables.product.product_name %} sur {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+Vous pouvez consulter la documentation qui décrit les fonctionnalités disponibles avec {% data variables.product.prodname_ghe_server %}. Pour plus d’informations, consultez « [À propos des versions de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs) ».
{% data reusables.enterprise.best-practices %}
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. Apprendre avec {% data variables.product.prodname_learning %}
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Faire appel au Support {% data variables.product.prodname_dotcom %} Enterprise
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/fr-FR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/fr-FR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 02ab297dbb..110f3438cd 100644
--- a/translations/fr-FR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
+++ b/translations/fr-FR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,6 +1,6 @@
---
-title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
-intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
+title: 'Migration depuis {% data variables.product.prodname_projects_v1 %}'
+intro: 'Vous pouvez migrer votre {% data variables.projects.projects_v1_board %} vers la nouvelle expérience de {% data variables.product.prodname_projects_v2 %}.'
miniTocMaxHeadingLevel: 3
versions:
feature: projects-v2
@@ -10,57 +10,53 @@ type: tutorial
topics:
- Projects
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e6db4fd8c6587f413ee0e6832dbae93bbf281573
+ms.sourcegitcommit: 9bf175b190674416ad4e11b5c567409f74c00ad2
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/23/2022
+ms.locfileid: '148181220'
---
-
-
{% note %}
-**Notes:**
+**Remarques :**
-- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
-- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
-- Automation will not be migrated.
-- Triage, archive, and activity will not be migrated.
-- After migration, the new migrated project and old project will not be kept in sync.
+- Si le projet que vous migrez contient plus de {% data variables.projects.item_limit %} éléments, les problèmes ouverts sont priorisés, suivis des demandes de tirage ouvertes, puis des notes. L’espace restant est utilisé pour les problèmes fermés, les demandes de tirage fusionnées et les demandes de tirage fermées. Les éléments qui ne peuvent pas être migrés en raison de cette limite sont déplacés vers l’archive. Si la limite d’archivage de {% data variables.projects.archived_item_limit %} éléments est atteinte, aucun élément supplémentaire n’est migré.
+- Notez que les cartes sont converties en brouillons de problème et que le contenu est enregistré dans le corps du brouillon. Si des informations apparaissent manquantes, affichez les champs masqués. Pour plus d’informations, consultez « [Affichage et masquage des champs](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields) ».
+- L’automatisation n’est pas migrée.
+- Le tri, l’archivage et l’activité ne sont pas migrés.
+- Après la migration, le nouveau projet migré et l’ancien projet ne restent pas synchronisés.
{% endnote %}
-## About project migration
+## À propos de la migration des projets
-You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
+Vous pouvez migrer vos panneaux de projet vers la nouvelle expérience de {% data variables.product.prodname_projects_v2 %} et essayer des tableaux, plusieurs vues, les nouvelles options d’automatisation et des types de champs performants. Pour plus d’informations, consultez « [À propos des projets](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) ».
-## Migrating an organization project board
+## Migration d’un tableau de projet d’organisation
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
-1. On the left, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
+1. Sur la gauche, cliquez sur **Projets (classique)** .
+  {% data reusables.projects.migrate-project-steps %}
-## Migrating a user project board
+## Migration d’un tableau de projet d’utilisateur
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_profile %}
-1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
- 
-1. Above the list of projects, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
+1. En haut de votre page de profil, dans le volet de navigation principal, cliquez sur {% octicon "table" aria-label="The project board icon" %} **Projets**.
+ 
+1. Au-dessus de la liste des projets, cliquez sur **Projets (classique)** .
+  {% data reusables.projects.migrate-project-steps %}
-## Migrating a repository project board
+## Migration d’un tableau de projet de dépôt
{% note %}
-**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
+**Remarque :** {% data variables.projects.projects_v2_caps %} ne prend pas en charge les projets de niveau dépôt. Lorsque vous migrez un tableau de projet de dépôt, celui-ci migre vers l’organisation ou le compte personnel propriétaire du projet de dépôt, tandis que le projet migré est épinglé au dépôt d’origine.
{% endnote %}
-{% data reusables.projects.enable-migration %}
-{% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
-
-1. Click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
+1. Sous le nom de votre dépôt, cliquez sur {% octicon "table" aria-label="The project board icon" %} **Projets**.
+
+1. Cliquez sur **Projets (classique)** .
+  {% data reusables.projects.migrate-project-steps %}
diff --git a/translations/fr-FR/content/packages/quickstart.md b/translations/fr-FR/content/packages/quickstart.md
index 7ff2db3442..3f285ef952 100644
--- a/translations/fr-FR/content/packages/quickstart.md
+++ b/translations/fr-FR/content/packages/quickstart.md
@@ -1,6 +1,6 @@
---
-title: Quickstart for GitHub Packages
-intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
+title: Démarrage rapide pour les packages GitHub
+intro: 'Publiez sur {% data variables.product.prodname_registry %} avec {% data variables.product.prodname_actions %}.'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -8,29 +8,34 @@ versions:
ghae: '*'
ghec: '*'
shortTitle: Quickstart
+ms.openlocfilehash: 887c4ee6c5e6b3e2c391c2d5754cfcb2787e4b86
+ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/24/2022
+ms.locfileid: '148181253'
---
-
{% data reusables.actions.enterprise-github-hosted-runners %}
## Introduction
-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 %}.
+Dans ce guide, vous allez créer un workflow {% data variables.product.prodname_actions %} pour tester votre code, puis publiez-le sur {% data variables.product.prodname_registry %}.
-## Publishing your package
+## Publication de votre package
-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.
+1. Créez un nouveau référentiel sur {% data variables.product.prodname_dotcom %}, en ajoutant le nœud `.gitignore`. Pour plus d’informations, consultez « [Création d’un dépôt](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository) ».
+2. Clonez le référentiel sur votre ordinateur local.
```shell
$ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
$ cd YOUR-REPOSITORY
```
-3. Create an `index.js` file and add a basic alert to say "Hello world!"
+3. Créez un fichier `index.js` et ajoutez une alerte de base pour dire « Bonjour le monde ! »
{% raw %}
```javascript{:copy}
console.log("Hello, World!");
```
{% endraw %}
-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.
+4. Initialisez un package npm avec `npm init`. Dans l’Assistant Initialisation du package, entrez votre package avec le nom : _`@YOUR-USERNAME/YOUR-REPOSITORY`_ et définissez le script de test sur `exit 0`. Cela génère un fichier `package.json` contenant des informations sur votre package.
{% raw %}
```shell
$ npm init
@@ -41,15 +46,15 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
...
```
{% endraw %}
-5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
+5. Exécutez `npm install` pour générer le fichier `package-lock.json`, puis validez et envoyez (push) vos modifications à {% 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. 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 %}.
+6. Créez un répertoire `.github/workflows`. Dans ce répertoire, créez un fichier nommé `release-package.yml`.
+7. Copiez le contenu YAML suivant dans le fichier `release-package.yml`{% ifversion ghes or ghae %}, en remplaçant `YOUR-HOSTNAME` par le nom de votre entreprise{% endif %}.
```yaml{:copy}
name: Node.js Package
@@ -85,22 +90,20 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
env:
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
```
-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 %}
+8. Indiquez à NPM l’étendue et le Registre pour publier des packages à l’aide de l’une des méthodes suivantes :
+ - Ajoutez un fichier de configuration NPM pour le référentiel en créant un fichier `.npmrc` dans le répertoire racine avec le contenu : {% raw %}
```shell
@YOUR-USERNAME:registry=https://npm.pkg.github.com
```
{% endraw %}
- - Edit the `package.json` file and specify the `publishConfig` key:
- {% raw %}
+ - Modifiez le fichier `package.json` et spécifiez la clé `publishConfig` : {% raw %}
```shell
"publishConfig": {
"@YOUR-USERNAME:registry": "https://npm.pkg.github.com"
}
```
{% endraw %}
-9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
+9. Validez et envoyez (push) vos modifications à {% 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.
@@ -108,28 +111,26 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
$ git commit -m "workflow to publish package"
$ git push
```
-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 %}.
+10. Le workflow que vous avez créé s’exécute chaque fois qu’une nouvelle version est créée dans votre référentiel. Si les tests réussissent, le package est publié sur {% data variables.product.prodname_registry %}.
- 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)."
+ Pour le tester, accédez à l’onglet **Coder** de votre référentiel et créez une version. Pour plus d’informations, consultez « [Gestion des versions dans un référentiel](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release) ».
-## Viewing your published package
+## Affichage de votre package publié
-You can view all of the packages you have published.
+Vous pouvez afficher tous les packages que vous avez publiés.
-{% 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
+## Utilisation d’un package publié
-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)."
+Maintenant que vous avez publié le package, vous souhaiterez l’utiliser comme dépendance entre vos projets. Pour plus d’informations, consultez « [Utilisation du registre npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package). »
-## Next steps
+## Étapes suivantes
-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.
+Le workflow de base que vous venez d’ajouter s’exécute chaque fois qu’une nouvelle version est créée dans votre référentiel. Mais ce n’est que le début de ce que vous pouvez faire avec {% data variables.product.prodname_registry %}. Vous pouvez publier votre package sur plusieurs registres avec un seul workflow, déclencher l’exécution du workflow sur différents événements tels qu’une demande de tirage fusionnée, gérer des conteneurs, etc.
-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 %}:
+La combinaison de {% data variables.product.prodname_registry %} et de {% data variables.product.prodname_actions %} peut vous aider à automatiser presque tous les aspects de vos processus de développement d’applications. Vous êtes prêt à commencer ? Voici quelques ressources utiles pour effectuer vos étapes suivantes avec {% data variables.product.prodname_registry %} et {% data variables.product.prodname_actions %} :
-- "[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
+- « [Découvrir {% data variables.product.prodname_registry %}](/packages/learn-github-packages) » pour obtenir un tutoriel approfondi sur les packages GitHub
+- « [Découvrir {% data variables.product.prodname_actions %}](/actions/learn-github-actions) » pour obtenir un tutoriel approfondi sur GitHub Actions
+- « [Utilisation d’un registre {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry) » pour découvrir des cas d’utilisation et des exemples spécifiques
diff --git a/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 305c0377c4..02c860bd1f 100644
--- a/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -15,12 +15,12 @@ versions:
topics:
- Pull requests
shortTitle: Deleted or changes visibility
-ms.openlocfilehash: d52215a7406edc84bc71022517f848faa9e48600
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 95296f33d9163cd1171481386efd0a2351095c39
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
ms.translationtype: HT
ms.contentlocale: fr-FR
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '147886797'
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191362'
---
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
@@ -32,7 +32,7 @@ Quand vous supprimez un dépôt privé, toutes ses duplications privées sont é
## Suppression d’un dépôt public
-Quand vous supprimez un dépôt public, l’une des duplications publiques existantes est choisie comme nouveau dépôt parent. Tous les autres dépôts sont dupliqués à partir de ce nouveau parent et les demandes de tirage suivantes sont poussées vers ce nouveau parent.
+Quand vous supprimez un référentiel public, l’une des duplications publiques existantes est choisie comme nouveau référentiel en amont. Tous les autres référentiels sont dupliqués à partir de ce nouveau référentiel en amont et les demande de tirage (pull request) suivantes se dirigent vers ce nouveau référentiel en amont.
{% endif %}
@@ -44,9 +44,9 @@ Quand vous supprimez un dépôt public, l’une des duplications publiques exist
## Changement d’un dépôt public en dépôt privé
-Si un dépôt public est rendu privé, ses duplications publiques sont séparées dans un nouveau réseau. Comme pour la suppression d’un dépôt public, une des duplications publiques existantes est choisie comme nouveau dépôt parent et tous les autres dépôts sont dupliqués à partir de ce nouveau parent. Les demandes de tirage suivantes sont poussées vers ce nouveau parent.
+Si un dépôt public est rendu privé, ses duplications publiques sont séparées dans un nouveau réseau. Comme pour la suppression d’un référentiel public, une des duplications publiques existantes est choisie comme nouveau référentiel en amont et tous les autres référentiels sont dupliqués à partir de ce nouveau référentiel en amont. Les demandes de tirage suivantes sont poussées vers ce nouveau référentiel en amont.
-En d’autres termes, les duplications d’un dépôt public restent publiques dans leur propre réseau de dépôts distinct, même après que le dépôt parent est devenu privé. Cela permet aux propriétaires de duplication de continuer à travailler et à collaborer sans interruption. Si les duplications publiques n’ont pas été déplacées dans un réseau distinct de cette façon, les propriétaires de ces duplications doivent obtenir les [autorisations d’accès](/articles/access-permissions-on-github) appropriées pour tirer les changements du dépôt parent (maintenant privé) et lui envoyer des demandes de tirage, même s’ils n’avaient pas besoin de ces autorisations avant.
+En d’autres termes, les duplications d’un référentiel public restent publiques dans leur propre réseau de référentiels distinct, même après que le référentiel en amont soit devenu privé. Cela permet aux propriétaires de duplication de continuer à travailler et à collaborer sans interruption. Si les duplications publiques n’ont pas été déplacées dans un réseau distinct de cette façon, les propriétaires de ces duplications doivent obtenir les [autorisations d’accès](/articles/access-permissions-on-github) appropriées pour tirer les changements du référentiel en amont (maintenant privé) et lui envoyer des demandes de tirage, même s’ils n’avaient pas besoin de ces autorisations avant.
{% ifversion ghes or ghae %} Si un dépôt public a un accès en lecture Git anonyme activé et que le dépôt est rendu privé, toutes les duplications du dépôt perdent l’accès en lecture Git anonyme et ont à nouveau le paramètre désactivé par défaut. Si un dépôt dupliqué est rendu public, les administrateurs de dépôt peuvent réactiver l’accès en lecture Git anonyme. Pour plus d’informations, consultez « [Activation de l’accès en lecture Git anonyme pour un dépôt](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) ».
{% endif %}
@@ -57,7 +57,7 @@ Si un dépôt public est rendu privé, puis supprimé, ses duplications publique
## Changement d’un dépôt privé en dépôt public
-Si un dépôt privé est rendu public, chacune de ses duplications privées est transformée en dépôt privé autonome et devient le parent de son propre nouveau réseau de dépôts. Les duplications privées ne sont jamais rendues publiques automatiquement, car elles peuvent contenir des commits sensibles qui ne doivent pas être exposés publiquement.
+Si un référentiel privé est rendu public, chacune de ses duplications privées est transformée en référentiel privé autonome et devient le référentiel en amont de son propre nouveau réseau de référentiels. Les duplications privées ne sont jamais rendues publiques automatiquement, car elles peuvent contenir des commits sensibles qui ne doivent pas être exposés publiquement.
### Suppression du dépôt public
diff --git a/translations/fr-FR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/fr-FR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
index a66e99ee9a..b1eb0982c3 100644
--- a/translations/fr-FR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
+++ b/translations/fr-FR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository from a template
-intro: You can generate a new repository with the same directory structure and files as an existing repository.
+title: Création d’un dépôt à partir d’un modèle
+intro: Vous pouvez générer un nouveau dépôt avec les mêmes structure de répertoires et fichiers qu’un dépôt existant.
redirect_from:
- /articles/creating-a-repository-from-a-template
- /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template
@@ -13,45 +13,46 @@ versions:
topics:
- Repositories
shortTitle: Create from a template
+ms.openlocfilehash: 16d124431426e19cf95c768e8a4cdaa5f4da2e17
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159763'
---
-## About repository templates
+## À propos des modèles de dépôt
-Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)."
+Toute personne disposant d’autorisations de lecture sur un modèle de dépôt peut créer un dépôt à partir de celui-ci. Pour plus d’informations, consultez « [Création d’un modèle de dépôt](/articles/creating-a-template-repository) ».
{% tip %}
-**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+**Astuce** : vous pouvez également créer un dépôt à partir d’un modèle à l’aide de la {% data variables.product.prodname_cli %}. Pour plus d’informations, consultez « [`gh repo create`](https://cli.github.com/manual/gh_repo_create) » dans la documentation {% data variables.product.prodname_cli %}.
{% endtip %}
-You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
+Vous pouvez choisir d’inclure la structure et les fichiers de répertoire uniquement à partir de la branche par défaut du modèle de dépôt, ou d’inclure toutes les branches. Les branches créées à partir d’un modèle ont des historiques séparés, ce qui signifie que vous ne pouvez pas créer de demandes de tirage ou de fusion entre les branches.
-Creating a repository from a template is similar to forking a repository, but there are important differences:
-- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit.
-- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph.
-- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly.
+La création d’un dépôt à partir d’un modèle est similaire à la duplication d’un dépôt, mais il existe des différences importantes :
+- Une nouvelle duplication inclut tout l’historique de validation du dépôt parent, tandis qu’un dépôt créé à partir d’un modèle commence avec une validation unique.
+- Les validations d’une duplication n’apparaissent pas dans votre graphique de contributions, tandis que les validations d’un dépôt créé à partir d’un modèle apparaissent dans votre graphique de contribution.
+- Une duplication peut être un moyen temporaire de contribuer au code d’un projet existant, tandis que la création d’un dépôt à partir d’un modèle démarre un nouveau projet rapidement.
-For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
+Pour plus d’informations sur les duplications, consultez « [À propos des duplications](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) ».
-## Creating a repository from a template
+## Création d’un dépôt à partir d’un modèle
{% data reusables.repositories.navigate-to-repo %}
-1. Above the file list, click **Use this template**.
+1. Au-dessus de la liste de fichiers, cliquez sur **Utiliser ce modèle**.
{% ifversion fpt or ghec %}
-1. Select **Create a new repository**.
+1. Sélectionnez **Créer un dépôt**.
- 
+ 
{% note %}
- **Note:** Alternatively, you can open the template in a codespace and publish your work to a new repository later. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+ **Remarque :** Vous pouvez également ouvrir le modèle dans un codespace et publier votre travail sur un nouveau dépôt plus tard. Pour plus d’informations, consultez « [Création d’un codespace à partir d’un modèle](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template) ».
- {% endnote %}
-{% endif %}
-{% data reusables.repositories.owner-drop-down %}
-{% data reusables.repositories.repo-name %}
-{% data reusables.repositories.choose-repo-visibility %}
-1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
- 
-{% data reusables.repositories.select-marketplace-apps %}
-8. Click **Create repository from template**.
+ {% endnote %} {% endif %} {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %}
+1. Si vous le souhaitez, pour inclure la structure et les fichiers de répertoire de toutes les branches dans le modèle, et pas seulement de la branche par défaut, sélectionnez **Inclure toutes les branches**.
+  {% data reusables.repositories.select-marketplace-apps %}
+8. Cliquez sur **Create repository from template** (Créer un référentiel à partir du modèle).
diff --git a/translations/fr-FR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/fr-FR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
index 151756761d..7174fcaa4b 100644
--- a/translations/fr-FR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
+++ b/translations/fr-FR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
@@ -1,6 +1,6 @@
---
-title: Automatically generated release notes
-intro: You can automatically generate release notes for your GitHub releases
+title: Notes de publication générées automatiquement
+intro: Vous pouvez générer automatiquement des notes de publication pour vos versions GitHub
permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release.
versions:
fpt: '*'
@@ -13,71 +13,63 @@ shortTitle: Automated release notes
communityRedirect:
name: Provide GitHub Feedback
href: 'https://github.com/orgs/community/discussions/categories/general'
+ms.openlocfilehash: aee951e6f57492240b5baf8870578409945aefdc
+ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/29/2022
+ms.locfileid: '148185193'
---
+## À propos des notes de publication générées automatiquement
-## About automatically generated release notes
+Les notes de publication générées automatiquement offrent une alternative automatisée à l’écriture manuelle des notes de publication pour vos versions {% data variables.product.prodname_dotcom %}. Avec des notes de publication générées automatiquement, vous pouvez rapidement générer une vue d’ensemble du contenu d’une version. Les notes de publication générées automatiquement incluent une liste de demandes de tirage (pull request) fusionnées, une liste de contributeurs à la version et un lien vers un journal de modification complet.
-Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. Automatically generated release notes include a list of merged pull requests, a list of contributors to the release, and a link to a full changelog.
+Vous pouvez également personnaliser vos notes de publication automatisées en utilisant des étiquettes pour créer des catégories personnalisées afin d’y organiser les demandes de tirage de votre choix, et exclure certaines étiquettes et utilisateurs dans la sortie.
-You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
+## Création de notes de publication générées automatiquement pour une nouvelle version
-## Creating automatically generated release notes for a new release
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
- 
-4. {% ifversion fpt or ghec %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag.
- {% ifversion fpt or ghec %}
- 
-5. If you are creating a new tag, click **Create new tag**.
-
- {% else %}
- 
-{% endif %}
-6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
- {% ifversion fpt or ghec %}
- {% else %}
- {% endif %}
-{%- data reusables.releases.previous-release-tag %}
-7. To the top right of the description text box, click {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% ifversion previous-release-tag %}
- {% else %}
- {% endif %}
-8. Check the generated notes to ensure they include all (and only) the information you want to include.
-9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
- 
-10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
- 
-{%- ifversion fpt or ghec %}
-11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
- 
-{%- endif %}
-12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+3. Cliquez sur **Créer un brouillon d’une nouvelle version**.
+ 
+4. {% ifversion fpt or ghec %}Cliquez sur **Choisir une étiquette** et tapez{% else %}Tapez{% endif %} un numéro de version pour votre version. Vous pouvez aussi sélectionner une étiquette existante.
+ {% ifversion fpt or ghec %} 
+5. Si vous créez une étiquette, cliquez sur **Créer une étiquette**.
+ {% else %}  {% endif %}
+6. Si vous avez créé une étiquette, utilisez le menu déroulant pour sélectionner la branche qui contient le projet à publier.
+ {% ifversion fpt or ghec %} {% else %} {% endif %} {%- data reusables.releases.previous-release-tag %}
+7. En haut à droite de la zone de texte de description, cliquez sur {% ifversion previous-release-tag %}**Générer des notes de publication**{% else %}**Générer automatiquement des notes de publication**{% endif %}.{% ifversion previous-release-tag %} {% else %} {% endif %}
+8. Passez en revue les notes générées pour vérifier qu’elles comprennent toutes (et uniquement) les informations que vous voulez ajouter.
+9. Vous pouvez aussi ajouter des fichiers binaires comme des programmes compilés dans votre mise en production, pour ce faire, faites un glisser-déposer des fichiers dans la zone Fichiers binaires, ou sélectionnez-les manuellement.
+ 
+10. Pour avertir les utilisateurs que la mise en production n’est pas prête pour la production et peut être instable, sélectionnez **Il s’agit d’une préversion**.
+  {%- ifversion fpt or ghec %}
+11. Vous pouvez aussi sélectionner **Créer une discussion pour cette version**, puis sélectionner le menu déroulant **Catégorie** et cliquer sur une catégorie pour la discussion de mise en production.
+  {%- endif %}
+12. Si vous êtes prêt à rendre publique votre mise en production, cliquez sur **Publier la mise en production**. Pour travailler sur la mise en production par la suite, cliquez sur **Enregistrer le brouillon**.
+ 
-## Configuring automatically generated release notes
+## Configuration des notes de publication générées automatiquement
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory.
- 
-4. In the file, using the configuration options below, specify in YAML the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Dans le champ de nom de fichier, tapez `.github/release.yml` pour créer le fichier `release.yml` dans le répertoire `.github`.
+ 
+4. Dans le fichier, en utilisant les options de configuration ci-dessous, spécifiez dans le YAML les étiquettes et les auteurs de demande de tirage à exclure de cette version. Vous pouvez également créer des catégories et lister les étiquettes de demande de tirage qui doivent être ajoutées dans chacune d’elles.
-### Configuration options
+### Options de configuration
-| Parameter | Description |
+| Paramètre | Description |
| :- | :- |
-| `changelog.exclude.labels` | A list of labels that exclude a pull request from appearing in release notes. |
-| `changelog.exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from release notes. |
-| `changelog.categories[*].title` | **Required.** The title of a category of changes in release notes. |
-| `changelog.categories[*].labels`| **Required.** Labels that qualify a pull request for this category. Use `*` as a catch-all for pull requests that didn't match any of the previous categories. |
-| `changelog.categories[*].exclude.labels` | A list of labels that exclude a pull request from appearing in this category. |
-| `changelog.categories[*].exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from this category. |
+| `changelog.exclude.labels` | Liste d’étiquettes qui excluent une demande de tirage dans les notes de publication. |
+| `changelog.exclude.authors` | Liste des descripteurs de connexion d’utilisateur ou de bot dont les demandes de tirage doivent être exclues des notes de publication. |
+| `changelog.categories[*].title` | **Obligatoire.** Titre d’une catégorie de changements dans les notes de publication. |
+| `changelog.categories[*].labels`| **Obligatoire.** Étiquettes qui qualifient une demande de tirage pour cette catégorie. Utilisez `*` comme « fourre-tout » pour les demandes de tirage qui ne correspondent à aucune des catégories précédentes. |
+| `changelog.categories[*].exclude.labels` | Liste d’étiquettes qui excluent une demande de tirage dans cette catégorie. |
+| `changelog.categories[*].exclude.authors` | Liste des descripteurs de connexion d’utilisateur ou de bot dont les demandes de tirage doivent être exclues de cette catégorie. |
-### Example configurations
+### Exemples de configurations
-A configuration for a repository that labels semver releases
+Configuration d’un référentiel qui étiquette les versions SemVer
{% raw %}
```yaml{:copy}
@@ -104,7 +96,7 @@ changelog:
```
{% endraw %}
-A configuration for a repository that doesn't tag pull requests but where we want to separate out {% data variables.product.prodname_dependabot %} automated pull requests in release notes (`labels: '*'` is required to display a catchall category)
+Configuration d’un référentiel qui ne balise pas les demandes de tirage, mais dans lequel nous voulons séparer les demandes de tirage automatisées {% data variables.product.prodname_dependabot %} dans les notes de publication (`labels: '*'` est nécessaire pour afficher une catégorie catchall)
{% raw %}
```yaml{:copy}
@@ -124,6 +116,6 @@ changelog:
```
{% endraw %}
-## Further reading
+## Pour aller plus loin
-- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)"
+- « [Gestion des étiquettes](/issues/using-labels-and-milestones-to-track-work/managing-labels) »
diff --git a/translations/fr-FR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/fr-FR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
index d20cda1455..4a612262dd 100644
--- a/translations/fr-FR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
+++ b/translations/fr-FR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
@@ -1,6 +1,6 @@
---
title: Compréhension des connexions entre dépôts
-intro: Vous pouvez mieux comprendre les connexions qui existent entre les dépôts en consultant le réseau et les duplication (fork) d’un dépôt et les projets qui dépendent de ce dernier.
+intro: Utilisez le graphique réseau et la liste des duplications pour comprendre les réseaux de duplications.
product: '{% data reusables.gated-features.repository-insights %}'
redirect_from:
- /articles/viewing-a-repository-s-network
@@ -22,16 +22,17 @@ versions:
topics:
- Repositories
shortTitle: Connections between repositories
-ms.openlocfilehash: f1b92a62d0acf9f31a16ce1b7c57850b87c1bf9c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 46cc440093c3ca8dc0952933847a6f04b0446661
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
ms.translationtype: HT
ms.contentlocale: fr-FR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147060065'
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191357'
---
## Affichage du réseau d’un dépôt
-Le graphique du réseau affiche l’historique des branches de tout le réseau du dépôt, y compris les branches du dépôt racine et celles des duplications qui contiennent des validations propres au réseau.
+Le graphique réseau affiche l’historique des branches de l’ensemble du réseau de référentiels, y compris les branches de duplication. Ce graphique est une chronologie des validations les plus récentes et affiche jusqu’à 100 des branches les plus récemment envoyées. La première ligne fait référence à la date et la première colonne fait référence au propriétaire de la branche. Utilisez des touches de direction ou d’autres raccourcis clavier pour naviguer plus facilement dans le graphique. Ils sont fournis dans la fenêtre contextuelle « Raccourcis clavier disponibles » sous le graphique.
+
@@ -51,7 +52,7 @@ Le graphique du réseau affiche l’historique des branches de tout le réseau d
Le graphique Membres affiche toutes les duplications d’un dépôt.
-Les duplications sont présentées dans l’ordre alphabétique du nom d’utilisateur de la personne qui a dupliqué le dépôt. Vous pouvez cliquer sur le nom d’utilisateur afin d’être redirigé vers la page de profil {% data variables.product.product_name %} de l’utilisateur, ou cliquer sur le nom de duplication afin d’être redirigé vers la duplication spécifique du dépôt.
+Les duplications sont présentées dans l’ordre alphabétique de l’organisation ou du nom d’utilisateur de la personne qui a dupliqué le référentiel. Vous pouvez cliquer sur l’organisation ou le nom d’utilisateur afin d’être redirigé vers la page de profil {% data variables.product.product_name %} de l’organisation ou de l’utilisateur ou cliquer sur le nom de duplication afin d’être redirigé vers la duplication spécifique du référentiel.
{% ifversion fpt or ghec %}
diff --git a/translations/fr-FR/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/fr-FR/content/repositories/working-with-files/using-files/viewing-a-file.md
index ea88316e23..d4f4d054f1 100644
--- a/translations/fr-FR/content/repositories/working-with-files/using-files/viewing-a-file.md
+++ b/translations/fr-FR/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -1,6 +1,6 @@
---
-title: Viewing a file
-intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
+title: Affichage d’un fichier
+intro: Vous pouvez afficher le contenu brut du fichier ou suivre les modifications apportées aux lignes d’un fichier et découvrir comment les différentes parties du fichier ont évolué au fil du temps.
redirect_from:
- /articles/using-git-blame-to-trace-changes-in-a-file
- /articles/tracing-changes-in-a-file
@@ -16,48 +16,54 @@ versions:
topics:
- Repositories
shortTitle: View files and track file changes
+ms.openlocfilehash: 7d34e776cb1747ee749531e49abf6f0e3d052b3b
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179848'
---
-## Viewing or copying the raw file content
+## Affichage ou copie du contenu d’un fichier brut
-With the raw view, you can view or copy the raw content of a file without any styling.
+L’affichage brut vous permet d’afficher ou de copier le contenu brut d’un fichier sans aucun style.
{% data reusables.repositories.navigate-to-repo %}
-1. Click the file that you want to view.
-2. In the upper-right corner of the file view, click **Raw**.
-
-3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
+1. Cliquez sur le fichier que vous souhaitez afficher.
+2. Dans le coin supérieur droit de l’affichage du fichier, cliquez sur **Brut**.
+
+3. Si vous le souhaitez, pour copier le contenu du fichier brut, dans le coin supérieur droit de l’affichage du fichier, cliquez sur **{% octicon "copy" aria-label="The copy icon" %}** .
-## Viewing the line-by-line revision history for a file
+## Affichage de l’historique de révision ligne par ligne pour un fichier
-With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
+L’affichage des blâmes vous permet de voir l’historique de révision ligne par ligne pour un fichier entier ou l’historique de révision d’une seule ligne dans un fichier en cliquant sur {% octicon "versions" aria-label="The prior blame icon" %}. Chaque fois que vous cliquez sur {% octicon "versions" aria-label="The prior blame icon" %}, vous voyez des informations sur la révision précédente pour cette ligne, notamment qui a commité la modification et quand.
-
+
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+Dans un fichier ou une demande de tirage (pull request), vous pouvez également utiliser le menu {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} pour afficher le blâme Git pour une ligne ou une plage de lignes sélectionnée.
-
+
{% tip %}
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+**Conseil :** À la ligne de commande, vous pouvez également utiliser `git blame` pour afficher l’historique de révision des lignes dans un fichier. Pour plus d’informations, consultez la [documentation Git sur `git blame`](https://git-scm.com/docs/git-blame).
{% endtip %}
{% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-
+2. Cliquez pour ouvrir le fichier dont vous souhaitez afficher l’historique des lignes.
+3. Dans le coin supérieur droit de l’affichage du fichier, cliquez sur **Blâmer** pour ouvrir l’affichage des blâmes.
+
+4. Pour voir les révisions antérieures d’une ligne spécifique, ou blâmer à nouveau, cliquez sur {% octicon "versions" aria-label="The prior blame icon" %} jusqu’à ce que vous trouviez les modifications qui vous intéressent.
+
{% ifversion blame-ignore-revs %}
-## Ignore commits in the blame view
+## Ignorer des commits dans l’affichage des blâmes
-All revisions specified in the `.git-blame-ignore-revs` file, which must be in the root directory of your repository, are hidden from the blame view using Git's `git blame --ignore-revs-file` configuration setting. For more information, see [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) in the Git documentation.
+Toutes les révisions spécifiées dans le fichier `.git-blame-ignore-revs`, qui doit se trouver dans le répertoire racine de votre dépôt, sont masquées de l’affichage des blâmes à l’aide du paramètre de configuration Git `git blame --ignore-revs-file`. Pour plus d’informations, consultez [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) dans la documentation Git.
-1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`.
-2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:
+1. Dans le répertoire racine de votre dépôt, créez un fichier nommé `.git-blame-ignore-revs`.
+2. Ajoutez les hachages de commit que vous souhaitez exclure de l’affichage des blâmes pour ce fichier. Nous vous recommandons de structurer le fichier comme suit, y compris les commentaires :
```ini
# .git-blame-ignore-revs
@@ -67,19 +73,19 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t
69d029cec8337c616552756310748c4a507bd75a
```
-3. Commit and push the changes.
+3. Commitez et poussez (push) les changements.
-Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden:
+Maintenant, lorsque vous visitez l’affichage des blâmes, les révisions listées ne sont pas incluses dans le blâme. Vous voyez la bannière **Révisions dans .git-blame-ignore-revs ignorées** qui indique que certains commits peuvent être masqués :
-
+
-This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well:
+Cela peut être utile si quelques commits apportent des modifications importantes à votre code. Vous pouvez également utiliser le fichier lors de l’exécution locale de `git blame` :
```shell
git blame --ignore-revs-file .git-blame-ignore-revs
```
-You can also configure your local git so it always ignores the revs in that file:
+Vous pouvez également configurer votre dépôt Git local afin qu’il ignore toujours les révisions dans ce fichier :
```shell
git config blame.ignoreRevsFile .git-blame-ignore-revs
@@ -87,6 +93,6 @@ git config blame.ignoreRevsFile .git-blame-ignore-revs
{% endif %}
-## Bypassing `.git-blame-ignore-revs` in the blame view
+## Contournement de `.git-blame-ignore-revs` dans l’affichage des blâmes
-If the blame view for a file shows **Ignoring revisions in .git-blame-ignore-revs**, you can still bypass `.git-blame-ignore-revs` and see the normal blame view. In the URL, append a `~` to the SHA and the **Ignoring revisions in .git-blame-ignore-revs** will disappear.
+Si l’affichage des blâmes d’un fichier indique **Révisions dans .git-blame-ignore-revs ignorées**, vous pouvez toujours contourner `.git-blame-ignore-revs` et consulter l’affichage des blâmes normal. Dans l’URL, ajoutez un `~` au SHA et les **Révisions dans .git-blame-ignore-revs ignorées** disparaîtront.
diff --git a/translations/fr-FR/content/rest/overview/libraries.md b/translations/fr-FR/content/rest/overview/libraries.md
index 9be500d2f6..80029ffd2b 100644
--- a/translations/fr-FR/content/rest/overview/libraries.md
+++ b/translations/fr-FR/content/rest/overview/libraries.md
@@ -11,12 +11,12 @@ versions:
ghec: '*'
topics:
- API
-ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
-ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
+ms.openlocfilehash: 5f633132edddb17ae129a3feba791ab8ec780366
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: fr-FR
-ms.lasthandoff: 12/01/2022
-ms.locfileid: '148190060'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191877'
---
@@ -26,7 +26,7 @@ Utilisez la bibliothèque Octokit officielle ou choisissez l’une des biblioth
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
-- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+- **JavaScript** → [octokit.js](https://github.com/octokit/octokit.js)
## Bibliothèques tierces
diff --git a/translations/fr-FR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/fr-FR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
index 58b43d823f..e53a389ec6 100644
--- a/translations/fr-FR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
+++ b/translations/fr-FR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -1,6 +1,6 @@
---
-title: Affichage et mise à jour des tickets de support
-intro: 'Vous pouvez afficher vos tickets de support{% ifversion ghes or ghec %}, collaborer avec des collègues sur des tickets,{% endif %} et répondre à {% data variables.contact.github_support %} à l’aide de {% data variables.contact.support_portal %}.'
+title: Viewing and updating support tickets
+intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.'
shortTitle: Managing your tickets
versions:
fpt: '*'
@@ -8,62 +8,64 @@ versions:
ghes: '*'
topics:
- Support
-ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: fr-FR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147051979'
---
-## À propos de la gestion des tickets
+
+## About ticket management
{% data reusables.support.zendesk-old-tickets %}
-Vous pouvez utiliser le [portail de support GitHub](https://support.github.com/) pour afficher les tickets de support actuels et passés et répondre à {% data variables.contact.github_support %}. Après 120 jours, les tickets résolus sont archivés{% ifversion ghec or ghes or ghae %} et les tickets archivés peuvent uniquement être consultés pour les comptes d’entreprise{% endif %}.
+You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}. After 120 days, resolved tickets are archived{% ifversion ghec or ghes or ghae %}, and archived tickets can only be viewed for enterprise accounts{% endif %}.
-{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+{% ifversion ghes or ghec %}
+{% data reusables.enterprise-accounts.support-entitlements %}
+{% endif %}
-## Affichage de vos tickets de support récents
+## Viewing your recent support tickets
{% data reusables.support.view-open-tickets %}
-1. Sous la zone de texte, vous pouvez lire l’historique des commentaires. La réponse la plus récente apparaît en haut.
-
+1. Under the text box, you can read the comment history. The most recent response is at the top.
+
+ 
+
+1. Optionally, to translate the ticket comment, click {% octicon "globe" aria-label="The globe icon" %} and choose your preferred language from the dropdown menu. You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish.
+
+ 
{% ifversion ghec or ghes or ghae %}
-## Affichage de vos tickets de support archivés
+## Viewing your archived support tickets
-Vous pouvez uniquement afficher les tickets archivés d’ compte d’entreprise.
+You can only view archived tickets for an enterprise account.
{% data reusables.support.navigate-to-my-tickets %}
-1. Sélectionnez le menu déroulant **Mes tickets** et cliquez sur le nom du compte d’entreprise.
+1. Select the **My Tickets** drop-down menu and click the name of the enterprise account.
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
- 
-1. Sous la table « Mes tickets », cliquez sur **Afficher les tickets archivés**.
+ 
+1. Under the "My tickets" table, click **View archived tickets**.
{% endif %}
-## Mise à jour de tickets de support
+## Updating support tickets
{% data reusables.support.view-open-tickets %}
-1. Si le problème est résolu, sous la zone de texte, cliquez sur **Fermer le ticket**.
-
-1. Pour répondre au support GitHub et ajouter un nouveau commentaire au ticket, entrez votre réponse dans la zone de texte.
-
-1. Pour ajouter votre commentaire au ticket, cliquez sur **Commentaire**.
-
+1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
+
+1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
+
+1. To add your comment to the ticket, click **Comment**.
+
{% ifversion ghec or ghes %}
-## Collaboration sur les tickets de support
+## Collaborating on support tickets
-Vous pouvez collaborer avec vos collègues sur des tickets de support à l’aide du portail de support. Les propriétaires, les gestionnaires de facturation et d’autres membres d’entreprise disposant de droits de support peuvent afficher les tickets associés à un compte d’entreprise ou à une organisation gérée par un compte d’entreprise. Pour plus d’informations, consultez « [Gestion des droits au support pour votre entreprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise) ».
+You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-En plus d’afficher les tickets, vous pouvez également ajouter des commentaires aux tickets de support si votre adresse e-mail est copiée sur le ticket ou si la personne qui a ouvert le ticket a utilisé une adresse e-mail avec un domaine vérifié pour le compte d’entreprise ou l’organisation gérée par un compte d’entreprise. Pour plus d’informations sur la vérification d’un domaine, consultez « [Vérification ou approbation d’un domaine pour votre entreprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise) » et « [Vérification ou approbation d’un domaine pour votre organisation](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization) ».
+In addition to viewing tickets, you can also add comments to support tickets if your email address is copied on the ticket or if the person who opened the ticket used an email address with a domain that is verified for the enterprise account or organization managed by an enterprise account. For more information about verifying a domain, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Verifying or approving a domain for your organization](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
{% endif %}
-## Pour aller plus loin
+## Further reading
-- « [À propos du support GitHub](/support/learning-about-github-support/about-github-support) »
+- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
diff --git a/translations/fr-FR/content/support/learning-about-github-support/about-github-support.md b/translations/fr-FR/content/support/learning-about-github-support/about-github-support.md
index f5d6525f05..be735ece17 100644
--- a/translations/fr-FR/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/fr-FR/content/support/learning-about-github-support/about-github-support.md
@@ -83,6 +83,10 @@ If you have any paid product or are a member of an organization with a paid prod
With {% data variables.product.product_name %}, you have access to support in English and Japanese.
{% endif %}
+{% ifversion fpt or ghec or ghes %}
+{% data reusables.support.support-ticket-translation-option %}
+{% endif %}
+
{% ifversion ghes or ghec %}
To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
diff --git a/translations/fr-FR/data/release-notes/enterprise-server/3-5/4.yml b/translations/fr-FR/data/release-notes/enterprise-server/3-5/4.yml
index 028b8750b6..2d4ef88879 100644
--- a/translations/fr-FR/data/release-notes/enterprise-server/3-5/4.yml
+++ b/translations/fr-FR/data/release-notes/enterprise-server/3-5/4.yml
@@ -29,4 +29,5 @@ sections:
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
- |
- GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
\ No newline at end of file
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/fr-FR/data/release-notes/enterprise-server/3-5/5.yml b/translations/fr-FR/data/release-notes/enterprise-server/3-5/5.yml
index e3c08b6549..05de05ac2b 100644
--- a/translations/fr-FR/data/release-notes/enterprise-server/3-5/5.yml
+++ b/translations/fr-FR/data/release-notes/enterprise-server/3-5/5.yml
@@ -1,27 +1,30 @@
date: '2022-08-30'
sections:
bugs:
- - 'Après avoir déverrouillé un référentiel pour un accès temporaire, un administrateur de site ne pouvait pas gérer les paramètres des produits de sécurité dans le référentiel.'
- - 'Des clés SSH administratives en double pouvaient apparaître à la fois dans la console de gestion et dans le fichier `/home/admin/.ssh/authorized_keys`.'
- - 'La page d’administration du site pour les utilisateurs individuels sur http(s)://HOSTNAME/stafftools/users/USERNAME/adminUSERNAME/admin contenait des fonctionnalités non prévues pour GitHub Enterprise Server.'
- - 'Dans certains cas, l’exécution de `ghe-cluster-config-apply` pouvait répliquer une configuration vide aux nœuds existants d’un cluster.'
- - 'Dans certains cas, les exécutions de configuration lancées avec `ghe-config-apply` ne se terminaient pas, ou renvoyaient une erreur `Container count mismatch`.'
- - 'Après la mise à jour d’un certificat TLS auto-signé sur une instance GitHub Enterprise Server, les éléments de l’interface utilisateur de certaines pages de l’interface web n’apparaissaient pas.'
- - 'La barre d’administration du site située en haut de l’interface web contenait un lien brisé vers le SHA de la version exécutée de l’application.'
- - 'Dans certains cas, les tâches d’arrière-plan pouvaient se bloquer à cause d’une bibliothèque qui était utilisée simultanément bien qu’elle ne soit pas thread-safe.'
- - 'Les alertes provenant de l’analyse des secrets pour les clients GitHub Advanced Security étaient absentes de l’interface web et de l’API REST si un administrateur de site n’effectuait pas directement la mise à niveau vers GitHub Enterprise Server 3.4. Les alertes sont maintenant visibles.'
- - 'Lorsqu’un utilisateur dupliquait un référentiel vers une organisation, une longue liste d’organisations ne s’affichait pas correctement.'
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
+ - When a user forked a repository into an organization, a long list of organizations would not render properly.
changes:
- - 'La génération des packs de support est plus rapide grâce à la parallélisation de l’assainissement des journaux. Pour plus d’informations sur les packs de support, consultez « [Fournir des données au support GitHub](/support/contacting-github-support/providing-data-to-github-support) »'
- - 'Les API qui contiennent la route `organization` ou `org` acceptent désormais le slug ou l’ID de l’organisation. Auparavant, les API n’acceptaient que les slugs, ce qui rendait inaccessibles les en-têtes `Link` des points de terminaison GitHub Advanced Security. Pour plus d’informations, consultez « [Organisations](https://docs.github.com/rest/orgs/orgs) » dans la documentation de l’API REST.'
- - "Le journal d’audit de l’entreprise inclut désormais davantage d’événements générés par les utilisateurs, comme `project.create`. L’API REST renvoie également des événements supplémentaires générés par les utilisateurs, comme `repo.create`. Pour plus d’informations, voir «\_[Accéder au journal d’audit de votre entreprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing the-audit-log-for-your-entreprise)\_» et «\_[Utiliser l’API du journal d’audit pour votre entreprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)\_»."
- - 'Dans certains cas, les réplicas du cache pouvaient rejeter certaines opérations Git sur des référentiels récemment mis à jour. Pour plus d’informations sur la mise en cache des référentiels, consultez « [À propos de la mise en cache des référentiels](/admin/enterprise-management/caching-repositories/about-repository-caching) »'
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
known_issues:
- - 'Sur une instance fraîchement configurée de {% data variables.product.prodname_ghe_server %} sans aucun utilisateur, un attaquant pourrait créer le premier utilisateur administrateur.'
- - 'Les règles de pare-feu personnalisées sont supprimées pendant le processus de mise à niveau.'
- - 'Les fichiers suivis par Git LFS [chargés via l’interface web](https://github.com/blog/2105-upload-files-to-your-repositories) sont incorrectement ajoutés directement au référentiel.'
- - 'Les questions ne peuvent pas être fermées si elles contiennent un permalien vers un blob dans le même référentiel, où le chemin de fichier du blob est supérieur à 255 caractères.'
- - "Lorsque l’option «\_Les utilisateurs peuvent effectuer des recherches sur GitHub.com\_» est activée avec GitHub Connect, les problèmes dans les référentiels privés et internes ne sont pas inclus dans les résultats de recherche de GitHub.com."
- - 'Le registre npm {% data variables.product.prodname_registry %} ne renvoie plus une valeur de temps dans les réponses de métadonnées. Cela a été fait pour permettre des améliorations substantielles des performances. Nous disposons toujours de toutes les données nécessaires pour renvoyer une valeur de temps dans le cadre de la réponse aux métadonnées et nous recommencerons à renvoyer cette valeur à l’avenir, une fois que nous aurons résolu les problèmes de performance existants.'
- - 'Les limites de ressources spécifiques au traitement des hooks de pré-réception peuvent entraîner l’échec de certains hooks de pré-réception.'
- - 'Les services Actions doivent être redémarrés après avoir restauré une appliance à partir d’une sauvegarde effectuée sur un hôte différent.'
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/fr-FR/data/release-notes/enterprise-server/3-6/1.yml b/translations/fr-FR/data/release-notes/enterprise-server/3-6/1.yml
index dc4d13e168..6e638df146 100644
--- a/translations/fr-FR/data/release-notes/enterprise-server/3-6/1.yml
+++ b/translations/fr-FR/data/release-notes/enterprise-server/3-6/1.yml
@@ -1,33 +1,38 @@
date: '2022-08-30'
sections:
bugs:
- - 'Après avoir déverrouillé un référentiel pour un accès temporaire, un administrateur de site ne pouvait pas gérer les paramètres des produits de sécurité dans le référentiel.'
- - 'Des clés SSH administratives en double pouvaient apparaître à la fois dans la console de gestion et dans le fichier `/home/admin/.ssh/authorized_keys`.'
- - 'La page d’administration du site pour les utilisateurs individuels sur http(s)://HOSTNAME/stafftools/users/USERNAME/adminUSERNAME/admin contenait des fonctionnalités non prévues pour GitHub Enterprise Server.'
- - 'Dans certains cas, l’exécution de `ghe-cluster-config-apply` pouvait répliquer une configuration vide aux nœuds existants d’un cluster.'
- - 'Dans certains cas, les exécutions de configuration lancées avec `ghe-config-apply` ne se terminaient pas, ou renvoyaient une erreur `Container count mismatch`.'
- - 'Après la mise à jour d’un certificat TLS auto-signé sur une instance GitHub Enterprise Server, les éléments de l’interface utilisateur de certaines pages de l’interface web n’apparaissaient pas.'
- - 'Dans certains cas, les tâches d’arrière-plan pouvaient se bloquer à cause d’une bibliothèque qui était utilisée simultanément bien qu’elle ne soit pas thread-safe.'
- - 'La barre d’administration du site située en haut de l’interface web contenait un lien brisé vers le SHA de la version exécutée de l’application.'
- - 'Les propriétaires d’organisations ne pouvaient pas définir le niveau d’accès requis pour créer des discussions.'
- - 'Les utilisateurs de discussions étaient dirigés à tort vers les directives communautaires de GitHub.com.'
- - 'Dans certains cas, les utilisateurs étaient informés à tort qu’ils devaient vérifier leur adresse e-mail avant de créer une discussion.'
- - 'Les alertes provenant de l’analyse des secrets pour les clients GitHub Advanced Security étaient absentes de l’interface web et de l’API REST si un administrateur de site n’effectuait pas directement la mise à niveau vers GitHub Enterprise Server 3.4. Les alertes sont maintenant visibles.'
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - Organization owners were unable to set the level of access required to create discussions.
+ - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
+ - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
changes:
- - 'La génération des packs de support est plus rapide grâce à la parallélisation de l’assainissement des journaux. Pour plus d’informations sur les packs de support, consultez « [Fournir des données au support GitHub](/support/contacting-github-support/providing-data-to-github-support) »'
- - 'Les API qui contiennent la route `organization` ou `org` acceptent désormais le slug ou l’ID de l’organisation. Auparavant, les API n’acceptaient que les slugs, ce qui rendait inaccessibles les en-têtes `Link` des points de terminaison GitHub Advanced Security. Pour plus d’informations, consultez « [Organisations](https://docs.github.com/rest/orgs/orgs) » dans la documentation de l’API REST.'
- - "Le journal d’audit de l’entreprise inclut désormais davantage d’événements générés par les utilisateurs, comme `project.create`. L’API REST renvoie également des événements supplémentaires générés par les utilisateurs, comme `repo.create`. Pour plus d’informations, voir «\_[Accéder au journal d’audit de votre entreprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing the-audit-log-for-your-entreprise)\_» et «\_[Utiliser l’API du journal d’audit pour votre entreprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)\_»."
- - 'Dans certains cas, les réplicas du cache pouvaient rejeter certaines opérations Git sur des référentiels récemment mis à jour. Pour plus d’informations sur la mise en cache des référentiels, consultez « [À propos de la mise en cache des référentiels](/admin/enterprise-management/caching-repositories/about-repository-caching) »'
- - 'Vous pouvez désormais configurer la bannière d’annonce globale pour qu’elle soit révocable à l’aide de l’API REST. Pour plus d’informations, consultez « [Personnalisation des messages utilisateur pour votre entreprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner) »'
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+ - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
known_issues:
- - 'Sur une instance fraîchement configurée de {% data variables.product.prodname_ghe_server %} sans aucun utilisateur, un attaquant pourrait créer le premier utilisateur administrateur.'
- - 'Les règles de pare-feu personnalisées sont supprimées pendant le processus de mise à niveau.'
- - 'Les fichiers suivis par Git LFS [chargés via l’interface web](https://github.com/blog/2105-upload-files-to-your-repositories) sont incorrectement ajoutés directement au référentiel.'
- - 'Les questions ne peuvent pas être fermées si elles contiennent un permalien vers un blob dans le même référentiel, où le chemin de fichier du blob est supérieur à 255 caractères.'
- - "Lorsque l’option «\_Les utilisateurs peuvent effectuer des recherches sur GitHub.com\_» est activée avec GitHub Connect, les problèmes dans les référentiels privés et internes ne sont pas inclus dans les résultats de recherche de GitHub.com."
- - 'Le registre npm {% data variables.product.prodname_registry %} ne renvoie plus une valeur de temps dans les réponses de métadonnées. Cela a été fait pour permettre des améliorations substantielles des performances. Nous disposons toujours de toutes les données nécessaires pour renvoyer une valeur de temps dans le cadre de la réponse aux métadonnées et nous recommencerons à renvoyer cette valeur à l’avenir, une fois que nous aurons résolu les problèmes de performance existants.'
- - 'Les limites de ressources spécifiques au traitement des hooks de pré-réception peuvent entraîner l’échec de certains hooks de pré-réception.'
- - 'Les services Actions doivent être redémarrés après avoir restauré une instance à partir d’une sauvegarde effectuée sur un hôte différent.'
- - 'Dans les paramètres d’un référentiel, l’activation de l’option permettant aux utilisateurs ayant un accès en lecture de créer des discussions n’active pas cette fonctionnalité.'
- - 'Dans certains cas, les utilisateurs ne peuvent pas convertir les questions existantes en discussions.'
- - 'Les modèles personnalisés pour l’analyse des secrets ont `.*` comme délimiteur de fin, spécifiquement dans le champ « After secret ». Ce délimiteur provoque des incohérences dans les analyses des secrets entre les référentiels, et vous pourriez remarquer des trous dans l’historique d’un référentiel où aucune recherche n’a été effectuée. Les analyses incrémentielles peuvent également être affectées. Pour éviter les problèmes d’analyse, modifiez la fin du modèle pour supprimer le délimiteur `.*`.'
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+ - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+ - In some cases, users cannot convert existing issues to discussions.
+ - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+ - |
+ After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/fr-FR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/fr-FR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 1e3bbf523a..1193172cdd 100644
--- a/translations/fr-FR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/fr-FR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,18 +1,10 @@
----
-ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: fr-FR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145103710"
----
-Vous pouvez utiliser le `jobs..if` conditionnel pour empêcher l’exécution d’un travail, sauf si une condition est remplie. Vous pouvez utiliser n’importe quel contexte et n’importe quelle expression pris en charge pour créer une condition.
+You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
-{% data reusables.actions.expression-syntax-if %} Pour plus d’informations, consultez « [Expressions](/actions/learn-github-actions/expressions) ».
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
-### Exemple : Exécuter un travail uniquement pour un dépôt spécifique
+### Example: Only run job for specific repository
-Cet exemple utilise `if` pour contrôler le moment où le travail `production-deploy` peut s’exécuter. Il s’exécute uniquement si le dépôt se nomme `octo-repo-prod`, et s’il se trouve dans l’organisation `octo-org`. Sinon, le travail est marqué comme étant _ignoré_.
+This example uses `if` to control when the `production-deploy` job can run. It will only run if the repository is named `octo-repo-prod` and is within the `octo-org` organization. Otherwise, the job will be marked as _skipped_.
```yaml{:copy}
name: example-workflow
diff --git a/translations/fr-FR/data/reusables/actions/reusable-workflows-enterprise-beta.md b/translations/fr-FR/data/reusables/actions/reusable-workflows-enterprise-beta.md
new file mode 100644
index 0000000000..6064e0e17e
--- /dev/null
+++ b/translations/fr-FR/data/reusables/actions/reusable-workflows-enterprise-beta.md
@@ -0,0 +1,17 @@
+{% ifversion ghes = 3.4 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently in beta and subject to change.
+
+{% endnote %}
+
+{% elsif ghae > 3.3 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently unavailable in {% data variables.product.product_name %}, but will be available in a future update.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/fr-FR/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/fr-FR/data/reusables/actions/reusable-workflows-ghes-beta.md
deleted file mode 100644
index 6fb3ef2e4f..0000000000
--- a/translations/fr-FR/data/reusables/actions/reusable-workflows-ghes-beta.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% ifversion ghes = 3.4 %}
-
-{% note %}
-
-**Note**: Reusable workflows are currently in beta and subject to change.
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/fr-FR/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/fr-FR/data/reusables/enterprise-accounts/dormant-user-activity.md
index 80878d1726..24b839f410 100644
--- a/translations/fr-FR/data/reusables/enterprise-accounts/dormant-user-activity.md
+++ b/translations/fr-FR/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
- Starring a repository
- Deleting a repository
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
+- Joining an organization
+
+{% ifversion ghes %}
+A user will also be considered active if their account has been updated by LDAP.
+{% endif %}
diff --git a/translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md b/translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md
index 558a3b591a..b637c27606 100644
--- a/translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md
+++ b/translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md
@@ -1 +1,9 @@
-{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
+---
+ms.openlocfilehash: 484a4230527deebe6f4aeb24ceabdf95eb75b492
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/03/2022
+ms.locfileid: "148191329"
+---
+{% data variables.enterprise.prodname_managed_users_caps %} ne peut pas dupliquer des référentiels depuis l’extérieur de l’entreprise. {% data variables.enterprise.prodname_managed_users_caps %} peut dupliquer des référentiels privés ou internes appartenant à des organisations de l’entreprise dans leur espace de noms de compte d’utilisateur ou d’autres organisations appartenant à l’entreprise, comme spécifié par la stratégie d’entreprise.
diff --git a/translations/fr-FR/data/reusables/repositories/fork-definition-long.md b/translations/fr-FR/data/reusables/repositories/fork-definition-long.md
new file mode 100644
index 0000000000..ea7159d132
--- /dev/null
+++ b/translations/fr-FR/data/reusables/repositories/fork-definition-long.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eb538c8746bf9d5ec4cd0e422e50ccc032309812
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: fr-FR
+ms.lasthandoff: 12/03/2022
+ms.locfileid: "148191363"
+---
+Une duplication est un nouveau référentiel qui partage le code et les paramètres de visibilité avec le référentiel « en amont » d’origine. Les duplications sont souvent utilisées pour itérer sur les idées ou les modifications avant qu’elles ne soient proposées à nouveau au référentiel en amont, par exemple dans des projets open source ou lorsqu’un utilisateur n’a pas d’accès en écriture au référentiel en amont.
diff --git a/translations/fr-FR/data/ui.yml b/translations/fr-FR/data/ui.yml
index 1e8377dd72..29dec0fbef 100644
--- a/translations/fr-FR/data/ui.yml
+++ b/translations/fr-FR/data/ui.yml
@@ -127,7 +127,7 @@ products:
rest:
banner:
api_versioned: The REST API is now versioned.
- api_version_info: For more information, see "About API versioning".
+ api_version_info: For more information, see "About API versioning."
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "About versions of GitHub Docs".
versioning:
about_versions: About REST API versions
diff --git a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
index 312fbe6f89..13fc4f07b3 100644
--- a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
@@ -16,12 +16,12 @@ type: overview
topics:
- Action development
- Fundamentals
-ms.openlocfilehash: ac933a5014750f75373fafa7f8dd52333b79a469
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 1e81bea551ceff1980b0bbe96202f60db0d0e7f2
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147154574'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191951'
---
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
@@ -35,7 +35,7 @@ ms.locfileid: '147154574'
## アクションの種類
-DockerコンテナのアクションとJavaScriptのアクションをビルドできます。 アクションには、アクションの入力、出力、およびメインのエントリポイントを定義するメタデータファイルが必要です。 メタデータ ファイル名は、`action.yml` または `action.yaml` である必要があります。 詳細については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions)」を参照してください。
+Docker コンテナーと JavaScript のアクション、および複合アクションを構築できます。 アクションには、アクションの入力、出力、およびメインのエントリポイントを定義するメタデータファイルが必要です。 メタデータ ファイル名は、`action.yml` または `action.yaml` である必要があります。 詳細については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions)」を参照してください。
| 種類 | オペレーティング システム |
| ---- | ------------------- |
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
index 382e81006b..f54adf093a 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
@@ -94,7 +94,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
shell: bash
```
{% endraw %}
- This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+ This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, adds the action's path to the runner system path (to locate the `goodbye.sh` script during execution), and runs the `goodbye.sh` script.
For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
index 5a1ea071a9..8dcb762313 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
@@ -271,3 +271,10 @@ jobs:
From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+
+## Template repositories for creating JavaScript actions
+
+{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
+
+* [`javascript-action` template repository](https://github.com/actions/javascript-action)
+* [`typescript-action` template repository](https://github.com/actions/typescript-action)
diff --git a/translations/ja-JP/content/actions/learn-github-actions/contexts.md b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
index bdf5bb0bfb..9217298a2a 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/contexts.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
@@ -811,7 +811,7 @@ The `inputs` context contains input properties passed to an action{% ifversion a
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
| Property name | Type | Description |
|---------------|------|-------------|
diff --git a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0d316eca1f..397d51b308 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -88,7 +88,7 @@ In addition to the usage limits, you must ensure that you use {% data variables.
{% ifversion fpt or ghes > 3.3 or ghec %}
## Billing for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
diff --git a/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md b/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
index 2adee6a3f4..1cc0d2d002 100644
--- a/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
---
{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
## Overview
diff --git a/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md b/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
index 8e4adb430f..837875fe9e 100644
--- a/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
@@ -123,7 +123,7 @@ You can use activity types and filters to further control when your workflow wil
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 4969f6b53e..e6e11c2ff5 100644
--- a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -72,7 +72,7 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `on.workflow_call`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
@@ -320,7 +320,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+You can use the `if` conditional to prevent a step from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
@@ -945,7 +945,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `jobs..uses`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
index c4156846ca..298cfe38e0 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
@@ -1,6 +1,6 @@
---
-title: Enabling Server Statistics for your enterprise
-intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.'
+title: 自社でサーバー統計を有効にする
+intro: '{% data variables.product.prodname_server_statistics %} を有効にすることで、{% data variables.product.prodname_ghe_server %} からの独自の集計データを分析し、{% data variables.product.company_short %} 製品の改善に役立てることができます。'
versions:
feature: server-statistics
redirect_from:
@@ -8,23 +8,27 @@ redirect_from:
topics:
- Enterprise
shortTitle: Server Statistics
+ms.openlocfilehash: 125651de793a45240008de34845762e6de637040
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191871'
---
+## {% data variables.product.prodname_server_statistics %}について
-## About {% data variables.product.prodname_server_statistics %}
+{% data variables.product.prodname_server_statistics %} は、{% data variables.location.product_location %} から集計された使用状況データを収集します。これを使うと、組織のニーズをより適切に予測し、チームの作業を把握し、{% data variables.product.prodname_ghe_server %} から得られる価値を確認できます。
-{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
+{% data variables.product.prodname_server_statistics %} によって収集されるのは、リポジトリ、イシュー、pull request、およびその他の機能に関する特定の集計メトリックのみです。 {% data variables.product.prodname_dotcom %} のコンテンツは収集されません (コード、イシュー、コメント、pull request のコンテンツなど)。 詳しい情報については、「[{% data variables.product.prodname_server_statistics %}について](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)」を参照してください。
-{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+{% data variables.product.prodname_server_statistics %}を有効にすると、{% data variables.product.company_short %}の改善にも役立ちます。 お客様から提供された集計データは、お客様が {% data variables.product.prodname_dotcom %} をどのように使っているかを把握し、より適切な情報に基づいた製品の意思決定を行う助けとなり、最終的にはお客様の利益になります。
-By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
+## {% data variables.product.prodname_server_statistics %}の有効化
-## Enabling {% data variables.product.prodname_server_statistics %}
+{% data variables.product.prodname_server_statistics %}を有効にする前に、まず {% data variables.product.prodname_ghe_server %} インスタンスを {% data variables.product.prodname_github_connect %} を使って {% data variables.product.prodname_dotcom_the_website %} に接続する必要があります。 詳細については、「[{% data variables.product.prodname_ghe_cloud %} への {% data variables.product.prodname_ghe_server %} の接続](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。
-Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+{% data variables.product.prodname_server_statistics %} は {% data variables.product.prodname_ghe_server %} からいつでも無効にできます。
-You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time.
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**.
- 
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
+4. [GitHub.com でサーバー統計を共有する] でドロップダウン メニューを選び、 **[有効]** または **[無効]** をクリックします。
+ 
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 98a84270fb..1e67bc7da9 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
+
| Path without subdomain isolation | Path with subdomain isolation |
| --- | --- |
-| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
-| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
-| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
-| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
-| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
-| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
-| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
+| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
+| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
+| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
+| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
+| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
{%- ifversion viewscreen-and-notebooks %}
-| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
-| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
-{%- else %}
-| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
+| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+{%- ifversion ghes < 3.7 %}
+| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
+| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
+{%- ifversion viewscreen-and-notebooks %}
+| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
+{%- endif %}
+{%- ifversion ghes > 3.4 %}
+| Not supported | `https://containers.HOSTNAME/` |
{%- endif %}
-| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
-| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %}
-| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported | `https://containers.HOSTNAME/` |{% endif %}
## Prerequisites
diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
index 6336814ef8..8a9f9b538c 100644
--- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
+++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Actions with MinIO storage
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO storage to store data generated by workflow runs.'
+title: MinIO ストレージで GitHub Actions を有効化する
+intro: '{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効化し、MinIO ストレージを使用してワークフローの実行によって生成されたデータを保存できます。'
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
versions:
ghes: '*'
@@ -14,36 +14,35 @@ redirect_from:
- /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
- /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage
shortTitle: MinIO storage
+ms.openlocfilehash: 3d9c6cfca6b81a66185515c8757cef22290ead30
+ms.sourcegitcommit: 8f1801040a84ca9353899a2d1e6782c702aaed0d
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148166570'
---
+## 前提条件
-## Prerequisites
+{% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。
-Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
+* ワークフローの実行によって生成されるデータを保存するための MinIO バケットを作成します。 MinIO のインストールと構成の詳細については、MinIO ドキュメントの「[MinIO ハイ パフォーマンス オブジェクト ストレージ](https://min.io/docs/minio/container/index.html)」および「[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)」を参照してください。
-* Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
+ アプライアンスでのリソースの競合を回避するために、MinIO を {% data variables.location.product_location %} とは別にホストすることをお勧めします。
- To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.
+ {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %}
- {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
-{% data reusables.actions.enterprise-common-prereqs %}
+## MinIO ストレージで {% data variables.product.prodname_actions %} を有効化する
-## Enabling {% data variables.product.prodname_actions %} with MinIO storage
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
+1. [Artifact & Log Storage]\(成果物とログ ストレージ\) の下で、 **[Amazon S3]** を選択し、ストレージ バケットの詳細を入力します。
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.actions %}
-{% data reusables.actions.enterprise-enable-checkbox %}
-1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
+ * **[AWS Service URL]\(AWS サービス URL\)** : MinIO サービスの URL。 たとえば、`https://my-minio.example:9000` のようにします。
+ * **[AWS S3 Bucket]\(AWS S3 バケット\)** : S3 バケットの名前。
+ * **[AWS S3 Access Key]\(AWS S3 アクセス キー\)** および **[AWS S3 Secret Key]\(AWS S3 秘密鍵\)** : MinIO インスタンスで使用される `MINIO_ACCESS_KEY` および `MINIO_SECRET_KEY`。
- * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`.
- * **AWS S3 Bucket**: The name of your S3 bucket.
- * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance.
+ 
+1. [Artifact & Log Storage]\(成果物とログ ストレージ\) の下で、 **[Force path style]\(パス スタイルの強制\)** を選択します。
- 
-1. Under "Artifact & Log Storage", select **Force path style**.
-
- 
-{% data reusables.enterprise_management_console.test-storage-button %}
-{% data reusables.enterprise_management_console.save-settings %}
+ ![[パス スタイルの強制] のチェックボックス](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
{% data reusables.actions.enterprise-postinstall-nextsteps %}
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 625a34aa98..c01ecca7a2 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
index 59f87dab08..36aa0b71bb 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
@@ -1,7 +1,7 @@
---
-title: About {% data variables.product.prodname_emus %}
+title: '{% data variables.product.prodname_emus %} について'
shortTitle: About managed users
-intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
+intro: 'ID プロバイダーから {% data variables.product.prodname_dotcom %} 上のエンタープライズ メンバーの ID とアクセスを一元管理することができます。'
redirect_from:
- /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
- /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
@@ -17,48 +17,53 @@ topics:
- Enterprise
- SSO
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 72d8263029317783e60d8f81f45edc3dbb8b1c8b
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180014'
---
+## {% data variables.product.prodname_emus %} について
-## About {% data variables.product.prodname_emus %}
+{% data variables.product.prodname_emus %} を使用すると、ID プロバイダー (IdP) を使用して Enterprise メンバーのユーザー アカウントを制御できます。 IdP で {% data variables.product.prodname_emu_idp_application %} アプリケーションに割り当てられたユーザーは、{% data variables.product.prodname_dotcom %} の新しいユーザー アカウントとしてプロビジョニングされ、Enterprise に追加されます。 IdP からユーザー アカウントのユーザー名、プロファイル データ、チーム メンバーシップ、リポジトリへのアクセスを制御します。
-With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP.
-
-In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+IdP では、各{% data variables.enterprise.prodname_managed_user %}に、ユーザー、Enterprise 所有者、または課金マネージャーのロールを付与できます。 {% data variables.enterprise.prodname_managed_users_caps %}は、Enterprise 内の Organization を所有でき、他の{% data variables.enterprise.prodname_managed_users %}を Organization とその中の Team に追加できます。 詳細については、「[Enterprise におけるロール](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)」および「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。
{% ifversion oidc-for-emu %}
-{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
+{% data reusables.enterprise-accounts.emu-cap-validates %}詳細については、「[IdP の条件付きアクセス ポリシー](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)」を参照してください。
{% endif %}
-You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)."
+{% data variables.enterprise.prodname_managed_users %}に、Enterprise 内のリポジトリへのアクセス権と、そこに投稿する機能を付与できますが、{% data variables.enterprise.prodname_managed_users %}では、パブリック コンテンツを作成したり、残りの {% data variables.product.prodname_dotcom %} で他のユーザー、Organization、Enterprise と共同作業を行ったりすることはできません。 詳しい情報については、「[{% data variables.enterprise.prodname_managed_users %}の機能と制限](#abilities-and-restrictions-of-enterprise-managed-users)」を参照してください。
-The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+Enterprise の{% data variables.enterprise.prodname_managed_users %}のユーザー名とそのプロファイル情報 (表示名やメール アドレスなど) は、IdP によって設定され、ユーザー自身が変更することはできません。 詳細については、「[ユーザー名とプロファイル情報](#usernames-and-profile-information)」を参照してください。
-Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)."
+Enterprise 所有者は、{% data variables.product.prodname_dotcom %} に対する{% data variables.enterprise.prodname_managed_users %}のすべてのアクションを監査できます。 詳細については、「[エンタープライズの監査ログ イベント](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)」を参照してください。
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
+{% data variables.product.prodname_emus %} を使用するには、{% data variables.product.prodname_emus %} を有効にした別の種類の Enterprise アカウントが必要です。 このアカウントの作成の詳細については、「[Managed User を含む Enterprise について](#about-enterprises-with-managed-users)」を参照してください。
{% note %}
-**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right 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)."
+**注:** {% data variables.product.prodname_ghe_cloud %} を使った ID とアクセスの管理には複数のオプションがあるので、{% data variables.product.prodname_emus %} はすべてのお客様にとって最適なソリューションではありません。 {% data variables.product.prodname_emus %} がお客様の企業に適しているかどうかについては、「[企業の認証について](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)」を参照してください。
{% endnote %}
-## About organization membership management
+## Organization メンバーシップの管理について
-Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+Organization メンバーシップは、手動で管理することも、IdP グループを使用して自動的に更新することもできます。 IdP を使用して Organization メンバーシップを管理するには、メンバーを IdP グループに追加し、IdP グループを Organization 内の Team に接続する必要があります。 Organization および Team のメンバーシップの管理に関する詳しい情報については、「[ID プロバイダー グループによる Team メンバーシップの管理](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)」を参照してください。
-The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization.
+Enterprise によって所有されている Organization にメンバーを追加する方法によって、Organization からメンバーを削除する方法が決定されます。
-- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
-- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
+- メンバーを手動で Organization に追加した場合、手動で削除する必要があります。 IdP 上の {% data variables.product.prodname_emu_idp_application %} アプリケーションからユーザーの割り当て解除を行うと、ユーザーは停止されますが、Organization から削除されません。
+- Organization 内の 1 つ以上の Team にマップされた IdP グループに追加されたために、ユーザーが Organization のメンバーになった場合、Organization に関連付けられている "すべて" のマップされた IdP グループからユーザーを削除すると、ユーザーは Organization から削除されます。
-To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
+メンバーが Organization に追加された方法を確認するには、メンバー リストを種類でフィルター処理できます。 詳細については、「[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)」 (Enterprise のメンバーを表示する) を参照してください。
-## Identity provider support
+## ID プロバイダーのサポート
-{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
+{% data variables.product.prodname_emus %} は、以下の IdP{% ifversion oidc-for-emu %} と認証方法をサポートしています。
| | SAML | OIDC |
|----------------------------------|-----------------------------------------------|-----------------------------------------------|
@@ -70,36 +75,36 @@ To discover how a member was added to an organization, you can filter the member
{% endif %}
-## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}
+## {% data variables.enterprise.prodname_managed_users %}の機能と制限
-{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests.
+{% data variables.enterprise.prodname_managed_users_caps %}で投稿できるのは、その Enterprise 内のプライベートおよび内部リポジトリと、そのユーザー アカウントによって所有されているプライベート リポジトリのみです。 {% data variables.enterprise.prodname_managed_users_caps %}には、より広範な {% data variables.product.prodname_dotcom %} コミュニティへの読み取り専用アクセス権が必要です。 ユーザーとコンテンツに対するこれらの可視性とアクセスの制限は、API 要求を含むすべての要求に適用されます。
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises.
-* Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}.
-* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
-* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate.
-* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
-* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories.
+* {% data variables.enterprise.prodname_managed_users_caps %}を Enterprise 外部の Organization またはリポジトリに招待することも、{% data variables.enterprise.prodname_managed_users %}を他の Enterprise に招待することもできません。
+* 外部のコラボレーターは、{% data variables.product.prodname_emus %} ではサポートされていません。
+* {% data variables.enterprise.prodname_managed_users_caps %}では、Enterprise 外部のリポジトリでの Issue または pull request の作成、Enterprise 外部のリポジトリへのリアクションの追加、Enterprise 外部のリポジトリに対する Star、Watch または Fork 操作を行うことはできません。
+* {% data variables.enterprise.prodname_managed_users_caps %}で {% data variables.product.prodname_dotcom_the_website %} のすべてのパブリック リポジトリを表示することはできますが、Enterprise 外部のリポジトリにコードをプッシュすることはできません。
+* {% data variables.enterprise.prodname_managed_users_caps %}と作成されたコンテンツは、その Enterprise の他のメンバーにのみ表示されます。
+* {% data variables.enterprise.prodname_managed_users_caps %}では、Enterprise 外部のユーザーをフォローできません。
+* {% data variables.enterprise.prodname_managed_users_caps %}では、gists を作成したり、gists に対してコメントしたりすることはできません。
+* {% data variables.enterprise.prodname_managed_users_caps %}では、{% data variables.product.prodname_actions %} のスターター ワークフローを作成できません。
+* {% data variables.enterprise.prodname_managed_users_caps %}では、そのユーザー アカウントに {% data variables.product.prodname_github_apps %} をインストールできません。
+* 他の {% data variables.product.prodname_dotcom %} ユーザーは、{% data variables.enterprise.prodname_managed_user %}を表示またはメンションしたり、共同作業に招待したりすることはできません。
+* ユーザー アカウントによって所有されるリポジトリを{% data variables.enterprise.prodname_managed_users %}で作成できるかどうかを選ぶことができます。 詳細については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)」を参照してください。
+* ユーザー アカウントによって所有されるリポジトリの作成を{% data variables.enterprise.prodname_managed_users %}に許可した場合、所有できるのはプライベート リポジトリのみであり、他のエンタープライズ メンバーを招待して共同作業を行うことができるのは、ユーザー所有のリポジトリのみです。
* {% data reusables.enterprise-accounts.emu-forks %}
-* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings.
-* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
+* {% data variables.enterprise.prodname_emu_enterprise %} が所有する Organization では、Organization および Enterprise リポジトリの可視性の設定に応じて、プライベートおよび内部リポジトリのみを作成できます。
+* {% data variables.enterprise.prodname_managed_users_caps %}は、{% data variables.product.prodname_pages %} の使用が制限されます。 詳細については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)」を参照してください。
* {% data reusables.copilot.emus-cannot-use-copilot %}
-## Getting started with {% data variables.product.prodname_emus %}
+## {% data variables.product.prodname_emus %} の概要
-Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps.
+お客様の開発者が {% data variables.product.prodname_ghe_cloud %} と {% data variables.product.prodname_emus %} を使用できるようにするには、お客様が一連の構成手順を実行する必要があります。
-1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+1. {% data variables.product.prodname_emus %} を使用するには、{% data variables.product.prodname_emus %} を有効にした別の種類の Enterprise アカウントが必要です。 {% data variables.product.prodname_emus %} を試用するか、既存の Enterprise から移行するためのオプションについて検討するには、[{% data variables.product.prodname_dotcom %} の営業チーム](https://enterprise.github.com/contact)にお問い合わせください。
- Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+ GitHub セールス チームの担当者が、新しい {% data variables.enterprise.prodname_emu_enterprise %} を作成するために協力します。 Enterprise を設定するユーザーのメール アドレスと、Enterprise メンバーのユーザー名のサフィックスとして使用されるショートコードを指定する必要があります。 {% data reusables.enterprise-accounts.emu-shortcode %} 詳細については、「[ユーザー名とプロファイル情報](#usernames-and-profile-information)」を参照してください。
-2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`.
+2. Enterprise を作成すると、{% data variables.product.prodname_dotcom %} からメールが届き、Enterprise のセットアップ ユーザーのパスワードを選択するよう求められます。このユーザーは、Enterprise の最初の所有者になります。 パスワードを設定する際は、Incognito ウィンドウまたはプライベート ブラウズ ウィンドウを使用します。 セットアップ ユーザーは、エンタープライズのシングル サインオンと SCIM プロビジョニング統合を構成するためにのみ使用されます。 SSO が正常に有効になると、エンタープライズ アカウントを管理するためのアクセス権はなくなります。 セットアップ ユーザーのユーザー名は、Enterprise のショートコードにサフィックス `_admin` が付きます。
{% note %}
@@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w
{% endnote %}
-3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+3. セットアップ ユーザーとしたログインしたら、2 要素認証を有効にすることをお勧めします。 詳細については、「[2 要素認証の構成](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)」を参照してください。
-1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). We recommend OIDC, which includes support for Conditional Access Policies (CAP). If you require multiple enterprises with {% data variables.enterprise.prodname_managed_users %} provisioned from one tenant, you must use SAML for each enterprise after the first. If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %}
+1. まず、{% ifversion oidc-for-emu %}メンバーが認証する方法を構成します。 Azure Active Directory を ID プロバイダーとして使っている場合、OpenID Connect (OIDC) と Security Assertion Markup Language (SAML) のいずれかを選択できます。 条件付きアクセス ポリシー (CAP) のサポートを含む OIDC をお勧めします。 {% data variables.enterprise.prodname_managed_users %} が 1 つのテナントからプロビジョニングされた複数のエンタープライズが必要な場合は、最初のエンタープライズ以降、それぞれに SAML を使用する必要があります。 ID プロバイダーとして Okta を使っている場合、SAML を使ってメンバーを認証することができます。{% else %}エンタープライズ用に SAML SSO を構成します。 詳細については、「[エンタープライズ マネージド ユーザーの SAML シングル サインオンの構成](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)」を参照してください。{% endif %}
{% ifversion oidc-for-emu %}
- To get started, read the guide for your chosen authentication method.
+ まず、選択した認証方法のガイドを参照してください。
- - "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
- - "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+ - 「[エンタープライズ マネージド ユーザーの OIDC の構成](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)」
+ - 「[エンタープライズ マネージド ユーザーの SAML シングル サインオンの構成](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)」
{% endif %}
-4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+4. SSO を構成したら、SCIM のプロビジョニングを構成できます。 SCIM は、ID プロバイダーを使って {% data variables.product.prodname_dotcom_the_website %} に{% data variables.enterprise.prodname_managed_users %}を作成する方法です。 SCIM のプロビジョニングを構成する場合の詳細については、「[エンタープライズ マネージド ユーザーの SCIM プロビジョニングの構成](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)」を参照してください。
-5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
+5. 認証とプロビジョニングが構成されたら、IdP グループを Team と同期することで、{% data variables.enterprise.prodname_managed_users %}の Organization メンバーシップの管理を開始できます。 詳細については、「[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)」 (ID プロバイダー グループを使用して Team のメンバーシップを管理する) を参照してください。
-If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)."
+Enterprise のメンバーが 1 つのワークステーションを使って、{% data variables.enterprise.prodname_managed_user %}と個人アカウントの両方から、{% data variables.location.product_location %} のリポジトリに投稿する必要がある場合は、サポートを提供できます。 詳しくは、「[{% data variables.product.prodname_dotcom_the_website %} で複数のユーザー アカウントを持つ開発者をサポートする](#supporting-developers-with-multiple-user-accounts-on-githubcom)」をご覧ください。
-## Authenticating as a {% data variables.enterprise.prodname_managed_user %}
+## {% data variables.enterprise.prodname_managed_user %}として認証を行う
-{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}.
+{% data variables.enterprise.prodname_managed_users_caps %}は、ID プロバイダーを介して認証を行う必要があります。 {% data variables.enterprise.prodname_managed_user %}は、認証を行うために、IdP アプリケーション ポータルにアクセスするか、{% data variables.product.prodname_dotcom_the_website %} のログイン ページを使用できます。
-By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
+既定では、認証されていないユーザーが {% data variables.product.prodname_emus %} を使用する Enterprise にアクセスしようとすると、{% data variables.product.company_short %} によって 404 エラーが表示されます。 Enterprise 所有者は、必要に応じて、404 の代わりにシングル サインオン (SSO) への自動リダイレクトを有効にすることができます。 詳細については、「[エンタープライズでのセキュリティ設定のポリシーの適用](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)」を参照してください。
-{% 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 %} 詳細については、「[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)」 (Enterprise の復旧コードの管理) を参照してください。
-### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %}
+### {% data variables.product.prodname_dotcom_the_website %} を介して{% data variables.enterprise.prodname_managed_user %}として認証を行う
-1. Navigate to [https://github.com/login](https://github.com/login).
-1. In the "Username or email address" text box, enter your username including the underscore and short code.
- 
- When the form recognizes your username, the form will update. You do not need to enter your password on this form.
-1. To continue to your identity provider, click **Sign in with your identity provider**.
- 
+1. [https://github.com/login](https://github.com/login) に移動します。
+1. [Username or email address] テキスト ボックスに、アンダースコアとショートコードを含むユーザー名を入力します。
+  このフォームでユーザー名が認識されると、フォームは更新されます。 このフォームでパスワードを入力する必要はありません。
+1. ID プロバイダーに進むには、 **[Sign in with your identity provider]** をクリックします。
+ ![[Sign in with your identity provider] ボタンを示すスクリーンショット](/assets/images/help/enterprises/emu-login-submit.png)
-## Usernames and profile information
+## ユーザー名とプロファイル情報
-{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+{% data variables.product.product_name %} は、IdP から提供された識別子を正規化することにより、各自のユーザー名を自動的に作成します。 詳細については、「[外部認証におけるユーザー名の考慮事項](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)」を参照してください。
-A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)."
+IdP から提供された識別子の一意の部分が正規化中に削除されると、ユーザーをプロビジョニングするときに競合が発生する場合があります。 ユーザー名の競合が原因でユーザーをプロビジョニングできない場合は、IdP によって提供されるユーザー名を変更する必要があります。 詳しい情報については、「[ユーザー名の問題の解決](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)」を参照してください。
{% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %}
-The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
+{% data variables.enterprise.prodname_managed_user %}のプロファイル名とメール アドレスも IdP によって提供されます。 {% data variables.enterprise.prodname_managed_users_caps %}では、{% data variables.product.prodname_dotcom %} 上のプロファイル名またはメール アドレスを変更できません。IdP が提供できるメール アドレスは 1 つのみです。
-## Supporting developers with multiple user accounts on {% data variables.location.product_location %}
+## {% data variables.location.product_location %} で複数のユーザー アカウントを持つ開発者をサポートする
-People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work.
+Team のユーザーは、{% data variables.enterprise.prodname_emu_enterprise %} の外部にある {% data variables.location.product_location %} のリソースに投稿することが必要になる場合があります。 たとえば、会社のオープンソース プロジェクト用に別のエンタープライズを保持したい場合があります。 {% data variables.enterprise.prodname_managed_user %}ではパブリック リソースに投稿できないため、ユーザーはこの作業のために個別の個人アカウントを維持する必要があります。
-People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
+1 つのワークステーションを使用して {% data variables.location.product_location %} で 2 つのユーザー アカウントから投稿する必要があるユーザーは、Git を設定してプロセスを簡略化できます。 詳しくは、「[複数のアカウントの管理](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)」をご覧ください。
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
index 33c6b16923..dcb2a7541d 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
@@ -1,7 +1,7 @@
---
-title: About support for your IdP's Conditional Access Policy
+title: IdP の条件付きアクセス ポリシーのサポートについて
shortTitle: Conditional access policy
-intro: 'When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} can validate access to your enterprise and its resources using your IdP''s Conditional Access Policy (CAP).'
+intro: 'Enterprise が OIDC SSO を使っている場合、{% data variables.product.prodname_dotcom %} は、お客様の IdP の条件付きアクセス ポリシー (CAP) を使って、Enterprise とそのリソースへのアクセスを検証できます。'
product: '{% data reusables.gated-features.emus %}'
versions:
feature: oidc-for-emu
@@ -10,35 +10,40 @@ topics:
- Authentication
- Enterprise
- SSO
+ms.openlocfilehash: aed7008bd008ccfd6303ccbb36f4d6f3bd7002ca
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148179998'
---
-
{% data reusables.enterprise-accounts.azure-emu-support-oidc %}
-## About support for Conditional Access Policies
+## 条件付きアクセス ポリシーのサポートについて
{% data reusables.enterprise-accounts.emu-cap-validates %}
-{% data variables.product.product_name %} supports CAP for any {% data variables.enterprise.prodname_emu_enterprise %} where OIDC SSO is enabled. {% data variables.product.product_name %} enforces your IdP's IP conditions but cannot enforce your device compliance conditions. Enterprise owners can choose to use this IP allow list configuration instead of {% data variables.product.product_name %}'s IP allow list, and can do so once OIDC SSO is configured. For more information about IP allow lists, see "[Restricting network traffic with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."
+{% data variables.product.product_name %} では、OIDC SSO が有効になっている {% data variables.enterprise.prodname_emu_enterprise %} の CAP がサポートされます。 {% data variables.product.product_name %} によって IdP の IP 条件が適用されますが、デバイスのコンプライアンス条件は適用できません。 Enterprise 所有者は、{% data variables.product.product_name %} の IP 許可リストではなく、この IP 許可リスト構成を使用することを選ぶことができ、OIDC SSO が構成されたらそれを行うことができます。 IP 許可リストについて詳しくは、「[IP 許可リストを使用したネットワーク トラフィックの制限](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)」および「[Organization の許可された IP アドレスの管理](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)」をご覧ください。
-For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."
+OIDC と {% data variables.product.prodname_emus %} の使用の詳細については、「[エンタープライズ マネージド ユーザー向けの OIDC の構成](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)」と「[SAML から OIDC への移行](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)」を参照してください。
-## Considerations for integrations and automations
+## 統合と自動化に関する考慮事項
-{% data variables.product.prodname_dotcom %} sends the originating IP address to your IdP for validation against your CAP. To make sure actions and apps are not blocked by your IdP's CAP, you will need to make changes to your configuration.
+CAP に対する検証のために、{% data variables.product.prodname_dotcom %} から IdP に送信元の IP アドレスが送信されます。 アクションとアプリが IdP の CAP によってブロックされないようにするには、構成を変更する必要があります。
{% data reusables.enterprise-accounts.oidc-gei-warning %}
### {% data variables.product.prodname_actions %}
-Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP.
+{% data variables.product.pat_generic %} を使用するアクションは、IdP の CAP によってブロックされる可能性が高いです。 {% data variables.product.pat_generic %}は、サービス アカウントを使って作成し、IdP の CAP で IP 制御の対象外とすることをお勧めします。
-If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)."
+サービス アカウントを使用できない場合、{% data variables.product.pat_generic %}を使うアクションのブロックを解除する別のオプションとして、{% data variables.product.prodname_actions %} で使われる IP 範囲を許可することができます。 詳細については、「[GitHub の IP アドレスについて](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)」を参照してください。
-### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+### {% data variables.product.prodname_github_apps %} と {% data variables.product.prodname_oauth_apps %}
-When {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} make requests on a member's behalf, {% data variables.product.prodname_dotcom %} will send the IP address of the app's server to your IdP for validation. If the IP address of the app's server is not validated by your IdP's CAP, the request will fail.
+{% data variables.product.prodname_github_apps %} と {% data variables.product.prodname_oauth_apps %} がメンバーの代理で要求を行うと、検証のために {% data variables.product.prodname_dotcom %} から IdP にアプリのサーバーの IP アドレスが送信されます。 アプリのサーバーの IP アドレスが IdP の CAP によって検証されない場合、要求は失敗します。
-You can contact the owners of the apps you want to use, ask for their IP ranges, and configure your IdP's CAP to allow access from those IP ranges. If you're unable to contact the owners, you can review your IdP sign-in logs to review the IP addresses seen in the requests, then allow-list those addresses.
+使いたいアプリの所有者に連絡し、その IP の範囲を問い合わせて、その IP の範囲からのアクセスを許可するように IdP の CAP を構成することができます。 所有者に連絡できない場合は、IdP のサインイン ログを確認し、要求に出現する IP アドレスを確認し、それらのアドレスを許可リストに登録できます。
-If you do not wish to allow all of the IP ranges for all of your enterprise's apps, you can also exempt installed {% data variables.product.prodname_github_apps %} and authorized {% data variables.product.prodname_oauth_apps %} from the IdP allow list. If you do so, these apps will continue working regardless of the originating IP address. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)."
+すべてのエンタープライズのアプリに対してすべての IP 範囲を許可しない場合は、インストールされている {% data variables.product.prodname_github_apps %} と承認された {% data variables.product.prodname_oauth_apps %} を IdP 許可リストから除外することもできます。 その場合、これらのアプリは発信元 IP アドレスに関係なく、動作し続けます。 詳細については、「[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)」 (Enterprise でセキュリティ設定のポリシーを適用する) を参照してください。
diff --git a/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
index a7060df4d0..59b71c57fd 100644
--- a/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
+++ b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Packages with Azure Blob Storage
-intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.'
+title: Azure Blob Storage で GitHub Packages を有効化する
+intro: 'Azure Blob Storage を外部ストレージとして {% data variables.product.prodname_registry %} を設定します。'
versions:
ghes: '*'
type: tutorial
@@ -9,42 +9,44 @@ topics:
- Packages
- Storage
shortTitle: Enable Packages with Azure
+ms.openlocfilehash: b851f698baba60323cbaaa69122cacdc92ec83c2
+ms.sourcegitcommit: 3ece72cf2d90987575d369c44101d19d3bb06f76
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190388'
---
-
{% warning %}
-**Warnings:**
-- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
-- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
-- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
+**警告:**
+- {% data variables.product.company_short %} は特定のオブジェクトのアクセス許可または追加のアクセス制御リスト (ACL) をストレージバケット設定に適用しないため、ストレージバケットに必要な制限付きアクセスポリシーを設定することが重要です。 たとえば、バケットを公開すると、バケット内のデータにパブリックなインターネットからアクセスできるようになります。
+- {% data variables.product.prodname_actions %} ストレージに使用するバケットとは別に、{% data variables.product.prodname_registry %} 専用のバケットを使用することをお勧めします。
+- 今後使用予定のバケットを忘れずに設定するようにしてください。 {% data variables.product.prodname_registry %} の使用開始後にストレージを変更することはお勧めしません。
{% endwarning %}
-## Prerequisites
+## 前提条件
-Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/).
+{% data variables.location.product_location_enterprise %}で {% data variables.product.prodname_registry %} を有効にして設定する前に、Azure Blob Storage バケットを準備する必要があります。 Azure Blob Storage バケットを準備するために、公式 [Azure Blob Storage ドキュメント サイト](https://docs.microsoft.com/en-us/azure/storage/blobs/)で公式 Azure Blob Storage ドキュメントを参照することをお勧めします。
-## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage
+## Azure Blob Storage で {% data variables.product.prodname_registry %} を有効化する
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_site_admin_settings.packages-tab %}
-{% data reusables.package_registry.enable-enterprise-github-packages %}
-1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %}
+1. [Packages Storage] で **[Azure Blob Storage]** を選択し、パッケージストレージバケットの Azure コンテナ名と接続文字列型を入力します。
- - You must create a storage container prior to setting the container name and connection string.
+ - コンテナー名と接続文字列を設定する前に、ストレージ コンテナーを作成する必要があります。
- 
+ 
{% note %}
- **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
- Usage of a SAS Token or SAS URL as connection string is not currently supported.
+ **注:** Azure ストレージ アカウントの [アクセス キー] メニューに移動すると、Azure の接続文字列を見つけることができます。
+ 現在、接続文字列としての SAS トークンまたは SAS URL の使用はサポートされていません。
{% endnote %}
{% data reusables.enterprise_management_console.save-settings %}
-## Next steps
+## 次の手順
{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 991873cdca..041431c2e8 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -56,7 +56,7 @@ You can enforce policies to control how members of your enterprise on {% data va
Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% ifversion ghes or ghae %}
@@ -166,7 +166,7 @@ Across all organizations owned by your enterprise, you can set the default branc
Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 571de5c750..fd766e780d 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -1,6 +1,6 @@
---
-title: About billing for GitHub Actions
-intro: 'If you want to use {% data variables.product.prodname_actions %} beyond the storage or minutes included in your account, you will be billed for additional usage.'
+title: GitHub Actions の課金について
+intro: 'アカウントに含まれるストレージや利用時間 (分) を超えて{% data variables.product.prodname_actions %}を使用したい場合は、追加の使用分が請求されます。'
miniTocMaxHeadingLevel: 3
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
@@ -13,103 +13,104 @@ topics:
- Actions
- Spending limits
shortTitle: Billing for GitHub Actions
+ms.openlocfilehash: fcc8f84b8a11b214ca66e8a3851a1afc9df6213a
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191887'
---
-## About billing for {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %} の課金について
{% data reusables.actions.actions-billing %}
-{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
+{% data reusables.actions.actions-spending-limit-brief %}詳細については、「[使用制限について](#about-spending-limits)」を参照してください。
-{% ifversion ghec %}
-If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% ifversion ghec %}Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合は、ご自身の Azure サブスクリプション ID をエンタープライズ アカウントに接続して、ご自身のアカウントに含まれている金額を超える {% data variables.product.prodname_actions %} の使用を有効にして支払うことができます。 詳細については、「[Azure サブスクリプションを Enterprise に接続する](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。
{% endif %}
-Minutes reset every month, while storage usage does not.
+時間 (分) は毎月リセットされますが、ストレージはリセットされません。
-### Included storage and minutes
+### 含まれるストレージと分
-{% ifversion actions-hosted-runners %}
-{% note %}
+{% ifversion actions-hosted-runners %} {% note %}
-**Note**: Entitlement minutes cannot be used for Windows and Ubuntu runners over 2-cores. These runners will always be charged for, including in public repos. For more information, see "[Per-minute rates for runners](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)."
+**注**: 2 コアを超える Windows ランナーおよび Ubuntu ランナーには、エンタイトルメント (分) を使用できません。 これらのランナーは、パブリック リポジトリを含め、常に課金されます。 詳しくは、[ランナーの 1 分あたりの料金](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)に関するページを参照してください。
-{% endnote %}
-{% endif %}
+{% endnote %} {% endif %}
-|Product | Storage | Minutes (per month)|
+|製品 | Storage | 分 (月あたり)|
|------- | ------- | ---------|
| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
| {% data variables.product.prodname_pro %} | 1 GB | 3,000 |
-| {% data variables.product.prodname_free_team %} for organizations | 500 MB | 2,000 |
+| 組織の {% data variables.product.prodname_free_team %} | 500 MB | 2,000 |
| {% data variables.product.prodname_team %} | 2 GB | 3,000 |
| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 |
-Jobs that run on Windows and macOS runners that {% data variables.product.prodname_dotcom %} hosts consume minutes at 2 and 10 times the rate that jobs on Linux runners consume. For example, using 1,000 Windows minutes would consume 2,000 of the minutes included in your account. Using 1,000 macOS minutes, would consume 10,000 minutes included in your account.
+{% data variables.product.prodname_dotcom %}がホストするWindows及びmacOSのランナー上で実行されるジョブは、Linuxのランナー上のジョブの消費に対して2倍及び10倍の分を消費します。 たとえば、Windows で 1,000 分使用すると、アカウントに含まれている 2,000 分が消費されます。 macOS で 1,000 分使用すると、アカウントに含まれている 10,000 分が消費されます。
-### Minute multipliers
+### 分の倍率
-| Operating system | Minute multiplier |
+| オペレーティング システム | 分の倍率 |
|------- | ---------|
| Linux | 1 |
| macOS| 10 |
| Windows | 2 |
-The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+リポジトリが使用するストレージは、{% data variables.product.prodname_actions %}の成果物と{% data variables.product.prodname_registry %}の消費の合計のストレージです。 ストレージのコストは、お客様のアカウントで所有しているすべてのリポジトリの合計使用量です。 {% data variables.product.prodname_registry %} の価格について詳しくは、「[{% data variables.product.prodname_registry %} の課金について](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。
- If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
+ アカウントによる使用がこれらの制限を超え、使用制限を 0 米国ドルより上に設定している場合、日ごとにストレージの GB あたり 0.008 米国ドル、そして {% data variables.product.prodname_dotcom %} ホステッド ランナーで使用されるオペレーティング システムに応じた使用量を分単位で支払うことになります。 {% data variables.product.prodname_dotcom %} は、各ジョブが使った分と分未満をもっとも近い分に切り上げます。
{% note %}
-**Note:** Minute multipliers do not apply to the per-minute rates shown below.
+**注:** 分の乗数は、以下に示す分あたりの料金には適用されません。
{% endnote %}
-### Per-minute rates
+### 分あたりの料金
-{% data reusables.billing.billing-standard-runners %}
-{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
+{% data reusables.billing.billing-standard-runners %} {%- ifversion actions-hosted-runners %} {% data reusables.billing.billing-hosted-runners %} {%- endif %}
-- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
-- {% data reusables.user-settings.context_switcher %}
-{% ifversion actions-hosted-runners %}
-- For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
-- Entitlement minutes cannot be used for {% data variables.actions.hosted_runner %}s.
-- The {% data variables.actions.hosted_runner %}s are not free for public repositories.
+- アカウントもしくはOrganization内のすべてのリポジトリにわたって同時に実行できるジョブ数は、あなたのGitHubのプランによります。 詳細について、{% data variables.product.prodname_dotcom %} ホステッド ランナーに関しては「[使用制限と課金](/actions/reference/usage-limits-billing-and-administration)」を、セルフホステッド ランナーの使用制限に関しては「[セルフホステッド ランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)」を参照してください。
+- {% data reusables.user-settings.context_switcher %} {% ifversion actions-hosted-runners %}
+- {% data variables.actions.hosted_runner %} の場合、パブリック静的 IP アドレスを {% data variables.actions.hosted_runner %} に割り当てる構成に追加のコストは発生しません。 {% data variables.actions.hosted_runner %} について詳しくは、「[{% data variables.actions.hosted_runner %} の使用](/actions/using-github-hosted-runners/using-larger-runners)」を参照してください。
+- {% data variables.actions.hosted_runner %} にはエンタイトルメント (分) を使用できません。
+- {% data variables.actions.hosted_runner %} は、パブリック リポジトリについては無料ではありません。
{% endif %}
-## Calculating minute and storage spending
+## 利用時間 (分) とストレージ消費量の計算
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_actions %}
-At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account.
+月末に、{% data variables.product.prodname_dotcom %}はアカウントに含まれている量に対して使用された分とストレージのコストを計算します。
-### Sample minutes cost calculation
+### 分のコスト計算例
-For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
+たとえば、Organizationが{% data variables.product.prodname_team %}を使用しており、使用量に制限をしていない場合、5,000分を使用すればジョブを実行しているオペレーティングシステムによって、合計でストレージと分は56米ドルの超過コストになるかもしれません。
-- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
- - 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
- - 2,000 Windows minutes at $0.016 USD per minute = $32 USD.
+- 5,000 (3,000 Linux と 2,000 Windows) 分 = 56米ドル (24米ドル + 32米ドル)。
+ - 単価 0.008米ドル で 3,000 Linux 分 = 24米ドル。
+ - 単価 0.016米ドル で 2,000 Windows 分 = 32米ドル。
-{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month.
+{% data variables.product.prodname_dotcom %} 毎月の利用状況は、その月の時間あたりの利用状況に基づいて計算されます。
-### Sample storage cost calculation
+### ストレージのコスト計算例
-For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be:
+たとえば、3 月の 10 日間に 3 GB のストレージを使用し、3 月の 21 日間に 12 GB 使用した場合、ストレージの使用量は次のようになります。
-- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours
-- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours
-- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours
-- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months
+- 3 GB x 10日 x (1日24 時間) = 720 GB時間
+- 12 GB x 21日 x (1日24 時間) = 6,048 GB時間
+- 720 GB時間 + 6,048 GB時間 = 6,768 GB時間
+- 6,768 GB時間 / (月あたり744時間) = 9.0967 GB月
-At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
+月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 そのため、3 月のストレージ使用量は 9.097 GB になります。
-Your {% data variables.product.prodname_actions %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
+{% data variables.product.prodname_actions %} の利用については、アカウントの既存の請求日、支払い方法、領収書が共有されます。 {% data reusables.dotcom_billing.view-all-subscriptions %}
-## About spending limits
+## 利用上限について
{% data reusables.actions.actions-spending-limit-detailed %}
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+アカウントの使用制限の管理と変更については、「[{% data variables.product.prodname_actions %} の使用制限の管理](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)」を参照してください。
{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
diff --git a/translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md b/translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
index d6daeb7614..d3e675ef7a 100644
--- a/translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
+++ b/translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
@@ -1,6 +1,6 @@
---
-title: Managing privately reported security vulnerabilities
-intro: Repository maintainers can manage security vulnerabilities that have been privately reported to them by security reseachers for repositories where private vulnerability reporting is enabled.
+title: 非公開で報告されたセキュリティの脆弱性の管理
+intro: リポジトリの保守担当者は、プライベート脆弱性レポートが有効になっているリポジトリのセキュリティ リサーチャーによって非公開で報告されたセキュリティ脆弱性を管理できます。
permissions: 'Anyone with admin permissions to a repository can see, review, and manage privately-reported vulnerabilities for the repository.'
versions:
fpt: '*'
@@ -11,35 +11,38 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Manage vulnerability reports
+ms.openlocfilehash: 942533788dc6ad9280ddc023f583462c7a0ff7f8
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160292'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## セキュリティの脆弱性を非公開で報告する方法について
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to you using a simple form.
+プライベート脆弱性レポートを使用すると、セキュリティ リサーチャーは簡単なフォームを使用して脆弱性を直接報告できます。
-When a security researcher reports a vulnerability privately, you are notified and can choose to either accept it, ask more questions, or reject it. If you accept the report, you're ready to collaborate on a fix for the vulnerability in private with the security researcher.
+セキュリティ リサーチャーによって脆弱性が非公開で報告されると、通知を受け取り、承諾するか、さらに質問するか、拒否するかを選択できます。 レポートを承諾した場合は、セキュリティ リサーチャーと非公開で脆弱性の修正を共同で行う準備が整います。
-## Managing security vulnerabilities that are privately reported
+## 非公開で報告されるセキュリティの脆弱性の管理
-{% data variables.product.prodname_dotcom %} notifies repository maintainers when security researchers privately report vulnerabilities in their repository, and sends notifications if maintainers watch the repository or if they have notifications enabled for the repository. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
+{% data variables.product.prodname_dotcom %} は、セキュリティ リサーチャーがリポジトリの脆弱性を非公開で報告したときにリポジトリの保守担当者に通知し、保守担当者がリポジトリを監視するか、リポジトリに対して通知を有効にした場合に通知を送信します。 詳細については、「[通知の設定](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)」を参照してください。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click the advisory you want to review. An advisory that is privately reported will have a status of `Needs triage`.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. 確認するアドバイザリをクリックします。 非公開で報告されるアドバイザリの状態は `Needs triage` になります。
- 
+ 
-2. Carefully review the report. You can:
- - Collaborate with the security researcher on a patch in private, by clicking **Start a temporary private fork**. This gives you a place for further discussions with the contributor without changing the status of the proposed advisory from `Needs triage`.
- - Accept the vulnerability report as a draft advisory on {% data variables.product.prodname_dotcom %}, by clicking **Accept and open as draft**. If you choose this option:
- - This doesn't make the report public.
- - The report becomes a draft repository security advisory and you can work on it in the same way as any draft advisory that you create.
- For more information on security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."
- - Reject the report by clicking **Close security advisory**. Where possible, you should add a comment explaining why you don't consider the report a security risk before you close the advisory.
+2. レポートを慎重に確認します。 次のようにすることができます。
+ - **[一時的なプライベート フォークを開始する]** をクリックして、パッチについてセキュリティ リサーチャーと非公開で共同作業します。 これにより、提案されたアドバイザリの状態を `Needs triage` から変更することなく、共同作成者とさらに話し合う場所が提供されます。
+ - **[承諾してドラフトとして開く]** をクリックして、{% data variables.product.prodname_dotcom %} のドラフト アドバイザリとして脆弱性レポートを承諾します。 このオプションを選択した場合、次のようになります。
+ - これにより、レポートが公開されることはありません。
+ - レポートはドラフトのリポジトリ セキュリティ アドバイザリになり、作成するドラフト アドバイザリと同じ方法で作業できます。
+ セキュリティ アドバイザリの詳細については、「[リポジトリ セキュリティ アドバイザリについて](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)」を参照してください。
+ - **[セキュリティ アドバイザリを閉じる]** をクリックして、レポートを拒否します。 可能であれば、アドバイザリを閉じる前に、レポートをセキュリティ リスクと見なさない理由を説明するコメントを追加する必要があります。
- 
\ No newline at end of file
+ 
diff --git a/translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md b/translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
index 521fa86d92..030a4dd2d3 100644
--- a/translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
+++ b/translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
@@ -1,6 +1,6 @@
---
-title: Privately reporting a security vulnerability
-intro: Some public repositories configure security advisories so that anyone can report security vulnerabilities directly and privately to the maintainers.
+title: セキュリティの脆弱性を非公開で報告する
+intro: 一部のパブリック リポジトリでは、セキュリティ アドバイザリを構成して、誰もがセキュリティの脆弱性を直接、または非公開で保守担当者に報告できるようにします。
versions:
fpt: '*'
ghec: '*'
@@ -10,61 +10,64 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Privately reporting
+ms.openlocfilehash: 7f4f208bd2724608cf9955efd82a256c3479e884
+ms.sourcegitcommit: 2ff4a43f0b14939da79d56c54402cfee8d90ae23
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/17/2022
+ms.locfileid: '148169558'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## セキュリティの脆弱性を非公開で報告する方法について
-Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
+セキュリティ リサーチャーは、多くの場合、脆弱性についてユーザーに通知しなくてはならないと感じますが、脆弱性は悪用されることがあります。 脆弱性を含むリポジトリのメンテナンス担当者への連絡について明確な指示がない場合には、セキュリティ リサーチャーが、その脆弱性についてソーシャル メディアに投稿したり、メンテナンス担当者にダイレクト メッセージを送信したり、issue を作成して公開したりすることになります。 このような状況では、脆弱性の詳細が広く知れわたってしまう可能性があります。
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to repository maintainer using a simple form.
+プライベート脆弱性レポートを使用すると、セキュリティ リサーチャーは簡単なフォームを使用してリポジトリの保守担当者に脆弱性を直接報告できます。
-For security researchers, the benefits of using private vulnerability reporting are:
-- Less frustration, and less time spent trying to figure out how to contact the maintainer.
-- A smoother process for disclosing and discussing vulnerability details.
-- The opportunity to discuss vulnerability details privately with repository maintainer.
+セキュリティ リサーチャーの場合、プライベート脆弱性レポートを使うと次のような利点があります。
+- フラストレーションが少なく、保守担当者に連絡する方法を把握するのに費やす時間も少なくなります。
+- 脆弱性の詳細を開示して話し合うためのよりスムーズなプロセス。
+- リポジトリの保守担当者と非公開で脆弱性の詳細について話し合う機会。
{% note %}
-**Note:** If the repository doesn't have private vulnerabiliy reporting enabled, you need to initiate the reporting process by following the instructions in the security policy for the repository, or create an issue asking the maintainers for a preferred security contact. For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
+**注:** リポジトリでプライベート脆弱性レポートが有効になっていない場合は、リポジトリのセキュリティ ポリシーの手順に従ってレポート プロセスを開始するか、推奨されるセキュリティ連絡先を保守担当者に要求する issue を作成する必要があります。 詳細については、「[セキュリティ脆弱性の調整された開示について](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)」を参照してください。
{% endnote %}
-## Privately reporting a security vulnerability
+## セキュリティの脆弱性を非公開で報告する
-Security researchers can privately report a security vulnerability to repository maintainers.
+セキュリティ リサーチャーは、リポジトリの保守担当者に脆弱性を非公開で報告できます。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **Report a vulnerability** to open the advisory form.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. **[脆弱性の報告]** をクリックして、アドバイザリ フォームを開きます。
- 
+ ![[脆弱性の報告] ボタンを示すスクリーンショット](/assets/images/help/security/report-a-vulnerability-button.png)
-2. Fill in the advisory details form.
+2. アドバイザリの詳細フォームに入力します。
{% tip %}
- **Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
+ **ヒント:** このフォームでは、タイトルと説明のみが必須です。 (リポジトリの保守担当者が開始する一般的なドラフト セキュリティ アドバイザリ フォームでは、エコシステムを指定する必要もあります)。ただし、セキュリティ リサーチャーは、送信されたレポートに関して保守担当者が情報に基づいた意思決定を行えるように、フォームにできるだけ多くの情報を提供することをお勧めします。 GitHub のセキュリティ研究者が使ったテンプレートを、[`github/securitylab` リポジトリ](https://github.com/github/securitylab/blob/main/docs/report-template.md)で利用できる {% data variables.product.prodname_security %} から採用できます。
{% endtip %}
- For more information about the fields available and guidance on filling in the form, see "[Creating a repository security advisory](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[Best practices for writing repository security advisories](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
+ 使用可能なフィールドとフォームへの入力に関するガイダンスの詳細については、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)」および「[リポジトリ セキュリティ アドバイザリを作成するためのベスト プラクティス](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)」を参照してください。
-1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
+1. フォームの下部にある **[レポートの送信]** をクリックします。 {% data variables.product.prodname_dotcom %} には、保守担当者に通知されたことと、このセキュリティ アドバイザリの保留中のクレジットがあることを知らせるメッセージが表示されます。
- 
+ ![[レポートの送信] ボタンを示すスクリーンショット](/assets/images/help/security/advisory-submit-report-button.png)
{% tip %}
- **Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
+ **ヒント:** レポートが送信されると、{% data variables.product.prodname_dotcom %} によって、コラボレーターとして、また提案されたアドバイザリのクレジット ユーザーとして脆弱性の報告者が自動的に追加されます。
{% endtip %}
-1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge that private fork.
+1. 必要に応じて、issue の解決を開始する場合は、 **[一時的なプライベート フォークを開始する]** をクリックします。 リポジトリの保守担当者のみがそのプライベート フォークをマージできることに注意してください。
- 
+ 
-The next steps depend on the action taken by the repository maintainer. For more information, see "[Managing privately reported security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)."
+次の手順は、リポジトリの保守担当者によって実行されるアクションによって異なります。 詳細については、「[非公開で報告されたセキュリティ脆弱性の管理](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
index 8f8ea3d298..78dcb59889 100644
--- a/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
+++ b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository security advisory
-intro: You can create a draft security advisory to privately discuss and fix a security vulnerability in your open source project.
+title: リポジトリ セキュリティ アドバイザリの作成
+intro: セキュリティアドバイザリのドラフトを作成して、オープンソースプロジェクトのセキュリティ脆弱性について非公開で議論して修正することができます。
redirect_from:
- /articles/creating-a-maintainer-security-advisory
- /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
@@ -15,31 +15,31 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Create repository advisories
+ms.openlocfilehash: 5c78a8b0c0a2d5085a876de2b0788ef093c4c6b1
+ms.sourcegitcommit: 74c60a4564bcc17e47b5a67941ac6d9fe13b6a5c
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/30/2022
+ms.locfileid: '148186156'
---
-
-Anyone with admin permissions to a repository can create a security advisory.
+リポジトリに対する管理者権限があるユーザなら誰でも、セキュリティアドバイザリを作成できます。
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-## Creating a security advisory
+## セキュリティ アドバイザリの作成
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **New draft security advisory** to open the draft advisory form. The fields marked with an asterisk are required.
- 
-1. Type a title for your security advisory.
-{% data reusables.repositories.security-advisory-edit-details %}
-{% data reusables.repositories.security-advisory-edit-severity %}
-{% data reusables.repositories.security-advisory-edit-cwe-cve %}
-{% data reusables.repositories.security-advisory-edit-description %}
-1. Click **Create draft security advisory**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. **[新しいドラフト セキュリティ アドバイザリ]** をクリックし、ドラフト アドバイザリ フォームを開きます。 アスタリスクが付いているフィールドは必須です。
+ ![[アドバイザリのドラフトを開く] ボタン](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png)
+1. セキュリティアドバイザリのタイトルを入力します。
+{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
+1. **[セキュリティ アドバイザリのドラフトの作成]** をクリックします。
+ ![[セキュリティ アドバイザリの作成] ボタン](/assets/images/help/security/security-advisory-create-security-advisory-button.png)
-## Next steps
+## 次の手順
-- Comment on the draft security advisory to discuss the vulnerability with your team.
-- Add collaborators to the security advisory. For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)."
-- Privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)."
-- Add individuals who should receive credit for contributing to the security advisory. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)."
-- Publish the security advisory to notify your community of the security vulnerability. For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
+- セキュリティアドバイザリのドラフトにコメントして、チームと脆弱性について話し合います。
+- セキュリティアドバイザリにコラボレータを追加します。 詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。
+- 一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートします。 詳細については、「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください。
+- セキュリティアドバイザリへの貢献に対してクレジットを受け取る必要がある個人を追加します。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)」を参照してください。
+- コミュニティにセキュリティの脆弱性を知らせるため、セキュリティアドバイザリを公開します。 詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
index aeb477c475..5fe6313c0c 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a codespace for a repository
-intro: You can create a codespace for a branch in a repository to develop online.
+title: リポジトリの codespace を作成する
+intro: リポジトリのブランチの codespace を作成して、オンラインで開発できます。
redirect_from:
- /github/developing-online-with-github-codespaces/creating-a-codespace
- /github/developing-online-with-codespaces/creating-a-codespace
@@ -14,95 +14,100 @@ topics:
- Fundamentals
- Developer
shortTitle: Create a codespace for a repo
+ms.openlocfilehash: 409c946feda4ffbd3d9ab615b6ea07fabee3f530
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188321'
---
+## リポジトリの codespace の作成について
-## About creating a codespace for a repository
+{% data reusables.codespaces.ways-to-create-a-codespace %} この記事のタブを使用して、codespace を作成するこれらの各方法の手順を表示します。
-{% data reusables.codespaces.ways-to-create-a-codespace %} Use the tabs in this article to display instructions for each of these ways of creating a codespace.
-
-{% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+{% data reusables.codespaces.starting-new-project-template %} 詳細については、「[テンプレートから codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)」を参照してください。
{% note %}
-**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[Using Codespaces in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
+**注**: JetBrains IDE を使用する場合は、{% data variables.product.prodname_cli %} を使用して codespace を作成できます。 その後、JetBrains Gateway アプリケーションを使用して、JetBrains IDE で codespace を開くことができます。 詳細については、「[JetBrains IDE での Codespaces の使用](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)」を参照してください。
{% endnote %}
-You can use {% data variables.product.prodname_github_codespaces %} on your personal {% data variables.product.prodname_dotcom_the_website %} account, with the quota of free use included each month for accounts on the Free and Pro plans. {% data reusables.codespaces.codespaces-continue-by-paying %}
+個人の {% data variables.product.prodname_dotcom_the_website %} アカウントで {% data variables.product.prodname_github_codespaces %} を使用できます。Free プランと Pro プランのアカウントには毎月無料使用のクォータが含まれています。 {% data reusables.codespaces.codespaces-continue-by-paying %}
-Organizations can enable members and outside collaborators to create and use codespaces at the organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
+組織は、メンバーと外部コラボレーターが組織の費用で codespace を作成して使用できるようにすることができます。 詳しくは、「[Organization での {% data variables.product.prodname_github_codespaces %} の有効化](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)」をご覧ください。
{% data reusables.codespaces.codespaces-are-personal %}
-If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch.
+リポジトリから codespace を作成すると、codespace は特定のブランチに関連付けられます。空にすることはできません。 リポジトリごと、さらにはブランチごとに1つ以上のcodespaceを作成できます。
{% data reusables.codespaces.you-can-see-all-your-codespaces %}
-### The codespace creation process
+### codespace の作成プロセス
-When you create a codespace, a number of steps happen to create and connect you to your development environment:
+codespace を作成すると、開発環境を作成して開発環境に接続するためのいくつかの手順が発生します。
-- Step 1: VM and storage are assigned to your codespace.
-- Step 2: Container is created and your repository is cloned.
-- Step 3: You can connect to the codespace.
-- Step 4: Codespace continues with post-creation setup.
+- 手順 1: VM とストレージが codespace に割り当てられます。
+- 手順 2: コンテナーが作成され、リポジトリが複製されます。
+- 手順 3: codespace に接続できます。
+- 手順 4: codespace では、作成後のセットアップが続行されます。
-For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
+codespace を作成した場合に起きることの詳細については、[詳細情報](/codespaces/getting-started/deep-dive)に関するページを参照してください。
-For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)."
+codespace のライフサイクルの詳細については、「[Codespace のライフサイクル](/codespaces/getting-started/the-codespace-lifecycle)」を参照してください。
-If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+codespace に Git フックを使用する場合は、手順 4. で [`devcontainer.json`ライフサイクル スクリプト](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts) (例: `postCreateCommand`) を使用してフックを設定する必要があります。 リポジトリの複製後に codespace コンテナーが作成されるため、コンテナー イメージで構成された [Git テンプレート ディレクトリ](https://git-scm.com/docs/git-init#_template_directory) は codespace には適用されません。 代わりに、codespace の作成後にフックをインストールする必要があります。 `postCreateCommand` の使用について詳しくは、{% data variables.product.prodname_vscode_shortname %} ドキュメントの「[`devcontainer.json` リファレンス](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties)」を参照してください。
{% data reusables.codespaces.use-visual-studio-features %}
{% data reusables.codespaces.prebuilds-crossreference %}
-## Creating a codespace for a repository
+## リポジトリの codespace を作成する
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create a codespace for.
+1. リポジトリ名の下で、[ブランチ] ドロップダウンメニューを使用して、codespace を作成するブランチを選びます。
- 
+ ![[ブランチ] ドロップダウンメニュー](/assets/images/help/codespaces/branch-drop-down.png)
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. **[{% octicon "code" aria-label="The code icon" %} コード]** ボタンをクリックし、 **[Codespaces]** タブをクリックします。
- 
+ ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
- If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
+ このリポジトリの codespace が組織、またはその親エンタープライズに対して課金可能な場合は、 **[<ブランチ名> で codespace を作成する]** ボタンの下に、codespace の料金を支払うユーザーを示すメッセージが表示されます。
-1. Create your codespace, either using the default options, or after configuring advanced options:
+1. 既定のオプションを使用するか、詳細オプションを構成した後に、codespace を作成します。
- * **Use the default options**
+ * **既定のオプションを使用する**
- To create a codespace using the default options, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). Alternatively, if you don't currently have any codespaces for this repository, you can click **Create codespace on BRANCH**.
+ 既定のオプションを使用して codespace を作成するには、プラス記号 ({% octicon "plus" aria-label="The plus icon" %}) をクリックします。 または、現在このリポジトリの codespace がない場合は、 **[ブランチで codespace を作成する]** をクリックできます。
- * **Configure options**
+ * **構成オプション**
- To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file:
+ 別のマシンの種類や特定の `devcontainer.json` ファイルなど、codespace の詳細オプションを構成するには:
- 1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab and select **New with options**.
+ 1. **[Codespaces]** タブの右上にある省略記号 ( **...** ) をクリックし、 **[オプションを含む新規]** を選びます。
- 
+ 
- 1. On the options page for your codespace, choose your preferred options from the dropdown menus.
+ 1. codespace のオプション ページで、ドロップダウン メニューから任意のオプションを選びます。
- 
+ 
{% note %}
- **Notes**
+ **メモ**
- * You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
- * The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
- * For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
- * For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+ * オプション ページをブックマークすると、このリポジトリとブランチの codespace をすばやく作成できるようになります。
+ * [https://github.com/codespaces/new](https://github.com/codespaces/new) ページでは、リポジトリとブランチの codespace をすばやく作成できます。 ブラウザーのアドレス バーに「`codespace.new`」と入力すると、このページにすばやくアクセスできます。
+ * `devcontainer.json` ファイルの詳細については、「[開発コンテナーの概要](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)」をご覧ください。
+ * マシンの種類について詳しくは、「[codespace のマシンの種類を変更する](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)」をご覧ください。
* {% data reusables.codespaces.codespaces-machine-type-availability %}
{% endnote %}
- 1. Click **Create codespace**.
+ 1. **[Create codespace]\(codespace の作成\)** をクリックします。
{% endwebui %}
@@ -116,30 +121,30 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
{% data reusables.cli.cli-learn-more %}
-To create a new codespace, use the `gh codespace create` subcommand.
+新しい codespace を作成するには、`gh codespace create` サブコマンドを使用します。
```shell
gh codespace create
```
-You are prompted to choose a repository. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
+リポジトリの選択を求められます。 このリポジトリの codespace が組織、またはその親エンタープライズに対して課金可能な場合は、codespace の料金を支払うユーザーを示すメッセージが表示されます。 その場合、ブランチ、開発コンテナー構成ファイル (複数ある場合)、コンピューターの種類 (複数ある場合) を選ぶように求められます。
-Alternatively, you can use flags to specify some or all of the options:
+または、フラグを使用して、次に示すオプションの一部またはすべてを特定することもできます。
```shell
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
```
-In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
+この例の `owner/repo` をリポジトリ識別子に置き換えます。 `branch` を codespace で最初にチェックアウトするブランチの名前、またはコミットの完全な SHA ハッシュに置き換えます。 `b` フラグなしで `-r` フラグを使用する場合、codespace は既定のブランチから作成されます。
-Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+新しいコードスペースで使用する開発コンテナー構成ファイルへのパスに `path` を置き換えます。 このフラグを省略し、複数の開発コンテナー ファイルを使用できる場合は、リストから 1 つを選ぶダイアログが表示されます。 開発コンテナーの構成ファイルについて詳しくは、「[開発コンテナーの概要](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)」を参照してください。
-Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
+`machine-type` を使用可能なマシンの種類の有効な識別子に置き換えます。 識別子は、`basicLinux32gb` や `standardLinux32gb` のような文字列です。 使用可能なマシンの種類は、リポジトリ、個人用アカウント、場所によって異なります。 無効または使用できないマシンの種類を入力すると、使用可能な種類がエラー メッセージに表示されます。 このフラグを省略し、複数のマシンの種類を使用できる場合は、リストから 1 つを選択するダイアログが表示されます。
-For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
+このコマンドのオプションについて詳しくは、[{% data variables.product.prodname_cli %} マニュアル](https://cli.github.com/manual/gh_codespace_create)を参照してください。
{% endcli %}
-## Further reading
-- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
-- "[Adding an 'Open in {% data variables.product.prodname_github_codespaces %}' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
+## 参考資料
+- [既存の codespace を開く](/codespaces/developing-in-codespaces/opening-an-existing-codespace)
+- 「[[{% data variables.product.prodname_github_codespaces %} で開く] バッジの追加](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)」
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
index 842a20e971..f5c8755cbb 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
@@ -1,6 +1,6 @@
---
-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.
+title: テンプレートから codespace を作成する
+intro: 新しいプロジェクトを開始する場合、空のテンプレートから codespace を作成するか、実行する作業の種類用に特別に設計されたテンプレートを選ぶことができます。
versions:
fpt: '*'
ghec: '*'
@@ -11,92 +11,95 @@ topics:
- Developer
shortTitle: Create a codespace from a template
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 9e7ee0d110e962fa755f5f57cc70bc3cab341808
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188313'
---
+## {% data variables.product.prodname_github_codespaces %} のテンプレートについて
-## 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.
+新しいプロジェクトを開始する場合、テンプレートから codespace を作成すると、開発作業をすばやく開始できます。 クラウドベースの開発環境でプロジェクトに取り組み、ファイルをクラウドに保存し、新しいリモート リポジトリに作業内容を公開することで、他のユーザーと共有したり、ローカル コンピューターに複製したりできます。
{% 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)."
+**注**: codespace をリポジトリではなくテンプレートから作成すると、常に個人アカウントに課金されます。 詳しくは、「[{% 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)."
+空のテンプレートから開始する、{% data variables.product.company_short %} が管理するテンプレートから React や Jupyter Notebook などの一般的なテクノロジを選ぶ、または {% data variables.product.prodname_dotcom %} 上の任意のテンプレート リポジトリから codespace を起動できます。 空のテンプレートを使う場合は、まず空のディレクトリから始めます。クラウドベースのコンピューティング リソースと、既定の codespace イメージにプレインストールされているツール、言語、ランタイム環境にアクセスできます。 他のテンプレートを使う場合は、扱うテクノロジのスターター ファイルに加え、通常は、README ファイル、`.gitignore` ファイル、カスタム環境構成を含む開発コンテナー構成ファイルなどの追加ファイルをいくつか取得します。 開発コンテナーと既定のイメージについて詳しくは、「[開発コンテナーの概要](/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.
+たとえば、{% data variables.product.company_short %} の React テンプレートから codespace を作成すると、`index.js`、`app.js`、`package.json` など、シンプルなアプリケーション向けのテンプレート ファイルが用意されているワークスペースが表示されます。 codespace が開いた直後に、開発サーバーが自動的に起動し、{% data variables.product.prodname_vscode_shortname %} Web クライアント内のシンプルなブラウザー タブで、実行中のアプリケーションを表示できるようになります。
-
+
-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.
+テンプレートに含まれるファイルと構成は、テンプレート リポジトリで定義されています。 codespace を作成すると、テンプレート リポジトリは codespace に複製されます。 その後、リンクは切断され、公開するまで codespace はリモート リポジトリにリンクされないようになります。
{% 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)."
+**ヒント:** ユーザーがフレームワーク、ライブラリ、またはその他のプロジェクトを使い始められるように、{% data variables.product.prodname_github_codespaces %} で使うテンプレート リポジトリを設定できます。 詳しくは、「[{% data variables.product.prodname_github_codespaces %} のテンプレート リポジトリを設定する](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)」を参照してください。
{% endtip %}
-## Creating a codespace from a {% data variables.product.company_short %} template
+## {% data variables.product.company_short %} テンプレートから codespace を作成する
-Templates maintained by {% data variables.product.company_short %}, including the blank template, are available from the "Your codespaces" page.
+空のテンプレートなど、{% data variables.product.company_short %} が管理するテンプレートは、"自分の codespace" ページから入手できます。
-{% 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.
+{% data reusables.codespaces.your-codespaces-procedure-step %} {% data reusables.codespaces.view-all-templates-step %}
+1. 必要に応じて、テンプレートのファイルを含むテンプレート リポジトリを表示するには、テンプレートの名前をクリックします。
- 
+ ![[クイック スタート テンプレートの探索] セクションの [React] が強調表示されているスクリーンショット](/assets/images/help/codespaces/react-template-name.png)
-1. Under the template you want to launch, click **Use this template**.
+1. 起動するテンプレートの下にある **[このテンプレートを使用]** をクリックします。
- 
+ ![React テンプレートの下にある [このテンプレートを使用] ボタンが強調表示されているクイック スタート テンプレートのスクリーンショット](/assets/images/help/codespaces/react-template-button.png)
{% data reusables.codespaces.template-codespaces-default-editor %}
-## Creating a codespace from a template repository
+## テンプレート リポジトリから codespace を作成する
-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)."
+任意のテンプレート リポジトリから codespace を作成し、準備ができたら新しいリポジトリに作業内容を公開できます。 テンプレート リポジトリについて詳しくは、「[テンプレートからリポジトリを作成する](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates)」を参照してください。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.codespaces.open-template-in-codespace-step %}
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.codespaces.open-template-in-codespace-step %}
{% note %}
- **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)."
+ **注:** 自分がテンプレート リポジトリの保守管理者で、テンプレート リポジトリ自体に変更をコミットする場合は、 **[{% octicon "code" aria-label="The code icon" %} コード]** ドロップダウンから codespace を作成する必要があります。 詳しくは、「[リポジトリの codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)」を参照してください。
{% endnote %}
{% data reusables.codespaces.template-codespaces-default-editor %}
-## Publishing to a repository on {% data variables.product.product_name %}
+## {% data variables.product.product_name %} のリポジトリに公開する
{% data reusables.codespaces.about-publishing-templates %}
-### Publishing from {% data variables.product.prodname_vscode_shortname %}
+### {% 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:
+codespace が公開されると、自分の {% data variables.product.prodname_github_codespaces %} エクスペリエンスをカスタマイズするためのさまざまなオプションにアクセスできます。 たとえば、次のように操作できます。
-- Change the machine type of your codespace to make sure you're using resources appropriate for the work you're doing (see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)").
-- Allow {% data variables.product.prodname_dotcom %} to automatically use GPG to sign commits you make in your codespace (see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)").
-- Share encrypted secrets with your codespace (see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)").
+- codespace のコンピューターの種類を変更して、作業に適したリソースを使っていることを確認します (「[codespace のコンピューターの種類を変更する](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)」を参照してください)。
+- {% data variables.product.prodname_dotcom %} が自動的に GPG を使って codespace で行うコミットに署名できるようにします (「[{% data variables.product.prodname_github_codespaces %} の GPG 検証を管理する](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)」を参照してください)。
+- 暗号化されたシークレットを codespace と共有します (「[codespaces の暗号化されたシークレットを管理する](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)」を参照してください)。
-### Publishing from {% data variables.product.prodname_dotcom_the_website %}
+### {% 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.
+公開されていない codespace は、{% data variables.product.prodname_dotcom_the_website %} の "自分の codespace" ページから公開できます。 これは、ブラウザー内で現在開いていない codespace を公開する場合に便利です。 これを行うと、作業内容はリポジトリに保持されますが、既存の codespace と新しいリポジトリの間のリンクはなくなります。 ただし、新しいリポジトリに移動し、そこから codespace を作成すると、この codespace はそのリポジトリに接続されるようになります。
{% data reusables.codespaces.your-codespaces-procedure-step %}
-1. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**.
+1. 公開されていない codespace の横にある省略記号 ( **...** ) をクリックし、 **[新しいリポジトリに公開する]** を選びます。
- 
-1. Choose a name for your new repository, set it as **Public** or **Private**, and click **Create repository**.
+ ![[新しいリポジトリに公開する] ボタンのスクリーンショット](/assets/images/help/codespaces/publish-to-new-repository.png)
+1. 新しいリポジトリの名前を選び、 **[パブリック]** または **[プライベート]** に設定して、 **[リポジトリの作成]** をクリックします。
- 
-1. Optionally, to view the new repository, click **See repository**.
+ ![[新しいリポジトリに公開する] ドロップダウンのスクリーンショット](/assets/images/help/codespaces/template-new-repository-settings.png)
+1. 必要に応じて、新しいリポジトリを表示するには、 **[リポジトリの表示]** をクリックします。
-## Further reading
+## 参考資料
-- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)"
-- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)"
-- "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
\ No newline at end of file
+- [リポジトリの codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)
+- [codespace ライフサイクル](/codespaces/getting-started/the-codespace-lifecycle)
+- [codespace でソース管理を使う](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)
diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
index 6514047f43..a7bbcc4c43 100644
--- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
+++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
@@ -9,12 +9,12 @@ topics:
- Codespaces
redirect_from:
- /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds
-ms.openlocfilehash: e0962e410f2227a23ff98c8a3e7995ea8ec8a914
-ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.openlocfilehash: eecb77b541cc735fcf788fbc5da6960cabad899d
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: ja-JP
-ms.lasthandoff: 11/09/2022
-ms.locfileid: '148158798'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191919'
---
## 概要
diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
index c7605e66fc..104c4c47c2 100644
--- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
+++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Configuring prebuilds
+title: プレビルドの構成
shortTitle: Configure prebuilds
-intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
+intro: 変更をリポジトリにプッシュするたびに自動的に codespace をプレビルドするようにプロジェクトを構成できます。
versions:
fpt: '*'
ghec: '*'
@@ -10,106 +10,111 @@ topics:
- Codespaces
- Set up
permissions: People with admin access to a repository can configure prebuilds for the repository.
+ms.openlocfilehash: dbb355e150695f27d1d6a7fa51eccc33a0ebde4f
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159118'
---
+プレビルド構成は、リポジトリの特定のブランチと特定の開発コンテナー構成ファイルの組み合わせに対して設定できます。
-You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file.
+通常、プレビルドが有効な親ブランチから作られたブランチはすべて、同じ開発コンテナー構成のプレビルドも取得します。 これは、親ブランチと同じ開発コンテナー構成を使う子ブランチのプレビルドがほとんどの場合同一であるためであり、これにより、開発者はこれらのブランチの codespace の作成時間を短縮できるというメリットも得られます。 詳細については、[開発コンテナーの概要](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)に関するページをご覧ください。
-Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because prebuilds for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+通常、ブランチにプレビルドを構成すると、複数のマシンの種類でプレビルドを使用できるようになります。 しかし、リポジトリが 32 GB を超える場合、提供されるストレージは 32 GB に制限されているため、2 コアと 4 コアのマシンの種類ではプレビルドを使用できません。
-Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB.
+## 前提条件
-## Prerequisites
+プレビルドは、{% data variables.product.prodname_actions %} を使用して作成されます。 その結果、プレビルドを構成するリポジトリに対して {% data variables.product.prodname_actions %} を有効にする必要があります。 詳細については、「[リポジトリの {% data variables.product.prodname_actions %} 設定の管理](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)」を参照してください。
-Prebuilds are created using {% data variables.product.prodname_actions %}. As a result, {% data variables.product.prodname_actions %} must be enabled for the repository for which you are configuring prebuilds. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)."
-
-## Configuring prebuilds
+## プレビルドの構成
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
+1. ページの [プレビルド構成] セクションで、 **[プレビルドの設定]** をクリックします。
- 
+ ![[プレビルドの設定] ボタン](/assets/images/help/codespaces/prebuilds-set-up.png)
-1. Choose the branch for which you want to set up prebuilds.
+1. プレビルドを設定するブランチを選びます。
- 
+ 
{% note %}
- **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
+ **注**: 通常、プレビルドが有効なベース ブランチから作られたブランチはすべて、同じ開発コンテナー構成のプレビルドも取得します。 たとえば、リポジトリの既定のブランチで開発コンテナー構成ファイルのプレビルドを有効にすると、ほとんどの場合、既定のブランチに基づくブランチも同じ開発コンテナー構成のプレビルドを取得するようになります。
{% endnote %}
-1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
+1. 必要に応じて、表示される **[構成ファイル]** ドロップダウン メニューで、ご自分のプレビルドに使う `devcontainer.json` 構成ファイルを選びます。 詳細については、[開発コンテナーの概要](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)に関するページをご覧ください。
- 
+ 
-1. Choose how you want to automatically trigger prebuild updates.
+1. プレビルドの更新を自動的にトリガーする方法を選びます。
- * **Every push** (the default setting) - With this setting, prebuilds will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies.
- * **On configuration change** - With this setting, prebuilds will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The {% data variables.product.prodname_actions %} workflow that updates the prebuilds will run less often, so this option will use fewer {% data variables.product.prodname_actions %} minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created.
- * **Scheduled** - With this setting, you can have your prebuilds updated on a custom schedule that's defined by you. This can reduce consumption of {% data variables.product.prodname_actions %} minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes.
+ * **すべてのプッシュ** (既定の設定) - この設定では、特定のブランチに対して行われるすべてのプッシュで、プレビルドの構成が更新されます。 これにより、プレビルドから生成された codespace には、最近追加または更新された依存関係を含む最新の codespace 構成が常に含まれます。
+ * **構成の変更時** - この設定では、特定のリポジトリとブランチの関連する構成ファイルが更新されるたびに、プレビルドが更新されます。 これにより、プレビルドから codespace が生成されるときに、リポジトリの開発コンテナー構成ファイルに対する変更が確実に使用されます。 プレビルドを更新する {% data variables.product.prodname_actions %} ワークフローは実行頻度が低いため、このオプションでは使用する {% data variables.product.prodname_actions %} の使用時間 (分) が少なくなります。 ただし、このオプションでは、codespace に常に最近追加または更新された依存関係が含まれるという保証はないため、codespace の作成後に手動で追加または更新する必要がある場合があります。
+ * **スケジュール済み** - この設定では、ユーザーが定義したカスタム スケジュールに基づいてプレビルドを更新できます。 これにより、{% data variables.product.prodname_actions %} の使用時間 (分) を減らすことができますが、このオプションでは、最新の開発コンテナー構成の変更を使用しない codespace を作成できます。
- 
+ 
-1. Optionally, select **Reduce prebuild available to only specific regions** to create prebuilds only in specified regions. Select the regions in which you want prebuilds to be available.
+1. 必要に応じて、 **[特定のリージョンでのみ使用できるプレビルドを減らす]** を選び、指定したリージョンにのみプレビルドを作成します。 プレビルドを使用できるようにするリージョンを選びます。
- By default, prebuilds are created in all of the available regions, incurring storage charges per prebuild.
+ 既定では、使用可能なすべてのリージョンにプレビルドが作成され、プレビルドごとにストレージ料金が発生します。
- 
+ 
{% note %}
- **Notes**:
- * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
- * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
+ **注**:
+ * 各リージョンのプレビルドでは、個々のストレージ料金が発生します。 そのため、使用されることがわかっているリージョンに対してのみプレビルドを有効にする必要があります。 詳しくは、「[{% data variables.product.prodname_github_codespaces %} の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)」をご覧ください。
+ * 開発者は、{% data variables.product.prodname_github_codespaces %} の既定のリージョンを設定できます。これにより、より少ないリージョンでプレビルドを有効にすることができます。 詳しくは、「[{% data variables.product.prodname_github_codespaces %} の既定のリージョンの設定](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)」を参照してください。
{% endnote %}
-1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved.
+1. 必要に応じて、 **[テンプレートの履歴]** で、保持するプレビルドのバージョンを設定します。 1 から 5 の任意の数を入力できます。 保存されるバージョンの既定の数は 2 です。つまり、最新のプレビルドと前のバージョンのみが保存されます。
- 
+ 
- Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. This setting allows you to set the number of retained versions to a level that is appropriate for your needs.
+ プレビルドのトリガー設定によっては、プッシュごと、または開発コンテナー構成の変更ごとに、プレビルドが変更される可能性があります。 以前のバージョンのプレビルドを保持すると、現在のプレビルドとは異なる開発コンテナー構成を使用して、以前のコミットからプレビルドを作成できます。 この設定を使用すると、保持されているバージョンの数を、ニーズに適したレベルに設定できます。
- If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration.
+ 保存するプレビルドのバージョンの数を 1 に設定した場合、{% data variables.product.prodname_github_codespaces %} によりプレビルドの最新バージョンのみが保存され、テンプレートが更新されるたびに古いバージョンが削除されます。 つまり、以前の開発コンテナー構成に戻った場合、プレビルドの codespace は取得されません。
- There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+ 保持されている各プレビルド バージョンには、ストレージ コストが関連付けられています。 たとえば、4 つのリージョンでプレビルドを生成し、2 つのバージョンを保持している場合、最大 8 つのプレビルドのストレージに対して課金されます。 課金について詳しくは、「[{% data variables.product.prodname_github_codespaces %} の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)」をご覧ください。
-1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation.
+1. 必要に応じて、この構成でプレビルド ワークフローの実行が失敗したときに通知するユーザーまたはチームを追加します。 ユーザー名、チーム名、またはフル ネームの入力を開始し、表示されたら名前をクリックしてリストに追加できます。 追加したユーザーまたはチームは、プレビルド エラーが発生したときに電子メールを受信します。詳しい調査に役立つワークフロー実行ログへのリンクが含まれています。
- 
+ 
-1. Optionally, at the bottom of the page, click **Show advanced options**.
+1. 必要に応じて、ページの下部にある **[詳細オプションの表示]** をクリックします。
- 
+ ![[詳細オプションの表示] が強調表示されているプレビルド構成ページのスクリーンショット](/assets/images/help/codespaces/show-advanced-options.png)
- In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
+ [詳細オプション] セクションで、 **[プレビルドの最適化を無効にする]** を選んだ場合、最新のプレビルド ワークフローが失敗したか、現在実行中の場合は、プレビルドなしで codespace が作成されます。 詳しくは、「[プレビルドのトラブルシューティング](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)」を参照してください。
-1. Click **Create**.
+1. **Create** をクリックしてください。
{% data reusables.codespaces.prebuilds-permission-authorization %}
-After you create a prebuild configuration it is listed on the {% data variables.product.prodname_github_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuilds in the regions you specified, based on the branch and dev container configuration file you selected.
+プレビルド構成を作ると、リポジトリ設定の {% data variables.product.prodname_github_codespaces %} ページに一覧表示されます。 {% data variables.product.prodname_actions %} ワークフローがキューに登録され、指定したリージョンで、選んだブランチと開発コンテナー構成ファイルに基づいて、プレビルドを作るために実行されます。
-
+
-For information about editing and deleting prebuild configurations, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)."
+プレビルド構成の編集と削除について詳しくは、「[プレビルドを管理する](/codespaces/prebuilding-your-codespaces/managing-prebuilds)」を参照してください。
-## Configuring environment variables
+## 環境変数の設定
-To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)."
+開発環境を作成するために必要な環境変数にプレビルド プロセスでアクセスできるようにするには、これらを {% data variables.product.prodname_codespaces %} リポジトリ シークレットとして、または {% data variables.product.prodname_codespaces %} Organization シークレットとして設定できます。 詳細については、「[リポジトリのシークレットの追加](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)」および「[のシークレットの追加](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)」を参照してください。
-Secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces.
+この方法で作ったシークレットは、このリポジトリから codespace を作るすべてのユーザーがアクセスできます。 そのようにしたくない場合は、代わりに `CODESPACES_PREBUILD_TOKEN` シークレットを設定できます。 `CODESPACES_PREBUILD_TOKEN` シークレットはプレビルドにのみ使用され、ユーザーの codespace ではその値にアクセスできません。
-Prebuilds cannot use any user-level secrets while building your environment, because these are not available until after the codespace has been created.
+環境の構築中は、プレビルドでユーザー レベルのシークレットを使うことはできません。これは、codespace が作られるまで利用できないためです。
-## Configuring time-consuming tasks to be included in the prebuild
+## プレビルドに含める時間のかかるタスクの構成
-You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)."
+`devcontainer.json` で `onCreateCommand` および `updateContentCommand` コマンドを使用して、プレビルド作成の一部として時間のかかるプロセスを含めることができます。 詳細については、{% data variables.product.prodname_vscode %} のドキュメントの「[devcontainer.json リファレンス](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)」を参照してください。
-`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at creation of the prebuild and at subsequent updates to it. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update.
+`onCreateCommand` はプレビルドが作成されるときに 1 回だけ実行されますが、`updateContentCommand` はテンプレートの作成時とそれ以降の更新時に実行されます。 インクリメンタル ビルドは `updateContentCommand` に含める必要があります。これらはプロジェクトのソースを表し、プレビルドの更新ごとに含める必要があるためです。
-## Further reading
+## 参考資料
-- "[Allowing a prebuild to access other repositories](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)"
-- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
+- [プレビルドで他のリポジトリにアクセスできるようにする](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)
+- [プレビルドに関するトラブルシューティング](/codespaces/troubleshooting/troubleshooting-prebuilds)
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
index 36e4e0ae51..1c9a118a85 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
@@ -1,7 +1,7 @@
---
-title: Adding an "Open in GitHub Codespaces" badge
+title: '[GitHub Codespaces で開く] バッジの追加'
shortTitle: Add a Codespaces badge
-intro: You can add a badge to a Markdown file in your repository which people can click to create a codespace.
+intro: リポジトリ内の Markdown ファイルにバッジを追加し、ユーザーがクリックして codespace を作成できるようにすることができます。
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -10,50 +10,55 @@ type: how_to
topics:
- Codespaces
- Set up
+ms.openlocfilehash: c69a815501f5943a56d32af3e58cd7850a69588b
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158782'
---
+## 概要
-## Overview
+Markdown ファイルに [{% data variables.product.prodname_github_codespaces %} で開く] バッジを追加すると、リポジトリの codespace を簡単に作成できます。
-Adding an "Open in {% data variables.product.prodname_github_codespaces %}" badge to a Markdown file gives people an easy way to create a codespace for your repository.
+
-
+バッジを作成するときに、そのバッジで作成される codespace に対して特定の構成オプションを選ぶことができます。
-When you create a badge you can choose specific configuration options for the codespace that the badge will create.
+ユーザーがバッジをクリックすると、codespace の作成用の [詳細オプション] ページに移動します。選んだオプションは事前に選択されています。 詳細オプション ページについて詳しくは、「[リポジトリの codespace の作成](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)」を参照してください。
-When people click the badge they'll be taken to the advanced options page for codespace creation, with the options you chose preselected. For more information about the advanced options page, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+[詳細オプション] ページから、ユーザーは必要に応じて事前に選択された設定を変更し、 **[codespace の作成]** をクリックできます。
-From the advanced options page, users can change the preselected settings if required, then click **Create codespace**.
-
-## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge
+## [{% data variables.product.prodname_github_codespaces %} で開く] バッジの作成
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create the badge for.
+1. リポジトリ名の下で、[ブランチ] ドロップダウンメニューを使用して、バッジを作成するブランチを選択します。
- 
+ ![[ブランチ] ドロップダウン メニューのスクリーンショット](/assets/images/help/codespaces/branch-drop-down.png)
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. **[{% octicon "code" aria-label="The code icon" %} コード]** ボタンをクリックし、 **[Codespaces]** タブをクリックします。
- 
+ ![[新しい codespace] ボタンのスクリーンショット](/assets/images/help/codespaces/new-codespace-button.png)
-1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab, then click **New with options**.
+1. **[Codespaces]** タブの右上にある省略記号 ( **...** ) をクリックし、 **[オプションを含む新規]** をクリックします。
- 
+ ![[codespace の構成と作成] オプションのスクリーンショット](/assets/images/help/codespaces/default-machine-type.png)
-1. On the advanced options page for codespace creation, select the values you want to be preselected in each field.
+1. codespace 作成の [詳細オプション] ページで、各フィールドで事前に選択される値を選びます。
- 
+ ![[詳細オプション] ページのスクリーンショット](/assets/images/help/codespaces/advanced-options.png)
-1. Copy the URL from the browser's address bar.
-1. Add the following Markdown to, for example, the `README.md` file of your repository:
+1. ブラウザーのアドレス バーから URL をコピーします。
+1. たとえば、リポジトリの `README.md` ファイルに次の Markdown を追加します。
```Markdown{:copy}
[](COPIED-URL)
```
- For example:
+ 次に例を示します。
```Markdown
[](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2)
```
- In the above example, `0000000` will be the reference number of your repository. The other details in the URL are determined by the values you selected in the fields on the advanced options page.
+ 上記の例では、`0000000` がリポジトリの参照番号になります。 URL のその他の詳細は、[詳細オプション] ページのフィールドで選んだ値によって決まります。
diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index 25a547449e..5a833716ec 100644
--- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Troubleshooting prebuilds
+title: プレビルドに関するトラブルシューティング
shortTitle: Codespaces prebuilds
-intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds.
+intro: プレビルドを使用して、codespace の作成を高速化できます。 この記事では、プレビルドを使った一般的な問題のトラブルシューティング手順を示します。
versions:
fpt: '*'
ghec: '*'
@@ -9,86 +9,91 @@ type: reference
topics:
- Codespaces
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: b8c45f9eae6094b78026d055ebea27c3748a8681
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158886'
---
+{% data variables.product.prodname_github_codespaces %} のプレビルドの詳細については、「[codespace のプレビルド](/codespaces/prebuilding-your-codespaces)」を参照してください。
-For more information about {% data variables.product.prodname_github_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)."
+## codespace がプレビルドから作成されたかどうかの確認
-## Checking whether a codespace was created from a prebuild?
+codespace を作成する際には、使用する仮想マシンの種類を選択できます。 仮想マシンの種類に対してプレビルドが使用可能な場合は、その横に "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready \(プレビルド対応\)" が表示されます。
-When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it.
+
-
+{% data variables.product.prodname_github_codespaces %} エディターの基本設定を [{% data variables.product.prodname_vscode %} for Web] に設定しており、プレビルドが使用されている場合は、[codespace の設定] ページに "プレビルド codespace が見つかりました" というメッセージが表示されます。
-If you have your {% data variables.product.prodname_github_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used.
+
-
+同様に、エディターの基本設定が [{% data variables.product.prodname_vscode_shortname %}] の場合、統合ターミナルには、新しい codespace を作成するときに、"リポジトリのプレビルド構成で定義されたプレビルド codespace を使用しています" というメッセージが含まれます。 詳しくは、「[{% data variables.product.prodname_github_codespaces %} の既定のエディターを設定する](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)」をご覧ください。
-Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
-
-After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal:
+codespace を作成した後、ターミナルで次の {% data variables.product.prodname_cli %} コマンドを実行して、プレビルドから作成されたかどうかを確認できます。
```shell{:copy}
gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild
```
-This returns `true` if the codespace was created using a prebuild.
+codespace がプレビルドを使用して作成された場合は、`true` が返されます。
-Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild:
+{% data variables.product.prodname_cli %} (`gh`) がインストールされていない場合は、次のコマンドを使用できます。codespace がプレビルドから作成された場合は、`createFromPrebuild` が返されます。
```shell{:copy}
cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME'
```
-## The "Prebuild Ready" label is sometimes missing
+## "Prebuild Ready" ラベルが欠落している場合がある
-You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
+プレビルドが有効なブランチから新しい codespace を作成する場合、コンピューターの種類を選択するためのダイアログ ボックスに "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" ラベルが表示されないことがあります。 これは、プレビルドが現在使用できないことを意味します。
-By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+既定では、プレビルドが有効なブランチにプッシュするたびに、プレビルドが更新されます。 プッシュ操作に開発コンテナー構成への変更が含まれている場合は、更新中に、"{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready \(プレビルド対応\)" ラベルがマシンの種類のリストから削除されます。 この期間も、プレビルドを使用せずに codespace を作成できます。 必要であれば、開発コンテナー構成ファイルを変更したときのみ、またはカスタム スケジュールで指定したときにのみプレビルドが更新されるように設定することで、リポジトリにプレビルドを使用できない場合を減らすことができます。 詳細については、「[プレビルドの構成](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)」を参照してください。
-If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
+ブランチがプレビルドに対して特に有効になっていない場合でも、プレビルドが有効なブランチから分岐された場合はプレビルドの利点が得られる可能性があります。 しかし、開発コンテナー構成がご利用のブランチで変更されたために、ベース ブランチの構成とは異なる場合、プレビルドはご利用のブランチで使用できなくなります。
-Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch:
+特定のブランチに対して "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" ラベルが表示されない場合の確認事項を以下に示します。
-* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this.
-* Confirm that the prebuild configuration includes your region.
-* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
-* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
+* このブランチのプレビルド構成が存在することを確認する。 リポジトリ管理者でない場合は、管理者に連絡して確認する必要があります。
+* プレビルド構成に自分のリージョンが含まれることを確認する。
+* 開発コンテナー構成への変更が、最近、プレビルドが有効になったブランチにプッシュされたかどうかを確認する。 そうである場合は、通常、このプッシュに対してプレビルド ワークフローが実行されるまで待たないと、プレビルドを再び使用することはできません。
+* 構成の変更が最近行われなかった場合は、リポジトリの **[アクション]** タブに移動し、ワークフロー リストの **{% octicon "codespaces" aria-label="The Codespaces icon" %} [{% data variables.product.prodname_codespaces %} プレビルド]** をクリックし、ブランチに対してプレビルド ワークフローが正常に実行されたことを確認します。 ワークフローの最新の実行が失敗し、これらの失敗した実行の 1 つ以上に開発コンテナー構成への変更が含まれていた場合、関連するブランチに対して使用可能なプレビルドはありません。
-## Some resources cannot be accessed in codespaces created using a prebuild
+## プレビルドを使って作った codespace で一部のリソースにアクセスできない
-If the `devcontainer.json` configuration file for a prebuild configuration specifies that permissions for access to other repositories are required, then the repository administrator is prompted to authorize these permissions when they create or update the prebuild configuration. If the administrator does not grant all of the requested permissions there's a chance that problems may occur in the prebuild, and in codespaces created from this prebuild. This is true even if the user who creates a codespace based on this prebuild _does_ grant all of the permissions when they are prompted to do so.
+プレビルド構成の `devcontainer.json` 構成ファイルで、他のリポジトリへのアクセス許可が必要であることが指定されている場合、リポジトリ管理者は、プレビルド構成を作成または更新するときに、これらのアクセス許可を認可するように求められます。 管理者が要求されたすべてのアクセス許可を付与していない場合、プレビルドと、このプレビルドから作った codespace で問題が発生する可能性があります。 これは、このプレビルドに基づいて codespace を作るユーザーが、すべてのアクセス許可を付与するように求められ、"付与した" 場合でも起こります。
-## Troubleshooting failed workflow runs for prebuilds
+## プレビルドに対するワークフロー実行が失敗した場合のトラブルシューティング
-### Increasing the {% data variables.product.prodname_actions %} spending limit
+### {% data variables.product.prodname_actions %} の使用制限を増やす
-Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+プレビルドは、{% data variables.product.prodname_actions %} を使用して作成および更新されます。 {% data variables.product.prodname_actions %} の分数をすべて使用し、使用制限に達した場合、プレビルド ワークフローは失敗します。 このような場合は、{% data variables.product.prodname_actions %} の使用制限を増やして、ワークフローが実行できるようにします。 詳しい情報については、「[{% data variables.product.prodname_actions %} の使用制限の管理](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)」を参照してください。
-### Authorizing access permissions
+### アクセス許可の承認
-If the `devcontainer.json` configuration file for a prebuild configuration is updated to specify that permissions for access to other repositories are required, and a repository administrator has not been prompted to authorize these permissions for the prebuild configuration, then the prebuild workflow may fail. Try updating the prebuild configuration, without making any changes. If, when you click **Update**, the authorization page is displayed, check that the requested permissions are appropriate and, if so, authorize the request. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" and "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)."
+プレビルド構成の `devcontainer.json` 構成ファイルが、他のリポジトリへのアクセス許可が必要であることを指定するように更新され、リポジトリ管理者がプレビルド構成にこれらのアクセス許可を認可するように求められなかった場合、プレビルド ワークフローが失敗する可能性があります。 何も変更せずに、プレビルド構成を更新してみてください。 **[更新]** をクリックして、認可ページが表示される場合は、要求されたアクセス許可が適切であることを確認し、適切であれば、要求を認可します。 詳しくは、「[プレビルドを管理する](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)」と「[codespace 内の他のリポジトリへのアクセスを管理する](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)」をご覧ください。
-If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
+プレビルド構成に対するワークフロー実行が失敗する場合は、調査の間、一時的にプレビルド構成を無効にすることができます。 詳細については、「[プレビルドの管理](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)」を参照してください。
-### Preventing out-of-date prebuilds being used
+### 古いプレビルドが使用されないようにする
-By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
+既定では、最新のプレビルド ワークフローが失敗した場合、リポジトリ、ブランチ、および `devcontainer.json` 構成ファイルの同じ組み合わせに対して以前のプレビルドが使用され、新しい codespace が作成されます。 この動作は、プレビルド最適化と呼ばれます。
-We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
+プレビルドの最適化を有効にしておくことをお勧めします。これは、最新のプレビルドが使用できない場合でも codespace を迅速に作成できるようにするためです。 ただし、リポジトリ管理者は、プレビルドの codespace が現在のブランチの状態の背後にあるという問題が発生した場合に、プレビルドの最適化を無効にすることができます。 プレビルドの最適化を無効にすると、最新のプレビルド ワークフローが失敗した場合、または現在実行中の場合、リポジトリ、ブランチ、`devcontainer.json` ファイルの関連する組み合わせの codespace がプレビルドなしで作成されます。
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
+1. 影響を受けるプレビルド構成の右側にある省略記号 ( **...** ) を選び、 **[編集]** をクリックします。
- 
-1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
+ ![[編集] が強調表示されているプレビルドの一覧のスクリーンショット](/assets/images/help/codespaces/edit-prebuild-configuration.png)
+1. [構成の編集] ページの下部までスクロールし、 **[詳細オプションの表示]** をクリックします。
- 
-1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
+ ![[詳細オプションの表示] が強調表示されているプレビルド構成ページのスクリーンショット](/assets/images/help/codespaces/show-advanced-options.png)
+1. 既定の設定を無効にする必要がある場合は、 **[プレビルドの最適化を無効にする]** を選びます。
- 
-1. To save your change, click **Update**.
+ ![詳細オプション セクションと [プレビルドの最適化を無効にする] 設定のスクリーンショット](/assets/images/help/codespaces/disable-prebuild-optimization.png)
+1. 変更を保存するには、 **[更新]** をクリックします。
-## Further reading
+## 参考資料
-- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
-- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
+- [プレビルドの構成](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)
+- [プレビルドの管理](/codespaces/prebuilding-your-codespaces/managing-prebuilds)
diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index e87056d558..8f7905ac45 100644
--- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -1,6 +1,6 @@
---
-title: 既定のコミュニティ正常性ファイルの作成
-intro: CONTRIBUTING や CODE_OF_CONDUCT など、デフォルトのコミュニティ健全性ファイルを作成できます。 デフォルトのファイルは、そのような種類の独自ファイルを持たないアカウントが所有するすべてのリポジトリに使用されます。
+title: Creating a default community health file
+intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
redirect_from:
- /articles/creating-a-default-community-health-file-for-your-organization
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
@@ -12,41 +12,46 @@ versions:
topics:
- Community
shortTitle: Community health file
-ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145117637'
---
-## デフォルトのコミュニティ健全性ファイルについて
-既定のコミュニティ正常性ファイルは、`.github` という名前のパブリック リポジトリ、リポジトリのルート、または `docs` や `.github` フォルダーに追加できます。
+## About default community health files
-{% data variables.product.product_name %} は、次のいずれかの場所にその種類の独自ファイルを持たないアカウントが所有するリポジトリのデフォルトファイルを使用および表示します。
-- リポジトリのルート
-- `.github` フォルダー
-- `docs` フォルダー
+You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders.
-たとえば、独自の CONTRIBUTING ファイルを持たないリポジトリで Issue またはプルリクエストを作成すると、デフォルトの CONTRIBUTING ファイルへのリンクが表示されます。 リポジトリの独自の `.github/ISSUE_TEMPLATE` フォルダーにファイルがある場合{% ifversion fpt or ghes or ghec %} (Issue テンプレートや *config.yml* ファイルを含む){% endif %}、既定の `.github/ISSUE_TEMPLATE` フォルダーの内容は使われません。
+{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
+- the root of the repository
+- the `.github` folder
+- the `docs` folder
-既定のファイルは、`.github` リポジトリにのみ格納されるため、個別のリポジトリのクローン、パッケージ、ダウンロードには含まれません。
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
-## サポートされているファイルの種類
+Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
-次のコミュニティ正常性ファイルの既定のものを、Organization {% ifversion fpt or ghes or ghec %} または個人アカウント {% endif %} に作成できます。
+## Supported file types
-コミュニティ正常性ファイル | 説明 --- | ---{% ifversion fpt or ghec %} *CODE_OF_CONDUCT.md* | CODE_OF_CONDUCT ファイルでは、コミュニティに参加する方法の標準が定義されています。 詳細については、「[プロジェクトへの行動規範の追加](/articles/adding-a-code-of-conduct-to-your-project/)」を参照してください。{% endif %} *CONTRIBUTING.md* | CONTRIBUTING ファイルでは、プロジェクトに投稿する方法が示されています。 詳細については、「[リポジトリ コントリビューターのためのガイドラインを定める](/articles/setting-guidelines-for-repository-contributors/)」を参照してください。{% ifversion fpt or ghec %} *FUNDING.yml* | FUNDING ファイルでは、リポジトリにスポンサー ボタンが表示されて、オープンソース プロジェクトの資金調達オプションの表示が増えます。 詳細については、「[リポジトリにスポンサー ボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照してください。{% endif %} Issue と pull request のテンプレート{% ifversion fpt or ghes or ghec %}および *config.yml*{% endif %} | Issue と pull request のテンプレートでは、自分のリポジトリに共同作成者が Issue や pull request を開くときに含めてほしい情報をカスタマイズおよび標準化します。 詳細については、「[Issue とプル リクエストのテンプレートについて](/articles/about-issue-and-pull-request-templates/)」を参照してください。{% ifversion fpt or ghes or ghec %} *SECURITY.md* | SECURITY ファイルでは、プロジェクトでセキュリティ脆弱性を報告する方法の手順を示します。 詳細については、「[リポジトリにセキュリティ ポリシーを追加する](/code-security/getting-started/adding-a-security-policy-to-your-repository)」を参照してください。{% endif %} *SUPPORT.md* | SUPPORT ファイルでは、プロジェクトに関するヘルプを得る方法がわかるようにします。 詳細については、「[プロジェクトへのサポート リソースの追加](/articles/adding-support-resources-to-your-project/)」を参照してください。
+You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
-デフォルトのライセンスファイルを作成することはできません。 ライセンスファイルは、プロジェクトのクローン時、パッケージ時、またはダウンロード時に含められるよう、個々のリポジトリに追加する必要があります。
+Community health file | Description
+--- | ---{% ifversion fpt or ghec %}
+*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
+*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion discussion-category-forms %}
+Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[Creating discussion category forms](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
+*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
+Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes or ghec %}
+*SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
-## デフォルトのファイル用にリポジトリを作成
+You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
+
+## Creating a repository for default files
{% data reusables.repositories.create_new %}
-2. **[所有者]** ドロップダウン メニューを使用し、既定のファイルを作成する Organization {% ifversion fpt or ghes or ghec %} または個人アカウント {% endif %} を選択します。
- ![[所有者] ドロップダウン メニュー](/assets/images/help/repository/create-repository-owner.png)
-3. リポジトリの名前として「 **.github**」と入力し、必要に応じて説明を入力します。
- 
-4. リポジトリの状態が **[パブリック]** に設定されていることを確認します (既定のファイルのリポジトリをプライベートにすることはできません)。
-  {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
-7. リポジトリの中に、サポートされているコミュニティ健全性ファイルの 1 つを作成します。 Issue テンプレート{% ifversion fpt or ghes or ghec %}とその構成ファイル{% endif %}は、`.github/ISSUE_TEMPLATE` という名前のフォルダーに存在する必要があります。 他のすべてのサポートされるファイルは、リポジトリのルート、`.github` フォルダー、または `docs` フォルダーに置くことができます。 詳細については、「[新しいファイルの作成](/articles/creating-new-files/)」を参照してください。
+2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
+ 
+3. Type **.github** as the name for your repository, and an optional description.
+ 
+4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+ 
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
index 44aa07505c..e40c35ff92 100644
--- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
+++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a pull request template for your repository
-intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.'
+title: リポジトリ用のプルリクエストテンプレートの作成
+intro: リポジトリにプルリクエストのテンプレートを追加すると、プロジェクトのコントリビューターはプルリクエストの本体にテンプレートの内容を自動的に見ることになります。
redirect_from:
- /articles/creating-a-pull-request-template-for-your-repository
- /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
@@ -12,41 +12,44 @@ versions:
topics:
- Community
shortTitle: Create a PR template
+ms.openlocfilehash: fa4d3cf78b63af147c85b8f6d77d7cca74e3853a
+ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190409'
---
+詳細については、「[Issue と pull request テンプレートについて](/articles/about-issue-and-pull-request-templates)」を参照してください。
-For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
-
-You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
+サポートしているどのフォルダーでも *PULL_REQUEST_TEMPLATE/* サブディレクトリを作成し、pull request テンプレートを複数含めることができます。また、`template` クエリ パラメーターで pull request の本文に使用するテンプレートを指定できます。 詳細については、「[クエリ パラメーターを使用して pull request を作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)」を参照してください。
{% ifversion fpt or ghes or ghec %}
-You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+ご自分の Organization {% ifversion fpt or ghes or ghec %}または個人用アカウント{% endif %}向けに既定の pull request を作成することができます。 詳細については、「[既定のコミュニティ正常性ファイルの作成](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。
{% endif %}
-## Adding a pull request template
+## プルリクエストテンプレートの追加
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field:
- - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`.
- 
- - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`.
- 
- - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`.
- 
- - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
- 
-4. In the body of the new file, add your pull request template. This could include:
- - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository.
- - A description of the changes proposed in the pull request.
- - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes.
-{% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. ファイル名フィールドで:
+ - pull request テンプレートをリポジトリのルート ディレクトリで表示するには、pull request テンプレートに `pull_request_template.md` という名前を付けます。
+ 
+ - pull request テンプレートをリポジトリの `docs` ディレクトリで表示するには、pull request テンプレートに `docs/pull_request_template.md` という名前を付けます。
+ 
+ - ファイルを非表示のディレクトリに格納するには、pull request テンプレートを `.github/pull_request_template.md` という名前にします。
+ 
+ - pull request テンプレートを複数作成し、`template` クエリ パラメーターを使用して pull request の本文を埋めるテンプレートを指定するには、 *.github/PULL_REQUEST_TEMPLATE/* と入力し、続けてお使いの pull request テンプレートの名前を入力します。 たとえば、「 `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md` 」のように入力します。 ルートまたは `docs/` ディレクトリ内の `PULL_REQUEST_TEMPLATE` サブディレクトリに複数の pull request テンプレートを格納することもできます。 詳細については、「[クエリ パラメーターを使用して pull request を作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)」を参照してください。
+ 
+4. 新しいファイルの本文にプルリクエストテンプレートを追加します。 そこに盛り込むべき項目として、以下のようなものがあります:
+ - ご自分のリポジトリ内の [関連する Issue への参照](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)。
+ - プルリクエストで提案された変更の説明。
+ - レビューを行っている提案された変更の責任を負う個人またはチームの [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)。
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} テンプレートがリポジトリの既定のブランチにマージされると、コラボレーターがテンプレートを使用できるようになります。
{% data reusables.files.propose_new_file %}
-## Further reading
+## 参考資料
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating a pull request](/articles/creating-a-pull-request)"
+- [Issue と pull request テンプレートについて](/articles/about-issue-and-pull-request-templates)
+- [クエリ パラメーターを使用した Issue および pull request の自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)
+- [pull request の作成方法](/articles/creating-a-pull-request)
diff --git a/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md
index db0162551d..44f65efe23 100644
--- a/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md
+++ b/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -1,6 +1,6 @@
---
-title: About apps
-intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}'
+title: アプリケーションについて
+intro: '{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API でインテグレーションを構築し、柔軟性を強化して自分のワークフローの摩擦を軽減できます。{% ifversion fpt or ghec %}また、[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) で他のユーザーとインテグレーションを共有することも可能です。{% endif %}'
redirect_from:
- /apps/building-integrationssetting-up-a-new-integration
- /apps/building-integrations
@@ -14,93 +14,99 @@ versions:
ghec: '*'
topics:
- GitHub Apps
+ms.openlocfilehash: a66af14f6047b2aff435ac4ac8dc83d7a1181e92
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107358'
---
-Apps on {% data variables.product.prodname_dotcom %} allow you to automate and improve your workflow. You can build apps to improve your workflow.{% ifversion fpt or ghec %} You can also share or sell apps in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). To learn how to list an app on {% data variables.product.prodname_marketplace %}, see "[Getting started with GitHub Marketplace](/marketplace/getting-started/)."{% endif %}
+{% data variables.product.prodname_dotcom %} のアプリケーションを使用すると、ワークフローを自動化し改善できます。 アプリをビルドしてワークフローを改善できます。{% ifversion fpt or ghec %} また、[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) でアプリを共有または販売することもできます。 {% data variables.product.prodname_marketplace %} にアプリを掲載する方法については、[GitHub Marketplace の概要](/marketplace/getting-started/)を参照してください。{% endif %}
-{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)."
+{% data reusables.marketplace.github_apps_preferred %}。ただし、GitHub は {% data variables.product.prodname_oauth_apps %} と {% data variables.product.prodname_github_apps %} の両方をサポートしています。 アプリの種類の選択については、「[GitHub App と OAuth App の違い](/developers/apps/differences-between-github-apps-and-oauth-apps)」を参照してください。
{% data reusables.apps.general-apps-restrictions %}
-For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+{% data variables.product.prodname_github_app %} をビルドする手順については、「[最初の {% data variables.product.prodname_github_app %} のビルド](/apps/building-your-first-github-app)」を参照してください。
-## About {% data variables.product.prodname_github_apps %}
+## {% data variables.product.prodname_github_apps %} について
-{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user.
+{% data variables.product.prodname_github_apps %} は GitHub の中でも主役級の存在です。 {% data variables.product.prodname_github_app %} は独自で動作し、独自の ID を使用して API 経由で直接アクションを実行します。つまり、ボットやサービスアカウントを別途維持する必要がありません。
-{% data variables.product.prodname_github_apps %} can be installed directly on organizations and personal accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository.
+{% data variables.product.prodname_github_apps %} は、Organization や個人アカウントに直接インストールでき、特定のリポジトリへのアクセス権を付与できます。 精細なアクセス権限が付いており、webhook が組み込まれています。 {% data variables.product.prodname_github_app %} をセットアップする際、アクセスさせるリポジトリを選択できます。 たとえば、リポジトリに問題を書き込み、リポジトリ`MyGitHub`のみに`octocat`_書_ き込むアプリを`octocat`設定できます。 {% data variables.product.prodname_github_app %} をインストールするには、Organization のオーナーであるか、リポジトリで管理者権限を持っている必要があります。
{% data reusables.apps.app_manager_role %}
-{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+{% data variables.product.prodname_github_apps %} は、どこかにホストする必要があるアプリケーションです。 サーバーとホスティングに関する詳しい手順については、「[最初の {% data variables.product.prodname_github_app %} のビルド](/apps/building-your-first-github-app)」をご覧ください。
-To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs.
+ワークフローを改善するため、複数のスクリプトまたはアプリケーション全体を含む {% data variables.product.prodname_github_app %} を作成し、それをその他の数多くのツールと接続できます。 たとえば、{% data variables.product.prodname_github_apps %} を GitHub、Slack、その他の社内アプリケーション、電子メールプログラム、その他の API などに接続できます。
-Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}:
+{% data variables.product.prodname_github_apps %} を作成する際は、以下に気を付けてください。
{% ifversion fpt or ghec %}
* {% data reusables.apps.maximum-github-apps-allowed %} {% endif %}
-* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %}
+* {% data variables.product.prodname_github_app %} は、(アプリが[ユーザーからサーバーへの](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)トークンを使用している場合を除き) ユーザーに依存しないアクションを実行する必要があります。 {% data reusables.apps.expiring_user_authorization_tokens %}
-* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories.
-* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization.
-* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can.
-* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things.
-* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %}
+* {% data variables.product.prodname_github_app %} は、必ず特定のリポジトリと統合するようにしてください。
+* {% data variables.product.prodname_github_app %} は個人アカウントまたは Organization に接続する必要があります。
+* ユーザができる全てのことを {% data variables.product.prodname_github_app %} が知り、行えるとは思わないでください。
+* 単に「GitHub でログイン」するサービスが必要な場合は、{% data variables.product.prodname_github_app %} を使用しないでください。 ただし、{% data variables.product.prodname_github_app %} では [、ユーザー識別フロー](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) を使用してユーザーをログイン _させ、_ 他の操作を実行できます。
+* GitHub ユーザーとして動作し、ユーザーが実行できることをすべて実行したい _だけ_ の場合は、{% data variables.product.prodname_github_app %} をビルドしないでください。{% ifversion fpt or ghec %}
* {% data reusables.apps.general-apps-restrictions %}{% endif %}
-To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %}
+{% data variables.product.prodname_github_apps %} アプリケーションの開発を始めるには、「[{% data variables.product.prodname_github_app %} の作成](/apps/building-github-apps/creating-a-github-app/)」から取りかかってください。{% ifversion fpt or ghec %}構成済みの {% data variables.product.prodname_github_apps %} を作成できる {% data variables.product.prodname_github_app %} マニフェストの使い方については、「[マニフェストからの {% data variables.product.prodname_github_apps %} の作成](/apps/building-github-apps/creating-github-apps-from-a-manifest/)」を参照してください。{% endif %}
-## About {% data variables.product.prodname_oauth_apps %}
+## {% data variables.product.prodname_oauth_apps %} について
-OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time.
+OAuth2 は、外部アプリケーションがパスワードにアクセスすることなく、ユーザの {% data variables.product.prodname_dotcom %} アカウントの個人情報にアクセスする承認を要求できるようにするプロトコルです。 これは Basic 認証よりも好ましい方法です。なぜなら、トークンは特定の種類のデータに限定でき、ユーザがいつでも取り消すことができるからです。
{% data reusables.apps.deletes_ssh_keys %}
-An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access.
+{% data variables.product.prodname_oauth_app %} は、アプリケーションにアクセス権を付与するユーザを認証するため、アイデンティティプロバイダとして {% data variables.product.prodname_dotcom %} を使用します。 つまり、ユーザーが {% data variables.product.prodname_oauth_app %} アクセスを許可すると、ユーザーは自分のアカウントでアクセスできる _すべての_ リポジトリにアクセス許可を付与します。また、サードパーティのアクセスをブロックしていない組織にもアクセス許可を付与します。
-Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere.
+単純なスクリプトで処理できるよりも複雑なプロセスを作成する場合、{% data variables.product.prodname_oauth_app %} を構築するのは良い選択肢です。 {% data variables.product.prodname_oauth_apps %} は、どこかにホストする必要があるアプリケーションであることに注意してください。
-Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}:
+{% data variables.product.prodname_oauth_apps %} を作成する際は、以下に気を付けてください。
{% ifversion fpt or ghec %}
* {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %}
-* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications).
-* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user.
-* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories.
-* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %}
+* {% data variables.product.prodname_oauth_app %} は、{% data variables.product.prodname_dotcom %} 全体にわたって、常に認証された {% data variables.product.prodname_dotcom %} ユーザとして振る舞う必要があります (たとえば、ユーザ通知を行う場合など)。
+* 認証されたユーザに対して「{% data variables.product.prodname_dotcom %} でログイン」を有効化することにより、{% data variables.product.prodname_oauth_app %} をアイデンティティプロバイダとして使用できます。
+* 単一のリポジトリで動作するアプリケーションが必要な場合、{% data variables.product.prodname_oauth_app %} を構築しないでください。 OAuth スコープを `repo` 使用すると、{% data variables.product.prodname_oauth_apps %} は、認証 _されたすべての_ ユーザーのリポジトリで動作できます。
+* Team や企業を代理するアプリケーションとして {% data variables.product.prodname_oauth_app %} を構築しないでください。 {% data variables.product.prodname_oauth_apps %} は単一のユーザとして認証を行うので、ある人が {% data variables.product.prodname_oauth_app %} を会社が使用するものとして作成し、その人が会社を辞めた場合は、他の人がアクセスできなくなります。{% ifversion fpt or ghec %}
* {% data reusables.apps.oauth-apps-restrictions %}{% endif %}
-For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)."
+{% data variables.product.prodname_oauth_apps %} について詳しくは、「[{% data variables.product.prodname_oauth_app %} の作成](/apps/building-oauth-apps/creating-an-oauth-app/)」および「[アプリの登録](/rest/guides/basics-of-authentication#registering-your-app)」をご覧ください。
-## {% data variables.product.pat_generic_caps %}s
+## {% data variables.product.pat_generic_caps %}
-A [{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A {% data variables.product.pat_generic %} is also similar to a password, but you can have many of them and you can revoke access to each one at any time.
+[{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/)は、[スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)を使用してそのアクセス許可を指定できる点で [OAuth トークン](/apps/building-oauth-apps/authorizing-oauth-apps/)と同様に機能する文字の文字列です。 また、{% data variables.product.pat_generic %}はパスワードとも似ています。ただし、個人アクセストークンは複数所有でき、それぞれのアクセス権をいつでも取り消すことができます。
-As an example, you can enable a {% data variables.product.pat_generic %} to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the {% data variables.product.pat_generic %} to authenticate. You can store the {% data variables.product.pat_generic %} as an environment variable to avoid typing it every time you use it.
+たとえば、{% data variables.product.pat_generic %}にリポジトリへの書き込みをできるように設定できます。 そして、リポジトリで [issue を作成する](/rest/reference/issues#create-an-issue) cURL コマンドを実行するかスクリプトを記述する場合、{% data variables.product.pat_generic %}を渡して認証します。 {% data variables.product.pat_generic %}を環境変数として保存することで、使用のたびに入力することを避けることができます。
-Keep these ideas in mind when using {% data variables.product.pat_generic %}s:
+{% data variables.product.pat_generic %}を使用する場合は、次の点に注意してください。
-* Remember to use this token to represent yourself only.
-* You can perform one-off cURL requests.
-* You can run personal scripts.
-* Don't set up a script for your whole team or company to use.
-* Don't set up a shared personal account to act as a bot user.
-* Grant your token the minimal privileges it needs.
-* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.
+* トークンは自分自身のみを表すものとして使用してください。
+* 1 回限りの cURL リクエストを実行できます。
+* 個人用のスクリプトを実行できます。
+* Team や会社全体が使用するスクリプトは設定しないでください。
+* ボット ユーザーとして動作する共有ユーザー アカウントは設定しないでください。
+* トークンに必要な最小限の特権を付与します。
+* 情報をセキュリティで保護するために、{% data variables.product.pat_generic %}の有効期限を設定します。
-## Determining which integration to build
+## 構築すべきインテグレーションを決定する
-Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use {% data variables.product.pat_generic %}s, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration.
+インテグレーションの作成に取りかかる前に、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API を使用したアクセス、認証、対話に最善の方法を見極める必要があります。 統合で{% data variables.product.pat_generic %}、{% data variables.product.prodname_github_apps %}、{% data variables.product.prodname_oauth_apps %} のどれを使用するかを決める際の考慮事項を以下の画像に示しています。
-
+
-Consider these questions about how your integration needs to behave and what it needs to access:
+インテグレーションがどう振る舞うべきか、何にアクセスできるべきかについては、以下の質問を検討してください。
-* Will my integration act only as me, or will it act more like an application?
-* Do I want it to act independently of me as its own entity?
-* Will it access everything that I can access, or do I want to limit its access?
-* Is it simple or complex? For example, {% data variables.product.pat_generic %}s are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting.
+* インテグレーションは自分自身としてのみ振る舞うのか、それともアプリケーションのように振る舞うのか?
+* 独自のエンティティとして、自分から独立して動作させるのか?
+* 自分がアクセスできるもの全てにアクセスするのか、それともアクセスを制限するのか?
+* 単純か、それとも複雑か? たとえば、{% data variables.product.pat_generic %}は単純なスクリプトや cURL に適し、{% data variables.product.prodname_oauth_app %} はより複雑なスクリプトを処理できます。
-## Requesting support
+## サポートのリクエスト
{% data reusables.support.help_resources %}
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
index 7ecfa4945b..3bcb0dabf9 100644
--- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,6 +9,8 @@ children:
- /managing-categories-for-discussions
- /moderating-discussions
- /viewing-insights-for-your-discussions
+ - /creating-discussion-category-forms
+ - /syntax-for-discussion-category-forms
ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
ms.translationtype: HT
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index 302f14adae..256d1e97e2 100644
--- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -1,215 +1,201 @@
---
-title: Managing discussions
-intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
+title: ディスカッションを管理する
+intro: ディスカッションを分類、スポットライト、転送、または削除できます。
permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
versions:
feature: discussions
shortTitle: Manage discussions
redirect_from:
- /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
+ms.openlocfilehash: e5e1474648973c90d16e8998db18518331233aa3
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164340'
---
+## ディスカッションの管理について
+{% data reusables.discussions.about-discussions %}詳細については、「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
-## About management of discussions
+組織所有者は、組織が所有するリポジトリのディスカッションを作成するために必要なアクセス許可を選択できます。 同様に、組織のディスカッションを作成するために必要なアクセス許可を選ぶために、組織所有者はソース リポジトリで必要なアクセス許可を変更できます。 詳細については、「[組織内のリポジトリのディスカッション作成を管理する](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)」を参照してください。
-{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+ディスカッションのメンテナとして、コミュニティリソースを作成して、プロジェクト全体の目標に沿ったディスカッションを促し、コラボレータのための親しみやすいオープンフォーラムを維持できます。 コラボレーターが従う{% ifversion fpt or ghec %}行動規範または{% endif %}コントリビューション ガイドラインを作成することは、協力的で生産的なフォーラムを促進するのに役立ちます。 コミュニティ リソースの作成について詳しくは、{% ifversion fpt or ghec %}「[プロジェクトへの行動規範の追加](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)」と{% endif %}「[リポジトリ コントリビューターのためのガイドラインを定める](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)」を参照してください。
-Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."
+すぐに取り組むことができるアイデアやバグがディスカッションから生まれた場合は、ディスカッションから新しい issue を作成できます。 詳細については、「[Issue の作成](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)」を参照してください。
-As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, 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 guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+リポジトリまたは組織のディスカッション一覧の先頭に、ディスカッションをピン留めできます。 {% ifversion discussions-category-specific-pins %}ディスカッションを特定のカテゴリにピン留めすることもできます。{% endif %}詳細については、「[ディスカッションをピン留めする](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)」を参照してください。
-When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
-
-You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
-
-For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
+健全なディスカッションの促進については、「[コメントおよび会話をモデレートする](/communities/moderating-comments-and-conversations)」を参照してください。
{% data reusables.discussions.you-can-label-discussions %}
-## Prerequisites
+## 前提条件
-To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)."
+リポジトリ内のディスカッションを管理するには、そのリポジトリに対して {% data variables.product.prodname_discussions %} を有効にする必要があります。 詳細については、「[リポジトリの {% data variables.product.prodname_discussions %} を有効化または無効化する](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)」を参照してください。
-To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+組織内のディスカッションを管理するには、その組織に対して {% data variables.product.prodname_discussions %} を有効にする必要があります。 詳細については、「[リポジトリの {% data variables.product.prodname_discussions %} を有効化または無効化する](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)」を参照してください。
-## Changing the category for a discussion
+## ディスカッションのカテゴリを変更する
-You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+ディスカッションを分類して、コミュニティメンバーが関連するディスカッションを見つけやすくすることができます。 詳細については、「[ディスカッションのカテゴリの管理](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)」を参照してください。
-You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category.
+ディスカッションを別のカテゴリに移動することもできます。 ディスカッションを投票カテゴリに移動する、またはそこから移動することはできません。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 右サイドバーにある [カテゴリ] の右の {% octicon "gear" aria-label="The gear icon" %} をクリックします。
- 
+ ![歯車アイコンが表示された [Category] のスクリーンショット](/assets/images/help/discussions/category-in-sidebar.png)
-1. Click a category.
+1. カテゴリをクリックします。
- 
+ ![[Change category] ドロップダウン メニューのスクリーンショット](/assets/images/help/discussions/change-category-drop-down.png)
-## Pinning a discussion
+## ディスカッションをピン留めする
-{% ifversion discussions-category-specific-pins %}
-You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
+{% ifversion discussions-category-specific-pins %}リポジトリまたは組織のディスカッション一覧の上にディスカッションをピン留めできます。 また、ディスカッションを特定のカテゴリにピン止めすることもできます。 グローバルにピン留めされたディスカッションは、特定のカテゴリにピン留めされたディスカッションに加えて表示されます。
-This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
+グローバルにピン留めされたディスカッションと、[Ideas] カテゴリにピン留めされたディスカッションがある場合の外観は、次のようになります。
-
+![グローバルにピン留めされたディスカッションと [Ideas] カテゴリにピン留めされたディスカッションのスクリーンショット](/assets/images/help/discussions/overview-pinned-discussions.png)
-### Pinning a discussion globally
+### ディスカッションをグローバルにピン留めする
{% endif %}
-You can pin up to four important discussions above the list of discussions for the repository or organization.
+リポジトリまたは組織のディスカッション一覧の上に、最大 4 つの重要なディスカッションをピン留めできます。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 右サイドバーにある {% octicon "pin" aria-label="The pin icon" %} **[Pin discussion]\(ディスカッションのピン留め\)** をクリックします。
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ ![ディスカッションの右側のサイド バーにある [Pin discussion] オプションのスクリーンショット](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png){% else %}
- {% endif %}
+ ![ディスカッションの右側のサイド バーにある [Pin discussion] オプションのスクリーンショット](/assets/images/help/discussions/click-pin-discussion.png){% endif %}
-1. Optionally, customize the look of the pinned discussion.
+1. 必要に応じて、ピン留めされたディスカッションの外観をカスタマイズします。
- 
+ 
-1. Click **Pin discussion**.
+1. **[Pin discussion]\(ディスカッションのピン留め\)** をクリックします。
- 
+ ![ピン留めされたディスカッションのカスタマイズ オプションの下にある [Pin discussion] ボタンのスクリーンショット](/assets/images/help/discussions/click-pin-discussion-button.png)
{% ifversion discussions-category-specific-pins %}
-### Pinning a discussion to a category
+### ディスカッションをカテゴリにピン留めする
-You can pin up to four important discussions above the list of discussions in a specific category.
+特定のカテゴリのディスカッション一覧の上に、最大 4 つの重要なディスカッションをピン留めできます。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 右側のサイド バーにある {% octicon "pin" aria-label="The pin icon" %} **[Pin discussion to CATEGORY]** をクリックします。
- 
+ ![ディスカッションの右側のサイド バーにある [Pin discussion to CATEGORY] オプションのスクリーンショット](/assets/images/help/discussions/pin-discussion-to-category.png)
-2. To confirm, click **Pin to CATEGORY**.
+2. 確定するには、 **[Pin to CATEGORY]** をクリックします。
- 
+ ![[Pin discussion to CATEGORY] モーダルのスクリーンショット](/assets/images/help/discussions/pin-discussion-to-category-modal.png)
{% endif %}
-## Editing a pinned discussion
+## ピン留めされたディスカッションを編集する
-Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+ピン留めされたディスカッションを編集しても、ディスカッションのカテゴリは変更されません。 詳細については、「[ディスカッションのカテゴリの管理](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)」を参照してください。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 右サイドバーにある {% octicon "pencil" aria-label="The pencil icon" %} **[Edit pinned discussion]\(ピン留めされたディスカッションの編集\)** をクリックします。
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+ ![ディスカッションの右側のサイド バーにある [Edit pinned discussion] オプションのスクリーンショット](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png) {% else %}
- {% endif %}
+ ![ディスカッションの右側のサイド バーにある [Edit pinned discussion] オプションのスクリーンショット](/assets/images/help/discussions/click-edit-pinned-discussion.png){% endif %}
-1. Customize the look of the pinned discussion.
+1. ピン留めされたディスカッションの外観をカスタマイズします。
- 
+ 
-1. Click **Pin discussion**.
+1. **[Pin discussion]\(ディスカッションのピン留め\)** をクリックします。
- 
+ ![ピン留めされたディスカッションのカスタマイズ オプションの下にある [Pin discussion] ボタンのスクリーンショット](/assets/images/help/discussions/click-pin-discussion-button.png)
-## Unpinning a discussion
+## ディスカッションをピン留め解除する
{% ifversion discussions-category-specific-pins %}
-You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
+リポジトリまたは組織のディスカッション一覧から、または特定のカテゴリのディスカッション一覧から、ディスカッションのピン留めを解除できます。
-### Unpinning a globally pinned discussion
+### グローバルにピン留めされたディスカッションのピン留めを解除する
-You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
+グローバルにピン留めされたディスカッションのピン留めを解除できます。 これによってディスカッションは削除されませんが、ディスカッション一覧の上には表示されなくなります。
{% endif %}
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 右サイドバーにある {% octicon "pin" aria-label="The pin icon" %} **[Unpin discussion]\(ディスカッションのピン留めを外す\)** をクリックします。
- 
+ ![ディスカッションの右側のサイド バーにある [Unpin discussion] オプションのスクリーンショット](/assets/images/help/discussions/click-unpin-discussion.png)
-1. Read the warning, then click **Unpin discussion**.
+1. 警告を読み、 **[Unpin discussion]\(ディスカッションのピン留めを外す\)** をクリックします。
- 
+ ![モーダルの警告の下にある [Unpin discussion] ボタンのスクリーンショット](/assets/images/help/discussions/click-unpin-discussion-button.png)
{% ifversion discussions-category-specific-pins %}
-### Unpinning a discussion from a category
+### カテゴリからディスカッションのピン留めを解除する
-You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
+特定のカテゴリにピン留めされたディスカッションのピン留めを解除できます。 これによってディスカッションは削除されませんが、カテゴリの上部には表示されなくなります。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 右側のサイド バーにある {% octicon "pin" aria-label="The pin icon" %} **[Unpin discussion from this category]** をクリックします。
- 
+ ![ディスカッションの右側のサイド バーにある [Unpin discussion from this category] オプションのスクリーンショット](/assets/images/help/discussions/unpin-discussion-from-category.png)
-1. Read the warning, then click **Unpin from this category**.
+1. 警告を読んでから、 **[Unpin from this category]** をクリックします。
- 
+ ![[Unpin this discussion from this category] モーダルの [Unpin from this category] ボタンのスクリーンショット](/assets/images/help/discussions/unpin-discussion-from-category-modal.png)
{% endif %}
-## Transferring a discussion
+## ディスカッションを移譲する
-To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
+ディスカッションを移譲するには、ディスカッションを移譲するリポジトリにディスカッションを作成する権限が必要です。 ディスカッションを組織に移譲する場合、組織のディスカッション用ソース リポジトリ内にディスカッションを作成するアクセス許可を持っている必要があります。 ディスカッションを移譲できるのは、同じユーザーまたは組織アカウントが所有するリポジトリ間のみです。 プライベート{% ifversion ghec or ghes %}または内部{% endif %}リポジトリからパブリック リポジトリにディスカッションを移譲することはできません。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 右側のサイド バーで、{% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %} **[Transfer this discussion]** {% else %} **[Transfer discussion]** {% endif %} をクリックします。
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+ ![ディスカッションの右側のサイド バーにある [Transfer discussion] オプションのスクリーンショット](/assets/images/help/discussions/transfer-discussion-with-category-pin.png) {% else %}
- {% endif %}
+ ![ディスカッションの右側のサイド バーにある [Transfer discussion] オプションのスクリーンショット](/assets/images/help/discussions/click-transfer-discussion.png){% endif %}
-1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
+1. **[Choose a repository]\(リポジトリの選択\)** ドロップダウンを選び、ディスカッションの移譲先のリポジトリをクリックします。 組織にディスカッションを移譲する場合、組織のディスカッション用ソース リポジトリを選びます。
- 
+ ![[Choose a repository] ドロップダウン、[Find a repository] 検索フィールド、リスト内のリポジトリのスクリーンショット](/assets/images/help/discussions/use-choose-a-repository-drop-down.png)
-1. Click **Transfer discussion**.
+1. **[Transfer discussion]\(ディスカッションの移譲\)** をクリックします。
- 
+ ![[Transfer discussion] ボタンのスクリーンショット](/assets/images/help/discussions/click-transfer-discussion-button.png)
-## Deleting a discussion
+## ディスカッションを削除する
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 右サイドバーにある {% octicon "trash" aria-label="The trash arrow icon" %} **[Delete discussion]\(ディスカッションの削除\)** をクリックします。
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ ![ディスカッションの右側のサイド バーにある [Delete discussion] オプションのスクリーンショット](/assets/images/help/discussions/delete-discussion-with-category-pins.png){% else %}
- {% endif %}
+ ![ディスカッションの右側のサイド バーにある [Delete discussion] オプションのスクリーンショット](/assets/images/help/discussions/click-delete-discussion.png){% endif %}
-1. Read the warning, then click **Delete this discussion**.
+1. 警告を読み、 **[Delete this discussion]\(このディスカッションを削除する\)** をクリックします。
- 
+ ![モーダルの警告の下にある [Delete this discussion] ボタンのスクリーンショット](/assets/images/help/discussions/click-delete-this-discussion-button.png)
-## Converting issues based on labels
+## ラベルに基づいて Issue を変換する
-You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.
+同じラベルのすべての Issue をまとめてディスカッションに変換できます。 このラベルの今後の Issue も、設定したディスカッションとカテゴリに自動的に変換されます。
-1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository.
-{% data reusables.repositories.sidebar-issues %}
-{% data reusables.project-management.labels %}
-1. Next to the label you want to convert to issues, click **Convert issues**.
-1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
-1. Click **I understand, convert this issue to a discussion**.
+1. {% data variables.location.product_location %} 上で、リポジトリのメイン ページ (組織のディスカッションの場合はソース リポジトリ) に移動します。
+{% data reusables.repositories.sidebar-issues %} {% data reusables.project-management.labels %}
+1. issue に変換するラベルの横にある **[Convert issues]\(issue の変換\)** をクリックします。
+1. **[カテゴリの選択]** ドロップダウン メニューを選択し、ディスカッションのカテゴリをクリックします。
+1. **[わかりました、この Issue をディスカッションに変換します]** をクリックします。
diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index ffef0a4aba..cb5cd7c4e8 100644
--- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -1,78 +1,84 @@
---
-title: Create a group assignment
-intro: You can create a collaborative assignment for teams of students who participate in your course.
+title: グループ課題の作成
+intro: コースに参加している学生のTeamのために、共同課題を作成できます。
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
redirect_from:
- /education/manage-coursework-with-github-classroom/create-group-assignments
- /education/manage-coursework-with-github-classroom/create-a-group-assignment
+ms.openlocfilehash: 71c5f5eaf97ba58e25921c1e2be6fc638550dfa8
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179761'
---
-## About group assignments
+## グループ課題について
-{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+{% data reusables.classroom.assignments-group-definition %}学生は、プロフェッショナルな開発者チームと同じように、共有リポジトリでグループ課題に協力して取り組むことができます。
-When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+グループ課題を受け入れた学生は、新しいTeamを作成するか、既存のTeamに参加できます。 {% data variables.product.prodname_classroom %}は、課題のためのTeamをセットとして保存します。 課題を作成する際、特定の課題に対するTeamのセットに名前を付けることができます。また、後の課題でTeamのセットを再利用できます。
{% data reusables.classroom.classroom-creates-group-repositories %}
{% data reusables.classroom.about-assignments %}
-You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+1つの課題に取り組むチームの数と、各Teamのメンバーの数を決めることができます。 学生が課題ために作成する各グループは、{% data variables.product.product_name %}のOrganization内のTeamです。 Teamの可視性はシークレットとなります。 {% data variables.product.product_name %}上で作成したTeamは、{% data variables.product.prodname_classroom %}では表示されません。 詳細については、「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
-For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+グループ課題の作成のビデオ デモについては、「[{% data variables.product.prodname_classroom %} のセットアップの基本](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)」を参照してください。
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## 前提条件
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## 課題を作成する
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## 課題の基本情報をセットアップする
-Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+課題に名前を付け、期限を設定するか、Teamを定義するかを決定し、課題リポジトリの可視性を選択します。
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Defining teams for an assignment](#defining-teams-for-an-assignment)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [課題に名前を付ける](#naming-an-assignment)
+- [課題に期限を設定する](#assigning-a-deadline-for-an-assignment)
+- [課題のタイプを選択する](#choosing-an-assignment-type)
+- [課題の Team を定義する](#defining-teams-for-an-assignment)
+- [課題リポジトリの可視性を選択する](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### 課題に名前を付ける
-For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+グループ課題では、{% data variables.product.prodname_classroom %}はリポジトリのプレフィックスとTeamの名前から、リポジトリに名前を付けます。 デフォルトでは、リポジトリのプレフィックスが課題のタイトルとなります。 たとえば、課題に "assignment-1" という名前を付けて、{% data variables.product.product_name %} での Team の名前名が "student-team" である場合、Team のメンバーの課題リポジトリの名前は `assignment-1-student-team` になります。
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### 課題に期限を設定する
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### 課題のタイプを選択する
-Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create an individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+[個人またはグループの課題] でドロップダウン メニューを選択して、 **[グループの課題]** をクリックします。 課題の作成後は、課題タイプを変更できません。 個人の課題を作成する場合は、「[個人課題の作成](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)」を参照してください。
-### Defining teams for an assignment
+### 課題のTeamを定義する
-If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+すでにクラスルームに対してグループ課題を作成している場合は、新しい課題にTeamのセットを再利用できます。 学生が課題用に作成したTeamで新しいセットを作成するには、そのセットの名前を入力します。 必要に応じて、Teamメンバーと合計チーム数の上限を入力してください。
{% tip %}
-**Tips**:
+**ヒント**:
-- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+- セットの名前には、Teamのセットについの情報を含めることをお勧めします。 たとえば、1つの課題用にTeamのセットを使う場合は、その課題にちなんだ名前を付けます。 学期またはコースを通じてセットを再利用する場合は、学期またはコースにちなんだ名前を付けます。
-- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+- 特定のTeamに学生を割り当てる場合は、学生にTeamの名前を伝え、メンバーのリストを提供します。
{% endtip %}
-
+
-### Choosing a visibility for assignment repositories
+### 課題リポジトリの可視性を選択する
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -80,22 +86,22 @@ If you've already created a group assignment for the classroom, you can reuse a
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## スターターコードを追加し、開発環境を構成する
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [テンプレートリポジトリを作成する](#choosing-a-template-repository)
+- [統合開発環境 (IDE) を選択する](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### テンプレートリポジトリを作成する
-By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %}
+デフォルトでは、新しい課題では学生が作成した各Teamに対し、空のリポジトリが作成されます。 {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
-### Choosing an integrated development environment (IDE)
+### 統合開発環境 (IDE) を選択する
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %}詳細については、「[{% data variables.product.prodname_classroom %} と IDE の統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)」を参照してください。
{% data reusables.classroom.classroom-codespaces-link %}
@@ -103,18 +109,18 @@ By default, a new assignment will create an empty repository for each team that
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-## Providing feedback
+## フィードバックの提供
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+必要に応じて、課題を自動的に採点し、各提出物をTeamで議論するための場を作成できます。
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [課題を自動的にテストする](#testing-assignments-automatically)
+- [フィードバックのために pull request を作成する](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### 課題を自動的にテストする
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### フィードバックのためにプルリクエストを作成する
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -122,36 +128,36 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## 学生を課題に招待する
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+課題の **[チーム]** タブで、課題を作業している、または提出済みのチームを確認できます。 {% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
+## 学生の進捗状況を監視する
+課題の概要ページには、課題の受け入れとチームの進捗状況に関する情報が表示されます。 課題の構成に基づいて、表示される概要情報が異なる場合があります。
-- **Total teams**: The number of teams that have been created.
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
-- **Accepted teams**: The number of teams who have accepted this assignment.
-- **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
+- **[チームの合計数]** : 作成されたチームの数。
+- **[名簿に登録された学生]** : Classroom の名簿に登録されている学生の数。
+- **[チームに参加していない学生]** : Classroom の名簿でチームにまだ参加していない学生の数。
+- **[承認済みチーム]** : この課題を受け入れたチームの数。
+- **[課題の提出]** : 課題を提出したチームの数。 提出は、課題の期限にトリガーされます。
+- **[合格したチーム]** : 現在、この課題の自動採点テストに合格しているチームの数。
-## Next steps
+## 次の手順
-- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}.
+- 課題を作成し、学生がTeamを編成した後、TeamメンバーはGitと{% data variables.product.product_name %}の機能を使用して課題を開始できます。 学生はリポジトリのクローン、コミットのプッシュ、ブランチの管理、プルリクエストの作成およびレビュー、マージコンフリクトへの対処、およびIssueの変更に関するディスカッションが可能です。 あなたもTeamも、リポジトリのコミット履歴をレビューできます。 詳細については、「[{% data variables.product.prodname_dotcom %} の概要](/github/getting-started-with-github)」、「[リポジトリ](/repositories)」、「[Git を使用する](/github/getting-started-with-github/using-git)」、「[issue と pull request を使用したコラボレーション](/github/collaborating-with-issues-and-pull-requests)」、および {% data variables.product.prodname_learning %} の[マージの競合の解決](https://github.com/skills/resolve-merge-conflicts)に関する無料コースを参照してください。
-- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- 課題を完了したチームがある場合は、そのリポジトリにあるファイルをレビューできます。また、チームがどのように協力したかをより深く理解するため、リポジトリの履歴や視覚化されたデータを確認できます。 詳細については、[グラフを使用したリポジトリ データの視覚化](/github/visualizing-repository-data-with-graphs)に関する記事を参照してください。
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- プルリクエストの内の個々のコミットや行にコメントすることで、課題にフィードバックを行うことができます。 詳細については、「[pull request へコメントする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)」および[コードから issue を開く方法](/github/managing-your-work-on-github/opening-an-issue-from-code)に関する記事を参照してください。 返信テンプレートを作成して一般的なエラーに関するフィードバックを提供する方法の詳細については、「[返信テンプレートについて](/github/writing-on-github/about-saved-replies)」を参照してください。
-## Further reading
+## 参考資料
-- [{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
-- "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
-- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
+- [教師向け {% data variables.product.prodname_global_campus %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- 「[学習管理システムのコースをクラスルームに接続する](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)」
+- {% data variables.product.prodname_education %} Community の「[グループ課題における既存チームの使用](https://education.github.community/t/using-existing-teams-in-group-assignments/6999)」
diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 8161608b81..7298d82b26 100644
--- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -1,6 +1,6 @@
---
-title: Create an individual assignment
-intro: You can create an assignment for students in your course to complete individually.
+title: 個人課題の作成
+intro: コースにおいて、個人で修了するための課題を学生のために作成できます。
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
@@ -8,8 +8,14 @@ redirect_from:
- /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
- /education/manage-coursework-with-github-classroom/create-an-individual-assignment
shortTitle: Individual assignment
+ms.openlocfilehash: 1ffa725be4e42695b297545f65c998b14ed8e000
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179749'
---
-## About individual assignments
+## 個人課題について
{% data reusables.classroom.assignments-individual-definition %}
@@ -17,42 +23,42 @@ shortTitle: Individual assignment
{% data reusables.classroom.about-assignments %}
-For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+個人課題の作成のビデオ デモについては、「[{% data variables.product.prodname_classroom %} のセットアップの基本](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)」をご覧ください。
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## 前提条件
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## 課題を作成する
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## 課題の基本情報をセットアップする
-Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+課題に名前を付け、期限を設定するかを決定し、課題リポジトリの可視性を選択します。
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [課題に名前を付ける](#naming-an-assignment)
+- [課題に期限を設定する](#assigning-a-deadline-for-an-assignment)
+- [課題のタイプを選択する](#choosing-an-assignment-type)
+- [課題リポジトリの可視性を選択する](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### 課題に名前を付ける
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+個人課題では、{% data variables.product.prodname_classroom %}はリポジトリのプレフィックスと学生の{% data variables.product.product_name %}ユーザ名から、リポジトリに名前を付けます。 デフォルトでは、リポジトリのプレフィックスが課題のタイトルとなります。 たとえば、課題に "assignment-1" という名前を付け、{% data variables.product.product_name %} での学生のユーザー名が @octocat である場合、@octocat の課題リポジトリの名前は `assignment-1-octocat` になります。
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### 課題に期限を設定する
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### 課題のタイプを選択する
-Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+[Individual or group assignment]\(個人またはグループの課題\) の下のドロップダウン メニューを選んで、 **[Individual assignment]\(個人課題\)** をクリックします。 課題の作成後は、課題タイプを変更できません。 グループ課題を作成する場合は、「[グループ課題の作成](/education/manage-coursework-with-github-classroom/create-a-group-assignment)」をご覧ください。
-### Choosing a visibility for assignment repositories
+### 課題リポジトリの可視性を選択する
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -60,41 +66,41 @@ Under "Individual or group assignment", select the drop-down menu, and click **I
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## スターターコードを追加し、開発環境を構成する
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [テンプレートリポジトリを作成する](#choosing-a-template-repository)
+- [統合開発環境 (IDE) を選択する](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### テンプレートリポジトリを作成する
-By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+デフォルトでは、新しい課題ではクラスルームの名簿に掲載されている各学生に対し、空のリポジトリが作成されます。 {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-### Choosing an integrated development environment (IDE)
+### 統合開発環境 (IDE) を選択する
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %}詳細については、「[{% data variables.product.prodname_classroom %} と IDE の統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)」を参照してください。
{% data reusables.classroom.classroom-codespaces-link %}
{% data reusables.classroom.assignments-guide-choose-an-online-ide %}
-## Providing feedback for an assignment
+## 課題にフィードバックを行う
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
+必要に応じて、課題を自動的に採点し、各提出物を学生と議論するための場を作成できます。
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [課題を自動的にテストする](#testing-assignments-automatically)
+- [フィードバックのために pull request を作成する](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### 課題を自動的にテストする
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### フィードバックのためにプルリクエストを作成する
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -102,34 +108,34 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## 学生を課題に招待する
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
+課題の **[クラスルームの名簿]** タブで、学生がクラスルームに参加して課題を受け取ったか、または提出したかを確認できます。 このタブでは、学生の {% data variables.product.prodname_dotcom %} エイリアスを関連する名簿識別子にリンクしたり、その逆にリンクしたりすることもできます。{% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
+## 学生の進捗状況を監視する
+課題の概要ページには、課題の受け入れと学生の進捗状況の概要が表示されます。 課題の構成に基づいて、表示される概要情報が異なる場合があります。
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
-- **Accepted students**: The number of accounts have accepted this assignment.
-- **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing students**: The number of students currently passing the autograding tests for this assignment.
+- **[名簿に登録された学生]** : Classroom の名簿に登録されている学生の数。
+- **[Added students]\(追加された学生\)** : 課題を受け入れていて、名簿識別子に関連付けられていない {% data variables.product.prodname_dotcom %} アカウントの数。
+- **[Accepted students]\(受け入れた学生\)** : この課題を受け入れたアカウントの数。
+- **[Assignment submissions]\(課題の提出\)** : 課題を提出した学生の数。 提出は、課題の期限にトリガーされます。
+- **[Passing students]\(合格した学生\)** : 現在、この課題の自動採点テストに合格している学生の数。
-## Next steps
+## 次の手順
-- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- 課題を作成した後、学生はGitおよび{% data variables.product.product_name %}の機能を使用して課題を開始できます。 学生はリポジトリのクローン、コミットのプッシュ、ブランチの管理、プルリクエストの作成およびレビュー、マージコンフリクトへの対処、およびIssueの変更に関するディスカッションが可能です。 あなたも学生も、リポジトリのコミット履歴をレビューできます。 詳しくは、[{% data variables.product.prodname_dotcom %} の概要](/github/getting-started-with-github)、[リポジトリ](/repositories)、[issue と pull request での共同作業](/github/collaborating-with-issues-and-pull-requests)に関する記事をご覧ください。
-- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- 課題を完了した学生がいる場合には、その学生のリポジトリにあるファイルをレビューできます。また、学生の作業についてをより深く理解するため、リポジトリの履歴や視覚化されたデータを確認できます。 詳細については、[グラフを使用したリポジトリ データの視覚化](/github/visualizing-repository-data-with-graphs)に関する記事を参照してください。
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- プルリクエストの内の個々のコミットや行にコメントすることで、課題にフィードバックを行うことができます。 詳細については、「[pull request へコメントする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)」および[コードから issue を開く方法](/github/managing-your-work-on-github/opening-an-issue-from-code)に関する記事を参照してください。 返信テンプレートを作成して一般的なエラーに関するフィードバックを提供する方法の詳細については、「[返信テンプレートについて](/github/writing-on-github/about-saved-replies)」を参照してください。
-## Further reading
+## 参考資料
-- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
+- 「[教師向け {% data variables.product.prodname_global_campus %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)」
+- [学習管理システムを {% data variables.product.prodname_classroom %} に接続する](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)
diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md
index 7a247d6c1c..1c04bdfb1e 100644
--- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -1,83 +1,88 @@
---
-title: Getting started with GitHub AE
-intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.'
+title: GitHub AE の概要
+intro: '{% data variables.location.product_location %} の {% data variables.product.product_name %} の設定と構成を開始します。'
versions:
ghae: '*'
+ms.openlocfilehash: 957a922a2493abd8f625cdb9e9d6650283820222
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180062'
---
+このガイドでは、Enterprise 所有者として {% data variables.product.product_name %} 上で {% data variables.location.product_location %} の設定を設定、構成、および管理を行う方法について説明します。 {% data variables.product.product_name %} について詳しくは、「[{% data variables.product.prodname_ghe_managed %} について](/admin/overview/about-github-ae)」をご覧ください。
-This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)."
+## パート 1: {% data variables.product.product_name %} の設定
+{% data variables.product.product_name %} の使用を開始するために、Enterprise アカウントを作成し、{% data variables.product.product_name %} を初期化し、IP 許可リストを構成し、ユーザー認証とプロビジョニングを構成し、{% data variables.location.product_location %} の課金を管理できます。
-## Part 1: Setting up {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}.
-
-### 1. Creating your {% data variables.product.product_name %} enterprise account
-You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+### 1. {% data variables.product.product_name %} Enterprise アカウントの作成
+まず、{% data variables.product.product_name %} を購入する必要があります。 詳細については、[{% data variables.product.prodname_dotcom %} の営業チーム](https://enterprise.github.com/contact)にお問い合わせください。
{% data reusables.github-ae.initialize-enterprise %}
-### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+### 2. {% data variables.product.product_name %} の初期化
+{% data variables.product.company_short %} により {% data variables.product.product_name %} の {% data variables.location.product_location %} の所有者アカウントが作成された後、サインインして初期化を完了するための電子メールが届きます。 初期化中に、Enterprise 所有者は {% data variables.location.product_location %} に名前を付け、SAML SSO を構成し、{% data variables.location.product_location %} 内のすべての Organization のポリシーを作成し、Enterprise メンバーのサポート連絡先を構成します。 詳細については、「[{% data variables.product.prodname_ghe_managed %} の初期化](/admin/configuration/configuring-your-enterprise/initializing-github-ae)」を参照してください。
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 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)."
+### 3. ネットワーク トラフィックの制限
+特定の IP アドレスの許可リストを構成し、Enterprise アカウント内の Organization が所有する資産へのアクセスを制限できます。 詳しくは、「[IP 許可リストを使って Enterprise へのネットワーク トラフィックを制限する](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)」をご覧ください。
-### 4. Managing identity and access for {% data variables.location.product_location %}
-You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[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)."
+### 4. {% data variables.location.product_location %} の ID とアクセスの管理
+ユーザー認証用の SAML シングル サインオン (SSO) とユーザー プロビジョニング用のクロスドメイン ID 管理システム (SCIM) を使用して、ID プロバイダー (IdP) から {% data variables.product.product_name %} の {% data variables.location.product_location %} へのアクセスを一元的に管理できます。 プロビジョニングを構成したら、IdP からアプリケーションにユーザーを割り当てるか、割り当て解除し、Enterprise 内のユーザー アカウントを作成または無効にすることができます。 詳細については、[Enterprise の ID およびアクセス管理](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)に関するページを参照してください。
-### 5. Managing billing for {% data variables.location.product_location %}
-Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+### 5. {% data variables.location.product_location %} の課金の管理
+{% data variables.product.product_name %} の {% data variables.location.product_location %} のサブスクリプションの所有者は、Azure portal で {% data variables.product.product_name %} の課金を詳しく表示できます。 詳細については、[Enterprise の課金の管理](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)に関するページを参照してください。
-## Part 2: Organizing and managing enterprise members
-As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
+## パート 2: Enterprise メンバーの編成と管理
+{% data variables.product.product_name %} の Enterprise 所有者は、ユーザー、リポジトリ、チーム、および Organization レベルで設定を管理できます。 {% data variables.location.product_location %} のメンバーの管理、Organization の作成と管理、リポジトリ管理に関するポリシーの設定、チームの作成と管理を行うことができます。
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. {% data variables.location.product_location %} のメンバーの管理
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. Organization の作成
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. Organization へのメンバーの追加
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. チームの作成
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. Organization とリポジトリのアクセス許可レベルの設定
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. リポジトリ管理ポリシーの適用
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations.
+## パート 3: 安全なビルド
+{% data variables.location.product_location %} のセキュリティを強化するために、{% data variables.location.product_location %} を監視し、Organization のセキュリティと分析機能を構成することができます。
-### 1. Monitoring {% data variables.location.product_location %}
-You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)."
+### 1. {% data variables.location.product_location %} の監視
+アクティビティ ダッシュボードと監査ログを使用して、{% data variables.location.product_location %} を監視できます。 詳細については、「[Enterprise でアクティビティを監視する](/admin/monitoring-activity-in-your-enterprise)」を参照してください。
-### 2. Configuring security features for your organizations
+### 2. Organization のセキュリティ機能の構成
{% data reusables.getting-started.configuring-security-features %}
-## Part 4: Customizing and automating work on {% data variables.location.product_location %}
-You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
+## パート 4: {% data variables.location.product_location %} での作業のカスタマイズと自動化
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %}、および {% data variables.product.prodname_pages %} を使用して、{% data variables.location.product_location %} 内の Organization での作業をカスタマイズおよび自動化することができます。
-### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API の使用
{% data reusables.getting-started.api %}
-### 2. Building {% data variables.product.prodname_actions %}
+### 2. {% data variables.product.prodname_actions %} のビルド
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."
+{% data variables.product.product_name %} の {% data variables.product.prodname_actions %} の有効化と構成の詳細については、「[{% data variables.product.prodname_ghe_managed %} の {% data variables.product.prodname_actions %} の概要](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)」を参照してください。
-### 3. Using {% data variables.product.prodname_pages %}
+### 3. {% data variables.product.prodname_pages %} の使用
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## パート 5: {% data variables.product.prodname_dotcom %} の学習およびサポート リソースの使用
+Enterprise メンバーは、学習リソースを使用して Git と {% data variables.product.prodname_dotcom %} の詳細を学ぶことができます。また、{% data variables.product.prodname_dotcom %} Enterprise サポートを使用して必要なサポートを受けることができます。
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+### 1. {% data variables.product.prodname_docs %} で {% data variables.product.product_name %} について読む
+{% data variables.product.prodname_ghe_managed %} で使用できる機能が掲載されたドキュメントを読むことができます。 詳細については、「[{% data variables.product.prodname_docs %} のバージョンについて](/get-started/learning-about-github/about-versions-of-github-docs)」を参照してください。
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. {% data variables.product.prodname_learning %} による学習
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. {% data variables.product.prodname_dotcom %} Enterprise サポートの使用
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index f3368b385c..af6bc487db 100644
--- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,128 +1,132 @@
---
-title: Getting started with GitHub Enterprise Server
-intro: 'Get started with setting up and managing {% data variables.location.product_location %}.'
+title: GitHub Enterprise Serverを使い始める
+intro: '{% data variables.location.product_location %} の設定と管理を開始します。'
versions:
ghes: '*'
+ms.openlocfilehash: 68cd462c42ef63863750d9edc5e122dc3c325115
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163417'
---
+このガイドでは、エンタープライズ管理者として {% data variables.location.product_location %} の設定、構成、管理を行う方法について説明します。
-This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator.
-
-{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
+{% data variables.product.company_short %} には、{% data variables.product.prodname_enterprise %} をデプロイするための方法として、次の 2 つが用意されています。
- **{% data variables.product.prodname_ghe_cloud %}**
- **{% data variables.product.prodname_ghe_server %}**
-{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
+{% data variables.product.prodname_ghe_cloud %} は、{% data variables.product.company_short %} でホストされます。 {% data variables.product.prodname_ghe_server %} は、自身のデータセンターまたはサポートされているクラウド プロバイダーにデプロイしてホストすることができます。
-For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)."
+{% data variables.product.product_name %} の詳細については、「[{% data variables.product.prodname_ghe_server %} について](/admin/overview/about-github-enterprise-server)」を参照してください。
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing.
-### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## パート 1: {% data variables.product.product_name %} のインストール方法
+{% data variables.product.product_name %} を使い始めるには、Enterprise アカウントの作成とインスタンスのインストールを行い、初期設定に管理コンソールを使用し、インスタンスを構成し、支払いを管理する必要があります。
+### 1. Enterprise アカウントの作成
+{% data variables.product.product_name %} をインストールする前に、[{% data variables.product.prodname_dotcom %} の営業チーム](https://enterprise.github.com/contact) に連絡して、{% data variables.product.prodname_dotcom_the_website %} に Enterprise アカウントを作成できます。 {% data variables.product.prodname_dotcom_the_website %} の Enterprise アカウントは、支払いや、{% data variables.product.prodname_github_connect %} を介した {% data variables.product.prodname_dotcom_the_website %} での共有機能に役立ちます。 詳細については、「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
+### 2. {% data variables.product.product_name %} のインストール
+{% data variables.product.product_name %} を使い始めるには、選択した仮想化プラットフォームにアプライアンスをインストールする必要があります。 詳細については、「[{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/admin/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
-### 3. Using the Management Console
-You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+### 3. 管理コンソールの使用
+{% data variables.location.product_location %} を初めて起動する場合、管理コンソールを使用して、初期設定プロセスを実行します。 また、管理コンソールを使用して、ライセンス、ドメイン、認証、TLS などのインスタンス設定を管理することもできます。 詳細については、「[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)」 (管理コンソールへのアクセス) を参照してください。
-### 4. Configuring {% data variables.location.product_location %}
-In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
+### 4. {% data variables.location.product_location %} の構成
+管理コンソールに加えて、サイト管理ダッシュボードと管理シェル (SSH) を使用して {% data variables.location.product_location %} を管理することもできます。 たとえば、アプリケーションやレート制限を構成したり、レポートを表示したり、コマンドライン ユーティリティを使用したりすることができます。 詳細については、「[Enterprise を設定する](/admin/configuration/configuring-your-enterprise)」を参照してください。
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+動的ホスト構成プロトコル (DHCP) を介して {% data variables.product.product_name %} で使用される既定のネットワーク設定を使用することも、仮想マシン コンソールを使用してネットワーク設定を構成することもできます。 プロキシサーバあるいはファイアウォールルールを設定することもできます。 詳細については、「[ネットワークを設定する](/admin/configuration/configuring-network-settings)」を参照してください。
-### 5. Configuring high availability
-You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
+### 5. 高可用性の構成
+{% data variables.location.product_location %} を高可用性向けに構成して、ハードウェア障害やネットワークの停止による影響を最小限に抑えることができます。 詳細については、「[High Availability の設定](/admin/enterprise-management/configuring-high-availability)」を参照してください。
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 6. ステージング インスタンスのセットアップ
+ステージング インスタンスを設定して、{% data variables.location.product_location %} に適用される前に変更をテストし、ディザスター リカバリーを計画し、更新プログラムを試すことができます。 詳細については、「[ステージング インスタンスのセットアップ](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)」を参照してください。
-### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+### 7. バックアップとディザスター リカバリーの指定
+運用データを保護するには、{% data variables.product.prodname_enterprise_backup_utilities %} による {% data variables.location.product_location %} の自動バックアップを構成できます。 詳細については、「[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)」 (アプライアンスでのバックアップの構成) を参照してください。
-### 8. Managing billing for your enterprise
-Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+### 8. Enterprise の支払いの管理
+Enterprise アカウントに接続されているすべての Organization および {% data variables.product.product_name %} インスタンスの支払いは、有料のすべての {% data variables.product.prodname_dotcom %}.com サービスに対する単一の請求料金として集計されます。 Enterprise オーナーと支払いマネージャーは、Enterprise アカウントの支払い設定にアクセスして管理することができます。 詳細については、「[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)」 (Enterprise の支払いの管理) を参照してください。
-## Part 2: Organizing and managing your team
-As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
+## パート 2: Team の編成と管理
+Enterprise オーナーまたは管理者は、ユーザー、リポジトリ、Team、Organization のレベルの設定を管理できます。 Enterprise のメンバーの管理、Organization の作成と管理、リポジトリ管理に関するポリシーの設定、Team の作成と管理を行うことができます。
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. {% data variables.location.product_location %} のメンバーの管理
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. Organization の作成
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. Organization へのメンバーの追加
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. チームの作成
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. Organization とリポジトリのアクセス許可レベルの設定
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. リポジトリ管理ポリシーの適用
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
-### 1. Authenticating enterprise members
-You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+## パート 3: 安全なビルド
+{% data variables.location.product_location %} のセキュリティを強化するには、エンタープライズ メンバーの認証を構成し、ツールと監査ログを使用してコンプライアンスを維持し、組織のセキュリティおよび分析機能を構成し、必要に応じて {% data variables.product.prodname_GH_advanced_security %} を有効にすることができます。
+### 1. Enterprise メンバーの認証
+{% data variables.product.product_name %} の組み込み認証方法を使用するか、CAS、LDAP、SAML などの外部の認証プロバイダーを選び、既存のアカウントを統合して、{% data variables.location.product_location %} へのユーザー アクセスを一元的に管理することができます。 詳しくは、「[Enterprise の認証について](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)」をご覧ください。
-You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
+また、Organization ごとに 2 要素認証を要求することもできます。 詳細については、「[Organization に 2 要素認証を要求する](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)」を参照してください。
-### 2. Staying in compliance
-You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+### 2. コンプライアンスの維持
+必要な状態チェックとコミット検証を実装して、Organization のコンプライアンス標準を適用し、コンプライアンス ワークフローを自動化できます。 また、Organization の監査ログを使用して、Team によって実行されるアクションをレビューすることもできます。 詳細については、「[Pre-receive フックを使ってポリシーを適用する](/admin/policies/enforcing-policy-with-pre-receive-hooks)」および「[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)」 (Enterprise の監査ログについて) を参照してください。
{% ifversion ghes %}
-### 3. Configuring security features for your organizations
-{% data reusables.getting-started.configuring-security-features %}
-{% endif %}
+### 3. Organization のセキュリティ機能の構成
+{% data reusables.getting-started.configuring-security-features %} {% endif %}
{% ifversion ghes %}
-### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
-You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+### 4. {% data variables.product.prodname_GH_advanced_security %} 機能の有効化
+{% data variables.product.product_name %} ライセンスをアップグレードして、{% data variables.product.prodname_GH_advanced_security %} を含めることができます。 これにより、コードやシークレット スキャンなど、ユーザーがコード内のセキュリティ上の問題を検出して修正するのに役立つ追加機能が提供されます。 詳細については、「[Enterprise の {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)」を参照してください。
{% endif %}
-## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
-You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
+## パート 4: {% data variables.product.prodname_dotcom %} での Enterprise の作業のカスタマイズと自動化
+{% data variables.product.prodname_dotcom %} と {% data variables.product.prodname_oauth_apps %}、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %}、{% data variables.product.prodname_pages %} を使用して、Enterprise 内の Organization での作業をカスタマイズおよび自動化できます。
-### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. {% data variables.product.prodname_github_apps %} と {% data variables.product.prodname_oauth_apps %} のビルド
+{% data variables.product.prodname_github_apps %} や {% data variables.product.prodname_oauth_apps %} などの {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API との統合を構築し、ワークフローを補完および拡張するために Enterprise 内の Organization で使用することができます。 詳細については、「[About apps](/developers/apps/getting-started-with-apps/about-apps)」 (アプリについて) を参照してください。
+### 2. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API の使用
{% data reusables.getting-started.api %}
{% ifversion ghes %}
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. {% data variables.product.prodname_actions %} のビルド
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+{% data variables.product.product_name %} で {% data variables.product.prodname_actions %} を有効にして構成する方法の詳細については、「[{% data variables.product.prodname_ghe_server %} の {% data variables.product.prodname_actions %} を使い始める](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)」を参照してください。
-### 4. Publishing and managing {% data variables.product.prodname_registry %}
+### 4. {% data variables.product.prodname_registry %} の公開と管理
{% data reusables.getting-started.packages %}
-For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+{% data variables.location.product_location %} の {% data variables.product.prodname_registry %} を有効にして構成する方法の詳細については、「[エンタープライズの {% data variables.product.prodname_registry %} を使い始める](/admin/packages/getting-started-with-github-packages-for-your-enterprise)」を参照してください。
{% endif %}
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. {% data variables.product.prodname_pages %} の使用
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
-You can use {% data variables.product.prodname_github_connect %} to share resources.
+## パート 5: 他の {% data variables.product.prodname_dotcom %} リソースとの接続
+{% data variables.product.prodname_github_connect %} を使用してリソースを共有することができます。
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+{% data variables.product.product_name %} インスタンスと、{% data variables.product.prodname_ghe_cloud %} の Organization または Enterprise アカウントの両方のオーナーである場合、{% data variables.product.prodname_github_connect %} を有効にすることができます。 {% data variables.product.prodname_github_connect %} を使用すると、{% data variables.location.product_location %} と {% data variables.product.prodname_ghe_cloud %} の間で、統合検索やコントリビューションなどの特定のワークフローや機能を共有できます。 詳細については、「[{% data variables.product.prodname_ghe_cloud %} への {% data variables.product.prodname_ghe_server %} の接続](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。
-## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## パート 6: {% data variables.product.prodname_dotcom %} の学習およびサポート リソースの使用
+エンタープライズ メンバーは、学習リソースを使用して Git と {% data variables.product.prodname_dotcom %} の詳細を学ぶことができます。また、{% data variables.location.product_location %} の設定および管理を行う際に、{% data variables.product.prodname_dotcom %} エンタープライズ サポートを使用して必要なサポートを受けることができます。
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+### 1. {% data variables.product.prodname_docs %} で {% data variables.product.product_name %} に関するドキュメントを読む
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+{% data variables.product.prodname_ghe_server %} で使用できる機能が掲載されたドキュメントを読むことができます。 詳細については、「[{% data variables.product.prodname_docs %} のバージョンについて](/get-started/learning-about-github/about-versions-of-github-docs)」を参照してください。
{% data reusables.enterprise.best-practices %}
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. {% data variables.product.prodname_learning %} による学習
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. {% data variables.product.prodname_dotcom %} Enterprise サポートの使用
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 02ab297dbb..634d0158e7 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,6 +1,6 @@
---
-title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
-intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
+title: '{% data variables.product.prodname_projects_v1 %} からの移行'
+intro: '{% data variables.projects.projects_v1_board %} を新しい {% data variables.product.prodname_projects_v2 %} エクスペリエンスに移行できます。'
miniTocMaxHeadingLevel: 3
versions:
feature: projects-v2
@@ -10,57 +10,53 @@ type: tutorial
topics:
- Projects
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e6db4fd8c6587f413ee0e6832dbae93bbf281573
+ms.sourcegitcommit: 9bf175b190674416ad4e11b5c567409f74c00ad2
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/23/2022
+ms.locfileid: '148181222'
---
-
-
{% note %}
-**Notes:**
+**注:**
-- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
-- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
-- Automation will not be migrated.
-- Triage, archive, and activity will not be migrated.
-- After migration, the new migrated project and old project will not be kept in sync.
+- 移行するプロジェクトに {% data variables.projects.item_limit %} を超える項目が含まれている場合は、未解決の issue が優先され、その後に未解決の pull request、メモが続きます。 残りの領域は、解決された issue、マージされた pull request、および解決された pull request に使用されます。 この制限により移行できない項目は、アーカイブに移動されます。 アーカイブの上限である {% data variables.projects.archived_item_limit %} 項目に達した場合、追加の項目は移行されません。
+- ノート カードは下書きの issue に変換され、内容は下書きの issue の本文に保存されます。 情報が見つからないように見える場合は、非表示フィールドを表示します。 詳しくは、「[フィールドの表示と非表示](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)」を参照してください。
+- 自動化は移行されません。
+- トリアージ、アーカイブ、アクティビティは移行されません。
+- 移行後、新しく移行されたプロジェクトと古いプロジェクトは同期されません。
{% endnote %}
-## About project migration
+## プロジェクトの移行について
-You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
+プロジェクト ボードを新しい {% data variables.product.prodname_projects_v2 %} エクスペリエンスに移行し、テーブル、複数のビュー、新しい自動化オプション、強力なフィールドの種類を試すことができます。 詳しくは、「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」を参照してください。
-## Migrating an organization project board
+## 組織のプロジェクト ボードの移行
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
-1. On the left, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
+1. 左側の **[プロジェクト (クラシック)]** をクリックします。
+ ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %}
-## Migrating a user project board
+## ユーザー プロジェクト ボードの移行
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_profile %}
-1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
- 
-1. Above the list of projects, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
+1. プロファイル ページの上部のメイン ナビゲーションにある {% octicon "table" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。
+ ![[プロジェクト] タブを示すスクリーンショット](/assets/images/help/projects-v2/tab-projects.png)
+1. プロジェクトの一覧の上にある **[プロジェクト (クラシック)]** をクリックします。
+ ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-user.png) {% data reusables.projects.migrate-project-steps %}
-## Migrating a repository project board
+## リポジトリのプロジェクトボードの移行
{% note %}
-**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
+**注:** {% data variables.projects.projects_v2_caps %} では、リポジトリ レベルのプロジェクトはサポートされていません。 リポジトリ プロジェクト ボードを移行すると、リポジトリ プロジェクトを所有する組織または個人アカウントに移行され、移行されたプロジェクトは元のリポジトリにピン留めされます。
{% endnote %}
-{% data reusables.projects.enable-migration %}
-{% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
-
-1. Click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
+1. リポジトリ名の下にある {% octicon "table" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。
+![[プロジェクト] タブ](/assets/images/help/projects-v2/repo-tabs-projects.png)
+1. **[プロジェクト (クラシック)]** をクリックします。
+ ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %}
diff --git a/translations/ja-JP/content/packages/quickstart.md b/translations/ja-JP/content/packages/quickstart.md
index 7ff2db3442..75cf8a196b 100644
--- a/translations/ja-JP/content/packages/quickstart.md
+++ b/translations/ja-JP/content/packages/quickstart.md
@@ -1,6 +1,6 @@
---
-title: Quickstart for GitHub Packages
-intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
+title: GitHub Packagesのクイックスタート
+intro: '{% data variables.product.prodname_actions %}で{% data variables.product.prodname_registry %}に公開します。'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -8,29 +8,34 @@ versions:
ghae: '*'
ghec: '*'
shortTitle: Quickstart
+ms.openlocfilehash: 887c4ee6c5e6b3e2c391c2d5754cfcb2787e4b86
+ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/24/2022
+ms.locfileid: '148181257'
---
-
{% data reusables.actions.enterprise-github-hosted-runners %}
-## Introduction
+## はじめに
-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 %}.
+このガイドでは、コードをテストする{% data variables.product.prodname_actions %}ワークフローを作成して、それを{% data variables.product.prodname_registry %}に公開します。
-## Publishing your package
+## パッケージを公開する
-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.
+1. {% data variables.product.prodname_dotcom %} に新しいリポジトリを作成し、ノードに `.gitignore` を追加します。 詳細については、「[新しいリポジトリの作成](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)」を参照してください。
+2. ローカル コンピューターにリポジトリを複製します。
```shell
$ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
$ cd YOUR-REPOSITORY
```
-3. Create an `index.js` file and add a basic alert to say "Hello world!"
+3. `index.js` ファイルを作成し、「Hello world!」を表示する基本的なアラートを作成します。
{% raw %}
```javascript{:copy}
console.log("Hello, World!");
```
{% endraw %}
-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.
+4. npm パッケージを `npm init` で初期化します。 パッケージ初期化ウィザードで、 _`@YOUR-USERNAME/YOUR-REPOSITORY`_ の形式で名前を入力し、テスト スクリプトを `exit 0` に設定します。 これにより、パッケージの情報が付いた `package.json` ファイルが生成されます。
{% raw %}
```shell
$ npm init
@@ -41,15 +46,15 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
...
```
{% endraw %}
-5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
+5. `npm install` を実行して `package-lock.json` ファイルを生成し、変更をコミットして {% 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. 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 %}.
+6. `.github/workflows` ディレクトリを作成します。 そのディレクトリ内に、`release-package.yml` という名前のファイルを作成します。
+7. 以下の内容の YAML を `release-package.yml` ファイルにコピーします。{% ifversion ghes or ghae %}`YOUR-HOSTNAME` をエンタープライズの名前に置き換えてください。{% endif %}
```yaml{:copy}
name: Node.js Package
@@ -85,22 +90,20 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
env:
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
```
-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 %}
+8. NPMに、以下のいずれかの方法を使ってどのスコープ及びリポジトリにパッケージを公開するかを伝えます。
+ - `.npmrc` ファイルを作成することによって、リポジトリのための NPM 設定ファイルを以下の内容でルート ディレクトリに追加する: {% raw %}
```shell
@YOUR-USERNAME:registry=https://npm.pkg.github.com
```
{% endraw %}
- - Edit the `package.json` file and specify the `publishConfig` key:
- {% raw %}
+ - `package.json` ファイルを編集し、`publishConfig` キーを次のように指定する: {% raw %}
```shell
"publishConfig": {
"@YOUR-USERNAME:registry": "https://npm.pkg.github.com"
}
```
{% endraw %}
-9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
+9. コミットして変更を{% 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.
@@ -108,28 +111,26 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
$ git commit -m "workflow to publish package"
$ git push
```
-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 %}.
+10. 作成したワークフローは、リポジトリに新しいリリースが作成されるたびに実行されます。 テストにパスすると、パッケージは{% data variables.product.prodname_registry %}に公開されます。
- 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)."
+ これを試すには、リポジトリの **[Code]** タブに移動し、新しいリリースを作成します。 詳細については、「[リポジトリのリリースを管理する](/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
+## 公開したパッケージをインストールする
-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)."
+これでパッケージを公開できたので、プロジェクト全体で依存関係として利用できます。 詳細については、「[npm レジストリの利用](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)」を参照してください。
-## Next steps
+## 次の手順
-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 %}でできることの手始めにすぎません。 単一のワークフローで複数のレジストリにパッケージを公開する、ワークフローをトリガーしてマージされたプルリクエストなどさまざまなイベントで実行する、コンテナを管理するなど、いろいろなことができます。
-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 %}:
+{% data variables.product.prodname_registry %}と{% data variables.product.prodname_actions %}を組み合わせることで、プリケーション開発プロセスのほぼすべての要素を自動化するために役立ちます。 使い始める準備はできていますか。 以下は、{% data variables.product.prodname_registry %}および{% data variables.product.prodname_actions %}で次のステップへ進むために役立つリソースです。
-- "[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
+- 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)」
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 44c7cc1752..e6311b734d 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -15,12 +15,12 @@ versions:
topics:
- Pull requests
shortTitle: Deleted or changes visibility
-ms.openlocfilehash: d52215a7406edc84bc71022517f848faa9e48600
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 95296f33d9163cd1171481386efd0a2351095c39
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
ms.translationtype: HT
ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '147886799'
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191360'
---
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
@@ -32,7 +32,7 @@ ms.locfileid: '147886799'
## パブリックリポジトリを削除する
-パブリックリポジトリを削除すると、既存のパブリックフォークの 1 つが新しい親リポジトリとして選択されます。 他のすべてのリポジトリはこの新しい親から分岐し、その後のプルリクエストはこの新しい親に送られます。
+パブリック リポジトリを削除すると、既存のパブリック フォークの 1 つが新しい上流リポジトリとして選択されます。 他のすべてのリポジトリはこの新しい上流から分岐し、その後の pull request はこの新しい上流リポジトリに送られます。
{% endif %}
@@ -44,9 +44,9 @@ ms.locfileid: '147886799'
## パブリックリポジトリをプライベートリポジトリに変更する
-パブリックリポジトリを非公開にすると、そのパブリックフォークは新しいネットワークに分割されます。 パブリックリポジトリの削除と同様に、既存のパブリックフォークの 1 つが新しい親リポジトリとして選択され、他のすべてのリポジトリはこの新しい親から分岐されます。 後続のプルリクエストは、この新しい親に行きます。
+パブリックリポジトリを非公開にすると、そのパブリックフォークは新しいネットワークに分割されます。 パブリック リポジトリの削除と同様に、既存のパブリック フォークの 1 つが新しい上流リポジトリとして選択され、他のすべてのリポジトリはこの新しい上流から分岐します。 後続の pull request は、この新しい上流リポジトリに送られます。
-言い換えれば、パブリックリポジトリのフォークは、親リポジトリが非公開にされた後も、独自の別のリポジトリネットワークで公開されたままになります。 これにより、フォークオーナーは作業を中断せずに作業を継続できます。 このようにパブリック フォークが別のネットワークに移動されなかった場合、それらのフォークのオーナーは適切な[アクセス許可](/articles/access-permissions-on-github)を取得してプルする必要があります。 以前はこれらのアクセス権が必要ではなかったとしても、(現在はプライベートになっている) 親リポジトリからの変更を取得して送信します。
+つまり、パブリック リポジトリのフォークは、上流リポジトリがプライベートにされた後も、独自の別のリポジトリ ネットワーク内でパブリックのままになります。 これにより、フォークオーナーは作業を中断せずに作業を継続できます。 このようにパブリック フォークが別のネットワークに移動されなかった場合、それらのフォークの所有者は、適切な[アクセス許可](/articles/access-permissions-on-github)を取得して、(現在はプライベートになっている) 上流リポジトリから変更をプルし、pull request を送信する必要があります (以前はそれらのアクセス許可が必要ではなかったとしても)。
{% ifversion ghes or ghae %} パブリック リポジトリで匿名の Git 読み取りアクセスが有効になっていて、そのリポジトリが非公開になっている場合、リポジトリのすべてのフォークは匿名の Git 読み取りアクセスを失い、既定の無効設定に戻ります。 分岐したリポジトリが公開された場合、リポジトリ管理者は匿名の Git 読み取りアクセスを再度有効にすることができます。 詳細については、「[リポジトリに対する匿名 Git 読み取りアクセスの有効化](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。
{% endif %}
@@ -57,7 +57,7 @@ ms.locfileid: '147886799'
## プライベートリポジトリのパブリックリポジトリへの変更
-プライベートリポジトリが公開されると、そのプライベートフォークはそれぞれスタンドアロンのプライベートリポジトリになり、独自の新しいリポジトリネットワークの親になります。 プライベートフォークは、公開されるべきではない機密のコミットを含む可能性があるため、自動的に公開されることはありません。
+プライベート リポジトリがパブリックに変更されると、そのプライベート フォークはそれぞれスタンドアロンのプライベート リポジトリになり、独自の新しいリポジトリ ネットワークの上流になります。 プライベートフォークは、公開されるべきではない機密のコミットを含む可能性があるため、自動的に公開されることはありません。
### パブリックリポジトリを削除する
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
index a66e99ee9a..0465de6bd1 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository from a template
-intro: You can generate a new repository with the same directory structure and files as an existing repository.
+title: テンプレートからリポジトリを作成する
+intro: 既存のリポジトリと同じディレクトリ構造およびファイルで、新しいリポジトリを作成できます。
redirect_from:
- /articles/creating-a-repository-from-a-template
- /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template
@@ -13,45 +13,46 @@ versions:
topics:
- Repositories
shortTitle: Create from a template
+ms.openlocfilehash: 16d124431426e19cf95c768e8a4cdaa5f4da2e17
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160244'
---
-## About repository templates
+## リポジトリテンプレートついて
-Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)."
+リポジトリに対する読み取り権限があるユーザなら誰でも、テンプレートからリポジトリを作成できます。 詳細については、「[テンプレート リポジトリの作成](/articles/creating-a-template-repository)」を参照してください。
{% tip %}
-**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+**ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリをテンプレートから作成することもできます。 詳細については、{% data variables.product.prodname_cli %} ドキュメントの "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" を参照してください。
{% endtip %}
-You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
+テンプレートリポジトリのデフォルトブランチのみからディレクトリ構造とファイルを含めるか、すべてのブランチを含めるかを選択できます。 テンプレートから作成されたブランチには関連のない履歴があるため、pull request を作成したり、ブランチ間でマージしたりすることはできません。
-Creating a repository from a template is similar to forking a repository, but there are important differences:
-- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit.
-- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph.
-- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly.
+テンプレートからリポジトリを作成することは、リポジトリをフォークすることに似ていますが、以下の点で異なります:
+- 新しいフォークは、親リポジトリのコミット履歴すべてを含んでいますが、テンプレートから作成されたリポジトリには、最初は 1 つのコミットしかありません。
+- フォークへのコミットはコントリビューショングラフに表示されませんが、テンプレートから作成されたリポジトリへのコミットはコントリビューショングラフに表示されます。
+- フォークは、既存のプロジェクトにコードをコントリビュートするための一時的な方法となります。テンプレートからリポジトリを作成することは、新しいプロジェクトを素早く始める方法です。
-For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
+フォークについて詳しくは、「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」をご覧ください。
-## Creating a repository from a template
+## テンプレートからリポジトリを作成する
{% data reusables.repositories.navigate-to-repo %}
-1. Above the file list, click **Use this template**.
+1. ファイルの一覧の上にある **[Use this template]\(このテンプレートを使用する\)** をクリックします。
{% ifversion fpt or ghec %}
-1. Select **Create a new repository**.
+1. **[新しいリポジトリの作成]** を選びます。
- 
+ ![[このテンプレートを使用する] ボタン](/assets/images/help/repository/use-this-template-button.png)
{% note %}
- **Note:** Alternatively, you can open the template in a codespace and publish your work to a new repository later. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+ **注:** または、codespace でテンプレートを開き、後で作業内容を新しいリポジトリに発行することもできます。 詳しくは、「[テンプレートから codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)」をご覧ください。
- {% endnote %}
-{% endif %}
-{% data reusables.repositories.owner-drop-down %}
-{% data reusables.repositories.repo-name %}
-{% data reusables.repositories.choose-repo-visibility %}
-1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
- 
-{% data reusables.repositories.select-marketplace-apps %}
-8. Click **Create repository from template**.
+ {% endnote %} {% endif %} {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %}
+1. 必要に応じて、既定のブランチだけでなく、テンプレートのすべてのブランチからディレクトリ構造とファイルを含めるには、 **[すべてのブランチを含める]** を選びます。
+ ![[すべてのブランチを含める] チェック ボックス](/assets/images/help/repository/include-all-branches.png) {% data reusables.repositories.select-marketplace-apps %}
+8. **[Create repository from template]\(テンプレートからリポジトリを作成する\)** をクリックします。
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
index 151756761d..82c91ccc98 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
@@ -1,6 +1,6 @@
---
-title: Automatically generated release notes
-intro: You can automatically generate release notes for your GitHub releases
+title: 自動生成リリース ノート
+intro: GitHub リリースのリリース ノートを自動的に生成できます
permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release.
versions:
fpt: '*'
@@ -13,71 +13,63 @@ shortTitle: Automated release notes
communityRedirect:
name: Provide GitHub Feedback
href: 'https://github.com/orgs/community/discussions/categories/general'
+ms.openlocfilehash: aee951e6f57492240b5baf8870578409945aefdc
+ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/29/2022
+ms.locfileid: '148185195'
---
+## 自動生成リリース ノートについて
-## About automatically generated release notes
+自動生成リリース ノートは、{% data variables.product.prodname_dotcom %} リリースのリリース ノートを手作業で記述する代わりに、自動的に生成する機能です。 自動生成リリース ノートを使うと、リリースの内容の概要をすばやく生成できます。 自動生成されたリリース ノートには、マージされた pull request の一覧、リリースの共同作成者の一覧、完全な変更ログへのリンクが含まれます。
-Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. Automatically generated release notes include a list of merged pull requests, a list of contributors to the release, and a link to a full changelog.
+また、自動リリース ノートをカスタマイズし、ラベルを使ってカスタム カテゴリを作成して、含める pull request をまとめたり、特定のラベルとユーザーを出力に表示しないように除外したりすることもできます。
-You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
+## 新しいリリースの自動生成リリース ノートを作成する
-## Creating automatically generated release notes for a new release
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
- 
-4. {% ifversion fpt or ghec %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag.
- {% ifversion fpt or ghec %}
- 
-5. If you are creating a new tag, click **Create new tag**.
-
- {% else %}
- 
-{% endif %}
-6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
- {% ifversion fpt or ghec %}
- {% else %}
- {% endif %}
-{%- data reusables.releases.previous-release-tag %}
-7. To the top right of the description text box, click {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% ifversion previous-release-tag %}
- {% else %}
- {% endif %}
-8. Check the generated notes to ensure they include all (and only) the information you want to include.
-9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
- 
-10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
- 
-{%- ifversion fpt or ghec %}
-11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
- 
-{%- endif %}
-12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+3. **[新しいリリースの下書き]** をクリックします。
+ 
+4. {% ifversion fpt or ghec %} **[タグの選択]** をクリックして、{% else %}{% endif %}リリースのバージョン番号を入力します。 または、既存のタグを選びます。
+ {% ifversion fpt or ghec %} 
+5. 新しいタグを作成する場合は、 **[新しいタグの作成]** をクリックします。
+{% else %}{% endif %}
+6. 新しいタグを作成した場合は、ドロップダウン メニューを使ってリリース対象のプロジェクトを含むブランチを選択します。
+ {% ifversion fpt or ghec %} {% else %} {% endif %} {%- data reusables.releases.previous-release-tag %}
+7. 説明テキスト ボックスの右上で、{% ifversion previous-release-tag %} **[リリース ノートの生成]** {% else %} **[リリース ノートの自動生成]** {% endif %}.{% ifversion previous-release-tag %} ![[リリース ノートの生成]](/assets/images/help/releases/generate-release-notes.png){% else %} ![[リリース ノートの自動生成]](/assets/images/enterprise/3.5/releases/auto-generate-release-notes.png){% endif %}をクリックします
+8. 生成されたノートをチェックし、含めたい情報がすべて (そしてそれだけが) 含まれることを確認します。
+9. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。
+ 
+10. リリースが不安定であり、運用の準備ができていないことをユーザーに通知するには、 **[これはプレリリースです]** を選択します。
+ {%- ifversion fpt or ghec %}
+11. 必要に応じて、 **[このリリースのディスカッションを作成する]** を選び、 **[カテゴリ]** ドロップダウン メニューを選んでリリース ディスカッションのカテゴリをクリックします。
+ {%- endif %}
+12. リリースを公開する準備ができている場合は、 **[リリースの公開]** をクリックします。 リリースの作業を後でする場合は、 **[下書きの保存]** をクリックします。
+ ![[リリースの公開] と [下書きの保存] ボタン](/assets/images/help/releases/release_buttons.png)
-## Configuring automatically generated release notes
+## 自動生成リリース ノートを構成する
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory.
- 
-4. In the file, using the configuration options below, specify in YAML the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. ファイル名フィールドに「`.github/release.yml`」と入力して、`.github` ディレクトリに `release.yml` ファイルを作成します。
+ ![[新しいファイルの作成]](/assets/images/help/releases/release-yml.png)
+4. このファイルでは、以下の構成オプションを使って、このリリースから除外する pull request ラベルと作成者を YAML で指定します。 新しいカテゴリを作成し、それぞれに含める pull request ラベルを列記することもできます。
-### Configuration options
+### 構成オプション
-| Parameter | Description |
+| パラメーター | 説明 |
| :- | :- |
-| `changelog.exclude.labels` | A list of labels that exclude a pull request from appearing in release notes. |
-| `changelog.exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from release notes. |
-| `changelog.categories[*].title` | **Required.** The title of a category of changes in release notes. |
-| `changelog.categories[*].labels`| **Required.** Labels that qualify a pull request for this category. Use `*` as a catch-all for pull requests that didn't match any of the previous categories. |
-| `changelog.categories[*].exclude.labels` | A list of labels that exclude a pull request from appearing in this category. |
-| `changelog.categories[*].exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from this category. |
+| `changelog.exclude.labels` | リリース ノートに表示しない pull request のラベルの一覧。 |
+| `changelog.exclude.authors` | pull request をリリース ノートから除外するユーザーまたはボット ログイン ハンドルの一覧。 |
+| `changelog.categories[*].title` | **必須。** リリース ノートでの変更のカテゴリのタイトル。 |
+| `changelog.categories[*].labels`| **必須。** このカテゴリの pull request を修飾するラベル。 前のカテゴリのいずれにも一致しなかった pull request のキャッチオールとして `*` を使います。 |
+| `changelog.categories[*].exclude.labels` | このカテゴリに表示しない pull request のラベルの一覧。 |
+| `changelog.categories[*].exclude.authors` | pull request をこのカテゴリから除外するユーザーまたはボット ログイン ハンドルの一覧。 |
-### Example configurations
+### 構成例
-A configuration for a repository that labels semver releases
+semver リリースにラベルを付けるリポジトリの構成
{% raw %}
```yaml{:copy}
@@ -104,7 +96,7 @@ changelog:
```
{% endraw %}
-A configuration for a repository that doesn't tag pull requests but where we want to separate out {% data variables.product.prodname_dependabot %} automated pull requests in release notes (`labels: '*'` is required to display a catchall category)
+pull request にはタグを付けないが、{% data variables.product.prodname_dependabot %} の自動 pull request はリリース ノートで分離する必要があるリポジトリの構成 (汎用カテゴリを表示するために `labels: '*'` が必要です)
{% raw %}
```yaml{:copy}
@@ -124,6 +116,6 @@ changelog:
```
{% endraw %}
-## Further reading
+## 参考資料
-- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)"
+- [ラベルを管理する](/issues/using-labels-and-milestones-to-track-work/managing-labels)
diff --git a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
index 83f1fdfe25..c20396f4cc 100644
--- a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
+++ b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
@@ -1,6 +1,6 @@
---
title: リポジトリ間の接続を理解する
-intro: リポジトリのネットワークおよびそのリポジトリに依存するフォークやプロジェクトを表示することで、リポジトリ間に存在する接続をよりよく理解できます。
+intro: ネットワーク グラフとフォークの一覧を使用して、フォークのネットワークを理解します。
product: '{% data reusables.gated-features.repository-insights %}'
redirect_from:
- /articles/viewing-a-repository-s-network
@@ -22,16 +22,17 @@ versions:
topics:
- Repositories
shortTitle: Connections between repositories
-ms.openlocfilehash: f1b92a62d0acf9f31a16ce1b7c57850b87c1bf9c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 46cc440093c3ca8dc0952933847a6f04b0446661
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
ms.translationtype: HT
ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147060067'
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191359'
---
## リポジトリのネットワークを表示する
-ネットワークグラフには、ルートリポジトリのブランチとネットワークに固有のコミットを含むフォークのブランチを含む、リポジトリネットワーク全体のブランチ履歴が表示されます。
+ネットワーク グラフには、フォーク ブランチを含む、リポジトリ ネットワーク全体のブランチ履歴が表示されます。 このグラフは最新のコミットのタイムラインであり、最近ブランチにプッシュされたものが最大 100 個まで表示されます。 最初の行は日付を参照し、最初の列はブランチ所有者を参照します。 方向キーやその他のキーボード ショートカットを使用して、グラフをより簡単に移動できます。 それらは、グラフの下の [Keyboard shortcuts available] ポップアップに表示されます。
+
@@ -51,7 +52,7 @@ ms.locfileid: '147060067'
メンバーグラフには、リポジトリのすべてのフォークが表示されます。
-フォークは、リポジトリをフォークしたユーザの名前のアルファベット順に表示されます。 ユーザ名をクリックして、そのユーザの {% data variables.product.product_name %} プロフィール ページにリダイレクトすることも、フォーク名をクリックして、リポジトリの特定のフォークにリダイレクトすることもできます。
+フォークは、リポジトリをフォークしたユーザーの組織または名前のアルファベット順に表示されます。 組織またはユーザー名をクリックして、その組織またはユーザーの {% data variables.product.product_name %} プロファイル ページに移動したり、またはフォーク名をクリックして、リポジトリの特定のフォークに移動したりできます。
{% ifversion fpt or ghec %}
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/ja-JP/content/repositories/working-with-files/using-files/viewing-a-file.md
index ea88316e23..6a4ffe8a1f 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/viewing-a-file.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -1,6 +1,6 @@
---
-title: Viewing a file
-intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
+title: ファイルの表示
+intro: 生ファイルの内容を表示するか、ファイルの行に対する変更を追跡し、時間の経過とともにファイルの各部分がどのように変化したかを確認できます。
redirect_from:
- /articles/using-git-blame-to-trace-changes-in-a-file
- /articles/tracing-changes-in-a-file
@@ -16,48 +16,54 @@ versions:
topics:
- Repositories
shortTitle: View files and track file changes
+ms.openlocfilehash: 7d34e776cb1747ee749531e49abf6f0e3d052b3b
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179864'
---
-## Viewing or copying the raw file content
+## 生ファイルの内容を表示またはコピーする
-With the raw view, you can view or copy the raw content of a file without any styling.
+生のビューを使用すると、スタイルを設定せずにファイルの生のコンテンツを表示またはコピーできます。
{% data reusables.repositories.navigate-to-repo %}
-1. Click the file that you want to view.
-2. In the upper-right corner of the file view, click **Raw**.
-
-3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
+1. 表示するファイルをクリックします。
+2. ファイル ビューの右上隅にある **[未加工]** をクリックします。
+![ファイル ヘッダーの [未加工] ボタンのスクリーンショット](/assets/images/help/repository/raw-file-button.png)
+3. 必要に応じて、生ファイルの内容をコピーするには、ファイル ビューの右上隅にある **{% octicon "copy" aria-label="The copy icon" %}** をクリックします。
-## Viewing the line-by-line revision history for a file
+## ファイルの行ごとのリビジョン履歴の表示
-With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
+[変更履歴] ビューでは、{% octicon "versions" aria-label="The prior blame icon" %} をクリックすることで、ファイル全体の行ごとのリビジョン履歴やファイル内の 1 つの行のリビジョン履歴を表示することができます。 {% octicon "versions" aria-label="The prior blame icon" %} をクリックするたびに、変更をコミットした者と時間を含む、その行の過去のリビジョン情報が表示されます。
-
+
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+ファイルや pull request では、{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} メニューを使って、選択した行または行の範囲の Git blame を表示することもできます。
-
+
{% tip %}
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+**ヒント:** コマンド ラインでは、`git blame` を使用してファイル内の行のリビジョン履歴を表示することもできます。 詳細については、[Git`git blame` のドキュメント](https://git-scm.com/docs/git-blame)を参照してください。
{% endtip %}
{% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-
+2. クリックして、表示したい行の履歴のファイルを開きます。
+3. ファイル ビューの右上隅で **[変更履歴]** をクリックして [変更履歴] ビューを開きます。
+![[変更履歴]](/assets/images/help/repository/blame-button.png) ボタン
+4. 特定の行の過去のリビジョンを表示、または変更履歴の変更を行うには、見てみたい変更が見つかるまで {% octicon "versions" aria-label="The prior blame icon" %} をクリックします。
+
{% ifversion blame-ignore-revs %}
-## Ignore commits in the blame view
+## [変更履歴] ビューのコミットを無視する
-All revisions specified in the `.git-blame-ignore-revs` file, which must be in the root directory of your repository, are hidden from the blame view using Git's `git blame --ignore-revs-file` configuration setting. For more information, see [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) in the Git documentation.
+リポジトリのルート ディレクトリ内に存在しなければならない、`.git-blame-ignore-revs` ファイルで指定されたリビジョンはすべて、Git `git blame --ignore-revs-file` の構成設定を使用して、[変更履歴] ビューに表示されなくなります。 詳細については、Git ドキュメントにある「[`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt)」を参照してください。
-1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`.
-2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:
+1. リポジトリのルート ディレクトリに `.git-blame-ignore-revs` という名前のフォルダーを作成します。
+2. [変更履歴] ビューから除外するコミット ハッシュをそのファイルに追加します。 コメントを含め、次のようにファイルを構成することをお勧めします。
```ini
# .git-blame-ignore-revs
@@ -67,19 +73,19 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t
69d029cec8337c616552756310748c4a507bd75a
```
-3. Commit and push the changes.
+3. 変更をコミットしてプッシュします。
-Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden:
+ここで、[変更履歴] ビューにアクセスしても、一覧表示されたリビジョンは変更履歴に含まれません。 **[.git-blame-ignore-revs でのリビジョンの無視]** バナーが表示され、一部のコミットが非表示になっている可能性があることが示されます。
-
+![.git-blame-ignore-revs ファイルにリンクしている [変更履歴] ビューのバナーのスクリーンショット](/assets/images/help/repository/blame-ignore-revs-file.png)
-This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well:
+これは、いくつかのコミットがコードに広範な変更を加える場合に役立ちます。 このファイルは、ローカルで `git blame` を実行する場合にも使用できます。
```shell
git blame --ignore-revs-file .git-blame-ignore-revs
```
-You can also configure your local git so it always ignores the revs in that file:
+ローカル Git を構成して、そのファイルのリビジョンを常に無視することもできます。
```shell
git config blame.ignoreRevsFile .git-blame-ignore-revs
@@ -87,6 +93,6 @@ git config blame.ignoreRevsFile .git-blame-ignore-revs
{% endif %}
-## Bypassing `.git-blame-ignore-revs` in the blame view
+## [変更履歴] ビューで `.git-blame-ignore-revs` をバイパスする
-If the blame view for a file shows **Ignoring revisions in .git-blame-ignore-revs**, you can still bypass `.git-blame-ignore-revs` and see the normal blame view. In the URL, append a `~` to the SHA and the **Ignoring revisions in .git-blame-ignore-revs** will disappear.
+ファイルの [変更履歴] ビューに **[Ignoring revisions in .git-blame-ignore-revs]\(.git-blame-ignore-revs でリビジョンを無視する\)** と表示されている場合でも、`.git-blame-ignore-revs` をバイパスして通常の [変更履歴] ビューを表示できます。 URL で `~` を SHA に追加すると、 **[Ignoring revisions in .git-blame-ignore-revs]\(.git-blame-ignore-revs でリビジョンを無視する\)** が消えます。
diff --git a/translations/ja-JP/content/rest/overview/libraries.md b/translations/ja-JP/content/rest/overview/libraries.md
index 10c5b704b1..ff89d07644 100644
--- a/translations/ja-JP/content/rest/overview/libraries.md
+++ b/translations/ja-JP/content/rest/overview/libraries.md
@@ -11,12 +11,12 @@ versions:
ghec: '*'
topics:
- API
-ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
-ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
+ms.openlocfilehash: 5f633132edddb17ae129a3feba791ab8ec780366
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: ja-JP
-ms.lasthandoff: 12/01/2022
-ms.locfileid: '148190062'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191879'
---
@@ -26,7 +26,7 @@ ms.locfileid: '148190062'
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
-- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+- **JavaScript** → [octokit.js](https://github.com/octokit/octokit.js)
## サードパーティ製ライブラリ
diff --git a/translations/ja-JP/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/ja-JP/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
index 1795e64950..e53a389ec6 100644
--- a/translations/ja-JP/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
+++ b/translations/ja-JP/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -1,6 +1,6 @@
---
-title: サポート チケットの表示と更新
-intro: '{% data variables.contact.support_portal %} を使って、サポート チケットを表示したり、{% ifversion ghes or ghec %}同僚と共同でチケットの作業を行ったり、{% endif %}{% data variables.contact.github_support %} に応答したりできます。'
+title: Viewing and updating support tickets
+intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.'
shortTitle: Managing your tickets
versions:
fpt: '*'
@@ -8,62 +8,64 @@ versions:
ghes: '*'
topics:
- Support
-ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147051981'
---
-## チケット管理について
+
+## About ticket management
{% data reusables.support.zendesk-old-tickets %}
-[GitHub Support ポータル](https://support.github.com/)を使用して、現在および過去のサポート チケットを表示し、{% data variables.contact.github_support %} に応答できます。 120 日を過ぎると、解決されたチケットはアーカイブされ{% ifversion ghec or ghes or ghae %}、アーカイブされたチケットは Enterprise アカウントについてのみ表示でき{% endif %}ます。
+You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}. After 120 days, resolved tickets are archived{% ifversion ghec or ghes or ghae %}, and archived tickets can only be viewed for enterprise accounts{% endif %}.
-{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+{% ifversion ghes or ghec %}
+{% data reusables.enterprise-accounts.support-entitlements %}
+{% endif %}
-## 最近のサポート チケットを表示する
+## Viewing your recent support tickets
{% data reusables.support.view-open-tickets %}
-1. テキスト ボックスの下で、コメント履歴を読むことができます。 最新の応答は一番上にあります。
-
+1. Under the text box, you can read the comment history. The most recent response is at the top.
+
+ 
+
+1. Optionally, to translate the ticket comment, click {% octicon "globe" aria-label="The globe icon" %} and choose your preferred language from the dropdown menu. You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish.
+
+ 
{% ifversion ghec or ghes or ghae %}
-## アーカイブされたサポート チケットを表示する
+## Viewing your archived support tickets
-Enterprise アカウントのアーカイブ済みチケットのみを表示できます。
+You can only view archived tickets for an enterprise account.
{% data reusables.support.navigate-to-my-tickets %}
-1. **[マイ チケット]** ドロップダウン メニューを選んで、Enterprise アカウントの名前をクリックします。
+1. Select the **My Tickets** drop-down menu and click the name of the enterprise account.
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
- ![[マイ チケット] ドロップダウン メニューのスクリーンショット。](/assets/images/help/support/ticket-context.png)
-1. [マイ チケット] テーブルで **[アーカイブ済みチケットの表示]** をクリックします。
+ 
+1. Under the "My tickets" table, click **View archived tickets**.
{% endif %}
-## サポート チケットの更新
+## Updating support tickets
{% data reusables.support.view-open-tickets %}
-1. 必要に応じて、Issue が解決した場合は、テキスト ボックスの下にある **[チケットを閉じる]** をクリックします。
-![[チケットを閉じる] ボタンの場所を示すスクリーンショット。](/assets/images/help/support/close-ticket.png)
-1. GitHub Support に返信し、チケットに新しいコメントを追加するには、テキスト ボックスに返信を入力します。
-![[コメントの追加] テキスト フィールドのスクリーンショット。](/assets/images/help/support/new-comment-field.png)
-1. チケットにコメントを追加するには、 **[コメント]** をクリックします。
-![[コメント] ボタンのスクリーンショット。](/assets/images/help/support/add-comment.png)
+1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
+
+1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
+
+1. To add your comment to the ticket, click **Comment**.
+
{% ifversion ghec or ghes %}
-## サポート チケットでの共同作業
+## Collaborating on support tickets
-サポート ポータルを使用して、サポート チケットについて同僚と共同作業を行うことができます。 所有者、課金マネージャー、サポート資格を持つその他のエンタープライズ メンバーは、エンタープライズ アカウントまたはエンタープライズ アカウントによって管理されている Organization に関連付けられているチケットを表示できます。 詳細については、「[Managing support entitlements for your enterprise (エンタープライズのサポート エンタイトルメントの管理)](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)」を参照してください。
+You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-チケットの表示に加えて、チケットに自分のメール アドレスがコピーされている場合や、チケットを開いた人がエンタープライズ アカウントまたはエンタープライズ アカウントで管理されている Organization で確認済みのドメインを持つメール アドレスを使用した場合は、サポート チケットにコメントを追加することもできます。 ドメインの確認の詳細については、「[企業のドメインの確認または承認](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)」および「[Organization のドメインの確認または承認](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)」を参照してください。
+In addition to viewing tickets, you can also add comments to support tickets if your email address is copied on the ticket or if the person who opened the ticket used an email address with a domain that is verified for the enterprise account or organization managed by an enterprise account. For more information about verifying a domain, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Verifying or approving a domain for your organization](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
{% endif %}
-## 参考資料
+## Further reading
-- "[GitHub サポートについて](/support/learning-about-github-support/about-github-support)"
+- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
diff --git a/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md b/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
index f5d6525f05..be735ece17 100644
--- a/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
@@ -83,6 +83,10 @@ If you have any paid product or are a member of an organization with a paid prod
With {% data variables.product.product_name %}, you have access to support in English and Japanese.
{% endif %}
+{% ifversion fpt or ghec or ghes %}
+{% data reusables.support.support-ticket-translation-option %}
+{% endif %}
+
{% ifversion ghes or ghec %}
To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/4.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/4.yml
index 028b8750b6..2d4ef88879 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/4.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/4.yml
@@ -29,4 +29,5 @@ sections:
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
- |
- GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
\ No newline at end of file
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/5.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/5.yml
index 93275748e6..05de05ac2b 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/5.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/5.yml
@@ -1,27 +1,30 @@
date: '2022-08-30'
sections:
bugs:
- - 一時的なアクセスのためにリポジトリのロックを解除した後、サイト管理者はリポジトリのセキュリティ製品の設定を管理できませんでした。
- - 管理コンソールと `/home/admin/.ssh/authorized_keys` ファイルの両方に、重複する管理 SSH キーが表示されることがありました。
- - "http(s)://<ホスト名>/stafftools/users/<ユーザー名>/admin の個人ユーザー向けサイト管理者ページに、GitHub Enterprise Server には意図されていない機能が含まれました。"
- - 場合によっては、`ghe-cluster-config-apply` を実行して空の構成をクラスターの既存のノードにレプリケートできました。
- - "`ghe-config-apply` で開始された構成の実行が、完了しないこと、または`Container count mismatch` エラーを返すことがありました。"
- - GitHub Enterprise Server インスタンス上の自己署名 TLS 証明書を更新した後、Web インターフェイスの一部のページの UI 要素が表示されませんでした。
- - Web インターフェイスの上部のサイト管理者バーに含まれる、現在実行中のアプリケーションのバージョンに対する SHA へのリンクが、壊れていました。
- - 場合によっては、スレッドセーフではないにも関わらず同時に使われたライブラリのため、バックグラウンド タスクが停止することがありました。
- - サイト管理者が GitHub Enterprise Server 3.4 に直接アップグレードしなかった場合、GitHub Advanced Security のお客様に対するシークレット スキャンからのアラートが、Web UI と REST API に表示されませんでした。現在は、アラートが表示されます。
- - ユーザーがリポジトリを Organization にフォークするとき、Organization の長い一覧が正しくレンダリングされませんでした。
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
+ - When a user forked a repository into an organization, a long list of organizations would not render properly.
changes:
- - "並列化されたログ サニタイズの結果、サポート バンドルの生成が速くなっています。サポート バンドルについて詳しくは、「[GitHub Support へのデータの提供](/support/contacting-github-support/providing-data-to-github-support)」をご覧ください。"
- - "`organization` または `org` ルートを含む API が、Organization のスラッグまたは ID を受け取るようになりました。以前の API はスラッグのみを受け取っており、そのために GitHub Advanced Security エンドポイントの `Link` ヘッダーにアクセスできませんでした。詳しくは、REST API のドキュメントの「[組織](https://docs.github.com/rest/orgs/orgs)」をご覧ください。"
- - "Enterprise の監査ログに含まれるユーザー生成イベントが増えました (`project.create` など)。REST API からも、追加のユーザー生成イベントが返されます (`repo.create` など)。詳しくは、「[企業の監査ログにアクセスする](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)」と「[Enterprise 用の監査ログ API の使用](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)」をご覧ください。"
- - "キャッシュ レプリカが、最近更新されたリポジトリでの一部の Git 操作を拒否することがありました。リポジトリのキャッシュについて詳しくは、「[リポジトリのキャッシュについて](/admin/enterprise-management/caching-repositories/about-repository-caching)」をご覧ください。"
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
known_issues:
- - "{% data variables.product.prodname_ghe_server %} インスタンスを設定したばかりでユーザーがいない場合、攻撃者が最初の管理者ユーザーを作成できました。"
- - カスタムのファイアウォール規則は、アップグレード プロセス中に削除されます。
- - "[Web インターフェイスからアップロードされた](https://github.com/blog/2105-upload-files-to-your-repositories) Git LFS 追跡ファイルが誤ってリポジトリに直接追加されます。"
- - 同じリポジトリ内の BLOB への固定リンクが含まれ、その BLOB のファイル パスが 255 文字を超える場合、issue はクローズできません。
- - "GitHub Connect で [Users can search GitHub.com]\\(ユーザーが GitHub.com を検索できる\\) が有効になっている場合、プライベートと内部リポジトリのイシューが GitHub.com の検索結果に含まれません。"
- - "{% data variables.product.prodname_registry %} npm レジストリが、メタデータ応答で時刻値を返さなくなります。これは、パフォーマンスの大幅な向上を見込んで行われました。メタデータ応答の一部として時刻値を返すために必要なすべてのデータを引き続き保持します。また、既存のパフォーマンスの問題を解決したら、将来的にはこの値を再び返す予定です。"
- - pre-receive フックの処理に固有のリソース制限が、一部の pre-receive フックのエラーを引き起こす場合があります。
- - 別のホストで作成されたバックアップからアプライアンスを復元した後、Actions のサービスを再起動する必要があります。
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-6/1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-6/1.yml
index 14749e4e64..6e638df146 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-6/1.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-6/1.yml
@@ -1,33 +1,38 @@
date: '2022-08-30'
sections:
bugs:
- - 一時的なアクセスのためにリポジトリのロックを解除した後、サイト管理者はリポジトリのセキュリティ製品の設定を管理できませんでした。
- - 管理コンソールと `/home/admin/.ssh/authorized_keys` ファイルの両方に、重複する管理 SSH キーが表示されることがありました。
- - "http(s)://<ホスト名>/stafftools/users/<ユーザー名>/admin の個人ユーザー向けサイト管理者ページに、GitHub Enterprise Server には意図されていない機能が含まれました。"
- - 場合によっては、`ghe-cluster-config-apply` を実行して空の構成をクラスターの既存のノードにレプリケートできました。
- - "`ghe-config-apply` で開始された構成の実行が、完了しないこと、または`Container count mismatch` エラーを返すことがありました。"
- - GitHub Enterprise Server インスタンス上の自己署名 TLS 証明書を更新した後、Web インターフェイスの一部のページの UI 要素が表示されませんでした。
- - 場合によっては、スレッドセーフではないにも関わらず同時に使われたライブラリのため、バックグラウンド タスクが停止することがありました。
- - Web インターフェイスの上部のサイト管理者バーに含まれる、現在実行中のアプリケーションのバージョンに対する SHA へのリンクが、壊れていました。
- - Organization 所有者は、ディスカッションの作成に必要なアクセスのレベルを設定できませんでした。
- - ディスカッションのユーザーは、GitHub.com のコミュニティ ガイドラインに誤って誘導されました。
- - ユーザーは、ディスカッションを作成する前にメールを検証するよう、誤って指示されることがありました。
- - サイト管理者が GitHub Enterprise Server 3.4 に直接アップグレードしなかった場合、GitHub Advanced Security のお客様に対するシークレット スキャンからのアラートが、Web UI と REST API に表示されませんでした。現在は、アラートが表示されます。
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - Organization owners were unable to set the level of access required to create discussions.
+ - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
+ - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
changes:
- - "並列化されたログ サニタイズの結果、サポート バンドルの生成が速くなっています。サポート バンドルについて詳しくは、「[GitHub Support へのデータの提供](/support/contacting-github-support/providing-data-to-github-support)」をご覧ください。"
- - "`organization` または `org` ルートを含む API が、Organization のスラッグまたは ID を受け取るようになりました。以前の API はスラッグのみを受け取っており、そのために GitHub Advanced Security エンドポイントの `Link` ヘッダーにアクセスできませんでした。詳しくは、REST API のドキュメントの「[組織](https://docs.github.com/rest/orgs/orgs)」をご覧ください。"
- - "Enterprise の監査ログに含まれるユーザー生成イベントが増えました (`project.create` など)。REST API からも、追加のユーザー生成イベントが返されます (`repo.create` など)。詳しくは、「[企業の監査ログにアクセスする](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)」と「[Enterprise 用の監査ログ API の使用](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)」をご覧ください。"
- - "キャッシュ レプリカが、最近更新されたリポジトリでの一部の Git 操作を拒否することがありました。リポジトリのキャッシュについて詳しくは、「[リポジトリのキャッシュについて](/admin/enterprise-management/caching-repositories/about-repository-caching)」をご覧ください。"
- - "REST API を使って閉じることができるよう、グローバル通知バナーを構成できるようになりました。詳しくは、「[Enterprise のユーザメッセージをカスタマイズする](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)」をご覧ください。"
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+ - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
known_issues:
- - "{% data variables.product.prodname_ghe_server %} インスタンスを設定したばかりでユーザーがいない場合、攻撃者が最初の管理者ユーザーを作成できました。"
- - カスタムのファイアウォール規則は、アップグレード プロセス中に削除されます。
- - "[Web インターフェイスからアップロードされた](https://github.com/blog/2105-upload-files-to-your-repositories) Git LFS 追跡ファイルが誤ってリポジトリに直接追加されます。"
- - 同じリポジトリ内の BLOB への固定リンクが含まれ、その BLOB のファイル パスが 255 文字を超える場合、issue はクローズできません。
- - "GitHub Connect で [Users can search GitHub.com]\\(ユーザーが GitHub.com を検索できる\\) が有効になっている場合、プライベートと内部リポジトリのイシューが GitHub.com の検索結果に含まれません。"
- - "{% data variables.product.prodname_registry %} npm レジストリが、メタデータ応答で時刻値を返さなくなります。これは、パフォーマンスの大幅な向上を見込んで行われました。メタデータ応答の一部として時刻値を返すために必要なすべてのデータを引き続き保持します。また、既存のパフォーマンスの問題を解決したら、将来的にはこの値を再び返す予定です。"
- - pre-receive フックの処理に固有のリソース制限が、一部の pre-receive フックのエラーを引き起こす場合があります。
- - 別のホストで作成されたバックアップからインスタンスを復元した後、Actions のサービスを再起動する必要があります。
- - リポジトリの設定で、読み取りアクセス権を持つユーザーにディスカッションの作成を許可するオプションを有効にしても、この機能は有効になりません。
- - ユーザーが既存の issue をディスカッションに変換できない場合があります。
- - "シークレット スキャンのカスタム パターンの末尾の区切り記号は `.*` です (具体的には [After secret]\\(シークレットの後\\) フィールド)。この区切り記号のためにリポジトリ間でのシークレットのスキャンで不整合が発生し、リポジトリの履歴にスキャンが完了していないギャップができる場合があります。増分スキャンも影響を受ける場合があります。スキャンでの問題を避けるには、パターンの末尾を変更して、`.*` 区切り記号を削除します。"
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+ - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+ - In some cases, users cannot convert existing issues to discussions.
+ - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+ - |
+ After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 9060c34cb7..1193172cdd 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,18 +1,10 @@
----
-ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145114230"
----
-`jobs..if` 条件文を使って、条件が満たされなければジョブを実行しないようにできます。 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
+You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
-{% data reusables.actions.expression-syntax-if %} 詳細については、「[式](/actions/learn-github-actions/expressions)」を参照してください。
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
-### 例: 特定のリポジトリに対してのみジョブを実行する
+### Example: Only run job for specific repository
-この例では `if` を使って `production-deploy` ジョブを実行できるタイミングを制御しています。 リポジトリが `octo-repo-prod` という名前で、`octo-org` という組織内にある場合のみ実行されます。 それ以外の場合、ジョブはスキップ済みとしてマーク _されます_。
+This example uses `if` to control when the `production-deploy` job can run. It will only run if the repository is named `octo-repo-prod` and is within the `octo-org` organization. Otherwise, the job will be marked as _skipped_.
```yaml{:copy}
name: example-workflow
diff --git a/translations/ja-JP/data/reusables/actions/reusable-workflows-enterprise-beta.md b/translations/ja-JP/data/reusables/actions/reusable-workflows-enterprise-beta.md
new file mode 100644
index 0000000000..6064e0e17e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/reusable-workflows-enterprise-beta.md
@@ -0,0 +1,17 @@
+{% ifversion ghes = 3.4 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently in beta and subject to change.
+
+{% endnote %}
+
+{% elsif ghae > 3.3 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently unavailable in {% data variables.product.product_name %}, but will be available in a future update.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/ja-JP/data/reusables/actions/reusable-workflows-ghes-beta.md
deleted file mode 100644
index d0cbeb0512..0000000000
--- a/translations/ja-JP/data/reusables/actions/reusable-workflows-ghes-beta.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-ms.openlocfilehash: 933805023c32c3e956b510000cdaff7326b880e3
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145068098"
----
-{% ifversion ghes = 3.4 %}
-
-{% note %}
-
-**注**: 再利用できるワークフローは現在ベータ版であり、変更される可能性があります。
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-activity.md
index 80878d1726..24b839f410 100644
--- a/translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-activity.md
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
- Starring a repository
- Deleting a repository
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
+- Joining an organization
+
+{% ifversion ghes %}
+A user will also be considered active if their account has been updated by LDAP.
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md
index 558a3b591a..23ab856128 100644
--- a/translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md
@@ -1 +1,9 @@
-{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.
+---
+ms.openlocfilehash: 484a4230527deebe6f4aeb24ceabdf95eb75b492
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/03/2022
+ms.locfileid: "148191331"
+---
+{% data variables.enterprise.prodname_managed_users_caps %} では、エンタープライズの外部からリポジトリをフォークできません。 {% data variables.enterprise.prodname_managed_users_caps %} では、エンタープライズ ポリシーで指定されているように、エンタープライズ内の組織が所有するプライベート リポジトリまたは内部リポジトリを、そのユーザー アカウント名前空間またはエンタープライズが所有する他の組織にフォークできます。
diff --git a/translations/ja-JP/data/reusables/repositories/fork-definition-long.md b/translations/ja-JP/data/reusables/repositories/fork-definition-long.md
new file mode 100644
index 0000000000..b829d0817c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/repositories/fork-definition-long.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eb538c8746bf9d5ec4cd0e422e50ccc032309812
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/03/2022
+ms.locfileid: "148191374"
+---
+フォークとは、元の "上流" リポジトリとコードと可視性の設定を共有する新しいリポジトリです。 多くの場合、フォークは、上流リポジトリに再提案する前に、アイデアや変更に繰り返し取り組むために使用されます。たとえば、オープンソース プロジェクトや、ユーザーが上流リポジトリへの書き込みアクセス権を持っていない場合などです。
diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml
index 1e8377dd72..29dec0fbef 100644
--- a/translations/ja-JP/data/ui.yml
+++ b/translations/ja-JP/data/ui.yml
@@ -127,7 +127,7 @@ products:
rest:
banner:
api_versioned: The REST API is now versioned.
- api_version_info: For more information, see "About API versioning".
+ api_version_info: For more information, see "About API versioning."
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "About versions of GitHub Docs".
versioning:
about_versions: About REST API versions
diff --git a/translations/ko-KR/content/actions/creating-actions/about-custom-actions.md b/translations/ko-KR/content/actions/creating-actions/about-custom-actions.md
index 8802ca57a0..eca2fa067c 100644
--- a/translations/ko-KR/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/ko-KR/content/actions/creating-actions/about-custom-actions.md
@@ -16,12 +16,12 @@ type: overview
topics:
- Action development
- Fundamentals
-ms.openlocfilehash: ac933a5014750f75373fafa7f8dd52333b79a469
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
+ms.openlocfilehash: 1e81bea551ceff1980b0bbe96202f60db0d0e7f2
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: MT
ms.contentlocale: ko-KR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147154575'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191950'
---
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
@@ -35,7 +35,7 @@ ms.locfileid: '147154575'
## 동작 유형
-Docker 컨테이너 및 JavaScript 작업을 빌드할 수 있습니다. 작업에는 작업에 대한 입력, 출력, 기본 진입점을 정의하는 메타데이터 파일이 필요합니다. 메타데이터 파일 이름은 `action.yml` 또는 `action.yaml`이어야 합니다. 자세한 내용은 “[{% data variables.product.prodname_actions %}에 대한 메타데이터 구문](/articles/metadata-syntax-for-github-actions)”을 참조하세요.
+Docker 컨테이너, JavaScript 및 복합 작업을 빌드할 수 있습니다. 작업에는 작업에 대한 입력, 출력, 기본 진입점을 정의하는 메타데이터 파일이 필요합니다. 메타데이터 파일 이름은 `action.yml` 또는 `action.yaml`이어야 합니다. 자세한 내용은 “[{% data variables.product.prodname_actions %}에 대한 메타데이터 구문](/articles/metadata-syntax-for-github-actions)”을 참조하세요.
| 형식 | 운영 체제 |
| ---- | ------------------- |
diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md
index 382e81006b..c1b63fc9c2 100644
--- a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md
@@ -1,7 +1,7 @@
---
-title: Creating a composite action
+title: 복합 작업 만들기
shortTitle: Create a composite action
-intro: 'In this guide, you''ll learn how to build a composite action.'
+intro: 이 가이드에서는 복합 작업을 빌드하는 방법을 알아봅니다.
redirect_from:
- /actions/creating-actions/creating-a-composite-run-steps-action
versions:
@@ -12,58 +12,61 @@ versions:
type: tutorial
topics:
- Action development
+ms.openlocfilehash: 5c7d332d2b3626a5628e85b09c35ffa6a0ca5f33
+ms.sourcegitcommit: 4f08a208a0d2e13dc109678750a962ea2f67e1ba
+ms.translationtype: MT
+ms.contentlocale: ko-KR
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148192041'
---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## 소개
-## Introduction
+이 가이드에서는 패키지된 복합 작업을 만들고 사용하는 데 필요한 기본 구성 요소에 대해 알아봅니다. 작업을 패키지하는 데 필요한 구성 요소에 가이드의 초점을 맞추기 위해 작업 코드의 기능은 최소화됩니다. 작업은 “Hello World”를 출력한 다음 “Goodbye”를 출력하거나 사용자 지정 이름을 제공하는 경우 “Hello [인사할 사람]”을 출력한 다음 “Goodbye”를 출력합니다. 이 작업은 또한 난수를 `random-number` 출력 변수에 매핑하고 `goodbye.sh`라는 스크립트를 실행합니다.
-In this guide, you'll learn about the basic components needed to create and use a packaged composite action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" and then "Goodbye", or if you provide a custom name, it prints "Hello [who-to-greet]" and then "Goodbye". The action also maps a random number to the `random-number` output variable, and runs a script named `goodbye.sh`.
-
-Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
+이 프로젝트를 완료한 후에는 고유한 복합 작업을 빌드하고 워크플로에서 테스트하는 방법을 이해해야 합니다.
{% data reusables.actions.context-injection-warning %}
-## Prerequisites
+## 필수 조건
-Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+시작하기 전에 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}에 리포지토리를 만듭니다.
-1. Create a new public repository on {% data variables.location.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. {% data variables.location.product_location %}에 새 퍼블릭 리포지토리를 만듭니다. 리포지토리 이름을 선택하거나 다음 `hello-world-composite-action` 예제를 사용할 수 있습니다. 프로젝트가 {% data variables.product.product_name %}에 푸시된 후 이러한 파일을 추가할 수 있습니다. 자세한 내용은 “[새 리포지토리 만들기](/articles/creating-a-new-repository)”를 참조하세요.
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. 컴퓨터에 리포지토리를 복제합니다. 자세한 내용은 “[리포지토리 복제](/articles/cloning-a-repository)”를 참조하세요.
-1. From your terminal, change directories into your new repository.
+1. 터미널에서 디렉터리를 새 리포지토리로 변경합니다.
```shell
cd hello-world-composite-action
```
-2. In the `hello-world-composite-action` repository, create a new file called `goodbye.sh`, and add the following example code:
+2. `hello-world-composite-action` 리포지토리에서 `goodbye.sh`라는 새 파일을 만들고 다음 예제 코드를 추가합니다.
```bash
echo "Goodbye"
```
-3. From your terminal, make `goodbye.sh` executable.
+3. 터미널에서 `goodbye.sh` 실행 파일을 만듭니다.
```shell
chmod +x goodbye.sh
```
-1. From your terminal, check in your `goodbye.sh` file.
+1. 터미널에서 `goodbye.sh` 파일을 체크 인합니다.
```shell
git add goodbye.sh
git commit -m "Add goodbye script"
git push
```
-## Creating an action metadata file
+## 작업 메타데이터 파일 만들기
-1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
+1. `hello-world-composite-action` 리포지토리에서 `action.yml`라는 새 파일을 만들고 다음 예제 코드를 추가합니다. 이 구문에 대한 자세한 내용은 “[`runs` 복합 작업](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)”을 참조하세요.
- {% raw %}
- **action.yml**
+ {% raw %} **action.yml**
```yaml
name: 'Hello World'
description: 'Greet someone'
@@ -93,14 +96,13 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
- run: goodbye.sh
shell: bash
```
- {% endraw %}
- This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+ {% endraw %} 이 파일은 입력을 `who-to-greet` 정의하고, 임의의 생성된 숫자를 출력 변수에 `random-number` 매핑하고, 실행기 시스템 경로에 작업의 경로를 추가하고(실행 중에 스크립트를 찾기 `goodbye.sh` 위해) 스크립트를 실행합니다 `goodbye.sh` .
- For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
+ 출력 관리에 대한 자세한 내용은 “[복합 작업에 대한 `outputs` ](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)”을 참조하세요.
- For more information about how to use `github.action_path`, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+ `github.action_path` 사용 방법에 대한 자세한 내용은 “[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)”를 참조하세요.
-1. From your terminal, check in your `action.yml` file.
+1. 터미널에서 `action.yml` 파일을 체크 인합니다.
```shell
git add action.yml
@@ -108,18 +110,18 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
git push
```
-1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+1. 터미널에서 태그를 추가합니다. 이 예제에서는 `v1`이라는 태그를 사용합니다. 자세한 내용은 “[작업 정보](/actions/creating-actions/about-actions#using-release-management-for-actions)”를 참조하세요.
```shell
git tag -a -m "Description of this release" v1
git push --follow-tags
```
-## Testing out your action in a workflow
+## 워크플로에서 작업 테스트
-The following workflow code uses the completed hello world action that you made in "[Creating an action metadata file](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
+다음 워크플로 코드는 “[작업 메타데이터 파일 만들기](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)”에서 수행한 완료된 hello world 작업을 사용합니다.
-Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name.
+워크플로 코드를 다른 리포지토리의 `.github/workflows/main.yml` 파일에 복사하지만 `actions/hello-world-composite-action@v1`는 만든 리포지토리 및 태그로 바꿉니다. `who-to-greet` 입력을 자신의 이름으로 바꿀 수도 있습니다.
**.github/workflows/main.yml**
```yaml
@@ -139,4 +141,4 @@ jobs:
shell: bash
```
-From your repository, click the **Actions** tab, and select the latest workflow run. The output should include: "Hello Mona the Octocat", the result of the "Goodbye" script, and a random number.
+리포지토리에서 **작업** 탭을 클릭하고 최신 워크플로 실행을 선택합니다. 출력에는 “Hello Mona the Octocat”, “Goodbye” 스크립트의 결과와 난수가 포함되어야 합니다.
diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md
index 5a1ea071a9..8dcb762313 100644
--- a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md
@@ -271,3 +271,10 @@ jobs:
From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+
+## Template repositories for creating JavaScript actions
+
+{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
+
+* [`javascript-action` template repository](https://github.com/actions/javascript-action)
+* [`typescript-action` template repository](https://github.com/actions/typescript-action)
diff --git a/translations/ko-KR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/ko-KR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index 30c0ee6762..a1760abf81 100644
--- a/translations/ko-KR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/ko-KR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -1,7 +1,7 @@
---
-title: About security hardening with OpenID Connect
+title: OpenID Connect를 사용한 보안 강화 정보
shortTitle: Security hardening with OpenID Connect
-intro: OpenID Connect allows your workflows to exchange short-lived tokens directly from your cloud provider.
+intro: OpenID Connect를 사용하면 워크플로가 클라우드 공급자에서 직접 단기 토큰을 교환할 수 있습니다.
miniTocMaxHeadingLevel: 4
versions:
fpt: '*'
@@ -10,50 +10,54 @@ versions:
type: tutorial
topics:
- Security
+ms.openlocfilehash: 90a2f8c6cb2114f060bfbd0f422cb1ef6dbca604
+ms.sourcegitcommit: 4f08a208a0d2e13dc109678750a962ea2f67e1ba
+ms.translationtype: MT
+ms.contentlocale: ko-KR
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148192033'
---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## OpenID Connect 개요
-## Overview of OpenID Connect
+{% data variables.product.prodname_actions %} 워크플로는 종종 소프트웨어를 배포하거나 클라우드의 서비스를 사용하기 위해 클라우드 공급자(예: AWS, Azure, GCP 또는 HashiCorp Vault)에 액세스하도록 설계되었습니다. 워크플로가 이러한 리소스에 액세스하기 전에 클라우드 공급자에게 암호 또는 토큰과 같은 자격 증명을 제공합니다. 이러한 자격 증명은 일반적으로 {% data variables.product.prodname_dotcom %}에 비밀로 저장되며 워크플로는 실행될 때마다 클라우드 공급자에게 이 비밀을 제공합니다.
-{% data variables.product.prodname_actions %} workflows are often designed to access a cloud provider (such as AWS, Azure, GCP, or HashiCorp Vault) in order to deploy software or use the cloud's services. Before the workflow can access these resources, it will supply credentials, such as a password or token, to the cloud provider. These credentials are usually stored as a secret in {% data variables.product.prodname_dotcom %}, and the workflow presents this secret to the cloud provider every time it runs.
+그러나 하드 코딩된 비밀을 사용하려면 클라우드 공급자에서 자격 증명을 만든 다음, {% data variables.product.prodname_dotcom %}에서 비밀로 복제해야 합니다.
-However, using hardcoded secrets requires you to create credentials in the cloud provider and then duplicate them in {% data variables.product.prodname_dotcom %} as a secret.
+OIDC(OpenID Connect)를 사용하면 클라우드 공급자에게 직접 수명이 짧은 액세스 토큰을 요청하도록 워크플로를 구성하여 다른 접근 방식을 취할 수 있습니다. 또한 클라우드 공급자는 OIDC를 지원해야 하며, 액세스 토큰을 요청할 수 있는 워크플로를 제어하는 트러스트 관계를 구성해야 합니다. 현재 OIDC를 지원하는 공급자로는 Amazon Web Services, Azure, Google Cloud Platform 및 HashiCorp Vault 등이 있습니다.
-With OpenID Connect (OIDC), you can take a different approach by configuring your workflow to request a short-lived access token directly from the cloud provider. Your cloud provider also needs to support OIDC on their end, and you must configure a trust relationship that controls which workflows are able to request the access tokens. Providers that currently support OIDC include Amazon Web Services, Azure, Google Cloud Platform, and HashiCorp Vault, among others.
+### OIDC 사용의 장점
-### Benefits of using OIDC
+OIDC 토큰을 사용하도록 워크플로를 업데이트하면 다음과 같은 적절한 보안 사례를 채택할 수 있습니다.
-By updating your workflows to use OIDC tokens, you can adopt the following good security practices:
+- **클라우드 비밀 없음**: 수명이 긴 {% data variables.product.prodname_dotcom %} 비밀로 클라우드 자격 증명을 복제할 필요가 없습니다. 대신 클라우드 공급자에서 OIDC 트러스트를 구성한 다음, 워크플로를 업데이트하여 OIDC를 통해 클라우드 공급자로부터 단기 액세스 토큰을 요청할 수 있습니다.
+- **인증 및 권한 부여 관리**: 워크플로가 자격 증명을 사용하고 클라우드 공급자의 인증(authN) 및 권한 부여(authZ) 도구를 사용하여 클라우드 리소스에 대한 액세스를 제어하는 방법을 보다 세부적으로 제어할 수 있습니다.
+- **자격 증명 순환**: OIDC를 사용하면 클라우드 공급자가 단일 작업에만 유효한 수명이 짧은 액세스 토큰을 발급한 다음, 자동으로 만료됩니다.
-- **No cloud secrets**: You won't need to duplicate your cloud credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. Instead, you can configure the OIDC trust on your cloud provider, and then update your workflows to request a short-lived access token from the cloud provider through OIDC.
-- **Authentication and authorization management**: You have more granular control over how workflows can use credentials, using your cloud provider's authentication (authN) and authorization (authZ) tools to control access to cloud resources.
-- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single job, and then automatically expires.
+### OIDC 시작
-### Getting started with OIDC
+다음 다이어그램에서는 {% data variables.product.prodname_dotcom %}의 OIDC 공급자가 워크플로 및 클라우드 공급자와 통합되는 방법에 대한 개요를 제공합니다.
-The following diagram gives an overview of how {% data variables.product.prodname_dotcom %}'s OIDC provider integrates with your workflows and cloud provider:
+
-
+1. 클라우드 공급자에서 클라우드에 액세스해야 하는 클라우드 역할과 {% data variables.product.prodname_dotcom %} 워크플로 간에 OIDC 트러스트를 만듭니다.
+2. 작업이 실행될 때마다 {% data variables.product.prodname_dotcom %}의 OIDC 공급자는 OIDC 토큰을 자동으로 생성합니다. 이 토큰에는 인증하려는 특정 워크플로에 대해 보안이 강화되고 확인 가능한 ID를 설정하는 여러 클레임이 포함되어 있습니다.
+3. {% data variables.product.prodname_dotcom %}의 OIDC 공급자에서 이 토큰을 요청하고 클라우드 공급자에게 표시하는 단계 또는 동작을 작업에 포함할 수 있습니다.
+4. 클라우드 공급자가 토큰에 제공된 클레임의 유효성을 성공적으로 검사하면 작업 기간 동안에만 사용할 수 있는 수명이 짧은 클라우드 액세스 토큰을 제공합니다.
-1. In your cloud provider, create an OIDC trust between your cloud role and your {% data variables.product.prodname_dotcom %} workflow(s) that need access to the cloud.
-2. Every time your job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. This token contains multiple claims to establish a security-hardened and verifiable identity about the specific workflow that is trying to authenticate.
-3. You could include a step or action in your job to request this token from {% data variables.product.prodname_dotcom %}'s OIDC provider, and present it to the cloud provider.
-4. Once the cloud provider successfully validates the claims presented in the token, it then provides a short-lived cloud access token that is available only for the duration of the job.
+## 클라우드를 사용하여 OIDC 트러스트 구성
-## Configuring the OIDC trust with the cloud
+{% data variables.product.prodname_dotcom %}의 OIDC 공급자를 신뢰하도록 클라우드를 구성하는 경우 신뢰할 수 없는 리포지토리 또는 워크플로가 클라우드 리소스에 대한 액세스 토큰을 요청할 수 없도록 들어오는 요청을 필터링하는 조건을 추가 **해야 합니다**.
-When you configure your cloud to trust {% data variables.product.prodname_dotcom %}'s OIDC provider, you **must** add conditions that filter incoming requests, so that untrusted repositories or workflows can’t request access tokens for your cloud resources:
-
-- Before granting an access token, your cloud provider checks that the [`subject`](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) and other claims used to set conditions in its trust settings match those in the request's JSON Web Token (JWT). As a result, you must take care to correctly define the _subject_ and other conditions in your cloud provider.
-- The OIDC trust configuration steps and the syntax to set conditions for cloud roles (using _Subject_ and other claims) will vary depending on which cloud provider you're using. For some examples, see "[Example subject claims](#example-subject-claims)."
+- 액세스 토큰을 부여하기 전에 클라우드 공급자는 트러스트 설정에서 조건을 설정하는 데 사용되는 [`subject`](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) 및 기타 클레임이 요청의 JWT(JSON Web Token)의 클레임과 일치하는지 확인합니다. 따라서 클라우드 공급자에서 _주체_ 및 기타 조건을 올바르게 정의하기 위해 주의해야 합니다.
+- OIDC 트러스트 구성 단계 및 클라우드 역할에 대한 조건을 설정(_주체_ 및 기타 클레임 사용)하는 구문은 사용 중인 클라우드 공급자에 따라 달라집니다. 몇 가지 예제는 "[주체 클레임 예제](#example-subject-claims)"를 참조하세요.
-### Understanding the OIDC token
+### OIDC 토큰 이해
-Each job requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. When the job runs, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition.
+각 작업은 {% data variables.product.prodname_dotcom %}의 OIDC 공급자로부터 OIDC 토큰을 요청합니다. 이 공급자는 생성된 각 워크플로 작업에 대해 고유한 자동으로 생성된 JWT(JSON Web Token)로 응답합니다. 작업이 실행되면 클라우드 공급자에게 OIDC 토큰이 표시됩니다. 토큰의 유효성을 검사하기 위해 클라우드 공급자는 OIDC 토큰의 주체 및 기타 클레임이 클라우드 역할의 OIDC 트러스트 정의에 미리 구성된 조건과 일치하는지 확인합니다.
-The following example OIDC token uses a subject (`sub`) that references a job environment named `prod` in the `octo-org/octo-repo` repository.
+다음 예제 OIDC 토큰은 `octo-org/octo-repo` 리포지토리에 `sub`라는 작업 환경을 참조하는 주체(`prod`)를 사용합니다.
```yaml
{
@@ -92,121 +96,120 @@ The following example OIDC token uses a subject (`sub`) that references a job en
}
```
-To see all the claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, review the `claims_supported` entries at
-{% ifversion ghes %}`https://HOSTNAME/_services/token/.well-known/openid-configuration`{% else %}https://token.actions.githubusercontent.com/.well-known/openid-configuration{% endif %}.
+{% data variables.product.prodname_dotcom %}의 OIDC 공급자에서 지원하는 모든 클레임을 보려면 {% ifversion ghes %}`https://HOSTNAME/_services/token/.well-known/openid-configuration`{% else %} https://token.actions.githubusercontent.com/.well-known/openid-configuration{% endif %}에서 `claims_supported` 항목을 검토합니다.
-The token includes the standard audience, issuer, and subject claims:
+토큰에는 표준 대상 그룹, 발급자 및 주체 클레임이 포함됩니다.
-| Claim | Description |
+| 클레임 | 설명 |
| ----------- | ---------------------- |
-| `aud`| _(Audience)_ By default, this is the URL of the repository owner, such as the organization that owns the repository. This is the only claim that can be customized. You can set a custom audience with a toolkit command: [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0) |
-| `iss`| _(Issuer)_ The issuer of the OIDC token: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} |
-| `sub`| _(Subject)_ Defines the subject claim that is to be validated by the cloud provider. This setting is essential for making sure that access tokens are only allocated in a predictable way.|
+| `aud`| _(대상 그룹)_ 기본적으로 리포지토리를 소유하는 조직과 같은 리포지토리 소유자의 URL입니다. 사용자 지정할 수 있는 유일한 클레임입니다. 도구 키트 명령 [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0)을 사용하여 사용자 지정 대상 그룹을 설정할 수 있습니다. |
+| `iss`| _(발급자)_ OIDC 토큰의 발급자: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} |
+| `sub`| _(주체)_ 클라우드 공급자가 유효성을 검사할 주체 클레임을 정의합니다. 이 설정은 액세스 토큰이 예측 가능한 방식으로만 할당되도록 하는 데 필수적입니다.|
-The OIDC token also includes additional standard claims:
+OIDC 토큰에는 추가 표준 클레임도 포함됩니다.
-| Claim | Description |
+| 클레임 | 설명 |
| ----------- | ---------------------- |
-| `alg`| _(Algorithm)_ The algorithm used by the OIDC provider. |
-| `exp`| _(Expires at)_ Identifies the expiry time of the JWT. |
-| `iat`| _(Issued at)_ The time when the JWT was issued. |
-| `jti`| _(JWT token identifier)_ Unique identifier for the OIDC token. |
-| `kid`| _(Key identifier)_ Unique key for the OIDC token. |
-| `nbf`| _(Not before)_ JWT is not valid for use before this time. |
-| `typ`| _(Type)_ Describes the type of token. This is a JSON Web Token (JWT). |
+| `alg`| _(알고리즘)_ OIDC 공급자가 사용하는 알고리즘입니다. |
+| `exp`| _(만료 날짜)_ JWT의 만료 시간을 식별합니다. |
+| `iat`| _(발급 시간)_ JWT가 발급된 시간입니다. |
+| `jti`| _(JWT 토큰 식별자)_ OIDC 토큰의 고유 식별자입니다. |
+| `kid`| _(키 식별자)_ OIDC 토큰의 고유 키입니다. |
+| `nbf`| _(이전이 아님)_ 이 시간 전에는 JWT를 사용할 수 없습니다. |
+| `typ`| _(유형)_ 토큰의 유형을 설명합니다. JWT(JSON Web Token)입니다. |
-The token also includes custom claims provided by {% data variables.product.prodname_dotcom %}:
+토큰에는 {% data variables.product.prodname_dotcom %}가 제공하는 사용자 지정 클레임도 포함됩니다.
-| Claim | Description |
+| 클레임 | 설명 |
| ----------- | ---------------------- |
-| `actor`| The personal account that initiated the workflow run. |
-| `actor_id`| The ID of personal account that initiated the workflow run. |
-| `base_ref`| The target branch of the pull request in a workflow run. |
-| `environment`| The name of the environment used by the job. |
-| `event_name`| The name of the event that triggered the workflow run. |
-| `head_ref`| The source branch of the pull request in a workflow run. |
-| `job_workflow_ref`| This is the ref path to the reusable workflow used by this job. For more information, see "["Using OpenID Connect with reusable workflows"](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)." |
-| `ref`| _(Reference)_ The git ref that triggered the workflow run. |
-| `ref_type`| The type of `ref`, for example: "branch". |
-| `repository_visibility` | The visibility of the repository where the workflow is running. Accepts the following values: `internal`, `private`, or `public`. |
-| `repository`| The repository from where the workflow is running. |
-| `repository_id`| The ID of the repository from where the workflow is running. |
-| `repository_owner`| The name of the organization in which the `repository` is stored. |
-| `repository_owner_id`| The ID of the organization in which the `repository` is stored. |
-| `run_id`| The ID of the workflow run that triggered the workflow. |
-| `run_number`| The number of times this workflow has been run. |
-| `run_attempt`| The number of times this workflow run has been retried. |
-| `workflow`| The name of the workflow. |
+| `actor`| 워크플로 실행을 시작한 개인 계정입니다. |
+| `actor_id`| 워크플로 실행을 시작한 개인 계정의 ID입니다. |
+| `base_ref`| 워크플로 실행에서 끌어오기 요청의 대상 분기입니다. |
+| `environment`| 작업에 사용되는 환경의 이름입니다. |
+| `event_name`| 워크플로 실행을 트리거한 이벤트의 이름입니다. |
+| `head_ref`| 워크플로 실행에서 끌어오기 요청의 소스 분기입니다. |
+| `job_workflow_ref`| 이 작업에서 사용하는 재사용 가능한 워크플로의 참조 경로입니다. 자세한 내용은 “[재사용 가능한 워크플로에서 OpenID Connect 사용](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)”을 참조하세요. |
+| `ref`| _(참조)_ 워크플로 실행을 트리거한 git 참조입니다. |
+| `ref_type`| `ref`의 유형(예: "branch")입니다. |
+| `repository_visibility` | 워크플로가 실행 중인 리포지토리의 표시 여부입니다. 값 `internal`, `private` 또는 `public` 중에서 수락합니다. |
+| `repository`| 워크플로가 실행 중인 리포지토리입니다. |
+| `repository_id`| 워크플로가 실행 중인 리포지토리의 ID입니다. |
+| `repository_owner`| `repository`가 저장되는 조직의 이름입니다. |
+| `repository_owner_id`| `repository`가 저장되는 조직의 ID입니다. |
+| `run_id`| 워크플로를 트리거한 워크플로 실행의 ID입니다. |
+| `run_number`| 이 워크플로가 실행된 횟수입니다. |
+| `run_attempt`| 이 워크플로가 다시 시도된 횟수입니다. |
+| `workflow`| 워크플로의 이름입니다. |
-### Defining trust conditions on cloud roles using OIDC claims
+### OIDC 클레임을 사용하여 클라우드 역할에 대한 트러스트 조건 정의
-With OIDC, a {% data variables.product.prodname_actions %} workflow requires a token in order to access resources in your cloud provider. The workflow requests an access token from your cloud provider, which checks the details presented by the JWT. If the trust configuration in the JWT is a match, your cloud provider responds by issuing a temporary token to the workflow, which can then be used to access resources in your cloud provider. You can configure your cloud provider to only respond to requests that originate from a specific organization's repository; you can also specify additional conditions, described below.
+OIDC를 사용하면 클라우드 공급자의 리소스에 액세스하기 위해 {% data variables.product.prodname_actions %} 워크플로에 토큰이 필요합니다. 워크플로는 클라우드 공급자로부터 JWT에서 제공하는 세부 정보를 확인하는 액세스 토큰을 요청합니다. JWT의 트러스트 구성이 일치하는 경우 클라우드 공급자는 워크플로에 임시 토큰을 발급하여 응답합니다. 그러면 클라우드 공급자의 리소스에 액세스하는 데 이 임시 토큰을 사용할 수 있습니다. 특정 조직의 리포지토리에서 시작된 요청에만 응답하도록 클라우드 공급자를 구성할 수 있습니다. 아래에 설명된 추가 조건을 지정할 수도 있습니다.
-Audience and Subject claims are typically used in combination while setting conditions on the cloud role/resources to scope its access to the GitHub workflows.
-- **Audience**: By default, this value uses the URL of the organization or repository owner. This can be used to set a condition that only the workflows in the specific organization can access the cloud role.
-- **Subject**: By default, has a predefined format and is a concatenation of some of the key metadata about the workflow, such as the {% data variables.product.prodname_dotcom %} organization, repository, branch, or associated [`job`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idenvironment) environment. See "[Example subject claims](#example-subject-claims)" to see how the subject claim is assembled from concatenated metadata.
+대상 그룹 및 주체 클레임은 일반적으로 클라우드 역할/리소스에 대한 조건을 설정하여 GitHub 워크플로에 대한 액세스 범위를 지정할 때 함께 사용됩니다.
+- **대상 그룹**: 기본적으로 이 값은 조직 또는 리포지토리 소유자의 URL을 사용합니다. 특정 조직의 워크플로만 클라우드 역할에 액세스할 수 있는 조건을 설정하는 데 사용할 수 있습니다.
+- **주체**: 기본적으로 미리 정의된 형식을 가지며 {% data variables.product.prodname_dotcom %} 조직, 리포지토리, 분기 또는 연결된 [`job`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idenvironment) 환경과 같은 워크플로에 대한 일부 주요 메타데이터를 연결한 것입니다. 연결된 메타데이터에서 주체 클레임이 어셈블되는 방법을 보려면 "[주체 클레임 예제](#example-subject-claims)"를 참조하세요.
-If you need more granular trust conditions, you can customize the issuer (`iss`) and subject (`sub`) claims that are included with the JWT. For more information, see "[Customizing the token claims](#customizing-the-token-claims)".
+보다 세부적인 신뢰 조건이 필요한 경우 JWT에 포함된 발급자(`iss`) 및 주체(`sub`) 클레임을 사용자 지정할 수 있습니다. 자세한 내용은 “[토큰 클레임 사용자 지정](#customizing-the-token-claims)”을 참조하세요.
-There are also many additional claims supported in the OIDC token that can be used for setting these conditions. In addition, your cloud provider could allow you to assign a role to the access tokens, letting you specify even more granular permissions.
+이러한 조건을 설정하는 데 사용할 수 있는 OIDC 토큰에서 지원되는 많은 추가 클레임이 있습니다. 또한 클라우드 공급자를 사용하면 액세스 토큰에 역할을 할당할 수 있으므로 보다 세부적인 권한을 지정할 수 있습니다.
{% note %}
-**Note**: To control how your cloud provider issues access tokens, you **must** define at least one condition, so that untrusted repositories can’t request access tokens for your cloud resources.
+**참고**: 클라우드 공급자가 액세스 토큰을 발급하는 방법을 제어하려면 신뢰할 수 없는 리포지토리가 클라우드 리소스에 대한 액세스 토큰을 요청할 수 없도록 하나 이상의 조건을 정의 **해야 합니다**.
{% endnote %}
-### Example subject claims
+### 주체 클레임 예제
-The following examples demonstrate how to use "Subject" as a condition, and explain how the "Subject" is assembled from concatenated metadata. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use.
+다음 예제에서는 "주체"를 조건으로 사용하는 방법과 연결된 메타데이터에서 "주체"가 어셈블되는 방법을 설명합니다. [주체](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims)는 [`job` 컨텍스트](/actions/learn-github-actions/contexts#job-context)의 정보를 사용하며, 특정 분기, 환경에서 실행되는 워크플로의 요청에 대해서만 액세스 토큰 요청을 부여할 수 있음을 클라우드 공급자에 알립니다. 다음 섹션에서는 사용할 수 있는 몇 가지 일반적인 주체에 대해 설명합니다.
-#### Filtering for a specific environment
+#### 특정 환경에 대한 필터링
-The subject claim includes the environment name when the job references an environment.
+주체 클레임에는 작업이 환경을 참조할 때의 환경 이름이 포함됩니다.
-You can configure a subject that filters for a specific [environment](/actions/deployment/using-environments-for-deployment) name. In this example, the workflow run must have originated from a job that has an environment named `Production`, in a repository named `octo-repo` that is owned by the `octo-org` organization:
+특정 [환경](/actions/deployment/using-environments-for-deployment) 이름을 필터링하는 주체를 구성할 수 있습니다. 이 예제에서 워크플로 실행은 `octo-org` 조직이 소유한 `octo-repo`라는 리포지토리에 `Production`이라는 환경이 있는 작업에서 시작되어야 합니다.
| | |
| ------ | ----------- |
-| Syntax: | `repo::environment:` |
-| Example:| `repo:octo-org/octo-repo:environment:Production` |
+| 구문 | `repo::environment:` |
+| 예제:| `repo:octo-org/octo-repo:environment:Production` |
-#### Filtering for `pull_request` events
+#### `pull_request` 이벤트 필터링
-The subject claim includes the `pull_request` string when the workflow is triggered by a pull request event, but only if the job doesn't reference an environment.
+워크플로가 끌어오기 요청 이벤트에 의해 트리거되는 경우 주체 클레임에 `pull_request` 문자열이 포함됩니다. 단, 작업에서 환경을 참조하지 않아야만 합니다.
-You can configure a subject that filters for the [`pull_request`](/actions/learn-github-actions/events-that-trigger-workflows#pull_request) event. In this example, the workflow run must have been triggered by a `pull_request` event in a repository named `octo-repo` that is owned by the `octo-org` organization:
+[`pull_request`](/actions/learn-github-actions/events-that-trigger-workflows#pull_request) 이벤트를 필터링하는 주체를 구성할 수 있습니다. 이 예제에서 워크플로 실행은 `octo-org` 조직이 소유한 `octo-repo`라는 리포지토리의 `pull_request` 이벤트에 의해 트리거되어야 합니다.
| | |
| ------ | ----------- |
-| Syntax: | `repo::pull_request` |
-| Example:| `repo:octo-org/octo-repo:pull_request` |
+| 구문 | `repo::pull_request` |
+| 예제:| `repo:octo-org/octo-repo:pull_request` |
-#### Filtering for a specific branch
+#### 특정 분기 필터링
-The subject claim includes the branch name of the workflow, but only if the job doesn't reference an environment, and if the workflow is not triggered by a pull request event.
+주체 클레임에는 워크플로의 분기 이름이 포함됩니다. 단, 작업이 환경을 참조하지 않고 워크플로가 끌어오기 요청 이벤트에 의해 트리거되지 않는 경우에만 해당됩니다.
-You can configure a subject that filters for a specific branch name. In this example, the workflow run must have originated from a branch named `demo-branch`, in a repository named `octo-repo` that is owned by the `octo-org` organization:
+특정 분기 이름을 필터링하는 주체를 구성할 수 있습니다. 이 예제에서 워크플로 실행은 `octo-org` 조직이 소유한 `octo-repo`라는 리포지토리에 `demo-branch`라는 분기에서 시작되어야 합니다.
| | |
| ------ | ----------- |
-| Syntax: | `repo::ref:refs/heads/branchName` |
-| Example:| `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` |
+| 구문 | `repo::ref:refs/heads/branchName` |
+| 예제:| `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` |
-#### Filtering for a specific tag
+#### 특정 태그 필터링
-The subject claim includes the tag name of the workflow, but only if the job doesn't reference an environment, and if the workflow is not triggered by a pull request event.
+주체 클레임에는 워크플로의 태그 이름이 포함됩니다. 단, 작업이 환경을 참조하지 않고 워크플로가 끌어오기 요청 이벤트에 의해 트리거되지 않는 경우에만 해당됩니다.
-You can create a subject that filters for specific tag. In this example, the workflow run must have originated with a tag named `demo-tag`, in a repository named `octo-repo` that is owned by the `octo-org` organization:
+특정 태그를 필터링하는 주체를 만들 수 있습니다. 이 예제에서 워크플로 실행은 `octo-org` 조직이 소유한 `octo-repo`라는 리포지토리의 `demo-tag` 태그로 시작되어야 합니다.
| | |
| ------ | ----------- |
-| Syntax: | `repo::ref:refs/tags/` |
-| Example:| `repo:octo-org/octo-repo:ref:refs/tags/demo-tag` |
+| 구문 | `repo::ref:refs/tags/` |
+| 예제:| `repo:octo-org/octo-repo:ref:refs/tags/demo-tag` |
-### Configuring the subject in your cloud provider
+### 클라우드 공급자에서 주체 구성
-To configure the subject in your cloud provider's trust relationship, you must add the subject string to its trust configuration. The following examples demonstrate how various cloud providers can accept the same `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` subject in different ways:
+클라우드 공급자의 트러스트 관계에서 주체를 구성하려면 해당 트러스트 구성에 주체 문자열을 추가해야 합니다. 다음 예제에서는 다양한 클라우드 공급자가 서로 다른 방식으로 동일한 `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` 주체를 수락하는 방법을 보여 줍니다.
| | |
| ------ | ----------- |
@@ -215,54 +218,54 @@ To configure the subject in your cloud provider's trust relationship, you must a
| Google Cloud Platform| `(assertion.sub=='repo:octo-org/octo-repo:ref:refs/heads/demo-branch')` |
| HashiCorp Vault| `bound_subject="repo:octo-org/octo-repo:ref:refs/heads/demo-branch" ` |
-For more information, see the guides listed in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)."
+자세한 내용은 "[클라우드 공급자에 대해 OpenID Connect 사용](#enabling-openid-connect-for-your-cloud-provider)"에 나열된 지침을 참조하세요.
-## Updating your actions for OIDC
+## OIDC에 대한 작업 업데이트
-To update your custom actions to authenticate using OIDC, you can use `getIDToken()` from the Actions toolkit to request a JWT from {% data variables.product.prodname_dotcom %}'s OIDC provider. For more information, see "OIDC Token" in the [npm package documentation](https://www.npmjs.com/package/@actions/core/v/1.6.0).
+OIDC를 사용하여 인증하도록 사용자 지정 작업을 업데이트하려면 작업 도구 키트에서 `getIDToken()`을 사용하여 {% data variables.product.prodname_dotcom %}의 OIDC 공급자로부터 JWT를 요청할 수 있습니다. 자세한 내용은 [npm 패키지 설명서](https://www.npmjs.com/package/@actions/core/v/1.6.0)에서 "OIDC 토큰"을 참조하세요.
-You could also use a `curl` command to request the JWT, using the following environment variables:
+다음 환경 변수를 사용하여 `curl` 명령을 사용하여 JWT를 요청할 수도 있습니다.
| | |
| ------ | ----------- |
-| `ACTIONS_ID_TOKEN_REQUEST_URL` | The URL for {% data variables.product.prodname_dotcom %}'s OIDC provider. |
-| `ACTIONS_ID_TOKEN_REQUEST_TOKEN` | Bearer token for the request to the OIDC provider. |
+| `ACTIONS_ID_TOKEN_REQUEST_URL` | {% data variables.product.prodname_dotcom %}의 OIDC 공급자에 대한 URL |
+| `ACTIONS_ID_TOKEN_REQUEST_TOKEN` | OIDC 공급자에 대한 요청의 전달자 토큰 |
-For example:
+예를 들면 다음과 같습니다.
```shell{:copy}
curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange"
```
-### Adding permissions settings
+### 사용 권한 설정 추가
{% data reusables.actions.oidc-permissions-token %}
{% ifversion actions-oidc-hardening-config %}
-## Customizing the token claims
+## 토큰 클레임 사용자 지정
-You can security harden your OIDC configuration by customizing the claims that are included with the JWT. These customisations allow you to define more granular trust conditions on your cloud roles when allowing your workflows to access resources hosted in the cloud:
+JWT에 포함된 클레임을 사용자 지정하여 OIDC 구성의 보안을 강화할 수 있습니다. 다음 사용자 지정을 사용하면 워크플로가 클라우드에서 호스트되는 리소스에 액세스할 수 있도록 허용할 때 클라우드 역할에 대해 보다 세부적인 신뢰 조건을 정의할 수 있습니다.
-{% ifversion ghec %} - For an additional layer of security, you can append the `issuer` url with your enterprise slug. This lets you set conditions on the issuer (`iss`) claim, configuring it to only accept JWT tokens from a unique `issuer` URL that must include your enterprise slug.{% endif %}
-- You can standardize your OIDC configuration by setting conditions on the subject (`sub`) claim that require JWT tokens to originate from a specific repository, reusable workflow, or other source.
-- You can define granular OIDC policies by using additional OIDC token claims, such as `repository_id` and `repository_visibility`. For more information, see "[Understanding the OIDC token](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#understanding-the-oidc-token)".
+{% ifversion ghec %} - 추가 보안 계층을 위해 엔터프라이즈 슬러그와 함께 `issuer` URL을 추가할 수 있습니다. 이렇게 하면 발급자(`iss`) 클레임에 조건을 설정하고 엔터프라이즈 슬러그를 포함해야 하는 고유한 `issuer` URL의 JWT 토큰만 허용하도록 구성할 수 있습니다.{% endif %}
+- 특정 리포지토리, 재사용 가능한 워크플로 또는 기타 원본에서 발생하는 데 JWT 토큰이 필요한 주체(`sub`) 클레임에 대한 조건을 설정하여 OIDC 구성을 표준화할 수 있습니다.
+- `repository_id` 및 `repository_visibility` 등과 같은 추가 OIDC 토큰 클레임을 사용하여 세분화된 OIDC 정책을 정의할 수 있습니다. 자세한 내용은 “[OIDC 토큰 이해](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#understanding-the-oidc-token)”를 참조하세요.
-To customize these claim formats, organization and repository admins can use the REST API endpoints described in the following sections.
+이러한 클레임 형식을 사용자 지정하기 위해 조직 및 리포지토리 관리자는 다음 섹션에 설명된 REST API 엔드포인트를 사용할 수 있습니다.
{% ifversion ghec %}
-### Switching to a unique token URL
+### 고유한 토큰 URL로 전환
-By default, the JWT is issued by {% data variables.product.prodname_dotcom %}'s OIDC provider at `https://token.actions.githubusercontent.com`. This path is presented to your cloud provider using the `iss` value in the JWT.
+기본적으로 JWT는 {% data variables.product.prodname_dotcom %}의 OIDC 공급자가 `https://token.actions.githubusercontent.com`에서 발급합니다. 이 경로는 JWT의 `iss` 값을 사용하여 클라우드 공급자에게 표시됩니다.
-Enterprise admins can security harden their OIDC configuration by configuring their enterprise to receive tokens from a unique URL at `https://token.actions.githubusercontent.com/`. Replace `` with the slug value of your enterprise.
+엔터프라이즈 관리자는 `https://token.actions.githubusercontent.com/`에서 고유한 URL에서 토큰을 받도록 엔터프라이즈를 구성하여 OIDC 구성의 보안을 강화할 수 있습니다. ``를 엔터프라이즈의 슬러그 값으로 바꿉니다.
-This configuration means that your enterprise will receive the OIDC token from a unique URL, and you can then configure your cloud provider to only accept tokens from that URL. This helps ensure that only the enterprise's repositories can access your cloud resources using OIDC.
+이 구성은 엔터프라이즈가 고유한 URL에서 OIDC 토큰을 수신하고 해당 URL의 토큰만 수락하도록 클라우드 공급자를 구성할 수 있음을 의미합니다. 이렇게 하면 엔터프라이즈의 리포지토리만 OIDC를 사용하여 클라우드 리소스에 액세스할 수 있습니다.
-To activate this setting for your enterprise, an enterprise admin must use the `/enterprises/{enterprise}/actions/oidc/customization/issuer` endpoint and specify `"include_enterprise_slug": true` in the request body. For more information, see "[Set the {% data variables.product.prodname_actions %} OIDC custom issuer policy for an enterprise](/rest/actions/oidc#set-the-github-actions-oidc-custom-issuer-policy-for-an-enterprise)."
+엔터프라이즈에 대해 이 설정을 활성화하려면 엔터프라이즈 관리자가 `/enterprises/{enterprise}/actions/oidc/customization/issuer` 엔드포인트를 사용하고 요청 본문에서 `"include_enterprise_slug": true`를 지정해야 합니다. 자세한 내용은 “[엔터프라이즈에 대한 {% data variables.product.prodname_actions %} OIDC 사용자 지정 발급자 정책 설정](/rest/actions/oidc#set-the-github-actions-oidc-custom-issuer-policy-for-an-enterprise)”을 참조하세요.
-After this setting is applied, the JWT will contain the updated `iss` value. In the following example, the `iss` key uses `octocat-inc` as its `enterpriseSlug` value:
+이 설정이 적용되면 JWT에 업데이트된 `iss` 값이 포함됩니다. 다음 예제에서 `iss` 키는 해당 `enterpriseSlug` 값으로 `octocat-inc`를 사용합니다.
```json
{
@@ -279,27 +282,27 @@ After this setting is applied, the JWT will contain the updated `iss` value. In
{% endif %}
-### Customizing the subject claims for an organization or repository
+### 조직 또는 리포지토리에 대한 주체 클레임 사용자 지정
-To help improve security, compliance, and standardization, you can customize the standard claims to suit your required access conditions. If your cloud provider supports conditions on subject claims, you can create a condition that checks whether the `sub` value matches the path of the reusable workflow, such as `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`. The exact format will vary depending on your cloud provider's OIDC configuration. To configure the matching condition on {% data variables.product.prodname_dotcom %}, you can can use the REST API to require that the `sub` claim must always include a specific custom claim, such as `job_workflow_ref`. You can use the [OIDC REST API](/rest/actions/oidc) to apply a customization template for the OIDC subject claim; for example, you can require that the `sub` claim within the OIDC token must always include a specific custom claim, such as `job_workflow_ref`.
-
-Customizing the claims results in a new format for the entire `sub` claim, which replaces the default predefined `sub` format in the token described in "[Example subject claims](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims)."
-
-The following example templates demonstrate various ways to customize the subject claim. To configure these settings on {% data variables.product.prodname_dotcom %}, admins use the REST API to specify a list of claims that must be included in the subject (`sub`) claim.
-
-{% data reusables.actions.use-request-body-api %}
-
-To customize your subject claims, you should first create a matching condition in your cloud provider's OIDC configuration, before customizing the configuration using the REST API. Once the configuration is completed, each time a new job runs, the OIDC token generated during that job will follow the new customization template. If the matching condition doesn't exist in the cloud provider's OIDC configuration before the job runs, the generated token might not be accepted by the cloud provider, since the cloud conditions may not be synchronized.
+보안, 규정 준수 및 표준화를 개선하기 위해 필요한 액세스 조건에 맞게 표준 클레임을 사용자 지정할 수 있습니다. 클라우드 공급자가 주체 클레임에 대한 조건을 지원하는 경우 `sub`값이 재사용 가능한 워크플로의 경로와 일치하는지 여부를 확인하는 조건을 만들 수 있습니다(예: `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`). 정확한 형식은 클라우드 공급자의 OIDC 구성에 따라 달라집니다. {% data variables.product.prodname_dotcom %}에서 일치 조건을 구성하려면 REST API를 사용하여 `sub` 클레임에 항상 특정 사용자 지정 클레임(예: `job_workflow_ref`)을 포함하도록 요구할 수 있습니다. [OIDC REST API를 사용하여 OIDC](/rest/actions/oidc) 주체 클레임에 대한 사용자 지정 템플릿을 적용할 수 있습니다. 예를 들어 OIDC 토큰 내의 `sub` 클레임에 항상 특정 사용자 지정 클레임(예: `job_workflow_ref`)을 포함하도록 요구할 수 있습니다.
{% note %}
-**Note**: When the organization template is applied, it will not affect any action workflows in existing repositories that already use OIDC. For existing repositories, as well as any new repositories that are created after the template has been applied, the repository owner will need to opt-in to receive this configuration, or alternatively could apply a different configuration specific to the repo. For more information, see "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)."
+**참고**: 조직 템플릿이 적용되면 이미 OIDC를 사용하는 기존 리포지토리의 워크플로에는 영향을 주지 않습니다. 기존 리포지토리와 템플릿이 적용된 후 생성된 새 리포지토리의 경우 리포지토리 소유자는 이 구성을 수신하기 위해 옵트인해야 하거나 리포지토리에 특정한 다른 구성을 적용할 수 있습니다. 자세한 내용은 "[리포지토리에 대한 OIDC 주체 클레임에 대한 사용자 지정 템플릿 설정"을 참조하세요](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository).
{% endnote %}
-#### Example: Allowing repository based on visibility and owner
+클레임을 사용자 지정하면 전체 `sub` 클레임에 대해 새 형식이 생성되며, 이는 “[예제 주체 클레임](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims)”에 설명된 토큰의 기본 미리 정의된 `sub` 형식을 대체합니다.
-This example template allows the `sub` claim to have a new format, using `repository_owner` and `repository_visibility`:
+다음 예제 템플릿에서는 제목 클레임을 사용자 지정하는 다양한 방법을 보여 줍니다. {% data variables.product.prodname_dotcom %}에서 이러한 설정을 구성하기 위해 관리자는 REST API를 사용하여 주체(`sub`) 클레임에 포함되어야 하는 클레임 목록을 지정합니다.
+
+{% data reusables.actions.use-request-body-api %}
+
+주체 클레임을 사용자 지정하려면 먼저 REST API를 사용하여 구성을 사용자 지정하기 전에 클라우드 공급자의 OIDC 구성에서 일치하는 조건을 만들어야 합니다. 구성이 완료되면 새 작업이 실행될 때마다 해당 작업 중에 생성된 OIDC 토큰이 새 사용자 지정 템플릿을 따릅니다. 작업이 실행되기 전에 일치하는 조건이 클라우드 공급자의 OIDC 구성에 없는 경우 클라우드 조건이 동기화되지 않을 수 있으므로 생성된 토큰이 클라우드 공급자에 의해 수락되지 않을 수 있습니다.
+
+#### 예: 표시 유형 및 소유자에 따라 리포지토리 허용
+
+이 예제 템플릿을 사용하면 `sub` 클레임이 `repository_owner` 및 `repository_visibility`를 사용하여 새 형식을 가질 수 있습니다.
```json
{
@@ -310,11 +313,11 @@ This example template allows the `sub` claim to have a new format, using `reposi
}
```
-In your cloud provider's OIDC configuration, configure the `sub` condition to require that claims must include specific values for `repository_owner` and `repository_visibility`. For example: `"repository_owner: "monalisa":repository_visibility:private"`. The approach lets you restrict cloud role access to only private repositories within an organization or enterprise.
+클라우드 공급자의 OIDC 구성에서 클레임에 `repository_owner` 및 `repository_visibility`에 대한 특정 값을 포함해야 하는 `sub` 조건을 구성합니다. 예: `"repository_owner: "monalisa":repository_visibility:private"` 이 접근 방식을 사용하면 클라우드 역할 액세스를 조직 또는 엔터프라이즈 내의 프라이빗 리포지토리로만 제한할 수 있습니다.
-#### Example: Allowing access to all repositories with a specific owner
+#### 예: 특정 소유자에게 모든 리포지토리에 대한 액세스 허용
-This example template enables the `sub` claim to have a new format with only the value of `repository_owner`.
+이 예제 템플릿을 사용하면 `sub` 클레임에 `repository_owner`의 값만 있는 새 형식을 사용할 수 있습니다.
{% data reusables.actions.use-request-body-api %}
@@ -327,11 +330,11 @@ This example template enables the `sub` claim to have a new format with only the
```
-In your cloud provider's OIDC configuration, configure the `sub` condition to require that claims must include a specific value for `repository_owner`. For example: `"repository_owner: "monalisa""`
+클라우드 공급자의 OIDC 구성에서 클레임에 `repository_owner`에 대한 특정 값을 포함해야 하는 `sub` 조건을 구성합니다. 예: `"repository_owner: "monalisa""`
-#### Example: Requiring a reusable workflow
+#### 예: 재사용 가능한 워크플로 필요
-This example template allows the `sub` claim to have a new format that contains the value of the `job_workflow_ref` claim. This enables an enterprise to use [reusable workflows](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims) to enforce consistent deployments across its organizations and repositories.
+이 예제 템플릿을 사용하면 `sub` 클레임에 `job_workflow_ref` 클레임의 값이 포함된 새 형식을 갖도록 할 수 있습니다. 이를 통해 엔터프라이즈는 [재사용 가능한 워크플로](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims)를 사용하여 조직 및 리포지토리에 일관된 배포를 적용할 수 있습니다.
{% data reusables.actions.use-request-body-api %}
@@ -343,15 +346,15 @@ This example template allows the `sub` claim to have a new format that contains
}
```
-In your cloud provider's OIDC configuration, configure the `sub` condition to require that claims must include a specific value for `job_workflow_ref`. For example: `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`.
+클라우드 공급자의 OIDC 구성에서 클레임에 `job_workflow_ref`에 대한 특정 값을 포함해야 하는 `sub` 조건을 구성합니다. 예: `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`
-#### Example: Requiring a reusable workflow and other claims
+#### 예: 재사용 가능한 워크플로 및 기타 클레임 필요
-The following example template combines the requirement of a specific reusable workflow with additional claims.
+다음 예제 템플릿은 재사용 가능한 특정 워크플로의 요구 사항을 추가 클레임과 결합합니다.
{% data reusables.actions.use-request-body-api %}
-This example also demonstrates how to use `"context"` to define your conditions. This is the part that follows the repository in the [default `sub` format](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims). For example, when the job references an environment, the context contains: `environment:`.
+이 예제에서는 `"context"`를 사용하여 조건을 정의하는 데 사용하는 방법도 보여 줍니다. 이 부분은 리포지토리를 [기본 `sub` 형식](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims)으로 따르는 부분입니다. 예를 들어 작업이 환경을 참조할 때 컨텍스트에는 `environment:`이 포함됩니다.
```json
{
@@ -363,14 +366,13 @@ This example also demonstrates how to use `"context"` to define your conditions.
}
```
-In your cloud provider's OIDC configuration, configure the `sub` condition to require that claims must include specific values for `repo`, `context`, and `job_workflow_ref`.
+클라우드 공급자의 OIDC 구성에서 클레임에 `repo``context` 및`job_workflow_ref`에 대한 특정 값을 포함해야 하는 `sub` 조건을 구성합니다.
-This customization template requires that the `sub` uses the following format: `repo::environment::job_workflow_ref:`.
-For example: `"sub": "repo:octo-org/octo-repo:environment:prod:job_workflow_ref:octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main"`
+이 사용자 지정 템플릿을 사용하려면 `sub`가 `repo::environment::job_workflow_ref:` 형식을 사용해야 합니다. 예: `"sub": "repo:octo-org/octo-repo:environment:prod:job_workflow_ref:octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main"`
-#### Example: Granting access to a specific repository
+#### 예: 특정 리포지토리에 대한 액세스 권한 부여
-This example template lets you grant cloud access to all the workflows in a specific repository, across all branches/tags and environments. To help improve security, combine this template with the custom issuer URL described in "[Customizing the token URL for an enterprise](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#customizing-the-token-url-for-an-enterprise)."
+이 예제 템플릿을 사용하면 모든 분기/태그 및 환경에서 특정 리포지토리의 모든 워크플로에 클라우드 액세스 권한을 부여할 수 있습니다. 보안을 강화하려면 이 템플릿을 “[엔터프라이즈용 토큰 URL 사용자 지정](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#customizing-the-token-url-for-an-enterprise)”에 설명된 사용자 지정 발급자 URL과 결합합니다.
{% data reusables.actions.use-request-body-api %}
@@ -382,11 +384,11 @@ This example template lets you grant cloud access to all the workflows in a spec
}
```
-In your cloud provider's OIDC configuration, configure the `sub` condition to require a `repo` claim that matches the required value.
+클라우드 공급자의 OIDC 구성에서 필요한 값과 일치하는 `repo` 클레임을 요구하도록 `sub` 조건을 구성합니다.
-#### Example: Using system-generated GUIDs
+#### 예: 시스템 생성 GUID 사용
-This example template enables predictable OIDC claims with system-generated GUIDs that do not change between renames of entities (such as renaming a repository).
+이 예제 템플릿은 엔터티 이름 바꾸기(예: 리포지토리 이름 바꾸기) 간에 변경되지 않는 시스템 생성 GUID를 사용하여 예측 가능한 OIDC 클레임을 사용하도록 설정합니다.
{% data reusables.actions.use-request-body-api %}
@@ -398,9 +400,9 @@ This example template enables predictable OIDC claims with system-generated GUID
}
```
-In your cloud provider's OIDC configuration, configure the `sub` condition to require a `repository_id` claim that matches the required value.
+클라우드 공급자의 OIDC 구성에서 필요한 값과 일치하는 `repository_id` 클레임을 요구하도록 `sub` 조건을 구성합니다.
-or:
+또는:
```json
{
@@ -410,11 +412,11 @@ or:
}
```
-In your cloud provider's OIDC configuration, configure the `sub` condition to require a `repository_owner_id` claim that matches the required value.
+클라우드 공급자의 OIDC 구성에서 필요한 값과 일치하는 `repository_owner_id` 클레임을 요구하도록 `sub` 조건을 구성합니다.
-#### Resetting your customizations
+#### 사용자 지정 초기화
-This example template resets the subject claims to the default format. This template effectively opts out of any organization-level customization policy.
+이 예제 템플릿은 주체 클레임을 기본 형식으로 초기화합니다. 이 템플릿은 조직 수준 사용자 지정 정책을 효과적으로 옵트아웃합니다.
{% data reusables.actions.use-request-body-api %}
@@ -427,11 +429,13 @@ This example template resets the subject claims to the default format. This temp
}
```
-In your cloud provider's OIDC configuration, configure the `sub` condition to require that claims must include specific values for `repo` and `context`.
+클라우드 공급자의 OIDC 구성에서 클레임에 `repo` 및 `context`에 대한 특정 값을 포함해야 하는 `sub` 조건을 구성합니다.
-#### Using the default subject claims
+#### 기본 주체 클레임 사용
-For repositories that can receive a subject claim policy from their organization, the repository owner can later choose to opt-out and instead use the default `sub` claim format. To configure this, the repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
+조직에서 주체 클레임 정책을 받을 수 있는 리포지토리의 경우 리포지토리 소유자는 나중에 옵트아웃하도록 선택하고 대신 기본 `sub` 클레임 형식을 사용할 수 있습니다. 즉, 리포지토리는 조직의 사용자 지정된 템플릿을 사용하지 않습니다.
+
+기본 `sub` 클레임 형식을 사용하도록 리포지토리를 구성하려면 리포지토리 관리자가 다음 요청 본문과 함께 "[리포지토리에 대한 OIDC 주체 클레임에 대한 사용자 지정 템플릿 설정](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)"의 REST API 엔드포인트를 사용해야 합니다.
```json
{
@@ -439,22 +443,34 @@ For repositories that can receive a subject claim policy from their organization
}
```
+#### 예: 조직 템플릿을 사용하도록 리포지토리 구성
+
+리포지토리 관리자는 조직의 관리자가 만든 템플릿을 사용하도록 리포지토리를 구성할 수 있습니다.
+
+조직의 템플릿을 사용하도록 리포지토리를 구성하려면 리포지토리 관리자가 다음 요청 본문과 함께 "[리포지토리에 대한 OIDC 주체 클레임에 대한 사용자 지정 템플릿 설정](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)"의 REST API 엔드포인트를 사용해야 합니다.
+
+```json
+{
+ "use_default": false
+}
+```
+
{% endif %}
-## Updating your workflows for OIDC
+## OIDC에 대한 워크플로 업데이트
-You can now update your YAML workflows to use OIDC access tokens instead of secrets. Popular cloud providers have published their official login actions that make it easy for you to get started with OIDC. For more information about updating your workflows, see the cloud-specific guides listed below in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)."
+이제 비밀 대신 OIDC 액세스 토큰을 사용하도록 YAML 워크플로를 업데이트할 수 있습니다. 인기 있는 클라우드 공급자는 OIDC를 쉽게 시작할 수 있도록 하는 공식 로그인 작업을 게시했습니다. 워크플로 업데이트에 대한 자세한 내용은 "[클라우드 공급자에 OpenID Connect 사용](#enabling-openid-connect-for-your-cloud-provider)"에 나열된 클라우드 관련 가이드를 참조하세요.
-## Enabling OpenID Connect for your cloud provider
+## 클라우드 공급자에 OpenID Connect 사용
-To enable and configure OIDC for your specific cloud provider, see the following guides:
+특정 클라우드 공급자에 대해 OIDC를 사용하도록 설정하고 구성하려면 다음 가이드를 참조하세요.
-- ["Configuring OpenID Connect in Amazon Web Services"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services)
-- ["Configuring OpenID Connect in Azure"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)
-- ["Configuring OpenID Connect in Google Cloud Platform"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform)
-- ["Configuring OpenID Connect in Hashicorp Vault"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault)
+- ["Amazon Web Services에서 OpenID Connect 구성"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services)
+- ["Azure에서 OpenID Connect 구성"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)
+- ["Google Cloud Platform에서 OpenID Connect 구성"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform)
+- ["HashiCorp 자격 증명 모음에서 OpenID Connect 구성"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault)
-To enable and configure OIDC for another cloud provider, see the following guide:
+다른 클라우드 공급자에 대해 OIDC를 사용하도록 설정하고 구성하려면 다음 가이드를 참조하세요.
-- ["Configuring OpenID Connect in cloud providers"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers)
+- ["클라우드 공급자에서 OpenID Connect 구성"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers)
diff --git a/translations/ko-KR/content/actions/learn-github-actions/contexts.md b/translations/ko-KR/content/actions/learn-github-actions/contexts.md
index bdf5bb0bfb..9217298a2a 100644
--- a/translations/ko-KR/content/actions/learn-github-actions/contexts.md
+++ b/translations/ko-KR/content/actions/learn-github-actions/contexts.md
@@ -811,7 +811,7 @@ The `inputs` context contains input properties passed to an action{% ifversion a
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
| Property name | Type | Description |
|---------------|------|-------------|
diff --git a/translations/ko-KR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ko-KR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0d316eca1f..397d51b308 100644
--- a/translations/ko-KR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/ko-KR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -88,7 +88,7 @@ In addition to the usage limits, you must ensure that you use {% data variables.
{% ifversion fpt or ghes > 3.3 or ghec %}
## Billing for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
diff --git a/translations/ko-KR/content/actions/using-workflows/reusing-workflows.md b/translations/ko-KR/content/actions/using-workflows/reusing-workflows.md
index 2adee6a3f4..1cc0d2d002 100644
--- a/translations/ko-KR/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/ko-KR/content/actions/using-workflows/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
---
{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
## Overview
diff --git a/translations/ko-KR/content/actions/using-workflows/triggering-a-workflow.md b/translations/ko-KR/content/actions/using-workflows/triggering-a-workflow.md
index 8e4adb430f..837875fe9e 100644
--- a/translations/ko-KR/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/ko-KR/content/actions/using-workflows/triggering-a-workflow.md
@@ -123,7 +123,7 @@ You can use activity types and filters to further control when your workflow wil
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
diff --git a/translations/ko-KR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/ko-KR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 4969f6b53e..e6e11c2ff5 100644
--- a/translations/ko-KR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/ko-KR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -72,7 +72,7 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `on.workflow_call`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
@@ -320,7 +320,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+You can use the `if` conditional to prevent a step from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
@@ -945,7 +945,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `jobs..uses`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
diff --git a/translations/ko-KR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/ko-KR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 98a84270fb..1e67bc7da9 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
+
| Path without subdomain isolation | Path with subdomain isolation |
| --- | --- |
-| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
-| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
-| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
-| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
-| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
-| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
-| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
+| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
+| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
+| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
+| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
+| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
{%- ifversion viewscreen-and-notebooks %}
-| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
-| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
-{%- else %}
-| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
+| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+{%- ifversion ghes < 3.7 %}
+| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
+| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
+{%- ifversion viewscreen-and-notebooks %}
+| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
+{%- endif %}
+{%- ifversion ghes > 3.4 %}
+| Not supported | `https://containers.HOSTNAME/` |
{%- endif %}
-| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
-| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %}
-| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported | `https://containers.HOSTNAME/` |{% endif %}
## Prerequisites
diff --git a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 625a34aa98..c01ecca7a2 100644
--- a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}
diff --git a/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 991873cdca..041431c2e8 100644
--- a/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -56,7 +56,7 @@ You can enforce policies to control how members of your enterprise on {% data va
Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% ifversion ghes or ghae %}
@@ -166,7 +166,7 @@ Across all organizations owned by your enterprise, you can set the default branc
Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 571de5c750..b2348bc546 100644
--- a/translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -67,7 +67,9 @@ The storage used by a repository is the total storage used by {% data variables.
### Per-minute rates
{% data reusables.billing.billing-standard-runners %}
-{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
+{%- ifversion actions-hosted-runners %}
+{% data reusables.billing.billing-hosted-runners %}
+{%- endif %}
- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
- {% data reusables.user-settings.context_switcher %}
diff --git a/translations/ko-KR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/translations/ko-KR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
index 81fe2b9c52..a041298c43 100644
--- a/translations/ko-KR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
+++ b/translations/ko-KR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: GitHub Codespaces 사전 빌드 관련 정보
+title: About GitHub Codespaces prebuilds
shortTitle: About prebuilds
-intro: '{% data variables.product.prodname_github_codespaces %} 사전 빌드는 크거나 복잡한 리포지토리에 대한 새 codespace 생성 속도를 향상하는 데 도움이 됩니다.'
+intro: '{% data variables.product.prodname_github_codespaces %} prebuilds help to speed up the creation of new codespaces for large or complex repositories.'
versions:
fpt: '*'
ghec: '*'
@@ -9,48 +9,43 @@ topics:
- Codespaces
redirect_from:
- /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds
-ms.openlocfilehash: e0962e410f2227a23ff98c8a3e7995ea8ec8a914
-ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
-ms.translationtype: MT
-ms.contentlocale: ko-KR
-ms.lasthandoff: 11/09/2022
-ms.locfileid: '148158799'
---
-## 개요
+
+## Overview
{% data reusables.codespaces.prebuilds-definition %}
-현재 리포지토리에 대한 codespace를 만드는 데 2분 이상 걸리는 경우 사전 빌드를 사용하면 도움이 될 수 있습니다. 사전 빌드를 사용하면 codespace를 만들기 전에 소스 코드, 편집기 확장, 프로젝트 종속성, 명령 및 구성이 이미 다운로드, 설치 및 적용되었기 때문입니다.
+If it currently takes more than 2 minutes to create a codespace for a repository, you are likely to benefit from using prebuilds. This is because, with a prebuild, any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace.
-기본적으로 리포지토리에 변경 내용을 푸시할 때마다 {% data variables.product.prodname_github_codespaces %}는 {% data variables.product.prodname_actions %}를 사용하여 미리 빌드를 자동으로 업데이트합니다.
+By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds.
-리포지토리의 특정 분기, 특정 개발 컨테이너 구성 파일 및 해당 지역에 대해 사전 빌드를 사용할 수 있는 경우, codespace를 만들 때 머신 유형 옵션 목록에 "{% octicon "zap" aria-label="The zap icon" %} 사전 빌드 준비됨" 레이블이 표시됩니다. 사전 빌드가 아직 만들어지고 있으면 "{% octicon "history" aria-label="The history icon" %} 사전 빌드 진행 중" 레이블이 표시됩니다. 자세한 내용은 "[리포지토리에 대한 codespace 만들기"를 참조하세요](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
+When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-label="The history icon" %} Prebuild in progress" label. 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)."
-
+
-"Codespaces" 페이지의 템플릿에서 codespace를 만들 때 {% data variables.product.prodname_dotcom %}는 자동으로 사전 빌드를 사용하여 생성 시간을 단축할 수 있습니다. 템플릿에 대한 자세한 내용은 "[템플릿에서 codespace 만들기"를 참조하세요](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template).
+When you create a codespace from a template on the "Your codespaces" page, {% data variables.product.prodname_dotcom %} may automatically use a prebuild to speed up creation time. For more information on templates, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
-## 사전 빌드 프로세스
+## The prebuild process
-사전 빌드를 만들려면 사전 빌드 구성을 설정합니다. 구성을 저장하면 {% data variables.product.prodname_actions %} 워크플로가 실행되어 필요한 각 사전 빌드를 만들며, 사전 빌드당 하나의 워크플로가 실행됩니다. 또한 워크플로는 구성에 대한 사전 빌드를 업데이트해야 할 때마다 실행됩니다. 예약된 간격, 사전 빌드 사용 리포지토리로 푸시 또는 개발 컨테이너 구성을 변경할 때 발생할 수 있습니다. 자세한 내용은 “[사전 빌드 구성](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)”을 참조하세요.
+To create a prebuild you set up a prebuild configuration. When you save the configuration, a {% data variables.product.prodname_actions %} workflow runs to create each of the required prebuilds; one workflow per prebuild. Workflows also run whenever the prebuilds for your configuration need to be updated. This can happen at scheduled intervals, on pushes to a prebuild-enabled repository, or when you change the dev container configuration. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
-사전 빌드 구성 워크플로가 실행되면 {% data variables.product.prodname_dotcom %}에서 임시 codespace를 만들어 `devcontainer.json` 파일의 모든 `onCreateCommand` 명령과 `updateContentCommand` 명령을 포함하여 설정 작업을 수행합니다. 사전 빌드를 만드는 동안에는 `postCreateCommand` 명령이 실행되지 않습니다. 이러한 명령에 대한 자세한 내용은 {% data variables.product.prodname_vscode_shortname %} 설명서에서 [`devcontainer.json`참조](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties)를 확인하세요. 생성된 컨테이너의 스냅샷이 만들어지고 저장됩니다.
+When a prebuild configuration workflow runs, {% data variables.product.prodname_dotcom %} creates a temporary codespace, performing setup operations up to and including any `onCreateCommand` and `updateContentCommand` commands in the `devcontainer.json` file. No `postCreateCommand` commands are run during the creation of a prebuild. For more information about these commands, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. A snapshot of the generated container is then taken and stored.
-다른 {% data variables.product.prodname_actions %} 워크플로와 마찬가지로 사전 빌드 구성 워크플로를 실행하면 계정에 포함된 {% data variables.product.prodname_actions %} 분 중 일부가 사용되거나 {% data variables.product.prodname_actions %} 분 요금이 부과됩니다. codespace 사전 빌드의 스토리지는 활성 또는 중지된 codespace 스토리지와 동일한 방식으로 청구됩니다. 자세한 내용은 “[{% data variables.product.prodname_github_codespaces %} 청구 정보](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)”를 참조하세요.
+As with other {% data variables.product.prodname_actions %} workflows, running a prebuild configuration workflow will either consume some of the {% data variables.product.prodname_actions %} minutes included with your account, if you have any, or it will incur charges for {% data variables.product.prodname_actions %} minutes. Storage of codespace prebuilds is billed in the same way as storage of active or stopped codespaces. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
-사전 빌드에서 codespace를 만들 때 {% data variables.product.prodname_dotcom %}에서는 스토리지로부터 기존 컨테이너 스냅샷을 다운로드하고 새 가상 머신에 배포하여 개발 컨테이너 구성에 지정된 나머지 명령을 완료합니다. 리포지토리 복제와 같은 많은 작업이 이미 수행되었으므로 사전 빌드에서 codespace를 만드는 것이 사전 빌드 없이 만드는 것보다 훨씬 빠를 수 있습니다. 리포지토리가 크거나 `onCreateCommand` 명령이 실행되는 데 시간이 오래 걸리는 경우에도 마찬가지입니다.
+When you create a codespace from a prebuild, {% data variables.product.prodname_dotcom %} downloads the existing container snapshot from storage and deploys it on a fresh virtual machine, completing the remaining commands specified in the dev container configuration. Since many operations have already been performed, such as cloning the repository, creating a codespace from a prebuild can be substantially quicker than creating one without a prebuild. This is true where the repository is large and/or `onCreateCommand` commands take a long time to run.
-## 사전 빌드된 분기로 변경 내용 푸시 정보
+## About pushing changes to prebuild-enabled branches
-기본적으로 사전 빌드 구성이 있는 분기에 푸시할 때마다 {% data variables.product.prodname_dotcom %}관리되는 {% data variables.product.prodname_actions %} 워크플로가 실행되어 사전 빌드를 업데이트합니다. 연결된 리포지토리의 개발 컨테이너 구성에 영향을 주는 변경 사항이 없는 한 사전 빌드 워크플로에는 지정된 사전 빌드 구성에 대해 한 번에 하나의 워크플로 실행의 동시성 제한이 있습니다. 자세한 내용은 “[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”를 참조하세요. 실행이 이미 진행 중인 경우 가장 최근에 대기열에 있던 워크플로 실행이 현재 실행이 완료된 후 다음으로 실행됩니다.
+By default, each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed {% data variables.product.prodname_actions %} workflow run to update the prebuild. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." If a run is already in progress, the workflow run that was queued most recently will run next, after the current run completes.
-각 푸시에 대해 사전 빌드를 업데이트하도록 설정하면, 리포지토리에 대한 푸시가 매우 자주 수행되는 경우 사전 빌드 업데이트는 최소한 사전 빌드 워크플로를 실행하는 데 걸리는 빈도만큼 발생합니다. 즉, 워크플로 실행을 완료하는 데 일반적으로 1시간이 걸린다면 실행이 성공하는 경우 또는 분기에 개발 컨테이너 구성을 변경하는 푸시가 있는 경우 약 1시간 동안 리포지토리에 대한 사전 빌드가 생성됩니다.
+With the prebuild set to be updated on each push, it means that if there are very frequent pushes to your repository, prebuild updates will occur at least as often as it takes to run the prebuild workflow. That is, if your workflow run typically takes one hour to complete, prebuilds will be created for your repository roughly hourly, if the run succeeds, or more often if there were pushes that change the dev container configuration on the branch.
-예를 들어 사전 빌드된 구성이 있는 분기에 대해 5개의 푸시가 연속해서 만들어지고 있다고 가정해 보겠습니다. 이 상황에서는 다음을 수행합니다.
+For example, let's imagine 5 pushes are made, in quick succession, against a branch that has a prebuild configuration. In this situation:
-* 사전 빌드를 업데이트하기 위해 첫 번째 푸시에 대한 워크플로 실행이 시작됩니다.
-* 나머지 4개 푸시가 개발 컨테이너 구성에 영향을 미치지 않으면 이러한 푸시에 대한 워크플로 실행이 “보류 중” 상태로 큐에 대기됩니다.
+* A workflow run is started for the first push, to update the prebuild.
+* If the 4 remaining pushes do not affect the dev container configuration, the workflow runs for these are queued in a "pending" state.
- 나머지 4개 푸시 중 하나가 개발 컨테이너 구성을 변경하는 경우 서비스는 해당 구성을 건너뛰지 않고 사전 빌드 만들기 워크플로를 즉시 실행하여 성공하면 그에 따라 사전 빌드를 업데이트합니다.
+ If any of the remaining 4 pushes change the dev container configuration, then the service will not skip that one and will immediately run the prebuild creation workflow, updating the prebuild accordingly if it succeeds.
-* 첫 번째 실행이 완료되면 푸시 2, 3, 4에 대한 워크플로 실행이 취소되고 마지막 큐에 대기된 워크플로(푸시 5의 경우)가 실행되며 사전 빌드가 업데이트됩니다.
+* Once the first run completes, workflow runs for pushes 2, 3, and 4 will be canceled, and the last queued workflow (for push 5) will run and update the prebuild.
diff --git a/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 23ea567b8b..8f7905ac45 100644
--- a/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -1,6 +1,6 @@
---
-title: Creating a default community health file(기본 커뮤니티 상태 파일 만들기)
-intro: CONTRIBUTING 및 CODE_OF_CONDUCT 같은 기본 커뮤니티 상태 파일을 만들 수 있습니다. 기본 파일은 해당 형식의 자체 파일을 포함하지 않는 계정에서 소유한 모든 리포지토리에 사용됩니다.
+title: Creating a default community health file
+intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
redirect_from:
- /articles/creating-a-default-community-health-file-for-your-organization
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
@@ -12,41 +12,46 @@ versions:
topics:
- Community
shortTitle: Community health file
-ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ko-KR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145117636'
---
-## 기본 커뮤니티 상태 파일 정보
-리포지토리의 루트 또는 `docs` 또는 `.github` 폴더에 있는 `.github`라는 이름의 공개 리포지토리에 기본 커뮤니티 상태 파일을 추가할 수 있습니다.
+## About default community health files
-{% data variables.product.product_name %}은(는) 해당 계정이 소유하고 있으며 다음과 같은 위치에 해당 유형의 파일이 없는 리포지토리에 대해 이러한 기본 파일을 사용하고 표시합니다.
-- 리포지토리의 루트
-- `.github` 폴더
-- `docs` 폴더
+You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders.
-예를 들어 자체 CONTRIBUTING 파일이 없는 리포지토리에서 문제 또는 끌어오기 요청을 생성하는 사용자는 기본 CONTRIBUTING 파일에 대한 링크를 볼 수 있습니다. 리포지토리에 자체 `.github/ISSUE_TEMPLATE` 폴더가 있는 경우{% ifversion fpt or ghes or ghec %}(문제 템플릿 또는 *config.yml* 파일 포함),{% endif %} 기본 `.github/ISSUE_TEMPLATE` 폴더의 내용이 사용되지 않습니다.
+{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
+- the root of the repository
+- the `.github` folder
+- the `docs` folder
-기본 파일은 `.github` 리포지토리에만 저장되므로 개별 리포지토리의 클론, 패키지 또는 다운로드에 포함되지 않습니다.
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
-## 지원되는 파일 형식
+Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
-다음 커뮤니티 상태 파일에 대한 조직{% ifversion fpt or ghes or ghec %} 또는 개인 계정{% endif %}에서 기본값을 만들 수 있습니다.
+## Supported file types
-커뮤니티 상태 파일 | 설명 --- | ---{% ifversion fpt or ghec %} *CODE_OF_CONDUCT.md* | CODE_OF_CONDUCT 파일은 커뮤니티에 참여하는 방법에 대한 표준을 정의합니다. 자세한 내용은 “[프로젝트에 사용 규정 추가](/articles/adding-a-code-of-conduct-to-your-project/)”를 참조하세요. {% endif %} *CONTRIBUTING.md* | CONTRIBUTEING 파일은 사용자가 프로젝트에 기여하는 방법을 전달합니다. 자세한 내용은 “[리포지토리 기여자에 대한 지침 설정](/articles/setting-guidelines-for-repository-contributors/)”을 참조하세요. {% ifversion fpt or ghec %} *FUNDING.yml* | FUNDING 파일은 리포지토리에 스폰서 단추를 표시하여 오픈 소스 프로젝트에 대한 자금 조달 옵션의 가시성을 높입니다. 자세한 내용은 “[리포지토리에 스폰서 단추 표시](/articles/displaying-a-sponsor-button-in-your-repository)”를 참조하세요. {% endif %} 문제 및 끌어오기 요청 템플릿{% ifversion fpt or ghes or ghec %} 및 *config.yml*{% endif %} | 문제 및 끌어오기 요청 템플릿은 리포지토리에서 문제 및 끌어오기 요청을 열 때 기여자가 포함할 정보를 사용자 지정하고 표준화합니다. 자세한 내용은 “[문제 및 끌어오기 요청 템플릿 정보](/articles/about-issue-and-pull-request-templates/)”를 참조하세요. {% ifversion fpt or ghes or ghec %} *SECURITY.md* | SECURITY 파일은 프로젝트에서 보안 취약성을 보고하는 방법에 대한 지침을 제공합니다. 자세한 내용은 “[리포지토리에 보안 정책 추가](/code-security/getting-started/adding-a-security-policy-to-your-repository)”를 참조하세요.{% endif %} *SUPPORT.md* | 지원 파일을 사용하면 프로젝트에 대한 도움말을 얻을 수 있는 방법을 알 수 있습니다. 자세한 내용은 “[프로젝트에 지원 리소스 추가](/articles/adding-support-resources-to-your-project/)”를 참조하세요.
+You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
-기본 라이선스 파일을 만들 수 없습니다. 프로젝트를 복제, 패키지 또는 다운로드할 때 파일이 포함되도록 라이선스 파일을 개별 리포지토리에 추가해야 합니다.
+Community health file | Description
+--- | ---{% ifversion fpt or ghec %}
+*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
+*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion discussion-category-forms %}
+Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[Creating discussion category forms](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
+*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
+Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes or ghec %}
+*SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
-## 기본 파일에 대한 리포지토리 만들기
+You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
+
+## Creating a repository for default files
{% data reusables.repositories.create_new %}
-2. **소유자** 드롭다운 메뉴를 사용하고 기본 파일을 만들려는 조직{% ifversion fpt or ghes or ghec %} 또는 개인 계정{% endif %}을 선택합니다.
- 
-3. 리포지토리의 이름과 설명(선택 사항)에 **.github** 를 입력합니다.
- 
-4. 리포지토리 상태가 **공개** 로 설정되어 있는지 확인합니다(기본 파일의 리포지토리는 비공개일 수 없음).
-  {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
-7. 리포지토리에서 지원되는 커뮤니티 상태 파일 중 하나를 만듭니다. 문제 템플릿{% ifversion fpt or ghes or ghec %} 및 해당 구성 파일{% endif %}은 `.github/ISSUE_TEMPLATE` 폴더에 있어야 합니다. 기타 지원되는 모든 파일은 리포지토리의 루트, `.github` 폴더 또는 `docs` 폴더에 있을 수 있습니다. 자세한 내용은 “[새 파일 만들기](/articles/creating-new-files/)”를 참조하세요.
+2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
+ 
+3. Type **.github** as the name for your repository, and an optional description.
+ 
+4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+ 
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
diff --git a/translations/ko-KR/content/discussions/managing-discussions-for-your-community/index.md b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/index.md
index ff6f5f9a93..4e0ace1d3a 100644
--- a/translations/ko-KR/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,6 +9,8 @@ children:
- /managing-categories-for-discussions
- /moderating-discussions
- /viewing-insights-for-your-discussions
+ - /creating-discussion-category-forms
+ - /syntax-for-discussion-category-forms
ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
ms.translationtype: HT
diff --git a/translations/ko-KR/content/rest/overview/libraries.md b/translations/ko-KR/content/rest/overview/libraries.md
index 5f33126beb..b2869962c0 100644
--- a/translations/ko-KR/content/rest/overview/libraries.md
+++ b/translations/ko-KR/content/rest/overview/libraries.md
@@ -11,14 +11,14 @@ versions:
ghec: '*'
topics:
- API
-ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
-ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
+ms.openlocfilehash: 5f633132edddb17ae129a3feba791ab8ec780366
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: MT
ms.contentlocale: ko-KR
-ms.lasthandoff: 12/01/2022
-ms.locfileid: '148190063'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191880'
---
-
+
## 다양한 버전으로 제공되는 Octokit
@@ -26,7 +26,7 @@ ms.locfileid: '148190063'
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
-- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+- **JavaScript** → [octokit.js](https://github.com/octokit/octokit.js)
## 타사 라이브러리
diff --git a/translations/ko-KR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/ko-KR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
index 87f32b381f..e53a389ec6 100644
--- a/translations/ko-KR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
+++ b/translations/ko-KR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -1,6 +1,6 @@
---
-title: 지원 티켓 보기 및 업데이트
-intro: '지원 티켓을 보고{% ifversion ghes or ghec %}, 티켓에 대해 동료와 공동 작업하고,{% endif %} {% data variables.contact.support_portal %}을 사용하여 {% data variables.contact.github_support %}에 응답할 수 있습니다.'
+title: Viewing and updating support tickets
+intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.'
shortTitle: Managing your tickets
versions:
fpt: '*'
@@ -8,62 +8,64 @@ versions:
ghes: '*'
topics:
- Support
-ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ko-KR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147051982'
---
-## 티켓 관리 정보
+
+## About ticket management
{% data reusables.support.zendesk-old-tickets %}
-[GitHub 지원 포털](https://support.github.com/)을 사용하여 현재 및 이전 지원 티켓을 보고 {% data variables.contact.github_support %}에 응답할 수 있습니다. 120일이 지나면 해결된 티켓이 보관되며{% ifversion ghec or ghes or ghae %}, 보관된 티켓은 엔터프라이즈 계정에 대해서만 볼 수 있습니다{% endif %}.
+You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}. After 120 days, resolved tickets are archived{% ifversion ghec or ghes or ghae %}, and archived tickets can only be viewed for enterprise accounts{% endif %}.
-{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+{% ifversion ghes or ghec %}
+{% data reusables.enterprise-accounts.support-entitlements %}
+{% endif %}
-## 최근 지원 티켓 보기
+## Viewing your recent support tickets
{% data reusables.support.view-open-tickets %}
-1. 텍스트 상자에서 주석 기록을 읽을 수 있습니다. 가장 최근의 응답은 맨 위에 있습니다.
-
+1. Under the text box, you can read the comment history. The most recent response is at the top.
+
+ 
+
+1. Optionally, to translate the ticket comment, click {% octicon "globe" aria-label="The globe icon" %} and choose your preferred language from the dropdown menu. You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish.
+
+ 
{% ifversion ghec or ghes or ghae %}
-## 보관된 지원 티켓 보기
+## Viewing your archived support tickets
-엔터프라이즈 계정의 보관된 티켓만 볼 수 있습니다.
+You can only view archived tickets for an enterprise account.
{% data reusables.support.navigate-to-my-tickets %}
-1. **내 티켓** 드롭다운 메뉴를 선택하고 엔터프라이즈 계정의 이름을 클릭합니다.
+1. Select the **My Tickets** drop-down menu and click the name of the enterprise account.
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
- 
-1. "내 티켓" 테이블 아래에서 **보관된 티켓 보기** 를 클릭합니다.
+ 
+1. Under the "My tickets" table, click **View archived tickets**.
{% endif %}
-## 지원 티켓 업데이트
+## Updating support tickets
{% data reusables.support.view-open-tickets %}
-1. 필요에 따라 이슈가 해결되면 텍스트 상자에서 **티켓 닫기** 를 클릭합니다.
-
-1. GitHub 지원에 응답하고 티켓에 새 주석을 추가하려면 텍스트 상자에 응답을 입력합니다.
-
-1. 티켓에 주석을 추가하려면 **주석** 을 클릭합니다.
-
+1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
+
+1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
+
+1. To add your comment to the ticket, click **Comment**.
+
{% ifversion ghec or ghes %}
-## 지원 티켓 공동 작업
+## Collaborating on support tickets
-지원 포털을 사용하여 지원 티켓에 대해 동료와 협력할 수 있습니다. 소유자, 청구 관리자 및 지원 자격이 있는 기타 엔터프라이즈 멤버는 엔터프라이즈 계정 또는 엔터프라이즈 계정으로 관리되는 조직과 연결된 티켓을 볼 수 있습니다. 자세한 내용은 “[엔터프라이즈에 대한 지원 자격 관리](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)”를 참조하세요.
+You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-티켓을 보는 것 외에도, 티켓에 메일 주소가 복사되었거나 티켓을 연 사람이 엔터프라이즈 계정 또는 엔터프라이즈 계정으로 관리되는 조직에 대해 확인된 도메인에서 메일 주소를 사용한 경우 지원 티켓에 주석을 추가할 수도 있습니다. 도메인 확인에 대한 자세한 내용은 “[엔터프라이즈의 도메인 확인 또는 승인](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)” 및 “[조직의 도메인 확인 또는 승인](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)”을 참조하세요.
+In addition to viewing tickets, you can also add comments to support tickets if your email address is copied on the ticket or if the person who opened the ticket used an email address with a domain that is verified for the enterprise account or organization managed by an enterprise account. For more information about verifying a domain, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Verifying or approving a domain for your organization](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
{% endif %}
-## 추가 참고 자료
+## Further reading
-- “[GitHub 지원 정보](/support/learning-about-github-support/about-github-support)”
+- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
diff --git a/translations/ko-KR/content/support/learning-about-github-support/about-github-support.md b/translations/ko-KR/content/support/learning-about-github-support/about-github-support.md
index f5d6525f05..be735ece17 100644
--- a/translations/ko-KR/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/ko-KR/content/support/learning-about-github-support/about-github-support.md
@@ -83,6 +83,10 @@ If you have any paid product or are a member of an organization with a paid prod
With {% data variables.product.product_name %}, you have access to support in English and Japanese.
{% endif %}
+{% ifversion fpt or ghec or ghes %}
+{% data reusables.support.support-ticket-translation-option %}
+{% endif %}
+
{% ifversion ghes or ghec %}
To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
diff --git a/translations/ko-KR/data/release-notes/enterprise-server/3-5/4.yml b/translations/ko-KR/data/release-notes/enterprise-server/3-5/4.yml
index 028b8750b6..2d4ef88879 100644
--- a/translations/ko-KR/data/release-notes/enterprise-server/3-5/4.yml
+++ b/translations/ko-KR/data/release-notes/enterprise-server/3-5/4.yml
@@ -29,4 +29,5 @@ sections:
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
- |
- GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
\ No newline at end of file
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ko-KR/data/release-notes/enterprise-server/3-5/5.yml b/translations/ko-KR/data/release-notes/enterprise-server/3-5/5.yml
index 8809fed1f3..05de05ac2b 100644
--- a/translations/ko-KR/data/release-notes/enterprise-server/3-5/5.yml
+++ b/translations/ko-KR/data/release-notes/enterprise-server/3-5/5.yml
@@ -1,27 +1,30 @@
date: '2022-08-30'
sections:
bugs:
- - 임시 액세스를 위해 리포지토리의 잠금을 해제한 후 사이트 관리자가 리포지토리의 보안 제품에 대한 설정을 관리할 수 없습니다.
- - 관리 콘솔과 `/home/admin/.ssh/authorized_keys` 파일 모두에 중복된 관리 SSH 키가 나타날 수 있습니다.
- - "기능이 포함된 http(s)://HOSTNAME/stafftools/users/USERNAME/admin에서 개별 사용자에 대한 사이트 관리자 페이지는 GitHub Enterprise Server용이 아닙니다."
- - 경우에 따라 `ghe-cluster-config-apply`를 실행하면 빈 구성이 클러스터의 기존 노드에 복제될 수 있습니다.
- - 경우에 따라 `ghe-config-apply`로 시작된 구성 실행이 완료되지 않았거나 `Container count mismatch` 오류를 반환했습니다.
- - GitHub Enterprise Server 인스턴스에서 자체 서명된 TLS 인증서를 업데이트한 후 웹 인터페이스의 일부 페이지에 UI 요소가 나타나지 않았습니다.
- - 웹 인터페이스 위쪽의 사이트 관리 표시줄에 현재 실행 중인 애플리케이션 버전의 SHA에 대한 끊어진 링크가 포함되었습니다.
- - 일부 경우에는 스레드가 안전하지 않음에도 불구하고 동시에 사용된 라이브러리로 인해 백그라운드 작업이 중단될 수 있습니다.
- - 사이트 관리자가 GitHub Enterprise Server 3.4로 직접 업그레이드하지 않은 경우 GitHub Advanced Security 고객에 대한 비밀 검사의 경고가 웹 UI 및 REST API에서 누락되었습니다. 이제 경고가 표시됩니다.
- - 사용자가 리포지토리를 조직에 포크하면 긴 조직 목록이 제대로 렌더링되지 않습니다.
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
+ - When a user forked a repository into an organization, a long list of organizations would not render properly.
changes:
- - "병렬 로그 검사를 통해 지원 번들을 더 빠르게 생성할 수 있습니다. 지원 번들에 대한 자세한 내용은 \"[GitHub 지원에 데이터 지원](/support/contacting-github-support/providing-data-to-github-support)\"을 참조하세요."
- - "`organization` 또는 `org` 경로를 포함하는 API는 이제 조직의 슬러그 또는 ID를 허용합니다. 이전에는 API가 슬래그만 허용했기 때문에 GitHub Advanced Security 엔드포인트에 대한 `Link` 헤더에 액세스할 수 없었습니다. 자세한 내용은 REST API 설명서에서 \"[조직](https://docs.github.com/rest/orgs/orgs)\"을 참조하세요."
- - "엔터프라이즈 감사 로그에는 이제 `project.create`와 같은 사용자 생성 이벤트가 더 많이 포함됩니다. REST API는 `repo.create`와 같은 추가 사용자 생성 이벤트도 반환합니다. 자세한 내용은 \"[엔터프라이즈의 감사 로그에 액세스](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)\" 및 \"[엔터프라이즈의 감사 로그 API 사용](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)\"을 참조하세요."
- - "경우에 따라 캐시 복제본이 최근에 업데이트된 리포지토리에서 일부 Git 작업을 거부할 수 있습니다. 리포지토리 캐싱에 대한 자세한 내용은 \"[리포지토리 캐싱 정보](/admin/enterprise-management/caching-repositories/about-repository-caching)\"를 참조하세요."
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
known_issues:
- - "사용자 없이 새로 설정된 {% data variables.product.prodname_ghe_server %} 인스턴스에서 공격자는 첫 번째 관리 사용자를 만들 수 있습니다."
- - 사용자 지정 방화벽 규칙은 업그레이드 프로세스 중에 제거됩니다.
- - "Git LFS 추적 파일[웹 인터페이스를 통해 업로드됨](https://github.com/blog/2105-upload-files-to-your-repositories)이 리포지토리에 직접 잘못 추가되었습니다."
- - 이슈에 동일한 리포지토리의 Blob에 대한 고정 링크가 포함되었지만 Blob의 파일 경로가 255자보다 긴 경우 해당 이슈를 종료할 수 없습니다.
- - GitHub Connect에서 “사용자가 GitHub.com을 검색할 수 있음”이 사용하도록 설정되면 프라이빗 및 내부 리포지토리의 이슈가 GitHub.com 검색 결과에 포함되지 않습니다.
- - "{% data variables.product.prodname_registry %} npm 레지스트리는 더 이상 메타데이터 응답에서 시간 값을 반환하지 않습니다. 이 작업은 성능을 크게 향상시키기 위해 수행되었습니다. 메타데이터 응답의 일부로 시간 값을 반환하는 데 필요한 모든 데이터를 계속 보유하고 있으며, 기존 성능 이슈가 해결되면 이 값의 반환을 다시 시작할 예정입니다."
- - 사전 수신 후크 처리에만 해당되는 리소스 한도로 인해 일부 사전 수신 후크가 실패할 수 있습니다.
- - 다른 호스트에서 수행된 백업에서 어플라이언스를 복원한 후에는 작업 서비스를 다시 시작해야 합니다.
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ko-KR/data/release-notes/enterprise-server/3-6/1.yml b/translations/ko-KR/data/release-notes/enterprise-server/3-6/1.yml
index 003e13d025..6e638df146 100644
--- a/translations/ko-KR/data/release-notes/enterprise-server/3-6/1.yml
+++ b/translations/ko-KR/data/release-notes/enterprise-server/3-6/1.yml
@@ -1,33 +1,38 @@
date: '2022-08-30'
sections:
bugs:
- - 임시 액세스를 위해 리포지토리의 잠금을 해제한 후 사이트 관리자가 리포지토리의 보안 제품에 대한 설정을 관리할 수 없습니다.
- - 관리 콘솔과 `/home/admin/.ssh/authorized_keys` 파일 모두에 중복된 관리 SSH 키가 나타날 수 있습니다.
- - "기능이 포함된 http(s)://HOSTNAME/stafftools/users/USERNAME/admin에서 개별 사용자에 대한 사이트 관리자 페이지는 GitHub Enterprise Server용이 아닙니다."
- - 경우에 따라 `ghe-cluster-config-apply`를 실행하면 빈 구성이 클러스터의 기존 노드에 복제될 수 있습니다.
- - 경우에 따라 `ghe-config-apply`로 시작된 구성 실행이 완료되지 않았거나 `Container count mismatch` 오류를 반환했습니다.
- - GitHub Enterprise Server 인스턴스에서 자체 서명된 TLS 인증서를 업데이트한 후 웹 인터페이스의 일부 페이지에 UI 요소가 나타나지 않았습니다.
- - 일부 경우에는 스레드가 안전하지 않음에도 불구하고 동시에 사용된 라이브러리로 인해 백그라운드 작업이 중단될 수 있습니다.
- - 웹 인터페이스 위쪽의 사이트 관리 표시줄에 현재 실행 중인 애플리케이션 버전의 SHA에 대한 끊어진 링크가 포함되었습니다.
- - 조직 소유자는 토론을 만드는 데 필요한 액세스 수준을 설정할 수 없었습니다.
- - 토론 사용자가 GitHub.com의 커뮤니티 지침을 잘못 참조했습니다.
- - 토론을 만들기 전에 이메일을 확인하라는 잘못된 지시를 받은 경우도 있습니다.
- - 사이트 관리자가 GitHub Enterprise Server 3.4로 직접 업그레이드하지 않은 경우 GitHub Advanced Security 고객에 대한 비밀 검사의 경고가 웹 UI 및 REST API에서 누락되었습니다. 이제 경고가 표시됩니다.
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - Organization owners were unable to set the level of access required to create discussions.
+ - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
+ - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
changes:
- - "병렬 로그 검사를 통해 지원 번들을 더 빠르게 생성할 수 있습니다. 지원 번들에 대한 자세한 내용은 \"[GitHub 지원에 데이터 지원](/support/contacting-github-support/providing-data-to-github-support)\"을 참조하세요."
- - "`organization` 또는 `org` 경로를 포함하는 API는 이제 조직의 슬러그 또는 ID를 허용합니다. 이전에는 API가 슬래그만 허용했기 때문에 GitHub Advanced Security 엔드포인트에 대한 `Link` 헤더에 액세스할 수 없었습니다. 자세한 내용은 REST API 설명서에서 \"[조직](https://docs.github.com/rest/orgs/orgs)\"을 참조하세요."
- - "엔터프라이즈 감사 로그에는 이제 `project.create`와 같은 사용자 생성 이벤트가 더 많이 포함됩니다. REST API는 `repo.create`와 같은 추가 사용자 생성 이벤트도 반환합니다. 자세한 내용은 \"[엔터프라이즈의 감사 로그에 액세스](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)\" 및 \"[엔터프라이즈의 감사 로그 API 사용](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)\"을 참조하세요."
- - "경우에 따라 캐시 복제본이 최근에 업데이트된 리포지토리에서 일부 Git 작업을 거부할 수 있습니다. 리포지토리 캐싱에 대한 자세한 내용은 \"[리포지토리 캐싱 정보](/admin/enterprise-management/caching-repositories/about-repository-caching)\"를 참조하세요."
- - "이제 REST API를 사용하여 전역 공지 배너를 해제할 수 있도록 구성할 수 있습니다. 자세한 내용은 \"[엔터프라이즈에 대한 사용자 메시지 사용자 지정](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)\"을 참조하세요."
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+ - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
known_issues:
- - "사용자 없이 새로 설정된 {% data variables.product.prodname_ghe_server %} 인스턴스에서 공격자는 첫 번째 관리 사용자를 만들 수 있습니다."
- - 사용자 지정 방화벽 규칙은 업그레이드 프로세스 중에 제거됩니다.
- - "Git LFS 추적 파일[웹 인터페이스를 통해 업로드됨](https://github.com/blog/2105-upload-files-to-your-repositories)이 리포지토리에 직접 잘못 추가되었습니다."
- - 이슈에 동일한 리포지토리의 Blob에 대한 고정 링크가 포함되었지만 Blob의 파일 경로가 255자보다 긴 경우 해당 이슈를 종료할 수 없습니다.
- - GitHub Connect에서 “사용자가 GitHub.com을 검색할 수 있음”이 사용하도록 설정되면 프라이빗 및 내부 리포지토리의 이슈가 GitHub.com 검색 결과에 포함되지 않습니다.
- - "{% data variables.product.prodname_registry %} npm 레지스트리는 더 이상 메타데이터 응답에서 시간 값을 반환하지 않습니다. 이 작업은 성능을 크게 향상시키기 위해 수행되었습니다. 메타데이터 응답의 일부로 시간 값을 반환하는 데 필요한 모든 데이터를 계속 보유하고 있으며, 기존 성능 이슈가 해결되면 이 값의 반환을 다시 시작할 예정입니다."
- - 사전 수신 후크 처리에만 해당되는 리소스 한도로 인해 일부 사전 수신 후크가 실패할 수 있습니다.
- - 다른 호스트에서 수행한 백업에서 인스턴스가 복원되면 Actions 서비스를 다시 시작해야 합니다.
- - 리포지토리 설정에서 읽기 권한을 가진 사용자가 토론을 만들 수 있도록 허용하는 옵션을 활성화해도 이 기능을 활성화하지 않습니다.
- - 경우에 따라 사용자는 기존 이슈를 토론으로 변환할 수 없습니다.
- - "비밀 검사에 대한 사용자 지정 패턴에는 특히 \"비밀 이후\" 필드에서 종료 구분 기호로 `.*`가 있습니다. 이 구분 기호로 인해 리포지토리 전체의 비밀 검사에서 불일치가 발생하며, 검사가 완료되지 않은 리포지토리의 기록에서 차이를 확인할 수 있습니다. 증분 검사도 영향을 받을 수 있습니다. 검사와 관련된 이슈를 방지하려면 '.*' 구분 기호를 제거하도록 패턴 끝을 수정합니다."
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+ - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+ - In some cases, users cannot convert existing issues to discussions.
+ - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+ - |
+ After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/actions/if-supported-contexts.md b/translations/ko-KR/data/reusables/actions/if-supported-contexts.md
new file mode 100644
index 0000000000..8bbb51aba9
--- /dev/null
+++ b/translations/ko-KR/data/reusables/actions/if-supported-contexts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 31687bc8c34a11de5a36e5db2877d279740f0f8f
+ms.sourcegitcommit: 4f08a208a0d2e13dc109678750a962ea2f67e1ba
+ms.translationtype: MT
+ms.contentlocale: ko-KR
+ms.lasthandoff: 12/06/2022
+ms.locfileid: "148192061"
+---
+지원되는 컨텍스트 및 식을 사용하여 조건부를 만들 수 있습니다. 이 키에서 지원되는 컨텍스트에 대한 자세한 내용은 "[컨텍스트 가용성"을 참조하세요](/actions/learn-github-actions/contexts#context-availability).
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/ko-KR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index bc1890f881..d8df9a8bfe 100644
--- a/translations/ko-KR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/ko-KR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,12 +1,12 @@
---
-ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
+ms.openlocfilehash: eb897a445a5e5a90014097ba76a5ecb095aa0bef
+ms.sourcegitcommit: 4f08a208a0d2e13dc109678750a962ea2f67e1ba
+ms.translationtype: MT
ms.contentlocale: ko-KR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145114231"
+ms.lasthandoff: 12/06/2022
+ms.locfileid: "148192064"
---
-`jobs..if` 조건부를 사용하여 조건이 충족되지 않는 한, 작업이 실행되지 않도록 할 수 있습니다. 지원되는 컨텍스트 및 식을 사용하여 조건부를 만들 수 있습니다.
+`jobs..if` 조건부를 사용하여 조건이 충족되지 않는 한, 작업이 실행되지 않도록 할 수 있습니다. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} 자세한 내용은 “[식](/actions/learn-github-actions/expressions)”을 참조하세요.
diff --git a/translations/ko-KR/data/reusables/actions/reusable-workflows-enterprise-beta.md b/translations/ko-KR/data/reusables/actions/reusable-workflows-enterprise-beta.md
new file mode 100644
index 0000000000..6064e0e17e
--- /dev/null
+++ b/translations/ko-KR/data/reusables/actions/reusable-workflows-enterprise-beta.md
@@ -0,0 +1,17 @@
+{% ifversion ghes = 3.4 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently in beta and subject to change.
+
+{% endnote %}
+
+{% elsif ghae > 3.3 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently unavailable in {% data variables.product.product_name %}, but will be available in a future update.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/ko-KR/data/reusables/actions/reusable-workflows-ghes-beta.md
deleted file mode 100644
index 6fb3ef2e4f..0000000000
--- a/translations/ko-KR/data/reusables/actions/reusable-workflows-ghes-beta.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% ifversion ghes = 3.4 %}
-
-{% note %}
-
-**Note**: Reusable workflows are currently in beta and subject to change.
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/ko-KR/data/reusables/enterprise-accounts/dormant-user-activity.md
index 80878d1726..24b839f410 100644
--- a/translations/ko-KR/data/reusables/enterprise-accounts/dormant-user-activity.md
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
- Starring a repository
- Deleting a repository
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
+- Joining an organization
+
+{% ifversion ghes %}
+A user will also be considered active if their account has been updated by LDAP.
+{% endif %}
diff --git a/translations/ko-KR/data/ui.yml b/translations/ko-KR/data/ui.yml
index 1e8377dd72..29dec0fbef 100644
--- a/translations/ko-KR/data/ui.yml
+++ b/translations/ko-KR/data/ui.yml
@@ -127,7 +127,7 @@ products:
rest:
banner:
api_versioned: The REST API is now versioned.
- api_version_info: For more information, see "About API versioning".
+ api_version_info: For more information, see "About API versioning."
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "About versions of GitHub Docs".
versioning:
about_versions: About REST API versions
diff --git a/translations/log/msft-cn-resets.csv b/translations/log/msft-cn-resets.csv
index 158d0572bb..660327c9eb 100644
--- a/translations/log/msft-cn-resets.csv
+++ b/translations/log/msft-cn-resets.csv
@@ -406,6 +406,7 @@ translations/zh-CN/data/reusables/getting-started/learning-lab.md,file deleted b
translations/zh-CN/data/reusables/open-source/open-source-learning-lab.md,file deleted because it no longer exists in main
translations/zh-CN/data/reusables/pages/pages-builds-with-github-actions-public-beta.md,file deleted because it no longer exists in main
translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md,file deleted because it no longer exists in main
+translations/zh-CN/data/reusables/rest-reference/apps/oauth-applications.md,file deleted because it no longer exists in main
translations/zh-CN/data/reusables/rest-reference/branches/branch-protection.md,file deleted because it no longer exists in main
translations/zh-CN/data/reusables/rest-reference/checks/runs.md,file deleted because it no longer exists in main
translations/zh-CN/data/reusables/rest-reference/deployments/statuses.md,file deleted because it no longer exists in main
@@ -434,20 +435,20 @@ translations/zh-CN/data/reusables/security-center/beta.md,file deleted because i
translations/zh-CN/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
+translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,rendering error
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error
@@ -456,9 +457,9 @@ translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-pers
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,rendering error
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md,rendering error
-translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
+translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
+translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags
+translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags
translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
@@ -491,11 +492,11 @@ translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-
translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
-translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
+translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
translations/zh-CN/content/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
+translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md,rendering error
translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
translations/zh-CN/content/actions/quickstart.md,rendering error
@@ -515,76 +516,71 @@ translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md,rend
translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
-translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,rendering error
+translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,rendering error
+translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
+translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
+translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
translations/zh-CN/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
translations/zh-CN/content/admin/enterprise-management/caching-repositories/index.md,rendering error
translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
translations/zh-CN/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
+translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,rendering error
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md,rendering error
+translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,rendering error
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
+translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
translations/zh-CN/content/admin/identity-and-access-management/index.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,rendering error
+translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
+translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,broken liquid tags
+translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags
+translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags
+translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
+translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
+translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,rendering error
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,rendering error
+translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
+translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags
@@ -593,73 +589,71 @@ translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-ser
translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error
translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
-translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error
-translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error
+translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags
+translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,rendering error
+translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md,rendering error
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/overview/about-data-residency.md,rendering error
+translations/zh-CN/content/admin/overview/about-data-residency.md,broken liquid tags
translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,rendering error
-translations/zh-CN/content/admin/overview/about-github-enterprise-server.md,rendering error
+translations/zh-CN/content/admin/overview/about-github-enterprise-server.md,broken liquid tags
translations/zh-CN/content/admin/overview/about-github-for-enterprises.md,rendering error
translations/zh-CN/content/admin/overview/system-overview.md,rendering error
-translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
-translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,rendering error
-translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
+translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
+translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
+translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
+translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags
+translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,rendering error
+translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags
translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,rendering error
+translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
+translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags
translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error
translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,rendering error
translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,rendering error
+translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
+translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags
+translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags
+translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,rendering error
+translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
translations/zh-CN/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,rendering error
-translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,rendering error
+translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags
translations/zh-CN/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error
translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error
+translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
+translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
-translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,rendering error
-translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
-translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
+translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,broken liquid tags
+translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
+translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
translations/zh-CN/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
@@ -668,13 +662,13 @@ translations/zh-CN/content/billing/managing-billing-for-github-packages/about-bi
translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,rendering error
translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
+translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags
translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,rendering error
-translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,rendering error
-translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,rendering error
+translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
+translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,rendering error
-translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,rendering error
-translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,rendering error
+translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
+translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
@@ -684,12 +678,12 @@ translations/zh-CN/content/code-security/code-scanning/automatically-scanning-yo
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
+translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
+translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
@@ -718,10 +712,7 @@ translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-
translations/zh-CN/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
translations/zh-CN/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error
translations/zh-CN/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
-translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error
-translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
-translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md,rendering error
translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md,rendering error
translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md,rendering error
@@ -731,54 +722,45 @@ translations/zh-CN/content/code-security/supply-chain-security/understanding-you
translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
translations/zh-CN/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
-translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error
-translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error
-translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error
-translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error
-translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
+translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
+translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
-translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
-translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
+translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
+translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
translations/zh-CN/content/copilot/quickstart.md,broken liquid tags
-translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error
+translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
+translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error
translations/zh-CN/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
+translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags
translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
-translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
-translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error
-translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
+translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,broken liquid tags
+translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md,broken liquid tags
+translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags
translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags
-translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
+translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags
+translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
translations/zh-CN/content/developers/overview/about-githubs-apis.md,broken liquid tags
-translations/zh-CN/content/developers/overview/managing-deploy-keys.md,rendering error
+translations/zh-CN/content/developers/overview/managing-deploy-keys.md,broken liquid tags
translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
translations/zh-CN/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,rendering error
-translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,rendering error
-translations/zh-CN/content/discussions/guides/finding-your-discussions.md,rendering error
-translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,rendering error
-translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md,rendering error
+translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
+translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
+translations/zh-CN/content/discussions/guides/finding-your-discussions.md,broken liquid tags
+translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,rendering error
translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
+translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
+translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
-translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
+translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
+translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags
translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md,broken liquid tags
translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
@@ -786,26 +768,24 @@ translations/zh-CN/content/get-started/getting-started-with-git/caching-your-git
translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
translations/zh-CN/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md,rendering error
-translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,rendering error
-translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,rendering error
+translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
+translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags
translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags
translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags
translations/zh-CN/content/get-started/learning-about-github/githubs-products.md,rendering error
-translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
+translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
+translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
+translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
translations/zh-CN/content/get-started/quickstart/be-social.md,broken liquid tags
translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md,rendering error
-translations/zh-CN/content/get-started/quickstart/create-a-repo.md,rendering error
+translations/zh-CN/content/get-started/quickstart/create-a-repo.md,broken liquid tags
translations/zh-CN/content/get-started/quickstart/fork-a-repo.md,rendering error
translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
-translations/zh-CN/content/get-started/using-git/about-git-rebase.md,rendering error
+translations/zh-CN/content/get-started/using-git/about-git-rebase.md,broken liquid tags
translations/zh-CN/content/get-started/using-github/github-mobile.md,rendering error
translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md,rendering error
translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
@@ -819,7 +799,7 @@ translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md,renderin
translations/zh-CN/content/graphql/guides/introduction-to-graphql.md,broken liquid tags
translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md,rendering error
translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
-translations/zh-CN/content/graphql/overview/about-the-graphql-api.md,rendering error
+translations/zh-CN/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
translations/zh-CN/content/graphql/reference/enums.md,rendering error
translations/zh-CN/content/graphql/reference/input-objects.md,rendering error
translations/zh-CN/content/graphql/reference/interfaces.md,rendering error
@@ -829,16 +809,15 @@ translations/zh-CN/content/graphql/reference/unions.md,rendering error
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error
translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
-translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
-translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
+translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
+translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
+translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md,rendering error
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
+translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags
translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error
translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error
@@ -849,7 +828,7 @@ translations/zh-CN/content/organizations/managing-organization-settings/managing
translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
+translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
@@ -862,7 +841,6 @@ translations/zh-CN/content/packages/learn-github-packages/introduction-to-github
translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md,rendering error
translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md,rendering error
translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/zh-CN/content/packages/quickstart.md,rendering error
translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
@@ -873,31 +851,31 @@ translations/zh-CN/content/packages/working-with-a-github-packages-registry/work
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
-translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
+translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
+translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
+translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags
+translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags
+translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags
+translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,rendering error
-translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,rendering error
+translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags
+translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags
+translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,rendering error
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,rendering error
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,rendering error
+translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md,rendering error
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error
@@ -906,29 +884,25 @@ translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,rendering error
+translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags
translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error
translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
+translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
+translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,rendering error
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
+translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags
translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,rendering error
translations/zh-CN/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
translations/zh-CN/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
-translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md,rendering error
+translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags
+translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
+translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags
translations/zh-CN/content/rest/activity/notifications.md,broken liquid tags
-translations/zh-CN/content/rest/apps/oauth-applications.md,rendering error
+translations/zh-CN/content/rest/apps/oauth-applications.md,broken liquid tags
translations/zh-CN/content/rest/codespaces/codespaces.md,broken liquid tags
translations/zh-CN/content/rest/dependabot/index.md,broken liquid tags
translations/zh-CN/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
@@ -954,14 +928,15 @@ translations/zh-CN/content/rest/overview/other-authentication-methods.md,renderi
translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md,rendering error
translations/zh-CN/content/rest/packages.md,broken liquid tags
translations/zh-CN/content/rest/projects/projects.md,broken liquid tags
-translations/zh-CN/content/rest/scim.md,rendering error
-translations/zh-CN/content/rest/teams/team-sync.md,rendering error
+translations/zh-CN/content/rest/scim.md,broken liquid tags
+translations/zh-CN/content/rest/teams/team-sync.md,broken liquid tags
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
-translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
+translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags
-translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,rendering error
-translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,rendering error
-translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md,rendering error
+translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
+translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
+translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
+translations/zh-CN/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
translations/zh-CN/content/support/learning-about-github-support/about-github-support.md,rendering error
translations/zh-CN/data/glossaries/external.yml,broken liquid tags
@@ -983,25 +958,29 @@ translations/zh-CN/data/release-notes/enterprise-server/3-4/7.yml,rendering erro
translations/zh-CN/data/release-notes/enterprise-server/3-4/8.yml,rendering error
translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml,rendering error
+translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
+translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md,rendering error
translations/zh-CN/data/reusables/actions/actions-billing.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/cache-default-size.md,rendering error
+translations/zh-CN/data/reusables/actions/cache-default-size.md,broken liquid tags
translations/zh-CN/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error
translations/zh-CN/data/reusables/actions/changing-the-name-of-a-runner-group.md,rendering error
translations/zh-CN/data/reusables/actions/create-runner-group.md,rendering error
translations/zh-CN/data/reusables/actions/creating-a-runner-group-for-an-organization.md,rendering error
translations/zh-CN/data/reusables/actions/disabling-github-actions.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,rendering error
+translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md,rendering error
-translations/zh-CN/data/reusables/actions/github-connect-resolution.md,rendering error
+translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
+translations/zh-CN/data/reusables/actions/github-connect-resolution.md,broken liquid tags
translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags
+translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md,broken liquid tags
translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md,rendering error
translations/zh-CN/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
translations/zh-CN/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
+translations/zh-CN/data/reusables/actions/reusable-workflows-enterprise-beta.md,rendering error
translations/zh-CN/data/reusables/actions/reusable-workflows.md,rendering error
translations/zh-CN/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
translations/zh-CN/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
@@ -1014,11 +993,11 @@ translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-pages-cus
translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error
translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error
translations/zh-CN/data/reusables/actions/sidebar-secret.md,rendering error
-translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,rendering error
-translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md,rendering error
+translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags
+translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
translations/zh-CN/data/reusables/actions/workflow-dispatch-inputs.md,rendering error
translations/zh-CN/data/reusables/actions/workflow-template-overview.md,rendering error
-translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,rendering error
+translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
translations/zh-CN/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
translations/zh-CN/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
@@ -1026,9 +1005,9 @@ translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protect
translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error
translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
-translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,rendering error
-translations/zh-CN/data/reusables/classroom/about-autograding.md,rendering error
-translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,rendering error
+translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
+translations/zh-CN/data/reusables/classroom/about-autograding.md,broken liquid tags
+translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
translations/zh-CN/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
@@ -1036,7 +1015,7 @@ translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-
translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
translations/zh-CN/data/reusables/code-scanning/licensing-note.md,broken liquid tags
translations/zh-CN/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md,rendering error
+translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
translations/zh-CN/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
translations/zh-CN/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
translations/zh-CN/data/reusables/codespaces/prebuilds-crossreference.md,broken liquid tags
@@ -1049,15 +1028,15 @@ translations/zh-CN/data/reusables/dependabot/dependabot-alerts-filters.md,render
translations/zh-CN/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error
translations/zh-CN/data/reusables/dependabot/sidebar-secret.md,rendering error
translations/zh-CN/data/reusables/dependabot/supported-package-managers.md,rendering error
-translations/zh-CN/data/reusables/desktop/get-an-account.md,rendering error
-translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,rendering error
-translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md,rendering error
-translations/zh-CN/data/reusables/discussions/starting-a-discussion.md,rendering error
+translations/zh-CN/data/reusables/desktop/get-an-account.md,broken liquid tags
+translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
+translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags
+translations/zh-CN/data/reusables/discussions/starting-a-discussion.md,broken liquid tags
translations/zh-CN/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags
-translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md,rendering error
+translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
+translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
@@ -1066,48 +1045,48 @@ translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error
-translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md,rendering error
+translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/repo-creation-policy.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise-accounts/security-tab.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise/apply-configuration.md,rendering error
+translations/zh-CN/data/reusables/enterprise/apply-configuration.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise/rate_limit.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
-translations/zh-CN/data/reusables/enterprise/test-in-staging.md,rendering error
-translations/zh-CN/data/reusables/enterprise_installation/download-package.md,rendering error
+translations/zh-CN/data/reusables/enterprise/test-in-staging.md,broken liquid tags
+translations/zh-CN/data/reusables/enterprise_installation/download-package.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,rendering error
translations/zh-CN/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md,rendering error
-translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,rendering error
-translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md,rendering error
-translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md,rendering error
-translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,rendering error
-translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,rendering error
-translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md,rendering error
+translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags
+translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags
+translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags
+translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags
+translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags
+translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags
+translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,rendering error
+translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
translations/zh-CN/data/reusables/files/choose-commit-email.md,broken liquid tags
translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
translations/zh-CN/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,rendering error
translations/zh-CN/data/reusables/gated-features/secret-scanning.md,rendering error
-translations/zh-CN/data/reusables/getting-started/actions.md,rendering error
-translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md,rendering error
+translations/zh-CN/data/reusables/getting-started/actions.md,broken liquid tags
+translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags
translations/zh-CN/data/reusables/getting-started/configuring-security-features.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/creating-organizations.md,rendering error
-translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md,rendering error
+translations/zh-CN/data/reusables/getting-started/creating-organizations.md,broken liquid tags
+translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags
translations/zh-CN/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md,rendering error
-translations/zh-CN/data/reusables/git/git-push.md,rendering error
+translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
+translations/zh-CN/data/reusables/git/git-push.md,broken liquid tags
translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,rendering error
translations/zh-CN/data/reusables/large_files/storage_assets_location.md,broken liquid tags
-translations/zh-CN/data/reusables/large_files/use_lfs_tip.md,rendering error
+translations/zh-CN/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
translations/zh-CN/data/reusables/notifications/outbound_email_tip.md,broken liquid tags
translations/zh-CN/data/reusables/notifications/shared_state.md,rendering error
translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md,rendering error
translations/zh-CN/data/reusables/organizations/billing_plans.md,rendering error
translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
translations/zh-CN/data/reusables/organizations/member-privileges.md,rendering error
-translations/zh-CN/data/reusables/organizations/navigate-to-org.md,rendering error
+translations/zh-CN/data/reusables/organizations/navigate-to-org.md,broken liquid tags
translations/zh-CN/data/reusables/organizations/repository-defaults.md,rendering error
translations/zh-CN/data/reusables/organizations/security-and-analysis.md,rendering error
translations/zh-CN/data/reusables/organizations/security.md,rendering error
@@ -1115,28 +1094,28 @@ translations/zh-CN/data/reusables/organizations/teams_sidebar.md,rendering error
translations/zh-CN/data/reusables/organizations/verified-domains.md,rendering error
translations/zh-CN/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md,rendering error
-translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,rendering error
+translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/packages-billing.md,rendering error
+translations/zh-CN/data/reusables/package_registry/packages-billing.md,broken liquid tags
translations/zh-CN/data/reusables/package_registry/required-scopes.md,broken liquid tags
translations/zh-CN/data/reusables/pages/build-failure-email-server.md,broken liquid tags
translations/zh-CN/data/reusables/pages/emu-org-only.md,broken liquid tags
translations/zh-CN/data/reusables/pages/sidebar-pages.md,rendering error
translations/zh-CN/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
translations/zh-CN/data/reusables/projects/graphql-ghes.md,rendering error
-translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md,rendering error
-translations/zh-CN/data/reusables/pull_requests/default_merge_option.md,rendering error
-translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md,rendering error
-translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md,rendering error
+translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
+translations/zh-CN/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
+translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
+translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
translations/zh-CN/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
-translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md,rendering error
+translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags
translations/zh-CN/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md,rendering error
translations/zh-CN/data/reusables/repositories/changed-files.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/deploy-keys.md,rendering error
+translations/zh-CN/data/reusables/repositories/deploy-keys.md,broken liquid tags
translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
translations/zh-CN/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error
translations/zh-CN/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/navigate-to-repo.md,rendering error
+translations/zh-CN/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
translations/zh-CN/data/reusables/repositories/repository-branches.md,rendering error
translations/zh-CN/data/reusables/repositories/sidebar-notifications.md,rendering error
translations/zh-CN/data/reusables/repositories/suggest-changes.md,broken liquid tags
@@ -1144,24 +1123,24 @@ translations/zh-CN/data/reusables/repositories/tracks-vulnerabilities.md,broken
translations/zh-CN/data/reusables/repositories/you-can-fork.md,broken liquid tags
translations/zh-CN/data/reusables/rest-api/dotcom-only-guide-note.md,rendering error
translations/zh-CN/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/about-linked-identities.md,rendering error
+translations/zh-CN/data/reusables/saml/about-linked-identities.md,broken liquid tags
translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags
translations/zh-CN/data/reusables/saml/authorized-creds-info.md,broken liquid tags
translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error
-translations/zh-CN/data/reusables/scim/enterprise-account-scim.md,rendering error
-translations/zh-CN/data/reusables/scim/supported-idps.md,rendering error
+translations/zh-CN/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
+translations/zh-CN/data/reusables/scim/supported-idps.md,broken liquid tags
translations/zh-CN/data/reusables/search/syntax_tips.md,broken liquid tags
translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
translations/zh-CN/data/reusables/security-overview/permissions.md,rendering error
-translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md,rendering error
-translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md,rendering error
+translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
+translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
translations/zh-CN/data/reusables/ssh/about-ssh.md,broken liquid tags
translations/zh-CN/data/reusables/ssh/key-type-support.md,rendering error
-translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,rendering error
-translations/zh-CN/data/reusables/support/help_resources.md,rendering error
+translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
+translations/zh-CN/data/reusables/support/help_resources.md,broken liquid tags
translations/zh-CN/data/reusables/support/submit-a-ticket.md,broken liquid tags
translations/zh-CN/data/reusables/user-settings/access_applications.md,rendering error
translations/zh-CN/data/reusables/user-settings/account_settings.md,rendering error
diff --git a/translations/log/msft-de-resets.csv b/translations/log/msft-de-resets.csv
index a9a21a660b..22bfae2f43 100644
--- a/translations/log/msft-de-resets.csv
+++ b/translations/log/msft-de-resets.csv
@@ -416,14 +416,14 @@ translations/de-DE/data/reusables/security-center/beta.md,file deleted because i
translations/de-DE/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
-translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
+translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags
translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
-translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,rendering error
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
-translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
@@ -431,9 +431,9 @@ translations/de-DE/content/account-and-profile/setting-up-and-managing-your-pers
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md,rendering error
-translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,rendering error
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md,rendering error
-translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
@@ -447,10 +447,10 @@ translations/de-DE/content/account-and-profile/setting-up-and-managing-your-pers
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md,rendering error
translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md,broken liquid tags
-translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,rendering error
-translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md,rendering error
-translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,broken liquid tags
+translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
+translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags
+translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags
translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
translations/de-DE/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
@@ -484,14 +484,14 @@ translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-
translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
-translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
+translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
translations/de-DE/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
translations/de-DE/content/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer.md,rendering error
-translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
+translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md,rendering error
translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
-translations/de-DE/content/actions/quickstart.md,rendering error
+translations/de-DE/content/actions/quickstart.md,broken liquid tags
translations/de-DE/content/actions/security-guides/automatic-token-authentication.md,rendering error
translations/de-DE/content/actions/security-guides/encrypted-secrets.md,rendering error
translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
@@ -509,82 +509,79 @@ translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md,rend
translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
-translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,rendering error
+translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md,broken liquid tags
-translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,rendering error
+translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,broken liquid tags
-translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-github-connect/index.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
+translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
+translations/de-DE/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags
translations/de-DE/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
translations/de-DE/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
translations/de-DE/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
translations/de-DE/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
translations/de-DE/content/admin/enterprise-management/caching-repositories/index.md,rendering error
translations/de-DE/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
translations/de-DE/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
-translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,rendering error
-translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
-translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
-translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
-translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
-translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,rendering error
-translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags
translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,rendering error
-translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md,rendering error
+translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,rendering error
translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error
translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
+translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
translations/de-DE/content/admin/identity-and-access-management/index.md,broken liquid tags
-translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,rendering error
+translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error
translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
+translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,rendering error
-translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,rendering error
+translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags
translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise.md,rendering error
translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags
translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags
@@ -595,84 +592,80 @@ translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-ser
translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md,rendering error
translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
-translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error
-translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md,rendering error
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,rendering error
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md,rendering error
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/overview/about-data-residency.md,rendering error
-translations/de-DE/content/admin/overview/about-github-enterprise-server.md,rendering error
+translations/de-DE/content/admin/overview/about-data-residency.md,broken liquid tags
+translations/de-DE/content/admin/overview/about-github-enterprise-server.md,broken liquid tags
translations/de-DE/content/admin/overview/about-github-for-enterprises.md,rendering error
translations/de-DE/content/admin/overview/system-overview.md,rendering error
translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md,rendering error
-translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
-translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,rendering error
-translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
+translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
+translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
translations/de-DE/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags
-translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
+translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
-translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,rendering error
-translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
-translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
-translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,rendering error
-translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
+translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags
+translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,rendering error
-translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,rendering error
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags
translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md,rendering error
-translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
-translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,rendering error
+translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags
translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
-translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,rendering error
-translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
-translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
-translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
+translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags
+translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags
+translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags
translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
translations/de-DE/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error
translations/de-DE/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,rendering error
translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/de-DE/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,rendering error
+translations/de-DE/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags
translations/de-DE/content/authentication/index.md,rendering error
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags
-translations/de-DE/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
-translations/de-DE/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md,rendering error
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md,rendering error
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/de-DE/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,rendering error
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags
translations/de-DE/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
translations/de-DE/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
translations/de-DE/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,rendering error
-translations/de-DE/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,rendering error
+translations/de-DE/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags
translations/de-DE/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error
-translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error
+translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags
translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags
translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md,rendering error
-translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
+translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags
translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
-translations/de-DE/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
-translations/de-DE/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
+translations/de-DE/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
+translations/de-DE/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error
translations/de-DE/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
-translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,rendering error
-translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
translations/de-DE/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
translations/de-DE/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
translations/de-DE/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags
@@ -687,14 +680,14 @@ translations/de-DE/content/billing/managing-billing-for-github-packages/viewing-
translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
translations/de-DE/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,rendering error
translations/de-DE/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
-translations/de-DE/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
+translations/de-DE/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags
translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,broken liquid tags
-translations/de-DE/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,rendering error
-translations/de-DE/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,rendering error
+translations/de-DE/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
+translations/de-DE/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
translations/de-DE/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md,rendering error
translations/de-DE/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,rendering error
-translations/de-DE/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,rendering error
-translations/de-DE/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,rendering error
+translations/de-DE/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
+translations/de-DE/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md,rendering error
translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
@@ -705,12 +698,12 @@ translations/de-DE/content/code-security/code-scanning/automatically-scanning-yo
translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
+translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
-translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
+translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
translations/de-DE/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
@@ -741,10 +734,7 @@ translations/de-DE/content/code-security/secret-scanning/protecting-pushes-with-
translations/de-DE/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
translations/de-DE/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error
translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
-translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error
-translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
translations/de-DE/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
-translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md,rendering error
translations/de-DE/content/code-security/security-overview/about-the-security-overview.md,rendering error
translations/de-DE/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
translations/de-DE/content/code-security/security-overview/index.md,rendering error
@@ -758,37 +748,31 @@ translations/de-DE/content/code-security/supply-chain-security/understanding-you
translations/de-DE/content/codespaces/codespaces-reference/security-in-github-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-for-a-repository.md,rendering error
-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/opening-an-existing-codespace.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-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,broken liquid tags
translations/de-DE/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md,broken liquid tags
-translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error
-translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error
-translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error
-translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
-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/about-wikis.md,broken liquid tags
+translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
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/creating-a-pull-request-template-for-your-repository.md,rendering error
+translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
+translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
translations/de-DE/content/copilot/quickstart.md,broken liquid tags
-translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error
+translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
-translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
+translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
translations/de-DE/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
translations/de-DE/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md,rendering error
translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error
translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app.md,rendering error
translations/de-DE/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error
-translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
+translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags
translations/de-DE/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
translations/de-DE/content/developers/apps/building-oauth-apps/creating-a-custom-badge-for-your-oauth-app.md,rendering error
translations/de-DE/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md,rendering error
translations/de-DE/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
translations/de-DE/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md,rendering error
-translations/de-DE/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error
-translations/de-DE/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
+translations/de-DE/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,broken liquid tags
+translations/de-DE/content/developers/apps/guides/using-the-github-api-in-your-app.md,broken liquid tags
translations/de-DE/content/developers/apps/managing-github-apps/deleting-a-github-app.md,rendering error
translations/de-DE/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md,rendering error
translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error
@@ -798,63 +782,58 @@ translations/de-DE/content/developers/apps/managing-github-apps/transferring-own
translations/de-DE/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md,rendering error
translations/de-DE/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md,rendering error
translations/de-DE/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md,rendering error
-translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
+translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags
translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags
translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md,rendering error
translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md,rendering error
translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md,rendering error
-translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
+translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags
+translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
translations/de-DE/content/developers/overview/about-githubs-apis.md,broken liquid tags
-translations/de-DE/content/developers/overview/managing-deploy-keys.md,rendering error
+translations/de-DE/content/developers/overview/managing-deploy-keys.md,broken liquid tags
translations/de-DE/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
translations/de-DE/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,rendering error
-translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,rendering error
-translations/de-DE/content/discussions/guides/finding-your-discussions.md,rendering error
-translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,rendering error
-translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md,rendering error
+translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
+translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
+translations/de-DE/content/discussions/guides/finding-your-discussions.md,broken liquid tags
+translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,rendering error
translations/de-DE/content/discussions/quickstart.md,rendering error
translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
-translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
+translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
-translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
-translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
+translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
translations/de-DE/content/education/quickstart.md,rendering error
-translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
+translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
+translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags
translations/de-DE/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
translations/de-DE/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
translations/de-DE/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
translations/de-DE/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
translations/de-DE/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md,rendering error
-translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,rendering error
-translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,rendering error
+translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
+translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags
translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags
translations/de-DE/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags
translations/de-DE/content/get-started/learning-about-github/githubs-products.md,rendering error
-translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
+translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags
translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/de-DE/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/de-DE/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
+translations/de-DE/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
+translations/de-DE/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
translations/de-DE/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md,rendering error
translations/de-DE/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md,rendering error
translations/de-DE/content/get-started/quickstart/contributing-to-projects.md,rendering error
-translations/de-DE/content/get-started/quickstart/create-a-repo.md,rendering error
+translations/de-DE/content/get-started/quickstart/create-a-repo.md,broken liquid tags
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/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
+translations/de-DE/content/get-started/using-git/about-git-rebase.md,broken liquid tags
translations/de-DE/content/get-started/using-github/github-mobile.md,rendering error
translations/de-DE/content/get-started/using-github/keyboard-shortcuts.md,rendering error
translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,rendering error
@@ -872,7 +851,7 @@ translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md,renderin
translations/de-DE/content/graphql/guides/introduction-to-graphql.md,broken liquid tags
translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md,rendering error
translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
-translations/de-DE/content/graphql/overview/about-the-graphql-api.md,rendering error
+translations/de-DE/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
translations/de-DE/content/graphql/reference/enums.md,rendering error
translations/de-DE/content/graphql/reference/input-objects.md,rendering error
translations/de-DE/content/graphql/reference/interfaces.md,rendering error
@@ -882,12 +861,11 @@ translations/de-DE/content/graphql/reference/unions.md,rendering error
translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
-translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error
translations/de-DE/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
-translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
+translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md,rendering error
-translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
+translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
+translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
translations/de-DE/content/organizations/keeping-your-organization-secure/index.md,rendering error
translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md,rendering error
translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
@@ -897,7 +875,7 @@ translations/de-DE/content/organizations/keeping-your-organization-secure/managi
translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md,rendering error
translations/de-DE/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md,rendering error
-translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
+translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags
translations/de-DE/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md,rendering error
translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md,rendering error
translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md,rendering error
@@ -922,7 +900,7 @@ translations/de-DE/content/organizations/managing-organization-settings/verifyin
translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md,broken liquid tags
translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md,broken liquid tags
-translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
+translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md,rendering error
translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md,rendering error
@@ -940,7 +918,6 @@ translations/de-DE/content/packages/learn-github-packages/introduction-to-github
translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md,rendering error
translations/de-DE/content/packages/learn-github-packages/viewing-packages.md,rendering error
translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/de-DE/content/packages/quickstart.md,rendering error
translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
@@ -951,7 +928,7 @@ translations/de-DE/content/packages/working-with-a-github-packages-registry/work
translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
-translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
+translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md,rendering error
translations/de-DE/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,rendering error
translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
@@ -962,24 +939,24 @@ translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/crea
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
-translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
-translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
-translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
-translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
-translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags
translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,rendering error
-translations/de-DE/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,rendering error
-translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,rendering error
+translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags
+translations/de-DE/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,rendering error
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,rendering error
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error
-translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,rendering error
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md,rendering error
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error
@@ -988,33 +965,30 @@ translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/de-DE/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,rendering error
-translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,rendering error
+translations/de-DE/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags
translations/de-DE/content/repositories/creating-and-managing-repositories/deleting-a-repository.md,rendering error
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/classifying-your-repository-with-topics.md,rendering error
+translations/de-DE/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,broken liquid tags
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
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,rendering error
translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,rendering error
translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error
-translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags
translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,rendering error
translations/de-DE/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
translations/de-DE/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error
-translations/de-DE/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
-translations/de-DE/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/de-DE/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md,rendering error
+translations/de-DE/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags
+translations/de-DE/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
+translations/de-DE/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags
translations/de-DE/content/rest/activity/notifications.md,broken liquid tags
-translations/de-DE/content/rest/apps/oauth-applications.md,rendering error
+translations/de-DE/content/rest/apps/oauth-applications.md,broken liquid tags
translations/de-DE/content/rest/codespaces/codespaces.md,broken liquid tags
translations/de-DE/content/rest/dependabot/index.md,broken liquid tags
translations/de-DE/content/rest/deployments/deployments.md,rendering error
@@ -1042,17 +1016,18 @@ translations/de-DE/content/rest/overview/permissions-required-for-github-apps.md
translations/de-DE/content/rest/packages.md,broken liquid tags
translations/de-DE/content/rest/projects/projects.md,broken liquid tags
translations/de-DE/content/rest/quickstart.md,broken liquid tags
-translations/de-DE/content/rest/scim.md,rendering error
-translations/de-DE/content/rest/teams/team-sync.md,rendering error
-translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
+translations/de-DE/content/rest/scim.md,broken liquid tags
+translations/de-DE/content/rest/teams/team-sync.md,broken liquid tags
+translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags
translations/de-DE/content/search-github/searching-on-github/searching-for-packages.md,rendering error
-translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
+translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags
translations/de-DE/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md,broken liquid tags
translations/de-DE/content/site-policy/privacy-policies/global-privacy-practices.md,broken liquid tags
translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags
-translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,rendering error
-translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,rendering error
-translations/de-DE/content/support/contacting-github-support/providing-data-to-github-support.md,rendering error
+translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
+translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
+translations/de-DE/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
+translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
translations/de-DE/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
translations/de-DE/content/support/learning-about-github-support/about-github-support.md,rendering error
translations/de-DE/data/glossaries/external.yml,broken liquid tags
@@ -1074,9 +1049,11 @@ translations/de-DE/data/release-notes/enterprise-server/3-4/7.yml,rendering erro
translations/de-DE/data/release-notes/enterprise-server/3-4/8.yml,rendering error
translations/de-DE/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml,rendering error
+translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
translations/de-DE/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
+translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
translations/de-DE/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags
-translations/de-DE/data/reusables/actions/cache-default-size.md,rendering error
+translations/de-DE/data/reusables/actions/cache-default-size.md,broken liquid tags
translations/de-DE/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error
translations/de-DE/data/reusables/actions/changing-the-name-of-a-runner-group.md,rendering error
translations/de-DE/data/reusables/actions/configure-runner-group-access.md,rendering error
@@ -1084,16 +1061,16 @@ translations/de-DE/data/reusables/actions/create-runner-group.md,rendering error
translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-enterprise.md,rendering error
translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-organization.md,rendering error
translations/de-DE/data/reusables/actions/disabling-github-actions.md,broken liquid tags
-translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md,rendering error
+translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
translations/de-DE/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
-translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md,rendering error
-translations/de-DE/data/reusables/actions/github-connect-resolution.md,rendering error
+translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
+translations/de-DE/data/reusables/actions/github-connect-resolution.md,broken liquid tags
translations/de-DE/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
+translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md,broken liquid tags
translations/de-DE/data/reusables/actions/more-resources-for-ghes.md,rendering error
translations/de-DE/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
translations/de-DE/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
-translations/de-DE/data/reusables/actions/reusable-workflows-ghes-beta.md,rendering error
translations/de-DE/data/reusables/actions/reusable-workflows.md,rendering error
translations/de-DE/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
translations/de-DE/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
@@ -1107,11 +1084,11 @@ translations/de-DE/data/reusables/actions/settings-ui/settings-actions-pages-cus
translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error
translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error
translations/de-DE/data/reusables/actions/sidebar-secret.md,rendering error
-translations/de-DE/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,rendering error
-translations/de-DE/data/reusables/actions/workflow-basic-example-and-explanation.md,rendering error
+translations/de-DE/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags
+translations/de-DE/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
translations/de-DE/data/reusables/actions/workflow-dispatch-inputs.md,rendering error
-translations/de-DE/data/reusables/actions/workflow-template-overview.md,rendering error
-translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,rendering error
+translations/de-DE/data/reusables/actions/workflow-template-overview.md,broken liquid tags
+translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
translations/de-DE/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
translations/de-DE/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
@@ -1120,15 +1097,15 @@ translations/de-DE/data/reusables/apps/user-to-server-rate-limits.md,broken liqu
translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error
translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
translations/de-DE/data/reusables/audit_log/retention-periods.md,rendering error
-translations/de-DE/data/reusables/branches/new-repo-default-branch.md,rendering error
-translations/de-DE/data/reusables/classroom/about-autograding.md,rendering error
-translations/de-DE/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,rendering error
+translations/de-DE/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
+translations/de-DE/data/reusables/classroom/about-autograding.md,broken liquid tags
+translations/de-DE/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
translations/de-DE/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
-translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md,rendering error
+translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
translations/de-DE/data/reusables/codespaces/codespaces-disabling-org-billing.md,broken liquid tags
translations/de-DE/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
translations/de-DE/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
@@ -1143,18 +1120,17 @@ translations/de-DE/data/reusables/dependabot/dependabot-alerts-filters.md,render
translations/de-DE/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error
translations/de-DE/data/reusables/dependabot/sidebar-secret.md,rendering error
translations/de-DE/data/reusables/dependabot/supported-package-managers.md,rendering error
-translations/de-DE/data/reusables/desktop/get-an-account.md,rendering error
-translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,rendering error
-translations/de-DE/data/reusables/discussions/navigate-to-repo-or-org.md,rendering error
-translations/de-DE/data/reusables/discussions/starting-a-discussion.md,rendering error
+translations/de-DE/data/reusables/desktop/get-an-account.md,broken liquid tags
+translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
+translations/de-DE/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags
+translations/de-DE/data/reusables/discussions/starting-a-discussion.md,broken liquid tags
translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags
-translations/de-DE/data/reusables/dotcom_billing/view-all-subscriptions.md,rendering error
+translations/de-DE/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md,rendering error
-translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
+translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
-translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md,rendering error
translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags
@@ -1162,26 +1138,26 @@ translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md
translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error
-translations/de-DE/data/reusables/enterprise-accounts/oidc-gei-warning.md,rendering error
+translations/de-DE/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
translations/de-DE/data/reusables/enterprise-accounts/security-tab.md,rendering error
translations/de-DE/data/reusables/enterprise-licensing/verified-domains-license-sync.md,rendering error
translations/de-DE/data/reusables/enterprise/3-5-missing-feature.md,rendering error
-translations/de-DE/data/reusables/enterprise/apply-configuration.md,rendering error
+translations/de-DE/data/reusables/enterprise/apply-configuration.md,broken liquid tags
translations/de-DE/data/reusables/enterprise/rate_limit.md,broken liquid tags
translations/de-DE/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
-translations/de-DE/data/reusables/enterprise/test-in-staging.md,rendering error
-translations/de-DE/data/reusables/enterprise_installation/download-package.md,rendering error
+translations/de-DE/data/reusables/enterprise/test-in-staging.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_installation/download-package.md,broken liquid tags
translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,rendering error
translations/de-DE/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags
-translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md,rendering error
-translations/de-DE/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,rendering error
-translations/de-DE/data/reusables/enterprise_site_admin_settings/sign-in.md,rendering error
-translations/de-DE/data/reusables/enterprise_site_admin_settings/tls-downtime.md,rendering error
-translations/de-DE/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,rendering error
-translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,rendering error
-translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication.md,rendering error
+translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags
translations/de-DE/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
-translations/de-DE/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,rendering error
+translations/de-DE/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
translations/de-DE/data/reusables/files/choose-commit-email.md,broken liquid tags
translations/de-DE/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
translations/de-DE/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
@@ -1190,26 +1166,26 @@ translations/de-DE/data/reusables/gated-features/secret-scanning-partner.md,rend
translations/de-DE/data/reusables/gated-features/secret-scanning.md,rendering error
translations/de-DE/data/reusables/gated-features/security-overview.md,rendering error
translations/de-DE/data/reusables/gcm-core/next-time-you-clone.md,rendering error
-translations/de-DE/data/reusables/getting-started/actions.md,rendering error
-translations/de-DE/data/reusables/getting-started/adding-members-to-organizations.md,rendering error
+translations/de-DE/data/reusables/getting-started/actions.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags
translations/de-DE/data/reusables/getting-started/configuring-security-features.md,broken liquid tags
-translations/de-DE/data/reusables/getting-started/creating-organizations.md,rendering error
-translations/de-DE/data/reusables/getting-started/enforcing-repo-management-policies.md,rendering error
+translations/de-DE/data/reusables/getting-started/creating-organizations.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags
translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
-translations/de-DE/data/reusables/getting-started/managing-enterprise-members.md,rendering error
-translations/de-DE/data/reusables/git/git-push.md,rendering error
-translations/de-DE/data/reusables/git/provide-credentials.md,rendering error
+translations/de-DE/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
+translations/de-DE/data/reusables/git/git-push.md,broken liquid tags
+translations/de-DE/data/reusables/git/provide-credentials.md,broken liquid tags
translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md,rendering error
translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,rendering error
translations/de-DE/data/reusables/large_files/storage_assets_location.md,broken liquid tags
-translations/de-DE/data/reusables/large_files/use_lfs_tip.md,rendering error
+translations/de-DE/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
translations/de-DE/data/reusables/notifications/outbound_email_tip.md,broken liquid tags
translations/de-DE/data/reusables/notifications/shared_state.md,broken liquid tags
translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-options.md,rendering error
translations/de-DE/data/reusables/organizations/billing_plans.md,rendering error
translations/de-DE/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
translations/de-DE/data/reusables/organizations/member-privileges.md,rendering error
-translations/de-DE/data/reusables/organizations/navigate-to-org.md,rendering error
+translations/de-DE/data/reusables/organizations/navigate-to-org.md,broken liquid tags
translations/de-DE/data/reusables/organizations/repository-defaults.md,rendering error
translations/de-DE/data/reusables/organizations/security-and-analysis.md,rendering error
translations/de-DE/data/reusables/organizations/security.md,rendering error
@@ -1222,9 +1198,9 @@ translations/de-DE/data/reusables/package_registry/authenticate-packages.md,brok
translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md,rendering error
translations/de-DE/data/reusables/package_registry/container-registry-ghes-beta.md,rendering error
translations/de-DE/data/reusables/package_registry/container-registry-hostname.md,rendering error
-translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,rendering error
+translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
translations/de-DE/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
-translations/de-DE/data/reusables/package_registry/packages-billing.md,rendering error
+translations/de-DE/data/reusables/package_registry/packages-billing.md,broken liquid tags
translations/de-DE/data/reusables/package_registry/required-scopes.md,broken liquid tags
translations/de-DE/data/reusables/pages/build-failure-email-server.md,broken liquid tags
translations/de-DE/data/reusables/pages/emu-org-only.md,broken liquid tags
@@ -1232,19 +1208,19 @@ translations/de-DE/data/reusables/pages/sidebar-pages.md,rendering error
translations/de-DE/data/reusables/project-management/choose-visibility.md,rendering error
translations/de-DE/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
translations/de-DE/data/reusables/projects/graphql-ghes.md,rendering error
-translations/de-DE/data/reusables/pull_requests/configure_pull_request_merges_intro.md,rendering error
-translations/de-DE/data/reusables/pull_requests/default_merge_option.md,rendering error
-translations/de-DE/data/reusables/pull_requests/pull_request_merges_and_contributions.md,rendering error
-translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md,rendering error
+translations/de-DE/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
translations/de-DE/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
-translations/de-DE/data/reusables/pull_requests/squash_and_merge_summary.md,rendering error
+translations/de-DE/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags
translations/de-DE/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md,rendering error
translations/de-DE/data/reusables/repositories/changed-files.md,broken liquid tags
-translations/de-DE/data/reusables/repositories/deploy-keys.md,rendering error
+translations/de-DE/data/reusables/repositories/deploy-keys.md,broken liquid tags
translations/de-DE/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
translations/de-DE/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error
translations/de-DE/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
-translations/de-DE/data/reusables/repositories/navigate-to-repo.md,rendering error
+translations/de-DE/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
translations/de-DE/data/reusables/repositories/repository-branches.md,rendering error
translations/de-DE/data/reusables/repositories/security-alert-delivery-options.md,rendering error
translations/de-DE/data/reusables/repositories/settings-sidebar-actions-general.md,rendering error
@@ -1254,24 +1230,24 @@ translations/de-DE/data/reusables/repositories/suggest-changes.md,broken liquid
translations/de-DE/data/reusables/repositories/you-can-fork.md,broken liquid tags
translations/de-DE/data/reusables/rest-api/dotcom-only-guide-note.md,rendering error
translations/de-DE/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
-translations/de-DE/data/reusables/saml/about-linked-identities.md,rendering error
+translations/de-DE/data/reusables/saml/about-linked-identities.md,broken liquid tags
translations/de-DE/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags
translations/de-DE/data/reusables/saml/authorized-creds-info.md,broken liquid tags
translations/de-DE/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
translations/de-DE/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
-translations/de-DE/data/reusables/scim/enterprise-account-scim.md,rendering error
-translations/de-DE/data/reusables/scim/supported-idps.md,rendering error
+translations/de-DE/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
+translations/de-DE/data/reusables/scim/supported-idps.md,broken liquid tags
translations/de-DE/data/reusables/search/syntax_tips.md,broken liquid tags
translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
translations/de-DE/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
translations/de-DE/data/reusables/security-overview/permissions.md,rendering error
-translations/de-DE/data/reusables/shortdesc/rate_limits_github_apps.md,rendering error
-translations/de-DE/data/reusables/sponsors/select-sponsorship-billing.md,rendering error
+translations/de-DE/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
+translations/de-DE/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
translations/de-DE/data/reusables/ssh/about-ssh.md,broken liquid tags
translations/de-DE/data/reusables/ssh/key-type-support.md,rendering error
-translations/de-DE/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,rendering error
-translations/de-DE/data/reusables/support/help_resources.md,rendering error
+translations/de-DE/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
+translations/de-DE/data/reusables/support/help_resources.md,broken liquid tags
translations/de-DE/data/reusables/support/submit-a-ticket.md,broken liquid tags
translations/de-DE/data/reusables/user-settings/access_applications.md,rendering error
translations/de-DE/data/reusables/user-settings/account_settings.md,rendering error
diff --git a/translations/log/msft-es-resets.csv b/translations/log/msft-es-resets.csv
index 92968b6a4b..3e094a58dd 100644
--- a/translations/log/msft-es-resets.csv
+++ b/translations/log/msft-es-resets.csv
@@ -413,6 +413,7 @@ translations/es-ES/data/reusables/getting-started/learning-lab.md,file deleted b
translations/es-ES/data/reusables/open-source/open-source-learning-lab.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/pages/pages-builds-with-github-actions-public-beta.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/apps/oauth-applications.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/billing/billing.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/branches/branch-protection.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/checks/runs.md,file deleted because it no longer exists in main
@@ -424,6 +425,7 @@ translations/es-ES/data/reusables/rest-reference/enterprise-admin/billing.md,fil
translations/es-ES/data/reusables/rest-reference/enterprise-admin/management-console.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/gists/comments.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/git/refs.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/gitignore/gitignore.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/interactions/interactions.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/issues/assignees.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/issues/issues.md,file deleted because it no longer exists in main
@@ -443,6 +445,7 @@ translations/es-ES/data/reusables/rest-reference/releases/assets.md,file deleted
translations/es-ES/data/reusables/rest-reference/repos/contents.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/repos/forks.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/repos/lfs.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/teams/team-sync.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/teams/teams.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/users/blocking.md,file deleted because it no longer exists in main
translations/es-ES/data/reusables/rest-reference/users/emails.md,file deleted because it no longer exists in main
@@ -454,20 +457,20 @@ translations/es-ES/data/reusables/security-center/beta.md,file deleted because i
translations/es-ES/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
-translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
+translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags
translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error
@@ -478,9 +481,9 @@ translations/es-ES/content/account-and-profile/setting-up-and-managing-your-pers
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md,rendering error
translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md,broken liquid tags
-translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md,rendering error
-translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
+translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
+translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags
+translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags
translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
@@ -512,14 +515,14 @@ translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-
translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
-translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
+translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
translations/es-ES/content/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
+translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md,rendering error
translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
-translations/es-ES/content/actions/quickstart.md,rendering error
+translations/es-ES/content/actions/quickstart.md,broken liquid tags
translations/es-ES/content/actions/security-guides/automatic-token-authentication.md,rendering error
translations/es-ES/content/actions/security-guides/encrypted-secrets.md,rendering error
translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
@@ -536,80 +539,77 @@ translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md,rend
translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
-translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,rendering error
+translations/es-ES/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
+translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,broken liquid tags
-translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-github-connect/index.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
+translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
+translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags
translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,rendering error
translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
translations/es-ES/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
-translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,rendering error
-translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
-translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
-translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
-translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
-translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,rendering error
-translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
+translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags
translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,rendering error
-translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md,rendering error
+translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,rendering error
translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
+translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/identity-and-access-management/index.md,broken liquid tags
-translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,rendering error
+translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error
translations/es-ES/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
+translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags
+translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags
+translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
+translations/es-ES/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
+translations/es-ES/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,rendering error
-translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,rendering error
+translations/es-ES/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
+translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags
translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags
translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags
translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags
@@ -618,73 +618,71 @@ translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-ser
translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error
translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
-translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error
-translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error
+translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags
+translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags
translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,rendering error
+translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/overview/about-data-residency.md,rendering error
-translations/es-ES/content/admin/overview/about-github-enterprise-server.md,rendering error
+translations/es-ES/content/admin/overview/about-data-residency.md,broken liquid tags
+translations/es-ES/content/admin/overview/about-github-enterprise-server.md,broken liquid tags
translations/es-ES/content/admin/overview/about-github-for-enterprises.md,rendering error
translations/es-ES/content/admin/overview/system-overview.md,rendering error
-translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
-translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,rendering error
-translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
+translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
+translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
translations/es-ES/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags
-translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
+translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
-translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,rendering error
-translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,rendering error
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
+translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags
+translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,rendering error
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,rendering error
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags
translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,rendering error
+translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
+translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags
translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
-translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,rendering error
-translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
-translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
-translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
+translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags
+translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
+translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags
+translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags
translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error
translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,rendering error
translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/es-ES/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,rendering error
+translations/es-ES/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
+translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags
+translations/es-ES/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags
+translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,rendering error
+translations/es-ES/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags
translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,rendering error
-translations/es-ES/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,rendering error
+translations/es-ES/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags
translations/es-ES/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error
translations/es-ES/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error
+translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags
translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags
translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
+translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags
translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
-translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,rendering error
-translations/es-ES/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
-translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
+translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,broken liquid tags
+translations/es-ES/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
+translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
translations/es-ES/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
-translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
translations/es-ES/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
@@ -693,13 +691,13 @@ translations/es-ES/content/billing/managing-billing-for-github-packages/about-bi
translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
translations/es-ES/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,rendering error
translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
-translations/es-ES/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
+translations/es-ES/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags
translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,broken liquid tags
-translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,rendering error
-translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,rendering error
+translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
+translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
translations/es-ES/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,rendering error
-translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,rendering error
-translations/es-ES/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,rendering error
+translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
+translations/es-ES/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
translations/es-ES/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
@@ -709,12 +707,12 @@ translations/es-ES/content/code-security/code-scanning/automatically-scanning-yo
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
-translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
+translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
@@ -744,10 +742,7 @@ translations/es-ES/content/code-security/secret-scanning/pushing-a-branch-blocke
translations/es-ES/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error
translations/es-ES/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities.md,rendering error
-translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error
-translations/es-ES/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
translations/es-ES/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
-translations/es-ES/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md,rendering error
translations/es-ES/content/code-security/security-overview/about-the-security-overview.md,rendering error
translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md,rendering error
@@ -757,55 +752,46 @@ translations/es-ES/content/code-security/supply-chain-security/understanding-you
translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
translations/es-ES/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
-translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error
-translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags
translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,broken liquid tags
-translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error
-translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error
-translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error
-translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error
+translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,broken liquid tags
translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
-translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
+translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md,rendering error
-translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
-translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
+translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
+translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
translations/es-ES/content/copilot/quickstart.md,broken liquid tags
-translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error
+translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
-translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
-translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
+translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
+translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags
translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
-translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
-translations/es-ES/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error
-translations/es-ES/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
-translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
+translations/es-ES/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,broken liquid tags
+translations/es-ES/content/developers/apps/guides/using-the-github-api-in-your-app.md,broken liquid tags
+translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags
translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags
-translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
+translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags
+translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
translations/es-ES/content/developers/overview/about-githubs-apis.md,broken liquid tags
-translations/es-ES/content/developers/overview/managing-deploy-keys.md,rendering error
+translations/es-ES/content/developers/overview/managing-deploy-keys.md,broken liquid tags
translations/es-ES/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,rendering error
-translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,rendering error
-translations/es-ES/content/discussions/guides/finding-your-discussions.md,rendering error
-translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,rendering error
-translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md,rendering error
+translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
+translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
+translations/es-ES/content/discussions/guides/finding-your-discussions.md,broken liquid tags
+translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,rendering error
translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
-translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
+translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
-translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
+translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
-translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
+translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
+translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags
translations/es-ES/content/get-started/exploring-projects-on-github/following-organizations.md,broken liquid tags
translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
@@ -813,26 +799,24 @@ translations/es-ES/content/get-started/getting-started-with-git/caching-your-git
translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
translations/es-ES/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md,rendering error
-translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,rendering error
-translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,rendering error
+translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
+translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags
translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags
translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags
translations/es-ES/content/get-started/learning-about-github/githubs-products.md,rendering error
-translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
+translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags
translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
+translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
+translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
translations/es-ES/content/get-started/quickstart/be-social.md,broken liquid tags
translations/es-ES/content/get-started/quickstart/contributing-to-projects.md,rendering error
-translations/es-ES/content/get-started/quickstart/create-a-repo.md,rendering error
+translations/es-ES/content/get-started/quickstart/create-a-repo.md,broken liquid tags
translations/es-ES/content/get-started/quickstart/fork-a-repo.md,rendering error
translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
-translations/es-ES/content/get-started/using-git/about-git-rebase.md,rendering error
+translations/es-ES/content/get-started/using-git/about-git-rebase.md,broken liquid tags
translations/es-ES/content/get-started/using-github/github-mobile.md,rendering error
translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,rendering error
translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
@@ -846,7 +830,7 @@ translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md,renderin
translations/es-ES/content/graphql/guides/introduction-to-graphql.md,broken liquid tags
translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md,rendering error
translations/es-ES/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
-translations/es-ES/content/graphql/overview/about-the-graphql-api.md,rendering error
+translations/es-ES/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
translations/es-ES/content/graphql/reference/enums.md,rendering error
translations/es-ES/content/graphql/reference/input-objects.md,rendering error
translations/es-ES/content/graphql/reference/interfaces.md,rendering error
@@ -856,17 +840,16 @@ translations/es-ES/content/graphql/reference/unions.md,rendering error
translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
-translations/es-ES/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error
translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags
-translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
-translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
+translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
+translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
+translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md,rendering error
translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
-translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
+translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags
translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error
translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error
@@ -877,7 +860,7 @@ translations/es-ES/content/organizations/managing-organization-settings/managing
translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
+translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
@@ -890,7 +873,6 @@ translations/es-ES/content/packages/learn-github-packages/introduction-to-github
translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md,rendering error
translations/es-ES/content/packages/learn-github-packages/viewing-packages.md,rendering error
translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/es-ES/content/packages/quickstart.md,rendering error
translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
@@ -901,31 +883,31 @@ translations/es-ES/content/packages/working-with-a-github-packages-registry/work
translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
-translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
+translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
translations/es-ES/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
+translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
+translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags
+translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags
+translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags
+translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags
translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,rendering error
-translations/es-ES/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,rendering error
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,rendering error
+translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags
+translations/es-ES/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags
+translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,rendering error
+translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error
@@ -934,28 +916,25 @@ translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/es-ES/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,rendering error
-translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,rendering error
+translations/es-ES/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags
translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error
translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
-translations/es-ES/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
+translations/es-ES/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
+translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,rendering error
translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
+translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags
translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,rendering error
translations/es-ES/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
-translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
-translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md,rendering error
+translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags
+translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
+translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags
translations/es-ES/content/rest/activity/notifications.md,broken liquid tags
-translations/es-ES/content/rest/apps/oauth-applications.md,rendering error
+translations/es-ES/content/rest/apps/oauth-applications.md,broken liquid tags
translations/es-ES/content/rest/codespaces/codespaces.md,broken liquid tags
translations/es-ES/content/rest/dependabot/index.md,broken liquid tags
translations/es-ES/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
@@ -982,14 +961,15 @@ translations/es-ES/content/rest/overview/permissions-required-for-github-apps.md
translations/es-ES/content/rest/packages.md,broken liquid tags
translations/es-ES/content/rest/projects/projects.md,broken liquid tags
translations/es-ES/content/rest/quickstart.md,broken liquid tags
-translations/es-ES/content/rest/scim.md,rendering error
-translations/es-ES/content/rest/teams/team-sync.md,rendering error
-translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
-translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
+translations/es-ES/content/rest/scim.md,broken liquid tags
+translations/es-ES/content/rest/teams/team-sync.md,broken liquid tags
+translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags
+translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags
translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags
-translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,rendering error
-translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,rendering error
-translations/es-ES/content/support/contacting-github-support/providing-data-to-github-support.md,rendering error
+translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
+translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
+translations/es-ES/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
+translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
translations/es-ES/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
translations/es-ES/content/support/learning-about-github-support/about-github-support.md,rendering error
translations/es-ES/data/glossaries/external.yml,broken liquid tags
@@ -1011,21 +991,24 @@ translations/es-ES/data/release-notes/enterprise-server/3-4/7.yml,rendering erro
translations/es-ES/data/release-notes/enterprise-server/3-4/8.yml,rendering error
translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
translations/es-ES/data/release-notes/enterprise-server/3-5/4.yml,rendering error
+translations/es-ES/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
translations/es-ES/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
+translations/es-ES/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
translations/es-ES/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags
translations/es-ES/data/reusables/actions/actions-do-not-trigger-workflows.md,broken liquid tags
-translations/es-ES/data/reusables/actions/cache-default-size.md,rendering error
+translations/es-ES/data/reusables/actions/cache-default-size.md,broken liquid tags
translations/es-ES/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error
translations/es-ES/data/reusables/actions/changing-the-name-of-a-runner-group.md,rendering error
translations/es-ES/data/reusables/actions/create-runner-group.md,rendering error
translations/es-ES/data/reusables/actions/creating-a-runner-group-for-an-organization.md,rendering error
translations/es-ES/data/reusables/actions/disabling-github-actions.md,broken liquid tags
-translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md,rendering error
+translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
-translations/es-ES/data/reusables/actions/enterprise-postinstall-nextsteps.md,rendering error
-translations/es-ES/data/reusables/actions/github-connect-resolution.md,rendering error
+translations/es-ES/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
+translations/es-ES/data/reusables/actions/github-connect-resolution.md,broken liquid tags
translations/es-ES/data/reusables/actions/hosted-runner-security.md,broken liquid tags
translations/es-ES/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
+translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md,broken liquid tags
translations/es-ES/data/reusables/actions/more-resources-for-ghes.md,rendering error
translations/es-ES/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
translations/es-ES/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
@@ -1042,11 +1025,11 @@ translations/es-ES/data/reusables/actions/settings-ui/settings-actions-pages-cus
translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error
translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error
translations/es-ES/data/reusables/actions/sidebar-secret.md,rendering error
-translations/es-ES/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,rendering error
-translations/es-ES/data/reusables/actions/workflow-basic-example-and-explanation.md,rendering error
+translations/es-ES/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags
+translations/es-ES/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
translations/es-ES/data/reusables/actions/workflow-dispatch-inputs.md,rendering error
-translations/es-ES/data/reusables/actions/workflow-template-overview.md,rendering error
-translations/es-ES/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,rendering error
+translations/es-ES/data/reusables/actions/workflow-template-overview.md,broken liquid tags
+translations/es-ES/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
@@ -1054,15 +1037,15 @@ translations/es-ES/data/reusables/advanced-security/secret-scanning-push-protect
translations/es-ES/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error
translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
-translations/es-ES/data/reusables/branches/new-repo-default-branch.md,rendering error
-translations/es-ES/data/reusables/classroom/about-autograding.md,rendering error
-translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,rendering error
+translations/es-ES/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
+translations/es-ES/data/reusables/classroom/about-autograding.md,broken liquid tags
+translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
translations/es-ES/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
translations/es-ES/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
-translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md,rendering error
+translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
translations/es-ES/data/reusables/codespaces/codespaces-disabling-org-billing.md,broken liquid tags
translations/es-ES/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
translations/es-ES/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
@@ -1076,17 +1059,16 @@ translations/es-ES/data/reusables/dependabot/dependabot-alerts-filters.md,render
translations/es-ES/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error
translations/es-ES/data/reusables/dependabot/sidebar-secret.md,rendering error
translations/es-ES/data/reusables/dependabot/supported-package-managers.md,rendering error
-translations/es-ES/data/reusables/desktop/get-an-account.md,rendering error
-translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,rendering error
-translations/es-ES/data/reusables/discussions/navigate-to-repo-or-org.md,rendering error
-translations/es-ES/data/reusables/discussions/starting-a-discussion.md,rendering error
+translations/es-ES/data/reusables/desktop/get-an-account.md,broken liquid tags
+translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
+translations/es-ES/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags
+translations/es-ES/data/reusables/discussions/starting-a-discussion.md,broken liquid tags
translations/es-ES/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags
-translations/es-ES/data/reusables/dotcom_billing/view-all-subscriptions.md,rendering error
+translations/es-ES/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags
translations/es-ES/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags
translations/es-ES/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
-translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
+translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags
translations/es-ES/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
-translations/es-ES/data/reusables/enterprise-accounts/emu-forks.md,rendering error
translations/es-ES/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
translations/es-ES/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
translations/es-ES/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags
@@ -1094,49 +1076,49 @@ translations/es-ES/data/reusables/enterprise-accounts/emu-permission-interact.md
translations/es-ES/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags
translations/es-ES/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags
translations/es-ES/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error
-translations/es-ES/data/reusables/enterprise-accounts/oidc-gei-warning.md,rendering error
+translations/es-ES/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
translations/es-ES/data/reusables/enterprise-accounts/security-tab.md,rendering error
-translations/es-ES/data/reusables/enterprise/apply-configuration.md,rendering error
+translations/es-ES/data/reusables/enterprise/apply-configuration.md,broken liquid tags
translations/es-ES/data/reusables/enterprise/rate_limit.md,broken liquid tags
translations/es-ES/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
-translations/es-ES/data/reusables/enterprise/test-in-staging.md,rendering error
-translations/es-ES/data/reusables/enterprise_installation/download-package.md,rendering error
+translations/es-ES/data/reusables/enterprise/test-in-staging.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_installation/download-package.md,broken liquid tags
translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,rendering error
translations/es-ES/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags
-translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md,rendering error
-translations/es-ES/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,rendering error
-translations/es-ES/data/reusables/enterprise_site_admin_settings/sign-in.md,rendering error
-translations/es-ES/data/reusables/enterprise_site_admin_settings/tls-downtime.md,rendering error
-translations/es-ES/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,rendering error
-translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,rendering error
-translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md,rendering error
+translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags
+translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags
translations/es-ES/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
-translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,rendering error
+translations/es-ES/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
translations/es-ES/data/reusables/files/choose-commit-email.md,broken liquid tags
translations/es-ES/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
translations/es-ES/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
translations/es-ES/data/reusables/gated-features/secret-scanning-partner.md,rendering error
translations/es-ES/data/reusables/gated-features/secret-scanning.md,rendering error
-translations/es-ES/data/reusables/getting-started/actions.md,rendering error
-translations/es-ES/data/reusables/getting-started/adding-members-to-organizations.md,rendering error
+translations/es-ES/data/reusables/getting-started/actions.md,broken liquid tags
+translations/es-ES/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags
translations/es-ES/data/reusables/getting-started/configuring-security-features.md,broken liquid tags
-translations/es-ES/data/reusables/getting-started/creating-organizations.md,rendering error
-translations/es-ES/data/reusables/getting-started/enforcing-repo-management-policies.md,rendering error
+translations/es-ES/data/reusables/getting-started/creating-organizations.md,broken liquid tags
+translations/es-ES/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags
translations/es-ES/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
-translations/es-ES/data/reusables/getting-started/managing-enterprise-members.md,rendering error
-translations/es-ES/data/reusables/git/git-push.md,rendering error
-translations/es-ES/data/reusables/git/provide-credentials.md,rendering error
+translations/es-ES/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
+translations/es-ES/data/reusables/git/git-push.md,broken liquid tags
+translations/es-ES/data/reusables/git/provide-credentials.md,broken liquid tags
translations/es-ES/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md,rendering error
translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,rendering error
translations/es-ES/data/reusables/large_files/storage_assets_location.md,broken liquid tags
-translations/es-ES/data/reusables/large_files/use_lfs_tip.md,rendering error
+translations/es-ES/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
translations/es-ES/data/reusables/notifications/outbound_email_tip.md,broken liquid tags
translations/es-ES/data/reusables/notifications/shared_state.md,broken liquid tags
translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md,rendering error
translations/es-ES/data/reusables/organizations/billing_plans.md,rendering error
translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
translations/es-ES/data/reusables/organizations/member-privileges.md,rendering error
-translations/es-ES/data/reusables/organizations/navigate-to-org.md,rendering error
+translations/es-ES/data/reusables/organizations/navigate-to-org.md,broken liquid tags
translations/es-ES/data/reusables/organizations/repository-defaults.md,rendering error
translations/es-ES/data/reusables/organizations/security-and-analysis.md,rendering error
translations/es-ES/data/reusables/organizations/security.md,rendering error
@@ -1144,9 +1126,9 @@ translations/es-ES/data/reusables/organizations/teams_sidebar.md,rendering error
translations/es-ES/data/reusables/organizations/verified-domains.md,rendering error
translations/es-ES/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md,rendering error
-translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,rendering error
+translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
translations/es-ES/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
-translations/es-ES/data/reusables/package_registry/packages-billing.md,rendering error
+translations/es-ES/data/reusables/package_registry/packages-billing.md,broken liquid tags
translations/es-ES/data/reusables/package_registry/required-scopes.md,broken liquid tags
translations/es-ES/data/reusables/pages/build-failure-email-server.md,broken liquid tags
translations/es-ES/data/reusables/pages/emu-org-only.md,broken liquid tags
@@ -1154,43 +1136,43 @@ translations/es-ES/data/reusables/pages/sidebar-pages.md,rendering error
translations/es-ES/data/reusables/policies/abuse.md,rendering error
translations/es-ES/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
translations/es-ES/data/reusables/projects/graphql-ghes.md,rendering error
-translations/es-ES/data/reusables/pull_requests/configure_pull_request_merges_intro.md,rendering error
-translations/es-ES/data/reusables/pull_requests/default_merge_option.md,rendering error
-translations/es-ES/data/reusables/pull_requests/pull_request_merges_and_contributions.md,rendering error
-translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md,rendering error
+translations/es-ES/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
+translations/es-ES/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
+translations/es-ES/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
+translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
translations/es-ES/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
-translations/es-ES/data/reusables/pull_requests/squash_and_merge_summary.md,rendering error
+translations/es-ES/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags
translations/es-ES/data/reusables/repositories/changed-files.md,broken liquid tags
-translations/es-ES/data/reusables/repositories/deploy-keys.md,rendering error
+translations/es-ES/data/reusables/repositories/deploy-keys.md,broken liquid tags
translations/es-ES/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
translations/es-ES/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error
translations/es-ES/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
-translations/es-ES/data/reusables/repositories/navigate-to-repo.md,rendering error
+translations/es-ES/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
translations/es-ES/data/reusables/repositories/repository-branches.md,rendering error
translations/es-ES/data/reusables/repositories/sidebar-notifications.md,rendering error
translations/es-ES/data/reusables/repositories/suggest-changes.md,broken liquid tags
translations/es-ES/data/reusables/repositories/you-can-fork.md,broken liquid tags
translations/es-ES/data/reusables/rest-api/dotcom-only-guide-note.md,rendering error
translations/es-ES/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
-translations/es-ES/data/reusables/saml/about-linked-identities.md,rendering error
+translations/es-ES/data/reusables/saml/about-linked-identities.md,broken liquid tags
translations/es-ES/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags
translations/es-ES/data/reusables/saml/authorized-creds-info.md,broken liquid tags
translations/es-ES/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
translations/es-ES/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
-translations/es-ES/data/reusables/scim/enterprise-account-scim.md,rendering error
-translations/es-ES/data/reusables/scim/supported-idps.md,rendering error
+translations/es-ES/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
+translations/es-ES/data/reusables/scim/supported-idps.md,broken liquid tags
translations/es-ES/data/reusables/search/syntax_tips.md,broken liquid tags
translations/es-ES/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
translations/es-ES/data/reusables/security-overview/permissions.md,rendering error
-translations/es-ES/data/reusables/shortdesc/rate_limits_github_apps.md,rendering error
+translations/es-ES/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
translations/es-ES/data/reusables/sponsors/feedback.md,broken liquid tags
-translations/es-ES/data/reusables/sponsors/select-sponsorship-billing.md,rendering error
+translations/es-ES/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
translations/es-ES/data/reusables/ssh/about-ssh.md,broken liquid tags
translations/es-ES/data/reusables/ssh/key-type-support.md,rendering error
-translations/es-ES/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,rendering error
-translations/es-ES/data/reusables/support/help_resources.md,rendering error
+translations/es-ES/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
+translations/es-ES/data/reusables/support/help_resources.md,broken liquid tags
translations/es-ES/data/reusables/support/submit-a-ticket.md,broken liquid tags
translations/es-ES/data/reusables/user-settings/access_applications.md,rendering error
translations/es-ES/data/reusables/user-settings/account_settings.md,rendering error
diff --git a/translations/log/msft-fr-resets.csv b/translations/log/msft-fr-resets.csv
index b3b4872d64..a55a2361e9 100644
--- a/translations/log/msft-fr-resets.csv
+++ b/translations/log/msft-fr-resets.csv
@@ -408,14 +408,14 @@ translations/fr-FR/data/reusables/security-center/beta.md,file deleted because i
translations/fr-FR/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
translations/fr-FR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
translations/fr-FR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
-translations/fr-FR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
+translations/fr-FR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags
translations/fr-FR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
translations/fr-FR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
-translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,rendering error
+translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
-translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
+translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
@@ -423,9 +423,9 @@ translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-pers
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md,rendering error
-translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,rendering error
+translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md,rendering error
-translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
+translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
@@ -439,10 +439,10 @@ translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-pers
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md,rendering error
translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md,broken liquid tags
-translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,rendering error
-translations/fr-FR/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/fr-FR/content/actions/creating-actions/creating-a-composite-action.md,rendering error
-translations/fr-FR/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
+translations/fr-FR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,broken liquid tags
+translations/fr-FR/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
+translations/fr-FR/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags
+translations/fr-FR/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags
translations/fr-FR/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
translations/fr-FR/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
translations/fr-FR/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
@@ -476,14 +476,14 @@ translations/fr-FR/content/actions/learn-github-actions/finding-and-customizing-
translations/fr-FR/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
translations/fr-FR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
translations/fr-FR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
-translations/fr-FR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/fr-FR/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
+translations/fr-FR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/fr-FR/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
translations/fr-FR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
translations/fr-FR/content/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer.md,rendering error
-translations/fr-FR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
+translations/fr-FR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
translations/fr-FR/content/actions/publishing-packages/publishing-docker-images.md,rendering error
translations/fr-FR/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
-translations/fr-FR/content/actions/quickstart.md,rendering error
+translations/fr-FR/content/actions/quickstart.md,broken liquid tags
translations/fr-FR/content/actions/security-guides/automatic-token-authentication.md,rendering error
translations/fr-FR/content/actions/security-guides/encrypted-secrets.md,rendering error
translations/fr-FR/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
@@ -501,83 +501,78 @@ translations/fr-FR/content/actions/using-workflows/triggering-a-workflow.md,rend
translations/fr-FR/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
translations/fr-FR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
translations/fr-FR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
-translations/fr-FR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,rendering error
+translations/fr-FR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
translations/fr-FR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md,broken liquid tags
-translations/fr-FR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,rendering error
+translations/fr-FR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md,broken liquid tags
+translations/fr-FR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,broken liquid tags
-translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-github-connect/index.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
+translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
translations/fr-FR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
+translations/fr-FR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags
translations/fr-FR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/fr-FR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/fr-FR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
translations/fr-FR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
translations/fr-FR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
translations/fr-FR/content/admin/enterprise-management/caching-repositories/index.md,rendering error
translations/fr-FR/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
translations/fr-FR/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
-translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,rendering error
-translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
-translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
-translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
-translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
-translations/fr-FR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,rendering error
-translations/fr-FR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/fr-FR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
+translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
+translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
+translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags
+translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags
+translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags
+translations/fr-FR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags
+translations/fr-FR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags
+translations/fr-FR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/fr-FR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags
translations/fr-FR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
translations/fr-FR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,rendering error
-translations/fr-FR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,rendering error
-translations/fr-FR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md,rendering error
+translations/fr-FR/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
+translations/fr-FR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,broken liquid tags
translations/fr-FR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,rendering error
translations/fr-FR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
translations/fr-FR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
translations/fr-FR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error
translations/fr-FR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
+translations/fr-FR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
translations/fr-FR/content/admin/identity-and-access-management/index.md,broken liquid tags
-translations/fr-FR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,rendering error
+translations/fr-FR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
translations/fr-FR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
translations/fr-FR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error
translations/fr-FR/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,rendering error
-translations/fr-FR/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,rendering error
-translations/fr-FR/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,rendering error
-translations/fr-FR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
-translations/fr-FR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
-translations/fr-FR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
-translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
-translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
+translations/fr-FR/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags
+translations/fr-FR/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags
+translations/fr-FR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
+translations/fr-FR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
+translations/fr-FR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
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/enabling-encrypted-assertions.md,rendering error
+translations/fr-FR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
+translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags
translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise.md,rendering error
translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags
translations/fr-FR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags
@@ -588,82 +583,80 @@ translations/fr-FR/content/admin/installation/setting-up-a-github-enterprise-ser
translations/fr-FR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md,rendering error
translations/fr-FR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
translations/fr-FR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
-translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error
-translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error
+translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags
+translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags
translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md,rendering error
translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,rendering error
+translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md,rendering error
translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/fr-FR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/overview/about-data-residency.md,rendering error
-translations/fr-FR/content/admin/overview/about-github-enterprise-server.md,rendering error
+translations/fr-FR/content/admin/overview/about-data-residency.md,broken liquid tags
+translations/fr-FR/content/admin/overview/about-github-enterprise-server.md,broken liquid tags
translations/fr-FR/content/admin/overview/about-github-for-enterprises.md,rendering error
translations/fr-FR/content/admin/overview/system-overview.md,rendering error
translations/fr-FR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
-translations/fr-FR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,rendering error
-translations/fr-FR/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
+translations/fr-FR/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
+translations/fr-FR/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
translations/fr-FR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
translations/fr-FR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags
-translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
+translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
translations/fr-FR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
-translations/fr-FR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,rendering error
-translations/fr-FR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
-translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
-translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,rendering error
-translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
+translations/fr-FR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags
+translations/fr-FR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
+translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags
+translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags
+translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,rendering error
-translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,rendering error
+translations/fr-FR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags
translations/fr-FR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
translations/fr-FR/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md,rendering error
-translations/fr-FR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
-translations/fr-FR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,rendering error
+translations/fr-FR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
+translations/fr-FR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags
translations/fr-FR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,rendering error
-translations/fr-FR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
-translations/fr-FR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
-translations/fr-FR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
+translations/fr-FR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags
+translations/fr-FR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
+translations/fr-FR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags
+translations/fr-FR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags
translations/fr-FR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
translations/fr-FR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
translations/fr-FR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error
translations/fr-FR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,rendering error
translations/fr-FR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/fr-FR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,rendering error
+translations/fr-FR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags
translations/fr-FR/content/authentication/index.md,rendering error
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
-translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
+translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags
+translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags
+translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md,rendering error
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md,rendering error
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,rendering error
+translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags
translations/fr-FR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
translations/fr-FR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
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/associating-an-email-with-your-gpg-key.md,broken liquid tags
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/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/about-two-factor-authentication.md,broken liquid tags
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
translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md,rendering error
-translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
+translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags
translations/fr-FR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
-translations/fr-FR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
-translations/fr-FR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
+translations/fr-FR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
+translations/fr-FR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
translations/fr-FR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error
translations/fr-FR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
-translations/fr-FR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
translations/fr-FR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
translations/fr-FR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
translations/fr-FR/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags
@@ -678,14 +671,14 @@ translations/fr-FR/content/billing/managing-billing-for-github-packages/viewing-
translations/fr-FR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
translations/fr-FR/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,rendering error
translations/fr-FR/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
-translations/fr-FR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
+translations/fr-FR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags
translations/fr-FR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,broken liquid tags
-translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,rendering error
-translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,rendering error
+translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
+translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md,rendering error
translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,rendering error
-translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,rendering error
-translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,rendering error
+translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
+translations/fr-FR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
translations/fr-FR/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md,rendering error
translations/fr-FR/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
translations/fr-FR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
@@ -696,13 +689,13 @@ translations/fr-FR/content/code-security/code-scanning/automatically-scanning-yo
translations/fr-FR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
translations/fr-FR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
translations/fr-FR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/fr-FR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
+translations/fr-FR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
translations/fr-FR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
translations/fr-FR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
translations/fr-FR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
translations/fr-FR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
-translations/fr-FR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
-translations/fr-FR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,rendering error
+translations/fr-FR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
+translations/fr-FR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,broken liquid tags
translations/fr-FR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
translations/fr-FR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
translations/fr-FR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
@@ -733,10 +726,7 @@ translations/fr-FR/content/code-security/secret-scanning/protecting-pushes-with-
translations/fr-FR/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
translations/fr-FR/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error
translations/fr-FR/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
-translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error
-translations/fr-FR/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
translations/fr-FR/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
-translations/fr-FR/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md,rendering error
translations/fr-FR/content/code-security/security-overview/about-the-security-overview.md,rendering error
translations/fr-FR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
translations/fr-FR/content/code-security/security-overview/index.md,rendering error
@@ -750,40 +740,35 @@ translations/fr-FR/content/code-security/supply-chain-security/understanding-you
translations/fr-FR/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
translations/fr-FR/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags
translations/fr-FR/content/codespaces/customizing-your-codespace/renaming-a-codespace.md,broken liquid tags
-translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error
-translations/fr-FR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error
translations/fr-FR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,broken liquid tags
translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags
translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,broken liquid tags
-translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error
+translations/fr-FR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,broken liquid tags
translations/fr-FR/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md,broken liquid tags
-translations/fr-FR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error
-translations/fr-FR/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error
translations/fr-FR/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md,broken liquid tags
-translations/fr-FR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error
-translations/fr-FR/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
-translations/fr-FR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
+translations/fr-FR/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
+translations/fr-FR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
translations/fr-FR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
-translations/fr-FR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
-translations/fr-FR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
+translations/fr-FR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
+translations/fr-FR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
translations/fr-FR/content/copilot/quickstart.md,broken liquid tags
-translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error
+translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
translations/fr-FR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
translations/fr-FR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
-translations/fr-FR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
+translations/fr-FR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
translations/fr-FR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
translations/fr-FR/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md,rendering error
translations/fr-FR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error
translations/fr-FR/content/developers/apps/building-github-apps/creating-a-github-app.md,rendering error
translations/fr-FR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error
-translations/fr-FR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
+translations/fr-FR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags
translations/fr-FR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
translations/fr-FR/content/developers/apps/building-oauth-apps/creating-a-custom-badge-for-your-oauth-app.md,rendering error
translations/fr-FR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md,rendering error
translations/fr-FR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
translations/fr-FR/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md,rendering error
-translations/fr-FR/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error
-translations/fr-FR/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
+translations/fr-FR/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,broken liquid tags
+translations/fr-FR/content/developers/apps/guides/using-the-github-api-in-your-app.md,broken liquid tags
translations/fr-FR/content/developers/apps/managing-github-apps/deleting-a-github-app.md,rendering error
translations/fr-FR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md,rendering error
translations/fr-FR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error
@@ -793,63 +778,58 @@ translations/fr-FR/content/developers/apps/managing-github-apps/transferring-own
translations/fr-FR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md,rendering error
translations/fr-FR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md,rendering error
translations/fr-FR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md,rendering error
-translations/fr-FR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
+translations/fr-FR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags
translations/fr-FR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags
translations/fr-FR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md,rendering error
translations/fr-FR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md,rendering error
translations/fr-FR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md,rendering error
-translations/fr-FR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/fr-FR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
+translations/fr-FR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags
+translations/fr-FR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
translations/fr-FR/content/developers/overview/about-githubs-apis.md,broken liquid tags
-translations/fr-FR/content/developers/overview/managing-deploy-keys.md,rendering error
+translations/fr-FR/content/developers/overview/managing-deploy-keys.md,broken liquid tags
translations/fr-FR/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
translations/fr-FR/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
translations/fr-FR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/fr-FR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,rendering error
-translations/fr-FR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,rendering error
-translations/fr-FR/content/discussions/guides/finding-your-discussions.md,rendering error
-translations/fr-FR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,rendering error
-translations/fr-FR/content/discussions/managing-discussions-for-your-community/managing-discussions.md,rendering error
+translations/fr-FR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
+translations/fr-FR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
+translations/fr-FR/content/discussions/guides/finding-your-discussions.md,broken liquid tags
+translations/fr-FR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
translations/fr-FR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,rendering error
translations/fr-FR/content/discussions/quickstart.md,rendering error
translations/fr-FR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
-translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
+translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
-translations/fr-FR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
-translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
+translations/fr-FR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
translations/fr-FR/content/education/quickstart.md,rendering error
-translations/fr-FR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/fr-FR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
+translations/fr-FR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
+translations/fr-FR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags
translations/fr-FR/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
translations/fr-FR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
translations/fr-FR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
translations/fr-FR/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
translations/fr-FR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
translations/fr-FR/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md,rendering error
-translations/fr-FR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,rendering error
-translations/fr-FR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,rendering error
+translations/fr-FR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
+translations/fr-FR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags
translations/fr-FR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags
translations/fr-FR/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
translations/fr-FR/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags
translations/fr-FR/content/get-started/learning-about-github/githubs-products.md,rendering error
-translations/fr-FR/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/fr-FR/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
+translations/fr-FR/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags
translations/fr-FR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/fr-FR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/fr-FR/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/fr-FR/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
+translations/fr-FR/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
+translations/fr-FR/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
translations/fr-FR/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md,rendering error
translations/fr-FR/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md,rendering error
translations/fr-FR/content/get-started/quickstart/contributing-to-projects.md,rendering error
-translations/fr-FR/content/get-started/quickstart/create-a-repo.md,rendering error
+translations/fr-FR/content/get-started/quickstart/create-a-repo.md,broken liquid tags
translations/fr-FR/content/get-started/quickstart/fork-a-repo.md,rendering error
translations/fr-FR/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
translations/fr-FR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
translations/fr-FR/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
-translations/fr-FR/content/get-started/using-git/about-git-rebase.md,rendering error
+translations/fr-FR/content/get-started/using-git/about-git-rebase.md,broken liquid tags
translations/fr-FR/content/get-started/using-github/github-mobile.md,rendering error
translations/fr-FR/content/get-started/using-github/keyboard-shortcuts.md,rendering error
translations/fr-FR/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,rendering error
@@ -867,7 +847,7 @@ translations/fr-FR/content/graphql/guides/forming-calls-with-graphql.md,renderin
translations/fr-FR/content/graphql/guides/introduction-to-graphql.md,broken liquid tags
translations/fr-FR/content/graphql/guides/managing-enterprise-accounts.md,rendering error
translations/fr-FR/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
-translations/fr-FR/content/graphql/overview/about-the-graphql-api.md,rendering error
+translations/fr-FR/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
translations/fr-FR/content/graphql/reference/enums.md,rendering error
translations/fr-FR/content/graphql/reference/input-objects.md,rendering error
translations/fr-FR/content/graphql/reference/interfaces.md,rendering error
@@ -877,12 +857,11 @@ translations/fr-FR/content/graphql/reference/unions.md,rendering error
translations/fr-FR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
translations/fr-FR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
translations/fr-FR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
-translations/fr-FR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error
translations/fr-FR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
-translations/fr-FR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
+translations/fr-FR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
translations/fr-FR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md,rendering error
-translations/fr-FR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/fr-FR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
+translations/fr-FR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
+translations/fr-FR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
translations/fr-FR/content/organizations/keeping-your-organization-secure/index.md,rendering error
translations/fr-FR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md,rendering error
translations/fr-FR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
@@ -892,7 +871,7 @@ translations/fr-FR/content/organizations/keeping-your-organization-secure/managi
translations/fr-FR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
translations/fr-FR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md,rendering error
translations/fr-FR/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md,rendering error
-translations/fr-FR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
+translations/fr-FR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags
translations/fr-FR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md,rendering error
translations/fr-FR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md,rendering error
translations/fr-FR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md,rendering error
@@ -917,7 +896,7 @@ translations/fr-FR/content/organizations/managing-organization-settings/verifyin
translations/fr-FR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
translations/fr-FR/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md,broken liquid tags
translations/fr-FR/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md,broken liquid tags
-translations/fr-FR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
+translations/fr-FR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
translations/fr-FR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md,rendering error
translations/fr-FR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
translations/fr-FR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md,rendering error
@@ -935,7 +914,6 @@ translations/fr-FR/content/packages/learn-github-packages/introduction-to-github
translations/fr-FR/content/packages/learn-github-packages/publishing-a-package.md,rendering error
translations/fr-FR/content/packages/learn-github-packages/viewing-packages.md,rendering error
translations/fr-FR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/fr-FR/content/packages/quickstart.md,rendering error
translations/fr-FR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/fr-FR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
translations/fr-FR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
@@ -946,7 +924,7 @@ translations/fr-FR/content/packages/working-with-a-github-packages-registry/work
translations/fr-FR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
translations/fr-FR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
translations/fr-FR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
-translations/fr-FR/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
+translations/fr-FR/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
translations/fr-FR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md,rendering error
translations/fr-FR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,rendering error
translations/fr-FR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
@@ -957,24 +935,24 @@ translations/fr-FR/content/pages/setting-up-a-github-pages-site-with-jekyll/crea
translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
-translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
+translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags
translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error
translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
translations/fr-FR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
-translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
-translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
-translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
-translations/fr-FR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
+translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags
+translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags
+translations/fr-FR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags
+translations/fr-FR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags
translations/fr-FR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
translations/fr-FR/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/fr-FR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,rendering error
-translations/fr-FR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,rendering error
-translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,rendering error
+translations/fr-FR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags
+translations/fr-FR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags
+translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,rendering error
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,rendering error
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error
-translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,rendering error
+translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md,rendering error
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error
@@ -983,32 +961,29 @@ translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
translations/fr-FR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/fr-FR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,rendering error
-translations/fr-FR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,rendering error
+translations/fr-FR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags
translations/fr-FR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md,rendering error
translations/fr-FR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error
translations/fr-FR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
-translations/fr-FR/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,rendering error
+translations/fr-FR/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md,rendering error
-translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
+translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,rendering error
translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,rendering error
translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error
-translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
+translations/fr-FR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags
translations/fr-FR/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/fr-FR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,rendering error
translations/fr-FR/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
translations/fr-FR/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
translations/fr-FR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
translations/fr-FR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error
-translations/fr-FR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
-translations/fr-FR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/fr-FR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/fr-FR/content/repositories/working-with-files/using-files/viewing-a-file.md,rendering error
+translations/fr-FR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags
+translations/fr-FR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
+translations/fr-FR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags
translations/fr-FR/content/rest/activity/notifications.md,broken liquid tags
-translations/fr-FR/content/rest/apps/oauth-applications.md,rendering error
+translations/fr-FR/content/rest/apps/oauth-applications.md,broken liquid tags
translations/fr-FR/content/rest/codespaces/codespaces.md,broken liquid tags
translations/fr-FR/content/rest/dependabot/index.md,broken liquid tags
translations/fr-FR/content/rest/deployments/deployments.md,rendering error
@@ -1036,17 +1011,18 @@ translations/fr-FR/content/rest/overview/permissions-required-for-github-apps.md
translations/fr-FR/content/rest/packages.md,broken liquid tags
translations/fr-FR/content/rest/projects/projects.md,broken liquid tags
translations/fr-FR/content/rest/quickstart.md,broken liquid tags
-translations/fr-FR/content/rest/scim.md,rendering error
-translations/fr-FR/content/rest/teams/team-sync.md,rendering error
-translations/fr-FR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
+translations/fr-FR/content/rest/scim.md,broken liquid tags
+translations/fr-FR/content/rest/teams/team-sync.md,broken liquid tags
+translations/fr-FR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags
translations/fr-FR/content/search-github/searching-on-github/searching-for-packages.md,rendering error
-translations/fr-FR/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
+translations/fr-FR/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags
translations/fr-FR/content/site-policy/content-removal-policies/github-private-information-removal-policy.md,broken liquid tags
-translations/fr-FR/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md,rendering error
+translations/fr-FR/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md,broken liquid tags
translations/fr-FR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags
-translations/fr-FR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,rendering error
-translations/fr-FR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,rendering error
-translations/fr-FR/content/support/contacting-github-support/providing-data-to-github-support.md,rendering error
+translations/fr-FR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
+translations/fr-FR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
+translations/fr-FR/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
+translations/fr-FR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
translations/fr-FR/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
translations/fr-FR/content/support/learning-about-github-support/about-github-support.md,rendering error
translations/fr-FR/data/glossaries/external.yml,broken liquid tags
@@ -1069,9 +1045,11 @@ translations/fr-FR/data/release-notes/enterprise-server/3-4/7.yml,rendering erro
translations/fr-FR/data/release-notes/enterprise-server/3-4/8.yml,rendering error
translations/fr-FR/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
translations/fr-FR/data/release-notes/enterprise-server/3-5/4.yml,rendering error
+translations/fr-FR/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
translations/fr-FR/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
+translations/fr-FR/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
translations/fr-FR/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags
-translations/fr-FR/data/reusables/actions/cache-default-size.md,rendering error
+translations/fr-FR/data/reusables/actions/cache-default-size.md,broken liquid tags
translations/fr-FR/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error
translations/fr-FR/data/reusables/actions/changing-the-name-of-a-runner-group.md,rendering error
translations/fr-FR/data/reusables/actions/configure-runner-group-access.md,rendering error
@@ -1079,17 +1057,18 @@ translations/fr-FR/data/reusables/actions/create-runner-group.md,rendering error
translations/fr-FR/data/reusables/actions/creating-a-runner-group-for-an-enterprise.md,rendering error
translations/fr-FR/data/reusables/actions/creating-a-runner-group-for-an-organization.md,rendering error
translations/fr-FR/data/reusables/actions/disabling-github-actions.md,broken liquid tags
-translations/fr-FR/data/reusables/actions/enterprise-common-prereqs.md,rendering error
+translations/fr-FR/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
translations/fr-FR/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
-translations/fr-FR/data/reusables/actions/enterprise-postinstall-nextsteps.md,rendering error
-translations/fr-FR/data/reusables/actions/github-connect-resolution.md,rendering error
+translations/fr-FR/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
+translations/fr-FR/data/reusables/actions/github-connect-resolution.md,broken liquid tags
translations/fr-FR/data/reusables/actions/hosted-runner-security.md,broken liquid tags
translations/fr-FR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
+translations/fr-FR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md,broken liquid tags
translations/fr-FR/data/reusables/actions/more-resources-for-ghes.md,rendering error
translations/fr-FR/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
translations/fr-FR/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
translations/fr-FR/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
-translations/fr-FR/data/reusables/actions/reusable-workflows-ghes-beta.md,rendering error
+translations/fr-FR/data/reusables/actions/reusable-workflows-enterprise-beta.md,rendering error
translations/fr-FR/data/reusables/actions/reusable-workflows.md,rendering error
translations/fr-FR/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
translations/fr-FR/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
@@ -1102,11 +1081,11 @@ 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/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/upgrade-runners-before-upgrade-ghes.md,broken liquid tags
+translations/fr-FR/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
translations/fr-FR/data/reusables/actions/workflow-dispatch-inputs.md,rendering error
-translations/fr-FR/data/reusables/actions/workflow-template-overview.md,rendering error
-translations/fr-FR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,rendering error
+translations/fr-FR/data/reusables/actions/workflow-template-overview.md,broken liquid tags
+translations/fr-FR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
translations/fr-FR/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
translations/fr-FR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
translations/fr-FR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
@@ -1115,15 +1094,15 @@ translations/fr-FR/data/reusables/apps/user-to-server-rate-limits.md,broken liqu
translations/fr-FR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error
translations/fr-FR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
translations/fr-FR/data/reusables/audit_log/retention-periods.md,rendering error
-translations/fr-FR/data/reusables/branches/new-repo-default-branch.md,rendering error
-translations/fr-FR/data/reusables/classroom/about-autograding.md,rendering error
-translations/fr-FR/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,rendering error
+translations/fr-FR/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
+translations/fr-FR/data/reusables/classroom/about-autograding.md,broken liquid tags
+translations/fr-FR/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
translations/fr-FR/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
translations/fr-FR/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
translations/fr-FR/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
translations/fr-FR/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
translations/fr-FR/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
-translations/fr-FR/data/reusables/code-scanning/what-is-codeql-cli.md,rendering error
+translations/fr-FR/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
translations/fr-FR/data/reusables/codespaces/codespaces-disabling-org-billing.md,broken liquid tags
translations/fr-FR/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
translations/fr-FR/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
@@ -1138,18 +1117,17 @@ translations/fr-FR/data/reusables/dependabot/dependabot-alerts-filters.md,render
translations/fr-FR/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error
translations/fr-FR/data/reusables/dependabot/sidebar-secret.md,rendering error
translations/fr-FR/data/reusables/dependabot/supported-package-managers.md,rendering error
-translations/fr-FR/data/reusables/desktop/get-an-account.md,rendering error
-translations/fr-FR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,rendering error
-translations/fr-FR/data/reusables/discussions/navigate-to-repo-or-org.md,rendering error
-translations/fr-FR/data/reusables/discussions/starting-a-discussion.md,rendering error
+translations/fr-FR/data/reusables/desktop/get-an-account.md,broken liquid tags
+translations/fr-FR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
+translations/fr-FR/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags
+translations/fr-FR/data/reusables/discussions/starting-a-discussion.md,broken liquid tags
translations/fr-FR/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags
-translations/fr-FR/data/reusables/dotcom_billing/view-all-subscriptions.md,rendering error
+translations/fr-FR/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md,rendering error
-translations/fr-FR/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
+translations/fr-FR/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
-translations/fr-FR/data/reusables/enterprise-accounts/emu-forks.md,rendering error
translations/fr-FR/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags
@@ -1157,26 +1135,26 @@ translations/fr-FR/data/reusables/enterprise-accounts/emu-permission-interact.md
translations/fr-FR/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error
-translations/fr-FR/data/reusables/enterprise-accounts/oidc-gei-warning.md,rendering error
+translations/fr-FR/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise-accounts/security-tab.md,rendering error
translations/fr-FR/data/reusables/enterprise-licensing/verified-domains-license-sync.md,rendering error
translations/fr-FR/data/reusables/enterprise/3-5-missing-feature.md,rendering error
-translations/fr-FR/data/reusables/enterprise/apply-configuration.md,rendering error
+translations/fr-FR/data/reusables/enterprise/apply-configuration.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise/rate_limit.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
-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/test-in-staging.md,broken liquid tags
+translations/fr-FR/data/reusables/enterprise_installation/download-package.md,broken liquid tags
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/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
-translations/fr-FR/data/reusables/enterprise_site_admin_settings/tls-downtime.md,rendering error
-translations/fr-FR/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,rendering error
-translations/fr-FR/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,rendering error
-translations/fr-FR/data/reusables/enterprise_user_management/built-in-authentication.md,rendering error
+translations/fr-FR/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags
+translations/fr-FR/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags
+translations/fr-FR/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags
+translations/fr-FR/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags
+translations/fr-FR/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags
+translations/fr-FR/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags
+translations/fr-FR/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags
translations/fr-FR/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
-translations/fr-FR/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,rendering error
+translations/fr-FR/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
translations/fr-FR/data/reusables/files/choose-commit-email.md,broken liquid tags
translations/fr-FR/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
translations/fr-FR/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
@@ -1185,26 +1163,26 @@ translations/fr-FR/data/reusables/gated-features/secret-scanning-partner.md,rend
translations/fr-FR/data/reusables/gated-features/secret-scanning.md,rendering error
translations/fr-FR/data/reusables/gated-features/security-overview.md,rendering error
translations/fr-FR/data/reusables/gcm-core/next-time-you-clone.md,rendering error
-translations/fr-FR/data/reusables/getting-started/actions.md,rendering error
-translations/fr-FR/data/reusables/getting-started/adding-members-to-organizations.md,rendering error
+translations/fr-FR/data/reusables/getting-started/actions.md,broken liquid tags
+translations/fr-FR/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags
translations/fr-FR/data/reusables/getting-started/configuring-security-features.md,broken liquid tags
-translations/fr-FR/data/reusables/getting-started/creating-organizations.md,rendering error
-translations/fr-FR/data/reusables/getting-started/enforcing-repo-management-policies.md,rendering error
+translations/fr-FR/data/reusables/getting-started/creating-organizations.md,broken liquid tags
+translations/fr-FR/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags
translations/fr-FR/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
-translations/fr-FR/data/reusables/getting-started/managing-enterprise-members.md,rendering error
-translations/fr-FR/data/reusables/git/git-push.md,rendering error
-translations/fr-FR/data/reusables/git/provide-credentials.md,rendering error
+translations/fr-FR/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
+translations/fr-FR/data/reusables/git/git-push.md,broken liquid tags
+translations/fr-FR/data/reusables/git/provide-credentials.md,broken liquid tags
translations/fr-FR/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md,rendering error
translations/fr-FR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,rendering error
translations/fr-FR/data/reusables/large_files/storage_assets_location.md,broken liquid tags
-translations/fr-FR/data/reusables/large_files/use_lfs_tip.md,rendering error
+translations/fr-FR/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
translations/fr-FR/data/reusables/notifications/outbound_email_tip.md,broken liquid tags
translations/fr-FR/data/reusables/notifications/shared_state.md,broken liquid tags
translations/fr-FR/data/reusables/notifications/vulnerable-dependency-notification-options.md,rendering error
translations/fr-FR/data/reusables/organizations/billing_plans.md,rendering error
translations/fr-FR/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
translations/fr-FR/data/reusables/organizations/member-privileges.md,rendering error
-translations/fr-FR/data/reusables/organizations/navigate-to-org.md,rendering error
+translations/fr-FR/data/reusables/organizations/navigate-to-org.md,broken liquid tags
translations/fr-FR/data/reusables/organizations/repository-defaults.md,rendering error
translations/fr-FR/data/reusables/organizations/security-and-analysis.md,rendering error
translations/fr-FR/data/reusables/organizations/security.md,rendering error
@@ -1217,9 +1195,9 @@ translations/fr-FR/data/reusables/package_registry/authenticate-packages.md,brok
translations/fr-FR/data/reusables/package_registry/authenticate-to-container-registry-steps.md,rendering error
translations/fr-FR/data/reusables/package_registry/container-registry-ghes-beta.md,rendering error
translations/fr-FR/data/reusables/package_registry/container-registry-hostname.md,rendering error
-translations/fr-FR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,rendering error
+translations/fr-FR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
translations/fr-FR/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
-translations/fr-FR/data/reusables/package_registry/packages-billing.md,rendering error
+translations/fr-FR/data/reusables/package_registry/packages-billing.md,broken liquid tags
translations/fr-FR/data/reusables/package_registry/required-scopes.md,broken liquid tags
translations/fr-FR/data/reusables/pages/build-failure-email-server.md,broken liquid tags
translations/fr-FR/data/reusables/pages/emu-org-only.md,broken liquid tags
@@ -1227,19 +1205,19 @@ translations/fr-FR/data/reusables/pages/sidebar-pages.md,rendering error
translations/fr-FR/data/reusables/project-management/choose-visibility.md,rendering error
translations/fr-FR/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
translations/fr-FR/data/reusables/projects/graphql-ghes.md,rendering error
-translations/fr-FR/data/reusables/pull_requests/configure_pull_request_merges_intro.md,rendering error
-translations/fr-FR/data/reusables/pull_requests/default_merge_option.md,rendering error
-translations/fr-FR/data/reusables/pull_requests/pull_request_merges_and_contributions.md,rendering error
-translations/fr-FR/data/reusables/pull_requests/rebase_and_merge_summary.md,rendering error
+translations/fr-FR/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
+translations/fr-FR/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
+translations/fr-FR/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
+translations/fr-FR/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
translations/fr-FR/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
-translations/fr-FR/data/reusables/pull_requests/squash_and_merge_summary.md,rendering error
+translations/fr-FR/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags
translations/fr-FR/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md,rendering error
translations/fr-FR/data/reusables/repositories/changed-files.md,broken liquid tags
-translations/fr-FR/data/reusables/repositories/deploy-keys.md,rendering error
+translations/fr-FR/data/reusables/repositories/deploy-keys.md,broken liquid tags
translations/fr-FR/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
translations/fr-FR/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error
translations/fr-FR/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
-translations/fr-FR/data/reusables/repositories/navigate-to-repo.md,rendering error
+translations/fr-FR/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
translations/fr-FR/data/reusables/repositories/repository-branches.md,rendering error
translations/fr-FR/data/reusables/repositories/security-alert-delivery-options.md,rendering error
translations/fr-FR/data/reusables/repositories/settings-sidebar-actions-general.md,rendering error
@@ -1249,25 +1227,25 @@ translations/fr-FR/data/reusables/repositories/suggest-changes.md,broken liquid
translations/fr-FR/data/reusables/repositories/you-can-fork.md,broken liquid tags
translations/fr-FR/data/reusables/rest-api/dotcom-only-guide-note.md,rendering error
translations/fr-FR/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
-translations/fr-FR/data/reusables/saml/about-linked-identities.md,rendering error
+translations/fr-FR/data/reusables/saml/about-linked-identities.md,broken liquid tags
translations/fr-FR/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags
translations/fr-FR/data/reusables/saml/authorized-creds-info.md,broken liquid tags
translations/fr-FR/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
translations/fr-FR/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
-translations/fr-FR/data/reusables/scim/enterprise-account-scim.md,rendering error
-translations/fr-FR/data/reusables/scim/supported-idps.md,rendering error
+translations/fr-FR/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
+translations/fr-FR/data/reusables/scim/supported-idps.md,broken liquid tags
translations/fr-FR/data/reusables/search/syntax_tips.md,broken liquid tags
translations/fr-FR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
translations/fr-FR/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
translations/fr-FR/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
translations/fr-FR/data/reusables/security-overview/permissions.md,rendering error
translations/fr-FR/data/reusables/security/displayed-information.md,broken liquid tags
-translations/fr-FR/data/reusables/shortdesc/rate_limits_github_apps.md,rendering error
-translations/fr-FR/data/reusables/sponsors/select-sponsorship-billing.md,rendering error
+translations/fr-FR/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
+translations/fr-FR/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
translations/fr-FR/data/reusables/ssh/about-ssh.md,broken liquid tags
translations/fr-FR/data/reusables/ssh/key-type-support.md,rendering error
-translations/fr-FR/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,rendering error
-translations/fr-FR/data/reusables/support/help_resources.md,rendering error
+translations/fr-FR/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
+translations/fr-FR/data/reusables/support/help_resources.md,broken liquid tags
translations/fr-FR/data/reusables/support/submit-a-ticket.md,broken liquid tags
translations/fr-FR/data/reusables/user-settings/access_applications.md,rendering error
translations/fr-FR/data/reusables/user-settings/account_settings.md,rendering error
diff --git a/translations/log/msft-ja-resets.csv b/translations/log/msft-ja-resets.csv
index 47cbf411c6..652e99af98 100644
--- a/translations/log/msft-ja-resets.csv
+++ b/translations/log/msft-ja-resets.csv
@@ -454,20 +454,20 @@ translations/ja-JP/data/reusables/security-center/beta.md,file deleted because i
translations/ja-JP/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
-translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
+translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,rendering error
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error
@@ -478,10 +478,10 @@ translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-pers
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md,rendering error
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md,broken liquid tags
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,rendering error
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,broken liquid tags
translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md,rendering error
-translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
+translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags
+translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags
translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
translations/ja-JP/content/actions/creating-actions/releasing-and-maintaining-actions.md,broken liquid tags
@@ -513,14 +513,14 @@ translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-
translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
-translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
+translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
translations/ja-JP/content/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
+translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md,rendering error
translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
-translations/ja-JP/content/actions/quickstart.md,rendering error
+translations/ja-JP/content/actions/quickstart.md,broken liquid tags
translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md,rendering error
translations/ja-JP/content/actions/security-guides/encrypted-secrets.md,rendering error
translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
@@ -537,80 +537,76 @@ translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md,rend
translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
-translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,rendering error
+translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
+translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
+translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md,rendering error
translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
+translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags
translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,rendering error
-translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md,rendering error
+translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,rendering error
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
+translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
translations/ja-JP/content/admin/identity-and-access-management/index.md,broken liquid tags
-translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,rendering error
+translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error
translations/ja-JP/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
+translations/ja-JP/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags
+translations/ja-JP/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags
+translations/ja-JP/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
+translations/ja-JP/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
+translations/ja-JP/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,rendering error
+translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,rendering error
+translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags
translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,rendering error
translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags
translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags
@@ -619,71 +615,69 @@ translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-ser
translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error
translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
-translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error
-translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error
+translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags
+translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,rendering error
+translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md,rendering error
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/overview/about-data-residency.md,rendering error
-translations/ja-JP/content/admin/overview/about-github-enterprise-server.md,rendering error
+translations/ja-JP/content/admin/overview/about-data-residency.md,broken liquid tags
+translations/ja-JP/content/admin/overview/about-github-enterprise-server.md,broken liquid tags
translations/ja-JP/content/admin/overview/about-github-for-enterprises.md,rendering error
translations/ja-JP/content/admin/overview/system-overview.md,rendering error
-translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
-translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,rendering error
-translations/ja-JP/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
+translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
+translations/ja-JP/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags
-translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
+translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
-translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
+translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags
+translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,rendering error
+translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags
translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,rendering error
+translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags
translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
+translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags
translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error
translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,rendering error
translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/ja-JP/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,rendering error
+translations/ja-JP/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
+translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags
+translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags
+translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,rendering error
+translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
translations/ja-JP/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,rendering error
-translations/ja-JP/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,rendering error
+translations/ja-JP/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags
translations/ja-JP/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error
-translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error
+translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
-translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
+translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
-translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
-translations/ja-JP/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
+translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
+translations/ja-JP/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
-translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
translations/ja-JP/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
@@ -692,13 +686,13 @@ translations/ja-JP/content/billing/managing-billing-for-github-packages/about-bi
translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,rendering error
translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
-translations/ja-JP/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
+translations/ja-JP/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags
translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,broken liquid tags
-translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,rendering error
-translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,rendering error
+translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
+translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,rendering error
-translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,rendering error
-translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,rendering error
+translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
+translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
@@ -708,12 +702,12 @@ translations/ja-JP/content/code-security/code-scanning/automatically-scanning-yo
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
+translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
@@ -742,10 +736,7 @@ translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-
translations/ja-JP/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error
translations/ja-JP/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
-translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error
-translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
-translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md,rendering error
translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md,rendering error
translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md,rendering error
@@ -755,83 +746,72 @@ translations/ja-JP/content/code-security/supply-chain-security/understanding-you
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
-translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md,rendering error
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md,rendering error
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,rendering error
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,rendering error
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md,rendering error
-translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error
translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md,broken liquid tags
-translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error
-translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error
-translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
-translations/ja-JP/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
+translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
+translations/ja-JP/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
-translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
-translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
+translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
+translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
translations/ja-JP/content/copilot/quickstart.md,broken liquid tags
-translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error
+translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
+translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags
translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
-translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
-translations/ja-JP/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error
-translations/ja-JP/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
+translations/ja-JP/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,broken liquid tags
+translations/ja-JP/content/developers/apps/guides/using-the-github-api-in-your-app.md,broken liquid tags
+translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags
translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags
-translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
+translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags
+translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
translations/ja-JP/content/developers/overview/about-githubs-apis.md,broken liquid tags
-translations/ja-JP/content/developers/overview/managing-deploy-keys.md,rendering error
+translations/ja-JP/content/developers/overview/managing-deploy-keys.md,broken liquid tags
translations/ja-JP/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
translations/ja-JP/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,rendering error
-translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,rendering error
-translations/ja-JP/content/discussions/guides/finding-your-discussions.md,rendering error
-translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,rendering error
-translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md,rendering error
+translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
+translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
+translations/ja-JP/content/discussions/guides/finding-your-discussions.md,broken liquid tags
+translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,rendering error
translations/ja-JP/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
+translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
+translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
-translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
+translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
+translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags
translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
translations/ja-JP/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
translations/ja-JP/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
translations/ja-JP/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md,rendering error
-translations/ja-JP/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,rendering error
-translations/ja-JP/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,rendering error
+translations/ja-JP/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
+translations/ja-JP/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags
translations/ja-JP/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags
translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags
translations/ja-JP/content/get-started/learning-about-github/githubs-products.md,rendering error
-translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
+translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags
translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
+translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
+translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md,rendering error
-translations/ja-JP/content/get-started/quickstart/create-a-repo.md,rendering error
+translations/ja-JP/content/get-started/quickstart/create-a-repo.md,broken liquid tags
translations/ja-JP/content/get-started/quickstart/fork-a-repo.md,rendering error
translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md,rendering error
translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
-translations/ja-JP/content/get-started/using-git/about-git-rebase.md,rendering error
+translations/ja-JP/content/get-started/using-git/about-git-rebase.md,broken liquid tags
translations/ja-JP/content/get-started/using-github/github-desktop.md,broken liquid tags
translations/ja-JP/content/get-started/using-github/github-mobile.md,rendering error
translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md,rendering error
@@ -847,7 +827,7 @@ translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md,renderin
translations/ja-JP/content/graphql/guides/introduction-to-graphql.md,broken liquid tags
translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md,rendering error
translations/ja-JP/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
-translations/ja-JP/content/graphql/overview/about-the-graphql-api.md,rendering error
+translations/ja-JP/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
translations/ja-JP/content/graphql/reference/enums.md,rendering error
translations/ja-JP/content/graphql/reference/input-objects.md,rendering error
translations/ja-JP/content/graphql/reference/interfaces.md,rendering error
@@ -857,16 +837,15 @@ translations/ja-JP/content/graphql/reference/unions.md,rendering error
translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
-translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error
translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
-translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
-translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
+translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
+translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
+translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md,rendering error
translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
-translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
+translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags
translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error
translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
translations/ja-JP/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error
@@ -878,7 +857,7 @@ translations/ja-JP/content/organizations/managing-organization-settings/managing
translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md,rendering error
translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
+translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
@@ -891,7 +870,6 @@ translations/ja-JP/content/packages/learn-github-packages/introduction-to-github
translations/ja-JP/content/packages/learn-github-packages/publishing-a-package.md,rendering error
translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md,rendering error
translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/ja-JP/content/packages/quickstart.md,rendering error
translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,rendering error
translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
@@ -902,33 +880,33 @@ translations/ja-JP/content/packages/working-with-a-github-packages-registry/work
translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
+translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,broken liquid tags
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
+translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,broken liquid tags
+translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md,broken liquid tags
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
+translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags
+translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags
+translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags
+translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags
translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,rendering error
-translations/ja-JP/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,rendering error
+translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags
+translations/ja-JP/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags
+translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,rendering error
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,rendering error
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,rendering error
+translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md,rendering error
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error
@@ -937,28 +915,25 @@ translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,rendering error
+translations/ja-JP/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags
translations/ja-JP/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error
translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
+translations/ja-JP/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
+translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,rendering error
translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
+translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags
translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,rendering error
translations/ja-JP/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
translations/ja-JP/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/using-files/viewing-a-file.md,rendering error
+translations/ja-JP/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags
+translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
+translations/ja-JP/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags
translations/ja-JP/content/rest/activity/notifications.md,broken liquid tags
-translations/ja-JP/content/rest/apps/oauth-applications.md,rendering error
+translations/ja-JP/content/rest/apps/oauth-applications.md,broken liquid tags
translations/ja-JP/content/rest/codespaces/codespaces.md,broken liquid tags
translations/ja-JP/content/rest/dependabot/index.md,broken liquid tags
translations/ja-JP/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
@@ -985,14 +960,15 @@ translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
translations/ja-JP/content/rest/packages.md,broken liquid tags
translations/ja-JP/content/rest/projects/projects.md,broken liquid tags
translations/ja-JP/content/rest/quickstart.md,broken liquid tags
-translations/ja-JP/content/rest/scim.md,rendering error
-translations/ja-JP/content/rest/teams/team-sync.md,rendering error
+translations/ja-JP/content/rest/scim.md,broken liquid tags
+translations/ja-JP/content/rest/teams/team-sync.md,broken liquid tags
translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
-translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
+translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags
translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags
-translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,rendering error
-translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,rendering error
-translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md,rendering error
+translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
+translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
+translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
+translations/ja-JP/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
translations/ja-JP/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
translations/ja-JP/content/support/learning-about-github-support/about-github-support.md,rendering error
translations/ja-JP/data/glossaries/external.yml,broken liquid tags
@@ -1014,25 +990,29 @@ translations/ja-JP/data/release-notes/enterprise-server/3-4/7.yml,rendering erro
translations/ja-JP/data/release-notes/enterprise-server/3-4/8.yml,rendering error
translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
translations/ja-JP/data/release-notes/enterprise-server/3-5/4.yml,rendering error
+translations/ja-JP/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
+translations/ja-JP/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
translations/ja-JP/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags
translations/ja-JP/data/reusables/actions/artifact-log-retention-statement.md,broken liquid tags
-translations/ja-JP/data/reusables/actions/cache-default-size.md,rendering error
+translations/ja-JP/data/reusables/actions/cache-default-size.md,broken liquid tags
translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error
translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md,rendering error
translations/ja-JP/data/reusables/actions/create-runner-group.md,rendering error
translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md,rendering error
translations/ja-JP/data/reusables/actions/disabling-github-actions.md,broken liquid tags
-translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md,rendering error
+translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
translations/ja-JP/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
-translations/ja-JP/data/reusables/actions/enterprise-postinstall-nextsteps.md,rendering error
-translations/ja-JP/data/reusables/actions/github-connect-resolution.md,rendering error
+translations/ja-JP/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
+translations/ja-JP/data/reusables/actions/github-connect-resolution.md,broken liquid tags
translations/ja-JP/data/reusables/actions/hosted-runner-security.md,broken liquid tags
translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
+translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md,broken liquid tags
translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md,rendering error
translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
translations/ja-JP/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
translations/ja-JP/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
+translations/ja-JP/data/reusables/actions/reusable-workflows-enterprise-beta.md,rendering error
translations/ja-JP/data/reusables/actions/reusable-workflows.md,rendering error
translations/ja-JP/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
translations/ja-JP/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
@@ -1046,11 +1026,11 @@ translations/ja-JP/data/reusables/actions/settings-ui/settings-actions-pages-cus
translations/ja-JP/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error
translations/ja-JP/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error
translations/ja-JP/data/reusables/actions/sidebar-secret.md,rendering error
-translations/ja-JP/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,rendering error
-translations/ja-JP/data/reusables/actions/workflow-basic-example-and-explanation.md,rendering error
+translations/ja-JP/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags
+translations/ja-JP/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
translations/ja-JP/data/reusables/actions/workflow-dispatch-inputs.md,rendering error
-translations/ja-JP/data/reusables/actions/workflow-template-overview.md,rendering error
-translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,rendering error
+translations/ja-JP/data/reusables/actions/workflow-template-overview.md,broken liquid tags
+translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
translations/ja-JP/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
@@ -1058,15 +1038,15 @@ translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protect
translations/ja-JP/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error
translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
-translations/ja-JP/data/reusables/branches/new-repo-default-branch.md,rendering error
-translations/ja-JP/data/reusables/classroom/about-autograding.md,rendering error
-translations/ja-JP/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,rendering error
+translations/ja-JP/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
+translations/ja-JP/data/reusables/classroom/about-autograding.md,broken liquid tags
+translations/ja-JP/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
-translations/ja-JP/data/reusables/code-scanning/what-is-codeql-cli.md,rendering error
+translations/ja-JP/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md,rendering error
translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
translations/ja-JP/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
@@ -1081,16 +1061,15 @@ translations/ja-JP/data/reusables/dependabot/enabling-disabling-dependency-graph
translations/ja-JP/data/reusables/dependabot/sidebar-secret.md,rendering error
translations/ja-JP/data/reusables/dependabot/supported-package-managers.md,rendering error
translations/ja-JP/data/reusables/desktop/get-an-account.md,rendering error
-translations/ja-JP/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,rendering error
-translations/ja-JP/data/reusables/discussions/navigate-to-repo-or-org.md,rendering error
-translations/ja-JP/data/reusables/discussions/starting-a-discussion.md,rendering error
+translations/ja-JP/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
+translations/ja-JP/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags
+translations/ja-JP/data/reusables/discussions/starting-a-discussion.md,broken liquid tags
translations/ja-JP/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags
-translations/ja-JP/data/reusables/dotcom_billing/view-all-subscriptions.md,rendering error
+translations/ja-JP/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
-translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
+translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
-translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md,rendering error
translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags
@@ -1098,49 +1077,49 @@ translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-interact.md
translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error
-translations/ja-JP/data/reusables/enterprise-accounts/oidc-gei-warning.md,rendering error
+translations/ja-JP/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise-accounts/security-tab.md,rendering error
-translations/ja-JP/data/reusables/enterprise/apply-configuration.md,rendering error
+translations/ja-JP/data/reusables/enterprise/apply-configuration.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise/rate_limit.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
-translations/ja-JP/data/reusables/enterprise/test-in-staging.md,rendering error
-translations/ja-JP/data/reusables/enterprise_installation/download-package.md,rendering error
+translations/ja-JP/data/reusables/enterprise/test-in-staging.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise_installation/download-package.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,rendering error
translations/ja-JP/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags
-translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md,rendering error
-translations/ja-JP/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,rendering error
-translations/ja-JP/data/reusables/enterprise_site_admin_settings/sign-in.md,rendering error
-translations/ja-JP/data/reusables/enterprise_site_admin_settings/tls-downtime.md,rendering error
-translations/ja-JP/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,rendering error
-translations/ja-JP/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,rendering error
-translations/ja-JP/data/reusables/enterprise_user_management/built-in-authentication.md,rendering error
+translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags
translations/ja-JP/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
-translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,rendering error
+translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
translations/ja-JP/data/reusables/files/choose-commit-email.md,broken liquid tags
translations/ja-JP/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
translations/ja-JP/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
translations/ja-JP/data/reusables/gated-features/secret-scanning-partner.md,rendering error
translations/ja-JP/data/reusables/gated-features/secret-scanning.md,rendering error
-translations/ja-JP/data/reusables/getting-started/actions.md,rendering error
-translations/ja-JP/data/reusables/getting-started/adding-members-to-organizations.md,rendering error
+translations/ja-JP/data/reusables/getting-started/actions.md,broken liquid tags
+translations/ja-JP/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags
translations/ja-JP/data/reusables/getting-started/configuring-security-features.md,broken liquid tags
-translations/ja-JP/data/reusables/getting-started/creating-organizations.md,rendering error
-translations/ja-JP/data/reusables/getting-started/enforcing-repo-management-policies.md,rendering error
+translations/ja-JP/data/reusables/getting-started/creating-organizations.md,broken liquid tags
+translations/ja-JP/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags
translations/ja-JP/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
-translations/ja-JP/data/reusables/getting-started/managing-enterprise-members.md,rendering error
-translations/ja-JP/data/reusables/git/git-push.md,rendering error
-translations/ja-JP/data/reusables/git/provide-credentials.md,rendering error
+translations/ja-JP/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
+translations/ja-JP/data/reusables/git/git-push.md,broken liquid tags
+translations/ja-JP/data/reusables/git/provide-credentials.md,broken liquid tags
translations/ja-JP/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md,rendering error
translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,rendering error
translations/ja-JP/data/reusables/large_files/storage_assets_location.md,broken liquid tags
-translations/ja-JP/data/reusables/large_files/use_lfs_tip.md,rendering error
+translations/ja-JP/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
translations/ja-JP/data/reusables/notifications/outbound_email_tip.md,broken liquid tags
translations/ja-JP/data/reusables/notifications/shared_state.md,rendering error
translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md,rendering error
translations/ja-JP/data/reusables/organizations/billing_plans.md,rendering error
translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
translations/ja-JP/data/reusables/organizations/member-privileges.md,rendering error
-translations/ja-JP/data/reusables/organizations/navigate-to-org.md,rendering error
+translations/ja-JP/data/reusables/organizations/navigate-to-org.md,broken liquid tags
translations/ja-JP/data/reusables/organizations/repository-defaults.md,rendering error
translations/ja-JP/data/reusables/organizations/security-and-analysis.md,rendering error
translations/ja-JP/data/reusables/organizations/security.md,rendering error
@@ -1148,55 +1127,55 @@ translations/ja-JP/data/reusables/organizations/teams_sidebar.md,rendering error
translations/ja-JP/data/reusables/organizations/verified-domains.md,rendering error
translations/ja-JP/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md,rendering error
-translations/ja-JP/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,rendering error
+translations/ja-JP/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
translations/ja-JP/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
-translations/ja-JP/data/reusables/package_registry/packages-billing.md,rendering error
+translations/ja-JP/data/reusables/package_registry/packages-billing.md,broken liquid tags
translations/ja-JP/data/reusables/package_registry/required-scopes.md,broken liquid tags
translations/ja-JP/data/reusables/pages/build-failure-email-server.md,broken liquid tags
translations/ja-JP/data/reusables/pages/emu-org-only.md,broken liquid tags
translations/ja-JP/data/reusables/pages/sidebar-pages.md,rendering error
translations/ja-JP/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
translations/ja-JP/data/reusables/projects/graphql-ghes.md,rendering error
-translations/ja-JP/data/reusables/pull_requests/configure_pull_request_merges_intro.md,rendering error
-translations/ja-JP/data/reusables/pull_requests/default_merge_option.md,rendering error
-translations/ja-JP/data/reusables/pull_requests/pull_request_merges_and_contributions.md,rendering error
-translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md,rendering error
+translations/ja-JP/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
+translations/ja-JP/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
+translations/ja-JP/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
+translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
translations/ja-JP/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
-translations/ja-JP/data/reusables/pull_requests/squash_and_merge_summary.md,rendering error
+translations/ja-JP/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/blocked-passwords.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/changed-files.md,broken liquid tags
-translations/ja-JP/data/reusables/repositories/deploy-keys.md,rendering error
+translations/ja-JP/data/reusables/repositories/deploy-keys.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/desktop-fork.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error
translations/ja-JP/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
-translations/ja-JP/data/reusables/repositories/navigate-to-repo.md,rendering error
+translations/ja-JP/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/repository-branches.md,rendering error
translations/ja-JP/data/reusables/repositories/sidebar-notifications.md,rendering error
translations/ja-JP/data/reusables/repositories/suggest-changes.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/you-can-fork.md,broken liquid tags
translations/ja-JP/data/reusables/rest-api/dotcom-only-guide-note.md,rendering error
translations/ja-JP/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
-translations/ja-JP/data/reusables/saml/about-linked-identities.md,rendering error
+translations/ja-JP/data/reusables/saml/about-linked-identities.md,broken liquid tags
translations/ja-JP/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags
translations/ja-JP/data/reusables/saml/authorized-creds-info.md,broken liquid tags
translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md,broken liquid tags
translations/ja-JP/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
translations/ja-JP/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
translations/ja-JP/data/reusables/scim/after-you-configure-saml.md,rendering error
-translations/ja-JP/data/reusables/scim/enterprise-account-scim.md,rendering error
-translations/ja-JP/data/reusables/scim/supported-idps.md,rendering error
+translations/ja-JP/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
+translations/ja-JP/data/reusables/scim/supported-idps.md,broken liquid tags
translations/ja-JP/data/reusables/search/syntax_tips.md,broken liquid tags
translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
translations/ja-JP/data/reusables/security-overview/permissions.md,rendering error
-translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md,rendering error
-translations/ja-JP/data/reusables/sponsors/select-sponsorship-billing.md,rendering error
+translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
+translations/ja-JP/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
translations/ja-JP/data/reusables/ssh/about-ssh.md,broken liquid tags
translations/ja-JP/data/reusables/ssh/key-type-support.md,rendering error
-translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,rendering error
-translations/ja-JP/data/reusables/support/help_resources.md,rendering error
+translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
+translations/ja-JP/data/reusables/support/help_resources.md,broken liquid tags
translations/ja-JP/data/reusables/support/submit-a-ticket.md,broken liquid tags
translations/ja-JP/data/reusables/user-settings/access_applications.md,rendering error
translations/ja-JP/data/reusables/user-settings/account_settings.md,rendering error
diff --git a/translations/log/msft-ko-resets.csv b/translations/log/msft-ko-resets.csv
index 66b00c1d0a..b1e9aa85e1 100644
--- a/translations/log/msft-ko-resets.csv
+++ b/translations/log/msft-ko-resets.csv
@@ -440,7 +440,6 @@ translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-pers
translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md,rendering error
translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,rendering error
translations/ko-KR/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md,rendering error
translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
@@ -457,7 +456,6 @@ translations/ko-KR/content/actions/deployment/deploying-to-your-cloud-provider/d
translations/ko-KR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,rendering error
translations/ko-KR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
translations/ko-KR/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md,rendering error
-translations/ko-KR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,rendering error
translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
translations/ko-KR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
@@ -773,6 +771,7 @@ translations/ko-KR/content/codespaces/getting-started/deep-dive.md,rendering err
translations/ko-KR/content/codespaces/getting-started/quickstart.md,rendering error
translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,rendering error
translations/ko-KR/content/codespaces/overview.md,rendering error
+translations/ko-KR/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md,rendering error
translations/ko-KR/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md,rendering error
translations/ko-KR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,rendering error
translations/ko-KR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,rendering error
@@ -784,6 +783,7 @@ translations/ko-KR/content/codespaces/troubleshooting/troubleshooting-prebuilds.
translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
translations/ko-KR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
translations/ko-KR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
+translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
translations/ko-KR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
translations/ko-KR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,rendering error
@@ -799,7 +799,7 @@ translations/ko-KR/content/developers/apps/building-github-apps/creating-a-githu
translations/ko-KR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error
translations/ko-KR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
translations/ko-KR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
-translations/ko-KR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error
+translations/ko-KR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,broken liquid tags
translations/ko-KR/content/developers/apps/building-oauth-apps/creating-a-custom-badge-for-your-oauth-app.md,rendering error
translations/ko-KR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md,rendering error
translations/ko-KR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
@@ -1056,7 +1056,7 @@ translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md,rend
translations/ko-KR/content/rest/guides/traversing-with-pagination.md,rendering error
translations/ko-KR/content/rest/guides/working-with-comments.md,rendering error
translations/ko-KR/content/rest/overview/api-previews.md,rendering error
-translations/ko-KR/content/rest/overview/breaking-changes.md,rendering error
+translations/ko-KR/content/rest/overview/breaking-changes.md,broken liquid tags
translations/ko-KR/content/rest/overview/other-authentication-methods.md,rendering error
translations/ko-KR/content/rest/overview/permissions-required-for-github-apps.md,rendering error
translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md,rendering error
@@ -1064,7 +1064,7 @@ translations/ko-KR/content/rest/packages.md,rendering error
translations/ko-KR/content/rest/quickstart.md,rendering error
translations/ko-KR/content/rest/scim.md,rendering error
translations/ko-KR/content/rest/teams/team-sync.md,rendering error
-translations/ko-KR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error
+translations/ko-KR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,broken liquid tags
translations/ko-KR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
translations/ko-KR/content/search-github/searching-on-github/searching-for-packages.md,rendering error
translations/ko-KR/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
@@ -1072,6 +1072,7 @@ translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponso
translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,rendering error
translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md,rendering error
translations/ko-KR/content/support/contacting-github-support/providing-data-to-github-support.md,rendering error
+translations/ko-KR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
translations/ko-KR/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
translations/ko-KR/content/support/learning-about-github-support/about-github-support.md,rendering error
translations/ko-KR/data/glossaries/external.yml,broken liquid tags
@@ -1094,7 +1095,9 @@ translations/ko-KR/data/release-notes/enterprise-server/3-4/7.yml,rendering erro
translations/ko-KR/data/release-notes/enterprise-server/3-4/8.yml,rendering error
translations/ko-KR/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
translations/ko-KR/data/release-notes/enterprise-server/3-5/4.yml,rendering error
+translations/ko-KR/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
translations/ko-KR/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
+translations/ko-KR/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
translations/ko-KR/data/reusables/accounts/create-personal-access-tokens.md,rendering error
translations/ko-KR/data/reusables/actions/about-actions-for-enterprises.md,rendering error
translations/ko-KR/data/reusables/actions/apply-configuration-and-enable.md,rendering error
@@ -1116,7 +1119,7 @@ translations/ko-KR/data/reusables/actions/moving-a-runner-to-a-group.md,renderin
translations/ko-KR/data/reusables/actions/onboarding-next-steps.md,rendering error
translations/ko-KR/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
translations/ko-KR/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
-translations/ko-KR/data/reusables/actions/reusable-workflows-ghes-beta.md,rendering error
+translations/ko-KR/data/reusables/actions/reusable-workflows-enterprise-beta.md,rendering error
translations/ko-KR/data/reusables/actions/reusable-workflows.md,rendering error
translations/ko-KR/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
translations/ko-KR/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
@@ -1244,7 +1247,7 @@ translations/ko-KR/data/reusables/organizations/github-apps-settings-sidebar.md,
translations/ko-KR/data/reusables/organizations/member-privileges.md,rendering error
translations/ko-KR/data/reusables/organizations/navigate-to-org.md,rendering error
translations/ko-KR/data/reusables/organizations/repository-defaults.md,rendering error
-translations/ko-KR/data/reusables/organizations/require-ssh-cert.md,rendering error
+translations/ko-KR/data/reusables/organizations/require-ssh-cert.md,broken liquid tags
translations/ko-KR/data/reusables/organizations/restricted-app-access-requests.md,rendering error
translations/ko-KR/data/reusables/organizations/security-and-analysis.md,rendering error
translations/ko-KR/data/reusables/organizations/security.md,rendering error
diff --git a/translations/log/msft-pt-resets.csv b/translations/log/msft-pt-resets.csv
index 8dc283a3a0..ac00ce124c 100644
--- a/translations/log/msft-pt-resets.csv
+++ b/translations/log/msft-pt-resets.csv
@@ -368,6 +368,7 @@ translations/pt-BR/data/reusables/actions/hardware-requirements-3.6.md,file dele
translations/pt-BR/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main
translations/pt-BR/data/reusables/actions/minio-gateways-removal.md,file deleted because it no longer exists in main
translations/pt-BR/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md,file deleted because it no longer exists in main
translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main
translations/pt-BR/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md,file deleted because it no longer exists in main
translations/pt-BR/data/reusables/apps/metadata-permissions.md,file deleted because it no longer exists in main
@@ -1007,6 +1008,7 @@ translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md,re
translations/pt-BR/data/reusables/actions/github-connect-resolution.md,rendering error
translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags
+translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md,broken liquid tags
translations/pt-BR/data/reusables/actions/more-resources-for-ghes.md,rendering error
translations/pt-BR/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
translations/pt-BR/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
diff --git a/translations/log/msft-ru-resets.csv b/translations/log/msft-ru-resets.csv
index 82e72b5311..f4a0aee22b 100644
--- a/translations/log/msft-ru-resets.csv
+++ b/translations/log/msft-ru-resets.csv
@@ -414,6 +414,7 @@ translations/ru-RU/data/reusables/rest-reference/actions/workflows.md,file delet
translations/ru-RU/data/reusables/rest-reference/activity/feeds.md,file deleted because it no longer exists in main
translations/ru-RU/data/reusables/rest-reference/activity/watching.md,file deleted because it no longer exists in main
translations/ru-RU/data/reusables/rest-reference/apps/installations.md,file deleted because it no longer exists in main
+translations/ru-RU/data/reusables/rest-reference/apps/oauth-applications.md,file deleted because it no longer exists in main
translations/ru-RU/data/reusables/rest-reference/apps/webhooks.md,file deleted because it no longer exists in main
translations/ru-RU/data/reusables/rest-reference/billing/billing.md,file deleted because it no longer exists in main
translations/ru-RU/data/reusables/rest-reference/branches/branch-protection.md,file deleted because it no longer exists in main
@@ -494,7 +495,6 @@ translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-pers
translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md,rendering error
translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,rendering error
translations/ru-RU/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md,rendering error
translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
@@ -558,7 +558,6 @@ translations/ru-RU/content/admin/code-security/managing-github-advanced-security
translations/ru-RU/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,rendering error
translations/ru-RU/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,rendering error
translations/ru-RU/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
-translations/ru-RU/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,rendering error
translations/ru-RU/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,rendering error
translations/ru-RU/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error
translations/ru-RU/content/admin/configuration/configuring-github-connect/index.md,rendering error
@@ -584,13 +583,12 @@ translations/ru-RU/content/admin/configuration/configuring-your-enterprise/confi
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
-translations/ru-RU/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
translations/ru-RU/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
translations/ru-RU/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
translations/ru-RU/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
translations/ru-RU/content/admin/enterprise-management/caching-repositories/index.md,rendering error
-translations/ru-RU/content/admin/enterprise-management/configuring-clustering/about-clustering.md,rendering error
+translations/ru-RU/content/admin/enterprise-management/configuring-clustering/about-clustering.md,broken liquid tags
translations/ru-RU/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,rendering error
translations/ru-RU/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,rendering error
translations/ru-RU/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md,rendering error
@@ -630,7 +628,7 @@ translations/ru-RU/content/admin/identity-and-access-management/using-cas-for-en
translations/ru-RU/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
translations/ru-RU/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
translations/ru-RU/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
-translations/ru-RU/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
+translations/ru-RU/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,broken liquid tags
translations/ru-RU/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
translations/ru-RU/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,rendering error
translations/ru-RU/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md,rendering error
@@ -829,6 +827,7 @@ translations/ru-RU/content/codespaces/troubleshooting/troubleshooting-your-conne
translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
translations/ru-RU/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
translations/ru-RU/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
+translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
translations/ru-RU/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
translations/ru-RU/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,rendering error
@@ -1146,6 +1145,7 @@ translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponso
translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,rendering error
translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,rendering error
translations/ru-RU/content/support/contacting-github-support/providing-data-to-github-support.md,rendering error
+translations/ru-RU/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
translations/ru-RU/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
translations/ru-RU/content/support/learning-about-github-support/about-github-support.md,rendering error
translations/ru-RU/data/glossaries/external.yml,broken liquid tags
@@ -1168,7 +1168,9 @@ translations/ru-RU/data/release-notes/enterprise-server/3-4/7.yml,rendering erro
translations/ru-RU/data/release-notes/enterprise-server/3-4/8.yml,rendering error
translations/ru-RU/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
translations/ru-RU/data/release-notes/enterprise-server/3-5/4.yml,rendering error
+translations/ru-RU/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
translations/ru-RU/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
+translations/ru-RU/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
translations/ru-RU/data/reusables/accounts/create-personal-access-tokens.md,rendering error
translations/ru-RU/data/reusables/actions/about-actions-for-enterprises.md,rendering error
translations/ru-RU/data/reusables/actions/actions-do-not-trigger-workflows.md,broken liquid tags
@@ -1194,7 +1196,7 @@ translations/ru-RU/data/reusables/actions/moving-a-runner-to-a-group.md,renderin
translations/ru-RU/data/reusables/actions/onboarding-next-steps.md,rendering error
translations/ru-RU/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
translations/ru-RU/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
-translations/ru-RU/data/reusables/actions/reusable-workflows-ghes-beta.md,rendering error
+translations/ru-RU/data/reusables/actions/reusable-workflows-enterprise-beta.md,rendering error
translations/ru-RU/data/reusables/actions/reusable-workflows.md,rendering error
translations/ru-RU/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
translations/ru-RU/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
index 382e81006b..f54adf093a 100644
--- a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
@@ -94,7 +94,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
shell: bash
```
{% endraw %}
- This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+ This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, adds the action's path to the runner system path (to locate the `goodbye.sh` script during execution), and runs the `goodbye.sh` script.
For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
index bdf5bb0bfb..9217298a2a 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
@@ -811,7 +811,7 @@ The `inputs` context contains input properties passed to an action{% ifversion a
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
| Property name | Type | Description |
|---------------|------|-------------|
diff --git a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0d316eca1f..397d51b308 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -88,7 +88,7 @@ In addition to the usage limits, you must ensure that you use {% data variables.
{% ifversion fpt or ghes > 3.3 or ghec %}
## Billing for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
diff --git a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md
index 2adee6a3f4..1cc0d2d002 100644
--- a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
---
{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
## Overview
diff --git a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
index 8e4adb430f..837875fe9e 100644
--- a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
@@ -123,7 +123,7 @@ You can use activity types and filters to further control when your workflow wil
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 4969f6b53e..e6e11c2ff5 100644
--- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -72,7 +72,7 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `on.workflow_call`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
@@ -320,7 +320,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+You can use the `if` conditional to prevent a step from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
@@ -945,7 +945,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `jobs..uses`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 625a34aa98..c01ecca7a2 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 571de5c750..b2348bc546 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -67,7 +67,9 @@ The storage used by a repository is the total storage used by {% data variables.
### Per-minute rates
{% data reusables.billing.billing-standard-runners %}
-{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
+{%- ifversion actions-hosted-runners %}
+{% data reusables.billing.billing-hosted-runners %}
+{%- endif %}
- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
- {% data reusables.user-settings.context_switcher %}
diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 93e7515005..1193172cdd 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,18 +1,10 @@
----
-ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
-ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145094356"
----
-Use o condicional `jobs..if` para impedir que um trabalho seja executado, a não ser que uma condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional.
+You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
-{% data reusables.actions.expression-syntax-if %} Para obter mais informações, confira "[Expressões](/actions/learn-github-actions/expressions)".
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
-### Exemplo: Somente executar o trabalho para um repositório específico
+### Example: Only run job for specific repository
-Este exemplo usa `if` para controlar quando o trabalho `production-deploy` pode ser executado. Ele só será executado se o repositório for chamado `octo-repo-prod` e estiver na organização `octo-org`. Caso contrário, o trabalho será marcado como _ignorado_.
+This example uses `if` to control when the `production-deploy` job can run. It will only run if the repository is named `octo-repo-prod` and is within the `octo-org` organization. Otherwise, the job will be marked as _skipped_.
```yaml{:copy}
name: example-workflow
diff --git a/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md
deleted file mode 100644
index fff36abb7c..0000000000
--- a/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-ms.openlocfilehash: 933805023c32c3e956b510000cdaff7326b880e3
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145065384"
----
-{% ifversion ghes = 3.4 %}
-
-{% note %}
-
-**Observação**: atualmente, os fluxos de trabalho reutilizáveis estão em versão beta e sujeitos a alterações.
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/ru-RU/content/actions/creating-actions/about-custom-actions.md b/translations/ru-RU/content/actions/creating-actions/about-custom-actions.md
index 47f249c613..4f0d69ab7f 100644
--- a/translations/ru-RU/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/ru-RU/content/actions/creating-actions/about-custom-actions.md
@@ -16,12 +16,12 @@ type: overview
topics:
- Action development
- Fundamentals
-ms.openlocfilehash: ac933a5014750f75373fafa7f8dd52333b79a469
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
+ms.openlocfilehash: 1e81bea551ceff1980b0bbe96202f60db0d0e7f2
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: MT
ms.contentlocale: ru-RU
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147154576'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191949'
---
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
@@ -35,7 +35,7 @@ ms.locfileid: '147154576'
## Типы действий
-Вы можете создать контейнер Docker и действия JavaScript. Для действий требуется файл метаданных, чтобы определить входные и выходные данные, а также основную точку входа для действия. Файл метаданных должен иметь имя `action.yml` либо `action.yaml`. Дополнительные сведения см. в разделе [Синтаксис метаданных для {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions).
+Вы можете создавать контейнер Docker, JavaScript и составные действия. Для действий требуется файл метаданных, чтобы определить входные и выходные данные, а также основную точку входа для действия. Файл метаданных должен иметь имя `action.yml` либо `action.yaml`. Дополнительные сведения см. в разделе [Синтаксис метаданных для {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions).
| Тип | Операционная система |
| ---- | ------------------- |
diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md
index 382e81006b..d9d7ae543c 100644
--- a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md
@@ -1,7 +1,7 @@
---
-title: Creating a composite action
+title: Создание составного действия
shortTitle: Create a composite action
-intro: 'In this guide, you''ll learn how to build a composite action.'
+intro: В этом руководстве приведены инструкции по созданию составного действия.
redirect_from:
- /actions/creating-actions/creating-a-composite-run-steps-action
versions:
@@ -12,58 +12,61 @@ versions:
type: tutorial
topics:
- Action development
+ms.openlocfilehash: 5c7d332d2b3626a5628e85b09c35ffa6a0ca5f33
+ms.sourcegitcommit: 4f08a208a0d2e13dc109678750a962ea2f67e1ba
+ms.translationtype: MT
+ms.contentlocale: ru-RU
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148192042'
---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## Введение
-## Introduction
+В этом руководстве вы узнаете об основных компонентах, необходимых для создания и использования упакованного составного действия. Чтобы сосредоточиться в этом руководстве на компонентах, необходимых для пакета действия, функциональность кода действия будет минимальна. Действие выведет текст Hello World, а затем — Goodbye, или, если вы укажете пользовательское имя, оно выведет Hello [who-to-greet], а затем — Goodbye. Действие также сопоставляет случайное число с выходной переменной `random-number` и запускает сценарий с именем `goodbye.sh`.
-In this guide, you'll learn about the basic components needed to create and use a packaged composite action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" and then "Goodbye", or if you provide a custom name, it prints "Hello [who-to-greet]" and then "Goodbye". The action also maps a random number to the `random-number` output variable, and runs a script named `goodbye.sh`.
-
-Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
+Завершив этот проект, вы узнаете, как создать собственное составное действие и протестировать его в рабочем процессе.
{% data reusables.actions.context-injection-warning %}
-## Prerequisites
+## Предварительные требования
-Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+Перед началом работы создайте репозиторий в {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
-1. Create a new public repository on {% data variables.location.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. Создайте общедоступный репозиторий в {% data variables.location.product_location %}. Вы можете выбрать любое имя репозитория или использовать следующий пример: `hello-world-composite-action`. Эти файлы можно добавить после отправки проекта в {% data variables.product.product_name %}. Дополнительные сведения см. в статье [Создание репозитория](/articles/creating-a-new-repository).
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. Клонируйте репозиторий на ваш компьютер. Дополнительные сведения см. в разделе [Клонирование репозитория](/articles/cloning-a-repository).
-1. From your terminal, change directories into your new repository.
+1. В окне терминала перейдите в новый репозиторий.
```shell
cd hello-world-composite-action
```
-2. In the `hello-world-composite-action` repository, create a new file called `goodbye.sh`, and add the following example code:
+2. В репозитории `hello-world-composite-action` создайте файл под названием `goodbye.sh` и добавьте следующий пример кода:
```bash
echo "Goodbye"
```
-3. From your terminal, make `goodbye.sh` executable.
+3. В окне терминала сделайте `goodbye.sh` исполняемым файлом.
```shell
chmod +x goodbye.sh
```
-1. From your terminal, check in your `goodbye.sh` file.
+1. В окне терминала зарегистрируйте файл `goodbye.sh`.
```shell
git add goodbye.sh
git commit -m "Add goodbye script"
git push
```
-## Creating an action metadata file
+## Создание файла метаданных действия
-1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
+1. В репозитории `hello-world-composite-action` создайте файл под названием `action.yml` и добавьте следующий пример кода. Дополнительные сведения об этом синтаксисе см. в разделе [`runs` для составных действий](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions).
- {% raw %}
- **action.yml**
+ {% raw %} **action.yml**
```yaml
name: 'Hello World'
description: 'Greet someone'
@@ -93,14 +96,13 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
- run: goodbye.sh
shell: bash
```
- {% endraw %}
- This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+ {% endraw %} Этот файл определяет входные данные, сопоставляет `who-to-greet` случайно созданное число с `random-number` выходной переменной, добавляет путь действия в системный путь средства выполнения (чтобы найти `goodbye.sh` скрипт во время выполнения) и запускает `goodbye.sh` скрипт.
- For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
+ Дополнительные сведения об управлении выходными данными см. в разделе [`outputs` для составного действия](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions).
- For more information about how to use `github.action_path`, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+ Дополнительные сведения об использовании `github.action_path` см. в разделе [`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context).
-1. From your terminal, check in your `action.yml` file.
+1. В окне терминала зарегистрируйте файл `action.yml`.
```shell
git add action.yml
@@ -108,18 +110,18 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
git push
```
-1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+1. В окне терминала добавьте тег. В этом примере используется тег под названием `v1`. Дополнительные сведения см. в статье [Сведения о действиях](/actions/creating-actions/about-actions#using-release-management-for-actions).
```shell
git tag -a -m "Description of this release" v1
git push --follow-tags
```
-## Testing out your action in a workflow
+## Тестирование действия в рабочем процессе
-The following workflow code uses the completed hello world action that you made in "[Creating an action metadata file](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
+В следующем коде рабочего процесса используется завершенное действие hello world, выполненное в разделе [Создание файла метаданных действия](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file).
-Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name.
+Скопируйте код рабочего процесса в файл `.github/workflows/main.yml` в другом репозитории, но замените `actions/hello-world-composite-action@v1` репозиторием и тегом, который вы создали. Вы также можете заменить ввод `who-to-greet` своим именем.
**.github/workflows/main.yml**
```yaml
@@ -139,4 +141,4 @@ jobs:
shell: bash
```
-From your repository, click the **Actions** tab, and select the latest workflow run. The output should include: "Hello Mona the Octocat", the result of the "Goodbye" script, and a random number.
+В репозитории перейдите на вкладку **Actions** (Действия) и выберите последний запуск рабочего процесса. Выходные данные должны включать: Hello Mona the Octocat, результат сценария Goodbye и случайное число.
diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md
index 5a1ea071a9..8dcb762313 100644
--- a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md
@@ -271,3 +271,10 @@ jobs:
From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+
+## Template repositories for creating JavaScript actions
+
+{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
+
+* [`javascript-action` template repository](https://github.com/actions/javascript-action)
+* [`typescript-action` template repository](https://github.com/actions/typescript-action)
diff --git a/translations/ru-RU/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/ru-RU/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index 30c0ee6762..0d240ae768 100644
--- a/translations/ru-RU/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/ru-RU/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -283,6 +283,12 @@ After this setting is applied, the JWT will contain the updated `iss` value. In
To help improve security, compliance, and standardization, you can customize the standard claims to suit your required access conditions. If your cloud provider supports conditions on subject claims, you can create a condition that checks whether the `sub` value matches the path of the reusable workflow, such as `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`. The exact format will vary depending on your cloud provider's OIDC configuration. To configure the matching condition on {% data variables.product.prodname_dotcom %}, you can can use the REST API to require that the `sub` claim must always include a specific custom claim, such as `job_workflow_ref`. You can use the [OIDC REST API](/rest/actions/oidc) to apply a customization template for the OIDC subject claim; for example, you can require that the `sub` claim within the OIDC token must always include a specific custom claim, such as `job_workflow_ref`.
+{% note %}
+
+**Note**: When the organization template is applied, it will not affect any workflows in existing repositories that already use OIDC. For existing repositories, as well as any new repositories that are created after the template has been applied, the repository owner will need to opt-in to receive this configuration, or alternatively could apply a different configuration specific to the repo. For more information, see "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)."
+
+{% endnote %}
+
Customizing the claims results in a new format for the entire `sub` claim, which replaces the default predefined `sub` format in the token described in "[Example subject claims](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims)."
The following example templates demonstrate various ways to customize the subject claim. To configure these settings on {% data variables.product.prodname_dotcom %}, admins use the REST API to specify a list of claims that must be included in the subject (`sub`) claim.
@@ -291,12 +297,6 @@ The following example templates demonstrate various ways to customize the subjec
To customize your subject claims, you should first create a matching condition in your cloud provider's OIDC configuration, before customizing the configuration using the REST API. Once the configuration is completed, each time a new job runs, the OIDC token generated during that job will follow the new customization template. If the matching condition doesn't exist in the cloud provider's OIDC configuration before the job runs, the generated token might not be accepted by the cloud provider, since the cloud conditions may not be synchronized.
-{% note %}
-
-**Note**: When the organization template is applied, it will not affect any action workflows in existing repositories that already use OIDC. For existing repositories, as well as any new repositories that are created after the template has been applied, the repository owner will need to opt-in to receive this configuration, or alternatively could apply a different configuration specific to the repo. For more information, see "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)."
-
-{% endnote %}
-
#### Example: Allowing repository based on visibility and owner
This example template allows the `sub` claim to have a new format, using `repository_owner` and `repository_visibility`:
@@ -431,7 +431,9 @@ In your cloud provider's OIDC configuration, configure the `sub` condition to re
#### Using the default subject claims
-For repositories that can receive a subject claim policy from their organization, the repository owner can later choose to opt-out and instead use the default `sub` claim format. To configure this, the repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
+For repositories that can receive a subject claim policy from their organization, the repository owner can later choose to opt-out and instead use the default `sub` claim format. This means that the repository will not use the organization's customized template.
+
+To configure the repository to use the default `sub` claim format, a repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
```json
{
@@ -439,6 +441,18 @@ For repositories that can receive a subject claim policy from their organization
}
```
+#### Example: Configuring a repository to use an organization template
+
+A repository administrator can configure their repository to use the template created by the administrator of their organisation.
+
+To configure the repository to use the organization's template, a repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
+
+```json
+{
+ "use_default": false
+}
+```
+
{% endif %}
## Updating your workflows for OIDC
diff --git a/translations/ru-RU/content/actions/learn-github-actions/contexts.md b/translations/ru-RU/content/actions/learn-github-actions/contexts.md
index bdf5bb0bfb..9217298a2a 100644
--- a/translations/ru-RU/content/actions/learn-github-actions/contexts.md
+++ b/translations/ru-RU/content/actions/learn-github-actions/contexts.md
@@ -811,7 +811,7 @@ The `inputs` context contains input properties passed to an action{% ifversion a
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
| Property name | Type | Description |
|---------------|------|-------------|
diff --git a/translations/ru-RU/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ru-RU/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0d316eca1f..397d51b308 100644
--- a/translations/ru-RU/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/ru-RU/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -88,7 +88,7 @@ In addition to the usage limits, you must ensure that you use {% data variables.
{% ifversion fpt or ghes > 3.3 or ghec %}
## Billing for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
diff --git a/translations/ru-RU/content/actions/using-workflows/reusing-workflows.md b/translations/ru-RU/content/actions/using-workflows/reusing-workflows.md
index 2adee6a3f4..1cc0d2d002 100644
--- a/translations/ru-RU/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/ru-RU/content/actions/using-workflows/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
---
{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
## Overview
diff --git a/translations/ru-RU/content/actions/using-workflows/triggering-a-workflow.md b/translations/ru-RU/content/actions/using-workflows/triggering-a-workflow.md
index 8e4adb430f..837875fe9e 100644
--- a/translations/ru-RU/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/ru-RU/content/actions/using-workflows/triggering-a-workflow.md
@@ -123,7 +123,7 @@ You can use activity types and filters to further control when your workflow wil
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
diff --git a/translations/ru-RU/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/ru-RU/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 4969f6b53e..e6e11c2ff5 100644
--- a/translations/ru-RU/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/ru-RU/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -72,7 +72,7 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `on.workflow_call`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
@@ -320,7 +320,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+You can use the `if` conditional to prevent a step from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
@@ -945,7 +945,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `jobs..uses`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
diff --git a/translations/ru-RU/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/ru-RU/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
index c4156846ca..86b39b9fa9 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
@@ -1,6 +1,6 @@
---
-title: Enabling Server Statistics for your enterprise
-intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.'
+title: Включение статистики сервера для предприятия
+intro: 'Вы можете анализировать собственные статистические данные из {% data variables.product.prodname_ghe_server %} и помочь нам улучшить продукты {% data variables.product.company_short %}, включив {% data variables.product.prodname_server_statistics %}.'
versions:
feature: server-statistics
redirect_from:
@@ -8,23 +8,27 @@ redirect_from:
topics:
- Enterprise
shortTitle: Server Statistics
+ms.openlocfilehash: 125651de793a45240008de34845762e6de637040
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: MT
+ms.contentlocale: ru-RU
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191873'
---
+## Сведения о {% data variables.product.prodname_server_statistics %}
-## About {% data variables.product.prodname_server_statistics %}
+{% data variables.product.prodname_server_statistics %} собирает статистические данные об использовании из {% data variables.location.product_location %}, которые можно использовать для лучшего прогнозирования потребностей организации, понимания принципов работы команды и отображения ценности, которую вы получаете от {% data variables.product.prodname_ghe_server %}.
-{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
+{% data variables.product.prodname_server_statistics %} собирает только определенные статистические метрики в репозиториях, проблемах, запросах на вытягивание и других функциях. Содержимое {% data variables.product.prodname_dotcom %}, например код, проблемы, комментарии или содержимое запроса на вытягивание, не собирается. Дополнительную информацию см. в разделе [Сведения о {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics).
-{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+Включив {% data variables.product.prodname_server_statistics %}, вы также помогаете улучшить {% data variables.product.company_short %}. Агрегированные данные, которые вы предоставите, помогут нам понять, как наши клиенты используют {% data variables.product.prodname_dotcom %}, и принимать более целесообразные и обоснованные решения о продукте, в конечном итоге получая выгоду.
-By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
+## Включение {% data variables.product.prodname_server_statistics %}
-## Enabling {% data variables.product.prodname_server_statistics %}
+Прежде чем включить {% data variables.product.prodname_server_statistics %}, необходимо сначала подключить экземпляр {% data variables.product.prodname_ghe_server %} к {% data variables.product.prodname_dotcom_the_website %} через {% data variables.product.prodname_github_connect %}. Дополнительные сведения см. в разделе [Подключение {% data variables.product.prodname_ghe_server %} к {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud).
-Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Можно отключить {% data variables.product.prodname_server_statistics %} из {% data variables.product.prodname_ghe_server %} в любое время.
-You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time.
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**.
- 
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
+4. В разделе "Общий доступ к статистике сервера с помощью GitHub.com" выберите раскрывающееся меню и щелкните **Включено** или **Отключено**.
+ 
diff --git a/translations/ru-RU/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/ru-RU/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 98a84270fb..1e67bc7da9 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
+
| Path without subdomain isolation | Path with subdomain isolation |
| --- | --- |
-| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
-| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
-| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
-| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
-| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
-| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
-| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
+| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
+| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
+| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
+| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
+| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
{%- ifversion viewscreen-and-notebooks %}
-| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
-| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
-{%- else %}
-| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
+| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+{%- ifversion ghes < 3.7 %}
+| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
+| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
+{%- ifversion viewscreen-and-notebooks %}
+| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
+{%- endif %}
+{%- ifversion ghes > 3.4 %}
+| Not supported | `https://containers.HOSTNAME/` |
{%- endif %}
-| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
-| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %}
-| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported | `https://containers.HOSTNAME/` |{% endif %}
## Prerequisites
diff --git a/translations/ru-RU/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md b/translations/ru-RU/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
index 4eb59cf491..8ebeb41808 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
@@ -1,7 +1,7 @@
---
-title: Restricting network traffic to your enterprise with an IP allow list
+title: Ограничение сетевого трафика для предприятия с помощью списка разрешенных IP-адресов
shortTitle: Restricting network traffic
-intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
+intro: Вы можете ограничить доступ к организации и разрешить доступ к ресурсам только с указанных IP-адресов с помощью списка разрешенных IP-адресов.
permissions: Enterprise owners can configure IP allow lists.
miniTocMaxHeadingLevel: 3
versions:
@@ -17,192 +17,154 @@ topics:
redirect_from:
- /admin/configuration/restricting-network-traffic-to-your-enterprise
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
+ms.openlocfilehash: 8511499e723fdeb4a2d24c2fce627bce56ad9777
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: MT
+ms.contentlocale: ru-RU
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191897'
---
+## Сведения об ограничениях сетевого трафика
-## About network traffic restrictions
-
-By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+По умолчанию авторизованные пользователи могут получить доступ к предприятию с любого IP-адреса. Вы можете ограничить доступ к ресурсам {% ifversion ghec %}, принадлежащим организациям в корпоративной учетной записи {% endif %}, настроив список разрешений для определенных IP-адресов. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
{% ifversion ghec %}
-If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
+Если ваше предприятие использует {% data variables.product.prodname_emus %} с Azure AD и OIDC, вы можете выбрать, следует ли использовать функцию списка разрешенных IP-адресов {% data variables.product.company_short %} или использовать ограничения списка разрешений для поставщика удостоверений (IdP). Если ваше предприятие не использует {% data variables.product.prodname_emus %} с Azure и OIDC, можно использовать функцию списка разрешений {% data variables.product.company_short %}.
{% elsif ghae %}
-By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
+По умолчанию правила группы безопасности сети (NSG) Azure оставляют весь входящий трафик открытым на портах 22, 80, 443 и 25. Вы можете связаться с {% data variables.contact.github_support %}, чтобы настроить ограничения доступа для {% data variables.product.product_name %}.
-For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+Чтобы ограничить использование групп безопасности сети Azure, обратитесь в {% data variables.contact.github_support %} с IP-адресами, которым должен быть разрешен доступ к {% data variables.product.product_name %}. Укажите диапазоны адресов, используя стандартный формат CIDR (бесклассовая междоменная маршрутизация). {% data variables.contact.github_support %} настроит соответствующие правила брандмауэра, чтобы ограничить сетевой доступ по протоколам HTTP, SSH, HTTPS и SMTP. Дополнительные сведения см. в разделе [Получение помощи от {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support).
{% endif %}
{% ifversion ghec %}
-## About {% data variables.product.company_short %}'s IP allow list
+## Сведения о списке разрешенных IP-адресов {% data variables.product.company_short %}
-You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
+Список разрешенных IP-адресов {% data variables.product.company_short %} можно использовать для управления доступом к предприятию и ресурсам, принадлежащим организациям предприятия.
{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
-## About your IdP's allow list
+## Сведения о списке разрешений поставщика удостоверений
-If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
+Если вы используете {% data variables.product.prodname_emus %} с Azure AD и OIDC, можно использовать список разрешений поставщика удостоверений.
-Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
+Использование списка разрешений поставщика удостоверений отключает конфигурации списка разрешений IP-адресов {% data variables.product.company_short %} для всех организаций на предприятии и отключает API GraphQL для включения списков разрешенных IP-адресов и управления ими.
-By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
+По умолчанию поставщик удостоверений запускает CAP при начальном интерактивном входе SAML или OIDC в {% data variables.product.company_short %} для любой выбранной конфигурации списка разрешенных IP-адресов.
-The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps)."
+OIDC CAP применяется только к запросам к API с использованием маркера "пользователь—сервер", например маркера для {% data variables.product.prodname_oauth_app %} или {% data variables.product.prodname_github_app %}, действующего от имени пользователя. Cap OIDC не применяется, если {% data variables.product.prodname_github_app %} использует токен "сервер-сервер". Дополнительные сведения см. в разделах [Проверка подлинности с помощью {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)и [Сведения о поддержке политики условного доступа поставщиков удостоверений](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps).
-To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
+Чтобы обеспечить беспроблемное использование OIDC CAP при одновременном применении политики к маркерам от пользователя к серверу, необходимо скопировать все диапазоны IP-адресов из каждого {% data variables.product.prodname_github_app %}, который использует ваше предприятие, в политику поставщика удостоверений.
-## Using {% data variables.product.company_short %}'s IP allow list
+## Использование списка разрешенных IP-адресов {% data variables.product.company_short %}
-### Enabling {% data variables.product.company_short %}'s IP allow list
-{% data reusables.profile.access_org %}
-{% data reusables.profile.org_settings %}
-{% data reusables.organizations.security %}
-1. Under "IP allow list", enable the IP allow list.
- - If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
- 
+### Включение списка разрешенных IP-адресов {% data variables.product.company_short %}
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
+1. В разделе "Список разрешенных IP-адресов" включите список разрешенных IP-адресов.
+ - Если вы используете {% data variables.product.prodname_emus %} с OIDC, выберите раскрывающееся меню и щелкните **GitHub**.
+ 
- Select **Enable IP allow list**.
- 
+ Выберите **Включить список разрешенных IP-адресов**.
+ 
- - If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
- 
-1. Click **Save**.
+ - Если вы не используете {% data variables.product.prodname_emus %} с OIDC, выберите **Включить список разрешенных IP-адресов**.
+ 
+1. Выберите команду **Сохранить**.
-### Adding an allowed IP address
+### Добавление разрешенного IP-адреса
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
{% data reusables.identity-and-permissions.ipv6-allow-lists %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
-{% data reusables.identity-and-permissions.check-ip-address %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
-### Allowing access by {% data variables.product.prodname_github_apps %}
+### Разрешение доступа {% data variables.product.prodname_github_apps %}
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
-### Editing an allowed IP address
+### Изменение разрешенного IP-адреса
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+8. Нажмите кнопку **Обновить**.
{% data reusables.identity-and-permissions.check-ip-address %}
-### Checking if an IP address is permitted
+### Проверка допустимости IP-адреса
{% data reusables.identity-and-permissions.about-checking-ip-address %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
-### Deleting an allowed IP address
+### Удаление разрешенного IP-адреса
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
-## Using your identity provider's allow list
+## Использование списка разрешений поставщика удостоверений
{% note %}
-**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
+**Примечание:** Использование списка разрешений поставщика удостоверений поддерживается только для {% data variables.product.prodname_emus %} с Azure AD и OIDC.
{% endnote %}
-{% data reusables.profile.access_org %}
-{% data reusables.profile.org_settings %}
-{% data reusables.organizations.security %}
-1. Under "IP allow list", select the dropdown and click **Identity Provider**.
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
+1. В разделе "Список разрешенных IP-адресов" выберите раскрывающийся список и щелкните **Поставщик удостоверений**.
- 
-1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
+ 
+1. При необходимости, чтобы разрешить установленным {% data variables.product.company_short %} и {% data variables.product.prodname_oauth_apps %} доступ к организации с любого IP-адреса, выберите **Пропустить проверку поставщика удостоверений для приложений**.
- 
-1. Click **Save**.
+ 
+1. Выберите команду **Сохранить**.
{% endif %}
{% ifversion ghae %}
-## Enabling allowed IP addresses
+## Включение разрешенных IP-адресов
{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-1. Under "IP allow list", select **Enable IP allow list**.
- 
-4. Click **Save**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
+1. В разделе "Список разрешенных IP-адресов" выберите **Включить список разрешенных IP-адресов**.
+ 
+4. Выберите команду **Сохранить**.
-## Adding an allowed IP address
+## Добавление разрешенного IP-адреса
-{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
-{% data reusables.identity-and-permissions.check-ip-address %}
+{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## Разрешение доступа {% data variables.product.prodname_github_apps %}
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
-## Editing an allowed IP address
+## Изменение разрешенного IP-адреса
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+8. Нажмите кнопку **Обновить**.
{% data reusables.identity-and-permissions.check-ip-address %}
-## Checking if an IP address is permitted
+## Проверка допустимости IP-адреса
{% data reusables.identity-and-permissions.about-checking-ip-address %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
-## Deleting an allowed IP address
+## Удаление разрешенного IP-адреса
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
{% endif %}
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## Использование {% data variables.product.prodname_actions %} со списком разрешенных IP-адресов
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 625a34aa98..c01ecca7a2 100644
--- a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}
diff --git a/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 991873cdca..041431c2e8 100644
--- a/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -56,7 +56,7 @@ You can enforce policies to control how members of your enterprise on {% data va
Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% ifversion ghes or ghae %}
@@ -166,7 +166,7 @@ Across all organizations owned by your enterprise, you can set the default branc
Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 571de5c750..b2348bc546 100644
--- a/translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -67,7 +67,9 @@ The storage used by a repository is the total storage used by {% data variables.
### Per-minute rates
{% data reusables.billing.billing-standard-runners %}
-{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
+{%- ifversion actions-hosted-runners %}
+{% data reusables.billing.billing-hosted-runners %}
+{%- endif %}
- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
- {% data reusables.user-settings.context_switcher %}
diff --git a/translations/ru-RU/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/translations/ru-RU/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
index e3833fc241..58ffc07bfa 100644
--- a/translations/ru-RU/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
+++ b/translations/ru-RU/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
@@ -9,26 +9,26 @@ topics:
- Codespaces
redirect_from:
- /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds
-ms.openlocfilehash: e0962e410f2227a23ff98c8a3e7995ea8ec8a914
-ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.openlocfilehash: eecb77b541cc735fcf788fbc5da6960cabad899d
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: MT
ms.contentlocale: ru-RU
-ms.lasthandoff: 11/09/2022
-ms.locfileid: '148158800'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191921'
---
-## Общие сведения
+## Обзор
{% data reusables.codespaces.prebuilds-definition %}
-Если в настоящее время создание codespace для репозитория занимает более 2 минут, вы, скорее всего, выиграете от использования предварительных сборок. Это связано с тем, что в предварительной сборке любой исходный код, расширения редактора, зависимости проекта, команды и конфигурации уже скачаны, установлены и применены перед созданием codespace.
+Если в настоящее время создание codespace для репозитория занимает более 2 минут, вы, скорее всего, выиграете от использования предварительных сборок. Это связано с тем, что в предварительной сборке любой исходный код, расширения редактора, зависимости проекта, команды и конфигурации уже были скачаны, установлены и применены перед созданием codespace.
По умолчанию всякий раз при отправке изменения в репозиторий {% data variables.product.prodname_github_codespaces %} использует {% data variables.product.prodname_actions %} для автоматического обновления предварительных сборок.
-Если для определенной ветви репозитория, файла конфигурации контейнера разработки и вашего региона доступны предварительные сборки, вы увидите метку "{% octicon "zap" aria-label="The zap icon" %} Доступна предварительная сборка" в списке типов компьютеров при создании codespace. Если предварительная сборка все еще создается, вы увидите метку "{% octicon "history" aria-label="The history icon" %} Предварительная сборка выполняется". Дополнительные сведения см. в разделе [Создание пространства кода для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
+Если для определенной ветви репозитория, файла конфигурации контейнера разработки и вашего региона доступны предварительные сборки, вы увидите метку "{% octicon "zap" aria-label="The zap icon" %} Доступна предварительная сборка" в списке типов компьютеров при создании codespace. Если предварительная сборка все еще создается, вы увидите метку "{% octicon "history" aria-label="The history icon" %} Предварительная сборка выполняется". Дополнительные сведения см. в разделе [Создание codespace для репозитория](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
-При создании codespace на основе шаблона на странице "Ваши codespaces" {% data variables.product.prodname_dotcom %} может автоматически использовать предварительную сборку для ускорения создания. Дополнительные сведения о шаблонах см. в разделе [Создание codespace на основе шаблона](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template).
+При создании codespace на основе шаблона на странице "Ваши codespaces" {% data variables.product.prodname_dotcom %} может автоматически использовать предварительную сборку для ускорения создания. Дополнительные сведения о шаблонах см. в разделе [Создание пространства кода из шаблона](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template).
## Процесс предварительной сборки
@@ -36,13 +36,13 @@ ms.locfileid: '148158800'
Когда запускается рабочий процесс предварительной сборки, {% data variables.product.prodname_dotcom %} создает временную среду codespace, выполняя операции настройки вплоть до любых команд `onCreateCommand` и `updateContentCommand` в файле `devcontainer.json` включительно. Во время создания предварительной сборки команды не `postCreateCommand` выполняются. Дополнительные сведения об этих командах [см. в справочнике по `devcontainer.json`](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) в документации по {% data variables.product.prodname_vscode_shortname %}. Затем будет создан и сохранен моментальный снимок созданного контейнера.
-Как и в случае с другими рабочими процессами {% data variables.product.prodname_actions %}, выполнение рабочего процесса конфигурации предварительной сборки будет либо потреблять часть минут {% data variables.product.prodname_actions %}, включенных в вашу учетную запись, либо будет взиматься плата за {% data variables.product.prodname_actions %} минут. Плата за хранение предварительных сборок codespace взимается так же, как за хранение активных или остановленных codespace. Дополнительные сведения см. в статье [Сведения о выставлении счетов за {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds).
+Как и в случае с другими рабочими процессами {% data variables.product.prodname_actions %}, выполнение рабочего процесса настройки предварительной сборки будет потреблять часть {% data variables.product.prodname_actions %} минут, включенных в вашу учетную запись, если таковые имеются, или будет взиматься плата за {% data variables.product.prodname_actions %} минут. Плата за хранение предварительных сборок codespace взимается так же, как за хранение активных или остановленных кодовых пространств. Дополнительные сведения см. в статье [Сведения о выставлении счетов за {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds).
Когда вы создаете среду codespace из предварительной сборки, {% data variables.product.prodname_dotcom %} скачивает существующий снимок контейнера из хранилища и развертывает его на новой виртуальной машине, выполняя оставшиеся команды, указанные в конфигурации контейнера разработки. Так как многие операции уже выполнены, например клонирование репозитория, создание codespace из предварительной сборки может быть значительно быстрее, чем создание без предварительной сборки. Это так, когда репозиторий большой и (или) команды `onCreateCommand` выполняются долго.
## Сведения об отправке изменений в ветви с включенной предварительной сборкой
-По умолчанию каждая отправка в ветвь с конфигурацией предварительной сборки приводит к запуску рабочего процесса {% data variables.product.prodname_dotcom %}, управляемого {% data variables.product.prodname_actions %}, для обновления предварительной сборки. Рабочий процесс предварительной сборки имеет ограничение параллелизма: запускается один рабочий процесс за раз для заданной конфигурации предварительной сборки, если только не были внесены изменения, влияющие на конфигурацию контейнера разработки для связанного репозитория. Дополнительные сведения см. в статье [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers). Если запуск уже выполняется, то запуск рабочего процесса, который был поставлен в очередь последним, будет выполнен после завершения текущего запуска.
+По умолчанию каждая отправка в ветвь с конфигурацией предварительной сборки приводит к запуску рабочего процесса {% data variables.product.prodname_dotcom %}, управляемого {% data variables.product.prodname_actions %}, для обновления предварительной сборки. Рабочий процесс предварительной сборки имеет ограничение параллелизма: запускается один рабочий процесс за раз для заданной конфигурации предварительной сборки, если только не были внесены изменения, влияющие на конфигурацию контейнера разработки для связанного репозитория. Дополнительные сведения см. в статье [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers). Если выполнение уже выполняется, запуск рабочего процесса, который был помещен в очередь, будет выполняться следующим после завершения текущего выполнения.
Если для предварительной сборки настроено обновление при каждой отправке, это означает, что в случае очень частых отправок в репозиторий обновления предварительной сборки будут происходить не реже, чем требуется для запуска рабочего процесса предварительной сборки. Итак, если выполнение рабочего процесса обычно занимает один час, предварительные сборки будут создаваться для репозитория примерно раз в час, если выполнение завершится успешно, или чаще, если были отправки, изменяющие конфигурацию контейнера разработки в ветви.
diff --git a/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 986c44b07f..8f7905ac45 100644
--- a/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -1,6 +1,6 @@
---
-title: Создание файла работоспособности сообщества по умолчанию.
-intro: 'Вы можете создать файлы работоспособности сообщества по умолчанию, такие как CONTRIBUTING и CODE_OF_CONDUCT. Файлы по умолчанию будут использоваться для любого репозитория, принадлежащего учетной записи, который не содержит собственный файл такого рода.'
+title: Creating a default community health file
+intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
redirect_from:
- /articles/creating-a-default-community-health-file-for-your-organization
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
@@ -12,41 +12,46 @@ versions:
topics:
- Community
shortTitle: Community health file
-ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ru-RU
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145117635'
---
-## Сведения о файлах работоспособности сообщества по умолчанию
-Файлы работоспособности сообщества по умолчанию можно добавить в общедоступный репозиторий `.github` в корневой каталог репозитория или в папки `docs` или`.github`.
+## About default community health files
-{% data variables.product.product_name %} будет использовать и отображать файлы по умолчанию для любого репозитория, принадлежащего учетной записи, которая не имеет собственного файла этого типа, в любом из следующих мест.
-- Корень репозитория
-- Папка `.github`
-- Папка `docs`
+You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders.
-Например, любой пользователь, создающий проблему или запрос на вытягивание в репозитории, у которого нет собственного файла CONTRIBUTING, увидит ссылку на файл CONTRIBUTING по умолчанию. Если в репозитории есть файлы в собственной папке `.github/ISSUE_TEMPLATE`{% ifversion fpt or ghes or ghec %}, включая шаблоны проблем или файл *config.yml*,{% endif %} содержимое папки по умолчанию `.github/ISSUE_TEMPLATE` использоваться не будет.
+{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
+- the root of the repository
+- the `.github` folder
+- the `docs` folder
-Файлы по умолчанию не включаются в клоны, пакеты или скачивания отдельных репозиториев, так как они хранятся только в репозитории `.github`.
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
-## Поддерживаемые типы файлов
+Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
-Вы можете создать заданные по умолчанию сведения в вашей организации{% ifversion fpt or ghes or ghec %} или личной учетной записи {% endif %} для следующих файлов работоспособности сообщества:
+## Supported file types
-Файл работоспособности сообщества | Описание --- | ---{% ifversion fpt or ghec %} *CODE_OF_CONDUCT.md* | Файл CODE_OF_CONDUCT определяет стандарты участия в деятельности сообщества. Дополнительные сведения см. в статье "[Добавление правил поведения в проект](/articles/adding-a-code-of-conduct-to-your-project/)".{% endif %} *CONTRIBUTING.md |* Файл CONTRIBUTEING содержит сведения о том, как люди должны участвовать в разработке проекта. Дополнительные сведения см. в статье "[Создание рекомендаций для участников репозитория](/articles/setting-guidelines-for-repository-contributors/)".{% ifversion fpt or ghec %} *FUNDING.yml* | Файл FUNDING отображает в репозитории кнопку спонсора, чтобы повысить видимость вариантов финансирования для проекта с открытым кодом. Дополнительные сведения см. в статье "[Отображение кнопки спонсора в репозитории](/articles/displaying-a-sponsor-button-in-your-repository)".{% endif %} Шаблоны проблем и запросов на вытягивание{% ifversion fpt or ghes or ghec %} и *config.yml*{% endif %} | Шаблоны проблем и запросов на вытягивание позволяют настраивать и стандартизовать сведения, которые участники должны указывать при открытии проблем и запросов на вытягивание в репозитории. Дополнительные сведения см. в статье "[Сведения о шаблонах проблем и запросов на вытягивание](/articles/about-issue-and-pull-request-templates/)".{% ifversion fpt or ghes or ghec %} *SECURITY.md |* Файл SECURITY содержит инструкции по отправке сведений об уязвимости системы безопасности в проекте. Дополнительные сведения см. в статье "[Добавление политики безопасности в репозиторий](/code-security/getting-started/adding-a-security-policy-to-your-repository)".{% endif %} *SUPPORT.md |* Файл SUPPORT содержит сведения о способах получения помощи по проекту. Дополнительные сведения см. в статье "[Добавление ресурсов поддержки в проект](/articles/adding-support-resources-to-your-project/)".
+You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
-Создать файл лицензии по умолчанию невозможно. Файлы лицензий должны быть добавлены в отдельные репозитории, чтобы файл включался при клонировании, упаковке или скачивании проекта.
+Community health file | Description
+--- | ---{% ifversion fpt or ghec %}
+*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
+*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion discussion-category-forms %}
+Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[Creating discussion category forms](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
+*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
+Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes or ghec %}
+*SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
-## Создание репозитория для файлов по умолчанию
+You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
+
+## Creating a repository for default files
{% data reusables.repositories.create_new %}
-2. В раскрывающемся меню **Владелец** выберите организацию{% ifversion fpt or ghes or ghec %} или личную учетную запись{% endif %}, для которой нужно создать файлы по умолчанию.
- 
-3. Введите **.github** в качестве имени репозитория и необязательное описание.
- 
-4. Убедитесь, что для состояния репозитория задано значение **Общедоступный** (репозиторий для файлов по умолчанию не может быть частным).
-  {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
-7. В репозитории создайте один из поддерживаемых файлов работоспособности сообщества. Шаблоны проблем{% ifversion fpt or ghes or ghec %} и их файл конфигурации{% endif %} должны находиться в папке с именем `.github/ISSUE_TEMPLATE`. Все остальные поддерживаемые файлы могут находиться в корне репозитория, папке `.github` или папке `docs`. Дополнительные сведения см. в статье "[Создание файлов](/articles/creating-new-files/)".
+2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
+ 
+3. Type **.github** as the name for your repository, and an optional description.
+ 
+4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+ 
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
diff --git a/translations/ru-RU/content/discussions/managing-discussions-for-your-community/index.md b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/index.md
index 1be25ec9fd..6cc72aa619 100644
--- a/translations/ru-RU/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,6 +9,8 @@ children:
- /managing-categories-for-discussions
- /moderating-discussions
- /viewing-insights-for-your-discussions
+ - /creating-discussion-category-forms
+ - /syntax-for-discussion-category-forms
ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
ms.translationtype: HT
diff --git a/translations/ru-RU/content/rest/overview/libraries.md b/translations/ru-RU/content/rest/overview/libraries.md
index cd3bdb7fb6..13783af96e 100644
--- a/translations/ru-RU/content/rest/overview/libraries.md
+++ b/translations/ru-RU/content/rest/overview/libraries.md
@@ -11,12 +11,12 @@ versions:
ghec: '*'
topics:
- API
-ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
-ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
+ms.openlocfilehash: 5f633132edddb17ae129a3feba791ab8ec780366
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: MT
ms.contentlocale: ru-RU
-ms.lasthandoff: 12/01/2022
-ms.locfileid: '148190064'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191881'
---
@@ -26,7 +26,7 @@ ms.locfileid: '148190064'
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
- [octokit.net](https://github.com/octokit/octokit.net) → **.NET**
-- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+- [ → javaScriptoctokit.js](https://github.com/octokit/octokit.js)
## Сторонние библиотеки
diff --git a/translations/ru-RU/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/ru-RU/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
index 9821d9b5b6..e53a389ec6 100644
--- a/translations/ru-RU/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
+++ b/translations/ru-RU/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -1,6 +1,6 @@
---
-title: Просмотр и обновление запросов в службу поддержки
-intro: 'Вы можете просматривать запросы в службу поддержки{% ifversion ghes or ghec %}, совместно работать над запросами с коллегами{% endif %} и отвечать {% data variables.contact.github_support %}, используя {% data variables.contact.support_portal %}.'
+title: Viewing and updating support tickets
+intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.'
shortTitle: Managing your tickets
versions:
fpt: '*'
@@ -8,62 +8,64 @@ versions:
ghes: '*'
topics:
- Support
-ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ru-RU
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147051983'
---
-## Сведения об управлении запросами в службу поддержки
+
+## About ticket management
{% data reusables.support.zendesk-old-tickets %}
-Вы можете использовать [Портал поддержки GitHub](https://support.github.com/) для просмотра текущих и прошлых запросов в службу поддержки и ответа на {% data variables.contact.github_support %}. Через 120 дней разрешенные запросы архивируются{% ifversion ghec or ghes or ghae %}, и архивные запросы можно просматривать только для корпоративных учетных записей{% endif %}.
+You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}. After 120 days, resolved tickets are archived{% ifversion ghec or ghes or ghae %}, and archived tickets can only be viewed for enterprise accounts{% endif %}.
-{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+{% ifversion ghes or ghec %}
+{% data reusables.enterprise-accounts.support-entitlements %}
+{% endif %}
-## Просмотр недавних запросов в службу поддержки
+## Viewing your recent support tickets
{% data reusables.support.view-open-tickets %}
-1. В текстовом поле можно просмотреть журнал комментариев. Последний ответ находится вверху.
-
+1. Under the text box, you can read the comment history. The most recent response is at the top.
+
+ 
+
+1. Optionally, to translate the ticket comment, click {% octicon "globe" aria-label="The globe icon" %} and choose your preferred language from the dropdown menu. You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish.
+
+ 
{% ifversion ghec or ghes or ghae %}
-## Просмотр архивных запросов в службу поддержки
+## Viewing your archived support tickets
-Вы можете просматривать архивные запросы только для корпоративной учетной записи.
+You can only view archived tickets for an enterprise account.
{% data reusables.support.navigate-to-my-tickets %}
-1. Выберите раскрывающееся меню **Мои запросы** и щелкните имя корпоративной учетной записи.
+1. Select the **My Tickets** drop-down menu and click the name of the enterprise account.
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
- 
-1. В таблице "Мои запросы" щелкните **Просмотреть архивные запросы**.
+ 
+1. Under the "My tickets" table, click **View archived tickets**.
{% endif %}
-## Обновление запросов в службу поддержки.
+## Updating support tickets
{% data reusables.support.view-open-tickets %}
-1. При необходимости, если проблема устранена, в текстовом поле нажмите кнопку **Закрыть запрос**.
-
-1. Чтобы ответить службе поддержки GitHub и добавить новый комментарий в запрос, введите ответ в текстовом поле.
-
-1. Чтобы добавить комментарий к запросу, нажмите кнопку **Комментарий**.
-
+1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
+
+1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
+
+1. To add your comment to the ticket, click **Comment**.
+
{% ifversion ghec or ghes %}
-## Совместная работа с запросами в службу поддержки
+## Collaborating on support tickets
-Вы можете совместно работать со своими коллегами над запросами в службу поддержки с помощью портала поддержки. Владельцы, менеджеры по выставлению счетов и другие участники предприятия с правами специалистов службы поддержки могут просматривать запросы, связанные с корпоративной учетной записью или организацией, которая управляется корпоративной учетной записью. Дополнительные сведения см. в разделе [Управление правами специалистов службы поддержки для вашего предприятия](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise).
+You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-Помимо просмотра запросов, вы также можете добавлять комментарии в запросы в службу поддержки, если ваш адрес электронной почты скопирован в запросе или если пользователь, открывший запрос, использовал адрес электронной почты с доменом, проверенным для корпоративной учетной записи или организации, которая управляется корпоративной учетной записью. Дополнительные сведения о проверке домена см. в разделе [Проверка или утверждение домена для вашего предприятия](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise) и [Проверка или утверждение домена для вашей организации](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization).
+In addition to viewing tickets, you can also add comments to support tickets if your email address is copied on the ticket or if the person who opened the ticket used an email address with a domain that is verified for the enterprise account or organization managed by an enterprise account. For more information about verifying a domain, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Verifying or approving a domain for your organization](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
{% endif %}
-## Дополнительные материалы
+## Further reading
-- [Сведения о поддержке GitHub](/support/learning-about-github-support/about-github-support)
+- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
diff --git a/translations/ru-RU/content/support/learning-about-github-support/about-github-support.md b/translations/ru-RU/content/support/learning-about-github-support/about-github-support.md
index f5d6525f05..be735ece17 100644
--- a/translations/ru-RU/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/ru-RU/content/support/learning-about-github-support/about-github-support.md
@@ -83,6 +83,10 @@ If you have any paid product or are a member of an organization with a paid prod
With {% data variables.product.product_name %}, you have access to support in English and Japanese.
{% endif %}
+{% ifversion fpt or ghec or ghes %}
+{% data reusables.support.support-ticket-translation-option %}
+{% endif %}
+
{% ifversion ghes or ghec %}
To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
diff --git a/translations/ru-RU/data/release-notes/enterprise-server/3-5/4.yml b/translations/ru-RU/data/release-notes/enterprise-server/3-5/4.yml
index 028b8750b6..2d4ef88879 100644
--- a/translations/ru-RU/data/release-notes/enterprise-server/3-5/4.yml
+++ b/translations/ru-RU/data/release-notes/enterprise-server/3-5/4.yml
@@ -29,4 +29,5 @@ sections:
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
- |
- GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
\ No newline at end of file
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ru-RU/data/release-notes/enterprise-server/3-5/5.yml b/translations/ru-RU/data/release-notes/enterprise-server/3-5/5.yml
index 340d5d0a24..05de05ac2b 100644
--- a/translations/ru-RU/data/release-notes/enterprise-server/3-5/5.yml
+++ b/translations/ru-RU/data/release-notes/enterprise-server/3-5/5.yml
@@ -1,27 +1,30 @@
date: '2022-08-30'
sections:
bugs:
- - 'После разблокировки репозитория для временного доступа администратор сайта не мог управлять параметрами продуктов безопасности в репозитории.'
- - 'Дубликаты административных ключей SSH могли появляться как в консоли управления, так и в файле "/home/admin/.ssh/authorized_keys".'
- - 'Страница администрирования сайта для отдельных пользователей по адресу http(s)://HOSTNAME/stafftools/users/USERNAME/admin содержала функции, не предназначенные для GitHub Enterprise Server.'
- - 'В некоторых случаях выполнение ghe-cluster-config-apply может реплицировать пустую конфигурацию на существующие узлы в кластере.'
- - 'В некоторых случаях выполнения конфигурации, запущенные с помощью ghe-config-apply, не завершались или возвращали ошибку "Несоответствие количества контейнеров".'
- - 'После обновления самозаверяющего сертификата TLS на экземпляре GitHub Enterprise Server элементы пользовательского интерфейса на некоторых страницах веб-интерфейса не отображались.'
- - 'Панель администратора сайта в верхней части веб-интерфейса содержала недействительную ссылку на SHA для текущей версии приложения.'
- - 'В некоторых случаях фоновые задачи могли останавливаться из-за того, что параллельно использовалась библиотека, несмотря на то, что она не является потокобезопасной.'
- - "Оповещения о сканировании секретов для клиентов GitHub Advanced Security отсутствовали в веб-интерфейсе и REST API, если администратор сайта не выполнил обновление непосредственно до GitHub Enterprise Server\_3.4. Теперь оповещения видны."
- - 'Когда пользователь создавал вилку репозитория для формирования организации, длинный список организаций не отображался должным образом.'
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
+ - When a user forked a repository into an organization, a long list of organizations would not render properly.
changes:
- - 'Создание пакетов поддержки происходит быстрее благодаря параллельной очистке журналов. Дополнительные сведения о пакетах поддержки см. в статье [Предоставление данных поддержке GitHub](/support/contacting-github-support/providing-data-to-github-support).'
- - 'API, которые содержат маршрут organization (или org), теперь принимают либо динамический идентификатор, либо идентификатор организации. Ранее API принимали только динамические идентификаторы, из-за чего заголовки "Link" для конечных точек GitHub Advanced Security были недоступны. Дополнительные сведения см. в статье [Организации] (https://docs.github.com/rest/orgs/orgs) в документации REST API.'
- - 'Журнал аудита предприятия теперь включает больше пользовательских событий, таких как project.create. REST API также возвращает дополнительные события, созданные пользователем, такие как repo.create. Дополнительные сведения см. в статье [Доступ к журналу аудита для вашего предприятия](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for -your-enterprise) и разделе [Использование API журнала аудита для вашего предприятия](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit- log-api-for-your-enterprise#querying-the-audit-log-rest-api).'
- - 'Иногда реплики кэша могли отклонять некоторые операции Git над недавно обновленными репозиториями. Дополнительные сведения о кэшировании репозитория см. в статье [Сведения о кэшировании репозитория](/admin/enterprise-management/caching-repositories/about-repository-caching).'
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
known_issues:
- - 'Злоумышленник мог создать первого пользователя с правами администратора на только что настроенном экземпляре {% data variables.product.prodname_ghe_server %} без пользователей.'
- - 'Настраиваемые правила брандмауэра удаляются в процессе обновления.'
- - "Отслеживаемые файлы Git\_LFS, [отправленные через веб-интерфейс](https://github.com/blog/2105-upload-files-to-your-repositories), ошибочно добавлялись напрямую в репозиторий."
- - "Проблемы нельзя закрыть, если они содержат постоянную ссылку на большой двоичный объект в том же репозитории, где путь к файлу большого двоичного объекта превышает 255\_символов."
- - "Когда в GitHub\_Connect включен параметр Users can search GitHub.com (Пользователи могут выполнять поиск на GitHub.com), результаты поиска на GitHub.com не включают в себя проблемы в частных и внутренних репозиториях."
- - 'Реестр npm {% data variables.product.prodname_registry %} больше не возвращает значение времени в ответах метаданных. Это изменение позволяет существенно улучшить производительность. Мы продолжим хранить все данные, необходимые для возврата значения времени в качестве части ответа метаданных, и возобновим возврат этого значения в будущем, как только решим существующие проблемы с производительностью.'
- - 'Ограничения ресурсов, относящиеся к обработке перехватчиков перед получением, могут приводить к сбою некоторых из них.'
- - 'Службы Actions необходимо перезапустить после восстановления устройства из резервной копии, созданной на другом узле.'
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ru-RU/data/release-notes/enterprise-server/3-6/1.yml b/translations/ru-RU/data/release-notes/enterprise-server/3-6/1.yml
index efb836eeab..6e638df146 100644
--- a/translations/ru-RU/data/release-notes/enterprise-server/3-6/1.yml
+++ b/translations/ru-RU/data/release-notes/enterprise-server/3-6/1.yml
@@ -1,33 +1,38 @@
date: '2022-08-30'
sections:
bugs:
- - 'После разблокировки репозитория для временного доступа администратор сайта не мог управлять параметрами продуктов безопасности в репозитории.'
- - 'Дубликаты административных ключей SSH могли появляться как в консоли управления, так и в файле "/home/admin/.ssh/authorized_keys".'
- - 'Страница администрирования сайта для отдельных пользователей по адресу http(s)://HOSTNAME/stafftools/users/USERNAME/admin содержала функции, не предназначенные для GitHub Enterprise Server.'
- - 'В некоторых случаях выполнение ghe-cluster-config-apply может реплицировать пустую конфигурацию на существующие узлы в кластере.'
- - 'В некоторых случаях выполнения конфигурации, запущенные с помощью ghe-config-apply, не завершались или возвращали ошибку "Несоответствие количества контейнеров".'
- - 'После обновления самозаверяющего сертификата TLS на экземпляре GitHub Enterprise Server элементы пользовательского интерфейса на некоторых страницах веб-интерфейса не отображались.'
- - 'В некоторых случаях фоновые задачи могли останавливаться из-за того, что параллельно использовалась библиотека, несмотря на то, что она не является потокобезопасной.'
- - 'Панель администратора сайта в верхней части веб-интерфейса содержала недействительную ссылку на SHA для текущей версии приложения.'
- - 'Владельцам организаций не удалось задать уровень доступа, необходимый для создания обсуждений.'
- - 'Пользователи обсуждений ошибочно перенаправлялись к руководствам сообщества для GitHub.com.'
- - 'В некоторых случаях пользователям предоставлялось неверное указание проверить свою электронную почту перед созданием обсуждения.'
- - "Оповещения о сканировании секретов для клиентов GitHub Advanced Security отсутствовали в веб-интерфейсе и REST API, если администратор сайта не выполнил обновление непосредственно до GitHub Enterprise Server\_3.4. Теперь оповещения видны."
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - Organization owners were unable to set the level of access required to create discussions.
+ - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
+ - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
changes:
- - 'Создание пакетов поддержки происходит быстрее благодаря параллельной очистке журналов. Дополнительные сведения о пакетах поддержки см. в статье [Предоставление данных поддержке GitHub](/support/contacting-github-support/providing-data-to-github-support).'
- - 'API, которые содержат маршрут organization (или org), теперь принимают либо динамический идентификатор, либо идентификатор организации. Ранее API принимали только динамические идентификаторы, из-за чего заголовки "Link" для конечных точек GitHub Advanced Security были недоступны. Дополнительные сведения см. в статье [Организации] (https://docs.github.com/rest/orgs/orgs) в документации REST API.'
- - 'Журнал аудита предприятия теперь включает больше пользовательских событий, таких как project.create. REST API также возвращает дополнительные события, созданные пользователем, такие как repo.create. Дополнительные сведения см. в статье [Доступ к журналу аудита для вашего предприятия](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for -your-enterprise) и разделе [Использование API журнала аудита для вашего предприятия](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit- log-api-for-your-enterprise#querying-the-audit-log-rest-api).'
- - 'Иногда реплики кэша могли отклонять некоторые операции Git над недавно обновленными репозиториями. Дополнительные сведения о кэшировании репозитория см. в статье [Сведения о кэшировании репозитория](/admin/enterprise-management/caching-repositories/about-repository-caching).'
- - 'Теперь вы можете настроить баннер глобального оповещения так, чтобы его можно было убрать, используя REST API. Дополнительные сведения см. в разделе [Настройка сообщений для пользователей на предприятии](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner).'
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+ - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
known_issues:
- - 'Злоумышленник мог создать первого пользователя с правами администратора на только что настроенном экземпляре {% data variables.product.prodname_ghe_server %} без пользователей.'
- - 'Настраиваемые правила брандмауэра удаляются в процессе обновления.'
- - "Отслеживаемые файлы Git\_LFS, [отправленные через веб-интерфейс](https://github.com/blog/2105-upload-files-to-your-repositories), ошибочно добавлялись напрямую в репозиторий."
- - "Проблемы нельзя закрыть, если они содержат постоянную ссылку на большой двоичный объект в том же репозитории, где путь к файлу большого двоичного объекта превышает 255\_символов."
- - "Когда в GitHub\_Connect включен параметр Users can search GitHub.com (Пользователи могут выполнять поиск на GitHub.com), результаты поиска на GitHub.com не включают в себя проблемы в частных и внутренних репозиториях."
- - 'Реестр npm {% data variables.product.prodname_registry %} больше не возвращает значение времени в ответах метаданных. Это изменение позволяет существенно улучшить производительность. Мы продолжим хранить все данные, необходимые для возврата значения времени в качестве части ответа метаданных, и возобновим возврат этого значения в будущем, как только решим существующие проблемы с производительностью.'
- - 'Ограничения ресурсов, относящиеся к обработке перехватчиков перед получением, могут приводить к сбою некоторых из них.'
- - 'Службы Actions необходимо перезапустить после восстановления экземпляра из резервной копии, созданной на другом узле.'
- - 'В настройках репозитория включение параметра, позволяющего пользователям с доступом для чтения создавать обсуждения, не включает эту функцию.'
- - 'В некоторых случаях пользователи не могут преобразовать существующие проблемы в обсуждения.'
- - 'Пользовательские шаблоны для сканирования секретов содержат ".*" в качестве конечного разделителя, особенно в поле "После секрета". Этот разделитель вызывает несоответствия при сканировании секретов в репозиториях, и вы можете заметить пробелы в журнале репозитория, если ни одно сканирование не было завершено. Добавочные сканирования также могут быть затронуты. Чтобы предотвратить проблемы со сканированием, измените конец шаблона, чтобы удалить разделитель ".*".'
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+ - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+ - In some cases, users cannot convert existing issues to discussions.
+ - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+ - |
+ After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/actions/if-supported-contexts.md b/translations/ru-RU/data/reusables/actions/if-supported-contexts.md
new file mode 100644
index 0000000000..c506c3bb14
--- /dev/null
+++ b/translations/ru-RU/data/reusables/actions/if-supported-contexts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 31687bc8c34a11de5a36e5db2877d279740f0f8f
+ms.sourcegitcommit: 4f08a208a0d2e13dc109678750a962ea2f67e1ba
+ms.translationtype: MT
+ms.contentlocale: ru-RU
+ms.lasthandoff: 12/06/2022
+ms.locfileid: "148192062"
+---
+Для создания условного выражения можно использовать любой поддерживаемый контекст и любое выражение. Дополнительные сведения о том, какие контексты поддерживаются в этом разделе, см. в разделе Доступность [контекста](/actions/learn-github-actions/contexts#context-availability).
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/ru-RU/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index bce8c98967..e6332d010a 100644
--- a/translations/ru-RU/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/ru-RU/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,12 +1,12 @@
---
-ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
+ms.openlocfilehash: eb897a445a5e5a90014097ba76a5ecb095aa0bef
+ms.sourcegitcommit: 4f08a208a0d2e13dc109678750a962ea2f67e1ba
+ms.translationtype: MT
ms.contentlocale: ru-RU
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145114232"
+ms.lasthandoff: 12/06/2022
+ms.locfileid: "148192063"
---
-Условное выражение `jobs..if` можно использовать для предотвращения выполнения задания, если условие не выполняется. Для создания условного выражения можно использовать любой поддерживаемый контекст и любое выражение.
+Условное выражение `jobs..if` можно использовать для предотвращения выполнения задания, если условие не выполняется. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} Дополнительные сведения см. в разделе [Выражения](/actions/learn-github-actions/expressions).
diff --git a/translations/ru-RU/data/reusables/actions/reusable-workflows-enterprise-beta.md b/translations/ru-RU/data/reusables/actions/reusable-workflows-enterprise-beta.md
new file mode 100644
index 0000000000..6064e0e17e
--- /dev/null
+++ b/translations/ru-RU/data/reusables/actions/reusable-workflows-enterprise-beta.md
@@ -0,0 +1,17 @@
+{% ifversion ghes = 3.4 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently in beta and subject to change.
+
+{% endnote %}
+
+{% elsif ghae > 3.3 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently unavailable in {% data variables.product.product_name %}, but will be available in a future update.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/ru-RU/data/reusables/actions/reusable-workflows-ghes-beta.md
deleted file mode 100644
index 6fb3ef2e4f..0000000000
--- a/translations/ru-RU/data/reusables/actions/reusable-workflows-ghes-beta.md
+++ /dev/null
@@ -1,9 +0,0 @@
-{% ifversion ghes = 3.4 %}
-
-{% note %}
-
-**Note**: Reusable workflows are currently in beta and subject to change.
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/ru-RU/data/reusables/enterprise-accounts/dormant-user-activity.md
index 80878d1726..24b839f410 100644
--- a/translations/ru-RU/data/reusables/enterprise-accounts/dormant-user-activity.md
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
- Starring a repository
- Deleting a repository
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
+- Joining an organization
+
+{% ifversion ghes %}
+A user will also be considered active if their account has been updated by LDAP.
+{% endif %}
diff --git a/translations/ru-RU/data/ui.yml b/translations/ru-RU/data/ui.yml
index 1e8377dd72..29dec0fbef 100644
--- a/translations/ru-RU/data/ui.yml
+++ b/translations/ru-RU/data/ui.yml
@@ -127,7 +127,7 @@ products:
rest:
banner:
api_versioned: The REST API is now versioned.
- api_version_info: For more information, see "About API versioning".
+ api_version_info: For more information, see "About API versioning."
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "About versions of GitHub Docs".
versioning:
about_versions: About REST API versions
diff --git a/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md b/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
index 9870f4ff2e..e503046a99 100644
--- a/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
@@ -16,12 +16,12 @@ type: overview
topics:
- Action development
- Fundamentals
-ms.openlocfilehash: ac933a5014750f75373fafa7f8dd52333b79a469
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 1e81bea551ceff1980b0bbe96202f60db0d0e7f2
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147154571'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191944'
---
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
@@ -35,7 +35,7 @@ ms.locfileid: '147154571'
## 操作的类型
-您可以创建 Docker 容器和 JavaScript 操作。 操作需要元数据文件来定义操作的输入、输出和主要进入点。 元数据文件名必须为 `action.yml` 或 `action.yaml`。 有关详细信息，请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions)”。
+可以构建 Docker 容器、JavaScript 和复合操作。 操作需要元数据文件来定义操作的输入、输出和主要进入点。 元数据文件名必须为 `action.yml` 或 `action.yaml`。 有关详细信息，请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions)”。
| 类型 | 操作系统 |
| ---- | ------------------- |
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
index 382e81006b..f54adf093a 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
@@ -94,7 +94,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
shell: bash
```
{% endraw %}
- This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+ This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, adds the action's path to the runner system path (to locate the `goodbye.sh` script during execution), and runs the `goodbye.sh` script.
For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
index 5a1ea071a9..8dcb762313 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
@@ -271,3 +271,10 @@ jobs:
From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+
+## Template repositories for creating JavaScript actions
+
+{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
+
+* [`javascript-action` template repository](https://github.com/actions/javascript-action)
+* [`typescript-action` template repository](https://github.com/actions/typescript-action)
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index 30c0ee6762..0d240ae768 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -283,6 +283,12 @@ After this setting is applied, the JWT will contain the updated `iss` value. In
To help improve security, compliance, and standardization, you can customize the standard claims to suit your required access conditions. If your cloud provider supports conditions on subject claims, you can create a condition that checks whether the `sub` value matches the path of the reusable workflow, such as `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`. The exact format will vary depending on your cloud provider's OIDC configuration. To configure the matching condition on {% data variables.product.prodname_dotcom %}, you can can use the REST API to require that the `sub` claim must always include a specific custom claim, such as `job_workflow_ref`. You can use the [OIDC REST API](/rest/actions/oidc) to apply a customization template for the OIDC subject claim; for example, you can require that the `sub` claim within the OIDC token must always include a specific custom claim, such as `job_workflow_ref`.
+{% note %}
+
+**Note**: When the organization template is applied, it will not affect any workflows in existing repositories that already use OIDC. For existing repositories, as well as any new repositories that are created after the template has been applied, the repository owner will need to opt-in to receive this configuration, or alternatively could apply a different configuration specific to the repo. For more information, see "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)."
+
+{% endnote %}
+
Customizing the claims results in a new format for the entire `sub` claim, which replaces the default predefined `sub` format in the token described in "[Example subject claims](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims)."
The following example templates demonstrate various ways to customize the subject claim. To configure these settings on {% data variables.product.prodname_dotcom %}, admins use the REST API to specify a list of claims that must be included in the subject (`sub`) claim.
@@ -291,12 +297,6 @@ The following example templates demonstrate various ways to customize the subjec
To customize your subject claims, you should first create a matching condition in your cloud provider's OIDC configuration, before customizing the configuration using the REST API. Once the configuration is completed, each time a new job runs, the OIDC token generated during that job will follow the new customization template. If the matching condition doesn't exist in the cloud provider's OIDC configuration before the job runs, the generated token might not be accepted by the cloud provider, since the cloud conditions may not be synchronized.
-{% note %}
-
-**Note**: When the organization template is applied, it will not affect any action workflows in existing repositories that already use OIDC. For existing repositories, as well as any new repositories that are created after the template has been applied, the repository owner will need to opt-in to receive this configuration, or alternatively could apply a different configuration specific to the repo. For more information, see "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)."
-
-{% endnote %}
-
#### Example: Allowing repository based on visibility and owner
This example template allows the `sub` claim to have a new format, using `repository_owner` and `repository_visibility`:
@@ -431,7 +431,9 @@ In your cloud provider's OIDC configuration, configure the `sub` condition to re
#### Using the default subject claims
-For repositories that can receive a subject claim policy from their organization, the repository owner can later choose to opt-out and instead use the default `sub` claim format. To configure this, the repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
+For repositories that can receive a subject claim policy from their organization, the repository owner can later choose to opt-out and instead use the default `sub` claim format. This means that the repository will not use the organization's customized template.
+
+To configure the repository to use the default `sub` claim format, a repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
```json
{
@@ -439,6 +441,18 @@ For repositories that can receive a subject claim policy from their organization
}
```
+#### Example: Configuring a repository to use an organization template
+
+A repository administrator can configure their repository to use the template created by the administrator of their organisation.
+
+To configure the repository to use the organization's template, a repository admin must use the REST API endpoint at "[Set the customization template for an OIDC subject claim for a repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository)" with the following request body:
+
+```json
+{
+ "use_default": false
+}
+```
+
{% endif %}
## Updating your workflows for OIDC
diff --git a/translations/zh-CN/content/actions/learn-github-actions/contexts.md b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
index bdf5bb0bfb..9217298a2a 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/contexts.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
@@ -811,7 +811,7 @@ The `inputs` context contains input properties passed to an action{% ifversion a
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
| Property name | Type | Description |
|---------------|------|-------------|
diff --git a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0d316eca1f..397d51b308 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -88,7 +88,7 @@ In addition to the usage limits, you must ensure that you use {% data variables.
{% ifversion fpt or ghes > 3.3 or ghec %}
## Billing for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
diff --git a/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md b/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md
index 2adee6a3f4..1cc0d2d002 100644
--- a/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
---
{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
## Overview
diff --git a/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md b/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
index 8e4adb430f..837875fe9e 100644
--- a/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
@@ -123,7 +123,7 @@ You can use activity types and filters to further control when your workflow wil
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 4969f6b53e..e6e11c2ff5 100644
--- a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -72,7 +72,7 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `on.workflow_call`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
@@ -320,7 +320,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+You can use the `if` conditional to prevent a step from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
@@ -945,7 +945,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
## `jobs..uses`
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
index c4156846ca..606bbc6a74 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
@@ -1,6 +1,6 @@
---
-title: Enabling Server Statistics for your enterprise
-intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.'
+title: 为企业启用服务器统计信息
+intro: '可以从 {% data variables.product.prodname_ghe_server %} 分析自己的聚合数据，并通过启用 {% data variables.product.prodname_server_statistics %} 帮助改进 {% data variables.product.company_short %} 产品。'
versions:
feature: server-statistics
redirect_from:
@@ -8,23 +8,27 @@ redirect_from:
topics:
- Enterprise
shortTitle: Server Statistics
+ms.openlocfilehash: 125651de793a45240008de34845762e6de637040
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191868'
---
+## 关于 {% data variables.product.prodname_server_statistics %}
-## About {% data variables.product.prodname_server_statistics %}
+{% data variables.product.prodname_server_statistics %} 从 {% data variables.location.product_location %} 中收集聚合使用情况数据，你可以使用这些数据更好地预测组织的需求、了解团队的工作方式并显示你从 {% data variables.product.prodname_ghe_server %} 获取的值。
-{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
+{% data variables.product.prodname_server_statistics %} 仅在存储库、问题、拉取请求和其他功能上收集某些聚合指标。 不会收集 {% data variables.product.prodname_dotcom %} 内容，例如代码、问题、评论或拉取请求内容。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)”。
-{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+通过启用 {% data variables.product.prodname_server_statistics %}，还可帮助提高 {% data variables.product.company_short %}。 你将提供的聚合数据有助于我们了解我们的客户使用 {% data variables.product.prodname_dotcom %} 的方式，并做出更好、更明智的产品决策，最终使你受益。
-By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
+## 启用 {% data variables.product.prodname_server_statistics %}
-## Enabling {% data variables.product.prodname_server_statistics %}
+启用 {% data variables.product.prodname_server_statistics %} 之前，必须首先通过 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.prodname_ghe_server %} 实例连接到 {% data variables.product.prodname_dotcom_the_website %}。 有关详细信息，请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
-Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+可随时从 {% data variables.product.prodname_ghe_server %} 禁用 {% data variables.product.prodname_server_statistics %}。
-You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time.
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.github-connect-tab %}
-4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**.
- 
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
+4. 在“与 GitHub.com 共享服务器统计信息”下，选择下拉菜单并单击“启用”或“禁用” 。
+ 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 98a84270fb..1e67bc7da9 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
+
| Path without subdomain isolation | Path with subdomain isolation |
| --- | --- |
-| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
-| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
-| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
-| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
-| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
-| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
-| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
+| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
+| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
+| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
+| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
+| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
+| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
{%- ifversion viewscreen-and-notebooks %}
-| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
-| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
-{%- else %}
-| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
+| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
+{%- ifversion ghes < 3.7 %}
+| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
+{%- endif %}
+| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
+| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
+{%- ifversion viewscreen-and-notebooks %}
+| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
+{%- endif %}
+{%- ifversion ghes > 3.4 %}
+| Not supported | `https://containers.HOSTNAME/` |
{%- endif %}
-| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
-| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %}
-| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported | `https://containers.HOSTNAME/` |{% endif %}
## Prerequisites
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
index 4eb59cf491..e7b84aca68 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md
@@ -1,7 +1,7 @@
---
-title: Restricting network traffic to your enterprise with an IP allow list
+title: 使用 IP 允许列表限制到企业的网络流量
shortTitle: Restricting network traffic
-intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
+intro: 可以使用 IP 允许列表限制对企业的访问，仅允许从指定的 IP 地址访问资源。
permissions: Enterprise owners can configure IP allow lists.
miniTocMaxHeadingLevel: 3
versions:
@@ -17,192 +17,154 @@ topics:
redirect_from:
- /admin/configuration/restricting-network-traffic-to-your-enterprise
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
+ms.openlocfilehash: 8511499e723fdeb4a2d24c2fce627bce56ad9777
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191892'
---
+## 关于网络流量限制
-## About network traffic restrictions
-
-By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+默认情况下，授权用户可以从任何 IP 地址访问您的企业。 可以通过为特定 IP 地址配置允许列表来限制对{% ifversion ghec %}企业帐户中组织拥有的{% endif %}资源的访问。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
{% ifversion ghec %}
-If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
+如果你的企业将 {% data variables.product.prodname_emus %} 与 Azure AD 和 OIDC 配合使用，你则可以选择是使用 {% data variables.product.company_short %} 的 IP 允许列表功能，还是为标识提供者 (IdP) 使用允许列表限制。 如果你的企业未将 {% data variables.product.prodname_emus %} 与 Azure 和 OIDC 配合使用，你则可以使用 {% data variables.product.company_short %} 的允许列表功能。
{% elsif ghae %}
-By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
+默认情况下，Azure 网络安全组 (NSG) 规则允许所有入站流量在端口 22、80、443 和 25 打开。 可以联系 {% data variables.contact.github_support %} 为 {% data variables.product.product_name %} 配置访问限制。
-For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+对于使用 Azure NSG 的限制，请联系 {% data variables.contact.github_support %} 以获取应允许访问 {% data variables.product.product_name %} 的 IP 地址。 使用标准 CIDR（无类域间路由）格式指定地址范围。 {% data variables.contact.github_support %} 将配置合适的防火墙规则，以限制通过 HTTP、SSH、HTTPS 和 SMTP 的网络访问。 有关详细信息，请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。
{% endif %}
{% ifversion ghec %}
-## About {% data variables.product.company_short %}'s IP allow list
+## 关于 {% data variables.product.company_short %} 的 IP 允许列表
-You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
+可以使用 {% data variables.product.company_short %} 的 IP 允许列表来控制对企业和企业中组织拥有的资产的访问。
{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
-## About your IdP's allow list
+## 关于 IdP 的允许列表
-If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
+如果将 {% data variables.product.prodname_emus %} 与 Azure AD 和 OIDC 配合使用，则可以使用 IdP 的允许列表。
-Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
+使用 IdP 的允许列表会停用企业中所有组织的 {% data variables.product.company_short %} IP 允许列表配置，并停用 GraphQL API 以启用和管理 IP 允许列表。
-By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
+默认情况下，你的 IdP 会在初始交互式 SAML 或 OIDC 登录到 {% data variables.product.company_short %} 时为你所选择的任何 IP 允许列表配置运行 CAP。
-The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps)."
+OIDC CAP 仅适用于使用用户到服务器令牌对 API 的请求，例如 {% data variables.product.prodname_oauth_app %} 或代表用户操作的 {% data variables.product.prodname_github_app %} 的令牌。 当 {% data variables.product.prodname_github_app %} 使用服务器到服务器令牌时，OIDC CAP 不适用。 有关详细信息，请参阅“[使用 {% data variables.product.prodname_github_apps %} 进行身份验证](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)”和“[关于对 IdP 条件访问策略的支持](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps)”。
-To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
+为了确保在将策略应用到用户到服务器令牌的同时无缝使用 OIDC CAP，必须将企业使用的每个 {% data variables.product.prodname_github_app %} 中的所有 IP 范围复制到 IdP 策略。
-## Using {% data variables.product.company_short %}'s IP allow list
+## 使用 {% data variables.product.company_short %} 的 IP 允许列表
-### Enabling {% data variables.product.company_short %}'s IP allow list
-{% data reusables.profile.access_org %}
-{% data reusables.profile.org_settings %}
-{% data reusables.organizations.security %}
-1. Under "IP allow list", enable the IP allow list.
- - If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
- 
+### 启用 {% data variables.product.company_short %} 的 IP 允许列表
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
+1. 在“IP 允许列表”下，启用 IP 允许列表。
+ - 如果将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，请选择下拉菜单并单击“GitHub”。
+ 
- Select **Enable IP allow list**.
- 
+ 选择“启用 IP 允许列表”。
+ 
- - If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
- 
-1. Click **Save**.
+ - 如果未将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，请选择“启用 IP 允许列表”。
+ 
+1. 单击“ **保存**”。
-### Adding an allowed IP address
+### 添加允许的 IP 地址
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
{% data reusables.identity-and-permissions.ipv6-allow-lists %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
-{% data reusables.identity-and-permissions.check-ip-address %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
-### Allowing access by {% data variables.product.prodname_github_apps %}
+### 允许 {% data variables.product.prodname_github_apps %} 访问
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
-### Editing an allowed IP address
+### 编辑允许的 IP 地址
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+8. 单击“更新”。
{% data reusables.identity-and-permissions.check-ip-address %}
-### Checking if an IP address is permitted
+### 检查是否允许使用 IP 地址
{% data reusables.identity-and-permissions.about-checking-ip-address %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
-### Deleting an allowed IP address
+### 删除允许的 IP 地址
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
-## Using your identity provider's allow list
+## 使用标识提供者的允许列表
{% note %}
-**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
+注意：仅 {% data variables.product.prodname_emus %} 和 Azure AD 和 OIDC 支持使用 IdP 的允许列表。
{% endnote %}
-{% data reusables.profile.access_org %}
-{% data reusables.profile.org_settings %}
-{% data reusables.organizations.security %}
-1. Under "IP allow list", select the dropdown and click **Identity Provider**.
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
+1. 在“IP 允许列表”下，选择下拉列表并单击“标识提供者”。
- 
-1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
+ 
+1. （可选）若要允许已安装的 {% data variables.product.company_short %} 和 {% data variables.product.prodname_oauth_apps %} 从任意 IP 地址访问你的企业，请选择“为应用程序跳过 IdP 检查”。
- 
-1. Click **Save**.
+ 
+1. 单击“ **保存**”。
{% endif %}
{% ifversion ghae %}
-## Enabling allowed IP addresses
+## 启用允许的 IP 地址
{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-1. Under "IP allow list", select **Enable IP allow list**.
- 
-4. Click **Save**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
+1. 在“IP 允许列表”下，选择“启用 IP 允许列表”。
+ 
+4. 单击“ **保存**”。
-## Adding an allowed IP address
+## 添加允许的 IP 地址
-{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
-{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
-{% data reusables.identity-and-permissions.check-ip-address %}
+{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## 允许 {% data variables.product.prodname_github_apps %} 访问
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
-## Editing an allowed IP address
+## 编辑允许的 IP 地址
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
-{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+8. 单击“更新”。
{% data reusables.identity-and-permissions.check-ip-address %}
-## Checking if an IP address is permitted
+## 检查是否允许使用 IP 地址
{% data reusables.identity-and-permissions.about-checking-ip-address %}
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
-## Deleting an allowed IP address
+## 删除允许的 IP 地址
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
-{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
{% endif %}
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
index 6336814ef8..b26b38b524 100644
--- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
+++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Actions with MinIO storage
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO storage to store data generated by workflow runs.'
+title: 使用 MinIO 存储启用 GitHub Actions
+intro: '可以在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %}，并使用 MinIO 存储来存储工作流运行生成的数据。'
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
versions:
ghes: '*'
@@ -14,36 +14,35 @@ redirect_from:
- /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
- /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage
shortTitle: MinIO storage
+ms.openlocfilehash: 3d9c6cfca6b81a66185515c8757cef22290ead30
+ms.sourcegitcommit: 8f1801040a84ca9353899a2d1e6782c702aaed0d
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148166567'
---
+## 先决条件
-## Prerequisites
+在启用 {% data variables.product.prodname_actions %} 之前，请确保您已完成以下步骤：
-Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
+* 创建 MinIO 存储桶，用于存储工作流运行生成的数据。 有关安装和配置 MinIO 的详细信息，请参阅 MinIO 文档中的“[MinIO 高性能对象存储](https://min.io/docs/minio/container/index.html)”和“[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)”。
-* Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
+ 为避免设备上的资源争用，我们建议将 MinIO 与 {% data variables.location.product_location %} 分开托管。
- To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.
+ {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %}
- {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
-{% data reusables.actions.enterprise-common-prereqs %}
+## 使用 MinIO 存储启用 {% data variables.product.prodname_actions %}
-## Enabling {% data variables.product.prodname_actions %} with MinIO storage
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
+1. 在“项目和日志存储”下，选择“Amazon S3”，然后输入存储桶的详细信息：
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_management_console.actions %}
-{% data reusables.actions.enterprise-enable-checkbox %}
-1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
+ * AWS 服务 URL：MinIO 服务的 URL。 例如 `https://my-minio.example:9000`。
+ * AWS S3 存储桶：S3 存储桶的名称。
+ * AWS S3 访问密钥和 AWS S3 密钥：用于 MinIO 实例的 `MINIO_ACCESS_KEY` 和 `MINIO_SECRET_KEY` 。
- * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`.
- * **AWS S3 Bucket**: The name of your S3 bucket.
- * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance.
+ 
+1. 在“项目和日志存储”下，选择“强制路径样式”。
- 
-1. Under "Artifact & Log Storage", select **Force path style**.
-
- 
-{% data reusables.enterprise_management_console.test-storage-button %}
-{% data reusables.enterprise_management_console.save-settings %}
+  {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
{% data reusables.actions.enterprise-postinstall-nextsteps %}
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 625a34aa98..c01ecca7a2 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
-{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
index 33c6b16923..d85f921b7a 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
@@ -1,7 +1,7 @@
---
-title: About support for your IdP's Conditional Access Policy
+title: 关于对 IdP 的条件访问策略的支持
shortTitle: Conditional access policy
-intro: 'When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} can validate access to your enterprise and its resources using your IdP''s Conditional Access Policy (CAP).'
+intro: '企业使用 OIDC SSO 时，{% data variables.product.prodname_dotcom %} 可以使用 IdP 的条件访问策略 (CAP) 验证对企业及其资源的访问。'
product: '{% data reusables.gated-features.emus %}'
versions:
feature: oidc-for-emu
@@ -10,35 +10,40 @@ topics:
- Authentication
- Enterprise
- SSO
+ms.openlocfilehash: aed7008bd008ccfd6303ccbb36f4d6f3bd7002ca
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148179995'
---
-
{% data reusables.enterprise-accounts.azure-emu-support-oidc %}
-## About support for Conditional Access Policies
+## 关于对条件访问策略的支持
{% data reusables.enterprise-accounts.emu-cap-validates %}
-{% data variables.product.product_name %} supports CAP for any {% data variables.enterprise.prodname_emu_enterprise %} where OIDC SSO is enabled. {% data variables.product.product_name %} enforces your IdP's IP conditions but cannot enforce your device compliance conditions. Enterprise owners can choose to use this IP allow list configuration instead of {% data variables.product.product_name %}'s IP allow list, and can do so once OIDC SSO is configured. For more information about IP allow lists, see "[Restricting network traffic with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."
+{% data variables.product.product_name %} 支持对启用了 OIDC SSO 的任何 {% data variables.enterprise.prodname_emu_enterprise %} 使用 CAP。 {% data variables.product.product_name %} 强制实施你的 IdP 的 IP 条件，但不能强制实施你设备的合规性条件。 企业所有者可以选择使用此 IP 允许列表配置，而不是 {% data variables.product.product_name %} 的 IP 允许列表，并且可以在配置 OIDC SSO 后执行此操作。 有关 IP 允许列表的详细信息，请参阅“[使用 IP 允许列表限制网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)”和“[管理组织的允许 IP 地址](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)”。
-For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."
+有关将 OIDC 与 {% data variables.product.prodname_emus %} 结合使用的详细信息，请参阅“[为企业托管用户配置 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)”和“[从 SAML 迁移到 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)”。
-## Considerations for integrations and automations
+## 集成和自动化的注意事项
-{% data variables.product.prodname_dotcom %} sends the originating IP address to your IdP for validation against your CAP. To make sure actions and apps are not blocked by your IdP's CAP, you will need to make changes to your configuration.
+{% data variables.product.prodname_dotcom %} 将发起的 IP 地址发送到你的 IdP 以针对你的 CAP 进行验证。 若要确保 IdP 的 CAP 未阻止操作和应用，需要对配置进行更改。
{% data reusables.enterprise-accounts.oidc-gei-warning %}
### {% data variables.product.prodname_actions %}
-Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP.
+使用 {% data variables.product.pat_generic %} 的操作可能将被你的 IdP 的 CAP 阻止。 我们建议由服务帐户创建 {% data variables.product.pat_generic %}，该服务帐户随后会从 IdP 的 CAP 中的 IP 控制中豁免。
-If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)."
+如果无法使用服务帐户，则取消阻止使用 {% data variables.product.pat_generic %} 的操作的另一个选项是允许 {% data variables.product.prodname_actions %} 使用的 IP 范围。 有关详细信息，请参阅“[关于 GitHub 的 IP 地址](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)”。
-### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+### {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %}
-When {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} make requests on a member's behalf, {% data variables.product.prodname_dotcom %} will send the IP address of the app's server to your IdP for validation. If the IP address of the app's server is not validated by your IdP's CAP, the request will fail.
+当 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %} 代表成员发出请求时，{% data variables.product.prodname_dotcom %} 会将应用的服务器的 IP 地址发送到 IdP 进行验证。 如果 IdP 的 CAP 未验证应用的服务器的 IP 地址，请求将失败。
-You can contact the owners of the apps you want to use, ask for their IP ranges, and configure your IdP's CAP to allow access from those IP ranges. If you're unable to contact the owners, you can review your IdP sign-in logs to review the IP addresses seen in the requests, then allow-list those addresses.
+可以联系要使用的应用的所有者，询问其 IP 范围，并配置 IdP 的 CAP，以允许从这些 IP 范围进行访问。 如果无法联系所有者，可以查看 IdP 登录日志，查看请求中显示的 IP 地址，然后允许列出这些地址。
-If you do not wish to allow all of the IP ranges for all of your enterprise's apps, you can also exempt installed {% data variables.product.prodname_github_apps %} and authorized {% data variables.product.prodname_oauth_apps %} from the IdP allow list. If you do so, these apps will continue working regardless of the originating IP address. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)."
+如果不希望允许所有企业应用的所有 IP 范围，还可以从 IdP 允许列表中免除已安装的 {% data variables.product.prodname_github_apps %} 以及授权的 {% data variables.product.prodname_oauth_apps %}。 如果这样做，无论起始 IP 地址如何，这些应用都将继续工作。 有关详细信息，请参阅“[为企业中的安全设置强制实施策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)”。
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
index 6812965089..b2542dfa32 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
@@ -1,7 +1,7 @@
---
-title: Configuring OIDC for Enterprise Managed Users
+title: 为企业托管用户配置 OIDC
shortTitle: OIDC for managed users
-intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring OpenID Connect (OIDC) single sign-on (SSO) and enable support for your IdP''s Conditional Access Policy (CAP).'
+intro: '可以通过配置 OpenID Connect (OIDC) 单一登录 (SSO) 自动管理对 {% data variables.product.prodname_dotcom %} 上的企业帐户的访问，并启用对 IdP 的条件访问策略 (CAP) 的支持。'
product: '{% data reusables.gated-features.emus %}'
versions:
feature: oidc-for-emu
@@ -10,40 +10,42 @@ topics:
- Authentication
- Enterprise
- SSO
+ms.openlocfilehash: caa557cb976fb60a59572e1623db6be87efeee54
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148179987'
---
-
{% data reusables.enterprise-accounts.azure-emu-support-oidc %}
-## About OIDC for Enterprise Managed Users
+## 关于适用于企业托管用户的 OIDC
-With {% data variables.product.prodname_emus %}, your enterprise uses your identity provider (IdP) to authenticate all members. You can use OpenID Connect (OIDC) to manage authentication for your {% data variables.enterprise.prodname_emu_enterprise %}. Enabling OIDC SSO is a one-click setup process with certificates managed by {% data variables.product.prodname_dotcom %} and your IdP.
+通过 {% data variables.product.prodname_emus %}，企业使用标识提供者 (IdP) 对所有成员进行身份验证。 可以使用 OpenID Connect (OIDC) 管理 {% data variables.enterprise.prodname_emu_enterprise %} 的身份验证。 启用 OIDC SSO 是一个一键式设置过程，证书由 {% data variables.product.prodname_dotcom %} 和你的 IdP 管理。
-{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
+{% data reusables.enterprise-accounts.emu-cap-validates %} 有关详细信息，请参阅“[关于对 IdP 的条件访问策略的支持](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)”。
-You can adjust the lifetime of a session, and how often a {% data variables.enterprise.prodname_managed_user %} needs to reauthenticate with your IdP, by changing the lifetime policy property of the ID tokens issued for {% data variables.product.prodname_dotcom %} from your IdP. The default lifetime is one hour. For more information, see "[Configurable token lifetimes in the Microsoft identity platform](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)" in the Azure AD documentation.
+可以通过从 IdP 更改为 {% data variables.product.prodname_dotcom %} 颁发的 ID 令牌的生存期属性，调整会话的生存期，以及 {% data variables.enterprise.prodname_managed_user %} 需要对 IdP 重新进行身份验证的频率。 默认生存期为 1 小时。 有关详细信息，请参阅 Azure AD 文档中的“[Microsoft 标识平台中的可配置令牌生存期](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)”。
{% data reusables.enterprise_user_management.SAML-to-OIDC-migration-for-EMU %}
{% data reusables.enterprise-accounts.oidc-gei-warning %}
-## Identity provider support
+## 标识提供者支持
-Support for OIDC is available for customers using Azure Active Directory (Azure AD).
+对 OIDC 的支持可供使用 Azure Active Directory (Azure AD) 的客户使用。
-Each Azure AD tenant can support only one OIDC integration with {% data variables.product.prodname_emus %}. If you want to connect Azure AD to more than one enterprise on {% data variables.product.prodname_dotcom %}, use SAML instead. For more information, see "[Configuring SAML single sign-on for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+每个 Azure AD 租户只能支持一个与 {% data variables.product.prodname_emus %} 的 OIDC 集成。 如果要将 Azure AD 连接到 {% data variables.product.prodname_dotcom %} 上的多个企业，请改用 SAML。 有关详细信息，请参阅“[为 {% data variables.product.prodname_emus %} 配置 SAML 单一登录](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)”。
-## Configuring OIDC for Enterprise Managed Users
+## 为企业托管用户配置 OIDC
-1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**.
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-1. Select **Require OIDC single sign-on**.
- 
-1. To continue setup and be redirected to Azure AD, click **Save**.
-{% data reusables.enterprise-accounts.emu-azure-admin-consent %}
-{% data reusables.enterprise-accounts.download-recovery-codes %}
+1. 使用用户名“@SHORT-CODE_admin”以新企业的安装用户身份登录到 {% data variables.product.prodname_dotcom_the_website %}。
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
+1. 选择“要求 OIDC 单一登录”。
+ 
+1. 若要继续设置并重定向到 Azure AD，请单击“保存”。
+{% data reusables.enterprise-accounts.emu-azure-admin-consent %} {% data reusables.enterprise-accounts.download-recovery-codes %}
-## Enabling provisioning
+## 启用设置
-After you enable OIDC SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+启用 OIDC SSO 后，启用预配。 有关详细信息，请参阅“[为企业托管用户配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。
diff --git a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
index a7060df4d0..3606213e54 100644
--- a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
+++ b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
@@ -1,6 +1,6 @@
---
-title: Enabling GitHub Packages with Azure Blob Storage
-intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.'
+title: 使用 Azure Blob 存储启用 GitHub Packages
+intro: '以 Azure Blob 存储作为外部存储设置 {% data variables.product.prodname_registry %} 。'
versions:
ghes: '*'
type: tutorial
@@ -9,42 +9,44 @@ topics:
- Packages
- Storage
shortTitle: Enable Packages with Azure
+ms.openlocfilehash: b851f698baba60323cbaaa69122cacdc92ec83c2
+ms.sourcegitcommit: 3ece72cf2d90987575d369c44101d19d3bb06f76
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190385'
---
-
{% warning %}
-**Warnings:**
-- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
-- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
-- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
+警告：
+- 为存储桶设置所需的限制性访问策略至关重要，因为 {% data variables.product.company_short %} 不会将特定对象权限或其他访问控制列表 (ACL) 应用于存储桶配置。 例如，如果将存储桶设为公共，则在公共互联网上可以访问存储桶中的数据。
+- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶，与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。
+- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后，我们不建议更改存储系统。
{% endwarning %}
-## Prerequisites
+## 先决条件
-Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/).
+在 {% data variables.location.product_location_enterprise %} 上启用和配置 {% data variables.product.prodname_registry %} 之前，需要准备 Azure Blob 存储 Bucket。 若要准备 Azure Blob 存储 Bucket，建议查阅官方 [Azure Blob 存储文档站点](https://docs.microsoft.com/en-us/azure/storage/blobs/)上的官方 Azure Blob 存储文档。
-## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage
+## 使用 Azure Blob 存储启用 {% data variables.product.prodname_registry %}
-{% data reusables.enterprise_site_admin_settings.access-settings %}
-{% data reusables.enterprise_site_admin_settings.management-console %}
-{% data reusables.enterprise_site_admin_settings.packages-tab %}
-{% data reusables.package_registry.enable-enterprise-github-packages %}
-1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %}
+1. 在“包存储”下，选择“Azure Blob 存储”，然后为包存储 Bucket 和连接字符串输入 Azure 容器名称。
- - You must create a storage container prior to setting the container name and connection string.
+ - 在设置容器名称和连接字符串之前，必须创建存储容器。
- 
+ 
{% note %}
- **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
- Usage of a SAS Token or SAS URL as connection string is not currently supported.
+ 注意：可以通过导航到 Azure 存储帐户中的“访问密钥”菜单来查找 Azure 连接字符串。
+ 目前不支持使用 SAS 令牌或 SAS URL 作为连接字符串。
{% endnote %}
{% data reusables.enterprise_management_console.save-settings %}
-## Next steps
+## 后续步骤
{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 991873cdca..041431c2e8 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -56,7 +56,7 @@ You can enforce policies to control how members of your enterprise on {% data va
Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% ifversion ghes or ghae %}
@@ -166,7 +166,7 @@ Across all organizations owned by your enterprise, you can set the default branc
Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 571de5c750..c280d50c8f 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -1,6 +1,6 @@
---
-title: About billing for GitHub Actions
-intro: 'If you want to use {% data variables.product.prodname_actions %} beyond the storage or minutes included in your account, you will be billed for additional usage.'
+title: 关于 GitHub Actions 的计费
+intro: '如果要对 {% data variables.product.prodname_actions %} 的使用超出帐户所含存储容量或分钟数，您需要支付额外的使用费。'
miniTocMaxHeadingLevel: 3
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
@@ -13,103 +13,104 @@ topics:
- Actions
- Spending limits
shortTitle: Billing for GitHub Actions
+ms.openlocfilehash: fcc8f84b8a11b214ca66e8a3851a1afc9df6213a
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191884'
---
-## About billing for {% data variables.product.prodname_actions %}
+## 关于 {% data variables.product.prodname_actions %} 的计费
{% data reusables.actions.actions-billing %}
-{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
+{% data reusables.actions.actions-spending-limit-brief %} 有关详细信息，请参阅“[关于支出限制](#about-spending-limits)”。
-{% ifversion ghec %}
-If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% ifversion ghec %} 如果通过 Microsoft 企业协议购买了 {% data variables.product.prodname_enterprise %}，则可以将 Azure 订阅 ID 连接到企业帐户，以启用和支付超出额度的 {% data variables.product.prodname_actions %} 使用量，包括帐户。 有关详细信息，请参阅“[将 Azure 订阅连接到企业](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)”。
{% endif %}
-Minutes reset every month, while storage usage does not.
+分钟数每月重置一次，而存储空间使用量不会重置。
-### Included storage and minutes
+### 包括存储和分钟数
-{% ifversion actions-hosted-runners %}
-{% note %}
+{% ifversion actions-hosted-runners %} {% note %}
-**Note**: Entitlement minutes cannot be used for Windows and Ubuntu runners over 2-cores. These runners will always be charged for, including in public repos. For more information, see "[Per-minute rates for runners](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)."
+注意：权利分钟数不能用于超过 2 核的 Windows 和 Ubuntu 运行器。 这些运行器将始终收取费用，包括在公共存储库中。 有关详细信息，请参阅“[运行器的每分钟费率](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)”。
-{% endnote %}
-{% endif %}
+{% endnote %} {% endif %}
-|Product | Storage | Minutes (per month)|
+|产品 | 存储 | 分钟数（每月）|
|------- | ------- | ---------|
| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
-| {% data variables.product.prodname_pro %} | 1 GB | 3,000 |
-| {% data variables.product.prodname_free_team %} for organizations | 500 MB | 2,000 |
+| {% data variables.product.prodname_pro %} | 1GB | 3,000 |
+| 组织的 {% data variables.product.prodname_free_team %} | 500 MB | 2,000 |
| {% data variables.product.prodname_team %} | 2 GB | 3,000 |
| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 |
-Jobs that run on Windows and macOS runners that {% data variables.product.prodname_dotcom %} hosts consume minutes at 2 and 10 times the rate that jobs on Linux runners consume. For example, using 1,000 Windows minutes would consume 2,000 of the minutes included in your account. Using 1,000 macOS minutes, would consume 10,000 minutes included in your account.
+在 {% data variables.product.prodname_dotcom %} 主机的 Windows 和 macOS 运行器上运行的作业，其消耗分钟数是在 Linux 运行器上运行的作业的 2 倍和 10 倍。 例如，1,000 分钟的 Windows 使用时间将占用帐户中包含的 2,000 分钟。 1,000 分钟的 macOS 使用时间将占用帐户中包含的 10,000 分钟。
-### Minute multipliers
+### 分钟乘数
-| Operating system | Minute multiplier |
+| 操作系统 | 分钟乘数 |
|------- | ---------|
| Linux | 1 |
| macOS| 10 |
| Windows | 2 |
-The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+仓库使用的存储空间是 {% data variables.product.prodname_actions %} 构件和 {% data variables.product.prodname_registry %} 使用的存储空间总计。 存储成本是帐户拥有的所有存储库的总使用量。 有关 {% data variables.product.prodname_registry %} 计费的详细信息，请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)”。
- If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
+ 如果你的帐户使用量超出了这些限额，并且你设置的支出限额高于 0 美元，则每天的每 GB 存储用量和每分钟用量需要支付 0.008 美元，具体取决于 {% data variables.product.prodname_dotcom %} 托管运行器使用的操作系统。 {% data variables.product.prodname_dotcom %} 将每个作业使用的分钟数和部分分钟数舍入到最接近的分钟整数。
{% note %}
-**Note:** Minute multipliers do not apply to the per-minute rates shown below.
+注意：分钟数乘数不适用于如下所示的每分钟费率。
{% endnote %}
-### Per-minute rates
+### 每分钟费率
-{% data reusables.billing.billing-standard-runners %}
-{%- ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{%- endif %}
+{% data reusables.billing.billing-standard-runners %} {%- ifversion actions-hosted-runners %} {% data reusables.billing.billing-hosted-runners %} {%- endif %}
-- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
-- {% data reusables.user-settings.context_switcher %}
-{% ifversion actions-hosted-runners %}
-- For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
-- Entitlement minutes cannot be used for {% data variables.actions.hosted_runner %}s.
-- The {% data variables.actions.hosted_runner %}s are not free for public repositories.
+- 可在用户或组织帐户的所有仓库中同时运行的作业数量取决于您的 GitHub 计划。 有关详细信息，请参阅 {% data variables.product.prodname_dotcom %} 托管运行器的“[使用限制和计费](/actions/reference/usage-limits-billing-and-administration)”和自托管运行器使用限制的“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)”。
+- {% data reusables.user-settings.context_switcher %} {% ifversion actions-hosted-runners %}
+- 对于 {% data variables.actions.hosted_runner %}，将公共静态 IP 地址分配给 {% data variables.actions.hosted_runner %} 的配置没有额外成本。 有关 {% data variables.actions.hosted_runner %} 的详细信息，请参阅“[使用 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-larger-runners)”。
+- 权利分钟数不能用于 {% data variables.actions.hosted_runner %}。
+- {% data variables.actions.hosted_runner %} 针对公共存储库不是免费的。
{% endif %}
-## Calculating minute and storage spending
+## 计算分钟和存储支出
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_actions %}
-At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account.
+在月末，{% data variables.product.prodname_dotcom %} 会计算您使用的超过帐户自带限额的分钟数和存储空间费用。
-### Sample minutes cost calculation
+### 样品分钟数成本计算
-For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
+例如，如果您的组织使用 {% data variables.product.prodname_team %} 并允许无限制支出，则使用 5,000 分钟可能会产生 56 美元的总存储空间和分钟数超额费用，具体取决于用于运行作业的操作系统。
-- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
- - 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
- - 2,000 Windows minutes at $0.016 USD per minute = $32 USD.
+- 5,000（3,000 Linux 加 2,000 Windows）分钟 = $56 ($24 + $32)。
+ - 3,000 Linux 分钟（每分钟 $0.008）= $24。
+ - 2,000 Windows 分钟（每分钟 $0.016）= $32。
-{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month.
+{% data variables.product.prodname_dotcom %} 根据每个月的小时用量计算该月的存储使用量。
-### Sample storage cost calculation
+### 样品存储成本计算
-For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be:
+例如，如果在三月的 10 天内使用 3 GB 的存储，在三月的 21 天使用 12 GB 的存储，则存储使用量为：
-- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours
-- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours
-- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours
-- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months
+- 3 GB x 10 天 x（每天 24 小时）= 720 GB-小时
+- 12 GB x 21 天 x（每天 24 小时）= 6,048 GB-小时
+- 720 GB-小时 + 6,048 GB-小时 = 6,768 GB-小时
+- 6,768 GB-小时 / (每月 744 小时) = 9.0967 GB-月
-At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
+到月底，{% data variables.product.prodname_dotcom %} 会将您的存储量舍入到最接近的 MB。 因此，三月的存储使用量为 9.097 GB。
-Your {% data variables.product.prodname_actions %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
+{% data variables.product.prodname_actions %} 使用将共用帐户的现有计费日期、付款方式和收据。 {% data reusables.dotcom_billing.view-all-subscriptions %}
-## About spending limits
+## 关于支出限制
{% data reusables.actions.actions-spending-limit-detailed %}
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+有关管理和更改帐户支出限制的信息，请参阅“[管理 {% data variables.product.prodname_actions %} 的支出限制](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)”。
{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
diff --git a/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md b/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
index d6daeb7614..b13a65174d 100644
--- a/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
+++ b/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md
@@ -1,6 +1,6 @@
---
-title: Managing privately reported security vulnerabilities
-intro: Repository maintainers can manage security vulnerabilities that have been privately reported to them by security reseachers for repositories where private vulnerability reporting is enabled.
+title: 管理私下报告的安全漏洞
+intro: 存储库维护人员可以管理由存储库安全研究人员向其私下报告的安全漏洞，这些存储库已启用了非公开漏洞报告。
permissions: 'Anyone with admin permissions to a repository can see, review, and manage privately-reported vulnerabilities for the repository.'
versions:
fpt: '*'
@@ -11,35 +11,38 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Manage vulnerability reports
+ms.openlocfilehash: 942533788dc6ad9280ddc023f583462c7a0ff7f8
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159786'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## 关于私下报告安全漏洞
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to you using a simple form.
+通过非公开漏洞报告，安全研究人员可以轻松使用简单的表单直接向你报告漏洞。
-When a security researcher reports a vulnerability privately, you are notified and can choose to either accept it, ask more questions, or reject it. If you accept the report, you're ready to collaborate on a fix for the vulnerability in private with the security researcher.
+当安全研究人员私下报告漏洞时，你会收到通知并且可以选择接受报告、提出更多问题或拒绝报告。 如果接受报告，则可以与安全研究人员私下协作修复漏洞。
-## Managing security vulnerabilities that are privately reported
+## 管理私下报告的安全漏洞
-{% data variables.product.prodname_dotcom %} notifies repository maintainers when security researchers privately report vulnerabilities in their repository, and sends notifications if maintainers watch the repository or if they have notifications enabled for the repository. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
+当安全研究人员私下报告存储库中的漏洞时，{% data variables.product.prodname_dotcom %} 会通知存储库维护人员，并在维护人员监视存储库或为存储库启用通知的情况下发送通知。 有关详细信息，请参阅“[配置通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)”。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click the advisory you want to review. An advisory that is privately reported will have a status of `Needs triage`.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. 单击要查看的通告。 私下报告的通告的状态为 `Needs triage`。
- 
+ 
-2. Carefully review the report. You can:
- - Collaborate with the security researcher on a patch in private, by clicking **Start a temporary private fork**. This gives you a place for further discussions with the contributor without changing the status of the proposed advisory from `Needs triage`.
- - Accept the vulnerability report as a draft advisory on {% data variables.product.prodname_dotcom %}, by clicking **Accept and open as draft**. If you choose this option:
- - This doesn't make the report public.
- - The report becomes a draft repository security advisory and you can work on it in the same way as any draft advisory that you create.
- For more information on security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."
- - Reject the report by clicking **Close security advisory**. Where possible, you should add a comment explaining why you don't consider the report a security risk before you close the advisory.
+2. 仔细查看报告。 可以：
+ - 单击“启动临时专用分叉”，与安全研究人员私下协作生成修补程序。 这为你提供了一个与参与者进一步讨论的空间，而无需从 `Needs triage` 更改建议的通告状态。
+ - 单击“接受并作为草稿打开”，在 {% data variables.product.prodname_dotcom %} 上将漏洞报告作为草稿通告接受。 如果你选择此选项：
+ - 该选项不会公开报表。
+ - 报表将成为存储库安全通告草稿，可以采用与创建的任何草稿通告相同的方式使用它。
+ 有关安全通告的详细信息，请参阅“[关于存储库安全通告](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)”。
+ - 单击“关闭安全通告”可拒绝报告。 在可能的情况下，在关闭通告之前应添加注释，解释为什么不将报告内容视为安全风险。
- 
\ No newline at end of file
+ 
diff --git a/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md b/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
index 521fa86d92..15ce371e67 100644
--- a/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
+++ b/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md
@@ -1,6 +1,6 @@
---
-title: Privately reporting a security vulnerability
-intro: Some public repositories configure security advisories so that anyone can report security vulnerabilities directly and privately to the maintainers.
+title: 私下报告安全漏洞
+intro: 某些公共存储库配置安全公告，以便任何人都可以直接并私下向维护人员报告安全漏洞。
versions:
fpt: '*'
ghec: '*'
@@ -10,61 +10,64 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Privately reporting
+ms.openlocfilehash: 7f4f208bd2724608cf9955efd82a256c3479e884
+ms.sourcegitcommit: 2ff4a43f0b14939da79d56c54402cfee8d90ae23
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/17/2022
+ms.locfileid: '148169555'
---
-
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
-## About privately reporting a security vulnerability
+## 关于私人报告安全漏洞
-Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
+安全研究人员通常有责任提醒用户注意可能被利用的漏洞。 如果没有关于联系包含该漏洞的存储库的维护人员的明确说明，安全研究人员可能别无选择，只好在社交媒体上发布该漏洞，直接向维护人员发送消息，甚至提出公共问题。 这种情况可能会导致公开披露漏洞详细信息。
-Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to repository maintainer using a simple form.
+通过私下漏洞报告，安全研究人员可以轻松地使用简单的表单直接向存储库维护人员报告漏洞。
-For security researchers, the benefits of using private vulnerability reporting are:
-- Less frustration, and less time spent trying to figure out how to contact the maintainer.
-- A smoother process for disclosing and discussing vulnerability details.
-- The opportunity to discuss vulnerability details privately with repository maintainer.
+对于安全研究人员来说，使用私下漏洞报告的好处是：
+- 减少挫折感，减少花费在尝试如何联系维护人员的时间。
+- 披露和讨论漏洞详细信息的过程更顺畅。
+- 有机会与存储库维护人员私下讨论漏洞详细信息。
{% note %}
-**Note:** If the repository doesn't have private vulnerabiliy reporting enabled, you need to initiate the reporting process by following the instructions in the security policy for the repository, or create an issue asking the maintainers for a preferred security contact. For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
+注意：如果存储库未启用私下漏洞报告，则需要按照存储库的安全策略中的说明启动报告过程，或者创建问题，让维护人员提供首选的安全联系人。 有关详细信息，请参阅“[关于协调披露安全漏洞](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)”。
{% endnote %}
-## Privately reporting a security vulnerability
+## 私下报告安全漏洞
-Security researchers can privately report a security vulnerability to repository maintainers.
+安全研究人员可以私下向存储库维护人员报告安全漏洞。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **Report a vulnerability** to open the advisory form.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. 单击“报告漏洞”可打开咨询表单。
- 
+ 
-2. Fill in the advisory details form.
+2. 填写咨询详细信息表单。
{% tip %}
- **Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
+ 提示：在此表单中，只有标题和说明是必填的。 （在存储库维护人员启动的一般安全咨询表单草稿中，还需要指定生态系统。）但是，建议安全研究人员在表单上提供尽可能多的信息，以便维护人员可以就提交的报告做出明智的决定。 可以采用我们的安全研究人员从 {% data variables.product.prodname_security %} 使用的模板，该模板可在 [`github/securitylab` 存储库](https://github.com/github/securitylab/blob/main/docs/report-template.md)中获取。
{% endtip %}
- For more information about the fields available and guidance on filling in the form, see "[Creating a repository security advisory](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[Best practices for writing repository security advisories](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
+ 有关可用字段和填写表单的指导的详细信息，请参阅“[创建存储库安全公告](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)”和“[编写存储库安全公告的最佳做法](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)”。
-1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
+1. 在表单底部，单击“提交报告”。 {% data variables.product.prodname_dotcom %} 将显示一条消息，告知你已通知维护人员，并且你拥有此安全公告的待处理额度。
- 
+ 
{% tip %}
- **Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
+ 提示：提交报告后，{% data variables.product.prodname_dotcom %} 会自动将漏洞报告者添加为协作者，并在建议的公告中作为信用用户添加。
{% endtip %}
-1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge that private fork.
+1. （可选）如果要开始修复问题，单击“启动临时专用分支”。 请注意，只有存储库维护人员才能合并该专用分支。
- 
+ 
-The next steps depend on the action taken by the repository maintainer. For more information, see "[Managing privately reported security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)."
+后续步骤取决于存储库维护人员执行的操作。 有关详细信息，请参阅“[管理私下报告的安全漏洞](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)”。
diff --git a/translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
index 8f8ea3d298..36a58e4f77 100644
--- a/translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
+++ b/translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository security advisory
-intro: You can create a draft security advisory to privately discuss and fix a security vulnerability in your open source project.
+title: 创建存储库安全公告
+intro: 您可以创建安全通告草稿，以私下讨论和修复开源项目中的安全漏洞。
redirect_from:
- /articles/creating-a-maintainer-security-advisory
- /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
@@ -15,31 +15,31 @@ topics:
- Security advisories
- Vulnerabilities
shortTitle: Create repository advisories
+ms.openlocfilehash: 5c78a8b0c0a2d5085a876de2b0788ef093c4c6b1
+ms.sourcegitcommit: 74c60a4564bcc17e47b5a67941ac6d9fe13b6a5c
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/30/2022
+ms.locfileid: '148186153'
---
-
-Anyone with admin permissions to a repository can create a security advisory.
+任何对仓库有管理员权限的人都可以创建安全通告。
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-## Creating a security advisory
+## 创建安全通知
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-security %}
-{% data reusables.repositories.sidebar-advisories %}
-1. Click **New draft security advisory** to open the draft advisory form. The fields marked with an asterisk are required.
- 
-1. Type a title for your security advisory.
-{% data reusables.repositories.security-advisory-edit-details %}
-{% data reusables.repositories.security-advisory-edit-severity %}
-{% data reusables.repositories.security-advisory-edit-cwe-cve %}
-{% data reusables.repositories.security-advisory-edit-description %}
-1. Click **Create draft security advisory**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+1. 单击“新建安全公告草稿”，打开草稿公告表单。 带有星号的所有字段为必填项。
+ 
+1. 键入安全通告的标题。
+{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
+1. 单击“创建安全公告草稿”。
+ 
-## Next steps
+## 后续步骤
-- Comment on the draft security advisory to discuss the vulnerability with your team.
-- Add collaborators to the security advisory. For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)."
-- Privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)."
-- Add individuals who should receive credit for contributing to the security advisory. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)."
-- Publish the security advisory to notify your community of the security vulnerability. For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
+- 评论安全通告草稿，与团队讨论漏洞。
+- 添加协作者到安全通告。 有关详细信息，请参阅“[将协作者添加到存储库安全公告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)”。
+- 在临时私有复刻中私下协作以修复漏洞。 有关详细信息，请参阅“[在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”。
+- 添加因对安全通告做出贡献而应获得积分的个人。 有关详细信息，请参阅“[编辑存储库安全公告](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)”。
+- 发布安全通告以向社区提醒安全漏洞。 有关详细信息，请参阅“[发布存储库安全公告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”。
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
index aeb477c475..05b77ff9b0 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a codespace for a repository
-intro: You can create a codespace for a branch in a repository to develop online.
+title: 为存储库创建 codespace
+intro: 您可以为仓库中的分支创建代码空间以便在线开发。
redirect_from:
- /github/developing-online-with-github-codespaces/creating-a-codespace
- /github/developing-online-with-codespaces/creating-a-codespace
@@ -14,95 +14,100 @@ topics:
- Fundamentals
- Developer
shortTitle: Create a codespace for a repo
+ms.openlocfilehash: 409c946feda4ffbd3d9ab615b6ea07fabee3f530
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188318'
---
+## 关于为存储库创建 codespace
-## About creating a codespace for a repository
+{% data reusables.codespaces.ways-to-create-a-codespace %}使用本文中的选项卡显示有关创建 codespace 的每种方法的说明。
-{% data reusables.codespaces.ways-to-create-a-codespace %} Use the tabs in this article to display instructions for each of these ways of creating a codespace.
-
-{% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+{% data reusables.codespaces.starting-new-project-template %}有关详细信息，请参阅“[通过模板创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)”。
{% note %}
-**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[Using Codespaces in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
+注意：如果使用 JetBrains IDE，则可以使用 {% data variables.product.prodname_cli %} 创建 codespace。 然后，你就可以使用 JetBrains Gateway 应用程序在 JetBrains IDE 中打开 codespace。 有关详细信息，请参阅“[在 JetBrains IDE 中使用 Codespaces](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)”。
{% endnote %}
-You can use {% data variables.product.prodname_github_codespaces %} on your personal {% data variables.product.prodname_dotcom_the_website %} account, with the quota of free use included each month for accounts on the Free and Pro plans. {% data reusables.codespaces.codespaces-continue-by-paying %}
+可以在个人 {% data variables.product.prodname_dotcom_the_website %} 帐户上使用 {% data variables.product.prodname_github_codespaces %}，其中免费版和专业版计划中的帐户包含每月免费使用配额。 {% data reusables.codespaces.codespaces-continue-by-paying %}
-Organizations can enable members and outside collaborators to create and use codespaces at the organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
+组织可以让成员和外部协作者能够创建和使用 codespace，费用由组织承担。 有关详细信息，请参阅“[为组织启用 {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)”。
{% data reusables.codespaces.codespaces-are-personal %}
-If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch.
+如果从存储库创建 codespace，该 codespace 将与不能为空的特定分支相关联。 每个仓库甚至每个分支可创建多个代码空间。
{% data reusables.codespaces.you-can-see-all-your-codespaces %}
-### The codespace creation process
+### codespace 创建过程
-When you create a codespace, a number of steps happen to create and connect you to your development environment:
+创建代码空间时，需要执行一些步骤并将您连接到开发环境。
-- Step 1: VM and storage are assigned to your codespace.
-- Step 2: Container is created and your repository is cloned.
-- Step 3: You can connect to the codespace.
-- Step 4: Codespace continues with post-creation setup.
+- 第 1 步：虚拟机和存储被分配到您的代码空间。
+- 第 2 步：创建容器并克隆仓库。
+- 第 3 步：您可以连接到代码空间。
+- 第 4 步：代码空间继续创建后设置。
-For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
+有关创建 codespace 时发生的情况的详细信息，请参阅“[深入探讨](/codespaces/getting-started/deep-dive)。”
-For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)."
+有关 codespace 生命周期的详细信息，请参阅“[codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle)”。
-If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+如果要对 codespace 使用 Git 挂钩，则应在步骤 4 中使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)（如 `postCreateCommand`）设置挂钩。 由于在克隆存储库之后创建了 codespace 容器，因此在容器映像中配置的任何[ git 模板目录](https://git-scm.com/docs/git-init#_template_directory)将不适用于你的 codespace。 在创建代码空间后，必须改为安装挂钩。 有关使用 `postCreateCommand` 的详细信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的 [`devcontainer.json` 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties)。
{% data reusables.codespaces.use-visual-studio-features %}
{% data reusables.codespaces.prebuilds-crossreference %}
-## Creating a codespace for a repository
+## 为存储库创建 codespace
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create a codespace for.
+1. 在存储库名称下，使用“分支”下拉菜单，然后选择要为其创建 codespace 的分支。
- 
+ 
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. 单击“{% octicon "code" aria-label="The code icon" %} 代码”按钮，然后单击“codespace”选项卡。
- 
+ 
- If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
+ 如果此存储库的 codespace 的计费对象为组织或其父企业，则会在“在 BRANCH 上创建 codespace”按钮下方显示一条消息，告知谁将为 codespace 付费。
-1. Create your codespace, either using the default options, or after configuring advanced options:
+1. 使用默认选项或在配置高级选项之后创建 codespace：
- * **Use the default options**
+ * 使用默认选项
- To create a codespace using the default options, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). Alternatively, if you don't currently have any codespaces for this repository, you can click **Create codespace on BRANCH**.
+ 要使用默认选项创建 codespace，请单击“加号 ({% octicon "plus" aria-label="The plus icon" %})”。 如果当前没有此存储库的任何 codespace，也可以单击“在 BRANCH 上创建 codespace”。
- * **Configure options**
+ * **配置选项**
- To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file:
+ 若要配置 codespace 高级选项（例如其他计算机类型或特定 `devcontainer.json` 文件），请执行以下操作：
- 1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab and select **New with options**.
+ 1. 单击“Codespaces”选项卡右上角的省略号 (…)，然后单击“使用选项新建” 。
- 
+ 
- 1. On the options page for your codespace, choose your preferred options from the dropdown menus.
+ 1. 在 codespace 选项页上，从下拉菜单中选择首选选项。
- 
+ 
{% note %}
- **Notes**
+ **说明**
- * You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
- * The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
- * For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
- * For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+ * 可以为选项页添加书签，以便快速创建此存储库和分支的 codespace。
+ * [https://github.com/codespaces/new](https://github.com/codespaces/new) 页提供了为任何存储库和分支创建 codespace 的快速方法。 可以通过在浏览器的地址栏中输入 `codespace.new` 来快速访问此页面。
+ * 有关 `devcontainer.json` 文件的详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)”。
+ * 有关计算机类型的详细信息，请参阅“[更改 codespace 的计算机类型](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)”。
* {% data reusables.codespaces.codespaces-machine-type-availability %}
{% endnote %}
- 1. Click **Create codespace**.
+ 1. 单击“创建 codespace”。
{% endwebui %}
@@ -116,30 +121,30 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
{% data reusables.cli.cli-learn-more %}
-To create a new codespace, use the `gh codespace create` subcommand.
+若要创建新的 codespace，请使用 `gh codespace create` 子命令。
```shell
gh codespace create
```
-You are prompted to choose a repository. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
+系统会提示你选择存储库。 如果此存储库的 codespace 的计费对象为组织或其父企业，则会显示一条消息，告知谁将为 codespace 付费。 系统将提示你选择分支、开发容器配置文件（如果有多个可用）和计算机类型（如果有多个可用）。
-Alternatively, you can use flags to specify some or all of the options:
+或者，您可以使用标志来指定部分或全部选项：
```shell
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
```
-In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
+在此示例中，将 `owner/repo` 替换为存储库标识符。 将 `branch` 替换为你希望最初在 codespace 中签出的分支的名称或提交的完整 SHA 哈希。 如果使用 `-r` 标志而不使用 `b` 标志，则从默认分支创建 codespace。
-Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+将 `path` 替换为要用于新的 codespace 的开发容器配置文件的路径。 如果省略此标志，并且有多个开发容器文件可用，系统将提示你从列表中选择一个文件。 有关开发容器配置文件的详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
-Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
+将 `machine-type` 替换为可用计算机类型的有效标识符。 标识符是字符串，例如：`basicLinux32gb` 和 `standardLinux32gb`。 可用的计算机类型取决于存储库、个人帐户以及你的位置。 如果输入无效或不可用的计算机类型，则错误消息中将显示可用类型。 如果省略此标志，并且有多个计算机类型可用，系统将提示您从列表中选择一个计算机类型。
-For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
+有关此命令的选项的完整详细信息，请参阅 [{% data variables.product.prodname_cli %} 手册](https://cli.github.com/manual/gh_codespace_create)。
{% endcli %}
-## Further reading
-- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
-- "[Adding an 'Open in {% data variables.product.prodname_github_codespaces %}' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
+## 延伸阅读
+- “[打开现有 codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)”
+- [添加“在 {% data variables.product.prodname_github_codespaces %} 中打开”徽章](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
index 842a20e971..13b8871069 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md
@@ -1,6 +1,6 @@
---
-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.
+title: 通过模板创建 codespace
+intro: 如果要启动新项目，可以通过空白模板创建 codespace，或者选择专为你要执行的工作类型设计的模板。
versions:
fpt: '*'
ghec: '*'
@@ -11,92 +11,95 @@ topics:
- Developer
shortTitle: Create a codespace from a template
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 9e7ee0d110e962fa755f5f57cc70bc3cab341808
+ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148188310'
---
+## 关于适用于 {% data variables.product.prodname_github_codespaces %} 的模板
-## 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.
+如果要启动新项目，可以通过从模板创建 codespace 来快速开始开发工作。 你将能够在基于云的开发环境中处理项目、将文件保存在云中，以及将工作发布到可与他人共享或克隆到本地计算机的新远程存储库中。
{% 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)."
+注意：通过模板（而不是存储库）创建的 codespace 将始终向个人帐户计费。 有关详细信息，请参阅“[关于 {% 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)."
+可以从空白模板开始着手，从 {% data variables.product.company_short %} 维护的模板中选择 React 或 Jupyter Notebook 等常用技术，或者从 {% data variables.product.prodname_dotcom %} 上的任何模板存储库中启动 codespace。 使用空白模板时，你将从空目录开始创建，并且可以访问基于云的计算资源，以及预安装了默认 codespace 映像的工具、语言和运行时环境。 使用其他模板时，你将获得当前所用技术的入门文件，通常还有一些额外文件，例如自述文件、`.gitignore` 文件和包含一些自定义环境配置的开发容器配置文件。 有关开发容器和默认映像的详细信息，请参阅“[开发容器简介](/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.
+例如，如果通过 {% data variables.product.company_short %} 的React 模板创建 codespace，则将到达包含简单应用程序的模板文件的工作区中，例如 `index.js`、`app.js` 和 `package.json`。 在 codespace 打开后不久，开发服务器将自动启动，并且你将能够在 {% data variables.product.prodname_vscode_shortname %} Web 客户端内的简单浏览器选项卡中查看正在运行的应用程序。
-
+
-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.
+模板中包含的文件和配置在模板存储库中定义。 创建 codespace 时，模板存储库将克隆到 codespace 中。 之后，链接将被切断，并且 codespace 将不会链接到远程存储库，直到你发布到远程存储库为止。
{% 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)."
+提示：为了帮助用户开始使用你的框架、库或其他项目，你可以设置模板存储库，以便与 {% data variables.product.prodname_github_codespaces %} 配合使用。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_github_codespaces %} 的模板存储库](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)”。
{% endtip %}
-## Creating a codespace from a {% data variables.product.company_short %} template
+## 通过 {% data variables.product.company_short %} 模板创建 codespace
-Templates maintained by {% data variables.product.company_short %}, including the blank template, are available from the "Your codespaces" page.
+{% data variables.product.company_short %} 维护的模板（包括空白模板）在“你的 codespace”页中提供。
-{% 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.
+{% data reusables.codespaces.your-codespaces-procedure-step %} {% data reusables.codespaces.view-all-templates-step %}
+1. （可选）若要查看包含模板文件的模板存储库，请单击模板的名称。
- 
+ 
-1. Under the template you want to launch, click **Use this template**.
+1. 在要启动的模板下，单击“**使用此模板**”。
- 
+ 
{% data reusables.codespaces.template-codespaces-default-editor %}
-## Creating a codespace from a template repository
+## 通过模板存储库创建 codespace
-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)."
+可以通过任何模板存储库创建 codespace，然后在准备就绪后将工作发布到新存储库。 有关模板存储库的详细信息，请参阅“[通过模板创建存储库](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates)”。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.codespaces.open-template-in-codespace-step %}
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.codespaces.open-template-in-codespace-step %}
{% note %}
- **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)."
+ 备注：如果你是模板存储库的维护者，并且要将更改提交到模板存储库本身，则应通过“{% octicon "code" aria-label="The code icon" %} 代码”下拉列表创建 codespace 。 有关详细信息，请参阅“[为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)”。
{% endnote %}
{% data reusables.codespaces.template-codespaces-default-editor %}
-## Publishing to a repository on {% data variables.product.product_name %}
+## 发布到 {% data variables.product.product_name %} 上的存储库
{% data reusables.codespaces.about-publishing-templates %}
-### Publishing from {% data variables.product.prodname_vscode_shortname %}
+### 从 {% 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:
+发布 codespace 后，你可以使用更多选项来自定义 {% data variables.product.prodname_github_codespaces %} 体验。 例如，你能够：
-- Change the machine type of your codespace to make sure you're using resources appropriate for the work you're doing (see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)").
-- Allow {% data variables.product.prodname_dotcom %} to automatically use GPG to sign commits you make in your codespace (see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)").
-- Share encrypted secrets with your codespace (see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)").
+- 更改 codespace 的计算机类型，以确保使用适合你当前所执行工作的资源（请参阅“[更改 codespace 的计算机类型](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)”）。
+- 允许 {% data variables.product.prodname_dotcom %} 自动使用 GPG 对 codespace 中的提交进行签名（请参阅“[管理 {% data variables.product.prodname_github_codespaces %} 的 GPG 验证](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)”）。
+- 与 codespace 共享加密机密（请参阅“[管理 codespace 的加密机密](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)”）。
-### Publishing from {% data variables.product.prodname_dotcom_the_website %}
+### 从 {% 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 variables.product.prodname_dotcom_the_website %} 上“你的 codespaces”页面中发布未发布的 codespace。 如果要发布当前未在浏览器中打开的 codespace，此做法非常有用。 如果执行此操作，你的工作将保留在存储库中，但现有 codespace 和新存储库之间不会有链接。 但是，你可以导航到新存储库并从那里创建 codespace，并且此 codespace 将连接到存储库。
{% data reusables.codespaces.your-codespaces-procedure-step %}
-1. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**.
+1. 在未发布的 codespace 旁边，单击省略号 (...) ，然后选择“发布到新存储库” 。
- 
-1. Choose a name for your new repository, set it as **Public** or **Private**, and click **Create repository**.
+ 
+1. 为新存储库选择一个名称，将其设置为“公共”或“专用”，然后单击“创建存储库” 。
- 
-1. Optionally, to view the new repository, click **See repository**.
+ 
+1. （可选）若要查看新存储库，请单击“查看存储库”。
-## Further reading
+## 延伸阅读
-- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)"
-- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)"
-- "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
\ No newline at end of file
+- [为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)
+- [codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle)
+- [在 codespace 中使用源代码管理](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)
diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
index c3d2e0b4af..271c02ff9d 100644
--- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
@@ -9,12 +9,12 @@ topics:
- Codespaces
redirect_from:
- /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds
-ms.openlocfilehash: e0962e410f2227a23ff98c8a3e7995ea8ec8a914
-ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.openlocfilehash: eecb77b541cc735fcf788fbc5da6960cabad899d
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: zh-CN
-ms.lasthandoff: 11/09/2022
-ms.locfileid: '148158795'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191916'
---
## 概述
diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
index c7605e66fc..651ee7f05b 100644
--- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Configuring prebuilds
+title: 配置预生成
shortTitle: Configure prebuilds
-intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
+intro: 可以配置项目，使其在你每次将更改推送到存储库时自动预生成 codespace。
versions:
fpt: '*'
ghec: '*'
@@ -10,106 +10,111 @@ topics:
- Codespaces
- Set up
permissions: People with admin access to a repository can configure prebuilds for the repository.
+ms.openlocfilehash: dbb355e150695f27d1d6a7fa51eccc33a0ebde4f
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159115'
---
+可以为存储库的特定分支与特定开发容器配置文件的组合设置预生成配置。
-You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file.
+从启用预生成的父分支创建的所有分支通常也会获得同一开发容器配置的预生成。 这是因为使用父分支所用开发容器配置的子分支的预生成在大多数情况下是相同的，因此可以帮助开发人员从这些分支更快地创建 codespace。 有关详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
-Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because prebuilds for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+通常，如果为分支配置预生成，预生成可用于多种计算机类型。 但是，如果存储库大于 32 GB，预生成就不适用于 2 核和 4 核计算机类型，因为这些计算机类型提供的存储限制为 32 GB。
-Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB.
+## 先决条件
-## Prerequisites
+预生成是使用 {% data variables.product.prodname_actions %} 创建的。 因此，必须在要为其配置预生成的存储库中启用 {% data variables.product.prodname_actions %}。 有关详细信息，请参阅“[管理存储库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)”。
-Prebuilds are created using {% data variables.product.prodname_actions %}. As a result, {% data variables.product.prodname_actions %} must be enabled for the repository for which you are configuring prebuilds. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)."
-
-## Configuring prebuilds
+## 配置预生成
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
+1. 在页面的“预生成配置”部分，单击“设置预生成”。
- 
+ 
-1. Choose the branch for which you want to set up prebuilds.
+1. 选择要为其设置预生成的分支。
- 
+ 
{% note %}
- **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
+ **注意**：从启用预生成的基础映像分支创建的所有分支通常也会获得同一开发容器配置的预生成。 例如，如果在存储库的默认分支上为开发容器配置文件启用预生成，则大多数情况下，基于默认分支的分支也会获得同一开发容器配置的预生成。
{% endnote %}
-1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
+1. 根据需要，可以在显示的“配置文件”下拉菜单中选择要用于预生成的 `devcontainer.json` 配置文件。 有关详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)”。
- 
+ 
-1. Choose how you want to automatically trigger prebuild updates.
+1. 选择要如何自动触发预生成更新。
- * **Every push** (the default setting) - With this setting, prebuilds will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies.
- * **On configuration change** - With this setting, prebuilds will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The {% data variables.product.prodname_actions %} workflow that updates the prebuilds will run less often, so this option will use fewer {% data variables.product.prodname_actions %} minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created.
- * **Scheduled** - With this setting, you can have your prebuilds updated on a custom schedule that's defined by you. This can reduce consumption of {% data variables.product.prodname_actions %} minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes.
+ * 每次推送（默认设置）- 通过此设置，预生成将在每次对给定分支进行推送时更新。 这可确保从预生成生成的 codespace 始终包含最新的 codespace 配置，包括任何最近添加或更新的依赖项。
+ * 配置更改时 - 使用此设置时，每次更新给定存储库和分支的相关配置文件时，都会更新预生成。 这可确保在从预生成生成 codespace 时使用对存储库的开发容器配置文件进行的更改。 更新预生成的 {% data variables.product.prodname_actions %} 工作流的运行频率较低，因此此选项使用的 {% data variables.product.prodname_actions %} 分钟数较少。 但是，此选项不保证 codespace 始终包含最近添加或更新的依赖项，因此在创建 codespace 后可能需要手动添加或更新这些依赖项。
+ * 计划 - 使用此设置，可以根据你定义的自定义计划更新预生成。 这可以减少 {% data variables.product.prodname_actions %} 分钟数消耗，但是，使用此选项，可以创建 codespace，而不使用最新的开发容器配置更改。
- 
+ 
-1. Optionally, select **Reduce prebuild available to only specific regions** to create prebuilds only in specified regions. Select the regions in which you want prebuilds to be available.
+1. 根据需要，可以选择“减少仅对特定区域可用的预生成”，以便仅在指定区域中创建预生成。 选择要在其中提供预生成的区域。
- By default, prebuilds are created in all of the available regions, incurring storage charges per prebuild.
+ 默认情况下，预生成在所有可用区域中创建，每个预生成都会产生存储费用。
- 
+ 
{% note %}
- **Notes**:
- * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
- * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
+ **注释**：
+ * 每个区域的预生成会产生单独的存储费用。 因此，应只为已知将使用的区域启用预生成。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)”。
+ * 开发人员可以为 {% data variables.product.prodname_github_codespaces %} 设置其默认区域，这样就可以减少要启用预生成的区域。 有关详细信息，请参阅“[为 {% data variables.product.prodname_github_codespaces %} 设置默认区域](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)”。
{% endnote %}
-1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved.
+1. 根据需要，可以在“模板历史记录”下设置要保留的预生成模板版本数。 可以输入介于 1 和 5 之间的任意数字。 默认保存的版本数为 2，这意味着只保存最新版本的和上一个版本的预生成。
- 
+ 
- Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. This setting allows you to set the number of retained versions to a level that is appropriate for your needs.
+ 根据预生成触发器设置，预生成可能会随每个推送或每个开发容器配置的更改而更改。 保留较旧版本的预生成使你能够使用与当前预生成不同的开发容器配置从较旧的提交创建预生成。 通过此设置可将保留的版本数设置为所需的级别。
- If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration.
+ 如果将保存的预生成版本数设置为 1，{% data variables.product.prodname_github_codespaces %} 将仅保存最新版本的预生成，并在每次模板更新时删除旧版本。 这意味着，如果返回到较旧的开发容器配置，则不会获取预生成的 codespace。
- There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+ 保留的每个预生成版本都需支付存储费用。 例如，如果要在 4 个区域中生成预生成并保留 2 个版本，则最多需要支付 8 个预生成的存储费用。 有关计费的详细信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)”。
-1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation.
+1. 根据需要，可以添加用户或团队，以便在此配置的预生成工作流运行失败时发出通知。 可以开始键入用户名、团队名称或全名，然后在显示名称后单击该名称以将其添加到列表中。 发生预生成失败时，添加的用户或团队将收到电子邮件，其中包含工作流运行日志链接，以帮助进一步调查。
- 
+ 
-1. Optionally, at the bottom of the page, click **Show advanced options**.
+1. 根据需要，单击页面底部的“显示高级选项”。
- 
+ 
- In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
+ 在“高级选项”部分中，如果选择“禁用预生成优化”，则当最新的预生成工作流失败或当前正在运行时，将在没有预生成的情况下创建 codespace。 有关详细信息，请参阅“[预生成故障排除](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)”。
-1. Click **Create**.
+1. 单击“创建”。
{% data reusables.codespaces.prebuilds-permission-authorization %}
-After you create a prebuild configuration it is listed on the {% data variables.product.prodname_github_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuilds in the regions you specified, based on the branch and dev container configuration file you selected.
+创建预生成配置后，它会列在存储库设置的 {% data variables.product.prodname_github_codespaces %} 页面中。 {% data variables.product.prodname_actions %} 工作流已排队，然后会运行，从而根据所选分支和开发容器配置文件在指定的区域中创建预生成。
-
+
-For information about editing and deleting prebuild configurations, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)."
+有关编辑和删除预生成配置的信息，请参阅“[管理预生成](/codespaces/prebuilding-your-codespaces/managing-prebuilds)”。
-## Configuring environment variables
+## 配置环境变量
-To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)."
+若要让预生成过程能够访问创建开发环境所需的环境变量，可将这些变量设置为 {% data variables.product.prodname_codespaces %} 存储库机密或为 {% data variables.product.prodname_codespaces %} 组织机密。 有关详细信息，请参阅“[为存储库添加机密](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)”和“[为组织添加机密](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)”。
-Secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces.
+以这种方式创建的机密将由从该存储库创建 codespace 的任何人访问。 如果不希望这样，也可以设置 `CODESPACES_PREBUILD_TOKEN` 机密。 `CODESPACES_PREBUILD_TOKEN` 机密仅用于预生成，并且无法在用户的 codespace 中访问其值。
-Prebuilds cannot use any user-level secrets while building your environment, because these are not available until after the codespace has been created.
+预生成在生成环境时不会使用任何用户级机密，因为这些机密在创建 codespace 后才会可用。
-## Configuring time-consuming tasks to be included in the prebuild
+## 配置预生成中包含的耗时任务
-You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)."
+可以在 `devcontainer.json` 中使用 `onCreateCommand` 和 `updateContentCommand` 命令，以将耗时过程作为预生成创建的一部分。 有关详细信息，请参阅 {% data variables.product.prodname_vscode %} 文档“[devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)”。
-`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at creation of the prebuild and at subsequent updates to it. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update.
+`onCreateCommand` 只在创建预生成时运行一次，而 `updateContentCommand` 在预生成创建和预生成后续更新时运行。 增量生成应包含在 `updateContentCommand` 中，因为它们代表项目的源，并且需要包含在每次预生成更新中。
-## Further reading
+## 延伸阅读
-- "[Allowing a prebuild to access other repositories](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)"
-- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
+- “[允许预生成访问其他存储库](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)”
+- [对预生成进行故障排除](/codespaces/troubleshooting/troubleshooting-prebuilds)
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
index 36e4e0ae51..b1d9289893 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
@@ -1,7 +1,7 @@
---
-title: Adding an "Open in GitHub Codespaces" badge
+title: 添加“在 GitHub Codespaces 中打开”锁屏提醒
shortTitle: Add a Codespaces badge
-intro: You can add a badge to a Markdown file in your repository which people can click to create a codespace.
+intro: 可以将锁屏提醒添加到存储库中的 Markdown 文件，用户可以单击该文件来创建 codespace。
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -10,50 +10,55 @@ type: how_to
topics:
- Codespaces
- Set up
+ms.openlocfilehash: c69a815501f5943a56d32af3e58cd7850a69588b
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158779'
---
+## 概述
-## Overview
+向 Markdown 文件添加“在 {% data variables.product.prodname_github_codespaces %} 中打开”锁屏提醒可让用户轻松地为存储库创建 codespace。
-Adding an "Open in {% data variables.product.prodname_github_codespaces %}" badge to a Markdown file gives people an easy way to create a codespace for your repository.
+
-
+创建锁屏提醒时，可以为锁屏提醒将创建的 codespace 选择特定配置选项。
-When you create a badge you can choose specific configuration options for the codespace that the badge will create.
+当人们单击锁屏提醒时，他们会进入用于创建 codespace 的高级选项页，其中包含你预先选择的选项。 有关高级选项页的详细信息，请参阅“[为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)”。
-When people click the badge they'll be taken to the advanced options page for codespace creation, with the options you chose preselected. For more information about the advanced options page, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+在高级选项页中，用户可以根据需要更改预先选择的设置，然后单击“创建 codespace”。
-From the advanced options page, users can change the preselected settings if required, then click **Create codespace**.
-
-## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge
+## 创建“在 {% data variables.product.prodname_github_codespaces %} 中打开”锁屏提醒
{% data reusables.repositories.navigate-to-repo %}
-1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create the badge for.
+1. 在存储库名称下，使用“分支”下拉菜单选择要为其创建徽章的分支。
- 
+ 
-1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+1. 单击“{% octicon "code" aria-label="The code icon" %} 代码”按钮，然后单击“codespace”选项卡。
- 
+ 
-1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab, then click **New with options**.
+1. 单击“Codespace”选项卡右上角的省略号 (…)，然后单击“新建选项” 。
- 
+ 
-1. On the advanced options page for codespace creation, select the values you want to be preselected in each field.
+1. 在用于创建 codespace 的高级选项页上，选择要在每个字段中预先选择的值。
- 
+ 
-1. Copy the URL from the browser's address bar.
-1. Add the following Markdown to, for example, the `README.md` file of your repository:
+1. 复制浏览器地址栏中的 URL。
+1. 例如，将以下 Markdown 添加到存储库的 `README.md` 文件：
```Markdown{:copy}
[](COPIED-URL)
```
- For example:
+ 例如：
```Markdown
[](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2)
```
- In the above example, `0000000` will be the reference number of your repository. The other details in the URL are determined by the values you selected in the fields on the advanced options page.
+ 在上面的示例中，`0000000` 会是存储库的引用编号。 URL 中的其他详细信息由在高级选项页上的字段中选择的值确定。
diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index 25a547449e..7117716ec8 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -1,7 +1,7 @@
---
-title: Troubleshooting prebuilds
+title: 对预生成进行故障排除
shortTitle: Codespaces prebuilds
-intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds.
+intro: 可以使用预生成来加快 codespace 的创建速度。 本文提供有关预生成的常见问题的故障排除步骤。
versions:
fpt: '*'
ghec: '*'
@@ -9,86 +9,91 @@ type: reference
topics:
- Codespaces
miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: b8c45f9eae6094b78026d055ebea27c3748a8681
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158883'
---
+有关 {% data variables.product.prodname_github_codespaces %} 预生成的详细信息，请参阅“[预生成 codespace](/codespaces/prebuilding-your-codespaces)”。
-For more information about {% data variables.product.prodname_github_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)."
+## 检查是否从预生成创建 codespace？
-## Checking whether a codespace was created from a prebuild?
+创建 codespace 时，可选择要使用的虚拟机类型。 如果预生成可用于该类型的虚拟机，其旁边会显示“{% octicon "zap" aria-label="The zap icon" %} 预生成就绪”。
-When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it.
+
-
+如果将 {% data variables.product.prodname_github_codespaces %} 编辑器首选项设置为“{% data variables.product.prodname_vscode %} for Web”，则“设置 codespace”页面将显示“找到预生成 codespace”消息（如果正在使用预生成）。
-If you have your {% data variables.product.prodname_github_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used.
+
-
+同样，如果编辑器首选项为“{% data variables.product.prodname_vscode_shortname %}”，则在创建新 codespace 时，集成终端将包含“你位于存储库预生成配置定义的预生成 codespace 上”消息。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_github_codespaces %} 的默认编辑器](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)”。
-Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
-
-After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal:
+创建 codespace 后，可以通过在终端中运行以下 {% data variables.product.prodname_cli %} 命令来检查它是否是从预生成创建的：
```shell{:copy}
gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild
```
-This returns `true` if the codespace was created using a prebuild.
+如果 codespace 是使用预生成创建的，则返回 `true`。
-Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild:
+或者，如果未安装 {% data variables.product.prodname_cli %} (`gh`)，则可以使用以下命令，该命令返回 `createFromPrebuild`（如果从预生成创建 codespace）：
```shell{:copy}
cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME'
```
-## The "Prebuild Ready" label is sometimes missing
+## 有时缺少“预生成就绪”标签
-You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
+你可能会注意到，有时，当从启用预生成的分支创建新 codespace 时，选择计算机类型的对话框中不会显示“{% octicon "zap" aria-label="The zap icon" %} 预生成就绪”标签。 这意味着预生成当前不可用。
-By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+默认情况下，每次推送到启用预生成的分支时，预生成都会更新。 如果推送涉及对开发容器配置的更改，则在进行更新时，将从计算机类型列表中删除“{% octicon "zap" aria-label="The zap icon" %} 预生成就绪”标签。 在此期间，仍然可以在没有预生成的情况下创建 codespace。 如果需要，可将预生成设置为仅在对开发容器配置文件进行更改时更新，或仅按自定义计划更新，从而减少预生成不可用于存储库的情况。 有关详细信息，请参阅“[配置预生成](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)”。
-If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
+如果你的分支没有专门为预生成启用，如果它是从启用预生成的分支分出来的，它仍然可以从预生成中受益。 但是，如果分支上的开发容器配置已更改，变得与基础分支上的配置不同，则分支上将不再提供预生成。
-Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch:
+检查特定分支是否未显示“{% octicon "zap" aria-label="The zap icon" %} 预生成就绪”标签需要完成以下事项：
-* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this.
-* Confirm that the prebuild configuration includes your region.
-* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
-* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
+* 确认此分支存在预生成配置。 如果你不是存储库管理员，则需要联系其中一个管理员来确认这一点。
+* 确认预生成配置包括你的区域。
+* 检查开发容器配置的更改最近是否已推送到启用预生成的分支。 如果是这样，则通常必须等到此推送的预生成工作流运行完成，才能再次使用预生成。
+* 如果最近未进行任何配置更改，请转到存储库的“操作”选项卡，单击工作流列表中的“{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} 预生成”，并检查分支的预生成工作流运行是否成功 。 如果工作流的最新运行失败，并且其中一个或多个失败的运行包含对开发容器配置的更改，则关联的分支将没有可用的预生成。
-## Some resources cannot be accessed in codespaces created using a prebuild
+## 在使用预生成创建的 codespace 中无法访问某些资源
-If the `devcontainer.json` configuration file for a prebuild configuration specifies that permissions for access to other repositories are required, then the repository administrator is prompted to authorize these permissions when they create or update the prebuild configuration. If the administrator does not grant all of the requested permissions there's a chance that problems may occur in the prebuild, and in codespaces created from this prebuild. This is true even if the user who creates a codespace based on this prebuild _does_ grant all of the permissions when they are prompted to do so.
+如果预生成配置的 `devcontainer.json` 配置文件指定需要其他存储库的访问权限，则系统会提示存储库管理员在创建或更新预生成配置时授权这些权限。 如果管理员未授予所有请求的权限，则预生成及其创建的 codespace 中可能会出现问题。 即使基于此预生成创建 codespace 的用户在收到提示时授予了所有权限，也是如此。
-## Troubleshooting failed workflow runs for prebuilds
+## 失败的预生成工作流运行故障排除
-### Increasing the {% data variables.product.prodname_actions %} spending limit
+### 提高 {% data variables.product.prodname_actions %} 支出限制
-Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+预生成是使用 {% data variables.product.prodname_actions %} 创建和更新的。 如果用完了所有 {% data variables.product.prodname_actions %} 分钟数并达到了支出限制，你的预生成工作流将会失败。 如果发生这种情况，可以增加 {% data variables.product.prodname_actions %} 支出限制，以允许工作流运行。 有关详细信息，请参阅“[管理 {% data variables.product.prodname_actions %} 的支出限制](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)”。
-### Authorizing access permissions
+### 授予访问权限
-If the `devcontainer.json` configuration file for a prebuild configuration is updated to specify that permissions for access to other repositories are required, and a repository administrator has not been prompted to authorize these permissions for the prebuild configuration, then the prebuild workflow may fail. Try updating the prebuild configuration, without making any changes. If, when you click **Update**, the authorization page is displayed, check that the requested permissions are appropriate and, if so, authorize the request. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" and "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)."
+如果更新了预生成配置的 `devcontainer.json` 配置文件以指定需要其他存储库的访问权限，并且系统未提示存储库管理员为预生成配置授权这些权限，则预生成工作流可能会失败。 尝试在不进行任何更改的情况下更新预生成配置。 如果单击“更新”显示了授权页面，请检查请求的权限是否合适，如果合适，请授权该请求。 有关详细信息，请参阅“[管理预生成](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)”和“[管理对 codespace 中其他存储库的访问](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)”。
-If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
+如果预生成配置的工作流运行失败，则可以在调查时暂时禁用预生成配置。 有关详细信息，请参阅“[管理预生成](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)”。
-### Preventing out-of-date prebuilds being used
+### 防止使用过时预生成
-By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
+默认情况下，如果最新的预生成工作流失败，将通过先前使用相同组合的存储库、分支和 `devcontainer.json` 配置文件的预生成来创建新的 codespace。 此行为称为预生成优化。
-We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
+建议启用预生成优化，因为它有助于确保在最新预生成不可用时仍可快速创建 codespace。 但如果遇到预生成 codespace 落后于分支当前状态的问题，存储库管理员可以禁用预生成优化。 如果禁用预生成优化，则当最新的预生成工作流失败或当前正在运行时，将在没有预生成的情况下创建存储库、分支和 `devcontainer.json` 文件相关组合的 codespace。
{% data reusables.codespaces.accessing-prebuild-configuration %}
-1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
+1. 在受影响的预生成配置右侧，选择省略号 (…)，然后单击“编辑” 。
- 
-1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
+ 
+1. 滚动到“编辑配置”页底部，然后单击“显示高级选项”。
- 
-1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
+ 
+1. 如果确定要禁用默认设置，请选择“禁用预生成优化”。
- 
-1. To save your change, click **Update**.
+ 
+1. 若要保存更改，请单击“更新”。
-## Further reading
+## 延伸阅读
-- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
-- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
+- [配置预生成](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)
+- [管理预生成](/codespaces/prebuilding-your-codespaces/managing-prebuilds)
diff --git a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index fc08f5709d..8f7905ac45 100644
--- a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -1,6 +1,6 @@
---
-title: 创建默认的社区运行状况文件
-intro: 您可以创建默认社区健康文件，例如 CONTRIBUTING 和 CODE_OF_CONDUCT。 默认文件将用于不包含该类型自有文件的帐户所拥有的任何仓库。
+title: Creating a default community health file
+intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
redirect_from:
- /articles/creating-a-default-community-health-file-for-your-organization
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
@@ -12,41 +12,46 @@ versions:
topics:
- Community
shortTitle: Community health file
-ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145099301'
---
-## 关于默认社区健康文件
-可以将默认社区运行状况文件添加到存储库根目录下或者 `docs` 或 `.github` 文件夹中名为 `.github` 的公共存储库中。
+## About default community health files
-对于在以下任何位置不含该类型自有文件的帐户所拥有的任何仓库，{% data variables.product.product_name %} 将使用并显示默认文件：
-- 仓库的根目录
-- `.github` 文件夹
-- `docs` 文件夹
+You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders.
-例如，在不含自有 CONTRIBUTING 文件的仓库中创建议题或拉取请求的人将会看到指向默认 CONTRIBUTING 文件的链接。 如果存储库在其自己的 `.github/ISSUE_TEMPLATE` 文件夹{% ifversion fpt or ghes or ghec %}中含有任何文件，包括议题模板或 config.yml 文件，{% endif %}则不会使用默认 `.github/ISSUE_TEMPLATE` 文件夹的内容。
+{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
+- the root of the repository
+- the `.github` folder
+- the `docs` folder
-默认文件不包含在各个存储库的克隆、包或下载中，因为它们只存储在 `.github` 存储库中。
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
-## 支持的文件类型
+Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
-可以在组织{% ifversion fpt or ghes or ghec %}或个人帐户{% endif %}中为以下社区运行状况文件创建默认内容：
+## Supported file types
-社区运行状况文件 | 说明 --- | ---{% ifversion fpt or ghec %} CODE_OF_CONDUCT.md | CODE_OF_CONDUCT 文件定义有关如何参与社区的标准。 有关详细信息，请参阅“[为项目添加行为准则](/articles/adding-a-code-of-conduct-to-your-project/)”。{% endif %} CONTRIBUTING.md | CONTRIBUTING 文件指示应如何参与你的项目。 有关详细信息，请参阅“[设置存储库贡献者指南](/articles/setting-guidelines-for-repository-contributors/)”。{% ifversion fpt or ghec %} FUNDING.yml | FUNDING 文件在存储库中显示发起人按钮，以提高开源项目资助选项的可见性。 有关详细信息，请参阅“[在存储库中显示发起人按钮](/articles/displaying-a-sponsor-button-in-your-repository)。”{% endif %} 问题和拉取请求模板 {% ifversion fpt or ghes or ghec %} 和 config.yml{% endif %} | 问题和拉取请求模板可自定义和标准化你希望参与者在存储库中打开问题或拉取请求时包含的信息。 有关详细信息，请参阅“[关于问题和拉取请求模板](/articles/about-issue-and-pull-request-templates/)。”{% ifversion fpt or ghes or ghec %} SECURITY.md | SECURITY 文件阐述了如何报告项目中的安全漏洞。 有关详细信息，请参阅“[向存储库添加安全策略](/code-security/getting-started/adding-a-security-policy-to-your-repository)。”{% endif %} SUPPORT.md | SUPPORT 文件介绍在项目中获取帮助的途径。 有关详细信息，请参阅“[向项目添加支持资源](/articles/adding-support-resources-to-your-project/)”。
+You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
-您不能创建默认许可文件。 必须将许可文件添加到各个仓库中，以便在克隆、打包或下载项目时包含该文件。
+Community health file | Description
+--- | ---{% ifversion fpt or ghec %}
+*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
+*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion discussion-category-forms %}
+Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[Creating discussion category forms](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
+*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
+Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes or ghec %}
+*SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
-## 创建用于默认文件的仓库
+You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
+
+## Creating a repository for default files
{% data reusables.repositories.create_new %}
-2. 使用“所有者”下拉菜单，选择要为其创建默认文件的组织{% ifversion fpt or ghes or ghec %}或个人帐户{% endif %}。
- 
-3. 输入“.github”作为存储库的名称和描述（可选）。
- 
-4. 确保存储库状态设置为“公共”（默认文件的存储库不能是私有的）。
-  {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
-7. 在仓库中，创建一个受支持的社区健康文件。 议题模板 {% ifversion fpt or ghes or ghec %} 及其配置文件 {% endif %} 必须位于名为 `.github/ISSUE_TEMPLATE` 的文件夹中。 所有其他支持的文件可能位于存储库根目录、`.github` 文件夹或 `docs` 文件夹中。 有关详细信息，请参阅“[新建文件](/articles/creating-new-files/)”。
+2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
+ 
+3. Type **.github** as the name for your repository, and an optional description.
+ 
+4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+ 
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
index 44aa07505c..172ccfb8bc 100644
--- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
@@ -1,6 +1,6 @@
---
-title: Creating a pull request template for your repository
-intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.'
+title: 为仓库创建拉取请求模板
+intro: 将拉取请求模板添加到仓库后，项目贡献者会自动在拉取请求正文中看到模板的内容。
redirect_from:
- /articles/creating-a-pull-request-template-for-your-repository
- /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
@@ -12,41 +12,44 @@ versions:
topics:
- Community
shortTitle: Create a PR template
+ms.openlocfilehash: fa4d3cf78b63af147c85b8f6d77d7cca74e3853a
+ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190406'
---
+有关详细信息，请参阅“[关于问题和拉取请求模板](/articles/about-issue-and-pull-request-templates)”。
-For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
-
-You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
+可以在任何支持的文件夹中创建 PULL_REQUEST_TEMPLATE/ 子目录，以包含多个拉取请求模板，并使用 `template` 查询参数指定填充拉取请求正文的模板。 有关详细信息，请参阅“[使用查询参数创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)”。
{% ifversion fpt or ghes or ghec %}
-You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+可以为组织{% ifversion fpt or ghes or ghec %}或个人帐户{% endif %}创建默认的拉取请求模板。 有关详细信息，请参阅[创建默认社区运行状况文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)。
{% endif %}
-## Adding a pull request template
+## 添加拉取请求模板
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field:
- - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`.
- 
- - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`.
- 
- - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`.
- 
- - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
- 
-4. In the body of the new file, add your pull request template. This could include:
- - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository.
- - A description of the changes proposed in the pull request.
- - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes.
-{% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. 在文件名字段中：
+ - 若要使拉取请求模板显示在存储库根目录中，请将拉取请求模板命名为 `pull_request_template.md`。
+ 
+ - 若要使拉取请求模板显示在存储库的 `docs` 目录中，请将拉取请求模板命名为 `docs/pull_request_template.md`。
+ 
+ - 若要将文件存储在隐藏目录中，请将拉取请求模板命名为 `.github/pull_request_template.md`。
+ 
+ - 若要创建多个拉取请求模板，并使用 `template` 查询参数指定填充拉取请求正文的模板，请键入“.github/PULL_REQUEST_TEMPLATE/”，后跟拉取请求模板的名称。 例如，`.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`。 也可以在根目录或 `docs/` 目录的 `PULL_REQUEST_TEMPLATE` 子目录中存储多个拉取请求模板。 有关详细信息，请参阅“[使用查询参数创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)”。
+ 
+4. 在新文件的正文中，添加您的拉取请求模板。 这可能包括：
+ - 存储库中[对相关问题的引用](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)。
+ - 对拉取请求中所提议更改的说明。
+ - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) 负责审查提议更改的人员或团队。
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} 模板可供协作者用来合并到存储库的默认分支。
{% data reusables.files.propose_new_file %}
-## Further reading
+## 延伸阅读
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating a pull request](/articles/creating-a-pull-request)"
+- [关于问题和拉取请求模板](/articles/about-issue-and-pull-request-templates)
+- [关于使用查询参数自动处理问题和拉取请求](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)
+- [创建拉取请求](/articles/creating-a-pull-request)
diff --git a/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md
index db0162551d..209a1a5bfb 100644
--- a/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md
+++ b/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -1,6 +1,6 @@
---
-title: About apps
-intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}'
+title: 关于应用程序
+intro: '你可以构建与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的集成来增加灵活性并减少自己工作流程中的摩擦。{% ifversion fpt or ghec %} 你也可以与 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 上的其他 API 集成。{% endif %}'
redirect_from:
- /apps/building-integrationssetting-up-a-new-integration
- /apps/building-integrations
@@ -14,93 +14,99 @@ versions:
ghec: '*'
topics:
- GitHub Apps
+ms.openlocfilehash: a66af14f6047b2aff435ac4ac8dc83d7a1181e92
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107355'
---
-Apps on {% data variables.product.prodname_dotcom %} allow you to automate and improve your workflow. You can build apps to improve your workflow.{% ifversion fpt or ghec %} You can also share or sell apps in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). To learn how to list an app on {% data variables.product.prodname_marketplace %}, see "[Getting started with GitHub Marketplace](/marketplace/getting-started/)."{% endif %}
+{% data variables.product.prodname_dotcom %} 上的应用程序允许您自动化并改进工作流程。 可以生成应用来改进工作流。{% ifversion fpt or ghec %}也可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 中分享或销售应用。 若要了解如何在 {% data variables.product.prodname_marketplace %} 中上架应用，请参阅“[GitHub 市场入门](/marketplace/getting-started/)”。{% endif %}
-{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)."
+{% data reusables.marketplace.github_apps_preferred %}，但 GitHub 支持 {% data variables.product.prodname_oauth_apps %} 和 {% data variables.product.prodname_github_apps %}。 有关选择应用类型的信息，请参阅“[GitHub 应用与 OAuth 应用的区别](/developers/apps/differences-between-github-apps-and-oauth-apps)”。
{% data reusables.apps.general-apps-restrictions %}
-For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+有关生成 {% data variables.product.prodname_github_app %} 的过程演练，请参阅“[生成第一个 {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)”。
-## About {% data variables.product.prodname_github_apps %}
+## 关于 {% data variables.product.prodname_github_apps %}
-{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user.
+{% data variables.product.prodname_github_apps %} 是 GitHub 中的一流产品。 {% data variables.product.prodname_github_app %} 应用程序以自己的名义运行，通过 API 直接使用自己的身份进行操作，这意味着您无需作为独立用户维护自动程序或服务帐户。
-{% data variables.product.prodname_github_apps %} can be installed directly on organizations and personal accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository.
+{% data variables.product.prodname_github_apps %} 可以直接安装在组织和个人帐户上，并获得对特定仓库的访问权限。 它们拥有内置 web 挂钩和狭窄的特定权限。 设置 {% data variables.product.prodname_github_app %}时，可以选择希望它访问的仓库。 例如，可以设置一个名为在存储库中`MyGitHub`写入问题且`octocat`仅 _写入_ 存储库的应用`octocat`。 要安装 {% data variables.product.prodname_github_app %}，您必须是组织所有者或在仓库中具有管理员权限。
{% data reusables.apps.app_manager_role %}
-{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+{% data variables.product.prodname_github_apps %} 是需要托管在某处的应用程序。 有关涵盖服务器和托管的分步说明，请参阅“[生成第一个 {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)”。
-To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs.
+要改进自己的工作流程，可以创建一个包含多个脚本或整个应用程序的 {% data variables.product.prodname_github_app %}，然后将此应用程序连接至许多其他工具。 例如，您可以将 {% data variables.product.prodname_github_apps %} 连接至 GitHub、Slack、自己可能拥有的其他内部应用程序、电子邮件程序或其他 API。
-Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}:
+创建 {% data variables.product.prodname_github_apps %} 时，请记住以下方法：
{% ifversion fpt or ghec %}
* {% data reusables.apps.maximum-github-apps-allowed %} {% endif %}
-* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %}
+* {% data variables.product.prodname_github_app %} 的操作应独立于用户（除非此应用使用[用户到服务器](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)令牌）。 {% data reusables.apps.expiring_user_authorization_tokens %}
-* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories.
-* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization.
-* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can.
-* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things.
-* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %}
+* 请确保 {% data variables.product.prodname_github_app %} 与特定仓库集成。
+* {% data variables.product.prodname_github_app %} 应该连接到个人帐户或组织。
+* 不要指望 {% data variables.product.prodname_github_app %} 知道并尽其所能。
+* 如果您只需要“使用GitHub登录”服务，请不要使用 {% data variables.product.prodname_github_app %}。 但是 {% data variables.product.prodname_github_app %} 可以使用[用户标识流](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)让用户登录和执行其他操作。
+* 如果只想充当 GitHub 用户并执行用户所能执行的所有操作，请不要生成 {% data variables.product.prodname_github_app %}。{% ifversion fpt or ghec %}
* {% data reusables.apps.general-apps-restrictions %}{% endif %}
-To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %}
+若要开始开发 {% data variables.product.prodname_github_apps %}，请从“[创建 {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)”开始。{% ifversion fpt or ghec %}若要了解如何使用 {% data variables.product.prodname_github_app %} 清单创建预配置的 {% data variables.product.prodname_github_apps %}，请参阅“[从清单创建 {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/creating-github-apps-from-a-manifest/)”。{% endif %}
-## About {% data variables.product.prodname_oauth_apps %}
+## 关于 {% data variables.product.prodname_oauth_apps %}
-OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time.
+OAuth2 是一种协议，它允许外部应用程序请求授权在不使用密码的情况下访问用户 {% data variables.product.prodname_dotcom %} 帐户中的私有信息。 此协议优先于基本验证，因为令牌可能仅限于特定类型的数据，用户可以随时撤销。
{% data reusables.apps.deletes_ssh_keys %}
-An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access.
+{% data variables.product.prodname_oauth_app %} 使用 {% data variables.product.prodname_dotcom %} 作为身份提供程序以验证为授予应用程序访问权限的用户。 这意味着，当用户授予 {% data variables.product.prodname_oauth_app %} 访问权限时，将授权访问其帐户有权访问的所有存储库，以及他们所属的、未阻止第三方访问的任何组织。
-Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere.
+如果要创建比简单脚本的处理范围更复杂的流程，构建 {% data variables.product.prodname_oauth_app %} 是一个很好的选择。 请注意，{% data variables.product.prodname_oauth_apps %} 是需要托管在某处的应用程序。
-Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}:
+创建 {% data variables.product.prodname_oauth_apps %} 时，请记住以下几点：
{% ifversion fpt or ghec %}
* {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %}
-* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications).
-* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user.
-* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories.
-* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %}
+* {% data variables.product.prodname_oauth_app %} 在所有 {% data variables.product.prodname_dotcom %} 中（例如，在提供用户通知时）应始终代表经身份验证的 {% data variables.product.prodname_dotcom %} 用户。
+* 通过为经身份验证的用户启用“使用 {% data variables.product.prodname_dotcom %} 进行登录”，{% data variables.product.prodname_oauth_app %} 可用作身份提供程序。
+* 如果您希望应用程序作用于单个仓库，请不要构建 {% data variables.product.prodname_oauth_app %}。 使用 `repo` OAuth 作用域，{% data variables.product.prodname_oauth_apps %} 可以作用于经身份验证用户的所有存储库。
+* 不要构建 {% data variables.product.prodname_oauth_app %} 作为团队或公司的应用程序。 {% data variables.product.prodname_oauth_apps %} 将验证为单个用户，因此，如果有人创建了 {% data variables.product.prodname_oauth_app %} 供公司使用，那么一旦他们离开公司，其他人将无法访问它。{% ifversion fpt or ghec %}
* {% data reusables.apps.oauth-apps-restrictions %}{% endif %}
-For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)."
+有关 {% data variables.product.prodname_oauth_apps %} 的详细信息，请参阅“[创建 {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)”和“[注册应用](/rest/guides/basics-of-authentication#registering-your-app)”。
## {% data variables.product.pat_generic_caps %}s
-A [{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A {% data variables.product.pat_generic %} is also similar to a password, but you can have many of them and you can revoke access to each one at any time.
+[{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) 是一个字符串，其功能类似于 [OAuth 令牌](/apps/building-oauth-apps/authorizing-oauth-apps/)，可以通过[作用域](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)指定其权限。 {% data variables.product.pat_generic %} 还与密码类似，但你能拥有很多令牌，而且可以随时撤销对每个令牌的访问权限。
-As an example, you can enable a {% data variables.product.pat_generic %} to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the {% data variables.product.pat_generic %} to authenticate. You can store the {% data variables.product.pat_generic %} as an environment variable to avoid typing it every time you use it.
+例如，可以启用 {% data variables.product.pat_generic %} 以写入存储库。 如果随后运行 cURL 命令或编写在存储库中[创建问题](/rest/reference/issues#create-an-issue)的脚本，则需要传递 {% data variables.product.pat_generic %} 以进行身份验证。 可以将 {% data variables.product.pat_generic %} 存储为环境变量，以免每次使用时都要输入。
-Keep these ideas in mind when using {% data variables.product.pat_generic %}s:
+使用 {% data variables.product.pat_generic %}s 时，请记住以下想法：
-* Remember to use this token to represent yourself only.
-* You can perform one-off cURL requests.
-* You can run personal scripts.
-* Don't set up a script for your whole team or company to use.
-* Don't set up a shared personal account to act as a bot user.
-* Grant your token the minimal privileges it needs.
-* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.
+* 记得只能用此令牌代表您自己。
+* 您可以执行一次性 cURL 请求。
+* 您可以运行个人脚本。
+* 不要为整个团队或公司设置脚本。
+* 不要设置共享个人账户以用作自动程序用户。
+* 为令牌授予所需的最低特权。
+* 为 {% data variables.product.pat_generic %}s 设置过期时间，以帮助确保信息安全。
-## Determining which integration to build
+## 确定要构建的集成
-Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use {% data variables.product.pat_generic %}s, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration.
+在开始创建集成之前，您需要确定使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 访问、验证和交互的最佳方式。 下图提供了一些问题，你在决定是否对集成使用 {% data variables.product.pat_generic %}s、{% data variables.product.prodname_github_apps %} 或 {% data variables.product.prodname_oauth_apps %} 时可以考虑这些问题。
-
+
-Consider these questions about how your integration needs to behave and what it needs to access:
+请考虑关于您的集成需要如何操作及它需要访问什么等问题：
-* Will my integration act only as me, or will it act more like an application?
-* Do I want it to act independently of me as its own entity?
-* Will it access everything that I can access, or do I want to limit its access?
-* Is it simple or complex? For example, {% data variables.product.pat_generic %}s are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting.
+* 我的集成是只像我一样，还是更像一个应用程序？
+* 我是否希望它作为单独的实体独立于我运行？
+* 它是否能访问我可以访问的一切，或者说我想限制它的访问权限？
+* 它是简单还是复杂？ 例如，{% data variables.product.pat_generic %}s 对简单的脚本和 cURL 有益，而 {% data variables.product.prodname_oauth_app %} 可以处理更复杂的脚本。
-## Requesting support
+## 请求支持
{% data reusables.support.help_resources %}
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
index c48174405e..0524b1d585 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,6 +9,8 @@ children:
- /managing-categories-for-discussions
- /moderating-discussions
- /viewing-insights-for-your-discussions
+ - /creating-discussion-category-forms
+ - /syntax-for-discussion-category-forms
ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
ms.translationtype: HT
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index 302f14adae..98747b78eb 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -1,215 +1,201 @@
---
-title: Managing discussions
-intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
+title: 管理讨论
+intro: 可以分类、聚焦、转让或删除讨论。
permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
versions:
feature: discussions
shortTitle: Manage discussions
redirect_from:
- /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
+ms.openlocfilehash: e5e1474648973c90d16e8998db18518331233aa3
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164337'
---
+## 关于讨论的管理
+{% data reusables.discussions.about-discussions %} 有关讨论的详细信息，请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。
-## About management of discussions
+组织所有者可以选择在组织拥有的存储库中创建讨论所需的权限。 同样，若要选择创建组织讨论所需的权限，组织所有者可以更改源存储库中所需的权限。 有关详细信息，请参阅“[管理组织中存储库的讨论创建](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)”。
-{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+作为讨论维护者，您可以创建社区资源，以鼓励与总体项目目标一致的讨论，并为协作者维护一个友好、开放的论坛。 为协作者制定{% ifversion fpt or ghec %}行为守则或{% endif %}参与指南将有助于促进协作和富有成效的论坛。 有关如何创建社区资源的详细信息，请参阅{% ifversion fpt or ghec %}“[向项目添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和{% endif %}“[设置适用于存储库参与者的指南](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)”。
-Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."
+当讨论产生可以解决的想法或漏洞时，您可以从讨论创建新议题。 有关详细信息，请参阅“[创建问题](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)”。
-As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, 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 guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+可以将讨论固定到存储库或组织的讨论列表顶部。 {% ifversion discussions-category-specific-pins %}还可以将讨论固定到特定类别。{% endif %}有关详细信息，请参阅“[固定讨论](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)”。
-When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
-
-You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
-
-For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
+有关如何促进健康讨论的详细信息，请参阅“[缓和评论和对话](/communities/moderating-comments-and-conversations)”。
{% data reusables.discussions.you-can-label-discussions %}
-## Prerequisites
+## 必备知识
-To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)."
+要管理仓库中的讨论，必须为仓库启用 {% data variables.product.prodname_discussions %}。 有关详细信息，请参阅“[启用或禁用存储库的 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)”。
-To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+若要管理组织中的讨论，必须为组织启用 {% data variables.product.prodname_discussions %}。 有关详细信息，请参阅“[启用或禁用组织的 {% data variables.product.prodname_discussions %}](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)”。
-## Changing the category for a discussion
+## 更改讨论类别
-You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+您可以对讨论进行分类，以帮助社区成员查找相关的讨论。 有关详细信息，请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。
-You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category.
+您也可以将讨论移动到另一个类别。 无法将讨论移动到投票类别或从投票类别移出。
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 在右侧边栏中“Category（类别）”的右侧，单击 {% octicon "gear" aria-label="The gear icon" %}。
- 
+ 
-1. Click a category.
+1. 单击一个类别。
- 
+ 
-## Pinning a discussion
+## 固定讨论
-{% ifversion discussions-category-specific-pins %}
-You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
+{% ifversion discussions-category-specific-pins %} 可以将讨论固定在存储库或组织的讨论列表上方。 还可以将讨论固定到特定类别。 除了固定到特定类别的讨论外，还将显示全局固定讨论。
-This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
+这是当你有一个全局固定讨论和固定到“想法”类别的讨论时的外观。
-
+
-### Pinning a discussion globally
+### 全局固定讨论
{% endif %}
-You can pin up to four important discussions above the list of discussions for the repository or organization.
+可以在存储库或组织讨论列表上固定多达四个重要的讨论。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 在右侧栏中，单击 {% octicon "pin" aria-label="The pin icon" %}“固定讨论”。
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ {% else %}
- {% endif %}
+ {% endif %}
-1. Optionally, customize the look of the pinned discussion.
+1. （可选）自定义固定讨论的外观。
- 
+ 
-1. Click **Pin discussion**.
+1. 单击“固定讨论”。
- 
+ 
{% ifversion discussions-category-specific-pins %}
-### Pinning a discussion to a category
+### 将讨论固定到类别
-You can pin up to four important discussions above the list of discussions in a specific category.
+可以在特定类别的讨论列表上固定四个重要讨论。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 在右侧边栏中，单击 {% octicon "pin" aria-label="The pin icon" %}“将讨论固定到类别”。
- 
+ 
-2. To confirm, click **Pin to CATEGORY**.
+2. 若要确认，请单击“固定到类别”。
- 
+ 
{% endif %}
-## Editing a pinned discussion
+## 编辑固定的讨论
-Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+编辑固定的讨论不会更改讨论的类别。 有关详细信息，请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 在右侧栏中，单击 {% octicon "pencil" aria-label="The pencil icon" %}“编辑固定讨论”。
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+  {% else %}
- {% endif %}
+ {% endif %}
-1. Customize the look of the pinned discussion.
+1. 自定义固定的讨论的外观。
- 
+ 
-1. Click **Pin discussion**.
+1. 单击“固定讨论”。
- 
+ 
-## Unpinning a discussion
+## 取消固定讨论
{% ifversion discussions-category-specific-pins %}
-You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
+可以从存储库或组织的讨论列表中取消固定讨论，也可以从特定类别的讨论列表中取消固定讨论。
-### Unpinning a globally pinned discussion
+### 取消固定全局固定讨论
-You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
+可以取消固定全局固定讨论。 这不会删除讨论，但讨论将不再显示在讨论列表上方。
{% endif %}
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 在右侧栏中，单击 {% octicon "pin" aria-label="The pin icon" %}“取消固定讨论”。
- 
+ 
-1. Read the warning, then click **Unpin discussion**.
+1. 阅读警告，然后单击“取消固定讨论”。
- 
+ 
{% ifversion discussions-category-specific-pins %}
-### Unpinning a discussion from a category
+### 从类别中取消固定讨论
-You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
+可以取消固定到特定类别的讨论。 这不会删除讨论，但讨论将不再显示在类别上方。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 在右侧边栏中，单击 {% octicon "pin" aria-label="The pin icon" %}“从该类别中取消固定讨论”。
- 
+ 
-1. Read the warning, then click **Unpin from this category**.
+1. 阅读警告，然后单击“从该类别取消固定”。
- 
+ 
{% endif %}
-## Transferring a discussion
+## 转让讨论
-To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
+要转让讨论，您必须具有在要转让讨论的仓库中创建讨论的权限。 如果要将讨论转让给组织，必须具有在组织的讨论的源存储库中创建讨论的权限。 您只能在同一用户或组织帐户拥有的仓库之间转让讨论。 不能将讨论从专用{% ifversion ghec or ghes %}或内部{% endif %}存储库转移到公共存储库。
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 在右侧边栏中，单击{% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}Transfer this discussion{% else %}“转移讨论”{% endif %} 。
{% ifversion discussions-category-specific-pins %}
-  {% else %}
+  {% else %}
- {% endif %}
+ {% endif %}
-1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
+1. 选择“选择存储库”下拉列表，并单击要将讨论转让到的存储库。 如果要将讨论转让给组织，请选择组织的讨论的源存储库。
- 
+ 
-1. Click **Transfer discussion**.
+1. 单击“转让讨论”。
- 
+ 
-## Deleting a discussion
+## 删除讨论
-{% data reusables.discussions.navigate-to-repo-or-org %}
-{% data reusables.discussions.discussions-tab %}
-{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. 在右侧栏中，单击 {% octicon "trash" aria-label="The trash arrow icon" %}“删除讨论”。
{% ifversion discussions-category-specific-pins %}
- {% else %}
+ {% else %}
- {% endif %}
+ {% endif %}
-1. Read the warning, then click **Delete this discussion**.
+1. 阅读警告，然后单击“删除此讨论”。
- 
+ 
-## Converting issues based on labels
+## 基于标签转换议题
-You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.
+您可以将具有相同标签的所有议题批量转换为讨论。 具有此标签的未来议题也将自动转换为您配置的讨论和类别。
-1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository.
-{% data reusables.repositories.sidebar-issues %}
-{% data reusables.project-management.labels %}
-1. Next to the label you want to convert to issues, click **Convert issues**.
-1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
-1. Click **I understand, convert this issue to a discussion**.
+1. 在 {% data variables.location.product_location %} 上，导航到存储库主页；对于组织讨论，导航到源存储库主页。
+{% data reusables.repositories.sidebar-issues %} {% data reusables.project-management.labels %}
+1. 在要转换为问题的标签旁边，单击“转换问题”。
+1. 选择“选择类别”下拉菜单，然后单击某个类别进行讨论。
+1. 单击“我明白，将此问题转化为讨论”。
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index ffef0a4aba..ffa41c6c1a 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -1,78 +1,84 @@
---
-title: Create a group assignment
-intro: You can create a collaborative assignment for teams of students who participate in your course.
+title: 创建组分配
+intro: 您可以为参加您课程的学生团队创建协作作业。
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
redirect_from:
- /education/manage-coursework-with-github-classroom/create-group-assignments
- /education/manage-coursework-with-github-classroom/create-a-group-assignment
+ms.openlocfilehash: 71c5f5eaf97ba58e25921c1e2be6fc638550dfa8
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179758'
---
-## About group assignments
+## 关于组分配
-{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+{% data reusables.classroom.assignments-group-definition %} 学生可以像专业开发人员团队一样，在共享仓库中共同完成小组作业。
-When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+当学生接受小组作业时，该学生可以创建新团队或加入现有团队。 {% data variables.product.prodname_classroom %} 将任务团队保存为集合。 您可以在创建作业时为特定作业指定一组团队，并且在后面的作业中可以重复使用该组团队。
{% data reusables.classroom.classroom-creates-group-repositories %}
{% data reusables.classroom.about-assignments %}
-You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+您可以决定一个任务可以拥有多少个团队，以及每个团队可以拥有多少成员。 学生为作业创建的每个团队都是 {% data variables.product.product_name %} 上组织内的团队。 团队的可见性是秘密。 您在 {% data variables.product.product_name %} 上创建的团队不会出现在 {% data variables.product.prodname_classroom %} 中。 有关详细信息，请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
-For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+有关创建小组作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本信息](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## 先决条件
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## 创建作业
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## 设置作业的基本信息
-Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+指定作业的名称，决定是否分配截止时间，确定团队，并选择作业仓库的可见性。
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Defining teams for an assignment](#defining-teams-for-an-assignment)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [指定作业名称](#naming-an-assignment)
+- [分配作业的截止时间](#assigning-a-deadline-for-an-assignment)
+- [选择作业类型](#choosing-an-assignment-type)
+- [确定作业的团队](#defining-teams-for-an-assignment)
+- [选择作业存储库的可见性](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### 指定作业名称
-For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+对于小组作业，{% data variables.product.prodname_classroom %} 使用仓库前缀和团队名称对仓库命名。 默认情况下，仓库前缀是作业标题。 例如，如果将作业命名为“assignment-1”，而团队在 {% data variables.product.product_name %} 上的名称是“student-team”，则团队成员的作业存储库的名称将是 `assignment-1-student-team`。
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### 分配作业的截止时间
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### 选择作业类型
-Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create an individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+在“个人或小组作业”下，选择下拉菜单，然后单击“小组作业”。 创建作业后不可更改作业类型。 如果希望创建个人作业，请参阅“[创建个人作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)”。
-### Defining teams for an assignment
+### 确定作业的团队
-If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+如果已为教室创建了小组作业，可以对新作业重复使用一组团队。 要使用学生为作业创建的团队创建一个新组，请输入组的名称。 （可选）键入团队成员和团队总数的最大数量。
{% tip %}
-**Tips**:
+**提示**：
-- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+- 我们建议在组的名称中包含有关该组团队的详细信息。 例如，如果要对某个作业使用团队组，请以作业命名该组。 如果要在整个学期或课程中重复使用该组，请以学期或课程命名该组。
-- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+- 如果想将学生分配到特定团队，请为学生指定团队的名称并提供成员列表。
{% endtip %}
-
+
-### Choosing a visibility for assignment repositories
+### 选择作业仓库的可见性
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -80,22 +86,22 @@ If you've already created a group assignment for the classroom, you can reuse a
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## 添加起始代码并配置开发环境
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [选择模板存储库](#choosing-a-template-repository)
+- [选择集成开发环境 (IDE)](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### 选择模板仓库
-By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %}
+默认情况下，新作业将为学生创建的每个团队创建一个空仓库。 {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
-### Choosing an integrated development environment (IDE)
+### 选择集成开发环境 (IDE)
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} 有关详细信息，请参阅“[将 {% data variables.product.prodname_classroom %} 与 IDE 集成](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)”。
{% data reusables.classroom.classroom-codespaces-link %}
@@ -103,18 +109,18 @@ By default, a new assignment will create an empty repository for each team that
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-## Providing feedback
+## 提供反馈
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+（可选）您可以自动对作业进行分级，并创建一个空间，用于与团队讨论每个提交。
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [自动测试作业](#testing-assignments-automatically)
+- [为反馈创建拉取请求](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### 自动测试作业
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### 为反馈创建拉取请求
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -122,36 +128,36 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## 邀请学生参加作业
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+可以在作业的“团队”选项卡中查看正在处理作业或已提交作业的团队。 {% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
+## 监控学生的进度
+作业概述页显示有关作业接受和团队进度的信息。 根据作业的配置，您可能有不同的摘要信息。
-- **Total teams**: The number of teams that have been created.
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
-- **Accepted teams**: The number of teams who have accepted this assignment.
-- **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
+- 团队总数：已创建的团队数。
+- 名册内学生：课堂名册上的学生人数。
+- 不在团队的学生：课堂名册上尚未加入团队的学生人数。
+- 接受的团队：已接受此作业的团队数。
+- 作业提交：已提交作业的团队数。 在作业截止日期触发提交。
+- 通过团队：当前通过此作业的自动评分测试的团队数。
-## Next steps
+## 后续步骤
-- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}.
+- 在创建作业和学生组成团队后，团队成员可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和团队都可以审查仓库的提交历史记录。 有关详细信息，请参阅“[开始使用 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)”、“[存储库](/repositories)”、“[使用 Git](/github/getting-started-with-github/using-git)”和“[协作处理问题和拉取请求](/github/collaborating-with-issues-and-pull-requests)”，以及 {% data variables.product.prodname_learning %} 关于[解决合并冲突](https://github.com/skills/resolve-merge-conflicts)的免费课程。
-- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- 当团队完成作业时，您可以查看仓库中的文件，或者查看仓库的历史和可视化内容，以更好地了解团队如何协作。 有关详细信息，请参阅“[使用图表可视化存储库数据](/github/visualizing-repository-data-with-graphs)”。
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- 您可以通过在拉取请求中评论个别提交或行来提供作业反馈。 有关详细信息，请参阅“[对拉取请求添加注释](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)”和“[从代码中打开问题](/github/managing-your-work-on-github/opening-an-issue-from-code)”。 有关创建已保存回复以提供常见错误反馈的详细信息，请参阅“[关于已保存回复](/github/writing-on-github/about-saved-replies)”。
-## Further reading
+## 延伸阅读
-- [{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
-- "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
-- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
+- [教师版 {% data variables.product.prodname_global_campus %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- “[将学习管理系统课程连接到教室](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)”
+- {% data variables.product.prodname_education %} 社区中的[在小组作业中使用现有团队？](https://education.github.community/t/using-existing-teams-in-group-assignments/6999)
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 8161608b81..b581ab3de7 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -1,6 +1,6 @@
---
-title: Create an individual assignment
-intro: You can create an assignment for students in your course to complete individually.
+title: 创建个人作业
+intro: 您可以为课程中的学生创建需单独完成的作业。
versions:
fpt: '*'
permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
@@ -8,8 +8,14 @@ redirect_from:
- /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
- /education/manage-coursework-with-github-classroom/create-an-individual-assignment
shortTitle: Individual assignment
+ms.openlocfilehash: 1ffa725be4e42695b297545f65c998b14ed8e000
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179743'
---
-## About individual assignments
+## 关于个人作业
{% data reusables.classroom.assignments-individual-definition %}
@@ -17,42 +23,42 @@ shortTitle: Individual assignment
{% data reusables.classroom.about-assignments %}
-For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+有关创建个人作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本信息](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
{% data reusables.classroom.reuse-assignment-link %}
-## Prerequisites
+## 先决条件
{% data reusables.classroom.assignments-classroom-prerequisite %}
-## Creating an assignment
+## 创建作业
{% data reusables.classroom.assignments-guide-create-the-assignment %}
-## Setting up the basics for an assignment
+## 设置作业的基本信息
-Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+指定作业的名称，决定是否分配截止时间，并选择作业仓库的可见性。
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [指定作业名称](#naming-an-assignment)
+- [分配作业的截止时间](#assigning-a-deadline-for-an-assignment)
+- [选择作业类型](#choosing-an-assignment-type)
+- [选择作业存储库的可见性](#choosing-a-visibility-for-assignment-repositories)
-### Naming an assignment
+### 指定作业名称
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+对于个人作业，{% data variables.product.prodname_classroom %} 使用仓库前缀和学生的 {% data variables.product.product_name %} 用户名对仓库命名。 默认情况下，仓库前缀是作业标题。 例如，如果你对作业 "assignment-1" 命名，学生在 {% data variables.product.product_name %} 上的用户名是 @octocat，则 @octocat 的作业存储库的名称将是 `assignment-1-octocat`。
{% data reusables.classroom.assignments-type-a-title %}
-### Assigning a deadline for an assignment
+### 分配作业的截止时间
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
-### Choosing an assignment type
+### 选择作业类型
-Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+在“个人或小组作业”下，选择下拉菜单，并单击“个人作业”。 创建作业后不可更改作业类型。 如果想要创建小组作业，请参阅“[创建小组作业](/education/manage-coursework-with-github-classroom/create-a-group-assignment)”。
-### Choosing a visibility for assignment repositories
+### 选择作业仓库的可见性
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
@@ -60,41 +66,41 @@ Under "Individual or group assignment", select the drop-down menu, and click **I
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
-## Adding starter code and configuring a development environment
+## 添加起始代码并配置开发环境
{% data reusables.classroom.assignments-guide-intro-for-environment %}
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [选择模板存储库](#choosing-a-template-repository)
+- [选择集成开发环境 (IDE)](#choosing-an-integrated-development-environment-ide)
-### Choosing a template repository
+### 选择模板仓库
-By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+默认情况下，新作业将为教室名册上的每个学生创建一个空仓库。 {% data reusables.classroom.you-can-choose-a-template-repository %}
{% data reusables.classroom.assignments-guide-choose-template-repository %}
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
-### Choosing an integrated development environment (IDE)
+### 选择集成开发环境 (IDE)
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} 有关详细信息，请参阅“[将 {% data variables.product.prodname_classroom %} 与 IDE 集成](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)”。
{% data reusables.classroom.classroom-codespaces-link %}
{% data reusables.classroom.assignments-guide-choose-an-online-ide %}
-## Providing feedback for an assignment
+## 为作业提供反馈
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
+（可选）您可以自动对作业进行分级，并创建一个空间，用于与学生讨论每个提交。
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [自动测试作业](#testing-assignments-automatically)
+- [为反馈创建拉取请求](#creating-a-pull-request-for-feedback)
-### Testing assignments automatically
+### 自动测试作业
{% data reusables.classroom.assignments-guide-using-autograding %}
-### Creating a pull request for feedback
+### 为反馈创建拉取请求
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
@@ -102,34 +108,34 @@ Optionally, you can automatically grade assignments and create a space for discu
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
-## Inviting students to an assignment
+## 邀请学生参加作业
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
+你可以在作业的“课堂名册”选项卡中查看学生是否已进入教室以及是否接受或提交作业。 你还可以在此选项卡中将学生的 {% data variables.product.prodname_dotcom %} 别名链接到其关联的名册标识符，反之亦然。{% data reusables.classroom.assignments-to-prevent-submission %}
-## Monitoring students' progress
-The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
+## 监控学生的进度
+作业概述页面提供了作业接受情况和学生进度的概述。 根据作业的配置，您可能有不同的摘要信息。
-- **Rostered students**: The number of students on the Classroom's roster.
-- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
-- **Accepted students**: The number of accounts have accepted this assignment.
-- **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
-- **Passing students**: The number of students currently passing the autograding tests for this assignment.
+- **名册内学生**：课堂名册上的学生人数。
+- **已添加的学生**：已接受作业且未与名册标识符关联的 {% data variables.product.prodname_dotcom %} 帐户数。
+- **已接受的学生**：已接受此作业的帐户数。
+- **作业提交**：已提交作业的学生人数。 在作业截止日期触发提交。
+- **及格学生**：当前通过此作业的自动评分测试的学生人数。
-## Next steps
+## 后续步骤
-- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- 在创建作业后，学生可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和学生都可以审查仓库的提交历史记录。 有关详细信息，请参阅“[开始使用 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)”、“[存储库](/repositories)”和“[协作处理问题和拉取请求](/github/collaborating-with-issues-and-pull-requests)”。
-- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+- 当学生完成作业时，您可以查看仓库中的文件，或者查看仓库的历史和可视化内容，以更好地了解学生的工作。 有关详细信息，请参阅“[使用图表可视化存储库数据](/github/visualizing-repository-data-with-graphs)”。
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- 您可以通过在拉取请求中评论个别提交或行来提供作业反馈。 有关详细信息，请参阅“[对拉取请求添加注释](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)”和“[从代码中打开问题](/github/managing-your-work-on-github/opening-an-issue-from-code)”。 有关创建已保存回复以提供常见错误反馈的详细信息，请参阅“[关于已保存回复](/github/writing-on-github/about-saved-replies)”。
-## Further reading
+## 延伸阅读
-- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
+- [教师版 {% data variables.product.prodname_global_campus %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- [将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
index 7a247d6c1c..ffc2889d6e 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -1,83 +1,88 @@
---
-title: Getting started with GitHub AE
-intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.'
+title: 开始使用 GitHub AE
+intro: '开始为 {% data variables.location.product_location %} 设置和配置 {% data variables.product.product_name %}。'
versions:
ghae: '*'
+ms.openlocfilehash: 957a922a2493abd8f625cdb9e9d6650283820222
+ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/22/2022
+ms.locfileid: '148180059'
---
+本指南将引导你作为企业所有者完成在 {% data variables.product.product_name %} 上设置、配置 {% data variables.location.product_location %} 并管理设置。 若要了解 {% data variables.product.product_name %} 相关详细信息，请参阅“[关于 {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)。”
-This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)."
+## 第 1 部分：设置 {% data variables.product.product_name %}
+若要开始使用 {% data variables.product.product_name %}，可以创建企业帐户、初始化 {% data variables.product.product_name %}、配置 IP 允许列表、配置用户身份验证和预配以及管理 {% data variables.location.product_location %} 的计费。
-## Part 1: Setting up {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}.
-
-### 1. Creating your {% data variables.product.product_name %} enterprise account
-You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+### 1. 创建你的 {% data variables.product.product_name %} 企业帐户
+您首先需要购买 {% data variables.product.product_name %}。 有关详细信息，请联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)。
{% data reusables.github-ae.initialize-enterprise %}
-### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+### 2. 初始化 {% data variables.product.product_name %}
+当 {% data variables.product.company_short %} 在 {% data variables.product.product_name %} 上为 {% data variables.location.product_location %} 创建所有者帐户后，你将收到一封电子邮件，要求你登录并完成初始化。 在初始化期间，作为企业所有者，你将命名 {% data variables.location.product_location %}、配置 SAML SSO、为 {% data variables.location.product_location %} 中的所有组织创建策略，并为企业成员配置支持联系人。 有关详细信息，请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)”。
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 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)."
+### 3. 限制网络流量
+您可以为特定 IP 地址配置允许列表，以限制对企业帐户中组织拥有的资产的访问。 有关详细信息，请参阅“[使用 IP 允许列表限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)”。
-### 4. Managing identity and access for {% data variables.location.product_location %}
-You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[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)."
+### 4. 管理 {% data variables.location.product_location %} 的标识和访问
+你可以使用 SAML 单一登录 (SSO) 进行用户身份验证和跨域身份管理系统 (SCIM) 进行用户预配，从标识提供者 (IdP) 集中管理对 {% data variables.product.product_name %} 上 {% data variables.location.product_location %} 的访问。 在配置预配后，您可以从 IdP 分配用户给应用程序或取消分配，从而在企业中创建或禁用用户帐户。 有关详细信息，请参阅“[关于企业标识和访问管理](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)”。
-### 5. Managing billing for {% data variables.location.product_location %}
-Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+### 5. 管理 {% data variables.location.product_location %} 的计费
+{% data variables.product.product_name %} 上 {% data variables.location.product_location %} 的订阅所有者可以在 Azure 门户中查看 {% data variables.product.product_name %} 的计费详细信息。 有关详细信息，请参阅“[管理企业的计费](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)”。
-## Part 2: Organizing and managing enterprise members
-As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
+## 第 2 部分：组织和管理企业成员
+作为 {% data variables.product.product_name %} 的企业所有者，您可以管理用户、存储库、团队和组织级别的设置。 你可以管理 {% data variables.location.product_location %} 的成员、创建和管理组织、设置存储库管理策略，以及创建和管理团队。
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. 管理 {% data variables.location.product_location %} 的成员
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. 创建组织
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. 向组织添加成员
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. 创建团队
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. 设置组织和存储库权限级别
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. 实施存储库管理策略
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations.
+## 第 3 部分：安全构建
+若要提高 {% data variables.location.product_location %} 的安全性，你可以监视 {% data variables.location.product_location %}，并为组织配置安全性和分析功能。
-### 1. Monitoring {% data variables.location.product_location %}
-You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)."
+### 1. 监视 {% data variables.location.product_location %}
+你可以使用活动仪表板和审核日志记录来监视 {% data variables.location.product_location %}。 有关详细信息，请参阅“[监视企业中的活动](/admin/monitoring-activity-in-your-enterprise)”。
-### 2. Configuring security features for your organizations
+### 2. 为组织配置安全功能
{% data reusables.getting-started.configuring-security-features %}
-## Part 4: Customizing and automating work on {% data variables.location.product_location %}
-You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
+## 第 4 部分：自定义和自动化 {% data variables.location.product_location %} 上的工作
+你可以使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_pages %} 在 {% data variables.location.product_location %} 中自定义和自动化组织中的工作。
-### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
{% data reusables.getting-started.api %}
-### 2. Building {% data variables.product.prodname_actions %}
+### 2. 生成 {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."
+有关为 {% data variables.product.product_name %} 启用和配置 {% data variables.product.prodname_actions %} 的详细信息，请参阅“[{% data variables.product.prodname_ghe_managed %} 的 {% data variables.product.prodname_actions %} 入门](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)”。
-### 3. Using {% data variables.product.prodname_pages %}
+### 3. 使用 {% data variables.product.prodname_pages %}
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## 第 5 部分：使用 {% data variables.product.prodname_dotcom %} 的学习和支持资源
+您的企业成员可以通过我们的学习资源了解有关 Git 和 {% data variables.product.prodname_dotcom %} 的更多信息，您也可以通过 {% data variables.product.prodname_dotcom %} Enterprise 支持获得所需的支持。
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+### 1. 在 {% data variables.product.prodname_docs %} 上阅读 {% data variables.product.product_name %}
+您可以阅读反映 {% data variables.product.prodname_ghe_managed %} 可用功能的文档。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)”。
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. 通过 {% data variables.product.prodname_learning %} 学习
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. 使用 {% data variables.product.prodname_dotcom %} Enterprise 支持
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index f3368b385c..7d52f9ba2f 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,128 +1,132 @@
---
-title: Getting started with GitHub Enterprise Server
-intro: 'Get started with setting up and managing {% data variables.location.product_location %}.'
+title: 开始使用 GitHub Enterprise Server
+intro: '开始设置和管理 {% data variables.location.product_location %}。'
versions:
ghes: '*'
+ms.openlocfilehash: 68cd462c42ef63863750d9edc5e122dc3c325115
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163414'
---
+本指南将引导你以企业管理员身份设置、配置和管理 {% data variables.location.product_location %}。
-This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator.
+{% data variables.product.company_short %} 提供了两种部署 {% data variables.product.prodname_enterprise %} 的方法。
-{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
+- {% data variables.product.prodname_ghe_cloud %}
+- {% data variables.product.prodname_ghe_server %}
-- **{% data variables.product.prodname_ghe_cloud %}**
-- **{% data variables.product.prodname_ghe_server %}**
+{% data variables.product.company_short %} 托管 {% data variables.product.prodname_ghe_cloud %}。 可以在自己的数据中心或受支持的云提供商中部署和托管 {% data variables.product.prodname_ghe_server %} 。
-{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
+有关 {% data variables.product.product_name %} 的详细信息，请参阅“[关于 {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)”。
-For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)."
+## 第 1 部分：安装 {% data variables.product.product_name %}
+要开始使用 {% data variables.product.product_name %}，您需要创建企业帐户、安装实例、使用管理控制台进行初始设置、配置实例和管理帐单。
+### 1. 创建企业帐户
+在安装 {% data variables.product.product_name %} 之前，可以通过联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)在 {% data variables.product.prodname_dotcom_the_website %} 上创建一个企业帐户。 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户可用于计费以及通过 {% data variables.product.prodname_github_connect %} 与 {% data variables.product.prodname_dotcom_the_website %} 共享功能。 有关详细信息，请参阅[关于企业帐户](/admin/overview/about-enterprise-accounts)。
+### 2. 安装 {% data variables.product.product_name %}
+要开始使用 {% data variables.product.product_name %}，您需要在所选的虚拟化平台上安装设备。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/installation/setting-up-a-github-enterprise-server-instance)”。
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing.
-### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+### 3. 使用管理控制台
+你将使用管理控制台在首次启动 {% data variables.location.product_location %} 时完成初始设置过程。 您还可以使用管理控制台管理实例设置，例如许可证、域、身份验证和 TLS。 有关详细信息，请参阅“[访问管理控制台](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)”。
-### 3. Using the Management Console
-You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+### 4. 配置 {% data variables.location.product_location %}
+除了管理控制台之外，还可以使用站点管理仪表板和管理 shell (SSH) 来管理 {% data variables.location.product_location %}。 例如，您可以配置应用程序和速率限制、查看报告、使用命令行实用程序。 有关详细信息，请参阅“[配置你的企业](/admin/configuration/configuring-your-enterprise)”。
-### 4. Configuring {% data variables.location.product_location %}
-In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
+您可以使用 {% data variables.product.product_name %} 通过动态主机配置协议 (DHCP) 使用的默认网络设置，也可以使用虚拟机控制台配置网络设置。 您还可以配置代理服务器或防火墙规则。 有关详细信息，请参阅“[配置网络设置](/admin/configuration/configuring-network-settings)”。
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+### 5. 配置高可用性
+可以配置 {% data variables.location.product_location %} 来实现高可用性，以最大程度地减少硬件故障和网络中断的影响。 有关详细信息，请参阅“[配置高可用性](/admin/enterprise-management/configuring-high-availability)”。
-### 5. Configuring high availability
-You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
+### 6. 设置暂存实例
+可以设置暂存实例来测试修改、规划灾难恢复，并在将更新应用于 {% data variables.location.product_location %} 之前试用更新。 有关详细信息，请参阅“[设置暂存实例](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)”。
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 7. 指定备份和灾难恢复
+要保护生产数据，可以使用 {% data variables.product.prodname_enterprise_backup_utilities %} 配置 {% data variables.location.product_location %} 的自动备份。 有关详细信息，请参阅“[在设备上配置备份](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)”。
-### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+### 8. 管理企业的账单
+对于连接到您的企业帐户的所有组织和 {% data variables.product.product_name %} 实例，帐单将汇总到所有付费 {% data variables.product.prodname_dotcom %}.com 服务的单个帐单费用中。 企业所有者和帐单管理员均可访问和管理企业帐户的帐单设置。 有关详细信息，请参阅“[管理企业的计费](/admin/overview/managing-billing-for-your-enterprise)”。
-### 8. Managing billing for your enterprise
-Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+## 第 2 部分：组织和管理团队
+作为企业所有者或管理员，您可以管理用户、存储库、团队和组织级别的设置。 您可以管理企业成员、创建和管理组织、设置存储库管理策略以及创建和管理团队。
-## Part 2: Organizing and managing your team
-As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
-
-### 1. Managing members of {% data variables.location.product_location %}
+### 1. 管理 {% data variables.location.product_location %} 的成员
{% data reusables.getting-started.managing-enterprise-members %}
-### 2. Creating organizations
+### 2. 创建组织
{% data reusables.getting-started.creating-organizations %}
-### 3. Adding members to organizations
+### 3. 向组织添加成员
{% data reusables.getting-started.adding-members-to-organizations %}
-### 4. Creating teams
+### 4. 创建团队
{% data reusables.getting-started.creating-teams %}
-### 5. Setting organization and repository permission levels
+### 5. 设置组织和存储库权限级别
{% data reusables.getting-started.setting-org-and-repo-permissions %}
-### 6. Enforcing repository management policies
+### 6. 实施存储库管理策略
{% data reusables.getting-started.enforcing-repo-management-policies %}
-## Part 3: Building securely
-To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
-### 1. Authenticating enterprise members
-You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+## 第 3 部分：安全构建
+要提高 {% data variables.location.product_location %} 的安全性，可以为企业成员配置身份验证，使用工具和审核日志记录以保持合规性，为组织配置安全性和分析功能，以及选择性地启用 {% data variables.product.prodname_GH_advanced_security %}。
+### 1. 对企业成员进行身份验证
+可以使用 {% data variables.product.product_name %} 的内置身份验证方法，也可以在外部身份验证提供程序（如 CAS、LDAP 或 SAML）之间进行选择，以集成现有帐户并集中管理用户对 {% data variables.location.product_location %} 的访问。 有关详细信息，请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)”。
-You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
+您还可以要求对每个组织进行双重身份验证。 有关详细信息，请参阅“[要求对组织进行双因素身份验证](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)”。
-### 2. Staying in compliance
-You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+### 2. 保持合规性
+您可以实施所需的状态检查和提交验证，以强制实施组织的合规性标准并自动执行合规性工作流。 您还可以使用组织的审核日志来查看团队执行的操作。 有关详细信息，请参阅“[使用预接收挂钩强制实施策略](/admin/policies/enforcing-policy-with-pre-receive-hooks)”和“[关于企业审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)”。
{% ifversion ghes %}
-### 3. Configuring security features for your organizations
-{% data reusables.getting-started.configuring-security-features %}
-{% endif %}
+### 3. 为组织配置安全功能
+{% data reusables.getting-started.configuring-security-features %} {% endif %}
{% ifversion ghes %}
-### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
-You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+### 4. 启用 {% data variables.product.prodname_GH_advanced_security %} 功能
+您可以升级 {% data variables.product.product_name %} 许可证以包含 {% data variables.product.prodname_GH_advanced_security %}。 这将提供额外的功能，帮助用户发现和修复其代码中的安全问题，例如代码和机密扫描。 有关详细信息，请参阅“[企业的 {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)”。
{% endif %}
-## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
-You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
+## 第 4 部分：自定义和自动化企业在 {% data variables.product.prodname_dotcom %} 上的工作
+您可以使用 {% data variables.product.prodname_dotcom %} 和 {% data variables.product.prodname_oauth_apps %}、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_pages %} 自定义和自动化企业中组织中的工作。
-### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. 构建 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %}
+您可以构建与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的集成，如 {% data variables.product.prodname_github_apps %} 或 {% data variables.product.prodname_oauth_apps %}，以便在企业中的组织中使用，以补充和扩展您的工作流程。 有关详细信息，请参阅“[关于应用](/developers/apps/getting-started-with-apps/about-apps)”。
+### 2. 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
{% data reusables.getting-started.api %}
{% ifversion ghes %}
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. 生成 {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+有关在 {% data variables.product.product_name %} 上启用和配置 {% data variables.product.prodname_actions %} 的详细信息，请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)”。
-### 4. Publishing and managing {% data variables.product.prodname_registry %}
+### 4. 发布和管理 {% data variables.product.prodname_registry %}
{% data reusables.getting-started.packages %}
-For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+有关启用和配置 {% data variables.location.product_location %} 的 {% data variables.product.prodname_registry %} 的详细信息，请参阅“[企业 {% data variables.product.prodname_registry %} 入门](/admin/packages/getting-started-with-github-packages-for-your-enterprise)”。
{% endif %}
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. 使用 {% data variables.product.prodname_pages %}
{% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
-You can use {% data variables.product.prodname_github_connect %} to share resources.
+## 第 5 部分：与其他 {% data variables.product.prodname_dotcom %} 资源连接
+您可以使用 {% data variables.product.prodname_github_connect %} 共享资源。
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+如果您既是 {% data variables.product.product_name %} 实例的所有者，又是 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者，则可以启用 {% data variables.product.prodname_github_connect %}。 {% data variables.product.prodname_github_connect %} 允许你在 {% data variables.location.product_location %} 和 {% data variables.product.prodname_ghe_cloud %} 之间共享特定的工作流和功能，例如统一搜索和贡献。 有关详细信息，请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
-## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## 第 6 部分：使用 {% data variables.product.prodname_dotcom %} 的学习和支持资源
+企业成员可以通过我们的学习资源了解有关 Git 和 {% data variables.product.prodname_dotcom %} 的更多信息，并且你可以在设置和管理 {% data variables.location.product_location %} 时向 {% data variables.product.prodname_dotcom %} Enterprise 支持获得所需的支持。
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+### 1. 在 {% data variables.product.prodname_docs %} 上阅读 {% data variables.product.product_name %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+您可以阅读反映 {% data variables.product.prodname_ghe_server %} 可用功能的文档。 有关详细信息，请参阅[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)。
{% data reusables.enterprise.best-practices %}
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. 通过 {% data variables.product.prodname_learning %} 学习
{% data reusables.getting-started.learning-enterprise %}
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. 使用 {% data variables.product.prodname_dotcom %} Enterprise 支持
{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 02ab297dbb..aafc899a78 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,6 +1,6 @@
---
-title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
-intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
+title: '从 {% data variables.product.prodname_projects_v1 %} 中迁移'
+intro: '可以将 {% data variables.projects.projects_v1_board %} 迁移到新的 {% data variables.product.prodname_projects_v2 %} 体验。'
miniTocMaxHeadingLevel: 3
versions:
feature: projects-v2
@@ -10,57 +10,53 @@ type: tutorial
topics:
- Projects
allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e6db4fd8c6587f413ee0e6832dbae93bbf281573
+ms.sourcegitcommit: 9bf175b190674416ad4e11b5c567409f74c00ad2
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/23/2022
+ms.locfileid: '148181219'
---
-
-
{% note %}
-**Notes:**
+**注意：**
-- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
-- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
-- Automation will not be migrated.
-- Triage, archive, and activity will not be migrated.
-- After migration, the new migrated project and old project will not be kept in sync.
+- 如果你要迁移的项目包含超过 {% data variables.projects.item_limit %} 个项，则将优先处理未结的问题，接着是未解决的拉取请求，然后是注释。 剩余的空间将用于已解决的问题、已合并的请求拉取和已解决的拉取请求。 由于此限制而无法迁移的项将被移动到存档。 如果达到 {% data variables.projects.archived_item_limit %} 个项的存档限制，则不会迁移其他项。
+- 注释卡被转换为草稿问题，内容被保存到草稿问题的正文中。 如果信息出现缺失，请使任何隐藏的字段可见。 有关详细信息，请参阅“[显示和隐藏字段](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)”。
+- 不会迁移自动化。
+- 不会迁移会审、存档和活动。
+- 迁移后，新迁移的项目和旧项目不会保持同步。
{% endnote %}
-## About project migration
+## 关于项目迁移
-You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
+可以将项目板迁移到新的 {% data variables.product.prodname_projects_v2 %} 体验，并试用表格、多个视图、新的自动化选项和强大的字段类型。 有关详细信息，请参阅“[关于项目](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)”。
-## Migrating an organization project board
+## 迁移组织项目板
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_org %}
-{% data reusables.user-settings.access_org %}
-{% data reusables.organizations.organization-wide-project %}
-1. On the left, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
+1. 在左侧，单击“Projects (经典)”。
+  {% data reusables.projects.migrate-project-steps %}
-## Migrating a user project board
+## 迁移用户项目板
-{% data reusables.projects.enable-migration %}
-{% data reusables.profile.access_profile %}
-1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
- 
-1. Above the list of projects, click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
+1. 在个人资料页面顶部的主导航栏中，单击 {% octicon "table" aria-label="The project board icon" %}“项目”。
+ 
+1. 在项目列表上方，单击“Projects (经典)”。
+  {% data reusables.projects.migrate-project-steps %}
-## Migrating a repository project board
+## 迁移存储库项目板
{% note %}
-**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
+注意：{% data variables.projects.projects_v2_caps %} 不支持存储库级别的项目。 当你迁移存储库项目板时，它将迁移到拥有存储库项目的组织或个人帐户，并且迁移的项目将被固定到原始存储库。
{% endnote %}
-{% data reusables.projects.enable-migration %}
-{% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
-
-1. Click **Projects (classic)**.
- 
-{% data reusables.projects.migrate-project-steps %}
+{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
+1. 在存储库名称下，单击 {% octicon "table" aria-label="The project board icon" %}“项目”。
+
+1. 单击“Projects (经典)”。
+  {% data reusables.projects.migrate-project-steps %}
diff --git a/translations/zh-CN/content/packages/quickstart.md b/translations/zh-CN/content/packages/quickstart.md
index 7ff2db3442..fbc1e38f29 100644
--- a/translations/zh-CN/content/packages/quickstart.md
+++ b/translations/zh-CN/content/packages/quickstart.md
@@ -1,6 +1,6 @@
---
-title: Quickstart for GitHub Packages
-intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
+title: GitHub Packages 快速入门
+intro: '通过 {% data variables.product.prodname_actions %} 发布到 {% data variables.product.prodname_registry %}。'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -8,29 +8,34 @@ versions:
ghae: '*'
ghec: '*'
shortTitle: Quickstart
+ms.openlocfilehash: 887c4ee6c5e6b3e2c391c2d5754cfcb2787e4b86
+ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/24/2022
+ms.locfileid: '148181251'
---
-
{% data reusables.actions.enterprise-github-hosted-runners %}
-## Introduction
+## 简介
-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 %}.
+在本指南中，您将创建 {% data variables.product.prodname_actions %} 工作流程来测试代码，然后将其发布到 {% data variables.product.prodname_registry %}。
-## Publishing your package
+## 发布包
-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.
+1. 在 {% data variables.product.prodname_dotcom %} 上创建新存储库，为节点添加 `.gitignore`。 有关详细信息，请参阅“[创建新存储库](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)”。
+2. 将存储库克隆到本地计算机。
```shell
$ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
$ cd YOUR-REPOSITORY
```
-3. Create an `index.js` file and add a basic alert to say "Hello world!"
+3. 创建 `index.js` 文件，并添加指示“Hello world!”的基本警报
{% raw %}
```javascript{:copy}
console.log("Hello, World!");
```
{% endraw %}
-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.
+4. 使用 `npm init` 初始化 npm 包。 在包初始化向导中，输入名称为 _`@YOUR-USERNAME/YOUR-REPOSITORY`_ 的包，并将测试脚本设置为 `exit 0`。 这将生成一个 `package.json` 文件，其中包含有关包的信息。
{% raw %}
```shell
$ npm init
@@ -41,15 +46,15 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
...
```
{% endraw %}
-5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
+5. 运行 `npm install` 以生成 `package-lock.json` 文件，然后提交更改并将其推送到 {% 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. 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 %}.
+6. 创建 `.github/workflows` 目录。 在此目录中，创建名为 `release-package.yml` 的文件。
+7. 将以下 YAML 内容复制到 `release-package.yml` 文件{% ifversion ghes or ghae %} 中，将 `YOUR-HOSTNAME` 替换为企业名称{% endif %}。
```yaml{:copy}
name: Node.js Package
@@ -85,22 +90,20 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
env:
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
```
-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 %}
+8. 告诉 NPM 使用以下方法之一发布包的范围和注册表：
+ - 在根目录中创建包含以下内容的 `.npmrc` 文件，为存储库添加 NPM 配置文件：{% raw %}
```shell
@YOUR-USERNAME:registry=https://npm.pkg.github.com
```
{% endraw %}
- - Edit the `package.json` file and specify the `publishConfig` key:
- {% raw %}
+ - 编辑 `package.json` 文件并指定 `publishConfig` 密钥：{% raw %}
```shell
"publishConfig": {
"@YOUR-USERNAME:registry": "https://npm.pkg.github.com"
}
```
{% endraw %}
-9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
+9. 提交并推送更改到 {% 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.
@@ -108,28 +111,26 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
$ git commit -m "workflow to publish package"
$ git push
```
-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 %}.
+10. 只要您的仓库中创建新版本，您创建的工作流程就会运行。 如果测试通过，则包将发布到 {% data variables.product.prodname_registry %}。
- 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)."
+ 要测试这一点，请导航到存储库中的“代码”选项卡，并创建新版本。 有关详细信息，请参阅“[管理存储库中的发行版](/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
+## 安装已发布的包
-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)."
+现在，您已发布包，您需要使用它作为项目之间的依赖项。 有关详细信息，请参阅“[使用 npm 注册表](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)”。
-## Next steps
+## 后续步骤
-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 %} 执行操作的开始。 您可以使用单个工作流和将包发布到多个注册表，触发工作流程以在发生不同事件（如合并拉取请求、管理容器等）时运行。
-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 %}:
+合并 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 可以帮助您实现应用程序开发过程几乎每个方面的自动化。 准备好开始了吗？ 以下是一些有用的资源，可用于执行 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 的后续步骤：
-- "[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
+- 有关 GitHub 包的深入教程，请“[了解 {% 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)”
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
index a66e99ee9a..6519ae98ef 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
@@ -1,6 +1,6 @@
---
-title: Creating a repository from a template
-intro: You can generate a new repository with the same directory structure and files as an existing repository.
+title: 从模板创建仓库
+intro: 您可以生成具有与现有仓库相同的目录结构和文件的新仓库。
redirect_from:
- /articles/creating-a-repository-from-a-template
- /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template
@@ -13,45 +13,46 @@ versions:
topics:
- Repositories
shortTitle: Create from a template
+ms.openlocfilehash: 16d124431426e19cf95c768e8a4cdaa5f4da2e17
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159762'
---
-## About repository templates
+## 关于仓库模板
-Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)."
+任何对模板仓库具有读取权限的人都可以从该模板创建仓库。 有关详细信息，请参阅“[创建模板存储库](/articles/creating-a-template-repository)”。
{% tip %}
-**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+提示：你也可以使用 {% data variables.product.prodname_cli %} 从模板创建存储库。 有关详细信息，请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh repo create`](https://cli.github.com/manual/gh_repo_create)”。
{% endtip %}
-You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
+您可以选择仅包括模板仓库的默认分支中的目录结构和文件，或者包括所有分支。 从模板创建的分支具有不相关的历史记录，这意味着您无法创建拉取请求或在分支之间合并。
-Creating a repository from a template is similar to forking a repository, but there are important differences:
-- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit.
-- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph.
-- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly.
+从模板创建仓库类似于创建仓库的复刻，但存在一些重要差异：
+- 新的复刻包含父仓库的整个提交历史记录，而从模板创建的仓库从一个提交开始记录。
+- 对复刻的提交不会显示在您的贡献图中，而对从模板创建的仓库的提交会显示在您的贡献图中。
+- 复刻可能是向现有项目贡献代码的临时方式，而从模板创建的仓库可以快速启动新项目。
-For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
+有关分支的详细信息，请参阅“[关于分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)”。
-## Creating a repository from a template
+## 从模板创建仓库
{% data reusables.repositories.navigate-to-repo %}
-1. Above the file list, click **Use this template**.
+1. 在文件列表上方，单击“使用此模板”。
{% ifversion fpt or ghec %}
-1. Select **Create a new repository**.
+1. 选择“创建新存储库”。
- 
+ 
{% note %}
- **Note:** Alternatively, you can open the template in a codespace and publish your work to a new repository later. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+ 注意：此外，你也可以在 codespace 中打开模板，稍后将工作发布到新存储库。 有关详细信息，请参阅“[通过模板创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)”。
- {% endnote %}
-{% endif %}
-{% data reusables.repositories.owner-drop-down %}
-{% data reusables.repositories.repo-name %}
-{% data reusables.repositories.choose-repo-visibility %}
-1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
- 
-{% data reusables.repositories.select-marketplace-apps %}
-8. Click **Create repository from template**.
+ {% endnote %} {% endif %} {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %}
+1. （可选）要在模板中包含来自所有分支的目录结构和文件，而不仅仅是默认分支，请选择“包含所有分支”。
+  {% data reusables.repositories.select-marketplace-apps %}
+8. 单击“从模板创建存储库”。
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
index 151756761d..c8db60f37b 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
@@ -1,6 +1,6 @@
---
-title: Automatically generated release notes
-intro: You can automatically generate release notes for your GitHub releases
+title: 自动生成的发行说明
+intro: 您可以为 GitHub 版本自动生成发行说明
permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release.
versions:
fpt: '*'
@@ -13,71 +13,63 @@ shortTitle: Automated release notes
communityRedirect:
name: Provide GitHub Feedback
href: 'https://github.com/orgs/community/discussions/categories/general'
+ms.openlocfilehash: aee951e6f57492240b5baf8870578409945aefdc
+ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/29/2022
+ms.locfileid: '148185192'
---
+## 关于自动生成的发行说明
-## About automatically generated release notes
+自动生成的发行说明为 {% data variables.product.prodname_dotcom %} 发行版手动编写发行说明提供了一种自动替代方法。 使用自动生成的发行说明，您可以快速生成发行版内容的概览。 自动生成的发行说明包括合并的拉取请求列表、发布参与者列表和完整更改日志的链接。
-Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. Automatically generated release notes include a list of merged pull requests, a list of contributors to the release, and a link to a full changelog.
+您还可以自定义自动发行说明，使用标签创建自定义类别来组织要包含的拉取请求，并排除某些标签和用户不出现在输出中。
-You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
+## 为新版本创建自动生成的发行说明
-## Creating automatically generated release notes for a new release
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
- 
-4. {% ifversion fpt or ghec %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag.
- {% ifversion fpt or ghec %}
- 
-5. If you are creating a new tag, click **Create new tag**.
-
- {% else %}
- 
-{% endif %}
-6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
- {% ifversion fpt or ghec %}
- {% else %}
- {% endif %}
-{%- data reusables.releases.previous-release-tag %}
-7. To the top right of the description text box, click {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% ifversion previous-release-tag %}
- {% else %}
- {% endif %}
-8. Check the generated notes to ensure they include all (and only) the information you want to include.
-9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
- 
-10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
- 
-{%- ifversion fpt or ghec %}
-11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
- 
-{%- endif %}
-12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
- 
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+3. 单击“草拟新发行版”。
+ 
+4. {% ifversion fpt or ghec %}单击“选择标记”，然后键入{% else %}键入{% endif %}发行版的版本号。 或者，选择现有标记。
+ {% ifversion fpt or ghec %} 
+5. 如果要创建新标记，请单击“创建新标记”。
+ {% else %}  {% endif %}
+6. 如果已创建新标记，请使用下拉菜单选择包含要发布的项目的分支。
+ {% ifversion fpt or ghec %}{% else %} {% endif %} {%- data reusables.releases.previous-release-tag %}
+7. 在说明文本框右上角，单击{% ifversion previous-release-tag %}“生成发行说明”{% else %}“自动生成发行说明”{% endif %}。{% ifversion previous-release-tag %}{% else %}{% endif %}
+8. 检查生成的注释，确保它们包含所有（且仅有）您要包含的信息。
+9. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。
+ 
+10. 若要通知用户发行版尚未准备投入生产，并且可能不稳定，请选择“这是预发行版”。
+  {%- ifversion fpt or ghec %}
+11. （可选）选择“为此版本创建讨论”，然后选择“类别”下拉菜单，然后单击类别进行版本讨论 。
+  {%- endif %}
+12. 如果已准备好公开发行版，请单击“发布发行版”。 若要稍后处理发行版，请单击“保存草稿”。
+ 
-## Configuring automatically generated release notes
+## 配置自动生成的发行说明
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.files.add-file %}
-3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory.
- 
-4. In the file, using the configuration options below, specify in YAML the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them.
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. 在文件名字段中，键入 `.github/release.yml` 以在 `.github` 目录中创建 `release.yml` 文件。
+ 
+4. 在文件中，使用下面的配置选项，在 YAML 中指定要从此版本中排除的拉取请求标签和作者。 您还可以创建新类别并列出要包含在每个类别中的拉取请求标签。
-### Configuration options
+### 配置选项
-| Parameter | Description |
+| 参数 | 说明 |
| :- | :- |
-| `changelog.exclude.labels` | A list of labels that exclude a pull request from appearing in release notes. |
-| `changelog.exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from release notes. |
-| `changelog.categories[*].title` | **Required.** The title of a category of changes in release notes. |
-| `changelog.categories[*].labels`| **Required.** Labels that qualify a pull request for this category. Use `*` as a catch-all for pull requests that didn't match any of the previous categories. |
-| `changelog.categories[*].exclude.labels` | A list of labels that exclude a pull request from appearing in this category. |
-| `changelog.categories[*].exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from this category. |
+| `changelog.exclude.labels` | 不在发行说明中显示拉取请求的标签列表。 |
+| `changelog.exclude.authors` | 要从发行说明中排除其拉取请求的用户或自动程序登录句柄的列表。 |
+| `changelog.categories[*].title` | **必填。** 发行说明中更改类别的标题。 |
+| `changelog.categories[*].labels`| **必填。** 符合此类别的拉取请求条件的标签。 使用 `*` 作为与上述任何类别都不匹配的拉取请求的统称。 |
+| `changelog.categories[*].exclude.labels` | 不在此类别中显示拉取请求的标签列表。 |
+| `changelog.categories[*].exclude.authors` | 要从此类别中排除其拉取请求的用户或自动程序登录句柄的列表。 |
-### Example configurations
+### 示例配置
-A configuration for a repository that labels semver releases
+标记 SemVer 版本的存储库配置
{% raw %}
```yaml{:copy}
@@ -104,7 +96,7 @@ changelog:
```
{% endraw %}
-A configuration for a repository that doesn't tag pull requests but where we want to separate out {% data variables.product.prodname_dependabot %} automated pull requests in release notes (`labels: '*'` is required to display a catchall category)
+不标记拉取请求但我们希望在发行说明中分离 {% data variables.product.prodname_dependabot %} 自动拉取请求的存储库的配置（`labels: '*'` 需要显示 catchall 类别）
{% raw %}
```yaml{:copy}
@@ -124,6 +116,6 @@ changelog:
```
{% endraw %}
-## Further reading
+## 延伸阅读
-- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)"
+- [管理标签](/issues/using-labels-and-milestones-to-track-work/managing-labels)
diff --git a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
index 15c875228b..0405c17d4f 100644
--- a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
+++ b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
@@ -1,6 +1,6 @@
---
-title: Understanding connections between repositories
-intro: Use the network graph and forks list to understand fork networks.
+title: 了解仓库之间的连接
+intro: 使用网络图和分支列表了解分支网络。
product: '{% data reusables.gated-features.repository-insights %}'
redirect_from:
- /articles/viewing-a-repository-s-network
@@ -22,57 +22,60 @@ versions:
topics:
- Repositories
shortTitle: Connections between repositories
+ms.openlocfilehash: 46cc440093c3ca8dc0952933847a6f04b0446661
+ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 12/03/2022
+ms.locfileid: '148191353'
---
+## 查看仓库的网络
-## Viewing a repository's network
-
-The network graph displays the branch history of the entire repository network, including fork branches. This graph is a timeline of the most recent commits, and shows up to 100 of the most recently pushed-to branches. The first row references the date and the first column references the branch owner. Use arrow keys or other keyboard shortcuts to more easily navigate the graph. They are provided in the “Keyboard shortcuts available” pop up under the graph.
+网络图显示了整个存储库网络的分支历史记录，包括创建分支。 此图是最近提交的时间线，最多显示 100 个最近已推送的分支。 第一行引用日期，第一列引用分支所有者。 使用箭头键或其他键盘快捷方式可以更轻松地在图中浏览。 图下面的“可用的键盘快捷方式”弹出窗口中提供了这些选项。
-
+
{% tip %}
-**Tip:** To see older branches, click and drag within the graph.
+提示：若要查看较旧的分支，请在图中单击并拖动。
{% endtip %}
-## Accessing the network graph
+## 访问网络图
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-3. In the left sidebar, click **Network**.
-
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+3. 在左侧边栏中，单击“网络”。
+
-## Listing the forks of a repository
+## 列出仓库的复刻
-The Members graph displays all the forks of a repository.
+成员图显示仓库的所有复刻。
-Forks are listed alphabetically by the organization or username of the person who forked the repository. You can click on the organization or username to be redirected to the organization or user's {% data variables.product.product_name %} profile page or click on the fork name to be redirected to the specific fork of the repository.
+分支按存储库分支创建组织或创建者用户名的字母顺序列出。 可以单击要重定向到组织或用户 {% data variables.product.product_name %} 个人资料页面的组织或用户名，或者单击要重定向到存储库特定分支的分支名称。
{% ifversion fpt or ghec %}
-
+
{% else %}
-
+
{% endif %}
-### Accessing the Members graph
+### 访问成员图
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.accessing-repository-graphs %}
-3. In the left sidebar, click **Forks**.
-
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+3. 在左侧边栏中，单击“分支”。
+
-## Viewing the dependencies of a repository
+## 查看仓库的依赖项
-You can use the dependency graph to explore the code your repository depends on.
+您可以使用依赖关系图来浏览仓库所依赖的代码。
-Almost all software relies on code developed and maintained by other developers, often known as a supply chain. For example, utilities, libraries, and frameworks. These dependencies are an integral part of your code and any bugs or vulnerabilities in them may affect your code. It's important to review and maintain these dependencies.
+几乎所有软件都依赖于其他开发者开发和维护的代码，常常被称为供应链。 例如，实用程序、库和框架。 这些依赖项是代码不可分割的一部分，其中的任何错误或漏洞都可能影响您的代码。 审查和维护这些依赖项非常重要。
-The dependency graph provides a great way to visualize and explore the dependencies for a repository. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)."
+依赖关系图提供了可视化和探索仓库依赖关系的好方法。 有关详细信息，请参阅“[关于依赖项关系图](/code-security/supply-chain-security/about-the-dependency-graph)”和“[探索存储库的依赖项](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)”。
-You can also set up your repository so that {% data variables.product.company_short %} alerts you automatically whenever a security vulnerability is found in one of your dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+您也可以设置仓库，以便在您的一个依赖项中发现安全漏洞时，{% data variables.product.company_short %} 会自动提醒您。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md
index ea88316e23..49e05da0b8 100644
--- a/translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -1,6 +1,6 @@
---
-title: Viewing a file
-intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
+title: 查看文件
+intro: 可以查看原始文件内容或跟踪对文件中各行的更改，了解文件的各个部分如何随时间演变。
redirect_from:
- /articles/using-git-blame-to-trace-changes-in-a-file
- /articles/tracing-changes-in-a-file
@@ -16,48 +16,54 @@ versions:
topics:
- Repositories
shortTitle: View files and track file changes
+ms.openlocfilehash: 7d34e776cb1747ee749531e49abf6f0e3d052b3b
+ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/21/2022
+ms.locfileid: '148179847'
---
-## Viewing or copying the raw file content
+## 查看或复制原始文件内容
-With the raw view, you can view or copy the raw content of a file without any styling.
+使用原始视图，可以查看或复制不带任何样式的文件原始内容。
{% data reusables.repositories.navigate-to-repo %}
-1. Click the file that you want to view.
-2. In the upper-right corner of the file view, click **Raw**.
-
-3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
+1. 单击要查看的文件。
+2. 在文件视图的右上角，单击“原始”。
+
+3. （可选）若要复制原始文件内容，请在文件视图右上角单击“{% octicon "copy" aria-label="The copy icon" %}”。
-## Viewing the line-by-line revision history for a file
+## 查看文件的逐行修订历史记录
-With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
+使用追溯视图时，可以查看整个文件的逐行修订历史记录，也可以单击 {% octicon "versions" aria-label="The prior blame icon" %} 查看文件中某一行的修订历史记录。 每次单击 {% octicon "versions" aria-label="The prior blame icon" %} 后，将看到该行以前的修订信息，包括提交更改的人员和时间。
-
+
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+在文件或拉取请求中，还可以使用 {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} 菜单查看所选行或行范围的 Git 追溯。
-
+
{% tip %}
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+提示：在命令行上，还可以使用 `git blame` 查看文件内各行的修订历史记录。 有关详细信息，请参阅 [Git 的 `git blame` 文档](https://git-scm.com/docs/git-blame)。
{% endtip %}
{% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-
+2. 单击以打开您想要查看其行历史记录的文件。
+3. 在文件视图的右上角，单击“追溯”以打开追溯视图。
+
+4. 若要查看特定行的早期修订，或重新追溯，请单击 {% octicon "versions" aria-label="The prior blame icon" %}，直至找到你想查看的更改。
+
{% ifversion blame-ignore-revs %}
-## Ignore commits in the blame view
+## 忽略追溯视图中的提交
-All revisions specified in the `.git-blame-ignore-revs` file, which must be in the root directory of your repository, are hidden from the blame view using Git's `git blame --ignore-revs-file` configuration setting. For more information, see [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) in the Git documentation.
+`.git-blame-ignore-revs` 文件中指定的所有修订（必须位于存储库的根目录中）利用 Git 的 `git blame --ignore-revs-file` 配置设置从追溯视图中隐藏。 有关详细信息，请参阅 Git 文档中的 [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt)。
-1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`.
-2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:
+1. 在存储库的根目录中，创建一个名为 `.git-blame-ignore-revs` 的文件。
+2. 在该文件中添加要从追溯视图中排除的提交哈希。 建议按如下所示构建文件（包括评论）：
```ini
# .git-blame-ignore-revs
@@ -67,19 +73,19 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t
69d029cec8337c616552756310748c4a507bd75a
```
-3. Commit and push the changes.
+3. 提交并推送更改。
-Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden:
+现在，访问追溯视图时，追溯中将不会包含列出的修订。 你会看到“忽略 .git-blame-ignore-revs 中的修订”横幅，表明某些提交可能已隐藏：
-
+
-This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well:
+当一些提交对代码进行大量更改时，这非常有用。 也可以在本地运行 `git blame` 时使用该文件：
```shell
git blame --ignore-revs-file .git-blame-ignore-revs
```
-You can also configure your local git so it always ignores the revs in that file:
+还可以配置本地 git，使其始终忽略该文件中的修订：
```shell
git config blame.ignoreRevsFile .git-blame-ignore-revs
@@ -87,6 +93,6 @@ git config blame.ignoreRevsFile .git-blame-ignore-revs
{% endif %}
-## Bypassing `.git-blame-ignore-revs` in the blame view
+## 绕过追溯视图中的 `.git-blame-ignore-revs`
-If the blame view for a file shows **Ignoring revisions in .git-blame-ignore-revs**, you can still bypass `.git-blame-ignore-revs` and see the normal blame view. In the URL, append a `~` to the SHA and the **Ignoring revisions in .git-blame-ignore-revs** will disappear.
+如果文件的追溯视图显示“忽略 .git-blame-ignore-revs 中的修订”，仍可以绕过 `.git-blame-ignore-revs` 并查看正常的追溯视图。 在 URL 中，将 `~` 追加到 SHA，“忽略 .git-blame-ignore-revs 中的修订”将消失。
diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md
index a8b760abd8..e3a572ae8f 100644
--- a/translations/zh-CN/content/rest/overview/libraries.md
+++ b/translations/zh-CN/content/rest/overview/libraries.md
@@ -11,12 +11,12 @@ versions:
ghec: '*'
topics:
- API
-ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
-ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
+ms.openlocfilehash: 5f633132edddb17ae129a3feba791ab8ec780366
+ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
ms.translationtype: HT
ms.contentlocale: zh-CN
-ms.lasthandoff: 12/01/2022
-ms.locfileid: '148190059'
+ms.lasthandoff: 12/06/2022
+ms.locfileid: '148191876'
---
@@ -26,7 +26,7 @@ ms.locfileid: '148190059'
- Ruby → [octokit.rb](https://github.com/octokit/octokit.rb)
- .NET → [octokit.net](https://github.com/octokit/octokit.net)
-- JavaScript → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+- JavaScript → [octokit.js](https://github.com/octokit/octokit.js)
## 第三方库
diff --git a/translations/zh-CN/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/zh-CN/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
index 60a2a21855..e53a389ec6 100644
--- a/translations/zh-CN/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
+++ b/translations/zh-CN/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -1,6 +1,6 @@
---
-title: 查看和更新支持工单
-intro: '可以查看支持票证{% ifversion ghes or ghec %}，与同事协作处理票证，{% endif %}并使用 {% data variables.contact.support_portal %} 响应 {% data variables.contact.github_support %}。'
+title: Viewing and updating support tickets
+intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.'
shortTitle: Managing your tickets
versions:
fpt: '*'
@@ -8,62 +8,64 @@ versions:
ghes: '*'
topics:
- Support
-ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147051978'
---
-## 关于工单管理
+
+## About ticket management
{% data reusables.support.zendesk-old-tickets %}
-可以使用 [GitHub 支持门户](https://support.github.com/)查看当前和过去的支持工单并回复 {% data variables.contact.github_support %}。 120 天后，已解决的票证将会存档{% ifversion ghec or ghes or ghae %}，并且只能查看企业帐户的已存档票证{% endif %}。
+You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}. After 120 days, resolved tickets are archived{% ifversion ghec or ghes or ghae %}, and archived tickets can only be viewed for enterprise accounts{% endif %}.
-{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+{% ifversion ghes or ghec %}
+{% data reusables.enterprise-accounts.support-entitlements %}
+{% endif %}
-## 查看最近的支持票证
+## Viewing your recent support tickets
{% data reusables.support.view-open-tickets %}
-1. 在文本框下，可以阅读评论历史记录。 最近的回复位于顶部。
-
+1. Under the text box, you can read the comment history. The most recent response is at the top.
+
+ 
+
+1. Optionally, to translate the ticket comment, click {% octicon "globe" aria-label="The globe icon" %} and choose your preferred language from the dropdown menu. You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish.
+
+ 
{% ifversion ghec or ghes or ghae %}
-## 查看已存档的支持票证
+## Viewing your archived support tickets
-只能查看企业帐户的已存档票证。
+You can only view archived tickets for an enterprise account.
{% data reusables.support.navigate-to-my-tickets %}
-1. 选择“我的票证”下拉菜单，然后单击企业帐户的名称。
+1. Select the **My Tickets** drop-down menu and click the name of the enterprise account.
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
- 
-1. 在“我的票证”表下，单击“查看已存档的票证”。
+ 
+1. Under the "My tickets" table, click **View archived tickets**.
{% endif %}
-## 更新支持工单
+## Updating support tickets
{% data reusables.support.view-open-tickets %}
-1. （可选）如果问题得到解决，请在文本框下单击“关闭工单”。
-
-1. 若要回复 GitHub 支持并向工单添加新评论，请在文本框中输入你的回复。
-
-1. 若要将评论添加到工单，请单击“评论”。
-
+1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
+
+1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
+
+1. To add your comment to the ticket, click **Comment**.
+
{% ifversion ghec or ghes %}
-## 协作处理支持工单
+## Collaborating on support tickets
-你可以使用支持门户与你的同事协作处理支持工单。 拥有支持权利的所有者、计费管理员和其他企业成员可以查看与企业帐户或由企业帐户管理的组织关联的工单。 有关详细信息，请参阅“[管理企业的支持权利](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)”。
+You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-除了查看票据外，如果电子邮件地址复制到了工单上，或者工单创建者使用的电子邮件地址的域名被验证为企业帐户或企业帐户管理的组织，则还可以向支持工单添加评论。 有关验证域的详细信息，请参阅“[为企业验证或批准域](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)”和“[为组织验证或批准域](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)”。
+In addition to viewing tickets, you can also add comments to support tickets if your email address is copied on the ticket or if the person who opened the ticket used an email address with a domain that is verified for the enterprise account or organization managed by an enterprise account. For more information about verifying a domain, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Verifying or approving a domain for your organization](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
{% endif %}
-## 延伸阅读
+## Further reading
-- [关于 GitHub 支持](/support/learning-about-github-support/about-github-support)
+- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
diff --git a/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md b/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
index f5d6525f05..be735ece17 100644
--- a/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md
@@ -83,6 +83,10 @@ If you have any paid product or are a member of an organization with a paid prod
With {% data variables.product.product_name %}, you have access to support in English and Japanese.
{% endif %}
+{% ifversion fpt or ghec or ghes %}
+{% data reusables.support.support-ticket-translation-option %}
+{% endif %}
+
{% ifversion ghes or ghec %}
To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml
index 028b8750b6..2d4ef88879 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml
@@ -29,4 +29,5 @@ sections:
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
- |
- GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
\ No newline at end of file
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml
index b7f41bbb96..05de05ac2b 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml
@@ -1,27 +1,30 @@
date: '2022-08-30'
sections:
bugs:
- - 解锁存储库以进行临时访问后，站点管理员无法管理存储库中安全产品的设置。
- - 管理控制台和 `/home/admin/.ssh/authorized_keys` 文件中可能会出现重复的管理 SSH 密钥。
- - "http(s)://HOSTNAME/stafftools/users/USERNAME/admin 的个人用户的站点管理员页面包含不适用于 GitHub Enterprise Server 的功能。"
- - 在某些情况下，运行 `ghe-cluster-config-apply` 可以将空配置复制到群集中的现有节点。
- - 在某些情况下，以 `ghe-config-apply` 开始的配置运行未完成，或返回了 `Container count mismatch` 错误。
- - 在 GitHub Enterprise Server 实例上更新自签名 TLS 证书后，Web 界面中某些页面上的 UI 元素没有显示。
- - Web 界面顶部的站点管理员栏包含指向当前正在运行的应用程序版本的 SHA 的断开链接。
- - 在某些情况下，尽管不是线程安全的，但由于同时使用的库，可能会导致后台任务停止。
- - 如果站点管理员没有直接升级到 GitHub Enterprise Server 3.4，则 Web UI 和 REST API 中缺少来自 GitHub Advanced Security 客户的机密扫描的警报。警报现在可见。
- - 当用户将存储库分叉到组织中时，一长串组织将无法正确呈现。
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
+ - When a user forked a repository into an organization, a long list of organizations would not render properly.
changes:
- - "由于并行日志清理，支持包的生成速度更快。有关支持包的详细信息，请参阅“[将数据提供给 GitHub 支持](/support/contacting-github-support/providing-data-to-github-support)”。"
- - "包含 `organization` 或 `org` 路由的 API 现在接受组织的 slug 或 ID。以前，API 只接受 slug，这导致 GitHub Advanced Security 终结点的 `Link` 标头无法访问。有关详细信息，请参阅 REST API 文档中的“[组织](https://docs.github.com/rest/orgs/orgs)”。"
- - "企业审核日志现在包含更多用户生成的事件，例如 `project.create`。REST API 还返回其他用户生成的事件，例如 `repo.create`。有关详细信息，请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for -your-enterprise)”和“[使用企业的审核日志 API](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit- log-api-for-your-enterprise#querying-the-audit-log-rest-api)”。"
- - "在某些情况下，缓存副本可能会拒绝对最近更新的存储库的某些 Git 操作。有关存储库缓存的详细信息，请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。"
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
known_issues:
- - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。"
- - 自定义防火墙规则在升级过程中被删除。
- - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。"
- - 如果问题包含指向同一存储库中 Blob 的永久链接，且 Blob 的文件路径长度超过 255 个字符，则无法关闭问题。
- - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。
- - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。"
- - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。
- - 从不同主机上的备份恢复设备后，需要重新启动操作服务。
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml
index 8ec4162b87..6e638df146 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml
@@ -1,33 +1,38 @@
date: '2022-08-30'
sections:
bugs:
- - 解锁存储库以进行临时访问后，站点管理员无法管理存储库中安全产品的设置。
- - 管理控制台和 `/home/admin/.ssh/authorized_keys` 文件中可能会出现重复的管理 SSH 密钥。
- - "http(s)://HOSTNAME/stafftools/users/USERNAME/admin 的个人用户的站点管理员页面包含不适用于 GitHub Enterprise Server 的功能。"
- - 在某些情况下，运行 `ghe-cluster-config-apply` 可以将空配置复制到群集中的现有节点。
- - 在某些情况下，以 `ghe-config-apply` 开始的配置运行未完成，或返回了 `Container count mismatch` 错误。
- - 在 GitHub Enterprise Server 实例上更新自签名 TLS 证书后，Web 界面中某些页面上的 UI 元素没有显示。
- - 在某些情况下，尽管不是线程安全的，但由于同时使用的库，可能会导致后台任务停止。
- - Web 界面顶部的站点管理员栏包含指向当前正在运行的应用程序版本的 SHA 的断开链接。
- - 组织所有者无法设置创建讨论所需的访问级别。
- - 讨论用户被错误地引导至 GitHub.com 的社区指南。
- - 在某些情况下，系统错误地指示用户在创建讨论之前验证其电子邮件。
- - 如果站点管理员没有直接升级到 GitHub Enterprise Server 3.4，则 Web UI 和 REST API 中缺少来自 GitHub Advanced Security 客户的机密扫描的警报。警报现在可见。
+ - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
+ - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+ - The site admin page for individual users at http(s)://HOSTNAME/stafftools/users/USERNAME/admin contained functionality not intended for GitHub Enterprise Server.
+ - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
+ - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
+ - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
+ - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+ - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+ - Organization owners were unable to set the level of access required to create discussions.
+ - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
+ - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
+ - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
changes:
- - "由于并行日志清理，支持包的生成速度更快。有关支持包的详细信息，请参阅“[将数据提供给 GitHub 支持](/support/contacting-github-support/providing-data-to-github-support)”。"
- - "包含 `organization` 或 `org` 路由的 API 现在接受组织的 slug 或 ID。以前，API 只接受 slug，这导致 GitHub Advanced Security 终结点的 `Link` 标头无法访问。有关详细信息，请参阅 REST API 文档中的“[组织](https://docs.github.com/rest/orgs/orgs)”。"
- - "企业审核日志现在包含更多用户生成的事件，例如 `project.create`。REST API 还返回其他用户生成的事件，例如 `repo.create`。有关详细信息，请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for -your-enterprise)”和“[使用企业的审核日志 API](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit- log-api-for-your-enterprise#querying-the-audit-log-rest-api)”。"
- - "在某些情况下，缓存副本可能会拒绝对最近更新的存储库的某些 Git 操作。有关存储库缓存的详细信息，请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。"
- - "你现在可以使用 REST API 将全局公告横幅配置为可关闭。有关详细信息，请参阅“[为企业自定义用户消息](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)”。"
+ - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+ - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
+ - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+ - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+ - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
known_issues:
- - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。"
- - 自定义防火墙规则在升级过程中被删除。
- - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。"
- - 如果问题包含指向同一存储库中 Blob 的永久链接，且 Blob 的文件路径长度超过 255 个字符，则无法关闭问题。
- - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。
- - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。"
- - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。
- - 从不同主机上的备份恢复实例后，需要重新启动操作服务。
- - 在存储库的设置中，启用允许具有读取访问权限的用户创建讨论的选项不会启用此功能。
- - 在某些情况下，用户无法将现有问题转换为讨论。
- - 机密扫描的自定义模式将 `.*` 作为结束分隔符，特别是在“机密之后”字段中。此分隔符会导致跨存储库的机密扫描不一致，并且你可能会注意到存储库历史记录中没有完成扫描的间隙。增量扫描也可能受到影响。为防止出现扫描问题，请修改模式的结尾以删除 `.*` 分隔符。
+ - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+ - Custom firewall rules are removed during the upgrade process.
+ - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+ - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+ - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+ - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+ - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+ - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+ - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+ - In some cases, users cannot convert existing issues to discussions.
+ - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+ - |
+ After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+ - |
+ GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
+ - '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 6453ec97cd..1193172cdd 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,18 +1,10 @@
----
-ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145098450"
----
-可以使用 `jobs..if` 条件来阻止步骤运行，除非满足条件。 您可以使用任何支持上下文和表达式来创建条件。
+You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. {% data reusables.actions.if-supported-contexts %}
-{% data reusables.actions.expression-syntax-if %} 有关详细信息，请参阅“[表达式](/actions/learn-github-actions/expressions)”。
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
-### 示例：仅针对特定存储库运行作业
+### Example: Only run job for specific repository
-此示例使用 `if` 控制 `production-deploy` 作业何时可以运行。 仅当存储库名为 `octo-repo-prod` 且位于 `octo-org` 组织内时，它才会运行。 否则，作业将被标记为“跳过”。
+This example uses `if` to control when the `production-deploy` job can run. It will only run if the repository is named `octo-repo-prod` and is within the `octo-org` organization. Otherwise, the job will be marked as _skipped_.
```yaml{:copy}
name: example-workflow
diff --git a/translations/zh-CN/data/reusables/actions/reusable-workflows-enterprise-beta.md b/translations/zh-CN/data/reusables/actions/reusable-workflows-enterprise-beta.md
new file mode 100644
index 0000000000..6064e0e17e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/reusable-workflows-enterprise-beta.md
@@ -0,0 +1,17 @@
+{% ifversion ghes = 3.4 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently in beta and subject to change.
+
+{% endnote %}
+
+{% elsif ghae > 3.3 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently unavailable in {% data variables.product.product_name %}, but will be available in a future update.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/zh-CN/data/reusables/actions/reusable-workflows-ghes-beta.md
deleted file mode 100644
index 12b8d14fe6..0000000000
--- a/translations/zh-CN/data/reusables/actions/reusable-workflows-ghes-beta.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-ms.openlocfilehash: 933805023c32c3e956b510000cdaff7326b880e3
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145065894"
----
-{% ifversion ghes = 3.4 %}
-
-{% note %}
-
-注意：可重用工作流目前处于 beta 版本阶段，可能会更改。
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md
index 80878d1726..24b839f410 100644
--- a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
- Starring a repository
- Deleting a repository
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
+- Joining an organization
+
+{% ifversion ghes %}
+A user will also be considered active if their account has been updated by LDAP.
+{% endif %}
diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml
index 1e8377dd72..29dec0fbef 100644
--- a/translations/zh-CN/data/ui.yml
+++ b/translations/zh-CN/data/ui.yml
@@ -127,7 +127,7 @@ products:
rest:
banner:
api_versioned: The REST API is now versioned.
- api_version_info: For more information, see "About API versioning".
+ api_version_info: For more information, see "About API versioning."
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "About versions of GitHub Docs".
versioning:
about_versions: About REST API versions
