From 5d9dc93babe0903fe58a1f8273bef9c5d547638c Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 19 Jul 2022 14:59:35 -0400 Subject: [PATCH] New translation batch for cn (#29146) * 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 Co-authored-by: Hector Alfaro --- translations/log/cn-resets.csv | 3 +- .../metadata-syntax-for-github-actions.md | 4 + ...-enterprise-server-with-a-load-balancer.md | 2 +- .../about-github-enterprise-server.md | 2 +- .../phase-4-create-internal-documentation.md | 18 +-- ...phase-5-rollout-and-scale-code-scanning.md | 34 +++--- ...ase-6-rollout-and-scale-secret-scanning.md | 48 ++++---- .../about-the-security-overview.md | 6 +- ...ltering-alerts-in-the-security-overview.md | 6 +- .../code-security/security-overview/index.md | 2 +- .../viewing-the-security-overview.md | 6 +- .../about-releases.md | 2 +- .../about-github-support.md | 15 ++- translations/zh-CN/data/features/README.md | 9 +- .../features/enterprise-owner-join-org.yml | 2 +- .../zh-CN/data/features/pr-tree-view.yml | 2 +- .../features/remove-enterprise-members.yml | 1 - .../enterprise-server/3-5/0-rc1.yml | 104 +++++++++--------- .../release-notes/enterprise-server/3-5/0.yml | 104 +++++++++--------- .../actions/enterprise-http-proxy.md | 6 +- .../actions/jobs/about-matrix-strategy.md | 2 +- .../actions/more-resources-for-ghes.md | 27 +++++ .../hardware-considerations-all-platforms.md | 4 + .../hardware-rec-table.md | 63 ++--------- ...ecurity-center.md => security-overview.md} | 0 .../beta.md | 0 .../permissions.md | 0 .../webhooks/check_suite_properties.md | 2 +- translations/zh-CN/data/variables/product.yml | 2 +- 29 files changed, 232 insertions(+), 244 deletions(-) create mode 100644 translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md rename translations/zh-CN/data/reusables/gated-features/{security-center.md => security-overview.md} (100%) rename translations/zh-CN/data/reusables/{security-center => security-overview}/beta.md (100%) rename translations/zh-CN/data/reusables/{security-center => security-overview}/permissions.md (100%) diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index a7e0d22d61..380c07fa64 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -139,6 +139,7 @@ translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/u translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md,broken liquid tags translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md,broken liquid tags +translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md,broken liquid tags @@ -351,6 +352,7 @@ translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken li translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags translations/zh-CN/data/reusables/actions/enterprise-no-internet-actions.md,broken liquid tags translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags +translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md,broken liquid tags translations/zh-CN/data/reusables/actions/self-hosted-runner-architecture.md,broken liquid tags translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md,broken liquid tags translations/zh-CN/data/reusables/actions/self-hosted-runner-description.md,rendering error @@ -380,7 +382,6 @@ translations/zh-CN/data/reusables/enterprise-licensing/about-license-sync.md,bro translations/zh-CN/data/reusables/enterprise-licensing/verified-domains-license-sync.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags -translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,rendering error translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md index f79c781cf5..3d1ed64db0 100644 --- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -369,10 +369,14 @@ runs: ``` {% endif %} +{% ifversion ghes > 3.5 or ghae-issue-6573 %} + #### `runs.steps[*].continue-on-error` **可选** 防止在步骤失败时操作失败。 设置为 `true` 以允许在此步骤失败时通过操作。 +{% endif %} + ## 用于 Docker 容器操作的 `runs` **必要** 配置用于 Docker 容器操作的图像。 diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md index c1fc697063..094c83696a 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md @@ -91,7 +91,7 @@ If you enable support for the `X-Forwarded-For` header on your instance and load If {% data variables.product.product_location %} indicates that your session has expired when you connect to the {% data variables.enterprise.management_console %} through a load balancer, try one of the following configurations on your load balancer. - Disable `X-Forwarded-For` headers for connections to your instance on ports 8080 and 8443. -- Configure your load balancer to operate on Layer 4, and use the PROXY protocol instead of `X-Forwarded-For` for passthrough of client IP addresses. For more information, see "[Enabling PROXY protocol support on {% data variables.product.product_location %} ](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)." +- Configure your load balancer to operate on Layer 4, and use the PROXY protocol instead of `X-Forwarded-For` for passthrough of client IP addresses. For more information, see "[Enabling PROXY protocol support on {% data variables.product.product_location %}](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)." For more information, refer to the documentation for your load balancer. diff --git a/translations/zh-CN/content/admin/overview/about-github-enterprise-server.md b/translations/zh-CN/content/admin/overview/about-github-enterprise-server.md index e22777ca4e..2536c1403d 100644 --- a/translations/zh-CN/content/admin/overview/about-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/overview/about-github-enterprise-server.md @@ -77,7 +77,7 @@ By default, {% data variables.product.product_name %} runs as a standalone insta To safeguard against data loss or service disruptions for your developers, {% data variables.product.company_short %} strongly recommends that you establish a plan for disaster recovery. You can back up your instance's configuration and user data by deploying and configuring a Linux or Unix host system with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." -Additionally, you can configure a passive replica instance to fail over to in the event of a system or network failure. For more information, see "[About deployment](#about-deployment-topologies)." +Additionally, you can configure a passive replica instance to fail over to in the event of a system or network failure. For more information, see "[About deployment topologies](#about-deployment-topologies)." ## About documentation diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md index 0c61eb5465..8fea8823d0 100644 --- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md +++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md @@ -1,32 +1,32 @@ --- -title: 'Phase 4: Create internal documentation' -intro: 'You will create internal documentation and then communicate this to the consumers of {% data variables.product.prodname_GH_advanced_security %}.' +title: 第 4 阶段：创建内部文档 +intro: '您将创建内部文档，然后将其传达给 {% data variables.product.prodname_GH_advanced_security %} 的使用者。' versions: ghes: '*' ghae: '*' ghec: '*' topics: - Advanced Security -shortTitle: 4. Create internal documentation +shortTitle: 4. 创建内部文档 miniTocMaxHeadingLevel: 3 --- {% note %} -本文是关于大规模采用 {% data variables.product.prodname_GH_advanced_security %} 系列文章的一部分。 For the previous article in this series, see "[Phase 3: Pilot programs](/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs)." +本文是关于大规模采用 {% data variables.product.prodname_GH_advanced_security %} 系列文章的一部分。 有关本系列的上一篇文章，请参阅“[第 3 阶段：试点计划](/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs)”。 {% endnote %} -Before enabling {% data variables.product.prodname_GH_advanced_security %}, you should create internal documentation that defines processes for teams to follow. Everyone needs to know what to do when they receive a security alert, even if the process simply asks the team to apply their best judgment. Documentation will also prevent developers from getting blocked when they have questions. You should put the documentation about GHAS with existing developer-focused documentation, such as your developer portal or custom knowledge base. +在启用 {% data variables.product.prodname_GH_advanced_security %} 之前，应创建内部文档，用于定义团队要遵循的流程。 每个人都需要知道在收到安全警报时该怎么做，即使该流程只是要求团队运用他们的最佳判断。 文档还可以防止开发人员在遇到问题时束手无策。 您应将有关 GHAS 的文档与现有的以开发人员为中心的文档（例如开发人员门户或自定义知识库）放在一起。 -If you ran pilot programs, use the experiences and feedback from the teams involved in those pilots to influence your documentation. This is especially useful if you encountered issues that are specific to your company, that other teams will also likely encounter. +如果您运行了试点计划，请使用参与这些试点的团队的经验和反馈来影响您的文档。 如果您遇到特定于公司的问题，这尤其有用，其他团队也可能会遇到这些问题。 -If you skip creating internal documentation, your rollout won’t go at your intended pace. Creating internal documentation may slow the initial rollout by a week or two, but that time will be made up when developers can answer their own questions instead of coming to your team. +如果您跳过创建内部文档，部署将无法按预期速度进行。 创建内部文档可能会使初始部署速度减慢一两周，但是当开发人员可以回答自己的问题而不是来到您的团队时，这段时间将被弥补。 -Education is probably the most crucial part of the rollout as it teaches developers what to do in different situations. You should ensure developers are empowered to maintain the security of their repository and that the security team are authorized to verify both what developers are doing and that it's in the best interest of security. In additional to internal documentation, education can take the form of online sessions, Q&As, etc. +教育可能是推出过程中最关键的部分，因为它教会开发人员在不同情况下该怎么做。 您应该确保开发人员有权维护其存储库的安全性，并且安全团队有权验证开发人员正在执行的操作以及这是否符合安全性的最佳利益。 除内部文档外，教育还可以采取在线会议、问答等形式。 {% note %} -For the next article in this series, see "[Phase 5: Rollout and scale code scanning](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)." +有关本系列的下一篇文章，请参阅“[第 5 阶段：推出和扩展代码扫描](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)”。 {% endnote %} diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md index bcffefea2e..3a94932663 100644 --- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md +++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md @@ -1,56 +1,56 @@ --- -title: 'Phase 5: Rollout and scale code scanning' -intro: 'You can leverage the available APIs to rollout {% data variables.product.prodname_code_scanning %} programmatically by team and by language across your enterprise using the repository data you collected earlier.' +title: 第 5 阶段：推出和扩展代码扫描 +intro: '您可以使用之前收集的存储库数据，利用可用的 API 按团队和语言在整个企业中以编程方式推出 {% data variables.product.prodname_code_scanning %}。' versions: ghes: '*' ghae: '*' ghec: '*' topics: - Advanced Security -shortTitle: 5. Rollout code scanning +shortTitle: 5. 推出代码扫描 miniTocMaxHeadingLevel: 3 --- {% note %} -本文是关于大规模采用 {% data variables.product.prodname_GH_advanced_security %} 系列文章的一部分。 For the previous article in this series, see "[Phase 4: Create internal documentation](/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation)." +本文是关于大规模采用 {% data variables.product.prodname_GH_advanced_security %} 系列文章的一部分。 有关本系列的上一篇文章，请参阅“[第 4 阶段：创建内部文档](/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation)”。 {% endnote %} ### 启用代码扫描 -Using the data you collated in [Phase 2](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale), you can begin to enable GHAS and then {% data variables.product.prodname_code_scanning %} on your repositories, one language at a time. The step-by-step process for enabling GHAS should look like this: +使用您在[第 2 阶段](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale)整理的数据，可以开始启用 GHAS，然后在存储库中的 {% data variables.product.prodname_code_scanning %} 上启用，一次一种语言。 启用 GHAS 的分步过程应如下所示： -1. Enable GHAS on the repository. 更多信息请参阅“[管理仓库的安全和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)”。 -1. Create a pull request against the repository's default branch with a `codeql-analysis.yml` file containing an example of how to run CodeQL for that language. 更多信息请参阅“[创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)”。 -1. Create an issue in the repository to explain why a pull request has been raised. The issue you create can contain a link to the previous communication sent to all users, but can also explain what changes the pull request introduces, what next steps the team have to take, what the team's responsibilities are, and how the team should be using {% data variables.product.prodname_code_scanning %}. 更多信息请参阅“[创建议题](/issues/tracking-your-work-with-issues/creating-an-issue)”。 +1. 在存储库上启用 GHAS。 更多信息请参阅“[管理仓库的安全和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)”。 +1. 使用 `codeql-analysis.yml` 文件创建针对存储库的默认分支的拉取请求，该文件包含如何为该语言运行 CodeQL 的示例。 更多信息请参阅“[创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)”。 +1. 在存储库中创建议题以解释引发拉取请求的原因。 您创建的议题可以包含指向发送给所有用户的上一次通信的链接，但还可以解释拉取请求引入了哪些更改，团队必须采取的后续步骤，团队的职责是什么，以及团队应如何使用 {% data variables.product.prodname_code_scanning %}。 更多信息请参阅“[创建议题](/issues/tracking-your-work-with-issues/creating-an-issue)”。 -There is a publicly available tool that completes the first two steps called the [ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement). You can re-run the ghas-enablement tool in batches of languages where it makes sense. For example, JavaScript, TypeScript, Python, and Go likely have a similar build process and could therefore use a similar CodeQL analysis file. The ghas-enablement tool can also be used for languages such as Java, C, and C++, but due to the varied nature of how these languages build and compile you may need to create more targeted CodeQL analysis files. +有一个公开可用的工具可以完成前两个步骤，称为 [ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement)。 您可以在有意义的语言中批量重新运行 ghas-enablement 工具。 例如，JavaScript、TypeScript、Python 和 Go 可能具有类似的构建过程，因此可以使用类似的 CodeQL 分析文件。 ghas-enablement 工具还可用于 Java、C 和 C++等语言，但由于这些语言构建和编译方式的不同，您可能需要创建更有针对性的 CodeQL 分析文件。 {% note %} -**Note:** If you are intending to use {% data variables.product.prodname_actions %} to control {% data variables.product.prodname_code_scanning %} and you do not use the [ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement), keep in mind that there is no API access to the `.github/workflow` directory. This means that you cannot create a script without a git client underlying the automation. The workaround is to leverage bash scripting on a machine or container which has a git client. The git client can push and pull files into the `.github/workflows` directory where the `codeql-analysis.yml` file is located. +**注意：** 如果您打算使用 {% data variables.product.prodname_actions %} 来控制 {% data variables.product.prodname_code_scanning %} ，并且不使用 [ghas-enablement 工具](https://github.com/NickLiffen/ghas-enablement)，请记住，`.github/workflow` 目录没有 API 访问权限。 这意味着如果没有自动化基础的 git 客户端，则无法创建脚本。 解决方法是在具有 git 客户端的计算机或容器上利用 bash 脚本。 git 客户端可以将文件推送和拉取到 `.github/workflows` `codeql-analysis.yml` 文件所在的目录中。 {% endnote %} -It is important to not just push the `codeql-analysis.yml` file the repository's default branch. Using a pull request puts ownership on the development team to review and merge, allowing the development team to learn about {% data variables.product.prodname_code_scanning %} and involving the team in the process. +重要的是，不要只是将 `codeql-analysis.yml` 文件推送到存储库的默认分支。 使用拉取请求将所有权交给开发团队进行审查和合并，从而使开发团队能够了解 {% data variables.product.prodname_code_scanning %} 并让团队参与该过程。 -You should capture the pull request URLs created by automation, and check each week for any activity and see which ones are closed. After a few weeks, it may be worth creating another issue or sending internal emails if the pull request remains unmerged. +您应该捕获由自动化创建的拉取请求 URL，每周检查是否有任何活动，并查看哪些活动已关闭。 几周后，如果拉取请求仍未合并，则可能值得创建另一个问题或发送内部电子邮件。 -### Creating subject matter experts +### 创建主题专家 -You can then proceed to the next stage of enablement, which is creating internal subject matter experts (or SMEs) and arranging company meetings. Opening pull requests and issues in repositories will likely tackle a large percentage of your adoption, but this doesn’t tackle one-off use cases where a specific build process, framework, or library needs specific feature flags to be enabled. A more personalized and hands-on approach is required to push high adoption, especially for Java, C, and C++. +然后，您可以进入启用的下一阶段，即创建内部主题专家（或 SME）并安排公司会议。 在存储库中打开拉取请求和议题可能要处理很大比例的采用，但这并不能解决特定构建过程，框架或库需要启用特定功能标志的一次性用例。 需要一种更加个性化和动手实践的方法来推动高采用率，特别是对于Java、C 和 C++。 -It’s a good idea to run regular company meetings on specific topics to educate and discuss the rollout with a larger group. This is much more time-efficient for an enterprise with thousands of repositories compared to working with one team at a time. Teams can come to sessions that are relevant to them. Some example sessions that have been run before include: +定期就特定主题召开公司会议是个好主意，以便与更大的团队进行教育和讨论。 对于拥有数千个存储库的企业来说，与一次与一个团队合作相比，这要省时得多。 团队可以参加与他们相关的会议。 以前运行的一些示例会话包括： - 容器中的 {% data variables.product.prodname_code_scanning_capc %} - {% data variables.product.prodname_code_scanning_capc %} & Java Struts - {% data variables.product.prodname_code_scanning_capc %} & JSP -You can use the data you have collected about the distribution of different languages among repositories to create targeted meetings. +您可以使用收集的有关存储库中不同语言分布的数据来创建目标会议。 {% note %} -For the next article in this series, see "[Phase 6: Rollout and scale secret scanning](/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning)." +有关本系列的下一篇文章，请参阅“[第 6 阶段：推出和扩展机密扫描](/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning)”。 {% endnote %} diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md index ee58926bcf..a66a670f5f 100644 --- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md +++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md @@ -1,25 +1,25 @@ --- title: 'Phase 6: Rollout and scale secret scanning' -intro: 'For the final phase, you will focus on the rollout of {% data variables.product.prodname_secret_scanning %}. {% data variables.product.prodname_secret_scanning_caps %} is a more straightforward tool to rollout than {% data variables.product.prodname_code_scanning %}, as it involves less configuration, but it''s critical to have a strategy for handling new and old results.' +intro: "For the final phase, you will focus on the rollout of {% data variables.product.prodname_secret_scanning %}. {% data variables.product.prodname_secret_scanning_caps %} is a more straightforward tool to rollout than {% data variables.product.prodname_code_scanning %}, as it involves less configuration, but it's critical to have a strategy for handling new and old results." versions: ghes: '*' ghae: '*' ghec: '*' topics: - Advanced Security -shortTitle: 6. Rollout secret scanning +shortTitle: '6. Rollout secret scanning' miniTocMaxHeadingLevel: 3 --- {% note %} -本文是关于大规模采用 {% data variables.product.prodname_GH_advanced_security %} 系列文章的一部分。 For the previous article in this series, see "[Phase 5: Rollout and scale code scanning](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)." +This article is part of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. For the previous article in this series, see "[Phase 5: Rollout and scale code scanning](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)." {% endnote %} -You can enable secret scanning for individual repositories or for all repositories in an organization. 更多信息请参阅“[管理仓库的安全性和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)”或“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 +You can enable secret scanning for individual repositories or for all repositories in an organization. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -This article explains a high-level process focusing on enabling {% data variables.product.prodname_secret_scanning %} for all repositories in an organization. The principles described in this article can still be applied even if you take a more staggered approach of enabling {% data variables.product.prodname_secret_scanning %} for individual repositories. +This article explains a high-level process focusing on enabling {% data variables.product.prodname_secret_scanning %} for all repositories in an organization. The principles described in this article can still be applied even if you take a more staggered approach of enabling {% data variables.product.prodname_secret_scanning %} for individual repositories. ### 1. Focus on newly committed secrets @@ -31,10 +31,10 @@ There are a few approaches for tackling newly committed credentials, but one exa 2. **Follow Up**: Create a high-level remediation process that works for all secret types. For example, you could contact the developer who committed the secret and their technical lead on that project, highlighting the dangers of committing secrets to GitHub, and asking the them to revoke, and update the detected secret. {% note %} - + **Note:** You can automate this step. For large enterprises and organizations with hundreds of repositories, manually following up is unsustainable. You could incorporate automation into the webhook process defined in the first step. The webhook payload contains repository and organization information about the leaked secret. Using this information, you can contact the current maintainers on the repository and create a email/message to the responsible people or open an issue. - - {% endnote %} + + {% endnote %} 3. **Educate**: Create an internal training document assigned to the developer who committed the secret. Within this training document, you can explain the risks created by committing secrets and direct them to your best practice information about using secrets securely in development. If the a developer doesn't learn from the experience and continues to commit secrets, you could create an escalation process, but education usually works well. Repeat the last two steps for any new secrets leaked. This process encourages developers to take responsibility for managing the secrets used in their code securely, and allows you to measure the reduction in newly committed secrets. @@ -54,33 +54,33 @@ How you define your most critical secrets will depend on your organization's pro Once you have decided on the secret types, you can do the following: 1. Define a process for remediating each type of secret. The actual procedure for each secret type is often drastically different. Write down the process for each type of secret in a document or internal knowledge base. - + {% note %} - + **Note:** When you create the process for revoking secrets, try and give the responsibility for revoking secrets to the team maintaining the repository instead of a central team. One of the principles of GHAS is developers taking ownership of security and having the responsibility of fixing security issues, especially if they have created them. {% endnote %} 2. When you have created the process that teams will follow for revoking credentials, you can collate information about the types of secrets and other metadata associated with the leaked secrets so you can discern who to communicate the new process to. - + {% ifversion not ghae %} - + You can use the security overview to collect this information. For more information about using the security overview, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)." - + {% endif %} - + Some information you may want to collect includes: - - - 组织 - - 仓库 - - 密钥类型 + + - Organization + - Repository + - Secret type - Secret value - Maintainers on repository to contact - + {% note %} - + **Note:** Use the UI if you have few secrets leaked of that type. If you have hundreds of leaked secrets, use the API to collect information. For more information, see "[Secret scanning REST API](/rest/reference/secret-scanning)." - + {% endnote %} 3. After you collect information about leaked secrets, create a targeted communication plan for the users who maintain the repositories affected by each secret type. You could use email, messaging, or even create GitHub issues in the affected repositories. If you can use APIs provided by these tools to send out the communications in an automated manner, this will make it easier for you to scale across multiple secret types. @@ -89,11 +89,11 @@ Once you have decided on the secret types, you can do the following: You can now expand beyond the five most critical secret types into a more comprehensive list, with an additional focus on education. You can repeat the previous step, remediating previously committed secrets, for the different secret types you have targeted. -You can also include more of the custom patterns collated in the earlier phases and invite security teams and developer teams to submit more patterns, establishing a process for submitting new patterns as new secret types are created. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”。 +You can also include more of the custom patterns collated in the earlier phases and invite security teams and developer teams to submit more patterns, establishing a process for submitting new patterns as new secret types are created. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% ifversion secret-scanning-push-protection %} -You can also enable push protection with secret scanning. Once enabled, secret scanning checks pushes for high-confidence secrets and blocks the push. 更多信息请参阅“[使用机密扫描保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)”。 +You can also enable push protection with secret scanning. Once enabled, secret scanning checks pushes for high-confidence secrets and blocks the push. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)." {% endif %} @@ -103,4 +103,4 @@ As you continue to build your remediation processes for other secret types, star This is the final article of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. If you have questions or need support, see the section on {% data variables.contact.github_support %} and {% data variables.product.prodname_professional_services_team %} in "[Introduction to adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale#github-support-and-professional-services)." -{% endnote %} +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md index 6c2ce17f5e..158d08df6b 100644 --- a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md @@ -1,8 +1,8 @@ --- title: 关于安全概述 intro: 您可以在一个位置查看、筛选和排序组织或团队拥有的存储库的安全警报：“安全概述”页。 -permissions: '{% data reusables.security-center.permissions %}' -product: '{% data reusables.gated-features.security-center %}' +permissions: '{% data reusables.security-overview.permissions %}' +product: '{% data reusables.gated-features.security-overview %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: @@ -23,7 +23,7 @@ shortTitle: 关于安全概述 --- {% ifversion ghes < 3.5 or ghae %} -{% data reusables.security-center.beta %} +{% data reusables.security-overview.beta %} {% endif %} ## 关于安全概述 diff --git a/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index b3467d793d..e20d8f2f8d 100644 --- a/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -1,8 +1,8 @@ --- title: 筛选安全性概述中的警报 intro: 使用筛选器查看特定类别的警报 -permissions: '{% data reusables.security-center.permissions %}' -product: '{% data reusables.gated-features.security-center %}' +permissions: '{% data reusables.security-overview.permissions %}' +product: '{% data reusables.gated-features.security-overview %}' versions: ghae: '*' ghes: '*' @@ -18,7 +18,7 @@ shortTitle: 筛选警报 --- {% ifversion ghes < 3.5 or ghae %} -{% data reusables.security-center.beta %} +{% data reusables.security-overview.beta %} {% endif %} ## 关于筛选安全性概述 diff --git a/translations/zh-CN/content/code-security/security-overview/index.md b/translations/zh-CN/content/code-security/security-overview/index.md index 720d4f4c94..29c5cfe947 100644 --- a/translations/zh-CN/content/code-security/security-overview/index.md +++ b/translations/zh-CN/content/code-security/security-overview/index.md @@ -2,7 +2,7 @@ title: 查看组织中仓库的安全警报 shortTitle: 安全概述 intro: 在一个位置查看、排序和过滤整个组织的安全警报。 -product: '{% data reusables.gated-features.security-center %}' +product: '{% data reusables.gated-features.security-overview %}' versions: fpt: '*' ghae: '*' diff --git a/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md index 72eb60765b..e095481513 100644 --- a/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md @@ -1,8 +1,8 @@ --- title: 查看安全性概述 intro: 导航到安全概述中可用的不同视图 -permissions: '{% data reusables.security-center.permissions %}' -product: '{% data reusables.gated-features.security-center %}' +permissions: '{% data reusables.security-overview.permissions %}' +product: '{% data reusables.gated-features.security-overview %}' versions: ghae: issue-5503 ghes: '*' @@ -18,7 +18,7 @@ shortTitle: 查看安全性概述 --- {% ifversion ghes < 3.5 or ghae %} -{% data reusables.security-center.beta %} +{% data reusables.security-overview.beta %} {% endif %} ## 查看组织的安全概述 diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md index 35cf3cda24..3f1eb6c4c7 100644 --- a/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md @@ -40,7 +40,7 @@ topics: 您可以在管理版本时手动创建发行说明。 或者，您可以从默认模板自动生成发行说明，或自定义您自己的发行说明模板。 更多信息请参阅“[自动生成的发行说明](/repositories/releasing-projects-on-github/automatically-generated-release-notes)”。 {% endif %} -{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7054 %} +{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7054 %} 查看发行版的详细信息时，每个发行版资产的创建日期显示在发行版资产旁边。 {% endif %} diff --git a/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md b/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md index c9590fdb76..7e32fc51c4 100644 --- a/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md +++ b/translations/zh-CN/content/support/learning-about-github-support/about-github-support.md @@ -58,9 +58,14 @@ For more information, see "[About GitHub Premium Support](/support/about-github- {% endif %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghae %} -Before contacting {% data variables.contact.github_support %}, check if there are currently any incidents affecting services on {% data variables.product.prodname_dotcom %} on [{% data variables.product.prodname_dotcom %} Status](https://www.githubstatus.com/). For more information, see "[About GitHub status](#about-github-status)." +Before contacting {% data variables.contact.github_support %}, check if there are currently any incidents affecting services on {% data variables.product.product_name %} on +{%- ifversion fpt or ghec %} +[{% data variables.product.prodname_dotcom %} Status](https://githubstatus.com/) +{%- elsif ghae %} +[{% data variables.product.product_name %} Status](https://ghestatus.com/) +{%- endif %}. For more information, see "[About GitHub status](#about-github-status)." {% endif %} @@ -94,12 +99,12 @@ Email communication from GitHub Support will always be sent from either a `githu {% data reusables.support.scope-of-support %} -{% ifversion ghec or fpt %} +{% ifversion ghec or fpt or ghae %} ## About GitHub status -You can check for any incidents currently affecting {% data variables.product.prodname_dotcom %} services and view information about past incidents on {% data variables.product.prodname_dotcom %}'s [Status page](https://www.githubstatus.com/). +You can check for any incidents currently affecting {% data variables.product.product_name %} services and view information about past incidents on {% data variables.product.prodname_dotcom %}'s [Status page]({% ifversion fpt or ghec %}https://githubstatus.com{% elsif ghae %}https://ghestatus.com{% endif %}). -You can also subscribe and get alerted via email, text message, and webhook whenever there's an incident affecting {% data variables.product.prodname_dotcom %}. +You can also subscribe and get alerted via email, text message, and webhook whenever there's an incident affecting {% data variables.product.product_name %}. {% endif %} diff --git a/translations/zh-CN/data/features/README.md b/translations/zh-CN/data/features/README.md index 71856170a4..5fc6785125 100644 --- a/translations/zh-CN/data/features/README.md +++ b/translations/zh-CN/data/features/README.md @@ -34,14 +34,7 @@ versions: feature: 'meow' ``` -如果您希望内容文件应用于多个功能，您可以执行以下功能： - -```yaml -versions: - fpt: '*' - ghes: '>3.1' - feature: ['meow', 'blorp'] -``` +You cannot use `feature:` to specify multiple concurrent versions, as this is not supported. Alternatively, you could create a new feature-based versioning file with the required versioning. ## 架构执行 diff --git a/translations/zh-CN/data/features/enterprise-owner-join-org.yml b/translations/zh-CN/data/features/enterprise-owner-join-org.yml index 847a54f8b5..3003576388 100644 --- a/translations/zh-CN/data/features/enterprise-owner-join-org.yml +++ b/translations/zh-CN/data/features/enterprise-owner-join-org.yml @@ -1,5 +1,5 @@ --- versions: ghec: '*' - ghes: '>=3.5' + ghes: '>=3.6' ghae: 'issue-5740' diff --git a/translations/zh-CN/data/features/pr-tree-view.yml b/translations/zh-CN/data/features/pr-tree-view.yml index 16e98ac47b..6476b43762 100644 --- a/translations/zh-CN/data/features/pr-tree-view.yml +++ b/translations/zh-CN/data/features/pr-tree-view.yml @@ -4,5 +4,5 @@ versions: fpt: '*' ghec: '*' - ghes: '>=3.5' + ghes: '>=3.6' ghae: 'issue-5892' diff --git a/translations/zh-CN/data/features/remove-enterprise-members.yml b/translations/zh-CN/data/features/remove-enterprise-members.yml index a9ef5be6d6..597a17142b 100644 --- a/translations/zh-CN/data/features/remove-enterprise-members.yml +++ b/translations/zh-CN/data/features/remove-enterprise-members.yml @@ -1,5 +1,4 @@ --- versions: ghec: '*' - ghes: '>=3.5' ghae: 'issue-5739' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml index 8ea8cfb702..99cde4f5bf 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -185,37 +185,37 @@ sections: - | GitHub Advanced Security 客户现在可以通过 UI 和 API 为存档的存储库启用机密扫描。更多信息请参阅 REST API 文档中的“[关于机密扫描](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)”、“[关于存档的存储库](/repositories/archiving-a-github-repository/archiving-repositories)”和“[Repositories](/rest/repos/repos#update-a-repository)”。 - - heading: Secret scanning webhooks for alert locations + heading: 警报位置的机密扫描 web 挂钩 notes: - | - GitHub Advanced Security customers using secret scanning can now opt to receive a webhook each time a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)." + 使用机密扫描的 GitHub Advanced Security 客户现在可以选择在新位置检测到机密时接收 web 挂钩。“secret_scanning_alert_location”web 挂钩事件包括位置详细信息（如提交 SHA）和检测的关联警报。将为包含检测到的机密的每个新文件路径创建一个位置。更多信息请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)”。 - - heading: View Dependabot alerts across an organization + heading: 查看整个组织的 Dependabot 警报 notes: - | - GitHub Advanced Security customers can now view Dependabot alerts in in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + GitHub Advanced Security 客户现在可以在组织的“**Security（安全）**”选项卡中查看 Dependabot 警报。此视图可供具有 [安全管理员角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization) 的组织所有者和团队成员使用。更多信息请参阅“[关于安全性概述](/code-security/security-overview/about-the-security-overview)”。 - - heading: Configure permissions for Dependabot alerts with custom repository roles + heading: 使用自定义存储库角色配置 Dependabot 警报的权限 notes: - | - You can now configure two new permissions for Dependabot alerts when managing custom repository roles. + 现在，您可以在管理自定义存储库角色时为 Dependabot 警报配置两个新权限。 - - View Dependabot alerts - - Dismiss or reopen Dependabot alerts + - + 查看 Dependabot 警报 - - For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + 关闭或重新打开 Dependabot 警报 有关更多信息，请参阅“[管理组织的自定义存储库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 - - heading: Reopen dismissed Dependabot alerts + heading: 重新打开忽略的 Dependabot 警报 notes: - | - You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + 现在，您可以通过已关闭警报的 UI 页面重新打开已消除的 Dependabot 警报。这不会影响 Dependabot 拉取请求或 GraphQL API。更多信息请参阅“[关于 Dependabot 警报](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)”。 - - heading: Pub support for Dependabot version updates is in public beta + heading: 对 Dependabot 版本更新的发布支持已公开测试 notes: - | - Users of Dependabot version updates can now proactively update dependencies for Flutter or Dart projects that use the Pub package manager. + Dependabot 版本更新的用户现在可以主动更新使用 Pub 包管理器的 Flutter 或 Dart 项目的依赖项。 - To test [version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates) on your own Dart or Flutter repository, add the following configuration file in [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates). Note the `package-ecosystem: "pub"` and `enable-beta-ecosystems: true` flags. + 要在您自己的 Dart 或 Flutter 存储库上测试 [版本更新](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)，请在 [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates) 中添加以下配置文件。请注意“包生态系统：”pub“和”enable-beta-ecosystems: true“标志。 ```yaml version: 2 enable-beta-ecosystems: true @@ -226,95 +226,95 @@ sections: interval: "weekly" ``` - - heading: See pull request associated with a repository's Dependabot alerts via GraphQL API + heading: 通过 GraphQL API 查看与存储库的 Dependabot 警报关联的拉取请求 notes: - | - The new `DependabotUpdate` GraphQL object lets you view information about what happens to your repository's security updates. When GitHub Enterprise Server detects that a dependency in your repository is vulnerable, Dependabot will attempt to open a pull request to update that dependency to a non-vulnerable version. You can now see the pull request that fixes the vulnerability. In some cases, Dependabot fails to open a pull request. Previously, the error message that Dependabot generated was only visible in the "Dependabot Alerts" section of the **Security** tab. Now, if Dependabot runs into an error when trying to open a pull request for a security alert, you can determine the reason using the GraphQL API. For more information, see "[Objects](/graphql/reference/objects#dependabotupdate)" in the GraphQL API documentation. + 新的“DependabotUpdate”GraphQL 对象允许您查看有关存储库安全更新发生的情况的信息。当 GitHub Enterprise Server 检测到存储库中的依赖项有漏洞时，Dependabot 将尝试打开拉取请求以将该依赖项更新为无漏洞的版本。现在，您可以看到修复漏洞的拉取请求。在某些情况下，Dependabot 无法打开拉取请求。以前，Dependabot 生成的错误消息仅在“安全”选项卡的“Dependabot 警报”部分可见。现在，如果 Dependabot 在尝试打开安全警报的拉取请求时遇到错误，您可以使用 GraphQL API 确定原因。更多信息请参阅 GraphQL API 文档中的“[Objects](/graphql/reference/objects#dependabotupdate)”。 - - heading: Access more information about Dependabot alerts via GraphQL API + heading: 通过 GraphQL API 访问有关 Dependabot 警报的更多信息 notes: - | - You can now view fixed alerts from Dependabot with the GraphQL API. You can also access and filter by state, as well as by unique numeric identifier, and you can filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`. + 现在，您可以使用 GraphQL API 查看来自 Dependabot 的固定警报。还可以按状态和唯一数字标识符进行访问和筛选，并且可以按漏洞警报对象的状态进行筛选。“RepositoryVulnerabilityAlert”的以下字段现在存在。 - `number` - `fixed_at` - `fix_reason` - `state` - For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation. + 更多信息请参阅 GraphQL API 文档中的“[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)”。 - - heading: Git events in the enterprise audit log + heading: 企业审核日志中的 Git 事件 notes: - | - The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV. + 以下与 Git 相关的事件现在可以显示在企业审核日志中。如果启用该功能并设置审核日志保留期，则新事件将可用于通过 UI 和 API 进行搜索，或通过 JSON 或 CSV 导出。 - - `git.clone` - - `git.fetch` - - `git.push` + - 'git.clone' + - 'git.fetch' + - 'git.push' - Due to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" and "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)." + 由于记录了大量的 Git 事件，我们建议您监控实例的文件存储并查看相关的警报配置。有关详细信息，请参阅“[企业的审核日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)”和“[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)”。 - - heading: Improvements to CODEOWNERS + heading: 对 CODEOWNERS 的改进 notes: - | - This release includes improvements to CODEOWNERS. + 此版本包括对 CODEOWNERS 的改进。 - - Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation. - - After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review. - - Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines. + - 现在，从 Web 查看 CODEOWNERS 文件时会出现语法错误。以前，当 CODEOWNERS 文件中的某一行出现语法错误时，该错误将被忽略，或者在某些情况下会导致整个 CODEOWNERS 文件无法加载。GitHub 应用程序和操作可以使用新的 REST 和 GraphQL API 访问相同的错误列表。有关更多信息，请参阅 REST API 文档中的“[Repositories]（/rest/repos/repos#list-codeowners-errors）”或 GraphQL API 文档中的“[Objects](/graphql/reference/objects#repositorycodeowners)”。 + - 在某人创建新的拉取请求或将新更改推送到草稿拉取请求后，将请求审阅的任何代码所有者现在都列在“审阅者”下的拉取请求中。此功能可让您提前了解在拉取请求标记为已准备好进行审核后，将请求审阅的人员。 + - CODEOWNERS 文件中的注释现在可以出现在一行的末尾，而不仅仅是在专用行上。 - For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)." + 有关更多信息，请参阅“[关于代码所有者](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)”。 - - heading: More ways to keep a pull request's topic branch up to date + heading: 使拉取请求的主题分支保持最新状态的更多方法 notes: - | - The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date. + 通过拉取请求页面上的**Update branch（更新分支）**按钮，您可以使用基本分支中的最新更改来更新拉取请求的分支。这对于在合并之前验证更改是否与基本分支的当前版本兼容非常有用。现在，两项增强功能为您提供了更多方法来使您的分支保持最新状态。 - - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)." + - 当拉取请求的主题分支与基本分支一起过期时，您现在可以选择通过重新基于最新版本的基础分支来更新它。重新定基将分支中的更改应用到基本分支的最新版本，从而生成具有线性历史记录的分支，因为不会创建合并提交。若要通过变基进行更新，请单击**Update branch（更新分支）**按钮旁边的下拉菜单，单击**Update with rebase（使用变基更新）**，然后单击**Rebase branch（变基分支）**。以前，**Update branch（更新分支）**执行了传统的合并，该合并始终导致拉取请求分支中的合并提交。此选项仍然可用，但现在您可以选择。更多信息请参阅“[保持您的拉取请求与基本分支同步](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)”。 - - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)." + - 新的存储库设置允许**Update branch（更新分支）**按钮在拉取请求的主题分支与基本分支不是最新的时始终可用。以前，仅当启用了**Require branches to be up to date before merging（要求分支在合并之前保持最新）**分支保护设置时，此按钮才可用。具有管理员或维护者访问权限的人员可以从存储库设置中的**Pull Requests（拉取请求）**部分中管理**Always suggest updating pull request branches（始终建议更新拉取请求分支）**设置。更多信息请参阅“[管理更新拉取请求分支的建议](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)”。 - - heading: Configure custom HTTP headers for GitHub Pages sites + heading: 为 GitHub Pages 网站配置自定义 HTTP 标头 notes: - | - You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see "[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)." + 现在，您可以配置自定义 HTTP 标头，这些标头适用于 GitHub 企业服务器实例提供的所有 GitHub Pages 站点。更多信息请参阅“[为您的企业配置 GitHub 页面](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)”。 - - heading: Ignore commits in blame view + heading: 在追溯视图中忽略提交 notes: - | - It's now possible to ignore revisions in the blame view by creating a _.git-blame-ignore-revs_ file in the root of your repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)." + 现在，通过在存储库的根目录中创建 _.git-blame-ignore-revs_ 文件，可以忽略责备视图中的修订。更多信息请参阅“[查看文件](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)”。 - - heading: Light high contrast theme is generally available + heading: 浅色高对比度主题已正式发布 notes: - | - A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. 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)." + 现在，前景和背景元素之间对比度更高的浅色高对比度主题现已正式发布。更多信息请参阅“[管理您的主题设置](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)”。 - heading: 标记保护规则 notes: - | - Repository owners can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with the Maintain or Admin role in the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." + 存储库所有者现在可以配置标签保护规则来保护存储库的标签。受标记保护规则保护后，与指定名称模式匹配的标签只能由存储库中具有“维护”或“管理员”角色的用户创建和删除。更多信息请参阅“[配置标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)”。 bugs: - | - It is now possible for GitHub Apps to upload release assets. + GitHub 应用程序现在可以上传发布资产。 changes: - | - To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." + 要将设备授权流用于 OAuth 和 GitHub 应用程序，必须手动启用该功能。此更改通过确保集成商了解风险并有意识地选择支持这种形式的身份验证，降低了在针对 GitHub 企业服务器用户的网络钓鱼攻击中使用应用的可能性。如果您拥有或管理 OAuth 应用程序或 GitHub 应用程序，并且想要使用设备流，则可以通过应用的设置页为您的应用程序启用它。设备流 API 端点将使用状态代码“400”响应尚未启用此功能的应用程序。更多信息请参阅“[授权 OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)”。 - | - The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into your code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)." + 代码扫描警报页现在始终显示默认分支的警报状态和信息。侧边栏中有一个新的“受影响的分支”面板，您可以在其中查看其他分支中的警报状态。如果默认分支中不存在警报，则警报页面将显示上次看到警报的位置的状态为“分支中”或“拉取请求中”。通过此改进，可以更轻松地了解已引入到代码库中的警报的状态。更多令牌请参阅“[关于代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)”。 - The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation. + 警报列表页不会更改，可以按“分支”进行筛选。可以使用代码扫描 API 检索更详细的警报分支信息。更多信息请参阅 REST API 文档中的“[代码扫描](/rest/code-scanning)”。 - | - Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. You can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)." + 代码扫描现在显示警报的分析来源的详细信息。如果警报具有多个分析源，则会显示在“受影响的分支”边栏和警报时间线中。您可以将鼠标悬停在“受影响的分支”边栏中的分析源图标上，以查看每个分析源中的警报状态。如果警报只有一个分析源，则警报页面上不会显示有关分析源的信息。这些改进将使人们更容易理解警报。特别是，它将帮助您了解具有多个分析源的那些。这对于具有多个分析配置的设置（如单存储库）特别有用。更多令牌请参阅“[关于代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)”。 - | - Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories. + 用户或组织拥有的存储库列表现在具有附加的筛选器选项“模板”，以便更轻松地查找模板存储库。 - | - GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)." + GitHub Enterprise Server 可以显示几种常见的图像格式，包括 PNG、JPG、GIF、PSD 和 SVG，并提供多种方法来比较版本之间的差异。现在，在拉取请求中查看添加或更改的图像时，默认情况下会显示这些图像的预览。以前，您会看到一条消息，表示无法显示二进制文件，您需要切换“显示多差异”选项。更多信息请参阅“[使用非代码文件](/repositories/working-with-files/using-files/working-with-non-code-files)”。 - | - New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)." + 现在，将使用默认分支名称“main”或用户设置中定义的备用默认分支名称创建新 gist。这与在 GitHub Enterprise Server 上创建其他存储库的方式相匹配。更多信息请参阅“[关于分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)”和“[管理存储库的默认分支名称](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)”。 - | - Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)." + Gists 现在只在首次显示时显示 30 条最新评论。您可以单击“**加载较早的评论...**”以查看更多内容。这允许具有许多注释的要点更快地显示。更多信息请参阅“[使用 gist 编辑和共享内容](/get-started/writing-on-github/editing-and-sharing-content-with-gists)”。 - | - Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/). + 重新设计了用户、组织、存储库和团队的设置页面，将类似的设置页面分组为多个部分，以改进信息体系结构和可发现性。更多信息请参阅 [GitHub 变更日志](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/)。 - | Focusing or hovering over a label now displays the label description in a tooltip. - | diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0.yml index 91b54f033e..024f084fa0 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0.yml @@ -178,37 +178,37 @@ sections: - | GitHub Advanced Security 客户现在可以通过 UI 和 API 为存档的存储库启用机密扫描。更多信息请参阅 REST API 文档中的“[关于机密扫描](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)”、“[关于存档的存储库](/repositories/archiving-a-github-repository/archiving-repositories)”和“[Repositories](/rest/repos/repos#update-a-repository)”。 - - heading: Secret scanning webhooks for alert locations + heading: 警报位置的机密扫描 web 挂钩 notes: - | - GitHub Advanced Security customers using secret scanning can now opt to receive a webhook each time a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)." + 使用机密扫描的 GitHub Advanced Security 客户现在可以选择在新位置检测到机密时接收 web 挂钩。“secret_scanning_alert_location”web 挂钩事件包括位置详细信息（如提交 SHA）和检测的关联警报。将为包含检测到的机密的每个新文件路径创建一个位置。更多信息请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)”。 - - heading: View Dependabot alerts across an organization + heading: 查看整个组织的 Dependabot 警报 notes: - | - GitHub Advanced Security customers can now view Dependabot alerts in in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + GitHub Advanced Security 客户现在可以在组织的“**Security（安全）**”选项卡中查看 Dependabot 警报。此视图可供具有 [安全管理员角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization) 的组织所有者和团队成员使用。更多信息请参阅“[关于安全性概述](/code-security/security-overview/about-the-security-overview)”。 - - heading: Configure permissions for Dependabot alerts with custom repository roles + heading: 使用自定义存储库角色配置 Dependabot 警报的权限 notes: - | - You can now configure two new permissions for Dependabot alerts when managing custom repository roles. + 现在，您可以在管理自定义存储库角色时为 Dependabot 警报配置两个新权限。 - - View Dependabot alerts - - Dismiss or reopen Dependabot alerts + - + 查看 Dependabot 警报 - - For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + 关闭或重新打开 Dependabot 警报 有关更多信息，请参阅“[管理组织的自定义存储库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 - - heading: Reopen dismissed Dependabot alerts + heading: 重新打开忽略的 Dependabot 警报 notes: - | - You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + 现在，您可以通过已关闭警报的 UI 页面重新打开已消除的 Dependabot 警报。这不会影响 Dependabot 拉取请求或 GraphQL API。更多信息请参阅“[关于 Dependabot 警报](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)”。 - - heading: Pub support for Dependabot version updates is in public beta + heading: 对 Dependabot 版本更新的发布支持已公开测试 notes: - | - Users of Dependabot version updates can now proactively update dependencies for Flutter or Dart projects that use the Pub package manager. + Dependabot 版本更新的用户现在可以主动更新使用 Pub 包管理器的 Flutter 或 Dart 项目的依赖项。 - To test [version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates) on your own Dart or Flutter repository, add the following configuration file in [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates). Note the `package-ecosystem: "pub"` and `enable-beta-ecosystems: true` flags. + 要在您自己的 Dart 或 Flutter 存储库上测试 [版本更新](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)，请在 [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates) 中添加以下配置文件。请注意“包生态系统：”pub“和”enable-beta-ecosystems: true“标志。 ```yaml version: 2 enable-beta-ecosystems: true @@ -219,76 +219,76 @@ sections: interval: "weekly" ``` - - heading: See pull request associated with a repository's Dependabot alerts via GraphQL API + heading: 通过 GraphQL API 查看与存储库的 Dependabot 警报关联的拉取请求 notes: - | - The new `DependabotUpdate` GraphQL object lets you view information about what happens to your repository's security updates. When GitHub Enterprise Server detects that a dependency in your repository is vulnerable, Dependabot will attempt to open a pull request to update that dependency to a non-vulnerable version. You can now see the pull request that fixes the vulnerability. In some cases, Dependabot fails to open a pull request. Previously, the error message that Dependabot generated was only visible in the "Dependabot Alerts" section of the **Security** tab. Now, if Dependabot runs into an error when trying to open a pull request for a security alert, you can determine the reason using the GraphQL API. For more information, see "[Objects](/graphql/reference/objects#dependabotupdate)" in the GraphQL API documentation. + 新的“DependabotUpdate”GraphQL 对象允许您查看有关存储库安全更新发生的情况的信息。当 GitHub Enterprise Server 检测到存储库中的依赖项有漏洞时，Dependabot 将尝试打开拉取请求以将该依赖项更新为无漏洞的版本。现在，您可以看到修复漏洞的拉取请求。在某些情况下，Dependabot 无法打开拉取请求。以前，Dependabot 生成的错误消息仅在“安全”选项卡的“Dependabot 警报”部分可见。现在，如果 Dependabot 在尝试打开安全警报的拉取请求时遇到错误，您可以使用 GraphQL API 确定原因。更多信息请参阅 GraphQL API 文档中的“[Objects](/graphql/reference/objects#dependabotupdate)”。 - - heading: Access more information about Dependabot alerts via GraphQL API + heading: 通过 GraphQL API 访问有关 Dependabot 警报的更多信息 notes: - | - You can now view fixed alerts from Dependabot with the GraphQL API. You can also access and filter by state, as well as by unique numeric identifier, and you can filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`. + 现在，您可以使用 GraphQL API 查看来自 Dependabot 的固定警报。还可以按状态和唯一数字标识符进行访问和筛选，并且可以按漏洞警报对象的状态进行筛选。“RepositoryVulnerabilityAlert”的以下字段现在存在。 - `number` - `fixed_at` - `fix_reason` - `state` - For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation. + 更多信息请参阅 GraphQL API 文档中的“[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)”。 - - heading: Git events in the enterprise audit log + heading: 企业审核日志中的 Git 事件 notes: - | - The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV. + 以下与 Git 相关的事件现在可以显示在企业审核日志中。如果启用该功能并设置审核日志保留期，则新事件将可用于通过 UI 和 API 进行搜索，或通过 JSON 或 CSV 导出。 - - `git.clone` - - `git.fetch` - - `git.push` + - 'git.clone' + - 'git.fetch' + - 'git.push' - Due to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" and "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)." + 由于记录了大量的 Git 事件，我们建议您监控实例的文件存储并查看相关的警报配置。有关详细信息，请参阅“[企业的审核日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)”和“[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)”。 - - heading: Improvements to CODEOWNERS + heading: 对 CODEOWNERS 的改进 notes: - | - This release includes improvements to CODEOWNERS. + 此版本包括对 CODEOWNERS 的改进。 - - Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation. - - After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review. - - Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines. + - 现在，从 Web 查看 CODEOWNERS 文件时会出现语法错误。以前，当 CODEOWNERS 文件中的某一行出现语法错误时，该错误将被忽略，或者在某些情况下会导致整个 CODEOWNERS 文件无法加载。GitHub 应用程序和操作可以使用新的 REST 和 GraphQL API 访问相同的错误列表。有关更多信息，请参阅 REST API 文档中的“[Repositories]（/rest/repos/repos#list-codeowners-errors）”或 GraphQL API 文档中的“[Objects](/graphql/reference/objects#repositorycodeowners)”。 + - 在某人创建新的拉取请求或将新更改推送到草稿拉取请求后，将请求审阅的任何代码所有者现在都列在“审阅者”下的拉取请求中。此功能可让您提前了解在拉取请求标记为已准备好进行审核后，将请求审阅的人员。 + - CODEOWNERS 文件中的注释现在可以出现在一行的末尾，而不仅仅是在专用行上。 - For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)." + 有关更多信息，请参阅“[关于代码所有者](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)”。 - - heading: More ways to keep a pull request's topic branch up to date + heading: 使拉取请求的主题分支保持最新状态的更多方法 notes: - | - The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date. + 通过拉取请求页面上的**Update branch（更新分支）**按钮，您可以使用基本分支中的最新更改来更新拉取请求的分支。这对于在合并之前验证更改是否与基本分支的当前版本兼容非常有用。现在，两项增强功能为您提供了更多方法来使您的分支保持最新状态。 - - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)." + - 当拉取请求的主题分支与基本分支一起过期时，您现在可以选择通过重新基于最新版本的基础分支来更新它。重新定基将分支中的更改应用到基本分支的最新版本，从而生成具有线性历史记录的分支，因为不会创建合并提交。若要通过变基进行更新，请单击**Update branch（更新分支）**按钮旁边的下拉菜单，单击**Update with rebase（使用变基更新）**，然后单击**Rebase branch（变基分支）**。以前，**Update branch（更新分支）**执行了传统的合并，该合并始终导致拉取请求分支中的合并提交。此选项仍然可用，但现在您可以选择。更多信息请参阅“[保持您的拉取请求与基本分支同步](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)”。 - - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)." + - 新的存储库设置允许**Update branch（更新分支）**按钮在拉取请求的主题分支与基本分支不是最新的时始终可用。以前，仅当启用了**Require branches to be up to date before merging（要求分支在合并之前保持最新）**分支保护设置时，此按钮才可用。具有管理员或维护者访问权限的人员可以从存储库设置中的**Pull Requests（拉取请求）**部分中管理**Always suggest updating pull request branches（始终建议更新拉取请求分支）**设置。更多信息请参阅“[管理更新拉取请求分支的建议](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)”。 - - heading: Configure custom HTTP headers for GitHub Pages sites + heading: 为 GitHub Pages 网站配置自定义 HTTP 标头 notes: - | - You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see "[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)." + 现在，您可以配置自定义 HTTP 标头，这些标头适用于 GitHub 企业服务器实例提供的所有 GitHub Pages 站点。更多信息请参阅“[为您的企业配置 GitHub 页面](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)”。 - - heading: Ignore commits in blame view + heading: 在追溯视图中忽略提交 notes: - | - It's now possible to ignore revisions in the blame view by creating a _.git-blame-ignore-revs_ file in the root of your repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)." + 现在，通过在存储库的根目录中创建 _.git-blame-ignore-revs_ 文件，可以忽略责备视图中的修订。更多信息请参阅“[查看文件](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)”。 - - heading: Light high contrast theme is generally available + heading: 浅色高对比度主题已正式发布 notes: - | - A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. 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)." + 现在，前景和背景元素之间对比度更高的浅色高对比度主题现已正式发布。更多信息请参阅“[管理您的主题设置](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)”。 - heading: 标记保护规则 notes: - | - Repository owners can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with the Maintain or Admin role in the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." + 存储库所有者现在可以配置标签保护规则来保护存储库的标签。受标记保护规则保护后，与指定名称模式匹配的标签只能由存储库中具有“维护”或“管理员”角色的用户创建和删除。更多信息请参阅“[配置标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)”。 bugs: - | - It is now possible for GitHub Apps to upload release assets. + GitHub 应用程序现在可以上传发布资产。 changes: - | Minimum requirements for root storage and memory increased for GitHub Enterprise Server 2.10 and 3.0, and are now enforced as of 3.5.0. @@ -298,23 +298,23 @@ sections: For more information, see the minimum requirements for each supported deployment platform in "[Setting up a GitHub Enterprise Server instance](/admin/installation/setting-up-a-github-enterprise-server-instance)." [Updated: 2022-06-20] - | - To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." + 要将设备授权流用于 OAuth 和 GitHub 应用程序，必须手动启用该功能。此更改通过确保集成商了解风险并有意识地选择支持这种形式的身份验证，降低了在针对 GitHub 企业服务器用户的网络钓鱼攻击中使用应用的可能性。如果您拥有或管理 OAuth 应用程序或 GitHub 应用程序，并且想要使用设备流，则可以通过应用的设置页为您的应用程序启用它。设备流 API 端点将使用状态代码“400”响应尚未启用此功能的应用程序。更多信息请参阅“[授权 OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)”。 - | - The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into your code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)." + 代码扫描警报页现在始终显示默认分支的警报状态和信息。侧边栏中有一个新的“受影响的分支”面板，您可以在其中查看其他分支中的警报状态。如果默认分支中不存在警报，则警报页面将显示上次看到警报的位置的状态为“分支中”或“拉取请求中”。通过此改进，可以更轻松地了解已引入到代码库中的警报的状态。更多令牌请参阅“[关于代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)”。 - The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation. + 警报列表页不会更改，可以按“分支”进行筛选。可以使用代码扫描 API 检索更详细的警报分支信息。更多信息请参阅 REST API 文档中的“[代码扫描](/rest/code-scanning)”。 - | - Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. You can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)." + 代码扫描现在显示警报的分析来源的详细信息。如果警报具有多个分析源，则会显示在“受影响的分支”边栏和警报时间线中。您可以将鼠标悬停在“受影响的分支”边栏中的分析源图标上，以查看每个分析源中的警报状态。如果警报只有一个分析源，则警报页面上不会显示有关分析源的信息。这些改进将使人们更容易理解警报。特别是，它将帮助您了解具有多个分析源的那些。这对于具有多个分析配置的设置（如单存储库）特别有用。更多令牌请参阅“[关于代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)”。 - | - Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories. + 用户或组织拥有的存储库列表现在具有附加的筛选器选项“模板”，以便更轻松地查找模板存储库。 - | - GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)." + GitHub Enterprise Server 可以显示几种常见的图像格式，包括 PNG、JPG、GIF、PSD 和 SVG，并提供多种方法来比较版本之间的差异。现在，在拉取请求中查看添加或更改的图像时，默认情况下会显示这些图像的预览。以前，您会看到一条消息，表示无法显示二进制文件，您需要切换“显示多差异”选项。更多信息请参阅“[使用非代码文件](/repositories/working-with-files/using-files/working-with-non-code-files)”。 - | - New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)." + 现在，将使用默认分支名称“main”或用户设置中定义的备用默认分支名称创建新 gist。这与在 GitHub Enterprise Server 上创建其他存储库的方式相匹配。更多信息请参阅“[关于分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)”和“[管理存储库的默认分支名称](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)”。 - | - Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)." + Gists 现在只在首次显示时显示 30 条最新评论。您可以单击“**加载较早的评论...**”以查看更多内容。这允许具有许多注释的要点更快地显示。更多信息请参阅“[使用 gist 编辑和共享内容](/get-started/writing-on-github/editing-and-sharing-content-with-gists)”。 - | - Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/). + 重新设计了用户、组织、存储库和团队的设置页面，将类似的设置页面分组为多个部分，以改进信息体系结构和可发现性。更多信息请参阅 [GitHub 变更日志](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/)。 - | Focusing or hovering over a label now displays the label description in a tooltip. - | diff --git a/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md b/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md index 4768b1b6ea..44bf559d24 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md @@ -1 +1,5 @@ -如果您在 {% data variables.product.product_location %}上配置了 **HTTP 代理服务器** ，则必须添加 `localhost` 和 `127.0.0.1` 到 **HTTP 代理排除** 列表中。 有关更改代理设置的更多信息，请参阅“[配置出站 Web 代理服务器](/admin/configuration/configuring-an-outbound-web-proxy-server)”。 +If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}: + - You must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. + - If the BYOS bucket is not routable, then you must also add the bucket's URL to the exclusion list. + + 有关更改代理设置的更多信息，请参阅“[配置出站 Web 代理服务器](/admin/configuration/configuring-an-outbound-web-proxy-server)”。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/jobs/about-matrix-strategy.md b/translations/zh-CN/data/reusables/actions/jobs/about-matrix-strategy.md index 46d8a1f51c..271d8d3e7d 100644 --- a/translations/zh-CN/data/reusables/actions/jobs/about-matrix-strategy.md +++ b/translations/zh-CN/data/reusables/actions/jobs/about-matrix-strategy.md @@ -1 +1 @@ -矩阵策略允许您在单个作业定义中使用变量来自动创建基于变量组合的多个作业运行。 例如，可以使用矩阵策略在一种语言的多个版本或多个操作系统上测试代码。 +A matrix strategy lets you use variables in a single job definition to automatically create multiple job runs that are based on the combinations of the variables. 例如，可以使用矩阵策略在一种语言的多个版本或多个操作系统上测试代码。 diff --git a/translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md b/translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md new file mode 100644 index 0000000000..f8ad26e219 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md @@ -0,0 +1,27 @@ +If you plan to enable {% data variables.product.prodname_actions %} for the users of your instance, more resources are required. + +{%- ifversion ghes = 3.2 %} + +{% data reusables.actions.hardware-requirements-3.2 %} + +{%- endif %} + +{%- ifversion ghes = 3.3 %} + +{% data reusables.actions.hardware-requirements-3.3 %} + +{%- endif %} + +{%- ifversion ghes = 3.4 %} + +{% data reusables.actions.hardware-requirements-3.4 %} + +{%- endif %} + +{%- ifversion ghes = 3.5 %} + +{% data reusables.actions.hardware-requirements-3.5 %} + +{%- endif %} + +For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)." diff --git a/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index aa4ac2b3e6..b8c4a7d8f3 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -8,6 +8,10 @@ We recommend different hardware configurations depending on the number of user l {% data reusables.enterprise_installation.hardware-rec-table %} +{% data reusables.actions.more-resources-for-ghes %} + +{% data reusables.enterprise_installation.about-adjusting-resources %} + ### Storage We recommend a high-performance SSD with high input/output operations per second (IOPS) and low latency for {% data variables.product.prodname_ghe_server %}. Workloads are I/O intensive. If you use a bare metal hypervisor, we recommend directly attaching the disk or using a disk from a storage area network (SAN). diff --git a/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md index 33dc420e4c..a74a7f5e45 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,56 +1,7 @@ -{% ifversion ghes %} - -| User licenses | vCPUs | Memory | Attached storage | Root storage | -| :- | -: | -: | -: | -: | -| Trial, demo, or 10 light users | 4 | 32 GB | 150 GB | 200 GB | -| 10 to 3,000 | 8 | 48 GB | 300 GB | 200 GB | -| 3,000 to 5000 | 12 | 64 GB | 500 GB | 200 GB | -| 5,000 to 8000 | 16 | 96 GB | 750 GB | 200 GB | -| 8,000 to 10,000+ | 20 | 160 GB | 1000 GB | 200 GB | - -{% else %} - -| User licenses | vCPUs | Memory | Attached storage | Root storage | -| :- | -: | -: | -: | -: | -| Trial, demo, or 10 light users | 2 | 16 GB | 100 GB | 200 GB | -| 10 to 3,000 | 4 | 32 GB | 250 GB | 200 GB | -| 3,000 to 5000 | 8 | 64 GB | 500 GB | 200 GB | -| 5,000 to 8000 | 12 | 96 GB | 750 GB | 200 GB | -| 8,000 to 10,000+ | 16 | 128 GB | 1000 GB | 200 GB | - -{% endif %} - -{% ifversion ghes %} - -If you plan to enable {% data variables.product.prodname_actions %} for the users of your instance, more resources are required. - - -{%- ifversion ghes = 3.2 %} - -{% data reusables.actions.hardware-requirements-3.2 %} - -{%- endif %} - -{%- ifversion ghes = 3.3 %} - -{% data reusables.actions.hardware-requirements-3.3 %} - -{%- endif %} - -{%- ifversion ghes = 3.4 %} - -{% data reusables.actions.hardware-requirements-3.4 %} - -{%- endif %} - -{%- ifversion ghes = 3.5 %} - -{% data reusables.actions.hardware-requirements-3.5 %} - -{%- endif %} - -For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)." - -{% endif %} - -{% data reusables.enterprise_installation.about-adjusting-resources %} +| 用户许可 | vCPU | 内存 | 附加的存储容量 | 根存储容量 | +|:----------------- | ----:| ------:| -------:| ------:| +| 试用版、演示版或 10 个轻度用户 | 4 | 32 GB | 150 GB | 200 GB | +| 10-3000 | 8 | 48 GB | 300 GB | 200 GB | +| 3000-5000 | 12 | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 16 | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 20 | 160 GB | 1000 GB | 200 GB | diff --git a/translations/zh-CN/data/reusables/gated-features/security-center.md b/translations/zh-CN/data/reusables/gated-features/security-overview.md similarity index 100% rename from translations/zh-CN/data/reusables/gated-features/security-center.md rename to translations/zh-CN/data/reusables/gated-features/security-overview.md diff --git a/translations/zh-CN/data/reusables/security-center/beta.md b/translations/zh-CN/data/reusables/security-overview/beta.md similarity index 100% rename from translations/zh-CN/data/reusables/security-center/beta.md rename to translations/zh-CN/data/reusables/security-overview/beta.md diff --git a/translations/zh-CN/data/reusables/security-center/permissions.md b/translations/zh-CN/data/reusables/security-overview/permissions.md similarity index 100% rename from translations/zh-CN/data/reusables/security-center/permissions.md rename to translations/zh-CN/data/reusables/security-overview/permissions.md diff --git a/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md b/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md index 6992f4d32e..26ffc09986 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md @@ -4,7 +4,7 @@ | `check_suite` | `对象` | [check_suite](/rest/reference/checks#suites)。 | | `check_suite[head_branch]` | `字符串` | 更改所在的头部分支的名称。 | | `check_suite[head_sha]` | `字符串` | 此检查套件的最新提交的 SHA。 | -| `check_suite[status]` | `字符串` | 检查套件中所有检查运行的摘要状态。 Can be `queued`, `requested`, `in_progress`, or `completed`. | +| `check_suite[status]` | `字符串` | 检查套件中所有检查运行的摘要状态。 可以是 `queued`、`requested`、`in_progress` 或 `completed`。 | | `check_suite[conclusion]` | `字符串` | 检查套件中所有检查运行的摘要结论。 可以是 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、`action_required` 或 `stale` 之一。 此值将为 `null`，直到检查运行 `completed`。 | | `check_suite[url]` | `字符串` | 指向检查套件 API 资源的 URL。 | | `check_suite[pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 如果拉取请求具有相同的 `head_branch`，则它们与检查套件匹配。

**注意：** | diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 8e69fc1696..521bb617b5 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -200,7 +200,7 @@ api_url_pre: >- oauth_host_code: >- {% ifversion fpt or ghec %}https://github.com{% else %}http(s)://[hostname]{% endif %} device_authorization_url: >- - [`https://github.com/login/device`](https://github.com/login/device) + {%- ifversion fpt or ghec %} [`https://github.com/login/device`](https://github.com/login/device) {%- elsif ghes %} `http(s)://[hostname]/login/device` {%- elsif ghae %} `https://[hostname]/login/device` {%- endif %} #Use this all other code blocks api_url_code: >- {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://[hostname]/api/v3{% elsif ghae %}https://[hostname]/api/v3{% endif %}