New translation batch for cn (github#27248)

* 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

Co-authored-by: Robert Sese <[email protected]>

Author: docubot

translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md

@@ -1,63 +1,63 @@
 ---
-title: Setting your profile to private
-intro: 'A private profile displays only limited information, and hides some activity.'
+title: 将您的个人资料设置为私密
+intro: 私密个人资料仅显示有限的信息，并隐藏某些活动。
 versions:
   fpt: '*'
 topics:
   - Profiles
-shortTitle: Set profile to private
+shortTitle: 将个人资料设置为私密
 ---
 
-## About private profiles
+## 关于私密个人资料
 
 {% note %}
 
-**Note:** Private profiles are currently in beta and are subject to change.
+**注意：**私密个人资料目前处于测试阶段，可能会有所变化。
 
 {% endnote %}
 
-To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity.
+要隐藏部分个人资料页面，您可以将个人资料设为私密。 这也会隐藏您在 {% data variables.product.prodname_dotcom_the_website %} 上的各种社交功能中的活动。 私密个人资料会隐藏所有用户的信息，并且当前没有允许指定用户查看您的活动的选项。
 
-After making your profile private, you can still view all your information when you visit your own profile.
+将个人资料设为私密后，您仍然可以在访问自己的个人资料时查看所有信息。
 
-Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private.
+私密个人资料在 [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) 下不能获得赞助。 要获得 {% data variables.product.prodname_sponsors %} 资格，您的个人资料不能是私密的。
 
-## Differences between private and public profiles
+## 私密个人资料与公共个人资料之间的差异
 
-When your profile is private, the following content is hidden from your profile page:
+当您的个人资料为私密时，您的个人资料页面中会隐藏以下内容：
 
-- Achievements and highlights.
-- Activity overview and activity feed.
-- Contribution graph.
-- Follower and following counts.
-- Follow and Sponsor buttons.
-- Organization memberships.
-- Stars, projects, packages, and sponsoring tabs.
+- 成就和亮点。
+- 活动概述和活动源。
+- 贡献图。
+- 关注者和关注数。
+- 关注和赞助者按钮。
+- 组织成员资格。
+- 星标、项目、包和赞助标签。
 
 {% note %}
 
-**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo.
+**注意**：当您的个人资料为私密时，某些可选字段仍可公开显示，例如自述文件、传记和头像。
 
 {% endnote %}
 
-## Changes to reporting on your activities
+## 更改活动报告
 
-By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled.
+通过将个人资料设为私密，您无法删除或隐藏过去的活动；此设置仅适用于启用私密设置时的活动。
 
-When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations:
+当您的个人资料为私密时，您的 {% data variables.product.prodname_dotcom_the_website %} 活动将不会显示在以下位置：
 
-- Activity feeds for other users.
-- Discussions leaderboards.
-- The [Trending](https://github.com/trending) page.
+- 其他用户的活动源。
+- 讨论排行榜。
+- [热门](https://github.com/trending)页面。
 
 {% note %}
 
-**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API.
+**注意**：您在公共仓库上的活动仍将对查看这些仓库的任何人公开可见，并且某些活动数据可能仍可通过 {% data variables.product.prodname_dotcom %} API 获得。
 
 {% endnote %}
 
-## Changing your profile's privacy settings
+## 更改个人资料的隐私设置
 
 {% data reusables.user-settings.access_settings %}
-1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**.
+1. 在“Contributions & Activity（贡献和活动）”下，选中 **Make profile private and hide activity（将个人资料设为私密并隐藏活动）**旁边的复选框。
 {% data reusables.user-settings.update-preferences %}

translations/zh-CN/content/actions/using-workflows/about-workflows.md

@@ -1,7 +1,7 @@
 ---
 title: 关于工作流程
 shortTitle: 关于工作流程
-intro: 'Get a high level overview {% data variables.product.prodname_actions %} workflows, including triggers, syntax, and advanced features.'
+intro: '获取 {% data variables.product.prodname_actions %} 工作流程的高级概述，包括触发器、语法和高级功能。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -20,48 +20,48 @@ miniTocMaxHeadingLevel: 3
 
 {% data reusables.actions.about-workflows-long %}
 
-## Workflow basics
+## 工作流程基础知识
 
-A workflow must contain the following basic components:
+工作流程必须包含以下基本组件：
 
-1. One or more _events_ that will trigger the workflow.
-1. One or more _jobs_, each of which will execute on a _runner_ machine and run a series of one or more _steps_.
-1. Each step can either run a script that you define or run an action, which is a reusable extension that can simplify your workflow.
+1. 将触发工作流程的一个或多个_事件_。
+1. 一个或多个_作业_，每个作业将在_运行器_计算机上执行，并运行一系列一个或多个_步骤_。
+1. 每个步骤都可以运行您定义的脚本，也可以运行操作，这是一个可重用的扩展，可以简化您的工作流程。
 
-For more information these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)."
+For more information on these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)."
 
 ![工作流程概述](/assets/images/help/images/overview-actions-simple.png)
 
 ## 触发工作流程
 
 {% data reusables.actions.about-triggers %}
 
-For more information, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)", and for a full list of events, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
+更多信息请参阅“[触发工作流程](/actions/using-workflows/triggering-a-workflow)”，有关事件的完整列表，请参阅“[触发工作流程的事件](/actions/using-workflows/events-that-trigger-workflows)”。
 
 ## 工作流程语法
 
-Workflow are defined using YAML. For the full reference of the YAML syntax for authoring workflows, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#about-yaml-syntax-for-workflows)."
+工作流程是使用 YAML 定义的。 有关用于创建工作流程的 YAML 语法的完整参考，请参阅“[GitHub Actions 的工作流程语法](/actions/using-workflows/workflow-syntax-for-github-actions#about-yaml-syntax-for-workflows)”。
 
 
 {% data reusables.actions.workflow-basic-example-and-explanation %}
 
-For more on managing workflow runs, such as re-running, cancelling, or deleting a workflow run, see "[Managing workflow runs](/actions/managing-workflow-runs)."
+有关管理工作流程运行（如重新运行、取消或删除工作流程运行）的详细信息，请参阅“[管理工作流程运行](/actions/managing-workflow-runs)”。
 
 ## 使用入门工作流程
 
 {% data reusables.actions.workflow-template-overview %}
 
-For more information on using and creating starter workflows, see "[Using starter workflows](/actions/using-workflows/using-starter-workflows)" and "[Creating starter workflows for your organization](/actions/using-workflows/creating-starter-workflows-for-your-organization)."
+有关使用和创建入门工作流程的详细信息，请参阅“[使用入门工作流程](/actions/using-workflows/using-starter-workflows)”和“[为组织创建入门工作流程](/actions/using-workflows/creating-starter-workflows-for-your-organization)”。
 
 ## 高级工作流程功能
 
-This section briefly describes some of the advanced features of {% data variables.product.prodname_actions %} that help you create more complex workflows.
+本节简介了 {% data variables.product.prodname_actions %} 的一些高级功能，可帮助您创建更复杂的工作流程。
 
 ### 存储密码
 
-如果您的工作流程使用敏感数据，例如密码或证书， 您可以将这些信息在 {% data variables.product.prodname_dotcom %} 中保存为 _机密_，然后在工作流中将它们用作环境变量。 This means that you will be able to create and share workflows without having to embed sensitive values directly in the workflow's YAML source.
+如果您的工作流程使用敏感数据，例如密码或证书， 您可以将这些信息在 {% data variables.product.prodname_dotcom %} 中保存为 _机密_，然后在工作流中将它们用作环境变量。 这意味着您将能够创建和共享工作流程，而无需直接在工作流程的 YAML 源中嵌入敏感值。
 
-This example job demonstrates how to reference an existing secret as an environment variable, and send it as a parameter to an example command.
+此示例作业演示如何将现有机密引用为环境变量，并将其作为参数发送到示例命令。
 
 {% raw %}
 ```yaml
@@ -81,7 +81,7 @@ jobs:
 
 ### 创建依赖的作业
 
-默认情况下，工作流程中的作业同时并行运行。 If you have a job that must only run after another job has completed, you can use the `needs` keyword to create this dependency. If one of the jobs fails, all dependent jobs are skipped; however, if you need the jobs to continue, you can define this using the `if` conditional statement.
+默认情况下，工作流程中的作业同时并行运行。 如果您有一个作业必须在另一个作业完成后运行，可以使用 `needs` 关键字来创建此依赖项。 如果其中一个作业失败，则跳过所有从属作业；但如果您需要作业继续，可以使用条件语句 `if` 来定义。
 
 在此示例中，`setup`、`build` 和 `test` 作业连续运行，`build` 和 `test` 取决于其前面的作业成功完成：
 
@@ -107,7 +107,7 @@ jobs:
 
 ### 使用构建矩阵
 
-You can use a build matrix if you want your workflow to run tests across multiple combinations of parameters, such as operating systems, platforms, and languages. 构建矩阵是使用 `strategy` 关键字创建的，它接收构建选项作为数组。 例如，此构建矩阵将使用不同版本的 Node.js 多次运行作业：
+如果您希望工作流程跨参数（如操作系统、平台和语言）的多个组合运行测试，可以使用构建矩阵。 构建矩阵是使用 `strategy` 关键字创建的，它接收构建选项作为数组。 例如，此构建矩阵将使用不同版本的 Node.js 多次运行作业：
 
 ```yaml
 jobs:
@@ -173,7 +173,7 @@ jobs:
           POSTGRES_PORT: 5432
 ```
 
-For more information, see "[Using containerized services](/actions/using-containerized-services)."
+更多信息请参阅“[使用容器化服务](/actions/using-containerized-services)”。
 
 ### 使用标签路由工作流程
 
@@ -187,12 +187,12 @@ jobs:
     runs-on: [self-hosted, linux, x64, gpu]
 ```
 
-工作流程只能在一个所有标签处于 `runs-on` 数组中的运行器上运行。 作业将优先转到具有指定标签的空闲自托管运行器。 {% ifversion fpt or ghec %}If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner.{% endif %}
+工作流程只能在一个所有标签处于 `runs-on` 数组中的运行器上运行。 作业将优先转到具有指定标签的空闲自托管运行器。 {% ifversion fpt or ghec %}如果没有可用且具有指定标签的 {% data variables.product.prodname_dotcom %} 托管运行器存在，作业将转到 {% data variables.product.prodname_dotcom %} 托管的运行器。{% endif %}
 
-To learn more about self-hosted runner labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+要了解自托管运行器标签的更多信息，请参阅“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)”。
 
 {% ifversion fpt or ghec %}
-To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see "[Supported runners and hardware resources](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)."
+要详细了解 {% data variables.product.prodname_dotcom %} 托管的运行器标签，请参阅[“支持的运行器和硬件资源”](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)。
 {% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
@@ -202,4 +202,4 @@ To learn more about {% data variables.product.prodname_dotcom %}-hosted runner l
 
 ### 使用环境
 
-You can configure environments with protection rules and secrets to control the execution of jobs in a workflow. 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。
+您可以使用保护规则和机密配置环境，以控制工作流程中作业的执行。 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。

translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md

@@ -14,9 +14,14 @@ redirect_from:
   - /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
 shortTitle: MinIO Gateway for NAS storage
 ---
-## Prerequisites
 
-{% data reusables.actions.enterprise-s3-support-warning %}
+{% warning %}
+
+**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_actions %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository.
+
+{% endwarning %}
+
+## Prerequisites
 
 Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
 

translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md

@@ -48,7 +48,7 @@ Each action is a repository in the `actions` organization, and each action repos
 
 **Notes:** 
 - When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)."
-- Upgrades to {% data variables.product.product_name %} will not result in the bundled actions being updated.
+- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated.
 
 {% endnote %}