+|
macOS Big Sur 11
|
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md
new file mode 100644
index 0000000000..776a08709f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md
@@ -0,0 +1,3 @@
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
+1. On the "Codespace policies" page, click **Create Policy**.
+1. Enter a name for your new policy.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md b/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md
new file mode 100644
index 0000000000..04e4a9bfda
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md
@@ -0,0 +1,11 @@
+1. In the "Change policy target" area, click the dropdown button.
+1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+1. [**Selected repositories**] を選択した場合、以下の手順に従います。
+ 1. {% octicon "gear" aria-label="The settings icon" %} をクリックします。
+
+ 
+
+ 2. Select the repositories you want this policy to apply to.
+ 3. At the bottom of the repository list, click **Select repositories**.
+
+ 
diff --git a/translations/ja-JP/data/reusables/projects/access-insights.md b/translations/ja-JP/data/reusables/projects/access-insights.md
index 4c7cf259d0..07383bb1f0 100644
--- a/translations/ja-JP/data/reusables/projects/access-insights.md
+++ b/translations/ja-JP/data/reusables/projects/access-insights.md
@@ -1,4 +1,4 @@
-1. Navigate to your project.
+1. プロジェクトにアクセスします。
2. In the top-right, to access insights, click {% octicon "graph" aria-label="the graph icon" %}.
{% note %}
diff --git a/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md b/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md
index fa23f9b50d..7fec011d57 100644
--- a/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md
+++ b/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md
@@ -1,4 +1,6 @@
-1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}.
+1. プロジェクトにアクセスします。
+1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
+1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
1. Under **Default workflows**, click on the workflow that you want to edit.
1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on.
1. Next to **Set**, choose the value that you want to set the status to.
diff --git a/translations/ja-JP/data/reusables/projects/project-settings.md b/translations/ja-JP/data/reusables/projects/project-settings.md
index bee73a5c66..9005046592 100644
--- a/translations/ja-JP/data/reusables/projects/project-settings.md
+++ b/translations/ja-JP/data/reusables/projects/project-settings.md
@@ -1,2 +1,3 @@
-1. Navigate to your project.
-1. Click {% octicon "gear" aria-label="the gear icon" %} to access the project settings.
+1. プロジェクトにアクセスします。
+1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
+1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings.
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
index 6d236d1cd1..59b535a581 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
@@ -1,63 +1,63 @@
---
-title: Setting your profile to private
-intro: 'A private profile displays only limited information, and hides some activity.'
+title: 将您的个人资料设置为私密
+intro: 私密个人资料仅显示有限的信息，并隐藏某些活动。
versions:
fpt: '*'
topics:
- Profiles
-shortTitle: Set profile to private
+shortTitle: 将个人资料设置为私密
---
-## About private profiles
+## 关于私密个人资料
{% note %}
-**Note:** Private profiles are currently in beta and are subject to change.
+**注意：**私密个人资料目前处于测试阶段，可能会有所变化。
{% endnote %}
-To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity.
+要隐藏部分个人资料页面，您可以将个人资料设为私密。 这也会隐藏您在 {% data variables.product.prodname_dotcom_the_website %} 上的各种社交功能中的活动。 私密个人资料会隐藏所有用户的信息，并且当前没有允许指定用户查看您的活动的选项。
-After making your profile private, you can still view all your information when you visit your own profile.
+将个人资料设为私密后，您仍然可以在访问自己的个人资料时查看所有信息。
-Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private.
+私密个人资料在 [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) 下不能获得赞助。 要获得 {% data variables.product.prodname_sponsors %} 资格，您的个人资料不能是私密的。
-## Differences between private and public profiles
+## 私密个人资料与公共个人资料之间的差异
-When your profile is private, the following content is hidden from your profile page:
+当您的个人资料为私密时，您的个人资料页面中会隐藏以下内容：
-- Achievements and highlights.
-- Activity overview and activity feed.
-- Contribution graph.
-- Follower and following counts.
-- Follow and Sponsor buttons.
-- Organization memberships.
-- Stars, projects, packages, and sponsoring tabs.
+- 成就和亮点。
+- 活动概述和活动源。
+- 贡献图。
+- 关注者和关注数。
+- 关注和赞助者按钮。
+- 组织成员资格。
+- 星标、项目、包和赞助标签。
{% note %}
-**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo.
+**注意**：当您的个人资料为私密时，某些可选字段仍可公开显示，例如自述文件、传记和头像。
{% endnote %}
-## Changes to reporting on your activities
+## 更改活动报告
-By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled.
+通过将个人资料设为私密，您无法删除或隐藏过去的活动；此设置仅适用于启用私密设置时的活动。
-When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations:
+当您的个人资料为私密时，您的 {% data variables.product.prodname_dotcom_the_website %} 活动将不会显示在以下位置：
-- Activity feeds for other users.
-- Discussions leaderboards.
-- The [Trending](https://github.com/trending) page.
+- 其他用户的活动源。
+- 讨论排行榜。
+- [热门](https://github.com/trending)页面。
{% note %}
-**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API.
+**注意**：您在公共仓库上的活动仍将对查看这些仓库的任何人公开可见，并且某些活动数据可能仍可通过 {% data variables.product.prodname_dotcom %} API 获得。
{% endnote %}
-## Changing your profile's privacy settings
+## 更改个人资料的隐私设置
{% data reusables.user-settings.access_settings %}
-1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**.
+1. 在“Contributions & Activity（贡献和活动）”下，选中 **Make profile private and hide activity（将个人资料设为私密并隐藏活动）**旁边的复选框。
{% data reusables.user-settings.update-preferences %}
diff --git a/translations/zh-CN/content/actions/using-workflows/about-workflows.md b/translations/zh-CN/content/actions/using-workflows/about-workflows.md
index 34f7c968d4..14e5cb9929 100644
--- a/translations/zh-CN/content/actions/using-workflows/about-workflows.md
+++ b/translations/zh-CN/content/actions/using-workflows/about-workflows.md
@@ -1,7 +1,7 @@
---
title: 关于工作流程
shortTitle: 关于工作流程
-intro: 'Get a high level overview {% data variables.product.prodname_actions %} workflows, including triggers, syntax, and advanced features.'
+intro: '获取 {% data variables.product.prodname_actions %} 工作流程的高级概述，包括触发器、语法和高级功能。'
versions:
fpt: '*'
ghes: '*'
@@ -20,15 +20,15 @@ miniTocMaxHeadingLevel: 3
{% data reusables.actions.about-workflows-long %}
-## Workflow basics
+## 工作流程基础知识
-A workflow must contain the following basic components:
+工作流程必须包含以下基本组件：
-1. One or more _events_ that will trigger the workflow.
-1. One or more _jobs_, each of which will execute on a _runner_ machine and run a series of one or more _steps_.
-1. Each step can either run a script that you define or run an action, which is a reusable extension that can simplify your workflow.
+1. 将触发工作流程的一个或多个_事件_。
+1. 一个或多个_作业_，每个作业将在_运行器_计算机上执行，并运行一系列一个或多个_步骤_。
+1. 每个步骤都可以运行您定义的脚本，也可以运行操作，这是一个可重用的扩展，可以简化您的工作流程。
-For more information these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)."
+For more information on these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)."
@@ -36,32 +36,32 @@ For more information these basic components, see "[Understanding GitHub Actions]
{% data reusables.actions.about-triggers %}
-For more information, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)", and for a full list of events, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
+更多信息请参阅“[触发工作流程](/actions/using-workflows/triggering-a-workflow)”，有关事件的完整列表，请参阅“[触发工作流程的事件](/actions/using-workflows/events-that-trigger-workflows)”。
## 工作流程语法
-Workflow are defined using YAML. For the full reference of the YAML syntax for authoring workflows, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#about-yaml-syntax-for-workflows)."
+工作流程是使用 YAML 定义的。 有关用于创建工作流程的 YAML 语法的完整参考，请参阅“[GitHub Actions 的工作流程语法](/actions/using-workflows/workflow-syntax-for-github-actions#about-yaml-syntax-for-workflows)”。
{% data reusables.actions.workflow-basic-example-and-explanation %}
-For more on managing workflow runs, such as re-running, cancelling, or deleting a workflow run, see "[Managing workflow runs](/actions/managing-workflow-runs)."
+有关管理工作流程运行（如重新运行、取消或删除工作流程运行）的详细信息，请参阅“[管理工作流程运行](/actions/managing-workflow-runs)”。
## 使用入门工作流程
{% data reusables.actions.workflow-template-overview %}
-For more information on using and creating starter workflows, see "[Using starter workflows](/actions/using-workflows/using-starter-workflows)" and "[Creating starter workflows for your organization](/actions/using-workflows/creating-starter-workflows-for-your-organization)."
+有关使用和创建入门工作流程的详细信息，请参阅“[使用入门工作流程](/actions/using-workflows/using-starter-workflows)”和“[为组织创建入门工作流程](/actions/using-workflows/creating-starter-workflows-for-your-organization)”。
## 高级工作流程功能
-This section briefly describes some of the advanced features of {% data variables.product.prodname_actions %} that help you create more complex workflows.
+本节简介了 {% data variables.product.prodname_actions %} 的一些高级功能，可帮助您创建更复杂的工作流程。
### 存储密码
-如果您的工作流程使用敏感数据，例如密码或证书， 您可以将这些信息在 {% data variables.product.prodname_dotcom %} 中保存为 _机密_，然后在工作流中将它们用作环境变量。 This means that you will be able to create and share workflows without having to embed sensitive values directly in the workflow's YAML source.
+如果您的工作流程使用敏感数据，例如密码或证书， 您可以将这些信息在 {% data variables.product.prodname_dotcom %} 中保存为 _机密_，然后在工作流中将它们用作环境变量。 这意味着您将能够创建和共享工作流程，而无需直接在工作流程的 YAML 源中嵌入敏感值。
-This example job demonstrates how to reference an existing secret as an environment variable, and send it as a parameter to an example command.
+此示例作业演示如何将现有机密引用为环境变量，并将其作为参数发送到示例命令。
{% raw %}
```yaml
@@ -81,7 +81,7 @@ jobs:
### 创建依赖的作业
-默认情况下，工作流程中的作业同时并行运行。 If you have a job that must only run after another job has completed, you can use the `needs` keyword to create this dependency. If one of the jobs fails, all dependent jobs are skipped; however, if you need the jobs to continue, you can define this using the `if` conditional statement.
+默认情况下，工作流程中的作业同时并行运行。 如果您有一个作业必须在另一个作业完成后运行，可以使用 `needs` 关键字来创建此依赖项。 如果其中一个作业失败，则跳过所有从属作业；但如果您需要作业继续，可以使用条件语句 `if` 来定义。
在此示例中，`setup`、`build` 和 `test` 作业连续运行，`build` 和 `test` 取决于其前面的作业成功完成：
@@ -107,7 +107,7 @@ jobs:
### 使用构建矩阵
-You can use a build matrix if you want your workflow to run tests across multiple combinations of parameters, such as operating systems, platforms, and languages. 构建矩阵是使用 `strategy` 关键字创建的，它接收构建选项作为数组。 例如，此构建矩阵将使用不同版本的 Node.js 多次运行作业：
+如果您希望工作流程跨参数（如操作系统、平台和语言）的多个组合运行测试，可以使用构建矩阵。 构建矩阵是使用 `strategy` 关键字创建的，它接收构建选项作为数组。 例如，此构建矩阵将使用不同版本的 Node.js 多次运行作业：
```yaml
jobs:
@@ -173,7 +173,7 @@ jobs:
POSTGRES_PORT: 5432
```
-For more information, see "[Using containerized services](/actions/using-containerized-services)."
+更多信息请参阅“[使用容器化服务](/actions/using-containerized-services)”。
### 使用标签路由工作流程
@@ -187,12 +187,12 @@ jobs:
runs-on: [self-hosted, linux, x64, gpu]
```
-工作流程只能在一个所有标签处于 `runs-on` 数组中的运行器上运行。 作业将优先转到具有指定标签的空闲自托管运行器。 {% ifversion fpt or ghec %}If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner.{% endif %}
+工作流程只能在一个所有标签处于 `runs-on` 数组中的运行器上运行。 作业将优先转到具有指定标签的空闲自托管运行器。 {% ifversion fpt or ghec %}如果没有可用且具有指定标签的 {% data variables.product.prodname_dotcom %} 托管运行器存在，作业将转到 {% data variables.product.prodname_dotcom %} 托管的运行器。{% endif %}
-To learn more about self-hosted runner labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+要了解自托管运行器标签的更多信息，请参阅“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)”。
{% ifversion fpt or ghec %}
-To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see "[Supported runners and hardware resources](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)."
+要详细了解 {% data variables.product.prodname_dotcom %} 托管的运行器标签，请参阅[“支持的运行器和硬件资源”](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)。
{% endif %}
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
@@ -202,4 +202,4 @@ To learn more about {% data variables.product.prodname_dotcom %}-hosted runner l
### 使用环境
-You can configure environments with protection rules and secrets to control the execution of jobs in a workflow. 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。
+您可以使用保护规则和机密配置环境，以控制工作流程中作业的执行。 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。
diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index 77caf14c10..514ab779d4 100644
--- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -14,9 +14,14 @@ redirect_from:
- /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
shortTitle: MinIO Gateway for NAS storage
---
-## Prerequisites
-{% data reusables.actions.enterprise-s3-support-warning %}
+{% warning %}
+
+**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_actions %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository.
+
+{% endwarning %}
+
+## Prerequisites
Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
index b507720da4..b2dca564bc 100644
--- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
@@ -48,7 +48,7 @@ Each action is a repository in the `actions` organization, and each action repos
**Notes:**
- When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)."
-- Upgrades to {% data variables.product.product_name %} will not result in the bundled actions being updated.
+- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated.
{% endnote %}
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
index cd2d65eab8..f8318d3f89 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
@@ -1,7 +1,7 @@
---
-title: Exporting audit log activity for your enterprise
-intro: You can export audit and Git events data to a file for offline analysis.
-shortTitle: Export audit logs
+title: 导出企业的审核日志活动
+intro: 可以将审核和 Git 事件数据导出到文件以进行脱机分析。
+shortTitle: 导出审核日志
permissions: Enterprise owners can export the audit log.
miniTocMaxHeadingLevel: 3
versions:
@@ -13,38 +13,38 @@ topics:
- Logging
---
-## About exports of audit log and Git events data
+## 关于审核日志和 Git 事件数据的导出
-You can export the audit log by downloading a JSON or CSV file from your enterprise on {% data variables.product.product_name %}. When you export audit log events, you can query by one or more of these supported qualifiers to filter for specific log events to export. For more information about search qualifiers, see "[Search based on the action performed](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)."
+您可以通过在 {% data variables.product.product_name %} 上从企业下载 JSON 或 CSV 文件来导出审核日志。 导出审核日志事件时，可以按一个或多个受支持的限定符进行查询，以筛选要导出的特定日志事件。 有关搜索限定符的更多信息，请参阅“[根据执行的操作进行搜索](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)”。
-You can export Git events data by downloading a JSON file from your enterprise audit log. Unlike audit log data, you cannot query for specific Git events to filter and export in the audit log user interface.
+可以通过从企业审核日志下载 JSON 文件来导出 Git 事件数据。 与审核日志数据不同，您无法在审核日志用户界面中查询要筛选和导出的特定 Git 事件。
{% data reusables.audit_log.exported-log-keys-and-values %}
-As an alternative to exporting log events, you can use the API to retrieve audit log events, or set up {% data variables.product.product_name %} to stream audit data as events are logged. For more information, see "[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)" and "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+作为导出日志事件的替代方法，您可以使用 API 检索审核日志事件，或设置 {% data variables.product.product_name %} 以在记录事件时流式传输审核数据。 更多信息请参阅“[对企业使用审核日志 API](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)”和“[流式传输企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)”。
-## Exporting audit log data
+## 导出审核日志数据
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.audit-log-tab %}
-1. Optionally, to only export filtered results, search by one or more supported qualifiers or log filters.
-2. Select the {% octicon "download" aria-label="The Download icon" %} **Export** dropdown menu, and choose the file format (JSON or CSV) to export log events in.
+1. （可选）若要仅导出筛选的结果，请按一个或多个受支持的限定符或日志筛选器进行搜索。
+2. 选择 {% octicon "download" aria-label="The Download icon" %} **Export（导出）**下拉菜单，然后选择要将日志事件导出到的文件格式（JSON 或 CSV）。
-## Exporting Git events data
+## 导出 Git 事件数据
-You can also export Git events data by date range.
+您还可以按日期范围导出 Git 事件数据。
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.audit-log-tab %}
-1. Select the {% octicon "download" aria-label="The Download icon" %} **Export Git Events** dropdown menu and choose a date range to export log events for.
+1. 选择 {% octicon "download" aria-label="The Download icon" %} **Export Git Events（导出 Git 事件）**下拉菜单，然后选择要为其导出日志事件的日期范围。
- 
-1. Click {% octicon "file-zip" aria-label="The File-zip icon" %} **Download Results** to download the file.
-1. The data is exported as a compressed JSON file. To extract the JSON data, uncompress the file using an archive utility client or command. 例如：
+ 
+1. 单击 {% octicon "file-zip" aria-label="The File-zip icon" %} **Download Results（下载结果）**以下载文件。
+1. 数据将导出为压缩的 JSON 文件。 要提取 JSON 数据，请使用归档实用程序客户端或命令解压缩文件。 例如：
```
gunzip export-avocado-corp-1642896556.json.gz
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index 706a63f2da..b91352a273 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -99,4 +99,4 @@ topics:
{% data reusables.code-scanning.false-positive-fix-codeql %}
-For more information about dismissing alerts, see {% if delete-code-scanning-alerts %}"[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."{% else %} "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)."{% endif %}
+有关消除警报的详细信息，请参阅 {% if delete-code-scanning-alerts %}“[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)”。{% else %} “[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)”。{% endif %}
diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
index 7f0ecd93fc..cd30442c20 100644
--- a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
@@ -12,6 +12,8 @@ shortTitle: 设置超时
代码空间将在一段时间不活动后停止运行。 您可以指定此超时期限的长度。 更新后的设置将应用于任何新创建的代码空间。
+Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
+
{% warning %}
**警告**：代码空间按分钟计费。 如果您未主动使用代码空间，但代码空间尚未超时，则仍需为代码空间运行的时间付费。 更多信息请参阅“[关于代码空间的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)”。
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
index 35b017f6c8..c682023d96 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -15,6 +15,7 @@ children:
- /reviewing-your-organizations-audit-logs-for-codespaces
- /restricting-access-to-machine-types
- /restricting-the-visibility-of-forwarded-ports
+ - /restricting-the-idle-timeout-period
shortTitle: 管理组织
---
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
index 5cac049ef6..4408f9395b 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -1,9 +1,9 @@
---
title: 限制对计算机类型的访问
-shortTitle: 计算机类型访问
+shortTitle: Restrict machine types
intro: 您可以对用户在组织中创建代码空间时可以选择的计算机类型设置约束。
product: '{% data reusables.gated-features.codespaces %}'
-permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.'
+permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.'
versions:
fpt: '*'
ghec: '*'
@@ -47,33 +47,22 @@ topics:
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. 在边栏的“Code, planning, and automation（代码、规划和自动化）”部分中，选择 **{% octicon "codespaces" aria-label="The codespaces icon" %}{% data variables.product.prodname_codespaces %}**，然后单击 **Policy（策略）**。
-2. 在“Codespace policies（代码空间策略）”页面上，单击 **Create Policy（创建策略）**。
-3. 输入新策略的名称。
-4. 单击 **Add constraint（添加约束）** ，然后选择 **Machine types（计算机类型）**。
+{% data reusables.codespaces.codespaces-org-policies %}
+1. 单击 **Add constraint（添加约束）** ，然后选择 **Machine types（计算机类型）**。
-5. 单击 {% octicon "pencil" aria-label="The edit icon" %} 以编辑约束，然后清除您不希望可用的任何计算机类型的选择。
+1. 单击 {% octicon "pencil" aria-label="The edit icon" %} 以编辑约束，然后清除您不希望可用的任何计算机类型的选择。
-6. 在“Change policy target（更改策略目标）”区域中，单击下拉按钮。
-7. 选择 **All repositories（所有存储库）** 或 **Selected repositories（选定的存储库）**，以确定此策略将应用于哪些存储库。
-8. 如果选择了 **Selected repositories（所选仓库）**：
- 1. 单击 {% octicon "gear" aria-label="The settings icon" %}。
-
- 
-
- 2. 选择要应用此策略的存储库。
- 3. 在存储库列表的底部，单击 **Select repositories（选择存储库）**。
-
- 
-
-9. 单击 **Save（保存）**。
-
+{% data reusables.codespaces.codespaces-policy-targets %}
+1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
+1. After you have finished adding constraints to your policy, click **Save**.
## 编辑策略
+You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
+
1. 显示“Codespace policies（代码空间策略）”页。 更多信息请参阅“[添加策略以限制可用计算机类型](#adding-a-policy-to-limit-the-available-machine-types)”。
1. 单击要编辑的策略的名称。
1. 进行所需的更改，然后单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
new file mode 100644
index 0000000000..0ead7424d6
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
@@ -0,0 +1,79 @@
+---
+title: Restricting the idle timeout period
+shortTitle: Restrict timeout periods
+intro: You can set a maximum timeout period for any codespaces owned by your organization.
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.'
+versions:
+ fpt: '*'
+ ghec: '*'
+type: how_to
+topics:
+ - Codespaces
+---
+
+## 概览
+
+By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage.
+
+The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)."
+
+As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces owned by your organization. This can help you limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for all codespaces owned by your organization, or for the codespaces of specific repositories.
+
+{% note %}
+
+**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization.
+
+{% endnote %}
+
+For more information about pricing for {% data variables.product.prodname_codespaces %} compute usage, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
+
+### Behavior when you set a maximum idle timeout constraint
+
+If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed:
+
+> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy.
+
+### 设置组织范围和存储库特定的策略
+
+When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied.
+
+If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add separate policies that set the maximum timeout to a shorter period for specific repositories in your organization.
+
+## Adding a policy to set a maximum idle timeout period
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.codespaces.codespaces-org-policies %}
+1. Click **Add constraint** and choose **Maximum idle timeout**.
+
+ 
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint.
+
+ 
+
+1. Enter the maximum number of minutes codespaces can remain inactive before they time out, then click **Save**.
+
+ 
+
+{% data reusables.codespaces.codespaces-policy-targets %}
+1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
+1. After you have finished adding constraints to your policy, click **Save**.
+
+The policy will be applied to all new codespaces that are created, and to existing codespaces the next time they are started.
+
+## 编辑策略
+
+You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
+
+1. 显示“Codespace policies（代码空间策略）”页。 For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)."
+1. 单击要编辑的策略的名称。
+1. 进行所需的更改，然后单击 **Save（保存）**。
+
+## 删除策略
+
+1. 显示“Codespace policies（代码空间策略）”页。 For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)."
+1. 单击要删除的策略右侧的删除按钮。
+
+ 
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
index e7f154ad6a..c63ab405cc 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
@@ -1,9 +1,9 @@
---
title: 限制转发端口的可见性
-shortTitle: 限制端口可见性
+shortTitle: Restrict port visibility
intro: 您可以对用户在从组织中的代码空间转发端口时可以选择的可见性选项设置约束。
product: '{% data reusables.gated-features.codespaces %}'
-permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an organization owner.'
+permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.'
versions:
fpt: '*'
ghec: '*'
@@ -40,14 +40,12 @@ topics:
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. 在边栏的“Code, planning, and automation（代码、规划和自动化）”部分中，选择 **{% octicon "codespaces" aria-label="The codespaces icon" %}{% data variables.product.prodname_codespaces %}**，然后单击 **Policies（策略）**。
-1. 在“Codespace policies（代码空间策略）”页面上，单击 **Create Policy（创建策略）**。
-1. 输入新策略的名称。
+{% data reusables.codespaces.codespaces-org-policies %}
1. 单击 **Add constraint（添加约束）** ，然后选择 **Port visibility（端口可见性）**。
-1. 单击 {% octicon "pencil" aria-label="The edit icon" %} 编辑约束。
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint.
@@ -55,22 +53,13 @@ topics:
-1. 在“Change policy target（更改策略目标）”区域中，单击下拉按钮。
-1. 选择 **All repositories（所有存储库）** 或 **Selected repositories（选定的存储库）**，以确定此策略将应用于哪些存储库。
-1. 如果选择了 **Selected repositories（所选仓库）**：
- 1. 单击 {% octicon "gear" aria-label="The settings icon" %}。
-
- 
-
- 2. 选择要应用此策略的存储库。
- 3. 在存储库列表的底部，单击 **Select repositories（选择存储库）**。
-
- 
-
-1. 单击 **Save（保存）**。
-
+{% data reusables.codespaces.codespaces-policy-targets %}
+1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
+1. After you have finished adding constraints to your policy, click **Save**.
## 编辑策略
+You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
+
1. 显示“Codespace policies（代码空间策略）”页。 更多信息请参阅“[添加策略以限制端口可见性选项](#adding-a-policy-to-limit-the-port-visibility-options)”。
1. 单击要编辑的策略的名称。
1. 进行所需的更改，然后单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
index bf36d4e7ae..de1c355e36 100644
--- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
+++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
@@ -123,3 +123,11 @@ shortTitle: 提交和审核更改
{% data reusables.desktop.push-origin %}
+
+6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request. For more information about checks, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)."
+
+ 
+
+ If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to create one. For more information, see "[Creating an issue or pull request](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)."
+
+ 
diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md
new file mode 100644
index 0000000000..bf122e88a8
--- /dev/null
+++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md
@@ -0,0 +1,63 @@
+---
+title: Configuring notifications in GitHub Desktop
+shortTitle: 配置通知
+intro: '{% data variables.product.prodname_desktop %} will keep you up-to-date with notifications about events that occur in your pull request branch.'
+versions:
+ fpt: '*'
+---
+
+## About notifications in {% data variables.product.prodname_desktop %}
+
+{% data variables.product.prodname_desktop %} will show a system notification for events that occur in the currently selected repository. Notifications will be shown when:
+
+- Pull request checks have failed.
+- A pull request review is left with a comment, approval, or requested changes.
+
+Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more detailed information.
+
+## Notifications about pull request check failures
+
+When changes are made to a pull request branch, you will receive a notification if the checks fail.
+
+
+
+Clicking the notification will display a dialog with details about the checks. Once you've reviewed why the checks have failed, you can re-run the checks, or quickly switch to the pull request branch to get started on fixing the errors. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)."
+
+
+## Notifications for pull request reviews
+
+{% data variables.product.prodname_desktop %} will surface a system notification when a teammate has approved, commented, or requested changes in your pull request. See "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" for more information on pull request reviews.
+
+
+
+Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more context for the pull request review comment.
+
+
+## Enabling notifications
+
+If system notifications are disabled for {% data variables.product.prodname_desktop %} you can follow the steps below to enable them.
+
+{% mac %}
+
+1. Click the **Apple** menu, then select **System Preferences**.
+2. Select **Notifications & Focus**.
+3. Select **{% data variables.product.prodname_desktop %}** from the list of applications.
+4. Click **Allow Notifications**.
+
+
+
+For more information about macOS system notifications, see "[Use notifications on your Mac](https://support.apple.com/en-us/HT204079)."
+
+{% endmac %}
+
+{% windows %}
+
+1. Open the **Start** menu, then select **Settings**.
+2. Select **System**, then click **Notifications**.
+3. Find **{% data variables.product.prodname_desktop %}** in the application list and click **On**.
+
+
+
+For more information about Windows system notifications, see "[Change notification settings in Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e)."
+
+{% endwindows %}
diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md
index 31e883ecb2..84155ee5c7 100644
--- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md
+++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md
@@ -8,6 +8,8 @@ versions:
children:
- /creating-an-issue-or-pull-request
- /viewing-a-pull-request-in-github-desktop
+ - /viewing-and-re-running-checks-in-github-desktop
+ - /configuring-notifications-in-github-desktop
- /changing-a-remotes-url-from-github-desktop
shortTitle: 使用远程仓库
---
diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
index 8df68191a4..cd6f7bb271 100644
--- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
+++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
@@ -15,6 +15,8 @@ versions:
在 {% data variables.product.prodname_desktop %} 中查看拉取请求时，您可以看到贡献者的提交历史记录。 您还可以查看修改、添加或删除了提交的文件。 从 {% data variables.product.prodname_desktop %} 可以在首选文本编辑器中打开仓库以查看任何更改或进行其他更改。 在审查拉取请求中的更改后，您可以对 {% data variables.product.prodname_dotcom %} 提供反馈。 更多信息请参阅“[关于拉取请求审查](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)”。
+If checks have been enabled in your repository, {% data variables.product.prodname_desktop %} will show the status of the checks on the pull request and allow you to re-run checks. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)."
+
## 在 {% data variables.product.prodname_desktop %} 中查看拉取请求
{% data reusables.desktop.current-branch-menu %}
{% data reusables.desktop.click-pull-requests %}
diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md
new file mode 100644
index 0000000000..d022a660b2
--- /dev/null
+++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md
@@ -0,0 +1,25 @@
+---
+title: Viewing and re-running checks in GitHub Desktop
+shortTitle: Viewing and re-running checks
+intro: 'You can view the status of checks and re-run them in {% data variables.product.prodname_desktop %}.'
+versions:
+ fpt: '*'
+---
+
+## About checks in {% data variables.product.prodname_desktop %}
+
+{% data variables.product.prodname_desktop %} displays the status of checks that have run in your pull request branches. The checks badge next to the branch name will display the *pending, passing,* or *failing* state of the checks. You can also re-run all, failed, or individual checks when viewing the status of the checks in {% data variables.product.prodname_desktop %}. For more information on setting up checks in your repository, see "[About status checks](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
+
+{% data variables.product.prodname_desktop %} will also show a system notification when checks fail. For more information on enabling notifications, see "[Configuring notifications in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop)."
+
+## Viewing and re-running checks
+
+{% data reusables.desktop.current-branch-menu %}
+{% data reusables.desktop.click-pull-requests %}
+ 
+{% data reusables.desktop.choose-pr-from-list %}
+ 
+4. Click on the pull request number, to the right of the pull request branch name. 
+5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**. 
+6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check. 
+7. You will see a confirmation dialog with the summary of the checks that will be re-run. Click **Re-run Checks** to confirm that you want to perform the re-run. 
diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
index bff87eeeb2..b6380c31a4 100644
--- a/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -67,9 +67,9 @@ X-Accepted-OAuth-Scopes: user
| `user:follow` | 授予关注或取消关注其他用户的权限。 |
| **`delete_repo`** | 授予删除可管理仓库的权限。 |
| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 |
-| `read:discussion` | 授予对团队讨论的读取权限。{% ifversion fpt or ghae or ghec %}
+| `read:discussion` | Allows read access for team discussions. |
| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 |
-| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 |
+| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
| **`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。{% endif %}
| **`admin:gpg_key`** | 全面管理 GPG 密钥。 |
| `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 |
diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index 5be52770de..8d2c487aa3 100644
--- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
@@ -811,8 +811,6 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如
{% endif %}
-{% ifversion fpt or ghae or ghec %}
-
## package
与 {% data variables.product.prodname_registry %} 有关的活动。 {% data reusables.webhooks.action_type_desc %}更多信息请参阅“[使用 {% data variables.product.prodname_registry %} 管理包](/github/managing-packages-with-github-packages)”以详细了解 {% data variables.product.prodname_registry %}。
@@ -832,7 +830,6 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如
### Web 挂钩有效负载示例
{{ webhookPayloadsForCurrentVersion.package.published }}
-{% endif %}
## page_build
diff --git a/translations/zh-CN/content/get-started/quickstart/be-social.md b/translations/zh-CN/content/get-started/quickstart/be-social.md
index a2d74c8ca8..496c283694 100644
--- a/translations/zh-CN/content/get-started/quickstart/be-social.md
+++ b/translations/zh-CN/content/get-started/quickstart/be-social.md
@@ -5,7 +5,7 @@ redirect_from:
- /articles/be-social
- /github/getting-started-with-github/be-social
- /github/getting-started-with-github/quickstart/be-social
-intro: '您可以在 {% data variables.product.prodname_dotcom %} 上与人员、仓库及组织进行互动。 See what others are working on and who they are connecting with from your personal dashboard.'
+intro: '您可以在 {% data variables.product.prodname_dotcom %} 上与人员、仓库及组织进行互动。 从您的个人仪表板查看其他人正在做什么，在跟谁联系。'
permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
versions:
fpt: '*'
@@ -24,17 +24,17 @@ topics:
## 关注他人
-When you follow someone on {% data variables.product.prodname_dotcom %}, you will get notifications on your personal dashboard about their public activity. If someone you follow creates a new repository, stars a repository, or follows another user, the activity will display in your dashboard.
+在 {% data variables.product.prodname_dotcom %} 上关注某人后，您将会在您的个人仪表板中收到有关其公共活动的通知。 如果您关注的某人创建了一个新存储库、为存储库添加星标或关注其他用户，则该活动将显示在您的仪表板中。
在某人的个人资料页面上单击 **Follow（关注）**可关注他们。
-For more information, see "[Following people](/get-started/exploring-projects-on-github/following-people)."
+更多信息请参阅“[关注人员](/get-started/exploring-projects-on-github/following-people)”。
## 关注仓库
-You can subscribe to a repository to watch it and receive notifications for activity in it. When the owner updates the repository, you will see the changes in your personal dashboard. For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)."
+您可以订阅存储库以关注它并接收其中活动的通知。 当所有者更新仓库时，您将在个人仪表板中看到其更改。 更多信息请参阅“[查看订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)”。
在仓库顶部单击 **Watch（关注）**可关注它。
@@ -46,28 +46,28 @@ You can subscribe to a repository to watch it and receive notifications for acti
## {% data variables.product.product_name %} 上的通信
-{% data variables.product.product_name %} provides built-in collaborative communication tools, allowing you to interact closely with your community when building great software. For example, you can contribute to another user's project by creating a pull request, or use issues to track bugs or suggest ideas in a repository. You can also brainstorm new ideas with your team with discussions.
+{% data variables.product.product_name %} 提供内置的协作通信工具，让您在构建出色的软件时与社区密切互动。 例如，您可以通过创建拉取请求来为其他用户的项目做出贡献，或者使用议题来跟踪 Bug 或在存储库中提出想法。 您还可以通过讨论与您的团队一起集思广益。
-For an overview of these tools, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
+有关这些工具的概述，请参阅“[{% data variables.product.prodname_dotcom %} 通信快速入门](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)”。
## 参与组织
组织是共享帐户，其中业务和开源项目可一次协助处理多个项目。 所有者和管理员可建立具有特殊权限的团队、拥有公共组织资料以及跟踪组织内的活动。 更多信息请参阅“[关于组织](/articles/about-organizations/)”。
-From your dashboard, click the drop down menu of your username on the left side of your dashboard. Here, you can view organizations that you are a part of and easily switch between them.
+在仪表板中，单击仪表板左侧用户名的下拉菜单。 在这里，您可以查看您所属的组织，并在它们之间轻松切换。
### 在 {% data variables.product.prodname_dotcom %} 上探索其他项目
-You can discover new and interesting projects on {% data variables.product.prodname_dotcom %}'s Explore page. You can star interesting projects to make them easy to find again later. Visit your stars page to see all your starred projects. For more information about stars, see "[Saving repositories with stars](/get-started/exploring-projects-on-github/saving-repositories-with-stars)."
+您可以在 {% data variables.product.prodname_dotcom %} 的 Explore（探索）页面上发现新的和有趣的项目。 您可以为有趣的项目加注星标，以便以后再次轻松找到它们。 访问您的星标页面，查看所有已加星标的项目。 有关星标的更多信息，请参阅“[使用星标保存仓库](/get-started/exploring-projects-on-github/saving-repositories-with-stars)”。
-Your dashboard feed displays projects based on your interests including repositories you star, people you follow, and your contributions to public repositories. From your dashboard, you can see trending projects, view topics, and check out collections.
+您的仪表板源会根据您的兴趣显示项目，包括您关注的存储库、您关注的人员以及您对公共存储库的贡献。 在仪表板中，您可以查看热门项目、查看主题和查看集合。
-To explore more projects, see "{% data variables.explore.explore_github %}".
+要探索更多项目，请参阅“{% data variables.explore.explore_github %}”。
## 后续步骤
-You are now connected to the {% data variables.product.product_name %} community. There are other ways to interact and build within {% data variables.product.product_name %}.
+您现在已连接到 {% data variables.product.product_name %} 社区。 还有其他方法可以在 {% data variables.product.product_name %} 中进行交互和构建。
* {% data reusables.getting-started.set-up-git %}
diff --git a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md
index 5b63548dc8..36c11ca399 100644
--- a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md
+++ b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md
@@ -5,7 +5,7 @@ redirect_from:
- /articles/create-a-repo
- /github/getting-started-with-github/create-a-repo
- /github/getting-started-with-github/quickstart/create-a-repo
-intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you will need to create a repository for it to live in.'
+intro: '要将项目放在 {% data variables.product.prodname_dotcom %} 上，您需要创建一个仓库来存放它。'
versions:
fpt: '*'
ghes: '*'
@@ -22,7 +22,7 @@ topics:
{% ifversion fpt or ghec %}
-您可以在 {% data variables.product.prodname_dotcom %} 仓库中存储各种项目，包括开源项目。 With open source projects, you can share code to make better, more reliable software. 您可以使用仓库与他人协作并跟踪您的工作。 更多信息请参阅“[关于仓库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)”。 To learn more about open source projects, visit [OpenSource.org](http://opensource.org/about).
+您可以在 {% data variables.product.prodname_dotcom %} 仓库中存储各种项目，包括开源项目。 通过开源项目，您可以共享代码以开发更好、更可靠的软件。 您可以使用仓库与他人协作并跟踪您的工作。 更多信息请参阅“[关于仓库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)”。 要了解有关开源项目的更多信息，请访问 [OpenSource.org](http://opensource.org/about)。
{% elsif ghes or ghae %}
@@ -78,7 +78,7 @@ A *[提交](/articles/github-glossary#commit)*就像是项目中所有文件在
2. 在文件内容的上方，单击 {% octicon "pencil" aria-label="The edit icon" %}。
3. 在 **Edit file（编辑文件）**选项卡上，键入一些关于您自己的信息。 
{% data reusables.files.preview_change %}
-5. 查看您对文件所做的更改。 You will see the new content in green. 
+5. 查看您对文件所做的更改。 您将看到绿色的新内容。 
{% data reusables.files.write_commit_message %}
{% data reusables.files.choose_commit_branch %}
{% data reusables.files.propose_file_change %}
diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
index 2985fa71bd..ef0e6f3013 100644
--- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
@@ -22,11 +22,11 @@ topics:
## 关于复刻
-Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. 您可以复刻仓库以创建仓库的副本，并在不影响上游仓库的情况下进行更改。 更多信息请参阅“[使用复刻](/github/collaborating-with-issues-and-pull-requests/working-with-forks)”。
+最常见的是，复刻用于对其他人的项目提出您没有写入权限的项目的更改，或者使用其他人的项目作为您自己想法的起点。 您可以复刻仓库以创建仓库的副本，并在不影响上游仓库的情况下进行更改。 更多信息请参阅“[使用复刻](/github/collaborating-with-issues-and-pull-requests/working-with-forks)”。
### 对其他人的项目提出更改
-例如，可以使用复刻提出与修复 Bug 相关的更改。 Rather than logging an issue for a bug you have found, you can:
+例如，可以使用复刻提出与修复 Bug 相关的更改。 无需为您发现的漏洞创建议题，您可以：
- 复刻仓库
- 进行修复
@@ -48,7 +48,7 @@ Most commonly, forks are used to either propose changes to someone else's projec
## 基本要求
-If you have not yet, you should first [set up Git](/articles/set-up-git). 不要忘记[从 Git 设置向 {% data variables.product.product_location %} 验证](/articles/set-up-git#next-steps-authenticating-with-github-from-git)。
+如果尚未[设置 Git](/articles/set-up-git)，您应该先设置它。 不要忘记[从 Git 设置向 {% data variables.product.product_location %} 验证](/articles/set-up-git#next-steps-authenticating-with-github-from-git)。
## 复刻仓库
@@ -84,7 +84,7 @@ gh repo fork repository --org "octo-org"
## 克隆复刻的仓库
-Right now, you have a fork of the Spoon-Knife repository, but you do not have the files in that repository locally on your computer.
+现在，您有了 Spoon-Knife 仓库的复刻，但您的计算机本地还没有该仓库中的文件。
{% webui %}
@@ -145,7 +145,7 @@ gh repo fork repository --clone=true
- 要列出当前目录中的文件和文件夹，请键入 `ls`。
- 要进入列出的某个目录，请键入 `cd your_listed_directory`。
- 要回到上一个目录，请键入 `cd ..`。
-5. 键入 `git remote -v`，然后按 **Enter** 键。 You will see the current configured remote repository for your fork.
+5. 键入 `git remote -v`，然后按 **Enter** 键。 您将看到当前为复刻配置的远程仓库。
```shell
$ git remote -v
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
@@ -157,7 +157,7 @@ gh repo fork repository --clone=true
$ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
```
-7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. 您应该看到复刻的 URL 为 `origin`，原始仓库的 URL 为 `upstream`。
+7. 要验证为复刻指定的新上游仓库，请再次键入 `git remote -v`。 您应该看到复刻的 URL 为 `origin`，原始仓库的 URL 为 `upstream`。
```shell
$ git remote -v
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
@@ -188,7 +188,7 @@ gh repo fork repository --remote-name "main-remote-repo"
{% endcli %}
-### Editing a fork
+### 编辑复刻
您可以对复刻进行任何更改，包括：
@@ -206,10 +206,10 @@ gh repo fork repository --remote-name "main-remote-repo"
您现在已经复刻了仓库、练习了克隆复刻并配置了上游仓库。
-* For more information about cloning the fork and syncing the changes in a forked repository from your computer, see "[Set up Git](/articles/set-up-git)."
+* 有关克隆复刻和从计算机同步复刻仓库更改的更多信息，请参阅“[设置 Git](/articles/set-up-git)”。
* 您也可以创建一个新的仓库，以将所有项目放在 {% data variables.product.prodname_dotcom %} 上并共享代码。 {% data reusables.getting-started.create-a-repository %}"
-* {% data variables.product.product_name %} 中的每个仓库均归个人或组织所有。 You can interact with users, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. {% data reusables.getting-started.being-social %}
+* {% data variables.product.product_name %} 中的每个仓库均归个人或组织所有。 您可以在 {% data variables.product.product_name %} 上连接和关注用户、仓库和组织以与之进行交互。 {% data reusables.getting-started.being-social %}
* {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/zh-CN/content/get-started/quickstart/github-glossary.md b/translations/zh-CN/content/get-started/quickstart/github-glossary.md
index 92b0c4905f..ce157b72ae 100644
--- a/translations/zh-CN/content/get-started/quickstart/github-glossary.md
+++ b/translations/zh-CN/content/get-started/quickstart/github-glossary.md
@@ -23,5 +23,5 @@ versions:
## 延伸阅读
- [官方 Git 术语表](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html)
-- [Git documentation](https://git-scm.com/doc)
-- [Git command list](https://git-scm.com/docs)
+- [Git 文档](https://git-scm.com/doc)
+- [Git 命令列表](https://git-scm.com/docs)
diff --git a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
index 1ffeed2655..f4716e5ca3 100644
--- a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
+++ b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -23,7 +23,7 @@ shortTitle: Introduction
## About {% data variables.product.prodname_registry %}
-{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion not ghae %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}.
+{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion fpt or ghec %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}.
You can integrate {% data variables.product.prodname_registry %} with {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
diff --git a/translations/zh-CN/content/packages/quickstart.md b/translations/zh-CN/content/packages/quickstart.md
index f0cf7373f2..74558266b7 100644
--- a/translations/zh-CN/content/packages/quickstart.md
+++ b/translations/zh-CN/content/packages/quickstart.md
@@ -21,7 +21,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)."
2. Clone the repository to your local machine.
```shell
- $ git clone https://{% ifversion ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
+ $ 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!"
@@ -49,7 +49,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
$ 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 ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}.
+7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghes or ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}.
```yaml{:copy}
name: Node.js Package
@@ -79,7 +79,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
- uses: {% data reusables.actions.action-setup-node %}
with:
node-version: 12
- registry-url: {% ifversion ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %}
+ registry-url: {% ifversion ghes or ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %}
- run: npm ci
- run: npm publish
env:
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml
index 542ec1716f..9e2abde51d 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml
@@ -47,7 +47,6 @@ sections:
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
- '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
- 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 appliance from backup taken on a different host.
- |
When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11]
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml
index d548034cac..0f28e72b91 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml
@@ -32,7 +32,6 @@ sections:
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
- '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
- 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 appliance from backup taken on a different host.
- |
When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11]
diff --git a/translations/zh-CN/data/reusables/actions/supported-github-runners.md b/translations/zh-CN/data/reusables/actions/supported-github-runners.md
index 437f235fcb..6382a882d0 100644
--- a/translations/zh-CN/data/reusables/actions/supported-github-runners.md
+++ b/translations/zh-CN/data/reusables/actions/supported-github-runners.md
@@ -50,6 +50,17 @@ Ubuntu 18.04
|