From 95e0073eb44a2a491cdcd3bcb6b6da62f5c9868c Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Thu, 17 Mar 2022 14:23:52 -0700 Subject: [PATCH] New translation batch for cn (#26301) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check parsing * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn * run script/i18n/reset-known-broken-translation-files.js * Check in cn CSV report Co-authored-by: Robert Sese --- translations/log/cn-resets.csv | 4 +- .../developing-a-third-party-cli-action.md | 34 +-- translations/zh-CN/content/actions/guides.md | 2 +- .../skipping-workflow-runs.md | 4 +- .../notifications-for-workflow-runs.md | 2 +- .../about-enterprise-configuration.md | 2 +- ...-dependency-insights-in-your-enterprise.md | 16 +- ...s-for-github-actions-in-your-enterprise.md | 21 +- ...or-security-settings-in-your-enterprise.md | 42 ++-- ...oject-board-policies-in-your-enterprise.md | 14 +- ...adding-organizations-to-your-enterprise.md | 16 +- ...nowned-organizations-in-your-enterprise.md | 2 +- ...rganizations-in-your-enterprise-account.md | 234 +++++++++--------- ...gs-for-organizations-in-your-enterprise.md | 4 +- ...viting-people-to-manage-your-enterprise.md | 6 +- ...upport-entitlements-for-your-enterprise.md | 6 +- .../roles-in-an-enterprise.md | 54 ++-- ...n-azure-subscription-to-your-enterprise.md | 2 +- ...configuring-dependabot-security-updates.md | 6 +- .../about-the-dependency-graph.md | 2 +- .../creating-a-github-app.md | 3 +- ...g-and-authorizing-users-for-github-apps.md | 2 +- .../authorizing-oauth-apps.md | 10 +- .../creating-an-oauth-app.md | 5 +- .../modifying-a-github-app.md | 3 +- ...sferring-an-issue-to-another-repository.md | 2 +- .../about-organizations.md | 2 +- ...ganizations-ssh-certificate-authorities.md | 2 +- .../about-permissions-for-github-packages.md | 2 +- .../data/features/device-flow-is-opt-in.yml | 6 + 30 files changed, 265 insertions(+), 245 deletions(-) create mode 100644 translations/zh-CN/data/features/device-flow-is-opt-in.yml diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index 0729418138..f00f9341da 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -67,10 +67,12 @@ translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,broken liquid tags translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md,parsing error translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,broken liquid tags translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags @@ -222,7 +224,7 @@ translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,Listed in localization-support#489 translations/zh-CN/content/rest/reference/enterprise-admin.md,broken liquid tags translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,broken liquid tags -translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags +translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,parsing error 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/actions/creating-actions/developing-a-third-party-cli-action.md b/translations/zh-CN/content/actions/creating-actions/developing-a-third-party-cli-action.md index f3e2a42907..a76178680f 100644 --- a/translations/zh-CN/content/actions/creating-actions/developing-a-third-party-cli-action.md +++ b/translations/zh-CN/content/actions/creating-actions/developing-a-third-party-cli-action.md @@ -1,7 +1,7 @@ --- -title: Developing a third party CLI action -shortTitle: CLI setup action -intro: 'Learn how to develop an action to set up a CLI on {% data variables.product.prodname_actions %} runners.' +title: 开发第三方 CLI 操作 +shortTitle: CLI 设置操作 +intro: '了解如何开发操作以在 {% data variables.product.prodname_actions %} 运行器上设置 CLI。' redirect_from: [] versions: fpt: '*' @@ -13,27 +13,27 @@ topics: ## 简介 -You can write an action to provide a way for users to access your servers via a configured CLI environment on {% data variables.product.prodname_actions %} runners. +您可以编写操作，为用户提供一种通过 {% data variables.product.prodname_actions %} 运行器上配置的 CLI 环境访问服务器的方法。 -Your action should: +您的操作应： -- Make it simple for users to specify the version of the CLI to install -- Support multiple operating systems -- Run in an efficient fashion to minimize run-time and associated costs -- Work across {% data variables.product.product_name %}-hosted and self-hosted runners -- Leverage community tooling when possible +- 使用户能够轻松指定要安装的 CLI 版本 +- 支持多种操作系统 +- 以高效的方式运行，以最大限度地减少运行时间和相关成本 +- 跨 {% data variables.product.product_name %} 托管和自托管运行器工作 +- 尽可能利用社区工具 -This article will demonstrate how to write an action that retrieves a specific version of your CLI, installs it, adds it to the path, and (optionally) caches it. This type of action (an action that sets up a tool) is often named `setup-$TOOL`. +本文将演示如何编写一个操作来检索特定版本的 CLI、安装它、将其添加到路径以及（可选）缓存它。 这种类型的操作（设置工具的操作）通常命名为 `setup-$TOOL`。 ## 基本要求 -You should have an understanding of how to write a custom action. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions)". For a more detailed guide on how to write a custom action, see "[Creating a JavaScript action](/actions/creating-actions/creating-a-javascript-action)." +您应该了解如何编写自定义操作。 更多信息请参阅“[关于自定义操作](/actions/creating-actions/about-custom-actions)”。 有关如何编写自定义操作的更详细指南，请参阅“[创建 JavaScript 操作](/actions/creating-actions/creating-a-javascript-action)”。 ## 示例 -The following script demonstrates how you can get a user-specified version as input, download and extract the specific version of your CLI, then add the CLI to the path. +以下脚本演示如何获取用户指定的版本作为输入，下载并提取 CLI 的特定版本，然后将 CLI 添加到路径中。 -{% data variables.product.prodname_dotcom %} provides [`actions/toolkit`](https://github.com/actions/toolkit), which is a set of packages that helps you create actions. This example uses the [`actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) and [`actions/tool-cache`](https://github.com/actions/toolkit/tree/main/packages/tool-cache) packages. +{% data variables.product.prodname_dotcom %} 提供了 [`actions/toolkit`](https://github.com/actions/toolkit)，这是一组可帮助您创建操作的包。 此示例使用 [`actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) 和 [`actions/tool-cache`](https://github.com/actions/toolkit/tree/main/packages/tool-cache) 包。 {% raw %} ```javascript{:copy} @@ -58,13 +58,13 @@ module.exports = setup ``` {% endraw %} -To use this script, replace `getDownloadURL` with a function that downloads your CLI. You will also need to create an actions metadata file (`action.yml`) that accepts a `version` input and that runs this script. For full details about how to create an action, see "[Creating a JavaScript action](/actions/creating-actions/creating-a-javascript-action)." +要使用此脚本，请将 `getDownloadURL` 替换为下载 CLI 的函数。 您还需要创建接受 `version` 输入并运行此脚本的操作元数据文件 (`action.yml`)。 有关如何创建操作的完整详细信息，请参阅“[创建 JavaScript 操作](/actions/creating-actions/creating-a-javascript-action)”。 -For a full example of how to set up this action, see [example-setup-gh](https://github.com/github-developer/example-setup-gh). +有关如何设置此操作的完整示例，请参阅 [example-setup-gh](https://github.com/github-developer/example-setup-gh)。 ## 延伸阅读 -This pattern is employed in several actions. For more examples, see: +此模式用于多个操作。 有关更多示例，请参阅： * [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby) * [`google-github-actions/setup-gcloud`](https://github.com/google-github-actions/setup-gcloud) diff --git a/translations/zh-CN/content/actions/guides.md b/translations/zh-CN/content/actions/guides.md index 67574a1620..5e9bb538b2 100644 --- a/translations/zh-CN/content/actions/guides.md +++ b/translations/zh-CN/content/actions/guides.md @@ -1,5 +1,5 @@ --- -title: Guides for GitHub Actions +title: GitHub Actions 指南 intro: '{% data variables.product.prodname_actions %} 的这些指南包含具体的使用案例和示例来帮助您配置工作流程。' allowTitleToDifferFromFilename: true layout: product-guides diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md index a03c236353..8604d3137a 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -1,6 +1,6 @@ --- title: 跳过工作流程运行 -intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message. +intro: 您可以通过在提交消息中包含命令来跳过由 `push` 和 `pull_request` 事件触发的工作流程运行。 versions: fpt: '*' ghes: '*' @@ -30,4 +30,4 @@ shortTitle: 跳过工作流程运行 {% endnote %} -Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. 更多信息请参阅“[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)。 +跳过指令仅适用于由包含跳过指令的提交触发的工作流程运行。 您还可以禁用工作流程的运行。 更多信息请参阅“[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)。 diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md index 05361c720a..2b22918e2f 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md @@ -1,6 +1,6 @@ --- title: 工作流程运行通知 -intro: You can subscribe to notifications about workflow runs that you trigger. +intro: 您可以订阅有关触发的工作流程运行的通知。 versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/about-enterprise-configuration.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/about-enterprise-configuration.md index 27a8b124fd..e3ea523c2a 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/about-enterprise-configuration.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/about-enterprise-configuration.md @@ -23,7 +23,7 @@ shortTitle: 关于配置 {% endif %} {% ifversion ghae %} -To get started with {% data variables.product.product_name %}, you first need to deploy {% data variables.product.product_name %}. For more information, see "[Deploying {% data variables.product.product_name %}](/admin/configuration/configuring-your-enterprise/deploying-github-ae)." +要开始使用 {% data variables.product.product_name %}，需要先部署 {% data variables.product.product_name %}。 更多信息请参阅“[部署 {% data variables.product.product_name %}](/admin/configuration/configuring-your-enterprise/deploying-github-ae)”。 第一次访问您的企业时，您将完成初始配置，以便 {% data variables.product.product_name %} 可供使用。 初始配置包括连接您的企业与身份提供程序 (IdP) 连接、通过 SAML SSO 进行身份验证、配置企业中仓库和组织的策略，以及为出站电子邮件配置 SMTP。 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)。” diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md index db4f720205..20cbdc75a4 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Enforcing policies for dependency insights in your enterprise -intro: 'You can enforce policies for dependency insights within your enterprise''s organizations, or allow policies to be set in each organization.' +title: 在企业中实施依赖性见解的策略 +intro: 您可以在企业组织内执行依赖性见解策略，或允许在每个组织中设置策略。 permissions: Enterprise owners can enforce policies for dependency insights in an enterprise. redirect_from: - /articles/enforcing-a-policy-on-dependency-insights @@ -16,19 +16,19 @@ topics: - Enterprise - Organizations - Policies -shortTitle: Policies for dependency insights +shortTitle: 依赖性见解策略 --- -## About policies for dependency insights in your enterprise +## 关于企业中的依赖性见解策略 -Dependency insights show all packages that repositories within your enterprise's organizations depend on. Dependency insights include aggregated information about security advisories and licenses. 更多信息请参阅“[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)”。 +依赖性见解显示企业组织内的存储库所依赖的所有包。 依赖性见解包括有关安全公告和许可的汇总信息。 更多信息请参阅“[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)”。 -## Enforcing a policy for visibility of dependency insights +## 实施依赖性见解的可见性策略 -Across all organizations owned by your enterprise, you can control whether organization members can view dependency insights. You can also allow owners to administer the setting on the organization level. 更多信息请参阅“[更改组织依赖项洞察的可见性](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)”。 +在企业拥有的所有组织中，您可以控制组织成员是否可以查看依赖性见解。 您还可以允许所有者在组织级别管理设置。 更多信息请参阅“[更改组织依赖项洞察的可见性](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} -3. In the left sidebar, click **Organizations**. ![Organizations tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-policies-org-tab.png) +3. 在左侧栏中，单击，单击 **Organizations（组织）**。 ![企业边栏中的 Organizations（组织）选项卡](/assets/images/help/business-accounts/settings-policies-org-tab.png) 4. 在“Organization policies”（组织政策）下。审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} 5. 在“Organization projects”（组织项目）下，使用下拉菜单并选择策略。 ![带有组织策略选项的下拉菜单](/assets/images/help/business-accounts/organization-policy-drop-down.png) diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index fd0858fdae..04bac88a29 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -27,21 +27,21 @@ shortTitle: GitHub Actions policies {% data reusables.actions.enterprise-beta %} -## 关于企业中 {% data variables.product.prodname_actions %} 的策略 +## About policies for {% data variables.product.prodname_actions %} in your enterprise {% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)." -{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. 您可以执行策略来控制 {% data variables.product.product_name %} 上的企业成员如何使用 {% data variables.product.prodname_actions %}。 By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)." +{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)." ## Enforcing a policy to restrict the use of actions in your enterprise -您可以选择对企业中的所有组织禁用 {% data variables.product.prodname_actions %}，或只允许特定的组织。 您还可以限制公共操作的使用，以使人们只能使用您的企业中存在的本地操作。 +You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.actions.enterprise-actions-permissions %} -1. 单击 **Save（保存）**。 +1. Click **Save**. {% ifversion ghec or ghes or ghae %} @@ -52,11 +52,11 @@ shortTitle: GitHub Actions policies {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. {%- ifversion ghes or ghae-issue-5094 %} - ![添加操作到允许列表](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} - ![添加操作到允许列表](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) {%- endif %} {% endif %} @@ -117,14 +117,15 @@ If a policy is enabled for an enterprise, the policy can be selectively disabled {% data reusables.actions.workflow-permissions-intro %} -您可以在企业、组织或仓库的设置中为 `GITHUB_TOKEN` 设置默认权限。 如果您在企业设置中选择受限制的选项为默认值，这将防止在组织或仓库设置中选择更多的允许设置。 +You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings. {% data reusables.actions.workflow-permissions-modifying %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. 在 **Workflow permissions（工作流程权限）**下，选择您是否想要 `GITHUB_TOKENN` 读写所有范围限， 或者只读`内容`范围。 ![为此企业设置 GITHUB_TOKENN 权限](/assets/images/help/settings/actions-workflow-permissions-enterprise.png) -1. 单击 **Save（保存）**以应用设置。 +1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. + ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise.png) +1. Click **Save** to apply the settings. {% 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 0156457a6d..1fcd044343 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 @@ -1,6 +1,6 @@ --- -title: Enforcing policies for security settings in your enterprise -intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.' +title: 为企业中的安全设置实施策略 +intro: 您可以实施策略来管理企业组织中的安全设置，或允许在每个组织中设置策略。 permissions: Enterprise owners can enforce policies for security settings in an enterprise. miniTocMaxHeadingLevel: 3 redirect_from: @@ -20,28 +20,28 @@ topics: - Enterprise - Policies - Security -shortTitle: Policies for security settings +shortTitle: 安全设置策略 --- -## About policies for security settings in your enterprise +## 关于企业中安全设置的策略 -You can enforce policies to control the security settings for organizations owned by your enterprise on {% data variables.product.product_name %}. By default, organization owners can manage security settings. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)." +您可以在 {% data variables.product.product_name %} 上实施策略以控制企业拥有的组织的安全设置。 默认情况下，组织所有者可以管理安全设置。 更多信息请参阅“[保护组织安全](/organizations/keeping-your-organization-secure)”。 {% ifversion ghec or ghes %} -## Requiring two-factor authentication for organizations in your enterprise +## 要求企业中的组织进行双重身份验证 -Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their personal accounts. +企业所有者可以要求企业拥有的所有组织中的组织成员、帐单管理员和外部协作者使用双重身份验证来保护其个人帐户。 -Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. 更多信息请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/articles/securing-your-account-with-two-factor-authentication-2fa/)”。 +您必须为自己的帐户启用双重身份验证，然后才能对企业拥有的所有组织都要求 2FA。 更多信息请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/articles/securing-your-account-with-two-factor-authentication-2fa/)”。 {% warning %} **警告：** -- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. 他们还会失去对组织私有仓库的复刻的访问权限。 如果他们在从您的组织中删除后的三个月内为其个人帐户启用双重身份验证，您可以恢复其访问权限和设置。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。 -- Any organization owner, member, billing manager, or outside collaborator in any of the organizations owned by your enterprise who disables 2FA for their personal account after you've enabled required two-factor authentication will automatically be removed from the organization. -- If you're the sole owner of a enterprise that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the enterprise. +- 当您需要为企业进行双重身份验证时，不使用 2FA 的企业拥有的所有组织中的成员、外部协作者和帐单管理员（包括自动程序帐户）将从组织中删除，并失去对其仓库的访问权限。 他们还会失去对组织私有仓库的复刻的访问权限。 如果他们在从您的组织中删除后的三个月内为其个人帐户启用双重身份验证，您可以恢复其访问权限和设置。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。 +- 为其个人帐户禁用 2FA 的企业拥有的任何组织中的任何组织所有者、成员、帐单管理员或外部协作者在您启用所需的双重身份验证后将自动从组织中删除。 +- 如果您是某个要求双重身份验证的企业的唯一所有者，则在不为企业禁用双重身份验证要求的情况下，您将无法为个人帐户禁用 2FA。 {% endwarning %} @@ -52,22 +52,22 @@ Before you can require 2FA for all organizations owned by your enterprise, you m {% data reusables.enterprise-accounts.security-tab %} 4. 在“Two-factor authentication（双重身份验证）”下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} 5. 在“Two-factor authentication（双重身份验证）”下，选择 **Require two-factor authentication for all organizations in your business（对您企业中的所有组织要求双重身份验证）**，然后单击 **Save（保存）**。 ![要求双重身份验证的复选框](/assets/images/help/business-accounts/require-2fa-checkbox.png) -6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**. ![确认双重实施框](/assets/images/help/business-accounts/confirm-require-2fa.png) -7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. 每个人都必须启用双重身份验证，然后才能接受您的邀请。 +6. 如果出现提示，请阅读有关将从企业所拥有的组织中删除的成员和外部协作者的信息。 要确认更改，请输入企业的名称，然后单击 **Remove members & require two-factor authentication（删除成员并要求双重身份验证）**。 ![确认双重实施框](/assets/images/help/business-accounts/confirm-require-2fa.png) +7. （可选）如果从您的企业拥有的组织中删除了任何成员或外部协作者，我们建议向他们发送邀请，以恢复其以前对组织的权限和访问权限。 每个人都必须启用双重身份验证，然后才能接受您的邀请。 {% endif %} {% ifversion ghec or ghae %} -## Managing allowed IP addresses for organizations in your enterprise +## 管理企业中组织允许的 IP 地址 {% ifversion ghae %} -You can restrict network traffic to your enterprise on {% data variables.product.product_name %}. 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)”。 +您可以在 {% data variables.product.product_name %}上限制到企业的网络流量。 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)”。 {% elsif ghec %} -Enterprise owners can restrict access to private assets owned by organizations in an enterprise by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %} +企业所有者可以通过为特定 IP 地址配置允许列表，来限制对企业中组织拥有的私有资产的访问。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %} {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %} @@ -122,15 +122,15 @@ Enterprise owners can restrict access to private assets owned by organizations i {% endif %} -## Managing SSH certificate authorities for your enterprise +## 管理企业的 SSH 认证机构 -You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。 +您可以使用 SSH 认证机构 (CA) 来允许企业拥有的任何组织的成员使用您提供的 SSH 证书访问该组织的存储库。 {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。 {% data reusables.organizations.add-extension-to-cert %} ### 添加 SSH 认证中心 -If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)”。 +如果您的企业需要 SSH 证书，企业成员应使用特殊的 URL 通过 SSH 进行 Git 操作。 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} @@ -150,6 +150,6 @@ If you require SSH certificates for your enterprise, enterprise members should u {% ifversion ghec or ghae %} ## 延伸阅读 -- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %} -- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %} +- "[关于企业的身份和访问权限管理](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %} +- "[访问企业的合规性报告](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %} {% endif %} diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md index 37f0d4dffd..5aa1fd7436 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Enforcing project board policies in your enterprise -intro: 'You can enforce policies for projects within your enterprise''s organizations, or allow policies to be set in each organization.' +title: 在企业中实施项目板策略 +intro: 您可以在企业组织内执行项目策略，或允许在每个组织中设置策略。 permissions: Enterprise owners can enforce policies for project boards in an enterprise. redirect_from: - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account @@ -18,16 +18,16 @@ topics: - Enterprise - Policies - Projects -shortTitle: Project board policies +shortTitle: 项目板策略 --- -## About policies for project boards in your enterprise +## 关于企业中项目板的策略 -You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. 更多信息请参阅“[关于项目板](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)”。 +您可以执行策略来控制企业在 {% data variables.product.product_name %} 上的企业成员如何管理项目板。 您也可以允许组织所有者管理项目板策略。 更多信息请参阅“[关于项目板](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)”。 ## 实施组织范围项目板的策略 -Across all organizations owned by your enterprise, you can enable or disable organization-wide project boards, or allow owners to administer the setting on the organization level. +在企业拥有的所有组织中，可以启用或禁用组织范围的项目板，或允许所有者在组织级别管理设置。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -37,7 +37,7 @@ Across all organizations owned by your enterprise, you can enable or disable org ## 实施仓库项目板的策略 -Across all organizations owned by your enterprise, you can enable or disable repository-level project boards, or allow owners to administer the setting on the organization level. +在企业拥有的所有组织中，可以启用或禁用仓库级项目板，或允许所有者在组织级别管理设置。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 071b17f14b..4f58cf00cc 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Adding organizations to your enterprise -intro: You can create new organizations or invite existing organizations to manage within your enterprise. +title: 将组织添加到企业 +intro: 您可以创建新的组织或邀请现有组织来管理您的企业。 redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account - /articles/adding-organizations-to-your-enterprise-account @@ -18,17 +18,17 @@ shortTitle: 添加组织 ## 关于组织 -Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. 更多信息请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。 +您的企业帐户可以拥有组织。 企业成员可以跨组织内的相关项目进行协作。 更多信息请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。 -Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings. +企业所有者可以在企业帐户设置内创建新组织，或邀请现有组织加入企业。 要将组织添加到企业，必须在企业帐户设置中创建组织。 -You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." +您只能以这种方式将组织添加到现有企业帐户。 {% data reusables.enterprise.create-an-enterprise-account %} 更多信息请参阅“[创建企业帐户](/admin/overview/creating-an-enterprise-account)”。 ## 在企业帐户中创建组织 在企业帐户设置中创建的新组织包含在企业帐户的 {% data variables.product.prodname_ghe_cloud %} 订阅中。 -创建企业帐户所拥有的组织的企业所有者自动成为组织所有者。 For more information about organization owners, 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 reusables.enterprise-accounts.access-enterprise %} 2. 在 **Organizations（组织）**选项卡中的组织列表上方，单击 **New organization（新组织）**。 ![新组织按钮](/assets/images/help/business-accounts/enterprise-account-add-org.png) @@ -39,12 +39,12 @@ You can only add organizations this way to an existing enterprise account. {% da ## 邀请组织加入您的企业帐户 -企业所有者可以邀请现有组织加入其企业帐户。 如果您要邀请的组织已经归其他企业所有，则在上一个企业放弃对组织的所有权之前，您将无法发出邀请。 For more information, see "[Removing an organization from your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)." +企业所有者可以邀请现有组织加入其企业帐户。 如果您要邀请的组织已经归其他企业所有，则在上一个企业放弃对组织的所有权之前，您将无法发出邀请。 更多信息请参阅“[从企业中删除组织](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)”。 {% data reusables.enterprise-accounts.access-enterprise %} 2. 在 **Organizations（组织）**选项卡中的组织列表上方，单击 **Invite organization（邀请组织）**。 ![邀请组织](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) 3. 在“Organization name（组织名称）”下，开始键入要邀请的组织名称，并在它出现在下拉列表中时选择它。 ![搜索组织](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) 4. 单击 **Invite organization（邀请组织）**。 -5. The organization owners will receive an email inviting them to join the enterprise. 至少有一个所有者接受邀请才能继续该过程。 您可以在所有者批准邀请之前随时取消或重新发送邀请。 ![取消或重新发送](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +5. 组织所有者将收到一封邀请他们加入企业的电子邮件。 至少有一个所有者接受邀请才能继续该过程。 您可以在所有者批准邀请之前随时取消或重新发送邀请。 ![取消或重新发送](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) 6. 一旦组织所有者批准了邀请，您可以在待定邀请列表中查看其状态。 ![待定邀请](/assets/images/help/business-accounts/enterprise-account-pending.png) 7. 点击 **Approve（批准）**完成传输，或点击 **Cancel（取消）**予以取消。 ![批准邀请](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md index 19ba0be246..3a9df9c243 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Managing unowned organizations in your enterprise +title: 管理企业中没有所有者的组织 intro: 您可以成为企业帐户中目前没有所有者的组织的所有者。 permissions: Enterprise owners can manage unowned organizations in an enterprise account. redirect_from: diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md index 11eb9d5d71..ea9a747065 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: Streaming the audit logs for organizations in your enterprise account -intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.' +title: 流式传输企业帐户中组织的审核日志 +intro: '您可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。' miniTocMaxHeadingLevel: 3 versions: ghec: '*' @@ -10,43 +10,43 @@ topics: - Enterprise - Logging - Organizations -shortTitle: Stream organization audit logs +shortTitle: 流式传输组织审核日志 redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account permissions: Enterprise owners can configure audit log streaming. --- -## About exporting audit data +## 关于导出审核数据 -You can extract audit log and Git events data from {% data variables.product.prodname_dotcom %} in multiple ways: +您可以通过多种方式从 {% data variables.product.prodname_dotcom %} 中提取审核日志和 Git 事件数据： -* Go to the Audit log page in {% data variables.product.prodname_dotcom %} and click **Export**. For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Exporting the audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)." -* Use the API to poll for new audit log events. For more information, see "[Using the audit log API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)." -* Set up {% data variables.product.product_name %} to stream audit data as events are logged. +* 转到 {% data variables.product.prodname_dotcom %} 中的审核日志页，然后单击 **Export（导出）**。 更多信息请参阅“[查看企业帐户中组织的审核日志](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)”和“[导出审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)”。 +* 使用 API 轮询新的审核日志事件。 更多信息请参阅“[使用审核日志 API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)”。 +* 设置 {% data variables.product.product_name %} 以在记录事件时流式传输审核数据。 -Currently, audit log streaming is supported for multiple storage providers. +目前，多个存储提供商支持审核日志流式处理。 - Amazon S3 - Azure Blob Storage - Azure Event Hubs - Google Cloud Storage - Splunk -## About audit log streaming +## 关于审核日志流 -To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor: +为了帮助保护您的知识产权并保持组织的合规性，您可以使用流式处理来保留审核日志数据的副本并监控： {% data reusables.audit_log.audited-data-list %} -The benefits of streaming audit data include: +流式传输审计数据的好处包括： -* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account. -* **Data continuity**. You can pause the stream for up to seven days without losing any audit data. -* **Data retention**. You can keep your exported audit logs and Git data as long as you need to. +* **数据探索**。 您可以使用首选工具检查流事件，以查询大量数据。 流包含整个企业帐户中的审核事件和 Git 事件。 +* **数据连续性**。 您可以暂停流长达七天，而不会丢失任何审核数据。 +* **数据保留**。 您可以根据需要保留导出的审核日志和 Git 数据。 -Enterprise owners can set up, pause, or delete a stream at any time. The stream exports the audit data for all of the organizations in your enterprise. +企业所有者可以随时设置、暂停或删除流。 流导出企业中所有组织的审核数据。 -## Setting up audit log streaming +## 设置审核日志流 -You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider. +您可以按照提供程序的说明在 {% data variables.product.product_name %} 上设置审核日志流。 - [Amazon S3](#setting-up-streaming-to-amazon-s3) - [Azure Blob Storage](#setting-up-streaming-to-azure-blob-storage) @@ -54,192 +54,192 @@ You set up the audit log stream on {% data variables.product.product_name %} by - [Google Cloud Storage](#setting-up-streaming-to-google-cloud-storage) - [Splunk](#setting-up-streaming-to-splunk) -### Setting up streaming to Amazon S3 +### 设置流式传输到 Amazon S3 -To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information. +要将审核日志流式传输到 Amazon 的 S3 终端节点，您必须拥有存储桶和访问密钥。 更多信息请参阅 AWS 文档中的[创建、配置和使用 Amazon S3 存储桶](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html)。 请务必阻止对存储桶的公共访问，以保护您的审核日志信息。 -To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need: -* The name of your Amazon S3 bucket -* Your AWS access key ID -* Your AWS secret key +要设置来自 {% data variables.product.prodname_dotcom %} 审核日志流式处理，您需要： +* Amazon S3 存储桶的名称 +* AWS 访问密钥 ID +* AWS 密钥 -For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation. +有关创建或访问访问密钥 ID 和密钥的信息，请参阅 AWS 文档中的[了解和获取您的 AWS 凭据](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html)。 {% data reusables.enterprise.navigate-to-log-streaming-tab %} -1. Click **Configure stream** and select **Amazon S3**. +1. 单击 **Configure stream（配置流）**，然后选择 **Amazon S3**。 - ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png) + ![从下拉菜单中选择 Amazon S3](/assets/images/help/enterprises/audit-stream-choice-s3.png) -1. On the configuration page, enter: - * The name of the bucket you want to stream to. For example, `auditlog-streaming-test`. - * Your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`. - * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`. +1. 在配置页面上，输入： + * 要流式传输到的存储桶的名称。 例如，`auditlog-streaming-test`。 + * 您的访问密钥 ID。 例如，`ABCAIOSFODNN7EXAMPLE1`。 + * 您的密钥。 例如，`aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`。 - ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png) + ![输入流设置](/assets/images/help/enterprises/audit-stream-add-s3.png) -1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Amazon S3 endpoint. +1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Amazon S3 端点。 - ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png) + ![检查端点](/assets/images/help/enterprises/audit-stream-check.png) {% data reusables.enterprise.verify-audit-log-streaming-endpoint %} -### Setting up streaming to Azure Blob Storage +### 设置流式传输到 Azure Blob Storage -Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have created a storage account and a container in Microsoft Azure. For details, see the Microsoft documentation, "[Introduction to Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)." +在 {% data variables.product.prodname_dotcom %} 中设置流之前，必须先在 Microsoft Azure 中创建存储帐户和容器。 有关详细信息，请参阅 Microsoft 文档中的“[Azure Blob Storage 简介](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)”。 -To configure the stream in {% data variables.product.prodname_dotcom %} you need the URL of a SAS token. +要在 {% data variables.product.prodname_dotcom %} 配置流，需要 SAS 令牌的 URL。 -**On Microsoft Azure portal**: -1. On the Home page, click **Storage Accounts**. -2. Click the name of the storage account you want to use, then click **Containers**. +**在 Microsoft Azure 门户中**： +1. 在主页上，单击 **Storage Accounts（存储帐户）**。 +2. 单击要使用的存储帐户的名称，然后单击 **Containers（容器）**。 - ![The Containers link in Azure](/assets/images/azure/azure-storage-containers.png) + ![Azure 中的容器链接](/assets/images/azure/azure-storage-containers.png) -1. Click the name of the container you want to use. -1. Click **Shared access tokens**. +1. 单击要使用的容器的名称。 +1. 单击 **Shared access tokens（共享访问令牌）**。 - ![The shared access token link in Azure](/assets/images/azure/azure-storage-shared-access-tokens.png) + ![Azure 中的共享访问令牌链接](/assets/images/azure/azure-storage-shared-access-tokens.png) -1. In the **Permissions** drop-down menu, change the permissions to only allow `Create` and `Write`. +1. 在 **Permissions（权限）**下拉菜单中，将权限更改为仅允许`创建`和`写入`。 - ![The permissions drop-down menu](/assets/images/azure/azure-storage-permissions.png) + ![权限下拉菜单](/assets/images/azure/azure-storage-permissions.png) -1. Set an expiry date that complies with your secret rotation policy. -1. Click **Generate SAS token and URL**. -1. Copy the value of the **Blob SAS URL** field that's displayed. You will use this URL in {% data variables.product.prodname_dotcom %}. +1. 设置符合机密轮换策略的到期日期。 +1. 单击 **Generate SAS token and URL（生成 SAS 令牌和 URL）**。 +1. 复制显示的 **Blob SAS URL** 字段的值。 您将在 {% data variables.product.prodname_dotcom %} 中使用此 URL。 -**On {% data variables.product.prodname_dotcom %}**: +**在 {% data variables.product.prodname_dotcom %} 上**： {% data reusables.enterprise.navigate-to-log-streaming-tab %} -1. Click **Configure stream** and select **Azure Blob Storage**. +1. 单击 **Configure stream（配置流）**，然后选择 **Azure Blob Storage**。 - ![Choose Azure Blob Storage from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azureblob.png) + ![从下拉菜单中选择 Azure Blob Storage](/assets/images/help/enterprises/audit-stream-choice-azureblob.png) -1. On the configuration page, enter the blob SAS URL that you copied in Azure. The **Container** field is auto-filled based on the URL. +1. 在配置页上，输入在 Azure 中复制的 blob SAS URL。 **Container（容器）**字段将根据 URL 自动填充。 - ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-azureblob.png) + ![输入流设置](/assets/images/help/enterprises/audit-stream-add-azureblob.png) -1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint. +1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Azure Blob Storage 端点。 - ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png) + ![检查端点](/assets/images/help/enterprises/audit-stream-check.png) {% data reusables.enterprise.verify-audit-log-streaming-endpoint %} -### Setting up streaming to Azure Event Hubs +### 设置流式传输到 Azure Event Hub -Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)." +在 {% data variables.product.prodname_dotcom %} 中设置流之前，必须先在 Microsoft Azure 中具有事件中心命名空间。 接下来，必须在命名空间中创建事件中心实例。 设置流时，需要此事件中心实例的详细信息。 有关详细信息，请参阅 Microsoft 文档“[快速入门：使用 Azure 门户创建事件中心](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)”。 -You need two pieces of information about your event hub: its instance name and the connection string. +需要有关事件中心的两条信息：其实例名称和连接字符串。 -**On Microsoft Azure portal**: -1. Search for "Event Hubs". +**在 Microsoft Azure 门户中**： +1. 搜索“事件中心”。 - ![The Azure portal search box](/assets/images/azure/azure-resources-search.png) + ![Azure 门户搜索框](/assets/images/azure/azure-resources-search.png) -1. Select **Event Hubs**. The names of your event hubs are listed. +1. 选择 **Event Hubs（事件中心）**。 将列出事件中心的名称。 - ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png) + ![事件中心列表](/assets/images/help/enterprises/azure-event-hubs-list.png) -1. Make a note of the name of the event hub you want to stream to. -1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**. -1. Select a shared access policy in the list of policies, or create a new policy. +1. 记下要流式传输到的事件中心的名称。 +1. 单击所需的事件中心。 然后，在左侧菜单中，选择 **Shared Access Policies（共享访问策略）**。 +1. 在策略列表中选择共享访问策略，或创建新策略。 - ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png) + ![共享访问策略列表](/assets/images/help/enterprises/azure-shared-access-policies.png) -1. Click the button to the right of the **Connection string-primary key** field to copy the connection string. +1. 单击 **Connection string-primary key（连接字符串 - 主键）**字段右侧的按钮以复制连接字符串。 - ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png) + ![事件中心连接字符串](/assets/images/help/enterprises/azure-connection-string.png) -**On {% data variables.product.prodname_dotcom %}**: +**在 {% data variables.product.prodname_dotcom %} 上**： {% data reusables.enterprise.navigate-to-log-streaming-tab %} -1. Click **Configure stream** and select **Azure Event Hubs**. +1. 单击 **Configure stream（配置流）**，然后选择 **Azure Event Hubs**。 - ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png) + ![从下拉菜单中选择 Azure Events Hub](/assets/images/help/enterprises/audit-stream-choice-azure.png) -1. On the configuration page, enter: - * The name of the Azure Event Hubs instance. - * The connection string. +1. 在配置页面上，输入： + * Azure Event Hubs 实例的名称。 + * 连接字符串。 - ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png) + ![输入流设置](/assets/images/help/enterprises/audit-stream-add-azure.png) -1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint. +1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Azure Event Hubs 端点。 - ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png) + ![检查端点](/assets/images/help/enterprises/audit-stream-check.png) {% data reusables.enterprise.verify-audit-log-streaming-endpoint %} -### Setting up streaming to Google Cloud Storage +### 设置流式传输到 Google Cloud Storage -To set up streaming to Google Cloud Storage, you must create a service account in Google Cloud with the appropriate credentials and permissions, then configure audit log streaming in {% data variables.product.product_name %} using the service account's credentials for authentication. +要设置流式传输到 Google Cloud Storage，您必须在 Google Cloud 中使用适当的凭据和权限创建一个服务帐户，然后使用服务帐户的凭据在 {% data variables.product.product_name %} 中配置审核日志流以进行身份验证。 -1. Create a service account for Google Cloud. You do not need to set access controls or IAM roles for the service account. For more information, see [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating) in the Google Cloud documentation. -1. Create a JSON key for the service account, and store the key securely. For more information, see [Creating and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating) in the Google Cloud documentation. -1. If you haven't created a bucket yet, create the bucket. For more information, see [Creating storage buckets](https://cloud.google.com/storage/docs/creating-buckets) in the Google Cloud documentation. -1. Give the service account the Storage Object Creator role for the bucket. For more information, see [Using Cloud IAM permissions](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add) in the Google Cloud documentation. +1. 为 Google Cloud 创建一个服务帐户。 您无需为服务帐户设置访问控制或 IAM 角色。 更多信息请参阅 Google Cloud 文档中的[创建和管理服务帐户](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating)。 +1. 创建服务帐户的 JSON 密钥，并安全地存储该密钥。 更多信息请参阅 Google Cloud 文档中的[创建和管理服务帐户密钥](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating)。 +1. 如果您尚未创建存储桶，请创建存储桶。 更多信息请参阅 Google Cloud 文档中的[创建存储桶](https://cloud.google.com/storage/docs/creating-buckets)。 +1. 为服务帐户分配存储桶的存储对象创建者角色。 更多信息请参阅 Google Cloud 文档中和[使用 Cloud IAM 权限](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add)。 {% data reusables.enterprise.navigate-to-log-streaming-tab %} -1. Select the Configure stream drop-down menu and click **Google Cloud Storage**. +1. 选择配置流下拉菜单，然后单击 **Google Cloud Storage**。 - ![Screenshot of the "Configure stream" drop-down menu](/assets/images/help/enterprises/audit-stream-choice-google-cloud-storage.png) + !["配置流"下拉菜单的屏幕截图](/assets/images/help/enterprises/audit-stream-choice-google-cloud-storage.png) -1. Under "Bucket", type the name of your Google Cloud Storage bucket. +1. 在“Bucket（存储桶）”下，键入 Google Cloud Storage 存储桶的名称。 - ![Screenshot of the "Bucket" text field](/assets/images/help/enterprises/audit-stream-bucket-google-cloud-storage.png) + !["存储桶"文本字段的屏幕截图](/assets/images/help/enterprises/audit-stream-bucket-google-cloud-storage.png) -1. Under "JSON Credentials", paste the entire contents of the file for your service account's JSON key. +1. 在“JSON Credentials（JSON 凭据）”下，粘贴服务帐户的 JSON 密钥文件的全部内容。 - ![Screenshot of the "JSON Credentials" text field](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png) + !["JSON 凭据"文本字段的屏幕截图](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png) -1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**. +1. 要验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Google Cloud Storage 存储桶，请单击 **Check endpoint（检查端点）**。 - ![Screenshot of the "Check endpoint" button](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png) + !["检查端点"按钮的屏幕截图](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png) {% data reusables.enterprise.verify-audit-log-streaming-endpoint %} -### Setting up streaming to Splunk +### 设置流式传输到 Splunk -To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation. +要将审核日志流式传输到 Splunk 的 HTTP 事件收集器 (HEC) 端点，必须确保将终端节点配置为接受 HTTPS 连接。 更多信息请参阅 Splunk 文档中的[在 Splunk Web 中设置和使用 HTTP 事件收集器](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector)。 {% data reusables.enterprise.navigate-to-log-streaming-tab %} -1. Click **Configure stream** and select **Splunk**. +1. 单击 **Configure stream（配置流）**，然后选择 **Splunk**。 - ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png) + ![从下拉菜单中选择 Splunk](/assets/images/help/enterprises/audit-stream-choice-splunk.png) -1. On the configuration page, enter: - * The domain on which the application you want to stream to is hosted. +1. 在配置页面上，输入： + * 要流式传输到的应用程序所在的域。 - If you are using Splunk Cloud, `Domain` should be `http-inputs-`, where `host` is the domain you use in Splunk Cloud. 例如：`http-inputs-mycompany.splunkcloud.com`。 + 如果您使用的是 Splunk Cloud，`Domain` 应为 `http-inputs-`，其中 `host` 是您在 Splunk Cloud 中使用的域。 例如：`http-inputs-mycompany.splunkcloud.com`。 - * The port on which the application accepts data.
+ * 应用程序接受数据的端口。
- If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`. + 如果您使用的是 Splunk Cloud，`Port` 应为 `443`（如果您尚未更改端口配置）。 如果您使用的是 Splunk Cloud 的免费试用版，`Port` 应为 `8088`。 - * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application. + * {% data variables.product.prodname_dotcom %} 可用来验证第三方应用程序的令牌。 - ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png) + ![输入流设置](/assets/images/help/enterprises/audit-stream-add-splunk.png) -1. Leave the **Enable SSL verification** check box selected. +1. 选中 **Enable SSL verification（启用 SSL 验证）**复选框。 - Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled. -1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png) + 审核日志始终作为加密数据进行流式传输，但是，如果选择此选项， {% data variables.product.prodname_dotcom %} 在传递事件时会验证 Splunk 实例的 SSL 证书。 SSL 验证有助于确保将事件安全地传递到 URL 端点。 您可以清除此选项的选择，但我们建议您将 SSL 验证保留为启用状态。 +1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Splunk 端点。 ![检查端点](/assets/images/help/enterprises/audit-stream-check-splunk.png) {% data reusables.enterprise.verify-audit-log-streaming-endpoint %} -## Pausing audit log streaming +## 暂停审核日志流 -Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream. +暂停流允许您对接收应用程序执行维护，而不会丢失审核数据。 审核日志在 {% data variables.product.product_location %} 上最多存储七天，然后在取消暂停流时导出。 {% data reusables.enterprise.navigate-to-log-streaming-tab %} -1. Click **Pause stream**. +1. 单击 **Pause stream（暂停流）**。 - ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png) + ![暂停流](/assets/images/help/enterprises/audit-stream-pause.png) -1. A confirmation message is displayed. Click **Pause stream** to confirm. +1. 将显示一条确认消息。 单击 **Pause stream（暂停流）**以确认。 -When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs. +当应用程序准备好再次接收审核日志时，单击 **Resume stream（恢复流）**以重新启动流式处理审核日志。 -## Deleting the audit log stream +## 删除审核日志流 {% data reusables.enterprise.navigate-to-log-streaming-tab %} -1. Click **Delete stream**. +1. 单击 **Delete stream（删除流）**。 - ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png) + ![删除流](/assets/images/help/enterprises/audit-stream-delete.png) -1. A confirmation message is displayed. Click **Delete stream** to confirm. +1. 将显示一条确认消息。 单击 **Delete stream（删除流）**以确认。 diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md index f6496d5cd5..21b8cf9e6b 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Viewing the audit logs for organizations in your enterprise +title: 查看企业中组织的审核日志 intro: 企业所有者可以在其审核日志中查看企业帐户拥有的所有组织的汇总操作。 redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account @@ -29,7 +29,7 @@ shortTitle: 查看组织审核日志 您可以在审核日志中搜索特定事件并导出审核日志数据。 有关搜索审核日志和特定组织事件的更多信息，请参阅“[审查组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)”。 -You can also stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit logs for organizations in your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)." +您还可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。 更多信息请参阅“[流式传输企业帐户中组织的审核日志](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index 118c7c798a..d4ce4c91cd 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -43,7 +43,7 @@ shortTitle: 邀请人员进行管理 ## {% ifversion ghec %}邀请{% elsif ghes %}添加{% endif %} 企业管理员到您的企业帐户 -{% ifversion ghec %}在邀请别人加入企业帐户后，他们必须接受电子邮件邀请，然后才可访问企业帐户。 Pending invitations will expire after 7 days.{% endif %} +{% ifversion ghec %}在邀请别人加入企业帐户后，他们必须接受电子邮件邀请，然后才可访问企业帐户。 待处理的邀请将在 7 天后过期。{% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} @@ -66,10 +66,10 @@ shortTitle: 邀请人员进行管理 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.enterprise-accounts.administrators-tab %} -1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click {% ifversion ghes %}**Remove owner**{% elsif ghec %}**Convert to member**{% endif %}. +1. 在您要删除的人员用户名旁边，单击 {% octicon "gear" aria-label="The Settings gear" %}，然后单击 {% ifversion ghes %}**Remove owner（删除所有者）**{% elsif ghec %}**Convert to member（转换为成员）**{% endif %}。 {% ifversion ghec %} ![包含删除企业管理员的菜单选项的设置齿轮](/assets/images/help/business-accounts/remove-admin.png) {% elsif ghes %} ![包含删除企业管理员的菜单选项的设置齿轮](/assets/images/help/business-accounts/ghes-remove-owner.png) {% endif %} -1. Read the confirmation, then click {% ifversion ghes %}**Remove owner**{% elsif ghec %}**Yes, convert USERNAME to member**{% endif %}. +1. 阅读确认信息，然后单击 {% ifversion ghes %}**Remove owner（删除所有者）**{% elsif ghec %}**Yes, convert USERNAME to member（是，将 [用户名] 转换为成员）**{% endif %}。 diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md index 18acc84060..de082a51d7 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md @@ -15,7 +15,7 @@ shortTitle: 管理支持权利 拥有企业帐户支持权限的人员可以使用支持门户打开、查看和评论与企业帐户相关的支持事件单。 -企业所有人和帐单管理员自动拥有支持权利。 Enterprise owners can add support entitlements to up to 20 additional members of organizations owned by their enterprise account. +企业所有人和帐单管理员自动拥有支持权利。 企业所有者可以向企业帐户拥有的最多 20 个额外组织成员添加支持权利。 ## 向企业成员添加支持权利 @@ -28,8 +28,8 @@ shortTitle: 管理支持权利 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} 3. 在“Settings（设置）”下，单击 **Support（支持）**。 ![支持菜单项](/assets/images/help/enterprises/settings-support.png) -4. 在“Add support member（添加支持成员）”下，开始键入要提供支持权利的人员的名称或用户名。 在匹配列表中单击其名称。 ![Add support entitlement search](/assets/images/help/enterprises/settings-support-entitlement-search.png) -5. 单击 **Add support entitlement（添加支持权利）**。 ![Add support entitlement button](/assets/images/help/enterprises/settings-support-add-entitlement.png) +4. 在“Add support member（添加支持成员）”下，开始键入要提供支持权利的人员的名称或用户名。 在匹配列表中单击其名称。 ![添加支持权利搜索](/assets/images/help/enterprises/settings-support-entitlement-search.png) +5. 单击 **Add support entitlement（添加支持权利）**。 ![添加支持权利按钮](/assets/images/help/enterprises/settings-support-add-entitlement.png) ## 从企业成员删除支持权利 diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md index 4c7c1d6872..37a94184be 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -1,6 +1,6 @@ --- -title: 企业中的角色 -intro: 企业中的每个人都是企业的成员。 要控制对企业的设置和数据的访问权限，您可以为企业成员分配不同的角色。 +title: Roles in an enterprise +intro: 'Everyone in an enterprise is a member of the enterprise. To control access to your enterprise''s settings and data, you can assign different roles to members of your enterprise.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account @@ -15,68 +15,68 @@ topics: - Enterprise --- -## 关于企业中的角色 +## About roles in an enterprise -企业中的每个人都是企业的成员。 您还可以为企业成员分配管理角色。 每个管理员角色都映射到业务职能，并提供在企业中执行特定任务的权限。 +Everyone in an enterprise is a member of the enterprise. You can also assign administrative roles to members of your enterprise. Each administrator role maps to business functions and provides permissions to do specific tasks within the enterprise. {% data reusables.enterprise-accounts.enterprise-administrators %} {% ifversion ghec %} -如果您的企业没有使用 {% data variables.product.prodname_emus %}，您可以邀请他人使用他们控制的 {% data variables.product.product_name %} 用户帐户来管理角色。 For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." +If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." -在使用 {% data variables.product.prodname_emus %} 的企业中，必须通过身份提供商预配新所有者和成员。 企业所有者和组织所有者不能使用 {% data variables.product.prodname_dotcom %} 向企业添加新成员或所有者。 您可以使用 IdP 选择成员的企业角色，它不能在 {% data variables.product.prodname_dotcom %} 上更改。 您可以在 {% data variables.product.prodname_dotcom %} 上选择成员在组织中的角色。 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。 +In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." {% else %} -有关向企业添加人员的更多信息，请参阅“[身份验证](/admin/authentication)”。 +For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)". {% endif %} ## Enterprise owners -企业所有者可以完全控制企业，并可以采取所有操作，包括： -- 管理管理员 +Enterprise owners have complete control over the enterprise and can take every action, including: +- Managing administrators - {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise{% if remove-enterprise-members %} - Removing enterprise members from all organizations owned by the enterprise{% endif %} -- 管理企业设置 -- 在组织范围内强制实施政策 -{% ifversion ghec %}- 管理帐单设置{% endif %} +- Managing enterprise settings +- Enforcing policy across organizations +{% ifversion ghec %}- Managing billing settings{% endif %} {% if enterprise-owner-join-org %} Enterprise owners do not have access to organization settings or content by default. To gain access, enterprise owners can join any organization owned by their enterprise. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)." Owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. {% else %} -企业所有者无法访问组织设置或内容，除非将其设为组织所有者或授予直接访问组织所拥有仓库的权限。 同样，除非您将其设为企业所有者，否则企业中的组织所有者无权访问企业。 +Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. {% endif %} -企业所有者仅在他们是企业中至少一个组织的所有者或成员时才可使用许可证。 Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}企业所有者必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。{% endif %} 作为最佳实践，我们建议只将少数人设为公司的企业所有者，以降低业务风险。 +An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. -## 企业成员 +## Enterprise members -您的企业所拥有组织的成员也会自动成为企业的成员。 成员可以在组织中进行协作，也可以是组织所有者，但成员无法访问或配置企业设置{% ifversion ghec %}，包括计费设置{% endif %}。 +Members of organizations owned by your enterprise are also automatically members of the enterprise. Members can collaborate in organizations and may be organization owners, but members cannot access or configure enterprise settings{% ifversion ghec %}, including billing settings{% endif %}. -企业中的人员可能对您的企业拥有的各种组织以及这些组织中的仓库具有不同级别的访问权限。 您可以查看每个人具有访问权限的资源。 更多信息请参阅“[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)”。 +People in your enterprise may have different levels of access to the various organizations owned by your enterprise and to repositories within those organizations. You can view the resources that each person has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)." For more information about organization-level permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -对组织所拥有仓库具有外部协作者访问权限的人员也会在企业的 People（人员）选项卡中列出，但他们不是企业成员，也没有对企业的任何访问权限。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." +People with outside collaborator access to repositories owned by your organization are also listed in your enterprise's People tab, but are not enterprise members and do not have any access to the enterprise. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." {% ifversion ghec %} -## 帐单管理员 +## Billing managers -帐单管理员只能访问企业的帐单设置。 企业的帐单管理员可以： -- 查看和管理用户许可证、{% data variables.large_files.product_name_short %} 包以及其他计费设置 -- 查看帐单管理员列表 -- 添加或删除其他帐单管理员 +Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can: +- View and manage user licenses, {% data variables.large_files.product_name_short %} packs and other billing settings +- View a list of billing managers +- Add or remove other billing managers -帐单管理员仅在他们是企业中至少一个组织的所有者或成员时才可使用许可证。 帐单管理员无权访问企业中的组织或仓库，也无法添加或删除企业所有者。 帐单管理员必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。 +Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}. -## 关于支持权利 +## About support entitlements {% data reusables.enterprise-accounts.support-entitlements %} -## 延伸阅读 +## Further reading -- “[关于企业帐户](/admin/overview/about-enterprise-accounts)” +- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)" {% endif %} diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md index 169f69d6a4..c4d8ce299e 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md @@ -31,7 +31,7 @@ shortTitle: 连接 Azure 订阅 {% note %} - **Note:** {% data variables.product.company_short %}'s Subscription Permission Validation requests read-only access to display the list of available subscriptions. To select an Azure subscription, you must have owner permissions to the subscription. If the default tenant does not have the right permissions, you may need to specify a different tenant ID. For more information, see [Microsoft identity platform and OAuth 2.0 authorization code flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code) in Microsoft Docs. + **注意：**{% data variables.product.company_short %}的订阅权限验证请求只读访问权限以显示可用订阅的列表。 要选择 Azure 订阅，必须对订阅拥有所有者权限。 如果默认租户没有正确的权限，则可能需要指定其他租户 ID。 更多信息请参阅 Microsoft 文档中的 [Microsoft 身份平台和 OAuth 2.0 授权代码流](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code)。 {% endnote %} 1. 单击 **Connect（连接）**。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md index 40c479eb51..4b5d03893f 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md @@ -37,7 +37,7 @@ You can disable {% data variables.product.prodname_dependabot_security_updates % ## Supported repositories -{% data variables.product.prodname_dotcom %} automatically enables {% data variables.product.prodname_dependabot_security_updates %} for every repository that meets these prerequisites. +{% data variables.product.prodname_dotcom %} automatically enables {% data variables.product.prodname_dependabot_security_updates %} for every repository that meets these prerequisites. {% note %} @@ -59,7 +59,7 @@ If security updates are not enabled for your repository and you don't know why, You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). -You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)." @@ -68,7 +68,7 @@ You can also enable or disable {% data variables.product.prodname_dependabot_sec {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. +1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}For public repositories, the button is disabled if the feature is always enabled.{% endif %} {% ifversion fpt or ghec %}!["Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png){% else %}!["Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index de81712e37..53c972c93f 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -84,7 +84,7 @@ The recommended formats explicitly define which versions are used for all direct {%- endif %} | Maven | Java, Scala | `pom.xml` | `pom.xml` | | npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} | +| pip | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} | {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %} | Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %} | RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md index 8639909d3a..4e5b322513 100644 --- a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md +++ b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md @@ -46,7 +46,8 @@ topics: {% endif %} 1. 默认情况下，为了提高应用程序的安全性，应用程序将使用过期用户授权令牌。 要选择不使用过期用户令牌，您必须取消选中“Expire user authorization tokens（过期用户授权令牌）”。 要了解有关设置刷新令牌流程和过期用户令牌的好处，请参阅“[刷新用户到服务器的访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”。 ![在 GitHub 应用程序设置过程中选择加入过期用户令牌的选项](/assets/images/github-apps/expire-user-tokens-selection.png) -1. 如果应用程序授权用户使用 OAuth 流程，您可以选择**在安装过程中请求用户授权 (OAuth)**，以允许用户在安装应用程序时授权它，从而省去一个步骤。 如果您选择此选项，则“设置 URL”将不可用，用户在安装应用程序后将被重定向到您的“用户授权回调 URL”。 更多信息请参阅“[在安装过程中授权用户](/apps/installing-github-apps/#authorizing-users-during-installation)”。 ![安装过程中请求用户授权](/assets/images/github-apps/github_apps_request_auth_upon_install.png) +1. 如果应用程序授权用户使用 OAuth 流程，您可以选择**在安装过程中请求用户授权 (OAuth)**，以允许用户在安装应用程序时授权它，从而省去一个步骤。 如果您选择此选项，则“设置 URL”将不可用，用户在安装应用程序后将被重定向到您的“用户授权回调 URL”。 更多信息请参阅“[在安装过程中授权用户](/apps/installing-github-apps/#authorizing-users-during-installation)”。 ![Request user authorization during installation](/assets/images/github-apps/github_apps_request_auth_upon_install.png){% if device-flow-is-opt-in %} +1. If your GitHub App will use the device flow to identify and authorize users, click **Enable Device Flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." ![Screenshot showing field for enabling device flow](/assets/images/oauth-apps/enable-device-flow.png){% endif %} 1. 如果安装后需要附加设置，请添加一个“设置 URL”以便在用户安装应用程序后重定向他们。 ![GitHub 应用程序的设置 URL 字段 ](/assets/images/github-apps/github_apps_setup_url.png) {% note %} 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 50e8b2b9c8..4eb9f65648 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 @@ -127,7 +127,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre 设备流程允许您授权用户使用无头应用程序，例如 CLI 工具或 Git 凭据管理器。 -有关使用设备流程授权用户的更多信息，请参阅“[授权 OAuth 应用程序](/developers/apps/authorizing-oauth-apps#device-flow)”。 +{% if device-flow-is-opt-in %}Before you can use the device flow to identify and authorize users, you must first enable it in your app's settings. For more information on enabling device flow, see "[Modifying a GitHub App](/developers/apps/managing-github-apps/modifying-a-github-app)." {% endif %}For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)." ## 检查用户可以访问哪些安装资源 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 877609a529..0ac0b56718 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 @@ -126,6 +126,12 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre 设备流程允许您授权用户使用无头应用程序，例如 CLI 工具或 Git 凭据管理器。 +{% if device-flow-is-opt-in %} + +Before you can use the device flow to authorize and identify users, you must first enable it in your app's settings. For more information about enabling the device flow in your app, see "[Modifying an OAuth App](/developers/apps/managing-oauth-apps/modifying-an-oauth-app)" for OAuth Apps and "[Modifying a GitHub App](/developers/apps/managing-github-apps/modifying-a-github-app)" for GitHub Apps. + +{% endif %} + ### 设备流程概述 1. 您的应用程序会请求设备和用户验证码，并获取用户将在其中输入用户验证码的授权 URL。 @@ -255,10 +261,12 @@ Accept: application/xml | `unsupported_grant_type` | 授予类型必须为 `urn:ietf:params:oauth:grant-type:device_code`，并在您轮询 OAuth 令牌请求 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 时作为输入参数包括在内。 | | `incorrect_client_credentials` | 对于设备流程，您必须传递应用程序的客户端 ID，您可以在应用程序设置页面上找到该 ID。 设备流程不需要 `client_secret`。 | | `incorrect_device_code` | 提供的 device_code 无效。 | -| `access_denied` | 当用户在授权过程中单击取消时，您将收到 `access_denied` 错误，用户将无法再次使用验证码。 | +| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.{% if device-flow-is-opt-in %} +| `device_flow_disabled` | Device flow has not been enabled in the app's settings. For more information, see "[Device flow](#device-flow)."{% endif %} 更多信息请参阅“[OAuth 2.0 设备授权授予](https://tools.ietf.org/html/rfc8628#section-3.5)”。 + ## 非 Web 应用程序流程 非 web 身份验证适用于测试等有限的情况。 如果您需要，可以使用[基本验证](/rest/overview/other-authentication-methods#basic-authentication)，通过[个人访问令牌设置页面](/articles/creating-an-access-token-for-command-line-use)创建个人访问令牌。 此方法支持用户随时撤销访问权限。 diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md index 7690a9b48a..86412e4b25 100644 --- a/translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md +++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md @@ -49,5 +49,6 @@ topics: **注：**与 {% data variables.product.prodname_github_apps %} 不同，OAuth 应用程序不能有多个回调 URL。 {% endnote %} -{% endif %} -10. 单击 **Register application（注册应用程序）**。 ![注册应用程序的按钮](/assets/images/oauth-apps/oauth_apps_register_application.png) +{% endif %}{% if device-flow-is-opt-in %} +1. If your OAuth App will use the device flow to identify and authorize users, click **Enable Device Flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." ![Screenshot showing field for enabling device flow](/assets/images/oauth-apps/enable-device-flow.png){% endif %} +2. 单击 **Register application（注册应用程序）**。 ![注册应用程序的按钮](/assets/images/oauth-apps/oauth_apps_register_application.png) diff --git a/translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md b/translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md index 8fcae91eb1..1f909022e2 100644 --- a/translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md +++ b/translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md @@ -18,5 +18,6 @@ topics: {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. 在“Basic information（基本信息）”中，修改您要更改的 GitHub 应用程序信息。 ![GitHub 应用程序的基本信息部分](/assets/images/github-apps/github_apps_basic_information.png) +5. 在“Basic information（基本信息）”中，修改您要更改的 GitHub 应用程序信息。 ![Basic information section for your GitHub App](/assets/images/github-apps/github_apps_basic_information.png){% if device-flow-is-opt-in %} +1. If your GitHub App will use the device flow to identify and authorize users, click **Enable device flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." ![Screenshot showing field for enabling device flow](/assets/images/oauth-apps/enable-device-flow.png){% endif %} 6. 单击 **Save changes（保存更改）**。 ![保存 GitHub 应用程序更改的按钮](/assets/images/github-apps/github_apps_save_changes.png) 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 56f8485386..113f7e274f 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 @@ -20,7 +20,7 @@ shortTitle: 转移议题 {% note %} -**Note**: You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}A private repository issue cannot be transferred to a public repository.{% endif %} +**注意**：您只能在同一用户或组织帐户拥有的仓库之间转移议题。 {% ifversion fpt or ghes or ghec %}私有存储库问题无法转移到公共存储库。{% endif %} {% endnote %} 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 2b6bee14ee..b4a7974963 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 @@ -28,7 +28,7 @@ topics: {% 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)." +{% data reusables.enterprise.create-an-enterprise-account %} 更多信息请参阅“[创建企业帐户](/admin/overview/creating-an-enterprise-account)”。 {% data reusables.enterprise-accounts.invite-organization %} {% endif %} diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md index be5cc19955..4d8bdf9131 100644 --- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md +++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -24,7 +24,7 @@ shortTitle: 管理 SSH 机构 ## 添加 SSH 认证中心 -If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)”。 +如果您的企业需要 SSH 证书，企业成员应使用特殊的 URL 通过 SSH 进行 Git 操作。 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)”。 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md index 08def5f3af..4f82a703e8 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md +++ b/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md @@ -47,7 +47,7 @@ shortTitle: 关于权限 例如： - 要从仓库下载和安装包，您的令牌必须具有 `read:packages` 作用域，并且您的用户帐户必须具有读取权限。 -- |{% ifversion fpt or ghes > 3.1 or ghec %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。{% endif %} +- |{% ifversion fpt or ghes > 3.1 or ghec %}要删除 {% data variables.product.product_name %}上的包，你的令牌必须至少具有 `delete:packages` 和 `read:packages` 作用域。 存储库作用域的软件包也需要 `repo` 作用域。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”{% elsif ghae %}要删除 {% data variables.product.product_name %} 上软件包的指定版本，令牌必须具有 `delete:packages` 和 `repo` 作用域。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。{% endif %} | 作用域 | 描述 | 所需权限 | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------ | | `read:packages` | 从 {% data variables.product.prodname_registry %} 下载和安装包 | 读取 | diff --git a/translations/zh-CN/data/features/device-flow-is-opt-in.yml b/translations/zh-CN/data/features/device-flow-is-opt-in.yml new file mode 100644 index 0000000000..1b66880f95 --- /dev/null +++ b/translations/zh-CN/data/features/device-flow-is-opt-in.yml @@ -0,0 +1,6 @@ +--- +#docs-content 6307. OAuth device auth flow is opt in. +versions: + fpt: '*' + ghec: '*' + ghae: 'issue-6307'