зеркало из https://github.com/github/docs.git
New translation batch for cn (#32584)
This commit is contained in:
docubot
GitHub
Родитель
87c887ff79
Коммит
0a6e3eee6e
|
|
@ -379,6 +379,7 @@ translations/zh-CN/data/reusables/codespaces/review-pr.md,file deleted because i
|
|||
translations/zh-CN/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/dependency-review/dependency-review-api-beta-note.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md,file deleted because it no longer exists in main
|
||||
|
|
@ -567,6 +568,7 @@ translations/zh-CN/content/admin/github-actions/getting-started-with-github-acti
|
|||
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error
|
||||
|
|
@ -743,6 +745,7 @@ translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply
|
|||
translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md,rendering error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md,rendering error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
|
||||
translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
|
||||
translations/zh-CN/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
|
||||
|
|
@ -874,6 +877,8 @@ translations/zh-CN/content/get-started/quickstart/create-a-repo.md,broken liquid
|
|||
translations/zh-CN/content/get-started/quickstart/fork-a-repo.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/quickstart/github-glossary.md,rendering error
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/about-git-rebase.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,broken liquid tags
|
||||
|
|
@ -903,6 +908,7 @@ translations/zh-CN/content/issues/organizing-your-work-with-project-boards/manag
|
|||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md,broken liquid tags
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
|
||||
|
|
@ -981,6 +987,7 @@ translations/zh-CN/content/repositories/creating-and-managing-repositories/creat
|
|||
translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
|
||||
|
|
@ -999,6 +1006,7 @@ translations/zh-CN/content/rest/activity/notifications.md,broken liquid tags
|
|||
translations/zh-CN/content/rest/apps/oauth-applications.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/codespaces/codespaces.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/dependabot/index.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/dependency-graph/dependency-review.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/enterprise-admin/announcement.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/enterprise-admin/billing.md,broken liquid tags
|
||||
|
|
|
|||
|
|
|
@ -66,24 +66,35 @@ The custom label is created and assigned to the self-hosted runner. Custom label
|
|||
1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.actions.actions-unused-labels %}
|
||||
{% endif %}
|
||||
|
||||
## Using the configuration script to create and assign labels
|
||||
## Programmatically assign labels
|
||||
|
||||
You can use the configuration script on the self-hosted runner to create and assign custom labels. For example, this command assigns a label named `gpu` to the self-hosted runner.
|
||||
You can programmatically assign labels to a self-hosted runner after the runner is created, or during its initial configuration.
|
||||
|
||||
```shell
|
||||
./config.sh --labels gpu
|
||||
```
|
||||
* To programmatically assign labels to an existing self-hosted runner, you must use the REST API. For more information, see the "[Self-hosted runners](/rest/actions/self-hosted-runners)" REST API.
|
||||
* To programmatically assign labels to a self-hosted runner during the initial runner configuration, you can pass label names to the `config` script using the `labels` parameter.
|
||||
|
||||
The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
|
||||
{% note %}
|
||||
|
||||
**Note:** You cannot use the `config` script to assign labels to an existing self-hosted runner.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can use comma separation to assign multiple labels. For example:
|
||||
For example, this command assigns a label named `gpu` when configuring a new self-hosted runner:
|
||||
|
||||
```shell
|
||||
./config.sh --labels gpu,x64,linux
|
||||
```
|
||||
```
|
||||
./config.sh --url <REPOSITORY_URL> --token <REGISTRATION_TOKEN> --labels gpu
|
||||
```
|
||||
|
||||
{% note %}
|
||||
The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
|
||||
|
||||
** Note:** If you replace an existing runner, then you must reassign any custom labels.
|
||||
You can use comma separation to assign multiple labels. For example:
|
||||
|
||||
{% endnote %}
|
||||
```
|
||||
./config.sh --url <REPOSITORY_URL> --token <REGISTRATION_TOKEN> --labels gpu,x64,linux
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
** Note:** If you replace an existing runner, then you must reassign any custom labels.
|
||||
|
||||
{% endnote %}
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: 关于企业身份验证
|
||||
title: About authentication for your enterprise
|
||||
shortTitle: About authentication
|
||||
intro: '{% ifversion ghae %}必须配置 SAML 单一登录 (SSO)，这样用户才能{% else %}选择身份验证{% endif %}方式，以便访问 {% ifversion ghec %}{% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %} 上有关 {% data variables.product.product_name %}{% endif %} 的企业资源。'
|
||||
intro: 'You {% ifversion ghae %}must configure SAML single sign-on (SSO) so people can{% else %}can choose how people{% endif %} authenticate to access {% ifversion ghec %}your enterprise''s resources on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -13,140 +13,136 @@ topics:
|
|||
- Enterprise
|
||||
- Identity
|
||||
- SSO
|
||||
ms.openlocfilehash: 9931a13150ff98d7ab113d37df9622b43367fa1b
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107019'
|
||||
---
|
||||
## 关于企业身份验证
|
||||
|
||||
## About authentication for your enterprise
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% data variables.product.product_name %} 上的企业所有者可以控制对企业资源的身份验证和访问权限的要求。
|
||||
Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources.
|
||||
|
||||
可以选择允许成员创建和管理用户帐户，或者企业可以使用 {% data variables.product.prodname_emus %} 为成员创建和管理帐户。 如果你允许成员管理自己的帐户，还可以配置 SAML 身份验证，以提高团队使用的 Web 应用程序的安全性并集中管理标识和访问权限。
|
||||
{% data reusables.enterprise.ghec-authentication-options %}
|
||||
|
||||
详细了解这些选项后，要确定哪种方法最适合企业，请参阅“[确定企业的最佳身份验证方法](#identifying-the-best-authentication-method-for-your-enterprise)”。
|
||||
After learning more about these options, to determine which method is best for your enterprise, see "[Identifying the best authentication method for your enterprise](#identifying-the-best-authentication-method-for-your-enterprise)."
|
||||
|
||||
## {% data variables.product.product_name %} 的身份验证方法
|
||||
## Authentication methods for {% data variables.product.product_name %}
|
||||
|
||||
以下选项可用于在 {% data variables.product.product_name %} 上进行帐户管理和身份验证。
|
||||
The following options are available for account management and authentication on {% data variables.product.product_name %}.
|
||||
|
||||
- [ {% data variables.location.product_location %} 进行身份验证](#authentication-through-githubcom)
|
||||
- [通过 {% data variables.location.product_location %} 进行身份验证，并具有其他 SAML 访问限制](#authentication-through-githubcom-with-additional-saml-access-restriction)
|
||||
- [使用 {% data variables.product.prodname_emus %} 和联合方法进行身份验证](#authentication-with-enterprise-managed-users-and-federation)
|
||||
- [Authentication through {% data variables.location.product_location %}](#authentication-through-githubcom)
|
||||
- [Authentication through {% data variables.location.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction)
|
||||
- [Authentication with {% data variables.product.prodname_emus %} and federation](#authentication-with-enterprise-managed-users-and-federation)
|
||||
|
||||
### 通过 {% data variables.location.product_location %} 进行身份验证
|
||||
### Authentication through {% data variables.location.product_location %}
|
||||
|
||||
默认情况下，每个成员必须在 {% data variables.location.product_location %} 上创建个人帐户。 你授予对企业的访问权限，成员在 {% data variables.location.product_location %} 上登录帐户后方可访问企业资源。 成员管理帐户，并且可以为 {% data variables.location.product_location %} 上的其他企业、组织和存储库做出贡献。
|
||||
By default, each member must create a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.location.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %}.
|
||||
|
||||
### 通过 {% data variables.location.product_location %} 进行身份验证，并具有其他 SAML 访问限制
|
||||
### Authentication through {% data variables.location.product_location %} with additional SAML access restriction
|
||||
|
||||
如果配置其他 SAML 访问限制，每个成员就必须在 {% data variables.location.product_location %} 上创建和管理个人帐户。 你授予对企业的访问权限，成员在 {% data variables.location.product_location %} 上登录帐户并成功通过 SAML 标识提供者 (IdP) 进行身份验证后，方可访问企业资源。 成员可以使用其个人帐户为 {% data variables.location.product_location %} 上的其他企业、组织和存储库做出贡献。 有关要求对所有企业资源访问进行 SAML 身份验证的详细信息，请参阅“[关于适用于企业 IAM 的 SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)”。
|
||||
If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.location.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
|
||||
|
||||
如果对 {% data variables.product.product_name %} 使用独立组织，或者不想对企业中的每个组织使用 SAML 身份验证，则可以为单个组织配置 SAML。 有关详细信息，请参阅[关于使用 SAML 单一登录进行标识和访问管理](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)。
|
||||
If you use a standalone organization with {% data variables.product.product_name %}, or if you don't want to use SAML authentication for every organization in your enterprise, you can configure SAML for an individual organization. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
|
||||
|
||||
### 使用 {% data variables.product.prodname_emus %} 和联合方法进行身份验证
|
||||
### Authentication with {% data variables.product.prodname_emus %} and federation
|
||||
|
||||
如果需要对 {% data variables.location.product_location %} 上的企业成员的帐户进行更多控制，可以使用 {% data variables.product.prodname_emus %}。 使用 {% data variables.product.prodname_emus %} 时，可以使用 IdP 在 {% data variables.location.product_location %} 上为企业成员预配和管理帐户。 每个成员会登录到你创建的帐户，由企业管理该帐户。 对 {% data variables.product.prodname_dotcom_the_website %} 的其余部分的贡献受到限制。 有关详细信息，请参阅[关于 {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)。
|
||||
If you need more control of the accounts for your enterprise members on {% data variables.location.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.location.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)."
|
||||
|
||||
## 确定企业的最佳身份验证方法
|
||||
## Identifying the best authentication method for your enterprise
|
||||
|
||||
SAML SSO 和 {% data variables.product.prodname_emus %} 都可增强企业资源的安全性。 {% data variables.product.prodname_emus %} 还可用于控制企业成员的用户帐户并限制帐户可以执行的操作。 但如果这些限制阻碍了开发人员的工作流，这些限制可能得不到企业的承认。
|
||||
Both SAML SSO and {% data variables.product.prodname_emus %} increase security for your enterprise's resources. {% data variables.product.prodname_emus %} additionally allows you to control the user accounts for your enterprise members and restricts what the accounts are able to do. However, those restrictions may be unacceptable for your enterprise if they obstruct your developers' workflows.
|
||||
|
||||
要确定企业是更多地受益于 SAML SSO 还是 {% data variables.product.prodname_emus %}，请问问自己以下这些问题。
|
||||
To determine whether your enterprise would benefit more from SAML SSO or {% data variables.product.prodname_emus %}, ask yourself these questions.
|
||||
|
||||
- [是否希望控制用户的用户帐户？](#do-you-want-to-control-the-user-accounts-for-your-users)
|
||||
- [企业使用的标识提供者是什么？](#which-identity-provider-does-your-enterprise-use)
|
||||
- [开发人员是在公共存储库、Gist 还是在 {% data variables.product.prodname_pages %} 站点上工作？](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites)
|
||||
- [开发人员是否依赖于企业外部的协作？](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise)
|
||||
- [企业是否依赖于外部协作者？](#does-your-enterprise-rely-on-outside-collaborators)
|
||||
- [企业能否容忍迁移成本？](#can-your-enterprise-tolerate-migration-costs)
|
||||
- [Do you want to control the user accounts for your users?](#do-you-want-to-control-the-user-accounts-for-your-users)
|
||||
- [Which identity provider does your enterprise use?](#which-identity-provider-does-your-enterprise-use)
|
||||
- [Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites)
|
||||
- [Do your developers rely on collaboration outside of your enterprise?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise)
|
||||
- [Does your enterprise rely on outside collaborators?](#does-your-enterprise-rely-on-outside-collaborators)
|
||||
- [Can your enterprise tolerate migration costs?](#can-your-enterprise-tolerate-migration-costs)
|
||||
|
||||
### 是否希望控制用户的用户帐户？
|
||||
### Do you want to control the user accounts for your users?
|
||||
|
||||
如果你不希望企业成员在 {% data variables.product.prodname_dotcom_the_website %} 上使用其自己的个人帐户来访问企业资源，则 {% data variables.product.prodname_emus %} 可能适合你的企业。
|
||||
{% data variables.product.prodname_emus %} may be right for your enterprise if you don't want enterprise members to use their own personal accounts on {% data variables.product.prodname_dotcom_the_website %} to access your enterprise's resources.
|
||||
|
||||
借助 SAML SSO，开发人员可以创建和管理其自己的个人帐户，并且每个帐户都链接到 IdP 中的 SAML 标识。 {% data variables.product.prodname_emus %} 的功能更像其他熟悉的 SSO 解决方案，因为你可以为用户预配帐户。 还可通过控制与帐户关联的用户名和电子邮件地址，确保用户帐户符合公司标识。
|
||||
With SAML SSO, developers create and manage their own personal accounts, and each account is linked to a SAML identity in your IdP. {% data variables.product.prodname_emus %} functions more like other familiar SSO solutions, as you will provision the accounts for your users. You can also ensure user accounts conform with your company identity, by controlling usernames and the email addresses associated with the accounts.
|
||||
|
||||
如果你当前要求用户在 {% data variables.product.prodname_dotcom_the_website %} 上创建新帐户以仅在你的企业中使用，则 {% data variables.product.prodname_emus %} 可能更适合你。 但是，如果将 IdP 用作用户和访问管理的真相源，则 SAML SSO 可能是更好的选择，因为它可以显著降低复杂性。 例如，也许你的企业没有在 IdP 中加入新用户的既定流程。
|
||||
If you currently require your users to create a new account on {% data variables.product.prodname_dotcom_the_website %} to use with your enterprise only, {% data variables.product.prodname_emus %} might be right for you. However, SAML SSO may be a better option if using your IdP as the source of truth for your user and access management would add too much complexity. For example, perhaps your enterprise does not have an established process for onboarding new users in your IdP.
|
||||
|
||||
### 企业使用的标识提供者是什么？
|
||||
### Which identity provider does your enterprise use?
|
||||
|
||||
{% data variables.product.prodname_emus %} 支持有限数量的 IdP，而 SAML SSO 充分支持大量 IdP，并对所有实施 SAML 2.0 标准的 IdP 提供有限支持。 有关每个选项支持的 IDP 列表，请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)”和“[关于企业 IAM 的 SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)”。
|
||||
{% data variables.product.prodname_emus %} is supported for a limited number of IdPs, while SAML SSO offers full support for a larger number of IdPs, plus limited support for all IdPs that implement the SAML 2.0 standard. For the list of supported IdPs for each option, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)" and "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)."
|
||||
|
||||
仅当将不受支持的 IdP 联合到受支持的 IdP 以用作集成点时，才能将 {% data variables.product.prodname_emus %} 与不受支持的 IdP 一起使用。 如果想要避免这种额外的复杂性，SAML SSO 可能是更好的解决方案。
|
||||
You can use {% data variables.product.prodname_emus %} with an unsupported IdP only if you federate the unsupported IdP to a supported IdP to use as an integration point. If you wish to avoid this extra complexity, SAML SSO may be a better solution for you.
|
||||
|
||||
### 开发人员是在公共存储库、Gist 还是在 {% data variables.product.prodname_pages %} 站点上工作？
|
||||
### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?
|
||||
|
||||
为防止企业成员在 {% data variables.product.prodname_dotcom_the_website %} 上意外将企业拥有的内容泄露给公众，{% data variables.product.prodname_emus %} 对用户可执行的操作施加了严格的限制。 例如，{% data variables.enterprise.prodname_managed_users %} 无法创建公共存储库、任何可见性的 Gist 或在企业外部可见的 {% data variables.product.prodname_pages %} 站点。 有关限制的完整列表，请参阅“[{% data variables.enterprise.prodname_managed_users %} 的功能和限制](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)”。
|
||||
To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.enterprise.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)."
|
||||
|
||||
某些企业可能无法接受这些限制。 要确定 {% data variables.product.prodname_emus %} 是否适合你，请与你的开发人员一起查看限制，并确认任何限制是否会阻碍你现有的工作流。 如果会，SAML SSO 可能是企业更好的选择。
|
||||
These restrictions are unacceptable for some enterprises. To determine whether {% data variables.product.prodname_emus %} will work for you, review the restrictions with your developers, and confirm whether any of the restrictions will hinder your existing workflows. If so, SAML SSO may be a better choice for your enterprise.
|
||||
|
||||
### 开发人员是否依赖于企业外部的协作？
|
||||
### Do your developers rely on collaboration outside of your enterprise?
|
||||
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} 仅适用于企业内的存储库。 如果开发人员必须参与企业内外的存储库（包括专用存储库），则 {% data variables.product.prodname_emus %} 可能不适合你的企业。 SAML SSO 可能是更好的解决方案。
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers must contribute to both repositories within and outside of your enterprise, including private repositories, {% data variables.product.prodname_emus %} may not be right for your enterprise. SAML SSO may be a better solution.
|
||||
|
||||
某些公司在 {% data variables.location.product_location %} 上使用 SAML SSO 维护现有企业中的存储库，还会创建 {% data variables.enterprise.prodname_emu_enterprise %}。 从单个工作站参与两个企业拥有的存储库的开发人员必须在单个浏览器中，在 {% data variables.location.product_location %} 上的帐户之间切换，或者为每个帐户使用不同的浏览器。 开发人员可能还需要自定义工作站的 Git 配置，以适应这两个帐户。 此工作流的复杂性可能会增加错误地将内部代码泄露给公众的风险。
|
||||
Some companies maintain repositories within an existing enterprise using SAML SSO on {% data variables.location.product_location %}, and also create an {% data variables.enterprise.prodname_emu_enterprise %}. Developers who contribute to repositories owned by both enterprises from a single workstation must switch between the accounts on {% data variables.location.product_location %} within a single browser, or use a different browser for each account. The developer may also need to customize the workstation's Git configuration to accommodate the two accounts. The complexity of this workflow can increase the risk of mistakenly leaking internal code to the public.
|
||||
|
||||
如果你决定创建 {% data variables.enterprise.prodname_emu_enterprise %}，但要求开发人员从单个工作站参与企业外部的资源，可以在开发人员的本地 Git 配置中为帐户之间的切换提供支持。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)”。
|
||||
If you decide to create an {% data variables.enterprise.prodname_emu_enterprise %} but require that developers contribute to resources outside of the enterprise from a single workstation, you can provide support for switching between the accounts in a developer's local Git configuration. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)."
|
||||
|
||||
### 企业是否依赖于外部协作者？
|
||||
### Does your enterprise rely on outside collaborators?
|
||||
|
||||
借助 SAML SSO，可使用外部协作者角色向非 IdP 目录成员的人员授予对特定存储库的访问权限。 这对于企业外部的合作者（如承包商）尤其有用。 有关详细信息，请参阅“[将外部协作者添加到组织中的存储库](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)”。
|
||||
With SAML SSO, you can give access to specific repositories to people who are not members of your IdP's directory, by using the outside collaborator role. This can be especially useful for collaborators that are external to your business, such as contractors. For more information, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
|
||||
|
||||
使用 {% data variables.product.prodname_emus %} 时，不存在外部协作者角色。 企业资源只能被 {% data variables.enterprise.prodname_managed_users %} 访问，后者始终由 IdP 预配。 要让外部合作者访问你的企业，必须在 IdP 中使用来宾帐户。 如果你对 {% data variables.product.prodname_emus %} 感兴趣，请与开发人员确认这是否会妨碍其任何现有工作流。 如果会，SAML SSO 可能是更好的解决方案。
|
||||
With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.enterprise.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution.
|
||||
|
||||
### 企业能否容忍迁移成本？
|
||||
### Can your enterprise tolerate migration costs?
|
||||
|
||||
如果企业不熟悉 {% data variables.product.prodname_dotcom_the_website %}，SAML SSO 和 {% data variables.product.prodname_emus %} 同样易于采用。
|
||||
If your enterprise is new to {% data variables.product.prodname_dotcom_the_website %}, SAML SSO and {% data variables.product.prodname_emus %} are equally easy to adopt.
|
||||
|
||||
如果已与管理其自己的用户帐户的开发人员一起使用 {% data variables.product.prodname_dotcom_the_website %}，则采用 {% data variables.product.prodname_emus %} 时需要迁移到新的企业帐户。 有关详细信息，请参阅“[关于具有 {% data variables.enterprise.prodname_managed_users %} 的企业](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)”。
|
||||
If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)."
|
||||
|
||||
虽然 {% data variables.product.prodname_emus %} 是免费的，但迁移过程可能需要团队付出时间或成本。 确认你的企业和开发人员可以接受此迁移过程。 如果无法接受，SAML SSO 可能是更好的选择。
|
||||
Although {% data variables.product.prodname_emus %} is free, the migration process may require time or cost from your team. Confirm that this migration process is acceptable to your business and your developers. If not, SAML SSO may be the better choice for you.
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
站点管理员可以决定用户如何进行身份验证以访问 {% data variables.product.product_name %} 实例。 可以使用 {% data variables.product.product_name %} 的内置身份验证，或者，如果要集中管理你的团队使用的 Web 应用程序的标识和访问权限，则可以配置外部身份验证方法。
|
||||
Site administrators can decide how people authenticate to access a {% data variables.product.product_name %} instance. You can use {% data variables.product.product_name %}'s built-in authentication, or, if you want to centralize identity and access management for the web applications that your team uses, you can configure an external authentication method.
|
||||
|
||||
## {% data variables.product.product_name %} 的身份验证方法
|
||||
## Authentication methods for {% data variables.product.product_name %}
|
||||
|
||||
{% data variables.product.product_name %} 可使用以下身份验证方法。
|
||||
The following authentication methods are available for {% data variables.product.product_name %}.
|
||||
|
||||
- [内置身份验证](#built-in-authentication)
|
||||
- [外部身份验证](#external-authentication)
|
||||
- [Built-in authentication](#built-in-authentication)
|
||||
- [External authentication](#external-authentication)
|
||||
|
||||
### 内置身份验证
|
||||
### Built-in authentication
|
||||
|
||||
{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} 若要访问实例，人员需使用帐户的凭据进行身份验证。 有关详细信息，请参阅“[配置内置身份验证](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)”。
|
||||
{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} To access your instance, people authenticate with the credentials for the account. For more information, see "[Configuring built-in authentication](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)."
|
||||
|
||||
### 外部身份验证
|
||||
### External authentication
|
||||
|
||||
如果使用外部目录或标识提供者 (IdP) 集中访问多个 Web 应用程序，可以为 {% data variables.location.product_location %} 配置外部身份验证。 有关详细信息，请参阅以下文章。
|
||||
If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.location.product_location %}. For more information, see the following articles.
|
||||
|
||||
- [将 CAS 用于企业 IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)
|
||||
- [将 LDAP 用于企业 IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)
|
||||
- [将 SAML 用于企业 IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam)
|
||||
- "[Using CAS for enterprise IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)"
|
||||
- "[Using LDAP for enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)"
|
||||
- "[Using SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam)"
|
||||
|
||||
如果选择使用外部身份验证，还可以为没有外部身份验证提供程序帐户的人员配置回退身份验证。 例如，你可能想要向承包商或计算机用户授予访问权限。 有关详细信息，请参阅“[允许对提供者外部的用户使用内置身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)”。
|
||||
If you choose to use external authentication, you can also configure fallback authentication for people who don't have an account on your external authentication provider. For example, you may want to grant access to a contractor or machine user. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)."
|
||||
|
||||
{% ifversion scim-for-ghes %}
|
||||
|
||||
如果使用 SAML SSO 进行身份验证，还可以使用 SCIM 预配用户并将 IdP 组映射到团队。 有关详细信息，请参阅“[使用 SCIM 为企业配置用户预配](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)”。
|
||||
If you use SAML SSO for authentication, you can also provision users and map IdP groups to teams using SCIM. For more information, see "[Configuring user provisioning with SCIM for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
{% data variables.product.product_name %} 使用 SAML SSO 进行身份验证。 企业所有者必须在初始化期间使用 SAML 标识提供者 (IdP) 配置 SAML SSO。 有关详细信息，请参阅“[关于适用于企业 IAM 的 SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)”。
|
||||
{% data variables.product.product_name %} uses SAML SSO for authentication. Enterprise owners must configure SAML SSO with a SAML identity provider (IdP) during initialization. For more information, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- “[{% data variables.product.company_short %} 帐户的类型](/get-started/learning-about-github/types-of-github-accounts)”
|
||||
- “[关于企业帐户](/admin/overview/about-enterprise-accounts)”{%- ifversion ghec %}
|
||||
- “[可以为组织中的人员创建帐户吗？](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)”
|
||||
- "[Types of {% data variables.product.company_short %} accounts](/get-started/learning-about-github/types-of-github-accounts)"
|
||||
- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
|
||||
{%- ifversion ghec %}
|
||||
- "[Can I create accounts for people in my organization?](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)"
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -16,6 +16,7 @@ children:
|
|||
- /about-enterprise-accounts
|
||||
- /system-overview
|
||||
- /about-the-github-enterprise-api
|
||||
- /best-practices-for-enterprises
|
||||
- /creating-an-enterprise-account
|
||||
- /accessing-compliance-reports-for-your-enterprise
|
||||
ms.openlocfilehash: d936542993310333e314efcc9d5bb5689be00701
|
||||
|
|
|
|||
|
|
@ -54,9 +54,12 @@ If you downgrade your organization from {% data variables.product.prodname_team
|
|||
If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %}
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
**Notes:**
|
||||
- If your organization is owned by an enterprise account, billing cannot be managed at the organization level. To downgrade, you must remove the organization from the enterprise account first. For more information, see "[Removing organizations from your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
|
||||
- If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ shortTitle: About the security overview
|
|||
|
||||
## About the security overview
|
||||
|
||||
The security overview provides high-level summaries of the security status of an organization or enterprise and make it easy to identify problematic repositories that require intervention. You can also use the security overview to see which repositories have enabled specific security features and to configure any available security features that are not currently in use. {% ifversion fpt %}For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview).{% endif %}
|
||||
{% data reusables.security-overview.about-the-security-overview %} {% ifversion fpt %}For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview).{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
The security overview shows which security features are enabled for repositories and consolidate alerts for each feature.
|
||||
|
|
|
|||
|
|
@ -46,8 +46,6 @@ The dependency review feature becomes available when you enable the dependency g
|
|||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
## Dependency review enforcement
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-action-beta-note %}
|
||||
|
||||
The action is available for all {% ifversion fpt or ghec %}public repositories, as well as private {% endif %}repositories that have {% data variables.product.prodname_GH_advanced_security %} enabled.
|
||||
|
||||
{% data reusables.dependency-review.action-enterprise %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
title: 配置依赖项审查
|
||||
intro: 可以使用依赖项评审来捕获漏洞，以避免将其添加到项目中。
|
||||
title: Configuring dependency review
|
||||
intro: You can use dependency review to catch vulnerabilities before they are added to your project.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: Configure dependency review
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
|
@ -14,90 +15,201 @@ topics:
|
|||
- Vulnerabilities
|
||||
- Dependencies
|
||||
- Pull requests
|
||||
ms.openlocfilehash: e7fae5d42e4f7c14098414c28e5b5eb857c39687
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107499'
|
||||
---
|
||||
## 关于依赖项评审
|
||||
|
||||
## About dependency review
|
||||
|
||||
{% data reusables.dependency-review.feature-overview %}
|
||||
|
||||
有关详细信息，请参阅“[关于依赖项审查](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)”和“[审查拉取请求中的依赖项更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。
|
||||
For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" and "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
|
||||
|
||||
## 关于配置依赖项审查
|
||||
## About configuring dependency review
|
||||
|
||||
{% ifversion fpt %} 依赖项审查在所有产品的所有公共存储库中都可用，并且无法禁用。 依赖项审查在使用 GitHub Enterprise Cloud 并拥有 [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) 许可证的组织拥有的专用存储库中可用。 有关详细信息，请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review)。
|
||||
{% ifversion fpt %}
|
||||
Dependency review is available in all public repositories in all products and cannot be disabled. Dependency review is available in private repositories owned by organizations that use GitHub Enterprise Cloud and have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security). For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review).
|
||||
|
||||
{% elsif ghec %} 依赖项审查包含在公共存储库的 {% data variables.product.product_name %} 中。 若要在组织拥有的专用存储库中使用依赖项审查，必须具有 [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) 许可证并启用依赖项关系图。
|
||||
{% elsif ghec %}
|
||||
Dependency review is included in {% data variables.product.product_name %} for public repositories. To use dependency review in private repositories owned by organizations, you must have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) and have the dependency graph enabled.
|
||||
|
||||
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
|
||||
1. 如果尚未启用“{% data variables.product.prodname_GH_advanced_security %}”，请单击此功能旁边的“启用”。
|
||||
|
||||
1. If "{% data variables.product.prodname_GH_advanced_security %}" is not enabled, click **Enable** next to the feature.
|
||||
|
||||
|
||||
{% elsif ghes or ghae %}
|
||||
|
||||
为 {% data variables.location.product_location %} 启用依赖项关系图并且为组织或存储库启用 {% data variables.product.prodname_advanced_security %} 时，依赖项审查可用。{% ifversion ghes %} 有关详细信息，请参阅“[为企业启用 {% data variables.product.prodname_GH_advanced_security %}](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)”。{% endif %}
|
||||
Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %}
|
||||
|
||||
### 检查是否已启用依赖项关系图
|
||||
### Checking if the dependency graph is enabled
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. 在“配置安全性和分析功能”下，检查是否启用了依赖项关系图。
|
||||
1. 如果已启用依赖项关系图，请单击“{% data variables.product.prodname_GH_advanced_security %}”旁边的“启用”以启用 {% data variables.product.prodname_advanced_security %}，其中包含了依赖项审查。 如果企业没有可用的 {% data variables.product.prodname_advanced_security %} 许可证，“启用”按钮会禁用。{% ifversion ghes %} {% endif %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Configure security and analysis features", check if the dependency graph is enabled.
|
||||
1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion dependency-review-action-configuration %}
|
||||
## 配置 {% data variables.product.prodname_dependency_review_action %}
|
||||
## About configuring the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-action-beta-note %} {% data reusables.dependency-review.dependency-review-action-overview %}
|
||||
{% data reusables.dependency-review.dependency-review-action-overview %}
|
||||
|
||||
可用配置选项如下。
|
||||
The following configuration options are available.
|
||||
|
||||
| 选项 | 必选 | 使用情况 |
|
||||
| Option | Required | Usage |
|
||||
|------------------|-------------------------------|--------|
|
||||
| `fail-on-severity` | 可选 | 定义严重性级别（`low`、`moderate`、`high`、`critical`）的阈值。</br>对于引入指定严重性级别或更高级别的漏洞的任何拉取请求，该操作都将失败。 |
|
||||
{%- ifversion dependency-review-action-licenses %} | `allow-licenses` | 可选 | 包含允许的许可证列表。 可以在 API 文档的[许可证](/rest/licenses)页中找到此参数可能的值。</br>如果拉取请求引入许可证与列表不匹配的依赖项，该操作将失败。|{% endif %} {%- ifversion dependency-review-action-licenses %} | `deny-licenses` | 可选 | 包含禁止的许可证列表。 可以在 API 文档的[许可证](/rest/licenses)页中找到此参数可能的值。</br>如果拉取请求引入许可证与列表匹配的依赖项，该操作将失败。|{% endif %}
|
||||
| `fail-on-severity` | Optional | Defines the threshold for level of severity (`low`, `moderate`, `high`, `critical`).</br>The action will fail on any pull requests that introduce vulnerabilities of the specified severity level or higher. |
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
| `fail-on-scopes` | Optional | Contains a list of strings representing the build environments you want to support (`development`, `runtime`, `unknown`). </br>The action will fail on pull requests that introduce vulnerabilites in the scopes that match the list.|{% endif %}
|
||||
| `allow-ghsas` | Optional | Contains a list of {% data variables.product.prodname_advisory_database %} IDs that can be skipped during detection. You can find the possible values for this parameter in the [{% data variables.product.prodname_advisory_database %}](https://github.com/advisories). |
|
||||
| `config-file` | Optional | Specifies a path to a configuration file. The configuration file can be local to the repository or a file located in an external repository.|
|
||||
| `external-repo-token` | Optional | Specifies a token for fetching the configuration file, if the file resides in a private external repository. The token must have read access to the repository.|
|
||||
|
||||
{% ifversion dependency-review-action-licenses %} {% tip %}
|
||||
|
||||
提示：`allow-licenses` 和 `deny-licenses` 选项互斥。
|
||||
|
||||
{% endtip %} {% endif %}
|
||||
|
||||
此 {% data variables.product.prodname_dependency_review_action %} 示例文件说明了如何使用这些配置选项。 请注意，该示例使用操作 (`v2`) 的短版本号，而不是 semver 版本号（例如，`v2.0.8`）。 这可确保使用操作的最新次要版本。
|
||||
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v2
|
||||
with:
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
# allow-licenses: GPL-3.0, BSD-3-Clause, MIT
|
||||
{% tip %}
|
||||
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
# deny-licenses: LGPL-2.0, BSD-2-Clause
|
||||
{% endif %}
|
||||
```
|
||||
**Tip:** The `allow-licenses` and `deny-licenses` options are mutually exclusive.
|
||||
|
||||
有关配置选项的更多详细信息，请参阅 [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme)。
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
## Configuring the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
There are two methods of configuring the {% data variables.product.prodname_dependency_review_action %}:
|
||||
- Inlining the configuration options in your workflow file.
|
||||
- Referencing a configuration file in your workflow file.
|
||||
|
||||
Notice that all of the examples use a short version number for the action (`v3`) instead of a semver release number (for example, `v3.0.8`). This ensures that you use the most recent minor version of the action.
|
||||
### Using inline configuration to set up the {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
1. Add a new YAML workflow to your `.github/workflows` folder.
|
||||
|
||||
{% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
```
|
||||
1. Specify your settings.
|
||||
|
||||
This {% data variables.product.prodname_dependency_review_action %} example file illustrates how you can use the available configuration options.
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
with:
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
allow-licenses: GPL-3.0, BSD-3-Clause, MIT
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
deny-licenses: LGPL-2.0, BSD-2-Clause
|
||||
{% endif %}
|
||||
# ([String]). Skip these {% data variables.product.prodname_advisory_database %} IDs during detection (optional)
|
||||
# Possible values: Any valid {% data variables.product.prodname_advisory_database %} ID from https://github.com/advisories
|
||||
allow-ghsas: GHSA-abcd-1234-5679, GHSA-efgh-1234-5679
|
||||
{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
# ([String]). Block pull requests that introduce vulnerabilities in the scopes that match this list (optional)
|
||||
# Possible values: "development", "runtime", "unknown"
|
||||
fail-on-scopes: development, runtime
|
||||
{% endif %}
|
||||
```
|
||||
### Using a configuration file to set up {% data variables.product.prodname_dependency_review_action %}
|
||||
|
||||
1. Add a new YAML workflow to your `.github/workflows` folder and use `config-file` to specify that you are using a configuration file.
|
||||
|
||||
{% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
|
||||
```yaml{:copy}
|
||||
name: 'Dependency Review'
|
||||
on: [pull_request]
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
dependency-review:
|
||||
{% ifversion ghes %}runs-on: self-hosted
|
||||
{% else %}runs-on: ubuntu-latest
|
||||
{% endif %}steps:
|
||||
- name: 'Checkout Repository'
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Dependency Review
|
||||
uses: actions/dependency-review-action@v3
|
||||
with:
|
||||
# ([String]). Representing a path to a configuration file local to the repository or in an external repository.
|
||||
# Possible values: An absolute path to a local file or an external file.
|
||||
config-file: './.github/dependency-review-config.yml'
|
||||
# Syntax for an external file: OWNER/REPOSITORY/FILENAME@BRANCH
|
||||
config-file: 'github/octorepo/dependency-review-config.yml@main'
|
||||
|
||||
# ([Token]) Use if your configuration file resides in a private external repository.
|
||||
# Possible values: Any GitHub token with read access to the private external repository.
|
||||
external-repo-token: 'ghp_123456789abcde'
|
||||
```
|
||||
1. Create the configuration file in the path you have specified.
|
||||
|
||||
This YAML example file illustrates how you can use the available configuration options.
|
||||
```yaml{:copy}
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
allow-licenses:
|
||||
- GPL-3.0
|
||||
- BSD-3-Clause
|
||||
- MIT
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
deny-licenses:
|
||||
- LGPL-2.0
|
||||
- BSD-2-Clause
|
||||
{% endif %}
|
||||
# ([String]). Skip these {% data variables.product.prodname_advisory_database %} IDs during detection (optional)
|
||||
# Possible values: Any valid {% data variables.product.prodname_advisory_database %} ID from https://github.com/advisories
|
||||
allow-ghsas:
|
||||
- GHSA-abcd-1234-5679
|
||||
- GHSA-efgh-1234-5679
|
||||
{% ifversion dependency-review-action-fail-on-scopes %}
|
||||
# ([String]). Block pull requests that introduce vulnerabilities in the scopes that match this list (optional)
|
||||
# Possible values: "development", "runtime", "unknown"
|
||||
fail-on-scopes:
|
||||
- development
|
||||
- runtime
|
||||
{% endif %}
|
||||
```
|
||||
For further details about the configuration options, see [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ You can work with {% data variables.product.prodname_github_codespaces %} in the
|
|||
|
||||
If you have not already done so, run `gh auth login` to authenticate with your {% data variables.product.prodname_dotcom %} account.
|
||||
|
||||
To use `gh` to work with {% data variables.product.prodname_github_codespaces %}, type `gh codespace <COMMAND>` or its alias `gh cs <COMMAND>`.
|
||||
To use `gh` to work with {% data variables.product.prodname_github_codespaces %}, type `gh codespace SUBCOMMAND` or its alias `gh cs SUBCOMMAND`.
|
||||
|
||||
As an example of a series of commands you might use to work with {% data variables.product.prodname_github_codespaces %}, you could:
|
||||
|
||||
|
|
@ -51,15 +51,15 @@ As an example of a series of commands you might use to work with {% data variabl
|
|||
* Create a new codespace for the required repository branch:<br>
|
||||
`gh codespace create -r github/docs -b main`
|
||||
* SSH into the new codespace:<br>
|
||||
`gh codespace ssh -c mona-github-docs-v4qxrv7rfwv9w`
|
||||
`gh codespace ssh -c octocat-literate-space-parakeet-7gwrqp9q9jcx4vq`
|
||||
* Forward a port to your local machine:<br>
|
||||
`gh codespace ports forward 8000:8000 -c mona-github-docs-v4qxrv7rfwv9w`
|
||||
`gh codespace ports forward 8000:8000 -c octocat-literate-space-parakeet-7gwrqp9q9jcx4vq`
|
||||
|
||||
## `gh` commands for {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
The sections below give example commands for each of the available operations.
|
||||
|
||||
For a complete reference of `gh` commands for {% data variables.product.prodname_github_codespaces %}, including details of all available options for each command, see the {% data variables.product.prodname_cli %} online help for "[gh codespace](https://cli.github.com/manual/gh_codespace)." Alternatively, use `gh codespace [<SUBCOMMAND>...] --help` on the command line.
|
||||
For a complete reference of `gh` commands for {% data variables.product.prodname_github_codespaces %}, including details of all available options for each command, see the {% data variables.product.prodname_cli %} online help for "[gh codespace](https://cli.github.com/manual/gh_codespace)." Alternatively, on the command line, use `gh codespace --help` for general help or `gh codespace SUBCOMMAND --help` for help with a specific subcommand.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
@ -163,7 +163,7 @@ The location of files and directories on the codespace is relative to the home d
|
|||
|
||||
* Copy a file to the directory in which a repository is checked out in a codespace:
|
||||
|
||||
`gh codespace cp myfile.txt remote:/workspaces/<REPOSITORY-NAME>`
|
||||
`gh codespace cp myfile.txt remote:/workspaces/REPOSITORY-NAME`
|
||||
|
||||
* Copy a file from a codespace to the current directory on the local machine:
|
||||
|
||||
|
|
@ -233,7 +233,7 @@ You can use the {% data variables.product.prodname_cli %} extension to create a
|
|||
### Change the machine type of a codespace
|
||||
|
||||
```shell
|
||||
gh codespace edit -m <em>machine-type-name</em>
|
||||
gh codespace edit -m MACHINE-TYPE-NAME
|
||||
```
|
||||
|
||||
For more information, see the "{% data variables.product.prodname_cli %}" tab of "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
|
||||
|
|
|
|||
|
|
@ -205,6 +205,8 @@ Members of your organization or enterprise can use GitHub's learning and support
|
|||
### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
|
||||
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
### 2. Learning with {% data variables.product.prodname_learning %}
|
||||
Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot.
|
||||
|
||||
|
|
|
|||
|
|
@ -119,6 +119,8 @@ Your enterprise members can learn more about Git and {% data variables.product.p
|
|||
|
||||
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
### 2. Learning with {% data variables.product.prodname_learning %}
|
||||
{% data reusables.getting-started.learning-enterprise %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 设置 GitHub Enterprise Cloud 试用版
|
||||
intro: '可以免费试用 {% data variables.product.prodname_ghe_cloud %}。'
|
||||
title: Setting up a trial of GitHub Enterprise Cloud
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_cloud %} for free.'
|
||||
redirect_from:
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-cloud
|
||||
- /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
|
||||
|
|
@ -12,74 +12,73 @@ versions:
|
|||
topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Cloud trial
|
||||
ms.openlocfilehash: 13cb43b5dfd4a9e207a9a1cca090b223c56f4678
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147389952'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise.ghec-cta-button %}
|
||||
|
||||
|
||||
## 关于 {% data variables.product.prodname_ghe_cloud %}
|
||||
## About {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} 是为在 {% data variables.product.prodname_dotcom_the_website %} 上进行协作的大型企业或团队制定的计划。 {% data reusables.enterprise.about-github-for-enterprises %}
|
||||
{% data variables.product.prodname_ghe_cloud %} is a plan for large businesses or teams who collaborate on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise.about-github-for-enterprises %}
|
||||
|
||||
{% data reusables.organizations.about-organizations %} 有关帐户的详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 帐户类型](/get-started/learning-about-github/types-of-github-accounts)”。
|
||||
{% data reusables.organizations.about-organizations %} For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
|
||||
|
||||
您可以通过 {% data variables.product.prodname_free_team %} 免费使用组织，其中包括有限的功能。 对于其他功能，例如 SAML 单点登录 (SSO)、{% data variables.product.prodname_pages %} 的访问控制以及包含的 {% data variables.product.prodname_actions %} 分钟数，您可以升级到 {% data variables.product.prodname_ghe_cloud %}。 有关 {% data variables.product.prodname_ghe_cloud %} 可用功能的详细列表，请参阅我们的[定价](https://github.com/pricing)页面。
|
||||
You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
|
||||
|
||||
您可以设置 {% data variables.product.prodname_ghe_cloud %} 试用版，以评估新组织帐户或现有组织帐户上的这些附加功能。
|
||||
You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
|
||||
|
||||
试用版也可用于 {% data variables.product.prodname_ghe_server %}。 有关详细信息，请参阅“[设置试用版 {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)”。
|
||||
Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## 关于 {% data variables.product.prodname_ghe_cloud %} 试用版
|
||||
## About trials of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
您可以设置 30 天试用版来试用 {% data variables.product.prodname_ghe_cloud %}。 在试用期间无需提供付款方式，除非您将 {% data variables.product.prodname_marketplace %} 应用程序添加到需要付款方式的组织。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_marketplace %} 的计费](/enterprise-cloud@latest/articles/about-billing-for-github-marketplace/)”。
|
||||
You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/enterprise-cloud@latest/articles/about-billing-for-github-marketplace/)."
|
||||
|
||||
试用版包括 50 个席位。 如果需要更多席位来评估 {% data variables.product.prodname_ghe_cloud %}，请联系 {% data variables.contact.contact_enterprise_sales %}。 在试用结束时，您可以选择不同数量的席位。
|
||||
Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
|
||||
|
||||
{% data reusables.saml.saml-accounts %}
|
||||
|
||||
有关详细信息，请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于使用 SAML 单一登录进行标识和访问管理](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}”。{% else %} {% endif %}
|
||||
For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
{% data variables.product.prodname_emus %} 不是 {% data variables.product.prodname_ghe_cloud %} 免费试用版的一部分。 如果你对 {% data variables.product.prodname_emus %} 感兴趣，请联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)。
|
||||
{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
|
||||
|
||||
## 设置 {% data variables.product.prodname_ghe_cloud %} 的试用版
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
在尝试 {% data variables.product.prodname_ghe_cloud %} 之前，你必须登录到个人帐户。 如果你在 {% data variables.product.prodname_dotcom_the_website %} 上还没有个人帐户，则必须创建一个。 有关详细信息，请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/free-pro-team@latest/articles/signing-up-for-a-new-github-account)”。
|
||||
Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a personal account. If you don't already have a personal account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/free-pro-team@latest/articles/signing-up-for-a-new-github-account)."
|
||||
|
||||
1. 导航到 [{% data variables.product.prodname_dotcom %} 企业版](https://github.com/enterprise)。
|
||||
1. 单击“开始使用免费试用版”。
|
||||
|
||||
1. 单击“Enterprise Cloud”。
|
||||
|
||||
1. 按照提示配置试用版。
|
||||
1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
|
||||
1. Click **Start a free trial**.
|
||||
|
||||
1. Click **Enterprise Cloud**.
|
||||
|
||||
1. Follow the prompts to configure your trial.
|
||||
|
||||
## 探索 {% data variables.product.prodname_ghe_cloud %}
|
||||
## Exploring {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
设置试用版后，可以按照组织的“概述”选项卡上的建议任务进行操作以探索 {% data variables.product.prodname_ghe_cloud %}。 如果你之前关闭了这些任务，可以通过单击页面顶部的“开始执行建议的任务”来再次访问这些任务。
|
||||
After you set up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the suggested tasks on the "Overview" tab of your organization. If you've previously dismissed the tasks, you can access them again by clicking **Get started with suggested tasks** at the top of the page.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.docs.you-can-read-docs-for-your-product %}
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## 结束试用
|
||||
## Finishing your trial
|
||||
|
||||
在试用期间，您可以随时购买 {% data variables.product.prodname_enterprise %}。 购买 {% data variables.product.prodname_enterprise %} 将结束试用期，取消最多 50 个席位并开始付款。
|
||||
You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
|
||||
|
||||
如果您不购买 {% data variables.product.prodname_enterprise %}，则在试用期结束时，您的组织将被降级。 如果您使用现有组织进行试用，则该组织将降级为您在试用之前使用的产品。 如果您为试用版创建了新组织，则该组织将降级至 {% data variables.product.prodname_free_team %}。
|
||||
If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}.
|
||||
|
||||
您的组织将无法访问新产品中未包含的任何功能，例如高级功能，如私有仓库的 {% data variables.product.prodname_pages %} 。 如果您不打算升级，为避免无法访问高级功能，请考虑在试用期结束前公开受影响的存储库。 有关详细信息，请参阅“[设置存储库可见性](/articles/setting-repository-visibility)”。
|
||||
Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
|
||||
|
||||
降级还会禁用在试用期内配置的任何 SAML 设置。 如果您以后购买了 {% data variables.product.prodname_enterprise %}，则将再次启用 SAML 设置，以便组织中的用户进行身份验证。
|
||||
Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.billing_plans %}
|
||||
5. 在“{% data variables.product.prodname_ghe_cloud %} 免费试用版”下，单击“购买 Enterprise 版”或“降级到 Team 版” 。
|
||||
|
||||
6. 按照提示输入付款方式，然后单击“提交”。
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
|
||||
|
||||
6. Follow the prompts to enter your payment method, then click **Submit**.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 设置 GitHub Enterprise Server 试用版
|
||||
intro: '您可以免费试用 {% data variables.product.prodname_ghe_server %}。'
|
||||
title: Setting up a trial of GitHub Enterprise Server
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
|
||||
redirect_from:
|
||||
- /articles/requesting-a-trial-of-github-enterprise
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-server
|
||||
|
|
@ -13,61 +13,58 @@ versions:
|
|||
topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Server trial
|
||||
ms.openlocfilehash: eba705715818c03cb7fd1316ede6507111728806
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146454235'
|
||||
---
|
||||
## 关于 {% data variables.product.prodname_ghe_server %} 试用版
|
||||
|
||||
您可以申请 45 天试用版来试用 {% data variables.product.prodname_ghe_server %}。 您的试用版将作为虚拟设备安装，带有内部或云部署选项。 有关 {% data variables.product.prodname_ghe_server %} 以及受支持的虚拟化平台列表的详细信息，请参阅“[关于 {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)”。
|
||||
## About trials of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报和 {% data variables.product.prodname_github_connect %} 目前在 {% data variables.product.prodname_ghe_server %} 试用版中不可用。 要获取这些功能的演示，请联系 {% data variables.contact.contact_enterprise_sales %}。 有关这些功能的详细信息，请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”和“[将企业帐户连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)”。
|
||||
You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For more information about {% data variables.product.prodname_ghe_server %}, and for a list of supported virtualization platforms, see "[About {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)."
|
||||
|
||||
试用版也可用于 {% data variables.product.prodname_ghe_cloud %}。 有关详细信息，请参阅“[设置试用版 {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)”。
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
|
||||
|
||||
Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## 设置 {% data variables.product.prodname_ghe_server %} 的试用版
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} 作为虚拟设备安装。 确定组织中设置虚拟机的最佳人选，并要求该人员提交[试用请求](https://enterprise.github.com/trial)。 您可以在提交申请后立即开始试用。
|
||||
{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
|
||||
|
||||
要为 {% data variables.product.prodname_enterprise %} Web 门户设置帐户，请单击提交试用申请后您收到的电子邮件中的链接，然后按照提示操作。 然后下载您的许可文件。 有关详细信息，请参阅“[管理 {% data variables.product.prodname_enterprise %} 的许可证](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)”。
|
||||
To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
|
||||
|
||||
要安装 {% data variables.product.prodname_ghe_server %}，请下载必要的组件并上传您的许可证文件。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)”中所选可视化平台的说明。
|
||||
To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
|
||||
## 后续步骤
|
||||
## Next steps
|
||||
|
||||
要充分利用您的试用版，请按以下步骤操作：
|
||||
To get the most out of your trial, follow these steps:
|
||||
|
||||
1. [创建一个组织](/enterprise-server@latest/admin/user-management/creating-organizations)。
|
||||
2. 要了解使用 {% data variables.product.prodname_dotcom %} 的基础知识，请参阅：
|
||||
- [{% data variables.product.prodname_dotcom %} 简介](https://resources.github.com/devops/methodology/maximizing-devops-roi/)网络广播
|
||||
- {% data variables.product.prodname_dotcom %} 指南中的[理解 {% data variables.product.prodname_dotcom %} 流](https://guides.github.com/introduction/flow/)
|
||||
- {% data variables.product.prodname_dotcom %} 指南中的 [Hello World](https://guides.github.com/activities/hello-world/)
|
||||
- [关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)
|
||||
3. 若要配置实例以满足组织的需求，请参阅“[配置企业](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)”。
|
||||
4. 要将 {% data variables.product.prodname_ghe_server %} 与标识提供者集成，请参阅“[使用 SAML](/enterprise-server@latest/admin/user-management/using-saml)”和“[使用 LDAP](/enterprise-server@latest/admin/authentication/using-ldap)”。
|
||||
5. 邀请不限数量的人员加入您的试用版。
|
||||
- 使用内置身份验证或配置的身份提供程序将用户添加到 {% data variables.product.prodname_ghe_server %} 实例。 有关详细信息，请参阅“[使用内置身份验证](/enterprise-server@latest/admin/user-management/using-built-in-authentication)”。
|
||||
- 若要邀请用户成为帐户管理员，请访问 [{% data variables.product.prodname_enterprise %} Web 门户](https://enterprise.github.com/login)。
|
||||
1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
|
||||
2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
|
||||
- [Intro to {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/) webcast
|
||||
- [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
- [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
- "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
|
||||
3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
|
||||
4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
|
||||
5. Invite an unlimited number of people to join your trial.
|
||||
- Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
|
||||
- To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
|
||||
|
||||
{% note %}
|
||||
|
||||
注意：受邀成为帐户管理员的人将收到一封电子邮件，其中包含接受邀请的链接。
|
||||
**Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## 结束试用
|
||||
## Finishing your trial
|
||||
|
||||
在试用期内，你可以随时在 [{% data variables.product.prodname_enterprise %} Web 门户](https://enterprise.github.com/login)中升级到完整许可证。
|
||||
You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
|
||||
|
||||
如果您在试用的最后一天仍未升级，将收到一封电子邮件，通知您试用已结束。 如果需要更多时间来评估 {% data variables.product.prodname_enterprise %}，请联系 {% data variables.contact.contact_enterprise_sales %} 申请延期。
|
||||
If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- [设置 {% data variables.product.prodname_ghe_cloud %} 的试用版](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)
|
||||
- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 关于组织
|
||||
intro: 组织是共享帐户，其中业务和开源项目可同时跨多个项目进行协作，具有复杂的安全性和管理功能。
|
||||
title: About organizations
|
||||
intro: 'Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.'
|
||||
redirect_from:
|
||||
- /articles/about-organizations
|
||||
- /github/setting-up-and-managing-organizations-and-teams/about-organizations
|
||||
|
|
@ -12,48 +12,48 @@ versions:
|
|||
topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
ms.openlocfilehash: e18c95475e06db0623aee67515eeb6d8a1ee641f
|
||||
ms.sourcegitcommit: e98b752895109965b32cb277610985da5799f8a1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/01/2022
|
||||
ms.locfileid: '148127633'
|
||||
---
|
||||
## 关于组织
|
||||
|
||||
{% data reusables.organizations.about-organizations %}有关帐户类型的详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 帐户](/get-started/learning-about-github/types-of-github-accounts)”。
|
||||
## About organizations
|
||||
|
||||
可以邀请无限数量的人员加入组织，然后为这些组织成员提供各种角色，通过这些角色授予成员对组织及其数据不同级别的访问权限。 有关详细信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。
|
||||
{% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
|
||||
|
||||
除了管理对组织本身的访问权限之外，还可以单独管理对组织的存储库、项目板和应用的访问权限。 有关详细信息，请参阅“[组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”、“[组织的项目板权限](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)”和“[管理对组织应用的访问权限](/organizations/managing-access-to-your-organizations-apps)”。
|
||||
You can invite an unlimited number of people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
|
||||
|
||||
为了简化访问管理并增强协作，可以创建能体现组结构的嵌套团队，具有级联访问权限和提及功能。 有关详细信息，请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
|
||||
In addition to managing access to the organization itself, you can separately manage access to your organization's repositories, project boards, and apps. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)", "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)", and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)."
|
||||
|
||||
可以通过管理设置（例如限制成员可以创建的存储库类型）来配置组织以满足组的独特需求。 有关详细信息，请参阅“[管理组织设置](/organizations/managing-organization-settings)”。
|
||||
To simplify access management and enhance collaboration, you can create nested teams that reflect your group's structure, with cascading access permissions and mentions. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
|
||||
|
||||
若要强化组织的安全性，可以强制实施安全要求并查看组织的审核日志。 有关详细信息，请参阅“[确保组织安全](/organizations/keeping-your-organization-secure)”。
|
||||
You can configure the organization to meet the unique needs of your group by managing settings, such as restricting the types of repositories that members can create. For more information, see "[Managing organization settings](/organizations/managing-organization-settings)."
|
||||
|
||||
{% data reusables.organizations.org-ownership-recommendation %}有关详细信息，请参阅“[维护组织的所有权连续性](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)”。
|
||||
To harden your organization's security, you can enforce security requirements and review the organization's audit log. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
|
||||
|
||||
To learn how to use organizations most effectively, see "[Best practices for organizations](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 关于功能可用性
|
||||
## About feature availability
|
||||
|
||||
{% data reusables.organizations.organization-plans %} {% endif %}
|
||||
{% data reusables.organizations.organization-plans %}
|
||||
{% endif %}
|
||||
|
||||
## 组织和企业帐户
|
||||
## Organizations and enterprise accounts
|
||||
|
||||
{% ifversion fpt %}企业帐户是 {% data variables.product.prodname_ghe_cloud %} 的一项功能，该功能让所有者能够集中管理多个组织的策略和计费。 有关详细信息，请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)。
|
||||
{% else %} {% ifversion ghec %}对于属于企业帐户的组织而言，计费在企业帐户级别进行管理，而计费设置在组织级别不可用。{% endif %}企业所有者可以为企业帐户中的所有组织设置策略，或允许组织所有者在组织级别设置策略。 组织所有者无法更改在企业帐户级对组织执行的设置。 如果对组织的策略或设置有疑问，请联系企业帐户的所有者。
|
||||
{% ifversion fpt %}
|
||||
Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
|
||||
{% else %}
|
||||
{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
|
||||
|
||||
{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %}有关详细信息，请参阅“[创建企业帐户](/admin/overview/creating-an-enterprise-account)”。
|
||||
{% 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-accounts.invite-organization %}
|
||||
|
||||
{% endif %} {% endif %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 组织的服务条款和数据保护
|
||||
## Terms of service and data protection for organizations
|
||||
|
||||
实体（如公司、非营利组织或集团）可同意用于其组织的标准服务条款或公司服务条款。 有关详细信息，请参阅“[升级到公司服务条款](/articles/upgrading-to-the-corporate-terms-of-service)”。
|
||||
An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -16,6 +16,7 @@ topics:
|
|||
children:
|
||||
- /about-organizations
|
||||
- /about-your-organization-dashboard
|
||||
- /best-practices-for-organizations
|
||||
- /creating-a-new-organization-from-scratch
|
||||
- /accessing-your-organizations-settings
|
||||
- /customizing-your-organizations-profile
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ topics:
|
|||
- Repositories
|
||||
children:
|
||||
- /about-repositories
|
||||
- /best-practices-for-repositories
|
||||
- /creating-a-new-repository
|
||||
- /creating-a-repository-from-a-template
|
||||
- /creating-a-template-repository
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 关于自述文件
|
||||
intro: 您可以将自述文件添加到仓库，告知其他人您的项目为什么有用，他们可以对您的项目做什么，以及他们可以如何使用。
|
||||
title: About READMEs
|
||||
intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
|
||||
redirect_from:
|
||||
- /articles/section-links-on-readmes-and-blob-pages
|
||||
- /articles/relative-links-in-readmes
|
||||
|
|
@ -14,31 +14,25 @@ versions:
|
|||
ghec: '*'
|
||||
topics:
|
||||
- Repositories
|
||||
ms.openlocfilehash: 7a18ed7051b0babdb5408821ce44a728968869d5
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148108763'
|
||||
---
|
||||
## 关于自述文件
|
||||
## About READMEs
|
||||
|
||||
您可以将 README 文件添加到仓库来交流有关您项目的重要信息。 自述文件以及存储库许可证、引文文件{% ifversion fpt or ghec %}、贡献指南、行为准则{% elsif ghes %}以及贡献指南{% endif %}传达了对项目的期望，并有助于管理贡献。
|
||||
{% data reusables.repositories.about-READMEs %}
|
||||
|
||||
有关为项目提供指南的详细信息，请参阅{% ifversion fpt or ghec %}“[为项目添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和{% endif %}“[设置健康贡献的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
|
||||
For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
|
||||
|
||||
自述文件通常是访问者在访问仓库时看到的第一个项目。 自述文件通常包含以下信息：
|
||||
- 项目做什么
|
||||
- 项目为什么有用
|
||||
- 用户如何使用项目
|
||||
- 用户能从何处获取项目的帮助
|
||||
- 谁维护和参与项目
|
||||
A README is often the first item a visitor will see when visiting your repository. README files typically include information on:
|
||||
- What the project does
|
||||
- Why the project is useful
|
||||
- How users can get started with the project
|
||||
- Where users can get help with your project
|
||||
- Who maintains and contributes to the project
|
||||
|
||||
如果将自述文件放在存储库隐藏的 `.github` 目录、根目录或 `docs` 目录中，{% data variables.product.product_name %} 将识别自述文件并自动向存储库访问者显示。
|
||||
If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
|
||||
|
||||
如果存储库包含多个自述文件，则按以下顺序从各位置中选择显示的文件：`.github` 目录，然后是存储库的根目录，最后是 `docs` 目录。
|
||||
If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
|
|
@ -46,28 +40,30 @@ ms.locfileid: '148108763'
|
|||
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
## 为 README 文件自动生成的目录
|
||||
## Auto-generated table of contents for README files
|
||||
|
||||
对于仓库中任何 Markdown 文件（包括 README 文件）的视图，{% data variables.product.product_name %} 将自动生成基于章节标题的目录。 您可以通过单击渲染页面左上侧的 {% octicon "list-unordered" aria-label="The unordered list icon" %} 菜单图标来查看 README 文件的目录。
|
||||
For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %} menu icon at the top left of the rendered page.
|
||||
|
||||
|
||||
|
||||
|
||||
## 自述文件和 blob 页面中的章节链接
|
||||
## Section links in README files and blob pages
|
||||
|
||||
{% data reusables.repositories.section-links %}
|
||||
|
||||
## 自述文件中的相对链接和图像路径
|
||||
## Relative links and image paths in README files
|
||||
|
||||
{% data reusables.repositories.relative-links %}
|
||||
|
||||
## Wiki
|
||||
## Wikis
|
||||
|
||||
自述文件应仅包含开发人员开始使用和参与项目的必要信息。 较长的文档最适合维基。 有关详细信息，请参阅“[关于 Wikis](/communities/documenting-your-project-with-wikis/about-wikis)”。
|
||||
A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- [添加文件到存储库](/articles/adding-a-file-to-a-repository)
|
||||
- 18F 的“[将自述文件设为可读](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)”{%- ifversion fpt or ghec %}
|
||||
- “[添加‘在 GitHub Codespaces 中打开’锁屏提醒](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)”{%- endif %}
|
||||
- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)"
|
||||
- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
|
||||
{%- ifversion fpt or ghec %}
|
||||
- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
|
||||
{%- endif %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 依赖项检查
|
||||
intro: 通过依赖项审查 API，可在将依赖项更改添加到环境之前，了解这些更改以及它们的安全影响。
|
||||
title: Dependency review
|
||||
intro: 'The Dependency review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.6'
|
||||
|
|
@ -10,15 +10,8 @@ topics:
|
|||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 64cb77b737927e8d44315fd40b51f68c77c50c54
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147064872'
|
||||
---
|
||||
## 关于依赖项审查 API
|
||||
|
||||
{% data reusables.dependency-review.dependency-review-api-beta-note %}
|
||||
## About the Dependency review API
|
||||
|
||||
通过依赖项审查 API，你可以在将这些更改添加到环境之前了解依赖项更改以及这些更改的安全影响。 可以查看存储库的两次提交之间的依赖项差异，包括具有已知漏洞的任何版本更新的漏洞数据。 有关依赖项审查的详细信息，请参阅“[关于依赖项审查](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)”。
|
||||
The Dependency Review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
|
|
|
|||
|
|
@ -1,13 +0,0 @@
|
|||
---
|
||||
ms.openlocfilehash: d1a631c8bcd74e56e3bd849292180f341f0ee75e
|
||||
ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: "147876045"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
注意：依赖项审查 API 目前处于公测阶段，可能会更改。
|
||||
|
||||
{% endnote %}
|
||||
Загрузка…
Ссылка в новой задаче