New translation batch for cn (#26441)

* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn * run script/i18n/reset-known-broken-translation-files.js * Check in cn CSV report
2022-03-22 17:28:12 -07:00 · 2022-03-22 17:28:12 -07:00 · 5ce083f66b
--- a/translations/log/cn-resets.csv
+++ b/translations/log/cn-resets.csv
@ -134,6 +134,7 @@ translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.m
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md,broken liquid tags
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
+translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,broken liquid tags
 translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,broken liquid tags
 translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,broken liquid tags
@ -186,6 +187,7 @@ translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-
 translations/zh-CN/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md,broken liquid tags
 translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,broken liquid tags
 translations/zh-CN/content/get-started/using-git/dealing-with-non-fast-forward-errors.md,broken liquid tags
+translations/zh-CN/content/get-started/using-github/github-command-palette.md,broken liquid tags
 translations/zh-CN/content/get-started/using-github/github-mobile.md,broken liquid tags
 translations/zh-CN/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags
 translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,broken liquid tags
@ -272,7 +274,7 @@ translations/zh-CN/data/reusables/rest-reference/activity/events.md,broken liqui
 translations/zh-CN/data/reusables/rest-reference/apps/marketplace.md,broken liquid tags
 translations/zh-CN/data/reusables/rest-reference/packages/packages.md,broken liquid tags
 translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,Listed in localization-support#489
-translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error
+translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
 translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags
 translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
 translations/zh-CN/data/reusables/sponsors/feedback.md,broken liquid tags
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
@ -40,9 +40,23 @@ You can also find a list of your recently visited repositories, teams, and proje

 ## Staying updated with activity from the community

-In the "All activity" section of your news feed, you can view updates from repositories you're subscribed to and people you follow. The "All activity" section shows updates from repositories you watch or have starred, and from users you follow.
+{% if for-you-feed %}
+The main section of your dashboard has two activity feeds:
+
+- Following: Activity by people you follow and from repositories you watch.
+- For you: Activity and recommendations based on your {% data variables.product.product_name %} network.
+
+### Following feed
+
+This feed shows activity from repositories and users you have shown a direct interest in, by following a user or watching a repository. For example, you'll see updates when a user you follow:
+
+{% else %}
+In the "All activity" section of your news feed, you can view updates from repositories you watch and users you follow.

 You'll see updates in your news feed when a user you follow:
+{% endif %}
+
+
 - Stars a repository.
 - Follows another user.{% ifversion fpt or ghes or ghec %}
 - Creates a public repository.{% endif %}
@ -51,7 +65,26 @@ You'll see updates in your news feed when a user you follow:
 - Forks a public repository.{% endif %}
 - Publishes a new release.

-For more information about starring repositories and following people, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)" and "[Following people](/articles/following-people)."
+For more information about following people and watching repositories, see "[Following people](/get-started/exploring-projects-on-github/following-people)" and "[Be social](/get-started/quickstart/be-social)."
+
+{% if for-you-feed %}
+### For you feed
+
+{% note %}
+
+**Note:** This new tab is currently in public beta and subject to change. 
+
+{% endnote %}
+
+This feed shows activity and recommendations based on your network on {% data variables.product.product_name %}. It's designed to provide updates that inspire you, keep you up-to-date, and help you find new communities you want to participate in. Your network includes:
+
+- Repositories you have starred
+- Repositories you've contributed to
+- Users you follow or sponsor
+- Users you've collaborated with
+- Organizations you follow
+
+{% endif %}

 ## Exploring recommended repositories

--- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@ -14,7 +14,6 @@ shortTitle: 管理对运行器的访问

 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
-{% data reusables.actions.restrict-runner-workflow-beta %}

 ## 关于自托管运行器组

--- a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md
@ -258,6 +258,7 @@ Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```

 {% endpowershell %}
+
 ## 对日志行分组

 在日志中创建一个可扩展的组。 要创建组，请使用 `group` 命令并指定 `title`。 打印到 `group` 与 `endgroup` 命令之间日志的任何内容都会嵌套在日志中可扩展的条目内。
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
@ -17,11 +17,11 @@ topics:

 如果配置的是主机名，而不是硬编码 IP 地址，您将能够更改运行 {% data variables.product.product_location %} 的物理硬件，而不会影响用户或客户端软件。

-{% data variables.enterprise.management_console %} 中的主机名设置应设置为合适的完全限定域名 (FQDN)，此域名可在互联网上或您的内部网络内解析。 For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}.
+{% data variables.enterprise.management_console %} 中的主机名设置应设置为合适的完全限定域名 (FQDN)，此域名可在互联网上或您的内部网络内解析。 例如，您的主机名设置可能是 `github.companyname.com。` Web 和 API 请求将自动重定向到 {% data variables.enterprise.management_console %} 中配置的主机名。

-After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。
+配置主机名后，可以启用子域隔离以进一步提高 {% data variables.product.product_location %} 的安全性。 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。

-For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2).
+有关支持的主机名类型的详细信息，请参阅 [HTTP RFC 2.1 节](https://tools.ietf.org/html/rfc1123#section-2)。

 {% data reusables.enterprise_installation.changing-hostname-not-supported %}

@ -33,4 +33,4 @@ For more information on the supported hostname types, see [Section 2.1 of the HT
 {% data reusables.enterprise_management_console.test-domain-settings-failure %}
 {% data reusables.enterprise_management_console.save-settings %}

-To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。
+为了帮助缓解各种跨站点脚本漏洞，我们建议您在配置主机名后为 {% data variables.product.product_location %} 启用子域隔离。 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md
@ -19,9 +19,9 @@ shortTitle: 启动故障转移到设备

 {% data reusables.enterprise_installation.promoting-a-replica %}

-1. If the primary appliance is available, to allow replication to finish before you switch appliances, on the primary appliance, put the primary appliance into maintenance mode.
+1. 如果主设备可用，要在切换设备之前允许复制完成，请在主设备上将主设备置于维护模式。

-    - Put the appliance into maintenance mode.
+    - 将设备置于维护模式。

       - 要使用 Management Console，请参阅“[启用和排定维护模式](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)”。

@ -44,7 +44,7 @@ shortTitle: 启动故障转移到设备
      $ ghe-repl-status -vv
      ```

-4. On the replica appliance, to stop replication and promote the replica appliance to primary status, use the `ghe-repl-promote` command. 此操作还会自动将主节点（若可到达）置于维护模式。
+4. 在副本设备上，要停止复制并将副本设备提升为主状态，请使用 `ghe-repl-promote` 命令。 此操作还会自动将主节点（若可到达）置于维护模式。
  ```shell
  $ ghe-repl-promote
  ```
--- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md
+++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md
@ -25,7 +25,7 @@ topics:

 在迁移中，一切都围绕仓库进行。 与仓库关联的大多数数据都可以迁移。 例如，组织内的仓库将迁移仓库*和*组织，以及与该仓库关联的任何用户、团队、问题和拉取请求。

-下表中的项可随仓库一起迁移。 Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets.
+下表中的项可随仓库一起迁移。 迁移数据列表中未显示的任何项都无法迁移，包括 {% data variables.large_files.product_name_short %} 资产。

 {% data reusables.enterprise_migrations.fork-persistence %}

--- a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
+++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
@ -33,7 +33,7 @@ $ ssh -T -p 443 git@ssh.github.com

 如果您能在端口 443 上通过 SSH 连接到 `git@ssh.{% data variables.command_line.backticks %}`，则可以覆盖您的 SSH 设置以强制与 {% data variables.product.product_location %} 的任何连接均通过该服务器和端口运行。

-To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
+要在 SSH 配置文件中设置此设置，请在 `~/.ssh/config` 编辑该文件，并添加以下部分：

 ```
 Host {% data variables.command_line.codeblock %}
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@ -256,6 +256,12 @@ updates:

 支持的选项

+{% note %}
+
+**Note:** The `prefix` and the `prefix-development` options have a 15 character limit.
+
+{% endnote %}
+
 - `prefix` 指定所有提交消息的前缀。
 - `prefix-development` 为更新“开发”依赖项组中依赖项的所有提交消息指定单独的前缀。 指定此选项的值时，`prefix` 仅用于更新“生产”依赖项组中的依赖项。 支持的包管理器：`bundler`、`composer`、`mix`、`maven`、`npm` 和 `pip`。
 - `include: "scope"` 指定任何前缀后接提交中更新的依赖项列表。
@ -309,7 +315,7 @@ updates:

 您可以搜索仓库中是否有 `"@dependabot ignore" in:comments`，以检查仓库是否存储了 `ignore` 首选项。 如果您希望取消忽略以这种方式忽略的依赖项，请重新打开拉取请求。

-For more information about the `@dependabot ignore` commands, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
+有关 `@dependabot ignore` 命令的更多信息，请参阅“[管理依赖关系更新的拉取请求](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)”。

 #### 指定要忽略的依赖项和版本

--- a/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md
@ -15,9 +15,9 @@ redirect_from:
  - /codespaces/codespaces-reference/using-copilot-in-codespaces
 ---

-## 使用 {% data variables.product.prodname_copilot %}
+## Using {% data variables.product.prodname_copilot %}

 [{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot).

-To include {% data variables.product.prodname_copilot_short %}, or other extensions, in all of your codespaces, enable Settings Sync. 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)”。 Additionally, to include {% data variables.product.prodname_copilot_short %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)."
+To include {% data variables.product.prodname_copilot_short %}, or other extensions, in all of your codespaces, enable Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." Additionally, to include {% data variables.product.prodname_copilot_short %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)."

--- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
@ -79,7 +79,7 @@ shortTitle: 配置

 以下是 *config.yml* 文件的一个例子：

-```shell
+```shell{:copy}
 blank_issues_enabled: false
 contact_links:
  - name: {% data variables.product.prodname_gcf %}
--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
@ -25,7 +25,7 @@ shortTitle: 为开源做贡献

 如果您一直活跃在 {% data variables.product.product_location %} 上，可以根据您过去的参与、标星以及在 [Explore](https://github.com/explore) 中的其他活动，为您的项目找到个性化的建议和合适的第一个议题。 您还可以注册 Explore 通讯以根据您的兴趣接收相关电子邮件，了解参与 {% data variables.product.product_name %} 的机会。 要注册，请参阅 [Explore 电子邮件通讯](https://github.com/explore/subscribe)。

-在个人仪表板的“All activity（所有活动）”部分中，了解您关注的仓库和人员的最新活动。 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
+Keep up with recent activity from repositories you watch and people{% if for-you-feed %}, and organizations{% endif %} you follow with your personal dashboard. 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。

 {% data reusables.support.ask-and-answer-forum %}

--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md
@ -0,0 +1,50 @@
+---
+title: Following organizations
+intro: 'You can follow organizations on {% data variables.product.product_name %} to receive notifications about their activity.'
+versions:
+  feature: for-you-feed
+topics:
+  - Profile
+---
+
+{% note %}
+
+**Note:** The ability to follow organizations is currently in public beta and subject to change.
+
+{% endnote %}
+
+## 关于 {% data variables.product.product_name %} 上的关注者
+
+When you follow organizations, you'll see their public activity on your personal dashboard. 更多信息请参阅“[关于个人仪表板](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)”。
+
+You can unfollow an organization if you do not wish to see their public activity on {% data variables.product.product_name %}.
+
+## Following an organization on {% data variables.product.product_name %}
+
+1. Go to the organization page you want to follow
+2. Click **Follow** in the top-right corner of the header
+
+  ![Screenshot of the organization header, with the follow button highlighted](/assets/images/help/profile/organization-profile-following.png)
+
+## Unfollowing an organization on {% data variables.product.product_name %}
+
+1. Go to the organization page you want to unfollow
+2. Click **Unfollow** in the top-right corner of the header.
+
+  ![Screenshot of the organization header, with the unfollow button highlighted](/assets/images/help/profile/organization-profile-unfollowing.png)
+
+## Viewing people and organizations a user follows on {% data variables.product.product_name %}
+
+1. 单击用户图像以显示该用户的配置文件。
+
+  ![用户图像](/assets/images/help/profile/user-profile-image.png)
+
+2. 在其个人资料图片下点击**关注**。
+
+  ![用户关注](/assets/images/help/profile/user-profile-following.png)
+
+{% ifversion fpt or ghec %}
+## 延伸阅读
+
+- "[Following people](/get-started/exploring-projects-on-github/following-people)"
+{% endif %}
--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md
@ -17,7 +17,7 @@ topics:

 ## 关于 {% data variables.product.product_name %} 上的关注者

-关注他人后，您将在消息馈送的活动视图中看到其公开活动。{% ifversion fpt or ghec %}如果您关注的人标注了某个公共仓库，{% data variables.product.product_name %} 可能会在您的消息馈送发现视图中向您推荐该仓库。{% endif %}
+When you follow people, you'll see their public activity on your personal dashboard.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you.{% endif %} For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)."

 如果您不希望在 {% data variables.product.product_name %} 上看到某人的公开活动，则可以取消关注他们。

--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/index.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/index.md
@ -18,6 +18,7 @@ children:
  - /finding-ways-to-contribute-to-open-source-on-github
  - /saving-repositories-with-stars
  - /following-people
+  - /following-organizations
 shortTitle: 探索项目
 ---

--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
@ -26,7 +26,7 @@ shortTitle: 保存有星标的仓库
 标星操作便于以后再次找到仓库或主题。 您可以到 {% data variables.explore.your_stars_page %} 查看已经加星标的所有仓库和主题。

 {% ifversion fpt or ghec %}
-您可以对仓库和主题加星标以在 {% data variables.product.product_name %} 上发现类似的项目。 对仓库或主题加星标时，{% data variables.product.product_name %} 可能会在消息馈送的发现视图中推荐相关内容。 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。
+您可以对仓库和主题加星标以在 {% data variables.product.product_name %} 上发现类似的项目。 When you star repositories or topics, {% data variables.product.product_name %} may recommend related content on your personal dashboard. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" and "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)."
 {% endif %}

 对仓库加星标也可表示赞赏仓库维护员的工作。 许多 {% data variables.product.prodname_dotcom %} 的仓库评级取决于仓库拥有的星标数。 此外，[Explore](https://github.com/explore) 也会根据星标数显示最受欢迎的仓库。
--- a/translations/zh-CN/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md
+++ b/translations/zh-CN/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md
@ -16,14 +16,14 @@ shortTitle: GitHub 对您的数据的使用

 ## 关于 {% data variables.product.product_name %} 使用您的数据

-{% data variables.product.product_name %} 汇总元数据并剖析内容模式，以在产品中提交一般化的见解。 它使用公共仓库中的数据，当仓库所有者选择与 {% data variables.product.product_name %} 共享数据时还会使用私有仓库中的元数据并汇总数据。 如果选择使用私有仓库的数据，它会对特定私有仓库执行只读分析。
+{% data variables.product.product_name %} 汇总元数据并剖析内容模式，以在产品中提交一般化的见解。 It uses data from public repositories, and also uses metadata and aggregate data from private repositories when a repository's owner has chosen to share the data with {% data variables.product.product_name %} by enabling the dependency graph. If you enable the dependency graph for a private repository, then {% data variables.product.product_name %} will perform read-only analysis of that specific private repository.
+
+If you enable data use for a private repository, we will continue to treat your private data, source code, or trade secrets as confidential and private consistent with our [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service). 我们了解的信息只来自汇总的数据。 更多信息请参阅“[管理私有仓库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)”。

 {% data reusables.repositories.about-github-archive-program %} 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上存档内容](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)”。

 {% data reusables.user-settings.export-data %} 更多信息请参阅“[请求个人帐户数据的存档](/articles/requesting-an-archive-of-your-personal-account-s-data)”。

-如果您选择使用私人仓库的数据，我们将继续按照[服务条款](/free-pro-team@latest/github/site-policy/github-terms-of-service)，将您的私人数据、源代码或商业秘密视为机密和私密。 我们了解的信息只来自汇总的数据。 更多信息请参阅“[管理私有仓库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)”。
-
 我们会在 [{% data variables.product.prodname_dotcom %} 博客](https://github.com/blog)中宣布使用元数据或汇总数据的重要新功能。

 ## 数据如何改进安全建议
--- a/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
+++ b/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
@ -16,9 +16,22 @@ shortTitle: Manage data use for private repo

 ## About data use for your private repository

+
+You can control data use for your private repository with the security and analysis features. 
+
+- Enable the dependency graph to allow read-only data analysis on your repository. 
+- Disable the dependency graph to block read-only data analysis of your repository. 
+
 When you enable data use for your private repository, you'll be able to access the dependency graph, where you can track your repository's dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."

-## Enabling or disabling data use features
+
+{% note %}
+
+**Note:** If you disable the dependency graph, {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} are also disabled. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." 
+
+{% endnote %}
+
+## Enabling or disabling data use through security and analysis features

 {% data reusables.security.security-and-analysis-features-enable-read-only %}

--- 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,7 +22,7 @@ topics:

 ## 关于复刻

-Most commonly, forks are used to either propose changes to someone else's project to which you don't 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)”。

 ### 对其他人的项目提出更改

--- a/translations/zh-CN/content/get-started/using-github/github-command-palette.md
+++ b/translations/zh-CN/content/get-started/using-github/github-command-palette.md
@ -8,7 +8,7 @@ shortTitle: GitHub Command Palette

 {% data reusables.command-palette.beta-note %}

-## 关于 {% data variables.product.prodname_command_palette %}
+## About the {% data variables.product.prodname_command_palette %}

 You can navigate, search, and run commands on {% data variables.product.product_name %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.product_name %}, which saves you time and keeps your hands on the keyboard.

@ -38,16 +38,16 @@ When you open the command palette, it shows your location at the top left and us

 {% note %}

-**注意：**
+**Notes:**
 - If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).
- If you are working on a project (beta), a project-specific command palette is displayed instead. 更多信息请参阅“[自定义项目（测试版）视图](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)”。
+- If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."

 {% endnote %}

 ### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts


-The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode.
+The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode. 

 ![Command palette keyboard shortcut settings](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png)
 ## Navigating with the {% data variables.product.prodname_command_palette %}
@ -122,7 +122,7 @@ When the command palette is active, you can use one of the following keyboard sh
 - Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
 - Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)

-If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette.
+If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette.  

 ## {% data variables.product.prodname_command_palette %} reference

@ -130,100 +130,100 @@ If you have customized the command palette keyboard shortcuts in the Accessibili

 These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode.

-| Keystroke                                                               | Function                                                                                                                                                                                                                                       |
-|:----------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>></kbd>                                                            | Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)."                                                        |
-| <kbd>#</kbd>                                                            | Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                             |
-| <kbd>@</kbd>                                                            | Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                       |
-| <kbd>/</kbd>                                                            | Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
-| <kbd>!</kbd>                                                            | Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                                                |
-| <kbd>Ctrl</kbd>+<kbd>C</kbd> or <kbd>Command</kbd>+<kbd>C</kbd>         | Copy the search or navigation URL for the highlighted result to the clipboard.                                                                                                                                                                 |
-| <kbd>Enter</kbd>                                                        | Jump to the highlighted result or run the highlighted command.                                                                                                                                                                                 |
-| <kbd>Ctrl</kbd>+<kbd>Enter</kbd> or <kbd>Command</kbd>+<kbd>Enter</kbd> | Open the highlighted search or navigation result in a new brower tab.                                                                                                                                                                          |
-| <kbd>?</kbd>                                                            | Display help within the command palette.                                                                                                                                                                                                       |
+| Keystroke | Function |
+| :- | :- |
+|<kbd>></kbd>| Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." |
+|<kbd>#</kbd>| Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
+|<kbd>@</kbd>| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
+|<kbd>/</kbd>| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
+|<kbd>!</kbd>| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
+|<kbd>Ctrl</kbd>+<kbd>C</kbd> or <kbd>Command</kbd>+<kbd>C</kbd>| Copy the search or navigation URL for the highlighted result to the clipboard.|
+|<kbd>Enter</kbd>| Jump to the highlighted result or run the highlighted command.|
+|<kbd>Ctrl</kbd>+<kbd>Enter</kbd> or <kbd>Command</kbd>+<kbd>Enter</kbd>| Open the highlighted search or navigation result in a new brower tab.|
+|<kbd>?</kbd>| Display help within the command palette.|

 ### Global commands

 These commands are available from all scopes.

-| Command                              | Behavior                                                                                                                                                                                                                                                                                   |
-|:------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `Import repository`                  | Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." |
-| `New gist`                           | Open a new gist. For more information, see "[Creating a gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)."                                                                                                                                      |
-| `New organization`                   | Create a new organization. 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。                                                                                                                                       |
-| `新项目`                                | Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)."                                                                                                                                           |
-| `New repository`                     | Create a new repository from scratch. 更多信息请参阅“[创建新仓库](/repositories/creating-and-managing-repositories/creating-a-new-repository)”。                                                                                                                                                        |
-| `Switch theme to <theme name>` | Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."                                            |
+| Command | Behavior|
+| :- | :- | :- |
+|`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)."  |
+|`New gist`|Open a new gist. For more information, see "[Creating a gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." |
+|`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." |
+|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)."  |
+|`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." |
+|`Switch theme to <theme name>`|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." |


 ### Organization commands

 These commands are available only within the scope of an organization.

-| Command    | Behavior                                                                                                                                                    |
-|:---------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `New team` | Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." |
+| Command | Behavior|
+| :- | :- |
+| `New team`| Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."

 ### Repository commands

 Most of these commands are available only on the home page of the repository. If a command is also available on other pages, this is noted in the behavior column.

-| Command                              | Behavior                                                                                                                                                                                                             |
-|:------------------------------------ |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Clone repository: <URL type>` | Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. 更多信息请参阅“[克隆仓库](/repositories/creating-and-managing-repositories/cloning-a-repository)”。 |
-| `New discussion`                     | Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."                                                               |
-| `New file`                           | Create a new file from any page in the repository. 更多信息请参阅“[添加文件到仓库](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)”。                                                                |
-| `New issue`                          | Open a new issue from any page in the repository. 更多信息请参阅“[创建议题](/issues/tracking-your-work-with-issues/creating-an-issue)”。                                                                                         |
-| `Open in new codespace`              | Create and open a codespace for this repository. 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。                                                                                       |
-| `Open in github.dev editor`          | Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."                           |
+| Command | Behavior|
+| :- | :- |
+|`Clone repository: <URL type>`|Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."|
+|`New discussion`|Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."|
+|`New file`|Create a new file from any page in the repository. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
+|`New issue`|Open a new issue from any page in the repository. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."|
+|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."|
+|`Open in github.dev editor`|Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."|

 ### File commands

 These commands are available only when you open the command palette from a file in a repository.

-| Command                     | Behavior                                                                                                                                                                                                                                                    |
-|:--------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Copy permalink`            | Create a link to the file that includes the current commit SHA and copy the link to the clipboard. 更多信息请参阅“[获取文件的永久链接](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)”。 |
-| `Open in github.dev editor` | Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."                                                                |
+| Command | Behavior|
+| :- | :- |
+|`Copy permalink`|Create a link to the file that includes the current commit SHA and copy the link to the clipboard. For more information, see "[Getting permanent links to files](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)."
+|`Open in github.dev editor`|Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."|

 ### Discussion commands

 These commands are available only when you open the command palette from a discussion. They act on your current page and are not affected by the scope set in the command palette.

-| Command                   | Behavior                                                                                                                                                                                               |
-|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `Delete discussion...`    | Permanently delete the discussion. 更多信息请参阅“[管理仓库中的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)”。                            |
-| `Edit discussion body`    | Open the main body of the discussion ready for editing.                                                                                                                                                |
-| `Subscribe`/`unsubscribe` | Opt in or out of notifications for additions to the discussion. 更多信息请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 |
-| `Transfer discussion...`  | Move the discussion to a different repository. 更多信息请参阅“[管理仓库中的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)”。            |
+| Command | Behavior|
+| :- | :- |
+|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)."
+|`Edit discussion body`|Open the main body of the discussion ready for editing.
+|`Subscribe`/`unsubscribe`|Opt in or out of notifications for additions to the discussion. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)."

 ### Issue commands

 These commands are available only when you open the command palette from an issue. They act on your current page and are not affected by the scope set in the command palette.

-| Command                          | Behavior                                                                                                                                                                                         |
-|:-------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `Close`/`reopen issue`           | Close or reopen the current issue. 更多信息请参阅“[关于议题](/issues/tracking-your-work-with-issues/about-issues)”。                                                                                         |
-| `Convert issue to discussion...` | Convert the current issue into a discussion. 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)”。                   |
-| `Delete issue...`                | Delete the current issue. 更多信息请参阅“[删除议题](/issues/tracking-your-work-with-issues/deleting-an-issue)”。                                                                                             |
-| `Edit issue body`                | Open the main body of the issue ready for editing.                                                                                                                                               |
-| `Edit issue title`               | Open the title of the issue ready for editing.                                                                                                                                                   |
-| `Lock issue`                     | Limit new comments to users with write access to the repository. 更多信息请参阅“[锁定对话](/communities/moderating-comments-and-conversations/locking-conversations)”。                                      |
-| `Pin`/`unpin issue`              | Change whether or not the issue is shown in the pinned issues section for the repository. 更多信息请参阅“[将议题固定到仓库](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)”。       |
-| `Subscribe`/`unsubscribe`        | Opt in or out of notifications for changes to this issue. 更多信息请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 |
-| `Transfer issue...`              | Transfer the issue to another repository. 更多信息请参阅“[将议题转让给其他仓库](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)”。                                             |
+| Command | Behavior|
+| :- | :- |
+|`Close`/`reopen issue`|Close or reopen the current issue. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."|
+|`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
+|`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."|
+|`Edit issue body`|Open the main body of the issue ready for editing.
+|`Edit issue title`|Open the title of the issue ready for editing.
+|`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
+|`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."|
+|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+|`Transfer issue...`|Transfer the issue to another repository. For more information, see "[Transferring an issue to another repository](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)."|

 ### Pull request commands

 These commands are available only when you open the command palette from a pull request. They act on your current page and are not affected by the scope set in the command palette.

-| Command                                                    | Behavior                                                                                                                                                                                                                                                                                                                          |
-|:---------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Close`/`reopen pull request`                              | Close or reopen the current pull request. 更多信息请参阅“[关于拉取请求](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)”。                                                                                                                                                      |
-| `Convert to draft`/`Mark pull request as ready for review` | Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."                                          |
-| `Copy current branch name`                                 | Add the name of the head branch for the pull request to the clipboard.                                                                                                                                                                                                                                                            |
-| `Edit pull request body`                                   | Open the main body of the pull request ready for editing.                                                                                                                                                                                                                                                                         |
-| `Edit pull request title`                                  | Open the title of the pull request ready for editing.                                                                                                                                                                                                                                                                             |
-| `Open in new codespace`                                    | Create and open a codespace for the head branch of the pull request. 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。                                                                                                                                                                                |
-| `Subscribe`/`unsubscribe`                                  | Opt in or out of notifications for changes to this pull request. 更多信息请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。                                                                                                                           |
-| `Update current branch`                                    | Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)." |
+| Command | Behavior|
+| :- | :- |
+|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."|
+|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."|
+|`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard.
+|`Edit pull request body`|Open the main body of the pull request ready for editing.
+|`Edit pull request title`|Open the title of the pull request ready for editing.
+|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."|
--- a/translations/zh-CN/content/issues/guides.md
+++ b/translations/zh-CN/content/issues/guides.md
@ -1,5 +1,5 @@
 ---
-title: Issues guides
+title: 议题指南
 shortTitle: 指南
 intro: '了解如何使用 {% data variables.product.prodname_github_issues %} 来规划和跟踪您的工作。'
 allowTitleToDifferFromFilename: true
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
@ -1,6 +1,6 @@
 ---
-title: Managing access to projects (beta)
-intro: 'You can control who can view, edit, or manage your projects.'
+title: 管理对项目的访问（测试版）
+intro: 您可以控制谁可以查看、编辑或管理您的项目。
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 2
 versions:
@ -13,78 +13,78 @@ topics:

 {% data reusables.projects.projects-beta %}

-## About project access
+## 关于项目访问

-Admins of organization-level projects can manage access for the entire organization, for teams, for individual organization members, and for outside collaborators.
+组织级项目的管理员可以管理整个组织、团队、单个组织成员和外部协作者的访问权限。

-Admins of user-level projects can invite individual collaborators and manage their access.
+用户级项目的管理员可以邀请单个协作者并管理其访问权限。

-Project admins can also control the visibility of their project for everyone on the internet. For more information, see "[Managing the visibility of your projects](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)."
+项目管理员还可以控制其项目在互联网上对每个人的可见性。 更多信息请参阅“[管理项目的可见性](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)”。

-## Managing access for organization-level projects
+## 管理组织级项目的访问权限

-### Managing access for everyone in your organization
+### 管理组织中每个人的访问权限

-The default base role is `write`, meaning that everyone in the organization can see and edit your project. To change project access for everyone in the organization, you can change the base role. Changes to the base role only affect organization members who are not organization owners and who are not granted individual access.
+默认的基本角色是`写入`，这意味着组织中的每个人都可以查看和编辑您的项目。 要更改组织中每个人的项目访问权限，您可以更改基本角色。 对基本角色的更改仅影响不是组织所有者且未被授予个人访问权限的组织成员。

 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-2. Under **Base role**, select the default role.
-   - **No access**: Only organization owners and users granted individual access can see the project. Organization owners are also admins for the project.
-   - **Read**: Everyone in the organization can see the project. Organization owners are also admins for the project.
-   - **Write**: Everyone in the organization can see and edit the project. Organization owners are also admins for the project.
-   - **Admin**: Everyone in the organization is an admin for the project.
+1. 单击 **Manage access（管理访问）**。
+2. 在 **Base role（基本角色）**下，选择默认角色。
+   - **无访问权限**：只有组织所有者和被授予个人访问权限的用户才能查看项目。 组织所有者也是项目的管理员。
+   - **读取**：组织中的每个人都可以查看该项目。 组织所有者也是项目的管理员。
+   - **写入**：组织中的每个人都可以查看并编辑该项目。 组织所有者也是项目的管理员。
+   - **管理员**：组织中的每个人都是项目的管理员。

-### Managing access for teams and individual members of your organization
+### 管理组织中团队和单个成员的访问权限

-You can also add teams, external collaborators, and individual organization members as collaborators for an organization-level project. 更多信息请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
+您还可以将团队、外部协作者和单个组织成员添加为组织级项目的协作者。 更多信息请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。

-You can only invite an individual user to collaborate on your organization-level project if they are already a member of the organization or an outside collaborator on at least one repository in the organization.
+仅当单个用户已经是组织中的成员或组织中至少一个存储库的外部协作者时，您才能邀请该用户协作处理组织级项目。

 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-2. Under **Invite collaborators**, search for the team or individual user that you want to invite.
-3. Select the role for the collaborator.
-   - **Read**: The team or individual can view the project.
-   - **Write**: The team or individual can view and edit the project.
-   - **Admin**: The team or individual can view, edit, and add new collaborators to the project.
-4. Click **Invite**.
+1. 单击 **Manage access（管理访问）**。
+2. 在 **Invite collaborators（邀请协作者）**下，搜索要邀请的团队或单个用户。
+3. 为协作者选择角色。
+   - **读取**：团队或个人可以查看项目。
+   - **写入**：团队或个人可以查看和编辑项目。
+   - **管理员**：团队或个人可以查看、编辑项目和添加新协作者。
+4. 单击 **Invite（邀请）**。

-### Managing access of an existing collaborator on your project
+### 管理现有协作者对项目的访问

 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
+1. 单击 **Manage access（管理访问）**。
+1. 在 **Manage access（管理访问）**下，找到要修改其权限的协作者。

-   You can use the **Type** and **Role** drop-down menus to filter the access list.
+   您可以使用 **Type（类型）**和 **Role（角色）**下拉菜单过滤访问列表。

-1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s).
+1. 编辑协作者的角色，或单击 {% octicon "trash" aria-label="the trash icon" %} 以删除协作者。

-## Managing access for user-level projects
+## 管理用户级项目的访问权限

-### Granting a collaborator access to your project
+### 授予协作者对项目的访问权限

 {% note %}

-This only affects collaborators for your project, not for repositories in your project. To view an item on the project, someone must have the required permissions for the repository that the item belongs to. 如果项目包含私有存储库中的项目，则不是存储库协作者的用户将无法查看该存储库中的项。 For more information, see "[Setting repository visibility](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
+这只会影响项目的协作者，而不会影响项目中的存储库。 要查看项目上的项，必须具有该项所属存储库所需的权限。 如果项目包含私有存储库中的项目，则不是存储库协作者的用户将无法查看该存储库中的项。 更多信息请参阅“[设置存储库可见性](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)”和“[管理有权访问存储库的团队和人员](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)”。

 {% endnote %}

 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-2. Under **Invite collaborators**, search for the user that you want to invite.
-3. Select the role for the collaborator.
-   - **Read**: The individual can view the project.
-   - **Write**: The individual can view and edit the project.
-   - **Admin**: The individual can view, edit, and add new collaborators to the project.
-4. Click **Invite**.
+1. 单击 **Manage access（管理访问）**。
+2. 在 **Invite collaborators（邀请协作者）**下，搜索要邀请的用户。
+3. 为协作者选择角色。
+   - **读取**：个人可以查看项目。
+   - **写入**：个人可以查看和编辑项目。
+   - **管理员**：个人可以查看、编辑项目和添加新协作者。
+4. 单击 **Invite（邀请）**。

-### Managing access of an existing collaborator on your project
+### 管理现有协作者对项目的访问

 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
+1. 单击 **Manage access（管理访问）**。
+1. 在 **Manage access（管理访问）**下，找到要修改其权限的协作者。

-   You can use the **Role** drop-down menu to filter the access list.
+   您可以使用 **Role（角色）**下拉菜单过滤访问列表。

-1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s).
+1. 编辑协作者的角色，或单击 {% octicon "trash" aria-label="the trash icon" %} 以删除协作者。
--- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
@ -1,6 +1,6 @@
 ---
-title: Exporting member information for your organization
-intro: 'You can export information about members in your organization, directly from the user interface.'
+title: 导出组织的成员信息
+intro: 您可以直接从用户界面导出有关组织中成员的信息。
 permissions: Organization owners can export member information for their organization.
 versions:
  fpt: '*'
@ -10,22 +10,22 @@ versions:
 topics:
  - Organizations
  - Teams
-shortTitle: Export member information
+shortTitle: 导出成员信息
 ---

-You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization.
+您可以导出有关组织中成员的信息。 如果要对组织内的用户执行审核，这将非常有用。

-The exported information includes:
- Username and display name details
- Whether the user has two-factor authentication enabled
- Whether the membership is public or private
- Whether the user is an organization owner or member
- Datetime of the user's last activity (for a full list of relevant activity, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)")
- The user's SAML NameID, if available
+导出的信息包括：
+- 用户名和显示名称详细信息
+- 用户是否启用了双重身份验证
+- 成员资格是公共的还是私有的
+- 用户是组织所有者还是成员
+- 用户上次活动的日期时间（有关相关活动的完整列表，请参阅“[管理休眠用户](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)”）
+- 用户的 SAML 名称 ID（如果可用）

-You can get member information directly from the {% data variables.product.product_name %} user interface, or using APIs. This article explains how to obtain member information from within {% data variables.product.product_name %}.
+您可以直接从 {% data variables.product.product_name %} 用户界面或使用 API 获取成员信息。 本文介绍如何从 {% data variables.product.product_name %} 中获取成员信息。

-For more information about the APIs, see our [GraphQL API](/graphql/reference/objects#user) and [REST API](/rest/reference/users) documentation about users.
+有关 API 的更多信息，请参阅我们有关用户的 [GraphQL API](/graphql/reference/objects#user) 和 [REST API](/rest/reference/users) 文档。

 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
@ -1,6 +1,6 @@
 ---
-title: Assigning the team maintainer role to a team member
-intro: You can give a team member the ability to manage team membership and settings by assigning the team maintainer role.
+title: 将团队维护者角色分配给团队成员
+intro: 您可以通过分配团队维护者角色，为团队成员提供管理团队成员身份和设置的能力。
 redirect_from:
  - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program
  - /articles/giving-team-maintainer-permissions-to-an-organization-member
@ -14,13 +14,13 @@ versions:
 topics:
  - Organizations
  - Teams
-shortTitle: Team maintainers
+shortTitle: 团队维护员
 permissions: Organization owners can promote team members to team maintainers.
 ---

-## About team maintainers
+## 关于团队维护员

-People with the team maintainer role can manage team membership and settings.
+具有团队维护员角色的人员可以管理团队成员身份和设置。

 - [更改团队名称和描述](/articles/renaming-a-team)
 - [更改团队的可见性](/articles/changing-team-visibility)
@ -38,7 +38,7 @@ People with the team maintainer role can manage team membership and settings.

 ## 将组织成员升级为团队维护员

-Before you can promote an organization member to team maintainer, the person must already be a member of the team.
+在将组织成员提升为团队维护员之前，该人员必须已经是团队的成员。

 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
--- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
+++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@ -1,45 +1,45 @@
 ---
-title: Verifying your custom domain for GitHub Pages
-intro: You can increase the security of your custom domain and avoid takeover attacks by verifying your domain.
+title: 验证 GitHub Pages 的自定义域
+intro: 您可以通过验证您的域来提高自定义域的安全性并避免接管攻击。
 product: '{% data reusables.gated-features.pages %}'
 versions:
  fpt: '*'
  ghec: '*'
 topics:
  - Pages
-shortTitle: Verify a custom domain
+shortTitle: 验证自定义域
 ---

-## About domain verification for GitHub Pages
+## 关于 GitHub Pages 的域验证

-When you verify your custom domain for your user account or organization, only repositories owned by your user account or organization may be used to publish a {% data variables.product.prodname_pages %} site to the verified custom domain or the domain's immediate subdomains.
+验证用户帐户或组织的自定义域时，只能使用您的用户帐户或组织拥有的存储库将 {% data variables.product.prodname_pages %} 站点发布到已验证的自定义域或域的直接子域。

-Verifying your domain stops other GitHub users from taking over your custom domain and using it to publish their own {% data variables.product.prodname_pages %} site. Domain takeovers can happen when you delete your repository, when your billing plan is downgraded, or after any other change which unlinks the custom domain or disables {% data variables.product.prodname_pages %} while the domain remains configured for {% data variables.product.prodname_pages %} and is not verified.
+验证您的域会阻止其他 GitHub 用户接管您的自定义域并使用它来发布他们自己的 {% data variables.product.prodname_pages %} 站点。 当您删除存储库、降低计费计划级别时，或者在取消链接自定义域或禁用 {% data variables.product.prodname_pages %} 而域仍配置为 {% data variables.product.prodname_pages %} 且未进行验证的任何其他更改之后，可能会发生域接管。

-When you verify a domain, any immediate subdomains are also included in the verification. For example, if the `github.com` custom domain is verified, `docs.github.com`, `support.github.com`, and any other immediate subdomains will also be protected from takeovers.
+验证域时，验证中还会包含任何直接子域。 例如，如果 `github.com` 自定义域经过验证，则 `docs.github.com`、`support.github.com` 和任何其他直接子域也将受到保护，以防止被接管。

-It's also possible to verify a domain for your organization{% ifversion ghec %} or enterprise{% endif %}, which displays a "Verified" badge on the organization {% ifversion ghec %}or enterprise{% endif %} profile{% ifversion ghec %} and, on {% data variables.product.prodname_ghe_cloud %},  allows you to restrict notifications to email addresses using the verified domain{% endif %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}" and "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}."
+还可以验证组织{% ifversion ghec %} 或企业{% endif %}的域，这会在组织 {% ifversion ghec %}或企业{% endif %} 配置文件{% ifversion ghec %} 以及 {% data variables.product.prodname_ghe_cloud %} 上显示“已验证”徽章，允许您使用已验证的域将通知限于电子邮件地址{% endif %}。 更多信息请参阅“[验证或批准组织的域](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}”和“[验证或批准企业的域](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}”。

-## Verifying a domain for your user site
+## 验证用户站点的域

 {% data reusables.user-settings.access_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**.
+1. 在侧边栏的“Code planning, and automation（代码规划和自动化）”部分中，点击 **{% octicon "browser" aria-label="The pages icon" %} Pages**。
 {% data reusables.pages.settings-verify-domain-setup %}
-1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
+1. 等待您的 DNS 配置更改，这可能是立即更改或最多需要 24 小时。 您可以通过在命令行上运行 `dig` 命令来确认对 DNS 配置的更改。 在下面的命令中，将 `USERNAME` 替换为您的用户名，将 `example.com` 替换为要验证的域。 如果您的 DNS 配置已更新，您应该会在输出中看到新的 TXT 记录。
  ```
  dig _github-pages-challenge-USERNAME.example.com +nostats +nocomments +nocmd TXT
  ```
 {% data reusables.pages.settings-verify-domain-confirm %}

-## Verifying a domain for your organization site
+## 验证组织站点的域

-Organization owners can verify custom domains for their organization.
+组织所有者可以验证其组织的自定义域。

 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
+1. 在边栏的“Code, planning, and automation（代码、规划和自动化）”部分中，点击 **{% octicon "browser" aria-label="The browser icon" %} Pages**。
 {% data reusables.pages.settings-verify-domain-setup %}
-1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
+1. 等待您的 DNS 配置更改，这可能是立即更改或最多需要 24 小时。 您可以通过在命令行上运行 `dig` 命令来确认对 DNS 配置的更改。 在下面的命令中，将 `ORGANIZATION` 替换为您的组织名称，并将 `example.com` 替换为要验证的域。 如果您的 DNS 配置已更新，您应该会在输出中看到新的 TXT 记录。
  ```
  dig _github-pages-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT
  ```
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md
@ -13,7 +13,7 @@ redirect_from:

 {% data reusables.pull_requests.merge-queue-beta %}

-## About pull request merge queue
+## 关于拉取请求合并队列

 {% data reusables.pull_requests.merge-queue-overview-short %}
 {% data reusables.pull_requests.merge-queue-references %}
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@ -29,7 +29,7 @@ shortTitle: 查看依赖项更改

 {% data reusables.dependency-review.feature-overview %}

-{% ifversion ghec %}Before you can use dependency review in a private repository, you must enable the dependency graph. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."{% endif %}
+{% ifversion ghec %}在私有存储库中使用依赖项审查之前，必须启用依赖项关系图。 更多信息请参阅“[探索仓库的依赖项](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)”。{% endif %}

 {% ifversion ghes > 3.1 %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上的有漏洞依赖项启用安全警报](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。{% endif %}

--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
@ -1,5 +1,5 @@
 ---
-title: Using a merge queue
+title: 使用合并队列
 intro: You can increase development velocity by enabling merge queues for pull requests in your repository.
 versions:
  fpt: '*'
@ -8,18 +8,18 @@ permissions: People with admin permissions can configure merge queues for pull r
 topics:
  - Repositories
  - Pull requests
-shortTitle: Use merge queue
+shortTitle: 使用合并队列
 ---

 {% data reusables.pull_requests.merge-queue-beta %}

-## About pull request merge queue
+## 关于拉取请求合并队列

 {% data reusables.pull_requests.merge-queue-overview %}

-The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh-readonly-queue/{base_branch}`.
+合并队列创建临时准备分支，以根据最新版本的基本分支验证拉取请求。 要确保 {% data variables.product.prodname_dotcom %} 验证这些预备分支，您可能需要更新 CI 配置，以触发以 `gh-readonly-queue/{base_branch}` 开头的分支名称的构建。

-For example, with {% data variables.product.prodname_actions %}, adding the following trigger to a workflow will cause the workflow to run when any push is made to a merge queue preparatory branch that targets `main`.
+例如，使用 {% data variables.product.prodname_actions %}，将以下触发器添加到工作流程将导致在面向 `main` 的合并队列准备分支进行任何推送时运行工作流程。

 ```
 on:
@ -31,25 +31,25 @@ on:

 {% data reusables.pull_requests.merge-queue-merging-method %}

-For information about merge methods, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." For information about the "Require linear history" branch protection setting, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)."
+有关合并方法的信息，请参阅“[关于拉取请求合并](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)”。 有关“需要线性历史记录”分支保护设置的信息，请参阅“[关于受保护分支](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)”。

 {% note %}

-**Note:** During the beta, there are some limitations when using the merge queue:
+**注意：** 在测试期间，使用合并队列时存在一些限制：

-* The merge queue cannot be enabled on branch protection rules using wildcards (`*`) in the name.
-* There is no support for squash merge commits. (Only merge commits and "rebase and merge" commits are supported.)
+* 无法在名称中使用通配符 (`*`) 的分支保护规则上启用合并队列。
+* 不支持压缩合并提交。 （仅支持合并提交和“变基并合并”提交。）

 {% endnote %}

 {% data reusables.pull_requests.merge-queue-reject %}
-## Managing pull request merge queue
+## 管理拉取请求合并队列

-Repository administrators can configure merge queues for pull requests targeting selected branches of a repository. The requirement to use a merge queue is a branch protection setting called "Require merge queue" that can be enabled in branch protection rules.
+存储库管理员可以为面向存储库的选定分支的拉取请求配置合并队列。 使用合并队列的要求是名为“需要合并队列”的分支保护设置，可以在分支保护规则中启用该设置。

-For information about how to enable the merge queue protection setting, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
+有关如何启用合并队列保护设置的信息，请参阅“[管理分支保护规则](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)”。

 ## 延伸阅读

- "[Adding a pull request to the merge queue](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)"
+- "[将拉取请求添加到合并队列](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)"
 - "[关于受保护分支](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)"
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
@ -37,11 +37,11 @@ $ git remote set-url origin <em>new_url</em>

 {% endif %}

-{% tip %}
+{% note %}

-**提示：**{% data reusables.organizations.owners-and-admins-can %}重命名仓库。 {% data reusables.organizations.new-repo-permissions-more-info %}
+**Note:** {% data variables.product.prodname_dotcom %} will not redirect calls to an action hosted by a renamed repository. Any workflow that uses that action will fail with the error `repository not found`. Instead, create a new repository and action with the new name and archive the old repository. 更多信息请参阅“[存档仓库](/repositories/archiving-a-github-repository/archiving-repositories)”。

-{% endtip %}
+{% endnote %}

 {% warning %}

--- 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
@ -47,3 +47,39 @@ With the raw view, you can view or copy the raw content of a file without any st
 2. 单击以打开您想要查看其行历史记录的文件。
 3. 在文件视图的右上角，单击 **Blame（追溯）**可打开追溯视图。 ![追溯按钮](/assets/images/help/repository/blame-button.png)
 4. 要查看特定行的早期修订，或重新追溯，请单击 {% octicon "versions" aria-label="The prior blame icon" %}，直至找到您有兴趣查看的更改。 ![追溯前按钮](/assets/images/help/repository/prior-blame-button.png)
+
+{% if blame-ignore-revs %}
+
+## Ignore commits in the blame view
+{% note %}
+
+**Note:** Ignoring commits in the blame view is currently in public beta and subject to change.
+
+{% endnote %}
+
+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.
+
+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:
+
+    ```ini
+    # .git-blame-ignore-revs
+    # Removed semi-colons from the entire codebase
+    a8940f7fbddf7fad9d7d50014d4e8d46baf30592
+    # Converted all JavaScript to TypeScript
+    69d029cec8337c616552756310748c4a507bd75a
+    ```
+
+3. Commit and push the changes.
+
+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:
+
+![Screenshot of a banner on the blame view linking to the .git-blame-ignore-revs file](/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:
+
+```shell
+git blame --ignore-revs-file .git-blame-ignore-revs
+```
+
+{% endif %}
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
@ -98,7 +98,7 @@ We do not allow content or activity on GitHub that:

 我们理解，您可能想通过在帐户中发布支持者的姓名或徽标来推广您的内容，但在帐户中或通过帐户发布到服务的内容不应侧重于广告或促销。 这包括在页面、包、仓库和服务所有其他部分或者通过它们发布的内容。 您可在与您的帐户关联的自述文件中或项目说明部分包含静态图像、链接和宣传文本，但它们必须与您在 GitHub 上托管的项目相关。 您不能在其他用户的帐户中发布广告，例如在议题中发布货币化或过多的批量内容。

-You may not promote or distribute content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service/)or [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies/), including excessive automated bulk activity (for example, spamming), get-rich-quick schemes, and misrepresentation or deception related to your promotion.
+You may not promote or distribute content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service/) or [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies/), including excessive automated bulk activity (for example, spamming), get-rich-quick schemes, and misrepresentation or deception related to your promotion.

 如果您决定在帐户中发布任何宣传材料，您将自行负责遵守所有适用的法律和法规，包括但不限于美国联邦贸易委员会的背书和推荐准则。 联邦贸易委员会的背书和推荐准则。 我们保留删除我们单方面认为违反了任何 GitHub 条款或政策的任何宣传材料或广告的权利。

--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/index.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/index.md
@ -6,16 +6,16 @@ topics:
  - Policy
  - Legal
 children:
-  - github-sexually-obscene-content
+  - github-acceptable-use-policies
+  - github-active-malware-or-exploits
+  - github-bullying-and-harassment
  - github-disrupting-the-experience-of-other-users
  - github-doxxing-and-invasion-of-privacy
  - github-hate-speech-and-discrimination
-  - github-acceptable-use-policies
-  - github-bullying-and-harassment
-  - github-active-malware-or-exploits
-  - github-threats-of-violence-and-gratuitously-violent-content
  - github-impersonation
  - github-misinformation-and-disinformation
+  - github-sexually-obscene-content
+  - github-threats-of-violence-and-gratuitously-violent-content
  - github-appeal-and-reinstatement
 ---

--- a/translations/zh-CN/content/site-policy/content-removal-policies/index.md
+++ b/translations/zh-CN/content/site-policy/content-removal-policies/index.md
@ -7,10 +7,10 @@ topics:
  - Legal
 children:
  - /submitting-content-removal-requests
+  - /dmca-takedown-policy
  - /github-private-information-removal-policy
  - /github-trademark-policy
  - /guide-to-submitting-a-dmca-counter-notice
  - /guide-to-submitting-a-dmca-takedown-notice
-  - /dmca-takedown-policy
 ---

--- a/translations/zh-CN/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
+++ b/translations/zh-CN/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
@ -3,6 +3,10 @@ title: GitHub 其他产品和功能条款
 redirect_from:
  - /github/site-policy/github-additional-product-terms
  - /github/site-policy/github-terms-for-additional-products-and-features
+  - /github/site-policy-deprecated/github-connect-addendum-to-the-github-enterprise-license-agreement
+  - /articles/github-com-connection-addendum-to-the-github-enterprise-license-agreement
+  - /articles/github-connect-addendum-to-the-github-enterprise-license-agreement
+  - /github/site-policy/github-connect-addendum-to-the-github-enterprise-license-agreement
 versions:
  fpt: '*'
 topics:
--- a/translations/zh-CN/content/site-policy/github-terms/index.md
+++ b/translations/zh-CN/content/site-policy/github-terms/index.md
@ -6,12 +6,12 @@ topics:
  - Policy
  - Legal
 children:
-  - /github-corporate-terms-of-service
-  - /github-community-forum-code-of-conduct
-  - /github-community-guidelines
  - /github-terms-of-service
-  - /github-sponsors-additional-terms
+  - /github-corporate-terms-of-service
  - /github-terms-for-additional-products-and-features
+  - /github-community-guidelines
+  - /github-community-forum-code-of-conduct
+  - /github-sponsors-additional-terms
  - /github-registered-developer-agreement
  - /github-marketplace-terms-of-service
  - /github-marketplace-developer-agreement
--- a/translations/zh-CN/content/site-policy/privacy-policies/index.md
+++ b/translations/zh-CN/content/site-policy/privacy-policies/index.md
@ -6,12 +6,12 @@ topics:
  - Policy
  - Legal
 children:
-  - /github-codespaces-privacy-statement
+  - /github-privacy-statement
  - /global-privacy-practices
  - /github-data-protection-agreement
-  - /github-privacy-statement
  - /github-subprocessors-and-cookies
  - /githubs-notice-about-the-california-consumer-privacy-act
+  - /github-codespaces-privacy-statement
  - /github-candidate-privacy-policy
 ---

--- a/translations/zh-CN/data/features/blame-ignore-revs.yml
+++ b/translations/zh-CN/data/features/blame-ignore-revs.yml
@ -0,0 +1,7 @@
+---
+#Reference: #6378.
+#Documentation for the `.git-blame-ignore-revs` file and the blame view
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
--- a/translations/zh-CN/data/features/for-you-feed.yml
+++ b/translations/zh-CN/data/features/for-you-feed.yml
@ -0,0 +1,6 @@
+---
+#Issues 4834 and 5722
+#New feed for personal dashboards and option to follow organizations
+versions:
+  fpt: '*'
+  ghec: '*'
--- a/translations/zh-CN/data/reusables/actions/restrict-runner-workflow-beta.md
+++ b/translations/zh-CN/data/reusables/actions/restrict-runner-workflow-beta.md
@ -1,7 +0,0 @@
-{% if restrict-groups-to-workflows %}
-{% note %}
-
-**Note:** Configuring the workflows that can access a runner group is currently in beta and subject to change.
-
-{% endnote %}
-{% endif %}
--- a/translations/zh-CN/data/reusables/user-settings/account_settings.md
+++ b/translations/zh-CN/data/reusables/user-settings/account_settings.md
@ -1,4 +1,4 @@
-{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-next %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
 1. In the left sidebar, click **{% octicon "gear" aria-label="The gear icon" %} Account**.
 {% else %}
 1. 在左侧边栏中，单击 **Account（帐户）**。 ![帐户设置菜单选项](/assets/images/help/settings/settings-sidebar-account-settings.png)
--- a/translations/zh-CN/data/variables/product.yml
+++ b/translations/zh-CN/data/variables/product.yml
@ -156,7 +156,7 @@ prodname_arctic_vault: 'Arctic 代码库'
 prodname_copilot: 'GitHub Copilot'
 prodname_copilot_short: 'Copilot'
 #Command Palette
-prodname_command_palette: 'GitHub Command Palette'
+prodname_command_palette: 'GitHub 命令面板'
 #Links
 product_url: >-
  {% ifversion fpt or ghec %}github.com{% else %}[hostname]{% endif %}