diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index bc8604d43c..902cdaca9f 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -133,8 +133,12 @@ translations/zh-CN/content/get-started/using-git/dealing-with-non-fast-forward-e translations/zh-CN/content/get-started/using-github/github-mobile.md,broken liquid tags translations/zh-CN/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,broken liquid tags +translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md,broken liquid tags +translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags +translations/zh-CN/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md,broken liquid tags translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md,Listed in localization-support#489 +translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md,parsing error translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags translations/zh-CN/content/packages/learn-github-packages/deleting-a-package.md,broken liquid tags translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md,broken liquid tags @@ -159,12 +163,15 @@ translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repos translations/zh-CN/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md,broken liquid tags translations/zh-CN/content/rest/guides/basics-of-authentication.md,Listed in localization-support#489 translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md,broken liquid tags +translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md,broken liquid tags translations/zh-CN/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489 translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken liquid tags translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,Listed in localization-support#489 translations/zh-CN/content/rest/reference/activity.md,broken liquid tags translations/zh-CN/content/rest/reference/apps.md,broken liquid tags translations/zh-CN/content/rest/reference/enterprise-admin.md,broken liquid tags +translations/zh-CN/content/rest/reference/packages.md,broken liquid tags +translations/zh-CN/content/rest/reference/secret-scanning.md,broken liquid tags translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,broken liquid tags translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md,broken liquid tags translations/zh-CN/content/support/contacting-github-support/creating-a-support-ticket.md,broken liquid tags diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index 225310eafe..07ace631b0 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -95,4 +95,4 @@ shortTitle: 权限用户仓库 ## 延伸阅读 -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md index a9d8e941ef..22ac062b8d 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md @@ -15,7 +15,7 @@ topics: shortTitle: 组织成员资格 --- -组织所有者可邀请您作为成员、帐单管理员或所有者加入其组织。 组织所有者或者对仓库具有管理员权限的成员可邀请您作为外部协作者，协作处理一个或多个仓库。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +组织所有者可邀请您作为成员、帐单管理员或所有者加入其组织。 组织所有者或者对仓库具有管理员权限的成员可邀请您作为外部协作者，协作处理一个或多个仓库。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 您可以在个人资料页面上访问您是其成员的组织。 更多信息请参阅“[访问组织](/articles/accessing-an-organization)”。 diff --git a/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index a51de191f0..c77cf96443 100644 --- a/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -232,4 +232,4 @@ restore-keys: | ## 使用限制和收回政策 -{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 可以存储的缓存数没有限制，但存储库中所有缓存的总大小限制为 10 GB。 如果超过此限制，{% data variables.product.prodname_dotcom %} 将保存缓存，但会开始收回缓存，直到总大小小于 10 GB。 +{% 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 to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB. 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 f018198405..d59a2a2c48 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 @@ -172,22 +172,22 @@ runs: ### `runs.using` -**Required** The runtime used to execute the code specified in [`main`](#runsmain). +**必要** 用于执行 [`main`](#runsmain) 中指定的代码的支行时。 -- Use `node12` for Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %} -- Use `node16` for Node.js v16.{% endif %} +- 将 `node12` 用于 Node.js v12。{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %} +- 将 `node16` 用于 Node.js v16。{% endif %} ### `runs.main` -**必要** 包含操作代码的文件。 The runtime specified in [`using`](#runsusing) executes this file. +**必要** 包含操作代码的文件。 [`using`](#runsusing) 中指定的运行时执行此文件。 ### `runs.pre` -**可选** 允许您在 `main:` 操作开始之前，在作业开始时运行脚本。 例如，您可以使用 `pre:` 运行基本要求设置脚本。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if). +**可选** 允许您在 `main:` 操作开始之前，在作业开始时运行脚本。 例如，您可以使用 `pre:` 运行基本要求设置脚本。 使用 [`using`](#runsusing) 语法指定的运行时将执行此文件。 `pre:` 操作始终默认运行，但您可以使用 [`runs.pre-if`](#runspre-if) 覆盖该设置。 在此示例中，`pre:` 操作运行名为 `setup.js` 的脚本： @@ -206,7 +206,7 @@ runs: ### `runs.pre-if` -**可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 In `pre-if`, status check functions evaluate against the job's status, not the action's own status. +**可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 在 `pre-if` 中，状态检查函数根据作业的状态而不是操作自己的状态进行评估。 请注意，`step` 上下文不可用，因为尚未运行任何步骤。 @@ -224,7 +224,7 @@ runs: ### `runs.post` -**可选** 允许您在 `main:` 操作完成后，在作业结束时运行脚本。 例如，您可以使用 `post:` 终止某些进程或删除不需要的文件。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. +**可选** 允许您在 `main:` 操作完成后，在作业结束时运行脚本。 例如，您可以使用 `post:` 终止某些进程或删除不需要的文件。 使用 [`using`](#runsusing) 语法指定的运行时将执行此文件。 在此示例中，`post:` 操作会运行名为 `cleanup.js` 的脚本： @@ -244,7 +244,7 @@ runs: ### `runs.post-if` -**可选** 允许您定义 `post:` 操作执行的条件。 `post:` 操作仅在满足 `post-if` 中的条件后运行。 如果未设置，则 `post-if` 默认使用 `always()`。 In `post-if`, status check functions evaluate against the job's status, not the action's own status. +**可选** 允许您定义 `post:` 操作执行的条件。 `post:` 操作仅在满足 `post-if` 中的条件后运行。 如果未设置，则 `post-if` 默认使用 `always()`。 在 `post-if` 中，状态检查函数根据作业的状态而不是操作自己的状态进行评估。 例如，此 `cleanup.js` 仅在基于 Linux 的运行器上运行： @@ -260,13 +260,13 @@ runs: ## 用于复合操作的 `runs` -**Required** Configures the path to the composite action. +**必要** 配置组合操作的路径。 ### `runs.using` -**Required** You must set this value to `'composite'`. +**必要** 必须将此值设置为 `'composite'`。 @@ -347,7 +347,7 @@ runs: #### `runs.steps[*].if` -**Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. 您可以使用任何支持上下文和表达式来创建条件。 +**可选** 您可以使用 `if` 条件使步骤仅在满足条件时才运行。 您可以使用任何支持上下文和表达式来创建条件。 {% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." @@ -366,7 +366,7 @@ steps: **示例：使用状态检查功能** -The `my backup step` only runs when the previous step of a composite action fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." +`my backup step` 仅在组合操作的上一步失败时运行。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." @@ -398,7 +398,7 @@ steps: #### `runs.steps[*].env` -**可选** 设置环境变量的 `map` 仅用于该步骤。 If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step. +**可选** 设置环境变量的 `map` 仅用于该步骤。 如果要修改存储在工作流程中的环境变量，请在组合运行步骤中使用 `echo "{name}={value}" >> $GITHUB_ENV`。 @@ -471,13 +471,13 @@ runs: -## `runs` for Docker container actions +## 用于 Docker 容器操作的 `runs` -**Required** Configures the image used for the Docker container action. +**必要** 配置用于 Docker 容器操作的图像。 -### Example: Using a Dockerfile in your repository +### 示例：在仓库中使用 Dockerfile @@ -490,7 +490,7 @@ runs: -### Example: Using public Docker registry container +### 示例：使用公共 Docker 注册表容器 @@ -511,9 +511,9 @@ runs: ### `runs.pre-entrypoint` -**可选** 允许您在 `entrypoint` 操作开始之前运行脚本。 例如，您可以使用 `pre-entrypoint:` 运行基本要求设置脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 启动此操作，并在使用同一基本映像的新容器中运行脚本。 这意味着运行时状态与主 `entrypoint` 容器不同，并且必须在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if). +**可选** 允许您在 `entrypoint` 操作开始之前运行脚本。 例如，您可以使用 `pre-entrypoint:` 运行基本要求设置脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 启动此操作，并在使用同一基本映像的新容器中运行脚本。 这意味着运行时状态与主 `entrypoint` 容器不同，并且必须在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `pre-entrypoint:` 操作始终默认运行，但您可以使用 [`runs.pre-if`](#runspre-if) 覆盖该设置。 -The runtime specified with the [`using`](#runsusing) syntax will execute this file. +使用 [`using`](#runsusing) 语法指定的运行时将执行此文件。 在此示例中，`pre-entrypoint:` 操作会运行名为 `setup.sh` 的脚本： @@ -554,7 +554,7 @@ runs: ### `post-entrypoint` -**可选** 允许您在 `runs.entrypoint` 操作完成后运行清理脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 来启动此操作。 因为 {% data variables.product.prodname_actions %} 使用同一基本映像在新容器内运行脚本，所以运行时状态与主 `entrypoint` 容器不同。 您可以在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if). +**可选** 允许您在 `runs.entrypoint` 操作完成后运行清理脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 来启动此操作。 因为 {% data variables.product.prodname_actions %} 使用同一基本映像在新容器内运行脚本，所以运行时状态与主 `entrypoint` 容器不同。 您可以在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `post-entrypoint:` 操作始终默认运行，但您可以使用 [`runs.post-if`](#runspost-if) 覆盖该设置。 @@ -585,7 +585,7 @@ runs: -#### Example: Defining arguments for the Docker container +#### 示例：为 Docker 容器定义参数 {% raw %} @@ -611,7 +611,7 @@ runs: -### Example: Configuring branding for an action +### 示例：为操作配置品牌宣传 diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 3f69732a46..c00175f21b 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -25,10 +25,10 @@ shortTitle: 管理运行器组 {% endnote %} -Self-hosted runner groups are used to control access to self-hosted runners. 组织管理员可以配置访问策略，用以控制组织中的哪些组织可以访问运行器组。 +自托管运行器组用于控制对自托管运行器的访问。 组织管理员可以配置访问策略，用以控制组织中的哪些组织可以访问运行器组。 如果您使用 -{% data variables.product.prodname_ghe_cloud %}, you can create additional runner groups; enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group; and organization admins can assign additional granular repository access policies to the enterprise runner group. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups). +{% data variables.product.prodname_ghe_cloud %}，您可以创建额外的运行器组；企业管理员可以配置访问策略，控制企业中哪些组织可以访问运行器组；组织管理员可以为企业运行器组分配额外的细致仓库访问策略。 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)。 {% endif %} {% ifversion ghec or ghes or ghae %} @@ -65,12 +65,12 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion ghes > 3.1 or ghae %}"Runners"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**. +1. 在 {% ifversion ghes > 3.1 or ghae %}“Runners（运行器）”{% elsif ghes < 3.2 %}“Self-hosted runners（自托管运行器）”{% endif %} 下，单击 **Add new（新增）**，然后单击 **New group（新建组）**。 ![添加运行器组](/assets/images/help/settings/actions-org-add-runner-group.png) 1. 输入运行程序组的名称，并分配仓库访问策略。 - {% ifversion ghes or ghae %} 您可以配置一个运行器组可供一组特定的仓库或组织中所有仓库访问。 默认情况下，只有私有仓库可以访问运行器组中的运行器，但您可以覆盖此设置。 This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %} + {% ifversion ghes or ghae %} 您可以配置一个运行器组可供一组特定的仓库或组织中所有仓库访问。 默认情况下，只有私有仓库可以访问运行器组中的运行器，但您可以覆盖此设置。 如果配置企业共享的组织的运行组，则不能覆盖此设置。{% endif %} {% warning %} @@ -185,7 +185,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 2. 选择运行器组下拉菜单。 3. 在“Move runner to group（将运行器移动到组）”中，选择运行器的目的地组。 {% elsif ghae or ghes < 3.4 %} -1. In the {% ifversion ghes > 3.1 or ghae %}"Runner groups"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png) +1. 在设置页面的{% ifversion ghes > 3.1 or ghae %}“Runners groups（运行器组）”{% elsif ghes < 3.2 %}“Self-hosted runners（自托管运行器）”{% endif %} 部分，找到要移动的运行器的当前组，并展开组成员列表。 ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png) 2. 选中自托管运行器旁边的复选框，然后单击 **Move to group（移动到组）**以查看可用的目的地。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move.png) 3. 要移动运行器，请单击目标组。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 27dcfa5717..e391ff8b0a 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -1,6 +1,6 @@ --- title: 删除自托管的运行器 -intro: 'You can permanently remove a self-hosted runner from a repository{% ifversion fpt %} or organization{% elsif ghec or ghes or gahe %}, an organization, or an enterprise{% endif %}.' +intro: '您可以从仓库{% ifversion fpt %} 或组织{% elsif ghec or ghes or gahe %}、 组织或{% endif %} 企业永久删除自托管运行器。' redirect_from: - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners - /actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners @@ -75,7 +75,7 @@ shortTitle: 删除自托管的运行器 {% ifversion fpt %} 如果您使用 -{% data variables.product.prodname_ghe_cloud %}, you can also remove runners from an enterprise. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise). +{% data variables.product.prodname_ghe_cloud %}，您还可以从企业中删除运行器。 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise)。 {% endif %} {% ifversion ghec or ghes or ghae %} {% note %} @@ -86,7 +86,7 @@ shortTitle: 删除自托管的运行器 {% endnote %} -To remove a self-hosted runner from an enterprise, you must be an enterprise owner. 建议您也访问自托管的运行器机器。 For information about how to remove a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). +要从企业帐户删除自托管运行器，您必须是企业所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅[企业管理 GitHub Actions API](/rest/reference/enterprise-admin#github-actions)。 {% data reusables.github-actions.self-hosted-runner-reusing %} {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 5929d8ac2d..1e23b72056 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -71,9 +71,9 @@ runs-on: [self-hosted, linux, x64, gpu] 将作业路由到自托管运行器时，{% data variables.product.prodname_dotcom %} 将查找与作业的 `runs-on` 标签匹配的运行器： {% ifversion fpt or ghes > 3.3 or ghae or ghec %} -- If {% data variables.product.prodname_dotcom %} finds an online and idle runner that matches the job's `runs-on` labels, the job is then assigned and sent to the runner. - - If the runner doesn't pick up the assigned job within 60 seconds, the job is re-queued so that a new runner can accept it. -- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner that matches the job's `runs-on` labels, then the job will remain queued until a runner comes online. +- 如果 {% data variables.product.prodname_dotcom %} 找到一个在线的空闲运行器与作业的 `runs-on` 标签匹配，则作业被分配并发送到运行器。 + - 如果运行器在 60 秒内未收到分配的任务，任务将被重新排队，以便新的运行器能够接纳它。 +- 如果 {% data variables.product.prodname_dotcom %} 找不到匹配作业 `runs-on` 标签的在线和空闲运行器，则任务将继续排队，直到运行器上线为止。 - 如果作业排队的时间超过 24 小时，则作业将失败。 {% elsif ghes = 3.3 %} - {% data variables.product.prodname_dotcom %} 先在仓库级别搜索运行器，然后在组织级别搜索运行器，然后在企业级别搜索运行器。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md index a3e7f19973..bcc6d3b9bf 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -24,9 +24,9 @@ topics: 在工作流程中使用的操作可以定义于： -- The same repository as your workflow file{% if internal-actions %} -- An internal repository within the same enterprise account that is configured to allow access to workflows{% endif %} -- Any public repository +- 与工作流程文件相同的仓库{% if internal-actions %} +- 在同一企业帐户中被配置为允许访问工作流程的内部仓库{% endif %} +- 任何公共仓库 - Docker Hub 上发布的 Docker 容器图像 {% data variables.product.prodname_marketplace %} 是您查找 {% data variables.product.prodname_dotcom %} 社区创建的操作的中心位置。{% ifversion fpt or ghec %} [{% data variables.product.prodname_marketplace %} 页面](https://github.com/marketplace/actions/)可用于按类别筛选操作。 {% endif %} @@ -45,11 +45,11 @@ topics: ## 添加操作到工作流程 -You can add an action to your workflow by referencing the action in your workflow file. +您可以通过在工作流程文件中引用操作来向工作流程添加操作。 -You can view the actions referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).” +您可以将 {% data variables.product.prodname_actions %} 工作流程中引用的操作视为包含工作流程的仓库依赖图中的依赖项。 更多信息请参阅“[关于依赖关系图](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”。 -### Adding an action from {% data variables.product.prodname_marketplace %} +### 从 {% data variables.product.prodname_marketplace %} 添加操作 操作的列表页包括操作的版本以及使用操作所需的工作流程语法。 为使工作流程在操作有更新时也保持稳定，您可以在工作流程文件中指定 Git 或 Docker 标记号以引用所用操作的版本。 @@ -62,7 +62,7 @@ You can view the actions referenced in your {% data variables.product.prodname_a {% endif %} -### Adding an action from the same repository +### 从相同仓库添加操作 如果操作在工作流程文件使用该操作的同一仓库中定义，您可以在工作流程文件中通过 ‌`{owner}/{repo}@{ref}` 或 `./path/to/dir` 语法引用操作。 @@ -91,13 +91,13 @@ jobs: - uses: ./.github/actions/hello-world-action ``` -`action.yml` 文件用于提供操作的元数据。 Learn about the content of this file in "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)." +`action.yml` 文件用于提供操作的元数据。 要了解此文件的内容，请参阅“[GitHub Actions 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions)”。 -### Adding an action from a different repository +### 从不同仓库添加操作 -If an action is defined in a different repository than your workflow file, you can reference the action with the `{owner}/{repo}@{ref}` syntax in your workflow file. +如果在与工作流程文件不同的仓库中定义了某个操作，则可以在工作流程文件中使用 `{owner}/{repo}@{ref}` 语法引用该操作。 -The action must be stored in a public repository{% if internal-actions %} or an internal repository that is configured to allow access to workflows. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}.{% endif %} +该操作必须存储在公共仓库{% if internal-actions %} 或配置为允许访问工作流程的内部仓库中。 更多信息请参阅“[与您的企业分享操作和工作流程](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)。”{% else %}。{% endif %} ```yaml jobs: diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index b5f8cc59c1..301097a1c3 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -12,7 +12,7 @@ shortTitle: 下载工作流程构件 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)”。 +默认情况下，{% data variables.product.product_name %} 存储 90 天内的构建日志和构件，您可以根据仓库类型定制此存储期。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)”。 {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md index cc8ea7b1ec..b018f50b6a 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -70,4 +70,4 @@ gh run watch 使用 REST API 时，应将 `inputs` 和 `ref` 配置为请求正文参数。 如果忽略输入，则使用工作流程文件中定义的默认值。 -For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)." +有关使用 REST API 的更多信息，请参阅“[创建工作流调度事件](/rest/reference/actions/#create-a-workflow-dispatch-event)”。 diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 12d0714427..bd2497414c 100644 --- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -59,19 +59,19 @@ Jenkins 将其 Declarative Pipelines 分为多个区段。 同样，{% data vari Jenkins 使用指令来管理 _Declarative Pipelines_。 这些指令定义工作流程的特性及其执行方式。 下表演示这些指令如何映射到 {% data variables.product.prodname_actions %} 中的概念。 -| Jenkins 指令 | {% data variables.product.prodname_actions %} -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment) | [`jobs..env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)
[`jobs..steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) | -| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`jobs..strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)
[`jobs..strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)
[`jobs..timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) | -| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)
[`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions) | -| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on)
[`on..types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)
[on..paths](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) | -| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs..needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) | -| [Jenkins cron syntax](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax) | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule) | -| [`阶段，暂存`](https://jenkins.io/doc/book/pipeline/syntax/#stage) | [`jobs.`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_id)
[`jobs..name`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idname) | -| [`tools`](https://jenkins.io/doc/book/pipeline/syntax/#tools) | | -| {% ifversion ghae %}The command-line tools available in `PATH` on your self-hosted runner systems. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software) | {% endif %} -| [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | -| [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | +| Jenkins 指令 | {% data variables.product.prodname_actions %} +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment) | [`jobs..env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)
[`jobs..steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) | +| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`jobs..strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)
[`jobs..strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)
[`jobs..timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) | +| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)
[`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions) | +| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on)
[`on..types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)
[on..paths](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) | +| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs..needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) | +| [Jenkins cron syntax](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax) | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule) | +| [`阶段，暂存`](https://jenkins.io/doc/book/pipeline/syntax/#stage) | [`jobs.`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_id)
[`jobs..name`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idname) | +| [`tools`](https://jenkins.io/doc/book/pipeline/syntax/#tools) | | +| {% ifversion ghae %}命令行工具在自托管运行器系统上的 `PATH` 中可用。 {% data reusables.actions.self-hosted-runners-software %}{% else %}[{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software) | {% endif %} +| [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | +| [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | ## 使用连续阶段 diff --git a/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md b/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md index 8a82e0c89d..8369d579c3 100644 --- a/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md @@ -34,7 +34,7 @@ If you reuse a workflow from a different repository, any actions in the called w When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. The called workflow is automatically granted access to `github.token` and `secrets.GITHUB_TOKEN`. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." -You can view the reused workflows referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).” +You can view the reused workflows referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. 更多信息请参阅“[关于依赖关系图](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”。 ### Reusable workflows and starter workflows diff --git a/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index ab37cfbd88..ecd31d31c6 100644 --- a/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -65,7 +65,7 @@ topics: {% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %} 1. 在“{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security（安全性）{% endif %}”下，选择要启用的功能，取消选择要禁用的任何功能。 {% ifversion ghes > 3.1 %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% else %} -1. 在“{% data variables.product.prodname_advanced_security %}”下，单击 **{% data variables.product.prodname_code_scanning_capc %}**。 ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png)用于启用 Public Pages 的复选框{% endif %} +1. 在“{% data variables.product.prodname_advanced_security %}”下，单击 **{% data variables.product.prodname_code_scanning_capc %}**。 ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} {% data reusables.enterprise_management_console.save-settings %} 当 {% data variables.product.product_name %} 完成重启后，您可以设置新启用功能所需的任何额外资源。 更多信息请参阅“[为设备配置 {% data variables.product.prodname_code_scanning %}](/admin/advanced-security/configuring-code-scanning-for-your-appliance)”。 diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md index d8441be833..7a492905cb 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md @@ -46,7 +46,7 @@ topics: {% data reusables.enterprise_management_console.select-tls-only %} 4. 在“TLS Protocol support”下，选择您想要允许的协议。 ![包含用于选择 TLS 协议的选项的单选按钮](/assets/images/enterprise/management-console/tls-protocol-support.png) 5. 在“Certificate”下，单击 **Choose File**，选择要安装的 TLS 证书或证书链（PEM 格式）。 此文件通常采用 *.pem*、*.crt* 或 *.cer* 扩展名。 ![用于查找 TLS 证书文件的按钮](/assets/images/enterprise/management-console/install-tls-certificate.png) -6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. 此文件通常采用 *.key* 扩展名。 ![用于查找 TLS 密钥文件的按钮](/assets/images/enterprise/management-console/install-tls-key.png) +6. 在“Unencrypted key（未加密密钥）”下，单击 **Choose File（选择文件）**选择要安装的 RSA 密钥（PEM 格式）。 此文件通常采用 *.key* 扩展名。 ![用于查找 TLS 密钥文件的按钮](/assets/images/enterprise/management-console/install-tls-key.png) {% warning %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md b/translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md index 56508ea613..4492cab6c8 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md @@ -42,7 +42,7 @@ topics: {% note %} -**注**：如果在 IdP 上更改某用户的 `NameID`，该用户在尝试登录到您的 {% data variables.product.prodname_ghe_server %} 实例时会看到错误消息。 {% ifversion ghes %}要恢复用户的访问权限，您需要更新用户帐户的 `NameID` 映射。 更多信息请参阅“[更新用户的 SAML `NameID`](#updating-a-users-saml-nameid)”。{% else %} 更多信息请参阅“[错误：另一个用户已拥有该帐户](#error-another-user-already-owns-the-account)”。{% endif %} +**注**：如果在 IdP 上更改某用户的 `NameID`，该用户在尝试登录到您的 {% data variables.product.prodname_ghe_server %} 实例时会看到错误消息。 {% ifversion ghes %}To restore the user's access, you'll need to update the user account's `NameID` mapping. 更多信息请参阅“[更新用户的 SAML `NameID`](#updating-a-users-saml-nameid)”。{% else %} 更多信息请参阅“[错误：另一个用户已拥有该帐户](#error-another-user-already-owns-the-account)”。{% endif %} {% endnote %} @@ -61,7 +61,7 @@ topics: ## SAML 属性 -以下属性可用。 您可以在 [Management Console](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/) 中更改属性名称，但 `administrator` 属性除外。 +以下属性可用。 You can change the attribute names in the [management console](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), with the exception of the `administrator` attribute. | 默认属性名称 | 类型 | 描述 | | ------------- | -- | --------------------------------------------------------------------------------------------------------------- | @@ -93,14 +93,14 @@ To specify more than one value for an attribute, use multiple `` 元素必须在根响应文档上提供，而且只有在根响应文档签署后才匹配 ACS URL。 如果断言已签名，它将被忽略。 - `` 元素必须始终作为 `` 元素的一部分提供。 It must match the `EntityId` for {% data variables.product.prodname_ghe_server %}. 这是 {% data variables.product.prodname_ghe_server %} 实例的 URL，如 `https://ghe.corp.example.com`。 -- 响应中的每一个断言都**必须**由数字签名加以保护。 签署各个 `` 元素或签署 `` 元素可以实现此操作。 +- Each assertion in the response **must** be protected by a digital signature. 签署各个 `` 元素或签署 `` 元素可以实现此操作。 - `` 元素必须作为 `` 元素的一部分提供。 可以使用任意持久名称标识符格式。 - `Recipient` 属性必须存在并设为 ACS URL。 例如： diff --git a/translations/zh-CN/content/admin/index.md b/translations/zh-CN/content/admin/index.md index 7b8cedcc2b..d34933c907 100644 --- a/translations/zh-CN/content/admin/index.md +++ b/translations/zh-CN/content/admin/index.md @@ -10,9 +10,7 @@ redirect_from: - /github/installing-and-configuring-github-insights/key-metrics-for-collaboration-in-pull-requests - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.21/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.20/github/site-policy/github-insights-and-data-protection-for-your-organization + - /github/site-policy/github-insights-and-data-protection-for-your-organization - /insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise - /github/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise @@ -134,4 +132,3 @@ children: - /release-notes - /all-releases --- - diff --git a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md index 256cb3ac3b..48a76adb45 100644 --- a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md @@ -39,7 +39,7 @@ topics: 只包含热补丁和漏洞补丁的补丁版本会更频繁地发布。 首次发布时通常提供补丁版本，没有候选版本。 升级到补丁版本通常需要不到五分钟的停机时间。 -要将您的企业升级到新版本，请参阅“[发行说明](/enterprise-server/admin/release-notes)”和“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)”。 Because you can only upgrade from a feature release that's at most two releases behind, use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version. +要将您的企业升级到新版本，请参阅“[发行说明](/enterprise-server/admin/release-notes)”和“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)”。 由于只能从最多落后两个版本的功能版本进行升级，因此请使用 [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) 查找当前版本中的升级路径。 {% endif %} diff --git a/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md index af97d12531..c21e4184ba 100644 --- a/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -44,7 +44,7 @@ shortTitle: 配置包生态系统 请注意，`registry.npmjs.com` 的连接遍历 Cloudflare 网络，但此后不连接至单个静态 IP 地址；而是连接到此处列出的 CIDR 范围内的 IP 地址：https://www.cloudflare.com/ips/。 -If you wish to enable npm upstream sources, select `Enabled` for `npm upstreaming`. +如果要启用 npm 上游源，请选择“`为 npm 上游`启用”。 {% endif %} diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md index 75a5107565..7773d7867c 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md @@ -10,7 +10,7 @@ redirect_from: - /github/articles/managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account - - github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account versions: ghec: '*' ghes: '*' diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md index 95d72c25a4..8581f6b36e 100644 --- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md +++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md @@ -18,7 +18,7 @@ topics: - Security --- -## About log forwarding +## 关于日志转发 支持使用任何支持 syslog-style 日志流的日志收集系统（例如 [Logstash](http://logstash.net/) 和 [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)）。 diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md index 2fe026185a..b8cc5ff4a4 100644 --- a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md +++ b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md @@ -32,7 +32,7 @@ shortTitle: 保护您的仓库 从仓库主页点击 **{% octicon "gear" aria-label="The Settings gear" %}设置**，然后向下滚动到“危险区”。 -- 要更改谁可以查看您的仓库，请点击 **Change visibility（更改可见性）**。 更多信息请参阅“[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)”。{% ifversion fpt or ghec %} +- 要更改谁可以查看您的仓库，请点击 **Change visibility（更改可见性）**。 For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec %} - 要更改谁可以访问您的仓库并调整权限，请点击 **Manage access（管理访问）**。 更多信息请参阅“[管理有权访问仓库的团队和人员](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)”。{% endif %} {% ifversion fpt or ghes > 3.0 or ghae or ghec %} @@ -87,7 +87,7 @@ The dependency graph is automatically generated for all public repositories, and 依赖项审查可让您在合并到仓库之前在拉取请求中显示依赖关系的变化。 更多信息请参阅“[关于依赖项审查](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)”。 -Dependency review is a {% data variables.product.prodname_GH_advanced_security %} feature. {% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec or ghes or ghae %}To enable dependency review for a {% ifversion ghec %}private or internal {% endif %}repository, ensure that the dependency graph is enabled and enable {% data variables.product.prodname_GH_advanced_security %}. +Dependency review is a {% data variables.product.prodname_GH_advanced_security %} feature. {% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#managing-dependency-review)。 {% endif %}{% endif %}{% ifversion ghec or ghes or ghae %}To enable dependency review for a {% ifversion ghec %}private or internal {% endif %}repository, ensure that the dependency graph is enabled and enable {% data variables.product.prodname_GH_advanced_security %}. 1. 从仓库的主页点击 **{% octicon "gear" aria-label="The Settings gear" %} Settings（设置）**。 2. 点击 **Security & analysis（安全和分析）**。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index e0a109f88a..1485e33202 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -38,7 +38,7 @@ redirect_from: 有时，您可能只想更新清单中一个依赖项的版本并生成拉取请求。 但是，如果此直接依赖项的更新版本也更新了依赖项，则拉取请求的更改可能超过您的预期。 每个清单和锁定文件的依赖项审查提供了一种简单的方法来查看更改的内容，以及任何新的依赖项版本是否包含已知的漏洞。 -通过检查拉取请求中的依赖项审查并更改被标记为有漏洞的任何依赖项，可以避免将漏洞添加到项目中。 For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +通过检查拉取请求中的依赖项审查并更改被标记为有漏洞的任何依赖项，可以避免将漏洞添加到项目中。 有关依赖项审查工作的更多信息，请参阅“[审查拉取请求中的依赖项更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 {% data variables.product.prodname_dependabot_alerts %} 将会查找依赖项中存在的漏洞，但避免引入潜在问题比在以后修复它们要好得多。 有关 {% data variables.product.prodname_dependabot_alerts %} 的更多信息，请参阅“[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)”。 diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index bfe33f94e0..523a02550b 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -47,7 +47,7 @@ shortTitle: 源控制 1. 在侧边栏的顶部，单击省略号 (**...**)。 ![查看和更多操作的省略号按钮](/assets/images/help/codespaces/source-control-ellipsis-button.png) 1. 在下拉菜单中，单击 **Pull（拉取）**。 -如果自创建代码空间以来开发容器配置已更改，则可以通过为代码空间重建容器来应用更改。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." +如果自创建代码空间以来开发容器配置已更改，则可以通过为代码空间重建容器来应用更改。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)”。 ## 设置代码空间以自动获取新更改 diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md index a3860bc891..f2846a532e 100644 --- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -19,7 +19,7 @@ topics: 使用 wiki，可以像在 {% data variables.product.product_name %} 的任何其他位置一样编写内容。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/articles/getting-started-with-writing-and-formatting-on-github)”。 我们使用[开源标记库](https://github.com/github/markup)将不同的格式转换为 HTML，以便选择使用 Markdown 或任何其他支持的格式编写。 -{% ifversion fpt or ghes or ghec %}如果您在公共仓库中创建 wiki，则该 wiki 可供{% ifversion ghes %}具有 {% data variables.product.product_location %} 访问权限的任何人{% else %}公共{% endif %}访问。 {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。 +{% ifversion fpt or ghes or ghec %}如果您在公共仓库中创建 wiki，则该 wiki 可供{% ifversion ghes %}具有 {% data variables.product.product_location %} 访问权限的任何人{% else %}公共{% endif %}访问。 {% endif %}如果您在私有{% ifversion ghec or ghes %} 或内部{% endif %} 存储库中创建 Wiki，则仅有权访问该仓库的{% ifversion fpt or ghes or ghec %}人员{% elsif ghae %}企业成员{% endif %} 才能访问该 Wiki。 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。 您可以直接在 {% data variables.product.product_name %} 上编辑 wikis，也可在本地编辑 wiki 文件。 默认情况下，只有能够写入仓库的人才可更改 wikis，但您可以允许 {% data variables.product.product_location %} 上的每个人参与{% ifversion ghae %}内部{% else %}公共{% endif %}仓库中的 wiki。 更多信息请参阅“[更改 wikis 的访问权限](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)”。 diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index af12ffbee6..35ee65fb7c 100644 --- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -48,7 +48,7 @@ Wikis 可显示 PNG、JPEG 和 GIF 图片。 ## 受支持的 MediaWiki 格式 无论您的 wiki 页面以哪种标记语言编写，始终可使用某些 MediaWiki 语法。 -- Links ([except AsciiDoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b)) +- 链接（[AsciiDoc 除外](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b)） - 水平规则通过 `---` - 简明符号实体（例如 `δ` 或 `€`） diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md index 8c7fd9e27b..e4cb8cc1ae 100644 --- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md +++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md @@ -34,8 +34,8 @@ shortTitle: 阻止您的帐户 - 您在他们仓库协作者的身份被删除 - 他们与您的赞助关系被取消 - 任何对被阻止用户的待处理仓库或帐户继承者邀请或来自该用户的邀请都被取消 -- The user is removed as a collaborator from all the Project Boards & Projects (beta) owned by you -- You are removed as a collaborator from all the Project Boards & Projects (beta) owned by the user +- 用户作为协作者将从您拥有的所有项目板和项目（测试版）中删除 +- 您作为协作者将从该用户拥有的所有项目板和项目（测试版）中删除 您阻止用户后，他们无法： - 向您发送任何通知，包括 [@提及](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)您的用户名 @@ -48,8 +48,8 @@ shortTitle: 阻止您的帐户 - 在评论中交叉引用您的仓库 - 复刻、关注、固定您的仓库或对其标星 - 赞助您 -- Add you as a collaborator on their Project Boards & Projects (beta) -- Make changes to your public Project Boards & Projects (beta) +- 将您添加为其项目板和项目（测试版）的协作者 +- 对公共项目板和项目进行更改（测试版） 在您拥有的仓库中，被阻止的用户也不能： - 打开议题 diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md index 370066e16b..fb38a9b5b6 100644 --- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md +++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md @@ -33,7 +33,7 @@ shortTitle: 从您的组织中解除阻止 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -{% data reusables.organizations.moderation-settings %}, then click **Blocked users**. +{% data reusables.organizations.moderation-settings %}，然后单击“**阻止的用户**”。 5. 在“Blocked users（已阻止的用户）”下您想要取消阻止的用户旁边，单击 **Unblock（取消阻止）**。 ![取消阻止用户按钮](/assets/images/help/organizations/org-unblock-user-button.png) ## 延伸阅读 diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md index 6fdb84d251..ea03289d48 100644 --- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md +++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md @@ -27,6 +27,6 @@ shortTitle: 限制帐户中的交互 ## 限制用户帐户的交互 {% data reusables.user_settings.access_settings %} -1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**. +1. 在侧边栏的“Access（访问）”部分中，选择 **{% octicon "report" aria-label="The report icon" %} 主持**，然后点击 **Interaction limits（互动限制）**。 {% data reusables.community.set-interaction-limit %} ![临时交互限制选项](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png) diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md index 4a9ccd2631..993c0bba92 100644 --- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md +++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md @@ -33,7 +33,7 @@ shortTitle: 限制组织中的交互 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**. +1. 在侧边栏的“Access（访问）”部分中，选择 **{% octicon "report" aria-label="The report icon" %} 主持** 然后点击 **Interaction limits（互动限制）**。 {% data reusables.community.set-interaction-limit %} ![临时交互限制选项](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png) @@ -41,4 +41,4 @@ shortTitle: 限制组织中的交互 - “[举报滥用或垃圾邮件](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)” - "[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)" - "[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository)" -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md index 95d1953596..d08c39760a 100644 --- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md +++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md @@ -28,7 +28,7 @@ shortTitle: 限制仓库中的交互 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**. +1. 在侧边栏的“Access（访问）”部分中，选择 **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} 主持选项**，然后点击 **Interaction limits（互动限制）**。 {% data reusables.community.set-interaction-limit %} ![临时交互限制选项](/assets/images/help/repository/temporary-interaction-limits-options.png) @@ -36,4 +36,4 @@ shortTitle: 限制仓库中的交互 - “[举报滥用或垃圾邮件](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)” - "[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)" - "[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository)" -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md index 16e6e31492..07bd08519e 100644 --- a/translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ b/translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md @@ -39,7 +39,7 @@ shortTitle: 身份验证 {% endnote %} ## 验证私钥 -{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. 您可以生成私钥指纹，然后与 {% data variables.product.product_name %} 显示的指纹相比较，以验证私钥是否与 {% data variables.product.product_name %} 上存储的公钥匹配。 +{% data variables.product.product_name %} 使用 SHA-256 哈希函数为每对私钥和公钥生成指纹。 您可以生成私钥指纹，然后与 {% data variables.product.product_name %} 显示的指纹相比较，以验证私钥是否与 {% data variables.product.product_name %} 上存储的公钥匹配。 要验证私钥： diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 162c197d63..b08a8b8b26 100644 --- a/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -248,7 +248,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre * [列出部署](/rest/reference/deployments#list-deployments) * [创建部署](/rest/reference/deployments#create-a-deployment) -* [Get a deployment](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} +* [获取部署](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} * [删除部署](/rest/reference/deployments#delete-a-deployment){% endif %} #### 事件 @@ -449,8 +449,8 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre {% ifversion fpt or ghec %} #### 组织团队同步 -* [List IdP groups for a team](/rest/reference/teams#list-idp-groups-for-a-team) -* [Create or update IdP group connections](/rest/reference/teams#create-or-update-idp-group-connections) +* [列出团队的 IdP 组](/rest/reference/teams#list-idp-groups-for-a-team) +* [创建或更新 IdP 组连接](/rest/reference/teams#create-or-update-idp-group-connections) * [列出组织的 IdP 组](/rest/reference/teams#list-idp-groups-for-an-organization) {% endif %} diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index c74337bd71..7de98b3fa6 100644 --- a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -293,7 +293,7 @@ Accept: application/xml 可选的 `redirect_uri` 参数也可用于本地主机 URL。 如果应用程序指定 URL 和端口，授权后，应用程序用户将被重定向到提供的 URL 和端口。 `redirect_uri` 不需要匹配应用程序回调 url 中指定的端口。 -For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`: +对于 `http://127.0.0.1/path` 回调 URL，您可以使用此 `redirect_uri`： ``` http://127.0.0.1:1234/path diff --git a/translations/zh-CN/content/developers/overview/github-developer-program.md b/translations/zh-CN/content/developers/overview/github-developer-program.md index 40ae273537..df10d6cda4 100644 --- a/translations/zh-CN/content/developers/overview/github-developer-program.md +++ b/translations/zh-CN/content/developers/overview/github-developer-program.md @@ -22,13 +22,13 @@ topics: ## 纳入企业 -Email partnerships@github.com to request developer licenses to build and test your application against {% data variables.product.prodname_ghe_server %}. +向 partnerships@github.com 发送电子邮件，请求开发者许可，以便根据 {% data variables.product.prodname_ghe_server %} 构建和测试应用程序。 ## 有适用于 GitHub 的集成？ 太棒了！ 我们希望您加入计划。 以下是您可以使用的推广方式：

-* [让我们知道您的集成](https://github.com/contact?form[subject]=New+GitHub+Integration) +* [让我们知道您的集成](https://support.github.com/contact?tags=rr-general-technical&form[subject]=New+GitHub+Integration) * 使用 [Octocat 或 GitHub 徽标](https://github.com/logos)来标识您的产品适用于 GitHub * 在您的网站上发布有关您的集成的视频或博客 diff --git a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md index ca2eec5233..7952601faa 100644 --- a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md +++ b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md @@ -34,11 +34,11 @@ topics: #### 设置 1. 在本地开启代理转发。 更多信息请参阅[我们的 SSH 代理转发指南][ssh-agent-forwarding]。 -2. 将部署脚本设置为使用代理转发。 For example, on a bash script, enabling agent forwarding would look something like this: `ssh -A serverA 'bash -s' < deploy.sh` +2. 将部署脚本设置为使用代理转发。 例如，在 bash 脚本中，启用代理转发如下所示： `ssh -A serverA 'bash -s' < deploy.sh` ## 使用 OAuth 令牌进行 HTTPS 克隆 -If you don't want to use SSH keys, you can use HTTPS with OAuth tokens. +如果不想使用 SSH 密钥，可以将 HTTPS 与 OAuth 令牌结合使用。 #### 优点 @@ -57,7 +57,7 @@ If you don't want to use SSH keys, you can use HTTPS with OAuth tokens. #### 设置 -See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). +请参阅 [我们的指南，了解如何创建个人访问令牌](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)。 ## 部署密钥 @@ -78,7 +78,7 @@ See [our guide on creating a personal access token](/authentication/keeping-your #### 设置 -1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public and private rsa key pair key pair. +1. 在服务器上[运行 `ssh-keygen` 进程][generating-ssh-keys]，并记住保存生成的公共和私有 RSA 密钥对的位置。 2. 在 {% data variables.product.product_name %} 的右上角，单击您的个人资料照片，然后单击 **Your profile（您的个人资料）**。 ![个人资料导航](/assets/images/profile-page.png) 3. 在个人资料页面上，单击 **Repositories（仓库）**，然后单击仓库的名称。 ![仓库链接](/assets/images/repos.png) 4. 在仓库中，单击 **Settings（设置）**。 ![仓库设置](/assets/images/repo-settings.png) @@ -182,7 +182,6 @@ $ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.c [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/ [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key -[generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/ [collaborator]: /articles/inviting-collaborators-to-a-personal-repository [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index b44d4b5c64..6cccb738b7 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -219,7 +219,7 @@ A Git ref has been successfully synced to a cache replica. For more information, {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -`sender` | `object` | 如果 `action` 是 `reopened_by_user` 或 `closed_by_user`，则 `sender` 对象将是触发事件的用户。 The `sender` object is {% ifversion fpt or ghec %}`github`{% elsif ghes > 3.0 or ghae %}`github-enterprise`{% else %}empty{% endif %} for all other actions. +`sender` | `object` | 如果 `action` 是 `reopened_by_user` 或 `closed_by_user`，则 `sender` 对象将是触发事件的用户。 `sender` 对象对所有其他操作是 {% ifversion fpt or ghec %}`github` {% elsif ghes > 3.0 or ghae %}`github-enterprise` {% else %}空 {% endif %}。 ### Web 挂钩有效负载示例 @@ -269,7 +269,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% note %} -**Note:** You will not receive a webhook for this event when you create more than three tags at once. +**注：**同时创建三个以上的标记时不会收到此事件的 web 挂钩。 {% endnote %} @@ -353,10 +353,10 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 ### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| ------------ | ------------------------------------------- | --------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} +| 键 | 类型 | 描述 | +| ------------ | ------------------------------------------- | --------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} | `action` | `字符串` | 执行的操作。 可以是 `created`。{% endif %} -| `deployment` | `对象` | The [deployment](/rest/reference/deployments#list-deployments). | +| `deployment` | `对象` | [部署](/rest/reference/deployments#list-deployments)。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -378,14 +378,14 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 ### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| ---------------------------------- | ------------------------------------------- | --------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} +| 键 | 类型 | 描述 | +| ---------------------------------- | ------------------------------------------- | ------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} | `action` | `字符串` | 执行的操作。 可以是 `created`。{% endif %} -| `deployment_status` | `对象` | The [deployment status](/rest/reference/deployments#list-deployment-statuses). | -| `deployment_status["state"]` | `字符串` | 新状态。 可以是 `pending`、`success`、`failure` 或 `error`。 | -| `deployment_status["target_url"]` | `字符串` | 添加到状态的可选链接。 | -| `deployment_status["description"]` | `字符串` | 添加到状态的可选人类可读说明。 | -| `deployment` | `对象` | The [deployment](/rest/reference/deployments#list-deployments) that this status is associated with. | +| `deployment_status` | `对象` | [部署状态](/rest/reference/deployments#list-deployment-statuses)。 | +| `deployment_status["state"]` | `字符串` | 新状态。 可以是 `pending`、`success`、`failure` 或 `error`。 | +| `deployment_status["target_url"]` | `字符串` | 添加到状态的可选链接。 | +| `deployment_status["description"]` | `字符串` | 添加到状态的可选人类可读说明。 | +| `deployment` | `对象` | 此状态关联的[部署](/rest/reference/deployments#list-deployments)。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -409,9 +409,9 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 ### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 Can be `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, `unanswered`, `labeled`, or `unlabeled`. | +| 键 | 类型 | 描述 | +| -------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited`、`deleted`、`pinned`、`unpinned`、`locked`、`unlocked`、`transferred`、`category_changed`、`answered`、`unanswered`、`labeled` 或 `unlabeled`。 | {% data reusables.webhooks.discussion_desc %} {% data reusables.webhooks.repo_desc_graphql %} {% data reusables.webhooks.org_desc_graphql %} @@ -457,7 +457,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 ### 可用性 -- GitHub Enterprise web 挂钩。 For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." +- GitHub Enterprise web 挂钩。 更多信息请参阅“[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)”。 ### Web 挂钩有效负载对象 @@ -1402,7 +1402,7 @@ The security advisory dataset also powers the GitHub {% data variables.product.p 当用户被 `created` 或 `deleted` 时。 ### 可用性 -- GitHub Enterprise web 挂钩。 For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." +- GitHub Enterprise web 挂钩。 更多信息请参阅“[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)”。 ### Web 挂钩有效负载示例 diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index 888f839a4a..fdb5a313b2 100644 --- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -71,7 +71,7 @@ shortTitle: 管理讨论 ## 转让讨论 -要转让讨论，您必须具有在要转让讨论的仓库中创建讨论的权限。 You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private repository to a public repository. +要转让讨论，您必须具有在要转让讨论的仓库中创建讨论的权限。 您只能在同一用户或组织帐户拥有的仓库之间转让讨论。 您无法将私有仓库的讨论转让给公共仓库。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md index fcd1370be3..73a2d8c20c 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md @@ -34,7 +34,7 @@ Roles work differently for different types of accounts. For more information abo 组织成员可以是*所有者*{% ifversion fpt or ghec %}、*帐单管理员*{% endif %}或*成员*角色。 所有者对组织具有完全管理权限{% ifversion fpt or ghec %}，而帐单管理员负责管理帐单设置{% endif %}。 成员是其他每个人的默认角色。 您可以通过团队一次管理多个成员的访问权限。 更多信息请参阅： - "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" - "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)" -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" - "[关于团队](/articles/about-teams)" ## 企业帐户 diff --git a/translations/zh-CN/content/get-started/using-git/about-git-rebase.md b/translations/zh-CN/content/get-started/using-git/about-git-rebase.md index eb89eced5c..15b6f86eee 100644 --- a/translations/zh-CN/content/get-started/using-git/about-git-rebase.md +++ b/translations/zh-CN/content/get-started/using-git/about-git-rebase.md @@ -2,7 +2,7 @@ title: 关于 Git 变基 redirect_from: - /rebase - - articles/interactive-rebase/ + - /articles/interactive-rebase - /articles/about-git-rebase - /github/using-git/about-git-rebase - /github/getting-started-with-github/about-git-rebase diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md index 4b6d8519a3..0cdcb55e20 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md +++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md @@ -67,6 +67,13 @@ Look! You can see my backticks. 我们使用 [Linguist](https://github.com/github/linguist) 来执行语言检测并选择[第三方语法](https://github.com/github/linguist/blob/master/vendor/README.md)进行语法突显。 您可以在[语言 YAML 文件](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml)中找出哪些关键词有效。 +{% if mermaid %} +## Creating diagrams + +You can use Mermaid syntax to add diagrams. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)." + +{% endif %} + ## 延伸阅读 - [{% data variables.product.prodname_dotcom %} Flavored Markdown 规格](https://github.github.com/gfm/) diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md new file mode 100644 index 0000000000..4f4f1a2e26 --- /dev/null +++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -0,0 +1,33 @@ +--- +title: Creating diagrams +intro: Create diagrams to convey information through charts and graphs +versions: + feature: mermaid +shortTitle: Create diagrams +--- + +You can use Mermaid syntax to create diagrams. Mermaid is a Markdown-inspired tool that renders text into diagrams. For example, Mermaid can render flow charts, sequence diagrams, pie charts and more. For more information, see the [Mermaid documentation](https://mermaid-js.github.io/mermaid/#/). + +To create a Mermaid diagram, add Mermaid syntax inside a fenced code block with the `mermaid` language identifier. For more information about creating code blocks, see "[Creating and highlighting code blocks](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)." + +For example, you can create a flow chart: + +
+Here is a simple flow chart:
+
+```mermaid
+graph TD;
+    A-->B;
+    A-->C;
+    B-->D;
+    C-->D;
+```
+
+ +![Rendered Mermaid flow chart](/assets/images/help/writing/mermaid-flow-chart.png) + +{% note %} + +**Note:** You may observe errors if you run a third-party Mermaid plugin when using Mermaid syntax on {% data variables.product.company_short %}. + +{% endnote %} diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/index.md index 5c1f690dd7..5ceac9e057 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/index.md @@ -13,6 +13,7 @@ children: - /organizing-information-with-tables - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks + - /creating-diagrams - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet diff --git a/translations/zh-CN/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/zh-CN/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md index 204f1c4e5e..5057935965 100644 --- a/translations/zh-CN/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ b/translations/zh-CN/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -10,13 +10,13 @@ topics: --- ## 摘要 -1. We want you to coordinate disclosure through our bug bounty program, and don't want researchers put in fear of legal consequences because of their good faith attempts to comply with our bug bounty policy. 我们无法约束任何第三方，因此不要假设这种保护适用于任何第三方。 如有疑问，请在采取您认为_可能_超出我们政策范围的任何具体行动之前先询问我们。 +1. 我们希望您通过我们的漏洞悬赏计划协调披露，不希望研究人员在有诚意遵守我们的漏洞悬赏政策时担心法律后果。 我们无法约束任何第三方，因此不要假设这种保护适用于任何第三方。 如有疑问，请在采取您认为_可能_超出我们政策范围的任何具体行动之前先询问我们。 2. 由于识别和非识别信息都可能使研究人员面临风险，因此我们限制与第三方分享信息的范围。 我们可能会将您报告中的非识别实质性信息提供给受影响的第三方，但必须在通知您并得到第三方不会对您提起法律诉讼的承诺之后才这样做。 我们只在您提供书面许可的情况下才会与第三方分享识别信息（姓名、电子邮件地址、电话号码等）。 3. 如果您在参与漏洞悬赏计划时的安全研究违反了我们站点政策中的某些限制，可根据安全港条款获得有限的豁免。 ## 1. 安全港条款 -To encourage research and coordinated disclosure of security vulnerabilities, we will not pursue civil or criminal action, or send notice to law enforcement for accidental or good faith violations of this policy. 我们认为，根据本政策进行的安全研究和漏洞披露活动，属于《计算机欺诈和滥用法案》、DMCA 及其他适用的计算机使用法律（例如 Cal. Penal Code 502(c)）下的“授权”行为。 如果您在本漏洞悬赏计划的范围内绕过我们用来保护应用程序的技术措施，我们放弃对您提出任何潜在 DMCA 索赔的权利。 +为鼓励研究和协调披露，对于意外或善意违反本政策的行为，我们不会提起民事或刑事诉讼，也不会通知执法机构。 我们认为，根据本政策进行的安全研究和漏洞披露活动，属于《计算机欺诈和滥用法案》、DMCA 及其他适用的计算机使用法律（例如 Cal. Penal Code 502(c)）下的“授权”行为。 如果您在本漏洞悬赏计划的范围内绕过我们用来保护应用程序的技术措施，我们放弃对您提出任何潜在 DMCA 索赔的权利。 请注意，如果您的安全研究涉及第三方（不是我们）的网络、系统、信息、应用程序、产品或服务，由于我们无法约束第三方，因此他们可能会提起法律诉讼或通知执法机构。 我们不能也不会以其他实体的名义授权安全研究，对于任何第三方针对您的行动提起的诉讼，我们不会以任何方式为您提供辩护、赔偿或其他形式的保护。 diff --git a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md index 604c3edecb..b1b65d8d8d 100644 --- a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md +++ b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md @@ -22,7 +22,7 @@ GitHub 社区的主要目的是协作处理软件项目。 我们希望人们能 * **包容开放** - 其他协作的经验水平或背景可能与您不同，但这并不意味着他们不能贡献好的想法。 鼓励大家欢迎新的协作者和刚入门的新手。 -* **Respect each other** - Nothing sabotages healthy conversation like rudeness. 保持礼貌和专业，不要发表被理性的人视为冒犯、侮辱或仇恨的言论。 不要骚扰或打击任何人。 在所有互动中应互相尊重和体谅。 +* **互相尊重** - 粗鲁是正常对话的天敌。 保持礼貌和专业，不要发表被理性的人视为冒犯、侮辱或仇恨的言论。 不要骚扰或打击任何人。 在所有互动中应互相尊重和体谅。 您可能要发表反对的意见。 没问题。 但请记住，您的批评要对事不对人。 不要说脏话、人身攻击、纠结于帖子的语气而罔顾其实际内容或制造下意识的矛盾。 而应该提供合理的反驳论据，保持友善的对话。 diff --git a/translations/zh-CN/content/github/site-policy/github-government-takedown-policy.md b/translations/zh-CN/content/github/site-policy/github-government-takedown-policy.md index 217c3a1869..7515df8772 100644 --- a/translations/zh-CN/content/github/site-policy/github-government-takedown-policy.md +++ b/translations/zh-CN/content/github/site-policy/github-government-takedown-policy.md @@ -30,8 +30,8 @@ GitHub 有时会收到政府要求，要求我们删除在其地方管辖区被 ## 如果我们在 gov-takedown 仓库中发布通知，它意味着什么？ 这意味着我们在指定日期收到了通知， 但*不*意味着内容是非法或错误的， 也*不*意味着通知中所指的用户犯了任何错误。 我们并不对政府请求的正误做出或暗示任何判断。 我们发布这些通知和请求只是提供信息。 -## Government takedowns based on violations of GitHub's Terms of Service -In some cases, GitHub receives reports from government officials of violations of GitHub's Terms of Service. We process those violations as we would process a Terms-of-Service violation reported by anyone else. However, we notify the affected users that the report came from a government and, as with any other case, allow them the opportunity to appeal. +## 基于违反 GitHub 服务条款的政府删除 +在某些情况下，GitHub 会收到政府官员关于违反 GitHub 服务条款的报告。 我们处理这些违规就像处理任何其他人报告的服务条款违规一样。 然而，我们通知受影响的用户，报告来自政府，并且同任何其他情况一样，允许他们提出上诉。 ## 透明度报告 -In addition to posting government takedown notices in our `github/gov-takedowns` repository, we report on them in our transparency report. 我们还会在透明度报告中跟踪并报告基于违反 GitHub 服务条款的政府删除。 +除了在我们的 `github/gov-takedowns` 仓库中发布政府删除通知外，我们的透明度报告中也会报告这些通知。 我们还会在透明度报告中跟踪并报告基于违反 GitHub 服务条款的政府删除。 diff --git a/translations/zh-CN/content/github/site-policy/github-terms-of-service.md b/translations/zh-CN/content/github/site-policy/github-terms-of-service.md index b3951f780a..bdd9a334f4 100644 --- a/translations/zh-CN/content/github/site-policy/github-terms-of-service.md +++ b/translations/zh-CN/content/github/site-policy/github-terms-of-service.md @@ -101,7 +101,7 @@ topics: 您在使用服务时可能创建或上传用户生成的内容。 对于您发布、上传、链接或通过服务提供的任何用户生成内容，无论内容的形式如何，您对其内容以及由此造成的任何伤害负有全部责任。 我们对用户生成内容的任何公开显示或滥用概不负责。 ### 2. GitHub 可删除内容 -我们有权删除我们认为违反了任何法律或 [GitHub 条款或政策](/github/site-policy)的用户生成内容。 User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms. +我们有权删除我们认为违反了任何法律或 [GitHub 条款或政策](/github/site-policy)的用户生成内容。 GitHub Mobile 上显示的用户生成内容可能受移动应用商店附加条款的约束。 ### 3. 内容所有权、发布权利和许可授予 您对您的内容保有所有权和责任。 如果您发布不是您自己创建或者您没有所有权的内容，则您同意对您发布的任何内容负责；您只会提交您有权发布的内容；并且您将完全遵守与您发布的内容有关的任何第三方许可。 diff --git a/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md b/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md index 921bbd2c20..06b32c3112 100644 --- a/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md +++ b/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md @@ -24,4 +24,4 @@ GitHub 商标政策可用于报告涉嫌使用您公司或企业的名称、徽 ## [GitHub 私人信息删除政策](/github/site-policy/github-private-information-removal-policy) GitHub 私人信息删除政策可用于报告私人（机密并且会造成安全风险）的数据，但这些数据不一定受版权或商标保护。 -Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer). +印度的用户可以在[这里](https://support.github.com/contact/india-grievance-officer)联系 GitHub 的申诉官。 diff --git a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md index 21dee842af..29d5877db8 100644 --- a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md @@ -95,7 +95,7 @@ GraphQL 可用于仅请求和返回您指定的数据。 例如，您可以创 ## 使用企业账户 API 的查询示例 -此 GraphQL 查询使用 Enterprise Accounts API 请求每个设备的组织中 {% ifversion not ghae %}`公共`{% else %}`私有`{% endif %} 仓库的总数。 To customize this query, replace `` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `` with `octo-enterprise`. +此 GraphQL 查询使用 Enterprise Accounts API 请求每个设备的组织中 {% ifversion not ghae %}`公共`{% else %}`私有`{% endif %} 仓库的总数。 要自定义此查询，请用企业帐户的句柄替换 ``。 例如，如果您的企业帐户位于 `https://github.com/enterprises/octo-enterprise`，则将 `` 替换为 `octo-enterprises`。 {% ifversion not ghae %} diff --git a/translations/zh-CN/content/graphql/index.md b/translations/zh-CN/content/graphql/index.md index dd53bd6357..a7287ff006 100644 --- a/translations/zh-CN/content/graphql/index.md +++ b/translations/zh-CN/content/graphql/index.md @@ -1,6 +1,6 @@ --- title: GitHub GraphQL API -intro: 'To create integrations, retrieve data, and automate your workflows, use the {% data variables.product.prodname_dotcom %} GraphQL API. The {% data variables.product.prodname_dotcom %} GraphQL API offers more precise and flexible queries than the {% data variables.product.prodname_dotcom %} REST API.' +intro: '要创建集成、检索数据和自动化工作流程，请使用 {% data variables.product.prodname_dotcom %} GraphQL API。 {% data variables.product.prodname_dotcom %} GraphQL API 比 {% data variables.product.prodname_dotcom %} REST API 提供更精确和更灵活的查询。' shortTitle: GraphQL API introLinks: overview: /graphql/overview/about-the-graphql-api diff --git a/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md b/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md index 2972924536..0cdfb3f76d 100644 --- a/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md +++ b/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md @@ -12,7 +12,7 @@ topics: ## 概览 -Here are some quick links to get you up and running with the GraphQL API: +下面是一些帮助您启动和运行 GraphQL API 的快速链接： * [身份验证](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) * [根端点](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) @@ -36,9 +36,9 @@ Here are some quick links to get you up and running with the GraphQL API: ## GitHub 为什么使用 GraphQL -GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over traditional REST API endpoints. GraphQL 可用于将多个 REST 请求替换为_单个调用_，以获取您指定的数据。 +GitHub 选择 GraphQL，因为它可以为我们的集成商提供明显更高的灵活性。 准确定义所需数据—_仅仅_是您所需的数据—的能力是它超越传统 REST API 端点的强大优势。 GraphQL 可用于将多个 REST 请求替换为_单个调用_，以获取您指定的数据。 -For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/). +有关 GitHub 为什么投资 GraphQL 的详细信息，请参阅原始[公告博客文章](https://github.blog/2016-09-14-the-github-graphql-api/)。 ## 关于 GraphQL 架构引用 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md index c356a9cc34..a47dfc1825 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -129,7 +129,7 @@ When you create an issue from a discussion, the contents of the discussion post {% endtip %} -必须具有适当的权限才可执行使用相关查询参数的操作。 例如，必须具有向议题添加标签的权限才可使用 `labels` 查询参数。 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +必须具有适当的权限才可执行使用相关查询参数的操作。 例如，必须具有向议题添加标签的权限才可使用 `labels` 查询参数。 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 如果使用查询参数创建无效的 URL，或者没有适当的权限，URL 将返回 `404 未找到`错误页。 如果您创建的 URL 超过服务器限制，URL 将返回 `414 URI 过长`错误页面。 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md index f777072488..a19474e472 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md @@ -16,7 +16,7 @@ topics: shortTitle: 转移议题 --- -To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 您只能在同一用户或组织帐户拥有的仓库之间转让议题。 {% ifversion fpt or ghes or ghec %}你不能将议题从私有仓库转移到公共仓库。{% endif %} diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index b95be3b513..2b6bee14ee 100644 --- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -14,7 +14,7 @@ topics: - Teams --- -{% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)." +{% data reusables.organizations.about-organizations %} 有关帐户类型的详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 帐户的类型](/get-started/learning-about-github/types-of-github-accounts)”。 {% data reusables.organizations.organizations_include %} @@ -23,9 +23,9 @@ topics: ## 组织和企业帐户 {% ifversion fpt %} -Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations). +企业帐户是 {% data variables.product.prodname_ghe_cloud %} 的一项功能，允许所有者集中管理多个组织的策略和计费。 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)。 {% else %} -{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. 组织所有者无法更改在企业帐户级对组织执行的设置。 如果对组织的策略或设置有疑问，请联系企业帐户的所有者。 +{% ifversion ghec %}对于属于企业帐户的组织，计费在企业帐户级别进行管理，而计费设置在组织级别不可用。{% endif %} 企业所有者可以为企业帐户中的所有组织设置策略，或允许组织所有者在组织级别设置策略。 组织所有者无法更改在企业帐户级对组织执行的设置。 如果对组织的策略或设置有疑问，请联系企业帐户的所有者。 {% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md index 6a826c5a00..4217654b38 100644 --- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -14,7 +14,7 @@ topics: shortTitle: 查看组织见解 --- -组织的所有成员均可查看组织洞察。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +组织的所有成员均可查看组织洞察。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 您可以使用组织活动洞察来帮助您更好地了解组织成员如何使用 {% data variables.product.product_name %} 进行协作和处理代码。 依赖项洞察可帮助您跟踪、报告和处理组织的开源使用情况。 diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md index 8efda0479f..71c95988e4 100644 --- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md @@ -1,6 +1,6 @@ --- title: 保护组织安全 -intro: 'You can harden security for your organization by managing security settings,{% ifversion not ghae %} requiring two-factor authentication (2FA),{% endif %} and reviewing the activity and integrations within your organization.' +intro: '您可以通过管理安全设置、{% ifversion not ghae %} 需要双重身份验证 (2FA)、{% endif %} 以及查看组织内的活动和集成来加强组织的安全性。' redirect_from: - /articles/preventing-unauthorized-access-to-organization-information - /articles/keeping-your-organization-secure diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 562df5e1c8..8701ddab1a 100644 --- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -692,11 +692,11 @@ GraphQL 响应可包含长达 90 至 120 天的数据。 {% endif %}{% ifversion ghec %} ### `role` category actions -| 操作 | 描述 | -| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create` | Triggered when an organization owner creates a new custom repository role. 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)." | -| `destroy` | Triggered when a organization owner deletes a custom repository role. 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)." | -| `update` | Triggered when an organization owner edits an existing custom repository role. 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)." | +| 操作 | 描述 | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create` | Triggered when an organization owner creates a new custom repository role. 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 | +| `destroy` | Triggered when a organization owner deletes a custom repository role. 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 | +| `update` | Triggered when an organization owner edits an existing custom repository role. 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 | {% endif %} {% ifversion ghec or ghes or ghae %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md index 16d378d1db..608d73fc5e 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -15,7 +15,7 @@ topics: shortTitle: 添加 GitHub 应用程序管理器 --- -For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)." +有关 {% data variables.product.prodname_github_app %} 管理员权限的详细信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)”。 ## 授权某人管理组织拥有的所有 {% data variables.product.prodname_github_apps %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md index 8f91ee8f31..95b08b8ce9 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -15,7 +15,7 @@ topics: shortTitle: 删除 GitHub 应用程序管理器 --- -For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)." +有关 {% data variables.product.prodname_github_app %} 管理员权限的详细信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)”。 ## 删除整个组织的 {% data variables.product.prodname_github_app %}管理员权限 diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md index 02d3b700b3..8735fe8696 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -20,10 +20,10 @@ permissions: People with admin access to a repository can add an outside collabo {% data reusables.organizations.outside-collaborators-use-seats %} -An organization owner can restrict the ability to invite collaborators. 更多信息请参阅“[设置添加外部协作者的权限](/articles/setting-permissions-for-adding-outside-collaborators)”。. +组织所有者可以限制邀请协作者的能力。 更多信息请参阅“[设置添加外部协作者的权限](/articles/setting-permissions-for-adding-outside-collaborators)”。. {% ifversion ghes %} -Before you can add someone as an outside collaborator on a repository, the person must have a user account on {% data variables.product.product_location %}. If your enterprise uses an external authentication system such as SAML or LDAP, the person you want to add must sign in through that system to create an account. If the person does not have access to the authentication system and built-in authentication is enabled for your enterprise, a site admin can create a user account for the person. 更多信息请参阅“[使用内置身份验证](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication#inviting-users)”。 +要将某人添加为仓库的外部协作者，此人必须在 {% data variables.product.product_location %} 上拥有用户帐户。 如果您的企业使用外部身份验证系统（如 SAML 或 LDAP），则要添加的人员必须通过该系统登录才能创建帐户。 如果此人无权访问身份验证系统，并且为您的企业启用了内置身份验证，则站点管理员可以为该人员创建用户帐户。 更多信息请参阅“[使用内置身份验证](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication#inviting-users)”。 {% endif %} {% ifversion not ghae %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md index 324b78fc5c..d77080b9f1 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md @@ -26,7 +26,7 @@ shortTitle: 将成员转换为协作者 - @提及任何可见团队 - 成为团队维护员 -For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 建议查看组织成员对仓库的访问权限，以确保其访问权限符合您的预期。 更多信息请参阅“[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)”。 diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md index e5c3c0753d..7c71c1b488 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -18,13 +18,13 @@ shortTitle: 管理个人访问 permissions: People with admin access to a repository can manage access to the repository. --- -## About access to organization repositories +## 关于对组织仓库的访问 从组织中的仓库删除协作者时，该协作者会失去对仓库的读写权限。 如果仓库是私有的，并且协作者对仓库进行了复刻，则其复刻也会被检测到，但协作者仍然保留仓库的任何本地克隆副本。 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %} -## Giving a person access to a repository +## 授予用户对仓库的访问权限 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -34,8 +34,8 @@ permissions: People with admin access to a repository can manage access to the r {% data reusables.repositories.navigate-to-manage-access %} {% endif %} {% data reusables.organizations.invite-teams-or-people %} -1. In the search field, start typing the name of the person to invite, then click a name in the list of matches. ![用于输入要邀请加入仓库的团队或人员名称的搜索字段](/assets/images/help/repository/manage-access-invite-search-field.png) -6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**. ![为团队或人员选择权限](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +1. 在搜索字段中，开始输入要邀请的人员的名称，然后单击匹配列表中的名称。 ![用于输入要邀请加入仓库的团队或人员名称的搜索字段](/assets/images/help/repository/manage-access-invite-search-field.png) +6. 在“Choose a role（选择角色）”下，选择要授予此人的仓库角色，然后单击 **Add NAME to REPOSITORY（将姓名添加到仓库）**。 ![为团队或人员选择权限](/assets/images/help/repository/manage-access-invite-choose-role-add.png) ## 管理个人对组织仓库的访问 @@ -50,4 +50,4 @@ permissions: People with admin access to a repository can manage access to the r ## 延伸阅读 {% ifversion fpt or ghec %}- "[限制与仓库的交互](/articles/limiting-interactions-with-your-repository)"{% endif %} -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md index 85a6dce44a..aa6980a546 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -52,4 +52,4 @@ shortTitle: 管理团队访问 ## 延伸阅读 -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md index f226728882..e9343ef194 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -33,7 +33,7 @@ shortTitle: 恢复协作者 **提示**： - - 只有组织所有者才能恢复外部协作者对组织的访问权限。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." + - 只有组织所有者才能恢复外部协作者对组织的访问权限。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 - 恢复 {% data variables.product.product_location %} 上的成员流量可以使用术语“成员”来描述恢复外部协作者，但如果您恢复此人员并保留其以前的权限，则他们将只拥有以前的[外部协作者权限](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)。{% ifversion fpt or ghec %} - 如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。{% endif %} @@ -76,4 +76,4 @@ shortTitle: 恢复协作者 ## 延伸阅读 -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index ef77152b00..f6e41f026c 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -32,14 +32,14 @@ From least access to most access, the roles for an organization repository are: {% ifversion fpt %} If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" in the {% data variables.product.prodname_ghe_cloud %} documentation. {% elsif ghec %} -You can create custom repository roles. 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)." +You can create custom repository roles. 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 {% endif %} 组织所有者可以在访问组织的任何仓库时设置适用于组织所有成员的基本权限。 更多信息请参阅“[设置组织的基本权限](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)”。 组织所有者还可以选择进一步限制对整个组织中某些设置和操作的权限。 有关特定设置选项的更多信息，请参阅“[管理组织设置](/articles/managing-organization-settings)”。 -In addition to managing organization-level settings, organization owners have admin access to every repository owned by the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +In addition to managing organization-level settings, organization owners have admin access to every repository owned by the organization. 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 {% warning %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md index 1ca6380fcb..1e711bd8ed 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -21,10 +21,10 @@ shortTitle: 设置基本权限 {% ifversion fpt or ghec %}默认情况下，组织成员具有对组织仓库的**读取**权限。{% endif %} -If someone with admin access to an organization's repository grants a member a higher level of access for the repository, the higher level of access overrides the base permission. +如果对组织存储库具有管理员访问权限的人员向成员授予对存储库的更高级别的访问权限，则较高级别的访问权限将覆盖基本权限。 {% ifversion ghec %} -If you've created a custom repository role with an inherited role that is lower access than your organization's base permissions, any members assigned to that role will default to the organization's base permissions rather than the inherited role. 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)." +如果您创建了继承角色的访问权限低于组织基本权限的自定义仓库角色，则分配给该角色的任何成员都将默认使用组织的基本权限，而不是继承的角色。 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 {% endif %} ## 设置基本权限 @@ -37,5 +37,5 @@ If you've created a custom repository role with an inherited role that is lower ## 延伸阅读 -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" - “[将外部协作者添加到组织中的仓库](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)” 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 ccc75c3493..0e758434ef 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 @@ -20,7 +20,7 @@ shortTitle: SSH 认证机构 SSH 证书是一种机制：一个 SSH 密钥对另一个 SSH 密钥签名。 如果使用 SSH 认证中心 (CA) 为组织成员提供已签名的 SSH 证书，您可以将 CA 添加到企业帐户或组织，以便组织成员使用其证书访问组织资源。 -在将 SSH CA 添加到组织或企业帐户后，您可以使用 CA 为组织成员签名客户 SSH 证书。 组织成员可以使用已签名的证书通过 Git 访问组织的仓库（并且只访问您组织的仓库）。 Optionally, you can require that members use SSH certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" and "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." +在将 SSH CA 添加到组织或企业帐户后，您可以使用 CA 为组织成员签名客户 SSH 证书。 组织成员可以使用已签名的证书通过 Git 访问组织的仓库（并且只访问您组织的仓库）。 （可选）您可以要求成员使用 SSH 证书访问组织资源。 更多信息请参阅“[管理组织的 SSH 认证机构](/articles/managing-your-organizations-ssh-certificate-authorities)”或“[在企业中实施安全设置策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)”。 例如，您可以构建内部系统，每天早上向开发者颁发新证书。 每个开发者可以使用其每日证书处理组织在 {% data variables.product.product_name %} 上的仓库。 在一天结束时，证书会自动到期，以保护仓库，避免证书以后被窃取。 @@ -32,7 +32,7 @@ SSH 证书是一种机制：一个 SSH 密钥对另一个 SSH 密钥签名。 为防止身份验证错误，组织成员应使用包含组织 ID 的特殊 URL，以使用签名证书克隆仓库。 对仓库具有读取权限的任何人都可在仓库页面上找到此 URL。 更多信息请参阅“[克隆仓库](/articles/cloning-a-repository)”。 -## Issuing certificates +## 颁发证书 在颁发每个证书时，必须包含扩展，以指定证书用于哪个 {% data variables.product.product_name %} 用户。 例如，您可以使用 OpenSSH 的 `ssh-keygen` 命令，将 _KEY-IDENTITY_ 替换为密钥标识，_USERNAME_ 替换为 {% data variables.product.product_name %} 用户名： 您生成的证书将授权代表该用户使用您组织的任何资源。 在签发证书之前，请确保验证用户的身份。 @@ -42,7 +42,7 @@ $ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% {% warning %} -**Warning**: After a certificate has been signed and issued, the certificate cannot be revoked. Make sure to use the -`V` flag to configure a lifetime for the certificate, or the certificate can be used indefinitely. +**警告**：证书签名并颁发后，无法吊销。 请确保使用 -`V` 标志来配置证书的生存期，否则证书可以无限期使用。 {% endwarning %} diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md index 8f4b03ec75..fcbc84c3ef 100644 --- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -1,6 +1,6 @@ --- -title: 我可以为组织中的人员创建帐户吗？ -intro: 虽然您可以将用户添加到您创建的组织，但您无法代表其他人创建其个人用户帐户。 +title: Can I create accounts for people in my organization? +intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.' redirect_from: - /articles/can-i-create-accounts-for-those-in-my-organization - /articles/can-i-create-accounts-for-people-in-my-organization @@ -11,12 +11,12 @@ versions: topics: - Organizations - Teams -shortTitle: 为人员创建帐户 +shortTitle: Create accounts for people --- -## 关于用户帐户 +## About user accounts -由于访问组织需要登录用户帐户，因此每个团队成员都需要创建自己的用户帐户。 在有了要添加到组织的每个人的用户名后，就可以将用户添加到团队。 +Because you access an organization by logging in to a user account, each of your team members needs to create their own user account. After you have usernames for each person you'd like to add to your organization, you can add the users to teams. {% ifversion fpt or ghec %} {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can use SAML single sign-on to centrally manage the access that user accounts have to the organization's resources through an identity provider (IdP). For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} @@ -24,8 +24,8 @@ shortTitle: 为人员创建帐户 You can also consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} {% endif %} -## 将用户添加到您的组织 +## Adding users to your organization -1. 向每个人提供关于[创建用户帐户](/articles/signing-up-for-a-new-github-account)的说明。 -2. 获取要赋予其组织成员资格的每个人的用户名。 -3. [邀请新个人帐户加入](/articles/inviting-users-to-join-your-organization)您的组织。 使用[组织角色](/articles/permission-levels-for-an-organization)和[仓库权限](/articles/repository-permission-levels-for-an-organization)限制每个帐户的访问权限。 +1. Provide each person instructions to [create a user account](/articles/signing-up-for-a-new-github-account). +2. Ask for the username of each person you want to give organization membership to. +3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account. diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md index f345e1a3c4..31b090c1f3 100644 --- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -1,5 +1,5 @@ --- -title: 邀请用户参加您的组织 +title: Inviting users to join your organization intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.product.product_location %}.' permissions: Organization owners can invite users to join an organization. redirect_from: @@ -12,16 +12,16 @@ versions: topics: - Organizations - Teams -shortTitle: 邀请用户加入 +shortTitle: Invite users to join --- ## About organization invitations -如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 +If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-scim %} -如果您的组织要求成员使用双重身份验证，则您邀请的用户在接受邀请之前必须启用双重身份验证。 更多信息请参阅“[在组织中要求双重身份验证](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)”和“[使用双重身份验证 (2FA) 保护您的帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。 +If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)." {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.prodname_dotcom_the_website %} through an identity provider (IdP). For more information, see "[About SCIM](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} @@ -38,5 +38,5 @@ shortTitle: 邀请用户加入 {% data reusables.organizations.send-invitation %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} -## 延伸阅读 -- "[向团队添加组织成员](/articles/adding-organization-members-to-a-team)" +## Further reading +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md index f0357e03c6..4336c9754e 100644 --- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -1,6 +1,6 @@ --- -title: 恢复组织的前成员 -intro: '组织所有者可以{% ifversion fpt or ghec %}邀请前组织成员重新加入{% else %}将前成员添加到{% endif%}您的组织，并可选择是否恢复该人员以前的角色、访问权限、复刻和设置。' +title: Reinstating a former member of your organization +intro: 'Organization owners can {% ifversion fpt or ghec %}invite former organization members to rejoin{% else %}add former members to{% endif%} your organization, and choose whether to restore the person''s former role, access permissions, forks, and settings.' redirect_from: - /articles/reinstating-a-former-member-of-your-organization - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization @@ -13,19 +13,19 @@ permissions: Organization owners can reinstate a former member of an organizatio topics: - Organizations - Teams -shortTitle: 恢复成员 +shortTitle: Reinstate a member --- -## 关于成员恢复 +## About member reinstatement -If a user is removed from your organization in one of the following ways, the user's access privileges and settings are saved for three months. +If a user is removed from your organization in one of the following ways, the user's access privileges and settings are saved for three months. - You manually removed the user from your organization. For more information, see "[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)."{% ifversion not ghae %} - The user was removed from your organization because you've required members and outside collaborators to enable two-factor authentication (2FA). For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)."{% endif %}{% ifversion fpt or ghec %} - The user was removed from your organization because you enforced SAML single sign-on. For more information, see "[Enforcing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} - You converted an organization member to an outside collaborator. For more information, see "[Converting an organization member to an outside collaborator](/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator)." -如果您在该时间范围内将用户{% ifversion fpt or ghec %}邀请{% else %}添加{% endif %}回组织，则可以恢复该用户的权限。 +You can restore the user's privileges if you {% ifversion fpt or ghec %}invite{% else %}add{% endif %} them back to the organization within that time frame. {% note %} @@ -35,24 +35,24 @@ If a user is removed from your organization in one of the following ways, the us {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} -恢复前组织成员时，您可以恢复以下各项： - - 用户在组织中的角色 - - 组织拥有的仓库的任何私有复刻 - - 组织团队的成员身份 - - 组织仓库以前的访问权限和权限 - - 组织仓库的星标 - - 组织中的议题分配 - - 仓库订阅（关注、不关注或忽略仓库活动的通知设置） +When you reinstate a former organization member, you can restore: + - The user's role in the organization + - Any private forks of repositories owned by the organization + - Membership in the organization's teams + - Previous access and permissions for the organization's repositories + - Stars for organization repositories + - Issue assignments in the organization + - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity) {% ifversion ghes %} -如果组织成员由于未使用双因素身份验证已从组织中删除，并且您的组织仍要求成员使用 2FA，则前成员必须启用双因素身份验证，然后才能恢复其成员身份。 +If an organization member was removed from the organization because they did not use two-factor authentication and your organization still requires members to use 2FA, the former member must enable two-factor authentication before you can reinstate their membership. {% endif %} {% ifversion fpt or ghec %} -如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 {% data reusables.organizations.org-invite-scim %} +If your organization has a paid per-user subscription, an unused license must be available before you can reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-scim %} {% endif %} -## 恢复组织的前成员 +## Reinstating a former member of your organization {% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} @@ -60,19 +60,23 @@ If a user is removed from your organization in one of the following ways, the us {% data reusables.organizations.invite_member_from_people_tab %} {% data reusables.organizations.reinstate-user-type-username %} {% ifversion fpt or ghec %} -6. 选择是恢复该人员在组织中以前的权限还是清除其以前的权限并设置新的访问权限，然后单击 **Invite and reinstate（邀请并恢复）**或 **Invite and start fresh（邀请并重新开始）**。 ![选择是否恢复信息](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Invite and reinstate** or **Invite and start fresh**. + ![Choose to restore info or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) {% else %} -6. 选择是恢复该人员在组织中以前的权限还是清除其以前的权限并设置新的访问权限，然后单击 **Add and reinstate（添加并恢复）**或 **Add and start fresh（添加并重新开始）**。 ![选择是否恢复权限](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Add and reinstate** or **Add and start fresh**. + ![Choose whether to restore privileges](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) {% endif %} {% ifversion fpt or ghec %} -7. 如果已清除前组织成员以前的权限，请为该用户选择一个角色，并（可选）将其添加到某些团队，然后单击 **Send invitation（发送邀请）**。 ![角色和团队选项及发送邀请按钮](/assets/images/help/organizations/add-role-send-invitation.png) +7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Send invitation**. + ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png) {% else %} -7. 如果已清除前组织成员以前的权限，请为该用户选择一个角色，并（可选）将其添加到某些团队，然后单击 **Add member（添加成员）**。 ![角色和团队选项及添加成员按钮](/assets/images/help/organizations/add-role-add-member.png) +7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Add member**. + ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png) {% endif %} {% ifversion fpt or ghec %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} {% endif %} -## 延伸阅读 +## Further reading -- "[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 9a4eed8780..80e88cf7a8 100644 --- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -25,7 +25,7 @@ shortTitle: 删除成员 - 付费的许可数不会自动降级。 要在从组织中删除用户后减少付费的许可数，请按照“[降级组织的付费席位](/articles/downgrading-your-organization-s-paid-seats)”中的步骤操作。 - 被删除的成员将无法访问组织私有仓库的私人复刻，但仍可拥有本地副本。 但是，它们无法将本地副本与组织的仓库同步。 如果用户在从组织中删除后的三个月内[恢复为组织成员](/articles/reinstating-a-former-member-of-your-organization)，则可以恢复其私人复刻。 最终，您负责确保无法访问仓库的人员删除任何机密信息或知识产权。 {%- ifversion ghec %} -- Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。 +- 如果被删除成员不是同一企业帐户拥有的任何其他组织的成员，则被删除成员也将失去对组织内部仓库私人复刻的访问权限。 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。 {%- endif %} - 被删除成员发出的任何组织邀请，如果没有被接受，都会取消，且无法访问。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md index e655d9d777..65ef8825dd 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -17,7 +17,7 @@ shortTitle: 允许议题删除 默认情况下，无法从组织的仓库中删除议题。 组织所有者必须先对所有组织的仓库启用此功能。 -Once enabled, organization owners and people with admin access in an organization-owned repository can delete issues. People with admin access in a repository include organization members and outside collaborators who were given admin access. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" and "[Deleting an issue](/articles/deleting-an-issue)." +在启用后，组织所有者以及在组织拥有的仓库中具有管理员权限的人员便可删除议题。 在仓库中具有管理员访问权限的人员包括被授予管理员访问权限的组织成员和外部协作者。 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”和“[删除议题](/articles/deleting-an-issue)”。 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md index 301c9f42ac..85983a9fdb 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -18,7 +18,7 @@ shortTitle: 将组织转换为用户 {% note %} -**Note**: After an account is deleted, the username at the time of deletion becomes unavailable for reuse for 90 days. To reuse an organization's username immediately, you must change the username before you delete the organization. +**注意**：删除帐户后，删除时的用户名将在 90 天内无法重复使用。 要立即重复使用组织的用户名，您必须在删除组织之前更改用户名。 {% endnote %} @@ -26,7 +26,7 @@ shortTitle: 将组织转换为用户 2. [将用户的角色更改为所有者](/articles/changing-a-person-s-role-to-owner)。 3. {% data variables.product.signin_link %} 到新用户帐户。 4. [将每个组织仓库转让](/articles/how-to-transfer-a-repository)给新用户帐户。 -5. [Rename the organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to make the current username available. +5. [重命名组织](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username)以使当前用户名可用。 6. [将用户重命名](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username)为组织的名称。 7. [删除组织](/organizations/managing-organization-settings/deleting-an-organization-account)。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md index 1a3c617087..962b2030ac 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -1,6 +1,6 @@ --- title: 删除组织帐户 -intro: '删除组织时，所有仓库、私有仓库复刻、wiki、议题、拉取请求和项目或组织页面也被删除。 {% ifversion fpt or ghec %}Your billing will end, and after 90 days the organization name becomes available for use on a new user or organization account.{% endif %}' +intro: '删除组织时，所有仓库、私有仓库复刻、wiki、议题、拉取请求和项目或组织页面也被删除。 {% ifversion fpt or ghec %}您的结算将结束，90 天后，组织名称将可用于新的用户或组织帐户。{% endif %}' redirect_from: - /articles/deleting-an-organization-account - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index d2b3061811..53904df98e 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -78,7 +78,7 @@ shortTitle: 禁用或限制操作 {% data reusables.github-actions.private-repository-forks-overview %} -{% ifversion ghec or ghae or ghes %}If a policy is disabled for an enterprise, it cannot be enabled for organizations.{% endif %} If a policy is disabled for an organization, it cannot be enabled for repositories. If an organization enables a policy, the policy can be disabled for individual repositories. +{% ifversion ghec or ghae or ghes %}如果对企业禁用了某个策略，则无法对组织启用该策略。{% endif %} 如果对组织禁用了某个策略，则无法对仓库启用该策略。 如果组织启用了某个策略，则可以对个别仓库禁用该策略。 {% data reusables.github-actions.private-repository-forks-options %} diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md index 94e8b3c7ba..752d895b95 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -13,7 +13,7 @@ shortTitle: 集成 Jira {% ifversion ghes > 3.4 or ghae-issue-5658 %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings**, then click **OAuth Apps**. ![左侧边栏中的 OAuth 应用程序选项卡](/assets/images/help/organizations/org-oauth-applications-ghe.png) +1. 在左侧边栏中，选择 **{% octicon "code" aria-label="The code icon" %} 开发者设置**，然后单击 **OAuth Apps（OAuth 应用程序）**。 ![左侧边栏中的 OAuth 应用程序选项卡](/assets/images/help/organizations/org-oauth-applications-ghe.png) 1. 单击 **New OAuth App（新建 OAuth 应用程序）**。 {% else %} {% data reusables.user_settings.access_settings %} diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md index 2273347c3a..0921342f19 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -24,7 +24,7 @@ shortTitle: 管理复刻策略 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.profile.org_member_privileges %} -1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**. +1. 在“Repository forking（仓库复刻）”下，选择**允许私有{% ifversion ghec or ghes or ghae %}和内部{% endif %}仓库复刻**。 {%- ifversion fpt %} ![允许或禁止组织复刻的复选框](/assets/images/help/repository/allow-disable-forking-fpt.png) @@ -36,4 +36,4 @@ shortTitle: 管理复刻策略 ## 延伸阅读 - "[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index 3d1225948b..58c89d7bf3 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -15,14 +15,14 @@ topics: shortTitle: 限制仓库创建 --- -您可以选择成员是否可以在组织中创建仓库。 {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository. +您可以选择成员是否可以在组织中创建仓库。 {% ifversion ghec or ghes or ghae %}如果允许成员创建仓库，您可以选择成员可以创建的仓库类型。{% elsif fpt %}如果允许成员创建仓库，您可以选择成员是可以同时创建公共和私有仓库，还是只能创建公共仓库。{% endif %} 组织所有者始终可以创建任何类型的仓库。 {% ifversion fpt %} -Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization). +使用 {% data variables.product.prodname_ghe_cloud %} 的组织还可以将成员限制于只能创建私有仓库。 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)。 {% endif %} {% ifversion ghec or ghae or ghes %} -Enterprise owners can restrict the options you have available for your organization's repository creation policy. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)”。 +企业所有者可以限制您可用于组织的仓库创建策略的选项。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)”。 {% endif %} {% warning %} @@ -43,7 +43,7 @@ Enterprise owners can restrict the options you have available for your organizat {% note %} - **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. + **注意：** 要将成员限制为只能创建私有仓库，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。 {% endnote %} {%- endif %} diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md index d5f1d0af4f..a220acfc04 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -32,4 +32,4 @@ shortTitle: 设置可见性更改策略 ## 延伸阅读 -- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" +- "[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md index 6440072c1d..c1dce79669 100644 --- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -1,6 +1,6 @@ --- -title: 为组织添加帐单管理员 -intro: '*帐单管理员*是负责为组织管理帐单设置的用户管理员，例如更新付款信息。 如果组织的常规成员通常不能访问帐单资源，这将是一个很好的选择。' +title: Adding a billing manager to your organization +intro: 'A *billing manager* is a user who manages the billing settings for your organization, such as updating payment information. This is a great option if regular members of your organization don''t typically have access to billing resources.' redirect_from: - /articles/adding-a-billing-manager-to-your-organization - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization @@ -11,59 +11,61 @@ topics: - Organizations - Teams - Billing -shortTitle: 添加帐单管理员 +shortTitle: Add a billing manager --- -组织所有者团队的成员可向人们授予*帐单管理员*权限。 在个人接受其邀请成为组织的帐单管理员后，他们可邀请其他人员为帐单管理员。 +Members of your organization's Owners team can give *billing manager* permissions to people. Once a person accepts their invitation to become a billing manager for your organization, they can invite additional people to be billing managers. {% note %} -**注：**帐单管理员在组织的订阅中不使用付费许可。 +**Note:** Billing managers do not use paid licenses in your organization's subscription. {% endnote %} -## 帐单管理员的权限 +## Permissions for billing managers -帐单管理员可以： +Billing managers can: -- 升级或降级帐户 -- 添加、更新或删除付款方式 -- 查看付款历史记录 -- 下载收据 -- 查看、邀请和删除帐单管理员 -- 开始、修改或取消赞助 +- Upgrade or downgrade the account +- Add, update, or remove payment methods +- View payment history +- Download receipts +- View, invite, and remove billing managers +- Start, modify, or cancel sponsorships -此外，所有帐单管理员在组织的结算日期都会通过电子邮件收到结算收据。 +In addition, all billing managers will receive billing receipts by email on the organization's billing date. -帐单管理员**不**能： +Billing managers **are not** able to: -- 在组织中创建或访问仓库 -- 查看组织的私人成员 -- 出现在组织成员列表中 -- 购买、编辑或取消 {% data variables.product.prodname_marketplace %} 应用程序订阅 +- Create or access repositories in your organizations +- See private members of your organization +- Be seen in the list of organization members +- Purchase, edit, or cancel subscriptions for {% data variables.product.prodname_marketplace %} apps {% tip %} -**提示：**如果您的组织[要求成员、帐单管理员和外部协作者使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)，则用户必须启用双重身份验证后才可接受您的邀请，成为组织的帐单管理员。 +**Tip:** If your organization [requires members, billing managers, and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), the user must enable two-factor authentication before they can accept your invitation to become a billing manager for the organization. {% endtip %} -## 邀请帐单管理员 +## Inviting a billing manager {% ifversion ghec %} {% note %} -**Note:** If your organization is owned by an enterprise account, you cannot invite billing managers at the organization level. 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。 +**Note:** If your organization is owned by an enterprise account, you cannot invite billing managers at the organization level. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." {% endnote %} {% endif %} -受邀人员将会收到邀请电子邮件，邀请他们成为您的组织的帐单管理员。 在受邀人员单击其邀请电子邮件中的接受链接后，他们会自动加入组织成为帐单管理员。 如果他们还没有 GitHub 帐户，将被重定向到注册页面注册一个，在创建帐户后会自动加入组织成为帐单管理员。 +The invited person will receive an invitation email asking them to become a billing manager for your organization. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the organization as a billing manager. If they don't already have a GitHub account, they will be directed to sign up for one, and they will be automatically added to the organization as a billing manager after they create an account. {% data reusables.organizations.billing-settings %} -1. 在“Billing management（帐单管理）”下的“Billing managers（帐单管理员）”旁边，单击 **Add（添加）**。 ![邀请帐单管理员](/assets/images/help/billing/settings_billing_managers_list.png) -6. 输入您要添加的人员的用户名或电子邮件地址，然后单击 **Send invitation（发送邀请）**。 ![邀请帐单管理员页面](/assets/images/help/billing/billing_manager_invite.png) +1. Under "Billing management", next to "Billing managers", click **Add**. + ![Invite billing manager](/assets/images/help/billing/settings_billing_managers_list.png) +6. Type the username or email address of the person you want to add and click **Send invitation**. + ![Invite billing manager page](/assets/images/help/billing/billing_manager_invite.png) -## 延伸阅读 +## Further reading -- "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %} +- "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md index 1e014763a1..bf06aaa30e 100644 --- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -1,6 +1,6 @@ --- title: 使用角色管理人们对您的组织的访问 -intro: 'You can control access to your organizations''s settings and repositories by giving people organization, repository, and team roles.' +intro: 您可以通过为人员提供组织、仓库和团队角色来控制对组织设置和仓库的访问。 redirect_from: - /articles/managing-people-s-access-to-your-organization-with-roles - /articles/managing-peoples-access-to-your-organization-with-roles 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 6be9c01fbd..6b751cc4f6 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 @@ -20,7 +20,7 @@ shortTitle: Roles in an organization ## About roles {% data reusables.organizations.about-roles %} -Repository-level roles give organization members, outside collaborators and teams of people varying levels of access to repositories. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +Repository-level roles give organization members, outside collaborators and teams of people varying levels of access to repositories. 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 Team-level roles are roles that give permissions to manage a team. You can give any individual member of a team the team maintainer role, which gives the member a number of administrative permissions over a team. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." @@ -227,5 +227,5 @@ If your organization has a security team, you can use the security manager role ## 延伸阅读 -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" - "[组织的项目板权限](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md index 0ea73b302d..11706b5e6e 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -14,20 +14,20 @@ shortTitle: 使用 Octa 配置 SAML 和 SCIM ## 关于 SAML 和 SCIM 与 Octa -You can control access to your organization on {% data variables.product.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP). +通过将组织配置为将 SAML SSO 和 SCIM 与身份提供程序 (IdP) Okta 结合使用，您可以从一个中心界面控制对您 {% data variables.product.product_location %} 和其他 Web 应用程序上的组织的访问。 -SAML SSO 控制并保护对组织资源（如仓库、议题和拉取请求）的访问。 SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. 更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”和“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 +SAML SSO 控制并保护对组织资源（如仓库、议题和拉取请求）的访问。 当您在 Okta 中进行更改时，SCIM 会自动添加、管理和删除成员对您在 {% data variables.product.product_location %} 上的组织的访问权限。 更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”和“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 启用 SCIM 后，您在 Okta 中为其分配了 {% data variables.product.prodname_ghe_cloud %} 应用程序的任何用户都可以使用以下配置。 -| 功能 | 描述 | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 推送新用户 | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.product.product_location %}. | -| 推送用户停用 | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.product.product_location %}. | -| 推送个人资料更新 | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. | -| 重新激活用户 | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}. | +| 功能 | 描述 | +| -------- | ----------------------------------------------------------------------------------------------- | +| 推送新用户 | 当您在 Okta 中创建新用户时，该用户将收到一封电子邮件，要求您在 {% data variables.product.product_location %} 上加入您的组织。 | +| 推送用户停用 | 当您在 Okta 中停用用户时，Okta 将从您在 {% data variables.product.product_location %} 上的组织中删除该用户。 | +| 推送个人资料更新 | 当您在 Okta 中更新用户的个人资料时，Okta 将更新您在 {% data variables.product.product_location %} 上的组织中该用户成员身份的元数据。 | +| 重新激活用户 | 当您在 Okta 中重新激活用户时，Okta 将发送电子邮件邀请该用户在 {% data variables.product.product_location %} 上重新加入您的组织。 | -Alternatively, you can configure SAML SSO for an enterprise using Okta. SCIM for enterprise accounts is only available with Enterprise Managed Users. For more information, see "[Configuring SAML single sign-on for your enterprise using Okta](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" and "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)." +或者，您可以使用 Okta 为企业配置 SAML SSO。 适用于企业帐户的 SCIM 仅适用于企业托管用户。 更多信息请参阅“[使用 Okta 为企业配置 SAML 单点登录](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)”和“[使用 Okta 为企业托管用户配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)”。 ## 在 Okta 中添加 {% data variables.product.prodname_ghe_cloud %} 应用程序 diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md index de67765d4e..b17e1b0ad7 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -22,7 +22,7 @@ shortTitle: 连接 IdP - PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector) - Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home) -You can access your organization's service provider metadata at the following URL, replacing ORGANIZATION with your organization's username. +您可以通过以下 URL 访问组织的服务提供商元数据，将 ORGANIZATION 替换为您的组织的用户名。 ``` http(s)://github.com/orgs/ORGANIZATION/saml/metadata.xml diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md index ec2ecc4e31..90f24dc7d3 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -20,7 +20,7 @@ shortTitle: 强制 SAML 单点登录 您也可以对组织实施 SAML SSO。 {% data reusables.saml.when-you-enforce %} 实施会从组织中删除尚未通过 IdP 进行身份验证的任何成员和管理员。 {% data variables.product.company_short %} 将向每个被删除的用户发送电子邮件通知。 -{% data reusables.saml.removed-users-can-rejoin %} If a user rejoins the organization within three months, the user's access privileges and settings will be restored. 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。 +{% data reusables.saml.removed-users-can-rejoin %} 如果用户在三个月内重新加入组织，则该用户的访问权限和设置将恢复。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。 未在组织的 IdP 中设置外部身份的自动程序和服务帐户在执行 SAML SSO 时也将被删除。 有关自动程序和服务帐户的更多信息，请参阅“[使用 SAML 单点登录管理自动程序和服务帐户](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)”。 diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md index 7de8b7175e..167639f494 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -1,6 +1,6 @@ --- title: 管理组织的 SAML 单点登录 -intro: Organization owners can manage organization members' identities and access to the organization with SAML single sign-on (SSO). +intro: 组织所有者可以使用 SAML 单点登录 (SSO) 管理组织成员的身份以及对组织的访问。 redirect_from: - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on - /articles/managing-saml-single-sign-on-for-your-organization diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index ac145df40b..1d235b4652 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -44,11 +44,11 @@ shortTitle: 管理团队同步 您必须为您的组织和支持的 IdP 启用 SAML 单点登录。 更多信息请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。 -You must have a linked SAML identity. To create a linked identity, you must authenticate to your organization using SAML SSO and the supported IdP at least once. 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。 +您必须具有链接的 SAML 身份。 要创建链接身份，您必须至少使用 SAML SSO 和支持的 IdP 向您的组织进行身份验证一次。 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。 -Your SAML settings **must** contain a valid IdP URL for the **Issuer** field. +您的 SAML 设置**必须**包含**颁发者**字段的有效 IdP URL。 -![SAML Issuer field](/assets/images/help/saml/saml_issuer.png) +![SAML 颁发者字段](/assets/images/help/saml/saml_issuer.png) @@ -66,13 +66,13 @@ Your SAML settings **must** contain a valid IdP URL for the **Issuer** field. ### 为 Okta 启用团队同步 -Okta team synchronization requires that SAML and SCIM with Okta have already been set up for your organization. +Okta 团队同步要求已为您的组织设置了具有 Okta 的 SAML 和 SCIM。 -To avoid potential team synchronization errors with Okta, we recommend that you confirm that SCIM linked identities are correctly set up for all organization members who are members of your chosen Okta groups, before enabling team synchronization on {% data variables.product.prodname_dotcom %}. +为避免与 Okta 发生潜在的团队同步错误，我们建议您先确认已为属于所选 Okta 组成员的所有组织成员正确设置了 SCIM 链接身份，然后再在 {% data variables.product.prodname_dotcom %} 上启用团队同步。 -If an organization member does not have a linked SCIM identity, then team synchronization will not work as expected and the user may not be added or removed from teams as expected. If any of these users are missing a SCIM linked identity, you will need to re-provision them. +如果组织成员没有链接的 SCIM 身份，则团队同步将无法按预期工作，并且可能不会按预期在团队中添加或删除用户。 如果这些用户中的任何一个缺少 SCIM 链接身份，则需要重新预配它们。 -For help on provisioning users that have missing a missing SCIM linked identity, see "[Troubleshooting identity and access management](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management)." +有关预配缺少 SCIM 链接身份的用户的帮助，请参阅“[身份和访问管理疑难解答](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management)”。 {% data reusables.identity-and-permissions.team-sync-okta-requirements %} @@ -81,7 +81,7 @@ For help on provisioning users that have missing a missing SCIM linked identity, {% data reusables.organizations.security %} {% data reusables.identity-and-permissions.team-sync-confirm-saml %} {% data reusables.identity-and-permissions.team-sync-confirm-scim %} -1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. 更多信息请参阅“[对组织实施 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)”。 +1. 请考虑在组织中强制实施 SAML，以确保组织成员链接其 SAML 和 SCIM 身份。 更多信息请参阅“[对组织实施 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)”。 {% data reusables.identity-and-permissions.enable-team-sync-okta %} 7. 在组织名称下，输入有效的 SSWS 令牌和 Okta 实例的 URL。 ![启用团队同步 Okta 组织表单](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) 6. 查看要与组织连接的身份提供程序租户信息，然后单击 **Create（创建）**。 ![启用团队同步创建按钮](/assets/images/help/teams/confirm-team-synchronization-okta.png) diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md index 5195b3a9cb..7817857eaf 100644 --- a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md +++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md @@ -17,7 +17,7 @@ shortTitle: 转换管理员团队 要删除旧管理员团队成员创建仓库的权限，请为这些成员创建新团队，确保该团队对组织仓库具有必要的权限，然后删除旧管理员团队。 -For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 {% warning %} diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md index c36b84a842..94aaf49017 100644 --- a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md +++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md @@ -21,7 +21,7 @@ shortTitle: 迁移管理团队 您可以将旧管理员团队迁移到改进的组织权限，以删除此能力。 -For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 {% warning %} diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md index e79ec505e0..2298c5379c 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -3,7 +3,7 @@ title: 管理团队的预定提醒 intro: 当您的团队有等待审查的拉取请求时，您可以在 Slack 中收到提醒。 redirect_from: - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests - - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index cf3aabd4ab..91450cd1b0 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -19,11 +19,11 @@ shortTitle: 与 IdP 同步 {% data reusables.identity-and-permissions.about-team-sync %} -{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. 组中的所有用户将自动添加到团队中，并作为成员添加到父组织。 当您断开组与团队的连接时，通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。 +{% ifversion ghec %}您可以将最多 5 个 IdP 组连接到 {% data variables.product.product_name %} 团队。{% elsif ghae %}您可以将 {% data variables.product.product_name %} 上的团队连接到一个 IdP 组。 组中的所有用户将自动添加到团队中，并作为成员添加到父组织。 当您断开组与团队的连接时，通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。 -{% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} +{% ifversion ghec %}团队同步不支持超过 5000 个成员的 IdP 组。{% endif %} -{% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后，您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}. +{% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后，您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 您不能在 {% data variables.product.product_name %} 上{% ifversion ghec %}或使用 API{% endif %} 管理团队成员资格。 {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} @@ -39,7 +39,7 @@ shortTitle: 与 IdP 同步 要管理 {% data variables.product.prodname_dotcom %} 团队（包括连接到 IdP 组的团队）的仓库访问权限，您必须使用 {% data variables.product.product_name %} 进行更改。 更多信息请参阅“[关于团队](/articles/about-teams)”和“[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)”。 -{% ifversion ghec %}You can also manage team synchronization with the API. 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %} +{% ifversion ghec %}您还可以使用 API 管理团队同步。 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %} {% ifversion ghec %} ## 已同步团队成员的要求 diff --git a/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md index f0094c8972..1c25862e10 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md +++ b/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md @@ -46,7 +46,7 @@ shortTitle: 删除和恢复包 {% endif %} -For packages that inherit their permissions and access from repositories, you can use GraphQL to delete a specific package version.{% ifversion fpt or ghec %} The {% data variables.product.prodname_registry %} GraphQL API does not support containers or Docker images that use the package namespace `https://ghcr.io/OWNER/PACKAGE-NAME`.{% endif %} For more information about GraphQL support, see "[Deleting a version of a repository-scoped package with GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)." +对于从仓库继承其权限和访问权限的包，您可以使用 GraphQL 删除特定的包版本。{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} GraphQL API 不支持使用包命名空间的容器或 Docker 映像 `https://ghcr.io/OWNER/PACKAGE-NAME`。{% endif %} 有关 GraphQL 支持的更多信息，请参阅“[使用 GraphQL 删除存储库范围包的版本](#deleting-a-version-of-a-repository-scoped-package-with-graphql)”。 {% endif %} @@ -87,7 +87,7 @@ For packages that inherit their permissions and access from repositories, you ca 对于从仓库继承其许可和访问权限的包，您可以使用 GraphQL 删除特定的包版本。 {% ifversion fpt or ghec %} -For containers or Docker images at `ghcr.io`, GraphQL is not supported but you can use the REST API. 更多信息请参阅“[{% data variables.product.prodname_registry %} API](/rest/reference/packages)”。 +对于在 `ghcr.io` 上的容器或 Docker 映像，GraphQL 不受支持，但您可以使用 REST API。 更多信息请参阅“[{% data variables.product.prodname_registry %} API](/rest/reference/packages)”。 {% endif %} 在 GraphQL API 中使用 `deletePackageVersion` 突变。 必须使用具有 `read:packages`、`delete:packages` 和 `repo` 作用域的令牌。 有关令牌的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)”。 @@ -102,9 +102,9 @@ curl -X POST \ HOSTNAME/graphql ``` -To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. 您需要具有 `read:packages` 和 `repo` 作用域的令牌。 更多信息请参阅 [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) 连接或 [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) 接口。 +要查找已发布到 {% data variables.product.prodname_registry %} 的所有私有包以及包的版本 ID，您可以使用 `registryPackagesForQuery` 通过 `repository` 对象连接。 您需要具有 `read:packages` 和 `repo` 作用域的令牌。 更多信息请参阅 [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) 连接或 [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) 接口。 -For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/mutations#deletepackageversion)." +有关 `deletePackageVersion` 突变的更多信息，请参阅“[`deletePackageVersion`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/mutations#deletepackageversion)”。 您不能直接使用 GraphQL 删除整个包，但如果您删除包的每个版本，该包将不再显示在 {% data variables.product.product_name %} 上。 @@ -123,11 +123,11 @@ For more information about the `deletePackageVersion` mutation, see "[`deletePac 5. 在要删除的版本的右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 并选择 **Delete version（删除版本）**。 ![删除包版本按钮](/assets/images/help/package-registry/delete-container-package-version.png) 6. 要确认删除，请输入包名称，然后单击 **I understand the consequences, delete this version（我明白后果，删除此版本）**。 ![确认包删除按钮](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) -### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %} +### 在 {% data variables.product.prodname_dotcom %} 上删除组织范围的包版本 要在 {% data variables.product.prodname_dotcom %} 上删除组织范围包的特定版本，例如 `ghcr.io` 上的 Docker 映像，请使用以下步骤。 要删除整个包，请参阅“[删除 {% data variables.product.prodname_dotcom %} 上整个组织范围的包](#deleting-an-entire-organization-scoped-package-on-github)”。 -To review who can delete a package version, see "[Required permissions to delete or restore a package](#required-permissions-to-delete-or-restore-a-package)." +要查看谁可以删除包版本，请参阅“[删除或恢复包的必需权限](#required-permissions-to-delete-or-restore-a-package)”。 {% data reusables.package_registry.package-settings-from-org-level %} {% data reusables.package_registry.package-settings-option %} @@ -176,17 +176,17 @@ To review who can delete a package version, see "[Required permissions to delete - 您在删除后 30 天内恢复包。 - 相同的包名称空间和版本仍然可用，并且不重复用于新包。 -For example, if you have a deleted RubyGems package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed. +例如，如果您删除了名为 `octo-package` 且范围为 repo `octo-repo-owner/octo-repo` 的 RubyGems 包，则您仅在包名称空间 `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` 仍然可用且 30 天未过时才可恢复包。 {% ifversion fpt or ghec %} -To restore a deleted package, you must also meet one of these permission requirements: +要恢复已删除的包，您还必须满足以下权限要求之一： - 对于仓库范围的包：您必须对拥有删除的包的仓库具有管理员权限。{% ifversion fpt or ghec %} - 对于用户帐户范围的包：您的用户帐户拥有已删除的包。 - 对于组织范围的包：您对拥有包的组织中删除的包具有管理员权限。{% endif %} {% endif %} {% ifversion ghae or ghes %} -To delete a package, you must also have admin permissions to the repository that owns the deleted package. +要删除包，还必须对拥有已删除包的仓库具有管理员权限。 {% endif %} 更多信息请参阅“[必需权限](#required-permissions-to-delete-or-restore-a-package)”。 @@ -195,7 +195,7 @@ To delete a package, you must also have admin permissions to the repository that ### 恢复组织中的包 - You can restore a deleted package through your organization account settings, as long as the package was in a repository owned by the organizaton{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}. + 您可以通过组织帐户设置恢复已删除的包，只要该包位于 organizaton{% ifversion fpt or ghec %} 拥有的仓库中，或者具有粒度权限，并且范围限定在您的组织帐户{% endif %}。 要查看谁可以恢复组织中的包，请参阅“[必需权限](#required-permissions-to-delete-or-restore-a-package)”。 diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md index d550f8de7c..7616b95e0b 100644 --- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md +++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -56,9 +56,9 @@ Apex 域配置通过 DNS 提供商使用 `A`, `ALAS` 或 `ANAME` 记录配置。 {% data reusables.pages.www-and-apex-domain-recommendation %}更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)”。 -## Securing the custom domain for your {% data variables.product.prodname_pages %} site +## 保护 {% data variables.product.prodname_pages %} 网站的自定义域 -{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)." +{% data reusables.pages.secure-your-domain %} 更多信息请参阅“[验证 {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)的自定义域”和“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。 有许多原因会导致您的网站被自动禁用。 diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md index 8dcde193da..58817207c7 100644 --- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md +++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -134,9 +134,9 @@ shortTitle: 管理自定义域 {% data reusables.pages.sidebar-pages %} 4. 在“Custom domain（自定义域）”下，单击 **Remove（删除）**。 ![保存自定义域按钮](/assets/images/help/pages/remove-custom-domain.png) -## Securing your custom domain +## 保护自定义域 -{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." +{% data reusables.pages.secure-your-domain %} 更多信息请参阅“[验证自定义域的 {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)”。 ## 延伸阅读 diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index b7e80cbcb4..882efc96de 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -1,6 +1,6 @@ --- title: 配置 GitHub Pages 站点的发布源 -intro: '如果您使用 {% data variables.product.prodname_pages %} 站点的默认发布源，您的站点将自动发布。 You can also choose to publish your site from a different branch or folder.' +intro: '如果您使用 {% data variables.product.prodname_pages %} 站点的默认发布源，您的站点将自动发布。 您也可以选择从不同的分支或文件夹发布您的站点。' redirect_from: - /articles/configuring-a-publishing-source-for-github-pages - /articles/configuring-a-publishing-source-for-your-github-pages-site @@ -21,7 +21,7 @@ shortTitle: 配置发布源 ## 选择发布源 -Before you configure a publishing source, make sure the branch you want to use as your publishing source already exists in your repository. +在配置发布源之前，请确保您要用作发布源的分支已经存在于您的仓库中。 {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} @@ -34,13 +34,13 @@ Before you configure a publishing source, make sure the branch you want to use a {% data reusables.pages.admin-must-push %} -If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误疑难排解](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)”。 +如果选择任意分支上的 `docs` 文件夹作为发布源，然后从仓库的该分支中删除了 `/docs` 文件夹，则您的站点将不会构建，并且您将收到提示缺失 `/docs` 文件夹的页面构建错误。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误疑难排解](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)”。 {% ifversion fpt %} -Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} worfklow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers. +{% data variables.product.prodname_pages %} 站点将始终使用 {% data variables.product.prodname_actions %} 工作流程运行进行部署，即使您已将 {% data variables.product.prodname_pages %} 站点配置为使用其他 CI 工具构建也是如此。 大多数外部 CI 工作流程通过将构建输出提交到仓库的 `gh-pages` 分支来“部署”到 GitHub Pages，并且通常包含一个 `.nojekyll` 文件。 发生这种情况时， {% data variables.product.prodname_actions %} 工作流程将检测分支不需要构建步骤的状态，并且仅执行将站点部署到 {% data variables.product.prodname_pages %} 服务器所需的步骤。 -To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." +若要查找构建或部署的潜在错误，可以通过查看仓库的工作流程运行来检查 {% data variables.product.prodname_pages %} 站点的工作流程运行情况。 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 有关如何在出现错误时重新运行工作流程的详细信息，请参阅”[重新运行工作流程和作业](/actions/managing-workflow-runs/re-running-workflows-and-jobs)“。 {% note %} diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md index 05bee74a23..a527958161 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -45,7 +45,7 @@ shortTitle: 创建 GitHub Pages 站点 {% tip %} - **Tip:** If `index.html` is present, this will be used instead of `index.md`. If neither `index.html` nor `index.md` are present, `README.md` will be used. + **提示：** 如果存在 `index.html`，则将使用它而不是 `index.md`。 如果没有 `index.html` 或 `index.md`，将使用 `README.md`。 {% endtip %} {% data reusables.pages.configure-publishing-source %} diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 0ac40bc970..d32aa21230 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -36,11 +36,11 @@ shortTitle: 使用 HTTPS 保护站点 {% data reusables.pages.sidebar-pages %} 3. 在 "{% data variables.product.prodname_pages %}" 下，选择 **Enforce HTTPS（实施 HTTPS）**。 ![强制实施 HTTPS 复选框](/assets/images/help/pages/enforce-https-checkbox.png) -## Troubleshooting certificate provisioning ("Certificate not yet created" error") +## 证书预配疑难解答（”证书尚未创建“错误） -When you set or change your custom domain in the Pages settings, an automatic DNS check begins. This check determines if your DNS settings are configured to allow {% data variables.product.prodname_dotcom %} to obtain a certificate automatically. If the check is successful, {% data variables.product.prodname_dotcom %} queues a job to request a TLS certificate from [Let's Encrypt](https://letsencrypt.org/). On receiving a valid certificate, {% data variables.product.prodname_dotcom %} automatically uploads it to the servers that handle TLS termination for Pages. When this process completes successfully, a check mark is displayed beside your custom domain name. +当您在 Pages 设置中设置或更改自定义域名时，系统会开始自动进行 DNS 检查。 此检查确定您的 DNS 设置是否配置为允许 {% data variables.product.prodname_dotcom %} 自动获取证书。 如果检查成功，{% data variables.product.prodname_dotcom %} 将作业排队以从 [Let's Encrypt](https://letsencrypt.org/) 请求 TLS 证书。 收到有效证书后，{% data variables.product.prodname_dotcom %} 会自动将其上传到处理 Pages 的 TLS 终止的服务器。 成功完成此过程后，您的自定义域名旁边将显示一个复选标记。 -The process may take some time. If the process has not completed several minutes after you clicked **Save**, try clicking **Remove** next to your custom domain name. Retype the domain name and click **Save** again. This will cancel and restart the provisioning process. +该过程可能需要一些时间。 如果在单击 **Save（保存）**后几分钟内该过程尚未完成，请尝试单击自定义域名旁边的 **Remove（删除）** 。 重新键入域名，然后再次单击 **Save（保存）** 。 这将取消并重新启动预配过程。 ## 解决具有混合内容的问题 diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md index 8f7765d94a..e777c04c96 100644 --- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -112,7 +112,7 @@ kramdown: 为了使网站更容易读取，代码片段在 {% data variables.product.prodname_pages %} 上突显，就像在 {% data variables.product.product_name %} 上突显一样。 有关在 {% data variables.product.product_name %} 上突显语法的更多信息，请参阅“[创建和突显代码块](/articles/creating-and-highlighting-code-blocks)”。 -默认情况下，网站上的代码块将被 Jekyll 突出显示。 Jekyll 使用 [Rouge](https://github.com/jneen/rouge) 突显工具，它兼容于 [Pygments](http://pygments.org/)。 Pygments has been deprecated and not supported in Jekyll 4. If you specify Pygments in your *_config.yml* file, Rouge will be used as the fallback instead. Jekyll 不能使用任何其他语法突显工具，如果您在 *_config.yml* 文件中指定其他语法突显工具，将会收到页面构建警告。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/about-jekyll-build-errors-for-github-pages-sites)”。 +默认情况下，网站上的代码块将被 Jekyll 突出显示。 Jekyll 使用 [Rouge](https://github.com/jneen/rouge) 突显工具，它兼容于 [Pygments](http://pygments.org/)。 Pygments 已被弃用，在 Jekyll 4 中不受支持。 如果在 *_config.yml* 文件中指定 Pygments，将改用 Rouge。 Jekyll 不能使用任何其他语法突显工具，如果您在 *_config.yml* 文件中指定其他语法突显工具，将会收到页面构建警告。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/about-jekyll-build-errors-for-github-pages-sites)”。 如果想使用其他突显工具，如 `highlight.js`，则必须更新项目的 *_config.yml* 文件来禁用 Jekyll 的语法突显。 diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md index 8cf6e9d198..067e4e6dec 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md @@ -20,7 +20,7 @@ topics: {% endtip %} -必须具有适当的权限才可执行使用相关查询参数的操作。 例如，必须具有向拉取请求添加标签的权限才可使用 `labels` 查询参数。 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +必须具有适当的权限才可执行使用相关查询参数的操作。 例如，必须具有向拉取请求添加标签的权限才可使用 `labels` 查询参数。 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 如果使用查询参数创建无效的 URL，或者没有适当的权限，URL 将返回 `404 未找到`错误页。 如果您创建的 URL 超过服务器限制，URL 将返回 `414 URI 过长`错误页面。 diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md index 6d8dd472c1..8b5f469d07 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -69,7 +69,7 @@ When you create a repository owned by your user account, the repository is alway - 所有企业成员均可访问内部仓库。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。 {%- endif %} -组织所有者始终有权访问其组织中创建的每个仓库。 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +组织所有者始终有权访问其组织中创建的每个仓库。 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 拥有仓库管理员权限的人可更改现有仓库的可见性。 更多信息请参阅“[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)”。 diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md index 2170eb83dc..a94235483d 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md @@ -26,4 +26,4 @@ shortTitle: 管理复刻策略 ## 延伸阅读 - "[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index aec9f4dc6c..1decc68bee 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -101,4 +101,4 @@ Members of an {% data variables.product.prodname_emu_enterprise %} can only set ## 延伸阅读 -- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" +- "[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" diff --git a/translations/zh-CN/content/rest/guides/delivering-deployments.md b/translations/zh-CN/content/rest/guides/delivering-deployments.md index 67f057f501..8cff3c3e63 100644 --- a/translations/zh-CN/content/rest/guides/delivering-deployments.md +++ b/translations/zh-CN/content/rest/guides/delivering-deployments.md @@ -20,7 +20,7 @@ topics: 本指南将使用该 API 来演示您可以使用的设置。 在我们的场景中，我们将： -* Merge a pull request. +* 合并拉取请求. * 在 CI 完成后，我们将相应地设置拉取请求的状态。 * 合并拉取请求后，我们将在服务器上运行部署。 diff --git a/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md b/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md index 7ba179781b..68292f390e 100644 --- a/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md +++ b/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md @@ -26,7 +26,7 @@ shortTitle: 为用户发现资源 ## 发现您的应用程序能够为用户访问的仓库 -用户除了拥有他们自己的个人仓库之外，可能还是其他用户和组织所拥有仓库上的协作者。 Collectively, these are the repositories where the user has privileged access: either it's a private repository where the user has read or write access, or it's {% ifversion fpt %}a public{% elsif ghec or ghes %}a public or internal{% elsif ghae %}an internal{% endif %} repository where the user has write access. +用户除了拥有他们自己的个人仓库之外，可能还是其他用户和组织所拥有仓库上的协作者。 总的来说，这些仓库是用户有权访问的仓库：要么是用户具有读取或写入权限的私有仓库，要么是用户具有写入权限的{% ifversion fpt %}公共{% elsif ghec or ghes %}公共或内部{% elsif ghae %}内部{% endif %}仓库。 [OAuth 作用域][scopes]和[组织应用程序策略][oap]决定了您的应用程序可以为用户访问其中哪些仓库。 使用下面的工作流程来发现这些仓库。 diff --git a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md index 17a964632a..4791afc212 100644 --- a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md @@ -1,6 +1,6 @@ --- -title: REST API 入门指南 -intro: 从身份验证和一些端点示例开始，了解使用 REST API 的基础。 +title: Getting started with the REST API +intro: 'Learn the foundations for using the REST API, starting with authentication and some endpoint examples.' redirect_from: - /guides/getting-started - /v3/guides/getting-started @@ -11,23 +11,28 @@ versions: ghec: '*' topics: - API -shortTitle: 开始 - REST API +shortTitle: Get started - REST API --- -让我们逐步了解在处理一些日常用例时涉及的核心 API 概念。 +Let's walk through core API concepts as we tackle some everyday use cases. {% data reusables.rest-api.dotcom-only-guide-note %} -## 概览 +## Overview -大多数应用程序将使用您选择的语言 中现有的 [wrapper 库][wrappers]，但您必须先熟悉基础 API HTTP 方法。 +Most applications will use an existing [wrapper library][wrappers] in the language +of your choice, but it's important to familiarize yourself with the underlying API +HTTP methods first. -没有比使用 [cURL][curl] 更容易的入手方式了。{% ifversion fpt or ghec %} 如果您使用其他客户的，请注意，您需要在请求中发送有效的 [用户代理标头](/rest/overview/resources-in-the-rest-api#user-agent-required)。{% endif %} +There's no easier way to kick the tires than through [cURL][curl].{% ifversion fpt or ghec %} If you are using +an alternative client, note that you are required to send a valid +[User Agent header](/rest/overview/resources-in-the-rest-api#user-agent-required) in your request.{% endif %} ### Hello World -让我们先测试设置。 打开命令提示符并输入以下命令： +Let's start by testing our setup. Open up a command prompt and enter the +following command: ```shell $ curl https://api.github.com/zen @@ -35,9 +40,9 @@ $ curl https://api.github.com/zen > Keep it logically awesome. ``` -响应将是我们设计理念中的随机选择。 +The response will be a random selection from our design philosophies. -接下来，我们 `GET` [Chris Wanstrath 的][defunkt github] [GitHub 资料][users api]： +Next, let's `GET` [Chris Wanstrath's][defunkt github] [GitHub profile][users api]: ```shell # GET /users/defunkt @@ -55,7 +60,7 @@ $ curl https://api.github.com/users/defunkt > } ``` -嗯，有点像 [JSON][json]。 我们来添加 `-i` 标志以包含标头： +Mmmmm, tastes like [JSON][json]. Let's add the `-i` flag to include headers: ```shell $ curl -i https://api.github.com/users/defunkt @@ -99,64 +104,75 @@ $ curl -i https://api.github.com/users/defunkt > } ``` -响应标头中有一些有趣的地方。 果然，`Content-Type` 为 `application/json`。 +There are a few interesting bits in the response headers. As expected, the +`Content-Type` is `application/json`. -任何以 `X-` 开头的标头都是自定义标头，不包含在 HTTP 规范中。 例如： +Any headers beginning with `X-` are custom headers, and are not included in the +HTTP spec. For example: -* `X-GitHub-Media-Type` 的值为 `github.v3`。 这让我们知道响应的[媒体类型][media types]。 媒体类型帮助我们在 API v3 中对输出进行版本控制。 我们稍后再详细讨论。 -* 请注意 `X-RateLimit-Limit` 和 `X-RateLimit-Remaining` 标头。 This pair of headers indicate [how many requests a client can make][rate-limiting] in a rolling time period (typically an hour) and how many of those requests the client has already spent. +* `X-GitHub-Media-Type` has a value of `github.v3`. This lets us know the [media type][media types] +for the response. Media types have helped us version our output in API v3. We'll +talk more about that later. +* Take note of the `X-RateLimit-Limit` and `X-RateLimit-Remaining` headers. This +pair of headers indicate [how many requests a client can make][rate-limiting] in +a rolling time period (typically an hour) and how many of those requests the +client has already spent. -## 身份验证 +## Authentication -未经身份验证的客户端每小时可以发出 60 个请求。 要每小时发出更多请求，我们需要进行_身份验证_。 事实上，使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行任何交互都需要[身份验证][authentication]。 +Unauthenticated clients can make 60 requests per hour. To get more requests per hour, we'll need to +_authenticate_. In fact, doing anything interesting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API requires +[authentication][authentication]. -### 使用个人访问令牌 +### Using personal access tokens -使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行身份验证的最简单和最佳的方式是[通过 OAuth 令牌](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)使用基本身份验证。 OAuth 令牌包括[个人访问令牌][personal token]。 +The easiest and best way to authenticate with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is by using Basic Authentication [via OAuth tokens](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). OAuth tokens include [personal access tokens][personal token]. -使用 `-u` 标志设置您的用户名： +Use a `-u` flag to set your username: ```shell $ curl -i -u your_username {% data variables.product.api_url_pre %}/users/octocat ``` -出现提示时，您可以输入 OAuth 令牌，但我们建议您为它设置一个变量： +When prompted, you can enter your OAuth token, but we recommend you set up a variable for it: -您可以使用 `-u "your_username:$token"` 并为 `token` 设置一个变量，以避免您的令牌留在 shell 历史记录中，这种情况应尽量避免。 +You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. ```shell $ curl -i -u your_username:$token {% data variables.product.api_url_pre %}/users/octocat ``` -进行身份验证时，您应该会看到您的速率限制达到每小时 5,000 个请求，如 `X-RateLimit-Limit` 标头中所示。 除了每小时提供更多调用次数之外，身份验证还使您能够使用 API 读取和写入私有信息。 +When authenticating, you should see your rate limit bumped to 5,000 requests an hour, as indicated in the `X-RateLimit-Limit` header. In addition to providing more calls per hour, authentication enables you to read and write private information using the API. -您可以使用[个人访问令牌设置页面][tokens settings]轻松[创建**个人访问令牌**][personal token]。 +You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]: {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} {% warning %} -为了帮助保护您的信息安全，我们强烈建议为您的个人访问令牌设置一个到期日。 +To help keep your information secure, we highly recommend setting an expiration for your personal access tokens. {% endwarning %} {% endif %} {% ifversion fpt or ghes or ghec %} -![个人令牌选择](/assets/images/personal_token.png) +![Personal Token selection](/assets/images/personal_token.png) {% endif %} {% ifversion ghae %} -![个人令牌选择](/assets/images/help/personal_token_ghae.png) +![Personal Token selection](/assets/images/help/personal_token_ghae.png) {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} -使用到期的个人访问令牌的 API 请求将通过 `GitHub-Authentication-Token-Expiration` 标头返回该令牌的到期日期。 当令牌接近其过期日期时，您可以使用脚本中的标头来提供警告信息。 +API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date. {% endif %} -### 获取自己的用户个人资料 +### Get your own user profile -在正确验证身份后，您可以利用与 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户相关的权限。 。 例如，尝试获取 +When properly authenticated, you can take advantage of the permissions +associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For example, try getting +[your own user profile][auth user api]: ```shell $ curl -i -u your_username:your_token {% data variables.product.api_url_pre %}/user @@ -173,72 +189,89 @@ $ curl -i -u your_username:your_token {% data variables.produc > } ``` -此时，除了先前为 [@defunkt][defunkt github] 检索到的公共信息集之外，您还可以查看您的用户个人资料的非公共信息。 例如，您将在响应中看到 `plan` 对象，它提供有关帐户的 {% data variables.product.product_name %} 计划的详细信息。 +This time, in addition to the same set of public information we +retrieved for [@defunkt][defunkt github] earlier, you should also see the non-public information for your user profile. For example, you'll see a `plan` object in the response which gives details about the {% data variables.product.product_name %} plan for the account. -### 对应用程序使用 OAuth 令牌 +### Using OAuth tokens for apps -需要代表其他用户使用 API 读取或写入私有信息的应用程序应使用 [OAuth][oauth]。 +Apps that need to read or write private information using the API on behalf of another user should use [OAuth][oauth]. -OAuth 使用_令牌_。 令牌具有两大特点： +OAuth uses _tokens_. Tokens provide two big features: -* **可撤销访问权限**：用户可以随时撤销对第三方应用程序的授权 -* **有限访问权限**：用户可以在授权第三方应用程序前审查令牌将提供的具体访问权限。 +* **Revokable access**: users can revoke authorization to third party apps at any time +* **Limited access**: users can review the specific access that a token + will provide before authorizing a third party app -令牌应通过 [web 工作流程][webflow]进行创建。 应用程序将用户发送到 {% data variables.product.product_name %} 进行登录。 {% data variables.product.product_name %} 随后显示一个对话框，指示应用程序的名称以及应用程序经用户授权后具有的权限级别。 经用户授权访问后，{% data variables.product.product_name %} 将用户重定向到应用程序： +Tokens should be created via a [web flow][webflow]. An application +sends users to {% data variables.product.product_name %} to log in. {% data variables.product.product_name %} then presents a dialog +indicating the name of the app, as well as the level of access the app +has once it's authorized by the user. After a user authorizes access, {% data variables.product.product_name %} +redirects the user back to the application: -![GitHub 的 OAuth 提示](/assets/images/oauth_prompt.png) +![GitHub's OAuth Prompt](/assets/images/oauth_prompt.png) -**像对待密码一样对待 OAuth 令牌！**不要与其他用户共享它们，也不要将其存储在不安全的地方。 这些示例中的令牌是假的，并且更改了名称以免波及无辜。 +**Treat OAuth tokens like passwords!** Don't share them with other users or store +them in insecure places. The tokens in these examples are fake and the names have +been changed to protect the innocent. -现在我们已经掌握了进行身份验证的调用，接下来我们介绍[仓库 API][repos-api]。 +Now that we've got the hang of making authenticated calls, let's move along to +the [Repositories API][repos-api]. -## 仓库 +## Repositories -几乎任何有意义的 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 使用都会涉及某种级别的仓库信息。 信息。 我们可以像之前获取用户详细信息一样 [`GET` 仓库详细信息][get repo]： +Almost any meaningful use of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API will involve some level of Repository +information. We can [`GET` repository details][get repo] in the same way we fetched user +details earlier: ```shell $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap ``` -同样，我们可以查看[经身份验证用户的仓库][user repos api]： +In the same way, we can [view repositories for the authenticated user][user repos api]: ```shell $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` -或者，我们可以[列出其他用户的仓库][other user repos api]： +Or, we can [list repositories for another user][other user repos api]: ```shell $ curl -i {% data variables.product.api_url_pre %}/users/octocat/repos ``` -或者，我们可以[列出组织的仓库][org repos api]： +Or, we can [list repositories for an organization][org repos api]: ```shell $ curl -i {% data variables.product.api_url_pre %}/orgs/octo-org/repos ``` -从这些调用返回的信息将取决于我们进行身份验证时令牌所具有的作用域： +The information returned from these calls will depend on which scopes our token has when we authenticate: {%- ifversion fpt or ghec or ghes %} * A token with `public_repo` [scope][scopes] returns a response that includes all public repositories we have access to see on {% data variables.product.product_location %}. {%- endif %} * A token with `repo` [scope][scopes] returns a response that includes all {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories we have access to see on {% data variables.product.product_location %}. -如[文档][repos-api]所示，这些方法采用 `type` 参数，可根据用户对仓库的访问权限类型来过滤返回的仓库。 这样，我们可以只获取直接拥有的仓库、组织仓库或用户通过团队进行协作的仓库。 +As the [docs][repos-api] indicate, these methods take a `type` parameter that +can filter the repositories returned based on what type of access the user has +for the repository. In this way, we can fetch only directly-owned repositories, +organization repositories, or repositories the user collaborates on via a team. ```shell $ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=owner" ``` -在此示例中，我们只获取 octocat 拥有的仓库，而没有获取她协作的仓库。 请注意上面的引用 URL。 根据您的 shell 设置，cURL 有时需要一个引用 URL，否则它会忽略查询字符串。 +In this example, we grab only those repositories that octocat owns, not the +ones on which she collaborates. Note the quoted URL above. Depending on your +shell setup, cURL sometimes requires a quoted URL or else it ignores the +query string. -### 创建仓库 +### Create a repository -获取现有仓库的信息是一种常见的用例，但 -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 也支持创建新的仓库。 要[创建仓库][create repo]， -我们需要 `POST` 一些包含详细信息和配置选项的JSON。 +Fetching information for existing repositories is a common use case, but the +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API supports creating new repositories as well. To [create a repository][create repo], +we need to `POST` some JSON containing the details and configuration options. ```shell $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ @@ -251,11 +284,14 @@ $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghe {% data variables.product.api_url_pre %}/user/repos ``` -在这个最小的示例中，我们为博客（也许要在 [GitHub Pages][pages] 上提供）创建了一个新的私有仓库。 虽然博客 {% ifversion not ghae %}将是公开的{% else %}可供所有企业成员访问{% endif %}，但我们已经将仓库设置为私有。 在这一步中，我们还将使用自述文件和 [nanoc][nanoc] 风格的 [.gitignore 模板][gitignore templates]对其进行初始化。 +In this minimal example, we create a new private repository for our blog (to be served +on [GitHub Pages][pages], perhaps). Though the blog {% ifversion not ghae %}will be public{% else %}is accessible to all enterprise members{% endif %}, we've made the repository private. In this single step, we'll also initialize it with a README and a [nanoc][nanoc]-flavored [.gitignore template][gitignore templates]. -生成的仓库可在 `https://github.com//blog` 上找到。 要在您拥有的组织下创建仓库，只需将 API 方法从 `/user/repos` 更改为 `/orgs//repos`。 +The resulting repository will be found at `https://github.com//blog`. +To create a repository under an organization for which you're +an owner, just change the API method from `/user/repos` to `/orgs//repos`. -接下来，我们将获取新创建的仓库： +Next, let's fetch our newly created repository: ```shell $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog @@ -267,36 +303,46 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog > } ``` -哦，不！ 它去哪儿了？ 因为我们创建仓库为 _私有_，所以需要经过身份验证才能看到它。 如果您是一位资深的 HTTP 用户，您可能会预期返回 `403`。 由于我们不想泄露有关私有仓库的信息，因此在本例中，{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 返回 `404`，就好像说“我们既不能确认也不能否认这个仓库的存在”。 +Oh noes! Where did it go? Since we created the repository as _private_, we need +to authenticate in order to see it. If you're a grizzled HTTP user, you might +expect a `403` instead. Since we don't want to leak information about private +repositories, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API returns a `404` in this case, as if to say "we can +neither confirm nor deny the existence of this repository." -## 议题 +## Issues -{% data variables.product.product_name %} 上的议题 UI 旨在提供“恰到好处”的工作流程，不会妨碍您的其他工作。 通过 {% data variables.product.product_name %} [议题 API][issues-api]，您可以利用其他工具来提取数据或创建议题，以打造适合您的团队的工作流程。 +The UI for Issues on {% data variables.product.product_name %} aims to provide 'just enough' workflow while +staying out of your way. With the {% data variables.product.product_name %} [Issues API][issues-api], you can pull +data out or create issues from other tools to create a workflow that works for +your team. -与 github.com 一样，API 为经过身份验证的用户提供了一些查看议题的方法。 要 [查看您的所有议题][get issues api]，请调用 `GET /issues`： +Just like github.com, the API provides a few methods to view issues for the +authenticated user. To [see all your issues][get issues api], call `GET /issues`: ```shell $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` -要仅获取[您的某个 {% data variables.product.product_name %} 组织下的议题][get issues api]，请调用 `GET -/orgs//issues`： +To get only the [issues under one of your {% data variables.product.product_name %} organizations][get issues api], call `GET +/orgs//issues`: ```shell $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` -我们还可以获取[单个仓库下的所有议题][repo issues api]： +We can also get [all the issues under a single repository][repo issues api]: ```shell $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues ``` -### 分页 +### Pagination -一个 Rails 规模的项目有数千个议题。 我们需要[分页][pagination]，进行多次 API 调用来获取数据。 我们来重复上次调用，这次请注意响应标头： +A project the size of Rails has thousands of issues. We'll need to [paginate][pagination], +making multiple API calls to get the data. Let's repeat that last call, this +time taking note of the response headers: ```shell $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues @@ -308,13 +354,20 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues > ... ``` -[`Link` 标头][link-header]提供了一种链接到外部资源（在本例中为额外的数据页面）的方法。 由于我们的调用发现的议题超过 30 个（默认页面大小），因此 API 将告诉我们在哪里可以找到结果的下一页和最后一页。 +The [`Link` header][link-header] provides a way for a response to link to +external resources, in this case additional pages of data. Since our call found +more than thirty issues (the default page size), the API tells us where we can +find the next page and the last page of results. -### 创建议题 +### Creating an issue -我们已经了解如何分页议题列表，现在我们来使用 API [创建议题][create issue]。 +Now that we've seen how to paginate lists of issues, let's [create an issue][create issue] from +the API. -要创建议题，我们需要进行身份验证，因此我们将在标头中传递 OAuth 令牌。 此外，我们还将 JSON 正文中的标题、正文和标签传递到要在其中创建议题的仓库下的 `/issues` 路径： +To create an issue, we need to be authenticated, so we'll pass an +OAuth token in the header. Also, we'll pass the title, body, and labels in the JSON +body to the `/issues` path underneath the repository in which we want to create +the issue: ```shell $ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ @@ -366,11 +419,14 @@ $ {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues > } ``` -JSON 响应的 `Location` 响应标头和 `url` 字段为我们提供了一些新建议题的指示。 +The response gives us a couple of pointers to the newly created issue, both in +the `Location` response header and the `url` field of the JSON response. -## 条件请求 +## Conditional requests -通过缓存未更改的信息来遵守速率限制，是成为一个良好 API 公民的重要特质。 API 支持[条件请求][conditional-requests]并帮助您正确行事。 请注意我们为获取 defunkt 的个人资料而进行的第一个调用： +A big part of being a good API citizen is respecting rate limits by caching information that hasn't changed. The API supports [conditional +requests][conditional-requests] and helps you do the right thing. Consider the +first call we made to get defunkt's profile: ```shell $ curl -i {% data variables.product.api_url_pre %}/users/defunkt @@ -379,7 +435,10 @@ $ curl -i {% data variables.product.api_url_pre %}/users/defunkt > etag: W/"61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0" ``` -除了 JSON 正文之外，还要注意 HTTP 状态代码 `200` 和 `Etag` 标头。 [ETag][etag] 是响应的指纹。 如果我们在后续调用中传递它，则可以告诉 API 仅在资源发生改变的情况才将其再次提供给我们。 +In addition to the JSON body, take note of the HTTP status code of `200` and +the `ETag` header. +The [ETag][etag] is a fingerprint of the response. If we pass that on subsequent calls, +we can tell the API to give us the resource again, only if it has changed: ```shell $ curl -i -H 'If-None-Match: "61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"' \ @@ -388,24 +447,25 @@ $ {% data variables.product.api_url_pre %}/users/defunkt > HTTP/2 304 ``` -`304` 状态表示该资源自上次请求以来没有发生改变，该响应将不包含任何正文。 As a bonus, `304` responses don't count against your [rate limit][rate-limiting]. +The `304` status indicates that the resource hasn't changed since the last time +we asked for it and the response will contain no body. As a bonus, `304` responses don't count against your [rate limit][rate-limiting]. -现在您了解 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的基础知识了！ +Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API! -* 基本 & OAuth 身份验证 -* 获取和创建仓库及议题 -* 条件请求 +* Basic & OAuth authentication +* Fetching and creating repositories and issues +* Conditional requests -继续学习下一个 API 指南 - [身份验证基础知识][auth guide]！ +Keep learning with the next API guide [Basics of Authentication][auth guide]! [wrappers]: /libraries/ [curl]: http://curl.haxx.se/ [media types]: /rest/overview/media-types [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/ [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ +[create a new authorization API]: /rest/reference/oauth-authorizations#create-a-new-authorization [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ [repos-api]: /rest/reference/repos -[repos-api]: /rest/reference/repos [pages]: http://pages.github.com [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore @@ -413,13 +473,14 @@ $ {% data variables.product.api_url_pre %}/users/defunkt [link-header]: https://www.w3.org/wiki/LinkHeader [conditional-requests]: /rest#conditional-requests [rate-limiting]: /rest/overview/resources-in-the-rest-api#rate-limit-http-headers -[rate-limiting]: /rest/overview/resources-in-the-rest-api#rate-limit-http-headers [users api]: /rest/reference/users#get-a-user -[defunkt github]: https://github.com/defunkt +[auth user api]: /rest/reference/users#get-the-authenticated-user [defunkt github]: https://github.com/defunkt [json]: http://en.wikipedia.org/wiki/JSON [authentication]: /rest#authentication -[personal token]: /articles/creating-an-access-token-for-command-line-use +[2fa]: /articles/about-two-factor-authentication +[2fa header]: /rest/overview/other-authentication-methods#working-with-two-factor-authentication +[oauth section]: /rest/guides/getting-started-with-the-rest-api#oauth [personal token]: /articles/creating-an-access-token-for-command-line-use [tokens settings]: https://github.com/settings/tokens [pagination]: /rest#pagination @@ -431,6 +492,6 @@ $ {% data variables.product.api_url_pre %}/users/defunkt [other user repos api]: /rest/reference/repos#list-repositories-for-a-user [org repos api]: /rest/reference/repos#list-organization-repositories [get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user -[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user [repo issues api]: /rest/reference/issues#list-repository-issues [etag]: http://en.wikipedia.org/wiki/HTTP_ETag +[2fa section]: /rest/guides/getting-started-with-the-rest-api#two-factor-authentication diff --git a/translations/zh-CN/content/rest/guides/working-with-comments.md b/translations/zh-CN/content/rest/guides/working-with-comments.md index abbaa25843..0b8921b4d2 100644 --- a/translations/zh-CN/content/rest/guides/working-with-comments.md +++ b/translations/zh-CN/content/rest/guides/working-with-comments.md @@ -73,7 +73,7 @@ end ## 提交注释 -最后一类注释专门针对单个提交。 For this reason, they make use of [the commit comment API][commit comment API]. +最后一类注释专门针对单个提交。 因此，它们使用 [提交注释 API][commit comment API]。 要检索对提交的注释，您需要使用该提交的 SHA1。 换句话说，您不能使用与拉取请求相关的任何标识符。 例如： diff --git a/translations/zh-CN/content/rest/index.md b/translations/zh-CN/content/rest/index.md index d27742aeca..969127dea5 100644 --- a/translations/zh-CN/content/rest/index.md +++ b/translations/zh-CN/content/rest/index.md @@ -1,7 +1,7 @@ --- title: GitHub REST API shortTitle: REST API -intro: 'To create integrations, retrieve data, and automate your workflows, build with the {% data variables.product.prodname_dotcom %} REST API.' +intro: '要创建集成、检索数据和自动化工作流程，请使用 {% data variables.product.prodname_dotcom %} REST API 构建。' introLinks: quickstart: /rest/guides/getting-started-with-the-rest-api featuredLinks: diff --git a/translations/zh-CN/content/rest/reference/actions.md b/translations/zh-CN/content/rest/reference/actions.md index 43cfd74a1d..8f93fca885 100644 --- a/translations/zh-CN/content/rest/reference/actions.md +++ b/translations/zh-CN/content/rest/reference/actions.md @@ -1,6 +1,6 @@ --- title: 操作 -intro: 'With the Actions API, you can manage and control {% data variables.product.prodname_actions %} for an organization or repository.' +intro: '通过 Actions API，您可以管理和控制组织或仓库的 {% data variables.product.prodname_actions %}。' redirect_from: - /v3/actions versions: @@ -33,7 +33,7 @@ miniTocMaxHeadingLevel: 3 {% ifversion fpt or ghes > 2.22 or ghae or ghec %} ## 权限 -The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions 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 %} +Permissions API 允许您为允许哪些组织和存储库运行 {% data variables.product.prodname_actions %} 以及允许运行哪些操作设置权限。{% ifversion fpt or ghec or ghes %} 更多信息请参阅“[使用限制、计费和管理](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)”。{% endif %} 您还可以为企业设置权限。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#github-actions)”REST API。 diff --git a/translations/zh-CN/content/rest/reference/billing.md b/translations/zh-CN/content/rest/reference/billing.md index e645927dbc..6136986e50 100644 --- a/translations/zh-CN/content/rest/reference/billing.md +++ b/translations/zh-CN/content/rest/reference/billing.md @@ -1,6 +1,6 @@ --- title: 计费 -intro: 'With the Billing API, you can monitor the charges and usage {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} for a user or organization.' +intro: '使用计费 API，可以监视用户或组织的费用和使用情况 {% data variables.product.prodname_actions %} 及 {% data variables.product.prodname_registry %}。' versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/rest/reference/checks.md b/translations/zh-CN/content/rest/reference/checks.md index 509650033d..88cf892caa 100644 --- a/translations/zh-CN/content/rest/reference/checks.md +++ b/translations/zh-CN/content/rest/reference/checks.md @@ -1,6 +1,6 @@ --- title: 检查 -intro: 'With the Checks API, you can build {% data variables.product.prodname_github_apps %} that run powerful checks against the code changes in a repository.' +intro: '使用 Checks API，您可以构建 {% data variables.product.prodname_github_apps %} ，针对仓库中的代码更改运行强大的检查。' redirect_from: - /v3/checks versions: diff --git a/translations/zh-CN/content/rest/reference/migrations.md b/translations/zh-CN/content/rest/reference/migrations.md index 85756d8dd1..be4405d4b5 100644 --- a/translations/zh-CN/content/rest/reference/migrations.md +++ b/translations/zh-CN/content/rest/reference/migrations.md @@ -19,7 +19,7 @@ miniTocMaxHeadingLevel: 3 ## 组织 -迁移 API 仅适用于经过身份验证的组织所有者。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." +迁移 API 仅适用于经过身份验证的组织所有者。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)”和“[其他身份验证方法](/rest/overview/other-authentication-methods)”。 {% data variables.migrations.organization_migrations_intro %} diff --git a/translations/zh-CN/content/rest/reference/packages.md b/translations/zh-CN/content/rest/reference/packages.md index 9f00278744..8af15e78f9 100644 --- a/translations/zh-CN/content/rest/reference/packages.md +++ b/translations/zh-CN/content/rest/reference/packages.md @@ -1,6 +1,6 @@ --- title: Packages -intro: '通过 {% data variables.product.prodname_registry %} API，您可以管理 {% data variables.product.prodname_dotcom %} 仓库和组织的软件包。' +intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.' product: '{% data reusables.gated-features.packages %}' versions: fpt: '*' @@ -10,16 +10,16 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data variables.product.prodname_registry %} API 允许您使用 REST API 管理包。 要了解有关恢复或删除包的更多信息，请参阅“[恢复和删除包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 +The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)." -要使用此 API ，您必须使用个人访问令牌进行验证。 - - 要访问包元数据，您的令牌必须包括 `read:packages` 范围。 - - 要删除包和包版本，您的令牌必须包括 `read:packages` 和 `delete:packages` 范围。 - - 要恢复包和包版本，您的令牌必须包括 `read:packages` 和 `write:packages` 范围。 +To use this API, you must authenticate using a personal access token. + - To access package metadata, your token must include the `read:packages` scope. + - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes. + - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes. -如果您的 `package_type` 是 `npm`、`maven`、`rubygems` 或 `nuget`，则您的令牌必须还包括 `repo` 范围，因为您的包从 {% data variables.product.prodname_dotcom %} 仓库继承权限。 如果您的包位于 {% data variables.product.prodname_container_registry %}，则 `package_type` 是 `container`，且令牌不需要 `repo` 作用域便可访问或管理此 `package_type`。 `container` 包提供与仓库分开的粒度权限。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %} 的权限](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)”。 +If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)." -如果您想使用 {% data variables.product.prodname_registry %} API 访问已启用 SSO 的组织中的资源，则必须对个人访问令牌启用 SSO。 For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your personal access token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/zh-CN/content/rest/reference/pages.md b/translations/zh-CN/content/rest/reference/pages.md index 5e58418b95..238ec7512a 100644 --- a/translations/zh-CN/content/rest/reference/pages.md +++ b/translations/zh-CN/content/rest/reference/pages.md @@ -27,6 +27,7 @@ miniTocMaxHeadingLevel: 3 - `branch`：用于发布[站点源文件](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)的仓库分支。 例如，_main_ 或 _gh-pages_。 - `path`：提供站点发布内容的仓库目录。 可能是 `/` 或 `/docs`。 +{% comment %}An extra blank line is needed here to make sure the operations below don't continue the list above.{% endcomment %} {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} diff --git a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md index b7132b223d..19406639a3 100644 --- a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md @@ -876,7 +876,7 @@ _团队_ {% endif %} {% ifversion fpt or ghec or ghes > 3.3%} -### Permission on "dependabot_secrets" +### 对 "dependabot_secrets" 的权限 - [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (:read) - [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (:read) - [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (:read) diff --git a/translations/zh-CN/content/rest/reference/rate-limit.md b/translations/zh-CN/content/rest/reference/rate-limit.md index d3bb10238c..f671823d3b 100644 --- a/translations/zh-CN/content/rest/reference/rate-limit.md +++ b/translations/zh-CN/content/rest/reference/rate-limit.md @@ -30,6 +30,6 @@ REST API 概述文档描述了[速率限制规则](/rest/overview/resources-in-t * `integration_manifest` 对象提供 [GitHub 应用程序清单代码转换](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)端点的速率限制状态。 -For more information on the headers and values in the rate limit response, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)." +有关速率限制响应中标头和值的更多信息，请参阅“[REST API 中的资源](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)”。 {% include rest_operations_at_current_path %} diff --git a/translations/zh-CN/content/rest/reference/search.md b/translations/zh-CN/content/rest/reference/search.md index 1f196902aa..3d50fc832d 100644 --- a/translations/zh-CN/content/rest/reference/search.md +++ b/translations/zh-CN/content/rest/reference/search.md @@ -51,7 +51,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -See "[Searching on GitHub](/search-github/searching-on-github)" for a complete list of available qualifiers, their format, and an example of how to use them. 有关如何使用运算符匹配特定数量、日期或排除结果，请参阅“[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)”。 +有关可用限定符及其格式的完整列表和使用示例，请参阅“[在 GitHub 上搜索](/search-github/searching-on-github)”。 有关如何使用运算符匹配特定数量、日期或排除结果，请参阅“[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)”。 ### 查询长度限制 @@ -69,7 +69,7 @@ See "[Searching on GitHub](/search-github/searching-on-github)" for a complete l ### 访问错误或缺少搜索结果 -You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. 例如，如果您的查询中包含 `repo:`、`user:` 或 `org:` 限定符，但它们请求的资源是您登录 {% data variables.product.prodname_dotcom %} 后无权访问的资源，则搜索将失败。 +您需要成功完成身份验证并且对您搜索查询的仓库具有访问权限，否则，您将看到 `422 Unprocessible Entry` 错误和“验证失败”消息。 例如，如果您的查询中包含 `repo:`、`user:` 或 `org:` 限定符，但它们请求的资源是您登录 {% data variables.product.prodname_dotcom %} 后无权访问的资源，则搜索将失败。 当您的搜索查询请求多个资源时，响应将只包含您有权访问的资源，并且**不会**提供列出未返回资源的错误消息。 diff --git a/translations/zh-CN/content/rest/reference/secret-scanning.md b/translations/zh-CN/content/rest/reference/secret-scanning.md index 9b6d8e4209..2cb0e7cdf5 100644 --- a/translations/zh-CN/content/rest/reference/secret-scanning.md +++ b/translations/zh-CN/content/rest/reference/secret-scanning.md @@ -1,6 +1,6 @@ --- -title: 秘密扫描 -intro: 要检索和更新来自私有仓库的秘密警报，您可以使用秘密扫描 API。 +title: Secret scanning +intro: 'To retrieve and update the secret alerts from a private repository, you can use Secret Scanning API.' versions: fpt: '*' ghes: '>=3.1' @@ -17,6 +17,6 @@ The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversi - Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below. {%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %} -有关 {% data variables.product.prodname_secret_scanning %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)”。 +For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." {% include rest_operations_at_current_path %} diff --git a/translations/zh-CN/content/rest/reference/teams.md b/translations/zh-CN/content/rest/reference/teams.md index 612eac25f1..59f72586c4 100644 --- a/translations/zh-CN/content/rest/reference/teams.md +++ b/translations/zh-CN/content/rest/reference/teams.md @@ -53,9 +53,9 @@ miniTocMaxHeadingLevel: 3 {% endfor %} {% ifversion ghec or ghae %} -## External groups +## 外部组 -The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization. +外部组 API 允许您查看可用于组织的外部身份提供程序组，并管理组织中外部组和团队之间的连接。 要使用此 API，经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。 @@ -64,8 +64,8 @@ The external groups API allows you to view the external identity provider groups **注意：** -- The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -- If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)." +- 外部组 API 仅适用于属于使用 {% data variables.product.prodname_emus %} 的企业中的组织。 更多信息请参阅“[关于企业管理用户](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。 +- 如果您的组织使用团队同步，则可以使用团队同步 API。 更多信息请参阅“[团队同步 API](#team-synchronization)”。 {% endnote %} {% endif %} @@ -85,7 +85,7 @@ The external groups API allows you to view the external identity provider groups {% note %} -**注意：** 团队同步 API 不能与 {% data variables.product.prodname_emus %} 一起使用。 To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)". +**注意：** 团队同步 API 不能与 {% data variables.product.prodname_emus %} 一起使用。 要了解有关管理 {% data variables.product.prodname_emu_org %} 的更多信息，请参阅“[外部组 API](/enterprise-cloud@latest/rest/reference/teams#external-groups)”。 {% endnote %} diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index 9c1ef47b56..3a2cf667b9 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -49,27 +49,27 @@ shortTitle: 管理付款等级 {% data reusables.sponsors.tier-update %} {% data reusables.sponsors.retire-tier %} -## Adding a repository to a sponsorship tier +## 将仓库添加到赞助等级 {% data reusables.sponsors.sponsors-only-repos %} -### About adding repositories to a sponsorship tier +### 关于将存储库添加到赞助等级 -To add a repository to a tier, the repository must be private and owned by an organization, and you must have admin access to the repository. +要将仓库添加到等级，仓库必须是私有的，并且由组织拥有，同时您必须具有对仓库的管理员访问权限。 -When you add a repository to a tier, {% data variables.product.company_short %} will automatically send repository invitations to new sponsors and remove access when a sponsorship is cancelled. +将仓库添加到等级时，{% data variables.product.company_short %} 将自动向新赞助商发送仓库邀请，并在取消赞助时删除访问权限。 -Only personal accounts, not organizations, can be invited to private repositories associated with a sponsorship tier. +只有个人帐户（而非组织）才能被邀请到与赞助等级关联的私有仓库。 -You can also manually add or remove collaborators to the repository, and {% data variables.product.company_short %} will not override these in the sync. +您还可以在仓库中手动添加或删除协作者，{% data variables.product.company_short %} 不会在同步中覆盖这些协作者。 -### About transfers for repositories that are added to sponsorship tiers +### 关于添加到赞助等级的仓库的转移 -If you transfer a repository that has been added to a sponsorship tier, sponsors who have access to the repository through the tier may be affected. +如果将已添加到赞助等级的存储库转移，则有权通过该等级访问仓库的发起人可能会受到影响。 -- If the sponsored profile is for an organization and the repository is transferred to a different organization, current sponsors will be transferred, but new sponsors will not be added. The new owner of the repository can remove existing sponsors. -- If the sponsored profile is for a personal account, the repository is transferred to an organization, and the personal account has admin access to the new repository, existing sponsors will be transferred, and new sponsors will continue to be added to the repository. -- If the repository is transferred to a personal account, all sponsors will be removed and new sponsors will not be added to the repository. +- 如果赞助的配置文件是针对某个组织的，并且仓库被转移到其他组织，则将转移当前的赞助商，但不会添加新的赞助商。 仓库的新所有者可以删除现有赞助商。 +- 如果赞助的个人资料用于个人帐户，仓库转移到组织，并且个人帐户具有对新仓库的管理员访问权限，则将转移现有赞助商，并且将继续将新赞助商添加到仓库。 +- 如果仓库转移到个人帐户，则所有赞助商都将被删除，并且不会将新的赞助商添加到仓库中。 ### Adding a repository a sponsorship tier diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md index d5024003a0..d898943aa3 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -18,29 +18,29 @@ shortTitle: 查看赞助者和赞助 您可以查看有关您当前和过去的赞助、从赞助者收到的付款以及事件（例如赞助取消和赞助等级变更）的分析。 您还可以查看新的赞助、赞助变更和赞助取消等活动。 您可以按日期过滤活动列表。 您还可以导出帐户的赞助数据以 CSV 或 JSON 格式查看。 -## About transaction metadata +## 关于交易元数据 -To track where your sponsorships are coming from, you can use custom URLs with metadata for your {% data variables.product.prodname_sponsors %} profile or checkout page. The metadata will be included in your transaction export in the metadata column. For more information about exporting transaction data, see "[Exporting your sponsorship data](#exporting-your-sponsorship-data)." +要跟踪您的赞助来源，您可以使用自定义网址以及 {% data variables.product.prodname_sponsors %} 个人资料或结账页面的元数据。 元数据将包含在您的交易导出的元数据列中。 有关导出交易数据的更多信息，请参阅“[导出赞助数据](#exporting-your-sponsorship-data)”。 -Metadata must use the `key=value` format and can be added to the end of these URLs. +元数据必须使用 `key=value` 格式，并且可以添加到这些 URL 的末尾。 -- Sponsored account profile: `https://github.com/sponsors/{account}` -- Sponsorship checkout: `https://github.com/sponsors/{account}/sponsorships` +- 赞助的帐户配置文件：`https://github.com/sponsors/{account}` +- 赞助的检出：`https://github.com/sponsors/{account}/sponsorships` -The metadata will persist in the URL as a potential sponsor switches accounts to sponsor with, selects monthly or one-time payments, and chooses a different tier. +元数据将保留在 URL 中，因为潜在的发起人将帐户切换为赞助者，选择每月或一次性付款，并选择其他层。 -### Syntax requirements +### 语法要求 -Your metadata must meet the following requirements, which do not apply to any other URL parameters that are passed. +您的元数据必须满足以下要求，这些要求不适用于传递的任何其他 URL 参数。 -- Keys must be prefixed by `metadata_`, such as `metadata_campaign`. In your transaction export, the `metadata_` prefix will be removed from the key. -- Keys and values must only contain alphanumeric values, dashes, or underscores. If non-accepted characters are passed in either keys or values, a 404 error will be presented. -- Whitespaces are not allowed. -- A maximum of **10** key-value pairs are accepted per request. If more are passed, only the first 10 will be saved. -- A maximum of **25** characters per key are accepted. If more than that are passed, only the first 25 will be saved. -- A maximum of **100** characters per value are accepted. If more than that are passed, only the first 100 will be saved. +- 密钥必须以 `metadata_` 为前缀，例如 `metadata_campaign`。 在交易导出中， `metadata_` 前缀将从密钥中删除。 +- 键和值只能包含字母数字值、短划线或下划线。 如果在键或值中传递不接受的字符，则将显示 404 错误。 +- 不允许使用空格。 +- 每个请求最多接受 **10** 个键值对。 如果传递较多，仅保存前 10 个。 +- 每个键最多接受 **25** 个字符。 如果超过此值，则仅保存前 25 个。 +- 每个值最多接受 **100** 个字符。 如果超过此值，则仅保存前 100 个。 -For example, you can use `https://github.com/sponsors/{account}?metadata_campaign=myblog` to track sponsorships that originate from your blog. `metadata_campaign` is the key and `myblog` is the value. In the metadata column of your transaction export, the key will be listed as `campaign`. +例如，您可以使用 `https://github.com/sponsors/{account}？metadata_campaign=myblog` 来跟踪源自您博客的赞助。 `metdata_activity` 是键，`myblog` 是值。 在交易导出的元数据列中，密钥将列为 `campaign`。 ## 查看您的赞助者和赞助 diff --git a/translations/zh-CN/data/features/mermaid.yml b/translations/zh-CN/data/features/mermaid.yml new file mode 100644 index 0000000000..09870e35f9 --- /dev/null +++ b/translations/zh-CN/data/features/mermaid.yml @@ -0,0 +1,8 @@ +--- +#Issue 5812 and 6172 +#Mermaid syntax support +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.5' + ghae: 'issue-6172' diff --git a/translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md b/translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md index 6833ff6dc0..7a799ed906 100644 --- a/translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md +++ b/translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md @@ -1,3 +1,3 @@ {% ifversion ghes < 3.3 %} -{% data variables.product.prodname_actions %} is available in {% data variables.product.prodname_ghe_server %} 3.0 or higher. If you're using an earlier version of {% data variables.product.prodname_ghe_server %}, you'll have to upgrade to use {% data variables.product.prodname_actions %}. For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +{% data variables.product.prodname_actions %} is available in {% data variables.product.prodname_ghe_server %} 3.0 or higher. If you're using an earlier version of {% data variables.product.prodname_ghe_server %}, you'll have to upgrade to use {% data variables.product.prodname_actions %}. 有关升级 {% data variables.product.prodname_ghe_server %} 实例的更多信息，请参阅“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”。 {% endif %} diff --git a/translations/zh-CN/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md b/translations/zh-CN/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md index 02145ede39..c7ad85c5fc 100644 --- a/translations/zh-CN/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md +++ b/translations/zh-CN/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md @@ -1,3 +1,3 @@ -You can give organization members, teams, and outside collaborators different levels of access to repositories owned by your organization with repository roles. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +You can give organization members, teams, and outside collaborators different levels of access to repositories owned by your organization with repository roles. 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 You can also customize access to your organization's project boards and allow individual organization members to manage your organization's {% data variables.product.prodname_github_apps %}. For more information, see "[Managing access to your organization's project boards](/organizations/managing-access-to-your-organizations-project-boards)" and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)." diff --git a/translations/zh-CN/data/reusables/getting-started/org-permissions-and-roles.md b/translations/zh-CN/data/reusables/getting-started/org-permissions-and-roles.md index 055cdb0a61..b74b602b3f 100644 --- a/translations/zh-CN/data/reusables/getting-started/org-permissions-and-roles.md +++ b/translations/zh-CN/data/reusables/getting-started/org-permissions-and-roles.md @@ -1 +1 @@ -Each person in your organization has a role that defines their level of access to the organization. The member role is the default, and you can assign owner and billing manager roles as well as "team maintainer" permissions. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +Each person in your organization has a role that defines their level of access to the organization. The member role is the default, and you can assign owner and billing manager roles as well as "team maintainer" permissions. 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 diff --git a/translations/zh-CN/data/reusables/getting-started/setting-org-and-repo-permissions.md b/translations/zh-CN/data/reusables/getting-started/setting-org-and-repo-permissions.md index 4ac7ee25f9..0d5d9684aa 100644 --- a/translations/zh-CN/data/reusables/getting-started/setting-org-and-repo-permissions.md +++ b/translations/zh-CN/data/reusables/getting-started/setting-org-and-repo-permissions.md @@ -1,3 +1,3 @@ -We recommend giving a limited number of members in each organization an organization owner role, which provides complete administrative access for that organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +We recommend giving a limited number of members in each organization an organization owner role, which provides complete administrative access for that organization. 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 For organizations where you have admin permissions, you can also customize access to each repository with granular permission levels. For more information, see "[Repository permissions levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." diff --git a/translations/zh-CN/data/reusables/gpg/desktop-support-for-commit-signing.md b/translations/zh-CN/data/reusables/gpg/desktop-support-for-commit-signing.md index 1b0c6725e6..5093127a3e 100644 --- a/translations/zh-CN/data/reusables/gpg/desktop-support-for-commit-signing.md +++ b/translations/zh-CN/data/reusables/gpg/desktop-support-for-commit-signing.md @@ -1,5 +1,5 @@ {% note %} -**注：** [GitHub Desktop](https://desktop.github.com/) 不支持提交签名。 +**Note:** [GitHub Desktop](https://desktop.github.com/) only supports commit signing if your Git client is configured to sign commits by default. {% endnote %} diff --git a/translations/zh-CN/data/reusables/organizations/new-org-permissions-more-info.md b/translations/zh-CN/data/reusables/organizations/new-org-permissions-more-info.md index 07f5f6d1a9..aef09bd5a9 100644 --- a/translations/zh-CN/data/reusables/organizations/new-org-permissions-more-info.md +++ b/translations/zh-CN/data/reusables/organizations/new-org-permissions-more-info.md @@ -1 +1 @@ -For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 diff --git a/translations/zh-CN/data/reusables/organizations/new-repo-permissions-more-info.md b/translations/zh-CN/data/reusables/organizations/new-repo-permissions-more-info.md index de8afc2ecc..8fc37d30bd 100644 --- a/translations/zh-CN/data/reusables/organizations/new-repo-permissions-more-info.md +++ b/translations/zh-CN/data/reusables/organizations/new-repo-permissions-more-info.md @@ -1 +1 @@ -For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 diff --git a/translations/zh-CN/data/reusables/repositories/you-can-fork.md b/translations/zh-CN/data/reusables/repositories/you-can-fork.md index 983542114d..89271e31a8 100644 --- a/translations/zh-CN/data/reusables/repositories/you-can-fork.md +++ b/translations/zh-CN/data/reusables/repositories/you-can-fork.md @@ -1,4 +1,4 @@ -{% ifversion ghae %}如果企业的策略允许复刻内部和私有仓库{% else %}您{% endif %}可以将仓库复刻到您的用户帐户或具有仓库创建权限的任何组织。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +{% ifversion ghae %}如果企业的策略允许复刻内部和私有仓库{% else %}您{% endif %}可以将仓库复刻到您的用户帐户或具有仓库创建权限的任何组织。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 {% ifversion fpt or ghes or ghec %}