From 1e469b707d823bf8713f9bbd9ceed4b35e5e2420 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Wed, 8 Jun 2022 17:17:05 -0400 Subject: [PATCH] New translation batch for cn (#28338) * 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 --- translations/log/cn-resets.csv | 2 +- .../building-and-testing-java-with-gradle.md | 2 +- .../building-and-testing-java-with-maven.md | 2 +- .../building-and-testing-nodejs.md | 2 +- .../building-and-testing-powershell.md | 2 +- .../building-and-testing-python.md | 2 +- ...g-openid-connect-in-amazon-web-services.md | 2 +- .../understanding-github-actions.md | 10 +- .../skipping-workflow-runs.md | 4 +- .../zh-CN/content/actions/quickstart.md | 3 + .../about-github-hosted-runners.md | 2 +- ...hing-dependencies-to-speed-up-workflows.md | 2 +- .../enabling-subdomain-isolation.md | 2 +- ...ith-github-packages-for-your-enterprise.md | 6 ++ .../restoring-a-deleted-repository.md | 9 +- ...ing-codeql-code-scanning-in-a-container.md | 2 +- ...g-code-scanning-alerts-in-pull-requests.md | 2 +- .../sarif-support-for-code-scanning.md | 11 ++- .../about-the-dependency-graph.md | 25 +++-- ...ting-a-listing-description-for-your-app.md | 2 +- .../create-a-group-assignment.md | 2 +- ...-and-searching-issues-and-pull-requests.md | 4 +- .../about-ssh-certificate-authorities.md | 2 +- .../roles-in-an-organization.md | 2 +- .../introduction-to-github-packages.md | 4 +- .../deleting-a-repository.md | 2 +- .../restoring-a-deleted-repository.md | 14 +-- ...ithub-actions-settings-for-a-repository.md | 6 +- .../automatically-generated-release-notes.md | 8 +- .../managing-releases-in-a-repository.md | 11 ++- .../zh-CN/content/rest/actions/permissions.md | 2 +- .../zh-CN/content/rest/secret-scanning.md | 2 +- .../searching-issues-and-pull-requests.md | 92 +++++++++---------- .../github-privacy-statement.md | 20 ++-- ...ons-inherit-secrets-reusable-workflows.yml | 2 +- .../dependency-graph-rust-support.yml | 7 ++ .../data/features/previous-release-tag.yml | 8 ++ .../release-notes/enterprise-server/3-5/0.yml | 1 + .../actions/link-to-example-library.md | 1 + .../getting-started/learning-enterprise.md | 2 +- .../reusables/getting-started/learning.md | 2 +- .../releases/previous-release-tag.md | 3 + .../reusables/repositories/relative-links.md | 2 +- .../reusables/webhooks/delete_properties.md | 8 +- 44 files changed, 173 insertions(+), 128 deletions(-) create mode 100644 translations/zh-CN/data/features/dependency-graph-rust-support.yml create mode 100644 translations/zh-CN/data/features/previous-release-tag.yml create mode 100644 translations/zh-CN/data/reusables/actions/link-to-example-library.md create mode 100644 translations/zh-CN/data/reusables/releases/previous-release-tag.md diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index ebe4a83535..7bfa4a9ae5 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -88,7 +88,7 @@ translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzin translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md,broken liquid tags translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,Listed in localization-support#489 -translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,rendering error +translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,broken liquid tags translations/zh-CN/content/admin/overview/creating-an-enterprise-account.md,broken liquid tags translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index c2a619fdeb..e26d09ce9c 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -22,7 +22,7 @@ shortTitle: 构建和测试 Java & Gradle ## 简介 -本指南介绍如何使用 Gradle 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以{% ifversion actions-caching %}缓存文件并且{% endif %}从工作流程运行上传构件。 +本指南介绍如何使用 Gradle 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 You can extend your CI workflow to {% ifversion actions-caching %}cache files and{% endif %} upload artifacts from a workflow run. {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index df78c01071..543e669811 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -22,7 +22,7 @@ shortTitle: 使用 Maven 构建和测试 Java ## 简介 -本指南介绍如何使用 Maven 软件项目管理工具为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以{% ifversion actions-caching %}缓存文件并且{% endif %}从工作流程运行上传构件。 +本指南介绍如何使用 Maven 软件项目管理工具为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 You can extend your CI workflow to {% ifversion actions-caching %}cache files and{% endif %} upload artifacts from a workflow run. {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index 7a9e10f712..48ede53694 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -134,7 +134,7 @@ jobs: {% data variables.product.prodname_dotcom %} 托管的运行器安装了 npm 和 Yarn 依赖项管理器。 在构建和测试代码之前，可以使用 npm 和 Yarn 在工作流程中安装依赖项。 Windows 和 Linux {% data variables.product.prodname_dotcom %} 托管的运行器也安装了 Grunt、Gulp 和 Bower。 -{% ifversion actions-caching %}您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %} +{% ifversion actions-caching %}You can also cache dependencies to speed up your workflow. 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %} ### 使用 npm 的示例 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index a711d0105d..e282a2ffa6 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -104,7 +104,7 @@ jobs: {% endnote %} -{% ifversion actions-caching %}您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %} +{% ifversion actions-caching %}You can also cache dependencies to speed up your workflow. 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %} 例如，以下作业将安装 `SqlServer` 和 `PSScriptAnalyzer` 模块： diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md index 6de57cb249..95c14089f6 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -195,7 +195,7 @@ jobs: {% data variables.product.prodname_dotcom %} 托管的运行器安装了 pip 软件包管理器。 在构建和测试代码之前，您可以使用 pip 从 PyPI 软件包注册表安装依赖项。 例如，下面的 YAML 安装或升级 `pip` 软件包安装程序以及 `setuptools` 和 `wheel` 软件包。 -{% ifversion actions-caching %}您也可以缓存依赖项来加快工作流程。 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %} +{% ifversion actions-caching %}You can also cache dependencies to speed up your workflow. 更多信息请参阅“[缓存依赖项以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。{% endif %} ```yaml{:copy} steps: diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md index 2acbd1ab19..5319140331 100644 --- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md +++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md @@ -43,7 +43,7 @@ OpenID Connect (OIDC) 允许您的 {% data variables.product.prodname_actions %} ```json{:copy} "Condition": { - "ForAllValues:StringEquals": { + "StringEquals": { "{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:aud": "sts.amazonaws.com", "{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:sub": "repo:octo-org/octo-repo:ref:refs/heads/octo-branch" } diff --git a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md index bcdc20cb42..adc7f99fe1 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md @@ -86,14 +86,14 @@ _操作_是 {% data variables.product.prodname_actions %} 平台的自定义应 {% data reusables.actions.workflow-basic-example-and-explanation %} +## 更复杂的示例 +{% data reusables.actions.link-to-example-library %} + ## 后续步骤 -要继续了解 {% data variables.product.prodname_actions %}，请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions)”。 - +- 要继续了解 {% data variables.product.prodname_actions %}，请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions)”。 {% ifversion fpt or ghec or ghes %} - -要了解 {% data variables.product.prodname_actions %} 的计费方式，请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)”。 - +- 要了解 {% data variables.product.prodname_actions %} 的计费方式，请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)”。 {% endif %} ## 联系支持 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md index efe93c676b..6bcf8bcc55 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -26,7 +26,9 @@ shortTitle: 跳过工作流程运行 * `[skip actions]` * `[actions skip]` -或者，您也可以使用两个空行后接 `skip-checks: true` 或 `skip-checks:true` 来结束提交消息。 +Alternatively, you can end the commit message with two empty lines followed by either: +- `skip-checks:true` +- `skip-checks: true` 如果您的仓库配置为需要先通过特定检查，则无法合并拉取请求。 要允许合并拉取请求，您可以将新提交推送到拉取请求，而无需提交消息中的跳过指令。 diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md index 4853637b43..a541e1790a 100644 --- a/translations/zh-CN/content/actions/quickstart.md +++ b/translations/zh-CN/content/actions/quickstart.md @@ -78,6 +78,9 @@ shortTitle: 快速入门 {% data reusables.actions.workflow-template-overview %} +## 更复杂的示例 +{% data reusables.actions.link-to-example-library %} + ## 后续步骤 每次将代码推送到分支时，您刚刚添加的示例工作流程都会运行，并显示 {% data variables.product.prodname_actions %} 如何处理仓库的内容。 但是，这只是您可以对 {% data variables.product.prodname_actions %} 执行操作的开始： diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 479516094e..df2c4f1aac 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -189,6 +189,6 @@ API 返回的 {% data variables.product.prodname_actions %} IP 地址列表每 ## 延伸阅读 - "[管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions)" -- You can use a matrix strategy to run your jobs on multiple images. 更多信息请参阅“[对作业使用矩阵](/actions/using-jobs/using-a-matrix-for-your-jobs)”。 +- 可以使用矩阵策略在多个映像上运行作业。 更多信息请参阅“[对作业使用矩阵](/actions/using-jobs/using-a-matrix-for-your-jobs)”。 {% endif %} diff --git a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index f5239af928..2c6749bad8 100644 --- a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -257,7 +257,7 @@ restore-keys: | ## 使用限制和收回政策 -{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 可以存储的缓存数没有限制，但存储库中所有缓存的总大小限制为{% ifversion actions-cache-policy-apis %} 默认情况下，每个存储库的限制为 10 GB，但此限制可能会有所不同，具体取决于企业所有者或存储库管理员设置的策略。{% else %} 10 GB。{% endif %} +{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited{% ifversion actions-cache-policy-apis %}. 默认情况下，每个存储库的限制为 10 GB，但此限制可能会有所不同，具体取决于企业所有者或存储库管理员设置的策略。{% else %} 10 GB。{% endif %} {% data reusables.actions.cache-eviction-process %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md index 0388f81141..9333e24de0 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md @@ -36,7 +36,7 @@ shortTitle: 启用子域隔离 | `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | | `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | | `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% ifversion ghes %} -| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %} +| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %} | `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | | `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | | `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | diff --git a/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md index 82600b15c7..86480eb524 100644 --- a/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -44,3 +44,9 @@ Choose which package ecosystems you'd like to enable, disable, or set to read-on If subdomain isolation is enabled for {% data variables.product.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `{% data reusables.package_registry.container-registry-hostname %}`. Make sure each package host URL includes `https://`. You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)." + +## Step 5: Check for and rename reserved names + +If you want to use the Docker ecosystem with subdomain isolation disabled, you **must** first rename any user or organization named `v2` on {% data variables.product.product_location %}, prior to enabling Docker ecosystem support in the {% data variables.enterprise.management_console %}. Docker uses a `v2` account name to manage path conflicts with the Docker API, and once Docker registry support is enabled, you won't be able to use this name anymore. + +You can view a full list of logins reserved for internal use by navigating to the "Reserved logins" page in the Site admin dashboard. For more information, see "[Reserved logins](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#reserved-logins)." diff --git a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md index 4000353c26..0a2712b747 100644 --- a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md +++ b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md @@ -1,6 +1,7 @@ --- title: 恢复已删除的仓库 -intro: 站点管理员可以恢复已删除的仓库来恢复其内容。 +intro: You can restore deleted repositories to recover their contents. +permissions: Enterprise owners can restore a deleted repository. versions: ghes: '*' ghae: '*' @@ -11,10 +12,12 @@ topics: shortTitle: 恢复已删除的仓库 --- -通常情况下，如果有人删除仓库，它将在磁盘上保留 90 天并且可以通过站点管理员仪表板进行恢复。 除非法定保留对用户或组织有效，否则 90 天后，存储库将被清除并永久删除。 - ## 关于仓库恢复 +通常情况下，如果有人删除仓库，它将在磁盘上保留 90 天并且可以通过站点管理员仪表板进行恢复。 更多信息请参阅“[站点管理仪表板](/admin/configuration/configuring-your-enterprise/site-admin-dashboard)”。 + +除非法定保留对用户或组织有效，否则 90 天后，存储库将被清除并永久删除。 + 如果存储库在被删除时是复刻网络的一部分，则还原的存储库将与原始复刻网络分离。 仓库被删除后，可能需要一个小时才能恢复。 diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index b9b6de4f84..90a07d1aeb 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -30,7 +30,7 @@ topics: 如果为编译语言设置 {% data variables.product.prodname_code_scanning %}，并且在容器化环境中构建代码，则分析可能会失败，并返回错误消息“No source code was seen during the build（在构建过程中没有看到源代码）”。 这表明 {% data variables.product.prodname_codeql %} 在代码编译过程中无法监视代码。 -您必须在构建代码的容器中运行 {% data variables.product.prodname_codeql %}。 无论您使用的是 {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %}、 {% data variables.product.prodname_codeql_runner %}、{% endif %} 还是 {% data variables.product.prodname_actions %}，这都适用。 对于 {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}或 {% data variables.product.prodname_codeql_runner %}{% endif %}，请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”{% ifversion codeql-runner-supported %} 或“[在 CI 系统](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)中运行 {% data variables.product.prodname_codeql_runner %}”{% endif %}以了解更多信息。 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。 +您必须在构建代码的容器中运行 {% data variables.product.prodname_codeql %}。 This applies whether you are using the {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %}, the {% data variables.product.prodname_codeql_runner %},{% endif %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}or the {% data variables.product.prodname_codeql_runner %}{% endif %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)"{% ifversion codeql-runner-supported %} or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} for more information. 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。 ## 依赖项 diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 29ae4daccc..43ea00665b 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -127,4 +127,4 @@ topics: {% data reusables.code-scanning.false-positive-fix-codeql %} -有关消除警报的详细信息，请参阅 {% ifversion delete-code-scanning-alerts %}“[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)”。{% else %} “[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)”。{% endif %} +For more information about dismissing alerts, see {% ifversion delete-code-scanning-alerts %}"[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."{% else %} "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)."{% endif %} diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index a1561f1bda..1895448cd4 100644 --- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -211,11 +211,12 @@ This SARIF output file has example values to show the minimum required propertie "id": "R01" ... "properties" : { - "id" : "java/unsafe-deserialization", - "kind" : "path-problem", - "name" : "...", - "problem.severity" : "error", - "security-severity" : "9.8", + "id" : "java/unsafe-deserialization", + "kind" : "path-problem", + "name" : "...", + "problem.severity" : "error", + "security-severity" : "9.8", + } } ] } diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index b680fb49ee..d3a697c8e2 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -67,10 +67,13 @@ The recommended formats explicitly define which versions are used for all direct | Package manager | Languages | Recommended formats | All supported formats | | --- | --- | --- | ---| +{%- ifversion dependency-graph-rust-support %} +| Cargo[*] | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` | +{%- endif %} | Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | | NuGet | .NET languages (C#, F#, VB), C++ | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | {%- ifversion github-actions-in-dependency-graph %} -| {% data variables.product.prodname_actions %} workflows[1] | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` | +| {% data variables.product.prodname_actions %} workflows[†] | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` | {%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | Go modules | Go | `go.sum` | `go.mod`, `go.sum` | @@ -79,21 +82,23 @@ The recommended formats explicitly define which versions are used for all direct {%- endif %} | Maven | Java, Scala | `pom.xml` | `pom.xml` | | npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| pip | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% ifversion github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} | +| pip | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`[‡] | {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %} -| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %} +| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` | +{%- endif %} | RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | -{% ifversion github-actions-in-dependency-graph %} -[1] Please note that {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs..uses` will be parsed as dependencies. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions)." - -[2] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. - -{% else %} -[1] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +{% ifversion dependency-graph-rust-support %} +[*] For the initial release of Rust support, dependency graph does not have the metadata and mappings required to detect transitive dependencies. Dependency graph displays transitive dependencies, one level deep, when they are defined in a `Cargo.lock` file. {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} are available for vulnerable dependencies defined in the `Cargo.lock` file. {% endif %} +{% ifversion github-actions-in-dependency-graph %} +[†] {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs..uses` will be parsed as dependencies. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions)." +{% endif %} + +[‡] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. + {% ifversion github-actions-in-dependency-graph %} {% note %} diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md index 4e0ac3e351..4c67f8a84c 100644 --- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md @@ -168,7 +168,7 @@ shortTitle: 写入列表说明 ### 学习所需的技能 - GitHub Skills can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more. + GitHub Skills 可以帮助您学习如何使用 GitHub、如何使用 Markdown 更有效地沟通以及如何处理合并冲突等。 - 仅大写专有名词。 diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md index 542fe27d59..338effce51 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md @@ -143,7 +143,7 @@ redirect_from: ## 后续步骤 -- 在创建作业和学生组成团队后，团队成员可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和团队都可以审查仓库的提交历史记录。 For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}. +- 在创建作业和学生组成团队后，团队成员可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和团队都可以审查仓库的提交历史记录。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 使用入门](/github/getting-started-with-github)”、“[仓库](/repositories)”、“[使用 Git](/github/getting-started-with-github/using-git)”和“[协作处理议题和拉取请求](/github/collaborating-with-issues-and-pull-requests)”，以及 {% data variables.product.prodname_learning %} 中的[解决合并冲突](https://github.com/skills/resolve-merge-conflicts)免费课程。 - 当团队完成作业时，您可以查看仓库中的文件，或者查看仓库的历史和可视化内容，以更好地了解团队如何协作。 更多信息请参阅“[使用图表可视化仓库](/github/visualizing-repository-data-with-graphs)”。 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index 6f35c0776e..0386b51b8a 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -175,8 +175,8 @@ gh pr list --search "team:octo-org/octo-team" 对于议题，您还可以使用搜索来： -- Filter for issues that are linked to a pull request by a closing reference: `linked:pr`{% ifversion issue-close-reasons %} -- Filter issues by the reason they were closed: `is:closed reason:complete` or `is:closed reason:"not planned"`{% endif %} +- 通过关闭引用过滤链接到拉取请求的议题：`linked:pr`{% ifversion issue-close-reasons %} +- 按议题关闭的原因筛选议题：`is:closed reason:complete` 或 `is:closed reason:"not planned"`{% endif %} 对于拉取请求，您还可以使用搜索来： - 过滤[草稿](/articles/about-pull-requests#draft-pull-requests)拉取请求：`is:draft` diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index 0971b23086..210d66edde 100644 --- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -44,7 +44,7 @@ SSH 证书是一种机制：一个 SSH 密钥对另一个 SSH 密钥签名。 {% note %} -**Note:** You must update to OpenSSH 7.6 or later to use these commands. +**注意：** 您必须更新到 OpenSSH 7.6 或更高版本才能使用这些命令。 {% endnote %} diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index e403291cd8..57ba2522d9 100644 --- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -191,7 +191,7 @@ shortTitle: 组织中的角色 | 将组织成员转换为[外部协作者](#outside-collaborators) | **X** | | | | [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | | |{% ifversion pull-request-approval-limit %} +| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | | |{% ifversion pull-request-approval-limit %} | 管理组织中的拉取请求审核（请参阅“[管理组织中的拉取请求审核](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)”） | **X** | | | {% endif %} {% ifversion ghae %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** | | |{% endif %} diff --git a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md index f4716e5ca3..85a6cae85d 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md +++ b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md @@ -75,12 +75,10 @@ For more information, see "[About permissions for {% data variables.product.prod {% ifversion ghes %} {% note %} -**Note:** Docker is not supported when subdomain isolation is disabled. +**Note:** When enabling the Docker registry, we highly recommend also enabling subdomain isolation. For more information, see "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)." {% endnote %} -For more information about subdomain isolation, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." - {% endif %} For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)." diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md index e13d101145..a9a8ee72ba 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md @@ -29,7 +29,7 @@ topics: {% endwarning %} -某些已删除的存储库可以在删除后的 {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif%} 天内恢复。 {% ifversion ghes or ghae %}站点管理员或能为您恢复已删除的存储库。 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 {% else %}更多信息请参阅“[恢复删除的仓库](/articles/restoring-a-deleted-repository)”。{% endif %} +某些已删除的存储库可以在删除后的 90 天内恢复。 {% ifversion ghes or ghae %}站点管理员或能为您恢复已删除的存储库。 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 {% else %}更多信息请参阅“[恢复删除的仓库](/articles/restoring-a-deleted-repository)”。{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md index e127c77b7c..83a9905b5c 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md @@ -1,6 +1,7 @@ --- title: 恢复已删除的仓库 -intro: 您可以恢复一些已删除的仓库来恢复其内容。 +intro: '{% ifversion ghes or ghae %}An enterprise owner{% elsif fpt or ghec %}You{% endif %} can restore some deleted repositories to recover their contents.' +permissions: '{% ifversion ghes or ghae %}{% elsif fpt or ghec %}Anyone can restore deleted repositories that were owned by their own personal account. Organization owners can restore deleted repositories that were owned by the organization.{% endif %}' redirect_from: - /articles/restoring-a-deleted-repository - /github/administering-a-repository/restoring-a-deleted-repository @@ -15,12 +16,15 @@ topics: shortTitle: 恢复已删除的仓库 --- -{% ifversion fpt or ghec %} -任何人都可以恢复其个人帐户拥有的已删除仓库。 组织所有者可以恢复该组织所拥有的已删除仓库。 +{% ifversion ghes or ghae %} + +Usually, deleted repositories can be restored within 90 days by an enterprise owner{% ifversion ghes %} on {% data variables.product.product_location %}{% endif %}. 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 + +{% else %} ## 关于仓库恢复 -已删除的存储库可以在 {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif %} 天内恢复，除非该存储库是当前不为空的复刻网络的一部分。 复刻网络由父仓库、仓库的复刻以及该仓库复刻的复刻组成。 如果仓库是复刻网络的一部分，则在网络中的每个其他仓库被删除或者从网络中脱离之前，无法恢复它。 有关复刻的更多信息，请参阅“[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)”。 +删除的仓库可在 90 天内恢复，除非仓库是目前非空白的复刻网络的一部分。 复刻网络由父仓库、仓库的复刻以及该仓库复刻的复刻组成。 如果仓库是复刻网络的一部分，则在网络中的每个其他仓库被删除或者从网络中脱离之前，无法恢复它。 有关复刻的更多信息，请参阅“[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)”。 如果要恢复属于当前非空白的复刻网络一部分的仓库，可以联系 {% data variables.contact.contact_support %}。 @@ -49,6 +53,4 @@ shortTitle: 恢复已删除的仓库 - "[删除仓库](/articles/deleting-a-repository)" -{% else %} -通常，已删除的存储库可以在 90 天内由 {% data variables.product.prodname_enterprise %} 站点管理员还原。 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 {% endif %} diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 1a5722db7d..3d6a8c6737 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -29,11 +29,11 @@ miniTocMaxHeadingLevel: 3 您可以对您的仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.actions.enabled-actions-description %} 您可以对您的仓库完全禁用 {% data variables.product.prodname_actions %}。 {% data reusables.actions.disabled-actions-description %} -或者，您也可以在存储库中启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作{% ifversion actions-workflow-policy %}和可重用工作流程{% endif %}。 +Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} a workflow can run. ## 管理仓库的 {% data variables.product.prodname_actions %} 权限 -您可以禁用存储库的 {% data variables.product.prodname_actions %} ，或设置策略来配置可在存储库中使用的 {% ifversion actions-workflow-policy %} 和可重用工作流{% endif %} 。 +You can disable {% data variables.product.prodname_actions %} for a repository, or set a policy that configures which actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} can be used in the repository. {% note %} @@ -147,7 +147,7 @@ miniTocMaxHeadingLevel: 3 企业成员可以使用内部存储库来处理项目，而无需公开共享信息。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)”。 -您可以使用以下步骤配置是否可以从存储库外部访问内部存储库中的 {% ifversion internal-actions%}操作和 {% endif %}工作流程。{% ifversion internal-actions %} 更多信息请参阅“[与企业共享操作和工作流程](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)”。 或者，您可以使用 REST API 来设置或获取访问级别的详细信息。 更多信息请参阅“[获取存储库外部工作流程的访问级别](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#get-the-level-of-access-for-workflows-outside-of-the-repository)”和“[设置存储库外部工作流程的访问级别](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#set-the-level-of-access-for-workflows-outside-of-the-repository)”。{% endif %} +You can use the steps below to configure whether {% ifversion internal-actions%}actions and {% endif %}workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." 或者，您可以使用 REST API 来设置或获取访问级别的详细信息。 更多信息请参阅“[获取存储库外部工作流程的访问级别](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#get-the-level-of-access-for-workflows-outside-of-the-repository)”和“[设置存储库外部工作流程的访问级别](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#set-the-level-of-access-for-workflows-outside-of-the-repository)”。{% endif %} 1. 在 {% data variables.product.prodname_dotcom %} 上，导航到内部仓库的主页面。 1. 在仓库名称下，单击 {% octicon "gear" aria-label="The gear icon" %}**Settings（设置）**。 diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md index e9b31abc23..06aa7fde70 100644 --- a/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -17,7 +17,9 @@ communityRedirect: ## 关于自动生成的发行说明 -自动生成的发行说明为 {% data variables.product.prodname_dotcom %} 发行版手动编写发行说明提供了一种自动替代方法。 使用自动生成的发行说明，您可以快速生成发行版内容的概览。 您还可以自定义自动发行说明，使用标签创建自定义类别来组织要包含的拉取请求，并排除某些标签和用户不出现在输出中。 +自动生成的发行说明为 {% data variables.product.prodname_dotcom %} 发行版手动编写发行说明提供了一种自动替代方法。 使用自动生成的发行说明，您可以快速生成发行版内容的概览。 自动生成的发行说明包括合并的拉取请求列表、版本贡献者列表以及指向完整更改日志的链接。 + +您还可以自定义自动发行说明，使用标签创建自定义类别来组织要包含的拉取请求，并排除某些标签和用户不出现在输出中。 ## 为新版本创建自动生成的发行说明 @@ -35,7 +37,9 @@ communityRedirect: {% ifversion fpt or ghec %}![选择分支](/assets/images/help/releases/releases-choose-branch.png) {% else %}![发行版标记分支](/assets/images/enterprise/releases/releases-tag-branch.png) {% endif %} -7. 在说明文本框的右上角，单击 **Auto-generate release notes（自动生成发行说明）**。 ![自动生成发行说明](/assets/images/help/releases/auto-generate-release-notes.png) +{%- data reusables.releases.previous-release-tag %} +7. 在说明文本框的右上角，单击{% ifversion previous-release-tag %}**Generate release notes（生成发行说明）**{% else %}**Auto-generate release notes（自动生成发行说明）**{% endif %}。{% ifversion previous-release-tag %} ![Generate release notes](/assets/images/help/releases/generate-release-notes.png){% else %} +![Auto-generate release notes](/assets/images/enterprise/3.5/releases/auto-generate-release-notes.png){% endif %} 8. 检查生成的注释，确保它们包含所有（且仅有）您要包含的信息。 9. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。 ![通过发行版提供 DMG](/assets/images/help/releases/releases_adding_binary.gif) 10. 要通知用户发行版本尚不可用于生产，可能不稳定，请选择 **This is a pre-release（这是预发布）**。 ![将版本标记为预发行版的复选框](/assets/images/help/releases/prerelease_checkbox.png) diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index 8c670bd0ae..e20bab207d 100644 --- a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -53,15 +53,16 @@ shortTitle: 管理版本 {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![选择分支](/assets/images/help/releases/releases-choose-branch.png) {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %} +{%- data reusables.releases.previous-release-tag %} 6. 键入发行版的标题和说明。 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} 如果您在描述中@提及任何 {% data variables.product.product_name %} 用户，则已发布的版本将包含**贡献者**部分，其中包含所有提及用户的头像列表。 {%- endif %} - {% ifversion fpt or ghec %} 或者，您可以通过单击 **Auto-generate release notes（自动生成发行说明）**来自动生成发行说明。 - {% endif %} - ![发行版说明](/assets/images/help/releases/releases_description_auto.png) -7. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。 ![通过发行版提供 DMG](/assets/images/help/releases/releases_adding_binary.gif) -8. 要通知用户发行版本尚不可用于生产，可能不稳定，请选择 **This is a pre-release（这是预发布）**。 ![将版本标记为预发行版的复选框](/assets/images/help/releases/prerelease_checkbox.png) + {% ifversion fpt or ghec or ghes > 3.3 %} 或者，您也可以通过单击{% ifversion previous-release-tag %}**Generate release notes（生成发行说明）**{% else %}**Auto-generate release notes（自动生成发行说明）**{% endif %} 来自动生成发行说明。{% endif %}{% ifversion previous-release-tag %} + ![发行版说明](/assets/images/help/releases/releases_description_auto.png){% else %} +![Releases description](/assets/images/enterprise/3.5/releases/releases_description_auto.png){% endif %} +1. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。 ![通过发行版提供 DMG](/assets/images/help/releases/releases_adding_binary.gif) +2. 要通知用户发行版本尚不可用于生产，可能不稳定，请选择 **This is a pre-release（这是预发布）**。 ![将版本标记为预发行版的复选框](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt or ghec %} 1. （可选）如果在存储库中启用了 {% data variables.product.prodname_discussions %}，选择 **Create a discussion for this release（为此版本创建讨论）**，然后选择 **Category（类别）**下拉菜单，然后点击类别进行版本讨论。 ![用于创建发行版讨论和下拉菜单以选择类别的复选框](/assets/images/help/releases/create-release-discussion.png) {%- endif %} diff --git a/translations/zh-CN/content/rest/actions/permissions.md b/translations/zh-CN/content/rest/actions/permissions.md index 201ba7e14f..5ee4f33442 100644 --- a/translations/zh-CN/content/rest/actions/permissions.md +++ b/translations/zh-CN/content/rest/actions/permissions.md @@ -14,4 +14,4 @@ versions: ## 关于权限 API -{% data variables.product.prodname_actions %} 权限 API 可让您设置权限，允许哪些企业、组织和存储库运行 {% data variables.product.prodname_actions %}，以及允许哪些操作{% ifversion actions-workflow-policy %} 和可重用工作流程{% endif %}运行。{% ifversion fpt or ghec or ghes %} 更多信息请参阅“[使用限制、计费和管理](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)”。{% endif %} +The {% data variables.product.prodname_actions %} Permissions API allows you to set permissions for what enterprises, organizations, and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %} diff --git a/translations/zh-CN/content/rest/secret-scanning.md b/translations/zh-CN/content/rest/secret-scanning.md index e40438bef5..1c34a5708d 100644 --- a/translations/zh-CN/content/rest/secret-scanning.md +++ b/translations/zh-CN/content/rest/secret-scanning.md @@ -18,7 +18,7 @@ redirect_from: {% data variables.product.prodname_secret_scanning %} API 可让您{% ifversion fpt or ghec or ghes > 3.1 or ghae %}： -- 启用或禁用仓库的 {% data variables.product.prodname_secret_scanning %}{% ifversion secret-scanning-push-protection %} 和推送保护{% endif %}。 更多信息请参阅“[存储库](/rest/reference/repos#update-a-repository)”，并展开 REST API 文档中的“`security_and_analysis` 对象的属性”部分。 +- 启用或禁用仓库的 {% data variables.product.prodname_secret_scanning %}{% ifversion secret-scanning-push-protection %} 和推送保护{% endif %}。 更多信息请参阅“[存储库](/rest/repos/repos#update-a-repository)”，并展开 REST API 文档中的“`security_and_analysis` 对象的属性”部分。 - 从仓库中检索和更新 {% data variables.product.prodname_secret_scanning_GHAS %} 警报。 有关更多详细信息，请参阅以下部分。 {%- else %} 从仓库检索和更新 {% data variables.product.prodname_secret_scanning %} 警报。{% endif %} diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index cc01ecb4d2..fe5d9068ed 100644 --- a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -73,14 +73,14 @@ shortTitle: 搜索议题和 PR | `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) 匹配含有 "android" 字样的已关闭议题和拉取请求。 | {% ifversion issue-close-reasons %} -## Search by the reason an issue was closed +## 按议题关闭原因进行搜索 -You can filter issues based on the reason given when the issue was closed, using the `reason` qualifier. +您可以使用 `reason` 限定符，根据议题关闭时给出的原因筛选议题。 -| 限定符 | 示例 | -| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `reason:complete` | [**libraries is:closed reason:complete**](https://github.com/search?q=libraries+is%3Aclosed+reason%3Acompleted&type=Issues) matches issues with the word "libraries" that were closed as "completed." | -| `reason:"not planned"` | [**libraries is:closed reason:"not planned"**](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) matches issues with the word "libraries" that were closed as "not planned." | +| 限定符 | 示例 | +| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `reason:complete` | [**libraries is:closed reason:complete**](https://github.com/search?q=libraries+is%3Aclosed+reason%3Acompleted&type=Issues) 匹配包含文字 "libraries"、已因“完成”而关闭的议题。 | +| `reason:"not planned"` | [**libraries is:closed reason:"not planned"**](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) 匹配包含文字 "libraries"、已因“未计划”而关闭的议题。 | {% endif %} @@ -156,10 +156,10 @@ You can filter issues based on the reason given when the issue was closed, using 您可以使用 `label` 限定符按标签缩小结果范围。 由于议题可有多个标签，因此您可为每个议题列出单独的限定符。 -| 限定符 | 示例 | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. | -| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." | +| 限定符 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) 匹配标签为 "help wanted"、位于 Ruby 仓库中的议题。 | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) 匹配正文中含有 "broken" 字样、没有 "bug" 标签但*有* "priority" 标签的议题。 | | | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) 匹配含有 "bug" 和 "resolved" 标签的议题。{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | | [**label:bug label:resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) 匹配含有 "bug" 或 "resolved" 标签的议题。{% endif %} @@ -167,82 +167,82 @@ You can filter issues based on the reason given when the issue was closed, using `milestone` 限定符查找作为仓库内[里程碑](/articles/about-milestones)组成部分的议题或拉取请求。 -| 限定符 | 示例 | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul." | -| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix." | +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) 匹配位于名为 "overhaul" 的里程碑中的议题。 | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) 匹配位于名为 "bug fix" 的里程碑中的议题。 | ## 按项目板搜索 您可以使用 `project` 限定符查找与仓库或组织中特定[项目板](/articles/about-project-boards/)关联的议题。 必须按项目板编号搜索项目板。 您可在项目板 URL 的末尾找到项目板编号。 -| 限定符 | 示例 | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| project:PROJECT_BOARD | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57. | -| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository. | +| 限定符 | 示例 | +| -------------------------- | --------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** 匹配 GitHub 拥有的、与组织项目板 57 关联的议题。 | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** 匹配与 @github 的 linguist 仓库中的项目板 1 关联的议题。 | ## 按提交状态搜索 您可以基于提交的状态过滤拉取请求。 这在使用 [Status API](/rest/reference/commits#commit-statuses) 或 CI 服务时特别有用。 -| 限定符 | 示例 | -| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending. | -| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status. | -| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status. | +| 限定符 | 示例 | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) 匹配在状态为待定的 Go 仓库中打开的拉取请求。 | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) 匹配正文中含有 "finally" 字样、具有成功状态的打开拉取请求。 | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) 匹配在 2015 年 5 月打开、具有失败状态的拉取请求。 | ## 按提交 SHA 搜索 如果您知道提交的特定 SHA 哈希，您可以使用它来搜索包含该 SHA 的拉取请求。 SHA 语法必须至少 7 个字符。 -| 限定符 | 示例 | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`. | -| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`. | +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) 匹配具有开头为 `e1109ab` 的提交 SHA 的拉取请求。 | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) 匹配具有开头为 `0eff326d6213c` 的提交 SHA 的合并拉取请求。 | ## 按分支名称搜索 您可以基于拉取请求来自的分支（"head" 分支）或其合并到的分支（"base" 分支）来过滤拉取请求。 -| 限定符 | 示例 | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed. | -| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch. | +| 限定符 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) 匹配从名称以 "change" 字样开头的已关闭分支打开的拉取请求。 | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) 匹配合并到 `gh-pages` 分支中的拉取请求。 | ## 按语言搜索 通过 `language` 限定符，您可以搜索以特定语言编写的仓库内的议题和拉取请求。 -| 限定符 | 示例 | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | -| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories. | +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) 匹配 Ruby 仓库中的开放议题。 | ## 按评论数量搜索 您可以使用 `comments` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)以按评论数量搜索。 -| 限定符 | 示例 | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. | -| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. | +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) 匹配具有超过 100 条评论的已关闭议题。 | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) 匹配具有 500 到 1,000 条评论的议题。 | ## 按交互数量搜索 您可以使用 `interactions` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)按交互数量过滤议题和拉取请求。 交互数量是对议题或拉取请求的反应和评论数量。 -| 限定符 | 示例 | -| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2000 个交互的拉取请求或议题。 | -| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000. | +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2000 个交互的拉取请求或议题。 | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) 匹配 500 至 1,000 个交互的拉取请求或议题。 | ## 按反应数量搜索 您可以使用 `reactions` 限定符以及 [大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)按反应数量过滤议题和拉取请求。 -| 限定符 | 示例 | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) 匹配超过 1000 个反应的议题。 | -| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000. | +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) 匹配超过 1000 个反应的议题。 | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) 匹配 500 至 1000 个反应的议题。 | ## 搜索草稿拉取请求 您可以过滤草稿拉取请求。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests#draft-pull-requests)”。 diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md index 2d31dfa64c..0d439bea5c 100644 --- a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md @@ -304,19 +304,19 @@ CCPA 为加州居民提供关于其个人信息的某些权利。 要提交基 我们收到请求后，将核实提出请求的个人是否为其个人信息适用于此类请求的居民。 加州居民可以自己行使自己的权利，也可以使用书面或授权书指定的授权代理人代表他们提出请求。 如果您通过授权代理人提交请求，我们可能要求您提供额外信息，以证明该代理人在代表您行事，并且我们可能需要您直接向我们验证您的身份。。 对于自己的个人信息，加州居民可行使下述权利。 #### 知情权。 -You have a right to request that we disclose to you the personal information we have collected about you. You also have a right to request additional information about our collection, use, disclosure, or sale of such personal information. Note that we have provided much of this information in this privacy statement. You can use GitHub’s User Migration API to access and download your data. Learn more here. You may also make such a “request to know” by contacting us here. -#### Right to Request Deletion. -You also have a right to request that we delete personal information under certain circumstances, subject to a number of exceptions. To make a request to delete, You can use GitHub’s User Migration API to access and download your data. Learn more here. You may also make such a “request to delete” by contacting us here. +您有权要求我们向您披露我们收集的有关您的个人信息。 您还有权要求提供有关我们收集、使用、披露或出售此类个人信息的其他信息。 请注意，我们在本隐私声明中提供了大部分此类信息。 您可以使用 GitHub 的用户迁移 API 来访问和下载您的数据。 在此处了解更多。 您也可以通过在此处与我们联系来提出此类“了解请求”。 +#### 请求删除的权利。 +您还有权在某些情况下要求我们删除个人信息，但有一些例外情况除外。 要提出删除请求，您可以使用 GitHub 的用户迁移 API 访问和下载您的数据。 在此处了解更多。 您也可以通过在此处与我们联系来提出此类“删除请求”。 -#### Right to Opt-Out. -You have a right to opt-out from future “sales” of personal information. Note that we do not “sell” personal information as defined by the CCPA and have not done so in the past 12 months. +#### 选择退出的权利。 +您有权选择退出个人信息的未来“销售”。 请注意，我们不会“出售”CCPA 定义的个人信息，并且在过去 12 个月内没有这样做过。 -#### Right to Non-Discrimination. -You have a right to not be discriminated against for exercising your CCPA rights. We will not discriminate against you for exercising your CCPA rights. +#### 不受歧视的权利。 +您有权不因行使 CCPA 权利而受到歧视。 我们不会因您行使 CCPA 权利而歧视您。 -You may designate, in writing or through a power of attorney, an authorized agent to make requests on your behalf to exercise your rights under the CCPA. Before accepting such a request from an agent, we will require the agent to provide proof you have authorized it to act on your behalf, and we may need you to verify your identity directly with us. Further, to provide or delete specific pieces of personal information we will need to verify your identity to the degree of certainty required by law. We will verify your request by asking you to submit the request from the email address associated with your account or requiring you to provide information necessary to verify your account. [Please note that you may use two-factor authentication with your GitHub account.](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication) -Finally, you have a right to receive notice of our practices at or before collection of personal information. +您可以书面或通过授权书指定授权代理人代表您提出请求，以行使您在 CCPA 下的权利。 在接受代理商的此类请求之前，我们将要求代理商提供您授权其代表您行事的证明，并且我们可能需要您直接向我们验证您的身份。 此外，要提供或删除特定的个人信息，我们需要在法律要求的确定程度上验证您的身份。 我们将通过要求您从与您的帐户关联的电子邮件地址提交请求，或要求您提供验证帐户所需的信息，以验证您的请求。 [请注意，您可以在 GitHub 帐户中使用双因素身份验证。](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication) +最后，您有权在收集个人信息时或之前收到有关我们做法的通知。 -Additionally, under California Civil Code section 1798.83, also known as the “Shine the Light” law, California residents who have provided personal information to a business with which the individual has established a business relationship for personal, family, or household purposes (“California Customers”) may request information about whether the business has disclosed personal information to any third parties for the third parties’ direct marketing purposes. Please be aware that we do not disclose personal information to any third parties for their direct marketing purposes as defined by this law. California Customers may request further information about our compliance with this law by emailing **(privacy [at] github [dot] com)**. Please note that businesses are required to respond to one request per California Customer each year and may not be required to respond to requests made by means other than through the designated email address. +此外，根据《加利福尼亚州民法典》第 1798.83 条（也称为“闪耀之光”法律），出于个人、家族或家庭目的向与该个人建立业务关系的企业提供个人信息的加利福尼亚州居民（“加州客户”），可以要求提供有关该企业是否已出于第三方的直接营销目的向任何第三方披露个人信息的信息。 请注意，我们不会向任何第三方披露个人信息，以用于本法规定的直接营销目的。 加州客户可以通过发送电子邮件到 **(privacy [at] github [dot] com)**索取有关我们遵守本法律的更多信息。 Please note that businesses are required to respond to one request per California Customer each year and may not be required to respond to requests made by means other than through the designated email address. California residents under the age of 18 who are registered users of online sites, services, or applications have a right under California Business and Professions Code Section 22581 to remove, or request and obtain removal of, content or information they have publicly posted. To remove content or information you have publicly posted, [please submit a Private Information Removal request](https://support.github.com/contact/private-information). Alternatively, to request that we remove such content or information, please send a detailed description of the specific content or information you wish to have removed to [GitHub support](https://support.github.com/contact). Please be aware that your request does not guarantee complete or comprehensive removal of content or information posted online and that the law may not permit or require removal in certain circumstances. If you have any questions about our privacy practices with respect to California residents, please contact us via our [contact form](https://support.github.com/contact?tags=docs-policy). diff --git a/translations/zh-CN/data/features/actions-inherit-secrets-reusable-workflows.yml b/translations/zh-CN/data/features/actions-inherit-secrets-reusable-workflows.yml index 1a80448cb4..dcf7f8f3f7 100644 --- a/translations/zh-CN/data/features/actions-inherit-secrets-reusable-workflows.yml +++ b/translations/zh-CN/data/features/actions-inherit-secrets-reusable-workflows.yml @@ -5,4 +5,4 @@ versions: fpt: '*' ghec: '*' ghes: '>= 3.6' - ghae: + ghae: 'issue-6920' diff --git a/translations/zh-CN/data/features/dependency-graph-rust-support.yml b/translations/zh-CN/data/features/dependency-graph-rust-support.yml new file mode 100644 index 0000000000..439b0edf01 --- /dev/null +++ b/translations/zh-CN/data/features/dependency-graph-rust-support.yml @@ -0,0 +1,7 @@ +--- +#Reference: Issue #6964 Support for Rust manifest parsing in Dependency graph +versions: + fpt: '*' + ghec: '*' + ghes: '>3.5' + ghae: 'issue-6964' diff --git a/translations/zh-CN/data/features/previous-release-tag.yml b/translations/zh-CN/data/features/previous-release-tag.yml new file mode 100644 index 0000000000..17e793c765 --- /dev/null +++ b/translations/zh-CN/data/features/previous-release-tag.yml @@ -0,0 +1,8 @@ +--- +#Issue 7052 +#Adding a previous (release) tag for users when creating a new release and autogenerating release notes +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-7052' 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 9d55d3cd9f..4e69c251bc 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 @@ -342,3 +342,4 @@ sections: - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 - Actions services need to be restarted after restoring an appliance from a backup taken on a different host. + - 'Deleted repositories will not be purged from disk automatically after the 90-day retention period ends. [Updated: 2022-06-08]' diff --git a/translations/zh-CN/data/reusables/actions/link-to-example-library.md b/translations/zh-CN/data/reusables/actions/link-to-example-library.md new file mode 100644 index 0000000000..b1391dacb2 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/link-to-example-library.md @@ -0,0 +1 @@ +For examples that demonstrate more complex features of {% data variables.product.prodname_actions %}, see "[Examples](/actions/examples)." You can see detailed examples that explain how to test your code on a runner, access the {% data variables.product.prodname_dotcom %} CLI, and use advanced features such as concurrency and test matrices. diff --git a/translations/zh-CN/data/reusables/getting-started/learning-enterprise.md b/translations/zh-CN/data/reusables/getting-started/learning-enterprise.md index 2647286168..9ce37784f8 100644 --- a/translations/zh-CN/data/reusables/getting-started/learning-enterprise.md +++ b/translations/zh-CN/data/reusables/getting-started/learning-enterprise.md @@ -1,3 +1,3 @@ -您的企业成员可以通过 [{% data variables.product.prodname_learning %}](https://skills.github.com/) 在自己的 GitHub 存储库中完成有趣、逼真的项目来学习新技能。 Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. +您的企业成员可以通过 [{% data variables.product.prodname_learning %}](https://skills.github.com/) 在自己的 GitHub 存储库中完成有趣、逼真的项目来学习新技能。 每门课程都是由 GitHub 社区创建的实践课程，由友好的机器人授课。 更多信息请参阅“[Git 和 {% data variables.product.prodname_dotcom %} 学习资源](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)”。 diff --git a/translations/zh-CN/data/reusables/getting-started/learning.md b/translations/zh-CN/data/reusables/getting-started/learning.md index 5e3cdd2b84..55daf44fa6 100644 --- a/translations/zh-CN/data/reusables/getting-started/learning.md +++ b/translations/zh-CN/data/reusables/getting-started/learning.md @@ -1,3 +1,3 @@ -您可以通过 [{% data variables.product.prodname_learning %}](https://skills.github.com/) 在自己的 GitHub 存储库中完成有趣，逼真的项目来学习新技能。 Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. +您可以通过 [{% data variables.product.prodname_learning %}](https://skills.github.com/) 在自己的 GitHub 存储库中完成有趣，逼真的项目来学习新技能。 每门课程都是由 GitHub 社区创建的实践课程，由友好的机器人授课。 更多信息请参阅“[Git 和 {% data variables.product.prodname_dotcom %} 学习资源](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)”。 diff --git a/translations/zh-CN/data/reusables/releases/previous-release-tag.md b/translations/zh-CN/data/reusables/releases/previous-release-tag.md new file mode 100644 index 0000000000..a1d109a396 --- /dev/null +++ b/translations/zh-CN/data/reusables/releases/previous-release-tag.md @@ -0,0 +1,3 @@ +{% ifversion previous-release-tag %} +1. Optionally, to the top right of the description text box, select the **Previous tag** drop-down menu and click the tag that identifies the previous release. ![Screenshot showing how to select a tag to identify the previous release](/assets/images/help/releases/releases-tag-previous-release.png) +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/relative-links.md b/translations/zh-CN/data/reusables/repositories/relative-links.md index 62497fe334..9be69d46da 100644 --- a/translations/zh-CN/data/reusables/repositories/relative-links.md +++ b/translations/zh-CN/data/reusables/repositories/relative-links.md @@ -6,6 +6,6 @@ [此项目的参与指南](docs/CONTRIBUTING.md) ``` -{% data variables.product.product_name %} 将根据您当前使用的分支自动转换相对链接或图像路径，从而使链接或路径始终有效。 您可以使用所有相对链接操作符，如 `./` 和 `../`。 +{% data variables.product.product_name %} 将根据您当前使用的分支自动转换相对链接或图像路径，从而使链接或路径始终有效。 The path of the link will be relative to the current file. Links starting with `/` will be relative to the repository root. 您可以使用所有相对链接操作符，如 `./` 和 `../`。 相对链接更便于用户克隆仓库。 绝对链接可能无法用于仓库的克隆 - 建议使用相对链接引用仓库中的其他文件。 diff --git a/translations/zh-CN/data/reusables/webhooks/delete_properties.md b/translations/zh-CN/data/reusables/webhooks/delete_properties.md index 8cd4ee0dd5..c54c37420c 100644 --- a/translations/zh-CN/data/reusables/webhooks/delete_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/delete_properties.md @@ -1,4 +1,4 @@ -| 键 | 类型 | 描述 | -| ---------- | ----- | -------------------------------------------------------- | -| `ref` | `字符串` | The [`git ref`](/rest/reference/git#get-a-reference) 资源。 | -| `ref_type` | `字符串` | 在仓库中删除的 Git ref 对象的类型。 可以是 `branch` 或 `tag`。 | +| 键 | 类型 | 描述 | +| ---------- | ----- | --------------------------------------------------------------------------- | +| `ref` | `字符串` | The [`git ref`](/rest/reference/git#get-a-reference) 资源。 | +| `ref_type` | `字符串` | The type of Git ref object deleted in the repository. 可以是 `branch` 或 `tag`。 |